Multiple DWC 2.1.4 Browser Tabs at Once - Drop Outs

DocTrucker

Edit: Upgraded all machines to DWC 2.1.4. Still HTTP timeouts and loss of connection.

Hi all. Running 2.0.7 on a mix of Duet v0.6 and v0.8.5. Tried to have four DWC pages open on Firefox (Ubuntu 18, recently updated) and the connections are really sketchy. Connect to one at a time with them all still running and all is fine.

Is this a known issue? Since one at a time is fine I'm assuming this is a problem on my computer (ie DWC) rather than the machines?

chrishamm

Yes, it is a known issue and a limitation in RepRapFirmware. You may not see G-code replies in all four sessions because RRF keeps G-code replies per IP address and if it was already sent, it just returns an empty one. Hence multiple sessions from the same IP address should be avoided.

In general it's fine to have 2-3 sessions running but each on a different device.

DocTrucker

@chrishamm I meant I had 4 duets running, all talking to a single device - my desktop. If I have four tabs open in Firefox tab aimed at a unique Duet there are lots of drop outs. If I only have one tab open at a time it is fine.

jay_s_uk

@DocTrucker
that'll probably be down to the way firefox is handling the tabs, not DWC

A Former User

Does firefox manage to keep two running if you have one in a private session or what firefox calls it?

DocTrucker

@jay_s_uk even on a active tab? Connection drop outs aren't just happening when the tab isn't up front.

DocTrucker

@bearer good idea. Will try that, and also go old school with seperate windows.

mwolter

@DocTrucker Recommend trying Chrome. I’ve had good luck with It and 2.07. Had many weird disconnection issues with Safari and since switching to Chrome it has been much more stable.

DocTrucker

Multiple browsers or private windows have no effect. Perhap https would be better to the DWC?

I'll try another browser.

DocTrucker

Tried Chromium, Chrome, Iridium, Firefox.

Private modes, separate windows.

All crap with four DWC windows open at the same time.

Connections may be made, but that can't be held.

Edit: +Opera

I think this confirms it is either a network issue or duet/DWC issue. All machines are stable on their own. The network is a subnet on my private network. I have a router that hooks into my home network, and all machines connect directly to that, or a network switch that is also connected to the router.

DocTrucker

Just tried a different patch lead between my sub-net switch and sub-net router. No improvement. All other internet including an Octopi and streaming radio works fine. The subnet is because the connection to internet is sketchy and it allows me to maintain connection to my machines if the connection to the main house router fails.

Is there any way to run DWC on HTTPS?

Edit: Rolling out 2.1.4 on RRF1 on all of the problem Machines. It's working fine. Should also say all machines are static IP Adresses, no IP address clashes, and outside of the range the router allocates DHCP addresses.

DocTrucker

All machines up graded to 2.1.4. No improvement in the drop-out issue.

droftarts

@DocTrucker do they all have the same MAC address?! That was sometimes an issue with the old Duets.

Ian

DocTrucker

I think they are different. Thanks for the heads up, I will check.

DocTrucker

@droftarts there was a clash with two machines sharing a MAC address, thanks that looks promising. Although the fault finding did prompt me to try a version of DWC that I thought wasn't compatible, and it's working fine so a minor plus out of my balls up!

It's still miss-behaving at the moment but I know which two machines to avoid having up at the same time. At the end of the days prints I will reset them all and the router + switch too before giving a verdict. At the moment it's still misbehaving but I'm guessing the board or router may need a reset.

I had asigned unique MAC addresses to all machines but obviously hadn't finished setting up this machine.

dc42

@DocTrucker said in Multiple DWC 2.1.4 Browser Tabs at Once - Drop Outs:

I had asigned unique MAC addresses to all machines but obviously hadn't finished setting up this machine.

Unless you are using older Duets (0.6 and 0.8.5 versions), it's not normally necessary to configure the MAC addresses, because for more recent boards RRF generates a default MAC address from the unique ID of the chip. There is only a small possibility that two Duets will have the same MAC address.

EDIT - I see from your original post that you are indeed running older Duets.

DocTrucker

@dc42 worth knowing though, thanks. Should the MAC address change instantly with M540, or only after a reset?

DocTrucker

All sorted now. Thanks. User error...