All Activity

Still an issue.

2 years later and this is still an issue. Super frustrating. Sometimes I open Zeiss and Spacemouse settings are applied. Other times not. I only know how to use it with controls inverted so when it doesn't work and everything is backwards it is useless to me. On top of that speed issues are still really bad and inconsistent. Especially when my Spacemouse settings where I have these settings applied it is basically unusuable even if I could get used to everything being reversed from what I am used to. It seems like sometimes the only way to get it back working is restarting my computer and praying it works next time.

I will be working on a program on a pretty big part, 600mm long. The part is a rolled shell with side ledges that I need to measure roughly 400mm inside. The problem is our CMM is not long enough to clear the part within the CMM limits on the long probe I developed. Here is my plan to overcome this... 1. Start the program using a shorter probe for alignments. 2. Return the probe to the rack. 3. Move the machine head to the front of the part at the "load/unload location." 4. Manually load the new long probe. 5. Measure all internal features with the new long probe. 6. Return to the probe "load/unload location." 7. Manually unload the long probe. 8. Perform an automatic probe change and continue measuring the rest of the program. How should I approach this? I do have PCM. I need advice for #3, 4 & 7. Appreciate the help!

I have 5 ZCR 70 Holders with 5 XTR Plates that I had to remove from the CMM and clean them up because they are on a CMM that is on the production floor. When I put them back on the CMM and relocated each holder now, I have an issue where the Vast XTR Gold will load all 5 but will only store 4 out of the 5. Any ideas would be very much appreciated.

Both helpful replies, thank you.

Hi all, Do you know how to change this so the probe is indexing in the correct direction and it has the same XYZ coordinates ? I do not have the planner, so as you can see I can't click on Drag Base Alignment

File output can also be found under Extras-Settings-Environment now in CALYPSO 2025. This will control global settings for new programs.

I installed VS Code. It may seem like a step forward, but it's definitely not. It's missing a lot of things that are essential for programmers. I'd be so kind as to be contacted by someone in development, because this is a serious problem. Thanks Antonio

Thank you very much Norbert for the advice. P.

There's no ready-made function for this as far as I know. But you can use equidistant deviation labels and enter the spacing according to the desired angle in radian. The formula to calculate the correct spacing is Diameter * Pi / Number of Points

Sounds like you need PiWeb Reporting Plus and a Table Protocol or similar, which can pull multiple runs into one report.

Filters and outliers also play a part. If you're just using the Calypso defaults, then the raw data in the feature isn't getting filtered, and the characteristic is getting a random preset value. The majority of the time, proper filtering often doesn't make a big difference however the more form error there is in a feature, the bigger the impact. I've personally seen it make as much as 0.018+" (0.457mm) difference, although most of the time it's somewhere between 0 - 0.0015" (0 - 0.038mm).

I was not aware that it existed before your post 😂

To be clear, when you say protocol are you referring to the results of the measurement? If so, yes I need all parts ran individually on one report. I haven't used AutoRun yet but will try that out today. Is this also how you can run multiple parts on the table at once if it's the same part?

I'm going to give away my age here, but that's ok. Where the practice of removing styli from heads came from was way back with the first CMMs. Many were totally manual where the operator had to physically move the head around so the probe could make contact with the part. Some were hard probe, some were touch probe. There weren't any motors or joysticks, 100% manual. All 3 axis' would glide very freely on a cushion of air. The only thing an operator could do is lock or unlock each axis. What would happen then is at night when everybody was going home, the air compressors would get shut down and the air pressure in the lines would drop. If the Z axis in particular wasn't locked in position, the Z mast would drop and smash the stylus system. As CMMs became automated, the problem of the Z mast dropping went away, but the practice of removing stylus systems at night kept on for a long time. Now it's simply a matter of choice, but you still need to be aware when homing as others have pointed out.

Hi Don, Thanks, I 've made a try and thats work for me. I don't have the environment in CAD so , I think only one CAD should work. And I could use result element, or make a alignement with a forumula in the translation and use point recall for feature, that's do the same (for me). just a dummy question, why don't you use "base alignement match" ? thanks

The guide for VS Code requires version 1.64 or higher, unfortunately the official website released the latest version 1.112 on March 18, 2026. You are a bit confused as well as worsening!

You can use caliper disctance or two single disc touch points. But in both cases it is up to you to define the measuring direction. If the element shown is aligned, you can select X/Y/Z axis in the dialog, otherwise you'll need a reference element to define that direction. It will NOT determine the smallest distance automatically! You can also use caliper distance on sections, so it will only measure in the defined section plane.

I'd like to congratulate Zeiss on this huge step backwards! Are you asking for external help to use your software starting in 2023? I've written thousands and thousands of lines from GOM Inspect 7.0 to today, and you've struck a chord with me with this absurd innovation!! Was it expensive to leave the two features behind? Zeiss licenses aren't that cheap, though.

Hi Antonio, since Inspect 2023, it is possible to use Visual Studio for scripting: Using Visual Studio Code as an add-on editor — App Development Documentation Nanno

My CMMs are never stored with an empty sensor. I wouldn't allow it. One of them has not been stored empty in over 20 years. This guidance is misguided. VAST Gold. I have no problem leaving a system 60" OAL in the sensor over a long weekend. That said, we only turn our machines off 3 times per year at most so... I'd say that's also optional.

Remember that the primary datum in every single case sets the orientation of the coordinate system and therefore all tolerance zones. The X value in the feature is the location of the feature origin on the X axis in whatever alignment you're using. The x value in the position is measured parallel (or perpendicular, or at some specified basic angle, I can't tell) to the primary datum, not your alignment. It looks like that datum might be a derived centerplane which could make it virtually impossible to orient correctly on a surface plate. I'd use a CMM for this 😁

This is totally legit but poorly engineered. With a big tolerance like this I'd have no problem using that short cylinder though I agree it's an unstable datum. This is not a CMM problem it's an engineering problem. If you're supplying this to internal customers you're pigeon-holed into figuring out how the job should have been done. If your customer is external, I strongly suggest you give them what they ask for. Use position to evaluate coaxiality. Don't move the cost burden from your customer's engineering into your CMM lab. Yes, it will fail over and over and over again. Charge them for re-runs when they get the drawing right.

I finally got around to trying Shawn's fix. It worked exactly as suggested. PiWeb designer is obtuse and terrible. I love the statement from the cited KB article: "highlight the relevant table". Clear as mud. I figured it out. For reference, the code in Shawn's suggestion will hide the (M) line, the (L) line, and these additional diameters. Those of us already hiding (M) and (L) lines will overwrite that existing code with this.

It costs a person's salary and adds ambiguity. Not a fan.