All Activity

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.

It can be a problem inside of those A1-9 variables. It complains about missing dot "." or right bracket ")"

wie kann ich einen DMO Report generieren ? Unter " export" finde ich nichts. Muß ich eine App installieren ? Gibt es verschiedene Formate ? Soll für Mercedes sein

I'm running into a weird error using executeCode. The great Eric Moberg wrote this snippet of code for me, and I have used it for years with no issues. Recently I have one measurement plan that it just doesn't work on. I get the following error. The code is loaded in, and ran via runPCMFile(preSettings), so this code lives inside of a txt file that is read by every measurement plan. Like I said, no other measurement plan is having issue with this, but apparently this measurement plan is. I just don't know what would cause it. Any thoughts?

I've searched forum and can not find it. There was a question on a spherical part with approx 45° angled cylindrical slots fixtured by top screw and author was looking for a dip on top to stop rotation. And one of the comments was that it's a job for optical. If it's not this thread, then i don't know which was it 🙂

Good morning. We were asked to report out results according to our requirements on our existing programs. Here's an example, If the print dimension is 25.475 ± .025 results would be reported 3 decimal places. If the print dimension is 25.47 ± .02 result would be reported 2 decimal places. My question is can I change decimal places to our existing programs by selecting multiple dimensions instead of going thru line by line?

I didn't even think of a start alignment. Thanks for that.

Well you can just fill XYZ from a sphere and nothing else. But i would fill start alignment and take granite scan and direction from that. Then you can run base alignment normally, but you just select start alignment from alignments list ( usually you have there "Existing alignment" )

oooohhhhhh. that would be awesome

I have a part that is basically a half sphere that is hollow. I need the ID and OD. I have never worked with spheres. How would I do the base alignment so that the machine can reliabley find the part to measure?

Hi, Indeed not automatically, manually i am able to. Thanks for your tips and responses!

yes good find Norbert ! I swore I attached an .xml, I'll search my files but I have a feeling it is gone, since migrating jobs, etc. Ah, I see , couldn't upload the .xml - so I posted the code; give it a shot. If you get it figured out, feel free to share with everyone ! good luck !!