Avoid Measurement If Feature is Obstructed?

[[Ma...]]

Hi
I'm trying to write a production program, where there is a possibility a hole may be obstructed due to a a "washer key" being installed. Is there a way to avoid probing the feature if the operator has flagged that it is obstructed?

here is my code so far in relation to "flagging":

WK = confirm("Does part have Washer Keys in the Ø " + M3_Nom + " hole?")
if WK == true then
Text2 = "Unable to check E08_0007DIAM_001_001 due to Washer Key obstruction in Ø " + M3_Nom + [color=#FF00FF]"hole"[/color])
[color=#0000FF]message[/color]([color=#00BF40]Text2[/color])
[color=#FF8000]endif else[/color]
[color=#FF8000]if[/color] [color=#00BF40]WK[/color] == [color=#FF8000]false then[/color]
[color=#00BF40]Text2[/color] = [color=#FF00FF]"No obstruction recorded in Ø "[/color] + [color=#00BF40]M3_Nom[/color] + [color=#FF00FF]"hole"[/color]
[color=#0000FF]message[/color]([color=#00BF40]Text2[/color])
[color=#FF8000]endif[/color]

[[Ma...]]

I've figured it out!
I needed to put WK as a Condition in the characteristic.

[[Er...]]

Why not just use missing bore and adjust the search distance. That way you don't need to depend on trained monkeys (operators) to answer you question correct. We have some operators, that I'm pretty sure can't read.

[[Ma...]]

hahaha! It's an idea, but i'd like to be able to completly bypass the measurement.

It seemed to work on the Offline station, but whilst proving out the program on the machine it wanted to measure the holes regardless of the answer. Am I missing something?

[[Ma...]]

[[Cl...]]

If this is a situation were the operator is answering a prompt as to whether the hole is obstructed or not, why
couldn't you just create a min-plan minus the hole. Then the operator can just choose to run the mini-plan?

[[Ma...]]

Please sign in to view this quote.

I wouldn't trust the operator to be able to select the mini plan when it isn't an obvious option. I'm trying to make it as idiot proof as possible.

[[Cl...]]

I completely understand, same here.

[[Er...]]

If you wish to make it idiot-proof. Missing bore is the way to go. Otherwise it's a 50% chance they mess up... And no one likes those odds...

But as you still seems to wish to have operator input. Go with clarke's way.
Make your question select the mini-plan with setRunID().

[[He...]]

If you want to use conditions on characteristics and still run from feature list you can use the same condition on all the strategies inside the feature. I don't remember if Calypso just skips the whole feature of if it just goes to the clearance position. I think it just skips it altogether.

[[Ma...]]

Please sign in to view this quote.

I managed to do that method, however you can't add the condition to the Clearance Position and because it is in a loop using the rotary table, it just rotates in a weird stepped fashon around 360° without probing. It works, but just looks odd.

[[Ma...]]

Please sign in to view this quote.

So you can use setRunID() to run a mini plan if a criteria is met?

eg

if SelectCondition == "Freestate" then
setRunID("Freestate")
endif else
if SelectCondition == "Restrained" then
setRunID("All")
endif

[[Er...]]

Yes.