Wifi module keeps disconnecting
-
See under M540 in the GCore wiki page at https://duet3d.dozuki.com/.
-
Thanks for the heads up on M540.
Still have the permanently–not-responding-over-wifi problem.
When it's in that state this is what M122 looks like now under 1.21RC3:
[c]SENT: m122
READ: === Diagnostics ===
READ: Used output buffers: 5 of 32 (14 max)
READ: === Platform ===
READ: RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21RC3 running on Duet WiFi 1.0 or 1.01
READ: Board ID: 08D6M-91AST-L23S4-7JTDL-3SD6N-96X5K
READ: Static ram used: 16144
READ: Dynamic ram used: 100448
READ: Recycled dynamic ram: 2192
READ: Stack ram used: 3568 current, 4648 maximum
READ: Never used ram: 7640
READ: Last reset 00:57:47 ago, cause: software
READ: Last software reset at 2018-03-11 13:17, reason: User, spinning module GCodes, available RAM 3752 bytes (slot 1)
READ: Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
READ: Error status: 0
READ: Free file entries: 10
READ: SD card 0 detected, interface speed: 12.0MBytes/sec
READ: SD card longest block write time: 0.0ms
READ: MCU temperature: min 30.6, current 30.8, max 31.1
READ: Supply voltage: min 24.5, current 24.6, max 24.6, under voltage events: 0, over voltage events: 0
READ: Driver 0: standstill, SG min/max not available
READ: Driver 1: standstill, SG min/max not available
READ: Driver 2: standstill, SG min/max not available
READ: Driver 3: standstill, SG min/max not available
READ: Driver 4: standstill, SG min/max not available
READ: Date/time: 2018-03-11 14:14:53
READ: Slowest main loop (seconds): 0.156608; fastest: 0.000047
READ: === Move ===
READ: MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
READ: Scheduled moves: 0, completed moves: 0
READ: Bed compensation in use: mesh
READ: Bed probe heights: 0.000 0.000 0.000 0.000 0.000
READ: === Heat ===
READ: Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
READ: Heater 1 is on, I-accum = 0.0
READ: === GCodes ===
READ: Segments left: 0
READ: Stack records: 1 allocated, 0 in use
READ: Movement lock held by null
READ: http is idle in state(s) 0
READ: telnet is idle in state(s) 0
READ: file is idle in state(s) 0
READ: serial is ready with "m122" in state(s) 0
READ: aux is idle in state(s) 0
READ: daemon is idle in state(s) 0
READ: queue is idle in state(s) 0
READ: autopause is idle in state(s) 0
READ: Code queue is empty.
READ: === Network ===
READ: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
READ: HTTP sessions: 1 of 8
READ: - WiFi -
READ: Network state is running
READ: WiFi module is idle
READ: Failed messages: pending 0, notready 0, noresp 0
READ: WiFi firmware version 1.21RC3(28b1)
READ: WiFi MAC address 5c:cf:7f:2b:ee:bb
READ: WiFi Vcc 3.42, reset reason Turned on by main processor
READ: WiFi flash size 4194304, free heap 18200
READ: Socket states: 0 0 0 0 0 0 0 0
READ: === Expansion ===
READ: ok[/c] -
The report says "WiFi module is idle" meaning that either it was never connected to the AP, or it was but something caused it to disconnect.
-
It was connected to the access point. And working fine.
I think it continued to be connected to the access point. Because if I try to connect, the web browser gives the message:
"unable to open the page because the server unexpectedly dropped the connection….. This sometimes happens when the server is busy..."
Whereas if I invent an IP on the same network the browser gives a message:
"unable to open the page.... because the server where the page is located isn't responding"
Also the Duet continues to show on the wifi router admin page.
So... something weird going on in the wifi stack?
-
I had erroneously loaded 1.21RC3 WifiServer….. Have now tested 1.21RC4 for a good hour and it seems to have cracked the problem.
Well done!
On the wifi router still see a "*" instead of the name of the printer, but who cares?
Really this embedded wifi has caused such grief over the years.... Yet also on home network have another ESP device - https://luftdaten.info/en/construction-manual/ - and it just seems to tick over without causing any trouble.
-
Thanks. It looks like the new SDK from Expressiv that fixed the KRACK WPA vulnerability introduced a new issue, but they seem to have resolved it in the more recent version that we use in RC4. Your other device is probably using the SDK that predates the KRACK fix.
-
ps don't forget the two links (from the documentation to the Betas on github) are broken: https://duet3d.dozuki.com/Wiki/Firmware_Overview#Section_Betas
-
ps don't forget the two links (from the documentation to the Betas on github) are broken: https://duet3d.dozuki.com/Wiki/Firmware_Overview#Section_Betas
Thanks, I've corrected that link.
-
I've gone through the Troubleshooting AJAX errors and my last signal strength says 50dbm. I can't stay connected for more than a minute before I get a request timeout. I'm using firmware, server & web control 1.21. Where should I go from here?
-
@kirk001, have you tried changing your router WiFi channel between 1, 6 and 11 ?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Yes, sir. All 3 and same result.
-
I think we need to change your Duet in case the WiFi module is faulty. Please contact your supplier. If you purchased it directly from Duet3D, see https://duet3d.com/warranty.
-
Thank you.
-
I just received my warranty replacement board and installed it. I'm getting fewer disconnect errors, but I'm still getting them. My M122 shows "WiFi signal strength -50dBm, reconnections 0, sleep mode modem."
I don't think I've configured anything incorrectly, but a second defective board would be quite unlucky. What are my options for getting this to work consistently?
-
kirk001 - the solution I used was to create a Wireless Hosted Network on my Win10 workstation that I use to access the Duet. This has the added bonus of keeping the Duet offline. If your computer is closer to the printer than your router it could be worth a shot. There's similar functions in Linux.
-
Both my computer and the printer are 6 feet away from the router. I have a raspberry pi 10 feet away that can has no problem staying connected.
I can't believe I spent almost $200 on this and still can't print 4 months later.
-
@kirk001 said in Wifi module keeps disconnecting:
I just received my warranty replacement board and installed it. I'm getting fewer disconnect errors, but I'm still getting them. My M122 shows "WiFi signal strength -50dBm, reconnections 0, sleep mode modem."
I don't think I've configured anything incorrectly, but a second defective board would be quite unlucky. What are my options for getting this to work consistently?
I'm sorry to hear that you are still getting problems. I would expect a signal strength a little better than -50dBm if the Duet is only 6ft from your router, but -50dBm should be enough for a reliable connection.
A few questions:
- Do the disconnections occur when the Duet is idle, or only when printing?
- Have you increased the maximum number of Ajax retries in the settings/general page of DWC?
- Do you have a password set, other than the default "reprap"?
-
Signal strength ranges from -40-50dBm, but -50dBM is the worst it gets. The board is sitting at the bottom of my Hypercube--I don't know if that is what's making the signal strength worse at 6ft.
Disconnections occur when idle. I haven't been able to print. I can't stay connected more than 10 seconds. I've tried channels 1,6, and 11. I'm using a Netgear Nighthawk and I had 4 other devices on the 2.4G working fine. I removed the other 4 devices in case they might interfere with the Duet.
AJAX retries are at 5.
And have no password at the moment (it was really tedious to have to enter a password 5 times in one minute because it kept disconnecting every 10 seconds.) -
@kirk001 said in Wifi module keeps disconnecting:
Disconnections occur when idle. I haven't been able to print. I can't stay connected more than 10 seconds.
That's worse than I've ever heard happen before. Please can you connect a PC running e.g. YAT or Pronterface to the Duet, and send M111 S1 P13 (if using YAT, set the end-of-line sequence to "LF only"). This will enable WiFi debugging. When DWC connects, you will see a few lines of debug. When you get a disconnection, there may be some more debug messages - please post them here.
And have no password at the moment (it was really tedious to have to enter a password 5 times in one minute because it kept disconnecting every 10 seconds.)
The latest DWC (1.21.1) remembers the password when it reconnects.
-
Something odd just happened. I logged into my Duet from 2 different computers. On one, I connected directly to the IP address, and on the other, I connected to my "duet.local" address. The one connected directly to the IP address has stayed connected for over an hour now while the "duet.local" connection has disconnected 20+ times. I haven't tried printing yet. but this is the longest I've been able to stay connected.
