Firmware wishlist and priorities for Duet WiFi and Duet Ethernet

yngndrw

In no particular order:

2. Better network security
6. Live monitoring of TMC2660 driver - Including live position updates as they move, rather than just at the end of the move
12. Better support for CNC machines - I've not tried the Duet with my CNC machine, but from what I've seen there's nothing to handle spindles. It would also be nice to have a little hardware module to convert the PWM output to a 0-10V output for the spindle speed
20. Ability to control an electronics cooling fan thermostatically

Dougal1957

David

1, 2, 6, 7, 12 is my vote?

Simspeed

5, 4, 9, 7, 13 My four new Z motors arrived so I'll soon be ready to implement #5.

deckingman

My personal preference would be 1, 13, 16, 17, 20.

3dprinting meathead

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

would that square up the x axis to the bed? like for an i3, probe z at left and right, and then move each z motor independently to make the x axis parallel to the points probed?

If this question is too off topic, just disregard.

roboduet

1. WiFi server, specially FTP support. I'm missing it after moving from Duet 0.6
3. Logging.
7. Dynamic microstepping to switch from x16 interpolated mode.
15. Support for 12864 displays.
16. Better temperature control
XX. Automatic firmware update from web interface (download firmware directly from internet, check md5 or sha hash and update if hashsum is ok). Plus check for updates button in DWC.

tomasf

1
19
20
16
7

3dprinting meathead

2
6
9
14
8
in no particular order

hairy_kiwi

3. Logging… of Temperature values also?
15. Support for PanelOne 20x4 text displays, or possibly 12864 mono graphics displays. Especially if useful/required for controlling a machine away from its usual WiFi network?
5. True bed levelling... The 2 z-motor solution would be sufficient for my current setup.
1. Reworked WiFi server code... Not sure I understand the limitations of the current code base well enough, but anyway.
17. Filament and printing time odometers.

Hugues

1
2
3
7
…And a filament monitor support based from rotary encoder

caphector

13, 1, 7, 2, 15

I'd love to see support for the Prometheus-style multi-filament hot ends as well. Both Prometheus and Prusa have made them. They retract filament when it's not in use and then advance the alternate filament. I think the only big change would be to filament movement distances.

demonio669

Allow M117 to send message via email
start and stop printing macros (o allow to send email when the print begins and ends)

tomwang256

18 - i accidently broke off my usb connector on the paneldue
5
6
7
9

windiesel

2
6
7
16
19

T3P3Tony

@caphector:

13, 1, 7, 2, 15

I'd love to see support for the Prometheus-style multi-filament hot ends as well. Both Prometheus and Prusa have made them. They retract filament when it's not in use and then advance the alternate filament. I think the only big change would be to filament movement distances.

These are already supported. The retraction length can be set either in the slicing software or the tool change gcode.

pjr3D

My vote(s):

1 - There is a need to be more tenacious about finding and then keeping a connection where there are many competing wifi routers. It is the most frustrating aspect at the moment especially in the evening when everyone in the area is going online!
7 - Dynamic stepping for my delta …
16 - Better temp control is always good.
18 - This is mostly a convenience but would be handy.
17 - Helps to keep track of usage for maintenance etc.

lars

My vote:
5
4
6
7
16

appjaws

I have been trying to implement a fail safe switch which will stop Z homing and move the bed down 5mm.
I am using your mini probe but want to test a piezo version I have constructed but I am worried that if it fails, nothing will stop the bed moving and damaging the hotend or bed surface.
I originally tried "M581 Z S1 T2 C0 ; Set Z stop as fail safe for Z zeroing and run /sys/trigger2.g"
and a /sys/trigger2.g file with the following entries G91, G1 Z5 F200

This works when moving the bed manually but has no effect when homing Z.

Deckingman suggested using the spare E0 connection "M581 E0 S1 T2 C0" this did not solve the issue and performed the same as the Z connection.

Does the firmware lock the system until homing has completed?
If so would it be possible to change that so the process can be interrupted in the way shown above or is their another way to protect the hotend and bed from probe failure?

lolorc

Hi,

my vote is : 1, 6, 7, 8, 14

jacksat

3
17
16
14
7