All Activity

A statement from support or development would certainly be helpful for this post...

Vielen Dank für das Weiterleiten dieses Punktes an Ihre Entwickler! Man fragt sich als Anwender aber halt schon: warum fällt das nicht schon bei der Implementierung auf? Wird das nicht getestet? Programmieren die Entwickler vielleicht schon zu viel mit KI die dann nicht SIEHT, was sie so zusammenprogrammiert...!?

>Vielen Dank, dass Sie uns auf diesen Punkt aufmerksam gemacht haben. Wenn wir Anwender Sie tatsächlich auf diesen offensichtlichen Punkt aufmerksam machen müssen - und das bereits seit 18. März 2025 mit dem ersten Post von Herrn Hübner! - dann müssen wir Anwender wohl davon ausgehen, dass Ihre Entwickler nicht mit der eigenen Software arbeiten bzw. diese testen. Ansonsten hätte es dieser Gruppe ja auch schon auffallen müssen. *kopfschüttel*

I usually uncheck other tolerance so you have only one side. We are reporting mismatch of upper and lower half of a part where it's always positive and ideally it's ZERO - so it looks ugly when it's warning while closer to ZERO

But as far as I know the collision detection always works with the stylus model, so even if you import the actual numbers from the physical CMM, it will ignore them for collision detection or even overwrite them with the ideal SSC values (hmmm, I never checked if the latter is true 🤔. I'd find it strange if Calypso would allow inconsistent values to coexist). If it would use the raw numbers for CD, it wouldn't be able to detect collisions of extensions etc., because they are not stored in a PCF.

There are times when we get a drawing with a dimension callout of, for example, .17 MAX or .17 MIN. I can figure out several ways of doing this with bilateral tolerances, but I wanted to know if there's a more intuitive or straight-forward way of setting this kind of tolerance in Zeiss Inspect. Thanks!

Please see this article as well if you plan to upgrade to v2026 https://carl-zeiss-industrial-metrology-llc.helpjuice.com/zeiss_inspect/-inspect-codemeter-license-update-workaround-inspect-2023-and-older-→-2026-upgrade-path-/version/1?kb_language=en_US

Hello All, Thank you for joining us on the ZEISS Quality Forum. While you're here, I wanted to take a moment to highlight another valuable resource available to our customers: the ZEISS Knowledge Base. The Knowledge Base contains a growing collection of technical articles, troubleshooting guides, best practices, workflow recommendations, and product information designed to help you get the most out of your ZEISS software and hardware. Whether you're looking for step-by-step instructions, answers to common questions, or guidance on specific features, the Knowledge Base can often provide a quick and convenient solution. We encourage you to explore the available content and make use of this resource alongside the Quality Forum. Together, these tools provide multiple avenues for finding information, learning new workflows, and resolving issues efficiently. Access the ZEISS Knowledge Base here:https://portal.zeiss.com/knowledge-base Thank you for being part of the ZEISS community, and we look forward to supporting your success.

If you have PCM licence, than you can use pcm file which automatically runs after report. "report_end_pcm.txt" stored inside inspection folder.

Thank you Martin, Now would I need to put that PCM code in the part program or is there somewhere I can add inside of autorun with the pallet?

For PiWeb -> no. For PDF -> can be used PCM or BAT file with correct code.

Hello all, I feel it is very easy to find the answer to this, but I'm unsure how to figure it out. I've checked other posts on here and can't seem to find anything. Does anyone know how to keep each report up after each individual run? Any help will be greatly appreciated!

Well i'm naming those dimensions with numbers - so "01; 115" and so on. I also write into keywords "qdas_k2001" and number of dimension for QDAS export. This value of keyword i then placed into this table as new column. Bad thing is that this change is more complex than it should be - you have to do it for XYZ, distances, gd&t and others. I am not sure if you can click on column to sort it ascending/descending - but it's alphabetically sorted.

Can You help me. We learnig Inspect and has a problem with raports. We sort dimension with numbers on drawing but in INSPECT we cant sort as we'd like for example: circles is a top, next leght and angle is on bottom. How to sort it in order numers 1,2,3 etc? We try to create in order 1>2>3 but when nr.3 is a circle is autmoatic on first place, or angle had nr.4 and is on the bottom. Is the way to sort on principle drag and drop, or similar? See attachment. I hope You understand me. Sorry for language but I learn english 20 years ago 🙂 Thanks for help. 623-46AA.pdf

Once you have your offline seat you should be able to update the stylus system offline to reduce false simulated collisions. So, even if you don't have the exact components offline you'll have the real world numbers from the qualification for that stylus system online. You can export the .pcf file from your online seat to a flash drive and then import it offline. After that, import the .ssc file to your planner and update the stylus system so that you have the graphics from the .ssc and the actual numbers from the .pcf

i've donwload the : handbook ISO-GPS dimensionning (16/10/2025) (english or french) at https://cetiso.fr/livret-iso-gps/ updated about ISO 5459 2024 and ISO 14405-1 2025, may be not exhaustive but 92 pages of knowledge I wish i have had some years ago there is one line about datum tangential, and nothing about gauss on feature, but some pages about the differences beetween ISO and ASME, wish is often asked on this forum. good reading

I would also make sure that your graphics card settings are configured according to the recommendations outlined in this article - https://portal.zeiss.com/knowledge-base?id=1596796

Jack, Do you have the latest service pack? Are you seeing any specific errors?

Just wondering - Is anybody else having a problem with your latest version Calypso off-line seat crashing when running a sim? Mine will close completely at random points during the execution with only a second or two of freeze up before crashing.

Hello Mike, If what Norbert suggested doesnt work, make sure you are at the latest service pack / patch for your version. I remember something like this to be a bug that was corrected.

Thanks Richard for the assistance. Your lightning responses are much appreciated!

Just add a formula for you points i, j & k. getActual("Plane1").normVector.x /.y /.z Or switch to show vectors if you only wish to see it once?

Create an association with user search terms/words to the knowledgebase articles. Bring the user to the knowledgebase articles.

Hi Yohan, you could define a secondary alignment with your plan on spatial rotation, and use this alignment for you point, so your point will be a i j k 001 in relation to your alignement/ plan

Hallo, Ich kann Ihren Unmut gut nachvollziehen. Gerade ein angemessenes System-Feedback ist essenziell, um effizient und angenehm mit einer Software arbeiten zu können. Dazu gehört auch eine kontrastreiche und gut lesbare Benutzeroberfläche. Im Zuge der Anpassung unserer Anwendungen an den globalen ZEISS Style Guide sind an einigen Stellen leider Unstimmigkeiten entstanden. Auch wenn wir neue Entwicklungen grundsätzlich unter Berücksichtigung der WCAG-AA-Kontrastanforderungen umsetzen, werden in einer so umfangreichen Software vereinzelt Bereiche übersehen. Umso wertvoller ist Ihr Feedback für uns. Das Thema Barrierefreiheit hat bei uns bereits einen hohen Stellenwert. Wir haben hierzu eine entsprechende Initiative gestartet und arbeiten kontinuierlich daran, die Darstellung und Nutzbarkeit unserer Software weiter zu verbessern. Dazu gehören auch Optimierungen hinsichtlich Kontrast, Lesbarkeit und allgemeiner Benutzerfreundlichkeit. Vielen Dank, dass Sie uns auf diesen Punkt aufmerksam gemacht haben. Viele Grüße Aileen Teamleiter User Experience