Please help: Duet Wifi stuck on Wifi Idle, No Networks, etc
-
@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!
