All Activity

I see it the same way as many others. There likely won't be a Calypso 2026 version. But perhaps a really good 2027 one instead?

I usually use Plane point - forcing vectors to nominal.

Make group of elements from those points, then you can easily do deviation on all points through this group. Or you can make cloud of discreet points from selection, where you select actual points ( green one ) - now you can make surface profile not from mesh, but this cloud and it will show you this coloured map only from those points. It's a question what you need.

Hello everyone, I am relatively new to Calypso but already have some experience with other CMM software. I would like to measure a simple dimension AB (see the attached photo). This dimension involves an angle, but that shouldn't be an issue in Calypso. To measure this distance, I follow these steps: 1- Create points A and B. 2- Configure clearance and retraction settings based on the geometry. 3- Create another point near A and construct a line. 4- Measure using the "perpendicular" function (between B and the previously created line) and select the "depth" option. Do you agree with this approach so far? If so, my question concerns how points A and B are captured. I have the choice between "Touch Point" and "Space Point." I should mention that I do not have a CAD model. With "Space Point," the AB dimension can vary significantly just by slightly altering the direction of the i, j, and k vectors. Which point capture method do you recommend for my application? I hope this is clear. Thanks for your help.

Greetings, I've scanned my part, RPS aligned it with my cad. Completed a general surface comparison. Now i want to call out variation for CAD points already on the model. How is this done? thx in advance

I didnt even notice I did that. Oops

Hello Here is link to knowledge base article to troubleshoot connection error https://portal.zeiss.com/knowledge-base?id=454224

The button is there when looking at the head in person and closer, but it is definitely not sticking out far.

We have done all that plus and it still does not want to work. Thank you.

https://portal.zeiss.com/knowledge-base?id=1572078

@Robert Kessell It looks like you need to replace this https://shop.metrology.zeiss.com/rds-sensor-mount-for-18-pin-vast-xxt-zid620670-9550-000 as the black button that acts as a manual release is either damaged or broken. With it damaged, it will cause it to be removed from the head much easier than it should be.

Rich - this is incorrect. The length is taken from the left hand dimension that you have marked NO.

ZEISS Portal This shows defining probe length being taken from the adapter plate.

Once you turn on Rotation, the Translation switches from X/Y individually to Translation that encompasses both - so you will have both checked in this case - Rotation and Translation.

Yes - you can use STL data for GearPro inspection, but most would advise against it as you aren't typically going to be able to scan it at a high enough accuracy.

Unfortunately I ran into a problem: If I use the command that queries tableFileChr in a new inspection plan where no custom path settings for the table file have ever been made, I get a PCM error (attribute not allowed). I guess it's because the Dictionary "outputFileDefinition" is either empty or doesn't contain an entry for tableFileChar. Is there a way around this or can I query this condition somehow?

This makes me think that after pickup, the magnets are not raising the stylus up high enough to pass the locking tang. This locking tang will catch and cause the stylus to stay in the pocket that could result in what is occurring with your system. I would suggest re-establishing the Master Probe length. If the Master Probe length is not correct, it will cause exactly what is happening when retrieving a stylus.

This explains the reason for this entire post (Read my initial post). Thanks to all.

I had another idea. Is it possible to evaluate 3d scan data from Zeiss inspect or other point cloud data in GearPro or is it only possible to evaluate points measured with GearPro? If I could import a point cloud into GearPro I could create a point cloud from the model and evalute that instead of real scanning data.

I have also just put in a ticket to Zeiss, but hoping I can get some help on how to remedy this. Thank you all for looking and helping.

I am hoping someone can give me a hand. My boss is up my butt trying to get this figured out and I have no idea where to start. We have been having a problem lately with retrieving probes from the rack on our Contura G2. It will try and get the probe, but it is almost like it is getting stuck and when it tries to move back out from the rack, the probe gets stuck and rotates the head of the machine. If it manages to move out from the rack, the entire head is loose and almost falls off the machine onto the table. See pictures of what happened just this morning. We re-aligned the probe rack, picked up all the holder locations and all, but cannot get this to work. PLEASE HELP. Thank you.

i've change the RJ45 cable between CMM and the computers, the old one was maybe a quarter of century years old, and doesn't clip anymore, wait and see...

The settings-per-user assumption is correct. We use a workaround where Autorun doesn't start automatically, but as soon as an operator opens it, the *.arn is automatically loaded. To set this up, we first make the setting as shown in the screenshot above (with path to *.arn entered), then switch back to "Start with Calypso". Now when Autorun is called, it automatically loads the *.arn from the path field. All of this has to be set up idividually for each user. And there are numerous occasions where the setup is reset for some reason, like after certain updates or so.

Hi , two times monday and one time this morning, i've a crash on the CMM, lost connection and the head very slowy goes to left and down through the marble. InterfaceGetSpoll : Connection reset by host (WSAGetLastError : 10054) do you know something about this problem ? I put the log in attached piece. rapport d erreur.txt

You can have a look here for the applicable standards. https://dgq.de/fachbeitraege/iso-gps-matrix-modell/