28 of May - Decoding state of the art

On Discord, Daniel Estévez summarized the decoding process state of the art.
Link to the post: https://discordapp.com/channels/1066055437457297469/1110258553689739276/1112487058326437960

Step 1

Starting from the SigMF recording of the TGO radio frequency signal done by Green Bank Telescope, the signal on the telemetry subcarrier has been demodulated and the Turbo code has been decoded. The output of this step is:

<frames.bin> frames.bin (7.01 MB)

This is a binary file that contains the TM Space Data Link frames transmitted by TGO. Each frame is 1115 bytes long, and there are 6591 frames in the file. The frames are stored back-to-back. Full transfer frames (as per Figure 4-1 in [CCSDS 132.0-B-3](https://public.ccsds.org/Pubs/132x0b3.pdf) are stored in this file).

There are no jumps in the master channel frame count of the frames in this file (indicating no lost frames), and all the frame error control fields (CRC-16) are correct, indicating no data corruption.

Step 2

The Space Packets in the Transfer Frame Data Field of the TM frames from step 1 have been extracted. The output of this step is:

<encap_001.bin> encap_001.bin (3.98 MB)

This is a binary file that contains the Space Packets transmitted by TGO in virtual channel 0. The length of each Space Packet is variable and there are 242725 Space Packets in the file. The Space Packets are stored back-to-back. Packet boundaries can be determined by reading the packet length data field in the Space Packet Primary Header (as per Section in [CCSDS 133.0-B-2](https://public.ccsds.org/Pubs/133x0b2e1.pdf)). Full space packets (as per Figure 4-1 in CCSDS 133.0-B-2) are stored in this file.

Leave a Reply

Your email address will not be published. Required fields are marked *


Your Signs in Space - vol.1
29 of May - What is this?