BMS functionality? about bldc HOT 2 OPEN

Oh yeah, I'm aware I'm proposing functionality normally found in a discrete BMS; hence the title of the ticket. However, I'm pointing out is that VESC already has the most difficult piece of that functionality done, which is monitoring and accumulating the consumed wattage. It's a fairly small step from there to supplying users with a fully functional gas gauge, accessible over the UART/CAN interface, and via peripherals such as the Wand.

Given that VESC now also includes such extras as an IMU for UAV use-cases, it seems reasonable to consider battery tracking for inclusion given the value it would provide to users in avoiding yet another component to have to integrate, and deal with interop issues on, etc.

from bldc.

Hi @mikepurvis,
The 3 points that you explain are the role of the BMS.
What you'd be interesting is to develop kind of a standard protocol with BMS connected through CANbus (such as DieBieMS ) for a soft cut out in case of battery dead or other faults.
We work on this here and we'll propose a PR for this.

from bldc.