On 24 October 2014 12:37, David Armstrong <cncbas...@gmail.com> wrote:
> look at the toolchangers we did for the orac and triac. > and the interaction between stages to see that each is completed ,. far far > easier than remap It depends.. For that toolchanger, definitely. For a rack-toolchanger that works entireley with axis movements then a G-code sub is easier. Then you can re-map so that M6 calls the G-code sub. > in fact i hate remap , but i dont know why if i'm honest , it just does not > seem to dig deep enough . It can dig as deep as you want, if you care to. It can call Python code with access to the the status and command channels, or you can send canonical commands. http://www.linuxcnc.org/docs/html/common/python-interface.html descibes the linuxcnc.command and linixcnc.stat interfaces. > i'm looking at auto tool measuring as part of the toolchanger process , > which is proving difficult There is a sample config which may be close to what you need: http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=tree;f=configs/sim/axis/remap/manual-toolchange-with-tool-length-switch;h=287edcc6c855b8396b0d5a116f72d6de22dcec6d;hb=HEAD It does the probe with a G-code sub, but it would be possible (probably) to send a STRAIGHT_PROBE command. This test shows how to import emccanon and send motion commands directly: http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=blob;f=tests/interp/pymove/oword.py;hb=acd743ec4e4c34b2e89e06a4c521824ff4bb1417 But, this rather makes the point that toolchanging could potentially be easier for non-programmers :-) -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
