Wifi/DWC Disconnecting with RRF3.5.2 on Duet2 Wifi Hardware
-
@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.
-
@DonStauffer Oh no, no rush! Hope you get well soon.
-
@rechrtb It hasn't been too horrible. Just horrible enough...
Here's the console log, RRF 3.6.0 alpha 4 with the WiFi firmware you posted here; the " Incompatible software" error message is just from having the alpha RFF:
8/21/2024, 11:52:40 AM Connection interrupted, attempting to reconnect...
Operation failed (Reason: Service Unavailable)
8/21/2024, 11:52:41 AM Connection established
8/21/2024, 11:52:43 AM Connection interrupted, attempting to reconnect...
Operation failed (Reason: Service Unavailable)
8/21/2024, 11:52:43 AM Connection established
8/21/2024, 11:52:54 AM Incompatible software versions
The installed software versions do not match. Please operate your setup only at equal versions to avoid potential incompatibilities and unexpected errors. -
im having similar disconnects and I'm on ethernet with a direct run to the switch that the pc i print from is plugged into. started with 3.5.1. duet 2 ethernet 2017 vintage. I noticed it happens when i pause (m226) to insert a nut to be printed over. ftp and telnet are off.
-
undefined Phaedrux moved this topic from Duet Hardware and wiring
-
@DonStauffer Ok, I mentioned previously I am unable to replicate the disconnect you're having. In the past builds I've given, I've just made general improvements to the stability of the WiFi firmware, hoping that it will solve your issue. I've managed to find and fix several issues in this endeavor, and I've been looking at the M122 output more closely because of this.
To that point, I looked at the previous M122 output you've made in this reply: https://forum.duet3d.com/post/341950
I just noticed:
Last software reset at 2024-07-16 11:06, reason: OutOfMemory, Gcodes spinning, available RAM 160, slot 1Could the 'disconnects' not be actually related to the network, but the board running out of RAM? If the board crashes because it runs out of RAM, then naturally DWC will disconnect and wait until reconnection after the reset.
In the afternoons, perhaps more stuff is also in the memory (do you turn off at the end of the day and turn on in the morning)?
-
@Miss-Rebekah I see you are also on a Duet 2 (Ethernet). Though this is more of a WiFi thread, can you check the output of your M122 as well after a 'disconnect' (or what might actually be a board crash)?
(Please check this reply for context: https://forum.duet3d.com/post/344015)
-
@rechrtb I don't think the disconnects are running out of memory. They happen even when nothing is happening on the printer, and that out of memory only happens when a job fails in the middle and doesn't reclaim memory. While I've been debugging new code, that happens occasionally but not frequently like teh WiFi disconnects. A restart fixes it, and I don't have it happen too much any more, while the WiFi disconnects continue to happen. I just was assuming there's RF pollution around.
Also I've watched it happen spontaneously, the reconnect, with no reset, and there was no error. Often I'm actually just editing a macro when it happens, and I may not have even run a print job in days.
-
@DonStauffer Just to verify, next time you notice it happens, can you do an M122 immediately after? Just to be able to rule this out completely.
There is another new build which fixes an issue on the previous one (it's not related to this issue however).
