Cytron 13A, 5-30V Single DC Motor Controller burned?

I was testing " Cytron 13A, 5-30V Single DC Motor Controller" using on board buttons, with 12V DC motor with no load. All worked fine , but suddenly the power light on the controller went off and it smelled burned. Motor controller was connected to li-ion battery pack with Vout=15V and maximum output current = 20A. The motor has stall current = 7A, so i don’t understand how it could get damaged by that.
Is it something i don’t understand or is it something else that could damage the controller?

Controller: https://www.robotshop.com/en/cytron-13a-5-30v-single-dc-motor-controller.html
Motor: https://www.robotshop.com/en/12v-dc-motor-251rpm-encoder.html

@dawik98 Can you spot anywhere the smoke may have come from to see which component burnt? If you do, can you provide a clear photo? You’re right that the battery should have been able to supply the necessary current, and the motor controller should have had no problem. Perhaps there was a short circuit somewhere (something metallic somehow landed on the controller?). You may have removed the plastic connector from the gear motor - could one of the other wires have contacted something?

When it happend i was holding the controller in my hand, that might have been a bit sweaty. I think its only way it could get shorten circuit.


I have a picture where i marked area that is getting hot quickest but i don’t have one component that is smoking.

That area is the for voltage regulation and yes, ti will get toasty, but shouldn’t burn. Can’t (evidently) spot anywhere on the board which looks burnt. Try to re-wire it and use the buttons to test?

When I connect the power-supply(battery) the power light turns a bit on then fades away. Then the marked area gets really hot, so I dont want to connect motor to it.

Have you tried contacting Cytron directly?

I see that their warranty is 6 months only.

I’m not sure it can be considered under warranty depending on how many times you have used the product.

I bought it quite a while ago so i guess it is too late anyway. :frowning:

You could still contact Cytron direclty and see if they can repair the product. https://www.cytron.io/support