Temp going to zero at tool change
-
Why do you set the temperatures multiple times?
Can you not simply set the temps, do those actions that can occur while the temps are rising, wait for the temps and then do the actions that should occur after the temps are stable?
That works for me.
And there is a command M116 that by itself will wait for all temperatures to reach their set point, you might find that useful.
Frederick
-
@fcwilt because if I use m109/m190 first it waits until temps are reached before advancing to any of the rest of my gcode. So it wouldn’t home or lower to my desired position until temp was reached.
-
@guycobb2 if you use G10 at the start of your start gcode to set the temperatures, then you can use M116 just before the print starts to ensure they are reached before the print starts.
-
@guycobb2 said in Temp going to zero at tool change:
@fcwilt because if I use m109/m190 first it waits until temps are reached before advancing to any of the rest of my gcode. So it wouldn’t home or lower to my desired position until temp was reached.
Hi,
Please read my post again.
It should be enough to use M104/M140 ONCE to start the heating processes and then use M116 ONCE where needed to wait for the heating to finish.
Frederick
-
@fcwilt yep, but G10 is preferred
-
@T3P3Tony said in Temp going to zero at tool change:
@fcwilt yep, but G10 is preferred
Hmm...
I don't see anything in the text on G10 that it actually starts the hearing process.
I just assumed it did what you can do from the DWC where the setting of temperatures is separate from the heater states (off, standby, active).
Frederick
-
@fcwilt G10 sets the temp both as standby and active for the tool it describes. Separately the tool state can be in one of three states, Standby, Active or Off. If it is Off then nothing happens, if it is standby the standby is set, if it is active the active is set.
That is why G10 is preferred in multiple tool (heater) setups because is explicitly sets those temperatures that are automatically toggled by Tn commands.
My answer was incomplete however because you do need to start with the tools in at least standby mode. My config.g does this by:
T3 P0
T2 P0
T1 P0
T0 P0
T-1 P0Which sets all the tools into standby without running any of the tool change macros (which would fail because the axis are not yet homed).
In @guycobb2 's case its a bit simpler because he has only 2 tools. I was just describing the general case.
-
@T3P3Tony said in Temp going to zero at tool change:
My answer was incomplete however because you do need to start with the tools in at least standby mode.
OK using G10 along with the T commands does make sense.
In reading the docs for G10 the form that allows setting the two temperatures is called out in the list of gcodes as "G10: Tool Offset"
Perhaps that should be altered to include something about setting of temps.
G10 certainly does a lot of different things.
Thanks.
Frederick
-
@fcwilt yes G10 is overloaded a lot.
The original logic for the temperatures being in G10 along with other offsets is that temperatures are just another offset that is applied to a tool!
-
@T3P3Tony said in Temp going to zero at tool change:
@fcwilt yes G10 is overloaded a lot.
The original logic for the temperatures being in G10 along with other offsets is that temperatures are just another offset that is applied to a tool!
Uh.... OK.... That seems a bit of a stretch.
Still the documentation of G10 could use a better heading than "Tool Offsets" don't you think?
Frederick
-
@fcwilt indeed:
https://duet3d.dozuki.com/Wiki/Gcode#Section_G10_Tool_Offset_and_Temperature_Setting(yes, i just added the temperature bit to the title!)
-
Thanks much!
