The scenario. You have a part that you want to program different operations on different machines. Here is the problem the tool library is linked to the part file. This is fine if you program all operations on a single machine.
Now try to program different operations on different machines and see how this works for you. There are workarounds of course. Like maintaining multiple different assembly files that have the same part in them for different machines. This way the assembly file will have the correct machine linked to it. Example - part123_mazakajv404 and part123_moriseki40. It can be done but you will have to come up with a scheme that works for you. I am currently doing this very scenario as I write this.
The idea is for the CAM system to link the library to the machine, the same machine that was setup in the job setup. Which makes for less file management to maintain. When you switch jobs (changing the default setting) the correct library would be active. What's wrong with this idea? Just a thought - run with it or leave it.
Thanks for lookin,
Greg Haisley