Skip to content
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

[BUG] BMW I3 double, data not colecting. #926

Open
havrla opened this issue Mar 1, 2025 · 0 comments
Open

[BUG] BMW I3 double, data not colecting. #926

havrla opened this issue Mar 1, 2025 · 0 comments
Labels

Comments

@havrla
Copy link

havrla commented Mar 1, 2025

Situation:
Double battery setup: the first LilyGO communicates with the batteries, while the second one communicates with the inverter.

  1. lilygo double battery 50A balancing 25 and 25A , perfect .
    Image

  2. lilygo reporting only first battery. 2. lily must reporting colecting data to Invertor .
    Image

Please fix, 2. lilygo must reporting colecting data to invertor.
SOC Management:
0–50%: The battery with the lower SOC is used.
50–100%: The battery with the higher SOC is used.

Energy in Wh – simply sum the values.

Temperatures – use the highest and lowest values from the entire system.

Charging and Discharging Power Strategy
This is an interesting strategy. Fortunately, the battery has sufficient power, exceeding that of standard inverters, so we can simplify the approach.
1.Maximum charging and discharging power will be reported from the battery that reports the lower value.
2. If a better strategy is proposed, it can be considered, but the minimum strategy is:
If the reported power value is 0, external charging should be stopped.

Regarding the values of individual cells, compare all cells (i.e., 2 × 96), and report the maximum and minimum values.

Note: Some BMS/batteries from around 2013 do not immediately send valid data after startup. Instead, they start transmitting accurate values after approximately 1 minute to 1 hour.
For example, in the first screen, the second battery reports 3.7V per cell, but this is not the real value—it’s just a default value for the emulator until it reads the correct data from CAN. Similarly, an SOH of 99% is also incorrect but eventually corrects itself over time.

thanks thanks

@havrla havrla added the Triage label Mar 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant