Duet 2 Ethernet IP address keeps flashing on display.
-
And it's not connecting to the network anymore. When this happened last time, I had to keep the board turned off for about 10 minutes and then try again and it connected to the network.
-
Do you have any "Cold spray"?
Maybe it's your Ethernet interface chip getting too hot? -
@alankilian I don't, but I have tiny heatsinks that came with my DRV8825 stepper drivers back when I was using RAMPS on my 3d printer. Let me try that.
-
The network isn't connecting right now and the yellow link status light on the ethernet port is blinking periodically.
-
I reconnected the board after putting on the heatsink on the ethernet interface chip and the network connected. Then it fritzed out 3 minutes later. I'm running out of options here....I've got a replacement Duet Ethernet board on the way. I think I'll test the new board once it arrives and use that if that works... This is beyond frustrating...
-
When the network isn’t reachable have you already hooked it up with a usb connection and send M552 to check the status of the network module?
-
@Argo said in Duet 2 Ethernet IP address keeps flashing on display.:
e have you already hooked it up with a usb connection and send M552 to check the status of the network m
Yes, and M552 shows Network is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0
This is despite the link status light on the port lit up steadily (amber) and the traffic light (green) flickering.
-
If then M552 S0 to disable the network and M552 S1 P<ipadress> doesn’t change anything my bet would also be a defective ethernet module.
-
That's what I think as well. I just downgraded to firmware 2.05.1 and am having the same issue. I'll get a replacement ethernet module for this board and try it out. I do have a Duet Ethernet board in the mail, so that will be for my second printer
-
Ok, so I received my new Duet 2 Ethernet board today and the first thing I did was flashed firmware 3.2.2 on it. It is working without a glitch so far (fingers crossed). I guess the ethernet module on the other board was bad. I have ordered a replacement for it, so hopefully that fixes my problem.
