Tool Selection and Tool Change Macros

[dc42]

A T command without the P parameter runs all the tool change macros. The only time it will block whole waiting for temperature when doing a tool change is if you have a M116 command in one of your tool change macros.

[gtj0]

@dc42 That's not how it seems to work now. I don't have an M116 in any macro but when I tap the tool button, I get "Changing Tools" and can't do anything else. The DWC does the same thing.

Let me try a few things though. Do the t* macros need to have executable commands in them for the no-wait to take effect?

[dc42]

No, the tool change files don't need to contain any commands. They can also be absent.

[gtj0]

Well, this is bizarre. I've always had the t* macro files in /sys and was experiencing the wait. Now it's working as you described.

Never Mind.

[Phaedrux]

Did you happen to have a temperature set when you enabled the tool?

[gtj0]

@phaedrux Yes. In every test I did I had both active and standby temps set. I know I was seeing the "Changing tool" message and waiting but I simply can't reproduce it now.

[zerspaner_gerd]

@gtj0 I have watched the same.
It only happens when all axes are homed (referenced).

[gtj0]

@zerspaner_gerd said in Tool Selection and Tool Change Macros:

@gtj0 I have watched the same.
It only happens when all axes are homed (referenced).

AhHa! Let me test that.

[gtj0]

Well, now I'm thoroughly confused. Regardless of homing and with the t* macro files deleted, I CAN'T get T0 to wait. @dc42 did something change where the T only waits if it's executed from a gcode print file or something?

[dc42]

@gtj0 said in Tool Selection and Tool Change Macros:

Well, now I'm thoroughly confused. Regardless of homing and with the t* macro files deleted, I CAN'T get T0 to wait. @dc42 did something change where the T only waits if it's executed from a gcode print file or something?

A T command will only wait for heating to complete if you have a M116 command in the tpost#.g file for that tool, to tell the firmware to wait.

[gtj0]

@dc42 said in Tool Selection and Tool Change Macros:

@gtj0 said in Tool Selection and Tool Change Macros:

Well, now I'm thoroughly confused. Regardless of homing and with the t* macro files deleted, I CAN'T get T0 to wait. @dc42 did something change where the T only waits if it's executed from a gcode print file or something?

A T command will only wait for heating to complete if you have a M116 command in the tpost#.g file for that tool, to tell the firmware to wait.

OK, That's not what the documentation says then... From the wiki for "T"...

Select tool number 1 as the active tool. will also set all other tools as inactive.

The sequence followed is:

Set the current tool to its standby temperatures specified by G10 (see above),
Set the new tool to its operating temperatures specified by G10 and wait for all temperatures to stabilise,
Apply any X, Y, Z offset for the new tool specified by G10,
Use the new tool.

At this point, the macros haven't been mentioned yet so that says to me that if there are no macros, T should wait.

Next...

There are normally three specified tool change macros (any of which can contain no commands if desired) that execute in this order:

Actions to do with the old tool before it is released - macro name: tfreeN.g where N is the tool number;
(Old tool is released);
Actions to do with the new tool before it is selected - macro name: tpreN.g where N is the tool number;
(New tool is selected); and
Actions to do with the new tool after it is selected - macro name: tpostN.g where N is the tool number.
With such implementations there is no wait for temperature stabilisation. That can be achieved by an M116 in any of the macros, of course. However be aware that recent RepRapFirmware versions does NOT run any tool change macros if the axes are not homed.

This section DOES say it'll only wait if there's an M116.

[dc42]

Thanks for pointing out the error in the wiki. I will correct it. [Edit: done.]

[gtj0]

@dc42 OK, Now things make perfect sense. I think my issue was that when I first started with the board I used the RRF Configuration tool and checked the "wait for temp" button. That created the M116 in my tpost0.g file and i never noticed it. I must have removed it in the confusion over the past few days days and not remembered that I did. I hate getting old.

[zerspaner_gerd]

Yes, I have M116 in tpost * .g macro (desired, for dual printing).
I am the wait time but not noticed with older firmware (1.21 or 1.20). Maybe by coincidence!

With manual DWC usage the wait time is very annoying.

I just found this setting

Does this really only for DWC operation, and does not apply to printing!

[dc42]

That only applies to tool selections made by DWC, not to T commands read from other input channels such as the SD card.