All Activity

offset plane is theoretically perfect I believe. Just create regular plane from scans and check flatness before offsetting ?

Another place to check is your CMM END PARK POSTION there might be a Stylus/system in there that no longer exists.

I have scanned 3 circle paths on 3 planes and one is offset so I made an offset plane but when I try to get flatness off of them it come out as perfect even thought the individual planes have some form deviation. Any thoughts?

Good Morning/Afternoon/Evening Everyone, Wondering if anyone has an excel template for a type 1 study or Gage R on hand they wouldn't mind sharing. I was going to put one together but figured I'd ask the community. Thanks,

That was my next suggestion as well, this might cover any intermediate points that are mis-assigned, if you just re-assign all probes in the test editor...

Hello, could you try to set the profile globally, not only for Zeiss Inspect and revert the changes regarding the laptop GPU? It's in German but this is how it should look like:

i see CAD Interop Error on the bottom which has been an issue in some outdated service packs. After you've ensured that you are on the latest SP, does this issue persist?

You could try assigning a different stylus system and then changing it back, to try and overwrite any hidden problems 🤷‍♂️

could also be hiding in an 'intermediate point' in a strategy , perhaps you wont see that in the plan editor. I've had this happen occasionally while opening and reviewing strategies etc.

I have a program that has multiple mini plans. For one specific miniplan, I would like to include a process protocol in addition to the standard protocol. For all other mini plans, just the standard protocol. Is this possible?

Screen shot of used probes in the program, not showing this Combo86R-2 which is an actual probe.

Use a Flat Head M5 screw, you can cut the neck, if necessary, the flat head will hold the Disk easily and you won't have much protrusion at the head of the Disk.

I think only working solution would be modifying VB script in excel sheet. You can store those files where you want, but excel won't know where would they be ( i think that defining user path for CHR,... won't be used for excel ). Last option would be custom excel sheet or any language script/app

Moin Kollegen, Ich komme das erste Mal in die Verlegenheit Prüfprotokolle nach Excel exportieren zu müssen. Mein erster Eindruck: Ich bin wieder in den 90ger gelandet.... - Kann ich das Zielverzeichnis in dem die Exceldatei abgelegt wird dynamisch ändern oder ist das unveränderbar auf <Anwenderverzeichnis>/workarea/results - Die Rohdaten für das Excelmakro (*_chr.txt, *_fet.txt, *_hdr.txt) bleiben im Zielverzeihnis. Sind die automatisch löschbar? - Es wird excel gestartet und muss dann per Hand nach Programmablauf geschlossen werden. Kann man das automatisch schließen lassen? Eigentlich möchte ich von einem Prüfprotokoll nur die nicht markierten Prüfmerkmale automatisch in eine CSV datei exportieren und dann die Datei in einem Dynamischen Pfad mit eindeutigen Namen ablegen.... Irgendwelche Tipps wie das gehen soll oder lieber gleiche: Finger Weg?? Gruß Karsten

this answer of the dealer is that this disk with M5 is to assemble with an other stylus, for just a disk a have to take a bolt hold disk and a special screw with it. And for the calibration I think a standard calibration and take the first Z point on the edge of the disk instead of center.

Hello, I'll have to pass through a Ø50±0.1mm to mesure a inner diameter of Ø68E7 (65mm long) , for that I found on the web a Stemless Disks of Ø50mm, with a M5 threaded center, how can I assemble it, is it just with a standard screw on a standard extention ? and how I will calibrate it ? (I know how to calibrate a standard disk ) inquire if the thick of the screw will matter ? do you think about an other method / material to mesure this Ø68 ?

the actual calculation wasn't the issue. i know calypso can do it and report it for me: 4. Calculate the Volume In the Results or Analysis section, CALYPSO can compute the enclosed volume from the measured geometry. You can: Use the Volume function in the measurement plan to directly calculate the volume. Or, import the point cloud into a CAD/CAE tool (e.g., SolidWorks, NX) and use its built-in volume calculation. this is a partial screenshot from a google search. thank you.

@Greg Chesley Measure a point to point distance for the planes. This is your cylinder height. Measure the diameter of the cylinder. Volume = Height X π X Radius² and your result element unit should be cubic (³).

i need to report 'volume' of an inside cylinder out to a customer. i have 3 features, two planes and a cylinder. i just dont know how to group them together and report out volume.

Pretty sure that I did but I'll try it again. Thank you.

Did you have "Cancel CNC start" selected and program saved before adding the measurement plan to Autorun? If not, and you selected this after you had already added the measurement plan to Autorun you may need to add it again.

In "Define and Activate Limit Values" I have "Maximum permissible time...." set for 2 days. In "Stylus check during CNC start" I have "Cancel CNC start" selected. In Calypso, we get a message when the probes haven't been calibrated within that time frame. In AutoRun, it doesn't give us a message. If I close AutoRun and start Calypso it immediately shows the message when opening a program. Do I need to set something up in AutoRun for it to work?

CMM positions and start/end park positions are sneaky places where probes can be assigned, but are not visible via the Plan Editor.

I have checked the obvious, Measurement Plan Editor, no entries shown. I did find entries in "inspec" and "inspection" files. Editing those entries caused some weird problems (Altered the entries to be Combo86R). 😂 inspec file: inspection file: I could not find an "#identifier" within plus or minus 30 lines of the "Combo86R-2" line.

Please note that while the issue was first observed following the installation of Windows 11 updates KB5077181 and KB5074105, all subsequent Windows updates released since then (early 2026) have exhibited the same behavior.