Fix typo in wind_x field description (line 384): 'North,Est, Down' -> 'North, East, Down'. This also matches the format used in the adjacent wind_y field on line 385. No protocol or code changes - description text only.
* common.xml: fix 'invalid' attribute on AUTOPILOT_STATE_FOR_GIMBAL_DEVICE
being an extension, we can't assume that a sender will know to send the attitude rate across. 0 must then be assumed to mean "unknown" not "not moving"
* ftp: add ListDirectoryWithTime with change time
The current ListDirectory command doesn't support the last changed time
of a file or directory. This is a limitation when it comes to using FTP
to download logs.
Therefore, I suggest to add ListDirectoryWithTime here, somewhat similar
to how it was done for in the internet FTP protocol which added the
machine-readable `MLSD` command alongside the original `LIST`.
See: RFC 3659: https://datatracker.ietf.org/doc/html/rfc3659
* Apply suggestion from @hamishwillee
---------
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
WHEP is a WebRTC extension that allows to read streams by using a URL,
without passing through a web page. This allows to use WebRTC as a
general purpose streaming protocol.
Unlike RTSP, WHEP benefits from WebRTC's built-in adaptive bitrate and
congestion control, making it significantly more resilient on poor or
unstable network connections.
the message was merged in 2020 and never moved out of wip / development.xml
No code in PX4-AutoPilot, ArduPilot, betaflight, paparazzi, QGC, MissionPlanner, apm_planner2
When param3 bit 0 is not set, the vehicle must reject the command if it will not
automatically manage horizontal position. Documents existing ArduPilot
behaviour (ArduCopter GCS_MAVLink_Copter.cpp).
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
ArduPilot uses these two values in MAV_CMD_PREFLIGHT_CALIBRATION
to force-accept an existing sensor calibration without re-running it:
param2 = 76 force-accept current compass calibration as valid
param5 = 76 force-accept current accelerometer calibration as valid
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This is an attempt to fix the gimbal device vs. manager flags.
Instead of capping the device flags at 16 bits, we add an extension for
32 bits, and we copy any manager flags across.
For backwards compatibility, a gimbal device needs to set the 16 lower
bits as well as the new 32 bits.
A ground station or gimbal manager can tell whether a gimbal device
supports the new 32 bit flag if it is non-zero.
Andrii Anoshyn