question

I have 2 overkill solar (JBD) BMS and only one is seen on my RPI running 2.85. If I’m reading right, after 2.73, multiple BMS may not be recognized. Is that still the case?

Good evening, I use this driver with DalyBMS.
I noticed that the values of power and current jump very strongly. e.g. within one second between 400W -> 720W -> 1250W and back again.
Can you do something about that?

To: Louis van der Walt

Looks like a very good work! Can i use it without a Victron inverter? Raspberry Pi, 2x Victron 100-50 SCCs and a JK BMS 200A 8S 2A balance. I have a spare Victron USB to VE.Direct cable i can modify. ps. i was using DYKB 200A 10-24S ANT BMS, with inaccurate current sensor; was planning to get a Victron Smart Shunt, but looks like dont need it with the JK and this setup. Thanks. pps. the DYKB 200mA balance got too hot, burned a resistor. Later 3x 104RONS MOSFETs on the charge side got blown, temperature reading fault first. Both charge and discharge current were severely limited.

Louis, I can install your driver manually. But I tried it through KWindrem's SetupHelper and couldn't get it to work. I tried:

Package name: dbus-serialbattery

GitHub user: Louisvdw

GitHub branch or tag: latest (also tried v0.10)

Am I doing anything wrong? It would be really handy if this was to work.

Hi Louis van der Walt, I am probably very late and to be honest, I am not looking forward of reading though all the comments and replies to find what I am looking for. So, let me het straight to the point. I have one of those batteries, a Victron Multiplus Inverter and a Victron CerboGX and wish to import the battery data into the CerboGX. However, I would prefer to use my Raspberry Pi with a 2-Channel RS485 HAT as the interface. So, perhaps you have the answers to help me, else I must spend time incorporating your scrips into what I have. I would therefore appreciate any assistance to mak life a lot easier for me.

Release v0.12 is available

https://github.com/Louisvdw/dbus-serialbattery/releases/tag/v0.12

The big changes are for fixing issues experienced with the driver on 2.80/2.90 firmware interfering with other devices, Tian/Revov BMS support and fixes for Daly BMS values.

Hi Louis,
i just installed V 0.12 and it is working flawlessly with two battery banks connected via two JK-BMS systems.

One question though: It says in the release notes that the single cell voltage feature was added, but it seems to me that the corresponding files did not make the cut into the building files list. Is there something that i overlooked?

Hello,

I have a few questions:

1) In the discussion, I noticed that so far GX cannot display two or more batteries controlled by BMS (JK or other) ... but displays one according to the given some principle :) it is possible for GX to display it as one calculated battery in the sum of total capacity ??? For me it's OK :P

2) I also noticed in the discussion that the charging and discharging voltage / current of a specific battery pack should be seen via VRM ... that is, if I read it correctly :) If it's true then 1) it's simply OK

3) if I have 3 pcs of mppt blue solar (not smart) I will be able to behave as one, resp. will I have the same functionality as smartMppts thought: master; slave; slave?

I got ordered 2x JK-B2A24S20P (CAN) and have 2ps of 16cells battery lifepo4 packs...
I hope it will work without battery graphic monitoring properly :)

thank you very much.

I'm having trouble installing v12

With script, I have these errors:

And via USB flash drive, nothing happens too..

I also lost v10 that was working nicely.

Could it be because I'm running Venus OS 2.72 large?

About the Multi Battery development...

For those of us who just use the driver for monitoring purposes (in my case, I monitor my 2 DIY Battery banks with a Pi 3B+) and don't actually use the Multi and Driver to change anything, the only real existing limitation is the Instance ID that is always the same for all banks/BMSs. This prevents VRM to show record values and show history of all but one Battery/ BMS, which is a pitty. For me, that's the most important thing missing - being able to monitor in VRM all banks.

But, for all other features, I'm perfectly happy as it is. It doesn't matter which bank SOC is shown on the venus OS gui.

If any development is being made to change this, can we have the option of not doing anything regarding SOC average and so on? Maybe just a selection of which bank is shown on gui?

Hello Louis,

i use your serial battery driver. great thing thanks!
I have a problem that my lifepo4 only charges with 80 watts for hours...

If I remove the RS485 connection to the raspberry, the mppt charge controller is no longer controlled externally and the charging power increases considerably.

settings of the parameters are:

CVL: 28.4V
CCL: 50A
DCL: 100A

these are also the settings of my daly bms, i limited my end-of-charge voltage to 26.8V in the dvcc menu.

I can't explain where the problem is. do you have any idea?

Hi,

I developed an adapter with ESP32 that read the data from JKBMS and send some info over CANbus to MultiPlus II GX invertor. I used the SMA/Pylontech CAN frames specifications.

Everything is Ok with only exception that GX limits the charge voltage on MPPT to 52.4V. My battery is Li-Ion 15S with 61.3V Absorption/Float. Due to 52.4V limit, the MPPT is stuck and not charging the battery that need from 52.5V to 61.3V.

How I can I change the charge voltage limit on MPPT when it is controlled by BMS? I attached the pictures.

Also, I configured ESS with CAN BUS BMS

I did more tries with CAN frames for manufacturer and data and somehow I triggered a LG Resu battery that changed the charger voltage on MPPT to 57.4V. I bit better but still not enough got my 61.3V needs.

It seams that Victron hardcoded the charge voltages in case of BMS controlled as per Battery vendor. I found out that for instance BMZ ESS 7.0 use the same SMA Can protocol and it has a high charge voltage value. The question is how can I trigger this model from BMZ? What kind of info should I send over CAN to have in VRM a BMZ ESS battery? Probably I need to add specific info for 0x35E and 0x35F frames but I don't know the values.

Do you know how Victron Venus OS driver identifies the product ID from those CAN frames? For example, Pylontech has 0xB009 and LG Resu has 0xB004. I didn't send those ID explicitly over CAN, so somehow VE.Can driver identified BMS from what I sent over CAN, al frames from the attached picture.

I am now trying to connect, 16S Li Ion 3.7V batterybank with multiple ANT 16S BMS.

I want to achieve 64V charging (4V per cell). I need 18 banks all with different MAC adresses in total of 250kWh.

Did anyone make something simmilar here ? Any success doing so ?

Can anyone help with such a project ?

I will be very gratefull for any help.

Hello @Louis van der Walt ,

great work and thank you for the effort.
I ve installed it on my raspberry (with venusOS 2.89) and i have an issue.
I have a JKBMS on my battery and the system recognise it as Sinowealth.
Is there any way to bypass this cause the battery stats are all over the place.

Thank you in advance

dev.list.PNGdvcc.PNGservices.PNGvnus os.PNG

@ @all

Hi, what I make wrong ?

I have pi2, on it installed venus 2.89 and I try to concect at them via RS485 JKBMS... i have two BMS JK-B2A24S20P... but I cant conneto with them :(

I try to use USB to UART PL2303HX (this is working with ve.direct comunication) , now I try to use USB to RS485 with recomended FTDI FT232R I try to change RX - A ; TX - A | TX - B ; RX - B ... nothing, connectet without Vcc... there it is battery voltage :o

Rx - Tx on converter blink every 15s.

What I make wrong ? I can belive that two pieces of BMS sould be bad... one OK but two :D It is necessary set baud rate in configs or some else ? whats the name of config file it is this "vi /data/etc/dbus-serialbattery/utils.py"

I will be endlessly happy if I find a bug and it starts to communicate and I will finally be able to monitor the batteries...

If anyone has had similar problems and has experience, pls. advise what helped you? Thank you.

pi2_setup.PNGpi2_setup serialdbutils.PNGlog.PNGlog2.PNG

Planning to upgrade my 3 DIY lithium batteries ( with JK BMS ) with the DBus Serial driver of yours ( Louis ) in the Venus . I currently have a BMV702 which I would like it to be the reference device for SOC/ DC voltage and current measurements and dashboard information. Do I have to ensure this is powered up first so that the VRM sees this as "master"? Is there anyone out there that can share a VRM advanced *.csv file from a system with Smartshunt/ BMV 70x and a JK BMS ( preferably 2 or more ) that would be greatly appreciated

I'm using 2 jkbms in one system... unfortunately they both have the same VRM Instance number, which means only one can be logged in the VRM Portal. What is more annoying is that I can't choose which one I want to log. It is always the one that connects first to my VenusGX (regardless of which USB port I will use).

@Louis van der Walt is there any progress to get it fixed and have different VRM Instance numbers for multiple BMS's? Or is there any workaround to log the bms that I want, not the one that connects first? (for example to log the BMS that is connected to ttyUSB0 port even if the BMS from ttyUSB1 connects first)

@Louis van der Walt

First of all thanks for the driver.

I have a Multiplus 2 48/5000 that can charge with 70A and discharge with 50A. Now I've read that your driver has a limit of 50A when loading. I have already changed the MAX_BATTERY_CURRENT setting to 70A in utility.py but nothing changes. Especially now that the sun is no longer shining through, it would be good if you could charge with higher power, i.e. faster. Or did I miss something?

Really excited to get this working with my new setup....thanks for making it possible. Any progress towards multiple BMSs?

At last installed the ddbusdriver 0.13 to my Venus v2.91 and have found an interesting issue . I have the recommended Victron radiation sensor connected using Victron RS485-USB interface module . The JK BMS is connected via Waveshare RS485-USB interface unit. The issue is that it seems you have to start the radiation sensor first else it will not work with the JK-BMS. If you reboot the unit all connected - sometimes the radiation sensor will not work and other times it will. I also have an ET112 connected to Venus. Both the radiation sensor and JK BMS are given VRM instance of 1. Any ideas what the issue could be ?

Hello, everyone,

I use the current beta with my 16s Daly BMS.

How or where can I have the cell voltages displayed? The sol but recently go if I'm properly informed?

I have 2 x Renogy Lithium batteries. For both to read out with this do I need 2 x the Renogy USB cables? I have tried with a couple of USB to RS485 leads but I suspect the FDMI or RS485 magic bit was missing. Or, is there something I need to do to have both batteries display?

Thank you in advance and thanks for your driver.

Hi @Louis van der Walt can u help me to connect my battery Huawei ESM 48100.

I can read all info battery use USB to TTL use software. But i dnt know command to call BMS.

If u can, i will send you this software. Thankyou

Hi!
Thank You so much for your great work!
I am replacing my JBD BMS now and want to buy JK BMS.

Is the following version (BT/RS485) working with Victron/ Serialbattery?
Or do I need the version with CANBUS also?

Thank You!

Hi Louis, first of all thank you for your excellent work on this driver.

I have installed driver on RPi4 Rev 1.5 Venus OS (Large v. 2.92) , having one Victron BMV-712and two 12V250A Daly BMS's connected. Everything worked great as a start, but after some hours the Victron BMV-712 suddenly started using the wrong driver causing below errors.

Is it possible to lock the Victron BMV-712 to NOT use the SerialBattery Sinowealth driver?

Thanks in advance.

Now have my 3 JK-BMS running beautifully and am finding tricky to work out which of the 3 BMS's is the Active one controlling DVCC ? Is there direct method to determine that ( that is without analysing the VRM portal for changes in charge current limits ) ? Well done to great battery driver Louis.

Hi all, is there a way to use the driver on a Raspberry Pi to have a relay switch when a certain cell voltage is reached? About the total voltage I could realize it via the load output of my Victron Smartsolar charge controller, but this is rather suboptimal. I want to activate or deactivate one of the well-known active balancers automatically when a certain cell voltage is reached and not have it running permanently. Andy from Off-Grid Garage has recently published an interesting video about a JBD-BMS on steroids that can do exactly this.

Edit:

Found the answer

Hello Louis,

the linear current limitation is really a great feature. I tested it today and noticed big jumps in the current due to jumps in the cell voltages. Is it possible to define a damping?

Lets say, using an average of the last n seconds for cell voltages.

Cheers,

luphi

Anyone here have this working with EG4 LifePower4 12v/400ah batteries? (Cerbo, v2.92, usb provided by signature solar) I've run into a few issues, mostly user error which Louis was kind enough to point out and help resolve. Still having some issues, however. Was interested to see what others with this setup have seen to see what I could still be doing wrong. Thanks.

Hi I wanted to adjust the charge and discharge currents. For this I have adjusted utils.py unfortunately the default values are still displayed in Venus os. Does anyone have an idea?

# -*- coding: utf-8 -*-
import logging
import serial
from time import sleep
from struct import *
import bisect

# Logging
logging.basicConfig()
logger = logging.getLogger("SerialBattery")
logger.setLevel(logging.INFO)

# battery types
# if not specified: baud = 9600
battery_types = [
    {'bms' : "LltJbd"},
    {'bms' : "Ant", "baud" : 19200},
    {"bms" : "Daly", "address" : b"\x40"},
    {"bms" : "Daly", "address" : b"\x80"},
    {"bms" : "Jkbms", "baud" : 115200},
#    {"bms" : "Sinowealth"},
    {"bms" : "Lifepower"},
    {"bms" : "Renogy", "address": b"\x30"},
    {"bms" : "Renogy", "address": b"\xF7"},
    {"bms" : "Ecs", "baud" : 19200},
#    {"bms" : "MNB"},
]

# Constants - Need to dynamically get them in future
DRIVER_VERSION = 0.14
DRIVER_SUBVERSION = '.3' 
zero_char = chr(48)
degree_sign = u'\N{DEGREE SIGN}'

# Choose the mode for voltage / current limitations (True / False)
# False is a Step mode. This is the default with limitations on hard boundary steps
# True "Linear"    # New linear limitations by WaldemarFech for smoother values
LINEAR_LIMITATION_ENABLE = False

######### Cell Voltage limitation #########
# Description:
# Maximal charge / discharge current will be in-/decreased depending on min- and max-cell-voltages
# Example: 18cells * 3.55V/cell = 63.9V max charge voltage. 18 * 2.7V = 48,6V min discharge voltage
#          ... but the (dis)charge current will be (in-/)decreased, if even ONE SINGLE BATTERY CELL reaches the limits

# Charge current control management referring to cell-voltage enable (True/False).
CCCM_CV_ENABLE = True
# Discharge current control management referring to cell-voltage enable (True/False).
DCCM_CV_ENABLE = True

# Set Steps to reduce battery current. The current will be changed linear between those steps
CELL_VOLTAGES_WHILE_CHARGING         = [3.55, 3.50, 3.45, 3.30]
MAX_CHARGE_CURRENT_CV                = [   0,    2,  30,  60]

CELL_VOLTAGES_WHILE_DISCHARGING      = [2.70, 2.80, 2.90, 3.10]
MAX_DISCHARGE_CURRENT_CV             = [   0,    5,  30,  60]

######### Temperature limitation #########
# Description:
# Maximal charge / discharge current will be in-/decreased depending on temperature
# Example: The temperature limit will be monitored to control the currents. If there are two temperature senors,
#          then the worst case will be calculated and the more secure lower current will be set.
# Charge current control management referring to temperature enable (True/False).
CCCM_T_ENABLE = True
# Charge current control management referring to temperature enable (True/False).
DCCM_T_ENABLE = True

# Set Steps to reduce battery current. The current will be changed linear between those steps
TEMPERATURE_LIMITS_WHILE_CHARGING    = [55, 40,  35,   5,  2, 0]
MAX_CHARGE_CURRENT_T                 = [ 0, 28, 60, 60, 28, 0]

TEMPERATURE_LIMITS_WHILE_DISCHARGING = [55, 40,  35,   5,  0, -20]
MAX_DISCHARGE_CURRENT_T              = [ 0, 28, 60, 60, 28,   0]

# if the cell voltage reaches 3.55V, then reduce current battery-voltage by 0.01V
# if the cell voltage goes over 3.6V, then the maximum penalty will not be exceeded
# there will be a sum of all penalties for each cell, which exceeds the limits
PENALTY_AT_CELL_VOLTAGE  = [3.45, 3.55, 3.6]
PENALTY_BATTERY_VOLTAGE  = [0.01, 1.0, 2.0]  # this voltage will be subtracted


######### SOC limitation #########
# Description:
# Maximal charge / discharge current will be increased / decreased depending on State of Charge, see CC_SOC_LIMIT1 etc.
# The State of Charge (SoC) charge / discharge current will be in-/decreased depending on SOC.
# Example: 16cells * 3.45V/cell = 55,2V max charge voltage. 16*2.9V = 46,4V min discharge voltage
# Cell min/max voltages - used with the cell count to get the min/max battery voltage
MIN_CELL_VOLTAGE = 2.9
MAX_CELL_VOLTAGE = 3.45
FLOAT_CELL_VOLTAGE = 3.35
MAX_VOLTAGE_TIME_SEC = 15*60
SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT = 90

# battery Current limits
MAX_BATTERY_CHARGE_CURRENT = 80
MAX_BATTERY_DISCHARGE_CURRENT = 100

# Charge current control management enable (True/False).
CCCM_SOC_ENABLE = True
# Discharge current control management enable (True/False).
DCCM_SOC_ENABLE = True

#charge current soc limits
CC_SOC_LIMIT1 = 98
CC_SOC_LIMIT2 = 95
CC_SOC_LIMIT3 = 91

#charge current limits
CC_CURRENT_LIMIT1 = 5
CC_CURRENT_LIMIT2 = MAX_BATTERY_CHARGE_CURRENT/4
CC_CURRENT_LIMIT3 = MAX_BATTERY_CHARGE_CURRENT/2

#discharge current soc limits
DC_SOC_LIMIT1 = 10
DC_SOC_LIMIT2 = 20
DC_SOC_LIMIT3 = 30

#discharge current limits
DC_CURRENT_LIMIT1 = 5
DC_CURRENT_LIMIT2 = MAX_BATTERY_DISCHARGE_CURRENT/4
DC_CURRENT_LIMIT3 = MAX_BATTERY_DISCHARGE_CURRENT/2

# Charge voltage control management enable (True/False).
CVCM_ENABLE = False

# Simulate Midpoint graph (True/False).
MIDPOINT_ENABLE = False

#soc low levels
SOC_LOW_WARNING = 20
SOC_LOW_ALARM = 10

# Daly settings
# Battery capacity (amps) if the BMS does not support reading it 
BATTERY_CAPACITY = 50
# Invert Battery Current. Default non-inverted. Set to -1 to invert
INVERT_CURRENT_MEASUREMENT = 1

# TIME TO SOC settings [Valid values 0-100, but I don't recommend more that 20 intervals]
# Set of SoC percentages to report on dbus. The more you specify the more it will impact system performance.
# TIME_TO_SOC_POINTS = [100, 95, 90, 85, 80, 75, 70, 65, 60, 55, 50, 45, 40, 35, 30, 25, 20, 15, 10, 5, 0]# Every 5% SoC
# TIME_TO_SOC_POINTS = [100, 95, 90, 85, 75, 50, 25, 20, 10, 0]
TIME_TO_SOC_POINTS = []# No data set to disable
# Specify TimeToSoc value type: [Valid values 1,2,3]
# TIME_TO_SOC_VALUE_TYPE = 1      # Seconds
# TIME_TO_SOC_VALUE_TYPE = 2      # Time string HH:MN:SC
TIME_TO_SOC_VALUE_TYPE = 3        # Both Seconds and time str "<seconds> [days, HR:MN:SC]"
# Specify how many loop cycles between each TimeToSoc updates
TIME_TO_SOC_LOOP_CYCLES = 5
# Include TimeToSoC points when moving away from the SoC point. [Valid values True,False] 
# These will be as negative time. Disabling this improves performance slightly.
TIME_TO_SOC_INC_FROM = False


# Select the format of cell data presented on dbus. [Valid values 0,1,2,3]
# 0 Do not publish all the cells (only the min/max cell data as used by the default GX)
# 1 Format: /Voltages/Cell# (also available for display on Remote Console)
# 2 Format: /Cell/#/Volts
# 3 Both formats 1 and 2
BATTERY_CELL_DATA_FORMAT = 1

# Settings for ESC GreenMeter and Lipro devices
GREENMETER_ADDRESS = 1
LIPRO_START_ADDRESS = 2
LIPRO_END_ADDRESS = 4
LIPRO_CELL_COUNT = 15

def constrain(val, min_val, max_val):
    if min_val > max_val:
        min_val, max_val = max_val, min_val
    return min(max_val, max(min_val, val))

def mapRange(inValue, inMin, inMax, outMin, outMax):
    return outMin + (((inValue - inMin) / (inMax - inMin)) * (outMax - outMin))

def mapRangeConstrain(inValue, inMin, inMax, outMin, outMax):
    return constrain(mapRange(inValue, inMin, inMax, outMin, outMax), outMin, outMax)

def calcLinearRelationship(inValue, inArray, outArray):
    if inArray[0] > inArray[-1]:    # change compare-direction in array
        return calcLinearRelationship(inValue, inArray[::-1], outArray[::-1])
    else:
 
        # Handle out of bounds
        if inValue <= inArray[0]:
            return outArray[0]
        if inValue >= inArray[-1]:
            return outArray[-1]
        
        # else calculate linear current between the setpoints
        idx = bisect.bisect(inArray, inValue)
        upperIN  = inArray[idx - 1]  # begin with idx 0 as max value
        upperOUT = outArray[idx - 1]
        lowerIN  = inArray[idx]
        lowerOUT = outArray[idx]            
        return  mapRangeConstrain(inValue, lowerIN, upperIN, lowerOUT, upperOUT)

def calcStepRelationship(inValue, inArray, outArray, returnLower):
    if inArray[0] > inArray[-1]:    # change compare-direction in array
        return calcStepRelationship(inValue, inArray[::-1], outArray[::-1], returnLower)
    
    # Handle out of bounds
    if inValue <= inArray[0]:
        return outArray[0]
    if inValue >= inArray[-1]:
        return outArray[-1]
    
    # else get index between the setpoints
    idx = bisect.bisect(inArray, inValue)
        
    return outArray[idx] if returnLower else outArray[idx-1]

def is_bit_set(tmp):
    return False if tmp == zero_char else True

def kelvin_to_celsius(kelvin_temp):
    return kelvin_temp - 273.1

def format_value(value, prefix, suffix):
    return None if value is None else ('' if prefix is None else prefix) + \
                                      str(value) + \
                                      ('' if suffix is None else suffix)

def read_serial_data(command, port, baud, length_pos, length_check, length_fixed=None, length_size=None):
    try:
        with serial.Serial(port, baudrate=baud, timeout=0.1) as ser:
            return read_serialport_data(ser, command, length_pos, length_check, length_fixed, length_size)

    except serial.SerialException as e:
        logger.error(e)
        return False


# Open the serial port
# Return variable for the openned port 
def open_serial_port(port, baud):
    ser = None
    tries = 3
    while tries > 0:
        try:
            ser = serial.Serial(port, baudrate=baud, timeout=0.1)
            tries = 0
        except serial.SerialException as e:
            logger.error(e)
            tries -= 1
            
    return ser

# Read data from previously openned serial port
def read_serialport_data(ser, command, length_pos, length_check, length_fixed=None, length_size=None):
    try:
        ser.flushOutput()
        ser.flushInput()
        ser.write(command)

        length_byte_size = 1
        if length_size is not None: 
            if length_size.upper() == 'H':
                length_byte_size = 2
            elif length_size.upper() == 'I' or length_size.upper() == 'L':
                length_byte_size = 4

        count = 0
        toread = ser.inWaiting()

        while toread < (length_pos+length_byte_size):
            sleep(0.005)
            toread = ser.inWaiting()
            count += 1
            if count > 50:
                logger.error(">>> ERROR: No reply - returning")
                return False
                
        #logger.info('serial data toread ' + str(toread))
        res = ser.read(toread)
        if length_fixed is not None:
            length = length_fixed
        else:
            if len(res) < (length_pos+length_byte_size):
                logger.error(">>> ERROR: No reply - returning [len:" + str(len(res)) + "]")
                return False
            length_size = length_size if length_size is not None else 'B'
            length = unpack_from('>'+length_size, res,length_pos)[0]
            
        #logger.info('serial data length ' + str(length))

        count = 0
        data = bytearray(res)
        while len(data) <= length + length_check:
            res = ser.read(length + length_check)
            data.extend(res)
            #logger.info('serial data length ' + str(len(data)))
            sleep(0.005)
            count += 1
            if count > 150:
                logger.error(">>> ERROR: No reply - returning [len:" + str(len(data)) + "/" + str(length + length_check) + "]")
                return False

        return data

    except serial.SerialException as e:
        logger.error(e)
        return False

Hi,

first of all thanks. Awesome work.

My installation is in my boat.

I have 5 batteries, each is 4 * 200ah CALB cells in series.

The 5 batteries are connected in parallel.

Out of the 20 cells, there are 2 cells that are lazy. Slow to change and fast to discharge. I will be replacing them.

However, the system works really well.

As it is a boat, usage varies. When it’s Not being used, the solar keeps the batteries full. When it is being used, the batteries cycle.

I have changed the utils code a little. I have put a storage max voltage and a storage float voltage that I can hash in or out. I don’t like keeping lifepo4 batteries at 100% when not being used.

Could you take a quick look, and let me know if you think this is a reasonable idea.

Secondly, as there are 5 bms, but only one is controlling, should I change the charge and discharge amps to 500?
they are 120a bms. Each bms will still limit the current to its own battery to 120a

here is my change to the code..

Hi,

first of all thanks. Awesome work.

My installation is in my boat.

I have 5 batteries, each is 4 * 200ah CALB cells in series.

The 5 batteries are connected in parallel.

Out of the 20 cells, there are 2 cells that are lazy. Slow to change and fast to discharge. I will be replacing them.

However, the system works really well.

As it is a boat, usage varies. When it’s Not being used, the solar keeps the batteries full. When it is being used, the batteries cycle.

I have changed the utils code a little. I have put a storage max voltage and a storage float voltage that I can hash in or out. I don’t like keeping lifepo4 batteries at 100% when not being used.

Could you take a quick look, and let me know if you think this is a reasonable idea.

Secondly, as there are 5 bms, but only one is controlling, should I change the charge and discharge amps to 500?
they are 120a bms. Each bms will still limit the current to its own battery to 120a

here is my change to the code..

Hello,

I also use these drivers on my Pi with an 8s Daly BMS. Thanks for that! Currently I only operate a Smart MPPT and a China inverter.

However, Venus OS does not show me if the battery is only charged with 50w. The MPPT states 50W in Venus, but according to the display nothing goes into the battery. I don´t knwo where it goes... The China Inverter is switched off.

If the battery is being discharged, charging will be displayed.

So exactly the wrong way around.

Is that because of a setting? Or is it the Daly? Or on Venus?

Best regards

Sebastian

I have a big problem to get this to work stable.

I use a multiplus II gx. Venus os 2.92

I use this adapter with a jk bms

https://www.amazon.de/dp/B07RQ8TVRJ?ref=ppx_yo2ov_dt_b_product_details&th=1

In idle mode there is no problem, but when i start to charge the driver fails

n 30 21:36:11 nanopi user.info kernel: [ 3665.493167] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
Jan 30 21:36:14 nanopi user.err kernel: [ 3668.033304] usb usb3-port1: disabled by hub (EMI?), re-enabling...
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.040062] usb 3-1: USB disconnect, device number 110
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.054007] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.062974] ftdi_sio 3-1:1.0: device disconnected
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.499668] usb 3-1: new full-speed USB device number 111 using ohci-platform
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.781684] usb 3-1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.790076] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.797388] usb 3-1: Product: FT232R USB UART
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.801943] usb 3-1: Manufacturer: FTDI
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.805790] usb 3-1: SerialNumber: AB0OH9VB
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.815769] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.822842] usb 3-1: Detected FT232RL
Jan 30 21:36:14 nanopi user.info kernel: [ 3668.832309] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
Jan 30 21:36:18 nanopi user.err kernel: [ 3672.468275] usb usb3-port1: disabled by hub (EMI?), re-enabling...

[ 3049.484634] ftdi_sio ttyUSB0: Unable to write latency timer: -62
[ 3049.491606] ftdi_sio 3-1:1.0: GPIO initialisation failed: -62
[ 3049.497664] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 3049.505482] usb usb3-port1: disabled by hub (EMI?), re-enabling...
[ 3049.511737] usb 3-1: USB disconnect, device number 124
[ 3049.517392] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 3049.526312] ftdi_sio 3-1:1.0: device disconnected
[ 3049.959866] usb 3-1: new full-speed USB device number 125 using ohci-platform
[ 3050.241689] usb 3-1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 3050.250001] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3050.257180] usb 3-1: Product: FT232R USB UART
[ 3050.261619] usb 3-1: Manufacturer: FTDI
[ 3050.265463] usb 3-1: SerialNumber: AB0OH9VB
[ 3050.274767] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected
[ 3050.281627] usb 3-1: Detected FT232RL
[ 3050.290461] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 3051.866334] usb usb3-port1: disabled by hub (EMI?), re-enabling...
[ 3051.873108] usb 3-1: USB disconnect, device number 125
[ 3051.882878] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 3051.891804] ftdi_sio 3-1:1.0: device disconnected
[ 3052.309645] usb 3-1: new full-speed USB device number 126 using ohci-platform
[ 3052.591634] usb 3-1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 3052.600111] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3052.607349] usb 3-1: Product: FT232R USB UART
[ 3052.612432] usb 3-1: Manufacturer: FTDI
[ 3052.616343] usb 3-1: SerialNumber: AB0OH9VB
[ 3052.625819] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected
[ 3052.632666] usb 3-1: Detected FT232RL
[ 3052.641121] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0

How does it behave in the meantime with the charging of two batteries that are connected in parallel, each with its own BMS, to the Victron? In my case, an Easysolar II GX.
I currently have a 24V/230Ah battery (connected to Daly BMS via RS485) installed which also works wonderfully. I now unexpectedly, an almost identical, came into the hands (This time CALB cells instead of EVE), same capacity, same BMS. Should now, for whatever reason, one battery is full earlier, the other does not continue to charge, because the charging voltage is reduced, right? How did you solve this most elegantly? A smartshunt is also available.

@Louis van der Walt I am getting ready to replace my drop in LifePo4 batteries with 2 diy banks with Daly smart bms x2. Is this driver able to communicate to both Daly bms and combine them into one "virtual" battery bank? Or would I need to use the virtual battery bank thru node red?

JBD BMS blocking charger from charging

Setting up a new system with 3,7v Lith Ion 18650 charged via Victron MPPT
I have a
Victron 30/100 MPPT
JBD BMS 60a
DIY battery 18650 lithium ion 7x3.7v 180ah 24v
RPI Venus OS large v2.9 with node red enabled
SerialBattery 0.14.3

I have changed Victron 100/30 MPPT settings using the Victron Connect
29.05v Absorption
29.05V Float
29.05v Equalization

I have changed the SerialBattery utils.py to

utils.py
MIN_CELL_VOLTAGE = 3.6
MAX_CELL_VOLTAGE = 4.1
FLOAT_CELL_VOLTAGE = 4.1
MAX_VOLTAGE_TIME_SEC = 15*60
SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT = 90

I have set the JBD BMS to

FullChargeVol 4150
ChargeEndVol 3000
BalanceStartVoltage 4000

In Remote Console
DVCC set

and REBOOTed

But there is something not allowing it to charge.

Victron Connect shows no reason, only showing

Status ON

When i look at the Remote Console Devicelist>SerialBattery JBD> IO

> Parameters
It shows the Allow to charge set to NO and ChargeCurrentLimit to 0.00A

If I disconnect the JBD BMS from the RPI it all charges up nicely. Its been taxing me on an off for over a week now so any ideas as to where i have gone wrong or what i could try would be gratefully appreciated.

Hello, Luis,

I have to change the current limits ! I need 75A charging current and 150A discharging current!

Best regards, Ulf Schneider

Hello, Louis,

i installed Your driver at Venus OS V2.93 at raspberry Pi3. It works well, but I have to change the current limits. Your driver allows only 50A charging current and 60A discharging current. But i need 75A charging current and 150A discharging current!

Ist there anywhere a config file to find and to change it by ssh?

Best regards and thanks for effort.

Ulf Schneider

Hello, Louis,

i installed Your serial driver at RaspberryPi3 under Venus OSV2.93. It works well. But I have to change the current limit values to 75A charging and 150A discharging. How can i do this? Is there anywhere a config file that can be edited by ssh with nano?

Thanks for effort, best regards, Ulf Schneider

Hallo, Sie müssen die utils.py bearbeiten

sorry, it is new. You must edit the default_config.ini

Recht vielen Dank!

Die utils.py konnte ich nämlich auch nicht finden!

Werde mich heute Abbend mit dem nano Editor daran versuchen und morgen hoffentlich über den Erfolg berichten können.

Dit utils.py muss aber trotzdem vorhanden sein, sonst ist was falsch gelaufen. nur wird diese nicht mehr bearbeitet sondern die default_config.ini

Ich finde die Verzeichnisse und files einfach nicht. Ich habe unter der letzten V2.93 mit diesem Kommando den Batterietreiber online nachinstalliert:

wget https://raw.githubusercontent.com/Louisvdw/dbus-serialbattery/master/etc/dbus-serialbattery/installrelease.sh

Der Treiber lief auf Anhieb:

Aber im Setup Helper warr er weder unter aktiven noch unter inaktiven packages sichtbar:

Dann habe ich im Verzeichnis /data/etc/

nach dbus-serialbattery/utils.py gesucht und nicht gefunden:

Wohl aber ein ähnlich klingendes Verzeichnis dbus-1.

Darunter befinden sich nur diese 3 files:

Aber wenn ich mit dem nano editor auf die system.conf zugreifen will, bekomme ich diese Warnung:

Ich komme einfach als Linux Laie nicht weiter und bitte um Hilfe.

Wenn mir jemand per Team Viewer helfen könnte, das Konfigurationsverzeichnis zu finden, würde ich das auch gerne honorieren wollen.

Ulf Schneider

You will not find this under package manager, that has not been incorporated that way yet. The following typed into ssh terminal should get you there if everything was installed correctly

Vi /data/etc/dbus-serialbattery/utils.py

Danke, ich war einfach im falschen /etc Verzeichnis. Es gibt mehrere gleichnamige in verschiedenen Oberverzeichnissen. Ich habe die utils.py gefunden, die Stromlimits mit nano auf 70A und 100A geändert, reboot gemacht, kontrolliert, daß die neuen Werte in utils.py auch drinstehen, aber es ändert sich Nichts.

Das sehe ich an diesem Limit Fenster im VRM Portal:

BMS Charge and Discharge Limits - SerialBattery(LLT/JBD) [1]

CVL - Charge Voltage Limit (V) CCL - Charge Current Limit (A) DCL - Discharge Current Limit (A)

Es zeigt die alten Limits 50 und 60A.

Bonzai gab mir diesen Hinweis:

bonzai beantwortet · Apr 02 2023 um 7:41 PM

Hallo, Sie müssen die utils.py bearbeiten

sorry, it is new. You must edit the default_config.ini

_______________________________________________________

Aber die default_config.ini finde ich nicht unter diesem Pfad.

Unter welchem kompletten Pfad kann ich die default_config.ini finden?

Danke für die Mühe mit einem DAU. (DAU = dümmster anzunehmender user).

Ulf

Schauen Sie mal in die Remote Console bei dem Treiber, ganz unten Parameter. Dort müßte die Änderung zu sehen sein.

empfehle ich https://github.com/Louisvdw/dbus-serialbattery/issues/421 .

Die ist momentan die neueste Weiterentwicklung

Leider kein Erfolg. Ich habe mit dem Befehl "find" im ganzen Raspberry kein Configfile mit dem Namen "default_config.ini" gefunden:

Mit dem gleichen Befehl konnte ich die utils.py unter dem Pfad /data/etc/dbus-serialbatt/utils.py die utils.py finden und darin mit nano die Lade- und Entladelimits hochsetzten. Ich habe nach reboot auch nochmal kontrolliert, ob die Änderungen auch wirklich übernommen wurden:

Trotzdem sehe ich auf der GUI unter Parameter nicht die geänderten Limits:

Was kann man als Linux Laie mit nur rudimentalen Programmierkenntnissen noch tun?

Ulf