Wifi not connecting

Paddy

Hi,
Full disclosure: I have a Duet Wifi 1.03 clone.

If after my disclosure you would still like to assist - this is my problem.

My board is about 1 year old. Last night I was connecting fine to DWC then this morning I couldn't.
I'm running the latest FW 3.01-beta3 and wifi 1.23.

I get the following errors randomly;
Error connecting to xxxxxx
Bad format
no known networks found.

I have re-flashed the firmware by placing it on the sdcard and running M997 S0 and M997 S1.
I also used the erase button and then used bossa to reload the firmware.

Nothing has helped.
Debug ;

m122<CR>
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-beta3 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3S4-6J1F8-3SN6L-1VNZG
Used output buffers: 1 of 24 (11 max)
=== RTOS ===
Static ram: 27988
Dynamic ram: 92792 of which 40 recycled
Exception stack ram used: 304
Never used ram: 9948
Tasks: NETWORK(ready,1272) HEAT(blocked,1240) MAIN(running,1612) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:06:13 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 9948 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
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 25.7, current 26.0, max 26.4
Supply voltage: min 24.0, current 24.1, max 24.2, 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 531601002
Slowest loop: 1.25ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
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.03ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
- WiFi -
Network state is changing mode
WiFi module is trying to connect
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address cc:50:e3:4a:b8:38
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 28264
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
ok

Phaedrux

https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors

Try this part

If unable to connect to your wireless network at boot up, try deleting all saved wifi networks with M588 S"*" (That is, using an asterix for the network name), then re-adding it with M587. For example, M587 S"networkname" P"password".
You can manually reset the wifi module if you have console access via USB, or a PanelDue. Send M552 S0, to disable networking, followed by M552 S1 to enable networking.

SIam

Have you tried to re add your network M587 ?

have you tried to reset your wlan router? and last change the W-lan Channel in your router

Paddy

Thanks for the replies.
@Phaedrux - Sorry I should have said that I had tried forgetting the save networks and then putting it back in. No joy.

@SIam - I did reboot my AP and firewall but this didn't help. I've just created a new ssid for testing but got the same results. Also no other devices are having problems.

As a test I set my mobile to be an AP and the duet wifi wouldn't connect to that either.

I was thinking it might be hardware as I was seeing

Error retrieving WiFi status message: bad reply format version

but as a final test I put the card into AP mode and this worked fine - I could connect and then reach the DWC.
Putting it back to client mode and it won't connect.

Phaedrux

Try reflashing the wifi server?

Paddy

@Phaedrux said in Wifi not connecting:

Try reflashing the wifi server?

I have reflashed the WiFi server. Didn't help

SIam

have you tried to flash the latest stable rrf version 3.0?

Phaedrux

When connected to a USB terminal, send M98 Pconfig.g and see if you're getting any errors on execution.

Paddy

I really want to thanks both of you guys for taking the time to help.

@Phaedrux M98 Pconfig.g returned no errors.

@SIam I flashed fw 3.0 but still got the error. I reflashed wifiserver 1.23 but still couldn't connect. Finally I deleted my known network and reapplied it and this time it connected no problem.

It's a strange one as it was connecting fine with 3.0-beta3 until it stopped for seemingly no reason.

I think I'll stay with 3.0-release for the time being.

A Former User

This thread deals with something similar, suggested bad wifi module. But maybe you can verify you've tried the suggestions there
https://forum.duet3d.com/topic/10139/failed-to-add-ssid-to-remembered-list-duet-2-wifi

Paddy

@bearer said in Wifi not connecting:

This thread deals with something similar, suggested bad wifi module. But maybe you can verify you've tried the suggestions there
https://forum.duet3d.com/topic/10139/failed-to-add-ssid-to-remembered-list-duet-2-wifi

I was thinking that was the problem, but then it worked in AP mode so that cast some doubt in my mind.

Anyway after multiple re-flashes and networks deleted and added it has started to work again.

Phaedrux

Maybe the firmware is revolted by being on a clone.

Paddy

@Phaedrux Possibly

I was upfront about using a clone and therefore appreciate the help given.

A Former User

The majority doesn't care one way or the other, but it's nice to know as component quality can be a factor.

I haven't studied the protocol between the esp and the duet, but I imagine AP mode is simpler than returning a list of networks so wouldn't be surprised if it worked despite failing at STA mode.

Silly question, but are you sure the wifi firmware upload was a success? If you have serial access maybe worth downgrading and upgrading to be relatively sure it works?

Paddy

@bearer said in Wifi not connecting:

Silly question, but are you sure the wifi firmware upload was a success? If you have serial access maybe worth downgrading and upgrading to be relatively sure it works?

Yeah I'm sure. I was actually running the previous version when the problem first appeared. I found a post that said it could be caused by the fw versions getting out of step - so upgrading to 1.23 was one of the first things I tried.

dc42

It might be worth measuring the voltage on the +3.3V rail, to see if it is within tolerance. The WiFi modules are fussier than other chips on the Duet WiFi about the supply voltage they get.

Is it the same ESP-12S module that we use on genuine Duets, or is it one of the older ESP-12 series modules?

Paddy

@dc42 said in Wifi not connecting:

It might be worth measuring the voltage on the +3.3V rail, to see if it is within tolerance. The WiFi modules are fussier than other chips on the Duet WiFi about the supply voltage they get.

Is it the same ESP-12S module that we use on genuine Duets, or is it one of the older ESP-12 series modules?

It's the ESP-8266MOD.

It's been rock solid for a year before it played up. Now that it's working again and has been stable for the last couple of days, I'm reluctant to start poking around with a probe. It would be just like me to short it out.
If it plays up again I'll bear it in mind to check.