Wifi/DWC Disconnecting with RRF3.5.2 on Duet2 Wifi Hardware
-
FWW
>>> M39 SENDING:M39 SD card in slot 0: capacity 7.74GB, partition size 7.74GB, free space 7.65GB, speed 20.00MBytes/sec, cluster size 32kB -
Got a new SD card over the weekend (SanDisk Ultra A1 HC).
Formatted according to the instructions on https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card
Still seeing the issues.
Going to test out a couple things (that are probably not going to do anything but I'm trying anything at this point).
- Going to boot the duet and connect to DWC and let it sit on the Dashboard, see if it loses access just sitting there.
- Going to clean up the SD card. It has old firmware from RFF-1.18 days
- Since I have multiple SD cards now, going to install RFF3.3 with the older Wifi Firmware (prior to 2.01)
- If stable, keep upgrading stable releases until it breaks?
-
@droftarts I didn't read all of the original posts, but it sounds like what I've been seeing. WiFi suddenly disconnects unexpectedly. It usually reconnects about 15 seconds later, but I've been dumped out of whatever macro folder I was looking at, and if I was editing, I'm dumped out of the editor. Everything functions fine until the next time it happens. M122 is below. I have replaced the SD card recently and this problem predates it (it's been happening for months). I also occasionally get WiFi failures at power on, but not frequently. Cycling the power fixes that.
When this happens I sometimes wish I had a wired ethernet connection to fall back on (or just use most of the time, but still have WiFi available). I've been considering replacing the Duet2 WiFi with a pair of Duet3 Minis, and I was wondering if one can have WiFi and the other ethernet and thus give me the choice.
7/16/2024, 11:38:19 AM M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.2 (2024-06-11 17:13:43) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SN-6JKD0-3S06Q-9AY7D
Used output buffers: 3 of 26 (21 max)
=== RTOS ===
Static ram: 23384
Dynamic ram: 80968 of which 0 recycled
Never used RAM 2208, free system stack 120 words
Tasks: NETWORK(2,nWait 6,18.7%,217) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,274) DUEX(5,nWait 5,0.0%,23) MAIN(1,running,79.7%,659) IDLE(0,ready,1.5%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:16:12 ago, cause: power up
Last software reset at 2024-07-16 11:06, reason: OutOfMemory, Gcodes spinning, available RAM 160, slot 1
Software reset code 0x41c3 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x20002578 Task MAIN Freestk 1150 ok
Stack: 20019868 0041079f 00000000 00400247 00000000 00000000 000000d0 00400299 200025d8 20002690 00473bec 20012464 00000001 0040018d 200025d8 00435295 200025d8 00000001 ffffffff 00435499 20002690 00000001 00000019 0043706b 00000004 ffffffff 2000a70c
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 43.1, current 46.3, max 47.7
Supply voltage: min 23.6, current 23.9, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 297/69, heap memory allocated/used/recyclable 4096/4036/2208, gc cycles 332
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min 0
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 2024-07-16 11:38:15
Cache data hit count 4294967295
Slowest loop: 50.79ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 11.3ms, write time 3.3ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 46129ms, bed compensation in use: mesh, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 16, completed 16, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.1
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is doing "G4 P{var.DaemonPeriod}" in state(s) 0 0, running macro
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Filament sensors ===
check 0 clear 4594439
Extruder 0 sensor: no data received
Extruder 1 sensor: no data received
=== DueX ===
Read count 1, 0.06 reads/min
=== Network ===
Slowest loop: 44.20ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(1) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address 84:f3:eb:83:47:be
Module reset reason: Power up, Vcc 3.36, flash size 4194304, free heap 39068
WiFi IP address 192.168.1.130
Signal strength -35dBm, channel 11, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 5 3 0 0 0 0 0 0 -
RRF3.4.6 WF2.1.0 - still dropped
RRF3.4.6 WF1.27 - good
- Much better ping times and consistent
- When connected to DWC, pings do drop but at least DWC never disconnects
64 bytes from xxx.xxx.xxx.254: icmp_seq=844 ttl=255 time=6.689 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=845 ttl=255 time=9.533 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=846 ttl=255 time=4.322 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=847 ttl=255 time=5.767 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=848 ttl=255 time=3.885 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=849 ttl=255 time=3.560 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=850 ttl=255 time=23.067 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=851 ttl=255 time=19.400 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=852 ttl=255 time=5.826 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=853 ttl=255 time=16.080 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=854 ttl=255 time=5.848 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=855 ttl=255 time=10.788 ms 64 bytes from xxx.xxx.xxx.254: icmp_seq=856 ttl=255 time=4.342 msRRF3.4.6 WF2.1.0d - still dropped
So at this point, I guess I will stay on RRF3.4.6 and WF1.27 for now.
-
Hi, I've been looking into some improvements to the WiFi firmware in terms of connection stability. Below is my initial build with those changes. If possible, please do try it out and let me know if you still encounter issues.
Note: After firmware update, please confirm M122 outputs wifi firmware version as 2.1.1beta1.
-
@rechrtb I'll try it! Just installed RRF 3.6 alpha 2, which seems to work fine.
-
@rechrtb I have it installed. I'll let you know if I have any disconnects.
-
@DonStauffer Thank you!
-
@DonStauffer By the way, is the disconnect something you can sort of 'induce'? Because, if you can, please do try it on this new firmware.
-
@rechrtb I haven't seen any way to make it happen. It may be my imagination, but I think it happens more in the afternoons than mornings, if that makes any sense.
No trouble since last night's update to RFF & WiFi.
-
@DonStauffer @trd87t Hi, I just wanted to ask if you encountered issues with the beta firmware build so far...
-
@rechrtb The WiFi still disconnects unpredictably. Alpha firmware and beta WiFi didn't make it better or worse. I don't see any pattern except it seems more in the afternoon. I was assuming it was an interference problem, although other houses are at least 100 feet away here, and the Duet is about 10 feet from my router. But with increasing bandwidth use for WiFi I figured interference.
The biggest problem is if I'm editing a macro or something it drops me out and unsaved changes are lost. If I had the ethernet board I'd just have gone with a wired connection.
-
@DonStauffer I see. Sorry to hear you're still encountering issues. When the issue occurs, is DWC open in multiple tabs (same or different device). Or perhaps a transfer is going on? Also, this doesn't happen on 1.27x wifi firmware?
-
@rechrtb Nothing is necessarily happening, and no, not multiple tabs. Sometimes I even go out of the room briefly and come back and I see in the console log it disconnected then reconnected. Sometimes I see it happen. Usually it's out for anywhere from 20 seconds to a minute or so.
I don't remember the firmware version for sure but I'm pretty sure I was on the latest released version, and now 2.1.1beta1.
-
console log it disconnected then reconnected.
Oh, do you have what that log says? Also, do you happen to have a mesh/multi-AP setup, and the router you mentioned just happened to be the closest one?
-
@rechrtb said in Wifi/DWC Disconnecting with RRF3.5.2 on Duet2 Wifi Hardware:
mesh/multi-AP
Only one router in my house. I think the log entry just said it lost connection. Next time it happens I'll copy the log entry and post it here.
-
@DonStauffer Thank you! I initially thought that it's only the DWC reloading, but in your case the module itself seems to be disconnecting from the access point).
In the meantime, there I have another beta build. This also contain more fixes compared to the last one. If you're still inclined to try it out, it would be highly appreciated!
-
@rechrtb I'll install and test it and report back. Thanks!
-
@DonStauffer Have you had the chance to take the new beta for a spin?
Also, do you have other protocols enabled? Ftp, Mqtt, etc?(Sorry, I just remembered I can look at the M122 output to have the answer to this question) -
@rechrtb Sorry for the delay. COVID-19. I'll try to figure this out today.
