You are here

BMS Harmony 16. Periodic annoying double-beeps.

3 posts / 0 new
Last post
SysGhost
Offline
Last seen: 1 day 8 hours ago
VESC Free
Joined: 2023-10-18 09:33
Posts: 4
BMS Harmony 16. Periodic annoying double-beeps.

Greetings 

Ny current e-scooter project is going well.

I'm in the process of making my second battery pack and this time around I'm going with the Harmony 16 BMS from VESC Labs AB.

Build process is at the final stage and it is a 13s6p pack with 3200mAh 18650 cells.

48v nominal, 54 6v total fully charged.

I found one annoying thing with the BMS:

It double-beeps every 10 minutes or thereabouts while in sleep. Extremely annoying. 

What is it, and what can I do about it?

SysGhost
Offline
Last seen: 1 day 8 hours ago
VESC Free
Joined: 2023-10-18 09:33
Posts: 4

Been looking at the configuration and the manual. I find nothing that could cause this. Is it randomly rebooting? Is it error-beeping for some odd reason, and if so, why? Is there a way to disable the beeper by a setting or a command? 

I could look deeper if I had the source code available or a set of terminal commands that might be helpful.

It only emits periodic/random "beep-beep" sounds while sleeping. Not otherwise.
If no solution is within reach, I plan to remove/desolder the beeper. It's more annoying than helpful as it is now.
Just that is a huge hassle to desolder the board off the battery terminals and undo it all again, just to desolder a speaker/beeper.

 

EDIT:

I found the source code of the BMS, and are currently looking into what's causing this. Would love to have some pointers on where to look .

https://github.com/vedderb/vesc_bms_fw

 

SysGhost
Offline
Last seen: 1 day 8 hours ago
VESC Free
Joined: 2023-10-18 09:33
Posts: 4

It seems the MCU reboots randomly. It can't stay alive for more than 10 minutes, often shorter.

These random reboots only happens in sleep, so I've blocked sleep mode in the vesc tool configuration for the time being.

Anyone else got any experience on this?

Do I have a defect board or is this a firmware/software problem? A bad watchdog?