px4-firmware/msg/battery_status.msg

float32 voltage_v		# Battery voltage in volts, 0 if unknown
float32 voltage_filtered_v	# Battery voltage in volts, filtered, 0 if unknown
float32 current_a		# Battery current in amperes, -1 if unknown
float32 current_filtered_a	# Battery current in amperes, filtered, 0 if unknown
float32 discharged_mah		# Discharged amount in mAh, -1 if unknown
float32 remaining		# From 1 to 0, -1 if unknown
float32 scale		# Power scaling factor, >= 1, or -1 if unknown
int32 cell_count		# Number of cells
bool connected			# Wether or not a battery is connected
#bool is_powering_off		# Power off event imminent indication, false if unknown


uint8 BATTERY_WARNING_NONE = 0       # no battery low voltage warning active
uint8 BATTERY_WARNING_LOW = 1        # warning of low voltage
uint8 BATTERY_WARNING_CRITICAL = 2   # alerting of critical voltage

uint8 warning    # current battery warning
Move battery status to generated topics 2015-05-25 14:23:43 -03:00			`float32 voltage_v # Battery voltage in volts, 0 if unknown`
			`float32 voltage_filtered_v # Battery voltage in volts, filtered, 0 if unknown`
			`float32 current_a # Battery current in amperes, -1 if unknown`
Inline comment addition 2016-05-10 05:17:48 -03:00			`float32 current_filtered_a # Battery current in amperes, filtered, 0 if unknown`
Move battery status to generated topics 2015-05-25 14:23:43 -03:00			`float32 discharged_mah # Discharged amount in mAh, -1 if unknown`
commander: move battery calculations to systemlib The commander used to consume the battery_status topic and write the contents after some calculations into the system state. Instead, the calculations now happen in library calls in systemlib/battery. This moves the battery fields out of the vehicle_status message into the battery_status topic. This brought quite some changes in all modules that need battery information. The current state is compiling but untested. 2016-02-24 14:08:56 -04:00			`float32 remaining # From 1 to 0, -1 if unknown`
Explicit internal battery resistance params 2016-10-10 21:31:14 -03:00			`float32 scale # Power scaling factor, >= 1, or -1 if unknown`
commander: move battery calculations to systemlib The commander used to consume the battery_status topic and write the contents after some calculations into the system state. Instead, the calculations now happen in library calls in systemlib/battery. This moves the battery fields out of the vehicle_status message into the battery_status topic. This brought quite some changes in all modules that need battery information. The current state is compiling but untested. 2016-02-24 14:08:56 -04:00			`int32 cell_count # Number of cells`
Battery status: Add valid flag 2016-05-15 10:37:46 -03:00			`bool connected # Wether or not a battery is connected`
commander: move battery calculations to systemlib The commander used to consume the battery_status topic and write the contents after some calculations into the system state. Instead, the calculations now happen in library calls in systemlib/battery. This moves the battery fields out of the vehicle_status message into the battery_status topic. This brought quite some changes in all modules that need battery information. The current state is compiling but untested. 2016-02-24 14:08:56 -04:00			`#bool is_powering_off # Power off event imminent indication, false if unknown`


			`uint8 BATTERY_WARNING_NONE = 0 # no battery low voltage warning active`
			`uint8 BATTERY_WARNING_LOW = 1 # warning of low voltage`
			`uint8 BATTERY_WARNING_CRITICAL = 2 # alerting of critical voltage`

			`uint8 warning # current battery warning`