Failed to add SSID to remembered list Duet 2 WIFI
-
@lickett_e_splitt said in Failed to add SSID to remembered list Duet 2 WIFI:
Error retrieving WiFi status message: bad reply format version
As @nhof says. This message:
Error retrieving WiFi status message: bad reply format version
suggests that the main and WiFi firmware versions may be out of step. Try upgrading the WiFi firmware to DuetWiFiServer version 1.23, available from https://github.com/dc42/RepRapFirmware/releases/download/2.03beta3/DuetWiFiServer.bin.
-
I just downloaded the WIFI Firmware from the Github link above, uploaded it, It counted down in 5% increments and I got Upload Successful.
M122 still reports
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSD-6J1F8-3SJ6L-K8TV9
Used output buffers: 7 of 20 (7 max)
=== RTOS ===Then
M587 S"my SSID" P"My network password"
ok
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
M587
M587: Failed to retrieve network list
ok
Error retrieving WiFi status message: bad reply format version
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
M552 S1
ok
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
M587 S"my SSID" P"My network password"
M587: Failed to add SSID to remembered list
ok
Error retrieving WiFi status message: bad reply format version
WiFi module is idle
WiFi reported error: no known networks found -
Does it actually show version 1.23 for the wifi server version at the end of the M122 report?
-
I suspect that your board has a faulty WiFi module, because you shouldn't be getting that "bad reply format version" message. Are you able to read the WiFi firmware version from the WiFi section of the M122 report, as @Phaedrux suggests?
-
Sorry, thought I had all the output from M122 that we needed. Here is the full output.
WiFi module is idle
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSD-6J1F8-3SJ6L-K8TV9
Used output buffers: 4 of 20 (4 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98532 of which 0 recycled
Exception stack ram used: 256
Never used ram: 6760
Tasks: NETWORK(ready,1276) HEAT(blocked,1256) MAIN(running,3868) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:00:21 ago, cause: power up
Last software reset time unknown, reason: Heat task stuck, spinning module Platform, available RAM 6356 bytes (slot 0)
Software reset code 0x00a0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043380f BFAR 0xe000ed38 SP 0x2000493c Task 0x4e49414d
Stack: 0043ca33 00449aae 41000000 00000000 00000000 00000000 00000000 3e178897 3e1cd04f 41880000 3e3a33b0 3e638eb9 3e92497a 3b750939 3ecccd35 bd7a7541 3f800000 c0a00000 00000000 60000010 00000001 2000855c 0043ca33
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 21.4, current 25.2, max 25.3
Supply voltage: min 0.0, current 0.1, max 0.2, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 39256480
Slowest loop: 0.26ms; fastest: 0.06ms
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
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 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: 1.27ms; 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 idle
Failed messages: pending 0, notready 0, noresp 0
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0
ok
Error retrieving WiFi status message: bad reply format version
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
- WiFi -
-
Not sure why it looks like the M122 cuts off after Socket States:
-
Please ask for your Duet to be replaced under warranty. i think it needs a new WiFi module.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 I think I am having the same issue on a v1.02 board that I hadn't ever used and am just now using after over 2 years since buying from Filastruder. I just uploaded Duet2Firmware-2.05.1.zip and DuetWiFiServer-1.23.bin. The wifi module blinks once when plugging into my desktop and M122 reads as follows ---
=== Network === Slowest loop: 1.25ms; 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 idle Failed messages: pending 0, notready 0, noresp 2 Failed to get WiFi status Socket states: 0 0 0 0 0 0 0 0 -
@UnderDoneSushi said in Failed to add SSID to remembered list Duet 2 WIFI:
I think I am having the same issue on a v1.02 board
probably best to make a new topic instead of adding to a year old one.
create the macros from the link below then run them, or send each individual command from all three over USB and post the output of it all in a new topic if it doesn't sort the issue. (you can skip M291)
also substitute your own wifi details in M587 ofc.
-
@bearer thank bearer, yeah I should have just posted it in a new one
