For a project I am trying to control a single vesc through can messages send from a PC.
By setting the CAN mode to VESC I can receive the cyclic status message no problem. However when I send a message (e.g. 0x00000002 0x00 0x00 0x27 0x10, which should send drive no 2 to duty cycle 10%) nothing happens.
If the CAN mode is set to Comm bridge I can see that the vesc tool does receive the messages that I send (this is not the case in the VESC mode).
So my first question is: what exactly is the difference between the CAN modes?
And what mode should I use for my goal?
I have read the information in the application, but I can't figure out the difference in use. Is the VESC mode when you want to control multiple vesc's through one master vesc and the comm bridge what you would use for my application?
As for my second question: Should I configure some parameters in the vesc tool for it to work with CAN inputs?
Do I need to write a custom app for this to work? I would expect this to work out of the box since this seems like a generic feature. Or maybe there is something wrong with how I am sending the message?
Also, I am using the precompiled vesc tool since I did not expect this to pose such a problem...
I am new to this so apologies if this is very basic, but I can't seem to find the answers that I am looking for in these threads. And hopefully this question can also help other beginners.
Thanks for any help!
Hello
I'm working on a project similar to you.
How could you read the CAN message when it was a single vesc? I can't read the CAN message.
I think CAN mode didn't set it up. Could you tell me how you did it?
Help me..