All Activity

And to add to the confusion: what exactly is out?????????

I have requested multiple things for Inspect, but I do not see any feedback from Zeiss. These were posted all the way back in 2024. https://portal.zeiss.com/my-voice/software/metrology/product/eaafdea8-9296-485d-82c1-cc6d1ca0eca2/request/c3051e15-87d9-436b-a489-1b142d7d6559 https://portal.zeiss.com/my-voice/software/metrology/product/eaafdea8-9296-485d-82c1-cc6d1ca0eca2/request/f0335067-2822-4b52-8912-fd2c2f43d696

Hello, Please share this request to the My Voice portal. https://portal.zeiss.com/my-voice/software/metrology

Please, please, please stop this behaviour.

I believe these diameters are being pulled from within the GD&T engine position characteristic and there is no option to mark those diameters

I think there's no way to do this with normal Calypso, although the controller itself would of course be capable of moving the CMM along a helix path when receiving the proper commands. May I ask why you need this?

Can you mark the diameters? In Multi Report button there is a button on the top right to mark characteristics. Then when you mark them you need to check the box that says "Hide (Selected characteristics are not displayed)" Which is also in the multi report window. I don't know if that fixes this issue but it does exclude things from the report.

Hello, Here are some troubleshooting articles that might help: https://portal.zeiss.com/knowledge-base?id=1105843 https://portal.zeiss.com/knowledge-base?id=1047524 https://portal.zeiss.com/knowledge-base?id=882615

Matt, What is the purpose of scanning in mid air?

I may be reading this wrong, but why do you want to air scan a feature that isn't there?

Hallo zusammen, bei uns wird der Winkel NIO bewertet (zumindest der rote Balken) obwohl er in Toleranz ist. Kann man das irgendwie einstellen? Wenn ich die Ausgabe auf Dezimal umstelle, ist der Balken grün, liegt also am PiWeb-Protokoll. MfG, Micha

Say what you will about AI, but it is absolutely fantastic at spitting out python to deal with folders full of excel files. It has been a game changer (And I already was a python programmer!)

@Daniel Nutka thanks, I tried that also, but it still needs first point to probe and while scanning stylus won't drop down.

If I remember correctly, this can only be done with the option "FlyScan", which used to be available only for the VAST XT heads, but should now be also available for the XXT head, but I'm not 100 % sure. And even with FlyScan, I doubt that it would work with helical paths.

Relogin after change

Hello, Does anybody know any solution to make a probe follow the path without touching the material? I would like to have a helix path around an imaginary sphere (like image below) but I can't create Sphere with strategy "Helix Path", because machine is looking for a material and it ends up stopping the "measurement". The only way of making it work is to create a Point with strategy "CMM position" and formula for X, Y and Z, but machine is moving in "step-mode" (achieve first point and stop, achieve next point and stop) instead of smooth, continuous motion.

how i can acess this page im on switzerland and nothing appends when i open the link

Hello Benjamin, this has been intentionally changed with CALYPSO 7.6.08 by development. The "identifier" alone will not be shown unless a Characteristic has been selected as well. Sorry for the inconvenience. Best Regards Marcel

Hi Robert I noticed - but could be wrong - that your XXT head lock looks like it is pressed in. If correctly noticed your XXT head will fall off when turning for a new position as only magnets hold it in place. Find some small pliers and pull the lock outwards to lock the head.

What is the solution, im very interested to applz cookbook strategies directly on features.

not sure is gear pro has this option, worst case you could try to covert roll angle -> diameter or roll length and 'transform' your tolerance, although not ideal I realize. Alternatively you can draw raster tolerance lines at those °of roll for a visual check, I've definitely had to do that in the past.

😄😅🤣 I'm still waiting for when we can apply cookbook setting to Features too (as an option), and before any features are made in the program, not AFTER !, you know .... SMART !! I'd reach out to your local zeiss guy they may have a solution for you...😉

If you constrain the vector, you are forcing it to the nominal vector of the alignment that it lives in - very dangerous imo.

I'm not certain how you have your presetting setup, but an FYI for Curve is that the Import to CNC means the following: "The nominal values of the curve and, if necessary, also its tolerances, will only be determined during the CNC run on the basis of the selected file." I have a pretty complex PCM program that checks some "dimensions" and then determines what variant it is running from those "dimensions". The way it works for me is the following: I have (3) check features. After those the first real feature has pre-settings. In this case you can see that the slot1setNo variable is what is set to which set or variant this particular group of features belongs to. Inside of the curve it looks like this: It will only change and read the new file once it is all executed, but I have confirmed that this works with no issues. Let us know more about how you have this setup, and maybe we can identify what is happening.

For Cone angle I would capture the cone with either line scans or helix path with start/stop about 20-30% from the edges. (this is to avoid surface finish from affecting angle readings) Second thing automatically go and constrain normal vector for the cone in the feature evaluation and then just report either cone angle (included) or half cone angle If you constrain the chamfer plane (it constrains it normal to the alignment it was captured in to say it's perfect to that alignment) then you are essentially checking your top plane to the alignment of the part. The cad eval issue might be the magnification factor way too high (or possibly set to auto)