All Activity

Do you think I could pull in the sphere diameter or radius? using result element?

I looked through this... I like it.

I did set all the probes at .0001" from the default of .00039" We want to catch the "bad"/"contaminated" qualification and make it fail with a low limit value. We are normally hanging around .00002" to all zeros.....millionths in "S" are normal for our Duramax's

@Lincoln Knott https://portal.zeiss.com/knowledge-base?id=443334 This will help you create a program with report output, so you can verify sizes.

I would check out the "Set Limit Values" option inside the Probing System Qualification. The attached screenshot shows the deafult values which are very loose. I think a reduced sigma and potentially radius would've have flagged this error. Additionaly, it can also allow a max time between qualifactions. Since these options are all built in Calypso, it looks a great place to start and might satify your needs.

We had an issue last week where the new operator in a cell ran an "ALL" probe qualification program and he didn't clean the balls of at least one of the probes. This specific probe gets used alot in comparison to the other probes in the rack on this Duramax. So as you could imagine the cylindrical parts that he run, although "in spec" on his CMM because a contaminated probe qualification were all in face oversized for the OD measurements and undersized for the ID measurements. We had a meeting about this today because we now 96 parts that or out of spec...OD/ID. Tolerance for these diameter are ±.00025" I did some investigating on Friday and found that the CMM thought the ball of the stylus was about .0004" bigger than is supposed to be. These are bronze parts and the residue/dust from the machined parts coated the ruby ball stylus. I was asked in a meeting today... 1. Can I make a program that measures the reference sphere, and it reports the diameter of it. Which I could probably do, I'm thinking. 2. Can I somehow report the radius of the probes as it runs the qualification program. We want more information to be shown after the qualification program is done. It does show a presentation pdf, but these types of programs don't show anything. I attached the reports that get saved. The operators only see the presentation pdf, not the .txt file. -Anyway to add stylus ball radius and radius or diameter of the reference sphere? Lincoln Probe Calibration06_22_2642862026-6-22.pdf Probe Calibration52026-6-22.txt

I reread the dynamic profile section, and I don’t think my suggestion works for this part since the note says MAX and "MEASURED SURFACE". I think reporting profile with no datums and a unilateral tolerance zone in the + material direction would satisfy Note 17.

I have the same symptoms. I need to improve this as soon as possible.

Never used End-Park with a Rotary inside of AutoRun, but you could also just turn on the homing run inside of the measurement plan, so that it will always home before starting - this would negate any stacking of misalignment.

Sorry I did not respond. Been occupied on another issue. This absolutely worked. Thank you so much.

It was 100% the differently applied filter settings. Thanks!

Then make it part of the Cookbook purchase. 🤷‍♂️

Then maybe, if PMI becomes more important, a naming convention could be agreed on, so that there's no difference between the reporting and the naming in the PMI file. Nevertheless all customers that I've spoken with want to keep the traceability therefore they either use the naming that comes automatically when you create features in the CAD-software or they have special naming schemes defined in design and metrology so that no changes are required. Ideas for such a scheme can be taken out of ISO 7499 and ISO 7533 Hope that helps. Best regards Dinko

It makes a lot of sense when you go from reports like mine, to reports that could come from a PMI part.

Hello Everyone, several BUGs about this message have been reported in different constellations, according to development this issue should be fixed with the upcoming Servicepack 8.0.16. Best Regards Marcel

I have the latest patch installed, and I still have the problem so I don't think the Zeiss team are aware of this bug.

I have started getting this same problem too. I think it started with an old program, that was saved with new calypso version. very simple program too. Now it waits for minutes. and after starting, also hangs on other programs. Anyone found any fix? I havent updated to the last servi pack yet.

I just wanted to add that ISO is extracted surface by default, but it can also be associated element, if extra modifiers are use in a drawing: source -> https://www.youtube.com/watch?v=PllGdeZTuEg&t=440s

Also, I noticed that the create_surface_curve command seems to produce a result by clicking on just a single image in the interactive window. Does this approach rely on different logic compared you mentioned?

That's a classical linear size with some extra information that is not very relevant for the process itself. So the way to solve this would be GD&T Quick Creation -> Independency principle (as we have here an ISO based drawing) -> Select 2 planes -> Right click -> Enter given tolerances -> Done. Repeat until all three possible linear sizes are covered. Hope that helps Best regards Dinko

Good to hear that I'm not the only one it happens to - it does close down eventually, but it took several minutes to close down the PiWeb reporting - very annoying.

Hi Nanno, Regarding my application, I am developing an automated system to detect features (such as lines) in the images and programmatically generate surface curves by creating equidistant points along those features. Thank you for the guidance and resources. I will test this workflow and see how it works for my case. I appreciate your help!

And also a whitepaper is available for you to download. https://www.zeiss.com/metrology/en/c/pmi-in-metrology.html And for Creo Designers we offer a CAD training for MBD as well

Renaming the features makes no sense as it destroys the traceability in the MBD process.

Haven't thought of that, and I would not know how to apply it in v2022. Is this a capability that v2025 has?