JKBMS high voltage alarm, support request, how to make a config file

[Fraser86]

Please please help.

I have a 8 cell setup with a jkbms.
I also have a raspberryPi that is running version V3.0

My trouble is that everyday I am getting notifications that I have a High Voltage alarm despite the OVPR set to 28.4V I get high voltage alarms occurring at 27.78V for example.
I have come to learn that there is within SerialJkbms a setting within Parameters called Charge Voltage Limit (CVL) and this is set by default to 27.60 volts, in others words 3.45V. This setting is not changeable.

I am having a problem daily and I have not the experience to know what is happening and how to prevent it. I posted to the forum to try to get some help and answers but was told not to post there but instead to make a support ticket.
I tried to do this but this requires a knowledge of how to create a config file and to submit that and something called ngrok which I have no knowledge of. I have been trying to understand what this is for several hours over several days but I am stuck. like to learn but I wanna know what is going on? What is the reason for these annoying High Voltage alarms? How can I prevent this?

@Louisvdw

[Fraser86]

I have made an account at Ngrok
I have manually added the authentication but this next bit is confusing me. I don't understand how I would check the logs . I dont know how this is done and the instructions are not clear to me

Config

Access to the remote console/GUI → Settings → Services → Ngrok
Debugging

The logs can be checked with tail -n 100 -F /data/log/venus-os_ngrok/current | tai64nlocal

You can check, if ngrok is running by executing ps | grep ngrok

If you do not see anything in the logs you can increase the log level in /data/etc/venus-os_ngrok/venus-os_ngrok.py by changing level=logging.INFO to level=logging.DEBUG

[mr-manuel]

The debugging you mentioned is for ngrok and not for the dbus-serialbattery. Did you check the dbus-serialbattery documentation? There is a troubleshooting section where you can get all relevant informations.

[Louisvdw]

Hi @Fraser86
Sorry the bug reports are a bit challenging. They are set up for us to be able to get all the information we need to assist you, without asking the same questions to each person that can take a lot of time. You don't need ngrok, just fill out the questions from support request

There are settings on the BMS itself (you set that with your phone on the BMS app)
Then there are settings that the driver has. (the config files that you can adjust)
And then there are settings in the GX device itself.

Any one of these could be causing the problem.
I suspect if your cells are not balanced that this might be causing your issue. Look at the VRM alarms and graphs described here to check the values of your min/max cell voltages at the time of the alarms.

[Fraser86]

Im reading this in the documentation but unsure about what its saying

What is meant my "If your battery works with lower limits"

[Fraser86]

for now I have put it like this

[Fraser86]

I'm am trying to understand this so the settings are correct. I don't want to keep asking dumb questions. So thanks for your patience.

So
Is "if battery works with lower limits" referring to cells with a lower Voltage when full, or something else that I am not getting?
Reading this sentence I guess I'm not understanding lower limit.

please clarify

[Fraser86]

with some googling I found this.. for educational reason I post it here for other looking for answers

[Fraser86]

So I corrected the dvcc setting.
and when my battery reached 100% and I again receive high voltage notifications.

the cell deviation is 0.125

so I again don't understand why I am getting this issue.

[Fraser86]

So winter is over and the first days of sun are back and I am again getting this issue. I hoped that the mistake of having dvcc in the wrong position would help but I am still getting High Voltage alarm and battery shutdowns

[Louisvdw]

If your battery was not fully charged for a long time then the cells will drift and go out of balance. The Battery Life feature on the Victron system will make sure the battery is reaching full at least once a week which I would suggest you should use.
But if it is out of balance you should slowly charge the battery to give the BMS time to balance the cells again.

Also remember that this issue is with your battery and not the driver. The driver is only highlighting the issues that you did not see before.
So it might be worth it to ask your battery supplier to check the hardware.
You could also lower the charge voltage setting, and also lower the charge current limits. Both will give your BMS more chance to manage the problem cells.

[Fraser86]

It's been on Battery Life function throughout the winter.
How do you change the Charge Voltage setting
I have looked in parameters - CVL

This is set to 27.6
but I am unable to adjust and not sure if this is what you mean.

[Louisvdw]

The parameters CVL is what the driver requests. If you want to override it the best option is in the DVCC settings in your GX device. Just lower that until you do not see the alarm hapenning anymore.
CVL is is the Charge Voltage and CCL is the Charge Current.