VESC Firmware

Hi, for a couple days I try to figure out how to upgrade the firmware. I have 4.12 vesc with 2.18 fw. 

Could you give me clear direction how to upgrade to latest fw?

This question is rized becouse the latest bldc-tool I uploaded from benjamin git-hub (don't know how to see the version of the bldc-tool ) can upgrade to 2.18 fw. 

The latest vesc-tool from vesc-project.com show message it can work properly only with 3.x version of the fw.

i just wanted to know what function (or code sequence), i can use, for utilizing the "PID Speed Control" feature..?

i wanted to mod the code so i can use the NRF, in conjunction with "PID Speed Control"  (instead of Current control)....

Thanks!

I'm just trying to use my own little custom remote using an NRF chip, with VESC 6

i modifed the: nrf_driver.c and few other files to make them compatible, but doesn't seem to work so far..

In the VESC Tool, there is a pairing process required, so that the remote ID and parameters, will be loaded into the VESC so they can communicate.

(i also know how, there is software available on vedder's github for a remote, which is fantastic, but i want my own one :-)

Hi guys,

I've noticed a new motor temp mesure, but I cannot get it working.

I can read -77,5 at this moment.

How do you setup the thermistor value ?

thanks !

It reports e.g.:  "Latest injected ADC duration: 0.0253 ms". 

FOC 20kHz PWM, and sampling in vectors V0 and V7, means interrupts come at 40kHz, right? 

         40*0.0253 > 1    

Does that mean interrupt overload/overrun and that I should reduce PWM freq?    How to detect overload?

By the way: RT-app works only sometimes...  can that be related to MCU overload?

The truncation of the val for the throttle curve has no effect because the absolute of it (val_a) is defined previously. So the truncation should be done before val_a is created.

float throttle_curve(float val, float curve_acc, float curve_brake, int mode) {
    float ret = 0.0;
    float val_a = fabsf(val); <-WRONG HERE

    if (val < -1.0) {
        val = -1.0;
    }

    if (val > 1.0) {
        val = 1.0;
    }

    <-BETTER HERE

mcpwm_foc.c line 2480:  utils_truncate_number(&i_term, -1.0, 1.0);

The i_term should not be truncated to 1.0, but rather to (1.0 - min(1.0, abs(p_term)) or something like that.

Reason: Reduce overshoot by truncating i_term to a lower value.

It seems like first detection stuck the motor for some reason, so it won't be able to detect from the first place!
U first need to set up the app, PPM for me. write default motor setting than run the motor a bit.
Than come back to motor detection! It works in both BLDC and FOC now,
Phew~

Update, FOC is detected but not working, for bizar reason it shorts the motor and making tiny sound. does not respond to ppm... well BLDC for a while I guess 

hi

maybe someone can compile 2 and 3miliohm 412hardware and 3.27firmware to experiment with mini vescs ?

thanks 

Is the 1e-20 in the second line a typo? In the old version this was 1e-10.
float utils_fast_atan2(float y, float x) {
    float abs_y = fabsf(y) + 1e-20; // kludge to prevent 0/0 condition
    float angle;