Can't connect to wifi after firmware update

dc42 · 8 Jan 2018, 07:29

Some suggestions:

1. Which DuetWiFiServer.bin are you using: 1.20 or 1.20+1 ? Try the other one.

2. Another user reported yesterday that he solved his connection issues by using a static IP address in the M587 command.

3. Connect a PC via USB, send M111 S1 P14 to enable WiFi debugging, and report here what debugging messages are shown when the disconnection occur.

briangilbert · 8 Jan 2018, 08:16

@dc42

#2 alone didn't do it, but reverting back to 1.20 of DuetWiFiServer.bin seems to have resolved it

Thanks.

Arty · 1 Aug 2018, 11:29

Hello. I'm new owner of duet wifi and also was experiencing problems with connecting. My wifiserver version 1.20 (also I had problems with preinstalled 1.19). In the beginning it connected but I've had numerous connection losts and AJAX webcontrol errors. So I've tried updating it to 1.20 version. It worked some time but after that it stopped connecting at all. Changing channels (btw in my flat it's totally useless because ALL 2.4ghz channels are overloaded, so I mainly use 5ghz wifi for my devices), wifi modes, I've tried everything - even using dedicated asus rt-n66u router solely for duet, but it wasn't any help.
And when I was totally frustrated I've tried to connect to my neighbour's open (no password) DIR-320 router (d-link I presume).
And it connected with no problems! Webcontrol was loading just instant, no AJAX errors at all.
So today I want to try creating AP with no password on my routers and see how it goes with duet. (Also want to try static IP address).

upd:

static address - nope, it didn't help. It connected and got IP but I couldn't open webcontrol, it starts loading but very slow.
Created AP with no password - connected with no problems.

dc42 · 8 Jan 2018, 12:08

Interesting, I wasn't aware that enabling/disabling WPA2 could make a difference. Have you tried DuetWiFiserver 1.20+1 yet? It's at https://github.com/dc42/RepRapFirmware/blob/dev/EdgeRelease/DuetWiFiServer.bin (follow the link, then press Download).

briangilbert · 9 Jan 2018, 07:10

So although I thought reverting to 1.20 duetwifiserver resolved the issue I am still getting DWC disconnects, just far less often now.

Gaza07 · 10 Jan 2018, 19:02

I have had a lot of the same issues using the v1.20+1 I used to get the odd issue with v1.20 but no where near as much as v1.20+1 I will revert back to v1.20 for now

Arty · 16 Jan 2018, 21:14

@dc42:

Interesting, I wasn't aware that enabling/disabling WPA2 could make a difference. Have you tried DuetWiFiserver 1.20+1 yet? It's at https://github.com/dc42/RepRapFirmware/blob/dev/EdgeRelease/DuetWiFiServer.bin (follow the link, then press Download).

Sorry no help. I'm still using with AP without password (set my AP to use MAC address filters because of security). Sometimes I experience rare disconnects.
AP with WPA2 password just don't work in my case. Firmware now - 1.21RC0 and 1.20+1 wifi.

briangilbert · 31 Jan 2018, 08:19

Just reporting back that after updating my network gear to Ubiquiti Unifi kit everything is working properly again.

dc42 · 31 Jan 2018, 10:22

Brian, what make/model of router were you using before when you had the disconnections?

Dougal1957 · 31 Jan 2018, 10:29

David just for info My Wifi wont connect at all to my Netgeear D6400 router but works to the cheap TP-Link travel router think it is a TL-720N or whatever I am due to change provider next week so will see what there Router is like I will report Back later.

Doug

MortarArt · 9 Dec 2018, 07:07

I'm getting the same error now, since replacing my power supply. When I turn the Duet on, it either reports no wifi networks, or that it "failed while trying to connect" to the one it previously used without issue.

So back to troubleshooting!

17:04:00.737 : serial: M552 S1
17:04:00.742 : WiFi: mode : sta(5c:cf:7f:76:73:38)
17:04:00.743 : WiFi: add if0
17:04:02.931 : WiFi: scandone
17:04:02.939 : WiFi: ../src/SocketServer.cpp(353): found network BLANK1
17:04:02.945 : WiFi: ../src/SocketServer.cpp(353): found network BLANK2
17:04:02.954 : WiFi: ../src/SocketServer.cpp(353): found network BLANK3
17:04:02.961 : WiFi: ../src/SocketServer.cpp(353): found network BLANK4
17:04:02.969 : WiFi: ../src/SocketServer.cpp(353): found network ETC
17:04:03.015 : WiFi: sleep enable,type: 2
17:04:03.578 : N13 M10521
17:04:05.206 : WiFi: scandone
17:04:05.208 : WiFi: state: 0 -> 2 (b0)
17:04:06.209 : WiFi: state: 2 -> 0 (2)
17:04:06.210 : WiFi: reconnect
17:04:06.645 : N14 M10518
17:04:08.401 : WiFi: scandone
17:04:08.403 : WiFi: state: 0 -> 2 (b0)
17:04:09.402 : WiFi: state: 2 -> 0 (2)
17:04:09.403 : WiFi: reconnect
17:04:09.707 : N15 M105*19
17:04:11.593 : WiFi: scandone
17:04:11.596 : WiFi: state: 0 -> 2 (b0)
17:04:12.595 : WiFi: state: 2 -> 0 (2)
17:04:12.596 : WiFi: reconnect
17:04:12.598 : ESP reported status change
17:04:12.598 : WiFi reported error: Failed while trying to connect to BLANK3
17:04:12.598 : WiFi module is idle
17:04:12.598 : WiFi: scandone
17:04:12.598 : WiFi: del if0
17:04:12.599 : WiFi: usl
17:04:12.601 : WiFi: mode : null

MortarArt · 9 Dec 2018, 07:32

Not too sure if it's relevant, but I'm getting reset buffer blocks via the COM port now. Not sure if that was happening previously.

Firmware version 2.02beta1(RT0S) - date 2018-08-12b5
Duet Wifi 1.02 or later

Using M588 S"*" to forgot the existing network, allowed me to use M587 S"network" P"password" to connect (M552 S1) to a new network. I'll check now if I can still connect to the old one.

Final edit; problem solved by deleting the network and reconnecting. No idea why.