You are here

VESC Firmware

Adding support for three phase shunts...

Submitted by Roger Wolff on Wed, 2017-11-08 16:03

Hi, My hardware has always had three phase shunts. I'm only now getting to the point where I'm starting to enable that in the firmware. 

Now I have arranged for the ADC vector to hold the extra current sample and defined its index. That's just fine. But when I enable HW_HAS_3_SHUNTS and command the motor to run at 1.5A, the motor jolts  as if it gets a 50 or 100A current spike. Doing a "sample when the motor starts" shows a 50 to 100A current spike. 

set current with custom app

Submitted by sirAnton on Thu, 2017-10-12 12:42

Hello, i have tried to write a custom app to set the max batt current (or better wattage) in runtime. My custom app started and can debug writes in the VESC Terminal.
Which function should i used to do that?   mc_interface_set_current_rel(10); does not work.

Edit: I used hw 4.12, und start the ADC app for speed control + My custom app

Help with Focbox firmware / bootloader upgrade [VESC TOOL]

Submitted by Enigmacpl03 on Thu, 2017-10-05 17:21

Hey guys,

So I installed new motors on my build and when I hooked up my vesc's to vesc tools, I received the error that my firmware was old and I needed to update. (FW3.26) ( HW410)

On my master vesc, everything worked out fine it is now running 3.29. My slave foc seems to show signs of a missing bootloader. I go to update the firmware it shows complete, the vesc shuts off but does not restart.

how update from 2.18 to the latest firmware

Submitted by aysubscriber@ic... on Tue, 2017-10-03 07:39

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.

Bypass NRF Pairing

Submitted by Dimitri on Wed, 2017-09-20 09:35

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 :-)

How to interpret the result of "last_adc_duration" (terminal command)?

Submitted by RSR on Fri, 2017-09-08 15:55

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?

Pages

Subscribe to RSS - VESC Firmware