Hi,
I've implemented UART communication with my VESC's and wanted to extend the program to also include the settings. My problem is that i used an old UART protocol, where GET_MCCONF=13, but in the VESC, packet_id 13 is SET_MCCONF (not GET)
The motor stopped responding to my commands, and a green light started flashing fast many times, then the red led flashes once on the VESC. I removed the power and unfortunately the VESC does not show up in device manager any more.
I did not know that the GET/SET had moved in the enum, and (stupid me) tested with another VESC... So now I have 2 VESCs that are not responding. BUT the last VESC is still flashing (i haven't removed the power yet), and i want to know if there is something i can do to recover it?
And is this a bug? For me it sounds strange that the vesc stops responding if i send this hex-string to the VESC: "0201 0DD1 AD03"
You must realize that the VESC boots not into the bootloader as an arduino, but into the application code. You can then ask the application to jump to Benjamin's bootloader. This has the side-effect that when the application no longer boots, you can't get into the bootloader either.
Does anyone have a solution to this problem? I ran into the same trap. Thank you.
I solved it. For anyone with the same problem: I played around on my Vesc 6 with uart and sent the wrong command. The vesc blinked red, i unplugged it and afterwards i only got a solid blue led and no USB connection whatsoever. I shat my pants a little.
I needed to flash the vesc with a cheap stlink v2. https://vesc-project.com/comment/225#comment-225 was my lifesaver. Many thanks to all of you!!
And https://vesc-project.com/comment/1362#comment-1362 was very helpful too!!