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

    New firmware 1.21RC3 available

    Scheduled Pinned Locked Moved
    Firmware installation
    31
    159
    23.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.
    • kraegarundefined
      kraegar
      last edited by

      Kind of odd. If I power on, go to the gcode console, and send G1 Z-10 S2 it'll move as expected. If I send the same thing again, though, no movement. But if I change the Z value to something else, like G1 Z-20 S2, then it'll move as expected.

      To further confuse me, now it's moving the opposite direction I should after a few more Z moves before homing.

      9:44:10 AMG1 Z-20 S2
      9:44:02 AMG1 Z-30 S2
      9:43:53 AMG1 Z-40 S2
      9:43:44 AMG1 Z-20 S2
      9:43:39 AMG1 Z-20 S2

      The Z-30 and Z-20 both moved the bed in positive Z instead of negative.

      Co-Creator of the RailcoreII CoreXY printer
      https://www.thingiverse.com/thing:2407174

      1 Reply Last reply Reply Quote 0
      • deckingmanundefined
        deckingman
        last edited by

        @whosrdaddy:

        @garyd9:

        Finally, I think this change is taking something away from users instead of giving something to them. It adds an (IMO) unneeded restriction that I'm not even sure makes sense (for cartesian printers.)

        Taking a WAG, it sounds like something an OEM might want in their firmware so the end-user doesn't drive an axis beyond a stop hear the steppers skipping. If that's the case, please make this an OPTION that OEM's can enable in config.g (or an option that everyone else can turn OFF in config.g) and not a requirement.

        Yes this should be a configurable feature!

        +1

        Ian
        https://somei3deas.wordpress.com/
        https://www.youtube.com/@deckingman

        1 Reply Last reply Reply Quote 0
        • Markdndundefined
          Markdnd
          last edited by

          @dc42:

          @Markdnd:

          Has current layer been removed from DWC in 1.21RC3?

          I can’t see it anywhere just a very inaccurate completion percentage where it used to be.

          (It claims I am 57.5% of the way through but the print has only 2mm to go of a 30mm print and is, in reality, at least 90% complete)

          Was the GCode file sliced by Cura? There is an issue with displaying the current layer when printing files generated by Cura.

          No, it was Simplify3D

          1 Reply Last reply Reply Quote 0
          • Mikeundefined
            Mike
            last edited by

            I'm getting "Error: Attempt to seek on a non-open file." upon trying to print files from slic3r PE on 1.21RC3. The same files work OK on 1.20.

            1 Reply Last reply Reply Quote 0
            • DjDemonDundefined
              DjDemonD
              last edited by

              I'm getting the same error on my corexy.

              M122 - https://1drv.ms/t/s!Apv79JfGbPIwg5QsmYhl9eYy6yVTZg

              when I try to downgrade to 1.21 rc2 I get

              M997 S0
              Error: M997: Firmware binary "Duet2CombinedFirmware.bin" not found
              

              I managed to restore RC2 after hitting erase and flashing it using SAM-BA.
              Working normally now, but still using wifiserver rc3, DWC rc3

              Simon. Precision Piezo Z-Probe Technology
              www.precisionpiezo.co.uk
              PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

              1 Reply Last reply Reply Quote 0
              • Mikeundefined
                Mike
                last edited by

                Same, the error pops on a CoreXY machine. As for reverting to an older version… Just rename the old firmware to Duet2CombinedFirmware.bin and proceed as usual. Worked for me.

                1 Reply Last reply Reply Quote 0
                • DjDemonDundefined
                  DjDemonD
                  last edited by

                  I tried that, it didn't work, perhaps I didn't get the filename exactly right but I copy and paste it knowing it would need to be.

                  Simon. Precision Piezo Z-Probe Technology
                  www.precisionpiezo.co.uk
                  PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

                  1 Reply Last reply Reply Quote 0
                  • tjb1undefined
                    tjb1
                    last edited by

                    @kraegar:

                    Kind of odd. If I power on, go to the gcode console, and send G1 Z-10 S2 it'll move as expected. If I send the same thing again, though, no movement. But if I change the Z value to something else, like G1 Z-20 S2, then it'll move as expected.

                    To further confuse me, now it's moving the opposite direction I should after a few more Z moves before homing.

                    9:44:10 AMG1 Z-20 S2
                    9:44:02 AMG1 Z-30 S2
                    9:43:53 AMG1 Z-40 S2
                    9:43:44 AMG1 Z-20 S2
                    9:43:39 AMG1 Z-20 S2

                    The Z-30 and Z-20 both moved the bed in positive Z instead of negative.

                    Those commands are being sent as absolute, once you move to Z-10, it can't go anywhere on the second Z-10 because it's already there. Same thing with the second issue, you are already at Z-40 and going back in the positive direction to Z-30 and Z-20, both are 10+ moves.

                    1 Reply Last reply Reply Quote 0
                    • garyd9undefined
                      garyd9
                      last edited by

                      I don't know if this was fixed in RC3 or not, but I just noticed the following issue in RC2:

                      When setting up a z-probe with P5 (It's a BLtouch) A3 (probe each location up to 3 times) and B1 (turn off bed heater while probing), the heater gets turned off for the FIRST of multi-tap probes, but not subsequent multi-tap probes.

                      So, assuming a M558 of:

                      M558 P5 X0 Y0 Z1 H5 F100 T4000 A3 B1

                      and a bed.g containing the following:

                      G30 P0 X1.1 Y-69.2 Z-99999
                      G30 P1 X-50 Y65.5 Z-99999
                      G30 P2 X49 Y65.5 Z-99999 S3

                      (and the manual levelling assistant configured.)

                      In each of the above probes, the heater is turned off for the FIRST test in each location, but the heater is turned back on (and stays on) for the SECOND probe. (My probes are apparently within 0.03 of each other, as I don't see a third probe in any location.)

                      "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

                      1 Reply Last reply Reply Quote 0
                      • kraegarundefined
                        kraegar
                        last edited by

                        @tjb1:

                        @kraegar:

                        Kind of odd. If I power on, go to the gcode console, and send G1 Z-10 S2 it'll move as expected. If I send the same thing again, though, no movement. But if I change the Z value to something else, like G1 Z-20 S2, then it'll move as expected.

                        To further confuse me, now it's moving the opposite direction I should after a few more Z moves before homing.

                        9:44:10 AMG1 Z-20 S2
                        9:44:02 AMG1 Z-30 S2
                        9:43:53 AMG1 Z-40 S2
                        9:43:44 AMG1 Z-20 S2
                        9:43:39 AMG1 Z-20 S2

                        The Z-30 and Z-20 both moved the bed in positive Z instead of negative.

                        Those commands are being sent as absolute, once you move to Z-10, it can't go anywhere on the second Z-10 because it's already there. Same thing with the second issue, you are already at Z-40 and going back in the positive direction to Z-30 and Z-20, both are 10+ moves.

                        Yep, I realized that once I had some more coffee. 🙂

                        Co-Creator of the RailcoreII CoreXY printer
                        https://www.thingiverse.com/thing:2407174

                        1 Reply Last reply Reply Quote 0
                        • Amiliousundefined
                          Amilious
                          last edited by

                          I think that I might have found a bug.
                          When doing the command
                          G1 X4 Y4 F200 S2;
                          only the X-axis moves

                          I am using this in my homeall.g

                          Here is my old homeall.g with added S2 does not work

                          [[language]]
                          G91				               ; Relative Positioning
                          G1 Z5 F6000 S2			; Lower Z
                          G1 X4 Y4 F600 S2             	; move away from the endstops
                          G1 S1 X-305 Y-305 F3000   	; course home X or Y
                          G1 S1 X-305               	        ; course home X
                          G1 S1 Y-305               	        ; course home Y
                          G1 X4 Y4 F600 S2             	; move away from the endstops
                          G1 S1 X-10                	        ; fine home X
                          G1 S1 Y-10                	        ; fine home Y
                          G90				                ; Absolute positioning
                          G1 X8 Y30 F5000 S2		; Move to first probe point
                          T0 				                ; select tool	
                          M280 P3 S160 I1			; release Z probe alarm
                          G1 Z5 F200 S2 			; lower bed
                          G4 P500 			                ; wait for the bed to lower
                          M401				        ; deploy the probe
                          G30 				                ; calibrate Z-axis
                          M402				        ; Retract Probe
                          G1 x0 y0 F5000			; Move to 0,0
                          G1 Z0 F200			        ; Move to Z 0
                          
                          
                          1 Reply Last reply Reply Quote 0
                          • Amiliousundefined
                            Amilious
                            last edited by

                            @DjDemonD:

                            I'm getting the same error on my corexy.

                            M122 - https://1drv.ms/t/s!Apv79JfGbPIwg5QsmYhl9eYy6yVTZg

                            when I try to downgrade to 1.21 rc2 I get

                            M997 S0
                            Error: M997: Firmware binary "Duet2CombinedFirmware.bin" not found
                            

                            I managed to restore RC2 after hitting erase and flashing it using SAM-BA.
                            Working normally now, but still using wifiserver rc3, DWC rc3

                            Maybe try renaming the old firmware that you are trying to downgrade to "Duet2CombinedFirmware.bin". The newer versions look for that file name, the same way you had to rename the Duet2CombinedFirmware.bin to DuetWiFiFirmware.bin when upgrading the first time.

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

                              When upgrading and downgrading between firmware versions in which the expected name of the firmware binary has changed, you need to take account of:

                              1. The binary name that the current installed firmware expects. Firmware 1.21RC3 expects Duet2CombinedFirmware.bin. Firmware 1.21RC2 on the Duet Ethernet expects DuetWiFiFirmware.bin. Firmware 1.21RC1 and earlier expect DuetWiFiFirmware.bin or DuetEthernetFirmware.bin depending on which board you have.

                              2. The binary name that the currently-installed version of DuetWebControl expects. DWC 1.21RC4 expects Duet2CombinedFirmware.bin. Older versions of DWC expect DuetWiFiFirmware.bin or DuetEthernetFirmware.bin depending on which board you have.

                              What always works is:

                              • upload the firmware binary you want to install;
                              • use the System Editor page of DWC to rename it to the name expected by the currently-installed firmware;
                              • send M997 to install it.

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

                                Okay, well that's simple enough. That was though just a minor issue, its the fact that RC3 doesn't seem to work on corexy that was the main event for me.

                                Simon. Precision Piezo Z-Probe Technology
                                www.precisionpiezo.co.uk
                                PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

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

                                  @DjDemonD:

                                  Okay, well that's simple enough. That was though just a minor issue, its the fact that RC3 doesn't seem to work on corexy that was the main event for me.

                                  Please provide more details of why RC3 didn't work for you, along with any relevant GCode files.

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

                                    It's working with my CoreXY OK.

                                    (I'm chasing some print artifacts, but they exist on 1.20 as well, so I don't think it's FW related)

                                    Co-Creator of the RailcoreII CoreXY printer
                                    https://www.thingiverse.com/thing:2407174

                                    1 Reply Last reply Reply Quote 0
                                    • Mikeundefined
                                      Mike
                                      last edited by

                                      In my case it was "Error: Attempt to seek on a non-open file." when trying to print anything sliced on Slic3r PE on my CoreXY. Reverted to the old firmware and finished the print without issues. I'll run a couple more tests on both my delta and the CoreXY in the evening.

                                      1 Reply Last reply Reply Quote 0
                                      • kraegarundefined
                                        kraegar
                                        last edited by

                                        I get that right at the end of files from Cura. Not at all from S3D. But it prints the full print for Cura.

                                        Co-Creator of the RailcoreII CoreXY printer
                                        https://www.thingiverse.com/thing:2407174

                                        1 Reply Last reply Reply Quote 0
                                        • DjDemonDundefined
                                          DjDemonD
                                          last edited by

                                          @dc42:

                                          @DjDemonD:

                                          Okay, well that's simple enough. That was though just a minor issue, its the fact that RC3 doesn't seem to work on corexy that was the main event for me.

                                          Please provide more details of why RC3 didn't work for you, along with any relevant GCode files.

                                          Hi David sorry scroll up a bit I provided a report and an M122. Corexy and attempting to print a SlicerPE file, so same issue others have had, downgrading just FW fixed it. Deltas working perfectly on rc3.

                                          Simon. Precision Piezo Z-Probe Technology
                                          www.precisionpiezo.co.uk
                                          PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

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

                                            I'm also running a CoreXY - didn't experience any issues with RC3 so far, about 5 prints or so successfully finished.

                                            DC42: I think it would make sense to add the new debug information about SD cluster size to M122 as well.

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