All Activity

We are located in Dallas - please feel free to reach out directly.

There shouldn't be any other path locations. I have manually edited the arn file before in addition to the path replacement tool without issue. I even made a copy of my arn file just now to change one arbitrarily as a test and confirmed that the change carried over to Autorun.

Thank you for the information. We weren’t aware that the DAKKS certificate might need to be purchased separately. We’ll contact our ZEISS representative for clarification. If your team is able to provide certification depending on our location, please let us know — we’d be interested in that option as well. We are located in San Francisco.

I'm not certain if you have to purchase the DAKKS certification with those or not. I'd reach out to whomever your Zeiss contact is and ask them. Depending on where you are located, we might be able to assist in certifying it for you. 🙂

We recently purchased the PSA 900 artefact from ZEISS, but it arrived without a calibration certificate. Could you advise us on how to obtain the certificate, or confirm where the artefact should be sent for calibration?

I'll look into this - i think it may be same like with tolerance files - whole Calypso needs to be restarted. Perhaps just closing autorun can help. But i'll see tomorrow.

Does anyone know of a way when using the simultaneous requirement option in the new GD&T engine, to separate the bore pattern plots out? It always combines them and can look really messy. Additionally, if there is a profile tolerance included in the simultaneous requirement, it wont plot anything. I know you can make copies of the position characteristics just to calculate the DRF, then use the GD&T best fit alignment to recall that, but was wondering if there was a cleaner way.

if you still have the same issue, you can always go back to your old config folder remove the config folder from C:\Users\Public\Documents\Zeiss\CALYPSO 7.0 folder the one you copy from 6.8 old and once removed, you can rename the config_old folder to config and that will bring you back the old config folder

Hello If 2019 is working and 2020 is not, i would recommend going to C:\Users\Public\Documents\Zeiss\CALYPSO 6.8 folder and copy the config folder. then go to C:\Users\Public\Documents\Zeiss\CALYPSO 7.0 and rename the existing config folder to config_old and transfer the config folder from 6.8 folder to this folder. once it is completed open calypso and check if issue is resolved

I have found using that interface was hit or miss. I have created the change and Clicked on the Check Mark and watched nothing change. This is why I attempted editing the arn file.

Yes, yes you can 😈

Inside of AutoRun - go to Edit - Replace paths for Measurement Plans. There is a much more effective way of quickly changing folder structures. 🙂

Haben wir irgendwann mal festgestellt, dass es da noch paar entfernte Verwandte gibt 🙂 Ob das jetzt die sind, die du meinst ka. Wusste bis jetzt nicht, dass es eine "heller family" als etablierten Begriff gibt und sogar Bücher darüber und so. Glaub doch andere Hellers. https://de.wikipedia.org/wiki/H._Robert_Heller

Hallo Jochen Ist schon seltsam. Habe es mit der Schablone (linke/rechte Kamera prüfen) überprüft. Kommen auf beiden Seiten optimal Ergebnisse. Habe dann neu kalibriert, Alles optimale Ergebnisse. Dann beim Scannen von unten wieder die Fehlermeldung. Beim Kalibrieren muß man ja auch den Scanner um 25°/45° schwenken und da kommt ja auch keine Fehlermeldung. P.S Heller ? Hast du zufälligerweise auch Verbindung nach USA " Heller Family"? Wäre großer Zufall.

I had a similar setup and oddly enough, a similar part. I created 500 V shaped Counterbores that were .015 deep, and used a spring pin similar to your setup. You would load the part into the V apply the force against the spring device and snap in two contact two surface. This allowed maximum feature area exposed. We would place them in by hand and for removal we used a best fit gage pin to tilt the part and snap it out of the pocket. These were too small for my manly fingers to remove. 😁

I am undergoing a path change for our Autorun programs, the path before was about 7 subfolders deep and will become 3 subfolders deep. Example: C:\Zeiss\Company Name\Programs\Another sub folder\Another sub folder\And another sub folder\Geezus\PCM Programs Will now be: C:\Inspections\PCM Programs I came up with the idea of editing the paths in the arn file, this was easy to do. Then I set my Calypso default paths accordingly in settings. When I opened the new Autorun arn file, all the paths were exactly as original, I confirmed the edited the paths in the arn file. Regardless of the path edits, I had to manually change all the paths in the Autorun system, which is a cumbersome task when you have 100's upon 100's of programs in different layers. Where else are the paths being saved for Autorun arn paths? There has to be another file or more to look at.

Something like this should work. The plot is displayed on the screen as it is being saved, and will remain visible even if you delete the file. saveViewToFile("ISO","C:\temp\dummy") deleteFile("C:\temp\dummy")

If you need a script for active stage and not for enabled/disabled, then change condition # previously getting all from active stages if stage.is_active: #only from selected stage ( clicked ) for stage in gom.app.project.stages: try: if stage.name == gom.app.project.get('stage.name'): print(gom.app.project.in_stage[stage.index].get('user_qdas_k1041')) except Exception as e: print(e) print('Non existent keyword')

Hallo zusammen Ich habe derzeit das gleiche Problem mit Calypso 2025. Beim Verbinden mit dem KMG bleibt Calypso hängen. Hat vielleicht jemand die Lösung auf das Problem gefunden? LG Samuel

Indeed I do something similar. And could improve my method by storing the index of the active stage in this list.

Hi, so to obtain only valid data ( excluding disabled stages ) i use this for stage in gom.app.project.stages: if stage.is_active: try: print(stage, gom.app.project.in_stage[stage.index].get('user_qdas_kk1041')) except: print('Non existent keyword') For assigning keywords there is another approach using gom.script.sys.set_project_keywords ( keywords={ 'qdas_k1041' : '123456', ...}, keywords_description={ 'qdas_k1041' : 'Part drw. number', ...})

I think licensing might be a problem. Assuming the OEM embedded the key in the firmware, I assume it is a key for the IoT enterprise flavor of Windows, and I think in order to get it to activate you would need to install that flavor, meaning Win10 Pro would not activate. Tom did show that Microsoft still has the Windows 10 download tool, but if that doesn't offer IoT Enterprise as an option then you might be hard-pressed to find it, as it was really meant for OEMs and system integrators and wasn't freely available to download. But, as Abbas suggests, if you have a company IT department then your best option is to make it their problem.

Hello I would talk to your IT dept, usually windows license keys are attached to computer motherboard. when you install then new SSD and windows again it might detect the license key from motherboard.

Per my copy of the PDF that you are looking for: "This manual (in printed or digital form) and the attached electronic templates are copyrighted. No part of this documentation may be copied, reproduced, translated or processed, multiplied or transfered by means of electronic machines without the expressive approval by Carl Zeiss Industrial Metrology ("ZEISS"). Non-compliance will be prosecuted." Am I now in trouble because copying this excerpt constitutes as "part of this documention"?

I forgot to mention I am using Calypso 2019