So with all that being said, what FW can be considered to be safe to use?
Without digging for 2016 reported bugs, 5.1 with duty cycle current limit start at 85% if your board can top out the speed limit
3 Likes
Sorry but I don’t understand what you mean by that 
I have a VESC 4.2 and 6.6. What FW would be the best to use?
1 Like
Use latest firmware. (That’s FW 5.1)
To mitigate the duty cycle limit bug / unintended feature, You want to set duty cycle current limit start to 85%, as @Athrx mentioned.
Then, if you’re using motors with temperature sensors, to mitigate the incorrect temperature filtering bug, you want to set your thermal limits to start at 75 degrees, end at 100, or maybe start at 85 degrees, end at 120. Basically you want the window between the 2 values to be larger than the default 15 degrees.
4 Likes
Triple point for duty cycle current limit start, NOT max duty cycle! Should be right under it
I say this because there have been people that stop reading after duty cycle and end up making their boards even more dangerous. If you need more guidance we’re in the noob questions thread to help
5 Likes
I’ve been bumping the duty cycle current limit start up from 85% by 1% each ride. 90% has given me no issues and I think I’m going to call it quits there since I have to be going ~45mph to hit that.
Every board is different, I had one that was having weird issues at 90%. Be careful and pad up when changing settings 
4 Likes
I just found out that my FSESC 6.6 is running on 3.62 haha.
There even is no such setting in the VESC tool like “duty cycle current limit start” for this version. It works fine for me since 1500km, I might just stick with it. I do not have motor thermistors so no promlems there.
1 Like
On escs that are by good qc or pure luck within very good tolerances you can probably leave it at 100%
On any 2 controllers that have even 0.1v readouts that get worse under load, one starts cutting out before the other and shit sucks
2 Likes
Been 2 years. anyone know if the list needs updating?
1 Like
Firmware 5.3 throws ABS_OC faults and cogs when full throttling your board with wheels in the air. Not really a big deal, it just freaks people out
1 Like
got a good link for that issue?
So this hasn’t been updated in a while.
I hear there are other concerns with firmware 5.3 but I don’t know what they are to list them. Anyone got details? links to discussions?
I just use 6.2 on everything nowadays. No problems
1 Like
i think 5.2 used to have this designation. 
still useful to document the known problems.
1 Like
All remaining versions are great now.
trying to exercise cunninghams law
To be fair, after my initial shitshow with fw6, i’ve been really happy with my 6.2 experience. Good experience with solos, and only a little so far but so far so good with dv6s
6.2 really has been my most trouble free vesc experience
1 Like
Firmware still flawed until vesc tool (on all platforms ) starts automatically reading settings when switching CAN devices imo.
1 Like
Knowing this bunch, you’re more likely to see Godwin’s law 
Having this issue on my shortie on 5.2.
Hadn’t ridden it much other than dog runs lately, but a spicier ride with a bud made this apparent.
Looking back, this probably caused a good crash I had couole years back.
Gonna go through all settings and most likely update FW.
1 Like
It’s is butt puckering to say the least.