Firmware wishlist and priorities for Duet WiFi and Duet Ethernet

T3P3Tony

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

Ntesla66

Hello, Love what you've done already! Just amazing.
Cast vote as : 1, 3, 6, 8, 16.
Best Regards.

Merlin

Vote of a 'simple' user
14,
13,
16,
17

jmjcoke2

7
10
11
14
6
16
12

Loffy770

1,4,6,8,18
4..being able to utilize 5v switches on Duex for XYZ

Reanimator2k

5
4
7
17
19

Miasmictruth

Just 11 for me, I definitely want to use the duet board for my laser cutter.

Now that I am used to 18 inst as big of a deal but would be nice I suppose.

Crash69

My order of preference

18, 3, 17, 1, 20, 6, 8, 14

I know I'm going against the grain but I think 2 is possibly asking too much for the duet, I just don't see most needing that level of security on their local network and if they do there is always the option of putting it behind a firewall. I'd rather have that processing power put into extra features myself

Alexander Mundy

14,17,18

T-Printer

My vote:
7
8
16
17
18

JohnOCFII

My ordered priorities:

1, 7, 6, 3, 20

Thanks,

John

Fickert

My votes:
1 for the fact I would love more solid wifi connection anything can help.
6 Would be nice to see as I am curious if my cooling fan is overkill or not. Or the effects of truly printing fast or slow
7 I think this is huge. I feel a lot of us are undercompensating these amazing stepper drivers with their ability to actually use X256 microstepping… Would it switch down to interpolated steps or just standard steps?
11 and 12 These are fairly important to me as this is what I will be doing for my project
16 Temperature control is always the battle so I am definitely in to see if this can be implimented
18 Also very nice to see.

Adamfilip

18
7
10
1
12

Thanks for your hard work and dedication!

Adam

yngndrw

I have another firmware feature to add to the list: Stepper motor linearity compensation.

There's no point in me explaining when Mariss Freimanis from GeckoDrive has explained it far better than I ever could:
https://en.industryarena.com/forum/showthread.php?t=129408&p=1057850&viewfull=1#post1057850

Now each make / model of motor will probably use the same compensation factor, so users would need to work out the correct factor for each type of motor that they are using.

This can either be done with a laser / mirror as Mariss mentioned, or an inexpensive encoder could be used with a 3D printed adapter. I've used these encoders with a 3.3V in the past and they work fine, even though they are only rated down to 5V, there's also some higher line count encoders available:
http://www.ebay.co.uk/itm/131515172625

With the encoder, calibration could be fully automatic.

T3P3Tony

Andrew, reading the Gecko drive post it looks like he is talking about compensating for this in the stepper driver chip using an FPGA to alter the Electrical waveform to compensate for the mechanical error in microstepping position. That means the compensation will be in fractions of microsteps. Within firmware we only have the ability to work in microsteps, and this sort of error is not cumulative so I think this is a stepper driver chip level functionality request.