Duet ethernet has no link
I have the same problem as in post https://forum.duet3d.com/topic/5938/duet-ethernet-is-not-working
When I plug in the ethernet cable, no led lights up on the ethernet board. The blue, green and red led on the system board are lit.
The ethernet board is mounted correctly and I can connect to the Duet over the USB port.
Network is enabled, configured IP address: 192.168.0.177, actual IP address: 192.168.0.177
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917DA-G4MS4-6J1DG-3S86L-98YBA
Used output buffers: 1 of 24 (2 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93140 of which 0 recycled
Exception stack ram used: 312
Never used ram: 11940
Tasks: NETWORK(ready,1972) HEAT(blocked,1236) MAIN(running,3756) IDLE(ready,160)
=== Platform ===
Last reset 00:00:35 ago, cause: reset button or watchdog
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11964 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 32.8, current 33.5, max 33.8
Supply voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 78590740
Slowest loop: 0.95ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is ready with “M122” in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.20ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
Interface state 2, link down
Dr_Ju_Ju last edited by
What is it plugged into ? a switch\hub or back to back computer ?
It is connected to a switch port.
Have you tried a different cable, and a different port on your Ethernet switch?
Dr_Ju_Ju last edited by
Make sure you aren't using a cross-over cable. Then try using some basic command line tools to test connectivity, i.e. can you ping the address you've set. If you get a response then try telnetting to the IP address \ port 80.
I am using a normal (not crossover) network cable on a working switch port. If I connect my Mac Book or a Windows PC with the same network cable to the same switch port, then everythin works. Both computers are connectoed to the network.
If I connect the duet controller to the same switch port nothing happens. No link, no network connection.
@rb2602 what if you connect the Duet to your notebook and use a fixed IP on the Duet and your laptop?