VESC Firmware

Hey,
I would like to disable the Bluetooth function of the VESC, so no one can connect to it via Bluetooth
and you have to physically get to the VESC and connect for example via USB to change the settings.

I couldn't find an existing function for that if there is one already, so I thought maybe it's possible to
take the firmware source code and set something like "Bluetooth_Enable" from "1" to "0" and rebuild it.

Hi,

I'm working on a custom firmware, where I wish to use the "servo_val" variable from the ppm app. I save the servo_val to another variable in the ppm loop to ensure I don't save the servo_val value at difference stages, such as before deadband, etc. And to avoid any corrupt reading of the variable from the custom app thread I'm trying to use "chMtxTryLock" and "chMtxUnlock".

Hello,

i have connected a VESC compatible Hardware from MakerX via CAN-Bus to my MCU (STM32). I read all CAN messages from 1 to 5.

Fast changing values like the motor-current and the battery-current tend to show strange behaviour. E.g. I observe the values with the VESC Tool and it shows the current between 0.8A and 0.9A what is a plausible value for the setup. However, the current data that is extracted by the extern MCU via CAN-Bus shows values between -2A and +2A.

I'm trying to flash a custom firmware on the VESC so that I can have custom CAN messages on the Bus, such as Fault codes.

I have 3 different VESC 75/300 versions. One that I know is a REV_3 and two more that I'm not sure which version they are. The PCB inside the VESC says V1.1 and VESC Tool says Fw: 5.2, HW: 75_300.

Hi everybody,

I am facing some instability issues with combination of vesc (trampa) MK3 with FW 5.1 et 5.2, so needed to downgrade to 4.2

Does somebody have a table of correspondence between version of HW and FW? I am particulary interested in trampaboards HW (MK3, MK4, MK5)

Thanks in advance!

Hello guys, 

I couldn't find on the files which compose the VESC Firmware, the lines responsible for the regenerative braking. Neither the lines of code responsible for the MOSFET Switching. 

I'm trying to improve my understanding of how to command the VESC to Switch the MOSFETS at will. Any help to this regard is welcome!

Hello everyone,

I've been working lately on a simple implementation of the FOC functionality (learning purposes) using a VESC 4.12 and a Hoverboard BLDC motor.

Problem: ADC values read are always positive (uint32_t) while the phase currents (ia, ib) can have both signs. How can I tell which sign a current has? I tried to refer to the VESC open-source firmware and found inside mcpwm_foc.c something like this:

Hello, I apologize in advance I'm completely new to all this, it's my first DIY electric skateboard build. So I bought torque6 vescs and running torqueboards direct drive. I'm using the vesc tool app on my phone and I ran the wizard but I keep getting firmware not up to date messages so i uploaded the new firmware but for some reason it is not loading new firmware, when i try to pair the vesc i just get a message firmware needs to be updated. Am i missing a step here? Thank you in advance I'm trying to learn

So the setup is a flipsky VESC spinning a tMotor MN5008 with hall effect sensors I have installed on it myself.

ESC: https://flipsky.net/collections/electronic-products/products/torque-esc-...

MOTOR: https://store-en.tmotor.com/goods.php?id=998

I am trying to collect some data from my VESC and for some reason it is always reporting that ah charged and wh charged are 0, despite the fact that I am able to use regen braking and both the motor and battery current are negative while I am doing so. Does anyone know why this might be the case? I am using firmware version 5.2, hardware version 4.12, and VESC tool version 3.00.