Guest
Show Posts
71
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 05, 2016, 05:45:49 AM »
turn off and restart Mach3. However - when you come to turn it back on again - and restart Mach - make sure it's "taken" - here at least - sometimes you have to do it twice before the pump comes back on.
Anyway - no need - I simulated it all here and I'm getting pretty much the same results as you've described.
Turns out (here at least) that I can make it "work" by either using a USER DRO rather than the A DRO, OR by putting the M code in the button rather than using code "M..." from the button
If you use BOTH - like you're doing - it hangs the interpreter. So the M code never actually executes and (for example) the MDI is now hung.
So I guess the moral of the story is:
a) don't use OEM DROs for things they aren't intended for (which Hood was suggesting)
b) don't call M codes from macros (which I've been suggesting).
Just as an aside - during this I came across a bit of behavior which I don't really get. It seems that sometimes but not always (haven't investigated further) - if you have tool offsets cancelled, the mere fact of opening and then CLOSING the tool offset table turns tool offsets back on. That could bite you if you're not aware. E.g. you set a tool, you check the table, you set the next tool BUT you're now going to be setting the second tool with the first tool's offset applied to it - that's never going to end well.
Anyway - no need - I simulated it all here and I'm getting pretty much the same results as you've described.
Turns out (here at least) that I can make it "work" by either using a USER DRO rather than the A DRO, OR by putting the M code in the button rather than using code "M..." from the button
If you use BOTH - like you're doing - it hangs the interpreter. So the M code never actually executes and (for example) the MDI is now hung.
So I guess the moral of the story is:
a) don't use OEM DROs for things they aren't intended for (which Hood was suggesting)
b) don't call M codes from macros (which I've been suggesting).
Just as an aside - during this I came across a bit of behavior which I don't really get. It seems that sometimes but not always (haven't investigated further) - if you have tool offsets cancelled, the mere fact of opening and then CLOSING the tool offset table turns tool offsets back on. That could bite you if you're not aware. E.g. you set a tool, you check the table, you set the next tool BUT you're now going to be setting the second tool with the first tool's offset applied to it - that's never going to end well.
