dark0707
/
px4-firmware
forked from Archive/PX4-Autopilot
1
0
Fork 0
Code Pull Requests Activity
px4-firmware/msg/battery_status.msg

34 lines
2.0 KiB
Plaintext
Raw Normal View History

add timestamp field to uORB msgs; sync timestamp whenever possible
2018-08-06 21:30:05 -03:00
uint64 timestamp # time since system start (microseconds)
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
Updated batt_smbus. Expanded battery_status.msg. Fixed mavlink_messages.cpp temperature. (#8991) * Updated and expanded batt_smbus to work with bq40z50-R2. Expanded battery_status.msg. Fixed mavlink_messages.cpp temperature, added commented out expanded battery_status.msg parameters for future mavlink expansion. * Changed errx to PX4_ERR * Added PX4_ERR returns
2018-03-06 05:42:20 -04:00
float32 average_current_a # Battery current average in amperes, -1 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
Mavlink: fixed temperature for batteries (#12605)
2019-08-02 11:09:03 -03:00
float32 temperature # temperature of the battery. NaN 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
Added Power Brick related battery_status.msg fields system_source - This battery status is for the brick that is supplying VDD_5V_IN priority - Zero based, This battery status is for the brick that is connected to the Power controller's N-1 priority input. V1..VN. 0 would normally be Brick1, 1 for Brick2 etc Battery now assigns connected from the api in the updateBatteryStatus, as well as system_source and priority
2017-06-29 17:45:52 -03:00
bool connected # Whether or not a battery is connected, based on a voltage threshold
bool system_source # Whether or not a this battery is the active power source for VDD_5V_IN
uint8 priority # Zerro based priority is the connection on the Power Controller V1..Vn AKA BrickN-1
Updated batt_smbus. Expanded battery_status.msg. Fixed mavlink_messages.cpp temperature. (#8991) * Updated and expanded batt_smbus to work with bq40z50-R2. Expanded battery_status.msg. Fixed mavlink_messages.cpp temperature, added commented out expanded battery_status.msg parameters for future mavlink expansion. * Changed errx to PX4_ERR * Added PX4_ERR returns
2018-03-06 05:42:20 -04:00
uint16 capacity # actual capacity of the battery
uint16 cycle_count # number of discharge cycles the battery has experienced
uint16 run_time_to_empty # predicted remaining battery capacity based on the present rate of discharge in min
uint16 average_time_to_empty # predicted remaining battery capacity based on the average rate of discharge in min
uint16 serial_number # serial number of the battery pack
batt_smbus rework
2018-10-15 13:00:27 -03:00
float32[4] voltage_cell_v # Battery individual cell voltages
float32 max_cell_voltage_delta # Max difference between individual cell voltages
Added Power Brick related battery_status.msg fields system_source - This battery status is for the brick that is supplying VDD_5V_IN priority - Zero based, This battery status is for the brick that is connected to the Power controller's N-1 priority input. V1..VN. 0 would normally be Brick1, 1 for Brick2 etc Battery now assigns connected from the api in the updateBatteryStatus, as well as system_source and priority
2017-06-29 17:45:52 -03:00
batt_smbus readd to configurations and fix compilation errors
2018-02-07 21:57:08 -04:00
bool is_powering_off # Power off event imminent indication, false 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
uint8 BATTERY_WARNING_NONE = 0 # no battery low voltage warning active
uint8 BATTERY_WARNING_LOW = 1 # warning of low voltage
Battery: Implement an emergency warn level
2017-02-22 17:01:21 -04:00
uint8 BATTERY_WARNING_CRITICAL = 2 # critical voltage, return / abort immediately
uint8 BATTERY_WARNING_EMERGENCY = 3 # immediate landing required
uint8 BATTERY_WARNING_FAILED = 4 # the battery has failed completely
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
uint8 warning # current battery warning