-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Multiple battery module support #12033
Comments
I should add that I tried testing what happens on fmuv5 with two bricks. It always reads from port 1 if two are plugged in. If you remove one it reports the other one instantly but not two at a time. |
@ryanjAA This still being worked on? |
FYI @ItsTimmy |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
I am still experiencing QGC only reading one of the batteries on master (1.13.0) with a CUAV x7 board. Trying to see where the issue lies but I've been tackling it all week and haven't found it yet. |
When two Power-modules are connected, the two voltage are readable but only the first "active" one show current... |
@brunweil if you have a particular feature request (or even possible bug?) could you please open a new issue and share more details like your particular board, maybe a flight log to see the data, etc. Typically the dual modules have been used for redundant general batteries, but more specific context per module should also be possible. We might also have to keep in mind the underlying power selector hardware in a lot of these boards, but that's a detail we can get into later. |
Thank you very Much Dagar ! |
It would be useful for anyone two different battery or battery types onboard to monitor those batteries, current, etc. think or a main battery and a backup or payload battery of a differing cell count, etc.
Various Pixhawk hardware (Pixhawk 4, Cube, Pixhack v5) have multiple power ports but they, from what I gather are used for redundancy, not different monitoring solutions under px4.
We should be able to monitor power port 1 and power port 2 battery input and current and the corresponding battery_status message so qgc can display it but we will also need parameters to configure both power sources and eventually fail-safe logic tied to one or both.
According to this, #8578 (comment) from @dagar the codebase can already handle 4x power bricks but there are no parameters for them. We should expose them so qgc will report them so at a minimum that would work quite quickly.
As qgc is currently stands, it looks for BATTERY_STATUS.id=X if x is 0 it reports the first battery, if x is >0 it displays the second battery. This was done to coincide with how Ardupilot reports multiple batteries so essentially we just need to publish a battery status message with an id greater than 0 and parameters to set the amps per volt and voltage divider for the second port and in theory it should work. Failsafe and related can come later.
A qgc front end would be great but as we are seemingly missing something on the firmware side, that probably comes first.
The text was updated successfully, but these errors were encountered: