Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    WiFi reported error: network scan failed

    Scheduled Pinned Locked Moved
    General Discussion
    4
    13
    1.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • paralepsisundefined
      paralepsis
      last edited by

      I've got a Duet Wifi (1.02+) running RRF 3.3.2. This printer has been running the same config.g and connecting to the same network for weeks. The router has not been repositioned (it's about 8 feet away) and there's nothing else (new) around it that ought to be interfering with the WiFi.

      The Duet is on a UPS and active cooled. The room is 65 degrees or so. It had been printing off and on for maybe a week before this started. The printer is semi-enclosed with PVA foam board.

      Some time last night I lost connectivity with the Duet. I have a Panel Due, so I was able to observe the status. I rebooted and got something like this:

      WiFi module is idle
      WiFi reported error: no known networks found
      WiFi module is idle
      WiFi reported error: Timed out while trying to connect to <correctnetworkname>
      WiFi module is idle
      WiFi reported error: Timed out while trying to connect to <correctnetworkname>
      WiFi module is idle
      Error retrieving WiFi status message: bad reply format version
      

      So that last bit seemed weird, and searching indicated maybe I needed to reflash the firmware. So, I re-grabbed the 3.2.2 zip file, unpacked, grabbed DuetWiFiServer.bin, copied on the SD card, and reflashed. Panel indicated success.

      Now I'm getting streams of

      WiFi reported error: network scan failed
      

      The router is working; there's a Pi in roughly the same location serving video that I can still connect to.

      Help? Thanks!

      Rob

      Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        What does M122 show for the wifi section?

        Can you try cycling through the wifi states?

        M552 S-1
        M552 S0
        M552 S1
        M552 S2

        Snnn 0 = disable networking, 1 = enable networking as a client, 2 = enable networking as an access point , -1 = disable WiFi module

        What does the status LED on the module itself show?

        Try reflashing again?

        If that still doesn't work, try testing it in access point mode and see if that works.

        https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M589_Configure_access_point_parameters

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • paralepsisundefined
          paralepsis
          last edited by

          Thanks for responding! Access point mode seems to have issues. I've tried a second reflash without luck. Details below. Thoughts?

          Lights

          You asked about lights. I believe I was getting a blinking blue light on the WiFi before the March 14th reflash, now no blinking (either before or after 2nd reflash).

          Status after boot (prior to 2nd reflash)

          Still in this state, repeating every couple of seconds:

          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
          

          Diagnostics (complete, prior to 2nd reflash)

          >> M122
          
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
          Board ID: 08DAM-9K9K2-NGNS0-7JKDJ-3SJ6K-T70BL
          Used output buffers: 5 of 24 (13 max)
          === RTOS ===
          Static ram: 23460
          Dynamic ram: 73440 of which 24 recycled
          Never used RAM 15156, free system stack 187 words
          Tasks: NETWORK(ready,322) HEAT(blocked,294) MAIN(running,451) IDLE(ready,20)
          Owned mutexes: USB(MAIN)
          === Platform ===
          Last reset 00:01:23 ago, cause: power up
          Last software reset details not available
          Error status: 0x00
          Aux0 errors 0,0,0
          MCU temperature: min 20.1, current 25.9, max 26.1
          Supply voltage: min 24.1, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
          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: 1970-01-01 00:00:00
          Cache data hit count 100163503
          Slowest loop: 6.92ms; fastest: 0.22ms
          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 2.7ms, 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 = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
          Heater 1 is on, I-accum = 0.0
          === 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 ready with "M122" 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: 1.48ms; fastest: 0.00ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
          HTTP sessions: 0 of 8
          - WiFi -
          Network state is changingMode
          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
          === Filament sensors ===
          Extruder 0 sensor: ok
          ok
          

          Cycling through WiFi states

          >> M552 S-1
          
          Error retrieving WiFi status message: SPI timeout
          WiFi module is idle
          Failed to change WiFi mode: SPI timeout
          ok
          
          >> M552 S-1
          
          ok
          
          >> M552 S0
          
          ok
          WiFi module started
          
          >> 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
          
          >> M552 S0
          
          ok
          WiFi reported error: no known networks found
          WiFi module is idle
          
          ok
          WiFi module is providing access point 314cf6c12bfd05e849455c6w4q2s, IP address 65.84.84.51
          Error retrieving WiFi status message: SPI timeout
          Error retrieving WiFi status message: SPI timeout
          Error retrieving WiFi status message: SPI timeout
          ...
          
          >> M552 S0
          
          WiFi module stopped
          ok
          

          Firmware refresh

          Following https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

          Copied all these over (overkill...):

          • Duet2_SDiap32_Maestro.bin
          • Duet2_SDiap32_WiFiEth.bin
          • Duet2CombinedFirmware.bin
          • Duet2CombinedIAP.bin
          • Duet2Firmware_SBC.bin
          • DuetWiFiServer.bin

          Q: Docs indicate four files. Did I miss one?

          ...
          WiFi module is idle
          
          >> M997 S0
          
          T:17.6 /0.0 T0:17.6 /0.0 B:18.4 /0.0
          Shutting down USB interface to update main firmware. Try reconnecting after 30 seconds.
          
          WiFi module is idle
          WiFi reported error: no known networks found
          WiFi module is idle
          ...
          
          >> M997 S1
          
          T:17.5 /0.0 T0:17.5 /0.0 B:18.4 /0.0
          WiFi reported error: no known networks found
          WiFi module is idle
          Trying to connect at 230400 baud:  success
          Erasing 4096 bytes...
          Erasing 196608 bytes...
          Uploading file...
          5% complete
          ...
          95% complete
          Upload successful
          ok
          WiFi module started
          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
          

          Diagnostics (after 2nd reflash)

          >> M122
          
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
          Board ID: 08DAM-9K9K2-NGNS0-7JKDJ-3SJ6K-T70BL
          Used output buffers: 1 of 24 (10 max)
          ...
          === Network ===
          Slowest loop: 2238.53ms; fastest: 0.00ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
          HTTP sessions: 0 of 8
          - WiFi -
          Network state is changingMode
          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: SPI timeout
          WiFi module is idle
          Failed to change WiFi mode: SPI timeout
          

          That last bit seems interesting. Otherwise status seems same as prior to first reflash (although I only flashed WiFi that time, M997 S1).

          Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

          1 Reply Last reply Reply Quote 0
          • paralepsisundefined
            paralepsis
            last edited by

            Also, just to be clear, the printer will print fine when supplied a gcode file on the SD card.

            Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

            1 Reply Last reply Reply Quote 0
            • Phaedruxundefined
              Phaedrux Moderator
              last edited by Phaedrux

              Before enabling access point mode did you configure the SSID and password, etc with M589?

              https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M589_Configure_access_point_parameters

              When and where did you purchase the Duet?

              Z-Bot CoreXY Build | Thingiverse Profile

              paralepsisundefined 1 Reply Last reply Reply Quote 0
              • paralepsisundefined
                paralepsis @Phaedrux
                last edited by

                @Phaedrux I did not configure the AP; I'll do that and report back.

                This Duet was purchased from Filastruder around April 29, 2017. Been working well this whole time, thousands of hours of prints.

                Are those SPI errors normal?

                Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

                1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator
                  last edited by

                  Let's see how AP mode goes. The SPI errors are normal in that they are a thing that can happen. But they are not ideal. It's possible that the wifi module is failing.

                  But try AP mode and try adding your SSID again.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • paralepsisundefined
                    paralepsis
                    last edited by

                    TL;DR: AP mode works ok. Console output below (inputs hand-inserted as best I can).

                    I guess this implies that something about my router or the overall environment changed. I'm going to rebuild the router (little GL-MT300a box) and also see if I can get it positioned even closer to the Duet. I'll follow up if it turns out that I cannot get it to connect after the rebuild.

                    Any other thoughts?

                    Thanks for the help in debugging!

                    Rob

                    >> M589 S"DuetWifi" P"duetwifi" I192.168.11.1
                    
                    Error: M589: Failed to configure access point parameters: WiFi module is disabled
                    
                    >> M552 S0
                    
                    ok
                    
                    >> 589 S"DuetWifi" P"duetwifi" I192.168.11.1
                    
                    ok
                    
                    >> M552 S2
                    
                    WiFi module started
                    ok
                    ok
                    WiFi module is providing access point DuetWifi, IP address 192.168.11.1
                    
                    >> M122
                    
                    === Diagnostics ===
                    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
                    Board ID: 08DAM-9K9K2-NGNS0-7JKDJ-3SJ6K-T70BL
                    Used output buffers: 1 of 24 (24 max)
                    === RTOS ===
                    Static ram: 23460
                    Dynamic ram: 73440 of which 60 recycled
                    Never used RAM 15120, free system stack 108 words
                    Tasks: NETWORK(ready,186) HEAT(blocked,294) MAIN(running,417) IDLE(ready,20)
                    Owned mutexes: USB(MAIN)
                    === Platform ===
                    Last reset 30:51:04 ago, cause: power up
                    Last software reset details not available
                    Error status: 0x0c
                    Aux0 errors 0,0,0
                    MCU temperature: min 26.9, current 28.6, max 29.3
                    Supply voltage: min 24.1, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
                    Driver 0: position 27000, standstill, SG min/max not available
                    Driver 1: position -23000, standstill, SG min/max not available
                    Driver 2: position 172437, 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-03-17 19:05:22
                    Cache data hit count 4294967295
                    Slowest loop: 99.86ms; fastest: 0.22ms
                    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 3.8ms, write time 0.0ms, max retries 0
                    === Move ===
                    DMs created 83, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
                    === MainDDARing ===
                    Scheduled moves 829277, completed moves 829277, 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 = 0 -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 ready with "M122" 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: 16.12ms; 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 providing access point 
                    Failed messages: pending 0, notready 0, noresp 0
                    WiFi firmware version 1.25
                    WiFi MAC address 5e:cf:7f:37:8f:14
                    WiFi Vcc 3.40, reset reason Turned on by main processor
                    WiFi flash size 4194304, free heap 25672
                    WiFi IP address 192.168.11.1
                    Connected clients 1
                    Clock register 00002002
                    Socket states: 0 0 0 0 0 0 0 0
                    === Filament sensors ===
                    Extruder 0 sensor: ok
                    ok
                    

                    Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

                    tylersuardundefined 1 Reply Last reply Reply Quote 0
                    • Phaedruxundefined
                      Phaedrux Moderator
                      last edited by

                      Well at least we know the wifi module is working.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • Macgyverundefined Macgyver referenced this topic
                      • tylersuardundefined
                        tylersuard @paralepsis
                        last edited by

                        @paralepsis I am having the same problem, except using the access point mode is not helping. Did you find a fix?

                        jay_s_ukundefined paralepsisundefined 2 Replies Last reply Reply Quote 0
                        • jay_s_ukundefined
                          jay_s_uk @tylersuard
                          last edited by

                          @tylersuard please start your own thread with your board info and M122 output

                          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                          1 Reply Last reply Reply Quote 0
                          • paralepsisundefined
                            paralepsis @tylersuard
                            last edited by

                            @tylersuard in my case I thought that the AP was fine, but in fact it had died.

                            Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

                            tylersuardundefined 1 Reply Last reply Reply Quote 1
                            • tylersuardundefined
                              tylersuard @paralepsis
                              last edited by

                              @paralepsis The AP died, how did you handle it? Did you get a replacement from Duet, or ...?

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Unless otherwise noted, all forum content is licensed under CC-BY-SA