I think you're likely right, there. It's a TP-Link router which I've never had a problem with before, but I think I came across a few posts on here that name TP-Link and strange problems.
Weirdly, it didn't affect any other devices on the network, including the laptop I posted here from (which is also on the 2.4 gig radio). The "bad reply format version" message confused me, too (although that doesn't take much these days
).
So, weirdly enough it just suddenly started working. I turned the power off and on again, it started the hotend fan as it normally does on startup, then maybe 20 seconds later the hotend fan ran again (as if the board had reset itself) and since then it appears to be working fine.
I had been having the same problems accessing from a tablet as well, otherwise I would have assumed it was my computer. Maybe something went funny with the wifi router (again, nothing had changed about it for months).
If anyone else has the same problem, I'm sorry but I can't suggest anything to try other than just waiting a couple of hours and trying again.
Hi,
I'm hoping someone can help me. I've been using my board (a Duet Wifi) for some time and had no problems with it (apart from blowing one of the fan mosfets, but that's my own fault).
This evening, I was uploading a file getting ready to print, and the upload seemed to fail (it never completed). Since then I've not been able to connect to the duet over the wifi.
I've restarted the duet several times (by removing all power) to no avail.
Right now, it's connected via USB and after a M552 S0 then M552 S1 I'm getting "Error retrieving WiFi status message: bad reply format version". A search showed this to be due to a mismatch between the firmwares on the ESP and the main board, but I've not done any firmware updates in a long time, and the machine's been powered off many times since then. M115 gives: "FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.02(RTOS) ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-12-24b1" and M122 gives:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 00000-00000-00000-00000-00000-00000
Used output buffers: 1 of 20 (10 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98612 of which 0 recycled
Exception stack ram used: 312
Never used ram: 6624
Tasks: NETWORK(ready,1492) HEAT(blocked,1232) MAIN(running,3796) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:00:28 ago, cause: power up
Last software reset at 2019-11-02 17:49, reason: User, spinning module GCodes, available RAM 6436 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 37.8, current 38.3, max 38.4
Supply voltage: min 12.1, current 12.1, max 12.3, 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: 1970-01-01 00:00:00
Cache data hit count 61119592
Slowest loop: 0.19ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 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 ready with "M122" 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: 0.14ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
- WiFi -
Network state is changing mode
WiFi module is trying to connect
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.22
WiFi MAC address 5c:cf:7f:a4:a4:76
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 30496
Socket states: 0 0 0 0 0 0 0 0
I've masked "board ID" 'cause I have no idea if it's sensitive (although TBF I have no idea if any of the rest of it is 
)
If it's of any relevance, the duet is less than 1m from the wifi router - the same one it's always been connected to.
Please help!
Thanks,
MexWave