mavros extras

Some extra plugins and nodes for [mavros][mr].

ADSB

Publish/subscribe to the location and information of an ADS-B vehicle.

cam_imu_sync

Publish camera trigger data for synchronisation of IMU and camera frames.

debug_value

Subs/Pubs debug msgs from and to the FCU.

distance_sensor

Publish DISTANCE_SENSOR message data from FCU or connected sensors in companion computer.

fake_gps

Sends fake GPS from local position estimation source data (motion capture, vision) to FCU.

gps_status

Publish GPS_RAW and GPS_RTK messages from FCU.

gps_rtk

Sends the RTCM messages to the FCU for the RTK Fix.

log_transfer

Expose firmware functionality, that is related to log transfer

mocap_pose_estimate

Send motion capture pose estimate to FCU. Currently, not used by the FCU. Data can be send via vision_position plugin.

obstacle_distance

Send obstacle distance report to the FCU.

odom

Send odometry to FCU from another estimator.

px4flow

Publish OPTICAL_FLOW_RAD data from FCU or PX4Flow module.

rangefinder

Publish RANGEFINDER message data from FCU sensors in companion computer.

trajectory

Receive planned path from the FCU and send back corrected path (collision free, smoothed) to the FCU.

wheel_odometry

Compute and publish wheel odometry coming from FCU sensors.

vibration

File truncated at 100 lines see the full file

Changelog for package mavros_extras

1.5.1 (2021-01-04)

• Initialise message structures Uninitialised Mavlink 2 extension fields were sent if the fields were not later set. Initialising the fields to zero is the default value for extension fields and appears to the receiver as though sender is unaware of Mavlink 2. Instances were found with regex below, more may exist: mavlink::[\^:]+::msg::[\^:={]+ ?[\^:={]*;
• Contributors: Rob Clarke

1.5.0 (2020-11-11)

• mavros_extras: Fix member initialization order
• mavros_extras: Add override specifiers
• mavros_extras: distance_sensor: Don't publish data when orientation configuration does not match incomming data.
• fake_gps: Fix assignment typo This colon should probably be an equals sign. With the colon, this assignment becomes a label instead, and [_gps_rate]{.title-ref} after the colon becomes an unused expression result.
• Contributors: Kristian Klausen, Morten Fyhn Amundsen

1.4.0 (2020-09-11)

• mavros: use mavlink::minimal:: after incompatible changes in mavlink package Incompatible change: https://github.com/mavlink/mavlink/pull/1463 Fix: #1483, https://github.com/mavlink/mavlink/issues/1474
• play_tune: Assign tune format directly
• play_tune: Uncrustify
• play_tune: Use msg_set_target and set_string_z
• play_tune: Write new plugin
• Contributors: Morten Fyhn Amundsen, Vladimir Ermakov

1.3.0 (2020-08-08)

• Take into account message count for message size
• Add esc_status plugin.
• fake_gps.cpp: Implement GPS time data
• fake_gps.cpp: implement speed accuracy
• fake_gps.cpp: Added horiz_accuracy and vert_accuracy parameters
• fake_gps.cpp: Add mocap_withcovariance configuration parameter
• fake_gps.cpp: add initial support for GPS_INPUT MAVLink message
• fake_gps.cpp: uncrustify
• Add gps_status plugin to publish GPS_RAW and GPS_RTK messages from FCU. The timestamps for the gps_status topics take into account the mavlink time and uses the convienence function
• uncrustify gps_rtk plugin
• adding support for publishing rtkbaseline msgs over ROS
• Contributors: CSCE439, Dr.-Ing. Amilcar do Carmo Lucas, Ricardo Marques

1.2.0 (2020-05-22)

• Revert "extras: odom: Hardcode BODY_FRD enum_value to fix compilation" This reverts commit 1a898dea2202ee1af56d698bd40d40994346c5cb.
• extras: odom: Hardcode BODY_FRD enum_value to fix compilation That PR broke build: https://github.com/mavlink/mavlink/pull/1112 TODO: find out what frame should be used
• Contributors: Vladimir Ermakov

1.1.0 (2020-04-04)

• Setting the same transparency for all elements
• Visualization of the direction of the device
• add support for bezier
• Contributors: Alamoris, Martina Rivizzigno

1.0.0 (2020-01-01)

• Change odometry subscription queue to 1 to avoid buffering.
• Contributors: James Goppert

0.33.4 (2019-12-12)

• obstacle_distance: Fill both increment and increment_f fields
• obstacle_distance: Fix wrong angle increment The computation [req->angle_increment * RAD_TO_DEG]{.title-ref} correctly computes angle increment in degrees as a float, but the [increment]{.title-ref} field of the OBSTACLE_DISTANCE MAVLink message is a uint8, so the float value gets truncated. So if your real increment is 10 degrees, you may a floating point value of something like 9.999999, which results in the integer value 9 getting written to the increment field. An improvement would be to round properly, with something like [static_cast<uint8_t>(increment_deg_float)]{.title-ref}, but a better solution is to allow non-integer degree values for the increment, which is supported by the [increment_f]{.title-ref} field. According to the MAVLink reference, increment_f is used instead of increment whenever increment_f is nonzero.
• Contributors: Morten Fyhn Amundsen

0.33.3 (2019-11-13)

• package: fix 6fa58e59 - main package depends on trajectory_msgs, not extras

File truncated at 100 lines see the full file