Duet 2 Ethernet- seems to be doa
-
Hey all! I am a new owner of a E3D toolchanger that I ordered with a Duet 2 Ethernet controller and Duex 5 expansion board. I have gone thru the setup via usb on YAT with M552 S1 P0.0.0.0 which should enable networking and direct it to allow dhcp, but I am unable to get a connection via ethernet after doing this.When I send M552 I get a response of "Network is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0"
The status lights on the ethernet port itself never light up, and neither do the status lights on the corresponding port on my router. I have tried several cables with the same results.
I have also updated the firmware to 3.4.5 and saw no change in behavior.
What are some good steps to troubleshoot this further?
At this point it feels like my ethernet board is doa. It does have some weird crusties on it around the solder joints for the header, but I just received it new from E3D so IDK what that is about. I attached a picture to attempt to show that weirdness.I'd greatly appreciate any insight into this. Thanks! - Cody
-
Here is some more data from the terminal with a m115 , m552 and m122
m115 FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet Ethernet 1.02 or later + DueX5v0.11 FIRMWARE_DATE: 2022-11-30 19:36:12 ok m552 Network is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0 ok m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet Ethernet 1.02 or later + DueX5v0.11 Board ID: 0JD0M-9X6JA-JUNSS-6J9F0-3SJ6L-TVLMT Used output buffers: 1 of 26 (1 max) === RTOS === Static ram: 23836 Dynamic ram: 73212 of which 0 recycled Never used RAM 15032, free system stack 193 words Tasks: NETWORK(ready,13.2%,549) HEAT(notifyWait,0.0%,344) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,85.7%,464) IDLE(ready,1.0%,30), total 100.0% Owned mutexes: USB(MAIN) === Platform === Last reset 00:01:12 ago, cause: power up Last software reset time unknown, reason: User, GCodes spinning, available RAM 17344, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 11.4, current 16.5, max 16.6 Supply voltage: min 0.0, current 0.6, max 0.9, under voltage events: 0, over voltage events: 0, power good: no Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: ok, SG min n/a Driver 1: ok, SG min n/a Driver 2: ok, SG min n/a Driver 3: ok, SG min n/a Driver 4: ok, SG min n/a Driver 5: ok, SG min n/a Driver 6: ok, SG min n/a Driver 7: ok, SG min n/a Driver 8: ok, SG min n/a Driver 9: ok, SG min n/a Driver 10: Driver 11: Date/time: 1970-01-01 00:00:00 Cache data hit count 3015817839 Slowest loop: 1.36ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 9.2ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 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 USB is ready with "m122" in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 1, 0.83 reads/min === Network === Slowest loop: 0.26ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 0 of 8 Interface state establishingLink, link down ok -
Here is my config file that i got from E3Ds github for this setup. I cant find anything wrong with it regarding networking.
It has M552 S1 P0.0.0.0 ; Enable Networking and get IP address dynamically; Configuration file for Duet WiFi / Ethernet running RRF3 on E3D Tool Changer ; executed by the firmware on start-up ; General preferences M111 S0 ; Debugging off G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M555 P2 ; Set firmware compatibility to look like Marlin M667 S1 ; Select CoreXY mode ; Network M550 P"ToolChanger" ; Set machine name M552 S1 P0.0.0.0 ; Enable Networking and get IP address dynamically M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; Drive direction M569 P0 S0 ; Drive 0 X M569 P1 S0 ; Drive 1 Y M569 P2 S1 ; Drive 2 Z M569 P3 S0 ; Drive 3 E0 M569 P4 S0 ; Drive 4 E1 M569 P5 S1 ; Drive 5 E2 M569 P6 S1 ; Drive 6 E3 M569 P7 S0 ; Drive 7 COUPLER M569 P8 S0 ; Drive 8 UNUSED M569 P9 S0 ; Drive 9 UNUSED M584 X0 Y1 Z2 C7 E3:4:5:6 ; Apply custom drive mapping M208 X-35:328.5 Y-49:243 Z0:300 C-45:360 ; Set axis maxima & minima M92 X100 Y100 Z1600 C91.022 E834:834:834:834 ; Set steps per mm assuming x16 microstepping M350 E16:16:16:16 I1 ; Configure microstepping with interpolation M350 C16 I10 ; Configure microstepping without interpolation M350 X16 Y16 Z16 I1 ; Configure microstepping with interpolation M566 X400 Y400 Z8 C2 E2:2:2:2 ; Set maximum instantaneous speed changes (mm/min) M203 X35000 Y35000 Z1200 C5000 E5000:5000:5000:5000 ; Set maximum speeds (mm/min) M201 X6000 Y6000 Z400 C500 E2500:2500:2500:2500 ; Set accelerations (mm/s^2) M906 X1800 Y1800 Z1330 I30 ; Idle motion motors to 30% M906 E1000:1000:1000:1000 C500 I10 ; Idle extruder motors to 10% ; Endstops M574 X1 Y1 S3 ; Set X / Y endstop stall detection M574 C0 Z0 ; No C Z endstop ; Z probe M558 P8 C"zstop" H3 F360 I0 T20000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds G31 P200 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height M557 X10:290 Y20:180 S40 ; Define mesh grid ;Stall Detection M915 X Y S3 F0 H400 R4700 ; X / Y Axes ; Heaters M308 S0 P"bedtemp" Y"thermistor" A"Bed" T100000 B4138 C0 ; Set thermistor M950 H0 C"bedheat" T0 ; Bed heater M143 H0 S225 ; Set temperature limit for heater 0 to 225C M140 H0 ; Bed heater is heater 0 M308 S1 P"e0temp" Y"thermistor" A"T0" T100000 B4725 C7.06e-8 ; Set thermistor M950 H1 C"e0heat" T1 ; Extruder 0 heater M143 H1 S305 ; Set temperature limit for heater 1 to 300C M308 S2 P"e1temp" Y"thermistor" A"T1" T100000 B4725 C7.06e-8 ; Set thermistor M950 H2 C"e1heat" T2 ; Extruder 0 heater M143 H2 S305 ; Set temperature limit for heater 2 to 300C M308 S3 P"e2temp" Y"thermistor" A"T2" T100000 B4725 C7.06e-8 ; Set thermistor M950 H3 C"duex.e2heat" T3 ; Extruder 0 heater M143 H3 S305 ; Set temperature limit for heater 3 to 300C M308 S4 P"e3temp" Y"thermistor" A"T3" T100000 B4725 C7.06e-8 ; Set thermistor M950 H4 C"duex.e3heat" T4 ; Extruder 0 heater M143 H4 S305 ; Set temperature limit for heater 4 to 300C ; Tools M563 P0 S"T0" D0 H1 F2 ; Define tool 0 G10 P0 X0 Y0 Z0 ; Reset tool 0 axis offsets G10 P0 R0 S0 ; Reset initial tool 0 active and standby temperatures to 0C M563 P1 S"T1" D1 H2 F4 ; Define tool 1 G10 P1 X0 Y0 Z0 ; Reset tool 1 axis offsets G10 P1 R0 S0 ; Reset initial tool 1 active and standby temperatures to 0C M563 P2 S"T2" D2 H3 F6 ; Define tool 2 G10 P2 X0 Y0 Z0 ; Reset tool 2 axis offsets G10 P2 R0 S0 ; Reset initial tool 2 active and standby temperatures to 0C M563 P3 S"T3" D3 H4 F8 ; Define tool 3 G10 P3 X0 Y0 Z0 ; Reset tool 3 axis offsets G10 P3 R0 S0 ; Reset initial tool 3 active and standby temperatures to 0C ; Fans M950 F1 C"fan1" M950 F2 C"fan2" M950 F3 C"duex.fan3" M950 F4 C"duex.fan4" M950 F5 C"duex.fan5" M950 F6 C"duex.fan6" M950 F7 C"duex.fan7" M950 F8 C"duex.fan8" M106 P1 S255 H1 T70 ; T0 HE M106 P2 S0 ; T0 PCF M106 P3 S255 H2 T70 ; T1 HE M106 P4 S0 ; T1 PCF M106 P5 S255 H3 T70 ; T2 HE M106 P6 S0 ; T2 PCF M106 P7 S255 H4 T70 ; T3 HE M106 P8 S0 ; T3 PCF M593 F42.2 ; cancel ringing at 42.2Hz (https://forum.e3d-online.com/threads/accelerometer-and-resonance-measurements-of-the-motion-system.3445/) ;M376 H15 ; bed compensation taper ;tool offsets ; !ESTIMATED! offsets for: ; V6-tool: X-9 Y39 Z-5 ; Volcano-tool: X-9 Y39 Z-13.5 ; Hemera-tool: X20 Y43.5 Z-6 G10 P0 X20 Y43.5 Z-6 ; T0 G10 P1 X20 Y43.5 Z-6 ; T1 G10 P2 X20 Y43.5 Z-6 ; T2 G10 P3 X20 Y43.5 Z-6 ; T3 ;M572 D0 S0.2 ; pressure advance T0 ;M572 D1 S0.2 ; pressure advance T1 ;M572 D2 S0.2 ; pressure advance T2 ;M572 D3 S0.2 ; pressure advance T3 M575 P1 S1 B57600 ; Enable LCD G29 S2 ; disable mesh T-1 ; deselect tools M501 ; load config-override.g -
I could have titled my post more clearly last night, I apologize for that. My only issue is potentially with the ethernet module, I dont think anything is wrong with the Duet2 itself.
The Duet 2 seems to be working fine locally. I have a PanelDue 7i that initializes and lets me home my axis and jog them correctly. I just need to get my ethernet working so I can get on the DWC and continue commissioning my new printer.
-
Dang it!! I found an old post about certain routers not playing nicely so I tried hooking to a different device and it works fine. I feel dumb. I guess that means its time for a new router?
FWIW the router at fault is a Linksys EA3500. -
undefined codymnelson marked this topic as a question
-
undefined codymnelson has marked this topic as solved
-
@codymnelson could it be that the router's ethernet ports are set to not auto cross over when required? if you can configure the router in anyway have a look if there is a setting for MDI-MDIX or similar. Most modern (last 20 years!) routers and switches should have that option. If it is this issue, and if they cant be set to auto, then another possibility would be to use a cross over ethernet cable.
