How to: Conditions.

[[Ry...]]

Hey Folks,

So I have a large program that is broken up into numerous mini-plans. One mini-plan I created for my operators to inspect the critical features of the part after machining but before anodizing. So it has some of its own characteristics that are tolerance compensated for the coating thickness. This program is run by the operators on all shifts, and because its off the CNC machine, the part does have the potential for dirt and FOD in the critical features. That if the operator doesn't clean the part well enough or forgets, of course causes probing/measurement errors. If this happens on my shift, no problems, clean and re-run the specific features. But not all of my operators are well versed in the programming and manual running of the CMM. Usually they just clean the part and re-run the whole program, hopefully adjusting the part count. And I come in the next day and review and clear out the piweb printouts that are duplicates. But this re-running does take time away from their machining, as well as holds up the machine this part is on. So I'd like to reduce that time wasting and make it easier in general for them to run these parts

I've never really used conditions before, but thinking they might be useful in this scenario.
I'd like to have the condition look at a handful of critical features (3-5 characteristics) and if any of them are out of tolerance, to bring up a manual input that states to re-clean part and then reruns only those features. If they come out a second time(not because of dirt), continue program and report results.

Now, is this doable without the PCM option?

Thanks for your time,
Ryan

[[Ow...]]

Quick and not a thorough answer but, because nobody else has, here's my thoughts..
I know you can put conditions in the characteristics or the feature strategy (if you run off features like most do) to stop a program with a message if the condition is not met or put a loop in the condition and re-run it the desired amount of loops put it if it's not met but, without PCM, I don't think you can automatically have it rerun just them characteristics without selecting and choosing to run selection in the start menu?
I've attached a crude example documents that you don't have to have PCM to use them and even thought it isn't very well explained , maybe give you some ideas.

Condition examples.docx

[[Ow...]]

$99 E-learning on the subject below in link.

https://shop.metrology.zeiss.com/zeiss- ... 3-0201-012#

[[Ry...]]

Owen,

Thank you for the reply and file.
I've taken the course you mentioned and it only gives the very basics of conditions, similar to the file you posted.
I guess I'm looking for something a little more complex where it understands that its measured the characteristics once already, prompted the operator for attention and proceeded to re-run. And if they are till out the second time, proceed with reporting of the results.

Maybe I'll send a email to my Zeiss Rep and make use of my yearly subscription service.

Thanks,
Ryan

[[La...]]

There's also a function called Repeat Measurement.

It alerts the user of characteristics out of tolerance and allows you to either Accept, Reject or Re-run the OOT characteristics.

This prevents the OOT data to be written to the PiWeb database until you are finished running the part & any re-checks.