HIGH DATA RATE RECEIVER
HDR-4G+ USER’S MANUAL
Ref. DTU 100782
Is.Rev 3.5
Date: June 1, 2021
© Safran Data Systems – IMP000074 e14r1
This document is the property of Safran Data Systems.
It cannot be duplicated or distributed without expressed written consent.
3 FUNCTIONAL DESCRIPTION
Monitoring & Control 3.1
Monitoring 3.1.1
The CORTEX HDR supplies its status on request from a Monitoring Client. On reception of a
monitoring request, the CORTEX HDR checks its validity. If the request is correct, it returns a
monitoring message embedded in an Ethernet packet. In the case of an invalid request, the CORTEX
HDR returns a negative acknowledgment message.
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.).
The Monitoring Client can request:
- the high-level monitoring table of the CORTEX
HDR,
- the Demodulator monitoring table,
- the Test Modulator monitoring table (if available),
- the Data Processing Unit table,
- the Data Recording Global table (if available),
- the Data Recording Unit table (if available),
- the project-specific monitoring table,
- the whole set of here above monitoring tables.
Up to eight Monitoring Clients can be simultaneously connected to the Monitoring port. For more detail
on the monitoring messages, refer to Annex 1.
Control 3.1.2
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).
A detailed description of the Graphical User Interface is available in Section 4.
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.
Logging 3.2
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.