You are here

VESC safety

4 posts / 0 new
Last post
alexantosh
Online
Last seen: 14 min 31 sec ago
VESC Free
Joined: 2021-04-05 18:05
Posts: 13
VESC safety

Hello. Does flashing the VESC with different firmware than the one meant for its version damage the VESC and motor connected to it? Whats the worst thing that can happen? Say I install firmware meant for VESC6 MKIII to a VESC6 MK V. Whats the worst thing that can happen? and whats the best thing that can happen. Help needed please.

frank
Offline
Last seen: 1 hour 47 min ago
VESC BronzeVESC GoldVESC OriginalVESC Silver
Joined: 2016-12-27 20:19
Posts: 501

You should never do that. MK V hase pahse filters for example, MK III not. Worst thing: dead unit, best outcome: doesn't work as supposed.

Pins on the processor might also be swapped around and the FW needs to know that!

If you flash 60 FW on a HW 4 or VS, it is pretty sure that the devices will be dead within second.

 

alexantosh
Online
Last seen: 14 min 31 sec ago
VESC Free
Joined: 2021-04-05 18:05
Posts: 13

Thanks alot Frank. Actually, I have a FSESC6.6. So am sure it has a VESC6. The only thing am not sure about the MK version number. Not even the Flipsky company knows the MK version number of this device so thats the sad part. And I need to flash it with a VESC_servoout.bin firmware. So am having trouble choosing the right MK version VESC_servoout.bin. Any suggestions to go about this will be  greatly appreciated. Is there a safe way to update the firmware without necessarily knowing the MK version number of the VESC6 that am using? If so a link to the steps or tutorial will be very very helpful. Say compile from source.

alexantosh
Online
Last seen: 14 min 31 sec ago
VESC Free
Joined: 2021-04-05 18:05
Posts: 13

Checking the FW, HW specs after installing the most recent vesc tool and connecting the FSESC, I can see that it has the following:

FW: 4.1, HW: 60

And the supported firmware loaded being: 4.1. Is it safe to assume that this falls under the MK IV category? Also, is it ok to upgrade the firmware because the VESC tool still issues the same warning. that:

"The connected VESC has old but mostly supported firmware ..."