I have two vesc 6 plus units on a tramp holy pro, twin 154Kv motors.
My problem is when I update the firmware from 3.57 to 3.58 it uploads , I wait for the lights to stop flashing and some, reboot and they still have the old firmware 3.57 .
That's using my laptop with vesc tool 1.16
The board is struck in slow mode, I can't change anything as it wants the firmware updated.
The phone app vesc tool does the same thing
What am I doing wrong
I am having the same problem. When I go to update to 3.58 it downloads but then reverts to 3.57. I can't initialize my motors without the latest update.
I have nearly the same problem.
It does not update the firmware from 3.56 to 3.58.
After the the 10 seconds I have to wait for initializing the red LED flashes one time and a second later, it flashes 18 times in a row.
When I cut the power supply and connect it again, the red LED does the same.
I tried to do the firmware update from Ubuntu VESC tool (version 1.11 and 1.16) with USB cable and Bluetooth, from Windows VESC tool (version 1.11 and 1.16) with USB cable and Bluetooth and from the Android app.
I also tried like in the instruction from page https://vesc-project.com/node/37 command #19 from benjamin:
"So, to get the new VESCs running, first go to the bootloader tab in the firmware page and upload the bootloader, then go back to the included files tab and upload the firmware. After a reboot everything should work.", because it sounds like the same problem. But it doesn't work.
It would be much easier if it was possible to just download the correct version of VESC tool for your firmware...
Or even if VESCTool worked on all firmwares...
Any developments for a solution? I am trying to upgrade from 3.57 to 3.58. So far I have tried the following:
Each potential solution tried still reverts to 3.57. Any help would be appreciated.
regards
Luke
This is something which I faced with my VESC6 as well., this happens to be the fault when the boot loader is corrupted or is in the wrong location on the memory init space.
here is the solution
Make sure you work with Linux Source Code / Linux VESC Tool in general rather than Mac OsX version as not doing so may change the boot loader size and location which might end up booting the older firmware on every reboot.
Clone the repo from here https://github.com/vedderb/bldc/
change the conf_general.h to the board which suits your hardware.
open the Makefile https://github.com/vedderb/bldc/blob/master/Makefile
and change the upload link to the one that suits your board
.... openocd -f interface/stlink-v2.cfg .... instead of discovery board
if the programmer flashes this properly it will show the debug connections after successful flashing ... once this is done your board will have the 3.58 on boot.
further more you can upload the fw again with the android or linux VESC Tools.
GL