Improved Level of Information provided in TM

Objectives

The continuous growing sophistication and size of GEO spacecraft leads to a large increase of the amount of TM available on board.

Moreover, the improvements in the performances of the data acquisition devices like A/D converters lead to an increase of the accuracy of the data acquired on board and in turn to an increase of the bandwidth necessary to download all the information.

Looking onto the heritage data and lesson learned from troubleshooting and on flight management of GEO satellite, and in the dialogue with usual prime industries, it has been paradoxically pointed out the decrease in the amount of meaningful TM available to satellite operators and the new difficulty for them to exploit all telemetry especially during emergency.

It has been found that:

  • Large amounts of telemetry are wasted due to exceeded accuracy w.r.t the parameter to be measured/monitored.
  • Some parameters are meaningless due to the multiple stage of the data acquisition chain.
  • Some parameters are meaningless due to the inappropriate monitoring on ground: checks are more often done on a wider range than the actual distribution of the data to cover all the life phase and to avoid false alarms. Right adjustment of the monitoring parameters requires prior knowledge that is difficult to acquire for the operators. 

In the end, the large amount of TM available distracts the operators from the strictly necessary telemetry to be treated during the emergency, and makes operations of the spacecraft overly complex.

The TMU (TeleMetry Unit) is a VHDL Core developed by Thales Alenia Space to acquire and process a set of telemetry channel data with the aim of improving the TM data usefulness and of reducing the amount of data downloaded on ground

Challenges

  • To take a fresh look at the needs of the operators and THALES as regards the TM capability of GEO telecom spacecraft, with a great care about the return from experience of in orbit satellite: lessons learned from spacecraft events or failures.
  • Considering the selected set of TM: to present the new method of accessing and processing these TM and to define a set of requirements, in particular for diagnostic mode and required accuracy.
  • To define, manufacture and validate an electric Bread Board (EBB) of a stand-alone TM interface, so called the “TM Unit”, implementing the previous requirements; the result of its impact on operability of the spacecraft should be analysed

Benefits

The great advantage of the TMU over a standard telemetry unit is that by only reading a “Synthetic Report” (composed by only 5 data words of 16 bit) the SMU can verify that all units monitored by the TMU are in nominal status; since the Synthetic Report can be sampled often, the reaction time in case of a unit fault is drastically shortened.

Also, by only fetching the various Algorithms Processing Reports (only 8 data words of 16 bit) the ground station can have useful information on the units status (such as average values, calibrated readings), reducing the bandwidth needed for telemetry.

Moreover, the TMU can apply an effective compression algorithm on the acquired data.

In case of a unit under monitor becomes faulty, the TMU signals the event by raising an event flag on its Synthetic Report and automatically fills in a detailed Event Report (composed by 15 data words of 16 bit) of the faulty unit at the specific moment of fault. 

Therefore the TMU features are:

  • Drastically save the required RF bandwidth needed for telemetry toward the ground station.
  • Reduce the ground station workload for processing the satellite telemetry (as such processing is performed on board by the TMU).
  • Reduce the storage memory requirements (hence layout space) for the telemetry unit board.
  • Possibility to apply relatively high sampling rates to units under monitor (as irrelevant or old data is automatically discarded or compressed). This allows detailed data analysis before and after events.

Features

The TMU (TeleMetry Unit) is a VHDL Core developed by Thales Alenia Space to acquire and process a set of telemetry channel data with the aim of improving the TM data meaning and of reducing the amount of data downloaded on ground.

The TMU implements the following functions:

  • Acquisition of a programmable set of TM channels, with the possibility to define for every channel a different acquisition rate and to apply a preliminary filter to select the useful part of the data only.
  • Association of every TM channels to a specific group in order to get temporally and functionally coherent sets of data as much as possible.
  • Processing of the TM acquired values by means of one or more processing algorithms.
  • Storage of the acquired data to make them available for investigation in case of un-expected event occurrence detected through the TM data processing.
  • Generation of Housekeeping Telemetry from the acquired telemetry channel data, Synthetic Reports of the data processing statuses, specific report on event occurrence and report on the data processing configuration status.

 

Plan

The project team involved TAS-France and TAS-Italy with task sharing based on respective background and respective competencies. 

TAS-F Cannes managed the study and covered mainly the system aspects:

  • Return from EXperience (REX) collection, recommendations for improvements.
  • Issue Specification for Telemetry Unit.
  • Study Conclusion.

TAS-I Milan performed development and testing of Telemetry Unit :

  • TMU Preliminary and Final Design.
  • TMU EBB manufacturing, including Test Equipment.
  • TMU integration and acceptance testing.
  • TMU demonstration on ESA RASTA test bench.

 To test and validate the TMU functions an Electrical Bread Board model (TMU EBB) was developed, supporting all the TMU functionalities.

Current status

TMU VHDL code has been designed and implemented onto Electrical Bread Board (EBB) unit.

Unit acceptance has been successfully performed.

Final demonstration was held at ESTEC premises on 1st April 2014.

Contacts

ESA Contacts

Status date

Thursday, December 17, 2015 - 11:28