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

app_battery: MAX17205 isn't calculating the pack capacity correctly #101

Open
andrewgreenberg opened this issue Jul 14, 2024 · 0 comments
Open
Labels
battery Battery app task bug Something isn't working

Comments

@andrewgreenberg
Copy link
Member

andrewgreenberg commented Jul 14, 2024

On each OreSat battery card, we have two 2S1P battery packs. Each pack has it's own MAX17205 battery IC which measures voltage, current, and calculates the capacity of the pack it's on.

Voltage, current, and temperature are working just fine.

But for some reason, the capacity measurements (in amp-hours (Ah)) are just terribly off. It's mostly just stuck at either 50% or some very low number. The MAX17205 has two ways of calculating the capacity: by measuring current in and out of the battery, and by measuring the open cell voltage on the cells when it can. Neither method seems to be working correctly.

Some possible ideas:

  • We power cycle the MAX17205 ICs once a day. This IC was never designed to be power cycled, since it's attached to the battery pack directly. So this might be reseting everything, or there's some kind of issue here?
  • We might not be setting up the ICs with the correct values and/or enabling the capacity algorithms in the right way.
@andrewgreenberg andrewgreenberg added bug Something isn't working battery Battery app task labels Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
battery Battery app task bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

1 participant