Probe Change Command on Operator side

(Global Advantage 2013) We have two different programs that use two different probes, one uses a star probe the other uses an extended (straight) probe. As long as we are on the programmer interface and call up a program it will follow the command to change the probe head in the program, but when we switch into the operator only interface we get an error message and have to call up the program that uses the current loaded probe begin running then stop it and call up the program we want to run then it will change the probe head. In short on the operator side it acts as though it has lost what probe is currently loaded.

If we correct the problem once it will run fine switching between the programs as long as we dont exit out of the operator interface for machine shut down or program edits etc.

R2ah1ze1l over 1 year ago

What if you made a program using flow control so based on which machine is running, it can skip to the proper load probe?
I think you would need to duplicate the feature code, MachineA would use 1 probebuild and the MachineA feature group, then skip MachineB code. Then it would be visa versa when running MachineB.

I will warn, wrist angle changes will still take effect, so don't jump from a place with an A0B0 wrist to a place with A90B90, be sure the groups all use the same A#B# angle prior to the Loadprobe command. (This can also be handled with the F5 settings, but that is for you to determine how you want it handled)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel