Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Duet firmware 2.03beta3 available

    Firmware installation
    18
    56
    4085
    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.
    • dc42
      dc42 administrators last edited by

      I've just released this at https://github.com/dc42/RepRapFirmware/releases/tag/2.03beta3. See the upgrade notes at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md for important change information.

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

        Just completed a 4 hour print, DuetWifi 1.02, CoreXY, no issues noted.

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

          i noticed 6 axis printer support. can you recommend 6-axis design mechanics ?
          or it is intended for future development ??

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

            @c310 I've already got a 7 axis machine running on Duet. Although it's only 7axes when homing. For printing it reverts to being a 3 axis machine. It's CoreXYUV with a separate load balancing/force cancelling gantry. So effectively XYU and V get course homed together, then fine homed individually. XY carries the 5colour hot end, UV carries the 5 extruders. The third XY gantry gets homed independently. After homing, the 6 Motors get re-assigned to a single XY gantry but the motor direction of the upper gantry is reversed so it does the opposite of the lower two gantries.

            1 Reply Last reply Reply Quote 0
            • Martin1454
              Martin1454 last edited by

              • If you try to use a G- or M-code that the firmware doesn't recognise, it will try to run a macro file of that name. For example, command M650 tries to run /sys/M650.g.

              Nice! - This will be useful for custom scripts!

              1 Reply Last reply Reply Quote 0
              • dragonn
                dragonn last edited by

                Strange, I read that:
                "If you used M141 to define a chamber heater using a heater number other than 0 or 1, the firmware crashed"
                And I used heater chamber on heater 6 and it worked fine on 2.03beta2.
                Will try beta3 in a few days.

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

                  @dragonn said in Duet firmware 2.03beta3 available:

                  Strange, I read that:
                  "If you used M141 to define a chamber heater using a heater number other than 0 or 1, the firmware crashed"
                  And I used heater chamber on heater 6 and it worked fine on 2.03beta2.
                  Will try beta3 in a few days.

                  Maybe it's OK if you use heater 6. Someone else used heater 5 and it always crashed on boot up.

                  1 Reply Last reply Reply Quote 1
                  • Jackal
                    Jackal last edited by

                    In earlier 2.03beta versions, if you auto-calibrated a delta printer then the motor positions were slightly wrong afterwards until you homed the printer

                    That's probably why I have been having weird height map when no hardware on the printer has been changed.

                    1 Reply Last reply Reply Quote 0
                    • wilriker
                      wilriker Moderator last edited by

                      Typo in release notes:

                      Known issues:

                      • Custom endstop input numbers in the M575 command (probe tool) don't work

                      Probe tool is M585. Also I am particularly interested in getting this fixed. Is that planned to be done before 2.03 final?

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

                        @wilriker said in Duet firmware 2.03beta3 available:

                        Typo in release notes:

                        Known issues:

                        • Custom endstop input numbers in the M575 command (probe tool) don't work

                        Probe tool is M585. Also I am particularly interested in getting this fixed. Is that planned to be done before 2.03 final?

                        Yes it will be fixed, probably in the next beta.

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

                          @dc42 Thanks!

                          1 Reply Last reply Reply Quote 0
                          • gavatron3000
                            gavatron3000 last edited by

                            M291 doesnt pause a tool change if the message is blocking ie M291 S2, the message now appears at the correct time but the tool change carrys on anyway until completed.

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

                              @gavatron3000 said in Duet firmware 2.03beta3 available:

                              M291 doesnt pause a tool change if the message is blocking ie M291 S2, the message now appears at the correct time but the tool change carrys on anyway until completed.

                              On my list to investigate.

                              1 Reply Last reply Reply Quote 0
                              • gavatron3000
                                gavatron3000 last edited by

                                thank you

                                1 Reply Last reply Reply Quote 0
                                • paboman
                                  paboman last edited by

                                  Updated to the 2.03beta3 then when uploading the last DuetWiFiServer.bin I get SKIPPED as response from DWC, why ?
                                  thx

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

                                    @paboman said in Duet firmware 2.03beta3 available:

                                    Updated to the 2.03beta3 then when uploading the last DuetWiFiServer.bin I get SKIPPED as response from DWC, why ?
                                    thx

                                    That happens if you upload DuetWiFiServer.bin to a board other than a Duet WiFi. What board do you have, and what does Duet Web Control think it is?

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

                                      @dc42 its an ethernet version, do I need that file ?

                                      wilriker 1 Reply Last reply Reply Quote 0
                                      • wilriker
                                        wilriker Moderator @paboman last edited by

                                        @paboman No, this file is only for the Wifi version.

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

                                          I Just installed beta3 and it's running well on my cartesian but I'm having an issue on the delta with smart effector. I decided to make a nozzle change that required me to reset the trigger height in the G31 and things have gone downhill from there.

                                          I am running through the steps of jogging Z until I get my paper trapped then...
                                          Do G92 Z0
                                          Do G1 Z25
                                          Do G30 S-1
                                          Get value from M114 and enter it into my G31 entry in config.g. So my config is now:
                                          M208 S1 Z-2.0
                                          M558 P8 R0.5 H12 F1000 T8000
                                          G31 X0 Y0 Z-0.32 P100
                                          Reboot...
                                          G28
                                          G1 Z0 <<- slight hit on bed. Absolutely no clearance. Need to jog Z up by .35 to get clearance

                                          I've run this a bunch of times with no luck and I'm starting to think that the Z value in the G31 is being ignored. I have looked and there is no other G31 anywhere.

                                          Did the procedure change or is my process wrong?

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

                                            @davea said in Duet firmware 2.03beta3 available:

                                            Get value from M114 and enter it into my G31 entry in config.g.

                                            Don't do that. Use the value that the firmware reports after the G31 S-1 command instead.

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

                                              Just ran the sequence again and used the value displayed in the results box (Stopped at height -0.319) . Updated G31 with no change in outcome - still slight hit on the bed. Need to jog Z up by .30ish to get clearance back.

                                              Also tried the same sequence on the cartesian and it appears to work as expected.

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

                                                On a delta, if you change the Z probe trigger height then you will also need to correct the homed height (M665 H parameter). The easiest way to do this is to run auto calibration, then save the new H value. Or you could just reduce the M665 H parameter by 0.3 in config.g or config-override.g as appropriate.

                                                DaveA 1 Reply Last reply Reply Quote 0
                                                • gavatron3000
                                                  gavatron3000 last edited by

                                                  Apart from the m291 issue I raised above. CoreXZ running normally. Just completed a 4 hour print

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

                                                    @gavatron3000 said in Duet firmware 2.03beta3 available:

                                                    Apart from the m291 issue I raised above. CoreXZ running normally. Just completed a 4 hour print

                                                    Thanks for the feedback!

                                                    1 Reply Last reply Reply Quote 0
                                                    • whosrdaddy
                                                      whosrdaddy last edited by

                                                      Ran a 2 hour print on my CoreXY yesterday, no problems to report 🙂

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