VESC 6.05 Warning, PSAs - READ THIS BEFORE UPGRADING

Announcements
1

Serious bugs in VESC v6.05 Firmware - DO NOT UPDATE UNTIL YOU READ THIS

PSA #1: Serious bug(s) in VESC App v6.05
PSA #2: Nosedive bug in UBox v6.05 firmware
PSA #3: Nosedive setting in all controllers!

Anyone with the latest v6.05 app (by now it’s most of us, Android users can side-load an old apk if they want) - when connecting to your board make sure you explicitly press the Read button for Float Cfg / Refloat Cfg if you want to make changes.

The app has a high chance of silently failing when trying to read your package config - if you then make a change and hit write you’ll end up with ALL DEFAULTS in your package config.

Happens with any 6.0x firmware!!!

Just last night I tried setting “disable moving faults” during a group ride and got hit with an all-default Refloat Cfg… Luckily I had a Backup!!!

UBox Firmware Bug: All Spintend UBox users, careful when upgrading firmware

Fix Available, see Syler’s (devnull) comment below!

The Spintend UBox v6.05 firmware has a serious issue with the auto-shutdown behavior potentially shutting you down even while riding!!! Do your research before upgrading!

In case you didn’t know, Spintend Ubox is a VESC controller. If your board has a different controller (e.g. Floatwheel ADV200 or others) then you aren’t affected!

Nosedive Setting

On some boards the erpm readings will be way off when migrating from 6.02 to 6.05 firmware. They’ll read 10-50x lower than they should.

To fix: set Speed Tracker Position Source to “Corrected Position” which is the new default in v6.05!

How to downgrade to VESC 6.02 (or prevent update)

How to disable Auto-Update of VESC Android App:

  • If you are on Android, go to the VESC Tool page in Play Store, hit the 3 dots on the top right and untick the “Enable auto-update” box
  • If you are on iOS, should be similar in the App Store app (can anyone report?)

Screenshot_20240819-221338
Screenshot_20240819-2213381008×2244 180 KB

Download and install VESC App Download 6.02 APK manually

So meanwhile you can use the VESC App 6.02 APK shared by GRIMM which he shared Vescify Discord:

Mirror 1: https://cdn.discordapp.com/attachments/846794258093703228/1275581319430012968/VESC_Tool_1.apk
Mirror 2: VESC Tool (1).apk - Google Drive

If you can’t access any of the files, try to open the message through this link and download it from there (you need to have joined Vescify Discord): Discord

3 Likes
2

I believe I have identified the root cause of the UBox firmware bug issue and how it was introduced in 6.05:

Fixed Critical Bug In Ubox VESC Controller Firmware – Syler Clayton

2 Likes
4

Great. At least now I know why it cut off on me last week.

I crashed at 30kmph on asphalt due to the thing literally cutting off on me.

Haven’t gotten back on it since. I’ll look into this update, but, damn. That’s messed up.

Oh wait, I’m on Little Focer v3.1… Could it also be affected?

5

That would be a hard no. The Spintend Box problem is 100% specific to that controller. No other controllers are affected.

6

so is it worth going back to version 6.2 of the application?

7

PSA #3: Heel lift disengages at any speed. Tested on Floatwheel. Very dangerous at high speeds.

2 Likes
8

True - fix it by setting Speed Source to “corrected position” in FOC Advanced @Tiztrain

3 Likes
10

Here’s the fix for Bug 2 & 3.

FW v6.05 UBOX Momentary Button Setup Bug #2 Fix:
App CFG > General > Shutdown Mode = TOGGLE_BUTTON_ONLY

FW v6.05 Nosedive Prevention Bug #3 Fix:
Motor CFG > FOC > Advanced
Speed Tracker Position Source = Corrected Position

Please let me know if this is correct or not so I can update my initial configuration guide.

3 Likes
11

I see. Any idea what could’ve caused mine to just shut down like that?

Few minutes beforehand it cut off when I was riding it stand still at a stop light once and when I mounted it another time. All in the span of 30 mins. I considered both as bad footpad connection, but third time it cut off while I was riding, so it couldn’t have been the footpad…

I’m riding 6.2 on 3.1 focer and ennoid v4.

I rode it today again slower and it didn’t do the cut offs any more, but I really need to find out what might have caused it.

12

Did it cut off power? Had to turn on the board it could it be that your heel was off and it deactivated the balancing?

13

I rolled back my firmware as it is super easy to do with the Archive tab in the app though I had problems looking for the 6.02 version of the vesc tool mobile app and could not find it.

14

When I got up from the ground and checked the board it was off and didn’t want to turn back on.

I took an Uber back home and after I cared for the wounds I tried to turn it on again and it worked as if nothing happened.

I was advised to activate logging and I took it for a slow ride around the block a few days later but couldn’t get any more cut offs.

Alas, im scared of it until I fix what happened…

15

Regarding the heel being off, i would expect that to matter when the board is being rode under 5kmph but wasn’t it a safety feature to ignore the footpad number of touch sensors while riding?
I mean when riding trails im not always pushing both pads but never had an issue before with onewheel fm

16

We added download links to VESC 6.02 update above

1 Like
17

I downloaded version 6.02 via an apk file here on pev.dev… everything works great!!

1 Like
18

How do you check which version of the app you have on iOS?

19

Press the cog in the bottom left corner → Click About.
In the modal that opens, you’ll see the version!

(Note that you can see this without being connected to a VESC first, just click “Hide” in the connection overlay that opens on app start, and you’ll be at the main menu.)

1 Like