Make sure docs are updated / settings_md (push) Canceled after 0s
Build firmware / test (push) Canceled after 0s
Build firmware / build-SITL-Windows (push) Canceled after 0s
Build firmware / build-SITL-Mac (push) Canceled after 0s
Build firmware / build-SITL-Linux (push) Canceled after 0s
Build firmware / build-SITL-Linux-arm64 (push) Canceled after 0s
Build firmware / upload-artifacts (push) Canceled after 0s
Build firmware / build-single-target (push) Canceled after 0s
Build firmware / build (9) (push) Canceled after 0s
Build firmware / build (8) (push) Canceled after 0s
Build firmware / build (7) (push) Canceled after 0s
Build firmware / build (6) (push) Canceled after 0s
Build firmware / build (5) (push) Canceled after 0s
Build firmware / build (4) (push) Canceled after 0s
Build firmware / build (3) (push) Canceled after 0s
Build firmware / build (2) (push) Canceled after 0s
Build firmware / build (14) (push) Canceled after 0s
Build firmware / build (13) (push) Canceled after 0s
Build firmware / build (12) (push) Canceled after 0s
Build firmware / build (11) (push) Canceled after 0s
Build firmware / build (10) (push) Canceled after 0s
Build firmware / build (1) (push) Canceled after 0s
Build firmware / build (0) (push) Canceled after 0s
Build firmware / detect (push) Canceled after 0s
Build pre-release / build (push) Canceled after 0s
Build pre-release / Release (push) Canceled after 0s
1.3 KiB
1.3 KiB
INAV MSP Messages reference
This page is auto-generated from the master INAV MSP definitions file
For details on the structure of MSP, see The wiki page
For list of enums, see Enum documentation page
JSON file rev: <file_rev>
Warning: Verification needed, exercise caution until completely verified for accuracy and cleared, especially for integer signs. Source-based generation/validation is forthcoming. Refer to source for absolute certainty
If you find an error, it must be corrected in the JSON spec, not this markdown.
Guide:
- MSP Versions:
- MSPv1: The original protocol. Uses command IDs from 0 to 254.
- MSPv2: An extended version. Uses command IDs from 0x1000 onwards.
- Request Payload: The request payload sent to the destination (usually the flight controller). May be empty or hold data for setting or requesting data from the FC.
- Reply Payload: The reply sent from the FC to the sender. May be empty or hold data.
- Notes: Pay attention to message notes and description.