All Activity

Hi PiWebians, Come across an issue I seemingly cannot fix. When plotting roundness in PiWeb it is “transposed” and there is no option to reverse it, if you use a legacy plot there is an option to transpose, this then makes the plot reflect the CAD evaluation when displaying points, which I can only assume is the true representation. Does anyone know how to transpose a PiWeb plot? Thanks in advance

Secondary Alignments and caliper distances are your keys to success here. The alignments will bring those numbers in line.

I am not sure if this Prismo is the Ultra or they are separate systems. I have worked with the large Prismo Ultra's at Cummins in Rocky Mount, and I swear those calibrations were under 1.0 for 1800 sizes. I could be wrong. Hell, I may be reading this report wrong, I usually don't pay them much mind. As far as I can tell, this particular CMM came in around 1.5, I thought it would have been lower.

We just had an error I've not seen before. The CMM was running a well-proven program through lunch. When we returned the stylus was in contact with the part, traffic light was red. The error was "418: problem with sliding average". I cleared the error and picked up where it left off. The stylus made contact with the piece, the sensor (VAST Gold) gave the green light indicating contact, and... seven entire seconds later the machine registered the hit. The machine moves normally and seems to be measuring fine, but every single-point-strategy cylinder in this program suffers from the same problem; it takes between 1 and 7 seconds to register a hit after contact. It appears this only happens with this program as I was able to successfully re-run a piece from another lot of a different part number with none of the weird behavior. There have been no collisions. The machine has run 2 shifts 5 days a week since calibration two weeks ago. It's an Accura2 with VAST Gold. I saw planes run, both single points and scanned; no problem. I saw 2D curves run without any issue. I changed the affected cylinders to other stylus systems and the problem persisted. I ran a qualification (Master Probe and another stylus), no issue. All cylinders mentioned here are oriented along the Y axis and at very similar X/Z positions. Probing forces and speeds are identical. It's an obscure problem. Is it familiar to anyone?

Can you explain how you did this?

Can anyone tell me what causes the Status Window to clear? We've had times in the past when we found it to contain just a day or two of data (fewer than 20 lines). Today, for other reasons, I restarted the computer running Calypso, restarted the C99, homed the machine, logged in as multiple users... None of these cleared it. The boss wants to know what's up. Mind you, we do know how to change the number of lines displayed in the window. We do know how to collect the sm_events.dat file. We do know about the C99 side logs as well.

I went to the portal to look at something, and I didn't see anything older than (2020) 7.0 Did Zeiss remove older version from the download portal? Lincoln

Thems R facts. The Zeiss technicians always tune the CMM to achieve the best possible results; even when they are well within the machines stated MPE.

In real life, if everything is working properly, then you'll always have a much smaller length measurement error than the stated MPE value. If you look at your calibration certs, you'll see they are well under the stated MPE values. I take care of my machines and that's the case for me at least. That's why the Prismo Ultra will advertise it's capable to 0.5 + L/500 µm, but its stated MPE is only 0.9 + L/350 µm.

I thought they were capable of 0.9 if all the requirements were met like temperature, humidity, and temp fluctuation over a specified time. but it could depend on which prismo you have as well.

Use theoretical alignments (Perfect rotations, locations), create the alignment from the part center relative to the slot, rotate to where the slot is built around the alignment.

How are you currently measuring the slots?

Is an MPE of 1.5+L/350 a high value for a Prismo 12/18/10 last calibrated in September 2026? I am under the impression a Prismo is capable of an MPE around 0.9.

I am dealing with several slots that are at odd angles to the X and Y axis. One is at 3.83 degrees from the Y Axis, another is at 43.62 degrees from the Y Axis, and yet another is 12.77 degrees from the X Axis. I have created the slot features from my solid model. Our customer print defines the slot widths as .145 inch, and the slot lengths as .197 inch. While writing the program, the slot width and slot length measurements of the model vary significantly from the nominals in the print. I am attributing this to the odd angles. Am I correct? How do I overcome this? The print also calls out True Position in the X Only and in the Y Only direction. I am concerned about the accuracy of these position callouts due to the odd angles. I have considered creating alternate alignments to use for these slots, but do not have features suitable for the angles that are causing me problems. Any tricks that would help me out? Ken Quast

I was trying that, but i ended up with python scripts. I got some errors which prevented me with even simple onesided scan. Perhaps you will be lucky and find a way.

I have a 16mm sphere that works fine for 0.5mm probes

certain features like circles allow you to put in a reference feature which will allow you to move faster without the air scanning. for those I do a 3 or four point circle as my reference then in a separate feature use the scanning option to go faster. this is helpful if you have a problem child, but doing it for every circle is not always faster.

Appreciate the suggestion @Richard Stanich. My one issue would be that it is such a complex program; it would be a bear to transfer and could risk corruption. The way I got around this issue was by updating one feature at a time and saving each time. It was a pain, especially since it took about 2 minutes to save each time.

Is it possible to use the Zeiss Inspect (Kiosk) from a Scanbox with a handheld system (Atos5)? What needs to be adjusted in the custom patch, or is this not supported? I would appreciate any suggestions for a solution. Best regards, Alex

Correct, I had asked a similar question in regard to Scanning Optimization with the XXT sensor. It can only be disabled program wide and is not recommended to disable.

Drawing a straw. If its one program, create a new program and move everything over to the new program.

Hi team , i solve this measurement for one customer , examples see below. - construct line / or points on surface - construct points from line - construct element group from points - evaluate element group (max/min) - it depents on datum system (i used plane as one of axis)

if you have too mutch air scanning warnings you should ajust the stylus on calibration and in program the force from standard to rubust

Así es, muchas gracias!