Firmware wishlist and priorities for Duet WiFi and Duet Ethernet
-
Can you read the driver temps over SPI? If so it would be awesome if one of the PWM fan channels could be temperature controlled.
Apparently not but I believe there is a temperature warning alarm and an over temperature alarm which DC has it on his todo list to look at monitoring and maybe switching a fan or (in the case of over temperature) taking some more extreme action.
You can however, do as I do and stick a thermistor on the chip (or anywhere else) with a small dab of epoxy adhesive then use one of the PWM channels to control a fan. I did a bit of a write up on my blog which you can view here if you are interested https://somei3deas.wordpress.com/2017/04/18/stepper-motor-and-electronics-cooling/
-
I did that on my last control board. For now I have the control box fan connected to fan 3. My start and end scripts turn it on about 30%. It works fine. It would be nice to have them bumped up if nesessary though.
Great write up!
-
Controlling a cooling fan based on CPU temperature and/or driver over-temperature warnings is implemented in firmware 1.19beta2.
-
Wow DC. That is impressive. Is there a change log or gcode update for that feature?
-
-
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
-
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?
-
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.
-
21. Mechanical Z endstop support that stops z movement no matter what!
1. -
my preference would be 5 5 5 5 5 for 4 z motors and quickly pleace
-
think you'll find this has already been implemented in 1.19
-
Any hope of getting telnet server anytime soon?
-
Already implemented in 1.19. See https://duet3d.com/wiki/G-code#M586:_Configure_network_protocols for how to enable it.
-
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)?
-
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.
-
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…)
-
@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
-
Great! I'm running a beta version of 1.19 (with the MTU fix), so I will give it a try.
Thanks!
-
It works for me I have both my Router and wifi AP listed so wherever the printer is in the house it works
-
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
