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

    RepRapFirmware 3.0RC1 released

    Scheduled Pinned Locked Moved
    Beta Firmware
    19
    77
    5.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.
    • Edgars Batnaundefined
      Edgars Batna
      last edited by Edgars Batna

      Oh yeah, a versioning discussion!

      I'm waiting for final 3.0 release to finally get to merging some stuff into it. Do we have any significant non-functional (e.g. performance) improvements over 2.x? I've seen some threads discussing similar stuff, but nothing concrete in the release notes. I'm that guy running crazy PA values with many motors on high speeds so the Duet 2 CPU struggles (not complaining at the moment, just wondering).

      1 Reply Last reply Reply Quote 0
      • c310undefined
        c310 @3dmntbighker
        last edited by

        @3dmntbighker WoW! thanks!!!

        3dmntbighkerundefined 1 Reply Last reply Reply Quote 0
        • 3dmntbighkerundefined
          3dmntbighker @c310
          last edited by

          @c310 said in RepRapFirmware 3.0RC1 released:

          @3dmntbighker WoW! thanks!!!

          I had to "guess" the same thing 2 days ago because they didn't include those port names under Maestro? I presumed the names would be the same as on Duet WiFi (which I also have with a PT100).

          Scratch built CoreXY with Maestro
          Heavily modified Ender 3 with Maestro
          MPCNC work in progress with Duet WiFi

          1 Reply Last reply Reply Quote 0
          • c310undefined
            c310
            last edited by

            another temperature / pin question:
            in RRF3 which ID should i assign to CPU temp sensor?
            in RRF2 it was

            M106 P1 L30 T44:63 H100:101 C"System"
            
            1riundefined 1 Reply Last reply Reply Quote 0
            • 1riundefined
              1ri @c310
              last edited by 1ri

              @c310
              i use this commands to declare the "virtual" sensors

              M308 S20 Y"mcu-temp" A"CPU" ; Defineix sensor S20 com a temperatura de la CPU
              M308 S21 Y"drivers" A"Duet_drv" ; Defineix sensor S21 com a temperatura dels drivers de la duet
              M308 S22 Y"drivers-duex" A"Duex_drv" ; Defineix sensor S22 com a temperatura dels drivers de la duex5

              In this case, sensors 20 to 22 to declare mcu & drivers.
              After that, use it as a standard sensor.

              Hope it helps you. I'm runing 3.0RC1 on a DuetWifi + Duex5 and there is no issue at all. A little tricky to configure but not impossible, using Reprap config tool as a start point.

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

                In the Upgrade Notes for RRF 3.0RC1 I forgot to mention that on Duet 3, there is no longer a default bed heater configured. Use M140 to configure one, for example M140 H0 will usee Heater 0 as the bed heater.

                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 1
                • 3dmntbighkerundefined
                  3dmntbighker
                  last edited by

                  For the record, 3.0RC1 on my Maestro seems to have the same issue Duets have always had for me. The DWC sometimes dies part way through the print. The print completes, but a hard reset is the only way to get the DWC working again. This happened in my WiFi as well.

                  Scratch built CoreXY with Maestro
                  Heavily modified Ender 3 with Maestro
                  MPCNC work in progress with Duet WiFi

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

                    @3dmntbighker said in RepRapFirmware 3.0RC1 released:

                    For the record, 3.0RC1 on my Maestro seems to have the same issue Duets have always had for me. The DWC sometimes dies part way through the print. The print completes, but a hard reset is the only way to get the DWC working again. This happened in my WiFi as well.

                    Are you able to get a M122 report from USB when that happens?

                    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
                    • supernovaeundefined
                      supernovae
                      last edited by

                      Got my Hypercube Evolution running RRF 3.0RC1 with bltouch, dual z leveling (g29) and so far so good!

                      took a bit to translate my config over, but i really appreciate the text labels now that i'm seeing them in gcode!

                      1 Reply Last reply Reply Quote 1
                      • DaveAundefined
                        DaveA
                        last edited by

                        Got both my cartesian (Maestro) and delta(Duet Ethernet) running on 3.0RC1 with no issues other than those that were self inflicted. I don't have any specific printing requirements right now so I've just been printing calibration stuff and Benchys but all is working well. Thanks guys for all the work.

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