It would be great for mobile application if the VESC FW could provide, a method to change some usual tuning parameters in live mode (max watt, eRPM, MAX/MIN Current, ...). Those change would be volatile (lost in VESC reboot) or persistent (saved in VESC).
I was thinking in isolating the conf_general_store_app_configuration and the conf_general_store_mc_configuration and make the persistence optional on both COMM_SET_MCCONF and COMM_SET_APPCONF, but I'm not sure if there is others objects need to be change/reset to apply the change in live way.
And I could be great to don't have to push everything (APP + MCCONF) just to change a little part of the parameters, because it's a bit overkill for the Bluetooth communication.
So maybe a good solution can be to add a new set of commands to manage Profile. The profile will be a subset of parameters relevant to be changed "online".
I'm ok to work on that but I wanted to share a bit with you, to find the clever way to implement that.
Yes, it's a good idea to make it adaptive with parameter identifier.
It could be also fine to add an profileId to know the actual profile. This ID will be fully managed by the mobile app.
Yes good idea for most applications, board, but also Bicycle, and others.
Some people are also trying to interface VESC with the well known and used LCD-3 from BMS Battery.
You can easily find the protocol used with the RS-232 on Endless Sphere or other bike forums.
Have a Nice Day.
Thierry
So the idea is to change VESC settings just temporarily? That would be amazing to have "legal" (250W, 25kmh, ...) settings when repowering the VESC. +1 on that feature.
I think it would be great if it could be persistent. If you could have presets or profiles to switch between like a commercial electronic skateboard.
Great job Benjamin!