DWC not accessible, M122 causes timeout

stretchy

@phaedrux the duet 2 board was purchased on duet3d.com, I believe in mid 2020 to early 2021.

chrishamm

@stretchy RepRapFirmware 3.0 is outdated, please upgrade to RRF+DWC v3.3 or newer - see here. If the board still fails to serve the web interface after that, please try to access it from another device (e.g. smartphone or tablet) and check if that works. If it still resets at some point, please share the output from M122 again.

stretchy

@chrishamm I've updated to RRF3.3 using these steps:

copy Duet2CombinedFirmware.bin to /sys
copy the folders /js, /css, /fonts, /img into /sys (not documented what they do but to be safe I copied these too)
copy the Duet2CombinedIAP.bin to the SD card (can only be found in the old RRF 3.0 release, iap4e.bin does not work anymore)
insert SD and M997 S0 to start update
M115 to verify update
M122 to gather new log

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet Ethernet 1.02 or later + DueX5 FIRMWARE_DATE: 2021-06-15 21:45:03
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet Ethernet 1.02 or later + DueX5
Board ID: XXX
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 70988 of which 24 recycled
Never used RAM 19528, free system stack 205 words
Tasks: NETWORK(ready,6.1%,565) HEAT(delaying,0.0%,341) Move(notifyWait,0.1%,364) DUEX(notifyWait,0.0%,24) MAIN(running,92.8%,467) IDLE(ready,1.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:01:04 ago, cause: software
Last software reset time unknown, reason: StuckInSpinLoop, GCodes spinning, available RAM 19528, slot 1
Software reset code 0x0083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0040080f BFAR 0xe000ed38 SP 0x200034dc Task NETW Freestk 541 ok
Stack: 00411ff3 00411eb8 01000000 00000108 00411c57 00000108 00000108 0000000b 0041217d 00000000 0041218f 00000000 00412225 00000000 ffffffff 20011800 00000000 00000001 00000000 00000006 004133cf 00000000 0045a465 20011744 00000000 20011744 0045a701
Error status: 0x00
Step timer max interval 0
MCU temperature: min 31.9, current 32.4, max 32.9
Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0, ok, SG min/max not available
Driver 6: position 0, ok, SG min/max not available
Driver 7: position 0, ok, SG min/max not available
Driver 8: position 0, ok, SG min/max not available
Driver 9: position 0, ok, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 2530716960
Slowest loop: 4.10ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== 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, chamberHeaters = -1 -1 -1 -1
=== 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 ready with "M122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== DueX ===
Read count 1, 0.94 reads/min
=== Network ===
Slowest loop: 0.22ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
Interface state disabled, link down
ok

stretchy

@stretchy
the issue still persists; DWC is not accessible through a browser while pinging the IP is possible.
M122 works but only before I enable networking (M552 S1), after I've done so M122 crashes the board, it's rebooted ~15s later and the config.g is loaded again with networking disabled. Therefore M122 works again.

Phaedrux

@stretchy said in DWC not accessible, M122 causes timeout:

copy the folders /js, /css, /fonts, /img into /sys (not documented what they do but to be safe I copied these too)

These must be in the /www folder. Do you also have them there?
Can you show a screen shot of your folder structure?

chrishamm

@stretchy Thanks for that! Any ideas @dc42?

dc42

@stretchy if sending M552 S1 followed by sending M122 causes timeout, then it sounds to me that the Ethernet module has failed. Is the chip on it getting hot?

If the board was less than one year old from when you purchased it to when you first reported this problem, then we will replace the board under warranty. If not, then the Ethernet module is available separately, and a new one may fix the problem.

stretchy

@phaedrux you're right, I removed the www folders from /sys.
Here's the file structure on the SD card

D:.
├───sys
│       iap4e.bin
│       config.json
│       bed.g
│       config.g
│       homeall.g
│       homex.g
│       homey.g
│       homez.g
│       pause.g
│       resume.g
│       sleep.g
│       stop.g
│       tfree0.g
│       tpre0.g
│       tpost0.g
│       Duet2CombinedFirmware.bin
│       favicon.ico.gz
│       index.html.gz
│       manifest.json.gz
│       precache-manifest.a4ab8f573fcc203b798fa7d11eee39d5.js.gz
│       service-worker.js.gz
│       Duet2CombinedIAP.bin
│
└───www
    │   favicon.ico.gz
    │   manifest.json.gz
    │   precache-manifest.a4ab8f573fcc203b798fa7d11eee39d5.js.gz
    │   service-worker.js.gz
    │   index.html.gz
    │   DuetAPI.xml
    │
    ├───css
    │       Accelerometer.5c60999b.css.gz
    │       app.ce075a4e.css.gz
    │       GCodeViewer.9597b317.css.gz
    │       HeightMap.4d390d72.css.gz
    │       ObjectModelBrowser.c5e13b42.css.gz
    │       OnScreenKeyboard.7f43fe4b.css.gz
    │
    ├───fonts
    │       materialdesignicons-webfont.147e3378.woff
    │       materialdesignicons-webfont.147e3378.woff.gz
    │       materialdesignicons-webfont.174c02fc.ttf.gz
    │       materialdesignicons-webfont.64d4cf64.eot.gz
    │       materialdesignicons-webfont.7a44ea19.woff2
    │       materialdesignicons-webfont.7a44ea19.woff2.gz
    │
    ├───img
    │   └───icons
    │           android-chrome-192x192.png.gz
    │           android-chrome-512x512.png.gz
    │           android-chrome-maskable-192x192.png.gz
    │           android-chrome-maskable-512x512.png.gz
    │           apple-touch-icon-120x120.png.gz
    │           apple-touch-icon-152x152.png.gz
    │           apple-touch-icon-180x180.png.gz
    │           apple-touch-icon-60x60.png.gz
    │           apple-touch-icon-76x76.png.gz
    │           apple-touch-icon.png.gz
    │           favicon-16x16.png.gz
    │           favicon-32x32.png.gz
    │           msapplication-icon-144x144.png.gz
    │           mstile-150x150.png.gz
    │           safari-pinned-tab.svg.gz
    │
    └───js
            Accelerometer.4a8a402b.js.gz
            Accelerometer.4a8a402b.js.map.gz
            app.24acd1b2.js.gz
            app.24acd1b2.js.map.gz
            GCodeViewer.95d3cd80.js.gz
            GCodeViewer.95d3cd80.js.map.gz
            HeightMap.a082b8e6.js.gz
            HeightMap.a082b8e6.js.map.gz
            ObjectModelBrowser.0b9b2798.js.gz
            ObjectModelBrowser.0b9b2798.js.map.gz
            OnScreenKeyboard.a880bca8.js.gz
            OnScreenKeyboard.a880bca8.js.map.gz

Phaedrux

is there also a firmware folder in the root of the sd card?

stretchy

@phaedrux there is not. It's running the latest stable RRF 3.3. AFAIK 3.3 introduces the /firmware directory but that has not been automatically created upon updating the firmware. I know the board is alive and responds to M115 and M122 (again as long as networking is disabled) and G28 work as well.

stretchy

@dc42 The chip on the ethernet daughterboard is indeed getting unreasonably hot.

Phaedrux

When and where did you purchase the Duet?

stretchy

@phaedrux February 2020 via Filafarm.de
The hardware is definitely faulty but the fault first occurred late 2021.

Phaedrux

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.

stretchy

final update:
I had my organization purchase a new Ethernet module off of ebay, installed said module and everything is running as expected again.
Many thanks for all your help