I'm working on developing custom VESC hardware, and when I try to connect the VESC Tool to it I get an error stating that it "could not deserialize motor configuration." I'm able to communicate with the custom hardware, but this error seems to be preventing me from writing the motor configuration to the VESC.
My understanding is that this is because the VESC tool does not recognize my custom firmware. Is there a way that I can create a custom build of VESC Tool that will recognize my custom firmware or is it possible to override this error somehow?
Any help will be much appreciated.
Edit: the error turned out to be due to a mismatch between the version of VESC Tool used (6.02) and the version that the custom firmware was built on (6.05 Beta).
i have the same problem can you share with me how to solved it
im having same issue
rafe