You are here

VESC Firmware

self-built FW does not work properly with VESC Tool?

Submitted by Jackl on Sun, 2024-03-17 21:32

Hi there,

I am trying to do some FW modifications and test some temperature-sensor related things.

So far, most things seems to work. I am able to build fw with for example "make 75_300_r2_no_limits". I am flashing the FW with a ST-Link directly.

It basically works and I am able to control the motor via the VESC-Tool, eg. current commands, etc. What does not work yet:

Firmware Compatibility Issue with Custom 75_300 Based Hardware

Submitted by kevin458 on Wed, 2024-02-28 19:55

Hello everyone,

I've developed my own hardware based on the 75_300 design, with the only modification being the shunt resistor values. Originally, the design used 500uohm resistors in a 3-parallel configuration, but I've changed these to 400uohm resistors. Apart from this alteration, all other hardware components remain unchanged.

BEMF glitches

Submitted by ProgramThyself on Thu, 2024-02-08 20:27

Running a new VESC 6 EDU w/ stock firmware.

-> fwinfo
GIT Branch: release_6_03
GIT Hash : f7c2b34e
Compiler : 7.3.1

The default Zero Vector Frequency of 30 kHz has glitchy BEMF (sampled data graph) and runs rougher.  20 kHz is cleaner and quieter.
 

FOC_Openloop terminal command via CAN?

Submitted by Jackl on Mon, 2024-01-15 10:09

Hi all,

for my application I need to apply a rotating field to my machine at high currents. Basically exactly what the terminal command foc_openloop does.

Is there any way to control this via the CAN Bus? I am sure you can activate it via can, because it also works if the VESC is connected to VESC Tool via another Vesc over can but I am struggling to understand how the much more complex can forwarding seems to work.

VESC TRAMPA NRF BLE firmware question and feature request

Spaceman's picture
Submitted by Spaceman on Sat, 2024-01-06 06:47

 Question regarding firmware revisions and to do list.   

List simple FW rev and product description in VESC tools SWD programmer for BLE's

Tx power Low/Mid/high instead of dbm, preconfigured for sensible RF duty keeping in mind both BLE units need to match levels.

Remove Integrity as it should be pretested or implement as auto ack. My understanding in integrity is mainly the radio speed option > small bandwidth for a robust carrier and modulation type.

Pages

Subscribe to RSS - VESC Firmware