IMBoring25 wrote:Do you have an M563 P0 D0 H1 somewhere in config.g?
It shouldn't be interpreting the G10 command as a firmware retract unless the P parameter is missing and other than checking for the M563, the only other thing I can think of that might be confusing it would be that I've always set the temperatures (S and R parameters) and tool offset (X, Y, and optionally Z parameters) in separate G10 commands. I would expect 0,0 is the firmware default, so you might not even need those parameters.
Thanks for the response. Actually, I think I've sent you off on a wild goose chase here.
I now think it's nothing to do with config.g and is instead a problem with my initialization code in the main gcode file. I have this section:
Code: Select all
T0 ; Select T0
M104 S205 T0
M109 S205 T0
I added the extra 'T0' because of this problem
where M109 wasn't waiting until the head reached temperature. The suggestion there was to add an explicit T0 to make sure that Head 0 was the selected tool. I suspect that the retraction is an unintended consequence of that extra T0. Perhaps Duet is seeing the T0 as a tool change (even though there are no other tools) and is therefore performing the retraction. I suspect I have a setting to turn that off somewhere in my slicer. Sorry for the misleading question. I need a single-step option in g code interpretation so I can see precisely which command is causing which action!