Last Updated: $Date: 2001/09/11 20:41:12 $
$PASSDIR/system.config
Each family name is followed by up to 11 settings and has the following format:
[chain number] telemetry chain number. Positive integer.
This chain number can appear only once in the file.
| telemetry.name | Type of telemetry acquired by this chain. Examples of telemetry are: unknown, rtd, hrpt, wefax, swhrpt, swcrpt, pdus, gvar, svissr. |
| telemetry.active | Telemetry acquisition active or inactive indicator.
active = enables acquisition. inactive = disables acquisition using this telemetry chain. |
| framer.index | Index to the frame synchronizer used by this telemetry chain. |
| antenna.index | Index to the antenna used by this telemetry chain. |
| receiver.index | Index to the receiver used by this telemetry chain. |
| bitsync.index | Index to the bit synchronizer used by this telemetry chain. |
| scheduler.type | Type of scheduler used by this telemetry chain.
scheduled - Passes are scheduled based on when the satellite(s) will be in view. Polar satellites and some geostationary satellites use this mode. continuous - Data is received continuously from one or more satellites. gvar and wefax telemetry use this mode. demand - Data is received at unknown start times. It is assumed that the passes will be received not more than once per hour and that the length of the pass will be about the same each time the pass is received. demand scheduling can be used for geostationary data (such as DOMSAT) or can be used for polar satellite data when the clock and data signal are supplied to the system and no antenna tracking is required. |
| scheduler.satellite | Satellite sending data. Required for non-scheduled types. |
| scheduler.initial_proc | When rdframe is started for the first time, this process is also started if this is a non-scheduled capture. |
| scheduler.normal_proc | When rdframe detects the start of the next pass in a non-scheduled capture, this process is called. |
| scheduler.extra_proc | If data is ingested from the GVAR sounder, this process is called. |
| decrypt.index | Index to the decryption unit used by this telemetry chain. |
| down_converter | Each satellite has its own downconverter status that is controlled by this command. This setting tells the antenna program which downconverter to use on the antenna associated with this telemetry chain. In general, only dual-frequency antennas will have this setting. A single-frequency antenna will not need this command. The downconverters are numbered 1,2,3. |
| feed.1.index | Index 1 is used for Xband, Receive Only (RO) feed polarity specifications. This setting is used only when the feed polarity can be controlled. The feed indexes are numbered 1 and 2. |
Example:
# Telemetry chain 4
[4]
antenna.index: 2
(other settings are also part of this chain)
#Telemetry chain 5
[5]
antenna.index: 2
[antenna-2]
antenna.device: /dev/term/a
antenna.type: 70260002
| antenna.device | Name of the operating system device driver that communicates with this antenna. Example: /dev/term/a |
| antenna.type | SeaSpace part number or description of this antenna. |
| receiver.device | Name of the operating system device driver that communicates with this receiver. Example: /dev/term/1 |
| receiver.type | Description of this receiver.
HR100 = HR100 and HR200 receiver/bit sync, any telemetry type MICRODYNE = MicroDyne receiver type |
| framer.device | Name of the operating system device driver that communicates with this framer. Example: /dev/s56dsp0 |
| framer.type | Description of this framer.
S56X = SUN S-Bus Frame Sync ISA = HP ISA Frame Sync SSD20 = SUN PCI Frame Sync |
| bitsync.device | Name of the operating system device driver that communicates with this bit sync. Example: /dev/term/2 |
| bitsync.type
|
Description of this bit sync.
HR100 = HR100 and HR200 receiver/bit sync, any telemetry type. DSI = DSI 7700 Bit Sync |
| [feed-X] family
feed.device
feed. type
feed.pol
|
Feed band.
Feed polarity
|
| decrypt.device | Name of the operating system device driver that communicates with this decryptor. Example: /dev/term/3 |
| decrypt.type | Description of this decryptor (KG44A, KG44B, KG144, SGP, or MKU). |
| satellite.keyparam | The following settings can occur more than once
in a decrypt family.
Each satellite has its own decryption key in the decryption unit. When data from this satellite is acquired, the decryption unit is set to this key value. One or more of these keyparam settings can be defined for each decrypt unit. Examples: f-14.keyparam: 2 f-15.keyparam: 3 For device.type: SGP, the keyparam is the site code for the decrypt unit. Example: orbview-2.keyparam: OXYZ For device.type: MKU, the keyparam is the serial number of the decrypt unit. |
| tape.device | Name of the operating system device driver that communicates with this tape. Example: /dev/rmt/0n |
| tape.model | Model defines the tape unit.
The model names are sundat, hpdat, exabyte, wangdat, dlt. |
| tape.driver | System-related driver type. The driver names are solaris, solaris_fixed, hpux, irix, aix. |
| lut.device | Name of the operating system device driver that communicates with this LUT. Example: /dev/term/2 |
| lut.type | SeaSpace part number or description of this LUT. Metocean is the only type currently defined. |
| lut.baudrate | Baud rate of the serial port connected to this LUT ( 2400,4800, 9600,19200, or 38400). |
| nav.device | Name of the operating system device that communicates with the NMEA serial port. Used if ship heading data source is nmea. Example: /dev/term/2 |
| nav.type | Source of ship heading data. Either the number or
the text name can be used.*
Number or Name (Description) 1 or gyro (Analog gyro input) 2 or gyro sbs (Analog gyro, step by step ) 3 or gyro 360 1 (Analog gyro, 360:1 synchro ) 4 or gyro 1 1 (Analog gyro, 1:1 synchro ) 1001 or flux 1893 (Fluxgate compass on 1893 class antenna) 2001 (NMEA digital input, 2400 baud message) 2002 (NMEA digital input, 4800 baud message) 2003 (NMEA digital input, 9600 baud message) 2004 (NMEA digital input, 19200 baud message) 2005 (NMEA digital input, 38400 baud message) nmea (NMEA digital input. Baud rate = nav.baudrate)** 4000 or fixed (This is a fixed-site system; no ship heading) *The preferred method is to use the text name instead of the number. **The preferred method for specifying NMEA data is to set nav.type to nmea and set nav.baudrate to the baud rate. The values 2001, 2002... are included for compatibility. |
| nav.baudrate | If digital ship heading data is sent using the nmea serial port, this value specifies the baud rate. The valid rates are: 2400, 4800, 9600, 19200, or 38400. |
| nav.msgfmt | Defines the message format being sent via the nmea
serial port. The choices are:
0183 v2.10 = NMEA 0183 version 2.10 sentence format. 0183 v2.30 = NMEA 0183 version 2.30 sentence format. nav1 cdg = NAV1 CDG miniCIN Mod 3 message format (10 ms and 100 ms messages). If this setting is not defined for a nav.type: nmea, the default message format is 0183 v2.10. |
| ups.device | Name of the operating system device that communicates with the Uninterruptible Power Supply (UPS) unit. Example: /dev/term/3 |
| ups.type | Description, model name, or SeaSpace part number of this UPS unit. |
| ups.index | Describes the command set of the UPS:
gold = Emerson AU gold series UPS. su = APC AP or Smart UPS series UPS. |
| gps.device | Name of the operating system device that communicates with the Global Positioning System (GPS) unit. Example: /dev/term/a |
| gps.type | Description, model name, or SeaSpace part number of this GPS unit. |
| gps.index | Command set and location of this GPS:
external-acutime = GPS unit is external from the antenna. internal-SV6 = GPS unit is tied to the antenna controller and is mounted inside the antenna's radome. nmea = Location and system time corrections are read by the nmea_monitor command. |
| gps.data.source | If the the GPS data is not received by a serial port, this
setting specifies the source of the data.
If gps.index: nmea (data is supplied using NMEA serial input), this setting is a numeric value that specifies the NMEA input port (1 for [nav-1] or 2 for [nav-2]) that supplies the data. See nmea_monitor. |
| gps.assoc.chain | Telemetry chain number. This telemetry chain uses an antenna that has the GPS mounted inside its radome. |
%cat $PASSDIR/system.config # # Telemetry chains # [1] telemetry.name: hrpt telemetry.active: yes framer.index: 1 antenna.index: 1 receiver.index: 1 bitsync.index: 1 scheduler.type: scheduled [2] telemetry.name: wefax telemetry.active: yes framer.index: 1 antenna.index: 1 receiver.index: 1 bitsync.index: 1 scheduler.type: continuous scheduler.satellite: goes-10 scheduler.initial_proc: wefax_pproc_wait scheduler.normal_proc: wefax_pproc # # Antenna specifications # [antenna-1] antenna.device: /dev/term/a antenna.type: 70260005 # # Receiver specifications # [receiver-1] receiver.device: /dev/term/0 receiver.type: HR100 [framer-1] framer.device: /dev/s56dsp0 framer.type: S56X [bitsync-1] bitsync.device: /dev/term/0 bitsync.type: HR100 # # nav specifications # nav.device: /dev/term/2 nav.type: nmea nav.baudrate: 4800 nav.msgfmt: 0183 v2.10 # # Hardware monitored by TeraScan. Not chain related. # [system] ups.device: /dev/term/1 ups.type: SU 1400 ups.index: su gps.device: /dev/term/a gps.type: 70162001 gps.index: internal-SV6 gps.assoc.chain: 1 #
%cat $PASSDIR/system.config
# # Telemetry chains # [1] telemetry.name: gvar telemetry.active: yes framer.index: 1 receiver.index: 1 bitsync.index; 1 scheduler.type: continuous scheduler.satellite: goes-10 scheduler.initial_proc: gvar_pproc_wait scheduler.normal_proc: gvar_pproc scheduler.extra_proc: gvar_sounder_proc [2] telemetry.name: hrpt telemetry.active: yes framer.index: 2 antenna.index: 1 receiver.index: 2 bitsync.index; 2 scheduler.type: scheduled [3] telemetry.name: swcrpt telemetry.active: yes framer.index: 2 antenna.index: 1 receiver.index: 2 bitsync.index: 2 decrypt.index: 1 scheduler.type: scheduled # # Antenna specifications # hrpt and wefax [antenna-1] antenna.device: /dev/term/a antenna.type: 12549007 # Receiver specifications # gvar receiver [receiver-1] receiver.device: /dev/term/0 receiver.type: HR100 # hrpt/swcrpt receiver [receiver-2] receiver.device: /dev/term/2 receiver.type: HR100 # bit sync specifications [bitsync-1] bitsync.device: /dev/term/0 bitsync.type: HR100 [bitsync-2] bitsync.device: /dev/term/2 bitsync.type: HR100 [framer-1] framer.device: /dev/s56dsp0 framer.type: S56X [framer-2] framer.device: /dev/s56dsp1 framer.type: S56X # decryption device [decrypt-1] decrypt.type: SGP # # Hardware monitored by TeraScan. Not chain related. # [system] ups.device: /dev/term/1 ups.type: 12076016 ups.index: su gps.device: /dev/term/3 gps.type: 12552014 gps.index: external-acutime #
Last Updated: $Date: 2001/09/11 20:41:12 $