PSA: Remember to reset your max current ramp step when programming your VESC

I’ve downloaded BLDC tool for Mac fairly recently and the “Max Current Ramp Step” bug still seems to be present. For those unaware, when you read and write config on the motor configuration tab, the Max current ramp step field under “advanced” will multiply by 10. This can possibly be fatal to your VESC so remember to reset it whenever you write to motor configuration.

The default value is 0.04, however, if you set it to that and write it will change to 0.4 since it multiplies by 10, so set it to 0.004 and write config.

I’ve heard the issue was fixed, but i’m unsure as to where or what versions it’s fixed for. This information is accurate as of 5/30 (when I downloaded BLDC tool) off Jacob’s site ( for OSX firmware v2.18. I can’t confirm if this is happening on Linux/Windows.

EDIT: This issue is fixed on latest f/w revisions by @jacobbloy and @elkick. Not sure who else has updated f/w’s uploaded, but these two have confirmed bug-free versions. The version will still be 2.18 so you won’t know if you have a bug free version until you test it out. Information accurate as of 8/28/16


Is this only for mac?

windows confirm as well

thanks for the info

I compiled FW 2.18 for VESCs 4.10 - 4.12 as a standalone version, it’s tested but no guarantees though:


Ok, some more people tested it, the error is fixed and it works without any issues.


I was just checking this because of my battery cutoffs at startup. It could have been related.

Both my VESC’s had this setting at 50,000. (new one from you @elkick FW2.18) and my other enertion one which was at FW2.16. I’ve updated the enertion VESC to 2.18. Reading and writing the config on the enertion one at 2.18 still has this bug. The other vesc doesn’t have this.

It should not be there anymore if you use the above posted version. But i don’t understand, which of the updated VESCs is still showing the max. current step fault?

I started uploading the new version directly with STlink under Ubuntu a while ago, but I could have also missed a few. :slight_smile:

The one from enertion that wasn’t fried. So either the firmware 2.18 from jacob bloy still has the bug. Or firmware upload (no st-link yet) doesn’t work, but changes the firmware number to 2.18

Jacobs FW and BLDC tool folder is not yet updated and still has this bug.

You have to upload the exact firmware I linked above with any BLDC tool. The BLDC tool you are using for this doesn’t matter, the error is in the FW.

1 Like

Allright, thanks for clearing that out. I will flash your firmware tomorrow !

I have a couple of new scramboards vescs with the Max current issue. Does anyone have a working link for the bug free firmware??? The one posted above By @elkick IS not working. Thank you very much

Honestly, just get @Ackmaniac’s firmware. I know it’s free from that bug, and does does everything that the original firmware does, plus much more.