Constant "Network Error" on Duet3 6HC
-
Is your DWC version matching the firmware at 3.4.5?
Is this a recent problem? Has it worked before? -
@Phaedrux the firmaware is matching the DWC version at 3.4.5.
I worked like a charm before and it's getting worse. There is some phase where it's unusable as I can't even upload a file without getting disconnected constantly -
Hi,
I have the same problem on multiple machines here. It's starting to be a real deal as our company is starting to produce 3D printers with Duet boards but this bug is still causing problems on all 6HC equipped prototypes internally.
@e4d I can see that in your M122 you have 6 connected clients, try reducing them, it definitely helps us here.
I'm currently trying to change some settings in the firmware but without any success so far.
-
@e4d In order to rule out the local network, can you configure the printer to connect directly to a computer via ethernet and see if the problem is resolved?
As described here: https://docs.duet3d.com/en/User_manual/Machine_configuration/Networking#wired-direct-connection
-
@Hugsy Do you have a thread on your issue already? If not, I suggest creating one so we can capture it and provide assistance.
-
@Phaedrux We were just thinking it's a hardware limitation so we didn't do a thread on it. But now that we struggle with just a few http clients maybe it's time to do a thread about it.
Connectivity always was really buggy with the 6HC between the mDNS not working and the Ethernet cutting off.
I'll make a thread about it right now
-
undefined Hugsy referenced this topic
-
@e4d I notice that you have 6 out of 8 HTTP sessions in use, are you connecting to the board from multiple devices?
-
@T3P3Tony I am, multiple computers in the office. I have better result with deconnections using a shielded router. It still disconnect from time to time but way less that before
-
@e4d one theory is that you are running out of HTTP sessions can you restrict the number of connected devices to 2 or 3 as a test and see if that changes the problem.
-
@e4d another possibility is that the large number of http clients is causing RRF to run out of output buffers. On the 6HC we have enough spare RAM to increase the number of buffers.
