Please help: Duet Wifi stuck on Wifi Idle, No Networks, etc
-
I did just discover some new-firmware instructions from seemecnc; I will have to allocate a big chunk of time to trying this I think. EDIT: Sigh, have to go buy an SD-to-USB thing.
-
@ddxdesign you need to increase the end of line settings to get the full output.
If you have a look at that link I posted a few pages up, it tells you all the settings you need to change in YAT -
@jay_s_uk Well, did that, but now when I paste in the true full output, I can't post it - forum gives me a Flagged As Spam error...
-
@ddxdesign said in Please help: Duet Wifi stuck on Wifi Idle, No Networks, etc:
@jay_s_uk Well, did that, but now when I paste in the true full output, I can't post it - forum gives me a Flagged As Spam error...
please try it again now
-
@siam Alrighty, how's this?
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7JKF4-3SN6P-TU97R
Used output buffers: 1 of 20 (4 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98820 of which 0 recycled
Exception stack ram used: 424
Never used ram: 6304
Tasks: NETWORK(ready,1260) HEAT(suspended,1232) MAIN(running,3788) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:44:43 ago, cause: software
Last software reset time unknown, reason: Heat task stuck, spinning module FilamentSensors, available RAM 6024 bytes (slot 0)
Software reset code 0x00ad HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f80f BFAR 0xe000ed38 SP 0x20004a54 Task 0x4e49414d
Stack: 0044bcc7 004495f2 21000000 00000000 00000000 00000000 00000000 3e178897 3e1cd04f 41800000 3e3a4b83 3e63a760 3e92581f 3ccd4e65 3eccdf1a 3e221bcd 3f800000 c0a00000 00000000 60000010 e000ed04 20004ad0 00000000
Error status: 1
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 40.4, current 40.9, max 41.8
Supply voltage: min 13.0, current 13.1, max 13.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 1.21ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 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: 1.30ms; 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 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok
- WiFi -
-
BTW network/wifi is disabled now just cause I stopped the module so it wouldn't flood the screen with errors any more
-
@ddxdesign ok, that's a good first step.
Can you try enabling the WiFi module using M552 S0 and then post the output of just the WiFi section from M122? -
@jay_s_uk OK here you go:
- WiFi -
Network state is running
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.22
WiFi MAC address f4:cf:a2:66:97:85
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 33632
Socket states: 0 0 0 0 0 0 0 0
ok
EDIT: when I run M587 now it looks like at least it remembers my current network as part of the known networks list, but it won't connect or anything still.
- WiFi -
-
@ddxdesign can you try this WiFi firmware here?
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/DuetWiFiServer-1.23.bin
I believe it should work ok.
You will need to place it in the sys folder of the SD card.
Take a backup of the one already there (in fact, backup all the SD card contents just in case).
Then put the SD card back in, power up the board and using YAT, send M997 S1.
Once flashed send M552 S0
Then M558 S"*"
Then M587... With your WiFi details.
Hopefully that sends ok, then use M552 S1 to activate the WiFi -
@jay_s_uk Yeah I know SeeMe has instructions for updating the RR FW itself but I couldn't see mention of the Wifi FW. Either way I will have to go out and buy an SD card reader with a USB plug. My new laptop is supposed to be fancy (for gaming) but has no SD port...
-
@ddxdesign thats a shame.
well when you are ready or need any more help just drop a message here.
If they give you instructions for upgrading the firmware to 2.05.1 then go through with that too. -
@jay_s_uk the instructions I found as of August of this year are to take the RRFW up to 3.2.2 but I just went through them again and nothing about the wifi FW. So hopefully the two won't clash and I can do it all.
-
@ddxdesign ah, if going to 3.2.2 then you will need 1.25 of the wifi firmware which can be found here https://github.com/Duet3D/DuetWiFiSocketServer/releases/download/1.25/DuetWiFiServer.bin
I'm assuming they provide new config files etc? as a fair amount of syntax changed between RRF2 and RRF3 -
@jay_s_uk Yeah looks like there are entire new cards' worth of files and directories to step it from 2.02 through two intermediate stages and then to 3.2.2
-
@ddxdesign thats great. (don't make the move to 3.3.0 just yet as there were changes to the spindle code).
But I would feel comfortable with you going from 2.02 to 3.2.2. -
@jay_s_uk OK, I will get a card reader this afternoon - so, are there instructions for the 1.25 wifi FW? And should I do that after I take the RRFW up to 322?
-
@ddxdesign the order doesn't matter.
And just pop it in sys replacing duetwifiserver.bin that's already there and run M997 S1 -
@jay_s_uk Doh, I just realized it would likely be the same instructions as you sent for 1.23 - heh.
-
@jay_s_uk Well, I just spent an hour sweating in my printer room going through EVERYTHING - it's all up at 3.2.2 now, wifi is up at 1.25....
And no dice. Exact same thing again. It just fails to get on the network: every M552 S1 yields an endless stream of "no known networks found, wifi module is idle." I even tried the thing I had to do once where I had to escape all the lowercase letters in the password with a single ' before each.
EDIT I GOT IT. I saw something in the docs about the Duet only working on 2.4ghz. Now, it's been working for 5 months since I moved here on my router where both bands were on the same SSID. I forcibly split the bands to have their own names, logged specifically into the 2.4ghz one, et voila.
UGH that was a heck of a dance.
-
@ddxdesign Great to hear you got there in the end!
