I recently updated my Stormcore firmware to V6.0, ran motor detection, etc and everything went ok. Was giving it a test on the bench before taking it for a ride and Initially both motors were running, but within seconds I think I heard a faint pop, one motor stopped and it smells like something got fried. Initially the power button was green, but the VESC couldn’t be turned off. I pulled the battery to power it off, then plugged the battery back in. Once powered again the power button was flashing red as well as a led on the VESC. At this stage I hooked up the VESC tool and saw that it was showing a fault “high offset current sensor”. Since then it’s been powered down again and can’t be turned back on with the on/off button. Not sure if it was due to the firmware upgrade, or possibly something else?
The only other change that I think was made was I had changed the motor current from 60 to 80 amps. I’m running 6374’s.
I’m guessing I’ll probably need a new one but want to work out what when wrong first.
I’ve managed to get it turned back on and cleared the faults. I can run motor detection on the 1st side of the VESC using either motor and it’s ok. The second side won’t run the motors in detection though. The power switch won’t turn the VESC off either. The light on the switch turns off momentarily but, the VESC itself remains powered and then the power switch light comes back on. The VESC itself is about a year old, but wasn’t installed until recently. I’ve only just finished the build and have barely ran the board. Everything was good until the firmware update though.
Swap motor and sensor cables from side to side on the esc and see if the same side of the esc fails (esc issue) or if the motor itself is failing (switches sides, motor issue)
Ok, so I just opened it up and I can see a couple of cooked component’s. Not sure what they are coz I’m not that smart lol. Id definitely caution anyone from updating this VESC to V6.0 though. I think at this stage I’m just going to purchase another VESC as I’m itching to try and complete the build, then try and have this one fixed if possible to use in a future build. Not sure if I should chance it with another Stormcore, or go with DV6 though.
Just to confuse things I did notice after the VESC blew that there was a screw from the motor mount support brace that had come loose and was obstructing/interfering with the belt from turning freely. I only ran the motors for maybe 10 seconds after the firmware update before the VESC went pop. So not sure if this could have caused anything to overload? It was the motor that was set to the same side of the VESC that burnt out, so it is a bit sus. I wouldn’t have thought that it was running for long enough to cause that sort of issue though…
Good question. I had only updated from 5.2 to 5.3 a couple of weeks ago. I was doing a final check of all my settings before giving it some proper ride time and the VESC tool notified that 5.3 was out of date. The change from 5.2 to 5.3 went well, so I thought why not.. My rookie brain failed to identify the pain and destruction that this could potentially unleash.
I was forced to do the update from 5.2 to 5.3 as the VESC tool wasn’t allowing a part of the setup without it. Not sure how you’re meant to set these things up if VESC tool forces this stuff. Not sure how to approach things if I buy a replacement Stormcore either. Feel like it’s going to get stuck in limbo until V6.0 is safe to use.
. My rookie brain failed to identify the pain and destruction that this could potentially unleash.