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

    M109 not waiting if temp higher?

    Scheduled Pinned Locked Moved
    Documentation
    4
    10
    413
    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.
    • Chrissundefined
      Chriss
      last edited by

      Hi *,

      I understood that M109 is waiting till the temp of the hotend has reached the target temp. I have seen that this doe not work if the temp is above the target temp. Like temp is at 250 and I use M109 S130 to go down to 130C. the firmware does not pause and wait till 130C has bean reached. That is a bit confusing to be honest...... I know that I can solve that with a loop but I think it would be nice if the M109 behaves from higher to lower temps as it does fro a low temp to a higher temp,

      Cheers, Chriss

      oliofundefined 1 Reply Last reply Reply Quote 0
      • oliofundefined
        oliof @Chriss
        last edited by

        @Chriss You would need to use M109 R130 for a wait for cooldown. The documentation at https://docs.duet3d.com/User_manual/Reference/Gcodes#m109-set-extruder-temperature-and-wait does explain this, but it's a bit terse (-:

        <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

        Chrissundefined 1 Reply Last reply Reply Quote 0
        • Chrissundefined
          Chriss @oliof
          last edited by

          @oliof I see... thanks... but the tails goes
          bit deeper here with M116. 🙂
          Anyway, I think that the docu for M109 needs some more words....

          droftartsundefined 1 Reply Last reply Reply Quote 0
          • droftartsundefined droftarts moved this topic from General Discussion
          • droftartsundefined
            droftarts administrators @Chriss
            last edited by

            @Chriss Thanks, I've updated M109 to say:

            • Rnnn accurate target temperature, waits until within 2.5C of target if heating or cooling down

            However, M109 is deprecated in RRF, though still functional and in wide use by slicers. As suggested in the notes, it would be better to use G10/M568 followed by M116. I believe M116 waits for temperature when either heating up or cooling, though it can be bypassed by using the P parameter.

            Ian

            Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

            Chrissundefined 2 Replies Last reply Reply Quote 0
            • Chrissundefined
              Chriss @droftarts
              last edited by

              @droftarts Cheers, I will have a look at that as soon as my stall detection problem is gone......

              1 Reply Last reply Reply Quote 0
              • Chrissundefined
                Chriss @droftarts
                last edited by

                @droftarts
                That is not true unfortunately.... Me tool was at 150°C

                M568 P0 S30 A2
                ok
                M116
                ok
                

                M116 is not waiting till the temp went down. It does work for fine when the temp lower than the configured temp.

                I guess that I would need a loop here.....

                @dc42 : I have a feature request here: Could you please make M116 to wait for the temp also when the temp is higher than it should be, please? I understand that it may end up in a deadlock, like setting the temp to a value below the room temperature.

                @oliof : M109 does also not wait till the temp is currently higher than that target temperature... and it is deprecated anyway.

                Cheers, Chriss

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

                  @Chriss I'm pretty sure M116 does wait for temperatures to drop - that's the main reason I started using conditional gcode instead of M116 because I have a use case where I need to check if the temperature is at or above a set point and M116 always used to wait for the tool to cool.

                  However, something at the back of my mind tells me that there is a limit to how cold you can go because the ambient temperature could be higher than the set point so it could potentially wait forever. I couldn't find any reference to that for M116 but for M109 we do indeed have the following - quote.....

                  "Note: M109 will not wait for temperatures below 40c because in many cases they may never be reached due to ambient temps. So if you want to wait for a hotend to cool, use 41c or higher".

                  .... end of quote.

                  Given that M116 supersedes M109, I'd say it's a fair bet that the minimum temperature is also carried over. In your example you showed a set temperature of 30 degrees C which would explain why you are not seeing the expected behaviour.

                  If my assumption is correct then maybe @droftarts could amend the documentation for M116 to include the minimum temperature note.

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

                  droftartsundefined 1 Reply Last reply Reply Quote 1
                  • droftartsundefined
                    droftarts administrators @deckingman
                    last edited by

                    @Chriss I think M116 does wait for temperature to drop to target temperature, but I'm checking with @dc42. If so, I'll rewrite the Gcode entry to make this clearer.

                    @deckingman The note about M116 not waiting for temperatures below 40C is in the Gcode dictionary (and I just checked the old Dozuki version, and it's there too, so it has been for a while), see the end of the entry for M116 https://docs.duet3d.com/User_manual/Reference/Gcodes#m116-wait-for-temperature-to-be-reached

                    Ian

                    Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

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

                      @droftarts said in M109 not waiting if temp higher?:

                      @deckingman The note about M116 not waiting for temperatures below 40C is in the Gcode dictionary ................................
                      Ian

                      Don't know how I missed that - I feel a trip to Specsavers coming on........

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

                      Chrissundefined 1 Reply Last reply Reply Quote 1
                      • Chrissundefined
                        Chriss @deckingman
                        last edited by Chriss

                        To my future me:

                        This works:

                        M568 P0 S250 A2
                        M116
                        M568 P0 S150 A2
                        M116
                        
                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA