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

    Strange Behaviour in RRF3.0

    Scheduled Pinned Locked Moved Solved
    General Discussion
    4
    17
    577
    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.
    • jay_s_ukundefined
      jay_s_uk
      last edited by

      Odd.
      Might be one for @dc42 to jump in on

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      1 Reply Last reply Reply Quote 0
      • chas2706undefined
        chas2706
        last edited by

        @jay_s_uk

        What is really odd is that the RRF Configurator puts the M140 command in and also puts the M950 commands AFTER the M307's and I cant get the heaters to work in any other configuration!

        Thanks for your valued help and suggestions.

        @dc42

        David have you any suggestions on this?

        1 Reply Last reply Reply Quote 0
        • chrishammundefined
          chrishamm administrators
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @jay_s_uk
            last edited by dc42

            @jay_s_uk said in Strange Behaviour in RRF3.0:

            M950 has to come before and M308's
            See https://duet3d.dozuki.com/Wiki/Gcode#Section_M950_Create_heater_fan_or_GPIO_servo_pin

            No, M308 should come before the M950 that uses it, so that the sensor number used in the T parameter of a M950 H command already exists. OTOH any command that refers to a heater or fan number must come after the M950 command that creates that heater or fan.

            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

            1 Reply Last reply Reply Quote 0
            • chas2706undefined
              chas2706
              last edited by

              @dc42

              Even with that though I cant get my bed heater to show up on DWC or work without the M140 (set bed temperature) command that RRF configurator put in and the M307 autotune settings commented out.

              1 Reply Last reply Reply Quote 0
              • chas2706undefined
                chas2706
                last edited by

                @dc42

                What does the command M140 H0 actually mean?
                It is not documented.

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

                  @chas2706 said in Strange Behaviour in RRF3.0:

                  @dc42

                  What does the command M140 H0 actually mean?
                  It is not documented.

                  It's mentioned at https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M140_Set_Bed_Temperature_Fast but not well documented. It tells RRF that the first bed heater is heater 0. I'll add some more examples to the documentation.

                  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

                  1 Reply Last reply Reply Quote 0
                  • chas2706undefined
                    chas2706
                    last edited by

                    @dc42
                    OK thanks.
                    In my current config I have the commands in the correct order and includes the M140 command. All is well unless I uncomment my autotune setting for Heater HO.
                    The actual settings are:

                    M307 H0 A108.4 C735.4 D1.4 S1.00 V12.5 B0 ; Autotune result for bed

                    When uncommented I get this:

                    Screenshot (3).png

                    Thanks in advance.

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

                      M307 must come later in config.g than then M950 command that creates that heater.

                      More generally, where a command references some entity (e.g. a heater, fan, sensor, GPIO port, or additional axis), that entity must be created first. Example:

                      M308 S2 ... ; create sensor 2
                      M950 H0 T2 ... ; create heater 0, uses sensor 2
                      M307 H0 ... ; uses heater 0
                      M140 H0 ; uses heater 0

                      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

                      1 Reply Last reply Reply Quote 0
                      • chas2706undefined
                        chas2706
                        last edited by

                        @dc42
                        Thanks David that works great now!

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