This is advice I saw from you early on in my time building my own boards (2017-2018ish), and well I’m a pansy so I’ve yet to ever put a board together that I’ve reached the limits on even with “significant headroom” profiles configured on them. By far and away the best advice here, less you’re in the hobby to “push it” why bother riding the edge of function?
Even one of my first boards is still being used by the guy I gave it to. Running a very modest 10s1p and one of flipsky’s first V6 dual-motor designs. As long as the ESC doesnt let out the magic smoke on the first start (anecdotally speaking) if you’re giving it headroom you’ll be fine.
I’ve got two still, been riding one tonight and it didn’t let me down. One caught fire following a DRV fault, but the other two still go good. Per kilometer though, my flipsky’s are still probably paying better dividends.
I like the stormcore in that they keep an odometer reading. The flipsky’s reset to 0km each time they’re used.
This is, in my view, the main issue with VESC. Not all VESC hardware has inherent flaws. Some VESC hardware is very impressive. But all VESC systems suffer from the endless VESC firmware and software pitfalls.
There should be no world in which a mis-click in the app results in a burned ESC and a broken collarbone. And yet that’s all too common.
VESC is a universal motor controller. That’s why it’s not “reliable” (pick whatever word you want) for esk8.
We need a fork (hardware and software) of vesc dedicated exclusively for esk8 (maybe exclusive to PEVs?). Until then we are just adapting this platform and it will lead to issues sometimes.
My most reliable PEVs are a onewheel that @TheBoardGarage built me that uses vesc. Onewheel vesc packages are really well developed and Mario knows his shit.
And my LaCroix 100D2, which was an over built ESC made specifically for ESK8 by Jeff Friesen who is a major contributor to the VESC codebase and changed a lot of it to make the stormcore. Coincidence? Idk lol. I just think this sport deserves better.