Program cornet is a simple tool used to monitor events, status, and telemetry from an IN-SNEC CORTEX Command Ranging & Telemetry baseband unit. (cornet runs under Unix, Windows, and VMS.)
cornet allows CORTEX ports and tables to be specified by name (case ignored) on the command line. The following NT ports are recognized:
MON TC SIM DOP CTRL MEAS RNG TM RST LOG SPA All
The following VME ports are recognized:
MON TC TMA-R TMB-R TMC-R RNG-1 CTRL MEAS TMA-H TMB-H TMC-H RNG-2 RST LOG TMS All
The following NT tables are recognized:
TCU IFR-1 TMU-A Version TMS IFR-2 TMU-B Global [Table] RAU IFR-3 TMU-C Noise [Generator] IFM-1 TMU-D Project[-specific] IFM-2 TMU-E All [Tables] TMU-F
The following VME tables are recognized:
TCU PMR-A TMU-A Version TMS PMR-B TMU-B Global [Table] RAU-1 PMR-C TMU-C Noise [Generator] RAU-2 IFM Project[-specific] All [Tables]
% cornet [-debug] [-help] [-nt] [-vme] [-flow
] [-norq] [-offset ] host [-calibrate PHASE|TIME|FLOAT] [-configure component,[parameter,value]*] [-connect port] [-events] [-initialize] [-monitor table] [-range PHASE|TIME|FLOAT] [-reset port] [-tc operation] [-tmh A|B|C|D|E|F] [-tmr A|B|C|D|E|F]
- enables debug output (written to stdout).
- displays information about running cornet.
- specifies the type of CORTEX unit, NT-based (the default) or VME-based.
- specifies the data flow indentification (NT-based CORTEX only) used in subsequent options; the default ID is 0.
- specifies that no telemetry request is to be sent to an NT-based CORTEX. Normally, a telemetry request containing the desired TMU channel must be sent to a real CORTEX-NT in order to initiate the flow of telemetry. Some single-channel, CORTEX-NT-emulating simulators, however, don't want such a request.
- specifies an offset to be added to the standard CORTEX port numbers (e.g., CORTEX-NT's TM port 3070) for subsequent operations. This option allows CORNET to connect to "virtual" CORTEX units listening at different service ports on a single host.
- specifies the host name or IP address of the CORTEX unit.
- requests a calibration loop measurement. The argument to this option specifies what to measure (case is ignored): PHASE for phase and time measurements (integer), TIME for time measurements only, or FLOAT for phase and time measurements (float). (VME-based CORTEX requests go to the RAU-2 ranging unit; ranging via RAU-1 is not supported.)
- configures a component on the CORTEX unit. The option argument is a string containing a list of fields separated by commas with no intervening spaces. The first field in the string is the name of the component (table) being reconfigured. Subsequent pairs of fields specify a parameter (identified by its offset in the component's table) and its new value. The value must be specified according to the type of its parameter; e.g., a float parameter being set to 123 must be specified as "123.0".
- connects to an arbitrary port on the CORTEX unit.
- specifies that CORTEX event messages are to received and displayed.
- causes the specified status table(s) to be periodically requested from the CORTEX unit and, when the table is received, displayed.
- requests a ranging measurement. The argument to this option specifies what to measure (case is ignored): PHASE for phase and time measurements (integer), TIME for time measurements only, or FLOAT for phase and time measurements (float). (VME-based CORTEX requests go to the RAU-2 ranging unit; ranging via RAU-1 is not supported.)
- causes the CORTEX unit to disconnect any clients on the specified port.
- sends a telecommand instruction or request to the CORTEX unit. Allowed operations are "COMMAND" (a dummy command), "EXECUTE", and "NOP".
- initiates the sending of frames from the specified telemetry channel. (CORTEX-VME only supports channels A, B, and C.) The
-tmroption directs the CORTEX unit to send real-time telemetry. The
-tmhoption directs the CORTEX unit to first send any buffered frames (i.e., history) and then send real-time telemetry. CORTEX-NT handles all telemetry channels through a single server port; CORTEX-VME has separate server ports for each channel. Consequently, it is important that the CORTEX type (
-vme) be specified on the command line.