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

    It's out! Firmware 1.21 released

    Scheduled Pinned Locked Moved
    Firmware installation
    25
    73
    13.2k
    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
      last edited by

      Is there a G31 command in config-override.g that is overriding the one in config.g? Prior to version 1.20, M500 used to save the G31 settings; now it does so only if you provide an extra parameter.

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

        @dc42:

        1. The Duet 06 and Duet 085 are older boards that pre-date the Duet WiFi and Duet Ethernet. The PCB revision is printed on the board. For those boards it is 0.6 or 0.8.5. For Duet WiFi or Ethernet it is 1.0, 1.01, 1.02 or 1.03.

        2. Please explain what you mean by "pressure range".

        3. Yes, stop.g.

        1. I have version "Duet2 V1.03" that means I would not need these files at all?

        2. Sorry, meant "print area" which was defined with M208.

        3. "Stop.g" not with me executed automatically at the end of the print, like "start.g" at the beginning of the print.

        Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

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

          1. So you need the files listed for the Duet WiFi or Duet Ethernet (whichever board you have).

          2. Yes, movement limits are applied during simulation. So G0/G1 moves that would go to outside the bed are modified to remain inside the bed, and G2/G3 moves that would go outside the bed cause the simulation to be aborted.

          3. stop.g is only executed if your end gcode finishes with command M0.

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

            no g31 in the config-override.g I added the config-override.g I also checked to make sure there was not a second g31 somehow

            ; This is a system-generated file - do not edit
            ; Heater model parameters
            M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
            M307 H1 A272.0 C158.9 D3.3 S1.00 V23.7 B0
            M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
            M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0

            1 Reply Last reply Reply Quote 0
            • zerspaner_gerdundefined
              zerspaner_gerd
              last edited by

              @dc42:

              1. So you need the files listed for the Duet WiFi or Duet Ethernet (whichever board you have).

              2. Yes, movement limits are applied during simulation. So G0/G1 moves that would go to outside the bed are modified to remain inside the bed, and G2/G3 moves that would go outside the bed cause the simulation to be aborted.

              1. Have DuetWifi.
                So I only need these files:
                [c]DuetWiFiFirmware.bin or Duet2CombinedFirmware.bin (which are the same file), DuetWiFiServer.bin and iap4e.bin[/c]
                I do not need these:
                [c]RepRapFirmware.bin and iap.bin[/c]

              2. There is no message if G0/G1 is outside the print area?

                So it does not come to a collision but my part is dan for the trash can, Mhh????

              Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

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

                1. Correct.

                2. In FDM printer mode, that is correct. The reason is that it is quite common for a skirt to exceed the bounds of the bed. In laser and CNC mode the print will be terminated. If you want this changes, please suggest what you would like instead in the Firmware Wishlist section.

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

                  I figured out my issue with the IR probe well got it working anyways must have been a bad update I guess formatted my sd card and added all my files back, and now it is working correctly.

                  1 Reply Last reply Reply Quote 0
                  • alclonkyundefined
                    alclonky
                    last edited by

                    Hi,
                    i tried to adjust my homing files for my Cartesian Printer
                    Homing X and Y works again, but home z just moves the 5 up and then stops with

                    G28 Z
                    Error: G0/G1: insufficient axes homed

                    myhomez.g:
                    G91
                    G1 Z5 F6000 S2
                    ; Back to absolute positioning
                    G90
                    ; Go to first bed probe point and home the Z axis
                    G1 X0 Y0 F6000
                    G30

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

                      Read the upgrade notes for firmware 1.21.

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

                        I did, otherwise i couldn't home X and Y

                        or did I miss something else?

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

                          Looking at the above, I'd have thought that your home Z will work but only if you have homed X and Y first. If you haven't, then this line G1 X0 Y0 F6000 will cause the problem. So to be safe, add S2 to it then it won't matter if X and Y have been homed.

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

                          1 Reply Last reply Reply Quote 0
                          • alclonkyundefined
                            alclonky
                            last edited by

                            i tried adding S2 to this line and without that line, but in both cases Z wont home

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

                              Please confirm: are you saying that even if you have homed X and Y first, you get that message if you try to home Z?

                              If you try to home Z without homing X and Y first, then that message is expected, because the firmware doesn't know where X0 Y0 is.

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

                                Yes, thats what i am saying

                                i can home X and Y first and when i home z it failes
                                if i home all it homes X and Y and failes with z

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

                                  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?

                                  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

                                  Bogey55undefined 1 Reply Last reply Reply Quote 0
                                  • alclonkyundefined
                                    alclonky
                                    last edited by

                                    yes after homing X and Y the buttons get blue

                                    i copied the files from the /sys folder on the SD

                                    ; homeall.g
                                    ; called to home all axes
                                    ; Relative positioning
                                    G91
                                    ; Lift Z
                                    G1 Z5 F6000 S2
                                    ; Course home X and Y
                                    G1 X-200 Y-210 F1800 S1
                                    ; Move away from the endstops
                                    G1 X5 Y5 F6000
                                    ; Fine home X and Y
                                    G1 X-200 Y-210 F360 S1
                                    ; Absolute positioning
                                    G90
                                    ; Go to first bed probe point and home Z
                                    G1 X0 Y0 F6000 S2
                                    G30

                                    ; homey.g
                                    ; called to home the Y axis
                                    ;
                                    ; Lift Z relative to current position
                                    G91
                                    G1 Z5 F6000 S2
                                    G90
                                    ; Move quickly to Y axis endstop and stop there (first pass)
                                    G1 Y-210 F1800 S1
                                    ; Go back a few mm
                                    G91
                                    G1 Y5 F6000
                                    G90
                                    ; Move slowly to X axis endstop once more (second pass)
                                    G1 Y-210 F360 S1
                                    ; Lower Z again
                                    G91
                                    G1 Z-5 F6000 S2
                                    G90

                                    ; homex.g
                                    ; called to home the X axis
                                    ; Lift Z relative to current position
                                    G91
                                    G1 Z5 F6000 S2
                                    G90
                                    ; Move quickly to X axis endstop and stop there (first pass)
                                    G1 X-200 F1800 S1
                                    ; Go back a few mm
                                    G91
                                    G1 X5 F6000
                                    G90
                                    ; Move slowly to X axis endstop once more (second pass)
                                    G1 X-200 F360 S1
                                    ; Lower Z again
                                    G91
                                    G1 Z-5 F6000 S2
                                    G90

                                    ; homez.g
                                    ; called to home the Z axis
                                    ; Lift Z relatively to current position
                                    G91
                                    G1 Z5 F6000 S2
                                    ; Back to absolute positioning
                                    G90
                                    ; Go to first bed probe point and home the Z axis
                                    ;G1 X0 Y0 F6000 S2
                                    G30

                                    1 Reply Last reply Reply Quote 0
                                    • jnolan72undefined
                                      jnolan72
                                      last edited by

                                      Something new in error in 1.21 that I did not see in 1.20
                                      Browser or web problem. Error after uploading a file

                                      JavaScript Error

                                      A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:

                                      Version: 1.21
                                      Message: Uncaught TypeError: Cannot read property 'axesHomed' of undefined
                                      URL: http://10.0.2.147/js/dwc.js
                                      Line: 776:70
                                      Error object: {}

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

                                        @jnolan72:

                                        Something new in error in 1.21 that I did not see in 1.20
                                        Browser or web problem. Error after uploading a file

                                        JavaScript Error

                                        A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:

                                        Version: 1.21
                                        Message: Uncaught TypeError: Cannot read property 'axesHomed' of undefined
                                        URL: http://10.0.2.147/js/dwc.js
                                        Line: 776:70
                                        Error object: {}

                                        Is it reproducible, or did it happen just once? Can you confirm that you are running version 1.21 of both the main firmware and DWC?

                                        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

                                        jnolan72undefined 1 Reply Last reply Reply Quote 0
                                        • DocTruckerundefined
                                          DocTrucker
                                          last edited by

                                          Subtle change noticed…

                                          My procedure:

                                          • Home axis
                                          • Warm up bed / enclosure
                                          • Run bed probe
                                          • Warm up nozzle
                                          • Check nozzle height with my calibrated feeler gauge (scrap of paper đŸ˜‰ )
                                          • Use G10 to set tool offset - i.e. if feeler'ed ideal z=0 plane is at Z=-0.15mm I'll send 'G10 P0 Z0.15'

                                          The G10 used to update the reported z position instantly. Now running the G10 command would virtually shift the axis but the value reported on 1.21 web control only updates after a G1 move of the z-axis - which may be a no-distance move.

                                          Running 3 P3Steel with Duet 2. Duet 3 on the shelf looking for a suitable machine. One first generation Duet in a Logo/Turtle style robot!

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

                                            @DocTrucker:

                                            Subtle change noticed…

                                            My procedure:

                                            • Home axis
                                            • Warm up bed / enclosure
                                            • Run bed probe
                                            • Warm up nozzle
                                            • Check nozzle height with my calibrated feeler gauge (scrap of paper đŸ˜‰ )
                                            • Use G10 to set tool offset - i.e. if feeler'ed ideal z=0 plane is at Z=-0.15mm I'll send 'G10 P0 Z0.15'

                                            The G10 used to update the reported z position instantly. Now running the G10 command would virtually shift the axis but the value reported on 1.21 web control only updates after a G1 move of the z-axis - which may be a no-distance move.

                                            On my list to look at.

                                            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