Wifi module is idle

Wifi reported error no known networks found wifi module is idle

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

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).

Источник

WiFi reported error: no known networks found

Hello, Just got my Duet 2 wifi in the mail today and an error is coming up when trying to connect it to internet. The error says «WiFi reported error: no known networks found» adn on the next line says «WiFi module is idle». I’m using YAT and followed all instructions. Please help.

• WiFi —
  Network state is changing mode
  WiFi module is idle
  Failed messages: pending 0, notready 0, noresp 6
  Failed to get WiFi status
  Socket states: 0 0 0 0 0 0 0 0
  ok
  Error retrieving WiFi status message: bad reply format version
  WiFi module is idle
  WiFi reported error: no known networks found
  WiFi module is idle

@garrett-good With that WiFi error, it looks like the WiFi firmware may be out of step with the main firmware. Though this, in itself, is pretty old too! I suggest you update to the latest RepRapFirmware 2 and update the WiFi firmware as well. See https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_1 I have to ask. is this a genuine Duet? We haven’t shipped boards with v2.02(RTOS) of the firmware for a looooong time. Where did you buy it? Ian

Cartesian bed-slinger with Duet 3 Mini 5+ WiFi : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 2 Wifi (in progress)

@droftarts I am having the same problem, I just started trying to use a board I bought from Filastruder 2 years ago. It is a v1.02 that had 1.81 loaded onto it. I will try the link you posted for fallback procedure #1 and let you know what happens.

Источник

Wifi always idle reported by terminal

On my Duet Wifi, I was attempting to reconfigure my wifi settings using the terminal, and now it never turns on blue anymore (except a little flash when I power up) When I try to run 552 S0 or S1, my terminal comes back with «»WiFi module is idle» I have also tried running my original scripts for setting and forgetting the network (exactly same as I ran to initially setup the duet) and again I get «Idle» back from the terminal.

It looks as though the wifi is not turning on at all. What are possible causes for no blue indicator when the Duet Wifi is fully powered up? Can that happen just because of a configuration problem?

M552 S0 puts the WiFi module in the Idle state, so the «WiFi module is idle» message is expected in that case. M552 S1 should scan for known networks and try to connect to the strongest one. If it fails then it should produce an error message before it reports «WiFi module is idle». You could try re-installing the DuetWiFiFirmware file. In another thread I announced the availability of version 1.22beta.

Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com

@henrydara Just to make sure all of the basics are occurring as expected: Does M587 report the expected network? Did you delete existing networks with M588 S»*», then re-enter your expected network using M587 S“mynetwork” P”mynetworkpassword” (making sure that the case of each is correct)? Note that attempts to overwrite the network setting with M587 doesn’t seem to work unless you delete the old one first — but it sounds like you did. When you enter M552 S1, the blue led should flash for a few seconds as it tries to connect. Then you should get a message back either saying that it is connected successfully with the IP address it obtained from DHCP reported, or you should get back a message saying that it failed to connect. Are you getting either message?

@dc42 I got it, thanks for the help. Im my own worst enemy sometimes. Thankfully you’ve been there to catch me.

Источник