Duet 2 WIFI "Over Temperature Shutdown..."
-
Please post the contents of your config.g
Also post the results of M122.Driver0 is your X axis? If you disconnect the motor (while the board is powered off) and leave it disconnected does it still produce the same error message?
Does the driver chip itself get hot?
Does there appear to be any damage to the driver chip? Can you post a photo?
-
Hi Phaedrux,
Thank you for your reply.
Here is the config.g file.
[0_1604607233790_config.g](Uploading 100%)
Yes, the driver 0 was X axis.I disconnect all cables from the board since the issue.
After rewiring them again, I will test the board as your points soon and update here again.
Thank you. -
Your upload didn't finish. Please copy and paste the text.
-
Uploading keep failing.
Here is the full text of the config file.
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Fri Oct 23 2020 17:13:35 GMT-0400 (Eastern Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"3DPrinter1" ; set printer name
M669 K1 ; select CoreXY mode; Network
M551 P"Hyunu2003" ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P4 S1 ; physical drive 4 goes forwards
M584 X0 Y1 Z2 E4 ; set drive mapping
M350 X1 Y1 Z1 E4 I0 ; configure microstepping without interpolation
M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X1500 Y1500 Z800 E1500 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X210 Y210 Z200 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop; Z-Probe
M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:195 Y15:195 S20 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue -
@obligor said in Duet 2 WIFI "Over Temperature Shutdown...":
M350 X1 Y1 Z1 E4 I0 ; configure microstepping without interpolation
M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mmThis is a very unusual microstepping configuration and doesn't seem to match your steps per mm settings at all.
Why not use x16 with interpolation for all motors?
What are your motors actually?
-
It was just a test setting for trying to understand the parameters.
Do you think it was the reason for the issue and it will be okay if I change it to proper value?
I really appreciate your support! -
@Phaedrux said in Duet 2 WIFI "Over Temperature Shutdown...":
Driver0 is your X axis? If you disconnect the motor (while the board is powered off) and leave it disconnected does it still produce the same error message?
Does the driver chip itself get hot?
Does there appear to be any damage to the driver chip? Can you post a photo? -
@Phaedrux
Sorry for taking a long time. There was a another urgent project.
I checked what you were asking.
Driver0 is X-axis.
I have the same error message when I connected the motor or not connected.
The middle chip among 5 chips is very hot, but the others are just warm.
I can see the burn mark on the chip which is hot. Please see the picture that I attached. I put an arrow sign on the burn area.
I look forward to your advice.
Thank you. -
Next question is likely when and where the board was purchased and if you've tested the old motor and wiring for short circuits.
Driver is damaged and driver or board will need to be replaced to use it; alternatively if E1 driver is unused you could remap X to use E1 driver (after making sure the wiring and motor is not faulty)
-
@bearer
I purchased it from Filastruder.
I connected wires and motors as soon as I received the board and then I got the error signs when I changed Amp to 1.5A. I'm sure it is in the safe range as the board instruction but the chip looks burned.
I used this motor.
https://www.ebay.com/itm/US-Ship-Nema-17-Stepper-Motor-Bipolar-84oz-in-59Ncm-CNC-3D-Printer-Reprap-Robot-/231514870097?hash=item35e75c9151:g:FQkAAOSwPcVVjqpo
The motor is still working fine with the other printer. -
When was it purchased?
-
@Phaedrux
I purchased it on October 21, 2020, from Filastruder.
I run the board on October 23, 2020, and the issue happened that day.
So, I posted the first posting on this thread the same day. -
@obligor Please contact Filastruder and initiate a warranty exchange. Include a link to this thread as authorization. It would appear you've had a premature failure on that driver chip.
-
@Phaedrux
Thank you. I will contact Filastruder.
