Your Products have been synced, click here to refresh
1. Don't know about this one, it might be possible to "set" a program as the active partprogram - never tried. All your opened partprograms are available through the Application.PartPrograms collection.
Only the first active program in the first active instance of PC-DMIS will run online with the machine. I think you could do what you want by:
1. Using subroutines inside of PC-DMIS, with one master program and subroutine references pointing to the other programs;
2. External application that iterates through a list of programs; opening, executing, and then closing each one within one instance of PC-DMIS.
1. Don't know about this one, it might be possible to "set" a program as the active partprogram - never tried. All your opened partprograms are available through the Application.PartPrograms collection.
2. No, only one instance of PC-DMIS can be open at the time.
You can use Bladerunner. It is opening and closing each program but at least it is fully automated so it only takes a couple of seconds between each. You do not need to have Blade active on the port lock to use Bladerunner.
The timed interval cal program is a great idea. I'm definitely going to implement that. I'm thinking that I'll also have it keep a running list of serial numbers that have been checked on the machine since the last calibration and if the cal check fails it will print a warning message telling the operator to locate and quarnatine the parts on the list.
+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....
© 2024 Hexagon AB and/or its subsidiaries. | Privacy Policy | Cloud Services Agreement |