So far I have repaired three VESC6 that have failed for various reasons. Here is what went wrong and how to prevent similar failures. I will update this thread if I repair more VESCs that have failed for different reasons.
Dead MCU
I got two VESCs where the STM32F4 had died. The reason was that the ADC inputs for an analog throttle have been connected in parallel. When VESCs are connected to the same battery there will be a voltage differential between them under load due do inductance and resistance in the cables. This voltage differential can reach quite high values and the MCU pins are very sensitive to that. Negative one volt is sure to kill the input and short the whole MCU. The PPM input is slightly less sensitive to this than the other pins as it has a low-pass filter, but it still is a bad idea (the VESC4 had a slower PPM filter and was slightly less sensitive). The CAN-bus can handle around +-60V difference, which is why it should be used on a multi-VESC setup. The CAN-bus also provides other advantages such as cruise control with several motors and traction control.
Solution: Always use the CAN bus to connect VESCs in parallel and set up the apps accordingly. Never connect the other inputs in parallel in VESCs that are connected to the same battery.
Dead voltage regulator
One of the VESCs that I repaired had a dead 3.3v regulator. One way to kill the regulator is to feed it backwards with a 3.3v source, which has happened to me a few times when connecting a programmer.
Solution: Never feed the 3.3v net with voltage, only current draw is allowed. If you, for example, have a stlink v2 from ebay that outputs 3.3v on a pin then don't connect that pin - power the VESC from the input while the programmer is connected.
The alternative is to have two separate batteries, and have the VESCs be completely separate except for the ground-and-ananlog signal. (ground-analog-3V3 on one VESC, ground-analog on the second).
Would a $0.05 bat54 connected between 5V (kathode) and 3.3V (anode) work to prevent this?
(there is a typo in the subject for -> far).
Yes, that should also work.
I think a diode could help to prevent reverse voltage, but 0.8V drop at 3.3v is a bit much.
Oh, no not like that. I mean: The regulator probably fails due to the 5V line (its input) being lower than the 3.3V line. So if you put a diode there so that this will not happen, the regulator will survive.
Have had canbus failure on my slave vesc. Unlike vesc 4.12, this vesc still powers up and has been reconfigured to run via ppm. Am running with a split ppm signal for now. Dual vesc 6 canbus 12s trampa dual mtb
So using PPM input (from the same autopilot) on 4 VESC for a multicopter is a bad idea? One single battery powers everything.
As with all other escs, just cut the red wire on all but one of the ppm cables. So the 5v power only comes from one VESC.
Don't do that! Y ppm causes ground loops, even if you cut the voltage supply. These loops can kill a Vesc 6 pretty fast. HW 4 designs can tolerate ground loops better, and most of them survive it. Its still no good idea to use Y ppm. Always CAN. HW 4 wants to be powered up simultaniously using CAN. Otherwise you can fry your CAN chip. Just make sure they run of the same power source and you won't have any issues. Vesc 6 can tolerate to be switched on individually while being connected via CAN bus cable.
Only connect CAN L and Can H, GND and 5V are unconnected.
Can anyone tell me why both can chips blew while riding? I have 2 fsesc4.12 connected in parallel with a 10s3p Samsung 40t battery pack, but when I was using one fsesc it was working fine. But as soon as I turned the slave fsesc on and rode it a bit, didn't even go hard. I weigh 155ib and I was probably going 5 miles an hour
Jb island
You didn't provide any details how the controllers were connected, and chances are that would provide a clue why they blew up.
NextGen FOC High voltage 144v/34s, 30kw (https://vesc-project.com/node/1477)
Jb island
But the negative on one side became disconnected
Jb island
Hi Ben. So I have a question. I have 2 single 4.12 on can bus to run dual, off of 1 10s3p battery using inr21700 40-t cells. I had a blown vp232 ic on both vesc, but I was able to replace those. So when I turn the vesc on the transmitter won't send commands to spin the motors, the remote will be all fine except for the joy stick for accel/ brk/decel. But I mixed up the Bluetooth module and now I'm not getting 5v on the uart port. Could you help give me an idea on what the most likely cause is
Jb island
While I was riding, my skateboard suddenly shut off. I assumed something might of hit the power button, but when I turned it on the vesc made a popping noise and the smell of burnt plastic and smoke started coming through the enclosure. Just wondering if you have an idea what might of happened? I have a FocBox Tenka vesc with hub motors and lipo batteries. I just finished the build a few days ago and in all my tests it was riding fine until now.
Thx :)
wich hubs ?
This is the VESC 6 thread. The Tenka is a third party product and not a VESC. It is VESC software compatible and it looks like it is Unity in a cheaper housing and with less features.
Hi .... I had connected two vesc from the same battery as soon as switched on the power supply the vesc led didn't show up. And when checked there was continuity between 3.3v and gnd. any suggestion how to fix the issue??
Needs repair. STM or 3.3V regulator is short.
regulator as in you are saying DRV???
The 3.3V regulator, outputting 3.3V for the processor and other stuff.
Hello!
My friends, it looks like I fried two dual esc 6 today by connecting them to one battery.
As a result, on one esc 6 dual
at the PPM output I observed 48v and the second esc 6 dual starts and turns off after a short time..(
Tell me what to do, I have 4 motors that I want to connect to two esc dual, is there any solution with the ability to connect from one battery?
And what could burn those escs that today were connected to the same battery.
Thank you all in advance for your time, help and your advice on how I should be!
Alex