That is strange, haven’t experienced it before. Maybe try installing this driver:
With some USB switching I finally manged to install fw5.0. And everything is working!!! Finally.
Thanks everyone for the help!
5 Likes
@Deodand can you talk to these limits as it relates to the Unity? What’s the max it’ll take for each? Does it matter, thinking of built-in protection circuits here?
1 Like
You need to set these limits in relation to what your battery can handle rather than the unity. Battery amps Max are the maximum limits that will be drawn from the battery. The motor currents are where the vesc converts higher voltage to lower voltage + higher amps at low speeds. Basically if you are going slower your vesc can push more amps to the motors for more torque whilst still adhering to the limitations set for the battery 
4 Likes
All hardware has limits, my battery can supply 390A constant, I’m merely asking how much of that can the Unity handle with the different parameters.
4 Likes
Just curious why there are multiple versions of different firmware with the same version number?
isn’t point of having a version number to stop this sort of confusion?
3 Likes
Because builds aren’t fully automated, and manually incrementing all the numbers nightly is a PITA and would cause large jumps in numbering schemes. The numbers also have to match between the tool and the firmware, and the tool needs a new config definition for each version it supports.
There are ways to make it all better, and its open source, so have at it
6 Likes
This is a fair point, unfortunately i dont have the know how to fix this and i appreciate that it would take time.
But these updates are patch / bug fix’s. They shouldn’t break anything in the tool so cant the tool just ignore the last digit?
It becomes much easier when you get bug reports like this :
6 Likes
Im aware of major/minor/patch it is a great scheme, you should implement it for the vesc tool.
Just make sure it also works for nightly builds while maintaining a stable channel.
6 Likes
Wish i had the experience for this.
2 Likes
Wanted to say, with 17 years app and database dev experience, versioning is a piece of cake. No reason why it couldn’t be implemented, and the tool to ignore the patch number.
2 Likes
Great, I look forward to your implementation!
5 Likes
Fuck off guys, don’t make a bigger deal out of it than it should be.
5 Likes
It’s very likely the ESC’s capabilities are limited by thermal measures and not by absolute current. The capability can probably vary a lot based on temperature, cooling, thermal mass, et cetera, and furthermore the ESC will throttle if it gets too hot, so in theory you should just set your battery limits and let the ESC throttle itself by temperature.
4 Likes
Well you don’t want the limits high enough to trigger an over current fault on the ESC. Or high enough to burn something before the ESC even reacts.
2 Likes
So @Deodand. If I was to install fw5 on my unity right now, where can I find the link to the latest build with the bugs fixed?
4 Likes
He also believes that his lipos also perform to the c rating on the label hahaha
If also he keen to put the latest firmware ony unity if most of the bugs are now ironed out.
@Deodand: Not sure if it’s 5.0 related but the “Timeout Break Current” option is not working as intended.
Vesc startup and no remote connected: breaking is on.
When I turn on the remote: breaking turns off.
But when I disconnect the remote again: breaking does not turn on.
Isn’t this the intention to have breaking turned on when there is no remote connection?
Are you in PPM ?
If so, and if the failsafe is set close to neutral, there is no way for the VESC to know that a drop out occured thus no break applied.