All Activity

Also note, to pass the variables they did require to be wrapped in quotes. OpSerNo="SC-999" OpMachCtr="K999" OpOper="M999" OpWOID="45009999"

I would guess to change default GPU for process in Windows to utilize only RTX and not iGPU. I am sure on knowledge base or in this forum will be shown how to setup for Calypso - same should be for Inspect.

Hello all, We are running ZEISS INSPECT in an automated environment with multiple INSPECT instances, and we occasionally encounter the “Graphics Card” dialog shown in the attached screenshot when an instance starts. The GPU is detected correctly, Hardware rendering (default) is selected, and the graphics card/driver is reported as compatible with no known problems. However, this dialog still appears intermittently. This is an issue for us because our INSPECT instances are started and controlled automatically. When this dialog appears, it requires user interaction and therefore interrupts/block the automation workflow. Could you please clarify: 1. What can trigger this Graphics Card dialog to appear intermittently? 2. Is there a way to disable/suppress this dialog permanently without using software rendering? 3. Can we force ZEISS INSPECT to always start with Hardware Rendering via a configuration file, command-line parameter, environment variable, or Python/script API? Thanks, Canset

Basic GD&T (i.e. without Surface Profile, pattern and the other stuff where nominal data is essential to estimate TED) is also supported on actual data only. To do so, open your project, check that you have set your project as aligned This allows you to use system elements without getting an alignment. Create you GD&T checks, please use I-Inspect It should work on the actual in the same way as on nominal. Afterwards you can enable the deviation plot in the toolbox. Now you can set picker or create min/max picker on the deviation plot. Of course the works for all other GD&T tolerances. If you not want to use GD&T, you can construct primitives for your own and afterwards use deviation to primitive (found in the inspection sub-menu) to get your deviation plot.

Are you iterating through stages or you are using fixed stage_name? I think you can also iterate through stages like this for stage in gom.app.project.stages: gom.app.project.in_stage[stage.index].get('user_keyword') #another approach ( hopefully correct ) for i in range(0, len(gom.app.project.stages)): gom.app.project.in_stage[i].get('user_keyword') you can access stages like this ( if there are usefull things ) gom.app.project.stages[1]

I would suggest trying this guide and see if it corrects the issue

I figured it out, I forgot (again) about the userfields.ini file. Oops.

I created a new "machine" in planner, I then created all of the probes in Stylus system creator. When I imported the Master Probe into planner, I get this: As you can see the probe does not align with the "system" probe. Is there any way to get them to align? With all the other probes I just manipulate the geo until they are lined up in all 3 axis.

I have several variables I need written to a PiWeb report. I am bypassing Calypso's normal input screen "Input Parameter" for header data to control what gets entered. I am using vb.net in an interface where the Serial number, Mach center, operator and WOID will be collected for strict control of what is entered. Current para file variables to write to PiWeb. OpSerNo="SC-999" OpMachCtr=K999 OpOper=M999 OpWOID=45009999 Using OpSerNo for this exercise (Solve one should solve all) with PCM. u_SerNumb=OpSerNo (works and resolves to "SC-999") But this resolves to nothing OpSerNumb=getRecordHead("u_SerNumb") Once that is solved, how do I pass the OpSerNumb to Piweb's "Incremental Counter"? (I use the Incremental Counter as a Counter and or Serial Number) (Interface shown in the image)

Despite all our complaints; Zeiss has actually done a good job of releasing stable versions for the last several years. While adding several good features along the way.

All I can say is that I am excited for this one. 😁

Hello, I'm trying to read the stage specific keyword the script only gives the value for the first stage. The code I'm using gom.app.project.in_stage[idx].get('user_keyword') To get the index I'm using gom.app.project.stages['stage_name'].index But this give always 0 as result, no matter what I'm doing. I used this https://zeiss.github.io/zeiss-inspect-app-api/2026/howtos/project_keywords/project_keywords.html as reference. What am I doing wrong? Or is it a bug. Zeiss inspect version: 2025.4.0.398 [531c6a7c425a] Thanks for the help.

Hi Kevin , one of the options for doing it : 1 - import mesh as Cad body 2- Cad to actual Mesh 3 - prealignment 4 - select area for plane 5 - create a plane ( with measuring principle/ fitting element) 6 - evaluation Give me feedback , Have a nice day😉

Hello I would recommend clearing cookies in your current browser, i would also recommend trying a different browser to login

One thing to note - i have one specific program, where i have problems with hiding some of CAD faces. Pressing to show all sometimes works. I think it can be with specific model, where only option is to remove old one and import again a new one.

Hello fellow Zeiss users! Currently I am using Zeiss Inspect 2026 and PiWeb 2026. I am needing to update how I am exporting the .dN dimension - instead of exporting showing .dN I need to change to just exporting as .N Any suggestions are appreciated! Have a good day!

Here is link to our Knowledge base article https://portal.zeiss.com/knowledge-base?id=528774

Hello i would recommend checking graphic cards settings

This looks like an outdated graphics card driver or settings issue.

We've been seeing this consistently since upgrading to SP4. While working in the CAD window, surfaces, edges, or other entities will suddenly disappear for no apparent reason. Sometimes changing the view, rebuilding, or reopening the CAD model brings them back, but the issue keeps coming back. A few things we've noticed: Happens on multiple parts and CAD models. Doesn't seem tied to any specific action. Missing entities are not actually deleted, just no longer displayed. Reopening the file may temporarily fix it. The issue is frequent enough that it's becoming a real frustration during programming. At first, I thought it was something specific to a CAD file, but after seeing it across multiple jobs, it feels more like a bug in SP4. Just wondering if others are seeing the same thing and if anyone has found a workaround or heard anything from ZEISS about a fix.

I also found "decimalUnits" in "inspset" file. I have no enough test data to see if you can set different decimal places for each characteristic. What i see in Calypso - when i enable view of probe, then i see probe in views even in programs which it was not enabled. So perhaps if it's not set, then some programs can have different settings and it is stored as "default" so any other program, which is not set inside it will use that settings.

getActualInspectionDir()+"\Logs\"+getRecordHead("planid")+"_"+getRecordHead("date")+"_"+getRecordHead("time")+"_"+"PartNo." +" "+getRecordHead("drawingno") Try the above

verified it in inspset file, the inLengthUnit is in mm, there is no inDecimalUnit. verified it in the program under characterisitics it is also in mm and 3 decimal places. still can't figure out where is the 4 digits coming from once in a while.

Adam, This is a generic crash error, from this alone the cause can not be determined. However It maybe due to using an updated Windows 11 machine with an older version of the INSPECT software. Please see the link below for details on that issue and what can be done to resolve the issue. https://www.zeiss.com/metrology/en/software/software-information-hub.html If that doesn't resolve your issue you will need to pull a GOMSIC and enter a support ticket. https://portal.zeiss.com/knowledge-base?id=3047314

You will create a Surface Profile characteristic for each surface; next, in one of the Surface Profiles you will turn on the CZ/SIM; finally once the CZ/SIM is activated you can select all other Surface Profile and/or Positions that should be linked to that CZ/SIM.