Bug with hotend temps?
-
I've been setting my temps using G10 P[x] S / R since going to dual extruders. I've noticed if I start a print from the web interface it waits for the nozzle to come up to temp as expected. However, both times I've tried starting a print from the SD card with the nozzle cold it's waited for the bed temp, then immediately started trying to print, despite my nozzle being way too cold.
Haven't tried again, since it's obviously not a result I want. Is this a bug, or was it just a fluke occurrence?
-
G10 sets heater temperatures for a tool, but heating doesn't start until you select that tool. If you want to wait for the heater(s) to reach temperature, us M116. In multiple-nozzle printers, you normally use this command in the tpost#.g file for each tool.
-
Gotcha. I can make that edit, thanks.
-
It's explained here https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Tool_change_files including how to wait for ther new tool to heat up without also waiting for the old tool to cool down.
-
Yeah, Using a single nozzle with two extruders, I didn't worry about that in my post yet, as I'm printing a single filament type all at a constant temp. It just bit me on the start of a print.
-
For a single nozzle machine, simplest is just to put M116 in your slicer start gcode.
-
That's actually what I did, M116 P0 in my startup code. I make sure all my prints start with the primary extruder. At some point I'd like to experiment with varying the temps at filament swap, and I'll add a M116 to the tpostX.g if/when I do.
