Duet 2 Ethernet not connecting to network

LKM

I'm following the "Getting Connected" documentation here, and I'm stuck at step "Connect Duet to Network". I'm trying to connect via DHCP, this is what I see in YAT:

M552
Network is disabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0
ok
M552 S1 P0.0.0.0
ok

After that, nothing else happens. What's curious is that the LEDs on neither end of the Ethernet cable are blinking. Both the Duet 2 Ethernet and the Ethernet router's Ethernet ports' LEDs remain off.

Any idea what I could try to get the Ethernet connection to work?

jumpedwithbothfeet

@lkm if I'm reading it right you need to enter your internet SSID, take a look at M552 in the Gcode dictionary -
https://docs.duet3d.com/User_manual/Reference/Gcodes

LKM

@jumpedwithbothfeet said in Duet 2 Ethernet not connecting to network:

you need to enter your internet SSID

That part of the documentation is specific to the Duet 2 Wifi, I guess. In my case, since I'm simply connecting an Ethernet cable to the board, I shouldn't have to enter my wireless network's SSID, right?

jay_s_uk

@lkm correct. if the lights aren't lighting up then i guess try a different cable/port on your router

LKM

@jay_s_uk said in Duet 2 Ethernet not connecting to network:

@lkm correct. if the lights aren't lighting up then i guess try a different cable/port on your router

Hm... I've now tried three different cables, including one that I just took fresh out of its packaging. I've also tried every port on the router (the router itself is working, my two other devices are plugged into it and both have access to the network).

Rushmere3D

@lkm Did you send M552 again after the M552 S1 P0.0.0.0 and did that show any change in state?

Or even try a fixed IP?

LKM

@rushmere3d When I send M552 again, it says

Network is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0

When I set an IP address manually, it returns:

M552 S1 P192.168.50.123
ok
M552
Network is enabled, configured IP address: 192.168.50.123, actual IP address: 192.168.50.123
ok

So that looks correct, but I can't ping that IP, Angry IP Scanner doesn't find it, and there's still no blinking lights on either Ethernet port.

Rushmere3D

@lkm What's your IP and that of your router? I'm assuming you've set that up yourself to have a 192.168.50.***

LKM

@rushmere3d Yep, my PC's IP is 192.168.50.192, router is 192.168.50.1.

markz

@lkm traditionally one of the LEDs on the ethernet shows presence (link-speed), so if you have no LEDs lit up then it's almost always a hardware problem. I hate to say it but I'd unplug one of your devices from the router and use that known-working cable and port and connect to that.

LKM

@markz Just tried that, no dice. none of the lights go on. I guess that means my Duet 2 Ethernet isn't working correctly. Looks like the Ethernet port is on a socketed daughterboard, I guess my best bet is to replace that, and see if it helps?

markz

@lkm I'm not one of the Duet3d folks so take it with a grain of salt but I'd guess yes. Do ensure your power supply has enough power first.

Phaedrux

@lkm said in Duet 2 Ethernet not connecting to network:

Looks like the Ethernet port is on a socketed daughterboard, I guess my best bet is to replace that, and see if it helps?

Can you power off, remove the ethernet daughter board, and re-seat it?

When and where did you purchase the Duet?

LKM

@phaedrux Re-seated the daughterboard, no change. I bought it from 3dware.ch on 20.03.2022 (just didn't have the time to install it until now).

Phaedrux

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

LKM

I've figured out what the problem was. It seems unlikely, but just in case anyone else has the same issue: I had a BLTouch connected to the board, but I had connected two of the wires to the wrong pins. This apparently caused the board to boot into a weird state where some features worked, and others didn't (e.g. connecting to the PC with USB and talking to the board with Pronterface still seemed to work fine, but the Ethernet port did not).

Connecting the BLTouch properly has fixed this issue.

Phaedrux

Thanks for the update. We probably should have asked you to ensure all other hardware was disconnected and starting from that state.