342509b3ab
New ROI commands implementation
2018-01-25 15:27:55 +01:00
ae52f74e78
landing target estimator: initialize landing target velocity with negative of vehicle velocity
2018-01-24 19:39:30 +01:00
b7dff95782
landing target estimator: check validity of the correct data before computing acceleration
2018-01-24 19:39:30 +01:00
c0615c9e70
logger add safety
2018-01-24 17:36:53 +01:00
2ae5e575a5
land detector initialize landed and publish periodically
2018-01-24 17:36:53 +01:00
fd3f59d8c4
commander publish periodic status messages at 1 Hz
2018-01-24 17:36:53 +01:00
edf178d4e8
commander safety update require successful orb_copy
2018-01-24 17:36:53 +01:00
d8164377a8
Navigator: Move mission param into mission params
...
This is important for the compile scope.
2018-01-22 15:56:42 +01:00
7ae3884944
heading towards ROI: do not require setting the MIS_YAWMODE param to enable multicopters yawing towards ROIs
...
ROI yaw control: configure yawing capability of mount in vmount parameters.
If configured that mount has no yaw control, vehicle will yaw towards ROI, irrespective of MIS_YAWMODE.
Vehicle will behave according to MIS_YAWMODE when there is no ROI.
2018-01-22 15:56:42 +01:00
add3692357
ROI: accept ROIs of type None in missions to enable 'deactivating' another ROI
2018-01-22 15:56:42 +01:00
bedaafcc20
NAV_CMD_DO_SET_ROI: handle relative altitude in mission ROI commands
2018-01-22 15:56:42 +01:00
38c949731f
mavlink_main: fix broadcast computation
...
The way the broadcast IP is currently fetched is by sending an ioctl()
request. The limitation of this is that the broadcast address may not
be set on the network interface (more specifically, it is usually not
set in docker containers). In those cases, it results in the broadcast
address becoming 0.0.0.0, which is not valid [1].
This fix uses the network IP and the netmask to compute the directed
broadcast address. This should be more reliable, as both of those are
always set on the network interface.
[1]: https://tools.ietf.org/html/rfc1122 , section 3.2.1.3 (a)
2018-01-21 14:58:04 +01:00
45458fe9eb
uORBManager: add comment about not having to set the priority
2018-01-19 14:11:01 +01:00
2cb698f01f
uORBDevices: set the priority when advertising a node that's already subscribed
...
This fixes the case where a topic instance is already subscribed, and
advertised later. The subscriber will create the DeviceNode with default
priority, and the advertiser will just use the existing DeviceNode,
without updating to the requested priority.
2018-01-19 14:11:01 +01:00
bda929bebb
commander fix hil_state regression again
2018-01-18 17:38:48 +01:00
821eb5ac87
navigator: precland_params: PLD_MAX_SRCH: fix min value from float to int
2018-01-17 17:52:24 -05:00
ae65289967
lpe: params: fix LPE_FUSION max value
2018-01-17 17:52:24 -05:00
f672152d2d
logger: change 'removing log directory' warning to info
2018-01-17 02:19:01 -05:00
3a52e7ee5d
simulator mavlink: set vision pos/val valid
2018-01-15 11:11:56 +01:00
66c67f89e6
ekf2: check if vision_position pos/vel are valid before using them
2018-01-15 11:11:56 +01:00
6609e4843b
mavlink receiver: set vision_position pos/vel invalid depending on covariance
2018-01-15 11:11:56 +01:00
c7cf442e16
ekf2: use ev eph/v for noise parameter if bigger than noise param
2018-01-15 11:11:56 +01:00
45fd908784
mavlink : add support for precision landing
2018-01-15 10:27:23 +01:00
90e3aeda6c
logger : add support for logging precision landing messages
2018-01-15 10:27:23 +01:00
f2dbb0ad3b
commander : add support for precision landing measurements
2018-01-15 10:27:23 +01:00
d9b9b4407a
ekf2 : add support for precision landing measurement fusion
2018-01-15 10:27:23 +01:00
dd1d0adfef
LPE : add support for precision landing measurement fusion
2018-01-15 10:27:23 +01:00
f600cfbb9f
Add support for testing precision landing in SITL simulation
2018-01-15 10:27:23 +01:00
d9221bb8d2
mc_pos_control : add support for precision landing
2018-01-15 10:27:23 +01:00
aa4c6c038d
navigator : add support for precision landing
2018-01-15 10:27:23 +01:00
652d295b2d
Add landing_target_estimator for precision landing from @ndepal
2018-01-15 10:27:23 +01:00
ec1c37e1af
modules: lpe: push sensor status update to object; prioritize lidar readings over sonar
2018-01-14 22:52:41 +01:00
b512759336
modules: lpe: refactor fusion bitmask
2018-01-14 22:52:41 +01:00
8b3ea27bb3
correct coding style
2018-01-14 12:55:47 +01:00
eec1ead233
update description of LPE_FUSION
2018-01-14 12:55:47 +01:00
28a5287a91
add FUSE_MOCAP, FUSE_LIDAR, and FUSE_SONAR to select more senors
2018-01-14 12:55:47 +01:00
b524c8a20f
navigator silence geofence update PX4_INFO
2018-01-14 12:53:53 +01:00
6e0f3ffa88
commander move mission init out of main loop
2018-01-14 12:53:53 +01:00
fe6006e22f
commander move mission_result to class
2018-01-14 12:53:53 +01:00
f49c061a3c
navigator fix mission_result increment and sign mismatch
2018-01-14 12:53:53 +01:00
b1a3475ebf
commander mission valid check require updated mission_result
2018-01-14 12:53:53 +01:00
916d6a15fd
Mission merge offboard + onboard and simplify
2018-01-14 12:53:53 +01:00
956935141e
Navigator simplify mission
2018-01-14 12:53:53 +01:00
25c7a03a8b
Navigator remove unnecessary calls to updateParams
...
- the SuperBlock already does this
2018-01-14 12:53:53 +01:00
6227139df1
MAVLink app: Make debug messages a compile time check
...
The debug messages are too verbose to be run in a production vehicle and inherently were something that should only be run in SITL / debug sessions on hardware. Switching the flag to the PX4_DEBUG() macro does not only make this more explicit, but also saves a lot of flash space that otherwise was consumed by the strings.
2018-01-13 22:02:57 -05:00
931482941c
mc_pos_control: use global _dt member from the control block architecture
2018-01-13 13:08:47 +01:00
a25ca0c37d
param include px4_config.h for FLASH_BASED_PARAMS
...
- fixes #8585
2018-01-12 23:46:15 +01:00
7b1b255158
EKF2 set zero unused estimator_status fields
2018-01-12 23:19:46 +01:00
f47d0c8f8c
load_mon: reduce FDS_LOW_WARNING_THRESHOLD to 3
...
This bound can be quite tight, because:
- The system still behaves well, even if all FD's are used (as opposed to
a stack overflow)
- The amount of used FD's is typically only increased one at a time
(e.g. adding new logged topics, adding a mavlink stream, ...)
- reducing CONFIG_NFILE_DESCRIPTORS to the minimum frees up a considerable
amount of RAM on systems that need it
2018-01-12 23:18:59 +01:00
794c7a5a0f
load_mon: fix tasks index & fds_free initialization
...
Makes sure that if CONFIG_NFILE_DESCRIPTORS == 0, no warning is printed.
2018-01-12 23:18:59 +01:00
DonLakeFlyer