Customer-specific site setups

Use the following questions to select and configure customized RCP features.

To access these questions, in the RCP> prompt, type: Site Custom

Output serial TAG lines: YES

Serial port: /dev/ttyS0

Baud rate of the serial TAGs: 9600

Choose: None RCV01 RCV02 RCV03 RCV05

Serial TAG data format: RCV01

Normally RCP8 outputs azimuth and elevation TAG angles as 16-bit parallel TTL outputs on the back panel. Use these questions to configure an optional serial output stream.

Use WSR-88D DCU Interface (Antenna/Pedestal): YES

Serial port: /dev/ttyS0

Baud rate for DCU: 19200

Choose None Odd Even

DCU data parity: Odd

Bits in position binary angles: 13

ID of DCU BITE status packets: 0x09

ID of DCU Self-Test-1 BITE packets: 0x05

ID of DCU Self-Test-2 BITE packets: 0x06

Spare adjustment for Azimuth : 1.00000

Spare adjustment for Elevation: 1.00000

Additional time lag for Azimuth: 0.000 sec

Additional time lag for Elevation: 0.000 sec

Simulator port:

For NEXRAD systems, use this section to configure the DCU interface. You must set the angle source questions in the axis sections to Custom to read these angles.

Use WSR-88D DAU Interface (BITE/Status): YES

Serial port: /dev/ttyS0

Baud rate for DAU: 19200

Choose None Odd Even

DAU data parity: Odd

ID of DAU standard BITE packets: 0x07

ID of Quantitative BITE packets: 0x08

Simulator port:

For NEXRAD systems, use this section to configure the DAU interface.

Use RVP10/IFD digital/analog I/O interfaces: NO

Use Kavouras TCU Interface (Radiate/BITE): YES

Serial port: /dev/ttyS0

ID of TCU standard BITE packets: 0x09

ID of Quantitative BITE packets: 0x0A

Simulator port: /dev/ttyS1

Choose which serial port and ID for the BITE and Q-BITE packets are associated with the TCU. Note that the serial baud rate, parity, and stop bits are fixed at 9600/Odd/2 because they are fixed by the TCU.

Use the built-in simulator for debugging the main code. To watch the live I/O from a real TCU, use the Monitor SIO command followed by Raw rTcu.

The standard BITE packet for the TCU is 13 bytes long, and maps the 64 TCU status bits into the first 64 packet bits. The timeout bit (no TCU communication) appears in the MSB of Byte #12. These 70 bits of BITE status (10 words of 7 bits each) are mapped to status bits S64-S133. To use any TCU status bits in a logic equation, grab those variables.

The Q-BITE packet is 27 bytes long and holds 12 14-bit values. The first two are the Max strike and Current strike counts from the TCU status packets, and the next 8 are from the temperature report. The last two slots (11 and 12) are unused.

The TCU is reset using the standard BITEresetting mechanism. A BITEX reset that is directed at the BITE or Q-BITE unit sends a reset command to the physical TCU. A rising edge on Control Variable C63 also resets the TCU.

The TrPower and Radiate control/status bits are the only ones needed for the TCU, giving you the states OFF, STANDBY, and RADIATE. When you toggle those two control bits, the appropriate commands are sent to the TCU. Likewise, status from the TCU sets the TrPower and Radiate status bits.

Use Radtec XCM Interface (Radiate/BITE):YES

Serial port: New Value

ID of XCM standard BITE packets: 0x09

ID of Quantitative BITE packets: 0x0A

offset of 70 mapped status bits: 64

Use IPA15HC Servo Amp interface: YES

AZ IP Address: New Value

EL IP Address: New Value

ID of regular BITE packets: 0x0C

offset of 133 mapped status bits: 128

Use Andrew-Canada serial pedestal interface: YES

Serial port: /dev/ttyS0

ID of Andrew BITE status packets: 11(decimal)

Map Andrew status into S[29:63] variables: NO

Apply boresite offsets to position angles: NO

Simulator port:

When the Andrew interface is enabled, you may hookup the serial lines either through a standard Linux TTY port such as /dev/ttyS0, or through the special io62-tty0 serializer that is built into the IO62 card firmware . RCP8 also contains a (minimal) serial simulation of a real Andrew ACU, which you can configure onto a TTY port for loop-back testing.

Normally RCP8 receives high-speed parallel AZ/EL angles from the Andrew ACU. However, if you set the axis angle source questions to custom, it sets RCP8 to use the low-speed (5 Hz) serial angle status information from the ACU instead. This option can be useful during testing.

Use Applied Systems TWT Transmitter: YES

Choose: 177 337 377

Model number of the transmitter: 337

Serial port: /dev/ttyS0

Offset of 29 mapped status bits: 64

Offset of 5 mapped control bits: 64

ID of Standard STS BITE packets: 0×0C

ID of Quantitative BITE packets: 0×0D

Simulator port:

When the Applied Systems interface is enabled, you may connect the serial lines through a standard Linux TTY port such as /dev/ttyS0, or through the special io62-tty0 serializer that is built into the IO62 card firmware. RCP8 also contains a serial simulation of a real Applied Systems TWT, which you can configure onto a TTY port for loop back testing. A blank device disables the simulation.

The different Applied Systems model vary in the status bytes returned.

Model 177 is: STX Digital Byte 1, Digital Byte 2, Digital Byte 3, Digital Byte 4, Analog 1 (4 characters), Analog 2 (4 characters), Analog 3 (4 characters), EXT Checksum. Total = 19 bytes

Model 377 has a fourth Analog value, for a total of 23 bytes, while model 337 also has a fifth Analog value, for a total of 27 bytes.

The analog fields translate into a Q-byte packet, as shown below. Depending on the model, the last values are missing, and the packet is shorter.

`Q-BITE` Packet
Char	Function
1	SYNC Byte (AF Hex)
2	Identification byte (User Choice)
3-4	Analog 1 (14-bits)
5-6	Analog 2
7-8	Analog 3
9-10	Analog 4 (for Model 377 and 337 only)
11-12	Analog 5 (for Model 337 only)
13	END OF MESSAGE (FF Hex)

Use Orbit serial pedestal controller: YES

Serial port: /dev/ttyS0

Offset of 33 mapped status bits: 64

ID of Standard STS BITE packets: 0×0E

Fixed time lag of Orbit angles: 1.0 ms

Simulator port:

Used for the Orbit pedestal controller. A blank device disables the simulation. Be sure to set the angle source questions in the axis sections to read these angles.

Use Dual-GigaCom serial Tx modulators: YES

Baud rate of the GigaCom interface: 19200

Serial port for Tx-A: New Value

Serial port for Tx-B: New Value

ID of BITE status packets for Tx-A: 0x05

ID of Q-BITE status packets for Tx-A: 0x06

ID of BITE status packets for Tx-B: 0x07

ID of Q-BITE status packets for Tx-B: 0x08

Fault mask for status bits <15: 0>: 0x77F6

Fault mask for status bits <31:16>: 0x0004

System switchover transition time: 2.0 sec

Debounce time for error status bits: 0.0 sec

GTX_RESET also resets active system: NO

Control bit for gtx_auto: 16

Control bit for gtx_reqb: 17

Control bit for gtx_hold: 18

Control bit for gtx_reset: 9

Status bit for gtx_trans: 20

Status bit for gtx_chanb: 21

Status bit for gtx_fault: 22

Use CAN-Bus serial control/status: YES

Use CAN-Bus to radar control: YES

Force shutdown for unresponsive antenna: YES

ID of Standard STS BITE packets: 0×0F

ID of Quantitative BITE packets: 0×10

Used for the CAN-Bus interface to control and monitor the Vaisala pedestal. To read these angles, you must set the angle source questions in the axis sections to Canbus.

Use dehydrator monitoring: YES

Choose: ETIserial CibredSNMP

Dehydrator type: CibredSNMP

SNMP IP address: 10.0.1.120

ID of Standard STS BITE packets: 0x26

ID of Quantitative BITE packets: 0x27

Monitor the status of the Cibred dehydrator thorugh SNMP interface. Dehydrator status includes the waveguide pressure, air flow, dehydrator run hours, and alarms for fault statuses (not responding, low pressure, high pressure, high humidity). These questions define the IP address of the dehydrator and the ID numbers of the generated Bite and QBite packets. For information on the packet formats, see Appendix Dehydrator BITE Packets.

Dehydrator type: ETIserial

Serial port: /dev/ttyS0

ID of Standard STS BITE packets: 0x11

ID of Quantitative BITE packets: 0x12

Monitor the status of the ETI ADH-2A dehydrator thorugh RS-422 interface. Dehydrator status includes the waveguide pressure, flow rate, device temperature, duty cycle, and alarms for fault statuses such as not responding, low pressure, dew point etc. These questions define the serial port to be used and ID numbers of the generated Bite and QBite packets. For information on the packet formats, see Appendix Dehydrator BITE Packets.

Use klystron connected in serial port: YES

Serial port: /dev/ttyS0

ID of Standard STS BITE packets: 0×14

ID of Quantitative BITE packets: 0×15

Control bit for fault log print: 30

Monitor the status of the Klystron transmitter in Vaisala WRK weather radars. The Klystron transmitters voltages, currents, and alarms are monitored. The status can be displayed on Bitex. This software thread retrieves status and measurement information through a serial interface (RS-422) and creates ITE and QBITE packets from it. For information on the packet formats, see Klystron BITE Packets.

Use Power Monitoring: YES

Frequency of the radar (MHz): 5625

Number of sensors: 4

Ser.No of horizontal forward sensor: 0

Ser.No of horizontal reverse sensor: 0

Ser.No of vertical forward sensor: 0

Ser.No of vertical reverse sensor: 0

Offset of 2 mapped status bits: 162

Control bit of rsenssor zeroing: 31

ID of Standard STS BITE packets: 0×16

ID of Quantitative BITE packets: 0×17

The Power Monitor thread opens a USB connection to the Rohde & Schwarz NRP power sensors. The weather radar may have 2 power sensors for each polarization on the waveguides measuring transmitted and received power level. When measurement is complete, BITE and QBITE packets are created. For information on the packet formats, see Power Monitor BITE Packets.

Use ARA ACU-3 Antenna: YES

Serial port: /etc/vaisala/irisrda/rcp8_ara_acu-y

Baud rate: 19200

Choose: None Odd Even

Data parity: Odd

ID of BITE status packets: 0×08

Fixed time lag of angles: 1.0 ms

Poll for position every 20 ms

Offset of 15 mapped status bits: 40

Control bit for reset: 40

Simulator Serial port: /etc/vaisala/irisrda/rcp8_ara_acu-x

If the ARA ACU-3 interface is enabled and you supply a serial port, the ARA_ACU3 thread is visible on the help view screen. If you put a string into the Simulator port, the screen shows the ARA_ACU3-Sim thread. The example above shows how to configure the simulator to talk to the main thread using FIFOs. You must create the 2 files using the mkfifo command.

There are 15 TSC TWT status bits output in the BITE packet. See ARA ACU-3 BITE Packet. For information on the bit meanings and command set, see the ICD.

These 15-bits are mapped to the specified status bits. The period at which RCP8 polls the ARA for position is set by the Poll position question. All other activity, such as polling for status, happens once a second. Command output occurs once a second unless there is a change.

Use TSC TWT Interface: YES

T/R Serial port: /etc/vaisala/irisrda/tsc_tr-y

Modulator Serial port: /etc/vaisala/irisrda/tsc_mod-y

ID of BITE status packets: 0×06

ID of QBITE status packets: 0×07

Offset of 23 mapped status bits: 20

Offset of 10 mapped control bits: 20

Simulator T/R Serial port: /etc/vaisala/irisrda/tsc_tr-x

Simulator Mod Serial port: /etc/vaisala/irisrda/tsc_mod-x

This is the TSC TWT transmitter used in the NOAA G4 aircraft. If you answer Yes to the initial question and supply either serial port, you get the TSC-TWT thread visible on the help view screen. If you put a string into either simulator ports, you get the TSC-TWT-Sim thread. The example above show how to configure the simulator to talk to the main thread using FIFOs. You must create these 4 files using the mkfifo command.

You can monitor the traffic transmitted and received from these 2 serial lines using the monitor sio command. Once you are in monitor mode, then type something like raw xtsc_tr rtsc_tr. Other available data is xtsc_mod and rtsc_mod.

For information on the TSC TWT BITE and QBITE packets, see TSC TWT Packets.

The TSC TWT simulator is fairly simple:

For the T/R port, it sends a 9-byte response containing all zeros, except for the first and last byte, and bytes 2 and 3 are copied from bytes 2 and 3 of the command (which have the same meanings).

The qualitative values are set to: Frequency code=50, Receiver protect leakage=100, Transmitter power=150, and Reflected power=200.
If no command, or a bad command arrives, then the whole payload is zero. For the Modulator port, it sends the string <1R0011?0000>\n, where the ? is set to 0 or 1 based on the command supplied.
If no command, or a bad command arrives, then the payload is all 0.

For best performance on an ARA controller, get the option for parallel outputs. If not, or if using a simulator, be sure to set the angle source questions in the axis sections to Custom to read these serial angles.

Use TDRS pedestal angle input: YES

Serial port: /dev/ttyS0

The TDRS pedestal has a serial interface to get angle information.

Use TDRS pedestal control output: YES

IP Address: 191.165.99.99

Port number: 32767

The TDRS pedestal is controlled via a socket interface. You can set the IP and port number here.

Use remote signal generator control: YES

Choose: Ethernet GPIB

Signal generator interface: GPIB

HPIB device name: siggen

RF/IF Signal generator is on the bus : YES

Signal generator has pulse modulation : YES

Use MELCO TKY01 Serial Q-Bite: YES

Serial port: /dev/ttyS0

Baud rate: 19200

ID of Quantitative BITE packets: 0×13

Simulator port:

You can read serial QBITE packets in MELCO Turkey-01 format. This message includes information from a generator and produces a QBITE packet. See MELCO Packets

Use remote signal generator control: YES

Ethernet GPIB Signal generator interface: Ethernet

Signal generator IP Address: 10.0.2.10

Signal generator Port Number: 5025

Answer the first question YES if a USB-to-HPIB interface module is plugged into a USB slot of the RCP8 computer, in which case its Linux device name is supplied on the next line. If a signal generator is attached to the bus, enter its HPIB address.

The first class of instruments supported are RF/IF signal generators. RCP8 can both control and sense the signal generators output power level, output On/Off switch, and pulse modulation selection. These parameters are then directly accessible from IRIS/Antenna utility.

RCP8 always keeps the signal generator in its normal local mode, and polls its settings every 0.5 seconds. This means that the signal generator's front panel is always fully functional. However, if RCP8 detects a change in the host computers requested settings, the changes are sent immediately to the signal generator. The correct settings are put in place, but you can still make further changes using the manual controls. The signal generator should appear to operate normally, unless changes are requested by the host computer.

When an HPIB signal generator is not installed on RCP8, the signal generator status sent back to the host computer is spoofed from whatever siggen settings the host computer is currently requesting. The RF-Level, On/Off, and Cont/Pulse status are all echoed back, and the fault status is FALSE (no fault).

For HPIB/GPIB support, you must install a new library for RCP8 to run. If you are installing a new system, this is covered in the sigconfig script, or in the steps described in IRIS and RDA Software Installation Guide (M211315EN). If you are upgrading, you must install a new rpm. This is supplied on our FTP site, and on the CDROM. The installation command is:

# rpm -Uhv linux-gpib-lib-3.2.09-1.EL.i686.rpm

If you use the GPIB feature, you must install the kernel module. There is a common kernel module rpm, and a version specific to the installed kernel. Vaisala provides the driver RPMs for CentOS7:

# rpm -Uhv linux-gpib-kmod-common-3.2.09-1.EL.i686.rpm
# rpm -Uhv kmod-linux-gpib-3.2.09-1.EL.2.6.9_5.EL.i686.rpm
# rpm -Uhv linux-gpib-kmod-common-3.2.09-1.EL.i686.rpm
# rpm -Uhv kmod-linux-gpib-smp-3.2.09-1.EL.2.6.9_5.EL.i686.rpm
# rpm -Uhv linux-gpib-kmod-common-3.2.09-1.el5.i686.rpm
# rpm -Uhv kmod-linux-gpib-3.2.09-1.el5.2.6.18_8.el5.i686.rpm

Use Pulse Systems TR-1163 Ethernet Interface:YES

IP Address: New Value

Port Number: 23

ID of BITE status packets: 0x20

ID of QBITE status packets: 0x21

Offset of 21 mapped status bits: 166

Control bit for transmitter reset: 0

Use EEC DDC pedestal control interface: NO

Use RPM pedestal control interface:NO

Use Dual/Redundant system configuration:NO

Generate trigger sector blanking output: YES

Hardware output line to use: None

Hardware input line to use: None

Include sector #1 in overall test: YES

Sector #1 uses pedestal angles: YES

Sector #1 lower azimuth: 0 deg

Sector #1 upper azimuth: 30 deg

Sector #1 lower elevation: 1 deg

Sector #1 upper elevation: 3 deg

Include sector #2 in overall test: NO

Include sector #3 in overall test: NO

Include sector #4 in overall test: NO

Include sector #5 in overall test: NO

Include sector #6 in overall test: NO

Include sector #7 in overall test: NO

Include sector #8 in overall test: NO

RCP8 can generate a trigger blanking output when the antenna falls within one the user-defined solid sectors in azimuth and elevation. Choose the remapped output line that should hold the blanking signal from: TrPwr SvPwr RdOff Reset IRS0 IRS1 IRS2 PW0 PW1 Rly AZ0. Choose an optional remapped input line to OR into the result from: TrPwr MagCr ILock Air WGPrs IRS0 IRS1 IRS2 PW0 PW1. For each sector that is enabled, choose whether Earth or Pedestal angles are to be used in the test, and the AZ and EL lower and upper limits.

The sector blanking latency is 3.5 ms. This latency is defined as the maximum time that can elapse between the antenna moving into or out of a blanked sector, and RCP8s mapped hardware output line that responds with that indication. The 3.5 ms latency is only realized when the mapped output line is AZ0 (LSB of the parallel azimuth output). All other output lines run with a 29 ms delay; as do any optional re-mapped input line that is fed into the blanking criteria. For example, at a 36 °/sec rotation rate, the 29 ms delay might have produced a 1.04° shift in the location of the blanked sector. The 3.5 ms delay would position the edge more precisely by introducing only a 0.13° shift.

Enable Shaft Encoder Simulator: YES

RCP8 can simulate the shaft encoder signals at 500 Hz. This only works at relatively slow antenna speeds. It produces outputs using the auxiliary control lines. The configuration is taken from the ax az and ax el setups.

The following table shows the output signals, including recommended cabling.

Shaft Encoder Output Signals
Signal	Control	Back Panel J9	Back Panel J3
`EL Index`	`C78`	`14`	`1`
`EL A`	`C76`	`15`	`2`
`EL B`	`C77`	`16`	`3`
`EL Prox`	`C79`	`17`	`8`
`AZ Index`	`C74`	`1`	`4`
`AZ A`	`C72`	`2`	`5`
`AZ B`	`C73`	`3`	`6`
`AZ Prox`	`C75`	`4`	`7`
`EL Limit Lo`	`C71`	`-`	`-`
`El Limit Hi`	`C70`	`-`	`-`

Inputting the hardware signals requires the following lines in the softplane.conf file:

splConfig.Io62[0].Opt.Cp.J3_01_14.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J3_01_14.iTerm = 0
splConfig.Io62[0].Opt.Cp.J3_01_14.pinPos = 
splConfig.Io62[0].Opt.Cp.J3_01_14.pinNeg = sAux[100]
splConfig.Io62[0].Opt.Cp.J3_02_15.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J3_02_15.iTerm = 0
splConfig.Io62[0].Opt.Cp.J3_02_15.pinPos = 
splConfig.Io62[0].Opt.Cp.J3_02_15.pinNeg = sAux[101]
splConfig.Io62[0].Opt.Cp.J3_03_16.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J3_03_16.iTerm = 0
splConfig.Io62[0].Opt.Cp.J3_03_16.pinPos = 
splConfig.Io62[0].Opt.Cp.J3_03_16.pinNeg = sAux[102]
splConfig.Io62[0].Opt.Cp.J3_04_17.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J3_04_17.iTerm = 0
splConfig.Io62[0].Opt.Cp.J3_04_17.pinPos = 
splConfig.Io62[0].Opt.Cp.J3_04_17.pinNeg = sAux[103]
splConfig.Io62[0].Opt.Cp.J3_05_18.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J3_05_18.iTerm = 0
splConfig.Io62[0].Opt.Cp.J3_05_18.pinPos = 
splConfig.Io62[0].Opt.Cp.J3_05_18.pinNeg = sAux[104]
splConfig.Io62[0].Opt.Cp.J3_06_19.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J3_06_19.iTerm = 0
splConfig.Io62[0].Opt.Cp.J3_06_19.pinPos = 
splConfig.Io62[0].Opt.Cp.J3_06_19.pinNeg = sAux[105]
splConfig.Io62[0].Opt.Cp.J3_07_20.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J3_07_20.iTerm = 0
splConfig.Io62[0].Opt.Cp.J3_07_20.pinPos = sProxSwAZ
splConfig.Io62[0].Opt.Cp.J3_07_20.pinNeg = 
splConfig.Io62[0].Opt.Cp.J3_08_21.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J3_08_21.iTerm = 0
splConfig.Io62[0].Opt.Cp.J3_08_21.pinPos = sProxSwEL
splConfig.Io62[0].Opt.Cp.J3_08_21.pinNeg =

Outputting the hardware signals requires the following lines in the softplane.conf file:

splConfig.Io62[0].Opt.Cp.J9_01_14.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J9_01_14.iTerm = 0
splConfig.Io62[0].Opt.Cp.J9_01_14.pinPos = cAux[74]
splConfig.Io62[0].Opt.Cp.J9_01_14.pinNeg = cAux[78]
splConfig.Io62[0].Opt.Cp.J9_02_15.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J9_02_15.iTerm = 0
splConfig.Io62[0].Opt.Cp.J9_02_15.pinPos = cAux[72]
splConfig.Io62[0].Opt.Cp.J9_02_15.pinNeg = cAux[76]
splConfig.Io62[0].Opt.Cp.J9_03_16.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J9_03_16.iTerm = 0
splConfig.Io62[0].Opt.Cp.J9_03_16.pinPos = cAux[73]
splConfig.Io62[0].Opt.Cp.J9_03_16.pinNeg = cAux[77]
splConfig.Io62[0].Opt.Cp.J9_04_17.lRS422 = 0
splConfig.Io62[0].Opt.Cp.J9_04_17.iTerm = 0
splConfig.Io62[0].Opt.Cp.J9_04_17.pinPos = cAux[75]
splConfig.Io62[0].Opt.Cp.J9_04_17.pinNeg = cAux[79]

To simulate the limit switches, use the following logic equations:

EQ00: # Set the lower limit switch
\--: sLowerEL = c71
EQ01: # Set the upper limit switch
\--: sUpperEL = c70

Automatically Calibrate Shaft Encoder: YES

Use this only on systems with shaft encoders.

This causes RCP8 to initiate an automatic calibration of the shaft encoders each time they become uncalibrated. If a calibration attempt fails, a failed flag is set and the calibration attempt does not repeat.

Resetting from shutdown clears the last failed state. Setting the lShaftForceCal logic control variable forces a new calibration by clearing the calibrate bit and failed bit for each axis.

While running, the auto calibration blocks normal control of the antenna, similar to the TTY monitor mode. The front panel SS1 and SS2 display show LockCal in this case.

The algorithm scans at 2 rpm in azimuth until calibrated. In elevation, it scans at 1 °/second down until the lower limit switch (it should disable shutdown while calibrating), then it goes up at 2 °/second until it is calibrated.

The elevation limit switch shutdown is disabled during auto calibration. The elevation shutdown limits are disabled until the elevation is calibrated. The calibration fails if the antenna travels more than 1.5 times the expected distance, or more than 2 minutes elapses before calibration.