@Chriss Hello, I'm also looking into this issue. I have a few questions:

1. You mentioned that before 3.5.0rc2 + 2.1beta6, you also observed disconnects but reconnection always succeeded. Do you remember the RRF version and WiFi firmware version you were running then?

2. You mentioned that all Duet boards you have on RRF 3.5rc + WiFi firmware 2.1beta6 have this issue, but the 'others' are fine. Can you tell me what versions these other boards are on?

3. Can you downgrade maybe one of the problematic boards to RRF 3.5.0rc2 + WiFi firmware v1.27?
   @moth4017 reports that this issue still occurs for the v1.27 firmware, just want to confirm if that also occurs for you.

4. I assume the RRF firmware you flashed on the boards are exactly the release binaries in the GitHub repo. Is this correct?

@trd87t @DonStauffer

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.

DuetWiFiServer.bin

@zemlin Glad its ok for you now. By the way, are these DWC's on different machines open at the same time by any chance? That's the case where this firmware tries to improve on...

@zemlin Hi, can you try this beta firmware and see if it solves the issue?

f37decf6-a946-443b-afdb-fd46ffdad83f-DuetWiFiServer.bin /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/build/DuetWiFiServer.bin

This firmware has some changes with regards to handling connections in the backlog, which might help with what you're experiencing.

@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).

DuetWiFiServer.bin

@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)

@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 1

Could 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)?

@DonStauffer Oh no, no rush! Hope you get well soon.

@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)

@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!

DuetWiFiServer.bin

@DonStauffer

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?

@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?