You are here

VESC 4.12 problems with FW newer then 3.10

3 posts / 0 new
Last post
muchtete
Offline
Last seen: 5 years 10 months ago
Joined: 2019-01-29 16:55
Posts: 1
VESC 4.12 problems with FW newer then 3.10

Hello,

I am having trouble updating my original VESC 4.12 to a newer Firmware version (desired version is 3.31).

In short: Updating the firmware over the VESC-tool or through flashing the newer firmware directly on the chip with an st-link, results in no led blinking and the VESC not being recognized as USB-device and consequently not being able to connect with VESC-tool -> basically bricked.

I wanted to update the FW, using the VESC tool. For that I connected and powered the controller over USB with no further hardware or power supply attached. After making sure HW-version matches I updated through the tool which went through without any error. After the update was done, the problem occurred as described above. I thought the chip was bricked. Connecting a st-link and flashing the desired firmware as well as the bootloader (flashing the chip worked fine, no errors during the process) didn't change anything.
After trying to work this out a whole day, I tried flashing older FW-versions. I found that up until version 3.10 the controller seems to work fine, with the LEDs showing the usual start-up routine and the controller being shown as usb-device and being able to connect to in vesc-tool.
The problem with updating still exists nonetheless.

Could there be a problem with powering the controller over USB only?

I have no idea what could cause this behaviour. Any help or suggestion is appreciated.

Kind regards,
Niels

 

ravenswood1955
Offline
Last seen: 5 years 6 months ago
Joined: 2019-02-23 03:34
Posts: 1

Same problem but all I got was I had old firmware. I would go through the motions for update, even the controller was flickering like a data transfer was occurring. reconnect and reboot only to find still had the old firmware. I tried drivers,cables,other programs, Enertions BLDC bla bla bla. I thought I got around this when I flew drones, you know that darn learning curve. Cant offer any help, sorry. I guess some day Ill figure this out.

GunnarW
Offline
Last seen: 8 months 3 weeks ago
Joined: 2017-09-06 13:50
Posts: 8

If you have not seen this thread already, read it. Some of us including myself seem to have solved their problems after reading it:

https://vesc-project.com/node/175

I would like to see a thorough instruction on how to do these things to avoid the ongoing troubles we, not so knowledgeable people, have. And some advice about when we should update our soft- and firmware even though our motor works. Or is it just "if you at last got it to work don´t touch it...ever". I mean surely there must be some benefit, even to us to update, from the outstanding knowledge and time Benjamin put into this project.