wite loading page

[rew3]

Hello there,
While setting up my duet 2 WiFi 90% of the times after an emergency reboot I get a white page instead of dwc.
Than after 30 minutes I can see DWC again.
What can I do?
Thanks

[dc42]

@rew3 have you tried reloading the browser tab? In most browsers you do this by pressing the F5 key.

[rew3]

@dc42 Yes, a lot of times

[dc42]

@rew3 which main firmware version, WiFi module firmware version and DWC version are you running?

[rew3]

@dc42 firmware is the latest stable version, and the same should be with wifi module firmware and DWC. How can i control wifi module and dwc version?

[jay_s_uk]

@rew3 the wifi version is reported in M122 (as well as the RRF version). feel free to post the full output here.
The DWC version can be found under settings > general

[rew3]

@jay_s_uk === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7JTD6-3SS6L-KA8ZQ
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 74132 of which 244 recycled
Never used RAM 16164, free system stack 184 words
Tasks: NETWORK(ready,13.1%,257) HEAT(delaying,0.0%,386) Move(notifyWait,0.1%,364) MAIN(running,86.4%,441) IDLE(ready,0.5%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:46 ago, cause: power up
Last software reset at 2021-09-18 15:05, reason: User, GCodes spinning, available RAM 13308, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 25.1, current 32.7, max 32.7
Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-09-20 10:37:31
Cache data hit count 4294967295
Slowest loop: 6.10ms; fastest: 0.16ms
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 4.2ms, 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 = -1 -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 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.62ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.26
  WiFi MAC address e0:98:06:a4:3a:5e
  WiFi Vcc 3.35, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 23920
  WiFi IP address 192.168.1.38
  WiFi signal strength -56dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

[rew3]

@dc42 hello still there?

[dc42]

@rew3 I don't see anything in that M122 report that would account for that problem. Here ar4 some suggestions:

• Which browser are you using? Have you tried a different browser?
• When this next happens, connect a laptop running a terminal emulator (e.g. YAT) to the Duet via USB. Then send M122 via USB and save the result. After that, send M122 P104 via USB to run a test of the SD card.