On 9 March 2014 01:42, Michael Chism <[email protected]> wrote:
> http://www.flintmachine.com/pdfs/fadal-manuals/maintenance-manual/Automatic_Tool_Changers.pdf I wouldn't normally suggest this approach, but it might be the most expedient in this case. Assuming that you have already configured the XYZ and Spindle axes to work, and you are familiar with G-code, it might be quickest to configure the carousel and slide as machine axes and get the tool-changes working with a G-code subroutine. It is possible to re-map the M6 command to call a G-code subroutine, but the quick way is just to use a subroutine, for example O100 CALL [5] in place of M6 T5 in your code. Once it is working then further refinements and neater approaches can follow later when time is avilable (It would be painful to attempt to code timeouts and aborts in a G-code subroutine). There is one advantage of the G-code subroutine approach, at least the Z-axis moves are easy to arrange. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
