All Activity

If you have the bubble help option active, there's a column on the right side of the header selection window that will show you what's assigned when you hover the mouse over it. Was more clearly visible in older Calypso versions.

thanks I will try that

Good afternoon everyone, I am having troubles when evaluating 2D curve via Measured point display. We recently switched from Calypso 2020 to 2024 and prior to that we used the measured point display when instructing operators on depth adjustment using distance between points. I can still kind of use this method, but it is much harder to visualize using the radii of the two lines. As you can see in my attachment, even with "lines" selected, it displays dots and pushes the line far above the CAD model and its true location. When I lower that "20" magnification to "1" it just reduces the dot magnification. Red arrows indicate where I want the line to go. 😒 What happened to these lines?

Asking for Calypso? Here is my thread for that - hope you find your way.

Hello everyone. Is it possible to add measurement plan info (it's location) to the pi web header? Like C\users\xxxx\xxxxx I tried searching around forum but couldn't find an answer. Thanks in advance

That worked thank you very much! How do you find the variables? I am also trying to do one for machine number, but it would be great to know how to find them out myself.

Hey @Roberto Flores, @Clarke Gilbert and @Marc Distefano. I just wanted to know if you might be able to share anything you ended up coming up with in regards to Autorun guides, PDF's or anything else. I see it looks like Clarke might have emailed you something and Marc had posted some PDF's but they are no longer visible when I click them. I am looking to setup some of our programs into an Autorun for the first time and wondered if anyone had any advice on how to start. Thanks

Hallo Yannick, wir hatten ein ähnliches Problem nach dem Update auf 2023. Da konnten wir keine Programme mehr mit CAD Modell Speichern. Wir hatten in unserem Speicherpfad für die Messprogramme vorher immer mit Ü Ä abgespeichert. Das wollte Calypso 2023 nicht mehr. Darauf sagte Zeiss wir sollten den UTF 8 Code einstellen. Wir habe unsere Problem jetzt aber so gelöst, das wir keine Umlaute mehr verwenden. Seit dem ist alles i.O. Aber vielleicht hilft ja die Einstellung bei Dir.

Hi, it is important to remember that the CAD shall be imported in the "defined" evaluation coordinate system. If this is not the case you end up in trouble because the X/Y/Z aren't aligned by default in the wished coordinate system. Of course, you can "workaround" the visualization with the use of a view coordinate system but usually this is only necessary if you have multiple datums which must be evaluated in different coordinate systems and you want to create for each subset of datums nice report pages. The alignment only aligns the measured data to the CAD. If you specify the alignment from an "arbitrary" actual coordinate system into the "Golbal coordinate system" you can transform your measured data far away from the original position of the CAD (which you have imported). In this case it seems that the actual elements can't be calculated anymore after you have switched into this alignment (the error message hints it with "Nicht alle benötigten Elemente konnten berechnet werden"). Hope this helps?! Regards

Hello Antonio, maybe a fitting point works for this? It is possible to create a "scripted element" Scripted elements — App Development Documentation. This needs scripting with python first, but the result is a normal dialog like any other element. Nanno

Hello Gaurav, many ways to evaluate the distance between planes: https://techguide.zeiss.com/en/zeiss-inspect-2025/article/faq_how_to_evaluate_the_distance_between_planes.html Maybe a position tolerance with min/max deviation labels works for you (activate color deviation representation in the properties first)? Nanno

Hello Rachel, maybe it can be detected with a surface defect analysis? https://techguide.zeiss.com/en/zeiss-inspect-2025/article/cmd_inspection_inspect_create_surface_defect_element.html Could you post a picture or sketch of the problem if this does not solve it? Nanno

Hello Tarek, I guess this is not a Correlate specific problem. You could give it a quick try and do a right click into the code -> Tools -> Update script. This would fix it, if the problem was the part based structure of Inspect 2019 and later. If this does not help, please contact support with the concrete script or post it into the customization subforum. Nanno

Hallo! Ich komme gerade nicht weiter. Kann man den Status von Tags abfragen? Z.B. ob Tags für ausgewählte Reportseiten aktiv sind (also die Reportseiten ausgewählt bzw. abgewählt sind). Würde mir sehr weiterhelfen, wenn das möglich wäre. Danke schonmal! Grüße E. Pusch

Moin, Nein, es heißt ja Monitor(anschauen), ohne Planer kannst du keine Änderungen machen schon gar nicht in die Datenbank.

Fun fact 😛 There was a UMESS-LX version long ago. It was end-of-sale in 2005 and end-of-support in 2010. Surprisingly late in my opinion . No Linux versions of anything on the horizon since then.

Nach dem was ich selber rausfinden konnte, gibt es in Calypso 8.0 definitiv eine neue Version der qdasconv.exe, also des Programms, das letztlich die QDAS-Datensätze erzeugt. Die exe hatte immer schon diverse Kommandozeilenschalter, um Eingabe- und Ausgabe-Dateien sowie die Konfigurationsdatei anzugeben. Hier sind anscheinend auch keine neuen dazugekommen, so daß eine Veränderung des Outputs zumindest schon mal nicht über einen Direktaufruf des Programms möglich ist (Direktaufruf ging auch bisher schon über eine qdas.bat im Config-Verzeichnis, um Zweit-Datensätze zu erzeugen). Das schließt immer noch nicht vollständig aus, daß es eine undokumentierte Konfigurationsmöglichkeit entweder über die qdasconv.con oder woanders geben KÖNNTE. Zwar unwahrscheinlich, weil die Ausgangs-Tabellendateien jetzt auch UTF-8 codiert sind (siehe Onlinehilfe), aber nicht unmöglich. Aber sowas dürfte sich wirklich nur über Zeiss rausfinden lassen.

Hallo, ist es möglich, Wenn ja wie, die Merkmale im Piweb Monitor zu ändern und dann in die Datenbank zu schreiben wenn ich z.B. die Toleranz ändern möchte oder bei einer MSA1 den waren Wert des Einstellmeisters einzutragen? Ich habe schon viel versucht aber es einfach nicht hinbekommen. Die Werte einer Messung kann ich ohne Probleme ändern. Nur eine Ebene höher nicht. Und ist es möglich Merkmale auch über den Monitor in der Datenbank anzulegen oder geht das nur über den Planer direkt? Hello, Is it possible to change the characteristics in Piweb Monitor and then write them to the database if, for example, I want to change the tolerance or enter the actual value of the adjustment master in an MSA1? If so, how? I have tried many things but simply cannot get it to work. I can change the values of a measurement without any problems. But not one level higher. And is it possible to create characteristics in the database via the monitor, or can this only be done directly via the planner? Translated with DeepL.com (free version)

Keep in mind that if you delete a holder and create a new one, the settings will need to be re-entered.

Thank you for quick response. If possible I think it will be a nice thing to add in the future releases.

Thank you all very much for the responses, I changed the approach parameter for position after change. I turned it up a ton to make sure i now have plenty of clearance and that seems to have fixed my issue. Thank you very much!

Small complaint: Simulation doesn't keep its settings, like speed, show/hide CMM, show collision warnings, transparency... Fix please 🧐

Dear community, Have any of you experienced issues with extracting a large number of projects? We created a script to automate this process, and in the old version of ARAMIS v2018, it worked perfectly. Unfortunately, it is not now. It only extracts the velocity major strain and stops there. After checking the project, I find the velocity major strain is the only one being selected, and the rest are not. Has anyone experienced this recently ? Best regards

I am just wondering if anyone else is having this issue and if so how did they fix it. My company just went to 2025 and today when I came in, there was an issue. The program was started up by one of the machinists that comes in early. He can only open it up as User, giving them limited access to certain things. Half of his report was reported in Metric, the other half English. The icons were all huge and very limited (which I am not too concerned with). When I went to see if I could change the report to English, the option was not there, so I went to change to Master (giving full control) and I could not do it. I had to close out the program and re-open it up under Master. When I did, everything was fine. The report came out all English, no Metric. I changed back to user and the same thing, half and half. I am very confused right now. Any help would be appreciated. Thanks.

Today I finally got around to installing Calypso 2025 (latest SP 8.0.08) and up to now I can't complain about Simulation at all. On the contrary, it's much faster than in previous releases, even on the lowest speed setting. So fast indeed that I was concerned it wouldn't detect collisions at travel speed as reliably as before. But even that worked very well in my first tests. I also see a slight stop'n'go behavior like in Ted's video, but it's much more subtle (may have to do with the speed setting - I always simulate on lowest speed). So far I'm impressed. But then our models might be far less complex than those of others.