VESC Firmware

i have seen that this question in this vesc forums.
jennyxcy2008' question:
1：switch (comm_step) {
      case 1: curr_samp_volt = (1 << 0) || (1 << 2); break; 
      case 2: curr_samp_volt = (1 << 1) || (1 << 2); break;
      case 3: curr_samp_volt = (1 << 1) || (1 << 2); break;
      case 4: curr_samp_volt = (1 << 0) || (1 << 1); break;
      case 5: curr_samp_volt = (1 << 0) || (1 << 1); break;

I have 2 vesc 4.12s with the latest vesc tool. I cant seem to figure out how to connect them together. i have done everthing that I have seen and I got it to work by chance. Then I turn off the power and turn it on again and it quits working. if anyone know how to do this it would be greatly appreciated I have been fighting this for 2 days now.

Hi - 

I recently bought a new pre-built Trampa board with 2 VESC 6s. One is on firmware 3.48 and the other on 3.57 and I am trying to set them up using the new VESC tool 1.16. It tells me that I need to update the firmware everytime they connect, but every time I update it secussfully goes through but then when it reboots it's on the same exact firmware and not updating. Is there anything else I can try? 

Thanks,

Tim 

So i bought my VESC from DIYectricskatebaords and when i connect it to my PC i get this error “The connect VESC has to old firmware. Since the connect VESC has firmware with bootloader support, it can be update from the firmware page. Until then limited communication mode will be used where only the firmware can be changed. I then go into the firmware page and update it which takes around 10 seconds. When the update is done i get the message that the update has been successful. This is the message " Firmware upload finished!

Hello All,

I have been experiencing problems with my electric long board lately and am desperate to get it up and running for the summer! I have done a little research about VESCs and have a background in mechanical engineering, but don't know too much about software and firmware. I would be extremely appreciative if anyone could help me with my issue that I describe below. First, let me get into the hardware I have in my setup:

Hardware:

The current implementation of adc app has quite a few shortcomings. Most notably the lack of info on different drive modes and inability to see/configure what pins have what functions.

I have started laying out a new path here:

https://github.com/Teslafly/bldc/tree/adc-app-upgrades

Hello,

We need to have a LED status panel of several vesc 4 Canbus connected. This panel we plan to have one LED (or 3 LED that shows the vesc is ON, when the vesc is receiving throttle input, or if there is any fault). Basically, we want to "extend" the vesc status LEDs status to the "outside"

I have two vesc 6 plus units on a tramp holy pro, twin 154Kv motors.

My problem is when I update the firmware from 3.57 to 3.58 it uploads , I wait for the lights to stop flashing and some, reboot and they still have the old firmware 3.57 .

That's using my laptop with vesc tool 1.16

The board is struck in slow mode, I can't change anything as it wants the firmware updated.

The phone app vesc tool does the same thing

What am I doing wrong 

I am trying to free up some pins for auxiliary pwm for fans / brake lights.
As timer 5 is mostly clobbered by critical pins, and timer 1,3,4,8 are also in use. timer 2 seems like the best bet as 3/4 outputs are available in my pinout.

I would like to switch over chibios systick to tim5 off tim2 so I can use tim2 for aux pwm. Is this a really bad idea?

Hey, guys, how to use VESC & CAN Bus Communication to another MCU (NOT VESC)? Old forums can't be displayed. Can you provide any useful information? Be deeply grateful