All Activity

With your gom versione don't you have this problem?

Hallo Markus, ein direkter PCM-Befehl existiert dafür nicht. Du kannst z.B. die Datei "inspection_pre_start_dialog_pcm.txt" oder "inspection_post_load_pcm.txt" in den Prüfplanordner oder den Standardpfad für die Prüfpläne packen und den Code unten einfügen (auf eigene Gefahr!). protPath und ProtName musst du gegebenenfalls anpassen. Achtung: Die Zeilen mit removeAll löschen die bisher aktivierten Protokollkopfvariablen. Wenn dies nicht gewünscht ist, einfach auskommentieren. protPath="C:\Users\Public\Documents\Zeiss\CALYPSO\data\protocol header\" // Pfad zur Protokollkopfdatei protName="ProtocolHeader.xml" // Name der Protokollkopfdatei codeProt = "(t1 := '" + protPath + protName + "') readStream. " codeProt = codeProt + "t2:=Zeiss.Calypso.OMInspection active protocol protDefObj. " codeProt = codeProt + "t2 settings at: #multiProtOn put: true. " codeProt = codeProt + "t3:=#phParaFor_E. " codeProt = codeProt + "t4:=#phParaFor_R. " codeProt = codeProt + "(t2 settings at: t3) removeAll. " codeProt = codeProt + "(t2 settings at: t4) removeAll. " codeProt = codeProt + "([(XML.XMLParser on: t1 asFilename) " codeProt = codeProt + " validate: false; scanDocument] " codeProt = codeProt + " on: XML.MalformedSignal , OsInaccessibleError do: [:t10 | ^Zeiss.Calypso.OMProtHeadParameterSelection new parameterListNotReadable: t1]) root realElements " codeProt = codeProt + "do: [:t5 | | t6 | t5 tag type = 'Edit' " codeProt = codeProt + "ifTrue: [t6:=t3] " codeProt = codeProt + "ifFalse: [t5 tag type = 'CNC' " codeProt = codeProt + "ifTrue: [t6:=t4] " codeProt = codeProt + "ifFalse: [ ^Zeiss.Calypso.OMProtHeadParameterSelection new parameterListNotReadable: t1]]. " codeProt = codeProt + "(t2 settings at: t6) addAll: (t5 realElements collect: [:t7 | t7 elements first text asSymbol]) asOrderedCollection. ]. " codeProt = codeProt + "^0 " executeCode(codeProt) clearParameter("codeProt", "protPath", "protName")

Hi Štefan, please make sure to have side 1 and side 2 in separate parts in the project and try to use the measuring principle again. There are some rare cases, when the automatic creation of the base point on side 2 does not work. In this case please construct a base point manually on the same plane as the point you are using the measuring principle at and define it in the dialog. Easiest way is to use an edge point at side 1 and click the base point on a section, which is defined by the plane of the edge point side 1. When the measuring principle is applied to a curve, a manually constructed curve on side 2 may help analogous to the manual constructed point. If this workaround is necessary, it would be nice to have the sample data available for analysis. So please contact your local support and refer to this thread Get in touch with our team | ZEISS Industrial Quality Solutions Nanno

Hi, that is not possible. We can only group the measurement tables according to part or measurement attributes. This would be a new requirement, which you are welcome to publish on the ZEISS Portal

Hello Kyle, but this is the ZEISS Inspect area of the forum. Maybe somebody who have knowledge from Calypso and ZEISS Inspect read this question, too, but to my understanding you would increase the chance to get a good answer if you repost your question inside the Calypso->General forum. Best regards Christoph Schult

Wir haben immer mit Benutzerdefinierten Protokollkopfvariablen gearbeitet. Das Heißt z.B. mit u_....... Wir haben eine PiWeb Schulung gehabt und jetzt möchten wir auf die "Zeiss" Variablen umsteigen, da man so in PiWeb filtern usw. kann. Desweiteren haben wir Gear bekommen und so müssen wir auch noch ein paar Namen im Hintergrund ändern damit die GDE passend befüllt wird. Jetzt müssten wir eine neue Protokollkopfparamter Datei erzeugen und diese bei jedem Prüfplan anwählen und abspeichern. Wenn ich jetzt eine PCM Datei mit dem richtigen Name erzeuge und im inspections Ordner ablege dann würde diese Datei für alle Messprogramme gelten.

Hello Kyle, It does drive back slightly behind the rack in the +Y. We have had this rack in this position for about 3 years. Never experienced this before. I did notice today that if I turn the speed down on the controller to about 3/4 the speed instead of all the way up when it is doing a stylus change, I don't get the error. I have changed the movement speed in our common every shift programs from 300 mm/s to 100 mm/s and so far I haven't gotten the error. I know this isn't the fix but more of a band-aid to hopefully keep us running.

Hey all, I'm looking to see if anyone has had success with importing MBD and PMI into Calypso to cut down on programming time. I've heard rumors that it can be done in Calypso and figured I would start here first. Any info is helpful. Thanks

Observing your name - you can change language of Inspect to your - closest would be czech - not sure about slovak. Look here https://techguide.zeiss.com/en/zeiss-inspect-2025/article/cmd_inspection_measure_edges.html

No, the connection to the database is hardcoded inside of Calypso. It needs to be Microsoft SQL and the files need to have very specific names for it to work.

To me, without seeing the machine of course, this looks like maybe the racks are too far in the +Y? "SMS_LIMIT" sounds like it might be complaining about the limits of the machine. Can you move the probe above your racks and move it all the way to the back of the +Y and see if it can actually reach all the way back there?

I don't think the separate characteristics are necessary in the new GD&T engine. After you make sure that the size tolerance is set correctly in the characteristic (the diameter symbol next to the MMC symbol in the characteristic), you can delete or hide any additional diameter characteristics you or the system made (see https://portal.zeiss.com/knowledge-base?id=1128721 for instructions on hiding the characteristics, assuming you are in the US).

@Jace Pink To my knowledge Acronis has always been set up to backup weekly, at least on the machines we send out. It is configurable, though, so perhaps in the intervening time someone turned it off (IT or something because they were concerned about the backup for some reason). I unfortunately don't have a lot of experience with the Acronis program on the computer itself (it's not on the computers we give to techs or AEs). There should just be a shortcut labelled "Acronis Backup" or something similar on the desktop. There is a password screen, but you should be able to just hit okay through it to my recollection. Do you have an Acronis folder on your D drive? I can't tell for certain, but is it a computer from us and when would you have gotten it? I think we only started giving Acronis around 2020, so its hard to tell.

Hello, very much please, can anyone help me? This error message is written by the software and I don't know how to set it up so that it finds the other side 2 Has anyone encountered this, please? Thank you so much. Štefan

Thanks for the reply Pat. I had tried everything you mentioned short of putting in a service ticket. I had slightly changed the approach parameters to pause further in the -Y direction thinking that might help and it seemed like it may have been working better, until it didn't. Perhaps its time to put that ticket in.

@Pat Bryant No, I did not.

Hi Johnny, could you share the the data and script with the support? support.optical.metrology.be@zeiss.com should be the correct address for your location. Please refer to this thread. We would like to analyse it with your data set. Thanks, Nanno

It gets weirder and weirder. Today I submitted a support ticket and the support guy basically made me reestablish the pallet and base alignment and for now the results seem to be more or less constant 😮 Ok, we did a lot more than just renew the alignments, but all extraneous stuff aside that's the essence of it. I have absolutely no idea why that should fix anything (see, I'm not a beginner in setting up alignments, I guess), but at the moment it looks like it did. I have to run more tests tomorrow and contact the support guy again. If I find out anything new I'll report.

Hello, Now I understand. The import template came from recording the command in the script editor. The template is also used by manual 1 by 1 importing. regards Johnny

Hello, do you really have 'some string' as input to the template_bin parameter? This is what defines the ascii import template. If not, the template maybe does not fit the data you are trying to import. Did you get the import command by recording? Regards Daniel

Hello Daniel, Yes I have a project open. This project has the nominal model, measurement and actuals. The actual are imported 3D point from the CMM machine. A mesh is not used. The nominals are connected to the actuals. There is no specific template used. If there is a default template (from installation) this is used. I hope this helps. If needed I can share the project privately. Johnny

I create a best-fit alignment (constraining XYZ) from the curve. Open a nominal circle and recall the points from the curve, then reference the BFA in the circle.

As far as i know Calypso is using MSSQL and it's running local file. Similar thing is PiWeb. So i don't think there will be a file/settings defining connection, to be editable.

What customer's question:Is it possible to migrate the Calypso DB to an SQL server that is already created into their network?Can Calypso work like that or it needs local DB?

Out of curiosity: Are there any patterns involved in your program?