ArduPilot/ardupilot

AP_DDS: Support IMU+gyro+accel data for rate control or offboard fusion

Offen

#23.478 geöffnet am 14.04.2023

 (12 Kommentare) (0 Reaktionen) (1 zugewiesene Person)C++ (15.603 Forks)batch import
EKFROSgood first issue

Repository-Metriken

Stars
 (9.336 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 26T 16h) (166 gemergte PRs in 30 T)

Beschreibung

From AP_AHRS, the data is filtered and good for rate control. This is the data after notch+low pass, phase lag and all. This goes on imu_filtered topic.

For offboard fusion, we can do it "badly". We would need delta angle, delta velocity, all the data products from INS that are not filtered. We have to know the lag to do delayed time fusion with lag on the GPS. This would be on imu_raw.

Current EKF does delayed time fusion (in delayed time) with forward propagation to the current time. Doesn't work as well in dynamic flight. Researchers want to do this.

Adding things like vision odometry back into ArduPilot (visual mavlink odometry) - this is preferred for performance so ArduPilot's EKF can fuse the data.

Contributor Guide