All Activity

You can self-center with an XXT, but mainly it works the best in probing in the Z axis (straight down). You could self-center with say a 0.8/1.0, and then measure with either a 0.3 or if you want more clearance a 0.2. I've used both 0.2/0.3 on our O-Inspect which is the same mechanically as the DuraMax. Just set the Probing Dynamics to say 5%, and it might make sure to change the speed for those features to a slower speed.

@Steve Baker I don't think so. Restarting Calypso would solve that.

Hi Gábor, the kiosk shortcut will be created when the kiosk setup script is run. I think it's handled a bit differently, because there is no license configuration saved with the kiosk shortcut. Instead it starts the kiosk script with this line as a target. You could copy and paste it to another shortcut if you deleted the kiosk shortcut for example. "C:\Program Files\Zeiss\INSPECT\2026\bin\ZEISS_INSPECT.exe" -kiosk -fullscreen -eval "gom.script.userscript.KioskInterface__Start()" Nanno

If you can't figure it out in PiWeb, then I think you'll be stuck with a print manager software or PDF editor. You could then use AI to write you a script that automatically stitches the cover letters to the PDF. GhostScript would be a good option. Here's a sample GhostScript powershell that AI wrote For example. CMM Exports PDF to a folder > When new files land in that folder Script stitches cover letter to front and back > Script saves PDF with cover letters to new file location. # ==================================================================== # Configuration: Update these paths to match your environment # ==================================================================== $watchFolder = "C:\Paths\To\WatchFolder" $outputFolder = "C:\Paths\To\OutputFolder" $frontCover = "C:\Paths\To\front_cover.pdf" $backCover = "C:\Paths\To\back_cover.pdf" # Path to the Ghostscript executable (Check your installed version number) $gsPath = "C:\Program Files\gs\gs10.03.0\bin\gswin64c.exe" # ==================================================================== # Set up the folder watcher $watcher = New-Object System.IO.FileSystemWatcher $watcher.Path = $watchFolder $watcher.Filter = "*.pdf" $watcher.IncludeSubdirectories = $false $watcher.EnableRaisingEvents = $true Write-Host "Watching $watchFolder for new PDFs..." -ForegroundColor Green # Define what happens when a new file is detected $action = { $path = $Event.SourceEventArgs.FullPath $name = $Event.SourceEventArgs.Name $outputPath = Join-Path $outputFolder $name Write-Host "New PDF detected: $name" # Wait for the file lock to release (ensures the file is fully copied before processing) $fileLocked = $true $retryCount = 0 while ($fileLocked -and $retryCount -lt 15) { try { $stream = [System.IO.File]::Open($path, 'Open', 'Read', 'None') $stream.Close() $fileLocked = $false } catch { Start-Sleep -Seconds 1 $retryCount++ } } if (-not $fileLocked) { Write-Host "Stitching covers to $name..." # Execute Ghostscript & $gsPath -q -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile="$outputPath" "$frontCover" "$path" "$backCover" Write-Host "Successfully saved to: $outputPath" -ForegroundColor Cyan # Optional: Delete the original file after processing to keep the watch folder clean # Remove-Item -Path $path -Force } else { Write-Host "Error: Timeout waiting for $name to unlock." -ForegroundColor Red } } # Register the event to trigger the action $job = Register-ObjectEvent $watcher "Created" -Action $action # Keep the script running continuously try { while ($true) { Start-Sleep -Seconds 1 } } finally { # Clean up the background job if you stop the script (Ctrl+C) Unregister-Event -SourceIdentifier $job.Name $watcher.Dispose() }

I did have Calypso open when I made the changes. Would that make the difference?

Chad, I don't hate this idea, but I don't think it will satisfy the requirement. There's a bit of this that doesn't make sense to me. As far as I know, the customer doesn't get printed copies of our reports. They only get PDF's or Excel files, or text files, so what's the point of having a coversheet, on the rear page of a packet, that doesn't get printed? Not to speak poorly of a customer requirement, but if I understood more, I'd be better prepared to satisfy the requirement.

Hallo, die Stufen könnte man in mehrere Stufenbereiche aufteilen und getrennt darstellen. Nanno

Since you already have a cover sheet for the front, couldn't you just print that twice and have the operator staple it to the back facing backwards? If the doesn't work for you, then there are virtual print manager software that can do this I think. For example, you can tell it to concatenate a document to the front and back of every thing printed. Something like [cover page] + [CMM Report] + [cover page]. Stuff like FinePrint or Print2PDF. I think you're going to have better luck doing this outside of PiWeb.

Richard, I've sent you the template I'm using.

@Martin Jánský is my hero. I had a special character in the directory name, so it was breaking the code. What a silly and embarrassing mistake. ❤️

@Casey Sigler Can you send me your PiWeb Report, and let me take a look at it? You can direct message me if you'd like.

I'm sorry Richard, I'm not understanding you. My current part has a report that's 4 pages total. The last page in the packet, needs to have a statement printed on the back of it, not on the front side with the data. So when I'm done, the report has a cover sheet with the statement (which I've done) and the back of the last page has the statement. No matter which side of the packet you see, all you see are the export restriction clauses.

Well.... wouldn't that only work on even odd number page of reports? Because if you have measurement data on (2) pages, then if it was on the back it would be watermarked over the last?

We have a Contura with an RDS that has both the XXT and DotScan, we also have it setup for an XTR. Great system, with no issues swapping heads. I even like that the Contura/Micura now have the ability to have a Rotary Table - makes gear inspections a breeze now.

But it needs to be on the BACK of the last page.

Yes, indeed

I would just think to just add a new page and then add the statement. You could also just add this as the header/footer to the Master Page, so that it prints on every page.

I need to add an Export Controlled Information clause to BACK of the last page in my PiWeb printouts, so it's still identifiable as sensitive information if the packet is face down. This last page back needs to be blank except for this statement. How can I set up PiWeb to print this on the back of the last page?

Very strange. Did you have CALYPSO and any programs open when you made the changes? Not sure if that would affect things.

Another option is to disable piweb reporting completely, then subsequently evaluate all your data (with reports enabled) during an overnight shift, or from an offline seat. We deal with lengthy reports with lots of CAD views and it feels terrible seeing the machine sit idle while the computer is "taking pictures" of itself!

But they are still for manual selection - it won't select +- 0,05 tolerance when nominal is x.0x. It works like ISO-2768 with tiers or like tolerated distance - example H8 tier - now table for from-to size will have that tolerance. But you can write a formula which would do that and place it to all upper and lower tolerances. In general - check nominal value as string - get number of characters after decimal point and report as tolerance value. All this can be editable in that editor for mass edition ( show formulas )

inspectionToleranceState will return #inTolerance or #outOfTolerance status of the inspection, then you could use something like defineProtocol("#medium","screen") if its in tolerance and defineProtocol("#medium","pdf") to enable the PDF if its out

@DWC Yes. I saw a forum thread about creating custom ranges for tolerancing (linked below) and wanted to see if anyone had dealt with custom decimal tolerancing. A lot of the prints I deal with has a decimal based global tolerance. Ideally, I would like to use a .xml or .tol file I can imbed into the CMM tolerance drop down. Custom tolerance bands: https://qualityforum.zeiss.com/migration/images/872_470e6c5cb2d0d776a844b7dc4be53f1d.pdf

I am not sure about using an xml file, but we do change probes, styli tips, coordinates, nominals, tolerances, scan speeds, density of scans all on the fly using an xlxs file and a custom interface that reads from the xlxs file to create the para file which is read into the program at run start. As an example, for one family of parts this xlxs file covers about 30-part numbers with varying sizes in all axis.

I now have XTR and XXT sensors, swapping takes minutes to complete. As of today, I do not mix sensors in a single program, I don't even know if that is possible or sensible. As for Probe racks, I designed a custom rack that sits above the XTR MSR 2.0 system (I have posts I the forum on this design). The design works as intended. In the past I worked on system that had an XT Gold, XTR, XXT, Dotscan and Viscan. The XXT, Dotscan and Viscan are all on the RDS head while the XT and XTR were of course a different system. This place was at the time a Zeiss vendor, I had access to all the goodies you could imagine, and it was glorious. Scroll through the posts to see the custom rack.