c92b8b03cd
Move variable initialization from constructor to declarations in MavlinkReceiver class, alphabetize var lists. Added update_params() method to ensure that parameters subscribed to are updated routinely.
2019-06-17 09:41:30 +02:00
7c4bf6ddae
Mavlink ODOMETRY (331) support MAV_FRAME_BODY_FLU
2019-06-16 13:23:57 -04:00
d7d0bd2764
Mavlink: Enable gimbal control using SET_ACTUATOR_CONTROL_TARGET while controlling the vehicle offboard ( #12146 )
...
* Stop ignoring setpoints when actuator setpoints are for the gimbal
2019-06-15 21:35:41 -04:00
a707403eaf
mc_att_ctrl: added yawrate control from offboard.
...
This commit adds Roll Pitch Yawrate Thrust (RPYrT) setpoint control to the
PX4 stack, enabling the UAV to follow specific yawrates sent from
offboard. It also introduces individual body_rate flags, along the
lines of mavros.
Tested on a MoCap enabled flight arena in KTH Royal Institute of
Technology, Stockholm. The MAV receives RPYrT setpoints from an
external PID controller to stabilize around position setpoints.
The UAV is also externally disturbed to assess the stability to
external unmodeled events.
Fixed Kabir comments.
Removed deprecated ignore_bodyrate.
Fixed integration test.
2019-06-04 08:26:09 +02:00
ac002db25c
MAVLink/Commander: @Pedro-Roque's offboard yawrate handling
2019-06-04 08:26:09 +02:00
579cbbb42c
mavlink move to new lightweight uORB::Subscription
2019-06-03 17:06:21 -04:00
f9324fb76a
mavlink: set correct distance_sensor timestamp. Fixes #11840
...
When PX4FLOW is connected to PX4 through MAVLink (e.g., through a USB
port), the timestamp assigned to the distance_sensor was wrong. This fix
uses the same timestamp assigned to the optical_flow message created from
the same OPTICAL_FLOW_RAD MAVLink message.
Signed-off-by: Gabriel Moreno <gabrielm@cs.cmu.edu >
2019-04-15 20:31:15 +02:00
9540869c20
Alphabetize a few methods and variable orders in mavlink_receiver.h.
2019-04-11 08:31:30 +02:00
319723a1ec
mavlink_receiver: ignore BATTERY_STATUS of other system
2019-03-23 15:18:46 -04:00
fb990d7de3
Removed subscribtion to multiple _telemetry_status instances.
...
Since commander handles all telemetry_status the same there is no need to subscribe to multiple instances.
Signed-off-by: Claudio Micheli <claudio@auterion.com >
2019-03-12 11:24:33 +01:00
b85cceebe9
mavlink_receiver: Ignore heartbeats coming from other vehicles.
...
Signed-off-by: Claudio Micheli <claudio@auterion.com >
2019-03-12 11:24:33 +01:00
a98f5d2ab2
suggestion for treating obstacle avoidance heartbeats
2019-03-12 11:24:33 +01:00
6dec451bab
HEARTBEAT and commander failsafe handling cleanup
2019-03-12 11:24:33 +01:00
2773fe6a54
Deprecate _hil_frames and _old_timestamp member vars and dead logic from MavlinkReceiver class.
2019-03-11 08:03:37 +01:00
d42bb01e0c
Standardize method definition newlines in mavlink_receiver.cpp.
2019-03-02 13:09:41 -05:00
e2bf4b1894
List container improvements and testing
...
- support range based for loops
- add remove() method to remove a node
- add clear() to empty entire list and delete nodes
- add empty() helper
2019-03-01 21:01:04 -05:00
c04147c53c
Mavlink receiver: Move most variable initializations out of the constructor to the variable declarations
2019-02-26 11:48:02 -05:00
9355324209
mavlink/MavlinkReceiver: Use hrt_absolute_time for distance_sensor timestamps
2019-02-25 12:07:53 +01:00
fbc8d01a7e
Rename distance_sensor.covariance to variance
2019-02-22 18:31:27 +00:00
ec3f1fd5c2
mavlink_receiver: fix DISTANCE_SENSOR covariance handling
2019-02-22 18:31:27 +00:00
6762f09490
Move variable initializations to header file that were no longer in the correct order in the constructor list.
2019-02-21 09:22:01 -05:00
8a6a5cc310
Deprecate #defines that are not needed, format whitespace and minor (incomplete) alphebetization of a few lists.
2019-02-21 09:22:01 -05:00
7c3999e00e
update mavlink and sitl_gazebo to latest with odometry velocity covariance
2019-02-10 16:32:59 -05:00
dc5f18bdcd
ToneAlarm class refactoring to implement an interface for hardware specific methods and a single ToneAlarm class.
2019-01-28 18:58:04 -08:00
504372f551
MAVLink: RC_CHANNELS_OVERRIDE generate correct RC channel count ( #11219 )
...
* mavlink_receiver: generate rc channel count
* mavlink_receiver: zero out ignored rc channels, add comments
2019-01-25 12:15:01 -05:00
5b9dea5604
Replacing usleep with px4_usleep
...
This is a step towards isolating time from the system.
2018-12-22 10:32:18 +01:00
90bfdb6f0a
VTOL rate control architecture improvements ( #10819 )
...
* attitude and rate setpoint message: use 3D array for thrust demand
* FixedWingAttitudeControl: rework airspeed scaling
* move airspeed and scaling calculation into separate method
* if vtol in hover and airspeed disabled use minimum airspeed instead of trim airspeed
2018-11-21 20:32:40 -05:00
571364c617
delete baro_report (alias for sensor_baro_s)
2018-11-06 07:43:43 +08:00
acc24da0c2
delete gyro_report (alias for sensor_gyro_s)
2018-11-06 07:43:43 +08:00
2a83a40491
delete accel_report (alias for sensor_accel_s)
2018-11-06 07:43:43 +08:00
6a3692cf6b
mavlink: publish GPS antenna heading offset as NAN
2018-10-17 09:48:38 -04:00
3228e494bd
radio_status: change 'fixed' field name to 'fix' so it does not clash with 'fixed' floating-point notation on the IDL generation
2018-10-08 10:58:45 +02:00
403f909e3a
mavlink_receiver: simplify sleeptime calculation
2018-10-02 14:14:10 +02:00
0e1e0b997d
mavlink_receiver: reduce s_variance_m_s for HIL GPS message from 1 to 0.1
...
1 was too high to pass the EKF2 test (EKF2_REQ_SACC which is 0.5 by default)
and thus switching into position mode in HIL was not possible.
2018-09-29 09:17:53 -04:00
cb3d86a609
Add support for mavlink message DEBUG_FLOAT_ARRAY
2018-09-27 12:33:12 -04:00
2c7c876c38
mavlink_receiver: parse all 18 channels from rc_override
2018-09-21 16:26:27 +02:00
4f0e090e88
drv_rc_input: replace useless rc_input_values define
2018-09-21 16:26:27 +02:00
f14125c160
Mavlink NuttX network support ( #10200 )
2018-09-18 23:29:58 -04:00
9887c463fd
mavlink_receiver: fill some missing fields in OPTICAL_FLOW_RAD handler
2018-09-18 09:53:35 +02:00
095cdeb4b0
add a local frame of reference field to vehicle_odometry
2018-09-18 09:52:33 +02:00
1cfaccfd7b
mavlink_receiver: use typedef dcmf for DCM matrices
2018-09-18 09:52:33 +02:00
746250d86d
use static_assert over covariance matrices URT array size
2018-09-18 09:52:33 +02:00
7db57bedb7
assert over the covariance matrices URT size matching
2018-09-18 09:52:33 +02:00
2f5b16a5d3
mavlink_receiver: odometry handler: simplify quaternion init
2018-09-18 09:52:33 +02:00
7303005373
mavlink_receiver: add ODOMETRY handler; use new visual_odometry uORB msg and aliases
2018-09-18 09:52:33 +02:00
4816adcdee
mavlink_receiver: remove attitude_quatertion_cov and local_position_ned_cov handlers
2018-09-18 09:52:33 +02:00
7691990a50
Pass through horizontal and vertial covariances
2018-09-16 21:30:20 -04:00
930ac8d4fe
Mavlink set telemetry_status type properly for Sik radios
...
- remove radio_status type since there's no type support in mavlink
2018-09-02 19:48:10 +02:00
b6b935026a
mavlink: switch back from _mavlink_timesync.sync_stamp to hrt_absolute_time
...
- the timestamp is only used for logging and log analysis. For that it's
important to have the timestamp when a setpoint becomes active.
- there was a consistent problem with the position_setpoint_triplet
timestamp, where the timestamp was just bogus. Timesync seems to work
correctly though. Might be a problem on the sender side?
For example here:
https://logs.px4.io/plot_app?log=41918a7d-4c1d-464d-9abe-aef2c0818d92
2018-08-22 08:31:37 +02:00
36403e9025
Mavlink expand telemetry_status and split radio_status
2018-08-16 17:32:15 +02:00
mcsauder