4. WiFi reported error: Failed while trying to connect

WiFi reported error: Failed while trying to connect

  • thrawn86

    Brand new board out of the box from filastruder (external antenna). Immediately run M587 through YAT, etc and was met with above error.

    Tried updating firmware with M997 and seems successful:

    Trying to connect at 230400 baud:  success<LF>Erasing 4096 bytes...<LF>Erasing 212992 bytes...<LF>Uploading file...<LF>5% complete<LF>10% complete<LF>15% complete<LF>20% complete<LF>25% complete<LF>30% complete<LF>35% complete<LF>40% complete<LF>45% complete<LF>50% complete<LF>55% complete<LF>60% complete<LF>65% complete<LF>70% complete<LF>75% complete<LF>80% complete<LF>85% complete<LF>90% complete<LF>95% complete<LF>Upload successful<LF>ok<LF>WiFi module started<LF>WiFi reported error: no known networks found<LF>WiFi module is idle

    Re running M587 unsuccessful.

    M122+M115 reports:

    FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-12-13b1<LF>ok<LF>WiFi reported error: Failed while trying to connect to "*****"<LF>WiFi module is idle<LF>

    === Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later<LF>Board ID: 08DLM-996RU-N8PS4-7JKDG-3S86P-TBA7N<LF>Used output buffers: 3 of 24 (3 max)<LF>=== RTOS ===<LF>Static ram: 25712<LF>Dynamic ram: 94000 of which 64 recycled<LF>Exception stack ram used: 256<LF>Never used ram: 11040<LF>Tasks: NETWORK(ready,1304) DHTSENSOR(blocked,240) HEAT(blocked,912) MAIN(running,3824) IDLE(ready,160)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:00:19 ago, cause: power up<LF>Last software reset details not available<LF>Error status: 0<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 33.8, current 36.8, max 36.9<LF>Supply voltage: min 0.0, current 0.0, max 0.0, under voltage events: 0, over voltage events: 0, power good: no<LF>Driver 0: ok, SG min/max not available<LF>Driver 1: ok, SG min/max not available<LF>Driver 2: ok, SG min/max not available<LF>Driver 3: ok, SG min/max not available<LF>Driver 4: ok, SG min/max not available<LF>Date/time: 1970-01-01 00:00:00<LF>Cache data hit count 28931951<LF>Slowest loop: 1.08ms; fastest: 0.05ms<LF>I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0<LF>=== Move ===<LF>Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms<LF>Bed compensation in use: none, comp offset 0.000<LF>=== DDARing ===<LF>Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0<LF>=== Heat ===<LF>Bed heaters = 0 -1 -1 -1, chamberHeaters = 2 -1<LF>Heater 1 is on, I-accum = 0.0<LF>=== GCodes ===<LF>Segments left: 0<LF>Stack records: 2 allocated, 0 in use<LF>Movement lock held by null<LF>http is idle in state(s) 0<LF>telnet is idle in state(s) 0<LF>file is idle in state(s) 0<LF>serial is ready with "M122" in state(s) 0<LF>aux is idle in state(s) 0<LF>daemon is idle in state(s) 0<LF>queue is idle in state(s) 0<LF>autopause is idle in state(s) 0<LF>Code queue is empty.<LF>=== Network ===<LF>Slowest loop: 1.26ms; fastest: 0.00ms<LF>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)<LF>HTTP sessions: 0 of 8<LF>- WiFi -<LF>Network state is changing mode<LF>WiFi module is trying to connect<LF>Failed messages: pending 0, notready 0, noresp 0<LF>WiFi firmware version 1.23<LF>WiFi MAC address bc:dd:c2:2d:64:f6<LF>WiFi Vcc 3.47, reset reason Turned on by main processor<LF>WiFi flash size 4194304, free heap 26984<LF>Socket states: 0 0 0 0 0 0 0 0<LF>ok<LF>

    Found another thread with very similar symptoms: https://forum.duet3d.com/topic/9807/failed-to-add-ssid-to-remember-list

    And followed the procedure within:
    dc42 said in Failed to add SSID to remember list:

    • Run M115 to check that the 2.03beta3 firmware is installed (or at least version 2.02)
    • Then run M997 S1 to install the DuetWiFiFirmware.bin file
    • Then run M552 S0 to put the WiFi module in idle mode
    • Then run M552 to check that it is in idle mode (not still "being started")
    • Then you should be able to use M587 to add the SSID and password.

    With slightly different results, now I get a code-7:

    ok<LF>WiFi reported error: Failed while trying to connect to ********<LF>WiFi module is idle<LF>Error retrieving WiFi status message: SPI timeout<LF>WiFi module is idle<LF>Failed to change WiFi mode (code -7)<LF>

    Little bit lost at this point 😕 Any ideas?

    0
  • bearer

    ref step 3 and set up line ending in yat
    https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7#s6

    0
  • thrawn86

    thank you for this insight.

    0
  • bearer

    Its a lot easier to read when the <LF> tuns into actual line feeds; your call.

    0
  • thrawn86

    The time you've spent typing these two posts is already >= the time it takes to skim the first few lines of diagnostic output, the other two YAT responses are two lines each and the rest of my procedure is documented both in bullets and in another thread with a similar issue.

    If you have any other suggestions I'm all ears, but dropping into a thread and saying only that comes off very rudely.

    e: not the machine right this second but hopefully this will help

    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later<LF>
Board ID: 08DLM-996RU-N8PS4-7JKDG-3S86P-TBA7N<LF>
Used output buffers: 14 of 24 (14 max)<LF>
=== RTOS ===<LF>
Static ram: 25712<LF>
Dynamic ram: 94000 of which 64 recycled<LF>
Exception stack ram used: 304<LF>
Never used ram: 10992<LF>
Tasks: NETWORK(ready,540) DHTSENSOR(blocked,228) HEAT(blocked,912) MAIN(running,3824) IDLE(ready,160)<LF>
Owned mutexes:<LF>
=== Platform ===<LF>
Last reset 00:03:52 ago, cause: power up<LF>
Last software reset details not available<LF>
Error status: 0<LF>
Free file entries: 10<LF>
SD card 0 detected, interface speed: 20.0MBytes/sec<LF>
SD card longest block write time: 0.0ms, max retries 0<LF>
MCU temperature: min 34.9, current 37.4, max 37.5<LF>
Supply voltage: min 0.0, current 0.0, max 0.1, under voltage events: 0, over voltage events: 0, power good: no<LF>
Driver 0: ok, SG min/max not available<LF>
Driver 1: ok, SG min/max not available<LF>
Driver 2: ok, SG min/max not available<LF>
Driver 3: ok, SG min/max not available<LF>
Driver 4: ok, SG min/max not available<LF>
Date/time: 1970-01-01 00:00:00<LF>
Cache data hit count 430705318<LF>
Slowest loop: 200.47ms; fastest: 0.05ms<LF>
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0<LF>=== Move ===<LF>
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms<LF>
Bed compensation in use: none, comp offset 0.000<LF>
=== DDARing ===<LF>
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0<LF>
=== Heat ===<LF>
Bed heaters = 0 -1 -1 -1, chamberHeaters = 2 -1<LF>
Heater 1 is on, I-accum = 0.0<LF>
=== GCodes ===<LF>
Segments left: 0<LF>
Stack records: 2 allocated, 0 in use<LF>
Movement lock held by null<LF>
http is idle in state(s) 0<LF>
telnet is idle in state(s) 0<LF>
file is idle in state(s) 0<LF>
serial is ready with "M122" in state(s) 0<LF>
aux is idle in state(s) 0<LF>
daemon is idle in state(s) 0<LF>
queue is idle in state(s) 0<LF>
autopause is idle in state(s) 0<LF>
Code queue is empty.<LF>=== Network ===<LF>
Slowest loop: 1280.47ms; fastest: 0.00ms<LF>
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)<LF>
HTTP sessions: 0 of 8<LF>- WiFi -<LF>
Network state is running<LF>
WiFi module is idle<LF>
Failed messages: pending 0, notready 0, noresp 0<LF>
WiFi firmware version 1.23<LF>
WiFi MAC address bc:dd:c2:2d:64:f6<LF>
WiFi Vcc 3.47, reset reason Turned on by main processor<LF>
WiFi flash size 4194304, free heap 26504<LF>
Socket states: 0 0 0 0 0 0 0 0<LF>ok<LF>```
    0
  • Phaedrux
    Moderator

    Hang tight while I figure out what code 7 is. Haven't seen that one before.

    And I'm sorry but if you looked at M122 posts all day you'd want the proper formatting as well. Trying to read that on a mobile phone is nearly impossible, and on a monitor it's still eye wrenching. Please do a courtesy to those trying to help you by saving their poor eyeballs. 🤓

    0 bearer thrawn86 2 Replies
  • bearer

    This post is deleted!
    0
  • thrawn86

    @Phaedrux
    Do you think this is a failed wifi module like dc42 suggested in the post I linked?

    This board was already a replacement for another failed duet thats out of warranty 😕

    0 Phaedrux droftarts 2 Replies
  • Phaedrux
    Moderator

    @thrawn86 It's possible. Still waiting for DC to take a look.

    0
  • dc42
    administrators

    That code means that the WiFi module didn't respond to a request for a transaction from the duet.

    Are you certain that the WiFi firmware that you put on it was the DuetWiFiServer-1.23.bin file, renamed to DuetWiFiServer.bin before you ran M997 S1 ?

    0 thrawn86 1 Reply
  • droftarts
    Moderator

    @thrawn86 from switching on/reset, no SD card, connect via YAT on USB, then try sending M552 S-1 to disable module, then M552 S0 to enable module but not turn on WiFi, then add SSID with M587, and finally enable with M552 S1. Sometimes disabling then enabling kicks it into life.

    Ian

    0
  • thrawn86

    @dc42
    Positive. Any reason I shouldn't be using 2.05.1 and 1.23?

    I have repeated the process a few times and occasionally have seen other errors including Code 4, Code 7, status error: Bad Reply format and status error: SPI timeout

    M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-7JKDG-3S86P-TBA7N
Used output buffers: 1 of 24 (10 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 94000 of which 64 recycled
Exception stack ram used: 320
Never used ram: 10976
Tasks: NETWORK(ready,1268) DHTSENSOR(blocked,228) HEAT(blocked,912) MAIN(running,3692) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:10:07 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11032 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 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 33.4, current 33.5, max 33.8
Supply voltage: min 11.8, current 11.9, max 11.9, 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 971815164
Slowest loop: 99.82ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = 2 -1
Heater 1 is on, I-accum = 0.0
=== 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: 1.28ms; 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.23
WiFi MAC address bc:dd:c2:2d:64:f6
WiFi Vcc 3.47, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26584
Socket states: 0 0 0 0 0 0 0 0
ok
WiFi reported error: Failed while trying to connect to ***
WiFi module is idle
    0 bearer 1 Reply
  • bearer

    @thrawn86 said in WiFi reported error: Failed while trying to connect:

    Any reason I shouldn't be using 2.05.1 and 1.23?

    There is no wifi firmware 2.05.1; that is reprap firmware. Reprap firmware 2.05.1 which is released together with DuetWiFiServer-1.23.bin; and it needs to be renamed to just DuetWifiServer.bin if you're doing things manually. In any case you'll have to have a valid DuetWiFiServer.bin file on the SD card as the latest M122 does show WiFi firmware version 1.23

    0 thrawn86 1 Reply
  • thrawn86

    @bearer
    2.05.1 being the firmware reported by the board. I assume its relevant, but I'm sorry if my nomenclature isn't correct here.

    The title of the github page I downloaded this firmware from is literally "Release 2.05.1" so I assume that both the combined firmware and wifi firmware linked therein are the correct ones to use. M122 reports that both are those versions are installed on their respective parts. If this isn't correct, please let me know.

    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later

    WiFi firmware version 1.23
    0 bearer 1 Reply
  • bearer

    @thrawn86 said in WiFi reported error: Failed while trying to connect:

    so I assume that both the combined firmware and wifi firmware linked therein are the correct ones to use

    but on the SD card the wifi firmware needs to be called just DuetWifiServer.bin not DuetWiFiServer-1.23.bin which is normally handled by the web interface automagically.

    still, odds are DuetWifiServer.bin on the SD card is version 1.23 as that is what the running wifi modue is reporting.

    0 thrawn86 1 Reply
  • thrawn86

    @bearer

    YAT is the only way I have to talk to the board right now since I can't connect to DWC, so firmware is done and renamed manually.

    Ultimately I just want to figure out if I need to send this board back or not, updating to the correct firmware has never been this difficult.

    0
  • dc42
    administrators

    If M122 reports that the WiFi firmware version is 1.23 then it has evidently been installed correctly. I think the WiFi module may be faulty and should be replaced.

    0 thrawn86 1 Reply
  • thrawn86

    @dc42

    unfortunately the replacement from filastruder has an identical issue

    M552 S0
ok
WiFi module started
M587 S"***" P"***"
ok
M552 S1
ok

...

WiFi reported error: Failed while trying to connect to ***
WiFi module is idle
M552
WiFi module is changing mode
ok
WiFi reported error: Failed while trying to connect to ***
WiFi module is idle
M552
WiFi module is changing mode
ok
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85T0-6JTD2-3S46Q-1UTZP
Used output buffers: 1 of 24 (9 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93340 of which 164 recycled
Exception stack ram used: 256
Never used ram: 11632
Tasks: NETWORK(ready,1268) HEAT(blocked,916) MAIN(running,3808) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:08:27 ago, cause: power up
Last software reset details not available
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 28.0, current 32.6, max 32.7
Supply voltage: min 1.7, current 1.7, max 1.8, 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 1006782636
Slowest loop: 100.14ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== 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.26ms; 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.23
WiFi MAC address bc:dd:c2:2d:5e:3e
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 27224
Socket states: 0 0 0 0 0 0 0 0
ok
WiFi reported error: Failed while trying to connect to ***
WiFi module is idle

    at this point I have done literally nothing but open the box, connect the antenna and perform the steps described in : https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7 , sans firmware update. 2.03 was what I was running on my first board connected to the same network, before the sd card slot died.

    0
  • thrawn86

    in addition, subsequent attempts (restarting, forgetting and re-adding network, creating a new SSID and connecting to that instead) have all yielded the same variety of wifi error messages including:

    -Error retrieving WiFi status message: bad reply format version

    Error retrieving WiFi status message: SPI timeout

    Failed to change WiFi mode (code -7)
    0 bearer 1 Reply
  • bearer

    @thrawn86 said in WiFi reported error: Failed while trying to connect:

    -Error retrieving WiFi status message: bad reply format version

    normally fixed by (from YAT etc)

    M552 S-1 ;to disable the wifi module
M552 S0 ;to disable networking/idle wifi
G4 S1 ;wait a second
M587 S"" P"" ; insert ssid and passphrase to add wifi
M552 S1 ;to enable networking

    but to try and get some more info on the other issues i'd run

    M588 S"*"; forget all previous access point info

    then power down, remove the SD card and power it back up without the SD card. connect to usb/YAT and run

    M111 P14 S1 ;to enable wifi debug
M552 S-1 ;to disable the wifi module
M552 S0 ;to disable networking/idle wifi
G4 S1 ;wait a second
M587 S"" P"" ; insert ssid and passphrase to add wifi
M552 S1 ;to enable networking

    (don't need to type ; and what comes after, but its safe to copy/paste as is)

    edit: unclear - you installed RRF 2.03 but wifi 1.23 was on there already?

    0 thrawn86 1 Reply
Log in to reply
 
Unless otherwise noted, all forum content is licensed under CC-BY-SA