1.797 Zodiac-Cortex-CRT-TMU

This page describes the Zodiac-Cortex-CRT-TMU device driver and its device window. The Zodiac-Cortex-CRT-TMU device driver uses the following tables: Telemetry Unit and Telemetry Unit extension. It is based on the STI 100013_CRT remote protocol document v 3.31, dated Jan. 10., 2020

If more than one telemetry unit is used on the CRT several instances of this driver can be added within the same thread

Beside the TMU multiple instances of the various functional elements may be configured in the sat-nms M&C to handle all features of the unit. All devices referring to the same physical device must be configured at the same device thread / interface to ensure that TCP requests and commands to the device do not overlap.

The different available module drivers for the CRT are:

• Zodiac-Cortex-CRT monitors and controls the base units features of the CRT
• Zodiac-Cortex-CRT-IFM monitors and controls one IF Modulator incl. an embedded frequency converter
• Zodiac-Cortex-CRT-IFR monitors and controls one IF Receiver incl. an embedded frequency converter
• Zodiac-Cortex-CRT-TCU monitors and controls one Telecommand unit
• Zodiac-Cortex-CRT-TMS monitors and controls one Telemetry Simulator
• Zodiac-Cortex-CRT-PRJ monitors and controls one Project Specific table

The CRT requires two separate IP connection for monitoring and commanding the device. The device driver establishes the connection to the monitoring port (usually 3000) by terminal server like TTY connection. This connection is permanently active. Address and port are set in the vlc.setup configuration file as for a terminal server serial port.
How to use TLS connection is described below.

Steps to configure the Zodiac-CRT drivers / devices for TLS communication

1. Create a PKCS12 keystore from the cert files read from the BBU:

openssl pkcs12 -export -out bbu.p12 \
   -inkey CRT-Services-Client-v2.key -in CRT-Services-Client-v2.cert.pem 

openssl prompts to select a password for keystore. e.g. crt

2. Copy the keystore file to /home/satnms/certs/ at the M&C

3. Edit the device configuration (client) to tell the M&C about the protocol and port.

PORT "TLS:192.168.2.202:53000" PROTOCOL CortexNT
    IDLE 1000
    DEVICE BBU-1 IS Zodiac-Cortex-CRT
    DEVICE BBU-1-IFR-1 IS Zodiac-Cortex-CRT-IFR
    DEVICE BBU-1-IFR-2 IS Zodiac-Cortex-CRT-IFR
    DEVICE BBU-1-IFR-3 IS Zodiac-Cortex-CRT-IFR
    DEVICE BBU-1-IFR-4 IS Zodiac-Cortex-CRT-IFR
    DEVICE BBU-1-IFM-1 IS Zodiac-Cortex-CRT-IFM
    DEVICE BBU-1-IFM-2 IS Zodiac-Cortex-CRT-IFM
    DEVICE BBU-1-TMU-A IS Zodiac-Cortex-CRT-TMU
    DEVICE BBU-1-TMU-B IS Zodiac-Cortex-CRT-TMU
    DEVICE BBU-1-TMU-C IS Zodiac-Cortex-CRT-TMU
    DEVICE BBU-1-TMU-D IS Zodiac-Cortex-CRT-TMU
    DEVICE BBU-1-TMU-E IS Zodiac-Cortex-CRT-TMU
    DEVICE BBU-1-TMU-F IS Zodiac-Cortex-CRT-TMU
    DEVICE BBU-1-TMU-G IS Zodiac-Cortex-CRT-TMU
    DEVICE BBU-1-TMU-H IS Zodiac-Cortex-CRT-TMU
    DEVICE BBU-1-TCU-1 IS Zodiac-Cortex-CRT-TCU
    DEVICE BBU-1-TCU-2 IS Zodiac-Cortex-CRT-TCU
    DEVICE BBU-1-TMS-1 IS Zodiac-Cortex-CRT-TMS
    DEVICE BBU-1-TMS-2 IS Zodiac-Cortex-CRT-TMS
    DEVICE BBU-1-PRJ IS Zodiac-Cortex-CRT-PRJ

Important is the TLS in front of the IP address and the port number to use with TLS communication.

4. Restart the M&C and for each BBU-* device edit these setup parameters.

config.cmdPort = 53001
address = certs/bbu.p12 crt

Device window pages

The following table shows which device window pages are available with this individual device type. Tool-bar functions not mentioned here are described at the general description of device windows .

• --- Telemetry unit settings and status.
• --- The faults page.
• --- The device info page.
• --- The maintenance page. The configuration parameters described below are set at this page.

Configuration parameters

At the maintenance page of the device window there are a couple of configuration parameters which must be set to make the software talk to the device.

• parameter --- description
• address --- empty or certificate and password when using TLS
• module --- Defines the telemetry module to be controlled (TMU-A, TMU-B, TMU-C, TMU-D, TMU-E, TMU-F, TMU-G or TMU-H).
• cmdPort --- standard port are 3001 or 53001 when using TLS preset
• deviceComment --- An optional text entered here appears as an addition to the tooltip which is shown while the mouse is placed over a device icon in the GUI. The "\n" character sequence is translated into a newline character, splitting the text into multiple lines.

Variables defined by this device driver