You are here

VESC Development and Beta Testing

For developers and bets testers.

Motor FOC + ALL self-study to all CANBUS devices

Submitted by Filcas on Sat, 2021-04-03 11:11

Hello guys,

Will it be possible to run a command line or add a custom button to the VESCTOOL to keep all the motor settings but update the FOC PARAMETERS and HALL SENSOR tables on all devices connected through CANBUS at same time?

This will be similar to the default WIZARD, but we would like the same command not to change the settings on each of the devices connected on the CANBUS, but just update the FOC parameters and hall sensors table.

Is there a way or any workaround you guys might know to achieve this? Thanks in advance.

PPM+UART: Priority to UART on HW6?

Submitted by Filcas on Sat, 2021-04-03 11:05

Hello guys,

This might be straightforward but it seems we can't figure this out on VESC 6.

We have a custom app that commands the VESC through UART, but we need to switch between PPM and UART.
On VESC 4, we can get PPM+UART and we can drive the motors with both inputs (no need to change APP), but for VESC 6, if PPM+UART is selected, PPM works well but UART just jitters the motors and they don't spin. 

Just as test, we changed ADC+UART, and UART commands go through on VESC6. 

Help with firmware bootloader on UAVCAN

Submitted by jmachuca77 on Mon, 2021-03-15 20:25

Hi, I am trying to extend the UAVCAN drivers to be able to update the firmware through UAVCAN. However I do not uderstand how the bootloader process works. I see in the file commands.c several functions that I think are relevant but I dont know the order in which they are called, for example:

COMM_ERASE_BOOTLOADER_ALL_CAN

COMM_JUMP_TO_BOOTLOADER_ALL_CAN (I suppose after the application has been recived this is called)

COMM_ERASE_NEW_APP_ALL_CAN (probably called before the hosts sends the application?)

Firmware 5.03

Submitted by benjamin on Sun, 2021-02-28 21:28

Firmware 5.03 is under development, and this thread is for beta testers. This firmware has some major changes in the FOC code which can significantly improve low-speed performance and fix some old problems (such as when the motor starts "screaming"). Due to the amount of changes there are most likely some regressions, so I would appreciate some testing and feedback. Here is a link to the beta build:

http://home.vedder.se/tmp2/vesc_tool_test_2022-01-12.zip

How to tell what HW version I have and set conf_general.h

Submitted by jmachuca77 on Fri, 2021-02-19 19:21

Excuse the newbie question but I am not familiar with the project. I am trying to modify the VESC firmware to support more UAVCAN features. I have a flipsky ESC (https://flipsky.net/collections/electronic-products/products/dual-fsesc6-6-based-upon-vesc6-with-aluminum-heatsink-1) I know its HW6, but then there are other settings I dont know what to set them to, llike these:

// Second revision with separate UART for NRF51

No UART Output on VESC6 MKIV

Submitted by uwala on Sun, 2020-10-25 12:13

Hi Everyone,

I'm desperately trying to make the UART output and input work on my VESC6. I currently have a VESC6 MKIV with FW (firmware) 5.1. I have tried all the configurations I can on the vesctool to try and get a UART signal output but nothing seems to work. I am monitoring the TX pin with an oscilloscope to see if any signal appears, but unfortunately the pin stays high all the time.

Can anyone help me with this issue?

Thank you!

Custom command testing

Submitted by felixcollins on Thu, 2020-10-15 23:31

I'm new to the project and am trying to add some custom commands to be accessed via BLE.  The rig I'm working on has two motors. To test my new commands I want to exercise them from the VESC tool. I have a few dumb questions to ask so please bear with me!

1. The two processors are connected to the nrf51 BLE module through a multiplexor controlled by a pin on the BLE module. Using the VESC Tool, how can I switch between them?

2. How can I send a custom command from the VESC terminal? Do I need to rebuild VESC Tool with support for my custom command?

[Solved] Bricked VESC when trying to upload a firmware built from source

Submitted by cfv-naio on Fri, 2020-08-21 16:28

TLDR; Compiles but not executes and seems to brick ESC.

Solved : use gcc7 toolchain "gcc-arm-none-eabi-7-2018-q2-update", later versions generates issues

---

Hello,

I’m a software developer and I’m trying to setup my development environment for playing with the vesc.

I cloned and build (fedora, system arm-none-eabi toolchain) the bldc project, but not having an stlink available at the time, tried to flash the resulting .hex through vesc tool and bricked my esc.

Pages

Subscribe to RSS - VESC Development and Beta Testing