Duet 2 ethernet connection

Veti

while connected with usb send M552 to see the assigned ip.

usas12

yes done that, it does not assign an IP. comes back with
" Network is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0"
and does not update from there, doesn't get detected by the router

Veti

can you manually assign an ip and test.
like this but adjusted for your network

M552 P192.168.1.20 S1 ; enable network and set IP address
M553 P255.255.255.0 ; set netmask
M554 P192.168.1.254 ; set gateway

usas12

@Veti said in Duet 2 ethernet connection:

P192.168.1.20

SENT: M552 P192.168.1.20 S1
READ: ok
SENT: M553 P255.255.255.0
READ: ok
SENT: M554 P192.168.1.254
READ: ok
SENT: m522
READ: M522 command is not supported
READ: ok
SENT: m554
READ: Gateway: 192.168.1.254
READ: ok
SENT: m552
READ: Network is enabled, configured IP address: 192.168.1.20, actual IP address: 192.168.1.20
READ: ok

Still no connection detected by the router. Nothing in the browser.
As i mentioned in the first post. The board is responding to commands via a usb connection just fine. But nothing is passing via Ethernet. The router is not recognizing it and the pc doesn't either if i connect it directly via Ethernet

Veti

whats the ip of your pc? just checking

usas12

@Veti 192.168.1.1

Veti

can you connect the duet directly to the pc and check with those settings?

usas12

@Veti Nothing detected same as before

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet Ethernet 1.02 or later + DueX5 FIRMWARE_DATE: 2020-02-09b1

A Former User

Long shot, but check the MAC address with M540? (could also try setting one if comes back all 1s or 0s, but make sure the U/L bit is high (2nd digit of first octet being 2, 6, A or E iirc) see https://duet3d.dozuki.com/Wiki/Gcode#Section_M540_Set_MAC_address for syntax)

If the MAC address looks good then I guess Wireshark to sniff the DHCP negotiation is the simplest way of telling which side is failing. (but as only parts of the traffic is broadcast the best would be to run tcpdump on the rotuer if its running OpenWRT or similar firmware. A managed switch to mirror the traffic is also a good option. Lastly having only your computer and the Duet on a switch that is otherwise not connected and running both Wireshark and DHCP server on your computer before powering up the Duet might give you some insight still)

usas12

MAC: be:63:50:4b:52:38 ???

A Former User

@usas12 said in Duet 2 ethernet connection:

be:63:50:4b:52:38

its already an locally administered address, but otherwise looks valid - it could be the router is refusing to serve a local address but I think that would be a bug in the router.

usas12

@bearer I have other devices here (not currently connected) when I connect them the router sets an IP no problems. It's just the duet that's having the problem

usas12

SOLVED, ran it through a switch and detected just fine. Also updated firmware but doubt that was it