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

    It's out! Firmware 1.21 released

    Scheduled Pinned Locked Moved
    Firmware installation
    25
    73
    13.1k
    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.
    • c310undefined
      c310
      last edited by

      here is the gcode file done by slic3r

      0_1523467244888_óãîëîê ëåñòíèöû.gcode

      another thing is encoding of file name (now it is completely wrong. i guess it is about UTF... )

      0_1523467348988_unicode file names.png

      ...file name in explorer - i removed card from duetwifi and put into win10 machine ...

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

        Looks like Windows is displaying the filename in a local code page. DWC should handle Unicode if the installed font supports the particular characters. PanelDue supports Unicode characters up to 0x17F only.

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

          @dc42
          Yes, It is related to what slicer created the file

          If sliced with Repetier Host Cura, shown in the Generated by Cura_SteamEngin 15.01.
          The error happens when calculation Object Height/Layer Height/ and Filament Usage.
          Onec calculation is done only Object Height that has any data, Layer Height/ and Filament Usage has n/a

          All other slicers I tried worked just fine Slic3r 1.2.9, Slic3r 1.34.1-prusa3d-win64, Sl1c3r 1.37.1-prusa3d-win64

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

            Have you tried a recent version of Cura?

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

              Yes, I Forgot to put that in the info. Cura 3.2.1 works fine also

              1 Reply Last reply Reply Quote 0
              • BenDieselundefined
                BenDiesel
                last edited by

                I tried updating last night to 1.21. Got the firmware to go but the webserver is still at 1.19.2. And I can't seem to get the duettest.local to work any more. I uploaded a the files that the gethub said I should for the duetwifi.

                1 Reply Last reply Reply Quote 0
                • vonGreezlyundefined
                  vonGreezly
                  last edited by vonGreezly

                  SOLVED! See Below!

                  Hey all, Just updated to 1.21 from 1.18. Having issues with Homing (yes it's a corexy!, and yes I put an S2 after my G1 Z lines). Machine attempts to home, but the endstops no longer seem to trigger properly. The LEDs turn off when the endstop is hit on the board itself, but the printer keeps moving =~~

                  Also, confirmed w/ M119 that they're being seen when triggered...

                  Not sure what I need to do, but i'm losing the battle! Help! 😄

                  /code
                  G91 ; relative mode
                  G1 Z10 S2 ; Lift Z 10mm CYA!
                  G1 S1 X-382 Y-382 F3000 ; course home X or Y
                  G1 S1 X-382 ; course home X
                  G1 S1 Y-382 ; 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~~

                  -VG

                  NEVERMIND! Somehow, the Firmware update reversed the direction of my X and Y motors o.O; SUPER STRANGE AND SLIGHTLY FRUSTRATING!

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

                    @vongreezly There was a bug fix between 1.18 and 1.21 which reversed the direction of a motor in the CoreXY kinematics.

                    Gotta read all the release notes for all the versions between your current version and the latest update to catch all the little tidbits.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    vonGreezlyundefined 1 Reply Last reply Reply Quote 0
                    • vonGreezlyundefined
                      vonGreezly @Phaedrux
                      last edited by

                      @phaedrux Fair enough! it was a big jump heh 1.18 was just so lovely, and my printer was busy... was just a little panicked at the sudden state of borkedness =P

                      1 Reply Last reply Reply Quote 0
                      • Zesty_Lykleundefined
                        Zesty_Lykle
                        last edited by

                        Absolutely flawless!
                        Did the whole upgrade, 3 files at once and it just did what it was supposed to do. Perfection!

                        Thanks David.

                        Lykle
                        Design, make and enjoy life

                        Co Creator of the Zesty Nimble

                        1 Reply Last reply Reply Quote 2
                        • Bogey55undefined
                          Bogey55
                          last edited by

                          @alclonky Did you ever resolve this? I think I have the same problem. Even after X and Y are homed when I try to home Z I get movement to the desired movement up 5, x and y move to center of bed, and then I get the error message... G28 Z
                          Error: G0/G1: insufficient axes homed

                          (Have looked at the FAQ's topic 1, etc...)

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

                            @dc42 Do you by chance know if @alclonky issue (G28 Z Error G0/G1: insufficient axes homed even if X and Y are homed / blue) was ever resolved? It sounds like I am having the same problem (on Firmware 2.01, have read FAQ#1, etc.) Thanks!

                            @dc42 said in It's out! Firmware 1.21 released:

                            Odd. In your homez.g you have the S2 parameter on the G1 Z5 command, which is the change you needed to make to homez.g. Please double check that the homez.g file in /sys on the SD card really does have that parameter, and what you posted isn't a copy on the PC that didn't make it to the printer.

                            The other possibility is that homing X or Y has failed. After you home X and Y, the X and Y homing buttons in DWC should be blue, and Z will still be orange because it hasn't been homed. Is that what you see?

                            Bogey55undefined 1 Reply Last reply Reply Quote 0
                            • Bogey55undefined
                              Bogey55 @Bogey55
                              last edited by

                              @bogey55 @dc42 @alclonky ...okay figured it out reading a recent thread on G30...removed the deploy probe and retract probe files...problem solved

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

                                @bogey55 said in It's out! Firmware 1.21 released:

                                @dc42 Do you by chance know if @alclonky issue (G28 Z Error G0/G1: insufficient axes homed even if X and Y are homed / blue) was ever resolved? It sounds like I am having the same problem (on Firmware 2.01, have read FAQ#1, etc.) Thanks!

                                See the release notes for firmware 2.0. But as it comes up quite often, I'll add an FAQ about 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
                                • First post
                                  Last post
                                Unless otherwise noted, all forum content is licensed under CC-BY-SA