Vibrates motor and error hight temp driver 0

o_lampe

@Esteban I'd take a closer look to the driver itself. There might be a shortcut between pins or a bad solder joint.

oliof

In addition, I'd check if the issue persists moving a working motor to driver0, and moving the non working motor to another driver. If the issue sticks with driver0, @o_lampe points at the right tests, if the issue wanders when swapping motors between drivers, it's most likely the motor.

Esteban

@oliof
So after further checking, visually the driver has no particular soldering defect.

As for my motors, as mentioned above, they all work on the other drivers but only vibrate on driver 0...
I double-checked that my motors were 1.8deg and the program. Everything seems correct.

motor reference : 42HD2037-01

code :

 - M584 X0.0 Y0.1 Z0.2:0.4 ; set axis mapping
 - M350 X256 Y256 Z256 I0 ; configure microstepping without interpolation
 - M906 X1500 Y1500 Z1500 ; set axis driver currents
 - M92 X1600 Y1600 Z6400 ; configure steps per mm
 - M208 X0:350 Y0:350 Z0:450 ; set minimum and maximum axis limits
 - M566 X900 Y900 Z12 ; set maximum instantaneous speed changes (mm/min)
 - M203 X600000 Y600000 Z9000 ; set maximum speeds (mm/min)
 - M201 X5000 Y5000 Z250 ; set accelerations (mm/s^2)

oliof

@Esteban that's not your actual config.g, please share the file unmodified (also 256x microstepping is likely not useful, 16x or 32x will be sufficient for 3d printers).

Esteban

@oliof

config.g

I restarted my configuration and here it is.

But still the same problem.

All the axes work. The X axis motor works on the other drivers but not on 0.0.

The machine has never worked before, I'm just putting it together, and these are my first tests.

jay_s_uk

@Esteban when and where did you purchase the board?

Esteban

@jay_s_uk

Ten days ago at ED3

Phaedrux

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

Esteban

@Phaedrux

OK, thanks for your help anyway

Phaedrux

Yes, unfortunately it seems like the driver has failed and should be replaced under warranty.