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

      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