Cannot connect Duet Wifi to new Wifi Router
-
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 0The 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. -
@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)
-
It's channel 11 fixed.
M122 always reports
Network state is changing mode WiFi module is trying to connectDoesn'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.
-
@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.
-
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 MHzBy 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.4GHzwith full signal strength.
-
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
-
@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.
-
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
-
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.
-
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... -
@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:
Connecting to the old router works just fine.
samme ssid and key?
-
I used to work with wifi routers a few years back and spent countless hours staring at sniffed packet logs to figure out why things did not connect.
Some things are simply not compatible with each other. It has nothing to do with radio quality, just that one of the parts involved has interpreted the standard in a different way. If it's a ISP provided router it will be the lowest bidder that has interpreted the standard...
-
@bearer
Tried same SSID and PW on the new one. Yes -
@bondus
This is so frustrating. What is the use of standards if no one sticks to them? -
-
@GaRv3 said in Cannot connect Duet Wifi to new Wifi Router:
What is the use of standards if no one sticks to them?
see if the new one has some ultra mega max 2000 multimedia streaming extensions and try fixing the channel width to 20mhz and setting bgn mode to a lower common denominator, apart from that sounds like you might be better off briding the Duet to the old router?
-
@GaRv3 Did you check/update the firmware on the router? Also, what router is it?
Ian
-
It's a so called "Vodafone Station".
To be precise it is the ARRIS Touchstone TG3442DE.The firmware gets updated by the ISP automatically.
-
@bearer said in Cannot connect Duet Wifi to new Wifi Router:
see if the new one has some ultra mega max 2000 multimedia streaming extensions and try fixing the channel width to 20mhz and setting bgn mode to a lower common denominator, apart from that sounds like you might be better off briding the Duet to the old router?
Limiting to 20 MHz didn't make any difference.
The mode cannot be changed to anything but "Mixed 802.11 g/n" for the 2.4 GHz wifi on this router.Edit: I cannot use the old router as an access point because I have to send it back to the ISP soon.
-
I'm afraid I'm running out of suggestions; if running the Duet as an AP and your AP as a client* isn't a workable option (which sounds unlikely if its an ISP device).
*) in addition to the regular AP
