All Activity

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.

You can hold down CTRL and select multiple items in characteristics editor to change them all at the same time

I forgot about the dark mode and haven't checked it in the latest service packs, maybe its already better than initially.

I'm very interested in the new compact XXT for the Contura we have. I hope they will have it at IMTS in Chicago this year. We do swap sensors on our oldest Accura between XT and RDS. Very simple process - no need to shut down the CMM or Calypso.

Make a copy before editing 🙂

We had our IT department restore the computer back to a later date and that corrected the problem. Still don't understand what went wrong. But it is corrected for now. Until I get my fingers in there again. LOL. Martin and Norbet thanks for your help. It is appreciated!!

Hi the latest 8.0.3083.0.7f66405 update not avaible via Zeiss Download portal yet. I managed to install it when ZQS released it as an update. The new option to create a desktop shortcut is great, so you can now launch 2026 from the desktop. It would be nice if this option also appeared in KIOSK in Tools, so you could create a desktop shortcut from it.

Hi Friedbert , check below.😉

Schönen guten Morgen, ich bin der Kollege von Sittik und das Problem bzw. der Software-Absturz passiert immer dann, wenn wir folgendes machen: 1. Messreihe durchlaufen (inkl. Fahrt zur Home-Position) 2. direktes Anfahren einer Messposition (z.B. Messposition 13 von 32) 3. von dort "teachen" also manuell eine weitere Messposition hinzufügen 4. nachdem Messen und transformieren der Messung crasht die Software Mir ist dabei aufgefallen, dass nach Punkt 2 der kleine Pfeil neben den Messpositionen der Messreihe nicht auf die angefahrene Messposition zeigt und auch nicht mehr weiß sondern rot ist (er bleibt auf der finalen Home-Position). Fährt man die neue Messung von der finalen Home-Position an, funktioniert es problemlos. Ist halt nur manchmal einfacher, wenn der Robi schon halbwegs an der richtigen Stelle ist. Grüße aus dem Eisenwerk Brühl Martin

@ Norbert, danke für deine hilfreiche Unterstützung, bin zu den Ergebnissen gekommen die ich brauche. Die von dir vorgeschlagene Strategie hat reibungslos funktioniert.👋👍

I'm interested to hear from users regarding Zeiss's M.A.S.S. (Multi Application Sensor System) swappable sensor technology on Contura CMMs. Do you use multiple probe types (XXT, DotScan, ViScan, LineScan, VAST, etc.) on your Contura CMM? If so, how well does it work for you? Sidenote #1: but have any of you used ViScan on an RDS? I wonder how effective this 2D camera on an articulating sensor has been for users. Sidenote #2: Have any of you used the new Compact XXT? How does it compare in performance to the legacy TL3 XXT? Thanks for your feedback.

@Patrick Maguire I am confused. Are you asking if you can use an XML file to automatically adjust the tolerance of a characteristic inside Calypso?

Without code i can not help more. Perhaps there is something set in program and others not.

I understand, but the problem I'm having is that the exact code runs on one program, and not another. I have a preSetting.txt file that every program reaches out and reads, so I'm struggling to understand how randomly one measurement plan doesn't work.

You may be able to do this with basic PCM code. If you have access to the PCM Presetting's, you can add code. In my example I placed information that does nothing so I can edit on seats that do not have a PCM license and no access to Presetting's. Then I edit the "inspset" file. Search for my code words "This is your PCM Code" I can then edit the roughly 50 lines I added as needed with PCM. I have not delved into the exact code, but you would basically have to establish variables for your tolerances. example: (You may have to declare your variables) Dec2plcs=0.010 Dec3plcs=0.005 Dec4plcs=0.001 Degang=1 Then in the characteristic. Upper Tol. use Formula and add "Dec2plcs" Lower Tol. use Formula with a negative sign "-Dec2plcs" And so on for three places, four places and Angles. I can now use this file on a non-licensed PCM seat. (The injected Code needs to be injected within a licensed PCM seat). Where to add PCM code in the file when you have no PCM License, Presetting I am not sure. Ignore the dmesn line, I was testing something and should have removed it.

hab gesehen daß das ein DMIS-File ist. Muß wahrscheinlich "nur" das Format mit dem Kunden abstimmen

Hi Keith, using 15mm styli, probe midpoint + actual probe radius in result element is that correct? just to confirm thanks.

You may have luck with "Circle in Contour Fit" if you have Curve; otherwise, you may need to purchase 15mm probes and use self-centering points

hi all, any idea how to tackle this? distance over ball on torus. any help will be much appreciated. thanks in advance.

Hi, I am using a Aramis 3D in Inspect 2026 and am having trouble detecting markers in the Camera tab (no green '+' symbol). In the camera tab, the window of the camera's views does not show the green '+' on the detected markers, and there is an error notice saying "Cannot find reference points." I have tried adjusting the markers' distance from the camera and the exposure time, but green nor red '+' symbols ever appear. (first screenshot) After acquiring an image, in the Measurements tab, the points also do not appear. (second screenshot) However, in the Measurements tab, I am able to go to Define Component > Create Point Component, which then causes the green spheres to appear, and I am able to select the points to create a rigid body. On subsequent image captures, that rigid body is detected in its new position, and I am able to export stage data as a csv with that body's motion data. (third screenshot) Troubleshooting steps taken: power cycling, re-calibration, adjusting camera distance from markers, adjusting exposure time, adjusting Acquisition Parameters > Reference Point Type to Automatic, Any Size, and 1mm. Any assistance resolving the "Cannot find reference points" so I can see the green targets again would be greatly appreciated. Seeing the reference points in the Camera tab is important in my use case because it allows me to ensure the markers are detected before doing more time-consuming captures.