Duet web control keeps disconnecting 'Failed to get file list'
-
Thx for the quick response!
I updated the firmware and DWC to 3.4.5. The error 'failed to get file list' is now gone and the connectivity issues are better but still there.
It seems to randomly disconnect with the message 'network error'. sometimes it reconnects itself and other times I have to put in te M552 commannd manualy.
Any ideas what I could try?
-
-
I've tried the the steps in WIFI troubelshouting that are applicable to duets with ethernet but no luck so far. I have also replaced the router + ethernet cable but also no effect.
I noticed the MCU temperature is consistently around 40C even when the printer is idle (it says max temp 41C). Is this normal and could it be the reason it keeps randomly disconnecting?
if anyone has an idea what I could try please let me know. If not I might consider sending the board back to see if its faulty.
-
@jasper-k i would suggest trying a different SD card and see if the error still occurs.
40 degrees isn't hot for an MCU -
@jay_s_uk I put a new SD card in with all news files and still the same issue. I think I am going to return the board to see if its faulty.
Thx for the help. I'Il post here if there are any updates on the situation
-
@jasper-k said in Duet web control keeps disconnecting 'Failed to get file list':
I think I am going to return the board to see if its faulty.
When and where did you purchase it?
-
-
@jasper-k said in Duet web control keeps disconnecting 'Failed to get file list':
@Phaedrux My apologies for the late response. I bought it in the Netherlands on 123-3D.nl
How long ago was that?
-
@Phaedrux Only a few weeks
-
Before we go down the road of warranty replacement can you send M122 again when you are connected to the network please?
-
@Phaedrux I just turned on the duet and couldnt connect. So I mannualy turned networking off with M552 S0 en turned it back on with M552 P'different IP adress' S1. After this I was able to connect for about one minute and got this M122 report:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.4+1 (2022-11-15 17:36:33) running on Duet 3 MB6HC v1.02 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3T0-6J9F2-3S46N-KU1Z8
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 152740
Dynamic ram: 98068 of which 0 recycled
Never used RAM 99864, free system stack 208 words
Tasks: NETWORK(ready,29.4%,210) ETHERNET(notifyWait,0.1%,443) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,333) TMC(notifyWait,6.8%,91) MAIN(running,63.5%,1079) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:07 ago, cause: power up
Last software reset at 2023-01-26 14:41, reason: User, GCodes spinning, available RAM 99744, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 127
MCU temperature: min 21.0, current 32.7, max 32.8
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.3, max 12.6, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 53637, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 53637, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 53637, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 53637, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 53641, writes 11 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 53641, writes 11 timeouts 0
Date/time: 2023-02-09 10:40:17
Slowest loop: 10.82ms; fastest: 0.06ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.0ms, write time 16.1ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle 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 609, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 340/0/0
Tx timeouts 0,0,339,0,0,268 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 11.52ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
= WiFi =
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0 -
@jasper-k said in Duet web control keeps disconnecting 'Failed to get file list':
3.4.4+1
Can you try updating the firmware using the USB flash technique described here?
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards
Use this firmware file: https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet3Firmware_MB6HC.bin
Then update the web interface files on the SD card by downloading this zip file: https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/DuetWebControl-SD.zip
and extracting it into to the WWW folder. Replace the existing files.
What kind of PC are you trying to connect to the Duet from? Can you describe your network setup? Is the Duet connected directly to a PC, or is there a switch in between?
-
@Phaedrux thanks for the tips, I'Il try it today. My PC is a 5 year old Acer laptop (windows 11). The Duet is connected to a normal tp-link wifi router via ethernet cable. Never had any problems with this setup untill I bought a new Duet board. Also tried a different router and ethernet cable and changed some settings like channel, but no succes yet
-
@Phaedrux I succesfully flashed the firmware to the Duet with the instructions. Also updated the web interface files on the SD card. Afterwards I started the Duet and it is still having the same issue: works for 1 min and randomly disconnects.
Is there anything I can still try or should I contact 123-3D.nl for warranty replacement?
-
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
