Duet2 Ethernet Diag LED is always on, no response from terminal
-
I recently got to replace my heat sensors, after doing so I turned on my Printer, but the screen kept saying "Connecting", and I noticed that even tho the ethernet wire is plugged in the green and yellow led are off. I tried plugging it into my laptop directly, but It didn't even find its serial port.
I disconnected everything and hooked it into my pc with a fresh wire, I saw it being detected, but after sending M115 to the board there was no response. I hooked the sd directly to the pc with an adapter and everything there was as usual. I don't know what's wrong, can you please help me?
Config.g:;Generated by Modix - 2.0 ;Modix Big-60, Duet Board, Dual Printhead ; Configuration file for Duet WiFi (firmware version 3.3) ; General preferences_________________________________________________________ G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M111 S0 ; Debug off M555 P2 ; Set output to look like Marlin M575 P1 B57600 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue) ; Network_____________________________________________________________________ M550 P"Misha" ; set printer name ;M551 P"MODIX3D" ; Set password (optional) M552 S1 ; enable network M552 P0.0.0.0 ; Uncomment this command for using Duet Ethernet board M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives_________________________________________________________________________ ;Main board_________________________________________________________ M569 P0 S0 ; Physical drive 0 goes forwards. X-Axis. M569 P1 S1 ; Physical drive 1 goes backwards. Y-Axis. M569 P2 S0 ; Physical drive 2 goes backwards. Z-Axis. M569 P3 S1 ; Physical drive 3 goes forwards. E0-Extruder. M569 P4 S0 ; Physical drive 4 goes backwards. E1-Extruder. ;Settings_________________________________________________________ M584 X0 Y1 Z2 E3:4 P3 ; Driver mapping ;___________________________________________________________________ M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation M92 X200.00 Y100.00 Z2000.00 E418.500:418.500 ; Set steps per mm M566 X240 Y360 Z30.00 E120.00:120.00 P1 ; Set maximum instantaneous speed changes (mm/min) M203 X9000.00 Y9000.00 Z360.00 E1200.00:1200.00 ; Set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z120.00 E250.00:250.00 ; Set accelerations (mm/s^2) M204 P500 ; Set print and travel accelerations (mm/s^2) M906 X1800.00 Y1800.00 Z1800.00 E1200.00:1200.00 I40 ; Set motor currents (mA) and motor idle factor in per cent M84 S60 X Y E0 E1 ; Set idle timeout - one minute ; Axis Limits M208 X0 Y0 Z-1 S1 ; set axis minima M208 X600 Y600 Z660 S0 ; set axis maxima ; Endstops M574 X1 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y1 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop ; Z-Probe M558 P9 C"^zprobe.in" H5 F120 T6000 A1 R0.7 ; set Z probe type to bltouch and the dive height + speeds M950 S0 C"exp.heater3" ; set probe pin G31 P500 X-14 Y21 Z2.967 ; set Z probe trigger value, offset and trigger height M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters M557 X-14:584.5 Y21:619.5 S66.5 ; define mesh grid M376 H10 ; Height (mm) over which to taper off the bed compensation ; Heaters___________________________________________________________ M140 H-1 ; disable heated bed (overrides default heater mapping) ;E0_________________________________________________________________ M308 S0 P"e0temp" Y"thermistor" T100000 B4725 ; configure sensor 0 as thermistor on pin e0temp M950 H0 C"e0heat" T0 ; create nozzle heater output on e0heat and map it to sensor 0 ;M307 H0 B0 S1.00 ; PID calibration M143 H0 S285 ; set temperature limit for heater 0 to 280C ;E1_________________________________________________________________ M308 S1 P"e1temp" Y"thermistor" T100000 B4725 ; configure sensor 1 as thermistor on pin e1temp M950 H1 C"e1heat" T1 ; create nozzle heater output on e1heat and map it to sensor 1 ;M307 H1 B0 S1.00 ; PID calibration M143 H1 S285 ; set temperature limit for heater 1 to 280C ; Fans & LED______________________________________________________________ M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S0 H-1 ; set fan 1 value. M950 F2 C"fan2" Q500 ; create LED on pin fan2 and set its frequency M106 P2 S0 H-1 ; Disable fan channel for LED ; Tools______________________________________________________________ ;T0_________________________________________________________________ M563 P0 S"E0 Primary" D0 H0 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S210 ; set initial tool 0 active and standby temperatures to 0C ;T1_________________________________________________________________ M563 P1 S"E1 Secondary" D1 H1 F1 ; define tool 1 G10 P1 X0 Y49 Z0 ; set tool 1 axis offsets G10 P1 R0 S210 ; set initial tool 1 active and standby temperatures to 0C ; Custom settings__________________________________________________ M591 D0 P1 C"e0stop" S1 ; Regular filament sensor for E0 M591 D1 P1 C"e1stop" S1 ; Regular filament sensor for E1 ; Automatic power saving____________________________________________ M911 S22.5 R29.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss. Power Failure Pause -
undefined Juris marked this topic as a question 6 Jul 2022, 10:00
-
@juris If the diag light is always on, most likely the firmware has been erased. See https://docs.duet3d.com/User_manual/Troubleshooting/Duet_wont_respond
Flash the firmware using this method: https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2
Ian
-
@droftarts I checked the sd card and everything was still there. Or is the firmware stored on the board itself?
-
@juris said in Duet2 Ethernet Diag LED is always on, no response from terminal:
Or is the firmware stored on the board itself?
Yes, the firmware is flashed to the non-volatile memory on the Duet, so it can run. A copy of the firmware is usually stored on the SD card, so you can update the Duet from the SD card. However, you need firmware on the Duet to be able to do this.
Most likely, you either shorted the 'ERASE' pins on the board (if you have a newer Duet), or pressed the 'ERASE' button on the edge of the board (if you have an older Duet). This erases the firmware on the Duet when you next restart.
If you post your config.g file from the SD card, we can have a pretty good guess as to which firmware you need to flash to the Duet, as you may be on an older version.Edit: Sorry, I realise you posted your config.g in the first post. It looks like you have a config.g for RepRapFirmware v3.3, so you should be fine to flash the latest version: https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.1
Firmware flashing instructions: https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2
Ian
-
@droftarts I cant understand which one I have to download since they all show the same release date
The upper one? -
@droftarts Alr so I did everything as the instructions said (I used Duet2Firmware_SBC.bin), except the part where I could understand if I was in the developer mode due to the LED always being on.
However, after I put the sd back in, the light Is still on. I will now try connecting to it with the YAT terminal.update: it did not respond, however instead of Unkown Device, now in Device manager, it shows as USB serial device (COM5)
-
No you'd want Duet2CombinedFirmware.bin as per the chart here: https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#firmware-file-naming
-
@phaedrux Alr I got it responding, Il hook it up and update you guys on if its working