User Manual

Table Of Contents
Maintenance RF-Orchestra!™ Transmitter Installation and Operation
6-88 6880493G02-C July 2000
user commands, and the appropriate data or parameter value should be entered instead
of the xxx shown in the procedure. This is explained at each section where the xxx is used
for system specific data or parameter values.
Downloadable RF-O! File: A downloadable file with the new software must be loaded
onto the TFTP server into the proper directory. The file name may contain the "dl"
designation and the release version number (i.e. rfo125dl), or may be stored as only the
release version number (i.e. rfo125). The file name must be entered into the RF-B!
transmitter controller exactly as it is stored on the TFTP server.
Note: For RFB_1.3.1 software and previous, the file to download to the RF-B! transmitter controller
is identified by an 8 character file name, and the file name MUST be exactly 8 characters. If the
RF-B! software is version 1.4.0 or later, the file name MUST be 5-7 characters.
TFTP Server/RF-Conductor: A TFTP server must be set up to act as the host that
downloads the file to the RF-B! transmitter controller. The TFTP server is identified by a
unique IP address that is used by the RF-B! transmitter controller to retrieve the file.
FIPS Session on RF-O!: Confirmation of download bank and progress of the download
can be monitored with a FIPS session on the RF-O! transmitter. If a FIPS session with the
RF-O! transmitter is not possible, the software download can still be accomplished. RF-O!
FIPS commands are shown in the procedure. The commands the user should enter at the
FIPS session are shown in bold text, and the expected response is shown on the following
line. A value of xxx may be shown with user commands, and the appropriate data or
parameter value should be entered instead of the xxx shown in the procedure. This is
explained at each section where the xxx is used for system specific data or parameter
values.
Software Download Procedure
Note: It is recommended that the download be performed during off-peak load times for highest
reliability and fastest completion. This also avoids high network congestion which can lead to
lower reliability.
A software-initiated reset (DIP 2) is done during the cutover to the new software version at the
end of a software download. Several parameters will be reset to their default values during
the reset. Some of these parameters may need to be preserved and will have to be reset to their