All Activity

Even the log in on the Zeiss portal is giving me an error message

Hi Zward, you could try to download the software using the Zeiss Portal portal.zeiss.com.

We use Autorun for family parts utilizing para and PCM. Other than that, due to Calypso software versions installed on Contura CMM's from v2016 thru v2022 we control part programs stored on a network. The network locations are read only preventing running programs from the network. Network locations are based on version using separate folders. some network url\Contura1 v2016 some network url\Contura2 V2022 etc. We have a retrieval hierarchy. Retrieve program from required location Run program to end of production If no changes are required, delete the program If changes are required, edit program, note all changes in Revision control worksheet of the Setup workbook Place programs in the transfer folder for review Review programs If approved, move to proper network location and rename original file for history archiving. All operators are trained in this procedure.

If this is directed at me, primarily Creo (prt) which are converted to either SolidWorks and or Step. So far when working with Discus, a prt file gave us the best PMI information. The step format AP242 was terrible in Discus. AP242 seems to be ok with PMI information in Calypso less if you save the file within Calypso it loses the PMI information. I don't think v2022 or earlier is capable of exporting AP242 files.

I would be suspicious of the carbon shaft having a fracture or possibly the glue at any joint of metal or stylus to the shaft. Personally, I would not accept the results of 0.0008-0.0014.

Hi Caitlin, Im using this stylus D6L100 with carbon fiber shaft. For the calibration im using the qualify passive stylus (scanning calibration) I will run some tests with ring gauge to make sure the stylus is still good, but the sigma values from 0.0001/0.0002 to 0.0008 to 0.0014 are concerning me

@Joe Kerman can you explain us?

I'm trying to download the latest graphics driver and Zeiss Inspect 2026, but when the quality suite prompts me to sign in it gives me an error. Is there a way around this or am I going to have to wait until the login issue is fixed? Thanks

Hallo zusammen, ich bin aktuell auf der Suche nach einer praktikablen Lösung für die Programmverwaltung in der Fertigung und wollte deshalb nach euren Erfahrungen fragen. Nutzt ihr zur Bereitstellung der Programme die Autorun-Oberfläche oder setzt ihr auf ein anderes Konzept? Bei uns existieren pro Maschine etwa 500-700 Programme. Das Anlegen und Hochladen einer separaten Autorun-Datei für jedes einzelne Programm ist entsprechend aufwendig. Bisher nutzen die Werker die Autorun-Oberfläche, rufen die Programme jedoch jedes Mal über die entsprechende Inspection-Datei auf. Das führt gelegentlich dazu, dass Programme versehentlich verschoben werden und anschließend nicht mehr auffindbar sind. Mich würde interessieren, welche Lösungen ihr hierfür einsetzt und ob ihr Möglichkeiten gefunden habt, den Prozess zu vereinfachen. Vielen Dank vorab für eure Rückmeldungen.

@na_vor Not the case, same results. I created new stylus system, did not qualify it and it says "false" to calibration property - as I thought.

check naming and quotes -> getProbe("1_-Z","10").calibration

@Michael Krauskopf Same as above. I bet it shows if the probe was EVER calibrated before (have date of calibration) but not its actual status.

getProbe().calibration // active stylus calibrated getProbe("STYLUS","STYLUS SYSTEM").calibration // for an existing specified stylus Further commands: https://qualityforum.zeiss.com/topic/17112-getprobe-characteristics/?do=findComment&comment=95734 or inside the pcm manual: C:\Program Files (x86)\Zeiss\CALYPSO X.X\userinfo\manuals\en\Calypso_02_PCM.pdf

@na_vor I already tried that and it does not show the status I need 😕

I'm not 100%, but close -> getProbe("5_-X","star_3").calibration it should return true or false.

Hi Daniel, unfortunately there is no workaround for it. Windows changed how API are handled in this patch. So the only way is to either use a older windows 11 build or switch to the software version 2023

Same with Probing System Qualification - cannot access the state of characteristic.

Is there any workaround this? I can't uninstall this two Windows updates anymore. This situation is not very user friendly, as we have many customers with older versions and it's very difficult to support them if we can't open their projects here locally...

You could compare it to the mesh of a reference sample. You can load that as CAD. for flatness this is possible like so: build an alignment build a plane check the plane for flatness go to properties and activate "show colour ..." put some deviation labels on if you like Also works for other geometric elemnts

Hello PCM Masters, Is there any property of getProbe or any other way to check probe's qualification status? It is green when qualified (qual. date and time are updated and all other data) It is red when is was NOT qualified (qual. date and time stay from the previous qualification and all other data)

Sounds good, will talk to the Forum Admin when she's back from vacation.

What CAD software does your company use for design?

Everything seems to be up to date and connected correctly, I will have my boss reach out for local support. Thank you

I would start with making sure you are on the most up to date version of the Image aquisition drive and hardware service for the version you are using. I would then make sure everything connects correctly in the Measuring Device Manager. If the issue persists please pull a GOMSIC and contact your local support. https://portal.zeiss.com/knowledge-base?id=3047314

I am trying to measure a break out diameter for size. basically it is a ring type part that has a center bore, a plane and web. The web has radius that is less than 60degrees of an arc that is intersected with the plane. Where the plane and radius meets is the diameter I need. The radius is part of a line profile (several around the part) measured with a curve. So i have the curve points. I recalled those points into individual diameters. If I was just measuring the radius, it would just constrain the size to get location and constrain the position to get the size... in this case I need both at same time. I tried using a theoretical diameter and formulas to input the location and size of the recalled points and then intersect with the plane. When i do this I get a diameter that does not make any sense. Any ideas on why?