All Activity

Hello ya'll, I was in need of a tool to mass create inspection points. I am using Zeiss Correlate on Photogrammetry data. I am using target markers. My projects all contain around 20 components, and the total target count is ~250. I could not find a way to get XYZ position data without creating inspection points, and I could not find a way to mass create these points through the Correlate program, so I created this app. I hope this helps someone else. If you know of something I could improve, or an easier way to achieve this - I am open to suggestions. I get the feeling that there is a button somewhere in the program for this already, because it seems like this would be a useful feature. Thank you! import gom array1 = gom.app.project.actual_elements array1 = sorted(array1, key=lambda e: str(e)) # Constructs and their number of points must be the same between projects, otherwise inspection point numbering will differ. for name in array1: if str(name) == "gom.app.project.actual_elements['actual_master']": continue if str(name) == "gom.app.project.actual_elements['all_measurement_series']": continue if str(name) == "gom.app.project.actual_elements['all_reference_points']": continue if str(name) == "gom.app.project.actual_elements['Analog input 0']": continue if str(name) == "gom.app.project.actual_elements['Analog input 1']": continue if str(name) == "gom.app.project.actual_elements['Analog input 2']": continue if str(name) == "gom.app.project.actual_elements['Analog input 3']": continue if str(name) == "gom.app.project.actual_elements['Analog input 4']": continue if str(name) == "gom.app.project.actual_elements['Analog input 5']": continue if str(name) == "gom.app.project.actual_elements['Analog input 6']": continue if str(name) == "gom.app.project.actual_elements['Analog input 7']": continue if "Point" in str(name): print("Operation Complete. Ending Script.") break print(name) print(name.data.coordinate.shape[1]) points_total = name.data.coordinate.shape[1] for x in range(points_total): if name.data.coordinate[0][1] is not None: try: MCAD_ELEMENT=gom.script.inspection.inspect_by_point (point={'id': x, 'target': name, 'type': 'coded'}) except Exception as e: print(f"Skipping {name}: {e}") continue

I dunno, it's vectors so.... 😛

@Norbert Bendl 2025 sp1

😂 that’s the wrong emoji.

That worked perfectly! Thanks🖕

Hi Martin, I also try that and I'm getting The Connection is blocked.

If you want to do this legally here would be my first suggestion: Measure (4) independent planes on the .050 surface: Create (2) Symmetry Planes (Features - Special Geometries - Symmetry Plane) from the (4) Planes Create (2) Position Characteristics for the upper tier. Turn on SIM Evaluation Create (2) Position Characteristics for the lower tier. Turn on SIM Evaluation

It has always been like this. I am wanting to see if anyone else is experiencing the same thing i am. And how they might have fixed it?

Hello all, I have a composite position call out with 0 tolerance using MMC. I understand that perpendicularity plays into this, but I also need to get orientation and position from 1 slot to the other. I have been trying to do this with bore pattern but have not yet been able to figure this out. I am using calypso 2025. Any help is always appreciated... Thanks

I tried this and it didnt work for me.

@AGH1977 As far as I am aware, the only actions that will automatically close the PiWeb report are saving the Calypso program, or if a subsequent PiWeb report is generated. Some things to poke around for - Any PCM calls at the end of the program? Any files (global or local) named measurement_end_pcm.txt, calculation_end_pcm.txt, inspection_end_pcm.txt, or report_end_PCM.txt that are causing the PiWeb closure through PCM? At then end of the program, when the popup shows "Report generating" or whatever it says, can you snapshot this before it closes and post that snapshot here? Is this new behavior or has it always been this way?

Minimize Calypso and it will popup again - but it's strange behaviour which i see often too

When i run a program the PiWeb report is visible for about 10 seconds and then it disappears. It is not on my task bar either, so i have to go in and go up to View and Multiple Report to bring it back up to view and save. Is there something that i am missing to keep the Report up and not disappear? Thank you for any information on this.

https://stackoverflow.com/questions/30011741/3d-vector-defined-by-2-angles This should be enough for understanding

ATOS Q 12m 170 should be sufficient, try adding more spray / additional measurements from various angles..etc. Improving data quality will go along way. You might want to try a different approach for inspection, sounds like you're trying to determine how much the form of that honeycomb surface deviates from a cylinder? Constructing an actual cylinder on a partial arc with that data will most definitely lead to poor results, touch point edges are going to be inconsistent too(unless you improve data quality significantly). I'd recommend aligning the part to CAD, creating a nominal cylinder from cad, roughly selecting the top of the honeycomb surface on the actual scan, then doing & Inspection-> deviation to geometry(select the 'nominal' cylinder). That should project all the points you selected perpendicular to the cylinders surface. you can then apply deviation labels at various nominal points. Hope it helps.

I am acccessing ATOS5 via it's IP - should be in the configuration.

Hi All, Need help troubleshooting this. Has anyone ever have an issue with Zeiss Hardware service that can't get to the Triple Scan on a Domain PC? I can get to 127.0.0.1:39025 but can't get to :39026. No Computers Policy apply. Firewall is off. no Endpoint install. On a Vanilla Win10, I can do all that without any issue. 1. Install Zeiss Quality Suite, 2. Install Zeiss Inspect hardware service, and 3. install Zeiss Inspect. Thank you.

Is there a formula to calculate the xyz vectors in the stylus definition? I have a prove at A90 B105, and I have not been able to find the correct vectors, As you can see the probes do not line up. Thanks for any help!🙂

Hallo ZueSt, das ist richtig, allerdings gibt es mehrere Gründe für den Fehler "Failed to log in". Die aktuellen Login-Probleme existieren seit letzter Woche und sind durch externe Einflüsse bedingt, s. aktueller Post im verlinkten Thread.

--- German version --- Durch externe Einflüsse auf unsere Infrastruktur kommt es derzeit vorübergehend zu Einschränkungen beim Log-In in die ZEISS Quality Suite. Unsere Experten arbeiten bereits an einer Lösung und informieren zeitnah. --- English version --- Due to external influences on our infrastructure, there are currently temporary restrictions on logging into the ZEISS Quality Suite. Our experts are already working on a solution and will provide you with information in a timely manner.

I know Robert Disser. 🙂 He told me about the "hidden feature" of qdas.bat, which allows to write a second QDAS file based on a second config file. Unfortunately it doesn't help in my case (because I can't invoke it seperately). I may contact him if I can't find a solution, but somehow I doubt there's yet another hidden feature like this.

Der erste Beitrag war am 21. Februar ??

You could search inside "inspset" and "inspection" files for links to a sab or sat file.

Thank you!