X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=AltOS%2Fdoc%2Fcompanion.html;h=7d903876bcb16864ffd3717ac4064c6abf55ee25;hb=821aac6888b80a89548b7ab7b9cbfa46f44ca1c3;hp=2d6ab4bd321e40e6d8d04097bae8f5e441b1d5b5;hpb=b35d0beb5b519dbec8bef286a3f8a0cb35c7bcf0;p=web%2Faltusmetrum diff --git a/AltOS/doc/companion.html b/AltOS/doc/companion.html index 2d6ab4b..7d90387 100644 --- a/AltOS/doc/companion.html +++ b/AltOS/doc/companion.html @@ -1,10 +1,10 @@ -
Copyright © 2012 Keith Packard
+
Copyright © 2012 Keith Packard
This document is released under the terms of the Creative Commons ShareAlike 3.0 license. -
Revision History | |
---|---|
Revision 0.1 | 13 January 2012 |
Initial content |
Table of Contents
Revision History | |
---|---|
Revision 0.1 | 13 January 2012 |
Initial content |
Table of Contents
Many Altus Metrum products come with an eight pin Micro MaTch connector, called the Companion Port. This is often used to program devices using a programming cable. However, it can also @@ -25,7 +25,7 @@ provide a matching SPI slave implementation which supplies telemetry information for the radio downlink during flight
-
The flight computer implements a SPI master communications channel over the companion port, and uses this to get information about a connected companion board and then to get @@ -42,11 +42,11 @@
Because of the limits of the AVR processors used in the first two companion boards, the SPI data rate is set to 187.5kbaud. -
This section first defines the command message format sent from the flight computer to the companion board, and then the various reply message formats for each type of command message. -
Table 1. Companion Command Message
Offset | Data Type | Name | Description |
---|---|---|---|
0 | uint8_t | command | Command identifier |
1 | uint8_t | flight_state | Current flight computer state |
2 | uint16_t | tick | Flight computer clock (100 ticks/second) |
4 | uint16_t | serial | Flight computer serial number |
6 | uint16_t | flight | Flight number |
8 |
Table 2. Companion Command Identifiers