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?
To be sure - what you see in DWC is the same single fan. Fan 0 is the print cooling fan (or should be configured that way for most slicers).
Fan 1 is the hotend cooling fan. Any fan that is configured to react to temperature will not show up in DWC (since there is no point).
I've been following your posts for a while now and I will freely admit, I do not remember everything that was said in them, but I just started wondering - if this is a test done on a simple hotend - would it make any sense if any of us got your gcode files and tried to print these objects on our printers provided they run Duet 3 6HC and at least one 3HC? Just to increase the testing device pool to see what else we can see?
I am not sure how the removal of your counterweight system would impact this here.
If it does make sense, I would be happy to take that gcode for a spin on my 6HC+3HC combo in a Voron 2.4 (where 6HC handles the movement, 3HC handles the extruder and hotend/part cooling).
@mentaluproar If I read correctly, lockdown is a form of a firewall and privacy tool.
So one could compare it against eset - which is what I have and I have exactly the same issues as you do. I have to disable web protection in my eset to be able to use the DWC. This came on with a DWC change a while back.
Man I'm blind... That did it! Thanks
I was just about to create a new topic on this - since I see the same issue. It stopped working on 3.2, but 3.1.1 was perfectly fine. I thought for a sec it was the DHT itself (I have another thread on my issues with it) and grabbed a brand new one - but that still didn't work.
I haven't really tested it yet after the initial test runs.
In my case, the range was always between 1% and 25%. So not really usable. I have loads of the 693ZZ now, so can experiment. I'll try to paint it over with a sharpie and see what that will do.
Another thing is that I had to enlarge the cutout for the bearing. My bearing is exactly 4mm and the gap is the same. There's no way washers will fit in there along with the bearing.
So this will be a small necro of the thread, but I believe I figured out what is causing the problem.
To be clear - my comparison is between a Mac and a regular Windows 10 PC.
The problem is the Eset Smart Security on the Mac, but only if you use ethernet. If you switch to Wifi - problem is gone. On Windows - also with Eset - the problem never exists.
Fortunately, with more recent firmwares for the Duet - the printer will no longer reboot midprint if I try to connect to it, but it will keep disconnecting all the time.
The workaround for the rebooting is to disable Web protection in Eset when working with Duets (and this happens on all my duet boards and different versions of DWC (even the newest one).
OK. Now I am even more lost...
3.3b1 solves the problem. Height map is scanned and loaded properly.
Same steps as above exactly. Worked first time.
Now to try a print!
Well assuming 3.3 comes out of beta soon, I will close this for now. I have a workaround for 3.2.2 that always works... it's just weird an annoying is all