Third enertion vesc failure

Turnigy SK 6354 motor (245 Kv) - I can go up hills that cyclists get off their bikes to go up, and I’m 90Kg,

Not so weird in my experience. My mate (GodeatDog - on here) is on his third Esc I believe. I set the 1st one up for him (and electronics is my thing). Worked ok until a firmware update and then dead when performing the motor sensing test. Second one blew the DRV chip after a month or two for no apparent reason. He’s on his third now I think.

All wires correct gauge, good soldering, nowhere near over current. 10S, SK 6 series motor. Cooling fan on ESC. His would have high temp cut out kick in without a fan. I’ve the distinct impression the VESC in it’s current form is not up to hauling grown adults around. It’s just too delicate. At the very least , it should be robust. I’m on year three with the same car esc I started with. Same motor, same weight, same board, same wiring, but 6s instead of 10.

1 Like

There was a bug in the first edition of the latest firmware that caused the current ramp setting to multiply during write and was blowing DRV chips. That bug was just recently fixed.

TL;DR Summary from reading kingbing buys 3 VESC. Each one fails. Bug found in firmware causing current ramp setting to blow DRV chips, fixed.

Not to high jack thread. From my knowledge and following the VESC’s movements. The open source VESC is not a plug and play device yet as of today as one user mentioned in comments above. Partly requires some knowledge. It’s is still being improve by Vedder. Next iteration changes board design to separate layout into a high and low power sides with no DRV blowouts. This is an increase in reliability of device. Currently no ETA on when next iteration will be release.

1 Like

The battery wires are the original wires, i always duck-tape the motor (on top of teh heat shrink) and esc connectors as much as i can and my motor has the lowest kv for a sk3 which is 149KV. The VESCs always fail me during the ride, that being said I always connect the battery and the VESC correctly and if there was a short I wouldnt be able to ride for a bit before the VESC failure.

I havent protected the positive wire coming from the capacitor board for the first two VESCs but after a close inspection, the wires are not pierced and there arent any burned marks. However for extra protection I trimmed the pins with nail clippers on the third and fourth VESC, added a dab of hot glue and even with that i had a failure.

Ok, gotta be something else then

@Jinra has made a topic for that parameter error firmware bug.

Is it actually dangerous ? I don’t really know. When I saw the topic and checked mine, both VESC’s had these on 50 since I’ve played a lot with my settings to try and fix my battery cutoffs. It could be related to the cutoffs though…

if you flash newest firmware it fixes the bug. Not sure how dangerous it is but I’ve seen a couple blown drvs with high max current ramp steps. I think it dictates how to ramp up current when throttling.

Whats the latest version?

still 2.18 but with bug fixes. get it at VESC.net.au

I have my original hw4.7 VESC on my GF’s Vanguard build - going strong now since July 2015.

Still running fw 1.13 (if it ain’t broke…) - and BLDC not FOC, on 6 or 8s.

1 Like

do I hear longer? going once. going twice… but does she really ride much.

1 Like

She rides when i ride, and i’ve ridden it when she’s not able to. If i go out w/ friends or visiting guests i ride hers and they ride my Marbel. (friendly mode for beginners is nice)

Not a huge # of miles, but gets ridden pretty regularly still.

I’m very surprised that yours are still alive! That parameter is responsible to limit the power that hits the components. Aka, we ramp it up soft and don’t hit it in the face with a sledgehammer. If I recall right it is increase in amp per hertz. 50A is huge!

I agree, but that makes me wonder if it was just a visual bug, not actually being set until you hit the apply button in the advanced tab. (model-view-controller programming logic)

2 enertion vescs - no issues. BLDC motor detect, slight adjustment on brakes. FTR

I checked your settings and your max battery setting is very high. Try it with 25 at the beginning. When you test the motor on the bench then use the current to spin the motor and not the rpm. Also your battery cutoff start and end is too low. When you have a 10s battery then set it at least to 32v start and 30v end. Maybe the vesc gets killed when those numbers are too low because it can’t shut down the vesc when you shut off the power (caps still have some power left) . But that is a very wild guess.

And please post a Screenshot of the motor advanced tab and the application tabs.

I’d say that probably 2 items having the same failure could conceivably be a coincidence but 3? No, something’s either wrong with the set up or something’s shorting somewhere. Imo :grinning:

1 Like

Wire length to the esc from battery has also been a issue known to blow drvs. You want it short as possible. The longer it is the more it is prone to voltage spikes that blow the drv. http://www.rcgroups.com/forums/showthread.php?t=952523