Closed Justice12t closed 2 months ago
mr-manuel
commented
2 months ago EG4 was not an option on the "bms type" drop down.
Because you did not open the issue in my repository ;)
Can you try with the latest nightly? There it should be fixed. Thank you very much for testing and providing all the needed informations!
Justice12t
commented
2 months ago My bad, sorry!
Yes, that is now working!! everything seems good thus far. I've got 3 batteries in my system total, so I'll have to look at combining them. Thanks for the quick fix!
mr-manuel
commented
2 months ago Is it possible to daisy chain the batteries over RS485 and give them different addresses?
Justice12t
commented
2 months ago Yes, they are currently all connected and different addresses. Would the battery aggregator in your repo work?
mr-manuel
commented
2 months ago Oh ok. I don't know how the batteries behave in this situation, since they are internally connected and not with RS485.
BlueY21
commented
2 months ago Those batteries look like they're connected to each other the same way as Renogy batteries. They probably have or could be set to have unique Modbus device addresses. Then they could all connect to the dbus driver over a single RS485-USB serial cable. They would show on a Cerbo as three batteries.
Justice12t
commented
2 months ago @BlueY21 Yea, I have them set with different addresses. I just don't think the multi battery beta includes the EG4 code. Because when I install it, nothing shows. But when I install the nightly build it seems to work perfect for a single battery.
BlueY21
commented
2 months ago You're right. I think the multi-battery on one cable code may only be in the Renogy module.
On Wed, Jul 3, 2024 at 9:55 PM Justice12t @.***> wrote:
@BlueY21 https://github.com/BlueY21 Yea, I have them set with different addresses. I just don't think the multi battery beta includes the EG4 code. Because when I install it, nothing shows. But when I install the nightly build it seems to work perfect for a single battery.
— Reply to this email directly, view it on GitHub https://github.com/Louisvdw/dbus-serialbattery/issues/1091#issuecomment-2207861090, or unsubscribe https://github.com/notifications/unsubscribe-auth/BC63RO7FHJOBLTV5GHXI2KTZKSTRRAVCNFSM6AAAAABKHWUPHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBXHA3DCMBZGA . You are receiving this because you were mentioned.Message ID: @.***>
mr-manuel
commented
2 months ago I updated the multiple batteries branch. Maybe it works now.
Justice12t
commented
2 months ago Thanks. I can get it to show on the GX now. I seem to be struggling with the modbus address. If I leave it blank in the config.default.ini file it will work for one battery. If I adjust it to 0x31, 0x32, 0x33 as I think it should be with my batteries being numbered 1, 2 and 3 via the dip switches. Is there a command I can run to see what modbus address it is pulling to see if that points me in the right direction? Threw a donation your way. Really appreciate all the work on this.
mr-manuel
commented
2 months ago Please continue in this discussion: https://github.com/mr-manuel/venus-os_dbus-serialbattery/discussions/46
Thank you very much for your donation!
Describe the problem
I installed the nightly build on my GX when I saw the EG4-LL bms added. Figured it could use some testing. It connects and outputs information via the troubleshoot commands but with an error and does not show on my GX device. EG4 was not an option on the "bms type" drop down. 2024-07-02 13:51:32.740628500 TypeError: 'str' object is not callable
Driver version
v1.4x-dev
Venus OS device type
Cerbo GX
Venus OS version
v3.40~33
BMS type
Life/Tian Power
Cell count
4
Battery count
1
Connection type
Serial USB adapter to RS485
Config file
Relevant log output
Any other information that may be helpful
No response