The initial idea of the flight task architecture was that
a task can freely set it's setpoints and doesn't have to
worry about takeoff and landing. It would just takeoff
when it's landed and there's a setpoint to go up and
land when it puts a setpoint that pushes into the ground.
With the takeoff logic there are some significant interface
problems depending on the way a task is implemented:
From the setpoint is not high enough to trigger to
an unexpected takeoff because of some estimator
fluctuation affecting the setpoint. It's easiest to solve this
by allowing the task to determine when a takeoff is triggered.
If no condition is implemented by default a task is not
allowing a takeoff  and cannot be used to get the vehicle
off the ground.

microRTPS_transport: use preprocessor declarations to setup different build contexts for client and agent code

RTPS IDL: fix const names; make IDL template similar to rosidl_generator_dds_idl/resource/msg.idl.em

simulator in hardware, new module added that allows to run a simulator in the hardware autopilot, for more documentation visit https://github.com/romain-chiap/PX4_SIH_QuadX

Signed-off-by: Roman <bapstroman@gmail.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

This allows to perform pre-arm checks and prevent arming if obstacle avoidance is enabled but not yet running.
Added a print once flag to prevent excessive message spamming in QGC.

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Roman <bapstroman@gmail.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Signed-off-by: Claudio Micheli <claudio@auterion.com>

Rename tune_control_s strength to volume to match Nuttx and Linux standard nomenclature for audio (loudness) control.

The previous code used the numeric baudrate as the speed argument
for cfsetispeed() and cfsetospeed(). This works in OSX and NuttX,
but is not portable.

This fix introduces a new method to convert baudrate to speed using
constants such as B115200.

Signed-off-by: Gabriel Moreno <gabrielm@cs.cmu.edu>

camera trigger and camera capture publish on two different topics and camera feedback module uses CAM_CAP_FBACK param to choose between the two.

camera_trigger.msg: add feedback field to understand if message camera from trigger or capture driver

    - gencpp in PX4/Firmware (ed8517a7d97f15cdf556cdc64496cc72bebb99ab): https://github.com/ros/gencpp/commit/b41ee3060badd660662e21cd9d4f81971c87a420
    - gencpp current upstream: https://github.com/ros/gencpp/commit/7e446a9976916a7b6fc7266098c67fc6f73a76e0
    - Changes: https://github.com/ros/gencpp/compare/b41ee3060badd660662e21cd9d4f81971c87a420...7e446a9976916a7b6fc7266098c67fc6f73a76e0

    7e446a9 2019-01-25 James Xu - enable Windows build (#38)

    - genmsg in PX4/Firmware (d4338773aa0139295caff03dc8275b44b88ccd04): https://github.com/ros/genmsg/commit/42e364661025b8f3d51486dc513d9e29cbd308da
    - genmsg current upstream: https://github.com/ros/genmsg/commit/5736b1f7ad037fb5811a3100ba9da2db0ec1f20a
    - Changes: https://github.com/ros/genmsg/compare/42e364661025b8f3d51486dc513d9e29cbd308da...5736b1f7ad037fb5811a3100ba9da2db0ec1f20a

    5736b1f 2019-01-28 Dirk Thomas - add missing run_depend on empy (#81)

Signed-off-by: CarlOlsson <carlolsson.co@gmail.com>

uorb_to_ros_msgs: delete all messages on the out dir first, so it can also consider message deletions on the input dir