mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-04-14 10:07:39 +08:00
* Applying PR #17084 * Comitting missing changes * Adding incoming SETUP_SIGNING handling * Adding proper message decoding for SETUP_SIGNING * Adding persistance of sign key in chunks of 32 bits into parameters * Allowing SETUP_SIGNING to be handled only on usb_uart * Removing unused type and variable * Changing the default for Mavlink Timestamp * Fixing styling * Merging * Merging submodules * Replacing parameters with sdcard storage for secured key and ts * Fixing styles * Isolating signing related items in separate class * Adding new files * Syncing with main * Fixing styles * Changing the signing logic to work only if key and ts properly initialized, adding store the ts on stop * Updated submodules to latest versions * Updated gz to proper version * libfc-sensor-api to proper version * libcanard to proper version * Updated fuzztest to proper version * Updated public_regulated_data_types to proper version * Updated mip_sdk to proper version * Updated pydronecan to proper version * Updated rosidl to proper version * Fixing styles * Fixing cyclonedds version * initializing sign control in the member declaration * Update src/modules/mavlink/mavlink_main.h Co-authored-by: Jacob Dahl <37091262+dakejahl@users.noreply.github.com> * Fixing comments * Fixing duplicate method * Fixing defines * Fixing styles * Fixing the define errors * replace duplicate logic with write_key_and_timestamp() function * add docs * Update docs/en/mavlink/message_signing.md Co-authored-by: Julian Oes <julian@oes.ch> * Update src/modules/mavlink/mavlink_sign_control.cpp Co-authored-by: Hamish Willee <hamishwillee@gmail.com> * Update src/modules/mavlink/mavlink_sign_control.h Co-authored-by: Hamish Willee <hamishwillee@gmail.com> * Update docs/en/mavlink/message_signing.md Co-authored-by: Hamish Willee <hamishwillee@gmail.com> * rename to MAV_SIGN_CFG, fix copyright dates, fix docs SHA type, rename secrets file * fix newlines --------- Co-authored-by: Jacob Dahl <37091262+dakejahl@users.noreply.github.com> Co-authored-by: Jacob Dahl <dahl.jakejacob@gmail.com> Co-authored-by: Julian Oes <julian@oes.ch> Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
3.6 KiB
3.6 KiB
MAVLink Microservices (Protocols)
MAVLink "microservices" are a protocols that use multiple messages exchanged between components to communicate more complicated information. For example, the Command Protocol provides an efficient mechanism for packaging a command in a (particular) message and receiving acknowledgement of the command in another message.
MAVLink microservices are documented the MAVLink Guide (this is not exhaustive: not all messages are grouped into protocols and not all protocols are documented).
This section lists the services known to be supported/not supported by PX4 in this version.
Supported Microservices
These services are known to be supported in some form:
- Battery Protocol
- BATTERY_STATUS and BATTERY_INFO are streamed.
- Camera Protocols
- Command Protocol
- Component Metadata Protocol
- Events Interface
- File Transfer Protocol (FTP)
- Gimbal Protocols
- Gimbal Protocol v2
- Can be enabled by Gimbal Configuration
- PX4 an act as a MAVLink Gimbal for one FC-connected Gimbal
- Gimbal Protocol v2
- Heartbeat/Connection Protocol
- High Latency Protocol — PX4 streams HIGH_LATENCY2
- Image Transmission Protocol
- Landing Target Protocol
- Manual Control (Joystick) Protocol
- MAVLink Id Assignment (sysid, compid)
- Message Signing (MAVLink spec)
- Mission Protocol
- Offboard Control Protocol
- Remote ID (Open Drone ID Protocol)
- Parameter Protocol
- Parameter Protocol Extended — Allows setting string parameters. Used for setting string parameters set in camera definition files.
- Payload Protocol
- Ping Protocol
- Standard Modes Protocol
- Terrain Protocol
- Time Synchronization
- Traffic Management (UTM/ADS-B)
- Arm Authorization Protocol
Unsupported
These services are not supported/used by PX4: