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

    RepRapFirmware 2.03RC4 available

    Scheduled Pinned Locked Moved
    Firmware installation
    10
    25
    2.9k
    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.
    • dc42undefined
      dc42 administrators @wilriker
      last edited by dc42

      @wilriker said in RepRapFirmware 2.03RC4 available:

      @dc42 Thanks.
      Just to clarify: this behavior is new with RC4 so probably when fixing the issue with M0 H1 something got switched in the order of execution.

      I just checked the code. The motors are set to idle current after stop.g has been run. So no change there.

      Of course, if the machine has been idle for more than the idle time when stop.g is run or within stop.g (perhaps because of a command to wait for something to cool down), then ordinary idle current reduction will kick in. But as soon as you move a motor, normal current should be restored.

      Edit: I've realised what might be happening, and I will fix it in the 2.03 release. Meanwhile, as a workaround, try adding a M400 command at the end of stop.g.

      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

      wilrikerundefined 2 Replies Last reply Reply Quote 0
      • wilrikerundefined
        wilriker @dc42
        last edited by

        @dc42 Thanks. I'll try that - and I think I also how have a clue what's happening. 🙂

        Manuel
        Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
        with probably always latest firmware/DWC (incl. betas or self-compiled)
        My Tool Collection

        1 Reply Last reply Reply Quote 0
        • Cavemanundefined
          Caveman
          last edited by

          Bed mesh level still the same issue as before. Z0 is all over the place. 2.02 works perfectly???

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

            @caveman said in RepRapFirmware 2.03RC4 available:

            Bed mesh level still the same issue as before. Z0 is all over the place. 2.02 works perfectly???

            Is this with 2.03RC4 ? Are you getting any warning messages on the console?

            Please provide a sequence that reproduces this issue for you, along with all the files needed to reproduce this (config,g, homing files, bed.g if used, and a very short GCode file to print if printing a file has to be part of the sequence).

            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
            • Cavemanundefined
              Caveman
              last edited by

              Whenever I have a wrong Z0 I get the message that the map has a substantial Z offset.....

              Sometimes I have a proper Z0

              0_1559504666357_2.03RC4meshleveltry_1.jpg 0_1559504682780_Error message_2.03RC4 meshbedlevel.jpg 0_1559504698147_@.03RC4meshbedleveltry_2.jpg

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

                @caveman How are you homing Z and how are you establishing Z0 before running the mesh compensation routine?

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • Gone2Farundefined
                  Gone2Far
                  last edited by

                  Had some odd leveling behavior on my delta.

                  Had a quite hard time getting G32 to converge on a particular height, but finally did. Then noticed several aborted probing points when running G29, followed by reports of 4.x mm max height error. After increasing the force needed by the smart effector from default to 128, got a kinda good height map. Now I have to edit the deflection setting in config.g--I had to add +0.15 mm baby step to get first layer correct. Everything was working quite well prior to upgrade.

                  Original Prusa i3 MK2S
                  Large Kossel Homebrew

                  1 Reply Last reply Reply Quote 0
                  • wilrikerundefined
                    wilriker @dc42
                    last edited by

                    @dc42 said in RepRapFirmware 2.03RC4 available:

                    Meanwhile, as a workaround, try adding a M400 command at the end of stop.g.

                    I can now confirm that this solves the issue.

                    Manuel
                    Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
                    with probably always latest firmware/DWC (incl. betas or self-compiled)
                    My Tool Collection

                    dc42undefined 1 Reply Last reply Reply Quote 0
                    • Cavemanundefined
                      Caveman
                      last edited by

                      Homing z happens by pressing home all. Establishing z0 happens by a papercheck.

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

                        @caveman said in RepRapFirmware 2.03RC4 available:

                        Homing z happens by pressing home all. Establishing z0 happens by a papercheck.

                        Can you post your homeall and config files?

                        Z-Bot CoreXY Build | Thingiverse Profile

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

                          @wilriker said in RepRapFirmware 2.03RC4 available:

                          @dc42 said in RepRapFirmware 2.03RC4 available:

                          Meanwhile, as a workaround, try adding a M400 command at the end of stop.g.

                          I can now confirm that this solves the issue.

                          Thanks. This should be fixed in 2.03RC5, which I have just released.

                          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
                          • T3P3Tonyundefined
                            T3P3Tony administrators
                            last edited by

                            Topic locked as RC5 is released:

                            https://forum.duet3d.com/topic/10786/firmware-2-03rc5-1-24rc5-released

                            www.duet3d.com

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