All Activity

To use the Common Datum option, the feature must be plane or cylinder. Try creating the Datum C holes as cylinders instead of circles.

I’m still having trouble with bolt circles in the new GD&T. For items 6 & 26, the new engine will let me select -A- and -B-, but I can only select -C- after I’ve basically made a simple circle using the bolt holes (it’s not going to clock to a best fit). When I select common datum, all of the features disappear except for -A- & -B-. Is there any way to do this staying completely in the new engine, or am I stuck trying to adapt part of the old way?

Thank you! Found the actual issue was the setting "Do you want to check if there is enough scan data for your elements?" causing a conflict with the existing alignment process. Hopefully this can help someone out in the future! it's under acquisition template

I usually see that whenever you have element set to compute only in specific alignment. Find not computed alignment and investigate which element is not computed.

Good morning/evening When trying to perform an inspection, i keep getting this error. Every element in the project is recalculated besides some alignments, but can't perform those without a scan. Scan works normally if all measurement positions are highlighted and right clicking "measure at selected positions". Would like to resolves this issue as the program is scanning through four parts with four different scans that are all dependent on the Photogrammetry series which is always performed first. any idea as to what the issue could be? Specifications: Zeiss Inspect 2026 pro Photogrammetry>Scan 1> Scan 2> Scan 3> Scan 4 ATOS 5 5130 Scanbox with Co-bot Kind regards, -Yager

@Luke Cashman, no apologies necessary. Your participation increases engagement across the forum, and that's a win for all of us. Please keep posting about anything, anytime.

If you would rely on directional touch point in direction of probe, then it would be sufficient. If you plan to touch sideways of probe tip, then it may be not precise enough ( but tolerance is boss here - with tight tolerances is coverage needed ) But you can always do comparison with known fully calibrated probe and how much it differs.

Sorry I keep flooding this one topic with a lot of questions, i just don't want to flood the Calypso general forum. I did some basic trig and i think the max degrees i will be able to get with my new sphere will be about 100 degrees, will that be enough? I think technically i could do 110 but that's with 0 clearance so i think 100 would be pretty good, though i have seen before it is recommended to get 180 degrees for the qualification but will i see a dramatic loss in accuracy with only having 100 degrees?

Good morning Nanno, I seem to be having a similar issue where it seems the orange boundary box for the CAD is cutting out the majority of my mesh. Is the script the only way to fix this or is there a native setting within Optical 3D 2026 pro that can be changed? Kind Regards, -Yager

Yes, but not natively by cavity number. The most reliable method is to fixture the parts in known positions, use multipart scanning, and assign cavity IDs based on position. If the cavity number is physically marked on the part, a custom OCR/Python solution may be possible to automatically identify and sort them before generating the PDF report

Hello, Recent Windows 11 updates have been known to cause issues with certain versions of the software and how the PC is able to communicate with the hardware as well. I am glad you were able to get this resolved on your own.

@Richard Shomaker I had a connection issue with our CT sensor (Metrotom 6) awhile back (same error as you), after I had installed/uninstalled some third party software. What happened was during the install/uninstall of the third party software (for an industrial webcam), the services/registry keys required for communicating with the CT were stopped/broken. I had to go into the Program Files>Zeiss>INSPECT>*versionYear* and manually fire the services, like TomCtServer.exe, then go in the "xray_services" folder and fire the other needed executables. Once fired, the services were back running and they wrote whatever to the Windows registry that was needed and I was back in the game. I have never found the documentation for this procedure anywhere (I even had elevated Zeiss support in Germany stumped). Might be worth checking out.

Well I was finally able to get it to connect.... I had to completely reset the PC, and disable all Windows Updates temporarily.

So after doing more research, I learned about how there is a "manual" or "single points" way of qualifying probes instead of "tensor" or "six points". The probe i was questioning is set to manual which is likely why the "180" degrees i mentioned earlier doesn't actually apply. Is there a way to see exactly where these manual points are on the reference sphere besides just running the qualification? The whole reason i am doing this is because we have a custom probe that has been used (rarely, but still used) for years now, and i have just discovered it is wildly inaccurate (I picked up a point in the same spot with the 2 different probes, and it was .002 inches different than a trusted probe) and I am just trying to find out as much info as to what went wrong and how it has been qualified in the past to make sure I wont be making those same mistakes. Thanks!

@Emiljan Pregelj I got this Place this into "Template row (default) - Text attribute ${if(Equal(Qdb.Characteristic(2002,1),Qdb.Characteristic(2002, 2))) then Qdb.Characteristic(2002) else "→ "+Qdb.Characteristic(2002)} Now go to conditional formating - add condition "Not equal" and place this with selected font color ${Qdb.Characteristic(2002, 1)}

Hello, in general it is possible to access the current point selection of any surface element in Zeiss Inspect using element.selection.coordinate instead of element.data.coordinate More details are available in the documentation (Frequently asked questions — App Development Documentation) It is however not possible to store or restore this selection when recalculating the custom element, because commands can’t be executed from inside a service. This means that the element will not be parametric.

first I need to get a name to define the location then how to define this condition... everything is logical in this way but getting to a logical place where I could implement the logic-idea is not so easy

@Martin Krüger Or if you want to have it like you have drawn, then you would need to have report exported into excel. Also you would make report page with diagram, but that would make a page per characteristic. You can edit table by making fixed columns and rows, but that would be a very specific table just for one characteristic. I have also made extra column with diagram inside ( just lines without numbers ) which was able to display deviation

Vielen Dank, werde ich testen 🙂

Thank you Martin! 🥳 Greetings to Zeiss software development, bubble help on a button you cannot see isn't very helpful 🙂

@Martin Krüger I don't think you can do any other than have columns per stage or rows per stage Ok, so do this Go to report and edit table Edit report template Click on a first row and on bottom left is icon for adding a row - expand that button and check "Stage for a row" Do that for all rows and you will get this

Move mouse to the end of line from window of your 1st picture ( there is "?" on top ) It will show you what needs to be written

@Martin Krüger Can you post a sketch how your report should look like? Thanks

Hallo alle zusammen, ich versuche gerade den Protokollkopf anzupassen, allerdings bekomme ich es nicht hin, dass die Zeichnungsnummer und der Bauteilname angezeigt werden. Vordefiniert und angewählt sind sie, aber es erfolgt keine Ausgabe auf dem Protokoll. Das Feld Auftrag funktioniert hingegen. Was muss ich im PiWeb-Editor bei Zeichnungsnummer und Bauteilname eingtragen? MfG, Micha