Firmware wishlist and priorities for Duet WiFi and Duet Ethernet

[dc42]

@nebulus7:

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.

[DarrenAnton]

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.

[dc42]

#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.

[cgcafer]

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.

[dc42]

#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

[JohnOCFII]

@dc42:

#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

Might be time to close this thread and start a new wishlist.

[dc42]

@JohnOCFII:

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.

[denke]

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.

[dc42]

The driver's don't actually report their temperatures, just overheat warning and overheat error flags.

[mfoltz]

1,2,7,17,18

[deckingman]

@denke:

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

[denke]

@deckingman:

@denke:

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.

[timcurtis67]

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?

[dc42]

@timcurtis67:

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".

[timcurtis67]

I mean having a steel cylinder with a precision hole bored through it mounted on a Piezo disk. The hole is larger than the hotend nozzle.

The way the routine would work is you would jog the nozzle roughly over the center of the hole. Then drop enough of the nozzle tip in below the top of the cylinder. Enough so the cone shape would make contact with the inside edge of the cylinder if it were moved in any direction in X or Y.

Then call up a G31 S-3 (or whatever parameter you choose). The printer would then move in X+ till it reads a contact (just like a Z probe move). When stopped record position, Then move back to start point. Probe in X- until another contact is read. record position position, subtract first stop point from second stop point (X+ pos. - X- pos.) then move to the resulting position. Basically moving the the center of the 2 stops in X.

Then do the same probes in Y+ & Y-. Do the calculation for y and move to that new center point.

Repeat X probes to ensure the true center of X again.

Now if you run the same routine on the second hotend then the difference in positions between the two hotends is what would get entered in G10 X Y for the second tool.

Does that make sense?

[BPisLife]

18
5
6

[MitchD]

Would it be possible to make the Paneldue play a tune when the print finishes? This just makes the whole experience a bit more friendly, especially when we show off the printers at maker faires etc.

[Quadcells]

19
17
1
2
18

Thanks

[dc42]

@mitchd said in Firmware wishlist and priorities for Duet WiFi and Duet Ethernet:

Would it be possible to make the Paneldue play a tune when the print finishes? This just makes the whole experience a bit more friendly, especially when we show off the printers at maker faires etc.

I think it should already be possible, using a combination of M300 and G4.

[audryhome]

@dc42 Implement G29 T1 tag to list the height table, this makes it possible to communicate with Bed Level Visualizer
see https://plugins.octoprint.org/plugins/bedlevelvisualizer/ for info.

All Octoprint users will love this I guess.

Low priority since this exists in the DUET GUI as a workaround.