Duet3D Logo

    Duet3D

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

    Firmware 2.02RC5 now available

    Firmware installation
    14
    47
    4906
    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.02RC5. It includes changes for CNC users, improvements to the 12864 display system on the Duet Maestro, other minor changes, and bug fixes. As always, read the upgrade notes before you install it.

      I hope this will be the last RC before the 2.02 release.

      Feedback:

      • If you try this release and it works well for you and/or fixes problems that you encountered with previous releases, please report that in this thread.
      • If you find any problems with this release and you have already read the upgrade notes and made any necessary changes to other files, please create a new thread with a title of the form "Release 2.02RC5 issue: " followed by a summary of the issue in a few words. It's hard for me to track multiple issues from different users in a single thread

      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 3
      • appjaws
        appjaws last edited by

        No problems with coreXYUV printer.
        Thank you David for all your hard work

        appjaws - Core XYUV Duet Ethernet Duex5
        firmware 3.4.4 Web Interface 3.4.4
        Ormerod 1-converted to laser engraver, Duet wifi
        OpenSCAD version 2022.10.09
        slic3r-1.3.0, Simplify3D 4.1.2, Cura-5.2.1

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

          No issues noted thus far.

          Z-Bot CoreXY Build | Thingiverse Profile

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

            Seemed to work last night.

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

              9:45:28 PM
              Finished printing file 20mm_cube.gcode, print time was 0h 34m
              9:44:42 PM
              Error: Internal Error in Read at ../src/Storage/FileStore.cpp(281)
              Error: Internal Error in Close at ../src/Storage/FileStore.cpp(148)
              9:11:28 PM
              M290 S-0.05
              9:11:05 PM
              M32 "20mm_cube.gcode"
              File 20mm_cube.gcode selected for printing

              This is the only issue I have noticed with RC5.

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

                @zzing said in Firmware 2.02RC5 now available:

                9:45:28 PM
                Finished printing file 20mm_cube.gcode, print time was 0h 34m
                9:44:42 PM
                Error: Internal Error in Read at ../src/Storage/FileStore.cpp(281)
                Error: Internal Error in Close at ../src/Storage/FileStore.cpp(148)
                9:11:28 PM
                M290 S-0.05
                9:11:05 PM
                M32 "20mm_cube.gcode"
                File 20mm_cube.gcode selected for printing

                This is the only issue I have noticed with RC5.

                Have you any idea what provoked the Internal Error messages? I presume you didn't remove the SD card before the print finished?

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

                  Hi David
                  Test 2.02RC5 on my Scara
                  Homing ok 🙂 --> oup's ko 😞

                  But after homnig absolute movement return error
                  possible move just on relative movement ...
                  Move on G90 impossible ...

                  G90 ; absolute movement
                  G1 Y0 X0 F1000
                  Error: G1/G2/G3: intermediate position outside machine limits

                  UPGRADE ...

                  David if i remove G1 S2 X1 Y-1; on my homeall.g before G0 I always have the same error as on the versionn 2.02RC4 brief G30 does not work and homig is wrong ...

                  ; Home Z ir-probe
                  G91; Add test ...
                  G1 S2 X1 Y-1; Add test ...
                  G90; absolute movement
                  G30; Single Z-Probe

                  In short on scara I have the same concerns as on version 2.02RC4

                  Scara with DuetWifi => Scarlette3D
                  https://youtu.be/mBF5cO8vGhI

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

                    Hi,
                    I'm still facing the perfect ,or more possible accurate ,calibration. And in the meanwhile I discovered a bug.
                    If I use the microstep 0.05 from the WC by pressing the Z-Baby stepping button, before or after a manual extrusion always from the WC ,the printer replicate the same extrusion as an other manual input (see picture ) . If this happen when the filament is near the nozzle occur the muse bite because the gears run faster the capability of the nozzle to release the material . (this because the manual extrusion for load the filament is done fast - my printer have near 15cm between the nozzle and the extruder gear)
                    I can reproduce this as many time I want.
                    0_1543604153341_20181130_193358.jpg

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

                      Working fine on my dual idex bigbox

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

                        @giostark said in Firmware 2.02RC5 now available:

                        If I use the microstep 0.05 from the WC by pressing the Z-Baby stepping button, before or after a manual extrusion always from the WC ,the printer replicate the same extrusion as an other manual input (see picture ) .

                        Thanks for reporting this, it's on my list to investigate.

                        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

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

                          Working fine on homebrew kossel.

                          Original Prusa i3 MK2S
                          Large Kossel Homebrew

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

                            @dc42 correct, no pulling of SD. There really wasn't anything I was doing directly, except for being in proximity to it.

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

                              @frafa said in Firmware 2.02RC5 now available:

                              Error: G1/G2/G3: intermediate position outside machine limits

                              Are you certain that X0 Y0 is accessible in a straight line from the initial position? What happens if you use G0 instead of G1?

                              This is the homeall.g file on my SCARA:

                              ; Home All file for Robotdigg SCARA arm printer
                              M561			; cancel bed compensation
                              G91
                              
                              G1 S2 Z28 F1000		; raise Z to keep nozzle clear of base frame
                              
                              G1 S1 X200 Y200 F1000	; home proximal and distal arms
                              G1 S2 X-5 Y-5 F1000	; back off
                              G1 S1 X10 Y10 F200	; repeat the homing more slowly
                              
                              G90
                              G1 X-75 Y75 F3000	; move to a position that correspond to one of the M557 grid points
                              G30			; home Z
                              G1 Z28 F1000		; move to safe height again
                              
                              G29 S1			; load height map
                              

                              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
                              • dc42
                                dc42 administrators @dc42 last edited by

                                @dc42 said in Firmware 2.02RC5 now available:

                                @giostark said in Firmware 2.02RC5 now available:

                                If I use the microstep 0.05 from the WC by pressing the Z-Baby stepping button, before or after a manual extrusion always from the WC ,the printer replicate the same extrusion as an other manual input (see picture ) .

                                Thanks for reporting this, it's on my list to investigate.

                                I confirm this issue. It will be fixed in 2.02RC6.

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

                                  Installed and working on a Larg-ish delta (600mm x 600mm). No issues found so far. Have done a couple of prints, one of them about six hours.

                                  And... this did clean up the HTTP line ends (reported in a separate thread, now marked resolved).

                                  Delta / Kossel printer fanatic

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

                                    Some odd behaviour during pause & resume:
                                    I have this in my resume.g:

                                    G1 R1 X0 Y0 Z3 F6000     ; return to point previously paused at (but above it)
                                    G1 R1 X0 Y0 Z0 F180      ; return to point previously paused at (lower nozzle)
                                    

                                    G1 R1 X0 Y0 Z3 actually moves to X0 and Y0 - instead of the "last saved point".
                                    Then it move 3mm down.
                                    Then it seems to continue to the correct "last saved point" location (not sure if this is still from with resume.g or already the next commanded move from my print code).
                                    Now it obviously crashes because the nozzle is too low.

                                    This is repeatable. Print something for a few minutes. Pause. (I usually do a filament change or clear a heat-creep and command some manual extrusion to prime the nozzle). The Resume. Then crash (if I'm not quick enough with the E-stop).

                                    I might have tweaked my config - but I don't see anything obvious in my version-controlled config files...
                                    @dc42 Should G0 R1 X0 Y0 behave the same as G1 R1 X0 Y0?

                                    edit: I just flashed RC4 again - and the problem is gone. So this is a regression in RC5.

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

                                      @David

                                      I have exactly the same problems as with version 2.02RC3
                                      https://forum.duet3d.com/topic/7316/firmware-2-02-release-candidate-3-now-available/70

                                      tested with your homing.all file adapted to my config, the same errors ...

                                      Downgrade 1.21RC3 waiting ...

                                      Scara with DuetWifi => Scarlette3D
                                      https://youtu.be/mBF5cO8vGhI

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

                                        @resam said in Firmware 2.02RC5 now available:

                                        Some odd behaviour during pause & resume:
                                        I have this in my resume.g:

                                        G1 R1 X0 Y0 Z3 F6000     ; return to point previously paused at (but above it)
                                        G1 R1 X0 Y0 Z0 F180      ; return to point previously paused at (lower nozzle)
                                        

                                        G1 R1 X0 Y0 Z3 actually moves to X0 and Y0 - instead of the "last saved point".
                                        Then it move 3mm down.
                                        Then it seems to continue to the correct "last saved point" location (not sure if this is still from with resume.g or already the next commanded move from my print code).
                                        Now it obviously crashes because the nozzle is too low.

                                        This is repeatable. Print something for a few minutes. Pause. (I usually do a filament change or clear a heat-creep and command some manual extrusion to prime the nozzle). The Resume. Then crash (if I'm not quick enough with the E-stop).

                                        I might have tweaked my config - but I don't see anything obvious in my version-controlled config files...
                                        @dc42 Should G0 R1 X0 Y0 behave the same as G1 R1 X0 Y0?

                                        edit: I just flashed RC4 again - and the problem is gone. So this is a regression in RC5.

                                        Strange, nobody else has reported this and I have similar lines in resume.g. I will test it again.

                                        RRF restores the last print position automatically immediately before resuming. Using G1 R1 commands is optional, and allows you to control how it is done. G0 R1 should behave the same as G1 R1 except that on some machines (e.g. SCARA) the movement may not be linear.

                                        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

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

                                          @dc42 I have a corexy. With RC4 it works as expected. RC5 moves to the wrong position.

                                          I suspect the G53&G54 changes might have introduced a bug?

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

                                            @resam said in Firmware 2.02RC5 now available:

                                            @dc42 I have a corexy. With RC4 it works as expected. RC5 moves to the wrong position.

                                            I suspect the G53&G54 changes might have introduced a bug?

                                            Were you using workplace coordinate offsets when this happened?

                                            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

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

                                              @dc42 said in Firmware 2.02RC5 now available:

                                              Were you using workplace coordinate offsets when this happened?

                                              No - I'm running in a simple plain FFF mode as 3D printer.
                                              I do not have any G53 or G54 codes in my sys/ or macros/ files.

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

                                                @resam said in Firmware 2.02RC5 now available:

                                                @dc42 said in Firmware 2.02RC5 now available:

                                                Were you using workplace coordinate offsets when this happened?

                                                No - I'm running in a simple plain FFF mode as 3D printer.
                                                I do not have any G53 or G54 codes in my sys/ or macros/ files.

                                                Thanks. Are you using any G10 tool offsets?

                                                EDIT: or M206 offsets?

                                                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

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

                                                  @dc42 said in Firmware 2.02RC5 now available:

                                                  Thanks. Are you using any G10 tool offsets?

                                                  The only G10's I have are hotend temperature and retract commands:
                                                  G10 10 P0 S0 R0, G10 S175 and similar.

                                                  EDIT: or M206 offsets?

                                                  No.

                                                  I do have a M208 with a negative Y minima - which I use as a pause position - maybe this is causing a weird edge case ("out of workspace"?)

                                                  My pause.g:

                                                  M83                      ; relative extruder moves
                                                  G1 E-2 F1200             ; retract
                                                  G91                      ; relative moves
                                                  G1 Z3                    ; raise nozzle
                                                  G90                      ; absolute moves
                                                  G0 X230 Y-5 F6000        ; move head out of the way of the print and clear nozzle
                                                  M106 S0                  ; fan off
                                                  

                                                  My resume.g:

                                                  G0 R1 X0 Y0 Z3 F6000     ; return to point previously paused at (but above it)
                                                  G1 R1 X0 Y0 Z0 F180      ; return to point previously paused at (lower nozzle)
                                                  M83                      ; relative extruder moves
                                                  G1 E2 F1200              ; undo the retraction
                                                  M106 R1                  ; restore fan speed
                                                  T R1                     ; restore tool selection
                                                  

                                                  I based these scripts on https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Pause_resume_and_cancel_files - but it seems some of it is redundant now because RRF already does the same steps before/after calling resume.g

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

                                                    Even though the G0 R1 and G1 R1 lines are not strictly needed, they should still work, at least if you are not using workplace coordinate offsets or tool offsets. As you are not using either of those, I don't know why they are not working properly. The negative Y coordinate is OK. I tested pause/resume in 2.02RC5 using this resume.g file:

                                                    ; Resume macro file
                                                    G1 R1 X0 Y0 Z2 F5000 ; move to 2mm above resume point
                                                    G1 R1 X0 Y0 Z0 ; lower nozzle to resume point
                                                    M83 ; relative extruder moves
                                                    G1 E4 F2500 ; undo the retraction

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

                                                      I flashed RC5 again - the bug is repeatable.

                                                      I added beeps to my resume.g to check when the faulty moves are made:
                                                      The G1 R1 ... commands in resume.g are not correctly executed. The head seems to be moved to (0,0) in absolute coordinates (front left corner).

                                                      The following similar moves in the firmware seem to be correct.

                                                      With RC4 this works as expected.
                                                      So this bug seems to happen somewhere during/before the execution of resume.g, because once we enter the resuming_1 state, it behaves correctly.
                                                      HandleMCode for case 24 is pretty simple - so I suspect DoFileMacro again...

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