Difference between revisions of "Gen 1 Software"
| Line 1: | Line 1: | ||
'''STINGR (Stack Transmission & Inter-Nodal Gesture Repository''' is the primary software suite used within the HONEY architecture for communication between boards in a HONEY flight stack. | '''STINGR (Stack Transmission & Inter-Nodal Gesture Repository''' is the primary software suite used within the HONEY architecture for communication between boards in a HONEY flight stack. | ||
| − | STINGR allows boards in the flight stack to do a number of critical operations and provides a large number of utilities for FTC's, providing an easy-to-use interface that masks the complexity of CAN Bus transmissions from developers. | + | STINGR allows boards in the flight stack to do a number of critical operations and provides a large number of utilities for FTC's, providing an easy-to-use interface that masks the complexity of CAN Bus transmissions from developers. The STINGR library is primarily comprised of operations called ''Gestures'' -- any request or response on the CAN Bus is referred to as a Gesture. Gestures are comprised of a series of frames, which provide the following information for each transmission: Type (Request/Response), Source Identifier, Destination Identifier, Data, State Flags, and Checksum. |
| + | |||
| + | == Gesture Specification == | ||
| + | As mentioned above, a Gesture consists of a series of frames, each with a specific purpose. Each Gesture is transmitted on the CAN Bus, and allows all boards to determine if a Gesture is targeted towards them, and act appropriately. This section defines the specification of a Gesture, including a description of each of the frames. | ||
| + | |||
| + | More explicitly, a Gesture looks as so, with the leftmost frames being transmitted first, and the rightmost frames being transmitted last. | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |Type (Req/Resp) | ||
| + | |Source Identifier | ||
| + | |Destination Identifier | ||
| + | |Data | ||
| + | |State Flags | ||
| + | |Checksum | ||
| + | |} | ||
| + | |||
| + | === Type Frame === | ||
| + | The Type frame, the first frame in | ||
| + | |||
| + | |||
| + | == Core Functions == | ||
Revision as of 02:28, 22 June 2017
STINGR (Stack Transmission & Inter-Nodal Gesture Repository is the primary software suite used within the HONEY architecture for communication between boards in a HONEY flight stack.
STINGR allows boards in the flight stack to do a number of critical operations and provides a large number of utilities for FTC's, providing an easy-to-use interface that masks the complexity of CAN Bus transmissions from developers. The STINGR library is primarily comprised of operations called Gestures -- any request or response on the CAN Bus is referred to as a Gesture. Gestures are comprised of a series of frames, which provide the following information for each transmission: Type (Request/Response), Source Identifier, Destination Identifier, Data, State Flags, and Checksum.
Gesture Specification
As mentioned above, a Gesture consists of a series of frames, each with a specific purpose. Each Gesture is transmitted on the CAN Bus, and allows all boards to determine if a Gesture is targeted towards them, and act appropriately. This section defines the specification of a Gesture, including a description of each of the frames.
More explicitly, a Gesture looks as so, with the leftmost frames being transmitted first, and the rightmost frames being transmitted last.
| Type (Req/Resp) | Source Identifier | Destination Identifier | Data | State Flags | Checksum |
Type Frame
The Type frame, the first frame in