Hello everyone! I just received my second ESC and motor from Torqueboards. (4.12 vesc and 6374 motor) when trying to set them up for canbus communications ( I’m on the newest release and firmware, it happens with every version/firmware)
I get an error stating that
“can bus is not supported on this version of vesc tool”
I’ve tried so many solutions to no avail and see many people with the same problem but no solution. Trampa’s best attempt at support was “it works for me”
I also run into the issue where when I try to run the app settup wizard on the master/slave vesc while the other is plugged in over can I get the error " one or more of your vescs are on an outdated firmware " I’ve reflashed the firmware many times and it changes nothing. The vesc tool lists both vescs in the bottom left and I can select the slave vesc.
Ackmaniac works flawlessly. When I use the app wizard I get the option to settup a master or slave vesc. VT doesn’t prompt me with those options and I’m not sure it ever had before.
Currently I’m running them through canbus on ackmaniac firmware but I cannot use my VX2 remote on that firmware so right now I’m stuck with my shitty emergency ppm remote.
Does anyone have experience with this issue ? Please help me. I want to use dual motors on my vx2
As far as I have been able to come across the concensus on the problem is " it’s just something wrong with your PC " I will try to set them up on another PC when I have access. Currently I cannot do anything to change any CAN settings on either vesc (can’t set a vesc ID) but ackmaniac has 0 problems with these features.
I am running Windows 10 pro with the newest version of the vesc tool for windows. (Just redownloaded it today)
@torqueboards Programming them isn’t the problem. I have already tried programming individually and then activating can forwarding but it does not work. My problem is that the canbus tools of the vesc program simply do not work. My vescs are programmed fine.
I have also seen this error message. It seems like the executable was compiled without a flag set or something. Not sure; I didn’t investigate because I didn’t plan to use CANBUS.
The compiler issue is what I’ve also heard. It has to be something with how my computer extracts the files or some sort of architecture VT uses that doesn’t play nice. Makes no sense that ackmaniac works fine.
So I had this issue as well and resolved it after flashing the firmware by going to each ESC individually and making sure that the canbus is enabled on both sides. I set mine to something like CAN_1_2 (i cant remember exactly what its called). If its set as disabled, you will see this message.
If you use the canbus function in the connections tab it gives this error.
Where you need to go for canbus functionality is in the lower left corner. They just magically appear there if they’re on the canbus line connected. Or there was a scan button… dunno… but that one works and it’s all you need
Also bluetooth android app is a lil bit more straightforward on this
Yeah I can set those settings just fine but it doesn’t matter because the can forwarding doesn’t work. I cannot change the ID of either vesc in vesc tool so they have their default ID. When I try to can forward to the slave vescs ID it still doesn’t work. If I put in 1 as the can forward it tells me it can’t find the firmware and disconnects the vesc. Can forwarding does not work. In ackmaniac all these features work flawlessly.
Still doesn’t work. It shows both vescs but I can’t actually interact with the second one. Can forwarding doesn’t work. The issue I have is very specific and is between my computer and the vesc tool. Not the vesc tool itself or how I’m trying to set it up.