Changes

| style="background-color: #8AFFDF;"|

| style="background-color: #8AFFDF;"|

Length - (00000000)

Length - (00000000)

| style="background-color: #AD6DF9;"|

| style="background-color: #AD6DF9;"|

Data -- Absolute Board Identifier (1 byte)

Data -- Absolute Board Identifier (1 byte)

|}

|}

This particular gesture definition is reserved, and is known as the ''beacon gesture''. It is defined by Source & Destination Identifiers of 15 (broadcast), 0 Flags, 0 Length, and a data frame consisting only of a 1 byte ABI.  

This particular gesture definition is reserved, and is known as the ''beacon gesture''. It is defined by Source & Destination Identifiers of 15 (broadcast), 0 Flags, 0 Length, a Gesture Type of 1, and a data frame consisting only of a 1 byte ABI, zero padded.

The beacon gesture is transmitted to the entirety of the stack, and uniquely identifies a given board as being present in the flight stack. In the initialization phase, each board transmits the beacon gesture every 2 seconds. The Avionics waits 5 seconds to receive all beacon gestures, then re-assigns the received ABI's into FSI's. The FSI's are then provided to STINGR, which provides the FSI's to all other boards in the stack. Once the FSI's have been re-assigned and re-distributed, the initialization phase is over.

The beacon gesture is transmitted to the entirety of the stack, and uniquely identifies a given board as being present in the flight stack. In the initialization phase, each board transmits the beacon gesture every 2 seconds. The Avionics waits 5 seconds to receive all beacon gestures, then re-assigns the received ABI's into FSI's. The FSI's are then provided to STINGR, which provides the FSI's to all other boards in the stack. Once the FSI's have been re-assigned and re-distributed, the initialization phase is over.