Is there any chance at all a new way of sorting could be added to the Panel Due Print file section?

Currently, they are being sorted alphabetically.
I would love to see an option to change it so that the order is by file creation date, so you can just quickly see which was the latest uploaded file and hit print

Could this be added? Pretty please?

While waiting, you can easily use this:
https://github.com/iz3man/duet3d/blob/main/duet3d.yaml

Just add the lines to your configuration.yaml, modify for your printer and restart HA.

I'm kinda looking forward to Pathio being the next big thing (way too feature starved at this point, but love the concept), or maybe, if S3D 5.0 is amazing - stick with that. I can't stand Cura
I chose Slic3r PE for my prints right now to get the strongest possible parts for a new HEVO, while not rattling the printer to bits with honeycomb. Gyroid is way easier on the printer.

So here's my hoping this is not premature (doubt it! ), but I just wanted to say thank you to both creators of the Duet Wifi and PanelDue and this amazing community.

So far, I'm absolutely amazed with the product and I am totally loving what it did to my Ender 3 (along with the help I got here when I was getting my config messed up).

I still have a long way to go ahead of me (dual z screws, figure out the blower fan noise that wasn't there on Ender and building a Hypercube Evolution with this setup), but I am still very happy.

Thank you and keep rocking like you already do

You also have farnell in the UK and Elfa Distrelec or TME within the EU. In the past, I would buy Wurth connectors from Farnell, but with Brexit and me being mainland EU - no longer makes sense ;/

Quick update.

I'm 5 hours into the print, so far the print has not failed, no skipped steps or underextrusion, etc. The 3HC starts flashing quickly immediately, catches sync within 2-3 seconds.

There is one more test I need to do - if all goes well, I'll have it done tomorrow morning - that's to check how the 3HC behaves after a long power off (at least one hour). For now I've had the printer running pretty much 24/7 since Saturday.

I ran a quick M122 just in case you want to see what's going on right now (pasting below). The assertion failure is still there and DHT22 does not work.

Diagnostics for board 2:
Duet EXP3HC firmware version 3.3beta (2021-02-01 22:29:11)
Bootloader ID: not available
Never used RAM 154972, free system stack 0 words
Move 80 HEAT 78 CanAsync 72 CanRecv 82 CanClock 74 TMC 30 MAIN 263 AIN 260
Last reset 12:15:33 ago, cause: software
Last software reset time unknown, reason: AssertionFailed, available RAM 173348, slot 0
Software reset code 0x0120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0445f85f BFAR 0xe000ed38 SP 0x2002ff8c Task MAIN Freestk 4294967295 ok
Stack: 000002f2 0002a9b0 00020f41 00000000 0002256d 20002ec8 20003100 00000031 00000001 20002980 03800209 0001a72d 0001a709 00000000 00000000 ffffffff 0001de4b 200022d8 20002330 00029c48 ffffffed 00000000 00f00000 e000ef34 c0000000 200041dc 00020ea5
Driver 0: position 19481636, 410.0 steps/mm,  ok, reads 39334, writes 0 timeouts 0, SG min/max 0/83, steps req 354599 done 354486
Driver 1: position 0, 80.0 steps/mm,  standstill, reads 39334, writes 0 timeouts 0, SG min/max not available, steps req 0 done 0
Driver 2: position 0, 80.0 steps/mm,  standstill, reads 39334, writes 0 timeouts 0, SG min/max not available, steps req 0 done 0
Moves scheduled 966506, completed 966505, in progress 1, hiccups 0, step errors 0, maxPrep 59, maxOverdue 3, maxInc 3, mcErrs 0, gcmErrs 0
Peak sync jitter 10, peak Rx sync delay 177, resyncs 0, next step interrupt due in 1138 ticks, enabled
VIN: 24.1V, V12: 12.1V
MCU temperature: min 45.7C, current 45.9C, max 46.1C
Ticks since heat task active 16, ADC conversions started 44133758, completed 44133757, timed out 0
Last sensors broadcast 0x00000000 found 0 22 ticks ago, loop time 0
CAN messages queued 1648, send timeouts 0, received 11585, lost 0, free buffers 36, min 36, error reg 0
dup 0, oos 0, bm 0, wbm 0

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3beta running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
Board ID: 08DJM-956L2-G43S4-6JKDA-3SJ6T-1B6GH
Used output buffers: 1 of 40 (40 max)
=== RTOS ===
Static ram: 149800
Dynamic ram: 92100 of which 72 recycled
Never used RAM 108700, free system stack 118 words
Tasks: NETWORK(ready,228) ETHERNET(blocked,117) SENSORS(blocked,15) HEAT(blocked,280) CanReceiv(blocked,877) CanSender(blocked,337) CanClock(blocked,326) TMC(blocked,16) MAIN(running,616) IDLE(ready,20)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 12:15:29 ago, cause: software
Last software reset at 2021-02-02 09:54, reason: User, GCodes spinning, available RAM 108908, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 331,331,331
Aux1 errors 0,0,0
MCU temperature: min 43.7, current 45.2, max 52.1
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Driver 0: position 27530, ok, reads 12882, writes 38 timeouts 0, SG min/max 0/1023
Driver 1: position 2814, ok, reads 12882, writes 38 timeouts 0, SG min/max 0/1023
Driver 2: position 2725, ok, reads 12882, writes 38 timeouts 0, SG min/max 0/1023
Driver 3: position 0, ok, reads 12882, writes 38 timeouts 0, SG min/max 0/1023
Driver 4: position 0, ok, reads 12883, writes 38 timeouts 0, SG min/max 0/1023
Driver 5: position 0, ok, reads 12883, writes 38 timeouts 0, SG min/max 0/1023
Date/time: 2021-02-02 22:09:51
Slowest loop: 211.65ms; fastest: 0.04ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 4.0ms, write time 152.3ms, max retries 0
=== Move ===
DMs created 125, maxWait 514613ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 458647, completed moves 458612, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 15], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is ready with "m122 b0" in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X190.481 Y213.861 E0.00113" in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 1143678, send timeouts 0, received 177174, lost 0, longest wait 21ms for reply type 6024, peak Tx sync delay 468, free buffers 48 (min 33)
=== Network ===
Slowest loop: 574.55ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0

@trobison What are you using to connect to the duet with? Is it a Mac or PC? What AV software have you got on it if any?

Acrylic, even regular plexi will work. You should also be able to order Coroplast panels online - that would be even better.

I don't have hints to give you other than https://fermio.xyz. While their stuff is mostly for Vorons, maybe they will be able to hook you up if you won't find a direct shop in your city or anywhere else within Germany.

If you are stuck, I can get you some recommendations from Poland

@phaedrux FYI - checked with 3.3b3 - behavior still there.

@mentaluproar what's your AV/Firewall?

There's a lot of variables going here that will make answering your question in a simple way difficult like how will you run the wires? In a chain? In a sleeve? Ziptied? What lengths? Loads of variables that will impact the type of wire to pick.

For example, if you go for chains, stay away from silicone sleeved wires. They will bind up on you and break with time.

I tried loads and recently I ended up either with PTFE or FEP sleeved wires - my brand of choice is Heluflon (easy to get in the EU, not sure about other places).
I use AWG 24 for almost everything except heaters - there I calculate the needed amperage and match gauge for the use.

You could also go with PTFE wires from Aliexpress or Amazon - they should work too. I used loads of those before switching to Heluflon and never had any issues.

They are more stiff - which can be both good and bad - again depending on your specific use case.

@Herve_Smith I think the design is great. It also helps us (duet peeps) get more representation in the Voron world and especially cool designs for our hardware.

One would hope we are all mature enough to appreciate the effort people go through to get something out there free of charge (no less).

There is interest

Good luck!

@wbrokow1 it might be easier for you to ask such questions in the Voron discord in the duet_rrf channel (where you already got some help in the past). People there are great and very helpful.

Also, check Voron's github for sample configs (including the UserMods) repo. You'll find a lot is already provided there and you just have to adapt the configs to your particular printer and needs.

@Lamooth Is it just on the Mac?
I remember having this problem for a long time - including duet resets midprint because of this. But this was in and before 3.2. Now it still happens every now and then, but never resets the Duet. At worst, I can't load the GUI at all, at best - I get a gray overlay over the GUI which prevents me from clicking stuff on the GUI, but at least I can see what's going on (this is much more often and worse when using BambuStudio-SoftFever edition).

The errors, freezes and resets only happened on Mac (regardless of browser) - never on Windows.

The one thing that could help was disabling Eset's Firewall I had installed.

@nikscha It works I've been using it for ages now, although I don't have a very elaborate layout. I mostly have HA watch hotend temp and once it's been at 45C for 2 minutes after a print - it switches the printer off.

My code is as follows:

  - platform: rest
    name: Voron_24 Status
    resource: http://<ip_here>/rr_status?type=3
    value_template: "{{ value_json.status }}"
    json_attributes:
      - temps
      - fractionPrinted
    force_update: true

  - platform: template
    sensors:
      voron_24_head_temp_current:
        value_template: "{{ states.sensor.voron_24_status.attributes.temps.current[1] }}"
        friendly_name: Hotend Temp
      voron_24_bed_temp_current:
        value_template: "{{ states.sensor.voron_24_status.attributes.temps.current[0] }}"
        friendly_name: Hotbed Temp
      voron_24_print_percentage:
        value_template: "{{ states.sensor.voron_24_status.attributes.fractionPrinted }}%"
        friendly_name: Print progress 

And this is how I put display it in Lovelace.

The important bits here (if you know this, forgive me, if not - maybe it will help) - is to keep the naming consistent. HA will convert the name from the first sensor into an entity_id.
So in my case, here it reads Voron_24 Status. HA will take it, convert it internally to voron_24_status and this is what you use below in the actual sensors.

And since I am waaaaaay too lazy ( ) I am going to wait for MQTT to come along before solving issues like not zeroing out of entries when the printer is off

See if that will work and if you get stuck, ping me and I'll be happy to help.

While waiting, you can easily use this:
https://github.com/iz3man/duet3d/blob/main/duet3d.yaml

Just add the lines to your configuration.yaml, modify for your printer and restart HA.

Shameless bump to @dc42

Is there any chance anything could be done here? Or should I abandon all hope?

I wonder if this is something we could get @dc42 to comment on? Is this something that can be adjusted?

Here's my attempt today (Took me a while longer to get it done).
I have not had a successful tune since the change of the heater. I tried both with the door open and hat off and on - it's always pretty much the same in terms of temp levels and differences.

Command was:

M303 T0 S265

Copying the result of the tune and the chart. You can clearly see the moment the fan kicked in.

Warning: Turning on the print cooling fan did not increase hot end cooling. Check that the correct fan has been configured.
Auto tuning heater 1 completed after 3 idle and 10 tuning cycles in 1026 seconds. This heater needs the following M307 command:
 M307 H1 R1.722 K0.381:0.000 D12.14 E1.35 S1.00 B0 V24.0
Edit the M307 H1 command in config.g to match this. Omit the V parameter if the heater is not powered from VIN.

I literally had the same problem yesterday, which was weird to me.
I'll take screenshots later today, but to explain what I did yesterday...

Duet 3 mini 5+ on 3.4.0 release build.
Heater was a 40W E3D packed into a Mosquito (blasphemy, I know ) inside a Voron V0.1 miniAfterburner toohead.

The 40W heater would work and PID tune properly, but was struggling.
I exchanged it to a 50W heater and from then on, I can't pid tune with the same error message above.

On the chart, the difference in heating up time once the part cooling fan kicked in was clearly visible, although the temperature drop itself was more or less the same as before the fan kicked in.