Replies: 9 comments 9 replies
-
Hi The software on the V2 seems is pretty bad with regards to multiple packs (I only have a single pack which works great). Paralleled packs seem to block the ability to send commands so we can only listen to whatever they are sending each other, possibly just 42H (Voltages/Current etc) and 44H (Alarms). When you add in CANbus we then lose pack 0 data, I'm pretty sure you'd have lost pack 0 in Battery Monitor too So my next beta version should handle single packs (sending commands) and multiple packs by just listening and processing any response whatever it is for multiple packs. This pretty much works at the moment but the way Home Assistant sets up the sensors has become the issue as it doesn't like setting them up "on the fly" as data comes in so just trying to rework that part to get it to work as I expected. |
Beta Was this translation helpful? Give feedback.
-
First of all: great job! |
Beta Was this translation helpful? Give feedback.
-
Dit a test with i believe beta version 1.1.17 test only version. As mentioned Seplos BMS 10E using protocol 2, |
Beta Was this translation helpful? Give feedback.
-
version 1.1.9 tested. same results. |
Beta Was this translation helpful? Give feedback.
-
Correct. But if you look at chematics it’s all connected . As soon as I leave the dongel in the usb input and the rj45 in the first batterypack victron gives an internal error. If I can find time I could check if this also occurs with original seplos pc software. Can’t recollect that it ever did. Look also at the dip settings to connect to victron. It’s can related not rs458. OTOH battery 1 has dp 5 an 6 on.. dipswitches are set only for canVerstuurd vanaf mijn iPhoneOp 24 mrt 2024 om 22:22 heeft flip555 ***@***.***> het volgende geschreven:
Oh ok, that's not what we want!
It shouldn't be interfering with the Cerbo though as that would be on your BMS's CAN port not the BMS's RS485 ports. The addon is setup to just listen/sniff the serial for multiple packs.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Well different BMS ? Also, not related to BMS connector but noteworthy to pay attention to: you got 1 battery right? Connected to Victron an have put settings for port VCTRN. Switch off the battery, mine has on the back a switch and switch on again. Now VCTRN can port setting is gone and set back to the default gives internal failure as result in victron. Verstuurd vanaf mijn iPhoneOp 25 mrt 2024 om 01:39 heeft flip555 ***@***.***> het volgende geschreven:
Thanks very strange I've not checked out any schematics etc It is hard to work with as I only have a single pack so maybe I should persuade myself to buy another pack soon :)
After some thought, you said V3 on v1.0.5 showed data, did this version mess the Cerbo up also? If not it sounds like it could be because we open the RS485 port and keep it open, listening always; on v1.0.5 it just opens connection, sends command gets response and closes, repeats every 5seconds.
One thing that would conflict with that theory is my battery, its connected to my Cerbo too and works fine using the same code but again its just a single pack which just seems to work.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Andere mogelijkheid is om de code van Victron te bekijken. Zie je remote console daar worden een aantal zaken binnen geslurpt: hoeveelheid packs, min Max cel en dat met vermelding van pack. Etc…. Verstuurd vanaf mijn iPhoneOp 26 mrt 2024 om 21:02 heeft flip555 ***@***.***> het volgende geschreven:
Ah yes! I've reset mine to Victron so many times, mines currently sitting on PNG_DYE i think doesn't have any errors on mine just most of the parameters are missing in Cerbo for the BMS.
Thanks you've given me quite a lot of useful information in your posts, I think maybe I'll have to reach out to Seplos with some of these issues before continuing trying to support multiple V2's as it really does look like its a problem with the Seplos software when running with CAN connected.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
v1.1.0 donde puedo conseguir? es buena version para varias baterias en paralelo en un pasado me funciono. |
Beta Was this translation helpful? Give feedback.
-
Do i have to connect the rs485>usb adapter to the usb of Home Assistant? I have no option for that. Can it be used directly to the usb port of the Cerbo and which port do i use? |
Beta Was this translation helpful? Give feedback.
-
i am trying to get this repo to work. I am using the seplos rs458 to usb. It needs a baudrate 19500
Have a victron can bus and 4 batteriepacks on the rsbus as master and slave. Seplos BMS version is 10E and its version 2
After install in hacks and adding the integration with pack adress 0x00 and ttyUSB0 there is no population of sensors.
If i install the bms connector (after completely remove the integration and in hacs) and use pack adress 0x01 there are two hubs vissible in the integration section but no population of sensors.
Plugging the device ass is in a windows system and start the seplos software there is straight away connection.
What is the best way to install this repo with multiple packs?
Would like some help and advice how to proceed and am thankfull for any help.
[edit]
after a reboot i got the error:
Deze fout is ontstaan door een aangepaste integratie.
Logger: custom_components.bms_connector.sensor
Bron: custom_components/bms_connector/sensor.py:53
integratie: BMS Connector (documentation, issues)
First occurred: 15:25:07 (1 gebeurtenissen)
Laatst gelogd: 15:25:07
Error setting up BMS sensors: not enough values to unpack (expected 5, got 2)
And:
Deze fout is ontstaan door een aangepaste integratie.
Logger: custom_components.bms_connector.sensor
Bron: custom_components/bms_connector/sensor.py:53
integratie: BMS Connector (documentation, issues)
First occurred: 15:25:07 (4 gebeurtenissen)
Laatst gelogd: 15:33:33
Error setting up BMS sensors: not enough values to unpack (expected 5, got 2)
Error setting up BMS sensors: 'utf-8' codec can't decode byte 0xfc in position 12: invalid start byte
Error setting up BMS sensors: 'utf-8' codec can't decode byte 0xfc in position 3: invalid start byte
Kind regareds,
Beta Was this translation helpful? Give feedback.
All reactions