Posts made by rechrtb

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

@DonStauffer @trd87t Hi, I just wanted to ask if you encountered issues with the beta firmware build so far...

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

@DonStauffer Thank you!

@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

@zBeeble said in Duet2 wifi stuck repeating Wifi Error.:

as generating a line every so often ... printer on or not.

But the machine is connected to the home server ... which is always on. I'm using minicom ... which is set to log all traffic

Reply

Those "already 4 conns" should be normal, especially when there are multiple clients with the web interface open.

@zBeeble Nothing beyond turning on the debug messages for network and WiFi. If I'm correct, you turned off the network debug messages though since it was too noisy? Also, please make sure it's logging to file so we don't miss anything.

@zBeeble You mean in terms of like upload/download speed? Debug builds would be 'unoptimized' so yes.
Also, by the way, did the repeated "SPI timeout" issue not appear till now?

@Exerqtor Hi, this was reported by one other user recently in https://forum.duet3d.com/topic/35761/bad-wifi-module/6. In their case, it seems they had the same SSID entries but different capitalization. @gloomyandy recommended looking at the list of SSIDs using M587, are you able to do that?

Also, just to confirm - this is for an enterprise network?

@zBeeble Seems like the disconnect was detected at the lower levels of the ESP WiFi stack. The upper layers did what it's supposed to and attempted a reconnect. I don't think this was what causes the repeated SPI timeout error - but noted nontheless.

@SonnyD1 Hi. I know you mentioned that it's ok now, but I want to do some light digging into this. Just to confirm, you are connecting to an enterprise network, right? And also, regarding the duplicate SSID but different capitalization, they both had the same secret (username/password, certificate,)?