From a9dcb2f0a63ecaddfc14d226e78cc3c2f2c9d941 Mon Sep 17 00:00:00 2001 From: Jonathan Hudson Date: Mon, 12 Jun 2023 22:45:13 +0100 Subject: [PATCH] fix msp nav typo --- MSP-Navigation-Messages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MSP-Navigation-Messages.md b/MSP-Navigation-Messages.md index 175e1d4..750f15b 100644 --- a/MSP-Navigation-Messages.md +++ b/MSP-Navigation-Messages.md @@ -469,7 +469,7 @@ All values are little endian; of particular note: * `action`, `p1`, `p2` and `p3` are encoding according to the values in sections [WayPoint and Action Attributes](#waypoint-and-action-attributes) and [P3 bitfield usage](#p3-bitfield-usage). * `flag` values are `0` (default), `72` Fly by home WP, `165` final WP. -Depending on your preference and programming language features, you can either write the (little endian) values directly into a packed structure, or individually serialise each element into a contiguous byte array (21 bytes total). In the latter case, the `lat` value would occupy byte offsets 4-7. +Depending on your preference and programming language features, you can either write the (little endian) values directly into a packed structure, or individually serialise each element into a contiguous byte array (21 bytes total). In the latter case, the `lat` value would occupy byte offsets 2-5. So for the simple mission (one geographic WP and RTH) -- 2.11.4.GIT