Cannot connect Duet Wifi to new Wifi Router

GaRv3

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2

@bearer
Yeah I knew ' too. That's why I wrote I don't have it in the SSID or pw.
What does "sending STA is leaving or has left Basic Service Set (BSS)" on the page you linked mean? Incompatible protocol versions?

GaRv3

@PaulHew
See my first post again "but I also tried with a broadcasted SSID"
And no, the SSID was not the same and I even tried using another SSID.

A Former User

@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:

What does "sending STA is leaving or has left Basic Service Set (BSS)" on the page you linked mean?

not sure I found anything relevant, but it does suggest client side issue, most topics relate to signal quality and roaming.

could be the wifi is confused after the hidden bssid, try clearing all stored networks and adding just the one? try:

M552 S-1
M552 S0
M588 S"*" 
M587 S"GarMir" P"key"
M552 S1 P"GarMir"

Edit: also could you confirm your wifi is set to channel 1 as a fixed channel, not auto? (log said 2412MHz)

droftarts

@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:

FIRMWARE_VERSION: 2.03

It would be good to update your firmware to the latest RRF2 version, 2.05.1. Get it from https://github.com/dc42/RepRapFirmware/releases/tag/2.05.1
Update instructions, by copying file to SD card on your PC: https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_1

So long as you have named the SSID correctly, it doesn't matter if it's hidden.

How is the WiFi encryption set on the router? Duet 2 Wifi only supports WPA and WPA-2 with either AES or TKIP encryption (I think!). Maybe take a screenshot of the WiFi setup page on the router?

Ian

A Former User

@droftarts said in Cannot connect Duet Wifi to new Wifi Router:

How is the WiFi encryption set on the router?

@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:

03/17/2020 20:29:36 WG-MAC=D4:3F:CB:91:5F:69; STA-MAC=2c:3a:e8:00:00:00; IF=wlan0_0; SSID=GarMir 2,4GHz; ConnectionState=connected; WirelessMode=802.11n; LastTxPhyRate=52Mbps; LastRxPhyRate=6Mbps; MaxSupportedRate:0Mbps; EncryptMode=AES; AuthMode=WpaPsk; RSSI=-33dBm; Channel=2412MHz; Radio=2.4G; Bandwidth=20M; TxFailPkts=0; RetransPkts=0 Wi-Fi

also, the log suggest the client is leaving, after successfully having connected, so unlikely to be a encryption issue (unless I'm reading the log incorrectly)

GaRv3

@bearer
Didn't help unfortunately.

@droftarts
As mentioned by @bearer , this should not be an encryption issue. Router is set to WPA2 and encryption mode is AES.

@droftarts said in Cannot connect Duet Wifi to new Wifi Router:

It would be good to update your firmware to the latest RRF2 version, 2.05.1.

I will try this next.

A Former User

@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:

Didn't help unfortunately.

mkay, still, try to make sure there arent more than one entry if you do make changes, just to rule out that going forward.

maybe its time to elaborate a little on the pysical conditions of the network. locations, other APs etc?

GaRv3

I will go into detail about this if the firmware update does not solve the issue.
But I've got a question about the fallback update procedure. There is no "iap4e.bin" in the repo but the guide tells me to copy it over. Should I simply leave the old file in place?

Phaedrux

Check this release for the iap files https://github.com/dc42/RepRapFirmware/releases/tag/2.03

A Former User

@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:

Should I simply leave the old file in place?

it won't do any harm, and will be needed if you should ever wish to downgrade. however as 2.03 is likely using wifi firmware 1.23 i doubt there is any change relevant to the issue; but won't hurt to be up to date. while you're at it do confirm the wifi firmware is 1.23. (its part of the M122 output.

GaRv3

Ok, so I updated the frimware and Wifi server:

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-95BLL-N6PSS-6J1F0-3S86R-90TVM
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93132 of which 0 recycled
Exception stack ram used: 264
Never used ram: 11964
Tasks: NETWORK(ready,540) HEAT(blocked,1232) MAIN(running,3824) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:04:44 ago, cause: software
Last software reset at 2020-01-26 16:51, reason: User, spinning module GCodes, available RAM 11284 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 24.3, current 27.3, max 27.4
Supply voltage: min 0.0, current 0.0, max 0.0, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 513307291
Slowest loop: 4.16ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== 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: 1173.89ms; 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 changing mode
WiFi module is trying to connect
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 2c:3a:e8:0b:17:0f
WiFi Vcc 3.32, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 27928
Socket states: 0 0 0 0 0 0 0 0

The problem persists.

About the physical conditions:

The printer is right next to the router (ap) with one wall in between. The signal strength should be easily sufficient with the 2.4GHz wifi. I even get full 5GHz signal strength right next to the printer on my phone.
There are many wifi signals around here. It's a pretty crouded place. But I made sure to use the wifi channel that has the fewest SSIDS. Currently it's 2AM and there should be near to no interference.

A Former User

@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:

But I made sure to use the wifi channel that has the fewest SSIDS.

is it a fixed channel (not auto?), if auto it could be the Duets wifi module cannot follow across all channels due to differing country regulations, but I have no idea whats set for either product.

re signal strength, see if you can run M122 repeatedly and catch the Duet in a moment where it is connected and shows its signal strength, it will likely have (significantly) lower receive sensitivity than your router (and phone)

GaRv3

It's channel 11 fixed.

M122 always reports

Network state is changing mode
WiFi module is trying to connect

Doesn't seem I can get a report in the very short time frame, when a connection is established.

But I am shure, the signal strength is very good. This can't be the issue. I can easily establish a very good wifi connection two rooms further from the router with any device.

A Former User

@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:

It's channel 11 fixed.

Channel=2412MHz;

does not compute, but might not be relevant as its usally 12-14 that gives problems.

But I am shure, the signal strength is very good. This can't be the issue.

Don't underestimate the ESP8266 module's ability to not get a signal; after all as it stands the options are defective module or poor singal as far as I can tell.

GaRv3

Some more information on the 2.4GHz wifi:

SSID: GarMir 2,4GHz
SSID broadcast: off
Security: WPA2
Wifi mode: Mixed 802.11 g/n
Channel: 11
Bandwidth: 20/40 MHz

By the way: Sometimes I can see the Duet in my router status as

Name: unknown
IPv4: 192.168.0.37
IPv6:
MAC: 2C:3A:E8:0B:17:0F
WiFi: 2.4GHz

with full signal strength.

A Former User

If its inconvenient to move the printer you could try switching roles; put the Duet in AP mode and see what signal strength you get where the router is (although it won't quite be an apples to apples thing).

https://duet3d.dozuki.com/Wiki/Gcode#Section_M589_Configure_access_point_parameters

A Former User

@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:

with full signal strength.

what it transmits and what it receives could differ by a lot tbh.

GaRv3

Yeah, but to be honest, this should really not be a thing.
The physical distance between the router and the Duet is maybe 0.5m. It's literally just this one wall in between.

I will actually try to remove the special chars from the wifi SSID and password now to see if this could be a thing.

Edit: No success

A Former User

All I'm saying is the Duet people are normally more than willing to replace faulty boards, but I'd hate to see you waste time with a replacement if the problem isn't the board; which I don't think is the case but thats just my $0.02.

GaRv3

I don't think it is a hardware problem with the board. This would be a strange coincidence cause it worked until I changed the router.

I will power up my old router now an check if the Duet connects to it.

Edit:
Connecting to the old router works just fine.
This has to be some kind of incompatibility...