All Activity

Hallo, danke das war die Ursache (nach dem Update). Jetzt geht´s wieder. Hatte da noch nie rein geschaut da es immer funktioniert hat.

I guess im going to install the latest sp and see if it still behaves like that

I had a similar problem. It was related to the license. In my case, it turned out to be a faulty cable connected to the USB port for the dongle.

Hi, after i was informed that 2026 release had indeed a flaw regarding the utilization of high core count CPU (i have 32C-64T) and the software was using maximum 16 Threads even if in option the logical core were set to 64. After updating to SP1 I observe the exact same behavior, so nothing changed apparently. I tried retesting 2025 release with latest SP installed and it uses all cores (in option i have the flaw on for use all cpu resources). I took a 18GB files of acquisitions and tried timing the 2 releases: 2026 did it in 4 minutes and 16 seconds while 2025 in 1 minute and 57 seconds. For us speed of polygonalization is quite important since we need the meshes right after the acquisition. If you need any king of specific information of log, setting, machine detail etc I'm welcome to give them to you to fix this problem with 2026 release.

PiWeb Reporting Plus 2020 has also stopped launching from the desktop shortcut!

I used the format from your original post (no "" around offsetCoordinates) and still got -0.1d for the 3rd value (-100.0). I used display() for output.

Have you tried AutoRun? Other than that it would most likely be an IT thing to setup user rights.

Hi, was this exported from a table? It is possible to edit the table template. The edited table is then called in the export function in the Kiosk. I do not unterstand this "change DN/DT to "Nominal"". If the property shows dN, there should be displayed 'Nominal'? Or is it about the arrangements of columns? Nanno

Hey, It only works properly for us if the sensor is calibrated in this way.

Hallo, wahrscheinlich werden auf der Reportseite Keywords abgefragt, die im Projekt nicht existieren -> "unbekanntes Keyword". Es könnte sein, dass unter Bearbeiten ► Projekt-Keywords... ein falsches Keyword-Set aktiv ist. Nanno

Hello, In fact, I was able to export the surface points in SW2025 as normal: after selecting the points in the expolorer: for stage projects File -> Export -> Stage Data -> CSV File -> Export -> Geometry-> CSV Regards, Mohamed

Hi Norbert, here u see what im getting here (ignore the parenthesis in front of val(), it doesnt change the result) And i swear, yesterday when testing the same code got me "" for coordsys = getParameterNamed("offtsetCoordinates",4)

I was also looking options to get *back* that important piece of information after updating and I couldn't find it. Thank you for providing solution, but this is a step *backwards* for users and I look forward to see it again.

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.....