DWC not opening in browser

TheIndianDude

I'm using a Duet 2 Wifi on the latest version of RRF (3.5.4), and for some reason, DWC just won't open on any browser on my PC or my phone (I've tried Chrome, Edge, Opera, and FireFox to no avail). The diagnostics show an IP address and I'm able to ping it with no issues, so I'm not sure what's going on. This has been an issue with earlier versions of RRF for me as well and only with the WiFi boards, which is why I've switched to using the Duet Ethernet on my other printers (When connected via ethernet, DWC opens without issues). However, I would like to get the WiFi connection working. M122, M39, and M552 results and a few other screenshots shown below:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.4 (2024-11-24 10:43:42) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N85S4-7JTD8-3SN6J-9V97R
Used output buffers: 1 of 26 (13 max)
=== RTOS ===
Static ram: 23488
Dynamic ram: 73720 of which 208 recycled
Never used RAM 16060, free system stack 186 words
Tasks: NETWORK(1,ready,13.1%,141) HEAT(3,nWait 5,0.0%,330) Move(4,nWait 5,0.0%,361) DUEX(5,nWait 5,0.0%,23) MAIN(1,running,86.9%,368) IDLE(0,ready,0.1%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:09:31 ago, cause: software
Last software reset at 2025-01-15 14:10, reason: User, Gcodes spinning, available RAM 12508, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 28.7, current 29.4, max 29.6
Supply voltage: min 1.6, current 1.8, max 1.9, 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
Events: 1 queued, 1 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5: ok, SG min n/a
Driver 6: ok, SG min n/a
Driver 7: ok, SG min n/a
Driver 8: ok, SG min n/a
Driver 9: ok, SG min n/a
Driver 10: 
Driver 11: 
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 7.15ms; fastest: 0.15ms
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 1.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks 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
Q0 segments left 0
Code queue 0 is empty
=== DueX ===
Read count 0, 0.00 reads/min
=== Network ===
Slowest loop: 21.24ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.0
MAC address e0:98:06:a4:5e:7c
Module reset reason: Turned on by main processor, Vcc 3.36, flash size 4194304, free heap 43844
WiFi IP address 192.168.1.166
Signal strength -48dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
M39
SD card in slot 0: capacity 3.98GB, partition size 3.98GB, free space 3.71GB, speed 20.00MBytes/sec, cluster size 64kB
ok
M552 S-1
WiFi module stopped
ok
M552 S0
ok
WiFi module started
M552 S1
ok
WiFi module is connected to access point BeastWifi, IP address 192.168.1.166

TheIndianDude

I have tried to manually update the DWC Files as mentioned in the guide by deleting the www folder from the SD Card and unzipping the DWC files from Github into a new www folder, but this has not helped.

droftarts

@TheIndianDude Because you're getting a blank page in the browser, I'd say it wasn't connecting to Duet, and most likely your network router has an isolation zone for guest WiFi devices. It may be that it allows ping, but not html requests. If you can connect to the Duet, but the www folder is missing or corrupt, you get this message:

Your Duet rejected the HTTP request: page not found
Check that the SD card is mounted and has the correct files in its /www folder

You can set the Duet up in access point mode, and see if you can connect directly, to check everything on the Duet end is working, see https://docs.duet3d.com/en/User_manual/Machine_configuration/Networking#configuring-duet-in-wifi-access-point-mode

Ian