Firmware wishlist and priorities for Duet WiFi and Duet Ethernet
-
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.
-
1,2,7,17,18
-
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.As David said, the driver chip itself does not supply the actual temperature, just alarms. However, there is a way to do it by sticking a bead thermistor to the top of the driver chip. Not only can you display the temperature but you can also use it to control a fan. I did a bit of write up on my blog explaining how to do it https://somei3deas.wordpress.com/2017/04/18/stepper-motor-and-electronics-cooling/. At the time, I had to create "dummy tools" but things have since moved on and I now use the "virtual heaters" feature which is in later firmware versions. This also allows meaningful names such as "X Driver chip" to be used.
HTH
-
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.As David said, the driver chip itself does not supply the actual temperature, just alarms. However, there is a way to do it by sticking a bead thermistor to the top of the driver chip. Not only can you display the temperature but you can also use it to control a fan. I did a bit of write up on my blog explaining how to do it https://somei3deas.wordpress.com/2017/04/18/stepper-motor-and-electronics-cooling/. At the time, I had to create "dummy tools" but things have since moved on and I now use the "virtual heaters" feature which is in later firmware versions. This also allows meaningful names such as "X Driver chip" to be used.
HTH
Thanks, it is not that crucial, I just tought that the driver ics reported the temp and the overheat warning was a software feature.
If this was the case, and we both had the ic temps and the infrastructure to report the cpu temp as well, it would have been a fun feature and one that was easily implemented. -
A nice feature for aligning hotends on IDEX printers would be a G31 hole probe routine. Where you could G31 probe X and Y in positive & negative directions (with multi touch) and then position in the center. Not sure how close the DuetWifi is to running out of resources for adding features but this would be a nice one.
One could then use a ring type gauge mounted on a piezo disk to pick up the touches. It can be done manually right now but an automatic routine would make life easier.
Any thoughts on that David?
-
A nice feature for aligning hotends on IDEX printers would be a G31 hole probe routine. Where you could G31 probe X and Y in positive & negative directions (with multi touch) and then position in the center. Not sure how close the DuetWifi is to running out of resources for adding features but this would be a nice one.
One could then use a ring type gauge mounted on a piezo disk to pick up the touches. It can be done manually right now but an automatic routine would make life easier.
Any thoughts on that David?
I'm sorry, I don't understand what you mean by a "hole probe routine".
