All Activity

We've been seeing this consistently since upgrading to SP4. While working in the CAD window, surfaces, edges, or other entities will suddenly disappear for no apparent reason. Sometimes changing the view, rebuilding, or reopening the CAD model brings them back, but the issue keeps coming back. A few things we've noticed: Happens on multiple parts and CAD models. Doesn't seem tied to any specific action. Missing entities are not actually deleted, just no longer displayed. Reopening the file may temporarily fix it. The issue is frequent enough that it's becoming a real frustration during programming. At first, I thought it was something specific to a CAD file, but after seeing it across multiple jobs, it feels more like a bug in SP4. Just wondering if others are seeing the same thing and if anyone has found a workaround or heard anything from ZEISS about a fix.

I also found "decimalUnits" in "inspset" file. I have no enough test data to see if you can set different decimal places for each characteristic. What i see in Calypso - when i enable view of probe, then i see probe in views even in programs which it was not enabled. So perhaps if it's not set, then some programs can have different settings and it is stored as "default" so any other program, which is not set inside it will use that settings.

getActualInspectionDir()+"\Logs\"+getRecordHead("planid")+"_"+getRecordHead("date")+"_"+getRecordHead("time")+"_"+"PartNo." +" "+getRecordHead("drawingno") Try the above

verified it in inspset file, the inLengthUnit is in mm, there is no inDecimalUnit. verified it in the program under characterisitics it is also in mm and 3 decimal places. still can't figure out where is the 4 digits coming from once in a while.

Adam, This is a generic crash error, from this alone the cause can not be determined. However It maybe due to using an updated Windows 11 machine with an older version of the INSPECT software. Please see the link below for details on that issue and what can be done to resolve the issue. https://www.zeiss.com/metrology/en/software/software-information-hub.html If that doesn't resolve your issue you will need to pull a GOMSIC and enter a support ticket. https://portal.zeiss.com/knowledge-base?id=3047314

You will create a Surface Profile characteristic for each surface; next, in one of the Surface Profiles you will turn on the CZ/SIM; finally once the CZ/SIM is activated you can select all other Surface Profile and/or Positions that should be linked to that CZ/SIM.

Getting this error when launching software, can someone advise?

Hallo Messtechniker, habe eine Frage zur Flächenform mit der SIM Angabe. Die linke und rechte Fläche müssen gemessen und über Bestfit eingepasst werden. Dann wird für die linke und rechte Seite die Flächenform mit einer Toleranz von 0,15 ausgewertet. Die linke und rechte Fläche werden dann gemeinsam auf Grund der SIM1 Angabe ausgewertet. Nun zu meiner Frage. Wenn ich die Flächenform öffne und CZ anwähle erscheint auch die SIM-Angabe. Wie bekomme ich aber die linke und rechte Fläche in das Messelement? Danke!

In file "inspset" there is: "inDecimalUnit" (integer) - number of decimal point "inLengthUnit" (string) - mm/inch If it's not there, then it can take that from system settings. If you want to have that fixed, then go to characteristic editor and force this settings of units.

I have a program that is running for ages without issue. Recently, for some reason the number of decimals in the report becomes 4 digits instead of 3 as it is in mm. Some days it reports in 3 some days 4. Not all programs on this cmm does it. The program was set in 3 digits as well as the cmm system settings environment. Any reason for this, and how to fix it? using Calypso V.6.8 if this helps.

I see that error all the time. Most of the time cleaning both the adapter plate contacts and the contacts on the probe head with contact cleaner solves it for a while. I've never had one stuck completely. Usually just doing manual pickup after the error recognizes the plate. I have ID Chip recognition disabled, don't know if that makes a difference.

@Richard Stanich I would assume that probe will travel to +X safety edge, then go down to point's Z origin + safety distance, then do to point's XY origin and scan from -Z.

Meiner Meinung nach verursacht die Pflege der Autorun-Oberfläche einen hohen zeitlichen Aufwand. Bei jedem neu erstellten Programm ist ein zusätzlicher Upload auf die Autorun-Oberfläche der Maschine erforderlich. Gleiches gilt für Programme, die aufgrund von Indexänderungen oder anderen Änderungen angepasst werden müssen. Diese müssen ebenfalls erneut hochgeladen werden. Gibt es hierfür eine effizientere Vorgehensweise oder nutzen wir den Prozess aktuell nicht korrekt?

What is the axis of travel for the point? If the point is intended to move in -Z (k) and the axis of travel is -1.000 in X (i), it will move in X and not Z.

I first wrote it directly in the File Selection Formula (as shown in the post image), and then tried to create a variable in the pre-program parameters. However, both didn't work. Weirdly enough, today it works for one curve out of two in my program. They have exactly the same method of import.

I’m starting to get the feeling that the 2026 version (8.2.00) won’t be released and Zeiss will launch the 2027 version (8.4.00) instead.

This works elsewhere in my program. Short circle paths running each direction over a scribe, pulling a min feature point, recalling that data into a theoretical point and using that point as a clocking feature in an alignment, using that alignment to take a centered probing point in the scribe. however in this case the prob touches the part at the scribe line and travels until it falls off the part. If I drop the jog down to stop it, it takes a prob point where it stops. I don't know why its traveling once it makes contact with the part but everything appears to function the same as my other clocking feature that accomplishes something similar. One oddity I see is that even though the new alignment has the min theoretical point as its planar rotation, on my CAD it shows the the alignment trihedron still the same as my base alignment and shows the nominal point to be taken in that axis's 0 even though the feature is at about 45° from that axis and the probe makes contact in the correct location. The other feature I'm doing this on also as the same oddity but works fine. Has anyone run into this or have an idea of what could be causing it?

I didn't purchase this, but I was under the impression this was the way to purchase the digital cookbook: https://www.zeiss.com/metrology/us/services/zeiss-academy-metrology/training-details.html?id=8e6fffb3-0d51-409b-a9ed-9d7df603a842&type=E_LEARNING_TRAINING

Can you install the app on a PC?

Yes, I want a free digital copy and I want this back.

The app is only available through the Google Play store (no iPhone support at the moment). If you're on your smartphone, it is listed under the Books section, not Apps. For reference: https://play.google.com/store/books/details/ZEISS_Academy_Metrology_Cookbook_Measuring_Strateg?id=igUmDwAAQBAJ The PDF Levan sent was the free sample also found on this page.

Hello Chad. I have attached PDF of cook book. Hope it Helps you cookbook_measuring_strategies_en.pdf

I was informed that PDF copies no longer existed and that the cookbook is only available via the App store. A tragedy.

You should be able to tell them what you want and do not want without issues. Chances are that your original licenses had these "extras" you show and now maybe the time to weed them out.