Any order execution

[phil george]

In 4.1 - does anyone know how to turn this off. It's appears to be causing a prolem with a staged program using an equate alignment command that runs fine in 3.7 mr3. I don't see anything in the setup box. A registry setting perhaps?

[Don Ruggieri]

Any Order Execute Tolerance

You need to set the ANyOrderExecuteTolerance to 0 (zero)

I believe this is under F5 (Setup) in that long list of settings in the middle of the dialog. YOu should also be able to find it in the Settings Editor if you prefer.

0 disable this function, non-zero acts as the tolerance and enables the function.

[phil george]

Thanks, Don.

[JamesMannes]

Throw me bone...

Throw me a frickin bone, I'm the boss, I need the info....

What is any order and how do I use it? Can you say module(i.e. $$$)?

[Don Ruggieri]

How Stuff Works

Any Order Execute is a feature put in to accomodate measurements with "arm" machines, or any manual machine for that matter. It means that you can run the program and measure any feature at any time, it finds the feature in the program based on the results of the measurement, within a certain tolerance (AnyOrderExecuteTolerance). It uses colors in the edit window to identify which have been measured and which are yet to be measured. These same colors have created complaints for uses of standard (DCC) CMMs, but now in v4.2 even the colors can be turned off. Currently, turning off AOE does not turn off the colors.

[Matthew D. Hoedeman]

Any Order Execute is a feature put in to accomodate measurements with "arm" machines, or any manual machine for that matter. It means that you can run the program and measure any feature at any time, it finds the feature in the program based on the results of the measurement, within a certain tolerance (AnyOrderExecuteTolerance). It uses colors in the edit window to identify which have been measured and which are yet to be measured. These same colors have created complaints for uses of standard (DCC) CMMs, but now in v4.2 even the colors can be turned off. Currently, turning off AOE does not turn off the colors.

OKAY, so if this is for MANUAL machines or machines running in MANUAL mode (I sure wouldn't want Pcdmis to determine the order it will measure DCC features in ~ CRASH!), why then does this new function not AUTOMATICALLY shut itself off when it gets to the DCC command in the program? Maybe it's just me, but that sure sounds logical to me and Mr. Spock, if it is for manual, DCC should SHUT IT OFF automatically.

[craiger_ny]

I have to believe in DCC the program will stay linear. This is the first I've heard of this, I bet it would speed up manual a lot. I am already thinking of problems though. Who knows maybe they are handled well. I'd love to hear from someone who uses it.

Craig

[#2#]

So what happens when someone measures a feature not in the program?

[JamesMannes]

Thanks Don for answering my question. Don't mind the rest of my drivel re: module crap, I appreciate you taking the time(really I do, where do I send the beer?)

[Wes Cisco]

Thanks Don for answering my question. Don't mind the rest of my drivel re: module crap, I appreciate you taking the time(really I do, where do I send the beer?)

SSSSCCCHHHHHHLLLLLLLLLLLLUUUUUUUUUUUPPPPP!!!

Welcome to the club!

[Don Ruggieri]

Drivel??

Jim, that's ok, I had my drivel filter on

Actually, this is a built-in (non-modular) component integral to PC-DMIS. I just forgot to answer that part.

AnyOrderExecute does not change the DCC execute order.

If you measure a feature that is not in the program, this is the same as if you measure a feature which is too far from where it should be (as deinfed by the tolerance) you get an error message. It basically says that it could not find the feature, and then offers some options on how tp proceed.

I agree that the default AnyOrderExecuteTolerance should be '0' (to disable it) but I am not sure if that's currently the case.

[phil george]

It is NOT zero by default, unfortunately. At least not on the three machines I've looked at.