TSC / CCS / MCS

Test - Integrate - Control

AlphaNumeric Displays

The TSC now supports displaying AND’s (Alphanumeric Displays)
Alphanumeric Displays are a simplified but very clear way to present a list of telemetry parameters, they are classically used in mission control systems: each parameter is displayed in a fixed location with its raw or engineering value and state clearly visible. This form of display is inspired by the SCOS2000 mission control system but with a few new graphical features and the ability to create new displays dynamically.

The definition of AND’s is stored in the MIB database in the DPF and DPC tables. Displays defined this way will also work with SCOS2000.

You can open any number of AND viewers. When you open a new AND viewer you will see a list of all the AND’s defined in the currently loaded databases with each its name and description. Click on one of the display boxes and the specific display will be opened. You can close and select a different display as you like. If you click on a specific parameter, you will be shown details of that parameter’s curves, limits and from which packets it was extracted.

The AND viewer allows you to define new displays on the fly: just hit the button at the bottom right of the window, and a new user defined display will be created. Into this new display you can drag and drop any of:
  • a single parameter from the telemetry parameter tree views
  • a group of parameters from the telemetry parameter tree views (drag & drop the whole group)
  • one or more parameters from the MIB browser

Static displays are created by loading the DPF and DPC tables from all the defined MIB databases that TSC has loaded. The dynamic displays are saved to DPF and DPC tables in the user’s own test environment, by default in the USER directory. If you want to make these tables static, or “official” (put them in the real database) you can copy or concatenate these files into the relevant database directory. Of course you should take care that if you define a display for a specific database, then you should only use parameters that occur in that database (otherwise the display will not pass a consistency check for that database!)

The AND viewer is quite demanding, so is not activated by default. If your workstation is reasonably powerful, you should have no problems. To activate the AND viewer you should set the following setting:

set utope::settings(DataBase/useAndViewer) 1