My problem is I'm trying to update my VESC6.6 firmware from the old VESC tool software firmware of 3.38 to the new VESC tool software and running firmware version 3.6. (not the newest firmware)
Current situation:
- The VESC6.6 is currently working and powering a dual drive setup with the old firmware 3.38
- I can connect my computer to the VESC and program it utilizing the old VESC tool running the 3.38 firmware without any issues.
Intent:
- I purchased a X2 Pro remote, which requires a Firmware version of at least 3.6.
- I would like to just load firmware 3.6 rather than the latest version
Troubleshooting:
I have attempted to update my bootloader, then update my firmware as normal and it does shows 100% complete via the status bar, I then wait a minute and shuut it down but when it reloads it does not actually update rather when iI look under the VESC tool debug program it provides me this:
2020-06-27 12:57:07: VESC® Tool 2.06 started
2020-06-27 12:57:08: Status: Not connected
2020-06-27 12:59:04: Status: Invalid serial port: \\.\COM3
2020-06-27 12:59:19: Status: Connected (serial) to COM3
2020-06-27 12:59:19: Status: Connected (serial) to COM3, limited mode
2020-06-27 12:59:58: DEBUG (:0 ): Reloading user interface due to configuration change.
2020-06-27 12:59:58: WARNING (:0 ): Param subgroup "hfi" not found.
2020-06-27 12:59:58: WARNING (:0 ): Param group "balance" not found.
2020-06-27 12:59:58: WARNING (:0 ): Param group "balance" not found.
2020-06-27 12:59:58: WARNING (:0 ): "can_mode" not found
2020-06-27 12:59:58: WARNING (:0 ): "can_mode" not found
I then restart the VESC and connect with the VESC tool and the firmware still reads 3.38.
I have reload the VESC firmware 3.38 several times and then load the newest firmware as well as various firmware version but I receive the same message.
The VESC is still functional and it works fine I just can not update the firmware.
I do not think this is what is referred to as Bricked?? and it never came unplugged or interrupted when iIwas updating the firmware.
Does anyone have any advice on how to correct this firmware update issue so I can test out this X2 Pro remote?
I have been working on this problem for a month now without success.
Thank you.
If I get this fixed---- I will upload pictures this custom board I designed and fabricated. I assure you there is nothing like this board out there.