NEW (9/13/2024): PSA1: Bug in v6.05 app, all users affected! PSA2: Bug in v6.05 firmware, UBox users watch out!
** Previous update (9/4/2024): Most issues with VESC Tool v6.05 related to VESC Express have now been resolved. Some users with VESC Express based Controllers still report connection issues, though many do not. If this applies to you, it may be best to wait for more consensus among reports. Otherwise, it should be safe to update.
Previous Warning (OUTDATED): DO NOT UPGRADE your Mobile VESC Tool App to v6.05 yet! There’s issues reported and Vedder is on vacation for 2 weeks now…
In order to upgrade to 6.05 you will need to upgrade both your controller and your VESC express (Thor, X12, etc) - unfortunately a firmware download wipes all your settings, which for the VESC Express means that it reverts back to having Bluetooth disabled. So it is best to avoid the upgrade until you know that you’ll be able to open up the controller box to access the USB port!
For users of Floaty a VESC Express update will bring the side benefit that the connection issues should get resolved!
How to disable Auto-Update:
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?)
My app says 6.05 but when I opened the app and connect to my board it says, “your running this app on old firmware…please update to get more features etc”. Also haven’t updated the app in Google play yet but when I tried to revert back to old firmware, it says access denied. Am I ok to use or is there an issue?
Damn total borked my tronic x12s I didn’t realize it updated and I go on and it was doing some crazy shit . Changed the numbers to my controller and changed all the settings won’t do motor setup now and doesn’t recognize my adc1 throttle on my Rion apex keeps resetting the settings to default every time I switch over to another device on canbus
on august 27th a new update for vesc tool was released… on august 20th it was automatically updated to version 6.05 after which I removed the automatic update… the question is do I have to do it the last one on august 27th?
Any reason why v6.05 would affect Refloat Voltage Pushbacks for High/Low Voltage Thresholds? It just started after updating to v6.05 on my LilFOCer 3.1. I also noticed VESCTool is also on v6.05. It seems to have worked itself out after a cold reboot. The high/low voltage thresholds values seem to load correctly versus displaying default values before the cold boot. If I had selected read values, they read correctly but VESCTool would keep loading default values unless I selected read. Strange things happen during firmware updates lol. Also helped a friend get his VESC running and the problem persists where setting high/low voltage threshold doesn’t stick. Hopefully there’s a fix to this bug soon
