DWC not accessible, M122 causes timeout

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