So, I'm posting this just in case it helps anybody else out:

I was having problems with the webserver crashing on my duet Ethernet. People here suggested all sorts of useful things. Some seemed to help a bit, some didn't. But the problem never entirely went away...

Well! I finally figured it out: Because all my steppers are mounted on shock mounts (Voron2, if anyone is interested), their casings are all electrically isolated. And there are lots of belts in my printer. So apparently, belt drives + isolated steppers = static build up. And apparently, the first consequence of that buildup is crashing the Ethernet module.... So, I added grounding leads to all my steppers, and Boom! total stability.

@snowcrash I think safety ground is the way to go. Since that's where your frame should nominally be connected anyway. And you're basically just extending your frame grounding to your motors. Connecting to DC or AC negative / ground creates some non-zero possibility of having something go wrong, and the motor casings ending up energized to one voltage or another!

So, I'm posting this just in case it helps anybody else out:

I was having problems with the webserver crashing on my duet Ethernet. People here suggested all sorts of useful things. Some seemed to help a bit, some didn't. But the problem never entirely went away...

Well! I finally figured it out: Because all my steppers are mounted on shock mounts (Voron2, if anyone is interested), their casings are all electrically isolated. And there are lots of belts in my printer. So apparently, belt drives + isolated steppers = static build up. And apparently, the first consequence of that buildup is crashing the Ethernet module.... So, I added grounding leads to all my steppers, and Boom! total stability.

@dc42 That fits pretty well. I often flip back and forth between my desktop and my laptop.

I'll wait for 2.0 to sort it then.

I've noticed that I sometimes (haven't really been able to figure out a pattern, sorry) get repeat notifications. For example, if I get the print finished notification, and then try to do some stuff with the manual controls, every button press will get me another "print finished" notification. Does anybody know why this happens, or how to fix it?

So…just as an update here, I moved to 1.21RC5 and the crashes got less frequent, but were still happening occasionally. Then I finally remembered to pickup a new network cable, and it's been stable for 48 hours now. So....fixed, I think!

Huh. Now that you mention it, I don't think I have tried that. And of course I don't have any more suitable length cables in my house at the moment. Well, I'll grab something and check that as soon as I can…

@dc42:

Are you using a static IP address in your M552 command, or relying on DHCP?

I've tried both (currently on static) doesn't seem to make a difference.

I don't believe the duet ethernet uses the wifi software. Am I wrong?

I guess I should also mention my hardware config: It's a Voron 2, so Core XY movement, 4 independent Z motors. I'm using a Duet Ethernet, with a DuetEX5 to run it. 24V power.

I've been having trouble with my Duet Ethernet: Randomly the webserver stops responding. The web interface indicates that the connection has timed out, and if I attempt to ping the machine's IP, there is no response.

If I connect a USB cable, and open a serial connection, I find that M552 still reports the connection as up, and M122 reports a nice low Maxreps (generally 4). doing M552 S0, followed by M552 S1 does restore normal function

I have experienced this problem both on 1.20, and 1.23RC4

What can I do next to troubleshoot this issue?