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

    Wifi Module remains idle error

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    4
    14
    572
    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.
    • AndrewStainesundefined
      AndrewStaines @jay_s_uk
      last edited by

      @jay_s_uk
      I have updated the firmware but still the error is present.

      m997 s0
      Shutting down USB interface to update main firmware. Try reconnecting after 30 seconds.<LF>
      m999
      m115
      FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet 3 MB6HC v1.02 or later FIRMWARE_DATE: 2023-07-21 14:11:38<LF>ok<LF>
      m552 i1
      WiFi module is disabled<LF>ok<LF>
      m552 i1 s0
      ok<LF>WiFi module started<LF>WiFi module started<LF>
      M587 S"GravityeX" P"123456789"
      ok<LF>
      M552 I1 S1
      ok<LF>Error: WiFi module reported: no known networks found<LF>WiFi module is idle<LF>
      
      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @AndrewStaines
        last edited by

        @AndrewStaines can you check if the wifi details have been saved using M587?
        usually when it says no known networks found, that means that the wifi details have been entered incorrectly or you are trying to connect to a 5GHz network as the ESP32 only supports 2.4GHz

        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

        AndrewStainesundefined 1 Reply Last reply Reply Quote 0
        • AndrewStainesundefined
          AndrewStaines @jay_s_uk
          last edited by

          @jay_s_uk
          Here is the output of M587,

          M552 I1 S0
          ok<LF>WiFi module started<LF>WiFi module started<LF>
          M587 S"GravityeX" P"123456789"
          ok<LF>
          M587
          Remembered networks:<LF>GravityeX IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0<LF>ok<LF>
          
          droftartsundefined 1 Reply Last reply Reply Quote 0
          • droftartsundefined
            droftarts administrators @AndrewStaines
            last edited by

            @AndrewStaines Have you connected the aerial to the WiFi module? Is your access point/router capable of 2.4GHz signal (usually this can be turned on)? How far from the router is the Duet?
            Can you send M122 and post the full output, so I can see which version of the WiFi firmware is installed? To make the YAT output more readable, please can you set the line endings correctly, see https://docs.duet3d.com/en/User_manual/Troubleshooting/Terminal_Emulators#setting-line-endings-in-yat

            Ian

            Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

            AndrewStainesundefined 1 Reply Last reply Reply Quote 0
            • AndrewStainesundefined
              AndrewStaines @droftarts
              last edited by

              @droftarts
              Output of M122 command

              M122<CR>
              === Diagnostics ===
              RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.02 or later (standalone mode)
              Board ID: 0JD4M-958L1-M24T8-6JTDG-3S46R-11V9X
              Used output buffers: 1 of 40 (10 max)
              === RTOS ===
              Static ram: 153252
              Dynamic ram: 97088 of which 0 recycled
              Never used RAM 100332, free system stack 190 words
              Tasks: NETWORK(ready,40.8%,505) ETHERNET(notifyWait,0.0%,661) HEAT(notifyWait,0.0%,373) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,344) TMC(notifyWait,0.0%,104) MAIN(running,58.9%,1126) IDLE(ready,0.2%,30), total 100.0%
              Owned mutexes: USB(MAIN)
              === Platform ===
              Last reset 00:00:47 ago, cause: software
              Last software reset time unknown, reason: User, GCodes spinning, available RAM 100332, slot 0
              Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00432000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
              Error status: 0x00
              Aux0 errors 0,0,0
              Step timer max interval 131
              MCU temperature: min 42.4, current 42.8, max 42.9
              Supply voltage: min 0.2, current 0.3, max 0.3, under voltage events: 0, over voltage events: 0, power good: no
              12V rail voltage: min 0.1, current 0.2, max 0.2, under voltage events: 0
              Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
              Events: 0 queued, 0 completed
              Driver 0: ok, SG min 0, mspos 0, reads 0, writes 0 timeouts 0
              Driver 1: ok, SG min 0, mspos 0, reads 0, writes 0 timeouts 0
              Driver 2: ok, SG min 0, mspos 0, reads 0, writes 0 timeouts 0
              Driver 3: ok, SG min 0, mspos 0, reads 0, writes 0 timeouts 0
              Driver 4: ok, SG min 0, mspos 0, reads 0, writes 0 timeouts 0
              Driver 5: ok, SG min 0, mspos 0, reads 0, writes 0 timeouts 0
              Date/time: 1970-01-01 00:00:00
              Slowest loop: 5.84ms; fastest: 0.05ms
              === Storage ===
              Free file entries: 10
              SD card 0 detected, interface speed: 25.0MBytes/sec
              SD card longest read time 2.2ms, write time 0.0ms, max retries 0
              === Move ===
              DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
              === MainDDARing ===
              Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
              === AuxDDARing ===
              Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
              === Heat ===
              Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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
              SBC is idle in state(s) 0
              Daemon is idle in state(s) 0
              Aux2 is idle in state(s) 0
              Autopause is idle in state(s) 0
              Code queue is empty
              === CAN ===
              Messages queued 236, received 0, lost 0, boc 0
              Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 236/0/0
              Tx timeouts 0,0,235,0,0,0 last cancelled message type 30 dest 127
              === Network ===
              Slowest loop: 0.21ms; fastest: 0.03ms
              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
              HTTP sessions: 0 of 8
              = Ethernet =
              State: establishingLink
              Error counts: 0 0 0 0 0 0
              Socket states: 0 0 0 0 0 0 0 0
              = WiFi =
              Interface state: disabled
              Module is disabled
              Failed messages: pending 0, notready 0, noresp 0
              Socket states: 0 0 0 0 0 0 0 0
              === Multicast handler ===
              Responder is inactive, messages received 0, responses 0
              ok
              
              

              I have not used any router, this is the connection of my setup.

              connection.jpg

              droftartsundefined 1 Reply Last reply Reply Quote 0
              • AndrewStainesundefined AndrewStaines marked this topic as a question
              • droftartsundefined
                droftarts administrators @AndrewStaines
                last edited by

                @AndrewStaines Thanks, but I need the M122 report when the WiFi is enabled. You are trying to connect to a WiFi SSID named "GravityeX", it is that that you need to check works with 2.4GHz WiFi.

                Ian

                Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                AndrewStainesundefined 1 Reply Last reply Reply Quote 0
                • AndrewStainesundefined
                  AndrewStaines @droftarts
                  last edited by

                  @droftarts
                  My laptop supports 2.4GHz networks and here is the M122 output when wifi is enabled

                  M122
                  === Diagnostics ===
                  RepRapFirmware for Duet 3 MB6HC version 3.5.0-rc.1 (2023-08-31 16:19:24) running on Duet 3 MB6HC v1.02 or later (standalone mode)
                  Board ID: 0JD4M-958L1-M24T8-6JTDG-3S46R-11V9X
                  Used output buffers: 1 of 40 (3 max)
                  === RTOS ===
                  Static ram: 154852
                  Dynamic ram: 120156 of which 208 recycled
                  Never used RAM 70776, free system stack 191 words
                  Tasks: NETWORK(1,ready,34.1%,332) ETHERNET(5,nWait,0.0%,662) HEAT(3,nWait,0.0%,369) Move(4,nWait,0.0%,340) CanReceiv(6,nWait,0.0%,941) CanSender(5,nWait,0.0%,335) CanClock(7,delaying,0.0%,344) TMC(4,nWait,0.0%,71) MAIN(1,running,65.9%,444) IDLE(0,ready,0.0%,30), total 100.0%
                  Owned mutexes: USB(MAIN)
                  === Platform ===
                  Last reset 00:04:40 ago, cause: software
                  Last software reset time unknown, reason: User, Gcodes spinning, available RAM 68016, slot 2
                  Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
                  Error status: 0x00
                  Aux0 errors 0,0,0
                  MCU temperature: min 41.2, current 42.2, max 42.7
                  Supply voltage: min 0.2, current 0.2, max 0.3, under voltage events: 0, over voltage events: 0, power good: no
                  12V rail voltage: min 0.1, current 0.2, max 0.2, under voltage events: 0
                  Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                  Events: 0 queued, 0 completed
                  Driver 0: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
                  Driver 1: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
                  Driver 2: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
                  Driver 3: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
                  Driver 4: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
                  Driver 5: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
                  Date/time: 1970-01-01 00:00:00
                  Slowest loop: 5939.73ms; fastest: 0.07ms
                  === Storage ===
                  Free file entries: 20
                  SD card 0 detected, interface speed: 25.0MBytes/sec
                  SD card longest read time 2.4ms, write time 0.0ms, max retries 0
                  === Move ===
                  DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
                  no step interrupt scheduled
                  Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
                  === DDARing 0 ===
                  Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                  === DDARing 1 ===
                  Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                  === Heat ===
                  Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
                  === GCodes ===
                  Movement locks held by null, 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
                  SBC is idle in state(s) 0
                  Daemon is idle in state(s) 0
                  Aux2 is idle in state(s) 0
                  Autopause is idle in state(s) 0
                  File2 is idle in state(s) 0
                  Queue2 is idle in state(s) 0
                  Q0 segments left 0, axes/extruders owned 0x0000000
                  Code queue 0 is empty
                  Q1 segments left 0, axes/extruders owned 0x0000000
                  Code queue 1 is empty
                  === CAN ===
                  Messages queued 1405, received 0, lost 0, boc 0
                  Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 1405/0/0
                  Tx timeouts 0,0,1404,0,0,0 last cancelled message type 30 dest 127
                  === Network ===
                  Slowest loop: 0.45ms; fastest: 0.03ms
                  Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                  HTTP sessions: 0 of 8
                  = Ethernet =
                  Interface state: establishingLink
                  Error counts: 0 0 0 0 0 0
                  Socket states: 0 0 0 0 0 0 0 0
                  === WiFi ===
                  Interface state: changingMode
                  Module is idle
                  Failed messages: pending 0, notrdy 0, noresp 0
                  Failed to get WiFi status
                  Socket states: 0 0 0 0 0 0 0 0
                  === Multicast handler ===
                  Responder is inactive, messages received 0, responses 0
                  ok
                  

                  Also I tried assigning IP, Gateway IP, Netmask manually,

                  M552 I1 S-1
                  WiFi module stopped
                  ok
                  M552 I1
                  WiFi module is disabled
                  ok
                  M552 I1 S0
                  ok
                  WiFi module started
                  M587 S"GravityeX" P"123456789" I192.168.1.20 J192.168.1.254 K255.255.255.0
                  ok
                  M587
                  Remembered networks:
                  GravityeX IP=192.168.1.20 GW=192.168.1.254 NM=255.255.255.0
                  ok
                  M552 I1 S1
                  ok
                  Error: WiFi module reported: no known networks found
                  WiFi module is idle
                  M552 I1 S-1
                  WiFi module stopped
                  ok
                  M552 I1 S0
                  ok
                  WiFi module started
                  M552 I1 S1
                  ok
                  Error: WiFi module reported: no known networks found
                  WiFi module is idle
                  
                  droftartsundefined fcwiltundefined 2 Replies Last reply Reply Quote 0
                  • droftartsundefined
                    droftarts administrators @AndrewStaines
                    last edited by droftarts

                    @AndrewStaines
                    For some reason the WiFi reports it is changingMode, and the WiFi status was not retrieved, so I don't know what version of the WiFi firmware you have installed. Make sure the WiFi module is in idle mode before sending M122, ie after sending M552 I1 S0. My Duet 3 Mini 5+ WiFi reports the WiFi section of M122 as:

                    === WiFi ===
                    Interface state: active
                    Module is connected to access point 
                    Failed messages: pending 0, notrdy 0, noresp 0
                    Firmware version 2.1beta4
                    MAC address f4:cf:a2:6f:be:62
                    Module reset reason: Power up, Vcc 3.39, flash size 2097152, free heap 39632
                    WiFi IP address 192.168.1.182
                    Signal strength -66dBm, channel 6, mode 802.11n, reconnections 0
                    Clock register 00002001
                    Socket states: 0 0 0 0 0 0 0 0
                    

                    Are you trying to connect the Duet to your laptop's WiFi, and running the laptop as an access point? Check the network name, password and band (click Edit to set the band) are set correctly in Mobile hotspot (assuming Windows). I would tend to not force the IP address, gateway and mask; the access point should do this for the Duet. You will need to delete the existing 'Remembered network' if you want to set up a new one, as it will default to trying to connect on the first, so send M588 S"*" and then add the SSID and password again with M587.

                    You can test if the WiFi sees any WiFi network by getting it to do a scan, as you are on RRF 3.5.0-rc.1. Enable the WiFi with M552 I1 S0, then send:
                    M587.1
                    wait 10 to 15 seconds for it to perform a scan, then send
                    M587.2
                    It should report the WiFi networks it can find, for example this is mine, :

                    24/11/2023, 13:12:59 	M587.1
                    24/11/2023, 13:13:08 	Connection interrupted, attempting to reconnect...
                    HTTP request timed out
                    24/11/2023, 13:13:09 	Connection established
                    24/11/2023, 13:13:29 	M587.2
                    Network Scan Results:
                    ssid=DIRECT-87-HP ENVY 5540 series chan=6 rssi=-37 phymode=n auth=WPA2-Personal mac=XX:XX:XX:XX:XX:XX
                    ssid=BT-3HATHX chan=6 rssi=-66 phymode=n auth=WPA2-Personal mac=XX:XX:XX:XX:XX:XX
                    ssid=EE WiFi chan=6 rssi=-67 phymode=n auth=Open mac=XX:XX:XX:XX:XX:XX
                    ssid= chan=6 rssi=-67 phymode=n auth=WPA2-Personal mac=XX:XX:XX:XX:XX:XX
                    ssid=BT-ZJCJ3G chan=11 rssi=-78 phymode=n auth=WPA2-Personal mac=XX:XX:XX:XX:XX:XX
                    ssid=EE WiFi chan=11 rssi=-78 phymode=n auth=Open mac=XX:XX:XX:XX:XX:XX
                    ssid=EE WiFi chan=1 rssi=-80 phymode=n auth=Open mac=XX:XX:XX:XX:XX:XX
                    ssid= chan=1 rssi=-80 phymode=n auth=WPA2-Personal mac=XX:XX:XX:XX:XX:XX
                    ssid= chan=11 rssi=-81 phymode=n auth=WPA2-Personal mac=XX:XX:XX:XX:XX:XX
                    ssid=Tenda chan=6 rssi=-90 phymode=n auth=WPA/WPA2-Personal mac=XX:XX:XX:XX:XX:XX
                    ssid=EE WiFi chan=6 rssi=-91 phymode=n auth=Open mac=XX:XX:XX:XX:XX:XX
                    ssid=TALKTALK73BA90 chan=6 rssi=-91 phymode=n auth=WPA2-Personal mac=XX:XX:XX:XX:XX:XX
                    

                    (I have obscured the mac address)

                    If it reports any error message for any of the above, please post it.

                    Ian

                    Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                    1 Reply Last reply Reply Quote 0
                    • fcwiltundefined
                      fcwilt @AndrewStaines
                      last edited by

                      @AndrewStaines

                      If you don't have a router what does your laptop connect to? Something must be serving as a WiFi Access Point.

                      Thanks.

                      Frederick

                      Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                      AndrewStainesundefined 1 Reply Last reply Reply Quote 0
                      • AndrewStainesundefined
                        AndrewStaines @fcwilt
                        last edited by

                        @fcwilt
                        Thank You for the clarification. Now I get it. I have tried it via router and now it works fine.

                        1 Reply Last reply Reply Quote 0
                        • AndrewStainesundefined AndrewStaines has marked this topic as solved
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA