zerotoeing
New here
I use the 130A ANT BMS in a product I build and sell. There are around 300 batteries out in the field worldwide. They’ve generally been reliable — I’ve only seen about a 1% failure rate, usually from MOSFET issues, which I put down to the fact they’re being pushed pretty hard.
What’s odd is that in the past three weeks I’ve had three customers, all staying in the same remote area (within about 1 km of each other), whose BMS have all failed in the exact same way.
I’ll see what ANT comes back with after inspecting the returned board. In the meantime, I’d be interested to hear if anyone else has had ANT BMS's go completely dead like this, or if there are known firmware/security issues that might explain it. Is it possible to reflash the firmware on a board using a serial adapter?
What’s odd is that in the past three weeks I’ve had three customers, all staying in the same remote area (within about 1 km of each other), whose BMS have all failed in the exact same way.
What happens
- When the customer goes to charge, the battery won’t turn on.
- No lights on the BMS, no Bluetooth signal, completely dead.
- The charger doesn’t see a load and shuts off.
Things I’ve checked
- Batteries were balanced and charged before this happened.
- They use the weak current switch to turn on/off.
- No discharge faults beforehand.
- Doesn’t appear to be charger-related (different models involved).
- All passwords (L1–L5) are set and private.
- Tried waking the BMS with charger input, external DC, and even paralleling with another battery — no luck.
- Swapping in a new BMS brings the pack back to life, so the battery wiring is fine.
- I have one failed unit on the bench now — completely dead, no LEDs, no Bluetooth, nothing.
- Another failed BMS has been sent to ANT for analysis.
Why it’s strange
The fact that three units died in the same way, all in the same location and timeframe, seems more than coincidence. Out of ~300 units globally, having three go down in the same 1 km radius within three weeks feels too specific to be random hardware failure.My best guess
I can’t shake the idea that it’s firmware or security-related — maybe something that’s wiped or locked the BMS firmware, leaving the board unresponsive. Hardware faults usually don’t line up this neatly across multiple units.I’ll see what ANT comes back with after inspecting the returned board. In the meantime, I’d be interested to hear if anyone else has had ANT BMS's go completely dead like this, or if there are known firmware/security issues that might explain it. Is it possible to reflash the firmware on a board using a serial adapter?