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

    Unofficial RRF 3.4.0beta7+4 files

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    10
    23
    1.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 @dc42
      last edited by

      I have replaced the Duet 3 MB6HC and Duet 3 Mini main board binaries at https://www.dropbox.com/sh/i5vox3xmkd55gaz/AAC19mI0WEC5GmEjLOBRbKs-a?dl=0 with build 3.4.0beta7+5. This corrects the problem with servos and BLTouch connected to expansion and tool boards.

      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

      joekoundefined MikeDCundefined oozeBotundefined PetrKroupaundefined 4 Replies Last reply Reply Quote 0
      • dc42undefined dc42 referenced this topic
      • joekoundefined
        joeko @dc42
        last edited by

        @dc42 said in Unofficial RRF 3.4.0beta7+4 files:

        I have replaced the Duet 3 MB6HC and Duet 3 Mini main board binaries at https://www.dropbox.com/sh/i5vox3xmkd55gaz/AAC19mI0WEC5GmEjLOBRbKs-a?dl=0 with build 3.4.0beta7+5. This corrects the problem with servos and BLTouch connected to expansion and tool boards.

        yes this combination i use.
        duet3 6hc with toolboard

        1 Reply Last reply Reply Quote 0
        • MikeDCundefined
          MikeDC @dc42
          last edited by

          @dc42 thankyou 🙂
          I have updated to b7+5,
          i will let you know how I get on later 🙂

          1 Reply Last reply Reply Quote 0
          • oozeBotundefined
            oozeBot @dc42
            last edited by

            @dc42 Curious if anything was done about the chamber heater faults we've reported in 3.3b7+5? I see some changes from around the same time you released it in the repository, but don't know what they targeted. Thanks

            dc42undefined 1 Reply Last reply Reply Quote 0
            • PetrKroupaundefined
              PetrKroupa @dc42
              last edited by

              @dc42 Looks like there's something wrong with calling filament_error.g. I'm for sure have both files (with _ and with -) but still pause.g is called when fillament error. (6HC + 1LC + SBC) In beta7 work OK. beta7+5 no.

              BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
              SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

              Petr

              dc42undefined 1 Reply Last reply Reply Quote 0
              • Argoundefined
                Argo @joeko
                last edited by

                @joeko
                It does not help you now but I lower my currents to about 60% during homing or probing moves so the motors never have enough torque to cause damage.

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

                  @oozebot said in Unofficial RRF 3.4.0beta7+4 files:

                  @dc42 Curious if anything was done about the chamber heater faults we've reported in 3.3b7+5? I see some changes from around the same time you released it in the repository, but don't know what they targeted. Thanks

                  We've reduced the occurrence of spurious heater files in RRF 3.4b7 and further increased the tolerances allowed before reporting a heater fault on a bed or chamber heater in 3.4beta7+2.

                  When you turn the chamber heater on, how long does it take before the associated sensor shows a temperature rise; and at what rate does the temperature then rise? You can measure these when you start a heater tuning cycle.

                  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

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

                    @petrkroupa said in Unofficial RRF 3.4.0beta7+4 files:

                    @dc42 Looks like there's something wrong with calling filament_error.g. I'm for sure have both files (with _ and with -) but still pause.g is called when fillament error. (6HC + 1LC + SBC) In beta7 work OK. beta7+5 no.

                    Thanks, I've put this on my list to try to reproduce.

                    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

                    PetrKroupaundefined 1 Reply Last reply Reply Quote 0
                    • oozeBotundefined
                      oozeBot @dc42
                      last edited by

                      @dc42 The fault always seems to occur 15-20 minutes after heating. The temp begins rising almost immediately upon enabling the heater, but does take a long time to reach the target temperature.

                      Please watch this 25s movie I've linked below where it was ramping to 60c. Note the temp jumps around by .1-.2c. That's pretty typical while heating and what I feel is the cause of the fault.

                      https://vimeo.com/665779274

                      What I can't wrap my head around is the error states Heater 0 faults, but Heater 2 is the chamber and is what really faults. Maybe that is an unrelated issue..

                      1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined Phaedrux referenced this topic
                      • Phaedruxundefined Phaedrux referenced this topic
                      • Phaedruxundefined Phaedrux referenced this topic
                      • Phaedruxundefined Phaedrux referenced this topic
                      • RomeoFoxundefined
                        RomeoFox
                        last edited by RomeoFox

                        Have installed the firmware due to file upload issues. Now I get the following errors on every move which make it impossible to work:

                        Error: Driver 0.2 error: ok
                        Error: Driver 0.3 error: ok
                        Error: Driver 0.0 error: ok
                        Error: Driver 0.1 error: ok
                        Error: Driver 0.5 error: ok

                        Furthermore an event notification window appears.

                        FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.0beta7+6 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2022-01-13 18:24:07

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

                          @romeofox this is now fixed in the 3.4.0beta7+7files at https://www.dropbox.com/sh/i5vox3xmkd55gaz/AAC19mI0WEC5GmEjLOBRbKs-a?dl=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 1
                          • OwenDundefined
                            OwenD
                            last edited by

                            In 3.4.0b7+7, filament_error.g is not being called.
                            pause.g is run immediately.
                            It was working correctly in earlier 3.4b versions

                            gloomyandyundefined 1 Reply Last reply Reply Quote 0
                            • gloomyandyundefined
                              gloomyandy @OwenD
                              last edited by

                              @owend I think the file has gone back to filament-error.g with a "-" rather than "_" do you have one of those?

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

                                @gloomyandy
                                You nailed it, but it's the other way around in the release notes.
                                I renamed to filament-error.g and it ran the macro when the sensor tripped.

                                RepRapFirmware 3.4.0beta7

                                Upgrade notes:

                                The handling of filament errors have changed. When a filament error occurs, an event is created. To handle the event, RRF runs macro file filament_error.g without appending the extruder number to the file name and without pausing the print first. The extruder number is passed as param.D along with some other parameters. If filament_error.g is not found then the print is paused (running pause.g) and the error is reported.

                                gloomyandyundefined 1 Reply Last reply Reply Quote 0
                                • gloomyandyundefined
                                  gloomyandy @OwenD
                                  last edited by

                                  @owend It used "_" in the original beta7 but has changed back to "-" in the most recent builds (and will be this way in RC1)....
                                  https://github.com/Duet3D/RepRapFirmware/commit/3ac3345333659785dcd21088ae0b9b93ec914a4d

                                  RepRapFirmware 3.4.0RC1
                                  This release is still in preparation. Further items may be added before the release.
                                  
                                  The macro files run after events are now heater-fault.g, filament-error.g (as in RRF 3.3), driver-error.g, driver-warning.g and driver-stall.g instead of these names with the '-' character replaced by '_'
                                  

                                  a little confusing!

                                  0 dc42 committed to Duet3D/RepRapFirmware
                                  Replace '_' by '-' when generating macro name from event type name
                                  OwenDundefined 1 Reply Last reply Reply Quote 1
                                  • OwenDundefined
                                    OwenD @gloomyandy
                                    last edited by

                                    @gloomyandy
                                    Thanks for that.
                                    I had both files until yesterday.
                                    I couldn't remember which to use, so I looked at the release notes, but in honesty I do now recall reading the snippet you posted, so my fault.

                                    1 Reply Last reply Reply Quote 1
                                    • PetrKroupaundefined
                                      PetrKroupa @dc42
                                      last edited by PetrKroupa

                                      @dc42 - UPDATE: in BETA7+7 is called filament-error.g . Not filament_error.g.
                                      (6HC + 1LC + SBC + MFM)

                                      BigOne:Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 400x400x420
                                      SmallOne : Duet3 6HC +1LC + Rpi5 +SSD, mosquito hotend, 210x250x210

                                      Petr

                                      1 Reply Last reply Reply Quote 0
                                      • gloomyandyundefined gloomyandy referenced this topic
                                      • gloomyandyundefined gloomyandy referenced this topic
                                      • Fred-Yundefined Fred-Y referenced this topic
                                      • Fred-Yundefined Fred-Y referenced this topic
                                      • jay_s_ukundefined jay_s_uk referenced this topic
                                      • dc42undefined dc42 marked this topic as a question
                                      • dc42undefined dc42 has marked this topic as solved
                                      • jay_s_ukundefined jay_s_uk referenced this topic
                                      • First post
                                        Last post
                                      Unless otherwise noted, all forum content is licensed under CC-BY-SA