- Partnership Projects
- Core Competitiveness
- How to Apply
- Our Projects
There are many expectations on a generic EGSE, but some of the major objectives during the project execution was:
The toolchain has been designed to seamlessly work together providing the operator an EGSE with necessary tools to efficiently focus on the essential testing campaign.
There have been two major challenges to solve:
First, major EGSE elements have been designed using a web-based interface. Against traditional EGSE where a local GUI is necessary, this concept allows the results analysis and control of the EGSE from remote locations using standard web-browsers.
Second, since the EGSE implements its measurements for parallel execution, this complexity was to be hidden from the integration tasks as much as possible. Not every RF engineer needs to know how to safeguard in multi-threaded environments.
The Telco EGSE can even be installed in headless VMs (Virtual Machines) since it is fully remote controllable. The web-based interface of its tools like reporting, synoptic, configuration editor and the client-server architecture of its main test-software makes it unique along traditional test-systems.
With its complete toolchain the Telco EGSE comes as a turn-key solution for various project requirements simplifying test and integration of various payload systems.
The Telco EGSE consists of several components, which could also be used as a stand-alone product:
The main test-application: The main application implemented as client-server architecture. The graphical user interface is completely decoupled from the main test-software. The test-software is multi-threaded, devices can be shared between tests and are synchronized automatically. Pre-defined telemetry packets, measurement tasks and uplink modulation schemes exist to facilitate testing.
The Telco EGSE focuses on real client-server architecture. All graphical elements are decoupled from the main testing software:
The GUI is operated in a separate process – independent from the main SCOE service. The GUI process can be started and closed without interfering ongoing operation of the SCOE service. Remote Control can be even operated without a started GUI.
The communication between SCOE service and SCOE GUI is realized via a local TCP/IP connection.
The activity has concluded. The product is fully operational in its first mission: ONEWEB DITL RF SCOE.