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

    Firmware 2.03beta2 available

    Scheduled Pinned Locked Moved
    Firmware installation
    25
    86
    12.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

      The endstop states are passed to DWC after remapping, so DWC should read correctly.

      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

      deckingmanundefined 1 Reply Last reply Reply Quote 0
      • Edgars Batnaundefined
        Edgars Batna
        last edited by

        Just did a quick print on my CoreXY. No obvious issues.

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

          CoreXY - everything seems to working fine.

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

            @dc42 Sorry to be a pain but for the purpose of re-mapping end stops, can I just ask if the following input assignments vs labels is correct?

            On the Duet Ethernet......

            Label "X" is input 0
            Label "Y" is input 1
            Label "Z" is input 2
            Label "E0" is input 3
            Label "E1" is input 4

            On the Duex 5.........

            Labels E2 to E6 are respectively inputs 5 to 9.

            Is that correct?

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

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

              @deckingman said in Firmware 2.03beta2 available:

              @dc42 Sorry to be a pain but for the purpose of re-mapping end stops, can I just ask if the following input assignments vs labels is correct?

              On the Duet Ethernet......

              Label "X" is input 0
              Label "Y" is input 1
              Label "Z" is input 2
              Label "E0" is input 3
              Label "E1" is input 4

              On the Duex 5.........

              Labels E2 to E6 are respectively inputs 5 to 9.

              Is that correct?

              Correct. Also inputs 10 and 11 are the two on the CONN_LCD connector. It's the same numbering as in the M591 command.

              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

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

                @dc42 Thanks. - I don't have any filament sensors so I've never looked at M591.

                May I suggest that this input numbering vs label be included in the Wiki somewhere. Either in the section entitled "connecting end stop switches" or in the section dealing with M574. I don't think I trust myself to edit the Wiki personally but I'll have a go if you like.

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

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

                  Next time we revise the Duet we will number the endstop inputs and motor outputs, instead of giving them axis and extruder labels.

                  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

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

                    @dc42 said in Firmware 2.03beta2 available:

                    Next time we revise the Duet we will number the endstop inputs and motor outputs, instead of giving them axis and extruder labels.

                    Yes I believe you've said that before - makes perfect sense. Hindsight is always 20:20 ☺

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

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

                      Just want to report that this (firmware 2.03 beta2) is all working well for me. CoreXYUV is all doing what it should do. Also I have been able to get homing working on my 3rd gantry by temporarily assigning both drives and end stops to X and Y axes.

                      The homing file is a bit complicated because basically I'm homing 7 axes - initially a course home, followed by a finer home at slower speed for each axis. Then re-mapping all drives and end stops so that for printing, it becomes a 3 axis machine.

                      Anyway, big thanks to David.

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

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

                        @deckingman said in Firmware 2.03beta2 available:

                        May I suggest that this input numbering vs label be included in the Wiki somewhere. Either in the section entitled "connecting end stop switches" or in the section dealing with M574. I don't think I trust myself to edit the Wiki personally but I'll have a go if you like.

                        I have put it in with M574.

                        deckingmanundefined wilrikerundefined 2 Replies Last reply Reply Quote 2
                        • deckingmanundefined
                          deckingman @AndreS
                          last edited by

                          @andres said in Firmware 2.03beta2 available:

                          @deckingman said in Firmware 2.03beta2 available:

                          May I suggest that this input numbering vs label be included in the Wiki somewhere. Either in the section entitled "connecting end stop switches" or in the section dealing with M574. I don't think I trust myself to edit the Wiki personally but I'll have a go if you like.

                          I have put it in with M574.

                          Thanks - I'm sure others will appreciate that information.

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

                          1 Reply Last reply Reply Quote 0
                          • wilrikerundefined
                            wilriker @AndreS
                            last edited by wilriker

                            @andres said in Firmware 2.03beta2 available:

                            I have put it in with M574.

                            And for the sake of completeness I also added a table to Connecting endstop switches in the wiki.

                            Manuel
                            Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
                            with probably always latest firmware/DWC (incl. betas or self-compiled)
                            My Tool Collection

                            deckingmanundefined 1 Reply Last reply Reply Quote 3
                            • deckingmanundefined
                              deckingman @wilriker
                              last edited by

                              @wilriker Very nice ☺

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

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

                                I've put an update to firmware 2.03beta2 for the Duet WiFi/Ethernet and Maestro at https://www.dropbox.com/sh/mk3jlsoi6gyxd8q/AABbEvX2qb19McbRe6UvRmI9a?dl=0. Changes in this version:

                                • New M505 command to support multiple configurations more easily (see separate thread)
                                • Bug fix for file selection on 12864 displays on the Maestro
                                • Bug fix for CNC and laser machines (was complaining about attempts to move outside the allowed limits during homing)
                                • Increase max numbers of extruders and heaters per tool to 8 on the Duet WiFi/Ethernet
                                • Babystepping command (M290) now works on any axis, however at present only Z babystepping can jump moves in the movement queue

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

                                  there have been changes for the M291 triggers / messages in tool change macros?

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

                                    @nicolab28 said in Firmware 2.03beta2 available:

                                    there have been changes for the M291 triggers / messages in tool change macros?

                                    M291 sets baby stepping, it has nothing to do with triggers.

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

                                      M290 is for baby stepping.
                                      I'm talking about blocking tool change macro with a message using trigger and M582.
                                      When we put M291 command in trigger#.g

                                      https://forum.duet3d.com/topic/8381/m291-s2-does-not-block-macro-execution

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

                                        My mistake, M291 is for displaying messages and optionally waiting for a response.

                                        What are you trying to use M291 in a trigger to do?

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

                                          Interrupt the tool change macro, to make a manual intervention, and resume.

                                          In tfree.g tpre.g or tpost.g, if we make an M582, then an M291 in trigger # .g the message arrives after the end of the tool change.

                                          As a result, the problem could not be resolved

                                          1 Reply Last reply Reply Quote 0
                                          • pawPrinterundefined
                                            pawPrinter
                                            last edited by

                                            CoreXY working well here, along with leadscrew bed levelling and sensorless homing

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