VESC Firmware

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, ... 

Hi all,

Firstly, I would like to congratulate and thank Benjamin on how much progress he is making, and his hard work with this amazing open source motor controller platform! 

I stupidly corrupted the bootloader on my new VESC 75/300 :(

Hi,

I am looking for a motor controller or to modify a motor controller to operate a very low inductance motor at high voltage.
The motor is a 5-10uh motor, and I intend to operate it at around 180-200v~
With such a low inductance, with most controllers, current decays to 0 before the next PWM cycle, leading to massive eddy current losses, hysteresis losses, skin effect losses and the controllers have issues regulating/controlling the current.

Hi,
My VESC is after DRV8302 replacement, because I shorted outputs when running engine. I corrected all pins seperately, they are connected neatly and properly to PCB now. Blue and green LED are on.
VESC tool connects to the device on limited mode (old firmware windows pops on on connection, and recommends to upgrade). When I go to firmware tab I see no firmware's available on the list, and whatsmore in this tab I can't connect to the target although I am actually connected to device, I see connected (limited) in right bottom corner. 

Hi Im new to VESC.

I have purchased a Flipsky VESC 6.6 with the firmware (VESC_default_no_hw_limits).

I am trying to interface using B Vedder's (VESC® Tool 1.08).

I am getting an error message saying firmware not compatible.

I need to know if I am using the correct version of B Vedder's VESC tool? or will I have to change the firmware on my new VESC ( which I am reluctant too)?

Any advice appreciated

Thanks

Chris

Hi all,

i want to buy a vesc 4.12 with the firmware 2.18. But i only can find the vesc 4.12 with a newer firmware (i.e. firmware 3.38)

Well, my question is:

If i buy a vesc 4.12 with the firmware 3.38, can i flash back the vesc to the firmware 2.18? Is that possible? And how can i do that?

I did not work with the vesc in the past. So i am very new.

Thank you.

Just as a heads up, we created a pull request to add our virtual motor support code.

With our virtual-motor branch you can engage a virtual motor using the vesc terminal and start playing with it.

More info and fancy screenshots in the Pull Request

https://github.com/vedderb/bldc/pull/82

Maybe someone finds it useful and can't wait for Benjamin to review it.