Changes

{{tech-sidebar

{{HONEY-sidebar

| header = STINGR

| header = STINGR

| img link = File:stingr.png

| img link = File:stingr.png

| version = Generation I

| version = Generation I

| name = STINGR

| name = STINGR

| missions = SSI-52 onward

| acronym = Stack Transmission & Inter-Nodal Gesture Repository

}}

}}

As mentioned above, a Gesture consists of a series of CAN Packets -- these packets specify the source and destination of a gesture, some auxiliary data, and the primary data payload. STINGR manages CAN Packets, which are hidden from the end-user, and managed entirely by STINGR.  

As mentioned above, a Gesture consists of a series of CAN Packets -- these packets specify the source and destination of a gesture, some auxiliary data, and the primary data payload. STINGR manages CAN Packets, which are hidden from the end-user, and managed entirely by STINGR.  

More explicitly, a Gesture looks is comprised of an initialization CAN Packet, followed by up to 256 additional CAN Packets, each comprised of a 1 byte header and 7 byte data payload, for a total possible data length of 256 * 7 = 1,792 bytes. The initialization CAN Packet consists of the standard header, 3 bytes of additional information, and 4 bytes of data payload. Subsequent CAN Packets consist of the 1 byte header and up to 7 bytes of data. The general structure of this format is as such:

More explicitly, a Gesture looks is comprised of an initialization CAN Packet, followed by up to 256 additional CAN Packets, each comprised of a 1 byte header and 7 byte data payload, for a total possible data length of 255 * 7 = 1,792 + 4 bytes (255 packets, plus 4 bytes of data in the initialization packet). The initialization CAN Packet consists of the standard header, 3 bytes of additional information, and 4 bytes of data payload. Subsequent CAN Packets consist of the 1 byte header and up to 7 bytes of data. The general structure of this format is as such:

{| class="wikitable"

{| class="wikitable"

When a flight stack is constructed and assembled, it ends up being comprised of a series of boards each with one of these unique, enumerated identifiers. It should be noted that a flight stack '''cannot exceed''' 15 boards total (3U). Upon boot-up, the Avionics receives a variety of messages from STINGR identifying all boards in the flight stack, and re-labels the identifiers to the '''Flight Stack Identifiers''' (FSI) format, whereby all 8-bit identifiers are re-categorized and re-assigned into 4-bit stack-relative addresses.  

When a flight stack is constructed and assembled, it ends up being comprised of a series of boards each with one of these unique, enumerated identifiers. It should be noted that a flight stack '''cannot exceed''' 15 boards total (3U). Upon boot-up, the Avionics receives a variety of messages from STINGR identifying all boards in the flight stack, and re-labels the identifiers to the '''Flight Stack Identifiers''' (FSI) format, whereby all 8-bit identifiers are re-categorized and re-assigned into 4-bit stack-relative addresses.  

More details about the re-assignment process can be found in the operations section of STINGR, below on this page.

More details about the re-assignment process can be found in the operations section of STINGR, below on this page.

The following are the current ABI's, as of writing (June 28, 2017).

The following are the current ABI's, as of August 10, 2017).

{| class="wikitable"

{| class="wikitable"

|Macaw (Gen 1 Radio)

|Macaw (Gen 1 Radio)

|00000010

|00000010

|}

|}

Data -- Absolute Board Identifier (1 byte)

Data -- Absolute Board Identifier (1 byte)

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

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

0 Padded (4 bytes)

0 Padded (3 bytes)

|}

|}

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.

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 a 1 byte ABI and a 1 byte Serial Number, 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.

</code><br />

</code><br />

Sends a speciality gesture to all boards to resume all operations.

Sends a speciality gesture to all boards to resume all operations.