- Catch the case where the case where the driver gets stuck because nothing is received by +SBDRB
- Add a mutex for the rx buffer
- Stop the standby loop if a mode change is already scheduled
- Move publishing the telemetry status from the IridiumSBD driver to the mavlink instance
- In the commander use the iridiumsbd_status message for heartbeat in case of a high latency link
- Move positive acknowledge to the mavlink instance
- Add a failed acknowledge in the commander if no high latency link exists
* Add return to land to mission
This method uses the planned mission for rtl. If a landing sequence
is present it will continue the mission and land. If not it will
fly back the mission and loiter/land at the home position.
These hard coded paths assume all Nuttx targets are ARMv7-M targets. Updating them to use ${CONFIG_ARCH} and ${CONFIG_ARCH_FAMILY} instead allows for the architecture defined by the incoming Nuttx defconfig to be correctly targeted.
- just use external mag, if they run together the sensor_mag_0 topic gets
corrupted even though they publish on different instances
- added sleep at two places, they resolve weird boot problems like params
not being read correctly...
Signed-off-by: Roman <bapstroman@gmail.com>
- ecl in PX4/Firmware (9e6449570a58587b7dd0f4919ea9d6f0a52f5239): cb63f16d48
- ecl current upstream: 50631e5d98
- Changes: cb63f16d48...50631e5d9850631e5 2018-05-21 Daniel Agar - geo remove use of DBL_EPSILON
- DriverFramework in PX4/Firmware (381d3ccd577484a57e555ec9ad6166249d590140): e06222dd15
- DriverFramework current upstream: 410e9fc4e7
- Changes: e06222dd15...410e9fc4e7
410e9fc 2018-05-18 Roman - mpu9250: set internal gyro dlpf frequency to 92 Hz
Beat Küng
acfloria
Hamish Willee
Daniel Agar
Lorenz Meier
mcsauder
Anthony Lamping
Sander Smeets
mcsauder
Joshua Whitehead
DanielePettenuzzo
Roman
PX4 Jenkins
barzanisar