All Activity

I had found a work around, all you have to do is enter a legitimate part number in the search bar, then proceed to the portal home page.

I think you can do this with BAT file in inspection folder. Can be found in manuals 02_PCM - Reference: Names of external PCM files

Hi Mike, As far as i know this is not possible without to alter the SQL table(s). Every characteristic is stored with an uniqe item. Contact your local ZEISS support and ask them what to do. I am sure that Zeiss has a non-public tool for this. We run in the same issue sometimes after it was necessary to change the characteristic name...

Hi @GHE, which ZEISS INSPECT version are you using?

Moin, Ja, CALYPSO ist nicht Netzwerkfähig! Immer wieder gern gelesen... Wir machen das so, das alle Zeiss Maschinen ihre Programme von einem Netzlaufwerk mit gleicher Ordnerstruktur lesen. Nur wenn das gleiche Programm zur gleichen Zeit auf 1+n Maschinen läuft wird es ( nicht kann es ! ) zu Problemen mit den runtimedaten kommen. Eine Möglichkeit um festzustellen ob das Programm gerade benutzt wird wäre das anlegen eine lock-datei. O.K. nicht wirklich file-lock; aber annähernd. Das geht z.B. über inspection_start.bat in dem eine lock-datei angelegt wird. Über report_end.bat diese datei wieder löschen. Dann kann dein robocopy prüfen ob diese datei vorhanden ist und ein kopieren aussetzen und später noch mal versuchen. Wie gesagt: kein echtes file-lock aber ein bisschen besser als nichts. 🙂 Ansonsten können wir ja mal weitere 10 Jahre warten und schauen ob Zeiss sich in das 21. Jahrhundert bewegen möchte und netzwerfähige Programme auf den Markt bring. Gruß Karsten

SMA is a software maintenance contract.

Hi everyone, in Calypso, is there any way to force the opening of a file (notification, photo, instructions, information, etc.) before running a program? I know about the measurement cycle information tab, but it doesn't work for what I need. I'm asking for something that prevents a program from running without first viewing a file. Thanks.

Aktuell haben wir auf beiden Messmaschinen die Programme nur lokal. Leider kam es immer wieder mal vor, dass bei Veränderungen der neueste Stand nicht direkt auf die andere Maschine kopiert wurde. Besonders ältere Programme die selten benutzt werden sind unterschiedlich auf beiden Anlagen. Ich kann auch nicht alles auf den Server kopieren und von dort starten lassen, weil wenn ein Programm dabei ist, das auf einer der beiden Anlagen nicht eingefahren ist, dann krachts. Unsere Mitarbeiter sehen das nämlich nicht. Die starten einfach nur. Das hat Calypso meiner Meinung nach nicht gut gelöst. Weil wenn ein Basissystem nicht vorhanden ist, dann nimmt es einfach "vorhandene Ausrichtung" anstatt dass es sagt "Achtung das Programm wurde noch nicht eingefahren. STOPP". Und des manuellen Ausrichten sind sie nicht mächtig. Zumindest zum Teil nicht. Ausserdem kommt es meiner Meinung nach zu Problem mit den Protokollkopfdaten (wie zb. Maschinennummer, Spindel der Maschine, Teile nummer etc.) Wenn beide das gleiche Programm gleichzeitig vom Server verwenden. Weil dann würden ja beide zb. die angesprochene protheadpara (für Datenfelder) oder die protocol Datei (in der das Arbeitsprotokoll zwischengespeichert wird) benutzten. Wenn das keiner hier im Forum bisher so macht, dann glaub ich mach ich es so, dass ich das robocopy skript nicht automatisiert ausführe (also nicht täglich um 9 Uhr), sondern nur bei Bedarf. Also wenn ich ein Programm auf dem Server verändere, dann ruf ich meine Kollegen an, dass sie kurz das Skript starten sollen. Glaub so bin ich auf der sicheren Seite. Auf unseren anderen Anlagen klappt das super seit sehr vielen Jahren. Bei Programmstart werden die Daten in den Arbeitspeicher geladen, somit ist es auch egal wenn im Hintergrund die Programmdateien überschrieben werden. Beim nächsten öffnen des Programms ist es dann aktuell. Hatte die Hoffnung dass es bei Zeiss auch so in der Art klappt. Und in älteren Beiträgen hier im Forum wurde Robocopy auch schon erwähnt, aber nicht so detailiert beschrieben. Aber Danke trotzdem für eure Hilfe. Wenn sich doch noch jemand findet der so ein Skript verwendet, wäre es toll die Erfahrungen zu teilen.

Hallo Andreas, wie sieht denn eine "GUT" Messung aus?

Unfortunately, there is no such person, we are trying to solve all the problems ourselves.

This whole process is far more convoluted than it used to be

I often use plane point, because they are fixed in vector, but reports true XYZ values. Now i don't know what space point does, but i had either space point or another type and when i was manually probing this point it was reporting only in vector correctly, but i needed Z value ( was +Y ), which was reported as nominal.

Hello, We have an arc segment type of part that distorts after the machining operation (the radius becomes smaller). So, the model is a bit different than the physical parts. The print essentially calls for arc length. I've programmed this successfully using some construction features and math functions; however, when I first tried to program it, I tried doing profile points (space points), and that didn't work. I would like to better understand why the space points didn't work. Here is the strategy that I used to create the space points: Leveling: Measured the top of the part for the base plane (rotation about the X axis, rotation about the Y axis, and Z translation) Translation: Measure the radius of the part (obtain the center point of the part) for XY translation Rotation: measured a line on the right side of the part. Then, I intersected this measured line with the radius of the part. Then, I constructed a line from the center of the part to that intersection point. I used this constructed line for rotation. This is the same strategy that I used with my arc length math functions... So why do my space points read far out of tolerance when my arc length measurement great? The form of the part form (circularity) is within tenths. Could the "space point" method possibly be fitting a nominal size radius to the part when it finds that XY center point?

It appears there are some core misunderstandings here. Lets see if I understand and I can help clear it up. Based on what has been communicated, you want an OFFLINE/PLANNER seat to match your ACCURA installation. You do not need to do anything with your ACCURA. It remains exactly as is. You need 1 OFFLINE SEAT w/ PLANNER + CURVE. This will get you a 2025 license for CALYPSO (which is backward compatible to 2024). For license technology change reasons only, you need to ask for the 2023 license as well as this is compatible with 2013-2023. Once you receive your entitlement, install 2023 on your OFFLINE workstation. I believe you are in the UK. I cannot say how this handled there. What I describe above is how it would be handled in the US but there shouldn't be much difference.

ASME Y14.5 mentions datums should be of 'sufficient size', I would say Datum D single hole is insufficient size for a 'primary' 'leveling datum'. I would suggest using the outer face of D as a REF plane and measuring D as a circle, and position to those...only as a REF check, etc.

Yes, the hole in question is to be in-line (concentric) with the datum D hole.

Of course, now I understand. With this information, it's much easier to configure the curve 👍

I presumed something similar to that... AIBIC obviously fully constrains the part. I also presume that what the engineer wants to use as Datum D is being evaluated to AIBIC? I would suggest making a notation on the print that the two holes are to be considered a single feature. This way, you can evaluate the two holes together as a Cylinder; so that if either hole is out of position then the part "fails" The only other way that I can think of that would make sense for this type of part, would be to constrain Datum D to AIBIC (this way AIBIC controls orientation, and Datum D would define the nominal position)... I am unsure of how this would need to be noted/called out to make it "legal"

One thing to note. Correct nominals from a circle can be taken only if that circle element has starting angle "0" and strategy has correct starting angle. Taking out from CAD can result in non zero angle in element, but "0" in strategy start angle. Example: element's starting angle will be 180° so recalled nominals will be rotated by 180° than true points - so you would have to rotate nominals i a curve to get correct ones. If you understand me 🙂

Back face is datum A, large center hole is datum B, and the lower right smaller diameter hole is datum C.

Thanks Martin Jánský for the support, I hadn't tried to obtain the measurement the way you described it to me, it was very practical. I had some issues with the probing vectors; when recalling the points of the elements not measured in the strategy, it wasn't performing the scan correctly with the physical part. I just adjusted the vectors and got my result.

Hi all, I was able to run the program with import gom but suddenly it stopped working. Connected to Host.

Seems like this is a mix up with the 2026 Version of Zeiss Inspect. After Updating to Zeiss Inspect 2026 i had to use the new driver and could update the firmware of the sensor. Would have been nice not to get an update under Zeiss Inspect 2025 that only works with zeiss inspect 2026 🙂

Do you by chance have an SMA to reach our hotline in regards to this issue? These errors can be quite tricky to fix sometimes.

Hi, there is no dedicated function for this. There is one iterative approach using a projected curve Construct Projected Curve: create curve on CAD project curve on mesh (shortest distance) project this curve back to CAD (shortest distance) project curve on mesh (shortest distance) ... It is also possible to create a surface comparison/surface distance between CAD and this mesh area. Then use a defect element to filter point with positive deviation (points above CAD) ZEISS Quality Tech Guide And as @Martin Jánský wrote, intersection points between curve and mesh can be created directly. Many Curves or Section on the CAD perpendicular to the mesh/CAD intersection could be used to create intersection points, then use these points for a curve. Nanno