VESC Development and Beta Testing

Hello. I had some background programming in embedded systems, but I'm new to VESC programming. I've done an application very simple, but now I plan to make an application more complex, so debugging is a must. How do you debug an application? There is a dev tools console in VESC-Tool, and communications via USB between VESC and VESC-Tool, so the printing should not be an issue. How is it made? How can I print from VESC application so the result is written out in VESC-Tool console??

Thanks in advance,

Diego

Edit 2022-12-09: The release is now done!

Now that firmware 5.03 is released the development of 6.00 has started. Considering the amount of changes that made it into 5.03 it should really have been called 6.00, but that is now done for this release instead (which probably also will include some major new features).

The master branch on github is now the version where all development happens and each stable release will be put in its own branch with the release name. There are a few reasons for that:

UPDATE:

Looks like I was using BETA75 but from a different branch.

Hi community,

I've changed the structure of the CAN Status5 message to be able to use an external display, compiled without errors and successfully flashed. However now the VESC tool pops up with 

"Could not deserialize motor configuration. You probably need to update the VESC firmware, as a new iteration of the test version has been made". How do I override that? I could not find any hint on the web. 

Thanks for the help! 

Hi, I tried flashing the compiled github master version for 100/250 and ended up bricking the board. Could someone please point me out how to select the target board in the build environment? Thank you. 

My setup, Macbook M1 with gcc version gcc-arm-none-eabi-10.3-2021.10 compiler

The modifications that I have done in conf_general.h

FW_VERSION_MAJOR changed to 6

FW_VERSION_MINOR changed to 01

Then I commented out the line:

//define HW75_300_REV3

Hi everyone, I have developed my own board based on the vesc 75 300 schematics. The only difference is that I have made a 6 fet version and each current sense resistor is 0.002 ohms. I have compiled the source code according to my hardware and edited the hwconf. In BLDC mode everything works fine and the motor spins no problem. When trying to set up foc I can only get squealing noises and sometimes juddering from the motor when measuring the flux linkage.

Hi! I want to test vesck6 mkv version hardware and firmware code by myself.

Is vesc6 mkv the latest version?

I could find vesc6.4, vesc6 plus and vesc6 mkv schematic files and it seems vesc6 mkv release date is newer than other files, is it?

Is vesc6 mkv version is same as other companies vesc 6.6 version?

Please give more detail vesc6 version information to me.

Thank you.

I solved the signature problem. Turns out the signature is just an integer converted from a very long string containing all parameters' settings. Once the correct signature is written in the firmware, the whole thing run perfectly.

Hello all,

At the end of the VESC Tool page, it reads,

"If you plan to use secondary devices, not yet compatible with the all new Firmware, please make sure not to use them in combination with VESC-Tool until the device and its software has been approved to work flawless with the latest VESC firmware!"

In the spirit of this, and with the hope that my work can possibly be helpful to someone, I am putting this out.

Hi Developers!

Folks, 

I did a dump of header files from vesc-tools with customized values

Then, starting with a clean build from github for vesc I made sure that conf_general.h pointed to mcconf_default.h and appconf_default.h

I compiled, flashed on to a vesc board using st-link, connected vesc tool, and I expected that my default values would appear in the tool. Going to "read motor configuration" and "read app configuration" did not change any values. 

In one specific case I changed the value of: