Connectivity issues with 6HC
-
@Hugsy thanks for the update. Please try and capture the issue when occu4ring with 3.4.5 on wireshark, also if possible connect a USB temrinal and send M122 after a crash.
-
@T3P3Tony Hi, on Wireshark I see a few "Destination unreachable (Network unreachable)" over ICMP protocol. This happens when I have multiple (6) DWC tabs open, as usual some tabs have their connection interrupted when of them is refreshed. This is with RRF3.4.5 and DWC3.4.5 non-customized.
Funny enough, I merged DWC3.4.5 into our custom DWC branch and the performance is similar between custom and non-custom DWC. I'm thinking it's more related to software.
I'll try some diagnostics via usb, M122 B0 and a M111 P1 S1.
-
@Hugsy thanks, and yes the diagnostics will be helpful. One thing that I note is that you have a maximum of 8 http sessions so you may be hitting that limit, M122 will let you know, although you only get 1 session per IP client address.
-
@T3P3Tony Oh wait, that's interesting. We're not hitting the 8 http sessions limit (I did quite some tests with that setting in the firmware), but you're telling me a physical client can have as many tabs as he wants and it will only generate 1 http session ?
Is it a hardware limitation of the ethernet chip or SoC on the 6HC to be limited on the number of sessions ? -
@Hugsy do not have more than one client from 1 IP address or else you will get odd behaviour with replies being consumed by one and thus not showing up in the other.
The session limit is due to memory limitations on the Duet MCU.
-
@T3P3Tony Okay, we can work with a 1 tab per client. Although we observed that 2 different IP clients can consume each other replies already, and while I did tests with one client that has multiple tabs, multiple clients with one tab each lead to the same problems. Do you want a multi-Wireshark session with different clients ?
-
@Hugsy before grabbing more wireshark essions I would like to see what @chrishamm thinks.
-
@Hugsy said in Connectivity issues with 6HC:
I just can't go with an SBC for sourcing issues and I'm having a lot of bugs related to meta commands (that I rely on heavily).
I use a lot of meta commands myself in SBC mode and I'm not aware of any bugs. Can you elaborate?
I'll have a look at your Wireshark dumps when I find some time.
-
@chrishamm Hi Chris,
It was at RRF3.3,
if I recall correctly it was the syntax on some commands that changed the motors current, it was a long time ago and I think these commands were changed (in our macros) so it's not relevant anymore.Actually I found the issue by looking into it, we rely on a lot of global variables in the machine and their support started at RRF3.4 on SBC mode, so it's not a problem anymore. -
@Hugsy I've had a chance to check out your Wireshark dumps and I believe the Duet is overloaded by network requests. For a similar reason we don't recommend putting your Duet on the public internet. Here some ideas how you can reduce the number of simultaneous requests:
- Use only one browser window (DWC instance) per client PC
- Increease the AJAX request interval in Settings -> Machine
- Upgrade your setup to SBC mode (it doesn't have to be a Pi although that's the easiest way)
We're increasing the number of maximum TCP connections in the underlying IP stack in the next firmware version, perhaps that will resolve the spurious disconnects as well.
