VESC Firmware

Hey!

I am using vesc with firmware 3.56. Vesc tool says that the supported firmware is 3.57. I can't find anywhere that firmware to download. Help? Where can I find it?

Regards, Ron.

Does anyone have an older version of the VESC Tool that has support for FW 3.56? My Flipsky 4.12 single VESC is on FW 3.56 and I can't update the firmware for whatever reason. 

Hello all,
Im trying to write a UART library in Espruino for the VESC6+.
Im wondering how if the VESC just spits out UART data or do i need to call a function to get the data over UART?

Thanks
/Gustav

Hi all,

I am working on implementing scalar control and foc control for induction machines, so I am wondering what the recommendations are in order to carry on with the programming. After reviewing the firmware source code, my first thoughts were to copy/rename/overwrite "mcpwm_foc.h" and "mcpwm_foc.c", so the microcontroller-related code could stay and I would focus on the motor control.

Could any of you with more experience in VESC firmware suggests me the best approach, best practices?, warnings are also welcome.

Thanks. 

Hi All,

I'm relatively new to the VESC tool and how to use it, etc...when I opened the tool the couple times I was notified there is an updated version. However when I follow the link it takes me to VESC home page and I can not find the link to DL the newest firmware. Does anyone know what I am supposed to do to get the new version? I am a bronze member and when I try to DL the current package I get denied.

Am I supposed to upgrade my VESC tool to the silver level or what exactly?

I'm using the comm_can_get_status_msg_index(int index) function to read the slave vesc's can status messages. The rpm and duty cycle are reported as expected (same values as in the vesc-tool), but the reported current is not the same as in the vesc-tool.

I saw that the current measure in the status message is generated with the mc_interface_get_tot_current_filtered(void) function so I played around with different current getter functions, but for no function I see the same output as in the realtime data page of the vesc-tool...

I'm sending COMM_GET_VALUES, and I'm getting back a 65-byte data packet that looks like this (values in decimal):-

2 65 4 0 249 ... lotsastuff ... ends with 0 0 0

Notice that it is missing a checksum and 0x3 terminator ?

When I send COMM_FW_VERSION, I do get back what I am expecting:-

Do you know if there is an easy way to save Motor and App setup before updating FW so that the initial parameters can be reloaded after FW update, to avoid having to begin again setting VESC up ?

I tried to use file save and load configuration XML but it looks like some parameters are not saved (or loaded) and one has to review completely setup.

Sorry if this question is not relevant I'm a new user even if a big fan of VESC project. 

Hello, 

I'm using the Vesc 4.12 Hardware. I also added an NRF based BLE to stream real time data to my phone. The vesc mobile App said I have to update the Firmware to 3.55 if i want to use the tool with full access, so I update the Vesc to 3.55. Now BLE connection ist also stable and I get real time data to my phone. But from now I can't use motor detection and the red LED is flashing. For a test I downgraded the firmware and everything worked, but not the BLE connection with full access to motor config, realtime data, ...