"No known networks found" error



  • Hello all,

    Just unboxed my duet2 wifi. I previously had one of the copy boards, so I was all wired and ready to just plug and play.

    I open YAT, and my basic sequence was:

    M997 S0 on latest 2.05 Combined Firmware
    reset
    M997 S1 on latest 1.23 Wifi Server Firmware
    reset
    M552 S0
    M587 S"Matt Damon" P"blahblah"
    M552 S1 No known networks found

    From here, i've tried everything, forgetting known networks, erasing the board and reflashing with BOSSA 1.91, I can never get past "No known networks". My M587 does return saved networks, including the one I set up.

    Nothing out of the ordinary in my M122, as compared to the many I've compared to in the hours spent troubleshooting this issue.

    If I poke around enough I eventually get "Failed to add SSID to remembered list", "failure to reset wifi module to factory settings", "Error retrieving WiFi status message: bad reply format version", and more seemingly fatal wifi errors. From there, I can only erase the board and start over. I've done this 3 or 4 times.

    Exact same issue as:

    https://forum.duet3d.com/topic/10799/another-no-known-networks-found-error/34

    I'm thinking my board needs to be replaced, but I've been told that making this post is a pre-requisite to starting the replacement process... which is odd because my clone was replaced simply by describing my problem in an email.

    Looking for my next steps, thanks.



  • It could be a faulty wifi module, or it could be a signal quality issue, or it could be an encryption issue.

    Easiest way to check if the radio is okay is to put the Duet into access point mode imo.
    https://duet3d.dozuki.com/Wiki/Gcode#Section_M589_Configure_access_point_parameters



  • M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-917NK-F2MS4-7J1F8-3SD6R-KHT4F
    Used output buffers: 1 of 24 (1 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 92740 of which 0 recycled
    Exception stack ram used: 256
    Never used ram: 12364
    Tasks: NETWORK(ready,1876) HEAT(blocked,1232) MAIN(running,4752) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:32 ago, cause: power up
    Last software reset time unknown, reason: Heat task stuck, spinning module FilamentSensors, available RAM 11916 bytes (slot 3)
    Software reset code 0x00ad HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043380f BFAR 0xe000ed38 SP 0x20004aac Task 0x4e49414d
    Stack: 0044d941 0044d940 61000000 00000000 3fdb4e81 3edb6db7 b7b4d800 3331bb4c 40000000 3f317200 b5ddea0e 388aa908 bb35fe81 3c4192f5 3f800000 00000000 3f800000 a0000000 00000000 60000010 0044d941 00000000 ffffffff
    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 18.1, current 21.6, max 21.7
    Supply voltage: min 0.0, current 0.4, max 0.5, 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 48878098
    Slowest loop: 0.15ms; fastest: 0.05ms
    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 = -1 -1
    === 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: 0.15ms; 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 disabled
      WiFi module is disabled
      Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
      Socket states: 0 0 0 0 0 0 0 0
      ok

    M589 S"test" P"test1234" I192.168.0.1
    ok
    M552 S2
    ok
    WiFi module is providing access point test, IP address 192.168.0.1
    Error retrieving WiFi status message: bad reply format version
    WiFi module is providing access point test, IP address 192.168.0.1

    Blue light is on. The SSID "test" is being broadcast.



  • @JaredP said in "No known networks found" error:

    Blue light is on. The SSID "test" is being broadcast.

    you can connect to it and it provides dhcp and connectivity in general?



  • It gave me an IP address, 192.168.0.2.

    And yes, I can connect to it and access the printer control panel.



  • I'm guess the radio is okay then, hopefully its doable to sort out what is wrong with the firmware.


  • administrators

    Three possible reasons for "No known networks found":

    1. You have hidden the SSID in your router configuration. If you do that then you must specify the SSID you want to connect to in the M552 S1 command.

    2. You have mistyped the SSID in the M587 command. Run M587 to list known networks and check that the one in the remembered list matches exactly the one that the router is transmitting on 2.4GHz.

    3. The chosen network signal is too weak where the printer is. Move the printer into the same room as the router and try again. If that works, see https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors.



  • I read the thread as it having another Duet working under the same conditions; was I mistaken?



  • I did have a clone board working from the same location previously. It went into another machine, and I bought a genuine Duet to replace it. My SSID is not hidden. I've tried quite a few times to connect, however I'll try moving closer temporarily.

    Here is M587:

    M587
    Remembered networks:
    TNCAPF2FD81 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
    Matt Damon IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
    ok



  • Thats what I thought; could you just make sure there isn't a difference in the rrf or wifi firmware between the two boards before/after making the swap?



  • Here is my M115

    M115
    FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1
    ok

    How can I check the wifi version? I have ran M997 S1 on version 1.23, I saw the whole install progression without any issues.



  • @JaredP said in "No known networks found" error:

    How can I check the wifi version? I

    its part of the M122output, way down at the bottom.



  • Okay, I suppose it errored out in the M112 i ran earlier.
    Now that i'm in AP mode, I can see my wifi version is 1.23

    === Network ===
    Slowest loop: 8446.02ms; 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 running
      WiFi module is providing access point
      Failed messages: pending 0, notready 0, noresp 1
      WiFi firmware version 1.23
      WiFi MAC address 86:0d:8e:b3:b4:93
      WiFi Vcc 3.34, reset reason Hardware watchdog
      WiFi flash size 4194304, free heap 25616
      WiFi IP address 192.168.0.1
      Connected clients 0
      Socket states: 0 0 0 0 0 0 0 0

    So now that I know I'm on 1.23 & 2.05.1, what else can I do? I did a speed test from my phone where my printer is located and I am getting 108 mbps/18 ms, i'm positive it's not connection strength.



  • Just figured it out. Nothing wrong with the board.

    I had to reset my routing and AP configurations on my Ubiquiti network hardware due to a corruption or something, just recently. I didn't realize I had specified this time to separate my 2.4 and 5Ghz SSIDs. Now my 2.4Ghz SSID became named Matt Damon_IoT by default, while I was asking the board to try to connect to the 5Ghz exclusive SSID.

    Specifying "Matt Damon_IoT" allowed me to connect with M552 S1.

    I apologize to you guys for framing this as a duet issue, but at least this can perhaps be a new part of the questionnaire if guys pop up with this problem again, haha.



  • @JaredP said in "No known networks found" error:

    but at least this can perhaps be a new part of the questionnaire

    it would have been it you'd said you changed any thing other than the Duet; anyways this probably why the Duet replacement is "difficult" - rarely anything wrong with the board;) All that ends well and all that jazz:)


Log in to reply