Telco EGSE TMTC SCOE:
The overall function of the Atos Baseband TM/TC SCOE and TM/TC Crossbar is to provide validated interface hardware and software functions to interface baseband TM and TC hardware with the remaining EGSE infrastructure. This includes high-speed baseband data interfaces to On-Board Computers, COMMS elements such as Transponders and Modulators, Security Units, etc. Further applications of the envisaged functions are EGSE systems on subsystem level, which require baseband TM/TC interfaces and functions based on these, as well as Umbilical Test Systems used at the launch location, prior to connecting the actual spacecraft.
Telco EGSE Power SCOE:
The Power Special Check-Out Equipment (SCOE) is part of the electrical ground Support Equipment that provides via the current Atos UniverSAS® product the required electrical power, simulates the real spacecraft battery and the solar array behaviour and provides monitoring of some onboard electrical parameters. It is used during all phases of the spacecraft integration and test, i.e. from Avionics Test Bench (ATB) and Service Module (SVM) integration up to the launch campaign. The main objective is to extend the capabilities of the Atos UniverSAS® product to cover also different Telecom satellite requirements through generic firmware and software solutions.
Telco EGSE TMTC SCOE:
Telco EGSE Power SCOE:
Telco EGSE TMTC SCOE:
Telco EGSE Power SCOE:
Telco EGSE TMTC SCOE:
Allow reliable long-duration operation over the USB interface to the host computer at the required data rates and latencies
Cover all TM/TC Crossbar requirements as in the legacy implementation, extend the functions to support longer ASMs (e.g. needed for LDPC), raw bit-stream output, graceful handling of almost noise CLTUs
Modular approach removing or reducing custom wiring and mechanical fixing
Migrate the lower levels of the software stack to USB communication. Extend the API functions to more parameter and functions.
Create the top-level TMTC SCOE Software, allowing TM and TC processing in various standard formats, display, routing, archiving and retrieval of data, support for external interfaces (e.g. CCS).
Telco EGSE Power SCOE:
Allow operation of at least 32 SAS channels
Allow synchronisation of at least 32 SAS channels with a high resolution
The TM packets including data for at least 32 SAS channels in master and slave configuration have to be delivered in a cycle time of less than 500ms.
Handle S3R with a toggling frequency of up to 30kHz.
Current slope dI/dU for output current between Isc and Imp shall be adjustable for a section with a range of 1/Rs from zero to 5% of Isc/Voc.
For generic load simulation inside a Payload Load Simulator (PLLS) the UniverSAS®Electronic Loads must also be capable to support the following modes:
Constant Current (CC), Constant Power (CP), Constant Resistance (CR).
Ripple ≤ 150mVpp @ 20 MHz bandwidth while retaining a low output capacitance ≤ 250nF.
Ripple ≤ 50mVpp @ 20 MHz bandwidth
Telco EGSE TMTC SCOE - Architecture:
Telco EGSE Power SCOE – Architecture:
A significant part of the enhancement development will focus to improve UniverSAS® with the requirements of Telco Satellites. The most important areas are indicated in orange in above figure.
High Level Project Plan with milestones
WP1000 PM / QM
KO: Kick-off Meeting PM / QM Activity
WP2000 Requirements Analysis
WP2100/WP2200 TMTC/POWER Requirements Analysis WP3000 Design
WP3100/WP3200 TMTC/POWER Design
MS#1: Critical Design Review (CDR) WP4000 Implementation
WP4100/WP4200 TMTC/POWER Implementation WP5000 Manufacturing
WP5100 TMTC Manufacturing
WP6000 - Integration, Verification and Validation WP6100 TMTC Integration and Verification
MS#2: TMTC/POWER - Test Readiness Review (TRR)
TMTC/POWER - System Test + Factory Acceptance Test (FAT)
MS#3: TMTC/POWER - Test Review Board (TRB)
WP6200 Power Integration and Verification
WP7000 Final Report
MS#4: Final Settlement
Project Kick-Off done and the HW/SW technical requirement specification and preparation for the requirement review milestone ongoing. The requirement documentation is currently in review at ESA.