- v2.0 in PX4/Firmware (485c5db2): https://github.com/mavlink/c_library_v2/commit/6404047979cadac62fecd75070cd995f1ca66ca2
    - v2.0 current upstream: https://github.com/mavlink/c_library_v2/commit/fe2349dea9a88fb5b873eff2a59a88125943fd61
    - Changes: https://github.com/mavlink/c_library_v2/compare/6404047979cadac62fecd75070cd995f1ca66ca2...fe2349dea9a88fb5b873eff2a59a88125943fd61

    fe2349d 2018-08-11 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/141637e21e87a9c4ade90dbb9d544375294c106a
1d49e43 2018-08-09 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/f4fda461caaa0cb2c5dfed20d21a9d2a254b6c03

- ecl in PX4/Firmware (5d5841de980ca2d108d52f4652a9437507652860): https://github.com/PX4/ecl/commit/35f628e68febc54abee801797da5f92612d89116
    - ecl current upstream: https://github.com/PX4/ecl/commit/34cd1366b715d80885d71f80c72cc5d0bfde64f0
    - Changes: https://github.com/PX4/ecl/compare/35f628e68febc54abee801797da5f92612d89116...34cd1366b715d80885d71f80c72cc5d0bfde64f0

    34cd136 2018-08-12 Daniel Agar - Jenkins update PX4BuildBot credential usage

* jenkins: decrease VTOL mission alt and FW mission use simple land wps
* startup: decrease min airspeed scaling factor for landing
* jenkins: FW mission include loiter_to_alt cmd

This data is published at the GPS publication rate and only when on ground.

Enable drift checks and reduce thresholds to reduce likelihood of commencing  use of  a unstable GPS position.
Publish drift data to assist with tuning.

This data is only updated at 5Hz and only required pre-flight.

Navigator RTL: Removed the condition to transition straight to RTL_LAND if the previous setpoint was of type LAND. Not only does this not normally work, as the setpoints are cleared to invalid when navigator changes nav states, but the land lat/lon is set as home.lat and home.lot which is very wrong, as the vehicle would just beeline straight towards thatlocation. (#10252)

    - libuavcan in PX4/Firmware (9c9160e015aa68ee7efe456dae7de6fc9a819715): https://github.com/UAVCAN/libuavcan/commit/3ca697e64d52ba86c8e831d563c746827473e5e3
    - libuavcan current upstream: https://github.com/UAVCAN/libuavcan/commit/aa3650d34d9732af51ced52add24dee044eac79a
    - Changes: https://github.com/UAVCAN/libuavcan/compare/3ca697e64d52ba86c8e831d563c746827473e5e3...aa3650d34d9732af51ced52add24dee044eac79a

    aa3650d 2018-08-16 Pavel Kirienko - Merge pull request #156 from UAVCAN/master_kinetis_flexcan
0dc5751 2018-07-30 Pavel Kirienko - Merge pull request #155 from hjoertel/change-start-script
ff040ea 2018-07-30 Oertel - removed the confusing "echo ..." line (it confused Pavel)
8bb5677 2018-07-30 Oertel - replaced the depricated ifconfig command by the ip command

- remove unused distance sensor rotation
- add possibility to define SPI bus for other boards
- use SENS_FLOW_ROT param to rotate sensor

This provides a clean ROS interface for external projects which is
independent from the px4 CLI interface.

It can be used with:
```
	<include file="$(find px4)/launch/px4.launch">
	</include>
```

without this tasks will be switched all the time and the drone starts driftig

 - a unity build is a single compilation unit per module

   hardware detection was overwriting the CAN2 GPIO setting

The -P argument seems not to be supported on OSX

The Simple HW detection was detecting the
  Pixhack V3 as a mini.

  This commit adds further discrimination, based on
  the fact the Pixhack V3 left VDD_5V_PERIPH_EN
  floating. Where a mini ,V2, V3 HW has it connected
  to the active low enable of the VDD_5V_PERIPH and
  VDD_5V_HIGHPOWER via a 10K pull down.

  The detection enables the 40K pull up and samples
  the pin. This reads back as a logical one on the
  Pixhack V3, and a logical zero on the Mini.

  Since the float is applied some 3.3 Ms post pin setting
  at reset the 10 us should leave the 5 Volt supplies in
  the on state because of the 10K pull down.
  This is assuming typical 40K pullup 10K pull down
  This results in typical 0.66V (.875V max) on the /EN pin
  which should not be detected as a high on the TPS2041.

  On a FMU without a px4io (FMUv4, NXPhlite etc), this code should
  not be run.