Vesc power loss after 2min

Hello, First my setup: Motor: 6374 192kv single VESC: Vedder 4.xx Battery: 10s4p Diy 20A/cell Wheel: 83mm Gears: 12/36

I finished my build 1 month ago, but the skate has lost power immidiatly after starting. I saw that the vesc is hovering always around 105-107 degrees (BLDC tool) so i turned it up to max 120C°, lowered battery max to 20A and put some heatsinks on. Still same problem after first 20meters. Now i changed the gear to 12/36 but it still only lasts to 30-50m untill it looses power and after 100m it had no power at all. What can I do? Motor max is 40 Voltage cutoff is ok at 57_34_32 Motor detection and test was ok too.

I am around 100kg and I tested on flat ground. I am pretty sure the vesc is overheating, but that should not be with this gearing. The Motor never got hot by touch and neighter the Vesc. Also i never shorted the motor wires.

This is even before use?

Where is the vesc from? I heard a while ago about a bad batch of vescs that had the problem with temperature being insanely high eventhough not used.

Vesc is from diyelectricskateboard. Yes it was from start. I could only use itbwith remote if i set max temp from 100 to 120.

Ok, Guy I know including one other thread got a bad batch(from what I heard) from there with temperature problems. When did u order it ?`

@hannesr Same problem as you had on your Diy Vesc?

I ordered it on the 10/03/17 from the US. Are this the sames

Connect it to BLDC tool, run real-time detection and see if you can duplicate the issue? Then go to terminal and type in “faults” (iirc) - to see what is going on specifically.


In a video which vedder showed a comparison of the VESC v6 and a VESC v4.12, he showed that the v4 VESC can do 27 amps continuous before it will start to rise in temperature uncontrollably. Basically, if your pumping less than 27 amps continuous, the VESC should not being having heat issues. (Knock a few amps off if you don’t have good airflow, but also add a few for the heatsink)

Have you modified the firmware?

Another idea, it could be a bad temp sensor. If you have any laser thermometers, I would suggest double checking that the FETs are actually at the temperature that the VESC claims they are. The temp sensor is on the 3rd FET between the FET and UART port.

Either way, I would suggest sending it back to DIY if you can cause it sounds fishy. My (chaka) VESCs sits at around 94-95 degrees Fahrenheit with 20 amps max going through each vesc. When I first turn it on, it sits at around 70-75 degrees (room temperature). I can do 20 con. with heatsinks and no ventilation, without issue. And I run 4 together.

1 Like

@TheManShaker please contact @torqueboards, I’m pretty sure he know about those issue

@evoheyax and @sl33py it has been confirm a few time that DIY got a bad batch of VESC… the problem is most likely to be hardware.

ahhh, I thought it was likely a temp sensor issue.

Glad to see Torqueboards stepping up, owning the problem, and fixing it! Great Work!

I think that was about the time span he ordered his aswell, Contact Diyelectric and ask. It most likely seem to be an unlucky batch that causes your problem.

I’ll contact them. Thanl you for all the help.

1 Like

I baught a new Vesc and did set it up. It’s working now. It was the Mosfets fault.

Today (the second day i took out the board) my board blocked completly at full speed and sent me flying twice. I checked the remote, but it was still.connected. what can I do? I don’t trust the board anymore…

Sounds like your remote isn’t binded correctly. When the receiver looses connection to the remote then it uses a default pulse width. You can change that default pulse width during the binding process. First you should test it by watching the ppm signal when you turn the remote off. When this goes way below 50% then it is braking when it looses the connection. To fix this just add the bind cable to the receiver and remove the bind cable again while leaving the throttle in the idle position. Then the receiver knows that it should send this signal when it looses the connection.

Well there’s your problem. Ordering VESCs from the future has been shown to corrupt the hardware. Something must be broken with the time-traveler. Ask Marty

Damn, i got 88mph mixed up with km/h. Ill try again. Btw, i´m European, so it was 10th March 2017.

I´ll try tomorrow. Thx!

That fixed my Problem. It was binded correctly, but I tightend the screw on the remote and on idle position it sent 59%. Just loosen the screw back to 50%. It‘s crazy fast now!