this adds a (commented by default) rectangle which uses the tool insets
from the widget layer to dynamically size itself. This is an example of
how to use tool insets to position something on the custom-layer
Previously the FlyViewMap only checked center tool insets to determine
whether to recenter the vehicle. This change makes it also check if the
vehicle has passed under a corner element using the corner tool insets.
This means the view will recenter if the vehicle flys under the
instrument panel for example.
ArduPilot's onboard calibration is superior to this old-style "offboard compass calibration", and we've just merged a patch which removes the mavlink API call to set the sensor offsets into the ArduPilot master branch.
Changed from QHashIterator to using a constant iterator for iterating through the map providers in _providersTable. This change prevents application crashes during a map download session caused by the potential modification of an implicitly shared hash.
Fetching failed because the remote changed in a submodule:
fatal: remote error: upload-pack: not our ref 391786c6c3abdd3eeb993a3154f1f2a4cfe137a0
Errors during submodule fetch:
libs/cpp/parse/nlohmann_json
As the arming flag is set from the heartbeat received at 1Hz, we need to
wait a bit longer than 1s.
The 1s timeout sometimes led to this error message when trying to start a
mission: "Unable to start mission: Vehicle rejected arming."
Fixes https://github.com/PX4/PX4-Autopilot/issues/22042
This adds two video settings:
1. QGC running on Herelink connecting to the AirUnit.
2. QGC running on any device connected to Herelink's hotspot.
By default (without custom build) only 2. is enabled.
Signed-off-by: Julian Oes <julian@oes.ch>
Both PX4 and APM supports circular geofences around the home point.
QGC with PX4 displays this by checking GF_MAX_HOR_DIST.
This commit adds equivalent functionality for APM.
Params used on APM are FENCE_ENABLE,FENCE_TYPE,FENCE_RADIUS.
Tested with ArduCopter 4.3, ArduPlane master, and PX4 1.13.