From b1fa2e39de949029f367ce9cc7eed5ef851d2167 Mon Sep 17 00:00:00 2001 From: jlpoltrack <41841496+jlpoltrack@users.noreply.github.com> Date: Wed, 21 Feb 2024 20:06:14 -0500 Subject: [PATCH] Update message_definitions/v1.0/development.xml Co-authored-by: Hamish Willee --- message_definitions/v1.0/development.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/message_definitions/v1.0/development.xml b/message_definitions/v1.0/development.xml index 63777e8876..aeceaff67e 100644 --- a/message_definitions/v1.0/development.xml +++ b/message_definitions/v1.0/development.xml @@ -54,7 +54,7 @@ The target_component field can normally be set to 0, so that all components of the system can receive the message. The channels array field can publish up to 32 channels; the number of channel items used in the array is specified in the count field. The time_last_update_ms field contains the timestamp of the last received valid channels data in the receiver's time domain. - The count field indicates the first index of the channel array that holds invalid data. + The count field indicates the first index of the channel array that is not used for channel data (this and later indexes are zero-filled). The RADIO_RC_CHANNELS_FLAGS_OUTDATED flag is set by the receiver if the channels data is not up-to-date (for example, if new data from the transmitter could not be validated so the last valid data is resent). The RADIO_RC_CHANNELS_FLAGS_FAILSAFE failsafe flag is set by the receiver if the receiver's failsafe condition is met (implementation dependent, e.g., connection to the RC radio is lost). In this case time_last_update_ms still contains the timestamp of the last valid channels data, but the content of the channels data is not defined by the protocol (it is up to the implementation of the receiver).