hexagon logo

Change the active machine for a part program.

Hey all,

here's what i'm trying to do. Many of our machines are dedicated to one part/one operation. In our UI, we would like to open all of the part programs that will run for a selected operation, when the operation is selected for the first time of the day. When the operator hits "Measure", the program will loop through all of the open programs, and measure the part. The problem i'm running into is that when you open more than one part program, every program except for the first one is set to "OFFLINE". Is there any way to change the active machine of an open Part Program or is some sort of safety feature built into PC-DMIS. Here's another thought, if i can't get around changing the ActiveMachine, would it be possible to use the "SpawnNewInstance" command and have multiple instances of PC-DMIS running, and loop through the instances of PC-DMIS?

Thanks in advance,

-Cappy
Parents
  • +1 We use BLADERUNNER and it works very well. Just set all of your programs you want to run in the op file and let 'er go. We have a timed interval calibration verification program set to run before each part. PC-DMIS reads a text file that is written with a "timestamp" and re-verifies the cal say after 2-3 hours. If the check fails, then it dumps straight into auto cal followed by another check.

    Makes life a whole lot easier....


    does this check if the calibration passes/fails also?
Reply
  • +1 We use BLADERUNNER and it works very well. Just set all of your programs you want to run in the op file and let 'er go. We have a timed interval calibration verification program set to run before each part. PC-DMIS reads a text file that is written with a "timestamp" and re-verifies the cal say after 2-3 hours. If the check fails, then it dumps straight into auto cal followed by another check.

    Makes life a whole lot easier....


    does this check if the calibration passes/fails also?
Children
No Data