LogAnalyzer - add binary log parsing
 - parse using ctypes.LittleEndianStructure
 - define classes from FMT messages
 - use the classes as with Text logs for processing
LogAnalyzer - adjust modeChanges for Plane/Rover
 - I lack logs for both, not tested.
LogAnalyzer - label/name & format/type consistency
LogAnalyzer - accept invalid FMT messages in binary logs
 - I really wish this was not necessary, but it is.
VibTest: fixed sample count output on console
LogAnalyzer: TestPitchRollCoupling add mode ""

 - "" is a valid alias for AUTOTUNE
LogAnalyzer: add TestAutotune

 - very basic, checks for autotune start/success/fail and provides the
   most recent ATUN/ATDE values
 - very handy in case autotune fails
AP_Baro: save some flash and memory on APM2

we don't need the I2C MS5611 driver
Copter: remove log CLI code when CLI disabled
AP_RangeFinder_PulsedLightLRF: Updated the register definitions for the new hardware
mk PX4: Added the new ll40ls device to modules list and start commands
AP_RangeFinder: Added a new PX4 range finder and modified the RangeFinder parent class to support having multiple devices simultaneously
AP_RangeFinder_PX4_test: Added an example sketch for the PX4 range finder
AP_RangeFinder_PulsedLightLRF: Updated the value to write to the register to trigger a measurement
AP_RangeFinder: Changes from the May 4th plane test flight
PX4 ROMFS INIT: Added starting the optional mb12xx sensor
AP_RangeFinder: Seperated the Backend driver functionality into a separate class
AP_RangeFinder: disable old rangefinder drivers 

these will be re-enabled when they are converted to the new class API
AP_RangeFinder: new rangefinder API ready for its first backend

the backends are setup to have just the minimum functionality needed
for a rangefinder, with all of the higher level logic in the
frontend. This should make writing a new backend easier
AP_RangeFinder: converted analog rangefinder backend to new API

this gets analog rangefinders of all types working