All Activity

@xing xu I've never experienced this, but @Richard Shomaker reminded me, that today i had a situation, where i've turned/moved sensor and it was suddenly darker image and there was no ref. points marked. I had to increase from 17ms to 48ms and still not getting correct image. Then i touched optical cable to ATOS and it was loose. After tightening screw it was back on. Perhaps this can be your problem - since your images shows no crosses ( if they should be there )

Can someone please provide an explanation of, or reference documentation for, the correct procedure to create a 3D Best‑Fit Base Alignment using XYZ coordinate data collected from tooling balls on a fixture? Specifically, I am looking to understand the recommended steps, assumptions, and alignment methodology used to establish a stable and repeatable alignment from discrete tooling ball coordinate data, including any best practices related to datum selection, constraint application, and evaluation of alignment quality. Any guidance, examples, or standard work that outlines this process would be greatly appreciated.

It doesn't look like the sensor even sees anything. Is everything connected properly?

I would download the latest service pack for 7.8 which is 7.8.20

By update you mean download the latest patch or update to 8.0? Also wouldn't I need an SMA for them to help with this?

@Nicholas Nelson That was my original config and it didn't work after a couple of probe changes. The only other thing that I can't try is swapping the VAST-Gold sensor, which was replaced back in December.

Try updating Calypso first just to ensure it isn't a bug. If that doesn't solve it - you might have to reach out to Zeiss to have them take a look at it.

2d polar distance is the straight-line 2d distance between two features that lies on a Datum plane. Think about measuring the distance between two ends of a slot (but the slot is not normal to any axis). 3d polar distance is the straight-line 3d distance between two features. Think about a sphere to sphere distance

It truly depends on what you are doing. There are a lot of commands that can be ran without a PCM license, but some commands cannot (mainly runPCMFile).

That will cause issues though because since it is a point you are evaluating all three axis. The hole position should only be constraining its rotational angle, and the height location.

Hello All, I am trying to set up a pallet to run 18 parts in a batch. When I run the part in the calypso it works fine with no errors. The second I try to run the part on a pallet it runs through the first inspection, and will even spit out a piweb report then I get an system error, "unhandled exception :Message not understood #pointView. When I go into the error report it seems to be in regards to one of my result elements, and 2d curves. This happens in any spot on the pallet and it stops the inspection. This is on my offline machine Trying to get the pallet set up as a proof of concept before I take up time on the machine. This would be the first pallet my site has used, and the second one I have tried creating since class a few years ago. running caylpso 7.8.06 service pack 1

I have just started using Calypso 2025 (8.0.12) and using the new GD&T characteristics. In 2024, I had to do some irritating stuff to get my line profile plots to display correctly in Piweb. I have 2D curves that have one contiguous nominal segment, but there are multiple parts that I cannot measure due to physical obstructions or surfaces we simply choose to ignore. In order to get these to display properly, i have to: mask the unscanned portions with limit evaluation, use segment tolerances to define evaluation segments for the parts I actually check, create a dedicated Piweb plot page for each profile and explicitly bind them per page, and finally de-select the segments that were not measured or evaluated. This is what I came up with to get Piweb plots to behave like I was used to with curve forms and graphics elements. The GD&T line profile characteristic does not appear to transfer this segment information to Piweb. Instead, I have a single segment available, and while the portions of the curve that aren't measured or evaluated aren't shown as part of the plot, Piweb is connecting the nominal and tolerance band lines together across these masked zones. This is basically the same problem I had with the old line profile plots if I didn't use segment tolerances. These segments don't appear in the green circle tab in the GD&T line profile characteristic either. Is this something that anyone else has encountered? Is it fixed in a patch? I'm having to revert to the old line profiles and use secondary alignments to properly set orientation in the meantime.

Hallo Saskia, soweit ich weiß, brauchst Du für alle Maschinen die PCM-Lizenz.

Hello everyone, just a quick question. If i´m buying one PMC License for Programming, are all other Zeiss Machines cabable of running those programs? Thanks in advance

@Zen Cat No, keep position was not checked.

That makes sense why Randawggs suggestion of using the intersection of the axis to the od worked for me

Did you make sure that "Keep Position" isn't checked when you changed to the new alignment?

Sorry for the question, what is polar distance based on and what does it calculate? Does anyone have an answer?

Unfortunatelly many steps, but i can figure only this without python script and with basic training

I have never run into this issue before, but I can only run some of my curve features using the base alignment. It keeps crashing when I attempt to run a feature using a secondary alignment. I ran it using the base alignment and got actual data, then I tried to swap it to a secondary alignment afterwards. The result is that it moves all of my actual data around, really screwy. In the images below, my curve is right at the nominal line; the second image shows it all over with red arrows. I have not run into this before. Does anyone know what's going on and how to fix it? Calypso version 2021.

I've never used clearParameter(), and I haven't seen it used either. I'm sure there are some use cases for it, but I doubt it is absolutely necessary.

Ahhhh. I didn't think about performing a TP on it. Perfect, Martin. A lot of steps though. Hahaha.

Bump. Curious as well

Hello, This "Agreed. I would appreciate a method to manage license usage without needing direct access to the server machine where the license is hosted. " would be a great thing to put into My Voice. https://portal.zeiss.com/my-voice/software/metrology/product/eaafdea8-9296-485d-82c1-cc6d1ca0eca2 My voice is the place where you can put your ideas for improving the software.