If you had FlexiBMS FW0.19, it was not supported, just added support for it in the Metr app and firmware, please update.
Ok, so this just happened. @SimosMCmuffin .
What happened: Left my board on storage capacity, somewhere in between 3 months flexi BMS has gone through entire battery (essentially killing it).
Setup: Flexi BMS
Serial number, FW version: Couldnât find original package right away but will let you know once I find it. Flexi I had was from last February drop with the firmware it came with.
Settings: device isnât recognized with usb cable anymore but the blue light lights up on the board when usb is connected. Tried different cables, different power supplies, reinstalling drivers. Still nothing.
Connections: only thing connected to bms was battery power, balance wires and Can bus connector from ESC. ESC and any other auxiliaries where disconnected with loopkey.
Genuinely depressing to say the least. While Iâm pissed off at the entire ordeal I hope this can get fixed so that anyone else doesnât have to endure seeing almost new battery go in the dumpster. Iâm ready supply any other info needed.
If you store your board and want the BMS to stay connected (not recommended with any BMS as they ALL draw a little power to monitor the cells) Iâd recommend to disable CAN listening, as this draws the most power in the flexi.
Shure, I agree, but it shouldnât be as fast as 3 months. And even if it does shouldnât there be protection where it shuts down bms in order to not drain battery dry and risk fire?
Regarding CAN, wasnât the power input line from vesc power there for that specific reason to not wait for can commands if VESC is powered off?
How would the BMS know that the VESC ist powered off if it doesnât listen for can signals? And fast is relative, a cell on storage voltage doesnât contain much energy at all. have you tried reviving the pack? You may be able to rescue some p-groups.
Using the supplied pin on the bms for that specific purpose, which was connected in this instance.

Still doesnât answer the question of why bms potentially doesnât have feature to protect battery from over discharge by completely disabling itself. Do I sound stupid for expecting a product that is built safely and wonât kill pretty much most expensive part of a device without me having to baby sit it every 3 weeks?
In past yes, with limited results (mostly a loss of 50% of capacity), in the end if the cell is damaged it posses risk which I am not willing to take. I know some people do it with no problems but Iâm not into that.
In the end, I am not expecting or want refunds, I donât want anyone anyone to pay damages. I have written it off as expenses for doing things DIY. Only thing I want is for this to be figured out, noted and ether instructions in github updated (that no you canât leave bms for more than a month connected to power, or it has to be after loopkey), or if there is bug for it to be fixed so that no one else has to endure this.
Idk, you have to ask Simo for that.
I heard some funky stories about that pin, not sure what that was though.
Damn, thats a harsh cut.
I cant find this anywhere, github shows FW .18
is the latest
I recently updated my Flexi to 0.19 and found that it doesnât work with the Metr and potentially has a bug.
I found that every time I restart the firmware through the console, the flexi doesnât boot up properly and requires a hard restart.
In the metr app, communication works. I am able to read setting, but receiving cell voltage and data about the battery doesnât work. I enabled the CAN status and can messages were being transferred but still nothing on the Metr.
I then downgraded the Flexi to 0.18 and everything worked just fine.
Closing my case on this, sold my flexi and built a new battery with LLT for now. @SimosMCmuffin No hard feeling and I hoping you will return to continue this project in future!
Maybe itâll help someone with debugging or something, but I have had a FlexiBMS plugged up to a pack for six months or so without charging. Battery voltage hasnât really changed. Itâs not connected to anything else (eg; VESC), literally just been sitting in a box. Never enabled wake on CAN.