Ground Support Software

Yongho KimAug 2, 2011

What CINEMA sub-system I been working on?

: My Job

What CINEMA sub-system I been working on?

: My Job

What was the state of the system when I got started?TLM_Receiver RS decoder GSEOS

Nothing.. Nothing.. Interface - Serial line - TCP/IP connection with MPS

Functions - CCSDS frame, packet parser - Decode telemetry based on APID - Transmit binary-type Immediate command to FSW

Error Handling - CCSDS parser exception - APID decoder exception - CMD generation exception

Integration test - Test with FSW for Mode change, start downlink, stop downlink command

TLM_receiver◦ Using C# (programming language)◦ Send telemetry transmitted from satellite to RS decoder◦ Store telemetry as a file which can be re-loaded if Mission Planning System wants

What is the state now, and who is affected by it?

Interface-TCP/IP(done)-Error handling(done)

Function-Receive telemetry from S-band RF device using RS422 I/F (done)-Error handling(almost done)-Remote operation(on going)-Store telemetry as a file(done)

Error Handling-TCP/IP exception(done)-Remote operation exception(on going)

Integration test & Inner functional test-Inner functional test (done)-Integration test with RS decoder (done)- Integration test with s-band RF chain(not performed)

CCSDS(255, 223) RS(Reed-Solomon) decoder◦ Use RS coder (verified by satellite company in Korea) based on C#◦ Decode telemetry and can correct up to 80 bytes for each CCSDS frame(1,275

bytes)

What is the state now, and who is affected by it?

Interface-TCP/IP(done)-Error handling(on going)

Function- Decode telemetry (done)- Error handling (done)- Remote operation(on going)

Error Handling-TCP/IP exception(on going)-Remote operation exception(on going)

Integration test & Inner functional test-Inner functional test (done)-Integration test with GSEOS (done)- Integration test with TLM_receiver (done)

CINEMA requirement

Bit rate for downlink 1 Mbps = 125,000 bytes/sec = 98 CCSDS

frames(1,275 bytes) / sec

Type Average time at once

Worstest time at once

Averagebit rate

WorstBit rate

Intel Core2duo (1.4 GHz) with no parity error

2.32 milisec 8 milisec 4.4

Mbps 1.2 Mbps

Intel Core2duo (1.4 GHz) with 5 parity error

2.51 milisec 7 milisec 4.0

Mbps 1.4 Mbps

Intel Core2duo (2.0 GHz) with no parity error

1.09 milisec 3 milisec 9.3

Mbps 3.4 Mbps

Intel Core2duo (2.0 GHz) with 5 parity error

2.03 milisec 3milisec 5.0

Mbps 3.4 Mbps

GSEOS(Update EPS, Battery statement in GSEOS)◦ Parsing EPS, Battery information with calibration equiation based on EPS

document◦ Integration test with FSW using EPS, Battery device is done

What is the state now, and who is affected by it?

GSEOS(Implementation of delay CMD based on CTM)◦ Generate delay CMD with timestamp(5 bytes)◦ Integration test with newest version of FSW is done◦ Transmitted delay CMD was executed depending on the timestamp◦ We tested only start downlink, stop downlink delay CMD. Implementation of other

delay CMD defined in CTM is matter of time

What is the state now, and who is affected by it?

Time

Transmit delay CMDWith timestamp CMD will be executed

The timestamp

GSEOS(Showing payload data)◦ STEIN

According to stein data structure, have to draw 32 stripcharts for 32 ch detector For now, we considerd only 2 ch

◦ MAGIC Just set up a window for MAGIC science data When MAGIC module in FPGA is done, we can test with FSW using IIB, MAGIC

What is the state now, and who is affected by it?

time

Event countSecond channel detector Fourth channel detector

GSEOS(RF test with Jonathan)◦ GSEOS transmits telecommand through radio equipments◦ Test was successful and transmitted data was shown in Helium radio configuration

program

What is the state now, and who is affected by it?

time

Attenuators

GSEOS

Digital

TransceiverWith TNC Helium Radio

Helium radioConfiguration programdsPic

RF signalDigital

(CDI packet) Digital

Ground Station Manager◦ Manage whole ground system◦ Send command(not telecommand) to perform what we want to do◦ Monitor the status of each sub-system(i.e. TLM_receiver, RS decoder, GSEOS1 and

2)◦ I/F is done◦ Connection between subsystem and GS Manager is using private TCP line

(not data line)

What is the state now, and who is affected by it?

Write ground support software CPD document

Write GSEOS CPD document Write ground station operation document

How has this progress been documented?

What remains before this system is part of a flight-ready satellite?

TLM_Receiver RS decoder GSEOS

Done

Interface-TCP/IP connection-Connect with GS ManagerFunctions-Receive TLM-Save TLM-Transmit TLMError handling-Connection ExceptionIntegration test -Test with RS decoder

Interface-TCP/IP connectionFunctions-Receive TLM-Decode RS encoded TLMError handling-noneIntegration test -Test with GSEOS, TLM_receiver-Test with FPGA’s RS encoder using text file

Interface - Serial line - TCP/IP connection with MPSFunctions - CCSDS frame, packet parser - Decode telemetry based on APID - Transmit binary-type Immediate command to FSWError Handling - CCSDS parser exception - APID decoder exception - CMD generation exceptionIntegration test - Test with FSW for Mode change, start downlink, stop downlink command

Remains

Interface- noneFunctions-Execute remote CMD from GS Manager-Remote command handlingError handling- Remote control exceptionIntegration test - Test with s-band RF devices

Interface- Connect with GS ManagerFunctions-Execute remote CMD from GS Manager-Remote command handlingError handling-Remote control exception-TCP/IP exceptionIntegration test - Decoding speed test using GSE computer with full load

Interface-noneFunctions-Decode CCSDS frame depending on TM module-Remote command handlingError handling-GS Manager ExceptionIntegration test -Test with FSW using MAG module-Test with FSW using STEIN module-Test CMD generation with MPS