VESC Firmware

I'd like to try a few changes to the firmware, and I am using a Flipsky FSESC 6.6.  It showed up in VESC Tool as hardware '60' and works fine with the default firmwares.  I've checked out vedderb/bldc from github, updated it to the regular hw60, and then compiled it.  It uploads to the board fine, but it doesn't work.  Is there something I'm missing here?  I'd like to figure out the workflow to get a firmware exactly like the existing v5.2 release before trying anything fancy.  Here is my git diff from the master branch of vedderb/bldc.  Thanks in advance for any help!

So I'm new to the VESC world. But maybe some of you guys could help me out with a little information.

I have seen the VESC Git repo: https://github.com/vedderb/bldc

But can someone tell me were are the functions defined for the control system?

When I use the VESC in FOC mode, I need to calculate the parameters like I_d and I_q but in which folder or part of Benjamins Code are those calculations.

Hi. I need to flash my Mini FSESC4.20

and need the *.*bin file.

Where can I find it? thanks.

Hi

I have with accident uploaded VESC 6 firmware on the 75300. Now when i connect the 75300 vesctool reconises the 75300 like a VESC 6. Somebody that have a 75300 .bin firmware file ? 

Regards

Markus

I am very new to using vesc.

I have a Trampa 2wd spur gear with two VESC 6 

I am trying to get the firmware updated but I get this message 

The connected VESC has test firmware, and this is not a test build of VESC Tool. You should update the firmware urgently, as this is not a safe situation.

Any help would be appreciated

and thank you . 

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!