| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 374024 |
| Application ID | TcHjL3vkJsxJUlCWhrKsvQ== |
| Document Description | S10 RECEIVER AND PROCESSOR USERS MANUAL PART 3 |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 49.55kB (619358 bits) |
| Date Submitted | 2003-11-17 00:00:00 |
| Date Available | 2004-01-13 00:00:00 |
| Creation Date | 2003-05-12 17:15:55 |
| Producing Software | Acrobat Distiller Command 3.02b for HP-UX A.09.01 and later (HPPA) |
| Document Lastmod | 2003-11-14 17:34:53 |
| Document Title | Document: |
| Document Creator | Interleaf, Inc. |
| Document Author: | alan |
RVP8 User’s Manual
April 2003
Software Installation
A. Software: Basics, Installation and Backup
A.1 Overview
The RVP8 and RCP8 are implemented using standard PCI components with some custom cards
supplied by SIGMET. While seemingly very different products, these actually have very similar
hardware and software. The software installation, configuration and backup/recovery procedures
are nearly identical. For this reason, this appendix is written to cover both the RVP8 and RCP8.
This appendix covers the following topics:
Login, logout and shutdown
Section A.2
Software installation
Section A.3
Software configuration
Section A.4
System backup/recovery
Section A.5
Software upgrade
Section A.6
Network basics
Section A.7
Your system is shipped with all software installed so you are really ready to start using the unit
immediately after opening the box. You should read this appendix to become familiar with the
general operating procedures, especially the system backup procedures which will help you if
you ever need to re-install the software after a disaster or install an upgrade provided by
SIGMET.
Other references related to the software are:
RVP8 Programmer’s Manual: Describes the development environment, public
source and API’s provided by SIGMET.
IRIS Utilities Manual: Describes utilities for radar calibration, test and
maintenance that are shipped with the RVP8 and RCP8
A–1
RVP8 User’s Manual
April 2003
Software Installation
A.2 Basics of Login, Logout and Shutdown
The RVP8 and RCP8 both use the Linux operating system and X–Windows. When logging into
the RVP8 either locally or over the network via “telnet” you will need to supply a user name and
password. The system is tolerant of the AC power being suddenly turned-off, but in general it is
recommended to follow a power-off shutdown procedure. These procedures are described in this
section.
Important: For network security reasons, both the RVP8 and RCP8 are shipped
with remote access disabled. To learn how to enable telnet, refer to the end of
Section A.7.2.
A.2.1 Power up procedure
The power switch is located on the lower right front of the unit. When you power the unit on,
the RVP8 goes through an automatic startup of the operating system at the end of which the
RVP8 software and performs power–up self tests. This is described in detail in Section 2.3.5.
If you are not doing any diagnostic or software maintenance work on the system, there is no
need to log-in after power-up; simply turn the unit on and your application software will take
over. No operator intervention is required. However, to perform maintenance functions such as
software upgrades, testing and backup/recovery, you will need to log-in.
A.2.2 Local and remote login
There are two ways to login to the RVP8:
Local login: The local keyboard, mouse and monitor can be used. Note these
often are not connected on operational systems. SIGMET provides a keyboard
and mouse with each system. The monitor is optional and may be provided by the
customer, to SIGMET specification. Most VGA monitors will work.
Remote login: If telnet is enabled you can use this for remote access. Check
with your network administrator.
For the remainder of this discussion it is assumed that local login is used.
A.2.3 Default operator and root login passwords
There are two default users defined in the standard software installation:
”root” with password ”xxxxxxxx” (8 lower case x’s). This is for Operating
System maintenance functions.
”operator”with password ”xxxxxx” (6 lower case x’s). This is for RVP8
application software maintenance functions. For a complete list of supported
utilities see Section 1.6. These are all described in detail in the IRIS Utilities
Manual.
A–2
RVP8 User’s Manual
April 2003
Software Installation
Your system administrator can change either of these passwords by using standard Linux
password support.
A.2.4 Login procedure
Local login as operator after power-up
Connect keyboard, mouse and monitor and then cycle power on the system to
force a reboot. This causes Linux to recognize these devices on power-up.
At the power-up “login” prompt type “operator” and press Enter. When
prompted, provide the appropriate password (factory default is “xxxxxx”, 6 lower
case x’s).
Logging-in as operator you will be taken to an X-Window screen.
Right-click the mouse and select “New Window” to get a terminal window.
The top of the terminal window shows, for example:
operator on rvp8–1 : /home/operator
i.e., your user name, the node name of the system and the current directory path.
If you would like to have a terminal with a bigger font, you can type “sigterm”.
Switching from operator to root login using su"
The easiest way to switch to a root login for system administration work is to type the super user
command “su” and then give the root password. The prompt will change from $ to # indicating
that you are root.
Exiting su" root login to return to operator
In an X–terminal where you have become the “super user (su)”, simply type “exit” to return to
operator. The prompt will change from # to $.
Local root login after powerup
To login as root after a power–up or after exiting X–Windows, simply type “root” and press
Enter at the login prompt, then give the appropriate password (factory default is “xxxxxxxx”, 8
lower case x’s).
You will be in a full screen terminal. This is not as convenient as X–Windows since only one
terminal can be displayed on the screen.
If you need a second full screen terminal type “Alt-F2”. You can return to your
original terminal by typing “Alt-F1”. The other function keys can provide
additional terminals.
A–3
RVP8 User’s Manual
April 2003
Software Installation
A.2.5 Logout procedure
Logout from XWindows
Method 1: Right-click the mouse and select “Exit”.
Method 2: Simultaneously click “Ctrl-Alt-Backspace”.
You will be logged out and the screen will show the initial login prompt. on the full screen
terminal.
Root Logout from full screen terminal
If you logged–in as root from the power-up full screen terminal,
A.2.6 Poweroff shutdown procedure
If you need to swap PCI cards in the chassis, you must first do a poweroff
shutdown as described here..
As either operator or root type “poweroff”. The system will go through a shutdown sequence.
When it is done “Power down” will be displayed. At this point you can press the power switch
located on the right lower front of the chassis.
A–4
RVP8 User’s Manual
April 2003
Software Installation
A.3 Software Installation
A.3.1 When to perform software installation
When your unit arrives, it is shipped with all software installed. Therefore, software installation
is usually not necessary at the initial installation. There are two occasions when you might want
to re-install the software:
Installation of a new CDROM release from SIGMET.
Recovery in the event of disk corruption or failure.
A.3.2 Preparing for the installation
The following should be done before you perform the software installation:
Either locate or, if possible, make a backup of your custom configuration files per
Section A.5. If you have made a backup in advance, then you will make the
re–installation much easier.
Locate your software installation CDROM that was originally supplied by
SIGMET or perhaps you will perform an installation of an upgraded version
supplied by SIGMET. In the event that you need a software installation CDROM,
contact SIGMET (support@sigmet.com). These are provided free of charge by
SIGMET. However, the specific version that was originally shipped with your
system may no longer be available. In this case you will install an updated
version.
Make sure that all PCI cards are properly installed.
From the “as-Built” documentation that is supplied with your system, verify the
type of motherboard or SBC that is installed. If you cannot locate this, then you
can check directly on the board itself by removing the top cover of the unit. For
example, the Super Micro G2 motherboard is labeled in the rear left part of the
board (relative to the front of the chassis). You may need a flashlight to read:
Super P4DPE–G2
Connect the connector panel to the I/O-62 via the cable that is provided.
Connect the keyboard, mouse and monitor. Note that the VGA monitor is
typically supplied by the customer.
For the RVP8, the IFD should be installed and powered so that it can pass its self
tests later in the procedure. If an external reference clock is used for the IFD, then
this should be active so that the unit can pass self tests.
For complete information on hardware installation see Section 2.
Once you have completed these steps, go to Section A.3.3 below.
A–5
RVP8 User’s Manual
April 2003
Software Installation
A.3.3 Installing the system software
After you have prepared for the installation, as described in the previous section, you are ready
to install the software.
Initial software installation steps
Ready the unit with keyboard, mouse, monitor, etc. as described in the previous
section.
Switch the power on using the switch on the lower right front of the unit.
Press the eject button on the CDROM drive and when it opens, insert the RDA
CDROM into the drive.
When prompted, press Del to enter the setup (lower right of number pad).
Hint: If you get too busy inserting the CDROM and miss the BIOS setup
prompt, simply power the unit off and on to start again, this time with the
CDROM already in the drive.
Setting the BIOS
If the BIOS has been configured already during a previous installation or at the
factory, then you should skip this step.
Note that specific BIOS keystrokes and menus often change. Use this section as a
general guide.
Reset to Defaults: In the BIOS setup, reset BIOS to default parameters. This is
typically done by pressing F9 or in the Exit section and then confirming the
YES/NO question.
Set Time: In the Main section, set the system time and date to UTC. This is a 24
hour clock (8:00 pm = 20:00).
Enable Floppy: In the Main section, set Legacy Diskette A: 1.44MB 3.5”.
Set Device Boot Order: In the Boot section, select the boot order to be:
CDROM
Floppy
Hard Drive
(sometimes listed under “Removable Devices”)
Select SAVE and EXIT. The unit will reboot automatically from the CDROM.
A–6
RVP8 User’s Manual
April 2003
Software Installation
Booting from the RDA Installation CDROM
When the BOOT: prompt is presented, type the following command, depending
on the version of CPU that is in your system:
For Supermicro –G2 board type:
linux ks=cdrom:/ks/ks–gb–hda.cfg
For Supermicro –Q board type:
linux ks=cdrom:/ks/ks–100.had.cfg4.8
After typing the appropriate command press ENTER.
The software is installed automatically at this point. If prompted with:
“Would you like to initialize this drive?”,
select YES (using the TAB key) and then select ENTER.
After about 10 minutes, the CDROM ejects. Remove it. The PC reboots
automatically. Continue to next section.
Installation steps to enable automatic startup of the RDA software
At login prompt, login as: “root” and password “xxxxxxxx” (8 x’s)
If you are installing an RVP8, type:
chkconfig ––level 2345 dspexport_init on
chkconfig ––level 016 dspexport_init off
chkconfig ––level 2345 rvp8_init on
If you are installing an RCP8, type:
chkconfig ––level 2345 rcp8_init on
Logout of root by typing “exit”.
A–7
RVP8 User’s Manual
April 2003
Software Installation
Installation steps to “flash” FPGA’s in SIGMET devices
In this section you will be installing FPGA software into each of the SIGMET components. You
will need to make an inventory of what is in your system and then issue an “rdaflash” command
to each one as described below:
Login as “operator” with password “xxxxxx” (6 x’s)
You will enter X–Windows. Right click the mouse and start a terminal window.
For each SIGMET component (italic) type the appropriate command (bold):
SIGMET Component
Unit ID
If RVP8, type:
Standard RVP8/Rx Card
–0
rdaflash –program rvp8rx–0
Standard I/O–62 Card
–0
rdaflash –program io62–0
Standard Connector Panel
–0
rdaflash –program io62cp–0
Optional RVP8/Tx Card
–0
rdaflash –program rvp8tx–0
Optional 2nd RVP8/Rx
–1
rdaflash –program rvp8rx–1
If RCP8, type:
Standard I/O–62 Card
–0
rdaflash –program io62–0
Standard Connector Panel
–0
rdaflash –program io62cp–0
Do a system shutdown by typing “poweroff”
When “Power down” is displayed, turn power off with power switch on lower
right of front panel.
This completes the FPGA software installation.
A–8
RVP8 User’s Manual
April 2003
Software Installation
Reboot power-up check and RDA diagnostics
After you have completed the installation steps above, you should reboot the unit. You can
observe the progress of the reboot on the monitor. In addition, the front panel LED display will
show the time of the reboot and display diagnostic messages. Typically about 1 minute is
required for the system to complete reboot.
After the reboot is completed:
Verify that the front panel LED display does not indicate any faults.
Log-in as operator, run dspx and issue the “v” command. Check the results
against the example in Section 3.1.4. Note that both the IFD and connector panel
should be installed and connected. An example session is shown below:
$ dspx
Digital Signal Processor ’Chat’ Mode
Checking for code upgrades... Okay
(Type ^C to exit Chat Mode)
(hit “Esc” to start)
SIGMET Incorporated, USA
RVP8 Digital IF Signal Processor V1.10(Pol)
––––––––––––––––––––––––––––––––––––––––––
RVP8> v
Important: When you are done, type “quit” and then “Ctrl-C” to exit dspx.
Stop the rvp8 (or rcp8) process by typing:
$ killall rvp8 (or rcp8)
Run the following diagnostics and observe the results:
(for RVP8 and RCP8 systems)
$ rdadiags io62–0
tests I/O–62
$ rdadiags io62cp–0
tests connector panel
(for RVP8 systems only)
$ rdadiags rvp8rx–0
Run these also for any optional RVP8 cards such as:
$ rdadiags rvp8tx–0
tests RVP8/Tx
$ rdadiags rvp8rx–1
tests 2nd RVP8/Rx
Restart the RVP8 or RCP8 process by typing (for the RVP8 example):
$ rvp8 &
Verify that the restart messages show no faults.
A–9
RVP8 User’s Manual
April 2003
Software Installation
A.4 System Software Configuration
After the receiving your unit from the factory, or after software re–installation, there are several
configuration steps required to customize your system for your particular environment and
application. The configuration tools available for this are summarized in the table below.
Configuration
Tool
RDA
Device
Description of Configuration Features
setup utility
RVP8
Configures the local environment required to run RVP8 the support utilities
such as ascope and dspx. Examples include radar equation parameters
that are required for calibration, pulse width definitions and PRF request
limits.
setup_ant.conf
RCP8
Configures the local environment required to run the RCP8 support utilities
that such as antenna or bitex. Examples include, max allowed AZ/EL ve
locity request, MIN and MAX elevation angles that can be requested and
LAT/LON of radar for sun tracking.
TTY setups
RVP8
Defines the details of the sampling and processing algorithms as well as
the operational configuration of the system. Examples include, IF filter de
sign and selection, PRF limits, relative trigger timing, dual polarization fea
tures.
rcp8.conf
RCP8
Used to configure which status and control bits are available and define the
antenna servo control parameters. Examples include, physical or virtual
tachometer selection, shutdown safety criteria and internal antenna simula
tor on/off.
softplane.conf
RVP8
File that is edited which defines the various I/O signals on the I/O62 con
nector panel, pin
by pin. For example, whether a line is an input or output,
pinbypin.
electrical spec such as RS422 or TTL, what local variable name is associat
ed with each line.
setup_dsp.conf
rvp8.conf
RCP8
Important: Both the setup utility and the TTY setups must be configured to
customize your system. This is part of the installation procedure.
All of the configuration results are stored as ASCII text “.conf” files, typically in a directory
called /usr/sigmet/ (factory default). The file names are indicated in the table above. Each file
has a factory default configuration file that is stored in the template directory (the default is
/usr/sigmet/config_template/init/). An advantage of this approach is that for a radar network
with identical hardware, configuration maintenance can be performed by copying pre-tested files
over the network.
The following serve as references and are not repeated here:
setup utility
IRIS Utilities Manual
RVP8 TTY setups
RVP8 User’s Manual
RCP8 TTY setups
RCP8 User’s Manual
The configuration of the softplane.conf file is described below.
A–10
RVP8 User’s Manual
April 2003
Software Installation
A.4.1 Configuring the softplane.conf file
What is the softplane.conf file ?
The softplane.conf file is used to define pin–by–pin assignment of I/O functions to various
connectors on the I/O-62 connector panel. It is a plain text ASCII file that is self-documented.
Since the RVP8 and RCP8 have virtually no jumpers, or wirewrap, all I/O configuration on the
I/O-62 connector panel is done by software approach according to this file.
Where is softplane.conf ?
The file resides in the IRIS_CONFIG directory. Typically this is /usr/sigmet/config (this is the
default directory that is factory installed). The factory configurations are also available in the
/usr/sigmet/template/init directory so that you can always return to the factory defaults if you
need to.
When do I need to change softplane.conf ?
The softplane.conf file that is shipped with your system is configured for a standard connector
panel with I/O as described in Appendix B. As long as you use the standard I/O pin
assignments, then you do not need to change softplane.conf.
If you need to redefine some of the I/O pins on the connector panel, or add additional SIGMET
cards such as a second I/O-62 then you must change softplane.conf.
Editing softplane.conf
You will need to use a text editor to modify the softplane.conf file. There are two editors
included in the system:
vi
The generic UNIX editor that is available on every UNIX system.
It is really arcane to use, but many people know how to use it out of necessity or
they are simply used to it now.
emacs:
This is more user friendly with keyboard commands and mouse
support when you are in X–Windows so it a little easier to learn than vi.
If you are not familiar with either of these, then you will need to either find someone who is or
learn how to use these tools.
To start an editing session you would do the following as operator:
$ cd /usr/sigmet/config
$ vi softplane.conf
or
A–11
emacs softplane.conf
RVP8 User’s Manual
April 2003
Software Installation
softplane.conf file example
An example from the beginning and some excerpts from the softplane.conf file are shown below
(note that the command “cat” causes the file to be listed on a terminal):
cat /usr/sigmet/config/softplane.conf
**********************************
* Softplane Configuration File *
**********************************
# The following general purpose control and status signals
# can be routed to/from any available hardware pin. The ’~’
# prefix character may be used for signal inversion.
Control Outputs
Status Inputs
–––––––––––––––––
–––––––––––––––
cPedAZ[15:0]
sPedAZ[15:0]
cPedEL[15:0]
sPedEL[15:0]
cEarthAZ[15:0]
sServoPwr
cEarthEL[15:0]
sLocal
cServoPwr
sStandby
cCabinetRelay
sLowerEL
cTransmitPwr
sUpperEL
cPWidth[3:0]
sTransmitPwr
cTrigBlank
sTransmitLocal
cRadiateOn
sPWidth[3:0]
cRadiateOff
sTrigBlank
cReset
sRadiate
cIrisMode[2:0]
sAirflowFlt
cAux[63:0]
sWavegpFlt
true
sInterlockFlt
false
sMagCurrentFlt
sReset
sIrisMode[2:0]
sAux[319:0]
splConfig.sVersion = ”7.32”
# ––––––––––––––––––– IO62 Slot #0 –––––––––––––––––––
splConfig.Io62[0].lInUse = 1
# The remote backpanel type should be one of the following:
Direct : Direct I/O with IO62 connector itself
IO62CP : Standard IO62–CP connector panel
RVP88D : RVP8 portion of WSR88D panel
RCP88D : RCP8 portion of WSR88D panel
splConfig.Io62[1].sExtPanel = ”IO62CP”
# TTL/CMOS on J1
splConfig.Io62[0].Opt.Cp.J1.pin01 = ”sPedAZ[0]”
splConfig.Io62[0].Opt.Cp.J1.pin02 = ”sPedAZ[1]”
splConfig.Io62[0].Opt.Cp.J1.pin03 = ”sPedAZ[2]”
...
A–12
RVP8 User’s Manual
April 2003
Software Installation
# Relays and relay drivers on J6
splConfig.Io62[0].Opt.Cp.J6_IntRelay1 = ””
splConfig.Io62[0].Opt.Cp.J6_IntRelay2 = ””
splConfig.Io62[0].Opt.Cp.J6_IntRelay3 = ””
splConfig.Io62[0].Opt.Cp.J6_ExtRelay1
splConfig.Io62[0].Opt.Cp.J6_ExtRelay2
splConfig.Io62[0].Opt.Cp.J6_ExtRelay3
splConfig.Io62[0].Opt.Cp.J6_ExtRelay4
””
””
””
””
# BNC testpoint monitors
splConfig.Io62[0].Opt.Cp.J13_BNC = ””
splConfig.Io62[0].Opt.Cp.J16_BNC = ””
# BNC trigger drivers direct from IO62 PCI card.
# Special signals ’trigger[8:1]’ may also be used here.
splConfig.Io62[0].Opt.Cp.J14_BNC = ””
splConfig.Io62[0].Opt.Cp.J15_BNC = ””
splConfig.Io62[0].Opt.Cp.J17_BNC = ””
splConfig.Io62[0].Opt.Cp.J18_BNC = ””
# RS232 TTY transmitters from IO62
splConfig.Io62[0].Opt.Cp.TTY0_Tx = ””
splConfig.Io62[0].Opt.Cp.TTY1_Tx = ””
# ––––––––––––––––––– IO62 Slot #1 –––––––––––––––––––
splConfig.Io62[1].lInUse = 0
# ––––––––––––––––––– IO62 Slot #2 –––––––––––––––––––
splConfig.Io62[2].lInUse = 0
....
A–13
RVP8 User’s Manual
April 2003
Software Installation
softplane. conf organization and syntax
The softplane.conf file is used to define every I/O pin on every connector, on the PCI cards
themselves and on the connector panel. There are two primary definitions that are made for each
pin:
Physical interface- the electrical properties (RS422 output, analog input, TTL
output, etc.).
Logical interface- The internal variable name that is associated with each pin.
With this in mind, we can describe the syntax of the file.
“#” at the beginning of a line indicates a comment. These are used for internal
documentation and if you make changes you should comment them, for example
# TTL I/O on J7
# Modification by REP on 2 Apr 03
# Added new interlock input on connector panel J7 pin07
...
The top part of the file provides a list of internal variables names that are used to
define the logical interface to the softplane. These are divided into status inputs
(also called indicators) and control outputs (also called requests). For example,
sPedAZ0 corresponds to the LSB of a digital azimuth angle relative to the
antenna pedestal. The tables on the next page provide a summary of the available
status and control variable names.
Important: This table is subject to change
Each definition line in the file starts with the keyword text:
# splConfig...
The first un-commented line of the file indicates the version of the IRIS support
software that was last used to machine–generate the file. This is an information
only field for traceability purposes and is thus not edited. In the example we have
this shown as:
# splConfig.sVersion = ”7.32”
A–14
RVP8 User’s Manual
April 2003
Software Installation
Summary of softplane.conf Status and Control Bits
Control Output
Meaning/Interpretation
cPedAZ[15:0]
16 bits of antenna azimuth angle relative to the pedestal (fixed base system)
cPedEL[15:0]
16 bits of antenna elevation angle relative to the pedestal (fixed base system)
cEarthAZ[15:0]
16 bits of antenna azimuth angle relative to the earth (moving platform)
cEarthEL[15:0]
16 bits of antenna elevation angle relative to the earth (moving platform)
cServoPwr
To control servo power on
cCabinetRelay
To control a relay signal
cTransmitPwr
Request transmit power on
cPWidth[3:0]
Request one of four pulse widths
cTrigBlank
Trigger blanking signal
cRadiateOn
Request radiate on
cRadiateOff
Request for radiate off
cReset
Request a reset of external equipment
cIrisMode[2:0]
Request the application software (e.g., IRIS) to switch to 1 of 8 operating modes.
cAux[63:0]
Arbitrarily assigned output requests
true
Internal logic variable
false
Internal logic variable
Status Input
Meaning/Interpretation
sPedAZ[15:0]
16 bits of antenna azimuth angle relative to the pedestal (fixed base system)
sPedEL[15:0]
16 bits of antenna elevation angle relative to the pedestal (fixed base system)
sServoPwr
Servo power on indicator
sLocal
Antenna local mode indicator, usually tied to an external local/remote switch.
sStandby
Radar ready to radiate indicator
sLowerEL
Lower limit switch indicator
sUpperEL
Upper limit switch indicator
sTransmitPwr
Transmitter cabinet power on indicator
sTransmitLocal
Transmitter local mode indicator, usually tied to an external local/remote switch.
sPWidth[3:0]
Indicator of the current pulse width
sTrigBlank
Indicator that trigger blanking is requested, usually from an external source.
sRadiate
Radiate on indicator
sAirflowFlt
Cooling airflow fault indicator
sWavegpFlt
Wave guide pressure fault indicator
sInterlockFlt
Master interlock fault indicator
sMagCurrentFlt
Transmitter overload fault indicator
sReset
Request for reset coming from external source
sIrisMode[2:0]
Information on which operating mode is active in the application software
sAux[319:0]
Arbitrary status indicators
A–15
RVP8 User’s Manual
April 2003
Software Installation
Next, each piece of hardware is identified as being either in use or not in use.
splConfig.Io62[0].InUse = 1
splConfig.Io62[0].InUse = 0
if in use
if unused or not installed
Currently, the I/O-62 is the only I/O device supported by the softplane.
The method of connecting to the I/O-62 is specified next, for example:
splConfig.Io62[0].sExtPanel = ”DIRECT”
Currently, the options are:
Type of Connection
softplane
Descriptor
Direct connect to I/O-62 via 62 pin connector
DIRECT
I/O-62 Connector Panel (used for RVP8 and RCP8)
IO62CP
WSR88D connector panel, RVP8 portion
RVP88D
WSR88D connector panel, RCP8 portion
RCP88D
The assignments for each connector and each pin are then made. For
convenience, these are usually grouped together by connector. For example let’s
say that , Pin 1 of connector J1 on the I/O-62 connector panel is assigned to be
the LSB of the input azimuth angle, i.e.,
# TTL/CMOS on J1
splConfig.Io62[0].Opt.Cp.J1.pin01 = ”sPedAZ[0]”
...
The notation ”” indicates that no assignment is made.
# BNC testpoint monitors
splConfig.Io62[0].Opt.Cp.J13_BNC = ””
In the example above the “pin name” is J13_BNC.
Putting a ~ in front of a logic variable inverts the variable.
splConfig.Io62[0].Opt.Cp.J1.pin03 = ”~sPedAZ[2]”
Check in the /usr/sigmet/config_template/init directory for other examples of softplane
configurations.
A–16
RVP8 User’s Manual
April 2003
Software Installation
A.5 System Backup and Recovery
Because both the operating system and the RDA software are contained on the RDA CDROM,
in the event of a serious failure, the complete software is simply re-installed from scratch. There
are however, a few files that contain your custom configurations. In general these are files in the
/usr/sigmet/config directory and the /etc directory. In fact, since they are all simple text files,
they will, in most cases, fit onto a 1.44 MB 3.5” floppy diskette.
SIGMET provides two utilities for backup/restore:
rda_backup- finds all files modified after the original installation (or
re–installation), puts them into a compressed UNIX “tar” file and copies the result
to either a floppy disk or a directory on the hard disk. System created files in
directories such as /tmp and /var are excluded from the backup.
rda_restore- restores the contents of a backup tar file from floppy disk to the hard
disk to the RVP8.
In the case where the backup tar file is written to a directory on the hard disk, the user can then
use ftp to put it on another computer on the network, or alternatively, put the file on CDROM
via the CDRW device. This section describes the use of the rda_backup and rda_restore utilities.
A.5.1 System Backup
When to make a backup
You should make a backup whenever you have made a change to the configuration of your
system: Examples include:
Changing softplane.conf or other .conf files in /usr/sigmet/config.
Changing files related to networking or security in /etc.
SIGMET does not recommend that you attempt to backup individual files. Instead you should
use the backup procedure described here since it will make the restore much easier, plus you
might miss something important that rda_backup will find.
Backup Media
There are two primary media for backup:
1.44 MB floppy disk drive (FDD)
A directory on the local hard disk drive (HDD)
In most cases you will use the 1.44 MB FDD approach. You would backup to an HDD directory
in the event that a backup, because it is too large, fails on the floppy .
If you use the HDD approach you must either transfer the backup to a
CDROM via the CDRW, or use ftp to copy files to another machine. See Section
A.5.3 for the procedure.
The next two sections describe how to prepare these two media.
A–17
RVP8 User’s Manual
April 2003
Software Installation
Preparing the floppy backup media
Every time you backup, you should use a freshly formatted floppy. It is possible to have several
backups on a single floppy, but this is a bit risky if that diskette fails. Indeed some system
managers even make two backups for added security. This is a smart thing to do.
There are three ways to format a floppy:
Purchase formatted floppies. This is the easy way.
Format the floppy on a Windows machine. Simply select the floppy drive
(usually A:) under “My Computer” and then right click the mouse to select
“Format”
Use Linux to format the floppy. The command (as root) is:
# mkfs.msdos –v –n RVPBACKUP /dev/fd0
Here the text RVPBACKUP serves as the DOS volume label for the floppy. For and RCP8 use
the text RCPBACKUP. You can use other text if you want, but do it in upper case with no spaces
or special characters. It is also assumed that the floppy drive is /dev/fd0.
After you have a formatted floppy, the next thing to do is to LABEL IT, for example, write on
the label
RVP
Date e.g.,YYMMDD
A–18
RVP8 User’s Manual
April 2003
Software Installation
Mounting the floppy backup media
Insert the floppy disk into the drive and then mount it (first use the su command to become
root):
$ su
Password:
# mount /dev/fd0 /mnt/floppy
If there is a problem with this, check that there is a directory called /mnt/floppy. If not, create it
as root with:
# mkdir /mnt/floppy
It is a good idea to make sure that the floppy does not contain anything from a previous backup
that you want so after you mount it check it with:
# cd /mnt/floppy
# ls –als
If the floppy disk contains files from a previous backup that you want to keep, select another
disk.
Preparing a hard disk backup directory
In the case that you are using a directory on the hard disk, as operator create a directory such as
/tmp/backup.
$ cd /tmp
$ mkdir backup
Backup files will be written to this directory with unique, machine generated file names that
contain the YYMMDDHHMMSS time code.
A–19
RVP8 User’s Manual
April 2003
Software Installation
Running rda_backup
After the media has been prepared and mounted (in the case of an FDD), then simply type the
command:
for floppy disk back-
$ rda_backup –v /mnt/floppy
up
In the case of a hard disk backup to a directory such as /tmp/backup you would type:
for hard disk backup
$ rda_backup –v /tmp/backup
The rda_backup utility will then check all of the directories where you have likely made
configuration file changes. Any files that were modified since the original installation will be
included in the backup.
If you use the –v option when starting rda_backup, then a listing of files will be displayed on
the terminal. When the backup is complete, the terminal will show:
...
Backup Complete:
0.9 MB
20 Files
Un-mounting and removing the floppy
To unmount the floppy, become root via the “su” command and type:
$ su
Password:
# cd /
# umount /dev/fd0
You may now push the eject button on the front of the drive to remove the floppy. Double check
that it is labeled with the proper date.
The most common problem encountered when un-mounting is that the FDD is “in use”. This
means that a terminal is in the /mnt/floppy directory. Typing “cd /” will take a terminal out of
the FDD directory.
A–20
RVP8 User’s Manual
April 2003
Software Installation
A.5.2 System Recovery
Recovering an entire system
In the event that your system becomes “un–bootable” perhaps because of a disk failure or
corruption, you will simply re–install the entire system per Section A.3.3, and then use your
rda_backup floppy disk and the rda_restore utility to recover your custom configuration files.
Recovering the configuration files is described below:
In the event of a hard disk failure, you will first need to replace the standard
IDE hard disk before attempting to recover your system. Most computer stores
will carry such a disk or you can contact support@sigmet.com to purchase a
new one.
Mounting the floppy or CDROM
If you are recovering from a floppy drive or CDROM, then you must first mount these devices.
Mounting the floppy is described in Section A.5.1.
Mounting the CDROM is described in Section A.6.5.
You must be root to mount devices. Use the “su” command to switch from
operator to root. Type “exit” to switch back to operator.
After the floppy is mounted, you should check to verify that the backup file that you want is
indeed on the disk. Do this as follows:
$ cd /mnt/floppy
$ ls –als
This will give you a listing of files on the floppy. The procedure for a CDROM is the same
except the device is /mnt/cdrom.
Running rda_restore
After the media has been mounted, run the rda_restore utility as operator. In the example
below, it is assumed that the device is /mnt/floppy.
$ rda_restore –v /mnt/floppy
Other possible devices are a CDROM (e.g., /mnt/cdrom) or a hard disk drive directory (e.g.,
/tmp/backup). The –v command will provide a list of all files that were restored. At the end of
the restore you will get a message:
...
Restore Complete
0.9 MB
20 Files
All that remains is to unmount and remove the floppy (this is done as root) as described below.
A–21
RVP8 User’s Manual
April 2003
Software Installation
Un-mounting and removing the floppy or CDROM
In the case of a floppy, become root and then issue the “umount” command:
$ su
Password:
# cd /
# umount /dev/fd0
(Note: spelling is indeed “umount”)
You may now push the button to eject the floppy.
For a CDROM, you can use the eject command (instead of “umount”):
# eject
This completes the restoration of your custom configuration files.
A.5.3 Transferring a backup file from the RVP8 hard disk
If you used rda_backup to make a backup file on the hard disk (e.g., in the /tmp/backup
directory), then you need to transfer this file to another medium for safety in case the hard disk
fails. There are three options:
ftp to another networked computer
Copy to the floppy
Copy to the CDROM
These are described below.
ftp to another computer
This assumes that there is another computer on the network, that you know its IP address or it is
configured in your /etc/hosts file and that the security settings on the other computer permit ftp.
Check with your network manager to verify these criteria.
For this example, it is assumed that you made your backup to a directory called /tmp/backup and
that you are going to send it to another computer in the /tmp directory. To copy the backup file
login as operator and in an X-Terminal type:
$ cd /tmp/backup
(or use the actual directory if different)
$ la –als
(to view the files in the directory)
Identify the file that you want to transfer via ftp and write down its name, then:
$ ftp
ftp> cd /tmp
ftp> put
ftp> quit
The backup file is now on the other computer in the directory /tmp
A–22
RVP8 User’s Manual
April 2003
Software Installation
Copy to a floppy
First check the size of the backup file to determine if it will fit on a floppy. To do this for backup
files stored in /tmp/backup:
$ cd /tmp/backup
$ ls –als
The file size in bytes is shown just to the left of the date column. To fit on a floppy the backup
file that you want to copy it must be less than 1,440,000 bytes (1.44 MB). If it is larger than this
you cannot use the floppy approach.
Note backup filename that you want to copy from the /tmp/backup to the floppy. Then:
Mount the floppy as described in Section A.5.1.
Copy the file to the floppy using the cp command:
# cp /tmp/backup/ /mnt/floppy
where the filename corresponds to the backup file that you want to copy.
Verify that the file was properly copied by typing:
$ cd /mnt/floppy
$ ls –als
Un-mount the floppy as root with the commands:
# cd /
# umount /dev/fd0
Copy to a CDROM
For large backup files that exceed 1.44 MB, then you can use the CDRW to write a CDROM.
To do this cd to the root of the directory you want to make into a cdrom. Using the example of
backups stored in /tmp/backup, as operator type,
# cd /tmp/backup
# mkisofs –v –V ”RVP8 SETUP” –o /tmp/rvp8.iso /tmp/backup
Where the volume label is arbitrary text specified in the quotes (e.g., ”RVP8 SETUP”), file
/tmp/rvp8.iso is the the temporary iso image file you are building. You can call this anything. To
actually burn the cdrom, place a blank write-once or re–writeable disk into the CDRW and then
type:
# cdrecord –v speed=8 dev=0,0,0 –eject /tmp/rvp8.iso
(Note the comma delimiters in 0,0,0)
The specific options might be a bit different based on hardware. For example the max speed, or
the device if there are more than one scsi devices. You can type ”cdrecord –scanbus”
to see all the scsi devices. If the CDROM drive is not in the list then you cannot use this
procedure. However, for a standard SIGMET installation it will show in the list.
A–23
RVP8 User’s Manual
April 2003
Software Installation
A.6 Software Upgrade and Support
A.6.1 Where to get software upgrades
The RVP8 and RCP8 (collectively the RDA) are active products. New features and bug repairs
are provided in the form of software upgrades. Software upgrades from SIGMET can be
obtained from two sources:
RDA Network Upgrades- These are available from ftp.sigmet.com. For
example, to obtain the release RDA 8.00 you would go to:
ftp.sigmet.com/outgoing/releases/rda–8.00
Section A.6.4 shows a typical ftp session. These public releases are FREE of
charge but do not include support services unless you are under warranty or have
purchased a support contract from SIGMET. Contact support@sigmet.com if you
need to arrange a support contract.
CDROM Upgrades- these are provided as part of a support contract and contain
manuals and source code as well as the operational software.
A.6.2 When should I upgrade
If your system is working fine and you do not require the new features of a release, then often
the best thing is to NOT upgrade. Check the release notes available at www.sigmet.com in the
customer support section to see what changes have been made since your current release was
installed. Be sure to check the release notes for all intervening releases.
To check the release that you have currently installed, you can type the command:
$ show_machine_code –version
IRIS Version 8.00
(indicates version 8.00)
A.6.3 How should I upgrade
There are two basic upgrade techniques:
CDROM Full Re-Install- Backup your configuration files and network files and
then do an install from scratch as described in Section A.3.3. This is not the
preferred technique since it is possible that the backup of configuration files will
be incomplete.
Upgrade using “install” utility- This is the preferred technique since it leaves all
configuration files intact. This is described in Section A.6.5.
Once you have decided on either a network or CDROM upgrade, then proceed with the upgrade
installation as described in the sections below.
A–24
RVP8 User’s Manual
April 2003
Software Installation
A.6.4 Getting the network upgrade files
There are two ways to get the network upgrade files. Both techniques use ftp to get the files
from ftp.sigmet.com. The ftp client service is enabled on the RVP8 allowing you to run an ftp
session on the RVP8 and “get” files from another networked computer:
Use the RVP8 to get the files- a one-step procedure that requires that you have
internet access from the RVP8.
Use another machine on the network– a two-step procedure to first ftp the files
from SIGMET to another computer, and then “get” them from this machine by
running ftp on RVP8. Note that an alternative is to copy the files to a CDROM
and then mount the CDROM on the RVP8 and copy the files.
No matter what technique you use, you will need some basic familiarity with ftp. Here we will
assume that the RVP8 has direct internet access (the one-step procedure). The two-step
procedure is analogous.
Important: The default security configuration allows the ftp client to run locally
on the RVP8, but does not allow ftp access from other systems to the RVP8.
Therefore, you must always run ftp from the RVP8 to “get” the files there.
The one-step approach: Direct download to RVP8
On the RVP8, create a directory called /tmp/rda–X.XX. Here the X.XX is the
version number of the RDA software that you want to install. This naming
convention makes it easy to identify the version of the install files. As operator
type (assuming version 8.00 for all examples here):
$ cd /
$ mkdir /tmp/rda–8.00
Position yourself in the /temp directory by typing:
$ cd /tmp/rda–8.00
Note that on a windows machine, all of the commands below can be typed in the MS–DOS
prompt window (remember to use the “\” backslash for DOS).
Start ftp and follow the sample session below (your responses are indicated by
bold)
$ ftp ftp.sigmet.com
Connected to ftp.sigmet.com
220 Welcome to SIGMET
Name: anonymous
331 Guest login ok, send your complete e–mail address as password.
Password:
Source Exif Data:
File Type : PDF
File Type Extension : pdf
MIME Type : application/pdf
PDF Version : 1.4
Linearized : No
Create Date : 2003:05:12 17:15:55Z
Modify Date : 2003:11:14 17:34:53-05:00
Page Count : 105
Creation Date : 2003:05:12 17:15:55Z
Producer : Acrobat Distiller Command 3.02b for HP-UX A.09.01 and later (HPPA)
Author : alan
Mod Date : 2003:11:14 17:34:53-05:00
Metadata Date : 2003:11:14 17:34:53-05:00
Creator : alan
Title : Document:
EXIF Metadata provided by EXIF.tools