drivers nt responding after spark

ageis

I don't know what happened.I just heated up my hotend and bed then started a print.
All of a sudden there was a spark. Then dwc reported driver 2 was shorted to gnd.
Now all the three drivers won't respond. Everything else seem fine.
I do see `so insulation damage on the right z axis motor which is connected to driver 2.

But i am pretty sure the spark was on the left. but no insulation damage on the left z axis motor. God damnit.

o_lampe

@ageis The shortcut on one motor probably caused a negative voltage spike across the board, which is way more distructive than overcurrent should be.
Some forum members have succesfully replaced drivers or MosFETs, but IMHO it's a gamble.

ageis

@o_lampe
I am up for he challenge.

Can anyone tell me where to start fixing this board?

ageis

@ageis
I keep getting an error saying phase A and phase B is shorted to gnd on driver 2 but I can't find a short with my multimeter. I tested between both phases and gnd with the motors plugged in.

The fact I am getting this error makes me think that the spi bus is still alive right? If so then it could be the drivers?

ageis

@o_lampe said in drivers nt responding after spark:

@ageis The shortcut on one motor probably caused a negative voltage spike across the board, which is way more distructive than overcurrent should be.
Some forum members have succesfully replaced drivers or MosFETs, but IMHO it's a gamble.

Also us Chinese love gambling. Just visit the casino in Manchester chinatown

dc42

@ageis said in drivers nt responding after spark:

I keep getting an error saying phase A and phase B is shorted to gnd on driver 2 but I can't find a short with my multimeter.

If a driver is blown or for some other reason it doesn't respond to the SPI message, then typically all the error bits are flagged as active, i.e. short to GND, short to VS, phases A and B not connected, and more.

Which Duet is it, and when/where did you purchase it? Does the Driver 2 chip (or any component around it) appear damaged?

You may be able to disable that driver (including reports from it) using the R-1 option of M569.

ageis

@ageis ok am stumped. I am getting an over temperature error from driver 2 but driver is no longer on the board. What? who is talking to the microcontroller

Is driver 2 not the one with the two connectors ?

dc42

@ageis said in drivers nt responding after spark:

Is driver 2 not the one with the two connectors ?

Yes if it's a Duet 2. In which case, with the driver chip missing you will see a lot of spurious errors from it. Use M569 P2 R-1 to disable reports from that driver; or fit a new TMC2660C driver chip if you need all 5 drivers.

ageis

@dc42
I have replaced my z axis driver and the error message has gone away. I presume this means it's properly communicating with the micro? The z axis motor driver was definitely dead because it's got a small pin hole in the ic. I don't get any similar errors on other drivers.

Despite replacing the ic I still can't get any of the axis to move. This includes the z axis as well which has a new driver.

So what could be going on?

droftarts

@ageis please post a good, in focus picture of the Z driver and the area around it, so we can check your soldering. Also please send M122 and post the response, post your config.g, and the commands you’re sending to try and move the motors.

Ian

dc42

@ageis if all the drivers are disabled then perhaps the Enable signal from the MCU isn't getting to them?