-
Notifications
You must be signed in to change notification settings - Fork 132
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
Feature/bmw 3 additional data #249
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice work! Some minor thoughts about webserver!
@@ -306,6 +348,12 @@ static uint16_t battery_prediction_voltage_longterm_charge = 0; | |||
static uint16_t battery_prediction_voltage_longterm_discharge = 0; | |||
static uint16_t battery_prediction_duration_charging_minutes = 0; | |||
static uint16_t battery_target_voltage_in_CV_mode = 0; | |||
|
|||
uint16_t battery_soc = 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
consider making these static
so no other battery tries to use the same name and get conflicts! battery_soc is quite generic :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
What
Additional data fetch from battery. Found additional method to fetch data that was not available before.
Why
Having min/max/avg cell voltage and SOH is needed to know the state and health of the battery.
How
Sending specific CAN messages makes it respond a little later with requested information.