Update common.xml

Proposal to add direct battery charge and energy consumption reporting in addition or instead of the current percentage of battery.  

The problem with the battery percentage is that the on-board system in most cases does not natively know the size of the energy storage and relies on the (possibly) configured battery capacity value.  In case of changing the battery on the field there may be different battery size or there may be a different type of power source on board. In any case, the percentage value is secondary information and dependent on a pre-configured capacity value, which may or may not be correct or relevant.  

If the on-board system has capability to report any consumption numbers, it almost certainly is measuring current and voltage samples.  These are primary information available to be reported and should be reported.

Possibly it could make sense to split message 147 to two separate messages: 1) multi-cell battery individual cell voltage reporting 2) total voltage & current readings and derivatives.
1. Fixed field closing tag.  2. Increased current and energy consumption field sizes.

Field size increase to accommodate kilowatt-size power trains and long missions. A more airlink economical option would be to use one scalar byte for both of the consumption fields.  However, not sure if the savings would carry their weight in added complexity.
Added M_PI_2 to mavlink_conversions.h if not defined.
pymavlink: added mavsearch.py tool
Update common.xml

Added two autopilot types
Update common.xml

Corrected the error
Added fix for python generator for float arrays.
Merge pull request #140 from mavlink/float-length-py-fix

Added fix for python generator for float arrays.
Merge pull request #137 from dagoodma/math_fix

Added M_PI_2 to mavlink_conversions.h if not defined.
Merge pull request #116 from MikkoSaarisalo/patch-1

Improve battery consumption reporting
Merge pull request #139 from ARMAZILA/patch-1

Patch 1
Fix generator name
Added RC receiver status, based on a request from Randy and Kevin
Clarified documentation
ardupilotmega: added RALLY_POINT and RALLY_FETCH point msg defs.

Rally points will be used to allow the plan to RTL to locations
other than the Home location.
mavwp: Added a rally point loader.

This will be used in MAVProxy to allow loading rally points.
ardupilotmega: added FENCE_ACTION_GUIDED_THR_PASS

this is for guided mode with throttle pass-thru
pymavlink: raise version for release
ardupilotmega: added MAV_CMD_DO_SET_CAM_TRIGG_DIST
Correcting description of VDOP in common defs