topic_unsolved Duet 2 Ethernet Major Meltdown!
vernon1xx last edited by vernon1xx
Hello, My new Duet Ethernet just made a loud pop noise and all the lights went out on the board and the Panel Due 7i shut down. For a while I could not even get a light to come on. However, after waiting a bit, I was able to get the green LED 3.3v, the red LED 5v, and the red LED next to the micro usb to come on. I was then able to connect via pronterface. The M552 command showed current ip address. A minute later I was able to connect via web page. The endstop lights were on for the x and y drives. I shut down, and I unplugged them started the board back up and they turned off. I unplugged the usb and plugged it back in again. The Panel Due is lit up dimly but nothing for an interface exists. It is simply blank. Now when I try to connect via ip address I get this response "Your Duet rejected the HTTP request: page not found". I have no idea on how to proceed, can someone please direct me??? Thank you
It looks as if I inadvertently inverted the positive and negative wires on BL Touch (wired to Heater 7/PWM 5). I thought I was switching the polarity for my new parts fan. Do I get a special award for such an ignorant mistake?? Should I order a new board and Panel Due now, or does someone know how I might rectify this problem??? Thank you!
fcwilt last edited by
I know how you feel having made a few such wrong connections in my time - thankfully never to my beloved Duet boards.
Hang in there.
Now when I try to connect via ip address I get this response "Your Duet rejected the HTTP request: page not found". I have no idea on how to proceed, can someone please direct me?
That normally means that the web files can't be read from the SD card. You can send M39 from Pronterface to check the SD card status. My guess is that the SD card was damaged, and you need to replace it and put the right files on the replacement. See https://duet3d.dozuki.com/Wiki/SD_Card and the page that it links to at the end.
Hello, Thank you for your response! M39 brought back:
SD card in slot 0: capacity 3.90Gb, free space 3.90Gb, speed 20.00MBytes/sec, cluster size 64kb
ok T0:2000.0 /0.0 B:23.7 /0.0
My Ethernet port on the Duet no longer lights up. I am unable to get any response via ip address. M552 via Pronterface brings back:
Network is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0
ok T0:2000.0 /0.0 B:23.8 /0.0
My best guess is that connecting the BLTouch the wrong way shorted the +5V rail out, and something in the 5V regulator circuit failed, creating a transient on the 5V rail and probably on the 3.3V rail too. That may have damaged the Ethernet module and perhaps other devices such as the main processor. Is the processor getting hot?
It's normal for the PanelDue to be a bit dim if the only 5V power is via the Duet's USB port, however it should still work unless it has been damaged. You could disconnect it from the Duet and connect it directly to your PC via its USB port. If it doesn't start up, you could try erasing the firmware on it, then after a reset see if it presents the Bossa port to your PC.
vernon1xx last edited by vernon1xx
I will follow your advice for the PanelDue. Thank you. I am not sure about the Main Processor temperature. I will pull out my IR gun and check it out. I did connect to Pronterface and input M564 H0 S0 with the main power on, and I got no response as far as movement from the axis. Not sure if there are other tests I could try??? Update: After plugging the PanelDue via USB into my laptop it appears to be working fine. I wish I could say the same for the Duet....
Do you know what went pop on the Duet? If it's a version 1.04 Duet, are all 3 fuses intact?
I was wondering about that myself... I inspected all the fuses, and they all look good. Also, I cannot see any physical damage to the board. In the beginning the board was completely dead. I took a few minutes of sitting to get the lights to come back on... Initially, after the lights returned, the ethernet was working. After several times of off/on while running tests, it stopped lighting up..