Usage with two independent BMS #904
Unanswered
smoothfroggy
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello All,
I apologize for the question that may sound slighlty off due to misunderstanding of the structure of the dbus-serialbattery code.
I am in the process of building a system incorporating two REC-ABMS for two independent LiFePO4 packs and circuits for a sail boat:
The charge section of the instrumentation circuit is just an isolated charger hooked upon engine state:
The objective of this structure is to offer some redundancy and possibilities in the event of failure of one component of the system with priority to navigation circuit.
The REC-ABMS firmware incorporates the Victron BMS CAN protocol and is more ore less plug&play on the CAN bus (confirmed by various tests). The BMS of the main circuit is hooked that way and integrates fairly well with the various functions of VenusOS.
For the second BMS, as VenusOS is designed to handle a single BMS, the objective would be to retrieve the operating data for information only (no integration with the VenusOS BMS structure) using a serial link (RS485 also provided by REC-ABMS for monitoring and setup). I understand that there is currently no driver available for the REC-ABMS but I am willing to write the python code as needed.
The question is then about the possibility to use the dbus-serialbattery code to solely retrieve and display BMS data without interfering with the other BMS already integrated. I lack understanding of the part of the code and, possibly more importantly, about the dbus structure that enable BMS integration with the VenusOS standard code.
Thanks in advance for the answers,
Best regards,
SmoothFroggy
Beta Was this translation helpful? Give feedback.
All reactions