Has anybody figured out a solution to this message whenever attempting to talk to a VESC via CAN bus? I am working with a VESC 75/300 and can use vesc-tool 6.02 via USB but my vehicle implementation calls for only CAN bus control. I am running two-wire CAN to a DB9 which is connected to a PEAK CAN-to-USB converter connected to my laptop. Using PCAN-View I can see the data dumping from my VESC meaning that I am able to stream data from the VESC but vesc-tool is not able to talk via CAN bus.
I know this is old but maybe it will help someone . I started getting this error when I accidentally changed the can communication in apo settings from “vesc” to “uavcan” and wrote the app . I had to manually connect to it via usb and change the settings back and make sure the baudrate was right then it was working again .
Super Speed Scooter
@SuperSpeed Scooter, Were you able to get the two motors run simultaneously using can bus connection with 'vesc' setting? I have been struggling for a few weeks now and I am not able to run the two motors simultaneously over can.
mansi
@SuperSpeedScooter,
Are you having this issue on VescTool version 6 ?
I can't seem to find this settings..
I think I am having a similar issue here where I changed the settings to UAVCAN on the ESCs but cannot see them on CANSCAN because the hub is on VESC can protocol. My problem is I have a Vesc Duet, and can only communicate with the hub over USB. If anyone figures out how to change the CAN protocol some other way, Id love to know.
SOLVED: Was able to change protocol back to VESC connecting with USB to UART connector, the option is unavailable on vesc express.
I am having this issue as well. It seems like whatever I try, my CAN network will not load and VESC Tool continues to throw the "CAN bus support is not enabled in this build of VESC Tool" error.
I have tried the following fixes to no avail:
I have no clue what the problem could be at this point. The especially confusing thing is earlier this week, all of my devices were recognized on the CAN bus. Each driver is recognized when plugged in individually, so I think everything is electrically sound.
I am running Flipsky Dual 75100's, which have CAN traces on the board. When plugging in to one side, I should see the other, and I do not. If anyone has any thoughts, please reach out.
Thanks,
NS