Recent content by Louisvdw

I was a bit busy with work. Did not have time to look much into the driver the past 4 weeks. If you want to look at it look for the issue then you need to look at 2 values for each bms type that both need to be populated to be able to calculate the consumed amp hours. battery.capacity...

The bulk/float/abs states is not something that the driver sets or use. Those are things that are used for lead acid batteries. LA batteries does not have a BMS so the chargers started implementing these charge states to better handle the LA charging. With Litium this all moved to the BMS and we...

Change the Battery Monitor to something else than the driver. DVCC is to read the CCL DCL parameters from the battery but it works along with the Battery Monitor setting.

If the communication protocol is published then normally that is possible.

Nice work @BradCagle You might want to have a look at the work some other guys are doing to do the same with bluetooth for the JKBMS. It is also pretty far along. It would be good if we can all use the same bluetooth libraries. That would make it merging back to the main serial battery project...

I see. I have created a ticket for that as we don't currently populate that path. You can subscribe to it at https://github.com/Louisvdw/dbus-serialbattery/issues/406

Daly have some BMS where the protocol values are swopped. Look for the following line in the utils.py and change it to -1 to swop your value

All the values are published to VRM. You can then create your own custom widgets in the advance tab and should be able to add it in there.

Use 2, but 1 will also work.

Yes if there is a BMS it gets the first piority, but you can then switch that with the Battery Monitor option

If you don't want to use the battery as the monitor, then you have to change the Battery Monitor setting to something else like the Multiplus. What is selected in there will give the system the SOC value. However what you are seeing is what the BMS is trying to tell you. That there is an issue...

The SOC comes from the BMS. The driver reads this value and then publish it to the VenusOS dbus. On the BMS settings (in the app) you will see cell voltage ranges spesified. This is used to adjust the SOC value for any drift that might happen, but normally the SOC is a calculation of the power...

If your JBD BMS has the RS485 port, then you use that to connect using that USB-RS485 adapter. Don't worry about the PC connection. It is easier to set up with the bluetooth app. After the setup, then connect that RS485 adapters you have for the JBD to the GX and it should all just work. You...

I'm planning to add that to the wiki for each BMS.

You need a GX device. This can either be a Multi II GX or another Multi/Phoenix and a seperate GX device like a CerboGX or VenusGX. Or you can install VenusOS on a Raspberry Pi. If you have more items than an inverter in your setup you should already have a GX that control these components.