CTS-SAT-1-OBC-Firmware
|
The first byte of the packet (after the 4-byte CSP header) is the packet type. The packet type is an enum which indicates the type of packet being sent. The packet type is used to determine how to parse the rest of the packet.
0x01
- beacon (basic telemetry, no peripherals)0x02
- beacon (peripheral telemetry)0x03
- log message0x04
- telecommand response0x10
- bulk file downlink0x01
)TODO: Fill in the format here. For now, see https://github.com/CalgaryToSpace/CTS-SAT-1-OBC-Firmware/issues/338.
0x02
)TODO: Fill in the format here. For now, see https://github.com/CalgaryToSpace/CTS-SAT-1-OBC-Firmware/issues/338.
0x03
)This packet type does not have sequence numbers. All log messages fit within (or are truncated to fit within) a single packet.
Plain text content, same as UART messages.
0x04
)This packet type has sequence numbers.
response_output_buf
, null terminated0x10
)This packet type has sequence numbers.
All multi-byte integers in these packets are in little-endian format.
For example, a uint16_t value of 1013 (0x03F5) would be sent as [0xF5, 0x03].
The packet length is encoded by the AX100 in the ASM+GOLAY encoding scheme.
It is not managed nor encoded in the packets at the level handled by this firmware on the OBC.