Strange behaviour after program stop button pressed in axis

So I have found some time to do some debugging here. I found not all g-code runs would produce the same error. This helped me trace it down to a line that the Fusion 360 post processor is adding after the tool change (M6 T5):

G43 Z7.35 H5

Removing this line stops the error. I tried removing the Z7.35 and having only G43 H5 but the move after a stop command still occurs.

I would assume this means there is a tool length offset for this tool somewhere I don't know where to find. The Z value in the tool table (which I have been assuming is the tool length offset) is zero. Any idea why it does this?

Clearly I can remove the line but I'd like to understand the behaviour.

Richard

After reading the G43 description I am wondering if the recent addition of the 'tool touch off with probe' sim that ships with LinuxCNC might be part of this issue. I have a spindle with collets (cant set the tool length the same between changes) and I think I am running the manual tool changer - is this a potential problem?

I just got caught with this and F'd everything.

I'm not sure this has always been the case... or that it's a Fusion issue. The only thing that has changed for me is linuxcnc - currently on 2-9-0.

Did you get anywhere with this?

It appears to only occur on the mill, not lathe (I use fusion for both). From what I can see, STOP does not stop until DTG on all axis is 0. And that's a problem!!

This seems to be a 2.9 bug:

github.com/LinuxCNC/linuxcnc/issues/865

One suggestion (from rmu) is to add

260 emcTaskPlanClose();
+++ emcTaskPlanReset();

after line 260 in emctask.cc

This fixes the issue in my simulations, but AFAIK no task expert has looked at this yet

Thank you PCW.

Hi cadcam

I was tired of chasing this and wanted to get on with making things... I modified Fusion g-code to remove all M6 calls and I removed the remap function I had put in for M6. Now I just run single g-code files for each tool and the stop button behaves. Feels much safer and no disappointment of written of jobs.

I don't have a tool changer and this is a sensible workaround for me.

Reading the bug on github makes it clear to me that this is the same behaviour I was experiencing. That was on 2.7.14 I think and I am now running a master from some time ago (so 2.9) but haven't retested this issue. And they were definitely large g-code files doing 3d surfacing type work.