Firmware wishlist and priorities for Duet WiFi and Duet Ethernet
-
Cool down power off wait is already implemented, see https://duet3d.com/wiki/G-code#M81:_ATX_Power_Off.
-
Use StallGuard to tune motors for maximum speed and acceleration.
StallGuard won't tell you the maximum speed you can achieve, but you can work it out using the spreadsheet linked to from https://duet3d.com/wiki/Choosing_stepper_motors#How_to_work_out_the_power_supply_voltage_you_need.
I am not sure that StallGuard can tell you the maximum accelerations available either, because what it actually detects is increasing slip angle between the ideal motor position and actual motor position. This slip angle increases with motor load. So it can warn you when the load increases to a value that is close to the maximum value before stalling, but only if you calibrate that value first.
If enough users participated, I guess we could build up a database of recommended stallgard settings for various stepper motor models.
I was thinking of a serpentine pattern that gradually increased speed and or acceleration until Stallguard indicated that the motor was slipping and then back off a little. In the past when I needed to tune steppers for dot matrix printers is was very much cut and try. I envision a process somewhat akin to tuning a PID loop where the intent is to converge as fast as possible without overshoot.
Admittedly, everything is easy if you don't have to do it yourself.
-
5
6
18
17 -
The problem is, Stallguard doesn't really tell you that the motor is slipping. What it tells you is that the load is higher than the threshold you have configured.
-
Oh. Clearly, I need to read the data sheet.
Maybe an accelerometer is what I should be thinking about.
Prusa claims some high print and move speeds. I had assumed they used StallGuard for their tuning but maybe they just raised the threshold until it stopped working, perhaps with an accelerometer to tell them it was skipping, and then backed it off. Or maybe it's just not a useful number that they claim.
-
Prusa will have done tests to establish how high the stallguard reading can safely get before the motor starts skipping steps, so they know what stallguard threshold to set to detect skipped steps in normal operation. It's unlikely that they used stallguard to do that testing.
-
5 , 6, 7, 10 ,17
-
Two suggestions, one to improve Z probing accuracy, the other to improve mesh bed leveling (background is here: https://www.duet3d.com/forum/thread.php?pid=32725).
-
A new option for G30 single-point probe commands to probe multiple points and average them to generate the final height for (X,Y). Ideally you'd add NUMBER_OF_POINTS and RADIUS to the probe command, and G30 would then probe that number of points around the given (X,Y), as well as (X,Y) itself. (Since I'm wishing, let's consider an additional option to apply a median filter to this before averaging and/or throw out the lowest and highest measurements.) I think this would increase the accuracy and repeatability of Z probes regardless of what kind of probe you're using.
-
The ability to apply a median filter to heightmap.csv to eliminate outliers (incorrect probe heights). This could prevent one or more bad points from distorting the bed map.
Yes for this … doing the averaging manually and spreadsheets for the BL Touch ... repeat-ability ? mehhhh ....
-
-
Veng1 Prusa have it easy in this regard they're using one carefully chosen motor and optimising it. But print a tower and just bump acceleration up every 5mm, then another for jerk. You'll soon see how far you can go.
-
18, 7, 1
-
1, 2, 6, 17
Additionally, the integration of something like this into the web interface would be awesome, to give accurate print time estimates and statistical info about the print job: http://www.gcodeanalyser.com/
-
Additionally, the integration of something like this into the web interface would be awesome, to give accurate print time estimates and statistical info about the print job: http://www.gcodeanalyser.com/
Please request that in the DWC Wishlist section.
-
6. Live monitoring of TMC2660 driver status and reporting of problems (e.g. overheat warning).
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.
2. Better network security, including SSL if it can be made to work fast enough. Requires most of #1 in this list as a prerequisite.
-
#6 is already implemented.
#1 is mostly implemented. You can read the network status via M552 and the signal strength via M122. FTP and Telnet are supported.
-
Hi, My order depends on priority
6. Live monitoring of TMC2660 driver status and reporting of problems (e.g. overheat warning).
14. Support for powering off during a print, then resuming it when the printer is powered up again.
5. True bed levelling using 2, 3 or possibly 4 independently-driven Z motors and a Z probe.
11. Better support for laser cutters. AND/OR 12. Better support for CNC machines.
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. -
#6 already done
#14 already done
#5 already done
#11 some progress made: M3/M4/M5/M450/M451/M452/M453/G53-G59.3 implemented
#16 not started -
#6 already done
#14 already done
#5 already done
#11 some progress made: M3/M4/M5/M450/M451/M452/M453/G53-G59.3 implemented
#16 not startedMight be time to close this thread and start a new wishlist.
-
Might be time to close this thread and start a new wishlist.
Yes, it looks like it's time to do that. Remind me to start a new thread when the 1.21 release is done.
-
Hi,
There is already support to visualize the cpu temp on the "Temperature chart" under the "Extra" tab.
Maybe add the driver temperatures here too? Since the overheat protection is being done / is done, at least part of the coding is done for that. -
The driver's don't actually report their temperatures, just overheat warning and overheat error flags.
