ESA > Join & Share > Technology Projects > ADAS-E project

ADAS-E project

Project Title		Advanced earth observation Data Acquisition System Evolution
Project Acronym		ADAS-E
Contractor(s)		Alcatel Bell Space NV, Kongsberg Spacetec AS

	Context
	Objectives
	Architecture
	Capabilities
	Output

Context

The versatility of an Earth Observation data acquisition station is highly determined by the performance characteristics of its demodulator section. The increasing diversity in the characteristics of the communication links used by advanced EO satellites require throughputs ranging from a few up to several hundreds Mbit/s, as well as the support of a wide spectrum of transmission schemes. Therefore a multi-mission demodulator is the basis to receive multiple satellite missions with the same ground station infrastructure.
A multi-mission demodulator/decoder can, thanks to the intervened technological evolution, be integrated with other functions, which could expand its capabilities into adjacent functions such as:

		Frequency conversion
		Data ingestion (with intermediate storage management)
		Front-end processing
		Modulation & coding (e.g.: for integrated equipment test)

Objectives

The principle project objective is the extension of the ADAS equipment modulation and demodulation capabilities with:


		A 4DxTCM encoder for the 8PSK modulator function. This will allow for fullfledged real-time loopback testing of the demodulator 4x8PSK TCM modulation/coding scheme up to frame synchronisation level.
		Implementation of a programmable multi-purpose digital FIR filter as an extension to modulator and demodulator signal processing functionality. This FIR filter shall support: - Bandwidth efficient modulation schemes employing Square Root Raised Cosine (SRRC) baseband pulse shaping (a discrete number of roll-off factors shall be selectable). - For the demodulator, in case of expected severe Inter Symbol Interference (ISI) due to e.g. imperfect TX filters: Combined (nonadaptive) equalisation and matched RX filtering tailored to a given distortion specification (group delay versus frequency characteristics).The proposed channel filtering and equalization architecture will allow in a future evolution, baseband pulse shaping and equalisation as required for the linear QAM approximation to GMSK.
		Study of the implementation of sub-optimal (but acceptable in terms of performance) demodulation of GMSK signals based on the linear QAM approximation to GMSK. Within the scope of this proposal, the GMSK work package shall consist of a technical requirements document and an architectural design document. These documents shall describe: - specifications of the GMSK transmitter and receiver that can be developed on the ADAS HW platform (performance degradation w.r.t. optimum theoretical receivers, minimum/maximum bit rate, selection of the bandwidth of the Gaussian filter, …) - how the GMSK functions can be implemented on the existing ADAS HW platform (definition of the extra VHDL building blocks required to do GMSK signal processing) The actual implementation, testing and demonstration of the GMSK functions on the ADAS are not part of this proposal.
		The extension of the ADAS upper data rate limit by integrating in a single acquisition equipment a multi-carrier modulation and demodulation capability for up to 4 carriers (TBC depending on heat dissipation and power consumption), allowing the reception of satellite missions such as Pleiades, ESA Sentinel program, CBERS, HY, … etc.

Architecture

The ADAS-E system is composed of several components (see diagram below).
The basic building blocks that are developed are:

		High Data Rate Demodulator (HDRD)
		High Data Rate Modulator (HDRM)
		X-Band DownConverter (XDBC)
		Data Ingest and Front End Processing (DIFEP)
		Monitoring & Control function and GUI

Based on these building blocks different equipment configurations will be possible. The ADAS Host Computer is an Industrial PC (IPC), running the Linux operating system. It has an integrated front panel TFT screen and a drawer with a keyboard and pointing device (touchpad, trackball or other). The host computer contains the processor board (SBC - Single Board Computer) and the ADAS specific boards (XBDC, HDRD, HDRM, DIFEP). Either an internal disk, or an external SCSII disk array is used for storage of acquired and processed data.

Capabilities

The ADAS-E system has the following key capabilities:

		Supports a wide range of current and planned missions
		Processes telemetry from radio frequency (X-band) to Front End Processing (FEP: production of annotated raw data, VCDU, ISP) when in full configuration
		Recovers BPSK, QPSK, SQPSK, UQPSK, AQPSK signals (evolution to 8PSK)
		Supports a maximum input bit rate of 500 Mbit/sec (QPSK. 250 Mbit/sec I and Q channels)
		Saves telemetry data to disk in real time
		Distributes telemetry data over a network
		Supports loop-back testing
		Supports quicklook display

Output

ADAS-E will provide ESA with an integrated earth observation data acquisisition system, able to Processes telemetry from radio frequency (X-band) to Front End Processing and supporting a wide range of current and future missions. The system will be validated in an ESA station using the CRYO, ALOS and ENVISAT missions.

Contributors to this page:

andreadv .

Page last modified on Tuesday 14 of December 2010 12:19:33 CET by andreadv.

Category: Technology Projects

wiki page:
- OSIRIS
- DAME Project
- ProbaV MEP
- SUCE
- OBEOS Team
- OBEOS
- IIMvLAB
- KLAUS
- UGEI Project
- UGEIP Project
- V-MANIP
- VRES Project
- VRES-I Project
- SATOPI Project
- SDD Project
- SMAAD Project
- SOSI Project
- SPA Project
- ProdTrees Project
- O3S Project
- OrthoServ Project
- Osprey Project
- OTE Project
- OTEG Project
- PALDMC Project
- PEPSI Project
- PIMS-DLR Project
- Prod-Trees Project
- ProdTree Project
- Projects Archive
- ProxSe Project
- MASS Project
- MIMS Project
- MIR Project
- MIR-E Project
- ICDY Project
- IIM-TS Project
- KEI Project
- KEO Project
- KES Project
- KES-B Project
- KIM Project
- KIMV Project
- HiProGen Project
- HiProGex Project
- DUKE Project
- EKAT Project
- EO-RCP Project
- EOLIB Project
- ADAS Project
- ADAS-E project
- CARD Project
- COISP Project
- COPS Project
- DBGS Project
- DEBAT Project
- Technology Projects
- GEAF
- ECEO-2
- ECEO
- PFA
- PRODTREES
- ESE Team
- ESE
- DRPF project
- DREAM
- EOLib
- PalDMC
- KLAUS Project
- STO Project
- ASIM Project
- RARE Project
- SMAAD
- SSEGrid
forum:
- PRODTREES

History

Search Help

Non Advanced Search or Natural Search

The documents are returned sorted on relevance depending on order, proximity, frequency of terms.

Advanced Search or Boolean Search

Default search behavior

By default, all search terms are optional. It behaves like an OR logic. Objects that contain the more terms are rated higher in the results and will appear first in their type. For example, wiki forum will find:

objects that include both terms
objects that include the term wiki
objects that include the term forum

Requiring terms

Add a plus sign ( + ) before a term to indicate that the term must appear in results. Example: +wiki forum will find objects containing at least wiki. Objects with both terms and many occurences of the terms will appear first.

Excluding terms

Add a minus sign ( - ) before a term to indicate that the term must not appear in the results. To reduce a term's value without completely excluding it, use a tilde. Example: -wiki forum will find objects that do not contain wiki but contain forum

Grouping terms

Use parenthesis ( ) to group terms into subexpressions. Example: +wiki +(forum blog) will find objects that contain wiki and forum or that contain wiki and blog in any order.

Finding phrases

Use double quotes ( " " ) around a phrase to find terms in the exact order, exactly as typed. Example: "Alex Bell" will not find Bell Alex or Alex G. Bell.

Using wildcards

Add an asterisk ( * ) after a term to find objects that include the root word. For example, run* will find:

objects that include the term run
objects that include the term runner
objects that include the term running

Reducing a term's value

Add a tilde ( ~ ) before a term to reduce its value indicate to the ranking of the results. Objects that contain the term will appear lower than other objects (unlike the minus sign which will completely exclude a term). Example: +wiki ~forum will rate an object with only wiki higher that an object with wiki and forum.

Changing relevance value

Add a less than ( < ) or greater than ( > ) sign before a term to change the term's contribution to the overall relevance value assigned to a object. Example: +wiki +(>forum < blog) will find objects that contain wiki and forum or wiki and blog in any order. wiki forum will be rated higher.