All Activity

Hello! There was an error when launching the report after the measurements. I found a description of the exact same error: https://carl-zeiss-industrial-metrology-llc.helpjuice.com/piweb/piweb:-piweb-cmm-server-not-started , but there is a transition from Calypso 2019 to 2020, and we have a transition from 2020 to 2021. We tried to fix the error using the method described in the link above, but it did not work! Has anyone encountered this error and knows how to solve it? Help!

Hi! What's this parameter?

I have just tried export of "diameter symbol" and it was in csv - i have to just change to correct character coding. Otherwise you would need to create own python script for exporting tables, which you have more and easier control over it.

It should help, that you set your probing force at calibration. But to change dynamics and probe force you can do it at Features editor on Probing page. Or i can have it on VAST XT page. Reduce both - dynamics and probing force in that dialog.

Can you post a screenshot for better explanation for us? Thanks

Martin, Thanks for response. I wish to get a way to modify inspection element by displaying symbol or character in the export csv file. If so, that would be a lot of easier for user. However, I have to write a scripts to replace all those symbols in export file as dimensional team request. I wish there could have an easy way to switch by user like some CMM software.

My company is moving towards ZEISS Inspect 2025+ and we're using a floating network license (Pro). In previous versions (e.g., ZEISS Inspect 2023/GOM Inspect) the floating license was handled through CodeMeter, which allowed us to: Open the CodeMeter Web Interface See which user/machine currently had the floating license checked out Remotely release/revoke the license if someone forgot to close the software This was very useful because we only have (1) floating license. For example, if someone left for the day without closing Zeiss Inspect, we could free the license so someone else could use it. After upgrading to ZEISS Inspect 2025, we can still use our Pro floating license, but when it is in use it no longer appears in CodeMeter, so we no longer have visibility into: Who is currently using the license A way to force-release the license if needed My question: Is there a new way in ZEISS Inspect 2025 to: See which user or machine is currently using the floating license Remotely revoke or free a license if it remains checked out Has this functionality moved somewhere else, or is there a different recommended workflow now? Any insight from others managing floating licenses would be greatly appreciated. Thanks! EDIT: Found that this is now managed through the Zeiss License Management Tool. Had to reach out to IT since the server machine is not something I have direct access to. Thanks.

I'm using a .3mm probe. How can i lessen the force its using when probing a feature. or slow it down sooner then standers settings.

wenn ich eine Protokollseite erzeugen möchte, egal welche Vorlage oder Format , steht immer " unbekanntes keyword". Ich kann so auch nicht die Titel-Seite ausfüllen. Ist der Pfad weg bzw was muß ich tun ?

You would need to edit table report template. But as i saw - you have to modify many things, because it's not global for every callout. Like distance, width, TP, profile, ... I don't understand why editing table for displaying K2001 value have to be done on so many categories.

Do you want to measure that "R" only or additional 14° line and the other line tangential to that "R"? I would ignore that formula and go straight to definition of basic features, like circle and lines. Define correct strategy. Now just recall those features into new curve and voila - you have nominals for a curve. One mention for that - to have correct nominals you have to do recall measured points on features without measured points - that will recall nominal points from strategy, otherwise you will create nominals from measured points.

Sorry, I forgot to attach the image of the feature.....

Hello everyone, I don't have much experience with PCM and I can't adjust the curve values to measure a 0.004 surface profile. I've attached a Excel and a reference image. I can't seem to create the curve correctly; it's not respecting the formula values. I hope you can help me edit it properly. Regards. Contours.xls

offtsetCoordinates = readListFile(offsetFile) ballFinderOffsetX = (val(getParameterNamed("offtsetCoordinates",1))/1000) ballFinderOffsetY = (val(getParameterNamed("offtsetCoordinates",2))/1000) ballFinderOffsetZ = (val(getParameterNamed("offtsetCoordinates",3))/1000) coordsys = getParameterNamed("offtsetCoordinates",4)

Hey, May I get help for changing table property from symbol to characters in Scanbox report? I want to change all Ø to "Diameter" in exported csv file. Change to: and also change DN/DT to "Nominal" Thanks

I Forgot about that option. Thank you!

Hey Nanno, yes, in live-Mode you can see a few green points.

Hi Jure, is there a reference point detected in the measuring volume?

Hello everyone, I am looking for a solution. I used the record button to create this code, which is supposed to scan automatically. gom.script.atos.set_acquisition_parameters(measurement_temperature=20.0) GOM_MMT_RETRIES = 10 GOM_MMT_ERROR_CODES = ['MPROJ-0037'] while True : try: gom.script.atos.insert_scan_measurement () except RuntimeError as ex: if GOM_MMT_ERROR_CODES and not ex.args[0] in GOM_MMT_ERROR_CODES : raise GOM_MMT_RETRIES -= 1 if GOM_MMT_RETRIES <= 0 : raise else: break Unfortunately, I get the following error message when I run it automatically: RequestError: MATOS-S032: Cannot check online sensor movement. File .... , line 29, in <module> gom.script.atos.insert_scan_measurement () What could be the reason for this and how can I fix the problem (I am using Zeiss Inspect 2026)? Best regards, Jure Baloh

Hi All Is there a way to limit which folders different users have access to in Calypso? I know you can define the default pathway, but I'm interested in limiting Operators to a single source for program retrieval while granting access for Programmer and Master users to all folders. Thank you

ok ... round about way... most likely a better way but found a solution .... I read the protheadpara file into a listfile, then made a loop looking for the line that had my variable name. the counter variable would be that line minus 1... so i set the same loop again with the exit at the counter minus 1 while setting each line to a variable. in the inspection_end_pcm.txt file... i simply deleted the file, then used addFile with the new variable.... programs now run with no errors. messy but it works.

What exactly ist it that doesn't work with your first code? If I simulate it, I get 0, 0 and -0.1d What exactly did you get and what did you expect instead? I never had any problems reading mixed lists with getParameterNamed()

Do you mean you used a different stylus just for simulation, then wanted to go back to the original used on the live machine? What you could do is to export the stylus from the live machine as a PCF and import it in Planner. This way you don't have a stylus model (SSC), but all the tips with the correct names.

I just scanned a bit of a part today and I'm seeing the same issue as you. The scanned surface looked more solid after a scan in the earlier versions. I even called my supplier to ask about it, but they couldn't say why it was such difference.

Hi, i have a .txt that im reading with readListFile() This is what it contains: With this code: offtsetCoordinates = readListFile(offsetFile) ballFinderOffsetX = (val(getParameterNamed(offtsetCoordinates,1))/1000) ballFinderOffsetY = (val(getParameterNamed(offtsetCoordinates,2))/1000) ballFinderOffsetZ = (val(getParameterNamed(offtsetCoordinates,3))/1000) coordsys = getParameterNamed(offtsetCoordinates,4) I get the two "0" values correctly because i guess they are integers and the rest is just "". I could make the file comma seperated and then use offSetStuff=offsetFile.asFilename.contentsOfEntireFile xOffset = val(strElement(1,",",offSetStuff))) yOffset = val(strElement(2,",",offSetStuff))) zOffset = val(strElement(3,",",offSetStuff))) coordSys = val(strElement(4,",",offSetStuff))) But i dont want that tbh. Is there a way to use getParamteterNamed() for that?