Flag "REJECTED / ACCEPTED

[[K...]]

I measured material thickness on 30 places, and reported. Now I want to report how many are out of spec, and if there are more then 3 are out, I want some flag on CMM report to show part is REJECTED and if less than 3 are out part is ACCEPTED.

Thank you

 

[[Mi...]]

Like this? It's a similar request I had. You could fairly easily modify this for your needs.

Program Pre and Post Settings

Post Settings of each Characteristic to be included in the count. Paintbrush is your friend. 

Result element to display the count.

Edited January 6

[[Je...]]

Please sign in to view this quote.

Inventive but significantly over-engineered.  There are 2 ways you can do this easier. 

1 - Put that formula in a "plugin_postcharacteristic_pcm.txt" file so you dont have to put it in every characteristic post-setting.

2 - Easier yet - Main Post-settings:
 

if (inspectionToleranceState("outOfTolerance") > 3) or (inspectionToleranceState("noResult") >3) then
setRecordHead("vda_remark","FAIL")
else
setRecordHead("vda_remark","GOOD")
endif

 

[[Mi...]]

First, I accidently clicked report on Mr. Penrods post... I think I cancelled it but to any admin that may review. It was unintentional, I was trying to quote quickly and failed...

Please sign in to view this quote.

Neither of your solutions completely solve the request that was put to me when I did this, or I would have been much happier to simply use the external file. Your solution may solve the OP's question as it will act for the whole program, but that certainly doesn't mean what I did was over-engineered. I'm also curious if you can still get away with not using the characteristic name in the code when it's in an external file reliably? When I did that before I had issues, especially when the program was running in AutoRun - that was an older Calypso version though.

#1 - I needed only a few of the characteristics in the program to have this, the engineer broke out the characteristics into 3 groups, Critical, Normal, and Reference Only. This code needed to act only on the Critical ones. The external file would act on all of them yes?

#2 - Engineer wanted a count of how many of the Critical Features were OOT, which goes back to #1.

#3 - Paintbrush tool to copy the post settings makes it only take a few seconds anyway

 

Edited Friday at 03:43 PM