Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    How to Deactivate the Heater/s?

    Scheduled Pinned Locked Moved
    Duet Web Control
    8
    21
    1.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • gbartschundefined
      gbartsch
      last edited by

      Everyone, thank you for all the answers! I'll work with the information you all provided. Best regards ..

      Custom cartesian dinosaur machine; it's a tank but just works so I just keep tweaking it. / Duet Ethernet 1.02 or later / RepRapFirmware for Duet 2 WiFi/Ethernet: 3.4.5 / SuperSlicer

      1 Reply Last reply Reply Quote 0
      • gbartschundefined
        gbartsch @weed2all
        last edited by

        @weed2all said in How to Deactivate the Heater/s?:

        @gbartsch M104 S0

        I finally was able to look at this. I already was calling M104 in my end g-code but that wasn't deactivating the heater.

        M104 S0 ; turn hotend off
        M140 S0 ; turn heated bed off
        M84 ; disable motors
        M220 S100 ; set speed back to default
        M221 S100; set flow rate back to 100%
        G28 ; home all axes
        M18 ; deactivate steppers

        Custom cartesian dinosaur machine; it's a tank but just works so I just keep tweaking it. / Duet Ethernet 1.02 or later / RepRapFirmware for Duet 2 WiFi/Ethernet: 3.4.5 / SuperSlicer

        Phaedruxundefined 1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator @gbartsch
          last edited by

          @gbartsch said in How to Deactivate the Heater/s?:

          M104 S0 ; turn hotend off
          M140 S0 ; turn heated bed off

          Zero is "Off" for some definitions of "Off". 🙂

          Z-Bot CoreXY Build | Thingiverse Profile

          gbartschundefined 1 Reply Last reply Reply Quote 0
          • gbartschundefined
            gbartsch @weed2all
            last edited by

            @weed2all Thank you; but this didn't work: M104 S-273.1

            Custom cartesian dinosaur machine; it's a tank but just works so I just keep tweaking it. / Duet Ethernet 1.02 or later / RepRapFirmware for Duet 2 WiFi/Ethernet: 3.4.5 / SuperSlicer

            1 Reply Last reply Reply Quote 0
            • gbartschundefined
              gbartsch @Phaedrux
              last edited by

              @Phaedrux Thank you; but this M104 doesn't turn off or deactivate the heater block heater.

              Custom cartesian dinosaur machine; it's a tank but just works so I just keep tweaking it. / Duet Ethernet 1.02 or later / RepRapFirmware for Duet 2 WiFi/Ethernet: 3.4.5 / SuperSlicer

              1 Reply Last reply Reply Quote 0
              • gbartschundefined
                gbartsch @OwenD
                last edited by gbartsch

                @OwenD Oh. So for the heater block hear I would do M104 Hn S-276 where n is the heater?

                Custom cartesian dinosaur machine; it's a tank but just works so I just keep tweaking it. / Duet Ethernet 1.02 or later / RepRapFirmware for Duet 2 WiFi/Ethernet: 3.4.5 / SuperSlicer

                deckingmanundefined OwenDundefined 2 Replies Last reply Reply Quote 0
                • deckingmanundefined
                  deckingman @gbartsch
                  last edited by

                  @gbartsch M104 is deprecated so you would be better off using G10 or M568. For tools with multiple heaters, use the colon separator. Also be aware that turning a heater off isn't like a switch which removes power. Whether you set the temperature to zero or "off" you'll still have voltage on the positive side of the heater (PWM switches the negative side).

                  Ian
                  https://somei3deas.wordpress.com/
                  https://www.youtube.com/@deckingman

                  1 Reply Last reply Reply Quote 0
                  • OwenDundefined
                    OwenD @gbartsch
                    last edited by

                    @gbartsch
                    Yes Hn woul be H0, H1 etc depending on how many heaters you have.

                    I use these macros which should work regardless of the number of tools and heaters you have.
                    That said I don't have multiple tools and I don't have a chamber heater. I just try to "future proof" my code.

                    I also have an "all-heaters-off.g" macro which just calls each of these in turn
                    I put that in my stop.g
                    My slicer end code just calls M0

                    For tool heaters

                    ; Shut down all tool heaters and set temps to zero.
                    M291 P"Shutting down tool heaters" R"Heaters" S0 T1
                    G4 S1.1 ; wait for popup
                    var ToolsDone = 0 ; create a variable to cope with tools that are not sequentially numbered (unlikely but possible)
                    while (iterations < limits.tools) && (var.ToolsDone < #tools) 
                    	;echo "iteration " ^ iterations
                    	if (tools[iterations]!=null)
                    		if (#tools[iterations].heaters > 0) ; check if the tool has a heater to turn off
                    			M568 P{iterations} S0 R0 ; Set active and standby to zero
                    			M568 P{iterations} A0 ; turn off heater(s) associated with this tool
                    			M291 P{"Tool " ^ (iterations) ^ " is set to off" } S0 T1.5 ; report heater state of tool
                    			G4 S1.6 ; wait for popup
                    		set var.ToolsDone = var.ToolsDone + 1 ; Increment the number of tools shut off.
                    	else
                    		echo "Null value Tool number - skipping #" ^ iterations
                    		G4 S1
                    		continue ; we've encountered a non sequential move to next tool number without incrementing the ToolsDone variable
                    echo "All tool heaters are off"
                    

                    For chamber heaters

                    M291 P"Shutting down chamber heaters" R"Heaters" S0 T1
                    G4 S1.1 ; wait for popup
                    while iterations < #heat.chamberHeaters
                    	;echo "checking chamber heater " ^ iterations-1
                    	if heat.chamberHeaters[iterations]!=-1
                    		M141 P{iterations} S0 R0
                    		M141 P{iterations} S-276
                    		M291 P{"Chamber # " ^ iterations ^ " off"} R"Heaters" S0 T1
                    echo "All chamber heaters turned off"
                    

                    For bed heaters

                    M291 P"Shutting down bed heaters" R"Heaters" S0 T1
                    G4 S1.1 ; wait for popup
                    while iterations < #heat.bedHeaters
                    	if heat.bedHeaters[iterations] !=-1
                    		M140 P{iterations} S0 R0
                    		M140 P{iterations} S-276
                    		M291 P{"Bed heater # " ^ iterations ^ " off"} R"Heaters" S0 T1
                    		G4 S1.1 ; wait for popup
                    echo "All bed heaters turned off"
                    
                    gbartschundefined 1 Reply Last reply Reply Quote 1
                    • gbartschundefined
                      gbartsch @OwenD
                      last edited by

                      Thank you @deckingman and @OwenD

                      Sorry for such a late reply. Our family got the plague and I was last to succumb; I felt quite unwell and could not think. I've finally implemented your advice.

                      This is is my slicer start code. I've done as you suggest and used M568 in place of M104. Is G10 directly interchangeable with M568? Is one 'better' than the other?

                      Is there a way to let the let the nozzle heater stabilize before printing of the prime strip begins? Now the nozzle sits as the heater temperature ramps up and as soon as the first layer temperature is reached the prime strip is printed. But because the heater is ramping up it over-shoots by about 5C before dropping to the first layer temperature as the first layer begins. This doesn't seem to be a problem but I'm just wondering if there is a way to avoid the overshoot?

                      I'm quite clueless with g-code and have mostly hacked together what I have by copying what I've seen elsewhere over time. I sort of understand what your macros do @OwenD but am not entirely sure nor am I sure how these run.

                      Your slicer end code calls M0 to shut down the nozzle heater? How exactly does that look? Sorry I'm really am clueless with this.

                      G28 ; home all axes
                      
                      M140 S{first_layer_bed_temperature} ; set bed temp
                      M190 S{first_layer_bed_temperature} ; wait for bed temp
                      
                      G1 X100 Y5 F9000 ; move nozzle over middle of the front of the build plate
                      G1 Z1.0 F9000 ; lower nozzle 1.0mm from glass
                      
                      M568 S{first_layer_temperature} ; set extruder temp
                      M109 S{first_layer_temperature} ; wait for extruder temp
                      
                      G92 E0
                      G1 X50 E6 F300 ; extrude a thick line to prime extruder
                      

                      Custom cartesian dinosaur machine; it's a tank but just works so I just keep tweaking it. / Duet Ethernet 1.02 or later / RepRapFirmware for Duet 2 WiFi/Ethernet: 3.4.5 / SuperSlicer

                      deckingmanundefined dc42undefined 2 Replies Last reply Reply Quote 0
                      • deckingmanundefined
                        deckingman @gbartsch
                        last edited by

                        @gbartsch G10 and M568 do exactly the same thing. But G10 does a lot of things besides setting the tool temperatures which is why it has been deprecated. Think of the current situation as a transition period where both commands will work but it's highly likely that at some point in the future, setting tool temperatures using G10 will no longer function.

                        Ref the overshoot, as you say a 5 degree overshoot shouldn't be a problem when printing a skirt but you could use G4 to add a short pause after your M109.

                        Ian
                        https://somei3deas.wordpress.com/
                        https://www.youtube.com/@deckingman

                        gbartschundefined 1 Reply Last reply Reply Quote 0
                        • dc42undefined
                          dc42 administrators @gbartsch
                          last edited by

                          @gbartsch said in How to Deactivate the Heater/s?:

                          But because the heater is ramping up it over-shoots by about 5C before dropping to the first layer temperature as the first layer begins. This doesn't seem to be a problem but I'm just wondering if there is a way to avoid the overshoot?

                          Try increasing the M308 R parameter for that heater by 5% or 10% above the value that you got when you ran M303 heater tuning.

                          Duet WiFi hardware designer and firmware engineer
                          Please do not ask me for Duet support via PM or email, use the forum
                          http://www.escher3d.com, https://miscsolutions.wordpress.com

                          gbartschundefined 1 Reply Last reply Reply Quote 0
                          • gbartschundefined
                            gbartsch @dc42
                            last edited by

                            @dc42 Thank you. My firmware is 2.04 so maybe that's why I don't have M308 and an R value?

                            These are my PID Autotune settings:

                            M307 P13.1, I0.489, D46.8
                            

                            Other heater values are:

                            ; Heaters
                            ; -----------------------------------------------------------------------------------------------
                            M305 P0 T100000 B4092 R4700               ; set thermistor + ADC parameters for heater 0
                            M143 H0 S120                              ; set temperature limit for heater 0 to 120C
                            
                            M305 P1 T100000 B4395 R4700             ; set thermistor + ADC parameters for heater 1
                            M143 H1 S260                            ; set temperature limit for heater 1 to 260C
                            

                            Custom cartesian dinosaur machine; it's a tank but just works so I just keep tweaking it. / Duet Ethernet 1.02 or later / RepRapFirmware for Duet 2 WiFi/Ethernet: 3.4.5 / SuperSlicer

                            1 Reply Last reply Reply Quote 0
                            • gbartschundefined
                              gbartsch @deckingman
                              last edited by

                              @deckingman Thank you, I'll try M109 just to learn even though the temperature fluctuation levels out during the skirt printing.

                              Custom cartesian dinosaur machine; it's a tank but just works so I just keep tweaking it. / Duet Ethernet 1.02 or later / RepRapFirmware for Duet 2 WiFi/Ethernet: 3.4.5 / SuperSlicer

                              deckingmanundefined 1 Reply Last reply Reply Quote 0
                              • deckingmanundefined
                                deckingman @gbartsch
                                last edited by

                                @gbartsch To be clear, M109 will wait until the heater reaches temperature. My suggestion was to add an additional G4 pause after the M109 command. The length of the pause would equal the time it takes for the overshoot to settle. But DCs suggestion to reduce the overshoot would be better.

                                Ian
                                https://somei3deas.wordpress.com/
                                https://www.youtube.com/@deckingman

                                1 Reply Last reply Reply Quote 1
                                • First post
                                  Last post
                                Unless otherwise noted, all forum content is licensed under CC-BY-SA