-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parallel BMS #52
Comments
I know pretty much exactly what I need to do to get multiple packs supported but I just get sidetracked too easily! I'll try and get an update out in the next week or 2, the BMS Connector repo does need a big update to get it inline with a broader project I'm working on If you are able to would you be able to get me an example of the Communications Log from Battery Monitor with parallel packs on? I only have a single pack so would just be testing against data found on other Github repos. Thanks |
Thank you so much for your reply.
Yes, I believe to be able to provide you tomorrow with a Log of multiple packs communication to the Windows App using its Log option.
Best Regards.
Pier
|
DataRecord_20240201_034205.xls here You are the data log. This log file has ben formatted by the Seplos BMS Windows App on a stack of three 1p16s Lifepo4 14kWh packs with Seplos BMS v. 2. Packs are in daisy chain with UTP-RJ45 cables connected to RS485 ports, one end (Pack1) linked to Windows using a RS485 to USB converter. BMS 8bit Switches set are: Pack1 10000000, Pack2 0100000; Pack3 11000000 Let me know if you would like some USB Sniffer Log as well. In such a case do you have a windows app to ssuggest to get it ? Best Regards |
Thanks for that! I have released a version for testing https://github.com/flip555/bms_connector/releases/tag/v1.1.0-TESTING-ONLY You should be able to update to this by going to HACS > BMS Connector > Redownload > Enable Beta Versions and selecting v1.1.0-TESTING-ONLY There is quite a bit missing from it, and needs some streamlining but would be great if you could test it before I add in the rest of the data as I'm only able to test my single battery pack. It does seem to work using test data |
Right now I'm far away from the battery stack to reconnect RS485 daisy chain and test new version. I'll do in a few days, next we.
Regards.
p.
|
I'm 1 week late because I've been focused to solve the issue due using 4 USB, sorry. I'll start tomorrow testing BMS-connector on parallel bms, using a separate Raspi platform. For your information I've found on Github the attached manual, describing parallel bms com protocol starting at pages 22. |
I'm pretty sure parallel won't work with current code from what I've seen on issue #60 - Looks like the main BMS polls the parallel BMS's automatically which all gets dumped into the same serial output (commands and responses) so I need change that part of the code to listen, poll, sort and verify the data before processing/submitting to HA, something I've been playing with today. That document is very nice, looks like it has complete data tables too some of which I was missing. Bluetooth was something I was looking at so I guess I finally have a starting point for that too. I do remember 42H is actually 62H in other documents I think it was the pylontech BMS's they're all very similar. |
Hmm interesting. I've been looking and testing remotely on a paralleled system. It has 3 packs but even listening to the RS485 port just shows pack 1 & 2 - Don't seem to be able to send commands to it though as its all scrolling far too quick. Your .xls communication log posted before also only shows packs 1, 2 and 3 but was a 4 pack battery. Those screenshots show Pack 1 & 2 from a 2 pack so I'm even more confused now as its not missing Pack 0 😂 Looks like there was/is a problem with paralleled batteries but watching Andy @ Off Grid Garage it was working like your 2pack and was switching from Pack 0 to Pack 1, then he enabled dip 5 for CAN and it stopped. Seems to be dip switches and firmware/hardware versions Could you confirm DIP switch setup on your setup? Andy seemed to have
and it worked in Battery Monitor he then changed it to enable CAN for his victron system to
and it stopped working in battery monitor, I'm just thinking a parallel pack starts with 0x01 when CAN is enabled I'm thinking you have:
Or maybe you have automatic dip switch setting enabled? |
Seplos dip switches are very confusing. Depending if you use CAN or not dip switches change, requiring to set dip 5,6,7,8 of first pack to total no. of packs in parallel; in such a case dips 1,2,3,4 starts from 1 instead of 0. I do not use CAN to communicate with inverter. '10000000'. pack1 tomorrow afternoon I'll be at packs location, so I'll configure the whole 4 packs to get the 4 packs log of windows monitor and test the bms connector behaviour at the same dip switch configuration . as well. |
Attached I'm sending you the log of the Seplos Battery Monitor, using a single RS485-USB and 4 batteries in parallel. Dip configuration are: '10000000' pack1 No CAN used. |
Thanks, I think it'll be best to rework it a bit so it adds whichever modbus parts it receives to HA and skips (not errors and exits) when missing a full set of data (42H, 44H, 47H, 51H), then it can poll later if missing/has old data. In the "BMS Modbus Responses" sensor you should have Attributes tab, this should have the latest modbus responses, for each battery pack so I guess I'm nearly where I need to be. |
Comment rewritten to clarify. tested with two packs in parallel Adding hub: Adding hub:
Entity names result to contain 0x00 in both cases. |
last 3 pictures on reverse order. |
BMS Version 🔄
seplos v.2
Connection Method 🌐
USB-RS485
Problem Description 🤔
Currently many installations have battery packs in parallel each one with its own BMS; in my case 4 packs with 4 Seplos x v.2. BMS RS485 ports of all Seplos are linked by UTP cables in a daisy chain configuration and Seplos switches set accordingly with installation manual in order to address each pack and set the total number of packs in parallel. One end of RS485 cable goes to PC Window APP provided by Seplos through a RS485 to USB converter.
The RS485 connection also provides the Master Seplos BMS with the capability to drive the load distribution among each pack of the parallel.
The App provides either a view of all parameters of each single selected pack by clicking the pack number on the Window screen or a recap of all packs parameters in anoher screen.
Currently it appears the BMS Connector doesn't work in this configuration.
Could you please put an eye on the protocol and see if it would be possible to have this upgrade @bms Connector v. 2? Thank you in advance
Proposed Solution 🛠️
I suspect the Seplos protocol adds some preamble string to identify the total number of packs in parallel and the pack address of following data.
Alternatives Considered 🔄
No response
Additional context 📄
No response
The text was updated successfully, but these errors were encountered: