ArduPilot / ArduPilot/MissionPlanner
Battery Sensing - Voltage and Current Calculations
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 2.9k
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 4
Description
Hi
I am trying to gather some data on the capacity drawn from the batteries I have been using on my quad.
The situation I am in is that the manufacture of my quad didn't do a good job of calibrating the Voltage and Current sensing on my platform. This means up until now the estimations of battery voltage and current draw produced by my quad and mission planner are incorrect.
I have now however gone through the process myself of calibrating the voltage and current readings and the estimated current draw seems to match up pretty well to the capacity I put back into the batteries when charging.
But I have all of the data from previous flights, well over 10 hours flying time, that I want to use to produce a complete knowledge of how much current I am using per flight and get an idea of how many milli-amps I use per KM flown.
Because I have the values for the old and new multiples for the voltage and current, I think I should be able to convert the data I have from when the multiplier values where wrong into a better estimate of the milli-amps consumed using the new multiplier values.
The issue I have with this is after a little searching online I cannot seem to find the Maths behind calculating the Voltage value and therefore the Current value that are logged. If I could get this I think i could work backwards and apply the new multipliers to the raw voltage and current sensor readings and complete to give me a better estimate of milli-amps used.
My question is, does anyone know the calculations, or the source file which contains said calculation are found?
Any help would be greatly appropriated
Regards
Chris
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file, test, or entry point is named in the issue. Begin by locating where Mission Planner derives and logs battery voltage and current from sensor readings; the issue would be complete only when the relevant formulas and the limits of applying recalibration to historical logs are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100