You are here

VESC 4.7 old firmware update issue

5 posts / 0 new
Last post
Lars_Dierickx
Offline
Last seen: 1 year 9 months ago
Joined: 2023-03-03 11:38
Posts: 2
VESC 4.7 old firmware update issue

Dear all, 

After wiring up an old VESC 4.7 to use in a current project, the VESC software states the detected firmware is too old, but can however be updated from the firmware page. 

After flashing the default 46&47 firmware (assuming this stands form 4.6 and 4.7) as listed in the VESC tool firmware tab, the software still displays the old firmware version (and thus stays in limited communication mode). The program itself states that, if after updating the firmware and additional reboot the old firmware is still shown, there might be a missing boot loader.

After installing the ...&47&... boot loader from the boot loader tab (which only takes a few seconds ?) and again flashing the 46&47 default firmware, the same issue remains. Old firmware is displayed and the controller stays in limited communication mode.

  • Did I perform the above steps in the correct order?
  • Did I select the correct firmware, or can I download a most recent .bin file somewhere online? 
  • Is there at the end anything more I can do to get the controller out of limited communication mode?

 

Thanks in advance, 

Lars

xkzx
Offline
Last seen: 1 year 2 months ago
Joined: 2023-09-21 20:16
Posts: 1

I am having the exact same issue, only with a old Flipsky V6.6-DK. It does work, motor spins and all, but I remain in Limited mode. Firmware V3.57. Tried updating the Bootloader. same.

Did you find a solution for your problem?

konabiker
Offline
Last seen: 1 week 1 day ago
VESC Free
Joined: 2024-11-12 15:22
Posts: 2

Same problem with an old VESC 4.12 and Fw v2.18 sad

JUST1975
Offline
Last seen: 3 weeks 4 hours ago
VESC Free
Joined: 2023-10-12 16:30
Posts: 3

I opened a new thread...

Found this here. Exdactly same issue.

 

On some pages, I found the notw, an older VESCtool version is needed?

konabiker
Offline
Last seen: 1 week 1 day ago
VESC Free
Joined: 2024-11-12 15:22
Posts: 2

Yes this fixed it for me. But to upgrade from Fw v2.18 I needed an older version of VESCtool than the oldest one I could find online. I then upgraded to 3.* and that version the newest VESCtool could handle.