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

    Firmware wishlist and priorities for Duet WiFi and Duet Ethernet

    Scheduled Pinned Locked Moved
    Firmware wishlist
    113
    236
    50.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.
    • dc42undefined
      dc42 administrators
      last edited by

      Controlling a cooling fan based on CPU temperature and/or driver over-temperature warnings is implemented in firmware 1.19beta2.

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

        Wow DC. That is impressive. Is there a change log or gcode update for that feature?

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

          See https://duet3d.com/wiki/G-code#M106:_Fan_On.

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

            Some new M-codes to whet your appetite:

            https://duet3d.com/wiki/G-code#M671:_Define_Z_leadscrew_positions

            https://duet3d.com/wiki/G-code#M911:_Enable_auto_save_and_set_threshold_voltages

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

              @dc42:

              Controlling a cooling fan based on CPU temperature and/or driver over-temperature warnings is implemented in firmware 1.19beta2.

              What are considered safe max temps for the CPU and motor drivers?

              Prusa i3 Style Printer with Duet WiFi, E3D Volcano, Bondtech BMG

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

                For the CPU, 85C should be considered the maximum. The reported driver temperature will go direct from 0C to 100C when an over-temperature warning is raised. So I suggest having the electronics cooling fan turn on when either the CPU or the drivers report about 55C or more.

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

                  21. Mechanical Z endstop support that stops z movement no matter what!
                  1.

                  1 Reply Last reply Reply Quote 0
                  • Will Baxterundefined
                    Will Baxter
                    last edited by

                    my preference would be 5 5 5 5 5 for 4 z motors and quickly pleace

                    1 Reply Last reply Reply Quote 0
                    • Dougal1957undefined
                      Dougal1957
                      last edited by

                      think you'll find this has already been implemented in 1.19

                      1 Reply Last reply Reply Quote 0
                      • inachisiojexusundefined
                        inachisiojexus
                        last edited by

                        Any hope of getting telnet server anytime soon? 🙂

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

                          Already implemented in 1.19. See https://duet3d.com/wiki/G-code#M586:_Configure_network_protocols for how to enable 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
                          • inachisiojexusundefined
                            inachisiojexus
                            last edited by

                            @dc42:

                            Already implemented in 1.19. See https://duet3d.com/wiki/G-code#M586:_Configure_network_protocols for how to enable it.

                            Apologies… and thanks!

                            P.s. Maybe the list in the first post should be updated to reflect features already implemented (telnet support is in the first bullet)?

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

                              After the TCT show I will review which requested features have/have not been implemented and start a new thread to prioritize the remaining items.

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

                                It would be nice to be able to register several wifi AP, and have the Duet connect on the first available.

                                Usefull when moving the printer in different places (home, friends, hackerspace…)

                                Frédéric

                                1 Reply Last reply Reply Quote 0
                                • Dougal1957undefined
                                  Dougal1957
                                  last edited by

                                  @fma:

                                  It would be nice to be able to register several wifi AP, and have the Duet connect on the first available.

                                  Usefull when moving the printer in different places (home, friends, hackerspace…)

                                  You can already do this in 1.19 Firmware you just add the AP as normal and then I believe the Duet then connects to the strongest one it finds in it's list

                                  See the last line under The upgrade section at the bottom of https://duet3d.com/wiki/Upgrading_to_DuetWiFiFirmware_1.19

                                  1 Reply Last reply Reply Quote 0
                                  • fmaundefined
                                    fma
                                    last edited by

                                    Great! I'm running a beta version of 1.19 (with the MTU fix), so I will give it a try.

                                    Thanks!

                                    Frédéric

                                    1 Reply Last reply Reply Quote 0
                                    • Dougal1957undefined
                                      Dougal1957
                                      last edited by

                                      It works for me I have both my Router and wifi AP listed so wherever the printer is in the house it works

                                      1 Reply Last reply Reply Quote 0
                                      • sverrebundefined
                                        sverreb
                                        last edited by

                                        Printers may experience a slight tilt of their carriage for their movement. Tilts that are small enough that they do not matter for actual printing may still cause problems during bed probing as the probe is often significantly offset from the pivot center (where the hot-end tend to be) This causes errors when probing the bed in which probes done when travel approaches from one side along the sensive axis vs. the other creating a bed height map with ripples that do not correspond to an actual imperfection in the bed.

                                        To minimize this the carriage should ideally approach each probe point from the same direction on both axis during probing.

                                        As a simpler but mostly good enough solution it is suggested to allow the user to select if the g29 command traverses X first or Y. While not a perfect solution it does solve any situation there tilting occurs on only one axis

                                        1 Reply Last reply Reply Quote 0
                                        • jmjcoke2undefined
                                          jmjcoke2
                                          last edited by

                                          10
                                          11
                                          12

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

                                            Time to review the wish list. Here is the original one, in order of decreasing votes, and a note of which ones have been implemented:

                                            (24 votes) 7. Dynamically-varying microstepping. This will allow you to configure 256x microstepping most cases, because the microstepping will be reduced automatically during high-speed moves.

                                            (19 votes) 1. Reworked WiFi server code, including configuration using files on the SD card, automatic retry if the connection is lost, live reporting of signal strength and status, more reliable support of multiple concurrent connections, and optional FTP and Telnet support. Done, although multiple concurrent clients can be problematic when one of them goes offline without disconnecting first.

                                            (17 votes) 6. Live monitoring of TMC2660 driver status and reporting of problems (e.g. overheat warning). Done.

                                            (17 votes) 16. Feed-forward temperature control to predict the effect of turning the print cooling fan on or increasing the extrusion rate, and therefore reduce the temperature fluctuation.

                                            (14 votes) 14. Support for powering off during a print, then resuming it when the printer is powered up again. Done, and being improved in 1.20.

                                            (13 votes) 3. Logging of various events, including print start/pause/resume/cancel/end, and error messages. Done in 1.20

                                            (13 votes) 17. Filament and printing time odometers.

                                            (13 votes) 18. Ability to update PanelDue firmware via the web interface. PanelDue version 3 has the hardware to support this but the firmware support needs to be written.

                                            (12 votes) 5. True bed levelling using 2, 3 or possibly 4 independently-driven Z motors and a Z probe. Done.

                                            (10 votes) 15. Support for PanelOne 20x4 text displays, or possibly 12864 mono graphics displays.

                                            (9 votes) 12. Better support for CNC machines. Partly done (M3/M4/M4 commands implemented in 1.20).

                                            (9 votes) 20. Ability to control an electronics cooling fan thermostatically based on CPU temperature and driver overheat warning. Done.

                                            (8 votes) 8. Standstill current reduction, which will allow higher motor currents to be used when the motors are moving.

                                            (8 votes) 19. Ability to wait for cool down before turning off ATX power.

                                            (7 votes) 11. Better support for laser cutters. Partly done (M3/M4/M4 commands implemented in 1.20).

                                            (6 votes) 13. Automatic advance of changes in the colour mix when using a mixing hot end. See deckingman's blog.

                                            (5 votes) 2. Better network security, including SSL if it can be made to work fast enough.

                                            (4 votes) 4. Independent homing switches for multiple Z motors. Largely superseded by #5, but can be done by defining additional axes.

                                            (4 votes) 9. Auto-park of motors when power is lost. This will help prevent motors getting out of sync when multiple motors are used to drive a single axis.

                                            (4 votes) 10. Axis hysteresis compensation.

                                            In addition, some new features have been requested:

                                            (requested and seconded) Filament monitor In beta

                                            (requested and seconded) Heater fault to pause print instead of aborting it Coming in 1.20beta2

                                            Automatic firmware update I would be reluctant to do this, because firmware updates sometimes require changes to the configuration files

                                            Email notifications of e.g. print complete

                                            Print start/stop macros There is already stop.g which is called when M0 is executed at the end of your print, and you can use the slicer start/end gcode to call your own macros

                                            Automatic XY skew compensation (using Mk42 bed)

                                            Use Stallguard for bed probing See recent thread on this subject

                                            Probe the bed multiple times at each point and take an average

                                            Allow file uploads to be requested during a print, defer them until the print has completed

                                            When bed probing, allow the probe point to be approached from the same direction each time, to mitigate the effect of combined tilt and backlash when positioning the head

                                            As many of the items have been completed now, I'll stat a new wishlist soon. Top of that list will be the highest-voted items that haven't yet been implemented. But before I create a new thread for the new wishlist, are there any other items that should be on it - for example, using StallGuard to detect printing problems?

                                            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

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