User
User
: 1 Revision: 26
CORTEX Series
EVOLUTIONS
1 20 April 16, 2012 Software upgrade e8r13 (Multi-DPU processing update) and e8r14
1 21 May 14, 2012 Software upgrade e9r0 (Support for Windows 7 Operating System and Diversity combining)
COPYRIGHT
CONTENTS
LIST OF FIGURES
FIGURE 1 : CORTEX HDR DEMODULATION AND INGESTION FUNCTIONAL BLOCK DIAGRAM ......................................... 12
FIGURE 2 : CORTEX HDR TEST MODULATOR FUNCTIONAL BLOCK DIAGRAM ............................................................... 13
FIGURE 3 : CORTEX HDR HARDWARE BLOCK DIAGRAM ................................................................................................ 14
FIGURE 4 : EXMPLE OF CORTEX HDR WORKSTATION .................................................................................................... 15
FIGURE 5 : TEST MODULATOR. FUNCTIONAL BLOCK DIAGRAM ........................................................................................ 16
FIGURE 6 : MCS SOFTWARE VERSION ............................................................................................................................... 19
FIGURE 7 : CORTEX HDR TCP-IP INTERFACES ............................................................................................................... 21
FIGURE 8 : DEMODULATOR STAGE WITH SINGLE IF INPUT ................................................................................................. 44
FIGURE 9 : DEMODULATOR STAGE WITH SEPARATE IF INPUTS ........................................................................................... 45
FIGURE 10 : CORTEX HDR I/OS WITH SINGLE IF INPUT AND OPTIONAL SCSI STORAGE.................................................. 47
FIGURE 11 : CORTEX HDR I/OS WITH SINGLE IF INPUT AND OPTIONAL LVDS / TTL INTERFACES ................................. 48
FIGURE 12 : CORTEX HDR I/OS WITH SEPARATE IF INPUTS ............................................................................................ 49
FIGURE 13 : CORTEX HDR I/OS WITH ECL OUTPUT EXTENSION ..................................................................................... 51
FIGURE 14 : SOFT DECISION CODING VS I/Q CONSTELLATION (NORMAL SOFT OUTPUT) .................................................. 63
FIGURE 15 : SOFT DECISION CODING VS I/Q CONSTELLATION (MERGE SOFT OUTPUT) .................................................... 64
FIGURE 16 : EFFECT OF THE DEAF. ................................................................................................................................... 78
FIGURE 17 : EFFECT OF THE XDEAF. ................................................................................................................................ 81
FIGURE 18 : VITERBI DECODING MODULE. SINGLE & DUAL OPERATING MODES ............................................................. 84
FIGURE 19 : PARALLEL VITERBI DECODING MODULE. ...................................................................................................... 85
FIGURE 20 : VITERBI DE-PUNCTURING PROCESS................................................................................................................ 86
FIGURE 21 : PUNCTURED VITERBI BER PERFORMANCES. .................................................................................................. 88
FIGURE 22 : STRUCTURE OF THE 4D 8PSK-TCM CODER/MAPPER .................................................................................... 94
FIGURE 23 : DIFFERENTIAL CODER AND MODULO-8 ADDER PRINCIPLE ............................................................................ 95
FIGURE 24 : CONVOLUTIONAL CODER RECOMMENDED FOR HIGH DATA RATES ............................................................... 96
FIGURE 25: CONSTELLATION MAPPER FOR 2 BITS/CHANNEL-SYMBOL ............................................................................... 97
FIGURE 26 : CONSTELLATION MAPPER FOR 2.25 BITS/CHANNEL-SYMBOL ......................................................................... 97
FIGURE 27 : CONSTELLATION MAPPER FOR 2.5 BITS/CHANNEL-SYMBOL ............................................................................ 98
FIGURE 28 : CONSTELLATION MAPPER FOR 2.75 BITS/CHANNEL-SYMBOL ......................................................................... 99
FIGURE 29: CODER AND MAPPER IMPLEMENTATION AT 2 BITS/CHANNEL-SYMBOL EFFICIENCY ....................................... 99
FIGURE 30 : CODER AND MAPPER IMPLEMENTATION AT 2.25 BITS/CHANNEL-SYMBOL EFFICIENCY................................ 100
FIGURE 31: CODER AND MAPPER IMPLEMENTATION AT 2.5 BITS/CHANNEL-SYMBOL EFFICIENCY .................................. 100
FIGURE 32 : CODER AND MAPPER IMPLEMENTATION AT 2.75 BITS/CHANNEL-SYMBOL EFFICIENCY................................ 100
FIGURE 33 : CONCATENATION PRINCIPLE ........................................................................................................................ 101
FIGURE 34 : RANDOMIZATION PRINCIPLE ........................................................................................................................ 102
FIGURE 35 : DATA ARRANGEMENT IN TCM 2.5 BITS/CHANNEL_SYMBOL ....................................................................... 104
FIGURE 36 : BER MEASUREMENT METHODS : TESTED AMBIGUITIES AND GUI DISPLAY ................................................ 106
FIGURE 37 : DATA PROCESSING UNIT BLOCK DIAGRAM ................................................................................................. 116
FIGURE 38 : FRAME SYNCHRONIZATION PROCESS ........................................................................................................... 118
FIGURE 39 : DATA TRANSMISSION OVER TCP-IP. MESSAGE FORMATTING ..................................................................... 131
FIGURE 40 : RECORDED DATA FILE STRUCTURE ............................................................................................................. 133
FIGURE 41 : CCSDS FTP MODE STORAGE DIRECTORIES ................................................................................................ 135
FIGURE 42 : PLAYBACK FUNCTION : TEST MODULATOR OPERATING MODE ..................................................................... 138
FIGURE 43 : PLAYBACK FUNCTION : TEST MODULATOR DATA + CLOCK MODE ............................................................... 138
FIGURE 44 : QPSK DEMODULATION WITH 2 DPU ............................................................................................................ 141
FIGURE 45 : QPSK OR 16QAM DEMODULATION WITH 4 DPU......................................................................................... 142
FIGURE 46 : 16QAM DEMODULATION WITH 8 DPU......................................................................................................... 143
FIGURE 47 : QPSK OR 16QAM DEMODULATION WITH 1 DPU......................................................................................... 144
FIGURE 48 : QPSK DEMODULATION WITH 2 DPU ............................................................................................................ 144
FIGURE 49 : 8 DPU DATA FLOW FOR AUTOMATIC AMBIGUITY RESOLUTION ................................................................... 145
FIGURE 50 : PROBABILITY OF BIT ERROR VS EB/NO FOR DIFFERENT PCM CODES ......................................................... 170
FIGURE 51 : PROBABILITY OF BIT ERROR VS EB/NO WITH CONVOLUTIONAL CODING (RATE: 1/2) .................................. 171
FIGURE 52 : PROBABILITY OF BIT ERROR VS EB/NO WITH REED-SOLOMON CODING ...................................................... 171
FIGURE 53 : PROBABILITY OF BIT ERROR VS EB/NO IN 8PSK MODE WITH OR AT 2,5 BIT/SYMBOL.................................. 172
FIGURE 54: PROBABILITY OF BIT ERROR VS EB/NO WITH GMSK ................................................................................... 173
FIGURE 55: PROBABILITY OF BIT ERROR VS EB/NO WITH 16QAM AND RS DECODING (800 MBPS) ............................... 174
FIGURE 56 : EXAMPLE OF NON-LINEARITY IN A RG188A/U CABLE ................................................................................ 178
FIGURE 57 : EXAMPLE OF COMPENSATION - SYMBOL RATE = 150 MBPS......................................................................... 179
FIGURE 58 : SPS START SEQUENCE ................................................................................................................................. 185
FIGURE 59: CTX DOCUMENT MANAGEMENT .................................................................................................................. 187
FIGURE 60 : MCS MENU MANAGEMENT WINDOW .......................................................................................................... 188
FIGURE 61 : ABOUT CORTEX SPS VERSION .................................................................................................................. 190
FIGURE 62 : MCS START SEQUENCE................................................................................................................................ 200
FIGURE 63 : MCS TOP-LEVEL WINDOW .......................................................................................................................... 203
FIGURE 64 : MCS LOGIN WINDOW .................................................................................................................................. 203
FIGURE 65 : MULTIPLE TABBED DOCUMENT INTERFACE ................................................................................................. 204
FIGURE 66 : CORTEX MCS ABOUT : SOFTWARE VERSION ............................................................................................... 213
FIGURE 67 : CHANGING A PASSWORD .............................................................................................................................. 214
FIGURE 68 : GRAPHICAL USER INTERFACE: WINDOWS BREAKDOWN .............................................................................. 224
FIGURE 69 : CORTEX HDR : GLOBAL WINDOW............................................................................................................ 225
FIGURE 70 : GLOBAL ENGINEERING WINDOW ................................................................................................................. 228
FIGURE 71 : TCP-IP SECONDARY WINDOW ..................................................................................................................... 229
FIGURE 72 : CORTEXXL « TIME » WINDOW ................................................................................................................... 230
FIGURE 73 : LEAP SECOND MANAGEMENT ...................................................................................................................... 233
FIGURE 74 : CORTEX HDR : CONFIG. WINDOW............................................................................................................. 236
FIGURE 75 : CORTEX HDR : CONFIG. WINDOW WITH EXTENSION BOARD .................................................................... 237
FIGURE 76 : CONFIGURATION HELP WINDOW FOR THE DEMODULATOR .......................................................................... 239
FIGURE 77 : CONFIGURATION HELP WINDOW FOR THE TEST MODULATOR ...................................................................... 239
FIGURE 78 : CORTEX HDR : PROJECT WINDOW ............................................................................................................ 241
FIGURE 79 : CORTEX HDR : INFORMATION WINDOW ................................................................................................... 242
FIGURE 80 : DEMODULATOR : GLOBAL WINDOW FOR QPSK MODULATION + I & D FILTER ........................................... 243
FIGURE 81 : DEMODULATOR : GLOBAL WINDOW FOR QPSK MODULATION + RAISED COSINE FILTER ........................... 243
FIGURE 82 : DEMODULATOR : GLOBAL WINDOW FOR QPSK MODULATION + CUSTOM FILTER ...................................... 244
FIGURE 83 : DEMODULATOR : GLOBAL WINDOW FOR OQPSK MODULATION................................................................. 244
FIGURE 84 : DEMODULATOR : GLOBAL WINDOW FOR GMSK MODULATION .................................................................. 245
FIGURE 85 : DEMODULATOR : GLOBAL WINDOW FOR SOQPSK MODULATION .............................................................. 245
FIGURE 86 : DEMODULATOR : GLOBAL WINDOW FOR UQPSK MODULATION................................................................. 246
FIGURE 87 : DEMODULATOR: GLOBAL WINDOW FOR 8PSK MODULATION ..................................................................... 246
FIGURE 88 : DEMODULATOR: GLOBAL WINDOW FOR 16QAM MODULATION ................................................................. 247
FIGURE 89 : DEMODULATOR: GLOBAL WINDOW FOR 16APSK MODULATION ................................................................ 247
FIGURE 90 : DEMODULATOR: GLOBAL WINDOW FOR 32APSK MODULATION ................................................................ 248
FIGURE 91 : DEMODULATOR: GLOBAL WINDOW FOR 64APSK MODULATION ................................................................ 248
FIGURE 92 : DEMODULATOR: GLOBAL WINDOW FOR VCM QPSK / 8PSK ..................................................................... 249
FIGURE 93 : DEMODULATOR: GLOBAL WINDOW FOR DVB-S2 /SCC .............................................................................. 249
FIGURE 94 : DEMODULATOR: GLOBAL WINDOW FOR MULTI-DPU OPERATION .............................................................. 250
FIGURE 95: DEMODULATOR : PHYSICAL LAYER WINDOW FOR SCCC AND DVB-S2 STANDARD...................................... 260
FIGURE 96: DEMODULATOR : BER WINDOW PRN MODE ................................................................................................ 263
FIGURE 97: DEMODULATOR : BER WINDOW FILE MODE ................................................................................................. 263
FIGURE 98 : DEMODULATOR : DECODING WINDOW FOR BPSK MODULATION ................................................................ 266
FIGURE 99 : DEMODULATOR : DECODING WINDOW FOR QPSK & OQPSK MODULATION (VITERBI SINGLE) ................. 266
FIGURE 100 : DEMODULATOR : DECODING WINDOW FOR QPSK & OQPSK MODULATION (VITERBI DUAL) ................. 267
FIGURE 101 : DEMODULATOR : DECODING WINDOW FOR UQPSK MODULATION ........................................................... 267
FIGURE 102 : DEMODULATOR : DECODING WINDOW FOR 8PSK MODULATION ............................................................... 268
FIGURE 103 : DEMODULATOR : SPECTRUM WINDOW....................................................................................................... 272
FIGURE 104 : DEMODULATOR : BPSK VECTOR WINDOW ................................................................................................ 274
FIGURE 105 : DEMODULATOR : QPSK(OQPSK) VECTOR WINDOW ................................................................................ 274
FIGURE 106 : DEMODULATOR : 8PSK VECTOR WINDOW ................................................................................................ 275
FIGURE 107 : DEMODULATOR : 16QAM VECTOR WINDOW ............................................................................................ 275
FIGURE 108 : DEMODULATOR : 16APSK VECTOR WINDOW............................................................................................ 276
FIGURE 109 : DEMODULATOR : 32APSK VECTOR WINDOW............................................................................................ 276
FIGURE 110 : FILTER: TIME DISPLAY SELECTION ............................................................................................................ 278
FIGURE 111 : FILTER: FREQUENCY DISPLAY SELECTION ................................................................................................. 278
SYMBOLS:
% Percent
Plus or minus
Greater than or equal
Less than or equal
And
Approximately
PREFIXES:
n Nano-
Micro-
m Milli-
k Kilo-
M Mega-
G Giga-
T Tera-
UNITS:
A Ampere
b Byte
bps Bit per second
C Celsius
dB Decibel
F Farad
Hz Hertz
mm Millimeter
rpm revolutions per minute
Ohms
s Second
sps Symbol per second
s/s Sample per second (ks/s, Ms/s,...)
V Volt
ABBREVIATIONS:
AD Applicable Document
AGC Automatic Gain Control
AIT Assembly Integration and Test
APSK Amplitude and Phase Shift Keying
AQPSK Asynchronous Quadrature Phase Shift Keying
ASB Anti Side Band
ASCII American Standard Code for Information Interchange
BR Bit Rate
BER Bit Error Rate
BEM Bandwidth Efficient Modulation
BP-L Bi-Phase-L
BP-M Bi-Phase-M
BP-S Bi-Phase-S
BPSK Binary Phase Shift Keying
BW Band Width
CADU Channel Access Data Unit
CCITT Consultative Committee on International Telegraphy and Telephony
CFDP CCSDS File Delivery Protocol
CCSDS Consultative Committee for Space Data Systems
CLK Clock
CMA Constant Modulus Algorithm
CPU Central Processing Unit
DAS Direct Attachment Storage
dBc dB with respect to the un-modulated carrier
DC Direct Current
DEAF Digital Equalization Automatic Filter
DEM / DMU Demodulation Unit
DNRZ Differential Non Return to Zero (NRZ-L with differential encoding in QPSK modulation)
DPU Data Processing Unit
DRG Data Recording Global
DRU Data Recording Unit
DSP Digital Signal Processor
DVB Digital Video Broadcasting (DVB-S / DVB-S2 standards)
D/C frequency Down Converter
ECL Emitter Coupled Logic
PC Personal Computer
PLL Phase Locked Loop
PM Phase Modulation
pp Peak to peak
PS Power Supply
PSK Phase Shift Keying
QPSK Quadrature Phase Shift Keying
RAID Redundant Array of Independent Disks
RF Radio Frequency
RMS Root Mean Square
RRC Root Raised Cosine
R-S (RS) Reed-Solomon
SAN Storage Array Network
SNUG (NASA) Space Network User’s Guide
SCSI Small Computer System Interface
SOQPSK Shaped Offset Quadrature Phase Shift Keying
SPS Signal Processing Software
SR Symbol Rate
SQPSK Staggered Quadrature Phase Shift Keying
TBC To Be Confirmed
TBD To Be Defined
TCM Trellis Coded Modulation
TCP/IP Transport Control Protocol / Internet Protocol
TM TeleMetry
UQPSK Unbalanced Quadrature Phase Shift Keying
UTC Universal Time, Coordinated
U/C frequency Up Converter
VC Virtual Channel
VCDU Virtual channel Data Unit
VCID Virtual Channel Identifier
VCM Variable Coding Modulation
VSWR Voltage Standing Wave Ratio
WAN Wide Area Network
ZDS Zodiac Data Systems
16QAM 16 states Quadrature Amplitude Modulation
CAUTION
CAUTION
RISK OF ELECTRICAL SHOCK
DO NOT OPEN
!
CAUTION : TO REDUCE THE RISK OF ELECTRIC SHOCK,
DO NOT REMOVE COVER (OR BACK).
REFER SERVICING TO QUALIFIED PERSONNEL.
LEGEND
The exclamation point within an equilateral triangle is intended to alert the user
to the presence of important operating and maintenance (servicing) instructions
in the literature accompanying the product.
This product is designed and manufactured to meet strict quality and safety standards (conformity to “EN
60950:2002 standard: Safety of information technology equipment.
However, you should be aware of the following installation and operation precautions:
You should read all the safety and operating instructions before operating this apparatus.
Retain this handbook for future reference and adhere to all warnings in the handbook or on the
apparatus
To reduce the risk of fire or electric shock, do not expose this apparatus to rain or moisture.
The presence of electricity near water can be dangerous. Do not use the apparatus near water.
Take care that objects do not fall and liquids are not spilled into the product chassis through
any openings.
Installation
This unit must should be used in a 19” rack mount cabinet only
Cleaning
To reduce the risk of electric shock, do not remove cover (or back).
No user serviceable parts inside ; the product chassis should only be opened by
qualified personnel for maintenance purpose ( except for opposite instructions in the
user’s manual ).
Technical Maintenance
Refer all servicing to qualified maintenance personnel. Servicing is required when apparatus
has been damaged in any way, such as power supply cord is damaged, liquid has been spilled
or objects have fallen into the apparatus, the apparatus has been exposed to rain or moisture,
does not operate normally, or has been dropped.
The qualified maintenance personnel must take reasonable precautions to face the
obvious DANGERS.
Powers sources
Only connect the apparatus to a power supply of the described in the operating instructions or
as marked on the apparatus.
Turning off the power switch does not completely isolate this product from the power line so
remove the plug from the socket if not using it for extended period of time.
Power supply cords should be routed so that they are not likely to be walked on or pinched by
items placed upon or against them, paying particular attention to cords and plugs, and the
point where they exit from the appliance
Grounding
This apparatus must be used with a power supply cable of 1 mm2 section minimum
The power supply socket must be located at a distance of less than 1.5 m from the
equipment
If this apparatus weighs over 25kgs, so take extreme care when lifting or moving this
unit. We recommend that two people are available to lift this unit.
CE MARKING
Markings are placed at the rear of the unit, regarding the power ratings and compliance.
The symbol on the PC chassis indicates that it is in compliance with the Electromagnetic
Compatibility directive (2006/95/EC) and the low Voltage directive (IEC60950-1/A1:200973/23/CEE) . A
certificate of compliance is available by contacting technical support. This equipment is a:
Group 1 Class A product
Recommendation concerning the cabling :
CE certification has been carried out with 3-meter interconnecting cables with remote equipment.
ZODIAC DATA SYSTEMS recommends the use of high quality interconnecting cables type. The high
quality recommended user interconnecting cables are “shield twisted pair” or “coaxial cable” industrial type
with cable shield. The cable shield will provide the necessary mechanical protection.
Not using this high quality designed cable could result in unexpected intersystem/extrasystem
electromagnetic emission and susceptibility.
1. CORTEX HDR
OVERVIEW
1.1 SCOPE
This manual contains the information necessary to install, configure, operate and maintain the ZDS PC-based
High Data Rate Receiver XXL (CORTEX HDR XXL).
Project-specific information (if any) and additional data on the CORTEX HDR are annexed to the document :
Annexes 2 & 3 : Layout of the Test Modulator board and Demodulator board.
Annex 5 : Hardware and software configuration of the CORTEX HDR at delivery. Project-specific data if any.
Digital filtering : RRC, GMSK, SOQPSK, User defined, Equalizer, static or auto-adaptive mode
(DEAF)
Viterbi decoding : CCSDS, single or dual mode, ½ (+ puncture) or ¼ rate, single or parallel
processing
Low Density Parity Check Code decoding (CCSDS LDPC 7/8, 2/3 and 1/2 )
Data ingestion : data storage with programmable filtering and sorting for further transmission to
remote clients or/and real-time data transmission to remote Clients
Extensive Use of Digital Signal Processing Techniques for Enhanced Performance, Upgradability
and Flexibility
PC-based Architecture
The Cortex HDR is part of the Cortex family products, all using the same architecture: a board with FPGA chips
plugged into the 4U-high Cortex chassis (equipped with Intel Server Board).
Telemetry demodulation,
Telemetry processing,
The first generation of demodulator board provides a single 720 MHz IF input. The second generation provides
two independent 720 MHz IF inputs and one independent 1.2 GHz IF input. Each input is dubbed with an alternate
connector.
Depending on the delivered hardware configuration (first or second generation of demodulator board), the
delivered operational configuration (licenses dependent) and the selected start-up menu, the HDR can be
operated in one of the following four operating modes:
The 4 modes are supported by the second generation of demodulator board. Only modes 1 and 2 are supported
by the first generation.
Performances and particularly the supported maximum bit rates are dependent on the operating mode.
Depending on the delivered configuration (licenses dependent) and the selected start-up menu, one or two data
processing units can be connected at the output of two parallel demodulator units, or up to heigh processing units
can be connected at the output of one demodulator unit.
or
1.2 GHz nominal, tunable between 910 MHz and 1490 MHz
BPSK, QPSK, OQPSK (SQPSK), UQPSK (AQPSK, AUQPSK, AUSQPSK), 8PSK, GMSK, SOQPSK, 16QAM,
16APSK, 32APSK, 64APSK demodulation
Bit synchronization
Fully digital matched and shaped filters: Raised Cosine, Root Raised Cosine, GMSK, SOQPSK shaping filter
(CCSDS and IRIG standard), User defined
Viterbi decoding : single or dual mode, ½ (+ puncture) or ¼ rate, single or parallel processing (stacked Viterbi)
De-randomization, De-interleaving, Virtual filling, Reed-Solomon decoding (supported standard: CCSDS, DVB-
S, ECSS)
CCSDS Low Density Parity Check decoding (LDPC 7/8, 2/3 and 1/2)
Programmable data filtering and sorting with dynamical creation of directories and files for recovery by remote
clients using FTP
Data files
Data interface :
Standard PCM outputs (differential Data plus Clock outputs): multi format provided:
- output of the demodulator unit (DMU) or output of the data processing unit (DPU)
- possibility of Soft Decision at the output of the demodulator(separate I and Q 3 bits or merged
I/Q 6 bits)
CFDP protocol
Telemetry simulation
Noise generation.
IF Modulation.
Doppler simulation
Digital Outputs
Data + Clock
BER Measurement
Vector Analysis
Spectrum Analysis
(Free Copyright)
Noise Generation
IF Output
A PC-compatible workstation,
An optional Test Modulator board, including a noise generator and a telemetry simulator (ZDS).
PC-compatible Workstation
1G Base T
ETHERNET PORT
PCI BUS
A CD drive.
PCM generation : internal data (pseudo-random or pattern from files) or external data (+ associated clock).
PCM encoding
Randomization
CCSDS RS,
LDPC.
Convolutional encoding.
BPSK, QPSK, OQPSK, UQPSK, (TCM) 8PSK, 16QAM, 16APSK, 32 APSK, 64 APSK
Doppler simulation
Carrier ON/OFF
External OL Carrier Generation
External I & Q
Data + Clock Modulation ON/OFF Vector Modulation
PCM & Viterbi BPSK/QPSK
Encoding OQPSK/UQPSK
Internal PCM 8PSK
Generation
PRN or File
Output Level
Setting
Level Setting
Noise ON/OFF
Noise Source
-93 to –132 dBm/Hz +
IF Output
Bit synchronization.
PCM decoding
Frame synchronization
Time tagging
De-randomization, RS or LDPC decoding
BER measurement.
Vector analysis.
The Demodulator board is monitored and controlled by the Pentium CPU board via the PCI bus.
These software are executed under the control of the Operating System. Software configuration at delivery is
described in Annex 5.
PROMed software (Demodulator and Test Modulator boards) : see the factory acceptance test results
(CRE100135).
Signal Processing Software (FPGA & DSP software downloaded to the Demodulator board at boot-up) :
open the CONFIG window (see Section 4.5.3.2 for more details).
Signal Processing Software (Pentium software) : click on at the bottom of the screen. Then select
About Cortex... to display the software version.
Monitoring & Control Software : click on or on Help in the top-level window, then select About
CrtxMcs... :
Some data flows accept multiple clients at a time (monitoring, logging, spectrum analysis, vector analysis data),
while other flows accept only one client at a time (equipment configuration and reset).
Each type of transfer flow is allocated a specific port number which the clients use for connecting to the
equipment. Port numbers are listed below :
MAXIMUM NUMBER OF
DATA FLOW PORT NUMBER
CONNECTIONS
Next figure shows data flows between CORTEX HDR software components and between the CORTEX HDR and
the outside world :
Single-client Connections
M&C SOFTWARE
Multi-client Connections
CLIENTS
SIGNAL PROCESSING
SOFTWARE
Spectrum Analysis Data (SPA)
3050
3001
In order to recover the constructed data files through the network by external Clients, the CORTEX HDR is fitted
with a powerful FTP server. External Clients can connect this server at the standard dedicated FTP port number.
PERFORMANCE DATA IN THIS SECTION ARE TYPICAL VALUES MEASURED IN BEST CASE CONDITIONS.
32-BIT INTEGERS OR SINGLE-PRECISION FLOAT (8-BIT EXPONENT AND TWO’s COMPLEMENT 24-BIT
MANTISSA). HOWEVER, RESOLUTION CAN BE LIMITED BY THE HARDWARE DESIGN. LIMITATIONS ARE
Input frequency 720 MHz 190 MHz or 1.2 GHz 290 MHz (hardware dependent)
Input impedance 50
AGC test 0 Volt (IF level -60 dBm) to 3 Volts (IF level -10 dBm)
Minimum termination : 1000
1.6.1.2 Demodulation
Demodulation (notes 1) BSPK , QPSK , OQPSK (SQPSK)
SOQPSK (MIL standard filter, IRIG TG filter, CCSDS A-type or B-type filters)
Bit rates (notes 1, 2 & 3)
Operating mode 1 (mono demodulator @ 720 MHz IF input)::
Maximum Bit rate in QPSK modes per channel 480 Mbps (600 Mbps
without any decoder)
Cable Equalizer (note 1) Yes. Amplitude equalization : 0 to 12 dB between 570 & 870 MHz
Accuracy : 1 dB
1.6.1.4 Filtering
(notes 1)
Raised Cosine
Additional filters Rejection filter HBF (sampling rate at 4 time the symbol rate with decimation by 2
at the output)
Auto-adaptability Static or Auto-adaptive: “Digital Equalization Automatic Filter”, with learn and
save mode.
G2 – G1
Maximum (encoded) bit rate In single Viterbi mode : up to 240 Mbps or 1160 Mbps with the high rate
menus
In dual Viterbi mode : up to 480 Mbps or 1160 Mbps with the high rate
menus (for Viterbi ½. else puncturing rate dependent).
In parallel processing mode (> 4xI / 4xQ) : > 600 Mbps
Decoder status Locked/unlocked. Symbol error rate (obtained by comparing the input
data to the re-encoded decoded data).
1.6.1.5.2 VITERBI ¼
Application example : ERS-2 low bit rate satellite.
1.6.1.6 De-scrambler
The cortex HDR supports several types of auto-synchronized de-scrambler (before frame synchronisation):
The Transport layer is implemented between the demodulator output and the input of the CADU frame
synchronizer (CCSDS Transfer Frame layer).
The Transport layer acts as a first specific frame synchronizer. The parameters of this synchronizer can be set in
Windows Registries (refer to the paragraph “Cortex HDR System Parameters in Registry”).
The following figure gives an example of the transport layer used with LDPC.
8PSK - 4D TCM trellis : output rate 2.0, 2.5 or 2.75 bits/symbol (rate 2.25 is available on request)
Transport layer status : lock/unlock, number of R-S correction, idle frames counter, corrected R-S CADU
counter (good/bad CADU), dropout events.
DVB-S2 standard : ETSI EN 302 307 V1.1.2, Digital Video Broadcasting, second generation framing
structure, channel coding and modulation systems for Broadcasting, Interactive Services, New Gathering
and other Broad band satellite applications.
CCSDS SCCC standard : CCSDS 131.2-R-1, Flexible advanced coding and modulation scheme for high
rate telemetry applications.
It has to be noted that the input symbol rate is constant. The demodulator of the HDR recognizes the current
modulation mode and switch automatically in the corresponding configuration (demodulation mode and differential
decoding).
Whatever the current modulation can be at a given time, the demoduated data are output on the same two parallel
ECL ports (Output mode = Split 2). The output clock rate is adjusted consequently.
This variable modulation mode is supported with the demodulator menu number 11.
- Combining of the two channels, through optimal weighting. In this case up to 3 dB gain can be
achieved when both signals have the same Eb/No.
The combining system, also named Diversity Combining Unit (DCU), receives the data from two demodulators. It
resolves phase ambiguity between both channels, and deals with the different locking states possible. Its output
feeds a FEC device, followed by a Format Output.
Default time-tag format 64 bits (second of the year + s of the current second)
Virtual filling
- LDPC 7/8 (mono mode after I/Q merged or dual mode on separate I and Q outputs)
The LDPC decoding is an iterative process with parity decoding. In this implementation, after the last iteration, the
parity control is processed one more time. This control is able to detect bit error before and after decoding, and
elaborates a quality “Good/Bad” status of the decoding CADU.
Bit rates supported by the LDPC decoderd depends on the rate of the decoder (7/8, ½ or 2/3) and on the use or
not of the Demodulator Extension board (hardware option). The Following table gives the maiximum bit rates.
The performance of the LDPC depends on the number of iterations, the following table gives as example the
obtained performances in terms of BER for BPSK and QPSK modulations: BER versus Eb/N0 performance @
BER = 10-6, with LDPC 7/8 (HDR XXL without the Extension Board).
LDPC coding can be used with or without the Transport layer (refer to the paragraph: Transport Layer).
TCP-IP
Associated Hardware:
Internal storage Internal hard disks
External Recorder (note 1) External Direct Attachment Storage (DAS) system (DR2912 or ER2912)
Up to 12 Tbyte (note 2)
RAID 5
Read/Write Performance:
Input data rate Up to 2 Gbps aggregate
Stored data Raw data or frames (CADU) or virtual channels (VCDU) or Packet or
files set (CFDP)
CADU frame
Read Data Rate Bandwidth Up to 600 Mbps (with 1 Gbyte Ethernet interface)
Up to 64 destination files
1.6.5 Playback
Operating Modes: Test Modulator mode: replay at IF level using the Test Modulator
board
User files
IF output port 1
Unwanted emissions Better than -40 dBc @ -10 dBm output level
1.6.6.3 Modulation
Modulation BSPK , QPSK , OQPSK (SQPSK)
TCM
CCSDS Reed-Solomon
DVB Reed-Solomon
LDPC 7/8
Data : NRZ-L
Clock phase : 0°
Impedance 50
DC max. = 4 V
Input port 1
Impedance 100 k
Depth : 550 mm
Weight 25 kg
1.6.11 Supply
Supply (last generation) 90 - 264 VAC
47 – 63 Hz
2. HARDWARE
DESCRIPTION
Depending on the delivered configuration, optional hardware parts can be added to the unit and consist in:
- second generation demodulator board with 2 x 720 MHz plus 1.2 GHz IF inputs
The main operational difference between the first and second generations of demodulator boards is detailed in the
paragraph 2.1.3.
The following table lists the HDR XXL available models and their reference number depending on the different
selected options:
The position of the boards inside the chassis must not be changed. A sticker at the rear panel of the equipment
shows how the boards must be mounted in the chassis. Do not change this setting.
The first generation of demodulator board provides a single 720 MHz IF input.
The second generation provides two independent 720 MHz IF inputs and one independent 1.2 GHz IF input. This
last board is configured in factory and delivered with 2 x 720 MHz IF inputs or 2 x 720 MHz plus 1 x 1.2 GHz IF
inputs.
The I/O mezzanine in its standard version provides only the ECL I/O. In option the mezzanine provides ECL plus
LVDS I/O.
Demodulator A
Nom. A
Analogue D
720 MHz
C
input
Alter.
Demodulator B
The incoming 720 MHz IF signal is distributed in parallel towards both digital demodulators after analogue filtering,
amplification and digital conversion.
Nom. IF 1
Analogue
1.2 GHz input
Ater. IF 1
2
A
D Demodulator A
C
1
Nom. IF 2
Analogue
720 MHz
Ater. IF 2 input
2
Nom. IF 3
A
Analogue
D Demodulator B
720 MHz
Ater. IF 3 input 1 C
1. D
The demodulator board provides double 720 MHz IF inputs (configuration 1) or single 1.2 GHz IF input
(configuration 2). Both configurations are exclusive. The selection between configurations is done by basic menu
selection.
EM
With configuration 1 (720 MHz inputs) both demodulators A and B are available. The 1.2 GHz IF inputs 1 are not
used, the 720 MHz IF inputs 2 and 3 (nominal and alternate) are available and can be selected from the GUI.
With configuration 2 the demodulator B is not available. Only the IF input 1 (nominal and alternate) is used.
OD
UL
ZODIAC DATA SYSTEMS PROPRIETARY
AT Page 45
HIGH DATA RATE RECEIVER HDR-XXL ZDS Ref : DTU 100355 Issue : 1 Rev.: 26
CORTEX SERIES - USER’s MANUAL Customer Ref : Date : June 28, 2013
The first generation board generates a 720 MHz IF frequency programmable within a few MHz range. The ZDS
reference of the board is : SM 01008857.
The second generation board generates a 720 MHz IF frequency or a 1.2 GHz IF frequency programmable within
a larger range (720 MHz ± 140 MHz and 1.2 GHz ± 50 MHz). The ZDS reference of the board is : SM 01019647.
This board is a PCI board fitted with a set of high performance FPGA. It is connected with the demodulator board.
H/B
H/B
J26 J16 J66 J56
HW CLK I-
OUT3+ OUT3+ IN3+
FAIL
1.1.1.1.1.1.1.1.3
STORAGE
1.1.1.1.1.1.1.1.1 C 1.1.1.1.1.1.1.1.2
HA
NN
EL
A
Figure 10 : CORTEX HDR I/Os with single IF input and optional SCSI storage
2.2.2.2 HDR I/Os with single IF input and optional LVDS / TTL interfaces
H/B
J71
LVDS
DEMOD
J23 J13 OUT B J3 J63 J53
OUT1- OUT1- AGC OUT IN1- IN1 +
1.1.1.1.1.1.1.1.7 D
J24 J14
J72
LVDS
E J4 J64 J54
IRIG IN IN1 -
OUT2+ OUT2+ DEMOD
IN M IN2+
O
J25
OUT2-
J15
OUT2-
D J5
10MHz IN
J65
IN2-
J55
CLK I+
OUT B
H/B
1.1.1.1.1.1.1.1.6
1.1.1.1.1.1.1.1.4 C IN
HA PU
NN T
EL 1.1.1.1.1.1.1.1.5
A
Figure 11 : CORTEX HDR I/Os with single IF input and optional LVDS / TTL interfaces
J20 J21 J22 J23 J24 J25 J26 J27 J10 J1 J50
CLK+ NOM IF1 IF OUT
J80 ALT-IF1
H/B
J60 J61 J62 J63 J64 J65 J66 J67 J12 J3 J52
OUT1+ NOM IF3 CLK OUT+
J82 ALT-IF3
CLK IN+ CLK IN- IN1+ IN1- IN2+ IN2- IN3+ IN3- J53
J13 J4
OUT1- AGC OUT IN1 +
DEMODULATOR INPUT INPUT IF
J14 J5 J54
OUT2+ IRIG IN IN1 -
J15 J6 J55
OUT2- 10MHz IN CLK I+
H/B
J16 J56
HW CLK I-
OUT3+
FAIL
J17 J57
OUT3- 10 MHz IN
1.1.1.1.1.1.1.1.
1.1.1.1.1.1.1.1.8 C
HA
NN
EL
A
2.2.2.4 HDR I/Os with separate IF inputs and optional optical fibre interface for
RAID-5 ER2912 storage device
2.2.2.5 HDR I/Os Demodulator with separate IF inputs and outputs extension
+ -
IN2 + J64 Data input V > -1 Volt, V < -1.7 Volt
IN2 - J65 for BER measurement or
data post-processing 50 termination required (note 2)
_ _
R = Z0
External 50 termination :
Unbalanced ECL :
+
50
-VT
_
50
-VT
Note 3 : Only available with the demodulator with Output Extension option
DATA STORAGE DATA I/O J40 Data for storage on Ultra 320 SCSI LVD
external Hard Disk
68 pin LVD SCSI connector
LVDS & TTL I/Os LVDS DEMOD J70 Data and clock outputs
LVDS standard characteristics
OUT A for demodulator A
LVDS Interface:
SH2
GND
CHA_OUT1 + 1
CHA_OUT1 – 2
CHA_OUT2 + 3
CHA_OUT2 –
DEMOD OUT A
4
CHA_OUT3 + 5
CHA_OUT3 - 6
CHA_CLK + 7
CHA_CLK – 8
SH1
GND
J70
SH2
GND
CHB_OUT1 + 1
CHB_OUT1 – 2
CHB_OUT2 + 3
CHB_OUT2 –
CHB_OUT3 +
4
5 DEMOD OUT B
CHB_OUT3 - 6
CHB_CLK + 7
CHB_CLK – 8
SH1
GND
J71
SH2
GND
CHA_IN1 + 1
CHA_IN1 – 2
CHA_IN2 + 3
CHA_IN2 –
DEMOD IN
4
CHA_IN3 + 5
CHA_IN3 - 6
CHA_CLK + 7
CHA_CLK – 8
SH1
GND
J72
The output level is adjusted around the typical 1.2 V offset, with a peak-to-peak amplitude varying from 250 mV to
450 mV.
CLKA_OUT 6
GROUND 1 11 CHA_OUT1
CHA_OUT2 7
CHA_OUT3 2 12 CHB_OUT1
CHB_OUT2 8
CHB_OUT3 3 13 CLKB_OUT
GROUND 9
DATA_IN2 4 14 DATA_IN1
DATA_IN3 10
GROUND 5 15 CLK_IN
J73
The following table shows the different configurations for both Demodulator A and Demodulator B (standard
outputs).
* BPSK demodulation can be set to SPLIT2 mode with high rates hardware menus (single demodulator). In this case
the data stream is split on the two outputs J12/ J13 and J22/J23.
The following table shows the available configurations with the demodulator hardawre menu 16
(multi-DPU process) and with the demodulator fitted with the Output Extension option.
J10 / J11 Clock @ output of DPU A Clock @ output of DPU A Clock @ BR / 4 Clock @ BR / 8
CLK +
CLK -
J12 / J13
OUT1 + Data of DPU A Data of DPU A Data I 1 Data I 1
OUT1 -
J14 / J15
OUT2 + Data of DPU C Data of DPU C Data Q 1 Data I 2
OUT2 -
J16 / J17 Clock @ output of DPU C Clock @ output of DPU C Clock @ BR / 4 Clock @ BR / 8
OUT3 +
OUT3 -
J20 / J21 Clock @ output of DPU E Clock @ output of DPU E Clock @ BR / 4 Clock @ BR / 8
CLK +
CLK -
J22 / J23
OUT1 + Data of DPU E Data of DPU E Data I 2 Data I 3
OUT1 -
J24 / J25
OUT2 + Data of DPU G Data of DPU G Data Q 2 Data I 4
OUT2 -
J26 / J27 Clock @ output of DPU G Clock @ output of DPU G Clock @ BR / 4 Clock @ BR / 8
OUT3 +
OUT3 -
J30 / J31 Reserved Clock @ output of DPU B Reserved Clock @ BR / 8
CLK +
CLK -
J32 / J33 Reserved Reserved
OUT1 + Data of DPU B Data Q 1
OUT1 -
J34 / J35 Reserved Reserved
OUT2 + Data of DPU D Data Q 2
OUT2 -
J36 / J37 Reserved Clock @ output of DPU D Reserved Clock @ BR / 8
OUT3 +
OUT3 -
J40 / J41 Reserved Clock @ output of DPU F Reserved Clock @ BR / 8
CLK +
CLK -
J42 / J43 Reserved Reserved
OUT1 + Data of DPU F Data Q 3
OUT1 -
J44 / J45 Reserved Reserved
OUT2 + Data of DPU H Data Q 4
OUT2 -
J46 / J47 Reserved Clock @ output of DPU H Reserved Clock @ BR / 8
OUT3 +
OUT3 -
Table 8 : Data & Clock Outputs with Demodulator Menu 16 (Multi DPU)
QPSK QPSK
NORMAL SOFT 3 MERGE SOFT
DEMODULATOR CHANNEL A
CLK + Clock @ BR/2 Clock @ BR
CLK - Demod A Demod A
Table 9 : Data & Clock Outputs vs Demodulation (soft outputs) Hardware menu dependent
Note 1: Except for the QPSK mode with soft decision output, which involves only the demodulator A, the output
configuration setting for each demodulator is done from the corresponding GUI windows (Demodulator Global
Window: Output mode selection).
Note 3: The coding of In and Qn used for the soft decision outputs is given in the following representation of the
I/Q constellation.
011
Q
010
001
000
111
110
Exact constellation
position depends
101
on AGC settings
100
2. Q
011111
I
000000
111111
100000
111111
000000
011111
100000
EXT LO J51 External Local Nominal freq. Range = 720 MHz 190 MHz
Oscillator input
Nominal input level = 0 dBm 1 dBm
Zin = 50
VSWR < 1.3
Destructive level ≥ +13 dBm
Note 1 : Depending on the modulation mode (BPSK, QPSK, OQPSK, UQPSK) and the setting of the Input Mode
parameter, data and clock input to the Test Modulator are :
1 / Bit Rate
CLK+ *
ts th
For I/Q merged output, RS CADU output and LDPC CADU output:
t s = 1/2BR - 500 ps
t h = 1/2BR - 500 ps
t s = 1/BR - 500 ps
t h = 1/BR - 500 ps
Remark: For data output after specific decoding process (example: TCM + RS-DVB, punctured Viterbi), “holes”
inside the output data and clock signals can be present. These “holes” are due to the delayed check symbols and /
or synchronization words. Nevertheless it has to be considered that for each data corresponds an edge of the
clock.
1 / Bit Rate
CLK +/-
2 / Bit Rate
CLK +/-
4 / Bit Rate
CLCK +/-
DATA I-2
I Data n+1 I Data n+3
1 / Bit Rate
CLK +/-
Data
Frame
Synchronization User Data Parity Data
Word
User Data
Clock
Synchro Pulse
CADU
3. FUNCTIONAL
DESCRIPTION
A monitoring message contains the current configuration of the unit (expected frequency, operating mode, etc.),
dynamic status (IF level, Eb/No, frequency offset, etc.) and alarms (hardware alarm, etc.).
Up to eight Monitoring Clients can be simultaneously connected to the Monitoring port. For more detail on the
monitoring messages, refer to Annex 1.
3.1.2 Control
Configuration commands received from a Control Client allow configuration of the equipment (example : change
the uplink carrier frequency on the Test Modulator) or triggering and action (example : restart the carrier
acquisition process on the Demodulator).
Simultaneous connection of several Control Clients to the Control port is not allowed for security reasons. For
more detail on the configuration commands, refer to Annex 1.
3.2 LOGGING
The CORTEX HDR reports on the Logging port all changes in its configuration.
Up to five Logging Clients can be simultaneously connected to the Logging port. For more detail on the logging
messages, refer to Annex 1.
3.3 DEMODULATION
3.3.1 IF Processing
Signal Processing :
Automatic gain control : the signal level must be in the range –10 dBm to –50 dBm.
IF acquisition : the programmed acquisition range must be compatible with the maximum frequency
uncertainty (Doppler shift, oscillators drift,…).
Cable equalizer filter (see Section 3.8) : cable loss equalizer with programmable attenuation.
IF filtering : matched filter, adjacent canal rejection or custom FIR filters (option).
A number of status enable to monitor the demodulation process at IF : IF signal level, PLL status, carrier
offset, etc…
Vector analysis : check that the displayed constellation is correct and corresponds to the noise and signal
characteristics.
Filter analysis : display in real time the pulse and frequency responses of the digital filtering.
Test & Monitoring : a number of status enable to monitor the bit synchronization process : PLL status, signal to
noise ratio (Eb/No), etc…
The filtering is based on one FIR for I channel and one FIR for Q channel.
or four time the symbol rate (only if symbol rate < 240 Msps)
Example : for a QPSK / 100 Mbps (50 Msps) data stream, the FIR filter sampling rate can be set to 100 MHz or
200 MHz.
symmetrical filter: 52 taps (even symmetrical FIR) or 51 taps (odd symmetrical FIR)
asymmetrical filter: 26 taps on direct path I and Q plus 8 complex taps (Q to I and I to Q)
The I & D filter design is usually the best answer to matched filtering needs. However, custom filters may improve
the performances in some circumstances, like :
phase/amplitude equalization
Filter coefficients can be programmed from files on the hard disk. Up to 1000 files can be loaded to the disk. Files
are ASCII-coded and can be edited using Notepad or any other text editor.
Access path to the filter files is : C:\Program Files\In-snec\crtxnt\FIR. Files are named fir_cust1 to
fir_cust1000.
1. the emitter filter : for frequency division multiplexing (FDM), the pass-band emitter filter is generally a cavity
filter. Base-band filtering depends on the application.
2. the channel : the channel could be considered as an amplitude fading channel with additive White Gaussian
Noise. Amplitude fading is resolved by automatic gain control. One can add the possibility of multi-paths
created by the structure of the satellite that can be modeled by a Finite Impulse Response filter.
3. the receiver filter : they are many possibilities, commonly used filters are Integral & Dump and Root Raised
Cosine (RRC) filters.
In order to get perfect recovery of transmitted pulses or symbols, the equivalent channel must verify the well-
known Nyquist criterion (for a symbol rate R = 2*fc where fc is the physical channel bandwidth, the impulse
response of the equivalent channel should be equal to 0 for each multiple of 1/R). This property is verified for a
chain made of a RRC emitter filter and a RRC receiver filter, as RRC are well-known Nyquist filters. However,
emitter filters at RF frequencies are very often cavity filter design to meet the regulatory rejection specifications,
they are able to work with the signal coming from the high-power amplifier and they have a non-linear phase
response. Moreover, changes of emitter filter characteristics (magnitude and phase) could not be avoided when
there are large variations of temperature like those which take place in space. So, the equivalent channel seldom
verify the Nyquist criterion and this induces inter-symbol interferences (ISI) that are harmful for performances.
A second aspect that is harmful for performances is noise. Two types of noises are present : the thermal noise and
the interference noise, coming from close channels.
In order to reduce the ISI and the influence of noise, two types of receiver could be used :
As they are, these filters are not useful because the equivalent channel is changing. So, they are implemented
through conventional equalizer which are adaptive filters, but these filters need a training sequence which causes
a payload loss.
A better solution for equalizing the incoming signal is to use an automatic adaptive equalizer.
The algorithm behind DEAF is a “Bussgang-like” algorithm implemented on a fractionally-spaced equalizer for
better performances :
Y is a vector of samples.
Second step : start-up / C is iteratively calculated / C(n1)C(n) f(Y,Z) where is the step-size and f a
non-linear and zero-memory function of Z.
The algorithm used by the DEAF device has a convergence time lower than 100 ms.
The main result of the DEAF operation is an important improvement of the measured Eb/No for high data rates
telemetry.
The following screen shot of the constellation display of the HDR shows the advantage of the DEAF for filter
equalization. The screen shot has been done during reception tests through an actual transmission filter. The
demodulator #1 is set without the DEAF and demodulator #2 is set with the DEAF.
If we consider one channel (one polarization), we can see that this channel has a high probability to be perturbed
by the other channel. And we can defined a cross polarization discrimination coefficient as:
Typically and in case of bad conditions of transmission, XPD can be down to < 14 dB for X-band systems and < 8
dB for K-band systems.
In order to compensate for the impact of the cross polarization effects on the data reception, the Cortex HDR
provides the XDEAF function.
The XDEAF function is a real time and automatic digital filtering which takes into account the reception of both
polarizations.
The following BER curves have been measured for a QPSK transmission at 200 Mbps using dual polarization. The
XPD coefficient is 12 dB. The gain for a BER = 10-6 is 4 dB between the green curve (XDEAF disabled) and the
red one (XDEAF enabled).
The following figure gives the effect of the XDEAF on the received constellation in the same previous conditions.
An interesting method offered by the HDR to customize the matched filter on the received signal is to use the
combination of the rejection filters and the DEAF process. In a first time a standard filter is selected (example RRC
filter) and the DEAF process is activated. When the frequency response of the filter is stabilized, it is possible to
store the parameters of the filter inside a specific file. Then, the matched filter can be set up with the customized
filter (file) constructed by the DEAF process. Refer to $ 4.4.4.1 “Global” Window and § 4.4.4.6 “Filter” Window.
Processing mode: single decoder or parallel decoders (up to 16 decoders on each I & Q).
BER estimate by re-encoding the Viterbi decoded data and comparing the re-encoded data to the data fed
to the Viterbi decoder. Note : if the Viterbi decoder(s) fails to lock (BER too high), check the Viterbi
characteristics (Normal or inverted G2, single or dual Viterbi, G1G2 or G2G1 sequencing) and verify
the setting of the I & Q output mode parameter (Demodulator output to the Viterbi decoder(s) input).
Test & Monitoring : a number of status enable to monitor the Viterbi decoding process : decoder lock status, BER
(in %), etc…
In the single mode, there is only one Viterbi decoder connected to the Demodulator module (I & Q output
channels of the demodulator are connected to G1 & G2 inputs of the Viterbi decoder).
In the dual mode, the Viterbi decoding module has two separate Viterbi decoders on I and Q Channels.
I channel
G1
IF input Data
QPSK, OQPSK Viterbi
Q channel decoder
G2
S11
Z-1 G1
D1
Viterbi
decoder
S12 #1
G2
S21
Z-1 G1
I or Q channel Viterbi D2
decoder
S22
G2
#2 …,DN,…,D2,D1,…
…, SN2,...S22,S12,SN1,….S21,S11
SN1
Z-1 G1 DN
Viterbi
decoder
SN2 #N
G2
Puncturing codes (Code 0 and Code 1) and swap sequence must be programmed in the registry (see section
4.2.6.2.2).
Code 0
1
I1 FIFO 1
0
Vector 0
Viterbi
NULL 1
0
Demodulator Decoder
I2 1 0
FIFO 2
C0(1) C1(2) C0(4) C1(5) C0(1) NULL C0(3) C0(4) NULL C0(6)
De-puncture
C1(1) C0(3) C1(4) C0(6) 3/4 C1(1) C1(2) NULL C1(4) C1(5) NULL
G1 Viterbi input = C0
G2 Viterbi input = C1
Viterbi decoder setting : “ G1-G2”
There are two conventions for Viterbi puncturing codes. The first is the one which is defined by CCSDS
recommendation and the second can be found on certain commercial encoders. The second convention only
exists for puncturing ratios with an even denominator.
Cod0 : 1000101
Cod1 : 1111010
Conv. 1 pattern : C0(1) C1(1) C1(2) C1(3) C1(4) C0(5) C1(6) C0(7) ...
Conv. 2 pattern : C0(1) C1(1) C1(3) C1(2) C1(5) C0(4) C1(7) C0(6) ...
Convention 2 pattern is convention 1 pattern with each pair of bit swapped apart from the first pair.
The following table shows the effect of the different values of VitPunctConv registry key.
0 : depuncturing is defined by the VitPunctSwap registry key as described in the previous chapter
1,E-01
1,E-02
1,E-03
NRZ-L
1,E-04 DNRZ
Viterbi 1/2
1,E-05 viterbi 3/4
Viterbi 3/4 DNRZ
1,E-06
1,E-07
1,E-08
2,0 3,0 4,0 5,0 6,0 7,0 8,0
When Viterbi decoding is not used, DNRZ is required for ambiguity resolution in QPSK and OQPSK mode.
Several possible DNRZ schemes can be defined, according to the demodulation (QPSK, or OQPSK).
In Qn Feature
code 1 11 10 01 00 C5A3 AC35 CCDSDS DNRZ
code 2 11 01 10 00 AC35 C5A3 CCDSDS DNRZ + Q;I
code 3 01 10 11 00 6996 AC35
code 4 10 01 11 00 AC35 6996
code 5 10 11 01 00 C5A3 6996
code 6 01 11 10 00 6996 C5A3
code 7 11 10 00 01 C5A3 9669
code 8 11 00 10 01 AC35 9669
code 9 00 10 11 01 6996 3A5C
code 10 10 00 11 01 AC35 3A5C CCDSDS DNRZ + Q;/I
code 11 10 11 00 01 C5A3 53CA CCDSDS DNRZ + I;/Q
code 12 00 11 10 01 6996 53CA
code 13 11 00 01 10 9669 AC35
code 14 11 01 00 10 9669 C5A3
code 15 01 00 11 10 3A5C AC35 CCDSDS DNRZ + /I;Q
code 16 00 01 11 10 3A5C 6996
code 17 00 11 01 10 53CA 6996
code 18 01 11 00 10 53CA C5A3 CCDSDS DNRZ + /Q;I
code 19 00 10 01 11 53CA 3A5C CCDSDS DNRZ + /Q;/I
code 20 00 01 10 11 3A5C 53CA CCDSDS DNRZ + /I;/Q
code 21 01 10 00 11 53CA 9669
code 22 10 01 00 11 9669 53CA
code 23 10 00 01 11 9669 3A5C
code 24 01 00 10 11 3A5C 9669
In 1 1 0 0 0 1 0 1 1 0 1 0 0 0 1 1 0xC5A3
Qn 1 0 1 0 1 1 0 0 0 0 1 1 0 1 0 1 0xAC35
To select this code in the registry, set the registry key to 1 (code number in the left-hand column of the above
table) or enter the DNRZ code value (0xC5A3AC35) as defined in the above decoding table).
In Qn Feature
code 1 0 1 1 0 3C3C 9999 Most common
code 2 1 0 0 1 C3C3 6666
code 3 0 0 1 1 0FF0 C3C3
code 4 1 1 0 0 F00F 3C3C
code 5 1 0 1 0 CC33 A5A5 NRZ-S
code 6 0 1 0 1 33CC 5A5A NRZ-M
code 7 0 1 1 0 3C3C 6666
code 8 1 0 0 1 C3C3 9999
code 9 0 0 1 1 0FF0 3C3C
code 10 1 1 0 0 F00F C3C3
code 11 1 0 1 0 CC33 5A5A
code 12 0 1 0 1 33CC A5A5
code 13 0 1 1 0 9999 3C3C
code 14 1 0 0 1 6666 C3C3
code 15 0 0 1 1 C3C3 0FF0
code 16 1 1 0 0 3C3C F00F
code 17 1 0 1 0 A5A5 CC33
code 18 0 1 0 1 5A5A 33CC
code 19 0 1 1 0 6666 3C3C
code 20 1 0 0 1 9999 C3C3
code 21 0 0 1 1 3C3C 0FF0
code 22 1 1 0 0 C3C3 F00F
code 23 1 0 1 0 5A5A CC33
code 24 0 1 0 1 A5A5 33CC
In 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0x3C3C
Qn 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 0x9999
To select this code in the registry, set the registry key to 1 (code number in the left-hand column of the above
table) or enter the DNRZ code value (0x3C3C9999) as defined in the above decoding table).
BER degradation is expected if the I-to-Q phase offset is not exactly half symbol.
For optimum BER performances, the HDR demodulator software is able to compensate, in real-time, for incorrect
phase offset. The maximum adjustment range is half-symbol ¼ symbol.
Parameter OQPSK I/Q delay allows enabling or disabling the compensation mechanism :
ON(static) : Compensation is enabled. The expected phase offset error must be manually programmed
(from +0.25 to –0.25 symbol).
The I/Q shift status indicates the measured phase offset error.
On the Test Modulator, the I/Q phase offset in OQPSK mode can be set in the range [half-symbol 0.5 symbol].
The phase offset adjust is disabled if the programmed bit rate is below 200 Mbps.
In the demodulation channel, this descrambler is implemented after the Viterbi decoder and the differential
decoder if used and before the frame synchronizer.
The V.35 descrambler is basically a 20-stages shift register with XORED specific outputs. In addition, a specific
operation is used inside the process to guarantee an output transition once every 32 bits for long sequences of 0
or 1.
The descrambler can be enabled or disabled by set-up (from the Cortex HDR GUI or by TCP/IP remote control).
The selection of the standard is done also by set-up.
3.3.7.1 Introduction
The L-dimensional MPSK-TCM (LD-MPSK-TCM) belongs to a family of modulations first introduced by G.
Ungerboeck and improved by S. Pietrobon with the introduction of the multidimensional techniques. The MPSK-
TCM are based on MPSK modulations with the use of convolutional coding to introduce “authorized sequences”
between signal points linked by the trellis of the code. Note that single constellation MPSK modulations may also
be referred to as "bi-dimensional" in reference to the representation of the MPSK constellation points in a signal
space defined by orthogonal I and Q vectors.
In any case, the application of this procedure to several parallel constellations of the same size is referred to as L-
dimensional TCM, denoted LD-MPSK-TCM (with L > 1 and M = 8). The trellis is constructed to maximize the
minimum Euclidian distance between different paths originating and merging to the same state. The construction
of the optimum trellis code and partitioning for the M points in the constellation is based on heuristic rules
proposed in G. Ungerboeck. "Channel Coding with Multilevel/Phase Signals", IEEE Transactions on Information
Theory, vol. IT-28, no. 1, pp.55-67, January 1982 and S. Pietrobon et al. "Trellis-Coded Multidimensional Phase
Modulation", IEEE Transaction on Information Theory, vol. 36, no. 1, pp.63-89, January 1990.
With 4D-8PSK-TCM, the combination of convolutional coding, multiphase modulation and multidimensional
techniques offers a substantial power gain together with bandwidth conservation or reduction, in comparison to
their separate utilization as it is done frequently with binary or quaternary modulations (i.e., sequential
implementation of convolutional coding). The result is an improvement of the performances in terms of BER versus
signal to noise ratio for the same or better bandwidth efficiency, compared with the uncoded (or even
convolutionally coded) OQPSK or QPSK modulations.
Example: Assuming the bit rate of input data equal to 100 Mbps, the 4D-8PSK-TCM channel symbol rate is 50
Msps for 2 bits/channel-symbol or 40 Msps for 2.5 bits/channel-symbol.
The performances of 4D-8PSK-TCM scheme can be substantially improved when concatenated with Reed
Solomon (R-S) on bytes block coding with a proper interleaving so as to ensure a good word error splitting (at the
output of the convolutional trellis decoder) and then good working conditions for the R-S decoder.
Note that in this figure, wi (with index i = 1, … , m) represent the uncoded bits and xj (with index j = 0, … , m) are
the coded bits. The trellis encoder is based on a 64 state systematic convolutional coder and can be considered as
the inner code if an outer block code is introduced. Carrier phase ambiguity is resolved by the use of a differential
coder located prior to the trellis encoder. Spectral efficiencies of 2, 2.25, 2.5, and 2.75 bits/channel-symbol are
achieved with four possible architectures of the constellation mapper. The output switch addresses successively
one of the four symbols ( Z(0) – Z(3) ) from the constellation mapper to the 8PSK modulator (which is in fact a
QPSK modulator for the 2 first efficiencies values).
The present standard is based on the use of a 4D-8PSK-TCM characterized by the following parameters:
Rate of the convolutional coder used for the construction of the trellis : R = 3/4
In fact, the serial to parallel conversion is a byte (8 bits) to symbol (8 to 11 bits) conversion that will be described
later.
An example of differential encoder connections is given in Figure 23 for the 2 bits/channel-symbol case. The
structure of the modulo 8 adder is also shown; it is applicable to both the coder mapper and differential coder.
OUT
For all the bits non concerned by the differential encoding, we have then :
xk wk k m 1
constraint length : K = 7
The convolutional encoder is specified by the following polynomial in octal: h 3 = 050, h2 = 024, h1 = 006, h0 = 103.
Figure 24 shows the recommended convolutional encoder. The shift registers of the encoder are clocked at the
rate of RChS/4.
The number of coded bits is the same for the four modulation efficiencies (i.e., the same structure is used for 2,
2.25, 2.5, and 2.75 bits/channel-symbol), only the number of uncoded bits is changed. The advantage of this coder
is its optimized performance and the reduced internal rate which is equal to 1/8, 1/9, 1/10, or 1/11 of the
information rate.
If Z(i) represents the signals (three lines) at the input of the modulator with Z(0) being the signal set of the first
constellation and Z(3) being the signal set of the fourth constellation, the signal set Z (i) is represented by the
following equation. This representation shows that the bits which are common to each vector set (shown in the first
part of right-hand side of each equation) are sensitive to a phase rotation of /4 and will be differentially encoded.
Z (0) 1 0 0
(1)
Z 4 x 2 x x 4
1 x 7
2
x 3
Z ( 2) 8 5 1 1 x6 x2 mod 8
( 3)
Z 1 x 7 x 6 x 4 x 3 x 2 x 0
x0
x1
x2
x3
x4 0
x5 0
x6
x7
x8 0
(1) (1) (1) 210 210
0 Z2 Z1 Z0
+
2 1 0
21 0 2 1 0 2 1 0 2 1 0 210 210
+ + +
2 1 0 2 1 0 2 1 0
Z ( 0) 1 0 0 0
(1)
Z 1
4 x 2 x x 4 x x x 0
1
8
2 4
0 mod 8
Z ( 2) 9 6 2
x7 x3
( 3)
1 x x x x x x x
Z 8 7 5 4 3 1 0
Z ( 0) 1 0 0 0
(1)
Z 1
4 x 2 x x 4 x x x
9
2 5
1
mod 8
x 0
3
Z
( 2 ) 10 7
1 x8 x4
( 3)
Z 9
1 x x 8 x 6 5
x x 4 x 2 1x x 0
Z ( 0) 1 0 0 0
(1)
Z 4 x 2 x x 1 4 x10
2
x6
x2
Z ( 2) 11 8 4
1 x9 x5 x1 mod 8
( 3)
1 x x x x x x x x x
Z 10 9 7 6 5 3 2 1 0
Z(0) Modulated
Carrier
Constellation mapper
Byte to Symbol
w8 x8 Z(1)
conversion
x7 x7
x6 x6
w5 x5
x4 x4 Z(2)
x3 x3
x2 x2
w1 x1 Z(3)
Differential Convolutional x0
coder Carrier
Coder R=3/4 Generator
Figure 29: Coder and Mapper Implementation at 2 bits/channel-symbol Efficiency
Constellation mapper
Byte to Symbol
w9 x9
x8 x8 Z(1)
conversion
x7 x7
w6 x6
x5 x5
x4 x4 Z(2)
x3 x3
w2 x2
x1 x1 Z(3)
Differential Convolutional x0
coder Carrier
Coder R=3/4 Generator
Figure 30 : Coder and Mapper Implementation at 2.25 bits/channel-symbol Efficiency
Data In(0:7)
Z(0) Modulated
w10 x10 Carrier
Constellation mapper
Byte to Symbol
x9 x9
x8 x8 Z(1)
conversion
w7 x7
x6 x6
x5 x5
x4 x4 Z(2)
w3 x3
x2 x2
x1 x1 Z(3)
Differential Convolutional x0
coder Carrier
Coder R=3/4 Generator
Figure 31: Coder and Mapper Implementation at 2.5 bits/channel-symbol Efficiency
Data In(0:7)
Z(0) Modulated
w11 x11
x10 x10 Carrier
Constellation mapper
Byte to Symbol
x9 x9
w8 x8 Z(1)
conversion
x7 x7
x6 x6
x5 x5
w4 x4 Z(2)
x3 x3
x2 x2
x1 x1 Z(3)
Differential Convolutional x0
coder Carrier
Coder R=3/4 Generator
Figure 32 : Coder and Mapper Implementation at 2.75 bits/channel-symbol Efficiency
hronisation
Transfer frames Randomized Codeblocks Transport frames MTCM symbols
Symb. to bytes
Descrambler R-S decoder MTCM 8PSK
transformation
(DVB-S type) (DVB-S type) decoding demodulation
/deinterleaving
Sync bytes
search/global sync.
This sequence is loaded at the beginning of each transport frame. Due to the chosen polynomial, it is possible to
output the data by bytes with the help of a shifted calculation , i.e. out bit1 or MSB of byte = reg15 EX-OR reg14,
out bit2 = reg14 EX-OR reg13, out bit3 = reg13 EX-OR reg12, out bit4 = reg12 EX-OR reg11, out bit5 = reg11 EX-
OR reg10, out bit6 = reg10 EX-OR reg9, out bit7 = reg9 EX-OR reg8 and out bit8 or LSB of byte = reg8 EX-OR
reg7 and then shift by 8 bits the contents of the register before calculating the PRBS sequence for the next byte.
It should be noticed that in order to avoid tedious rate changes, the data have to be captured at the interface by
group of 238 bytes with one blank byte in front and 16 blank bytes at the rear. During the blank bytes, the
randomization is shifting but the enable bit must be downed to zero.
B 8
first, one byte (00 hexa.) is added in front of the 238 data bytes
then a standard (239,255) R-S code (from DVB-S standard) is applied by computing 16 redundancy
bytes.
The interleaving is performed by using a matrix of (8)16 rows and 254 columns. The 254-bytes packets are writen
row by row, the first byte being put in the first cell. When filled, the matrix is read column by column by packets of
254 bytes separated by synchronization markers. The process goes on with the following group of 16(8)*254 data
bytes creating then a complete frame of 16(8)*255 bytes.
The 16 (8) blocks of 255 bytes (254 data bytes plus one synchro. byte) form the transport frame. This frame
accounts for 4080 (2040) bytes or 32640 (16320) bits.
The synchronization marker of the frame (corresponding to the first block of 254 bytes) is B8 (in hexadecimal) and
the separation between the other 15 (7) blocks of the frame is made by a marker whose value in hexadecimal is
47 when the medium data rate is used.
For high data rates interface, the equipment has the capacity for inserting filling frames. The synchronization
marker for those filling frame are specific. 96 (in hexadecimal) for the first block and 69 for the 15 (7) following
blocks.
It should be noticed that at the receiver side, those filling packets have to be removed.
The succession of the three processes described here above give the way to :
254 bytes
Sync Ri RS redund.
or sync i 238 bytes 16 bytes
Randomized transport packets : Sync bytes and interleaved randomized block IRi
The convention is the following, depicted for 4D-8PSK-TCM 2.5 with the arrangement of the 10 bits with regard to
the 8 input bits is described on next figure.
A B C D E
Byte 1 Byte 2 Byte 3 Byte 4 Byte 5
D7 D6 D5 D4 D3 D2 D1 D0 D7 D6 D5 D4 D3 D2 D1 D0 D7 D6 D5 D4 D3 D2 D1 D0 D7 D6 D5 D4 D3 D2 D1 D0 D7 D6 D5 D4 D3 D2 D1 D0
When restarting BER measurement (see 4.5.4.2), each ambiguity is tested (~1s), before selecting the ambiguity
which provides with the lower BER. The BER is then measured applying this ambiguity. This method is particularly
interesting when the ambiguity is not resolved by the demodulation (example : Metop satellite configuration).
Even with these ambiguities, BER measure can be done in this mode.
Using this method, BER I and BER Q can be separately displayed (see 4.2.6.2.3, value 1), or averaged (see
4.2.6.2.3, value 0).
Example 2 : 8PSK, NRZ-L demodulation, using a PRN code for each 3 8PSK data flows.
Providing that the right 8PSK de-mapping (normal or inverse, natural or Gray) has been selected, BER measure
can be done in this mode.
In this mode, no ambiguity tests are done. Data which are used for BER measure are an image of output data
(channel A for Demodulation Unit # 1, channel B for Demodulation Unit # 2, see 2.2.2). Ambiguities can then be
manually tested, using the 8 first values of OUTPUT MODE parameter (see 4.5.4.1).
0 Method 1 :
IQ,/IQ,I/Q,/I/Q,
QI,/QI, Q/I,/Q/I
GUI : 1 BER value Method 1 : Method 1 : Method 1 : Method 1 :
(I,Q average)
IQ,/I/Q I,/I I,/I, on I 8 phase
(IQ merged before GUI : 1 BER value Q,/Q on Q ambiguities
Viterbi decoding)
1 Method 1 : GUI : 2 BER values GUI : 1 BER value
GUI : 1 BER value (BER I & BER Q) (averaged BER)
IQ,/IQ,I/Q,/I/Q,
QI,/QI, Q/I,/Q/I
GUI : 2 BER values
(BER I & BER Q)
Data swap : Normal I & Q, I inverted & Q, I & Q inverted, I inverted & Q inverted
+ Swap : Q & I, Q inverted & I, Q & I inverted, Q inverted & I inverted
Output mode : Normal or split (separate I & Q output) or I/Q merged or CADU output (refer to the
Hardware Description chapter)
The elementary Doppler measurements (IF offset measurements) are generated every 13.1072 ms. They are
sampled at the rate specified by the parameter « Doppler measurement sampling rate » (every 100 ms to every 10
seconds). As the sampling rate and the generation rate are asynchronous, a linear interpolation is applied for
improved measurement accuracy. Samples are stored, for further transmission, in a measurement block which
size is programmable between 1 and 1000 elementary measurement(s).
The Elementary integrated phase measurements are generated every 13.1072 ms. They are sampled at the rate
specified by the parameter « Doppler measurement sampling rate » (every 100 ms to every 10 seconds). As the
sampling rate and the generation rate are asynchronous, a linear interpolation is applied for improved
measurement accuracy. Samples are stored, for further transmission, in a measurement block which size is
32-N
programmable between 1 and 1000 elementary measurement(s). The integrated phase resolution is 2π/2
radian, with N tunable (see user’s manual for more information). The 64-bit phase counter capacity is 232+N/IF
seconds. As an example, N = 15 gives a counter capacity of 1 day 8 hours and 46 minutes at 1.2GHz.
The following demodulator menus support advanced Doppler measurements, integrating the phase of the
carrier oscillator: Menus # 6, 7, 9, 10, 12, 13, 17, 18, 27, 28, 36, 38, 39, 50.
A single Doppler port is used for transmitting IF offset measurements or integrated phase measurements.(refer to
the STI 100013 HDR document).
Doppler and phase measurements are time-tagged. For precise datation of Doppler and phase measurements, it
is strongly recommended to connect the demodulator to an IRIG-B generator. In such case, the precision of the
time tag is 1µs.
64 bits 32 bits
Cycle counter 2π rad
A 64 bit counter, using 32 bits for the modulo part, and 32 bits for the cycle counting part, has a revolution period
of 5s for an IF at 720 MHz. The overall 96 bits counter has a revolution period of more than 800 years. The
Doppler port thus discards some of the MSBs and LSBs to output 64 bits phase measurements. The truncature
operates as follows. The registry value:
HKEY_LOCAL_MACHINE\SOFTWARE\IN-SNEC\CrtxHdr\SetDefault\Signal Processing\DmuX\Integ_Phase_BinShift
sets the number of LSBs that are discarded. Let N be the value of Integ_Phase_BinShift:
The phase resolution thus becomes 2π/232-N radian. The revolution period of this counter is 232+N/IF where IF is the
input IF frequency. The default value for the registry key is 15 (decimal), 0xE (hex).
Table 13 and Table 14 give phase resolution and revolution period for different settings of N, with an IF of
720MHz, and 1.2 GHz.
Samples are stored for further transmission, in a measurement block which size is programmable between 1 and
1000 elementary measurement(s). The first measurement in the block is time-tagged. The figure below shows how
to set the block size in the DMU window.
Phase Doppler
Truncature 64-bits phase
resolution resolution
(N) revolution time
in deg over 1s in Hz
Phase Doppler
Truncature 64-bits Phase
resolution resolution
(N) revolution time
in deg over 1s (in Hz)
3.3.10.5 Displaying the carrier offset of the Doppler port in the DMU window
When using menu 6 or 7, the display of the carrier offset in the DMU window (see figure below) is modified to take
advantage of the accurate estimate of the Doppler port.
By default, in these two menus the carrier offset is computed using the integrated phase of the Doppler
measurement feature, with a fixed sampling period of 10ms.
The sampling period of the integrated phase offset can be modified through the Windows registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\IN-SNEC\CrtxHdr\SetDefault\Signal Processing\DMUX\Integ_Phase_Freq_Offset
Such an interpolation generates an error. Let’s call inter the interpolated phase, err the phase error, T the 10-ms
period and the time between 0 and T when the phase is interpolated.
inter(t)(t) (tT)(t)
T
The Taylor expression of the phase at t+ is :
2
(t)(t)F D(t) D'(t) R2(t) , where D(t) is the input Doppler and R2(t) the rest such
2
that :
3
R2(t ) sup D''(x) (Lagrange overestimation).
3! xt,t
err(t )inter (t )(t ) (t T)(t)(t )(t) T R2(t T)R2(t )
D'(t)
T 2 T
T2 T3
so err(t ) sup D'(t) sup D''(x)
8 xt,t T 3 xt,t T
For instance, a Doppler rate of 1000 Hz/s with a second-order Doppler variation of 10 Hz.s-2 give a phase error
lower than (0.0125 + 3.3310-6) cycle.
IN MOST CASES, USER WOULD NOT USE CRANKY VALUES FOR THE SAMPLING RATE. THUS, NO INTERPOLATION WOULD BE
APPLIED, BECAUSE ACCUMULATED PHASE ARE GENERATED SYNCHRONOUSLY WITH THE SAMPLING RATE DATES.
Receiver center frequency and the accumulated phase with a resolution of 2-32 cycle.
ferr t Ts
The Doppler error is
2
(t Ts)(t)
Ts
' t Ts
2
Ts 2 Ts 3
With (t Ts)(t)Ts'(t) ''(t) (3)(t) R3(t Ts)
2 6
Ts 4
where R3(t Ts) sup (4)(x) ,
4! xt,t Ts
Ts2 2
and 2
' t Ts2 '(t) Ts''(t)
2
(3)(t) R'2 t Ts
2
Ts
3
where R'2 t Ts
2
2
sup (4)(x) .
3! xt,t Ts
So ferr t Ts
Ts2
Ts3
sup D(2)(x) sup D(3)(x) where D(t) is the input Doppler.
2 24 xt,t Ts 16 xt,t Ts
A typical second-order Doppler variation of 10 Hz.s-2and third-order Doppler variation of 10-4 Hz.s-3 give a phase
error lower than (4.1610-3 + 6.2510-9) Hz for a sampling period Ts of 0.1 s, and lower than (41.6 + 6.2510-3)
Hz for a sampling period Ts of 10 s.
So, the maximum error on the Doppler computing due to the linear interpolation on the second-order phase
variation is
Ts 2
DR T
2
.
For example, with a Doppler rate of 1000 Hz/s, the maximum error will be 0.43 Hz for a sampling period of 0.1 s
and 0.0043 Hz for a sampling period of 10 s.
f 2vr
The relation between range rate and Doppler is : , where f is the satellite carrier frequency, vr the radial
f c
velocity (range rate) and c the light celerity.
For a 2.2-GHz beacon, the corresponding range rate error will be 2.93 cm/s for a sampling period of 0.1 s and
0.293 mm/s for a sampling period of 10s.
increment computing (in this computing Tseff is approximated by Ts, and e is consided as <<< incr).
Due to double-float format limitations, e = 214 is higher than the possible error (11 bits come from the difference
between the 64 bits and the 53 bits mantissa of the double-float representation, on which up to 3 bits may be lost
in the computing process).
This resolution is effective when the programmed sampling period is a value for which the floating representation
does not generate any error (examples : 10 s, 1 s or 0.125 s).
An error made on the sampling period generates an error on the Doppler estimation :
With a typical value of 720 MHz, the Doppler computing error will be 39 mHz with Ts = 0.125 s.
IF Input
Digital Outputs
Demodulatio
Demodulation n Data + Clock
Bit synchronization Generation
PCM decoding
Frame synchronization
Demodulatio n
R-S decoding/descrambling
Time Code Input
LDPC decoding
Virtual Channel extraction
Time Distribution
Time tagging
SCSI
Data output
FTP
DAS
Up to 3 Tbytes
RAID 5
In this mode, the frame synchronizer compares the signal bit by bit, until it matches the expected
synchronization word to within n bits where « n » is a programmable error factor, referred to as the
synchronization threshold (SYN). The synchronization threshold can vary from 0 to 15 (inclusive).
A programmable mask can also be applied to the synchronization word to ignore corrupted bits in the
synchronization word resulting from a spacecraft failure.
Before moving onto the LOCK mode, the frame synchronizer will check « i » consecutive occurrences of the
synchronization word (to within n errors). The contents of the telemetry block between two synchronization
words is not checked. During this phase, any occurrence of an incorrect synchronization word returns the
frame synchronizer to the SEARCH mode. « i » is programmable between 0 and 15 (inclusive) and referred as
the CTL (Check-To-Lock) threshold. To switch from SEARCH to LOCK, the frame synchronizer must receive
i+1 correct synchronization words except when i = 0 (in that case, the frame synchronizer will transmit frames
starting from the frame containing the first occurrence of a correct synchronization word).
In the LOCK mode, the frame synchronizer merely checks the occurrence of a new synchronization word (to
within n errors) every frame. The window in which the synchronization word should be found is enlarged by N
bits (N = bit slip parameter = 0, 1 or 2 bits) to cope with potential bit slip in the telemetry demodulation process.
Transmission errors (signal heavily affected by noise) or loss of PSK demodulator lock may occur : the frame
synchronizer will then only return to SEARCH mode after « j » consecutive occurrences of incorrect
synchronization words (number of errors greater than the synchronization threshold). « j » is programmable
between 0 and 15 (inclusive) referred to as the LTS (Lock-To-Search) threshold.
The frame synchronizer synchronizes the frame in accordance with the SYN, CTL, LTS and Bit Slip parameters
provided to it :
SW 1,9
SW 0,8
C correct
NT
correct
NT C SW 2,A
correct
(1) NT (2)
NT T
S (1)
NT L
SW 7,F incorrect
NT (3)
T
Scenario: CTL = 2, LTS = 3
Received telemetry:
Dotted lines: alternate scenario (different frame contents)
Frames 0 to 2: SW correct
Frames 3 to 7: SW incorrect (1): return to search mode if SW incorrect
Frames 8 to A: SW correct (2): stay in lock mode while SWs are correct
Frames B to F: SW incorrect (3): return to lock mode if SW correct
Phase or channel ambiguity resolution is then automatically performed by the frame synchronizer during the
SEARCH phase (and only during this phase). If the comparison between the expected synchronization word and
a given window on the received data stream fails, another phase & channel configuration is checked and the
process is repeated until the frame synchronization word is identified. The frame synchronizer switches then to the
CHECK phase.
When the synchronization input is set to I ( respectively Q) (see section above)., the frame synchronizer
searches the synchronization word on I and Q channels (at Frame synchronizer input) and automatically
route the selected channel to the I (respectively Q) ECL output.
Note 2 : Allows to retrieve the original data stream even if the on-board data process is unknown to the operator.
Note 3 : Providing that correct 8PSK de-mapping (normal or Gray) has been selected.
- to maintain bit or symbol synchronization on the telemetry processing chain, by always having a minimum bit
transition density on the received telemetry signal,
- to avoid a false carrier lock that can occur on a modulated signal with periodic data,
De-randomization by the CORTEX HDR complies to the CCSDS recommendation 101.0-B-3 (Blue Book - May
1992). The pseudo-random sequence is generated using the following polynomial :
h(x) = x8 + x7 + x5 + x3 + 1
Are programmable:
- the polynomial of the generator of the pseudo-random sequence The supported maximum degree of the
polynomial is 16 (refer to the examples below)
- the initial value of the generator (fully programmable between 0x0000 and 0xFFFF).
8 7 5 3
Example 2: Polynomial: X + X + X + X +1 (polynomial set-up value: 0x1A9)
For modulation schemes with separate I and Q, each de-randomization function is configurable
independently of each other.
The customized de-randomization can performed before or after the associated decoding (Reed Solomon or
LDPC). That is programmable (refer to CADU window).
The CRC is user-programmable via two parameters : CRC Polynomial (CRC16, CCITT, etc…) and CRC Preset
Value (usually all bits set to 0 or to 1).
The CRC value is supposed to be the last two bytes of each frame. The CRC Preset Value is added to the
computed checksum.
E = 16 R-S symbol error correction capability within a R-S codeword (coded to decoded information
ratio = 255/223),
The Virtual fill length and Interleaving depth are automatically deduced by the HDR from the CADU length
set by the operator with the following formula:
V max = 15
CL max = 2044
CL min = 244
I: Interleaving depth
CL: CADU length (in bytes)
V: Virtual fill length (in bytes)
Vmax: Virtual fill length max (in bytes)
The R-S decoder status includes two counters (good frames and bad frames), the number of corrected errors (per
frame) and the BER.
E = 8 R-S symbol error correction capability within a R-S codeword (coded to decoded information
ratio = 255/239),
Interleaving depth : 1 to 8
Other characteristics : refer to: ECCS - Space data links – Telemetry synchronization and channel
coding ECCS-E-50-01.
Interleaving depth and virtual filling length are automatically deduced from the CADU length set by the operator
with the same formula as for RS (255,223).
Other characteristics : refer to: CCSDS – AOS Space Data Link Control- CCSDS 732.0-B-1 Blue Book .
On each I and Q separate outputs, the supported format of a CADU is the following:
RS frame format: 2 interleaved (223,255)RS blocks with 7 bytes of virtual filling per RS block
In conformity with the CCSDS experimental specification, the CORTEX HDR supports:
- the 1/2 and 2/3 LDPC codes optimized for deep space applications
For more details on these codes, refer to the following CCSDS document:
Low Density Parity Check codes for use in near-earth and deep space applications
Experimental Specification - CCSDS 131.1-O-2
September 2007
3.4.10.3 LDPC 1/2 and 2/3 codes for deep space applications
The Cortex HDR supports a subset of the LDPC codes family optimized for deep space applications and specified
by CCSDS. These codes are also known as AR4JA LDPC codes.
3.4.10.4 Implementation
The LDPC decoder is implemented after a frame synchronizer and after the de-randomizer if the randomization is
used. The LDPC is a block decoder that can be synchronized to CADU processing and when it is, from this aspect
it is identical to the Turbo decoding and very close to the Reed Solomon decoding. The LDPC code can also be
asynchronous from the CADU (refer to § 1.6.1.7 Transport layer (RSDVB or asynchronous LDPC layer)).
Any phase ambiguity at the output of the demodulation has to be resolved by the frame synchronizer
before the decoding
The decoder uses soft decision at the output of the bit synchronizer
In the HDR implementation, after the last iteration the parity control is processed one more time. This control is
able to detect bit errors before and after decoding. This allows to elaborate a BER estimation before and after the
decoding and also a quality indication “Good/Bad” of the decoded CADU.
In the Cortex HDR, the LDP decoder can be enable in the CADU layer or in the Transport Layer if this one is used.
The selection can be done from the GUI
3.4.10.5 Performances
The following BER curves give the performances of the Cortex HDR in QPSK, OQPSK and 8PSK modulation
modes with LDPC 7/8. Curves are given for the following Bit rates: 150, 200 and 400 Mbps. Performance depends
on the number of iterations used by the LDPC decoding process and consequently depends on the Bit Rate
value. These BER curves can be compared with the given NASA CCSDS reference curve.
QPSK Modulation:
1,00E-01
1,00E-02
1,00E-03
1,00E-04
1,00E-05
BER
1,00E-06
1,00E-07
1,00E-08
1,00E-09
1,00E-10
3 3,2 3,4 3,6 3,8 4 4,2 4,4 4,6 4,8 5 5,2 5,4 5,6 5,8
Eb/N0 [dB]
OQPSK Modulation:
1,00E-01
1,00E-02
1,00E-03
1,00E-04
1,00E-05
BER
1,00E-06
1,00E-07
1,00E-08
1,00E-09
1,00E-10
3 3,2 3,4 3,6 3,8 4 4,2 4,4 4,6 4,8 5 5,2 5,4 5,6 5,8
Eb/N0 [dB]
8PSK Modulation:
1,00E+00
1,00E-01
1,00E-02
1,00E-03
1,00E-04
BER after 14 iterations
BER
BER Av
1,00E-05
1,00E-06
1,00E-07
1,00E-08
1,00E-09
6,0 6,5 7,0 7,5
En/N0(dB)
The following table gives the performance of the LDPC decoder of the HDR, in term of Eb/No @ BER = 10-6
(QPSK mode). The performance is given here in function of the number of iterations of the decoding process.
With the external data storage option, DAS RAID5 is supported as archiving system using an SCSI interface
(DR2912) or optical fibre interface (ER2912).
Example : DR2912-SA
The ZDS NTU 100272 document gives a description of the installation of the RAID system with the HDR-XXL.
In each case (internal or external) data recovery can be done by transferring files via an FTP server.
The first TM Block to transmit : first block in the HDR real-time buffer or TM block with specified time-tag
(real-time or recorded data).
Next figure illustrates the data formatting for real-time and recorded TM Messages. See Annex 1, STI
100013_HDR Section 2.6 for more details on the Ethernet interface.
Message preamble
& status
Message postamble
RAM Buffers TM Message
X, Y & Z defined in DRG table # 1
FIFO-structured
(applies also to disk partitioning)
8 TM packets per buffer
Header (512-byte alignment)
TM Packet # 1 TM Block # 1 SW Frame…
TM Packet # 2 TM Block # 2
PC RAM Buffer
or raw data
for TM-A … …
(8-byte words + filler
… …
X%
… … Time-tag (8 bytes)
PC RAM Buffer
TM Block :
for TM-B
TM Block size : up to 1,048,656 bytes
(DRU table # 35)
Y%
Frame size : up to 1,048,576 bytes
(DPU table # 3)
Free space
Z% Data storage in TM files on the hard disk
Number of TM packets per file : DRU table # 4
The data are recorded at the frame level after the Reed-Solomon decoding if used (CADU). The data are recorded
on an external DAS archiving system connected with the CORTEX HDR unit.
Before being recorded, successive filtering and sorting operations can be applied on specific words inside the
incoming data frames in order to store into dedicated directories the frames which are useful for the Users.
Nevertheless the other frames are temporary recorded in a specific “trash” directory. These operations are fully
programmable and can be individually selected or not.
RS filtering, allows to discard or not the Reed-Solomon code blocks declared as non corrected,
Filter A,
Sort A,
Sort B,
Sort C.
The filtered and sorted frames are recorded inside binary files. To be easily recovered by the Users, the binary
files are written inside specific dedicated directories of which tree construction and names are fully
programmable and are in relation with the successive filtering and sorting operations.
For each recording session, a pass report file is created. A the end of a recording session, the corresponding text
file provides information about the recorded data files. These report files are also placed at the disposal of the
Users in a dedicated directory.
The names of the files are automatically defined at the starting of a recording session. The names are divided into
several fields providing the start date of the recording session, specific markers and programmable characters
strings associated with the different filtering and sorting operations.
The HDR unit is fitted with a standard FTP server “FileZillaServer” and the users can recover the useful files from
the dedicated directories using a standard remote FTP client in a simple read operations.
The files storage durations are programmable and depend on the directory type: the directories containing useful
data files have a nominal storage duration and the “trash” directories have a temporary storage duration.
For the setting and operation of the functionality basically there are two steps. The first step is the static set-up and
it is done one time for the mission of the unit,. The static set-up consists in the definition of the partition of the
memory space for data and report directories, the definition of the rules to construct the dedicated directories and
the definition of the roots of the files names. A static set-up is defined inside a set of configuration files which are
text files, there can be several different sets of configuration files. The second step is the dynamic set-up and it is
done before a pass of a given satellite. It consists in selecting the filtering and sorting operations for the given
pass, its set of configuration files and if necessary the generation of the associated directories tree, in
programming fields to complete the construction of the files names, in giving a start and a stop dates for the
recording. This dynamic set-up is done through the TCP/IP Control TCP/IP port of the HDR unit. Detailed
instructions to program the functionality are given in the “Recording and FTP Recovery” User Manual DTU
100381.
The maximum number of TM blocks per file is defined by the current configuration of the CORTEX HDR. The
effective number of TM blocks per file can be less that the maximum only when the recording session is stopped.
… /…
Time Tag
(8 Bytes)
Status
(8 Bytes)
When the frame synchronizer is disabled, the Status field is never included inside the TM blocks. On the other
hand and independently, the insertion of the Time Tag field can be disabled or not (it is a set-up parameter, refer
to the “Real Time” window in chapter 4).
For example, in order to record raw data without any added bytes inside the binary files, the following set-up
conditions must be satisfied:
2 - the selected TM data block size must be set to N x 8 bytes (example: 1024 bytes)
The CORTEX HDR generates a pass report file in the result passes directory. The name of the report file is
reconstructed as the TM file name, except for its extension.
There is one line per TM file in the ASCII report file. Each line is composed of 5 fields separated by ‘; ‘ .
In this mode, 64 directories for the storage of the data are created (VC_00 to VC_63) per defined reception
channel. Each directory corresponds to a given VCID.
Only the Sort A operation is used (the other filtering and sorting operations are disable by set-up in the FTP
window). The Sort A operation consists in extracted from each received CADU its VCID and comparing it with the
different possible VCID values (from 0 up to 63), its operation is defined inside the configuration file:
SORT_A_0.txt. The VCDU are store inside dedicated files in their corresponding directories and put at the
disposal of remote Users using a FTP client software.
For each session a corresponding report file is generated included information on the recorded files. These files
are store in specific directories.
DiskController_1_00
Directories for session report
Report_TMA files for TMA and TMB
1 report file per recording
session
Report_TMB
DiskController_1_01
VC_00
TMA
VC_01 Directories for the 64 VCID
+
Directory for unidentified VCID (>63)
VC_63
VC_XX
TMB
DiskController_1_02 (same structure as TMA)
The names of the recorded data files are defined by the SORT_A_0.txt configuration file and by the set-up in the
FTP window, an example of a file name is given below :
R_20070225093835_00001.TMI
The contents of the data files are defined in the paragraph 3.4.6.4.1.2.
The names of the session report files are defined by the set-up in the FTP window :
R_20070225093835.TXT
The contents of the session report files are defined in the paragraph 3.4.6.41.3.
For detailed explanation on how to program and operate the FTP functionality refer to the “Recording and FTP
Recovery” User Manual DTU 100381.
Replay of data using the Test Modulator (Test Modulator mode). In this case the data are sent to the Test
Modulator for modulation and re-transmission at the IF level (720 MHz or 1.2 GHz). The data can be
demodulated by the Demodulators just as in real time reception.
Replay of data at the ECL outputs (Data + Clock mode). In this case the data are sent directly to the ECL
outputs of the selected demodulator(s) in the selected output format. The Test Modulator is not used nor
the demodulation function of the Demodulators.
Recorded data by the Cortex HDR itself during a pass of a satellite (Report TM mode)
In the first case, all the data contained inside files recorded during a pass of a satellite and corresponding to a
report are replayed in the chronological order. It is also possible to select only one specific file of a selected report.
In the second mode (User Data), in order to be easily selected from the Playback Window, the data files must be
written in a sub-directory called “PLAYBACK” in a selected recording partition (example: TMA, TMB,… refer to the
recording section). The files can be written directly in this directory, then it is necessary to change their names by
1, 2, 3 …. or inside sub-directories , in this second case the names of the subdirectories have to be named: 1, 2,
3…The format of the User files must be compatible with the standard HDR files, i.e. binary files.
The multi-DPU functionalities are implemented inside a specific demodulator menu (menu 52) and a
specific test modulator menu (menu 5), which can be configured by parameters setting.
Basically this menu supports the following configurations described in the following figures:
- One channel QPSK demodulation with 2 DPU connected to the demodulator outputs (DPU A and
DPU C)
- One channel QPSK or 16QAM demodulation with 4 DPU connected to the demodulator outputs
(DPU A, DPU C, DPU E and DPU G)
- One channel 16QAM demodulation with 8 DPU connected to the demodulator outputs (DPU A, DPU
B, DPU C, DPU D, DPU E, DPU F, DPU G and DPU H)
- One channel QPSK or 16QAM demodulation with 1 DPU (DPU A) connected to the demodulator
merged output, essentially used for BER measurement purpose
For each configuration, the input is done at 720 MHz IF level, the demodulated and processed data at the
output of each DPU can be recorded inside the internal hard disks of the unit (1 Terra Bytes available). The
data can be recovered using FTP.
Each DPU (data processing Unit) consists in the following CCSDS compliant functions:
- a frame synchronizer
- a de-randomizer
- a Reed Solomon RS(223,255) decoder with supported interleaving and virtual filling
- a VCDU detector
The total internal recording capability (internal Hard disks) is 1 Terra Bytes.
For example with the 16 QAM – 8 DPU mode, the received data flows at the inputs of the DPUs is given in the
following figure. An offset of 1 byte is inserted between the successive CADUs.
An identical mechanism is implemented for the QPSK – 4 DPU mode and the QPSK – 2 DPU mode.
The following tables gives the correspondence between the offsets and the DPUs for the different modes. For
each mode, two mapping are today available and selectable from the GUI (parameter: DPU Map in the DPU
CADU window).
Bit number odd-b1 even-b1 odd-b2 even-b2 odd-b3 even-b3 odd-b4 even-b4
DPU-X DPU-A DPU-C DPU-E DPU-G DPU-B DPU-D DPU-F DPU-H
Offset (bytes) 0 1 2 3 4 5 6 7
Bit number odd-b1 odd-b3 even-b1 even-b3 odd-b2 odd-b4 even-b2 even-b4
DPU-X DPU-A DPU-C DPU-E DPU-G DPU-B DPU-D DPU-F DPU-H
Offset (bytes) 0 4 1 5 2 6 3 7
Bit number b1 b2
DPU-X DPU-A DPU-C
Offset (bytes) N/A N/A
Bit number b1 b2
DPU-X DPU-A DPU-C
Offset (bytes) 0 4
If the CCSDS Virtual Channel sorting is disabled (TFP window), the data files are recorded inside the sub-
directories CV_XX of each directory.
If the CCSDS Virtual Channel sorting is enabled, the data files are recorded inside the specific sub-
directories: CV_NN with NN = 00 to 63 being the Virtual Channel ID number.
Multi-DPU outputs on ECL connectors are described in chapter 2.
CONFIGURATION
The Configuration window allows to mount and connect up to 8 DPU (Data Processing Unit) with the DMU
(Demodulation Unit A).
From the following windows examples it can be seen that the hardware menu (FPGA basic menu) number is 5 for
the test modulator and 16 for the demodulator. These menus support the multi-DPU processing.
In the following first example, the 8 DPU and associated 8 DRU (Data Recording Unit) are enabled. This selection
corresponds to the 16QAM – 8DPU configuration.
In the following second example, 4 DPU and associated 4 DRU are enabled. This selection corresponds to the
QPSK or 16QAM – 4DPU configuration.
Remark that with the 4 DPU configuration, must be selected : DPU and DRU A, C, E and G.
For the standard QPSK- 2 DPU configuration, must be selected only DPU and DRU A and C .
Only one DMU (DMU A) is available with this demodulator hardware menu number 16.
DEMODULATION UNIT
The demodulation function contains a specific feature, this is at this point of the data processing chain that the
data flow is arranged in order to meet the 8 bits symbol shift special feature for ambiguity resolution purpose. To
properly work it receives the frame synchronisation signals from the “Frame Sync”. This way it can reorder bits to
route the right channel to the right DPU.
The configuration field in the MCS is the I/Q Polarity filed. If the used configuration used is 16QAM, 8 channels we
must select the “Ambig 8DPU” item, if the used configuration used is QPSK 4 channels we must select the
“Ambig 4DPU” item and if the used configuration used is QPSK 2channels we must select the “Ambig DPUA+C”
item.
The setting of the demodulator for the 16QAM 8 DPU mode is the following:
The setting of the demodulator for the QPSK 4 DPU mode is the following:
The setting of the demodulator for the QPSK 2 DPU mode is the following:
Remark 1: The ambiguity resolution for multi DPU works only if all of the concerned channels are valid (e.g. the 2,
4 or 8 Frame sync are locked), if one of these channels becomes and stays unlocked during equivalent time of 15
frames, the ambiguity resolution state machine will consider itself in a bad ambiguity resolution state and then will
search for a new one. As a result, if one of the channels does not work broken for any reason, it will impact all the
channels.
Remark 2: The mode “8DPU Ambig” does work only for 16 QAM’s mapping : map 2.
For each DPU, a specific parameter (Input Selection) must be set. The role of this parameter is to split the data
flow coming from the demodulator and depending on the DPU configuration. This is at this stage that the data flow
is split in 2, 4 or 8 depending on the configuration needed.
The configuration fields in the MCS are those corresponding to “Input selection” section.
The NRZ-M to NRZ-L decoding function is activated in the MCS by ticking the “NRZM DPU” field.
BER TESTER
The PRN tester has been added at the DPU level. It can be configured via the MCS “Operating mode” field:
- Possibility to test an inverse PRN has been added too (it is done by inverse the binary flow before the PRN
tester). It can be configured via the MCS “Inverse” field.
- Possibility to test whole data or only user data has been added. “Whole data” consists in the entire data flow with
the Synchronization word and the RS parity bytes. “User data” excludes synchronization word and RS parity
bytes. It can be configured by the field “Tested Data”.
TEST MODULATOR
The test modulation function provides the possibility to select: 1, 2, 4 or 8 parallel data processing channels. This
selection is controlled by the MCS field “Parallel Channels” in the “PCM” window of the test demodulator.
For “2 Data Units”, ” 4 Data Units” and “8 data Units” selections, the generated data frames are delayed by one
byte from on unit to the other an following the rules described earlier.
DpuOffset2=0x40
DpuOffset4=0x5140
DpuOffset8=0x75316420
The test modulator NRZ-M encoding function is a specific feature. It is controlled by ticking the NRZM-DPU
selection field on the encoding page of the modulator unit.
2 - Access using the uihm tool (Also named HDR debug MMI)
The uihm tool (HDR debug MMI) is a software integrated inside the HDR and can be started and operated from
the screen of the HDR. This tool connects the HDR software (SPS) and allows through specific windows the User
to monitor and control some specific internal parameters as the setting of the PN generator.
To start uihm, double click on “uihm.exe” in C:/Program Files/IN-SNEC/uihm. A first window will appear. Click on
“Connect” (to connect the interfaces between uihm and the SPS). Then select the folder “Parameters”. Two
buttons are dedicated to the control of the channels of the test modulator. They are: MODRG1 and MODST1.
The first button MODRG1 (see the following figure) allows the User to change parameters which are also in
registry (Sync Word and Pseudo generator initial values) independently on each channel. The first parameter
(DPU Offset) allows the user to define the Sync Word offset (in bytes) between each channel. The values are (0
for 1 byte offset, 1 for 2, 2 for 3… and –1 for 0). For example, as per MELCO specification this field must contain 0
which correspond to an offset of one byte between each channel.
Remark 1: the number of bits used to initialize the PRN generator depends on the PRN type, the bits used are in
any case the LSB.
Remark 2: the size (in bytes) of the Sync Word depends on the corresponding STI parameter, the bytes used if the
size is less than 8 bytes are the MSB.
Remark 3: the default values of these parameters can be configured directly in registry.
/HKEY_LOCAL_MACHINE/SOFTWARE/IN-SNEC/CrtxHdr/SetDefault/SignalProcessing/Tstu
"SW1" to "SW8”
"DpuOffset"
The second button: MODST (see the following figure) allows the User to configure parameters which are defined
in STI (SW size, operating mode, file number, file size, block code) independently (refer to the STI documents). If
we want to command these parameters via the debug windows we must first disable STI, this is done by setting
the first field to 1.
The precise description of each field is defined in STI document (STI10013 HDR).
- Combining of the two channels, through optimal weighting. In this case up to 3 dB gain can be achieved
when both signals have the same Eb/N0.
The combining system, also named Diversity Combining Unit (DCU), receives data from two demodulators. It
resolves phase ambiguity between the two channels, and deals with the different locking states possible. Its output
feeds a FEC device, followed by a Format Output.
- m and n are dynamically adjusted by the combining system. This is described in the “Signal processing”
section.
- Best channel: only the signal of the channel with the best Eb/N0 is fed through the combining system.
- Combining: signals of both channels are combined using optimal weighting. In this case, the combining
gain versus the best channel is :
EbN
0
Eb
(dB)combining N0 (dB)best_ channel
10Log10 110 Level(dBm) worst _ channel Level(dBm)best _ channel
10
Amplitude _Channel
x100
Amplidude _Channel _ A Amplitude _Channel _ B
The sum of the relative signal amplitudes is 100. The best case (3-dB gain) is achieved when both IF Receivers
are locked onto equal-strength signals.
- Unlocked if the output is set to combining, and both demodulators are unlocked.
- Acquisition if both demodulators are locked, and the system searches for a fit between both signals. The
system identifies the differential ambiguity between both signals.
- Check if the system verifies the differential ambiguity found during the acquisition phase. This happens
when the observed combining gain is lower than the theory by more than 0.3dB. This is also the normal
working state when “Best channel” mode is selected.
Specific attention should be paid to the following points otherwise warnings will be issued :
- modulations must be identical, and must be one of the following : QPSK, OQPSK, 8PSK.
- IF inputs must be different (no gain can be achieved with the same signal feeding both inputs).
- Configuration of matched filters must be identical (data paths before the DCU must be equivalent).
Functional tests Telemetry reception and processing without noise (IF demodulation, bit synchronization, BER
measurement).
BER tests BER measurement in the presence of noise. Bit-by-bit comparison of the simulated PCM to
the regenerated PCM from the bit synchronizer (File mode or pseudo random mode).
Note : the signal-to-noise ratio (Eb/No) can be computed from the following formula :
Where :
C_carrier : carrier level (in dBm)
9 8 7 6 5 4 3 2 1 0
PRN10 data
PCM data can be retrieved from files on the disk. Files are hexadecimal-coded and can be edited using Notepad
or any other text editor. Access path to the simulated telemetry files is :
C:\Program Files\In-snec\crtxnt\BER
- Tset_time < 1 ns
Because this clock signal is directly used by the modulator, the phase jitter should be as low as possible (< 1 ns).
One recommends to connect the input clock before selecting the External Data mode. In this mode, the external
clock must be permanently provided.
In UQPSK (AQPSK, AUQPSK, AUSQPSK) mode, the external data stream is supposed to be I Channel (Q
Channel is generated by the internal Test Modulator)
Warning : In the External Mode, the programmed bit rate on the Test Modulator must be the addition of the bit
rates on I & Q Channels (QPSK, OQPSK). This number must be multiplied by 2 if data are convolutionaly encoded
by the Test Modulator.
01 00 10 00
11 10 11 01
Q Q Q Q
First bit
111 101 111 101 111 011 111 110
Q Q Q Q
Q Q Q Q
First bit
011 001 110 100 110 010 011 010
101
Q
001 101
Q
S 100 010
S Q
001 010
S Q
100
100 6. C 000
I
001 7. C 000
I
011 8. C 000
I
110 9. C 000
I
111 C
011 111 C 110 101 CS 110 101 CS 011
Inverted Gray 5
S
Inverted Gray 6
S
Inverted Natural 1
S
Inverted Natural 2
S S DS DS
ZODIAC DATA SYSTEMS PROPRIETARY
DI 13.
DI 15. I
NA 12.
NAI
HIGH DATA RATE RECEIVER HDR-XXL ZDS Ref : DTU 100355 Issue : 1 Rev.: 26
CORTEX SERIES - USER’s MANUAL Customer Ref : Date : June 28, 2013
Q Q Q
B 9 1 3 2 6 E A 2 3 1 0
A 8 0 2 3 7 F B A B 9 8
E C 4 6 1 5 D 9 E F D C
F D 5 7 0 4 C 8 6 7 5 4
Q MSB
LSB
0111 0011
19. I 0100
0110
20. I
0101
R2
0001
0010
0000
R1 F = p/4 F =p/12 I
1110 1010
1111 1011
No PCM coding (NRZ-L) or differential coding (NRZ-M or S, DNRZ) (see Figure 50).
Convolutional coding possibly combined with PCM coding (see Figure 51).
Reed-Solomon coding possibly combined with convolutional coding (see Figure 52).
8PSK with or without 4D-TCM and R-S coding (See Figure 53)
-6
10
-8
10
0 2 4 6 8 10 12
10log(Eb/N0) (dB)
-2
10
<-VITERBI
-4 <- NRZ-L
10
-8
10
<-VITERBI+NRZ-M
-10
10
2 3 4 5 6 7 8 9 10 11 12
10log(Eb/N0) (dB)
Figure 51 : Probability of Bit Error vs Eb/No with convolutional Coding (rate: 1/2)
-1
10
-2
10
-3 <- RS
10
<-VITERBI
-4 <- no code (NRZ-L or BP-L)
10
-5
10
-6
10
-7
10
-8
10
<-VITERBI+RS
-9
10
-10
10
0 2 4 6 8 10 12 14
10log(Eb/N0) (dB)
1,E-02
1,E-03
1,E-04
BER
1,E-05
1,E-06
1,E-07
1,E-08
1,E-09
4 5 6 7 8 9 10
EbNo
Figure 53 : Probability of Bit Error vs Eb/No in 8PSK Mode with or at 2,5 bit/symbol
1,E-01
1,E-02
1,E-03
1,E-04
1,E-05
BER
1,E-06
4D-TCM-RS 2.5b/Hz (th)
1,E-07
4D-TCM-RS 2.5b/Hz (ty)
1,E-08
1,E-09
1,E-10
5,5 5,7 5,9 6,1 6,3 6,5 6,7 6,9 7,1 7,3
Eb/No
(th = theoretical degradation. Ty = typical degradation values for the CORTEX HDR)
1,0E-01
1,0E-02
1,0E-03
BER
1,0E-04
1,0E-05
1,0E-06
1,0E-07
1,0E-08
-2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Eb/No
1,00E-01
1,00E-02
1,00E-03
ber
1,00E-04
1,00E-05
1,00E-06
1,00E-07
8 9 10 11 12 13 14 15 16
EB/N0
Figure 55: Probability of Bit Error vs Eb/No with 16QAM and RS decoding (800 Mbps)
Note : When convolutional encoding is used, Eb/No (Eb : energy per information bit) should be computed from the
above formula, using as BR value the information bit rate (For convolutionally encoded data (rate ½), the effective
data bit rate on the RF downlink is twice the information bit rate).
3.7.3.1.1 PROCEDURE
Step 1 :
From the type of modulation and PCM coding, select the appropriate BER curve in section 3.7.1.
Step 2 :
Important :
In case there is no convolutional or R-S coding, the effective BER on the transmission link corresponds to
the system BER.
If convolutional or R-S coding is used, the effective BER on the transmission link is higher than the
system BER. In this case, to obtain the implementation loss, the transmission link effective BER should
be considered, and not the targeted BER.
Typically, a targeted BER of 10-6 after Viterbi decoding corresponds to an effective BER of 10 -2 on the
transmission link (see Figure 51 : Probability of Bit Error vs Eb/No with convolutional Coding).
Step 3 :
From the effective Eb/No and the system configuration parameters, calculate the required C/No (see
formulas in Section 3.7.2).
3.7.4 Examples
RADARSAT :
System Configuration :
QPSK modulation
D-NRZ
Implementation loss = 1 dB
NPP :
System Configuration :
SQPSK modulation
Theoretical Eb/No = 6 dB
Effective Eb/No = 7 dB
CORRIOLIS :
System Configuration :
SQPSK modulation
NRZ-M coding
Information Bit Rate (Viterbi decoder output) : 51.2 Mbps (10 log BR = 77.1 dB)
Theoretical Eb/No = 5 dB
Effective Eb/No = 6 dB
TERRA :
System Configuration :
UQPSK modulation
NRZ-M coding
Theoretical Eb/No = 5 dB
Effective Eb/No = 6 dB
Q_Power = 1.2 dB
More flexibility,
Higher performances.
The primary cause of transmission loss below 1 GHz is skin effect, which is proportional to the square root of
frequency :
Since this type of non-linearity is almost linear between 500 MHz and 1 GHz (above figure), it can be well
compensated by a straight line with opposite rope of the tangent.
The sampled signal is filtered before baseband transposition. By this way, a symmetrical low-pass filter can be
implemented :
Fully programmable solution : the gain slope defined by the amplitude difference between the
transmission at 570 MHz and 870 MHz. This gain slope can be locally or remotely programmed
between 0 to 12 dB.
Gain compensation performance in the bandwidth better than 0.1dB (see Figure 56)
960 MHz 860 MHz 760 MHz 660 MHz 560 MHz
C:\Program files\IN-SNEC\log\param_surv\TMx
The names of the logging files are defined by the type of recording (periodic, transition or variation) associated
with a configuration file number N (0 to 100):
periodic_logN.txt
transition_logN.txt
variation_logN.txt
These files contain the date of the recording, the label of the parameters to log and their corresponding values.
They can be edited with “Notepad”.
The following listing gives an example of the contains of a generated periodic_log0.tx file:
………………………………………..
SURVTMA(date,IFLevel_A,eb_n0_A,bitSync_A,frameSync_A);7671.678239;-20.0;25.8;1=Locked;2=Locked
SURVTMA(date,IFLevel_A,eb_n0_A,bitSync_A,frameSync_A);7672.188597;-20.1;25.8;1=Locked;2=Locked
SURVTMA(date,IFLevel_A,eb_n0_A,bitSync_A,frameSync_A);7672.689086;-20.0;25.7;1=Locked;2=Locked
SURVTMA(date,IFLevel_A,eb_n0_A,bitSync_A,frameSync_A);7673.204423;-20.0;25.7;1=Locked;2=Locked
SURVTMA(date,IFLevel_A,eb_n0_A,bitSync_A,frameSync_A);7673.719847;-20.1;25.7;1=Locked;2=Locked
…………………………………………..
In this example, have been periodically recorded for TMA the values of the IF level (label: IFLevel_A), Eb/N0
(label: eb_n0_A), the status of the bit synchronizer (label: bitSync_A), the status of the frame synchronizer (label:
frameSync_A).
The rules for the recording are defined inside text files named: spyconfN.txt recorded in the following directories:
C:\Program files\IN-SNEC\log\param_surv\conf\TMx
A specific window allows the user to build this control file: definition of the control parameters/status to record,
labels of these parameters, occurrence of the recording or thresholds.
4. OPERATING MANUAL
2. Check that the CORTEX HDR chassis is properly grounded and connected to the AC power via the appropriate
power cord.
3. Switch on the chassis (ON/OFF switch is at the rear panel). Allow 8 to 10 seconds for the power supply to start.
4. At the front panel display, follow the boot-up sequence. Depending on the Autolog setting (ON or OFF),
manual intervention may be required (type Ctrl + Alt + Delete, then enter the login password). Default password
at delivery is cortex. Default Autolog setting at delivery : ON.
If the Demodulator board is present, the following SPS icon appears at the lower right corner of the screen :
If the board is not mounted or in the case of a major hardware problem, the following message is displayed :
A detailed description of the Graphical User Interface is given in the next sections.
Each CORTEX HDR unit comes with a factory acceptance test book showing the detailed hardware and software
configuration of the unit at delivery.
Click on Yes to update the MCS File on the disk. Otherwise, click on No or Cancel the command.
To restart the MCS only, click on shortcut menu Start / All Programs / Cortex HDR-XXL / HDR XXL Monitoring
and Control.
To restart the SPS only, click on shortcut menu Start / All Programs / Cortex HDR-XXL / HDR XXL Signal
Processing Software.
SHUT DOWN THE PC-COMPATIBLE WORKSTATION (CLICK ON Start / Shutdown / Shut down the computer).
FAILURE TO OBSERVE THIS PROCEDURE CAN AFFECT DATA ON THE DISK AND THE SYSTEM ITSELF.
WARNING:
THE SCREEN SAVER INSTALLED AT DELIVERY ALLOWS TO SWITCH THE LCD BACKLIGHT OFF.
TO AVOID PREMATURE AGEING / FAILURE OF THE LCD AND DATA TRANSFER PROBLEMS ON THE PCI BUS,
A CTX Document is loaded by the SPS every time the CORTEX is started and the CORTEX is automatically
configured from the contents of this CTX file.
If the machine has never been started since its software was installed, the default loaded CTX file is menu1.ctx.
Else (usual case), the CTX document which is loaded is the last active CTX file (See 4.2.6.1.1 and 4.2.6.1.2).
A copy of this file (CTX Table) is maintained in SRAM and is updated whenever the CORTEX configuration is
changed by the operator. The CTX Table is automatically saved to the CTX Document on the hard disk every 10
seconds and at application ending.
Additional CTX Documents reflecting mission-specific configurations can be created at will by the operator.
CTX Documents are binary files; they cannot be displayed on the screen or printed out.
CORTEX SPS
A copy of the original CTX files (those installed from the reference CORTEX CD ROM) is available in C:\Program
Files\IN-SNEC\crtxnt\Menus\CTX_ref directory. These files are set to read-only. They can be copied to
C:\Program Files\IN-SNEC\crtxnt\Menus\CTX, if required, for being used by the SPS (remove the read-only
protection on the copies).
The CTX Document Name Table is ASCII-coded and is transmitted over the LAN on reception of a monitoring
request with component code 200H.
The CTX Document Name Table is not included in the set of tables returned to the monitoring client on reception
of a monitoring request for All component tables.
The CTX Document Name Table is automatically saved to the disk (C:\Program Files\In-snec\Crtxnt\
CTXDocument\NameTable.TXT) whenever the name of a CTX Document is changed or at application ending.
Save command : name and store the active CTX Table into one of the 10 CTX Documents on the disk.
Load command : select and load one of the 10 CTX Documents and reconfigure the CORTEX.
The CTX Document name can also be modified by editing the NameTable.TXT file before starting the CORTEX
SPS. If a CTX Document is not available (not existing or corrupted), the assigned name is set to an empty
character string.
In the CORTEX Series monitoring table (offset 16) and in the Global CORTEX monitoring table (offset 22), the
CTX Document ID status indicates which one of the 10 CTX Documents was previously loaded or stored and
whether or not this CTX Document was modified since loaded or stored (Update CTX Document status). See
STI 100013 and STI 100013_HDR in Annex 1 for more details.
CORTEX SPS Last Active CTX Document CTX Document Name Table CTX Document # N
REMOTE USERS (Disk) (Disk) (disk)
Start Application
Applicati
Loaded
Accept
Saved
Configuration Request
Accept
Accept
4.2.4.1 General
On some CORTEX products (CORTEX CRT, CORTEX HDR, etc…) a start-up menu offers several high-level
architectures (combination of hardware and software resources) corresponding to different mission requirements.
When starting up the CORTEX software, menu selection can be done either locally (user interface described
hereafter) or remotely (Remote Access Control) by sending control commands to a specific RAC data server on
the CORTEX machine (RAC port # 3003). Control commands are described in the Ethernet ICD STI 100013,
section 2.6.
Starting a new menu while the CORTEX is running takes only a few seconds (2 seconds best case, up to 20
seconds when a new FPGA software needs to be downloaded from the hard disk to the target FPGA).
Stop the active menu : the CORTEX application software is not stopped but all IP connections (to the
monitoring port, telemetry port, ranging ports, etc…), except the connections to the RAC port, are
automatically closed. The connection status on the top level window of the GUI indicates
DISCONNECTED.
Load the menu table : on reception of this command, the CORTEX returns the list of available menus.
Next picture shows the operational scenarios offered by the start-up menu. Use the Stop active menu and Start
new menu pushbuttons to re-configure the CORTEX.
Lines of comments (or disabled choices) starts with a # character (see the four first lines of the file). Other lines are
menu lines.
A menu line consists of several arguments separated by a semi-comma character. Arguments are (from left to
right) :
Menu index : the above menu allows for different configuration. Indexes 1 through 7 are for basic menus
while others indexes are for mission menus.
Menu name : basic menus are named Menu 1 through Menu 7 while missions menus refer mainly to the
satellite to be tracked.
To know the version of the PROMed software (ZDS electronic cards), refer to the Acceptance Test Report
(see also the marking on the PROM chips).
To know the Signal Processing Software (SPS) version and what version of software is downloaded at boot to
the ZDS electronic cards, click on at the lower right corner of the display and select About
Cortex :
The SPS is built around an SPS kernel (supporting multiple CORTEX products such as the CORTEX CRT,
CORTEX HDR, CORTEX ACS, CORTEX RTR, etc…) and a product-specific SPS software layer.
The header of the above window shows the version of the SPS kernel (example : Version 2.4).
Enter 1 for disabling the clock signal when the Bit Synchronizer is unlocked.
Enter 2 for limiting the clock signal frequency deviation to 0.1% of the programmed bit rate when the Bit
Synchronizer is unlocked, and outputting the effective bit rate when the Bit Synchronizer is locked.
Enter 3 for clock setting accuracy better than 1 ppm when the Bit Synchronizer is unlocked and outputting the
effective bit rate when the Bit Synchronizer is locked.
With #m: 12 for LDPC 1/2, 23 for LDPC 2/3 , 78 for LDPC 7/8
With #m : 12 for LDPC 1/2, 23 for LDPC 2/3 , 78 for LDPC 7/8
With #m : 12 for LDPC 1/2, 23 for LDPC 2/3 , 78 for LDPC 7/8
Keywords : PermanentTransportStatus
0: when the frame synchronizer of the CADU layer is unlock, the counters of the Transport layer are set to 0 and
not updated
1: when the frame synchronizer of the CADU layer is unlock, the counters of the Transport layer are updated.
Default setting : 0
Default setting : 0
0: in raw data mode, data are recorded even if the demodulator is not locked
1: in raw data mode, data are recorded only if the bit synchronizer of the demodulator is locked
Default setting : 0
1: disable the DMX table from the All Components table (refer to the document STI 100013 HDR )
Default setting : 0
Display the current CORTEX configuration and status from the monitoring tables transmitted by the SPS,
Reset the TCP-IP connections to the CORTEX (close all TCP-IP connections to a given port or close all
connections to the CORTEX). This function is password-protected.
Product-specific functions : telemetry Quick Look (CORTEX CRT), satellite commanding and ranging
(CORTEX CRT), etc…. For more details, see next sections.
The MCS can be installed in any PC workstation using and having 32 Mbytes of RAM or more. The MCS and SPS
communicate via an Ethernet link under TCP-IP.
Some of the TCP-IP ports of the CORTEX (monitoring, logging, etc…) accept simultaneous connections of several
clients while other ports (Control, Reset, etc…) accept only one connection at a time. For more details concerning
the Ethernet interface, refer to :
CORTEX Series TCP-IP Ethernet interface (reference STI 100013) : Ethernet ICD common to all CORTEX
products),
CORTEX XXX TCP-IP Ethernet interface : product-specific Ethernet interface extension, where XXX is the
product extension name. Example : STI 100013_CRT is the CORTEX CRT Ethernet ICD, STI 100013_HDR is
the CORTEX HDR Ethernet ICD, STI 100013_ACS is the CORTEX ACS Ethernet ICD, etc….
The MCS is built around an MCS kernel (supporting multiple CORTEX products such as the CORTEX CRT,
CORTEX HDR, CORTEX ACS, CORTEX RTR, etc…) and a product-specific SPS software layer which is
automatically identified when the MCS connects to the CORTEX SPS.
An MCS Document contains the whole set of configuration parameters that have been previously stored on the
disk under file extension .MCS.
The MCS document also contains the name or Ethernet address of the CORTEX whose configuration has been
saved in the MCS document. This name or address is displayed on top of the graphical window.
A default MCS Document (cortex-nt.mcs) is loaded by the MCS when the CORTEX is started; it can be then used
to re-configure the machine. A copy of this file (MCS Table) is maintained in RAM and is updated whenever the
CORTEX configuration is changed by the MCS operator. The MCS Table can be manually saved to the MCS
Document on the hard disk by MCS Operator.
Additional MCS Documents can be created at will by the operator. A set of MCS Documents (common satellites
configuration) is available on the hard disk C:\Program Files\IN-SNEC\crtxMcs\DefaultConfig).
A copy of the original MCS files (those installed from the CORTEX reference CD-ROM) is available in directory
C:\Program Files\IN-SNEC\crtxMcs\DefaultConfig_ref. These files are in read-only mode. They can be copied to
the working directory (C:\Program Files\IN-SNEC\crtxMcs\DefaultConfig) if necessary (remove the read-only
protection on the copies).
MCS documents are binary files. They cannot be displayed on the screen or printed out, except if the MCS
software package is installed in a remote PC with printing capability (PRINT PREVIEW & PRINT commands).
cortex-nt.mcs
IP address
Configuration
Parameters only
(see STI100013)
Global status
setting
TM Quick look
setting
1
CTX table
MCS table
IP address
2 Configuration
Parameters
Configuration 3 TCP-IP And
Parameters GUI IP address Status
& Global status
4
shhjdssdh
shhjdssdh
shhjdssdh
kjdsk
kjdsk
kjdsk
wks
wks
wks
,jhkjhsh
,jhkjhsh
,jhkjhsh
kjshchsckd
kjshchsckd
kjshchsckd
lisclslk
lisclslk
lisclslk
lkdjlkj
lkdjlkj
lkdjlkj
M&C Clients
(see STI100013) shhjdssdh
shhjdssdh
kjdsk
kjdsk
wks
wks
,jhkjhsh
,jhkjhsh
kjshchsckd
kjshchsckd
lisclslk
lisclslk
lkdjlkj
lkdjlkj (see STI100013)
shhjdssdh kjdsk wks ,jhkjhsh kjshchsckd lisclslk lkdjlkj
shhjdssdh kjdsk wks ,jhkjhsh kjshchsckd lisclslk lkdjlkj
TM Quick look
? shhjdssdh
shhjdssdh
kjdsk
kjdsk
wks
wks
,jhkjhsh
,jhkjhsh
kjshchsckd
kjshchsckd
lisclslk
lisclslk
lkdjlkj
lkdjlkj
setting
OK / DIFFER
5 CORTEX SPS
IN-SNEC MCS
STEP 1 : When the Monitoring & Control Software (MCS) is started, it opens the default MCS Document (program
argument) c :\Program Files\In-snec\crtxMcx\cortex-nt.mcs on the disk and makes a copy in RAM (MCS Table). If
the default MCS Document is not found the following warning message is displayed :
STEP 2 : The MCS connects to the Monitoring port of the CORTEX and starts monitoring the machine. If the
MCS fails to open the connection, the MCS Login window indicates Disconnected and a warning message is
displayed.
STEP 3 : Once the connection to the CORTEX has been established, the configuration parameters, the status
and alarms received from the connected machine are refreshed in real time on the GUI. Configuration
commands entered at the GUI are executed and the MCS Table refreshed accordingly.
STEP 4 : The MCS permanently compares the configuration parameters from the MCS Table to the ones
displayed on the GUI.
STEP 5 : If the GUI strictly reflects the contents of the MCS Table, the MCS control status at the bottom of the
Top Level window displays :
Else (the CORTEX has been reconfigured by a remote M&C client or the MCS document has not been saved
properly prior shutting down the machine) the MCS control status is changed to :
Click on icon to update the MCS Table from the configuration parameters on the GUI (CTX table).
Enter the IP address or name of the CORTEX unit and click on (or click on CONNECT). Once the
monitoring connection is established, the MCS starts monitoring the unit and initializes the contents of the
MCS Table (IP address or name of the unit included). The MCS control status is set to ,
indicating that the contents of the MCS Table strictly matches the configuration of the unit. The MCS Table is
automatically updated every time the Operator modifies the setting of the unit from the MCS on which the
M&C session has been started (the MCS control status remains to ).
The MCS control status automatically turns to if any remote Monitoring & Control system modifies
the configuration of the unit.
For saving the MCS Table to an MCS Document on the disk, see next section. Note : multiple M&C sessions
can be simultaneously started from the MCS.
If the MCS Table has never been saved to the disk, click on FILE → SAVE or FILE → SAVE AS and either
confirm the name proposed in the dialog box or enter another name.
If the MCS Table has already been previously saved to the disk, click on FILE → SAVE to save it again to the
same MCS Document or click on FILE → SAVE AS to save it to another new or existing MCS Document.
Click on FILE → OPEN and select an MCS Document in the proposed list. The selected MCS Document is
copied to an MCS Table in RAM.
Click on to reconfigure the CORTEX from the new MCS Table. The MCS control status is changed to
The MCS login window allows to connect or disconnect to the Cortex SPS and check the connection status. The
connection buttons are disabled if no machine name or IP address is provided in the host identification zone. Start
entering the machine name or IP address and the connection button will automatically be enabled.
Connect the MCS to the SPS by clicking on or by pressing the RETURN or ENTER key. If the host machine
accepts the connection, the disconnection button is enabled and the connection status turns to .
Otherwise, a connection error message appears on the screen.
After the connection is established the host identification zone becomes gray. Changing the IP address is no more
Next sections describe the commands en status available from the MCS window after the connection is
established.
The tabs allow to know the status of the connection and host CORTEX :
Another option allows to display on the tab the name of the host machine or MCS Document (menu
PREFERENCE).
The following commands are common to all of the CORTEX products. For product specific commands, see
next section.
FILE NEW : Create a new MCS Document to open a new M&C session.
OPEN : Open an M&C session from an existing MCS Document on the disk
CLOSE : Close the current M&C session and document. If the document is not saved, a
messages proposes to save it. The workspace is closed too.
SAVE : Save the active MCS Document to the original document on the disk.
SAVE AS : Save and rename the active MCS Document to the disk.
PRINT : Print out the contents of the active MCS Table.
PRINT PREVIEW : Display the contents of the active MCS Table.
PAGE SETUP : Change the printer and printing options.
EXIT : Exit the MCS.
<file_list > : Select an existing MCS document from the list.
CONNECT CONNECT TO : Connect the MCS to the monitoring port of a CORTEX. Command
available only if an IP address is provided in the host identification zone.
DISCONNECT : Close the monitoring connection to the CORTEX.
HELP ABOUT : Display the versions of the MCS kernel, products and plugins.
Update the MCS Table from the real configuration of the connected CORTEX.
Toggle command : open/close the connection to the Control port (see section 4.3.6.3).
Restart signal acquisition by the Demodulator. Turns to yellow when the Demodulator is locked.
Turns to gray when the Demodulator is unlocked (see SPECIAL COMMAND - RESTART IFR).
Reset the BER counter for the active Demodulator Unit window or
Restart the status counter for the active Data Processing Unit window.
Close the TCP-IP connection for the active window. Turns to red when the connection is active and
to gray when the connection is closed (see SPECIAL COMMAND - CLOSE TCP)
In Acquisition mode, close all open data acquisition processes to toggle in Configuration mode.
Invert one bit in the simulated data pattern (pseudo-random pattern or file). Bit inversion takes
place before convolutional encoding (if enabled).
Allows the setting of a same parameter in all the active channels from a single window.
OK/DIFFER mode : Standard (Std), Protected (Prot) or Automatic (Auto). See section 4.3.6.4)
Alarm status :
OK (gray background).
Alarm (red background) if any CORTEX component is in alarm. Detailed information on the alarm is
available at the GUI.
Temperature (red background) if any temperature monitored by the IPMIMonitor tool exceeds the
alarm threshold (see section 5.3.2).
Date and time from the built-in time code reader : . Yellow background if the time
decoder is unlocked or in flywheel mode; gray background if the decoder is locked.
Configuration changes (by the MCS Operator or by any remote Control client), status and alarms are refreshed in
real time on the GUI.
Enter the Control password. Default setting at delivery : no password. Control pushbuttons are changed to :
3. closes the connection to the Control port and returns to the monitoring mode. The pushbutton is
changed to .
To open a connection to the Control port, click on EXECUTE OPEN CONTROL PORT. To close the connection
to the Control port, click on EXECUTE CLOSE CONTROL PORT.
New parameter values entered by the Operator are stored in the MCS Table and when the APPLY button is
pressed, the CORTEX is re-configured from the MCS Table and the MCS control status indicates .
This message is to warn the Operator that the CORTEX will be re-configured from the MCS Table and that one or
several parameters, else than those modified by the Operator, will be changed, thus affecting other remote
CORTEX Operators. Click on NO to abort or YES to re-configure the machine.
The MCS is built around an MCS kernel (supporting multiple CORTEX products such as the CORTEX CRT,
CORTEX HDR, CORTEX ACS, CORTEX RTR, etc…) and a product-specific MCS software layer.
The header of the above window shows the version of the MCS kernel.
The inner window shows the version of the MCS software layer specific to the CORTEX HDR product.
To change a password :
2. Click on CHANGE,
Notes :
1. The Control password does not protect the CORTEX from re-configuration by remote Control Clients.
2. The TCP-IP password does not protect from reset commands issued by remote Reset Clients.
Click on and enter the password enabling the Load and Save commands.
Click on Save to capture the current CORTEX configuration and save it to an existing or a new .CTX
Document on the disk (maximum name size : 16 characters) :
The last loaded or saved CTX Document is identified in the upper part of the window by its ID number and name.
A configuration status indicates whether the current configuration of the unit matches the contents of the last
loaded or saved CTX Document ( ) or not ( ).
The CTX Document name can be modified only with the Save Command or by editing the NameTable.TXT file
before starting the Signal Processing Software (SPS). If a CTX Document is not available (not created or
damaged), the assigned name is blank. The Configuration Names table is transmitted over the LAN on reception
of a monitoring request with Component code 200H. This table is not part of the tables that can be monitored under
an All components tables monitoring cycle.
This windows allows to display and to load a configuration file (MCS file) previously recorded inside the directory:
c:\Program File\In-Snec\CrtxMcs\UserConfig or d:\ZDS\Data\HDR\CrtxMcs\UserConfig (for Windows 7) by the
user.
Note that these MCS configuration files can be also remotely loaded using a special TCP/IP command.
Click on (Upper toolbar of the GUI) to access the User Configuration Command window :
Click on “Refresh List” to refresh the list of the available MCS files previously recorded by the user inside the
directory: …\CrtxMcs\UserConfig.
The number of the selected file appears inside the “Selected” box. The status “Last Conf” is equivalent to the
OK/Differ status of GUI.
4.3.12.1 Monitoring
4.3.12.1.1 MONITORING RATE
To change the time interval between two consecutive monitoring cycles by the MCS software :
Example : for a monitoring request every four seconds, enter FA0 (in hexadecimal) or 4000 (in decimal). Minimum
value : 1F4H = 500D (monitor the equipment twice per second).
Keyword : SW Mask
Enter 0 (ignore SW bits corresponding to bits set to 1 in the mask) or 1 (ignore SW bits corresponding to bits set
to 0 in the mask).
Default setting : 0.
Depending on the Operating System, the Cortex HDR software and files can be found in different directories. The
paths of these different directories are given in the following paragraphs.
To improve security, with Windows 7, the Cortex user does not have access to C drive anymore. The
configurations files have been moved to D drive.
- Network Connections (Desktop – Network Connections): Offers the possibility to modify the IP address,
subnet, gateway of the Cortex Unit.
- Rename Workstation Utility (Start Menu – All Programs – Rename Workstation): Offers the possibility to
change network name of the Cortex Unit.
Procedure: Enter the new network name and click on rename (Cortex unit will restart
automatically with its new name).
- IPMI Monitor (Start Menu – All Programs – Tools – IPMIMonitor): Offers the possibility to view
motherboard integrated sensors.
- Problem Step Recorder (Start Menu – All Programs – Tools – psr): Tool to makes a visual and text-
based documentation of everything that happens on the Cortex Unit while you’re recording.
- Regedit (Start Menu – All Programs – Tools – Regedit): Offers the possibility to modify the Cortex
application registry (HKEY_LOCAL_MACHINE\SOFTWARE\IN-SNEC).
IS RED-MARKED WITH THE NAME OF A CORTEX « UNIT ». THIS MARK ALLOWS TO LOCATE THE
Demodulation
Time TIME Unit
PHYSICAL DVBS2 / SCCC M&C
LAYER
Miscellaneous CONFIG
BER DMU BER M&C
Project-specific PROJECT
DECODING Data decoders M&C
Test Modulation
Unit PCM Test data M&C
Data Playback
Unit FILE Playback data selection
TCP-IP
CLIENTS
ENGINEERING
DISPLAY
The following window appears on the screen after the MCS is connected to the SPS (note that the number of
functional units depends on the selected configuration menu and available licenses) :
Demodulator locked if the LED is green (Carrier PLL and Bit Synchronizer locked - DMU) or unlocked if the
LED is unlit (gray background). The LED turns to red if a serious hardware or software (license) problem is
detected on the demodulation chain.
Frame synchronizer status: green LED when locked, amber LED in flywheel mode, unlit LED when unlocked
(searching). The LED turns to red if a serious hardware or software problem is detected on the demodulation
chain.
Recorder status: green LED when recording in progress, unlit LED when recording off. The LED turns to red if
a problem is detected on the recording chain.
Playback status: green LED when playback is operating, unlit LED when playback is off The LED turns to red if
a problem is detected on the playback function.
Number of clients connected to the Spectral port (SPA) and Vector port (VEC) : none (left), one (middle) or
more than one (right).
IF inputs status:
Reflects the IF input selection for both demodulators with N for normal input, and A for Alternate input
In normal conditions, this LED must be green. The LED turns to red if a serious hardware problem (Test
Modulator failure) or software problem is detected.
The Global Engineering window displays dynamically the current configuration and status of the Cortex HDR in a
single window. The following figure gives an example.
The number of clients connected to each TCP-IP port is displayed in the above window. Each Reset button allows
closure of all the TCP-IP sockets connected to the associated port. The Reset All pushbutton allows closure of all
connections to all ports.
The TCP-IP reset function is password protected: click on and enter the TCP-IP password. Default setting at
delivery : no password. To change the TCP-IP password, see Section 4.3.8).
XL
Figure 72 : CORTEX « Time » Window
4.5.3.2.1 CONTROL
LEAP YEAR Leap year programming (365 or 366 days). Select Yes or No (ensure the external
time code generator setting is identical).
CURRENT OFFSET Configuration parameter and status. Allows to enter a time offset for immediate
application and to read the current time offset. Expressed in seconds (signed
value).
The current time offset is added to the time delivered by the internal Time Code
Reader, for time tagging telemetry frames, range measurements, etc...
DATE OF NEXT At this date, Next Offset 1 will replace the current offset. Expressed in seconds
OFFSET 1 with January 1st 00:00:00 = 0.
NEXT OFFSET 1 This time offset, expressed in seconds (signed value), will become effective
when the current date matches Date of Next Offset 1. See note 1.
DATE OF NEXT At this date, Next Offset 2 will replace the current offset. Expressed in seconds
OFFSET 2 with January 1st 00:00:00 = 0.
NEXT OFFSET 2 This time offset, expressed in seconds (signed value), will become effective
when the current date matches Date of Next Offset 2. See note 1.
Note that if Date of Next Offset 1 = Date of Next Offset 2, then Date of Next
Offset 2 will be ignored (no offset update : priority to Offset 1).
TIME CODE Expected time code (IRIG-B or NASA-36) or NTP if expected time from an
external NTP server (refer to § 4.4.3.2.3)
Note 1 : At boot up, the current offset value is set to the latest value programmed by the Operator (automatic
adjustment of Current Offset from Next Offset 1 or Next Offset 2 is not memorized by the machine).
4.5.3.2.2 MONITORING
Two parameters are available for the set-up: the address of the server and the time refresh period (Server name or
IP address, Adjustment period in seconds). The time is periodically updated when the HDR is set in
Configuration mode.
These set-up parameters are not directly accessible through the GUI. The setup is done using the tool “uihm.exe”.
This tool is available in the directory C:\Program Files\ZDS\uihm for Windows 7 otherwise C:\Program Files\IN-
SNEC\uihm.
After having started uihm.exe and connected it with the SPS software, the NTP server parameters are available
and can be set following, in the “uihm” window, the path Commands -> Hardware Configuration -> NTP
Configuration:
If data time-tagging on the CORTEX require to be aligned on UTC, then the leap second changes can be made
either on the external Time Code Generator or on the CORTEX.
If the change is made on the Time Code Generator, the Time Code Reader in the CORTEX will loose lock for a
short period of time (typically : 10 seconds) at the very moment the time information, which modulates the time
code signal, is updated.
Ensure that parameters Current Offset, Next Offset 1 and Next Offset 2 are set to 0 to avoid taking twice into
account the leap second change.
Should it be mandatory to keep the Time Code Reader permanently synchronized (or if the external Time Code
Generator does not feature leap second entry), the leap seconds entry must be done on the CORTEX instead of
the external Time Code Generator.
st
a positive leap second change (new value = 11) has been notified for July 1 , 00 h, 00 mn, 00 s
st
the CORTEX is started before June 30 , with all time offsets set to 0.
Current Offset = 10
Next Offset 1 = 11
st
3. On July 1 , 00 h, 00 mn, 00 s, check that the Current Offset is automatically set to 11 and that the time-tags
st
are updated accordingly. Note : 15 638 400 = July 1 , 00 h, 00 mn, 00 s = 181 days x 86400.
Next Offset 1 = 11
TIME COUNTING
)
lay
sp
di
s+
tag
e-
t im
ta
da
N e(
tim e
cte
d od
re ec
C or tim
X d ed
co
De
TIME
N seconds before end of year, force corrected time to 0 for starting new year (Offset = - X seconds)
The IRIG-B and NASA-36 time codes are serial time format with the time-of-year coded in Binary Coded Decimal
(BCD) notation as days, hours, minutes and seconds. Years are not coded and the day counter is reset every
st
January 1 , 00 h, 00 mn, 00 s. Time parameters can be programmed so that the day counter will not be restarted
every year.
Example :
Next Offset 1 = 31 536 000 (year 1998 = 365 days = 31 536 000 seconds)
st
2. On January 1 , 1999 at 0 AM, check that the Current Offset is set to 31 536 000 and that the time-tags are
updated accordingly (365 days are automatically added to the time-tags). The day counter is equal to 366.
3. In the course of 1999, enter Next Offset 1 = 63 072 000 (year 1999 = 365 days = 31 536 000 seconds).
st
4. On January 1 , 2000 at 0 AM, check that the Current Offset is set to 63 072 000 and that the time-tags are
updated accordingly. The day counter is now equal to 731.
5. Each following year, increment parameter Next Offset 1 by the number of seconds of the current year.
Example :
st
2. On January 1 , 1999 at 1 AM, (3600 seconds after boot up) check that the Current Offset is set to 31 536 010
and that the time-tags are updated accordingly. The day counter is now equal to 366.
st
4. On January 1 , 2000 at 0 AM, check that the Current Offset is set to 63 072 010 and that the time-tags are
updated accordingly. The day counter is now equal to 731.
4.5.3.4.1 CONTROL
UNIT MOUNTED Identification of the mounted units in the current configuration. A green LED
indicates that the unit is mounted and enabled. A unit can be enabled or disabled
by clicking in the associated selection box:
DMU: Demodulator Unit
DPU: Data Processing Unit
DRU: Data Recording Unit
TSTU: Test Modulator Unit
PLBK: Playback Unit
MONITORING FLOW ID Identification of the monitoring data flow. This value is reported in all TCP-IP
messages transmitted over the Monitoring port (MON). Enter any hexadecimal
value from 0 to FFFFFFF. The Flow ID value in the incoming monitoring
LOGGING FLOW ID Identification of the logging flow. This value is reported in all TCP-IP messages
transmitted over the Logging port (LOG). Enter any hexadecimal value from 0
to FFFFFFFF.
CABLE Determines the evaluated loss (in dB) due to cables among the propagating path.
COMPENSATION This value is reported in the calculation of the compensating filter’s coefficients.
Enter any value from 0 to 12 (Option)
CONFIGURATION The easier way to configure the unit is to load the selected MCS file (refer to
MENU paragraph 4.3). As soon as the MCS file is loaded, the unit can automatically
load the firmware corresponding to this MCS file.
The Configuration Window allows the User to force the selection of a basic
menu and gives also indications about the status of the selection an loading
operations.
In manual mode (Mode: On Request or On Accept) the operator can input in the
field: Menu Nbr the numbers of a basic menus (Demodulator, test Modulator
and the optional Extension board when present). If the operation mode is set to
On Accept, the loading will be effective only after having clicked the button
Accept Request Menu
In automatic mode (Automatic or Automatic with Accept) the basic menu
corresponding to the current configuration is selected automatically and its
number is displayed in the Recommended status field. If the operational mode is
set to Automatic with Accept, the loading will be effective after having clicked
the button Accept Requested Menu.
In all cases the number of the current and active basic menu is displayed in the
Active status field.
A status field indicates if the menu is being loaded or has been loaded and is
ready to operate. This status is displayed in the Configuration Window and in
the upper right corner of the Global Window:
For detailed information on the current configuration and the possible basic menus, click on icon to acces
the help windows:
The help windows recall inside a single table the capabilities of each basic hardware menu available for the
demodulator, the test modulator and the optional extension board.
The tables indicate also which basic menu(s) is or are authorized for the current loaded configuration: green or
yellow columns (green: full compliance between the menu and the loaded configuration, yellow: full compliance
only for the demodulation channel #1). For the other non authorized menus, a red stamp is applied on the
function(s) or performance(s) which do not match what is required by the loaded configuration.
4.5.3.4.2 MONITORING
4.5.3.5.1 CONTROL
4.5.3.5.2 MONITORING
STATUS 1 to 32 32 project-specific status & alarms. (project-specific status and alarms are
described in Annex 5).
An other way to check the availability of the functionalities is to position the mouse cursor on the Function status in the
different windows
Figure 81 : Demodulator : Global Window for QPSK Modulation + Raised Cosine Filter
GMSK Modulation :
SOQPSK Modulation :
UQPSK Modulation :
8PSK Modulation :
16QAM Modulation :
16APSK Modulation :
32APSK Modulation :
64APSK Modulation :
4.5.4.1.1 CONTROL
Parameters in this window are described in DMU.
4.5.4.1.1.1 IF PROCESSING
INPUT FREQUENCY Expected IF 520 to 920 MHz (720 MHz IF input) or 900 to 1500 MHz (1.2 GHz IF
input). expressed in Hz. Enter any value in float or real format. Example: for 720 MHz,
type: 72e+7 or 720000000. The programmed value is always displayed in float format.
Resolution step : 32-bit float format.
ACQUISITION RANGE Carrier acquisition peak range (from the expected carrier frequency) and PLL tracking
range. Expressed in Hz. Enter any value from 10,000 to 1e6. Select a value that takes
into account the frequency offset in the worst operational conditions. (Doppler,
frequency uncertainties, etc.).
VCM - 8PSK/OQPSK Enable the automatic switch function between 8PSK and OQPSK demodulation. This
function is only available with OQPSK and 8PSK modulation. In this mode, the
programmed symbol rate is constant.
BIT RATE Telemetry bit rate. Expressed in bps. Enter any value from 1e6 to the maximum
admissible bit rate (license, modulation and firmware are menu dependent)
OR
Important : if the data are convolutionally encoded, enter the bit rate at the Viterbi
SYMBOL RATE
decoder input (bit synchronizer output).
In DVB-S2, SCCC and VCM modes, the Bit Rate is replaced by the Symbol Rate
PCM CODE Telemetry PCM coding technique : NRZ-L/M/S, DNRZ, Bi-P-L/M/S, NRZ-M Merge
Important : if NRZ-M Merge is selected, the NRZ-M to NRZ-L decoding is performed
after the merging of the data coming from I and Q. If NRZ-M is selected the decoding
is performed separately on I and Q before data merging.
Note: DPU A and DPU C are connected to DMU 1. DPU B and DPU D are connected
to DMU 2
Note: with the specific basic menu # 16, all DPU (up to 8) are connected to the only
available demodulator DMU 1
Note: DPU A and DPU C are connected to DMU 1. DPU B and DPU D are
connected to DMU 2
EBN0 MIN AUTO Selection of the automatic adjustment of the acquisition threshold.
If not selected , a value must be set from –3 to 10 dB, with unit: 1 dB
In OQPSK mode, the following additional parameters appear at the GUI for controlling the I/Q delay
compensation :
Important : in UQPSK (AQPSK, AUQPSK, AUSQPSK) mode, parameters BIT RATE, PCM CODE and
OUTPUT CLOCK described here above are for the I Channel. The following additional parameters appear at the
GUI for controlling the Q Channel :
BIT RATE Q Telemetry bit rate for the Q Channel. Expressed in bps. Enter any value from
1e6 to 480.e6 (model dependent)
In AQPSK mode, the I Channel bit rate is supposed to be higher or equal to the
Q Channel bit rate.
I/Q RATIO Power ratio between I Channel & Q Channel in dB : from 0 to 100
PHASE ROTATION Select CCSDS (Counter Clock Wise) or Inverted (Clock Wise). (see section
3.6.2.4)
8PSK MAPPING Select Natural, Natural2, Gray1, Gray2, Gray3, Gray4, Gray5 or Gray6
mapping (see section 3.6.2.4)
In DVB-S2 and SCCC modes, the demodulation mode is controlled from the Physical Layer window.
In Multi DPU mode, the following additional parameter appears at the GUI:
DPU MAP Select 0 or 1 for th emulti-DPU processing mapping (refer to paragrah 3.4.13)
VECTOR Identification of the Vector Analysis data flow. This value is reported in all
TCP-IP messages transmitted over the Vector Analysis Data port (VEC). Enter
any hexadecimal value from 0 to FFFFFFFF
ROLL-OFF Filter roll-off factor: enter any value from 0.1 to 1.0.
FIR CUSTOM NB FIR custom Number : enter any value from 1 to 1000.
ASYM Select asymmetrical FIR coefficients, else symmetrical FIR coefficients are
applied.
COMP Select complex FIR coefficients, else real FIR coefficients are applied
(dependent of the other FIR characteristics selections).
ODD Select odd FIR coefficients, else even FIR coefficients are applied.
4*SR Select the sample rate of the FIR filter as 4 time the symbol rate, else 2 time the
symbol rate is applied.
CMA / LMS Select the algorithm of the DEAF function. It is recommended to use the LMS
algorithm for the reception of frequency non symmetrical signals.
LPF Select additional Low Pass Filter +/- 128 MHz bandwidth
4.5.4.1.2 MONITORING
Status and alarms in this window are described in DMU
BIT SYNC Q Bit Synchronizer status for Q Channel (for UQPSK configuration) :
Locked green
Unlocked red
VITERBI DECODER Viterbi decoder status for I & Q Channels (logical AND of the VITERBI DECODER
I and VITERBI DECODER Q status in case of dual Viterbi configuration) :
Locked
Unlocked
FUNCTIONS One or more parameter values do not match the installed licenses, or firmware
capabilities :
Functions (green) : OK Move the cursor to the status field to see the lists
of available capabilities
Warning (red) : the requested configuration is not supported. Move the
cursor to the status field to check which parameter is incorrect (Tool Tip).
IF LEVEL IF carrier level in dBm. The nominal AGC range is from -10 to -50 dBm.
Degraded measurement if the level of the received signal is not within these limits.
CARRIER OFFSET Offset from the expected IF carrier frequency (real frequency - expected
frequency). Expressed in Hz. This value depends both on the oscillator drift (on-
board and ground equipment) and on the Doppler conditions.
BR OFFSET Offset from the expected bit rate (real BR - expected BR). Expressed in bit per
second.
OR
In DVB-S2 and SCCC modes, the Bit Rate Offset is replaced by the Symbol
SR OFFSET
Rate Offset
Eb/No Energy per bit in a 1-Hz noise bandwidth, measured at the bit synchronizer input.
Expressed in dB.
OR
In DVB-S2 and SCCC modes, the Eb/No is replaced by the Es/No (Es: Energy
Es/No
per symbol
In OQPSK mode, the following additional status appears at the GUI for monitoring the I/Q delay compensation :
Note 1 : The I/Q shift compensation applies to Q channel (after IF to base-band down-conversion). As the OQPSK
demodulation is ambiguous, the sign of the status changes in accordance with the demodulation ambiguity.
Note 2 : In fixed mode, as the demodulation is ambiguous, both signs are tested and an error estimation is done in
both cases. If the best error value is inferior to a certain threshold, the automate will be locked on this sign. If the
two errors are not acceptable (i.e. if the programmed compensation does not reflect the real delay), the automate
will indefinitely change the sign of the compensation, which is reflected by the sign change of this status. In this
unstable configuration, the I/Q shift value must be refined.
Important : in UQPSK (AQPSK, AUQPSK, AUSQPSK) mode, status BR OFFSET, Eb/No and BIT SYNC
described here above are for the I Channel. The following additional status appears at the GUI for monitoring the
Q Channel :
BR OFFSET Q Offset from the expected bit rate for the Q Channel (real Q Channel BR –
expected Q Channel BR). Expressed in bit per second.
Eb/No Q Energy per bit in a 1-Hz noise bandwidth, measured at the bit synchronizer input
for the Q Channel. Expressed in dB.
Figure 95: Demodulator : Physical layer window for SCCC and DVB-S2 standard
4.5.4.2.1 CONTROL
Parameters in this window are described in DMU.
VCM Enable or not the VCM mode: Automatic detection of the current modulation
RATE
PILOTS If enabled, indicates that the received physical frames are with pilots
SHORT FRAME If enabled, indicates that the received physical frames are short frames (only
with DVB-S2 standard).
PL SCRAMBLING If enabled, indicates that the received physical frames are randomized.
N-APSK G1, G2, G3 Set the radius ratios of the mapping for the different available APSK modes
(16APSK, 32APSK and 64APSK)
4.5.4.2.2 MONITORING
Status and alarms in this window are described in DMU
DROP OUT Number of drop out events at the physical layer level.
ACM NB Detected current ACM number: Modulation and Coding format (refer to DVB-S2
and SCCC standard).
MODULATION Detected current modulation mode (refer to DVB-S2 and SCCC standard).
CODING RATE Detected current coding rate (refer to DVB-S2 and SCCC standard).
PILOT Presence or not of pilot inside the current received frame (refer to DVB-S2 and
SCCC standard).
SHORT FRAME The received frames are short frames or not (refer to DVB-S2).
4.5.4.3.1 CONTROL
Parameters in this window are described in DMU.
OPERATING MODE BER measurement mode (simulated data for BER analyzis) :
Off BER measurement stopped (for reset purposes)
File Simulated data from a file on the disk (note 1)
PseudoDxx Pseudo random data, using from PN generator xx
(where xx = 7, 10, 11, 15, 23 or 31. See Section 3.6.2.1)
Note : In File mode, the BER is computed by comparing the original frame to the reconstructed frame from the frame
synchronizer. The BER value is not significant if the frame synchronizer is not correctly configured and locked.
FILE NUMBER File number for BER in file mode : enter any value from 1 to N for each
associated DPU.
BER COUNTER Total number of bits to process for BER measurement in Pseudo mode
Resolution step : 65536 bits. In File Mode, Infinite accumulation.
(upper banner)
4.5.4.3.2 MONITORING
Status and alarms in this window are described in DMU
NUMBER OF ERROR I + Q Number of bits in error since the BER counter was reset.
NUMBER OF ERROR I Number of bits in error since the BER counter was reset.
NUMBER OF ERROR Q Number of bits in error since the BER counter was reset.
NUMBER OF ERROR DPU N Number of bits in error since the BER counter was reset for DPU #N
Note : From this window, by clicking on “Show DPU Details”, it is possible to view the BER values computed at the
output of each DPU associated with the DMU and the used BER mode.
BPSK Modulation :
Figure 99 : Demodulator : Decoding Window for QPSK & OQPSK Modulation (Viterbi Single)
Figure 100 : Demodulator : Decoding Window for QPSK & OQPSK Modulation (Viterbi Dual)
8PSK Modulation :
4.5.4.4.1 CONTROL
Parameters in this window are described in DMU.
VITERBI DECODER Viterbi decoder setting for the I Channel in BPSK or UQPSK (AQPSK, AUQPSK,
AUSQPSK) mode or for both I & Q Channels in QPSK, OQPSK (SQPSK) mode :
Off Viterbi decoder disabled
G1 G2 Inv Viterbi decoder enabled with G2 inverted. G1transmitted first
(CCSDS recommendation)
G1G2 Viterbi decoder enabled with G2 normal. G1 transmitted first.
G2 InvG1 Viterbi decoder enabled with G2 inverted. G2 transmitted first
G2 G1 Viterbi decoder enabled with G2 normal. G2 transmitted first
Refer to the CCSDS recommendations for “G2 Normal/ G2 Inverted” definition.
VITERBI Viterbi puncturing setting for I Channel in BPSK or UQPSK (AQPSK, AUQPSK,
PUNCTURING AUSQPSK) mode or for both I & Q Channels in QPSK, OQPSK (SQPSK) mode :
Off Viterbi puncturing disabled
ON ( registry) Puncturing scheme defined in registry.
2/3 2/3 Viterbi
¾ (conv.1) 3/4 Viterbi (convention 1)
¾ (conv.2) 3/4 Viterbi (convention 2)
4/5 4/5 Viterbi
5/6(conv.1) 5/6 Viterbi (convention 1)
5/6(conv.2) 5/6 Viterbi (convention 2)
6/7 6/7 Viterbi
7/8 (conv.1) 7/8 Viterbi (convention 1)
7/8 (conv.2) 7/8 Viterbi (convention 2)
1/4 Esrin 1/4 Viterbi (ESA / ESRIN type)
VITERBI DECODER Q Viterbi decoder setting for Q Channel in UQPSK (AQPSK, AUQPSK, AUSQPSK)
mode :
Off Viterbi decoder disabled
G1 G2 Inv Viterbi decoder enabled with G2 inverted. G1transmitted first
(CCSDS recommendation)
G1G2 Viterbi decoder enabled with G2 normal. G1 transmitted first.
G2 InvG1 Viterbi decoder enabled with G2 inverted. G2 transmitted first
G2 G1 Viterbi decoder enabled with G2 normal. G2 transmitted first
Refer to the CCSDS recommendations for “G2 Normal/ G2 Inverted” definition.
VITERBI Viterbi puncturing setting for Q Channel in UQPSK (AQPSK, AUQPSK, AUSQPSK)
PUNCTURING Q mode :
Off Viterbi puncturing disabled
ON ( registry) Puncturing scheme defined in registry.
2/3 2/3 Viterbi
3/4 (conv.1) 3/4 Viterbi (convention 1)
3/4 (conv.2) 3/4 Viterbi (convention 2)
4/5 4/5 Viterbi
5/6(conv.1) 5/6 Viterbi (convention 1)
5/6(conv.2) 5/6 Viterbi (convention 2)
6/7 6/7 Viterbi
4.5.4.4.2 MONITORING
4.5.4.4.2.1 UPPER BANNER
See section 4.5.4.1.2.1.
BER TCM Bit Error Rate (must be 0 if no error detected). Important : the BER is
analyzed at the bit synchronizer output (before TCM decoding)
BER Viterbi Bit Error Rate (must be 0 if no error detected). Important : the BER is
analyzed at the bit synchronizer output (before Viterbi decoding)
In the Demodulator Spectrum window, click on Enable. A TCP-IP connection is opened to the Spectrum
port (SPA). To close the connection, click on Disable or click on icon or exit the Spectrum window.
In the Demodulator Spectrum window, click on Vid Avg En.. The averaging mode display is selected. To
return to the non averaging display mode , click on Vid Avg Dis..
Adjust the signal level scale (vertical toolbar) from 0.1 to 10 dB/division.
Clicking in the spectrum, with the left key of the mouse, will set a red marker. The signal frequency and
level at this point is displayed in the window entitled Center Frequency Selection (F1 marker).
To center the spectrum on frequency F1 :
- Click on CONFIG,
- Set the red marker with the left key of the mouse,
- Click on F1 marker,
- Click on APPLY.
Clicking in the spectrum, with the right key of the mouse, will set a green marker. The signal frequency and
level at this point are displayed in the next window under F2 marker. To center the spectrum on frequency
F2, follow the above procedure using F2 marker.
The frequency and level offsets between markers F1 and F2 are displayed in a separate window :
BPSK Modulation :
8PSK Modulation :
16QAM Modulation :
16APSK Modulation :
32APSK Modulation :
In the Demodulator Global window (see section 4.5.4.1.1.1), set parameter Mode to Demod.
In the Demodulator Vector window, click on Enable. A TCP-IP connection is opened to the Vector port
(VEC). To close the connection, click on Disable or click on icon or exit the Vector window.
Vector display :
Vectors are transmitted to the local MCS in bursts (TCP-IP packets) of 256 vectors.
In Single mode, the display is refreshed burst by burst, with all vectors displayed.
In Cumulative mode, the display is refreshed every 20 bursts only.
In Average S mode, the MCS displays the average vector value for the received burst of vectors in each
I/Q quadrant.
In Average C mode, the MCS displays the average vector value for the 20 last bursts of vectors in each I/Q
quadrant.
Click on the Reset button to reset the display.
Vector analysis :
I & Q values and associated signal-to-noise ratio (Eb/No) are displayed for each quadrant.
Signal analysis :
Ampli. Err. And Phase Err. give respectively the RMS errors on the Amplitude and phase measurements.
Note: The “Filter” Window allows to give a representation of the characteristics of the digital matched filter used in
the demodulation process just before the Bit Decision. Depending on the User’s selection, this representation can
be done in the time domain (pulse response, i.e. taps of the digital filter) or in the frequency domain (amplitude and
phase responses). If the DEAF filter mode is selected, the display is continuously updated with new computed
filter characteristics. The selection of the filter type and consequently its characteristics is done in the “Global”
Window (Matched Filter box).
To select the auto-adaptive mode and to get a dynamical update display of the filtering characteristics, click
on DEAF
Saving the filter parameters in a custom filter file (save and learn mode) :
In DEAF mode Click on Store to freeze the display and to temporary save the filter characteristics in a
buffer.
Select a filter file number from 0 to 1000, this number will be used to recall the custom filter in the DEMOD
global window.
Click on Save to store the filter parameters in the selected custom file.
Position the mouse cursor on Function to see which DPU-related licenses are available.
Depending on the available option (DVB Transport Layer, CCSDS Reed Solomon, or LDPC decoding), the right
low part of the window lets appear the status of the corresponding function: RS DVB Status, Reed Solomon Status
or LDPC Status.
4.5.5.1.1 CONTROL
Parameters in this window are described in DPU.
FRAME SYNC. Click on the check box to enable or disable the frame synchronizer :
NRZM DPU Click on the check box to enable or disable the function :
Enable The received data in the DPU are decoded from NRZ-M to
NRZ-L before being sent to the frame synchronizer
Disable No PCM decoding is performed
AUTO AMBIG. Click on the check box to enable or disable the ambiguity resolution operation
by the frame synchronizer :
LSB FIRST Enable The frame synchronizer works with LSB first byte format
Disable The frame synchronizer works with MSB first byte format
SYNC. WORD Synchronization Word. Enter any 64-bit hexadecimal value (left field = 32 MS
bits, right field = 32 LS bits). MSB-aligned value. Example : If the
Synchronization Word is 1ACFFC1DH, enter 1ACFFC1D00000000H).
SW MASK Synchronization Word mask. Enter any 64-bit hexadecimal value. MSB-aligned
value. « 1 » bits in the mask indicate which bits in the Synchronization Word
must be ignored by the frame synchronizer. Enter 0 for no mask. Example : for
a 32-bit Synchronization word, enter 00000000XXXXXXXXH (no masked bits).
SYNC. WORD SIZE Synchronization Word size, in bits. Must be an integer number of bytes. Enter
8, 16, 24, 32, 40, 48, 56, 64 or 128.
Example : if the Synchronization Word is 1ACFFC1DH, enter 32.
For an non integer number of bytes specification, use the upper integer number
of bytes value and use the mask to meet specification.
FRAME/BLOCK SIZE Telemetry frame length, in bytes. Enter any integer from 16 to 1048580.
Includes the Synchronization Word.
In1+In2
Both ECL data inputs are merged and sampled on the rising
(rising edge)
edge of the clock
In1
Select ECL data input 1 and sample on the rising edge of the
(rising edge)
clock
In2
Select ECL data input 2 and sample on the rising edge of the
(rising edge)
clock
In1+In2
Both ECL data inputs are merged and sampled on the falling
(falling edge)
edge of the clock
In1
Select ECL data input 1 and sample on the falling edge of the
(falling edge)
clock
In2
Select ECL data input 2 and sample on the falling edge of the
(falling edge)
clock
DESCRAMBLING OFF
CCSDS CCSDS derandomization
Custom Customized derandomization applied before decoding
Custom after decoding Customized derandomization applied after decoding
DESCR. POLY. (HEX) Derandomizer polynomial value, in hexadecimal (16 bits max)
QPSK/OQPSK : No Viterbi or dual Viterbi mode Merged I & Q : select Merged (I&Q)
Separate I & Q : select Split 2(I) or(Q)
4.5.5.1.2 MONITORING
Status and alarms in this window are described in DPU.
FRAME COUNTER Telemetry frame counter. Reset to 0 when the frame synchronizer unlocks or by
clicking on in the upper tool bar (the DPU window must be active).
DROP OUT COUNTER Number of loss of lock on the frame synchronizer. Reset to 0 by clicking on
in the upper tool bar (the DPU window must be active).
FRAME CHECK CRC or Check-Sum test result : Alarm or OK. Forced to OK if parameter Frame
Checking is set to Off.
CORRECTED ERRORS Number of symbols corrected by the Reed-Solomon decoder (average value
computed over a one-second period of time). Displays Exceeded if the maximum
correction capability is reached (number of corrected symbols greater than [16 x
Interleave Factor]).
GOOD FRAMES Number of good transfer frames received from the Reed Solomon decoder. Reset
to 0 when the Frame Synchronizer or the Reed Solomon decoder is set to OFF or
by clicking on in the upper tool bar (the DPU window must be active).
BAD FRAMES Number of bad transfer frames received from the Reed Solomon decoder. Reset
to 0 when the Frame Synchronizer or the Reed Solomon decoder is set to OFF or
by clicking on in the upper tool bar (the DPU window must be active).
BIT ERROR RATE Ratio between the number of corrected bits and the total number of bits processed
by the Reed Solomon decoder. Reset to 0 when the Frame Synchronizer or the
Reed Solomon decoder is set to OFF or by clicking on in the upper tool bar
(the DPU window must be active).
Important : the BER is calculated before Reed Solomon decoding.
CORRECTED ERRORS Number of symbols corrected by the LDPC decoder (average value computed
over a one-second period of time).
GOOD FRAMES Number of good transfer frames received from the LDPC decoder. Reset to 0
when the Frame Synchronizer or the LDPC decoder is set to OFF or by clicking
BAD FRAMES Number of bad transfer frames received from the LDPC decoder. Reset to 0 when
the Frame Synchronizer or the LDPC decoder is set to OFF or by clicking on
BIT ERROR RATE ON Estimation of the BER at the input of the LDPC decoding. Reset to 0 when the
INPUT DATA
Frame Synchronizer or the LPC decoder is set to OFF or by clicking on in
the upper tool bar (the DPU window must be active).
BIT ERROR RATE ON Estimation of the BER at the output of the LDPC decoding. Reset to 0 when the
OUTPUT DATA
Frame Synchronizer or the LDPC decoder is set to OFF or by clicking on in
the upper tool bar (the DPU window must be active).
GOOD FRAMES Number of good transfer frames received from the CRC decoder. Reset to 0 when
the Frame Synchronizer or the Reed Solomon decoder is set to OFF or by clicking
BAD FRAMES Number of bad transfer frames received from the CRC decoder. Reset to 0 when
the Frame Synchronizer or the Reed Solomon decoder is set to OFF or by clicking
IDLE DISCARDED Discard (ON ) or transmit the idle frames to the CADU frame synchronizer
(OFF)
DROP OUT COUNTER Number of frame drop-out events at transport layer level
CORRECTED ERRORS Number of bits corrected by the decoder at transport layer level
Note : When the frame synchronizer of the CADU layer is lock, the status of the counters in the Transport layer
can be updated or not. That is controlled by a Registry key (PermanentTransportStatus).
4.5.5.3.1 CONTROL
Unless otherwise specified, parameters in this window are described in DPU.
OPERATING MODE BER measurement mode (simulated data for BER analyzis) :
Off BER measurement stopped
File Simulated data from a file on the
PseudoDxx Pseudo random data, using from PN generator xx
(where xx = 7, 10, 11, 15, 23 or 31)
INVERSE Inverse (Enable) or not (Disable) the data used for BER computation
TESTED DATA User Data Compute the BER only on the User data of the frames
(excluded added check symbols)
Whole Data Compute the BER on all the received data of the frames
FILE NUMBER File number for BER in file mode : enter any value from 1 to N.
BER COUNTER Total number of bits to process for BER measurement in Pseudo mode
Resolution step : 65536 bits. In File Mode, Infinite accumulation.
4.5.5.3.2 MONITORING
Unless otherwise specified, status & alarms in this window are described in DPU.
Ingestion parameters :
TM FLOW ID. Identification of the telemetry flow. This value is reported in all telemetry
messages over the Telemetry port (TM). Enter any hexadecimal value from 0 to
FFFFFFFF.
Decommutation :
VC POSITION Offset, in bits, between the last bit of the synchronization word and the first
bit of the Virtual Channel ID field. Example : enter 0 if the VC ID field
starts right after the synchronization word.
SPARE DATA Select number of spare fields in the TM Block. Enter 0 to 8. See Figure 39 :
Data Transmission over TCP-IP. Message Formatting
TM block configuration :
SPARE DATA Allows to add spare data (64 bits word) at the end of the TM data blocks
(recorded and transmitted over TCP/IP). Possible values: 0 to 8.
DISABLE FRAME Allows to disable the insertion of the 8 time tag bytes at the end of the TM
DATATION data blocks (recorded and transmitted over TCP/IP)
4.5.5.4.2 MONITORING
Status & alarms in this window are described in DPU.
RECEIVED FRAMES Number of demodulated TM Blocks. Reset to 0 when the CORTEX HDR is
restarted.
TRANSMITTED FRAMES Total number of TM Blocks (for all TM Clients) over TCP-IP. Reset to 0
when the CORTEX HDR is restarted or when switching from Acquisition
mode to Configuration mode
4.5.5.5.1 CONTROL
Parameters in this window are described in DPU.
ENABLE/DISABLE Enable (the MCS opens a connection to the telemetry port) or Disable the Quick
Look display.
Important : the Quick Look can only be enabled if the Acquisition mode is
SAVE Save the data displayed on the Quick Look to a text file on the disk (click on
SAVE only after the Quick Look has been disabled).
Telemetry Blocks are structured as follows (see section 3.4.11: for more details) :
… /…
Time Tag
(8 Bytes)
Status
(8 Bytes)
Telemetry frame :
Synchronization Word + telemetry frame (if frame synchronizer ON) or raw data (if frame synchronizer
OFF). At the end of the frame, spare bytes for 8 bytes alignment (if required). These added spare bytes
can have any values.
Bits D0-31 (offset N) : number of seconds elapsed since January 1st, 00:00:00 of current year
The time tag can be disabled by set-up (refer to “Real Time Frame” window: disable frame datation).
Telemetry Block status (8 bytes) : the Telemetry Block status is captured and displayed in this field only if the
frame synchronizer is ON.
Optional spare field (from 0 to 8 words of 8 bytes) : the number of spare data words (64 bit words) is selected
in the “Real Time Frame” Window. These data words are filled with “00000000” values.
4.5.5.5.3 MONITORING
Status & alarms in this window are described in DPU.
4.5.6.1.1 CONTROL
Parameters in this window are described in DCU
OUTPUT Affects the output of the DCU. Possible values are : DMU1, DMU3
or Combining.
OPERATING MODE Best channel only the best channel is fed to the output
4.5.6.1.2 MONITORING
Status of the channels:
DMU 1/3 Locking state of each channel. Displays “Locked” (green) when the PLL
and the Bit Synchronization loops are locked, “Unlocked” (red)
otherwise.
CARRIER OFFSET Offset from the specified IF carrier frequency (real frequency – expected
frequency). Expressed in Hz.
COMBINING STATUS Locked (green), Check (green), Acquisition (amber), 1-channel (green),
Unlocked (red), N/A (gray).
RELATIVE GAINS Comining weights, expressed in %. In Best Channel mode one weights is
equal to 0, % the other one equals 100 %. The same goes when the unit is
in Single channel state.
EB/N0 Energy per bit in a 1-Hz noise bandwith of the combining unit output.
Expressed in dB.
COMBINING GAINS Gain in energy per bit in a 1-Hz noise bandwith of the combining unit
output. Expressed in dB.
When an incorrect configuration is detected (different bitrates of both demodulators, same IF input…), the box
displays “Warning” (red). A tool tip is displayed when the pointer stops on the box. Below stands an example of
an incorrect configuration :
In the upper toolbar, click on to open the Disk Partitioning & Memory Allocation window :
4.5.7.1.1 CONTROL
Parameters in this window are described in DRG.
Channels configuration:
DISK AND MEMORY Disk and PC RAM buffer partitioning. For TCP-IP and FTP recording modes,
ALLOCATION % allows to allocate a percentage of the available memory for each mounted TM:
0% to 100 %
FOR EACH MOUNTED
DPU
LOGICAL CHANNEL For FTP mode only, allows for the current pass to select a logical channel (first
level FTP directory) 0 to 255.
FOR EACH MOUNTED
DPU
ACTIVE PARTITION For FTP mode only, allows for the current pass to select the active partition 0 to
64.
FOR EACH MOUNTED
DPU
ACTIVE DISK For FTP mode only, allows for the current pass to select the active disk
CONTROLLER controller 0 or1. In case of one available controller, the value must be set to 0.
FOR EACH MOUNTED
DPU
DISK LATE % Status of the delay during the recording of the data on the disk.
DISK OVERRUN Overrun during the recording of the received data (disk).
MEMORY LATE % Status of the delay during the writing of the received data in the buffer memory.
MEMORY OVERRUN Overrun during the writing of the received data (buffer memory).
Disk Management:
MODE In TCP-IP mode only. Select FIFO Mode (permanent recording. The
storage area is structured as a FIFO) or Manual Erase (record data until the
storage area is full, then stop and wait for manual erase of the recorded
session).
Note : it is recommended to use the FIFO mode (with auto-erase) only for
single recording session (auto-erase of the least recent TM Files).
FILES KEEPING Temporary In FTP mode only. Duration of the temporary storage
for the directories keeping the files declared as NOK
by the filtering operations.
The unity is in days for values between 1 and 128
The unity is in minutes for values between -1 and -
128
Storage Selection:
To select a storage type click on the corresponding line in the upper window and then click on “Select”.
Storage types with the label “Disk_T” are used for internal hard disk storage. Storage type with the label “DR2912”
are used for external storage on a RAID 5 DR2912 or ER2912 recorder.
Storage types with the label “Pleiades” are used for specific projects.
Storage number 8 and 9 are reserved for CCSDS Packet data and CCSDS CFDP recording in AOS mode and
Telemetry mode.
Set default:
Click on to select the current storage number as the default storage number. The following window
will be displayed to confirm:
4.5.7.1.2 MONITORING
Status & alarms in this window are described in DRG.
STORAGE TYPE Indicates which mode of storage is active example: FTP CCSDS (standard)
SELF TEST In configuration mode, a periodical auto-test is performed on the defined partitions.
This test consists in writing a file in the directories and trying to read it. The result is
OK or Non OK as soon as one partition is in error.
4.5.7.2.1 CONTROL
Unless otherwise specified, parameters in this window are described in DRU.
TM BLOCK PER FILE Maximum number of TM blocks per recorded File (defines the recorded files
maximum size). If set to 0, the recorded files maximum size will be 2 Gbytes.
To access to the erase functions by DRU (Refer to the paragraph “Global Disk and Memory
Management window).
Select a report by clicking on the corresponding line in the upper window to display the recorded files listing
corresponding to the report.
.
Once the storage is started, the following message appears on the screen :
The recording cannot be started as long as the HDR is not set in “Acquisition” mode; use the button to switch
from “Configuration” mode to the “Acquisition” mode.
4.5.7.2.2 MONITORING
Status & alarms in this window are described in DRU.
RECORDED DATA Amount of recorded data for the current recording session. Expressed in
Mbytes
NBR. OF RECORDED FILES Recorded TM file number for the current recording session. 0 to N
DATE OF FIRST BLOCK Time-tag of the first recorded TM Block for the current recording session
DATE OF LAST BLOCK Time-tag of the last recorded TM Block for the current recording session
TM Status :
CTRL/PART Active hard disk controller (0 or 1) / Active hard disk partition (1 to 64)
Disk Information :
CAPACITY Total data recording capacity for both hard disk controllers (in Mbytes)
OCCUPIED Occupied capacity for both hard disk controllers (in Mbytes)
FREE Free capacity for both hard disk controllers (in Mbytes)
TM Information :
FILE SIZE Size of the TM File (in bytes). This value corresponds to the TM block size
multiplied by the value set in “TM block per”. The maximum value is 4
Gbytes.
BLOCK SIZE TM Block size (in bytes). Up to 1,048, 656 bytes. This value corresponds to
the defined frame (CADU) size plus a few bytes of time tagging and frame
sync. Status.
4.5.7.3.1 CONTROL
Parameters in this window are described in DPU.
RS FILTER Enable or disable the filtering of Reed Solomon code blocks in errors.
SORT BAD Enable or disable the sorting of the RS code blocks considered as not corrected
SORT A OR VIRTUAL Enable or disable the Sort A operation (Generic mode) or the Virtual Channels
CHANNEL sorting (CCSDS mode)
Offset: Offset in bits in the frame of the position of the word to extract to be
used for the sorting A operation (0 is the first bit of the synchronization marker)
Size: Size in bits of the word to extract, from 0 to 8
File: Index of the Sort A configuration file, from 0 to 255
EXTRACT A Enable or disable the operation of Extract A, the operation is the same as for
Sort A,B and C operations except that it impacts only the files names and not
the directories.
Offset: Offset in bits in the frame of the position of the word to extract to be
used for the Extract A operation (0 is the first bit of the synchronization marker)
Size: Size in bits of the word to extract, from 0 to 8
File: Index of the Extract A configuration file, from 0 to 255
Note: the data values used in the filtering, sorting and extract operations are defined in their
corresponding configuration files selected by the index values.
Filename:
The basic name of a recorded file is the date of its creation (default name). From this basic name a number of
programmable markers can be added:
R/W Enable or disable the insertion of the R/W marker in the recorded files
names
CHANNEL Enable or disable the insertion of the selected Logical Channel marker in
the recorded files names (The selection of the logical channel for a recording
session is done in the “Global Disk and Memory Management Window)
EXTRACT A Enable or disable the insertion of the Extract A marker in the recorded files
names
FILE NBR Enable or disable the insertion of the File Number marker in the recorded
files names (counter of the number of generated files during a recording
session inside a dedicated directory)
FILTER RS Enable or disable the insertion of the RS Filter marker in the recorded files
names
FILTER A Enable or disable the insertion of the Filter A marker in the recorded files
names
SORT A OR VIRTUAL Enable or disable the insertion of the Sort A marker (Generic mode) or the
CHANNEL Virtual Channels marker (CCSDS mode) in the recorded files names
SORT B Enable or disable the insertion of the Sort B marker in the recorded files
names
SORT C Enable or disable the insertion of the Sort C marker in the recorded files
names
SPECIFIC PROJECT P1, P2, P3, and P4, hexadecimal values from 0 to FFFFFFFF. Theses
parameters are specific to the project.
PARAMETERS Specific user defined markers. For A, B and C, the corresponding fields
allow to enable or disable the insertion of the marker and to enter the
characters string of the marker (up to 12 characters for each field)
EXTENSIONS Allows for the recorded Data files and the session Report files to define an
extension suffix which will be inserted in the files names
Note: the characters strings markers of the filtering, sorting and extract operation are defined in their
corresponding configuration files.
4.5.7.3.2 MONITORING
Status & alarms in this window are described in DPU.
TOTAL TM BLOCK Total number of TM Blocks for all directories (All line) and for each
directory.(DR00 to DR63 lines)
BAD TM BLOCK Total number of bad TM Blocks for all directories and for each directory
SORT TM FILE Total number of Sort TM files created for all directories and for each
directory
SORT VALUE First four bytes of the last frame data which created the corresponding last
sorting.
Detailed information for the set-up and operation of the functionality is given in the Recording and FTP
Recovery User Manual DTU 10038.
4.5.7.4.1 CONTROL
None
4.5.7.4.2 MONITORING
4.5.7.4.2.1 VIRTUAL CHANNELS INFORMATION
From left to right :
- Number of good TM Blocks (including corrected ones) for each virtual channel
Click right in the window to select either Session Virtual Channel (display VC information for the current
recording) or TM File Virtual Channel (display VC information for the current TM File).
Figure 125 : Test Modulator : Modulation Window for BPSK, QPSK and UQPSK
OQPSK Modulations :
8PSK Modulation :
16QAM Modulation :
16APSK Modulation :
32APSK Modulation :
64APSK Modulation :
4.5.8.1.1 CONTROL
CARRIER FREQUENCY IF carrier frequency 716 to 724 MHz. Expressed in Hz. (former modulator
board, SM 01008857 model only).
IF carrier frequency 580 to 860 MHz. (SM 01019647 model).
IF carrier frequency 1150 to 1250 MHz. (SM 01019647 model)..
Enter any value in float or real format. Example: for 720 MHz, type: 7.2e+8 or
720000000. The programmed value is always displayed in float format. The
resolution is limited by the hardware design to ~200 kHz.
CARRIER LEVEL Carrier level at the Nominal output port . Expressed in dBm. Enter any value
from -10 to –40. Resolution step : 1 dBm.
I/Q SHIFT Allows adjusting the I/Q offset in OQPSK mode for test purposes.
Enter any value from +0.5 to –0.5 (in symbol). Select 0 for optimal OQPSK
(half-symbol offset). Note : for bit rates higher than 200 Mbps only
PHASE ROTATION Select CCSDS (Counter Clock Wise) or Inverted (Clock Wise). (see section
3.6.2.4)
(8PSK) MAPPING Select Natural, Natural2, Gray1, Gray2, Gray3, Gray4, Gray5 or Gray6 (see
section 3.6.2.4)
FILTER Allows to enable and cjhoose the modulation filter. Select OFF, RC, RRC or
GMSK
The filter is available in the symbol rate range: 500 Ksps to 120 Msps (for other
rates consult ZDS) with modulator menu #6
ROLL-OFF OR BT Roll-off factor for the RC/RRC filter or BT factor for the GMSK filter. Enter
any value from 0.1 to 1.0
DOPPLER RATE Rate of frequency sweeping. Enter any value from 0 to 100 KHz/s
DOPPLER ERANGE Range of the frequency sweeping. Enter any value from 0 to +1 MHz
NOISE LEVEL Noise level. Expressed in dBm/Hz. Enter any value from –132 to –93.
Resolution step : 1 dB.
NOISE Enable or disable the noise generator by clicking on the check box.
FREQUENCY Display the selected frequency reference Internal (10 MHz) or External.
REFERENCE
PLL ON EXTERNAL Status of the PLL on the external reference: Disabled, Locked or Unlocked
REFERENCE
4.5.8.1.3 MONITORING
Status and alarms in this window are described in TSTU
H/W STATUS 1, 2 Test Modulator hardware status : OK (green display) or ALARM (red display).
(upper banner)
See also the error code (if any) reported in the TCP-IP address field in the Top
Level window.
Figure 133 : Test Modulator : PCM Window for BPSK, QPSK, OQPSK, 8PSK, 16QAM and n-APSK
UQPSK Modulation:
MODULATING In BPSK, QPSK, OQPSK (SQPSK), 8PSK or 16QAM modes, select Internal or
SIGNAL External
In UQPSK (AQPSK, AUQPSK, AUSQPSK) mode, select: Internal, External I,
External Q or External I/Q.
PLAYBACK AUTO If selected insert PRN data before and after the actual recorded data in Playback
mode
FILE NUMBER File number for BER in File mode: enter any value from 1 to 4294967295 (note
1)
CYCLE LENGTH Cycle length, for File mode only (in bytes). Enter a value from 32 to 2097152.
See Section 3.6.2.2.2.
BIT RATE Telemetry bit rate. Expressed in bps. Enter any value from 1e6 to 1500.e6
(modulation, firmware dependent). See note 2.
In QPSK or OQPSK (SQPSK) mode, the bit rate must be set to (I Channel Bit
Rate + Q Channel Bit Rate)
In BPSK, UQPSK (AQPSK, AUQPSK, AUSQPSK) mode, enter the bit rate of I
Channel
Note 1 : Click on in the lower tool bar to invert one bit in the simulated data pattern (pseudo-random pattern
or file). Bit inversion takes place before convolutional encoding (if enabled).
Important : in UQPSK (AQPSK, AUQPSK, AUSQPSK) mode, parameters BIT RATE, PCM CODE, FILE
NUMBER, CYCLE LENGTH described here above are for the I Channel. The following additional parameters
appears at the GUI for controlling the Q Channel :
BIT RATE Q Telemetry bit rate for the Q Channel. Expressed in bps. Enter any value from
1e6 to 720.e6 (modulation, firmware dependent).
See also definition of BIT RATE parameter
I/Q RATIO Ratio between I Channel & Q Channel in dB, from 0 to 100
FILE NUMBER Q File number for BER in File mode for the Q channel: enter any value from 1 to
4294967295
CYCLE LENGTH Q Cycle length for the Q channel, for File mode only (in bytes). Enter a value
from 32 to 2097152. See Section 3.6.2.2.2.
Figure 135 : Test Modulator : Encoding Window for BPSK, QPSK, OQPSK, UQPSK and 16QAM
8PSK Modulation:
VITERBI ENCODER Q Convolutional encoder setting for the Q Channel in UQPSK (AQPSK, AUQPSK,
AUSQPSK) mode :
Off Encoder disabled
G1-G2 Inv Encoder enabled with G2 inverted (G1 first)
G1-G2 Encoder enabled with G2 normal (G1 first)
G2inv-G1 Encoder enabled with G2 inverted (G2 first)
G2-G1 Encoder enabled with G2 normal (G2 first)
VITERBI PUNCTURING Puncturing setting for I Channel in BPSK or UQPSK (AQPSK, AUQPSK,
AUSQPSK) mode or for both I & Q Channels in QPSK, OQPSK (SQPSK) mode :
Off Puncturing disabled
from reg. Puncturing scheme defined in registry.
2/3 2/3 Viterbi
¾ (conv.1) 3/4 Viterbi (convention 1)
¾ (conv.2) 3/4 Viterbi (convention 2)
4/5 4/5 Viterbi
5/6(conv.1) 5/6 Viterbi (convention 1)
5/6(conv.2) 5/6 Viterbi (convention 2)
6/7 6/7 Viterbi
7/8 (conv.1) 7/8 Viterbi (convention 1)
7/8 (conv.2) 7/8 Viterbi (convention 2)
1/4 Esrin 1/4 Viterbi (ESA / ESRIN type)
VITERBI PUNCTURING Q Puncturing setting for Q Channel in UQPSK (AQPSK, AUQPSK, AUSQPSK)
mode :
Off Puncturing disabled
from reg. Puncturing scheme defined in registry.
2/3 2/3 Viterbi
¾ (conv.1) 3/4 Viterbi (convention 1)
¾ (conv.2) 3/4 Viterbi (convention 2)
4/5 4/5 Viterbi
5/6(conv.1) 5/6 Viterbi (convention 1)
5/6(conv.2) 5/6 Viterbi (convention 2)
6/7 6/7 Viterbi
7/8 (conv.1) 7/8 Viterbi (convention 1)
7/8 (conv.2) 7/8 Viterbi (convention 2)
1/4 Esrin 1/4 Viterbi (ESA / ESRIN type)
CADU SYNC WORD Enable or Disable the synchronization word inside the data. Essentially used with
simulated pseudo-random data.
REED SOLOMON 223 Enable or Disable the CCSDS Reed Solomon encoder RS(223,255).
REED SOLOMON 239 Enable or Disable the Reed Solomon encoder RS(239,255).
LSB FIRST Enable or Disable the LSB-first byte formatting in the simulated data..
Figure 137 : Test Modulator : Physical layer Window for SCCC and DVB-S2 standard
4.5.8.4.1 CONTROL
VCM Enable or not the VCM mode: Automatic detection of the current modulation
VCM FILE If VCM mode is enabled, the modulation and coding modes sequence is
described inside a simulation ASCII file. This field allows to select the file
number
RATE If VCM mode is disabled, select the coding rate (DVB-S2 and SCCC standard)
PILOTS Enable or not the insertion of pilots indide the frames (DVB-S2 and SCCC
standard)
SHORT FRAME Enable or not the transmission of short frames (DVB-S2 standard only)
PL SCRAMBLING Enable or not the randomization of the frames (DVB-S2 and SCCC standard)
START TIME Allows to define an automatic starting date for the replay.
Must be selected to be active.
STOP TIME Allows to define an automatic stop date for the replay.
Must be selected to be active.
BIT RATE Selects the bit rate of the playback only used in “Data+Clock” mode.
Important: In “Test modulator” mode, the bit rate of the playback is the bit
rate set in the test modulator window.
MEMORY ALLOCATION Allows to allocate a fixed part of the available memory to the playback function
FOR PLAYBACK when the selection box Auto is disabled. The recommended operating mode is to
enable the Auto mode.
4.5.9.1.2 STATUS
Status and alarms in this window are described in PLBK
A general status line gives the status of the operation: “Ready to start” or “Play in progress, waiting for stop”.
A bar-graph gives in real-time the level of the current playback as a percentage of the consumed data from the
selected file.
4.5.9.2.1 CONFIGURATION
OPERATING MODE Select the source of the data for the replay:
Report TM: Selects recorded data from a previous satellite pass (from the
recorded report file of the pass – refer to “From report” command)
Playback Data from File: Selects data recorded inside a User-defined file
Playback Data from Directory: Selects data recorded inside a set of User-
defined files recorded inside one directory
Rec Frames by date: Selects data CADUs by dates
BER file : Selects a PRN code or a data simulation file
FRAME LENGTH Selects the length of the data frames for the playback (synchronization word
included).
64-BIT ALIGN Allows to indicate that TM blocks of the file(s) to be replayed are 64-BIT aligned.
DATE FIELD Allows to indicate that a date field (8-bytes word) is inserted in the TM block of the
file(s) to be replayed.
STATUS FIELD Allows to indicate that a status field (8-bytes word) is inserted in the TM block of the
file(s) to be replayed.
SPARE Allows to indicate if other spare 8-bytes words are inserted in the TM block of the
file(s) to be replayed. Number of words from 0 to 8.
LOOP ON FILE Enable or disable the loop replay on the selected file.
DRU NUMBER A to H selection of the DRU from where the replayed data are extracted.
FIRST CADU Date of the first CADU to replay (only in “Rec Frames by date” mode)
LAST CADU Date of the last CADU to replay (only in “Rec Frames by date” rmode)
CHANNEL Selection of the Recording channel (DRU-A, B, C, …H) where the pass report file
has to be selected.
DRU-A to DRU-H
REPORT NUMBER Selection of the report number: 1 to N. Can be selected directly by clinking in the
Storage report and TM files Window
LINE Selection of a specific line (a specific file) inside the selected pass report : 0 to N.
Can be selected directly by clinking in the Storage report and TM files Window
FILE NBR. Selection of the file number for the replay: 1 to N. The file must be recorded in the
“PLAYBACK” directory of the selected partition.
To control the data logging function, in the upper toolbar click on . This operation opens the data logging
control window :
4.5.10.1.1 CONTROL
START / STOP Start or stop the data logging in manual mode.
AUTOMATIC LOG If selected, the recording starts automatically with the Acquisition mode. In this
case the parameters are recorded in the file number 0 for TMA, TMB, TMC and
TMD.
CONFIGURATION FILE Select the number of the configuration file used for the current data logging
operation
CHOOSE CHANNELS Select the channel(s) TMA, TMB, TMC and/or TMD for the current logging
operation.
Open the editor window to configure a new configuration file (see next section).
4.5.10.1.2 STATUS
The status field can take the following values: Inactive, Running or Automatic. In case of a non valid
configuration file number, Error is reported in this status field.
For details on the data logging editor function, refer to section 3.8.
To edit an already existing or a new logging configuration file, click on in the previous data logging control
window to open the following data logging editor window :
CONFIGURATION FILE Select the number of the configuration file to edit: 0 to 100
LOG NAME Enter a general label associated with the logging file (this label will appear
inside the data logging text file).
MAX DURATION If 0, the recording will stop only by clicking on the stop button in the control
window. If a value is set (in seconds), the recording will stop at the end of this
delay even is the stop button has not been clicked.
PARAMETER LABEL Enter a label for the parameter to log (this label will appear inside the data
logging text file).
COMPONENT AND Select the effective HDR control parameter or status by entering its component
OFFSET number (hexadecimal format) and offset (hexadecimal or decimal format) as
defined in the STI document.
LOGGING TYPE Select the logging type associated with the selected parameter
Periodic Logging
Log on Transition
Log on Variation
VALUE TYPE Select the logging format for the value of the selected parameter:
Unsigned Integer
Signed Integer
Hexadecimal
Float
Double float
STATE VALUE In “Log on Transition” mode, defined the status labels associated with the
actual status values (these label will appear inside the data logging text file).
BASIC
INGESTION
MENU
DEMODULATOR # 1 DEMODULATOR # 2
1 5 1 5
NBR. Max. SR A/UQPSK FIR Coding MAX. SR A/UQPSK FIR Coding DPU NUMBER
2 2
1 240 NO YES TCM 2.5/3 240 NO YES TCM 2.5/3 2 x FS
RS DVB RS DVB
3 3
3 240 NO YES Viterbi 1/2 240 NO YES Viterbi 1/2 2 x FS
V.35 V.35
RS (223,255) RS (223,255)
3 3
4 240 NO YES Viterbi 1/2 240 NO YES Viterbi 1/2 2 x FS
V.35 V.35
RS (239,255) RS (239,255)
3 3
5 2x240 YES YES Viterbi 1/2 2x240 YES YES Viterbi 1/2 4 x FS
RS (223,255)
RS (223,255)
2 2
8 240 NO YES TCM 2.00/3 240 NO YES TCM 2.00/3 2 x FS
RS DVB RS DVB
2
9 360 NO YES Fast TCM 2.5/3 Not available 1 x FS
RS DVB
2
10 360 NO YES Fast TCM 2.00/3 Not available 1 x FS
RS DVB
RS (223,255) RS (223,255)
and De-randomizer and De-randomizer
2
12 360 NO YES Fast TCM 2.5/3 Not available 1 x FS
RS (239,255)
4 2
13 600 NO YES Fast TCM 2.5/3 Not available 1 x FS
RS (239,255)
Soft bit output
(4096 bits)
Extension board
Extanesion board
(4096 bits)
(1024 bits)
(1024 bits)
Soft bit output
Fast Viterbi
RS (223,255)
RS (239,255) RS (239,255)
RS(6,10) CRC RS(6,10) CRC
VCM
(223,255)
RS DVB
Fast Viterbi
RS (239,255)
30 6 NA NA NA RS (223,255) NA NA NA RS (223,255) 2 x FS
RS(6,10) CRC RS(6,10) CRC
31 6 NA NA NA RS (239,255) NA NA NA RS (239,255) 2 x FS
RS(223,255)
RS(6,10) CRC
RS (239,255) RS (239,255)
RS (239,255) RS (239,255)
RS (223,255)
Soft bit output
RS (223,255) RS (223,255)
RS(223, 255)
fast Viterbi
RS(239, 255)
RS(239,255)
RS (223,255) RS (223,255)
RS (239,255) RS (239,255)
RS(6,10) CRC RS(6,10) CRC
3
50 240 YES YES Viterbi 1/2 Not Available 2 x FS
RS (223,255)
3 3
51 240 NO YES Viterbi 1/2 240 NO YES Viterbi 1/2 2 x FS
RS (239,255) RS (239,255)
+
RS (239,255)
XDEAF
+
RS (223,255)
XDEAF
+
RS (223,255)
XDEAF
Note 1: Maximum Symbol Rate of the demodulator (Msps). Refer to the following tables which give the maximum
Bit Rates measured at the demodulator input for different demodulation and decoding schemes.
Note 2: Maximum Bit Rates at the input of the TCM decoder are given in the following tables .
Note 3: Maximum Bit Rates at the input of the Viterbi decoder are given in the following tables.
Note 4: Menus 6, 13, 18,19, 20, 22, 23, 26, 27, 28, 29, 38 and 39 are available with 1.2 GHz IF input.
Menus 1 to 5 : up to 26 direct taps (16 bits) or 8 crossed taps (8 bits), symmetric or asymmetric.
Menu 7: up to 26 direct taps (16 bits) or 8 crossed taps (8 bits), asymmetric only.
Note 6: Menus 30 and 31 are available with DPU inputs (Data + Clock) . The input bit rate is limited to 350 Mbps.
Note 7: Menus 45 to 49 are customers menus with specific I/O (Refer to the specific DTU documents).
Note 8: Menus 42 and 44 are customers menus with 1.2 GHz IF inputs.
The following table shows the hardware limitations for each basic menu of the test modulator:
Basic UQPSK 16QAM High rate Parallel Data Byte Output 1 Filtering Doppler DVBS2
1
Menu modulation modulation modulation generation Simulation SCCC
1 Not available YES Not available Not available Not available Not available Not available Not available
2 YES Not available Not available Not available Not available Not available Not available Not available
3 Not available YES YES Not available Not available Not available Not available Not available
4 Not available YES Not available Not available YES Not available Not available Not available
5 Not available YES Not available YES Not available Not available Not available Not available
6 Not available YES Not available Not available Not available YES Not available Not available
7 Not available YES Not available Not available Not available Not available YES Not available
8 Not available YES YES Not available Not available Not available Not available YES
9 Not available YES Not available Not available Not available YES Not available YES
The following table gives the hardware menus available with the Extension Board (option):
Viterbi decoding mode Maximum Bit rate at the input Maximum Bit rate at the input
Remark: For Punctured Viterbi codes the maximum bit rate is equal to the maximum bit rate of the Viterbi ½
multiplied by the puncturing rate.
Remark: The previous tables give the intrinsic performance of each decoder versus the selected menus and not
the performance of the overall demodulation channel for a specific demodulation mode and a specific decoding
scheme. The following table gives some example of achievable performances:
To check which licenses are mounted in the machine, position the mouse cursor on the Function status fields of
the GUI or select the “Information” Window in the CORETX HDR top-level Global Window to have an overall
view. This view takes into account the available licenses and the capabilities of the current basic menu.
5. MAINTENANCE
PROCEDURES
5.1 GENERAL
5.1.1 Mechanical Inspection and Cleaning
It is recommended to take the following precautions to get the best performance from the system :
Do not carry out any dust-producing work in the room housing the CORTEX HDR. Clean the air filters regularly
to avoid electronic components overheating.
Use only alcohol or a water-based cleaner on the front and rear panels of equipment. Other solvents may
damage the keys, LCD and markings.
Perform a regular operating check on the fan units (check for any abnormal temperature rise, check the air flow
at the air exhaust). The system is not designed for permanent operation without ventilation.
Preventive maintenance: it is recommended to change the Pentium cooling fan every 3 years.
SOME OF THE HARDWARE COMPONENTS USE CMOS TECHNOLOGY AND CAN BE DAMAGED
Never remove a board from the CORTEX HDR without switching it off first and removing the power cord !
When a module has been removed from the chassis, it is essential to handle and store it with care. It is
particularly important to ensure that it is not exposed to electrostatic shocks.
Certain precautions must also be taken when reinstalling a board in the chassis : when plugging the board into
the PCI bus connectors, never force it; screw the board strip attaching screws back into the frame; reinstall the
connector locking screws. Only then may the CORTEX HDR be switched back on.
1. If the IF level status is lower than 50 dBm, check the RF connecting cable. Check also that the IF input
port is correctly programmed (Nominal or Alternate IF).
2. Check the correctness of the Demodulator status : Carrier Offset, BR Offset, PLL locked, Bit
Synchronizer Locked.
3. Check that the displayed constellation is the expected one and remains stable (see Figure 106) :
Four points on a circle for QPSK, OQPSK (SQPSK) and UQPSK (AQPSK, AUQPSK, AUSQPSK)
modulations.
3. Check that the Viterbi BER status is in accordance with the estimated Eb/No status.
4. If the Viterbi fails to decode, check the setting of the Viterbi decoder : single or dual Viterbi mode, G2
inverted, etc…
1. The output ports setting is correct : Output Clock, I/Q polarity, Normal or I&Q merged, Output mode. If
the problem remains, try different setting.
Incorrect IF setting (signal = QPSK 720 MHz. Demodulator setting = 721 MHz)
Incorrect bit rate setting (signal = QPSK 50 Mbps. Demodulator setting : 47 Mbps). Matched filter
inefficient.
Dual 50 Mbps QPSK signals at 720 and 770 MHz (adjacent channel
interferences).
Dual 50 Mbps QPSK signals at 720 and 770 MHz. Limited interferences thanks to an RRC filter
(Roll-off 0.1) on the Demodulator.
HW Turns to green and flashes at 1-PPS to show that the hardware is correct.
Unlit (or high rate flashing) in the case of Test Modulator board or CPU board failure.
HW Turns to green and flashes at 1 PPS to show that the hardware is correct.
Unlit (or high rate flashing) in the case of Demodulator board or CPU board failure.
These sensors are permanently monitored by a dedicated software tool IPMIMonitor. To run this software, click
on START -> PROGRAM -> IPMIMonitor -> IPMIMonitor.
Baseboard Temp. 34 °C 52 °C
Processor 1 Temp. 43 °C 72 °C
Processor 2 Temp. 43 °C 72 °C
These alarms are reported to the remote monitoring clients via the Global CORTEX Monitoring table (Annex 1, STI
100013_<product name>, Table 6, offset 41) and at the CORTEX GUI (bottom status bar. See section 4.3.5.5).
Immediately shutdown and switch off the chassis to avoid any damage to the hardware.
Verify that the air exhaust system of the housing rack works properly,
Verify that the air intake and exhaust grids are clear. Important : a free rack space must be provided
above and below the chassis,
Check the cooling fans on both sides of the chassis, at the rear panel of the chassis (power supply
module) and on both CPU processors.
Return the chassis to ZDS or its maintenance representative if the problem cannot be fixed on site.
The keyboard/trackball.
Windows OS for re-installing the operating system in the case of disk failure.
HDR software. The CD ROM contains the Signal Processing Software (SPS), Monitoring & Control Software
(MCS), Demodulator board software (disk-resident part only) and the user documentation.
1. Load Windows Operating System (procedure described at the back of the CD ROM).
2. Load the HDR software (procedure described on the back of the CD ROM).
6. SATELLITES
CONFIGURATION
EXAMPLES
Next table is a non-exhaustive list of in-orbit satellites with their main downlink configuration parameters :
modulation, bit rate, PCM code, Viterbi mode, output mode.
These parameters can be entered manually on the CORTEX HDR or, more easily, by loading the MCS file
indicated in the left column. These MCS files can be found in :
C:\Program Files\IN-SNEC\CrtxMcs\Default\Config
Reminder : procedure for configuring the CORTEX HDR from an MCS file :
1. Click on FILE, CLOSE. If necessary, save the current configuration to the active MCS document.
2. Click on FILE, OPEN. Select a new MCS document in the list and click on OK to load it. The configuration
status turns to (unless the new MCS document is strictly identical to the previous one).
3. Enable the configuration mode if necessary (click on in the lower toolbar and enter the Configuration
password).
WARNING :
THE OPERATOR SHOULD KNOW THE DETAILED FEATURES OF THE TRACKED SATELLITE
NRZ-M
Akari.mcs NRZ-M
Alos.mcs DNRZ
AquaDB.mcs NRZ-M
AquaDP.mcs NRZ-M
ATV.mcs NRZ-M
CBERS.mcs DNRZ
Corriolis1.mcs NRZ-M
Corriolis2.mcs NRZ-M
Corriolis2_FS.mcs
Cosmo.mcs DNRZ
Cryosat.mcs DNRZ
Envisat_Asar.mcs DNRZ
Envisat_Meris.mcs DNRZ
Envisat_Meris_Asar.mcs DNRZ
EROS.mcs DNRZ
Formosat-2.mcs DNRZ
GOES-R.mcs NRZ-L
LDPC
Gosat.mcs NRZ-M
HY1.mcs DNRZ
Icesat.mcs NRZM
Icesat_fs.mcs
Ikonos.mcs NRZ-M
IRS-1C_liss3.mcs DNRZ
IRS-1C_pan.mcs DNRZ
IRS-1D_liss3.mcs DNRZ
IRS-1D_pan.mcs DNRZ
IRSP4.mcs DNRZ
IRSP5.mcs DNRZ
IRSP6.mcs DNRZ
JEM.mcs NRZ-M
JEMFordward.mcs NRZ-M
Kompsat2.mcs NRZ-M
Metop.mcs NRZ-L
Metop_FS.mcs
Metop_HRPT_FS.mcs NRZ-L
NPOES.mcs NRZ-M
NPOES_FS.mcs
NPP.mcs NRZ-M
NPP_FS.mcs
NRL1.mcs NRZ-M
NRL2.mcs NRZ-M
OFEC.mcs DNRZ
Oryx.mcs NRZ-M
PROBA.mcs NRZ-L
PROBA_FS.mcs
QuickBird.mcs NRZ-M
Radarsat.mcs DNRZ
RazakSat.mcs DNRZ
RESURS_DK.mcs NRZ-L
SAC-C.mcs NRZ-M
SAC-C_FS.mcs
sdo.mcs NRZ-M
sdo_fsrs.mcs
SICH-2.mcs NRZ-M
SICH-3.mcs NRZ-M
SICH-BPSK-HR.mcs NRZ-M
SICH-BPSK-LR.mcs NRZ-M
SPOT2.mcs DNRZ
SPOT4.mcs DNRZ
spot5.mcs DNRZ
spot5_FS.mcs
SPOT_VGT_LBand.mcs NRZ-M
SPOT_VGT_Band.mcs NRZ-M
SSTL-Bpsk.mcs NRZ-M
SSTL-Qpsk.mcs NRZ-M
Terra_highdatarate.mcs NRZ-M Q: 8 //
decod.
TerraSARX.mcs DNRZ
TopSat-BPSK.mcs NRZ-M
TopSat-BPSK.mcs NRZ-M
Worldview2.mcs NRZ-M
DEAF
8. ANNEX 2:
DEMODULATOR BOARD
9. ANNEX 3: TEST
MODULATOR BOARD