Help! DWC Disconnects and Drops after extensive troubleshooting

Danal

@alexd607 said in Help! DWC Disconnects and Drops after extensive troubleshooting:

When I try to access the DWC I'm met with a blank white screen that never populates...

Does it time out?

Can you ping it?

dc42

@alexd607 said in Help! DWC Disconnects and Drops after extensive troubleshooting:

@droftarts

I don't have a filament sensor or panel due fitted.

It's strange that that is what it's reporting considering the last reset was done by me via M112.

Please run another M122 report after the network has disconnected, without doing any emergency stops. I want to see if the "Heat task stuck" report is a recurring thing, or if it is a consequence of the emergency stop.

alexd607

@Danal

It does not timeout, and it still pings without any loss.

alexd607

@dc42

I was able to get momentarily connected and run M122 right after power-up, here's the result:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.04 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3S0-7J1F6-3S06T-9A43F
Used output buffers: 3 of 24 (18 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 92808 of which 356 recycled
Exception stack ram used: 268
Never used ram: 11960
Tasks: NETWORK(ready,676) HEAT(blocked,1232) MAIN(running,3808) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:00:44 ago, cause: power up
Last software reset at 2019-12-04 09:23, reason: Heat task stuck, spinning module FilamentSensors, available RAM 11568 bytes (slot 1)
Software reset code 0x40ad HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20004a9c Task 0x4e49414d
Stack: 0044d38f 004451d6 6100f000 3f000000 00000000 00000000 00000000 3331bb4c 41880000 3e178897 3e1cd04f be09b238 3e3a3fd4 00000000 00000000 00000000 3f800000 3f800000 3f000000 20000010 20003258 20002b88 0044d38f
Error status: 0
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 26.5, current 26.8, max 27.0
Supply voltage: min 24.3, current 24.4, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-12-06 08:24:47
Cache data hit count 157313766
Slowest loop: 1.10ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 2 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 201.19ms; fastest: 0.08ms
Responder states: HTTP(2) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.23
WiFi MAC address 84:f3:eb:83:48:e5
WiFi Vcc 3.39, reset reason Power on
WiFi flash size 4194304, free heap 16832
WiFi IP address 192.168.1.151
WiFi signal strength -21dBm, reconnections 0, sleep mode modem
Socket states: 2 2 0 0 0 0 0 0

Danal

If it pings, you have a solid network connection and we can quit looking at the basic networking stuff.

Were it me, I'd rebuild the www directory on the SD card.

And/or, as a test, you can put your own "test.html" page on the www directory, and test via:

http://(ip of printer)/test.html

droftarts

@alexd607 said in Help! DWC Disconnects and Drops after extensive troubleshooting:

Last software reset at 2019-12-04 09:23, reason: Heat task stuck, spinning module FilamentSensors, available RAM 11568 bytes (slot 1)
Software reset code 0x40ad HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20004a9c Task 0x4e49414d
Stack: 0044d38f 004451d6 6100f000 3f000000 00000000 00000000 00000000 3331bb4c 41880000 3e178897 3e1cd04f be09b238 3e3a3fd4 00000000 00000000 00000000 3f800000 3f800000 3f000000 20000010 20003258 20002b88 0044d38f
Error status: 0

@dc42 Same error again

Ian

alexd607

@Danal

I've tried rebuilding the www folder already, as well as every other folder. I've tried rolling back to older firmware, and I've tried reloading the most recent full releases. All had the same result, no luck.

Danal

If it pings, you can get packets to/from. That means WiFi is working, fundamental packet routing, etc. If it does not show a web page, that means something is broken in the HTTP layer, or web server, or content.

To help decide which try putting:

<html>
<head>
<title>Test Title</title>
</head>
<body>
Test Body
</body>
</html>

In /www/test.html

Then use a browser to attempt to load http://(ip of printer)/test.html

What happens?

alexd607

@Danal

I'll give this a try this evening and report back.

droftarts

@alexd607 said in Help! DWC Disconnects and Drops after extensive troubleshooting:

Last software reset at 2019-12-04 09:23, reason: Heat task stuck, spinning module FilamentSensors, available RAM 11568 bytes (slot 1)
Software reset code 0x40ad HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20004a9c Task 0x4e49414d
Stack: 0044d38f 004451d6 6100f000 3f000000 00000000 00000000 00000000 3331bb4c 41880000 3e178897 3e1cd04f be09b238 3e3a3fd4 00000000 00000000 00000000 3f800000 3f800000 3f000000 20000010 20003258 20002b88 0044d38f
Error status: 0

@dc42 Same error again

Ian

dc42

Please try firmware 2.05RC2 in case this issue is related to a USB output issue in previous releases.

alexd607

@dc42

Tried upgrading to firmware 2.05RC2. No change.