All Activity

It's Windows 8 of CMM software. For me, the service packs did improve from completely unusable to practically useless. Collision detection doesn't work at all even if entire stylus system and column go thru the part. Importing SSC files is borked (ignores probes, tip numbers, messes up vectors, adds non-existent probe with number "0"). Tried a completely new PC with no Calypso on it before to start completely fresh - still the same issues. The problem is - I don't believe the next version will be much better.

I would suggest to disable "reconnect during system start" on both machine tabs if you have it enabled on the other. If Calypso crashes and you restart it with a different sensor than the one selected to reconnect, it's very annoying and can cause problems.

Hi Team, I am currently performing a tensile test on a cylindrical specimen and using the available tensile test analysis script. However, I noticed that the script is designed only for rectangular and elliptical specimens. Could you please let me know if there is an existing script available for cylindrical specimens? If not, I would appreciate guidance on how to correctly define the cross-sectional area of a cylindrical sample for accurate stress calculation within the current framework. Thank you for your support.

It can be safely turned off. This used to be an issue with older 8-bit controllers, which were full of temperature-sensitive electronics. In modern control systems, keeping them powered on continuously makes no sense—it only accelerates the aging of the electronics.

I do. I use it quite a bit for family of parts programs. Same geometry, only size changes. I have a template program with all the code I need. I just have to make some minor changes to accommodate different parts.

I just want to know for future: Do you have pcm?

Make sure to close Calypso first. And yes, if it ever prompts you talking about about the current sensor being different than the previous, click NO otherwise it will wipe everything. Painful, I know.

Just received our new Contura, it has an RDS-XXT and a Vast-XT gold sensor. I was shown how to switch the sensors but it cannot be correct. I am getting a multitude of errors and I have lost all styli twice (I didn't learn the first time). In the CMM configuration settings/Control, they made 2 Control Types, Contura_XT and ConturaRDS. I have to switch between the 2. Current Steps. Turn off controller at Joystick, Remove sensor, Insert other sensor. Open CMM Configuration/Control, select the correct Control type then select Initialize-Connect. Does anyone have a procedure that works for swapping Sensors? Running Calypso 2025.

How come these two essential functions in script programming have been eliminated? Step-by-step play no longer exists, nor does the on-line pause with F9! Can I have some clarification? Thanks

The ATOS is a very good sensor, and the accuracy is mind blowing.

I've created programs on oversized parts in the past using additional alignments and an extra CAD model to get it all in one shot. 1. Import your CAD model and establish your start/base alignments as normal. Program the features you need from the first setup on this model. 2. Import a second copy of the CAD model, translating and rotating to the same orientation except space it apart from the original in your desired axis (normally I do X+ shift a few inches). It won't matter how far you place it since we will manually pick it up on the machine. 3. Now when you want to establish your second setup, pick a few features that can be utilized in both setups (think plane, line, circle near the center of the part) and create a simple start alignment from the resources menu (Resources > Utilities > Alignment). Pick these features on your secondary CAD model. Be sure to to set these features to MAN mode under (Features Setting Editor > Man CNC Mode). These features will reference the Base Alignment. Be sure to add a programmable stop and move the probe to a safe position on your final feature before these manual points. 4. Now that the secondary start alignment is done, redefine your setup with a more robust alignment (typically I call this a secondary base alignment). You will use the second start alignment as your reference workpiece alignment. This will be CNC mode. 5. Program your remaining features on the second setup/CAD model. If you have dimensions that require data from both setups you can use Result Elements to calculate them (ex. overall length can be calculated taking the length from the front edge to a hole in the center and the rear edge to that same hole). Ideally the run will look like this: 1. Set the part up on the machine. 2. Establish your start alignment, run the first side. 3. Probe clears to safe distance. 4. Move part to new location. 5. Take second start alignment, run second side.

Success! Thanks again Jens!

I got it figured out. It makes sense now that the ACSII points would pull from the alignment instead of the reference plane used for slicing. I find more interesting stuff in the software every time I play with it. So far, I've been very impressed with the ATOS III. We inherited it for free when our affiliate shut down, and I've already found tons of use cases for it. And its shockingly very accurate, even when compared with our Micura's and Accura's. I really like this thing and already want more.

Hi, i am looking for a way to obtain internal icons like "mesh", "clipboard" and others and use them on buttons or as image. I am working on app to load measured data into project - similar to what Calypso is able. Thanks for hints. ( I have found a file containing svgs, but can not find right one )

make sure, that you have the needed probe changed in do you have pcm? plan->Advanced->PCM Editor copy the code into the editor, mark it, and press the calculate-button (an arrow inside a gear-wheel) without pcm you can write a small program (with your master probe) with two characteristics with conditions. in them just write something like setNewGeoStatToActualProbe(0,0,0,0,0,-1)=="GG" and setNewRadiusToActualProbe("2.5")=="gg", select "yes" for end program, and run that program offline

Thank you Jens. Where do I insert this code?

Hard to say, this was a legacy program written around 2016 or 2017.

Another try (other part) without succes, I 've done a large surface of recovery, projection of the two circle, put Z points in first, and the CMM mesure the Z point , and try to mesure the first diametrer 1cm beside this position. I have no guide when I move the part, Have I to respect the spatial rotation of the first Alignement, does it matter if I move the rotation slightly ?

I am not sure if that helps, but we have updated the zeiss-inspect-api wheels on PyPI: For ZEISS INSPECT 2025: zeiss-inspect-api 2025.4.0.398 For ZEISS INSPECT 2026: zeiss-inspect-api 2026.3.0.984

At my planner seat with vast XTR I can change the vector.. but you can try with PCM: setNewGeoStatToActualProbe(0,0,0,0,0,-1) setNewRadiusToActualProbe("2.5") that should work

I use Navigator on our small parts (they´re all small) only at cylinders and circles, only with big tolerances, and only while tangential probing for speed and angle range. I set the number of points by myself, to make sure, that my filters fit

Was möchtest du denn messen? Kreisbahn auf Ebene kann gescannt werden oder mit Einzelpunkte dann fährt das KMG den kürzesten weg außer man aktiviert den Fixierten Fahrweg dann nicht mehr. Wie gesagt nur bei Einzelpunkte. Wenn du Kreise in Bohrungen oder auf Wellen machst fährt das KMG immer in Kreisbahnen ob Einzel oder Scanning.

We are not using it, but i would imagine when you want to reduce measuring time, that you will tryout where you can speed up.

I don’t use it much anymore, I used to but trust it but I took another path. I run the part, features/ characteristics set to the Cookbook, then increase the speed slowly, if needed, until I get an unsuitable variation from my slower speed. In some shops speed and throughput are the focus, but accuracy should prevail. I’m willing to speed it up a little but won’t sacrifice accuracy over speed.

I think Navigator also has worse repeatability than the cookbook values for active heads, so I would only bother using it if I'm really short on time and have a wide enough tolerance band that the measurement variance isn't an issue.