For developers and bets testers.
This is the beta testing thread for firmware 5.02, which will mainly contain bugfixes and small improvements. It would be nice to have some help testing it out. Here is a link to the new VESC Tool with the new included firmwares for all platforms:
http://home.vedder.se/tmp2/vesc_tool_test_2020-12-30.zip This version is now released!
So far, the changes are:
Is there any mechanism to save state data on the vesc?
I was thinking about the gyro bias compensation, and i though it would be better to save the calculated offsets so the next boot resumes from where they were rather than 0, as those are (i think, in many scenarios) more likely to be accurate.
Looking at the code the only thing i saw was writing settings and that stops the motor and apps and etc. Which wont work for values that are updated frequently.
Hi dear VESC users and developers,
FW 5.00 is on its way, thanks to the good work of Benjamin Jeffrey and many contributors.
Thank you everyone !
As many things are on the table for a rework, could we take the opportunity to upgrade the CANbus integration ?
There are some devices that can (or will soon) hook to the CANbus, such as BMS, accessories, telemetry device or even chargers.
At the moment this implies to find workarounds for every device to communicate together.
I'm currently working on firmware version 5 for the VESC, and the major new feature is dual motor support. This means that the focbox unity should work with this release, as well as other dual motor controllers that will come in the future. In some upcoming projects I'm going to work more closely with Jeffrey who made the unity, so the other controllers he makes should be based on the main VESC code base soon. Jeff and me collaborating should be good news for the community, and I look really look forward to seeing what we can do.
