The LEDR radio’s firmware can be upgraded with new software
releases that may be issued from time-to-time by Microwave Data Systems. To support firmware upgrades while the radio is in use, the LEDR
radio contains two complete copies of its firmware. Once the inactive
version is replaced, the radio can be rebooted using the code in the new
firmware. However, if an error occurs during the download, the radio
can easily recover because it always has a complete copy of firmware
available.
Reprogramming can be done through three common options:
1. Locally through the front panel
2. Locally using TFTP and Telnet through the
3. Remotely over a network connection using TFTP and Telnet to the
ETHERNET Port .
The procedures that follow use one or both of two utilities found in
MDS’ LEDR Utilities package. These utilities will facilitate local and
remote transferring of firmware files to and from the LEDR radio. These
applications are available from Microwav e Data Systems on floppy disk
(P/N 03-3631A01) or on MDS’ Internet sites FTP section of the primary
site of www.microwavedata.com.
The following sections will explain how to program new firmware into
the radio using each of the three connection options. They assume the
LEDR Utilities are installed on each computer system named in the procedure.
NOTE: The ETHERNET, SERVICE CHANNEL and CONSOLE Ports
share a common data channel when loading firmware
over-the-air. Transferring the radio firmware image file (≈ 1
MB), may take up to 30 minutes if there is other activity on any
of the other ports.
CONSOLE Port .
ETHERNET Port .
Regardless of your connection to the LEDR radio, loading
data/firmware into the radio’s SRAM is much slower than
loading software onto a PC hard drive or RAM.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide93
8.2OPTION 1: Uploading Firmware via the
This method of upgrading the firmware is well suited to field service
personnel that carry a laptop PC to field installation. Any computer running the Windows operating system is suitable. Figure 17 shows the
basic arrangement.
FLASH
UTILITY
INITIATE UPLOAD
FROM HERE
Figure 17. Direct connection through the LEDR CONSOLE Port
CONSOLE Port
Invisible place holder
LEDR RADIO UNITWINDOWS PC
9-PIN SERIAL CABLE
COM1, 2, ETC.
(DTE)
CONSOLE PORT
(DCE)
Setup
Connect a PC to the radio’s front panel
CONSOLE Port using a 9-pin
RS-232 cable. (See Figure 33 on Page 129 for cable wiring details.) The
CONSOLE Port supports RS-232 at 9600 bps to 38.4 kbps.
Download Procedure
1. Start the MDS MDS Flash Utility application.
2. From the
baud rate. Ensure that
View>Options menu, select the appropriate COM Port and
autobaud is enabled (Look in the lower
right-hand corner of the Flash Utility window).
3. From the
dow to the LEDR radio. At the
View menu, select console. This will bring up a NMS win-
LEDR> prompt, enter a login name
and password and then close the session.
4. Using the
ware is located. In the file window, highlight the correct (
and then press the green
File|Open dialog, select the directory where the new firm-
.mpk) file
start arrow.
94LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
Verification and Reboot
1. To verify the correct operation of the new firmware, open the NMS
again by pressing
Alt + L. Enter boot to determine which image is
currently active. This command will respond as follows:
boot: Image 1 is Active or, boot: Image 2 is Active
2. The new firmware is do wnloaded into the inactive image. Therefore,
if the radio responded
mand,
iverify 2, otherwise, enter iverify 1. The radio will respond indi-
Image 1 is Active, enter “image verify” com-
cating whether or not the image has been verified as being a valid
file, it will not determine if the contents are complementary to the
other firmware image. If the image does not verify, try downloading
the firmware again into the radio.
NOTE: The following paragraph describes rebooting the radio. This
action will disrupt the communications link.
3. Once the image has been verified, the radio must be rebooted using
the new firmware. This is done by entering the command
boot 2, where the 1 or 2 corresponds with the image number used
with the
iverify command above.
boot 1 or
4. Once the radio has rebooted and Flash Utility screen displays the
LEDR> prompt, the firmware can be downloaded or copied into the
other image. Often, copying the firmware from one image to the
other can be faster than performing a second download. To copy the
firmware over to the other image, simply enter
prompt you for confirmation (
y/n) and then begin copying.
icopy. The radio will
8.3OPTION 2: Uploading Firmware Locally by
Telnet via Ethernet
This method can be used in the field or in a workshop by using a Windows computer equipped with an Ethernet interface. Figure 17 shows
the basic arrangement.
NOTE: You must know the IP address of the LEDR Radio and the PC
that you are going to connect together. (Both units must have
the same Subnet, Netmask and Gateway addresses, or at least
have routes to one another.) This is essential for a direct
Ethernet connection.
If you do not know your Windows computer’s IP address, you
can use the RUN function from the Start menu and enter winipcfg
to determine your local PC’s IP address. The IP address of the
radio can be found by the use of the radio’s ip command.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide95
LOCAL WINDOWS PC
W/FIRMWARE FILES
TFTP
SERVER
&TELNET
IP ADDRESS: 192.168.X.B
INITIATE UPLOAD
FROM HERE
LEDR> REPROGRAM NETWORK FILENAME.MPK 192.168.X.B
(CHECK STATUS: LEDR> REPROGRAM STATUS)
ETHERNET
PORT
CROSS-OVER CABLE
Figure 18. Direct connection through the LEDR ETHERNET Port
Setup
Invisible place holder
ETHERNET
PORT
LEDR RADIO UNIT
IP ADDRESS: 192.168.X.W
1. Connect the PC’s Ethernet interface to the radio’s
ETHERNET Port
using a Category 5 Ethernet cross-over cable.
2. Copy the file LEDR firmware image file (
directory on your PC. For example,
ledr.mpk) into a known
c:\windows\LEDR\Firmware V2.5\.
This directory path will be used later by the TFTP server.
Download Procedure
1. Launch the MDS TFTP Server on a PC connected to the LEDR
radio’s
ETHERNET Port through a cross-connect cable.
2. Point the TFTP server to the directory from which you desire to
upload the new firmware. In the SNMP TFTP server, you should
execute the
where
set root command and point to the known directory
ledr.mpk has been copied.
3. Launch your Telnet application and login to the radio which you
desire to load (reprogram) the firmware image file.
4. Determine the active (firmware) image from which you are currently
executing by typing
boot. The new firmware will downloaded into
the inactive image.
5. Execute the command
command, in place of
address of the TFTP server. For example,
192.168.1.2
reprogram network ledr.mpk [IP address]. In the
[IP address], you should actually type the IP
reprogram network ledr.mpk
96LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
6. If desired, the status of the transfer during reprogramming may be
displayed by typing
reprogram status.
7. The TFTP Server and radio will notify you when the programming
is complete.
Verification and Reboot
1. To verify the integrity of the new firmware enter
boot to determine
which image is currently active. This command will respond as
follows:
boot: Image 1 is Active or, boot: Image 2 is Active
If the radio responded to the boot command with Image 1 is Active,
enter the “image verify” command,
iverify 1. The radio will respond indicating whether or not the image
iverify 2, otherwise, enter
has been verified as being a valid file, it will not determine if the
contents are complementary to the other firmware image. If the
image does not verify, try downloading the firmware again into the
radio.
NOTE: The following paragraph describes rebooting the radio. This
action will disrupt the communications link.
2. Once the image has been verified, the radio must be rebooted using
the new firmware. This is done by entering the command
boot 2, where the 1 or 2 corresponds with the image number used
with the
iverify command above.
boot 1 or
3. Once the radio has rebooted and Flash Utility screen displays the
LEDR> prompt, the firmware can be downloaded or copied into the
other image. Often, copying the firmware from one image to the
other can be faster than performing a second download. To copy the
firmware over to the other image, simply enter
prompt you for confirmation (
y/n) and then begin copying.
icopy. The radio will
8.4OPTION 3: Uploading Firmware from a Remote
Server via Ethernet
Setup
Connect the LEDR radio’s ETHERNET connector to network which has
a PC connected with the desired LEDR firmware on its hard drive. The
“network” can be a local area network, a wide-area network or any IP
network that can connect the two units.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide97
The computer hosting the firmware image, must be running a TFTP
server software. If not, install, launch and configure the MDS TFTP Server software found on the LEDR Utilities disk. The setup configura-
tion is shown in Figure 19.
REMOTE PC
W/FIRMWARE FILES
TFTP
SERVER
ETHERNET
PORT
IP ADDRESS: 192.168.X.B
Invisible place holder
HUB/LAN/WAN/MAN
TCP/IP
ETHERNET
PORT
LOCAL WINDOWS PC
TERM
PROG.
INITIATE UPLOAD
FROM HERE
COM1, 2, ETC.
(DTE)
LEDR> REPROGRAM NETWORK FILENAME.MPK 192.168.X.B
(CHECK STATUS: LEDR> REPROGRAM STATUS)
CONSOLE PORT
(DCE)
9-PIN SERIAL
CABLE
LEDR RADIO UNIT
IP ADDRESS: 192.168.X.W
Figure 19. Uploading firmware from a remote server via Ethernet
Download Procedure
1. Start a terminal program, such as HyperTerminal, on the local PC.
2. Log into the LEDR radio using the login command.
3. Use the ip command to ensure that the radio has a valid IP address.
4. Use the ping command from the local PC to ensure that the PC and
the radio have valid routes to pass information between them.
5. At the radio’s
gram network
monitored from the radio by entering
LEDR> prompt, start the download by entering repro-
[filename] [source PC’s IP Address]. The download can be
reprogram status. When the
download is complete the radio will sound two short beeps and the
response from
reprogram status will indicate that the download has
finished.
98LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
SNMP OptionThe TFTP download process can also be initiated using an SNMP man-
ager. The
Firmware|FwProgTable object provides a means for specifying
the TFTP server IP address and the filename for the firmware.
Verification and Reboot
When the download is complete, verify the firmware image and reboot
the radio as described under Verification and Reboot in Paragraph See
“Verification and Reboot” on Page 95 for the procedure.
9.0USING ORDERWIRE
9.1Introduction
A handset may be plugged into the front panel of the LEDR radio to
allow voice communications between radio sites (see Figure 20). This
can be especially useful during setup and service of the radio equipment.
All radios on the network can hear what is said by any individual
speaking into a handset. No other radio may transmit on the orderwire
until the current speaker is finished. Depending on the number of hops,
the link data rates, and Interleave setting, there may be a noticeable
latency from one end of the network to the other.
The front panel alert function (See “Unit ID” on Page 34) and
alert com-
mand (Page 51) can be used to signal all units in the network or a specific radio.
Normal payload data is not affected by Orderwire use. The Orderwire
uses voice-compression technology that introduces a slight, but noticeable, delay in Orderwire audio.
The orderwire will not interrupt the normal data flow through the LEDR
data communication channel, however, it will reduce the throughput
efficiency of any data communications on the Service Channel during
periods of voice transmission.
A handset is available from MDS (P/N 12-1307A01), which has a
push-to-talk button and provides basic communication services but does
not contain a built-in DTMF (tone) keypad. (The Orderwire supports the
transmission of DTMF-type signaling by detecting tones at the source,
and regenerating them at the receiving end, however, there are no
DTMF supported radio functions in the LEDR radios.)
9.2Setup
Program the vox and volume setting for each radio. The volume setting is
user preference. The
the
vox setting, the louder the user must speak to get the voice decoder
to recognize the speech. This will, however, prevent noise from entering
vox setting requires some forethought. The higher
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide99
the “line.” A low vox level will recognize speech better but may transmit
more noise with the speech. The user should experiment with the
vox
setting to determine the best level for the speaker and the noise environment.
9.3Operation
1. Plug the handset into the front panel jack labeled . (Figure 32
on Page 129 provides pinout details for this connector.)
2. Press or at the menu’s top level until Orderwire appears on
ENTER
the LCD display . Press
3. To call a specific radio station, enter the Unit ID number for the station to be called. (At this point, an alert signal (“ring”) will be sent
to earpiece of the handset connected to the “called” station.
4. Press the PTT on handset to speak to the other station(s) listening to
their handsets connected to LEDR equipment on the network.
Release the handset PTT to listen. VOX (voice-activated transmit)
operation is also supported. (See “vox” on Page 88.)
to move to the lower levels of the menu.
5. Alternatively, a DTMF-style handset can be used to “dial” the
required radio station.
6. Remember, regardless of the number of users, only one may speak
at a time.
NOTE: The LEDR radio has a built-in DTMF decoder in the orderwire
circuitry. If a standard DTMF telephone test set is plugged into
the orderwire, the user can dial in the three digit unit address
on the handset to “ring” the earpiece of the handset of the associated LEDR unit.The LEDR chassis will not provide power to
ring a standard bell or electronic ringer.
100LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
Invisible place holder
Figure 20. Orderwire Connection
9.4Related NMS Commands
The orderwire can be configured by the NMS commands or through the
front panel. The earpiece volume is more easily set by the front panel
controls as the level is dependent on personal preference.
vox – Voice level (relative) at which speech will be detected by the soft-
ware (See “vox” on Page 88)
volume – Sets/displays the handset volume (See “volume” on Page 88)
alert – Sends an orderwire alert to a specific radio or to all the radios on
the network (See “alert” on Page 51)
10.0 USING THE SERVICE CHANNEL
10.1 Concept
The Service Channel sends and receives ASCII-based information at
9600 bps in a half-duplex broadcast mode throughout the network. This
means that any data coming through the Service Channel Port of a radio
will be broadcast to the Service Channel of each radio in the network.
There can be only one radio transmitting Service Channel data over the
network at a time and the data will always be sent to every radio on the
network. No other radio will be allowed to transmit until the current sender is finished.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide101
If a radio does receive data in the Service Channel Port while another
radio is the active-sender, the data coming in the port will be queued and
sent when the active sender is finished. Depending on the number of
hops, link data rate, and Interleave setting, there may be a noticeable
latency from one end of the network to the other.
10.2 Setup
The user can configure all the Service Channel parameters for a specific
radio. The port may be enabled or disabled. In the disabled state (
port off
), any data that comes in the Service Channel port will be discarded and any Service Channel data that comes into the radio from
another radio in the network will be passed along to the rest of the network but not sent out the Service Channel Port. When the Service
Channel Port (
svch port on) is enabled, it will behave based on the other
settings.
The most important setting is the echo parameter. Echo is used with a
terminal emulator on a PC and the program does not display on the
screen character keyed in by the user.
svch
When you set up a system, you must be careful to avoid an infinite loop.
If echo is enabled, then every character that enters the Service Channel
port will be echoed back out the port. When echo is disabled then data
that comes in the Service Channel port is not sent back out the port.
Trouble may arise if the device that is connected to the Service Channel
also echoes the data it sends. In that case, the device will send characters
into the Service Channel Port, the radio will echo the characters back to
the device, the device will consider the echoed data to be input which it
will in turn echo back to the radio, etcetera, until an overflow condition
occurs.
You must also set the communication parameters (baud rate, stop bits,
char length, and parity) via the
svch subcommands so that the settings
match those at the device connected to the Service Channel Port.
Lastly, the user can re-initialize the Service Channel port via the svch
command. This may be helpful in the case where an infinite loop
reset
overflow condition has locked the port.
10.3 Usage
The Service Channel supports ASCII data transfer over the network in
broadcast fashion. As a result, devices connected to the Service Channel
Ports of different radios will appear to have a transparent half-duplex
connection between them.
102LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
10.4 NMS Commands
This command is used to set/display Service Channel parameters.
Usage:
svch [subcommand] [<argument>]
Subcommands:
on
—Enable the Service Channel
off—Disable the Service Channel
reset—Re-initialize the Service Channel
echo—on/off
baud—300, 600, 1200, 2400, 4800 and 9600
char— 5, 6, 7, 8 (ASCII character length in bits)
parity—none, even, odd
stop—1, 2 (Stop bits)
baud
char
echo
off
off
on
parity
reset
stop
11.0 PROTECTED CONFIGURATION
11.1 Introduction
The LEDR radio can be supplied in a protected (also called redundant
or “1+1”) configuration (Figure 21). The protected version is designed
to perform automatic switchover to a second radio in the event of a
failure in the primary unit.
Protected operation is important for many mission-critical or revenue
producing links. By configuring two identical LEDR radios in parallel
and including a third switch box containing the RF switching circuits
and the customer interfaces, it is possible to protect against failure in any
of the LEDR radio sub-systems. Failures can be either malfunction or
external environmental effects, such as multipath fading or nearby lightning strikes.
A Protected station consists of two standard LEDR Series radios and a
Protected Switch Chassis (center unit in Figure 21). Ordinarily, the three
chassis are mounted together in a “stacked” arrangement, one above the
other, as shown in the figure.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide103
The top unit is referred to as the system’s “Unit A”, and the lower one
as “Unit B”. Each unit is considered to be the “sibling” of the other. The
sibling of Unit A is Unit B, and the sibling of Unit B is Unit A. This distinction is used in the
rdnt command found on Page 74 under the sub-
heading “Read & Write Commands.”
Invisible place holder
UNIT A
PSC
UNIT B
Figure 21. LEDR Radio Protected Version
The front panel of the Protected Switch Chassis (PSC) front panel has
only two LEDs and an RJ-45 jack for an orderwire handset. The LEDs
indicate by light and an arrow outline which LEDR chassis is active. It
is assumed the two LEDR chassis will be mounted above and below the
PSC as shown in Figure 21.
11.2 Protected Operation
During normal operation, one radio path is selected and the RF and
interface switches are set to service that path. (The illuminated
LED indicator on the front panel of the Protected Switch Chassis (PSC)
points to the currently active unit.) A switch in the transmitter circuitry
allows one transmitter to be connected to the common
ANTENNA port on
the Protected Switch Chassis. On the receive path, a splitter in the Protected Switch Chassis allows both radio receivers to receive the
incoming RF signal for processing.
The Protected Switch Chassis is a gateway for data coming and going
between each of the LEDR radio units and the common data circuits
connected to the PSC. The PSC monitors various RF and data signal
paths for predefined fault-determining parameters. If signal conditions
are not normal, the PSC’s microprocessor controller will issue an alarm
and move the standby LEDR radio to the active mode.
POWER
104LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
Fault-determining parameters can be programmed from the Network
Management System (NMS) software. Examples of these parameters
are:
• Low transmitter power
• High transmitter temperature
• Synthesizers is out-of-lock
• Problem with the option board or framers
• CPU failure wherein the CPU watchdog causes a reset
• Fan fault
Transmitter Failure
Any failure on the “active” transmitter path will create a fault condition
which will place the currently the active transmitter on standby and
switch the “standby” transmitter to “active.” The newly active transmit
path will remain in use until a manual changeover returns the configuration to the original transmitter path. This allows the link to remain
fully operational until the user has replaced the faulty transmitter circuitry.
Receiver Failure
Both receivers are fed via an RF splitter from the antenna port. Each RF
path is buffered and monitored for receive signal integrity for uncorrectable bit-errors. If the “active” receive circuitry fails, uncorrectable
bit-errors will be detected. The modem receive switch will first determine that the “standby” receive path is operational (no uncorrectable bit
errors) and will switch accordingly.
11.3 Configuration Options
The protected LEDR radio is available with a number of configuration
options, each designed to optimize particular system solutions:
1+1 Operation—Warm or Hot Standby
In a warm standby link, the standby transmitter is powered down. In a
hot standby link, the standby transmitter is powered up and transmitted
in a dummy load. The warm standby option offers the advantages of significantly reduced power consumption, since only one transmitter path
is powered. However, upon transmitter failure, the switchover takes
longer due to the transmitter having to be powered. Thus the hot standby
mode offers the advantages of faster switchover time and increased
overall system availability.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide105
Symmetrical or Asymmetrical Receiver Splitters
The default protected radio is configured with a 3 dB splitter on the
receive path, meaning that each radio’s receiver signal level is equal, but
typically 4dB worse than an unprotected radio (3 dB due to splitter, plus
dB cabling and additional connectors). As an option, an asymmetrical
splitter (1 dB / 10 dB) is offered. Using this option, the active path is 2
dB stronger than with a symmetrical splitter (1 dB compared to 3 dB
splitter loss), allowing for a better fade margin and increased system
availability during normal operation.
However, upon receiver change over, the receive signal strength will be
significantly reduced due to the 10 dB of splitter loss rather than the
equal splitter’s 3 dB loss, making the link more sensitive to fading in this
temporary switched state. Providing the failed standby receiver is
replaced within a short period of time, many users find that the asymmetric splitter’s increased normal performance offsets any deterioration
in the temporary switched state.
11.4 PSC Rear Panel Connectors
The following are descriptions of the rear panel connections of the Protected Switch Chassis. The PSC’s rear chassis is shown in Figure 22.
RF CONNECTORS
Figure 21 presents an inter-unit cabling diagram for protected configu-
rations.
Invisible place holder
PROTECTED DATA
A
B
TxBAntennaTxARxBRxA
E1 DATA
ETHERNET
12
34
530 (A&B)
530 (A&B)
Figure 22. Protected Switch Chassis—Rear Panel
EIA-530-A
SERVICE CHANNEL
EIA-530-AService ChannelEthernetE1Protected
RxA
The RXA (Receive—Radio A) connector is a N-type coaxial connector.
It connects to the
RX port on the rear panel of Radio A via a short coaxial
cable.
RxB
Same as
RXA, but for Radio B.
Antenna
The
ANTENNA connector is a N-type coaxial connector. It serves as the
connection point for the station antenna.
106LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
TxA
The
TXA (transmit, radio A) connector is a N-type coaxial connector. It
connects to the
TX port on the rear panel of Radio A via a short coaxial
cable.
TxB
Same as
TXA, but for Radio B.
Protected (Data)
This pair of connectors accepts G.703 signals from each of the LEDR
radios. The top connector is for Radio A, and the bottom connector is for
Radio B. For pinout information, see Figure 36 on Page 130.
E1
This is a block of four RJ-45 modular connectors for connection to a
multiplexer or other customer-supplied E1 equipment. For detailed pin
information, Figure 34 on Page 130.
These connectors are not operational on “S” Series (Subrate) radios.
Ethernet
The
ETHERNET connector provides access to the embedded SNMP
agent and other elements of the TCP/IP network management system.
The connector is a standard 10 Base-T connection with an RJ-45 modular connector. For detailed pin information, see Figure 34 on Page 130.
530 (A&B)
This pair of DB-25 connectors accepts EIA-530 data signals from each
of the LEDR radios. The top connector is for Radio A, and the bottom
connector is for Radio B. For pinout information, see Figure 36 on
Page 130.
EIA-530-A
This DB-25 connector provides a connection point for customer-supplied EIA-530 data equipment. Note: This port is not operational in fullrate models.
Service Channel
In a protected configuration, this DB-9 connector becomes the Service
Channel connection for both LEDR radios. (In the protected radio configuration, the Service Channel connectors on the radios are non-functional.) For detailed pin information, see “Service Channel—Rear
Panel” on Page 131.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide107
11.5 Inter-Unit Cabling for Protected Stations
The required cabling between the two radios and the Protected Switch
Chassis is dependent on the data interface, unit type (subrate versus
full-rate), and transmit and receive antenna configuration.
The cabling for a pair of standard radios with internal duplexers is
shown in Figure 23.
DO NOT USE IN
G.703/Expansion Data
PROTECTED CONFIG.
Ethernet
NMS
EIA-530-A
Service
Channel
Alarm I/O DC Power Input
RADIO A
RX
COAXIAL CABLES (4)
P/N 19-1323A02CABLE 1A
RX
External
TO
STATION
ANTENNA
External
TX
P/N 03-3837A01
TxBAntennaTxARxBRxA
TX
Figure 23. Inter-unit Cabling—Protected Version
CABLE 1B
P/N 03-3837A01
G.703/Expansion Data
Data Interface
CABLE 2A
P/N 03-3828A01
(SUBRATE MODELS)
TO
MUX OR OTHER
E1 EQUIPMENT
12
34
TO ETHERNET HUB
CABLE 2B
P/N 03-3828A01
(SUBRATE MODELS)
Ethernet
NMS
Data Interface
PROTECTED CONFIG.
530 (A&B)
EIA-530-A
DO NOT USE IN
with Internal Duplexers
TO EIA-530
DATA EQUIPMENT
(SUBRATE MODELS)
PROTECTED SWITCH
EIA-530-AService ChannelEthernetE1Protected
SERVICE CHANNEL
(SERVES BOTH RADIOS)
Service
Channel
Alarm I/O DC Power Input
RADIO B
11.6 Configuration Commands for a Protected
System
NOTE: In a protected link configuration, ensure that the E1/T1 inter-
face settings are identical for both radios at a each end of the
link.
Once the inner-chassis cabling is in place and the units are powered up,
several parameters are required to place the LEDR radio into proper
operation as a member of a protected system.
The tasks involved are reviewing and setting up of the following parameters:
108LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
•Radio Operation
• General
• Redundant Specific
•Data Interface
• Subrate—Fractional-T1
• Fullrate—E1/T1
Redundant Specific Parameters
There are several parameters that must be set to enable proper operation
of a protected station. These are all covered under the
rdnt command
found on Page 74.
Sample Redundant Configuration Session
The following is a example of a session used to configure a LEDR radio
to serve in a protected system. This sequence will need to be repeated
for each radio in the protected pair.
1. Configure the protected mode to hot-standby:
LEDR> rdnt mode 1
rdnt {mode}: 1+1 Hot Standby
LEDR>
2. Configure the IP address of each radio:
LEDR> ip address 192.168.1.1
ip {netmask}: (255.255.0.0)
ip {gateway}: (0.0.0.0)
ip {port}: (ETH)
ip {address}: 192.168.1.1
ip {netmask}: 255.255.0.0
ip {gateway}: 0.0.0.0
ip {port}: ETH
ip: A reboot is strongly recommended. Do you wish to reboot? (y/n) >y
LEDR>
3. Configure the sibling IP address of each radio:
LEDR> rdnt ip 192.168.1.2
redundant {ip}: 192.168.1.2
LEDR>
4. Configure the hitless switching. (Note that the default is on.):
LEDR> rdnt hitless on
rdnt {hitless}: on
LEDR>
5. Configure the temperature (°C) threshold:
LEDR> rdnt temp 100
rdnt {temp}: 100
LEDR>
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide109
Transmit Clock Selection (Subrate Models Only)
The transmit clock selection must be addressed for every radio in a subrate radio system installation. The single most important consideration
is that there be only one master clock in a subrate radio network. The
master clock can originate from the radio or from the Customer Premises Equipment (CPE).
The radio is capable of several different clocking modes. Refer to
Figure 24 on Page 111 for typical system clocking methods.
Refer to the Clock Mode screen description on Page 35 for setting the
radio transmit clocking from the front panel. Refer to the
clkmode
description on Page 56 for setting the radio transmit clocking mode from
the
CONSOLE Port.
NOTE: When customer premises equipment (CPE) is operated in
looped clock mode, it is recommended that the radio not be set
to line clock mode. To do so may cause the transmitting
radio’s PLL to be pulled out-of-lock, especially when operating at 4E1 data rates.
110LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
Invisible place holder
Scenario 1:
LEDR Radio Clock
Source: Line 1, 2, 3, 4
Scenario 2:
LEDR Radio Clock
Source: Internal
LEDR Radio
Clock Source: Remote
SITE A
CPE
Scenario 1:
Network or
Internal Clock
Scenario 2:
Looped Clock
Mode
REPEATER NULL-MODEM
DATA INTERCONNECT CABLE
ETHERNET CROSS-CABLE
SITE C
SITE B
REPEATER SITE
LEDR Radio
Clock Source: Remote
LEDR Radio Clock
Source: Line 1, 2, 3, 4
CPE
Looped Clock
Mode
Figure 24. Typical Repeater Clocking Arrangement
(no multiplexer at repeater site)
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide111
12.0 SPACE DIVERSITY OPERATION
12.1 Introduction
Space diversity operation is an effective mechanism of increasing a
radio link’s resilience to transmission impairments such as multipath
fading or frequency selective fading. In difficult transmission environments such as over highly reflective and moving water paths, or in arid
environments where atmospheric ducting occurs, space diversity is the
most effective way of maintaining a continuous radio link.
In a space diversity link, two radio receivers are operated in parallel,
from two separate antennas mounted several wavelengths apart vertically on the antenna tower. The separation of antennas is such that when
one antenna experiences fading due to multi-path interference, the other
antenna, being several wavelengths away, is not likely to experience the
same fade. Thus, one receive path may experience uncorrectable errors,
while the other path will be error free. Similar to the protected operation,
the receive modem switch will determine which buffered data path is
operating with the highest integrity, and select that path without
inducing any additional bit errors into the link.
Space diversity is especially effective in changeable multi-path environments such as over tidal water paths. Since water is highly reflective,
there will be continual “constructive” and “destructive” interference at
each single antenna over the course of the day as the water rises and falls
and the reflected water path interferes with the line-of-sight path. By
correct vertical positioning of the antennas, these effects can be negated,
allowing one antenna to see a good signal while the other is experiencing fading, and the modem switching accordingly to allow the link
to operate error- free.
The space diversity LEDR radio is available only in a hot standby configuration.
12.2 User Interface & Control
Protected operation is configured using the Redundant screen (Page 41)
on either radio front panel, or with the
minal (see Page 74).
rdnt command from a NMS ter-
12.3 Transmit Clock Selection
There is no difference between a space diversity system and redundant
radio arrangements with respect to transmit clock selection. Fullrate
radios require no user intervention for clocking. Users of subrate systems should set the radio clocks as described for subrate systems. See
“Transmit Clock Selection” on Page 112 for further information.
112LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
12.4 Inter-Unit Cabling for Space Diversity Stations
The RF cabling for space diversity stations depends on the location of
the duplexers. The block diagram in Figure 25 shows the RF connections in a typical system with two external duplexers.
Invisible place holder
TX
LEDR
UNIT A
TX
RX
RX
DUPLEXER
ANT
A
TO RX PORT OF
DUPLEXER A
RX
COAXIAL CABLES (2)
P/N 19-1323A02
External
ANTENNA
SYSTEM
TX
TO
LEDR
UNIT B
RX
TX
RX
DUPLEXER
ANT
B
Figure 25. Block Diagram of a Space Diversity Station
with External Duplexers
The inter-unit cabling for a space diversity system with external
duplexers is shown in Figure 26.
DO NOT USE IN
PROTECTED CONFIG.
G.703/Expansion Data
CABLE 1A
P/N 03-3837A01
Ethernet
NMS
Data Interface
P/N 03-3828A01
(SUBRATE MODELS)
TO
MUX OR OTHER
E1 EQUIPMENT
12
EIA-530-A
CABLE 2A
Service
Channel
TO EIA-530
DATA EQUIPMENT
(SUBRATE MODELS)
Alarm I/O DC Power Input
PROTECTED SWITCH
RADIO A
EIA-530-AService ChannelEthernetE1Protected
SERVICE CHANNEL
(SERVES BOTH RADIOS)
Service
Channel
Alarm I/O DC Power Input
RADIO B
TO TX PORT OF
DUPLEXER A
RX
External
TX
TO RX PORT OF
DUPLEXER B
TxBAntennaTxARxBRxA
CABLE 1B
P/N 03-3837A01
G.703/Expansion Data
34
TO ETHERNET HUB
CABLE 2B
P/N 03-3828A01
(SUBRATE MODELS)
Ethernet
NMS
Data Interface
EIA-530-A
DO NOT USE IN
PROTECTED CONFIG.
530 (A&B)
Figure 26. Inter-unit Cabling—Space Diversity
with External Duplexers
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide113
The inter-unit cabling for a space diversity system with internal
duplexers is shown in Figure 27.
DO NOT USE IN
PROTECTED CONFIG.
G.703/Expansion Data
Ethernet
NMS
EIA-530-A
Service
Channel
Alarm I/O DC Power Input
RADIO A
RX
COAXIAL CABLES (4)
P/N 19-1323A02CABLE 1A
TO TX/RX ANTENNA
SYSTEM A
RX
External
External
TX
TX
TO RX ANTENNA
SYSTEM
P/N 03-3837A01
TxBAntennaTxARxBRxA
Figure 27. Inter-unit Cabling—Space Diversity
CABLE 1B
P/N 03-3837A01
G.703/Expansion Data
Data Interface
CABLE 2A
P/N 03-3828A01
(SUBRATE MODELS)
TO
MUX OR OTHER
E1 EQUIPMENT
12
34
530 (A&B)
TO ETHERNET HUB
CABLE 2B
P/N 03-3828A01
(SUBRATE MODELS)
Ethernet
NMS
Data Interface
EIA-530-A
DO NOT USE IN
PROTECTED CONFIG.
with Internal Duplexers
TO EIA-530
DATA EQUIPMENT
(SUBRATE MODELS)
PROTECTED SWITCH
EIA-530-AService ChannelEthernetE1Protected
SERVICE CHANNEL
(SERVES BOTH RADIOS)
Service
Channel
Alarm I/O DC Power Input
RADIO B
114LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
13.0 SPARE PARTS, UNITS AND
ACCESSORIES
13.1 Spares
Spare assemblies and units used for repair of LEDR radios are listed in
Table 28. Field servicing, or replacement of PC boards and assemblies,
should only be performed by qualified service personnel.
When ordering parts from the factory, always give the complete model
number of the radio as found on the serial number label on the chassis.
Contact information can be found on Page 140 of this guide.
FT1 Data Interface PCBLEDR 900S03-3846A01
E1/FE1 Data Interface PCBLEDR 400F
LEDR 400S
LEDR 900F
LEDR 900S
LEDR 1400F
LEDR 1400S
Subrate Data Interface PCBLEDR PSC03-2824A01
Fullrate Data Interface PCBLEDR PSC03-3539A01
Number
dependent;
Contact
factory.
03-3846A02
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide115
13.2 Accessories
Table 28 lists accessories available from the factory as a convenience to
our customers. Factory contact information can be found on Page 140 of
this guide.
Table 29. Accessory Items for LEDR Radios
ItemDescriptionPart
V.35 Interface Cable6 ft (1.8 m) cable adapter used to convert
G.703 Balun Miniature G.703 balun used to convert a
EIA-530 Null-MODEM
Crossover Cable
SNMPc™ Network
Management Manager
SNMPc™ Network
Management Manager
Orderwire Handset Voice handset with 4-wire cord (RJ-11
Orderwire Handset KitVoice handset with 4-wire cord (RJ-11
AC Power Adapter External AC power supply provides 24
subrate LEDR radio EIA-530 data
interface to V.35 male data interface.
fullrate LEDR radio’s 120 Ω balanced
data interface to two 75 Ω BNC coaxial
data interfaces.
One balun required per E1 port.
6 ft (1.8 m) cable adapter to connect
subrate interfaces in a repeater
configuration.
SNMP Management Software to access
the LEDR embedded SNMP agent,
allowing management of the LEDR radio
network and any interconnected SNMP
enabled peripherals.
For Windows 95 O/S
SNMP Management Software to access
the LEDR embedded SNMP agent,
allowing management of the LEDR radio
network and any interconnected SNMP
enabled peripherals.
For Windows 98 or NT O/S.
modular plug).
modular plug), hanger and mounting
bracket.
Vdc to LEDR radio.
Input: 110 Vac to 240 Vac, 50 to 60 Hz
Number
03-2174A01
01-3494A01
97-2841L06
03-3530A01
03-3530A02
12-1307A03
02-1207A01
03-3862A01
116LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
14.0 FRACTIONAL-T1 INTERFACE
CARD 03-3846A01
FRACTIONAL-E1 INTERFACE
CARD 03-3846A02
14.1 Introduction
The Fractional-T1 (FT1) and Fractional-E1 (FE1) Interface cards are
optional assemblies which provide additional connectivity within a
LEDR network for all subrate (S) models. The installation of the
FT1/FE1 Interface card inside the radio allows the standard EIA-530
customer data interface to be bypassed and the radio data lines to be connected directly to a G.703 T1 or E1 interface.
With the optional FT1/FE1 Interface, users are able to place a LEDR
link from a network service access point to a remote site, where an
installation supports multiple communications devices. Direct interface
to customer equipment, such as channel banks, is possible without the
use of expensive protocol converters.
14.2 Fractional-T1/E1 Performance
The FT1 and FE1 Interface allows the LEDR radio to be connected
directly with a G.703 T1 or E1 interface. The line rate of the interface
operates at the T1 rate of 1.544 Mbps, or E1 rate of 2.048 Mbps. Twelve
user selectable DS0 timeslots are transmitted over the air in either case.
The FT1 interface is G.703 at 100 Ω line impedance. The FE1 interface
is G.703 at 120 Ω line impedance. Physical connection is via an RJ-45
jack on the rear panel.
14.3 Configurable Parameters
The following performance specifications of the T1 fractional interface
are adjustable by the user. All of these parameters are manageable
locally, or over the air via SNMP network management. (Refer to the
SNMP Handbook, P/N 05-3532A01 for more information.)
Timeslots and Framing
Twelve DS0 timeslots are permitted. In FT1, the timeslot selection is
arbitrary. In FE1, timeslot 0 is always sent and the remaining timeslots
are arbitrary with the exception of timeslot 16. (Timeslot 16 must be sent
when any CAS frame structures are selected.) The selection of timeslots
can be different at each end of the link, provided their number is equal.
The timeslots may not be reordered.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide117
Alarm signals RAI and AIS are generated as appropriate. The user may
optionally have these signals forwarded over the RF link.
The frame formats available for Fractional-T1 operation are as follows:
• FT only
• ESF without CRC checking and generation
• SF (D4)
• SF with JYEL indication
• ESF with CRC checking and generation
The frame formats available for Fractional-E1 operation are as follows:
• FAS only
• FAS with BSLIP
• FAS with CRC
• FAS with CRC and BSLIP
• FAS and CAS
• FAS with CAS and BSLIP
• FAS with CAS and CRC
• FAS with CAS
• CRC and BSLIP.
The re-framing criteria may be adjusted to the following settings: 2 out
of 4 Fbit errors, 2 out of 5 Fbit errors, 2 out of 6 Fbit errors. For FE1, the
reframing criteria is selectable between consecutive FAS errors or CRC
errors.
Line Codes
The following standard T1 line codes are supported: B8ZS, AMI, and
per-channel B7ZS.
The following standard E1 line codes are supported: HDB3 and AMI.
Diagnostics
The T1 line at each end of the link may be tested using a variety of bit
patterns. In normal operation, statistics are stored for any errors occurring at the line interface, such as framing errors, bipolar violations, and
CRC errors.
Data may be looped back at the local port, through the T1 option only,
and at the remote unit. Further, the unit will respond to in-band (SF) and
data link (ESF) loopback codes at the local port.
When in ESF framing mode, the option can automatically generate performance report messages.
118LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
The following alarms may be monitored & logged. They may also be
associated with a user-selectable indication (alarm contact or front panel
LED): Remote Loopback, Lost Frame, Lost Signal, Lost Analog Signal,
AIS, RAI (RYEL), MultiFrame RAI, Severely Errored Frame, Frame
Re-Align, MultiFrame AIS, Far End Block Error, Line Code Error, CRC
Errors and Frame Bit Error.
Clocking
The clock source is configurable for network, loopback, and internal
timing, with secondary selections available should the primary source
become faulty. Refer to the discussion of the
clkmode command
(Page 54) for more information
14.4 Field Installation of the FT1 Interface Board
An “S” Series LEDR radio can be fitted with a Fractional-T1 (FT1) or
Fractional-E1 (FE1)Interface Board (Figure 28). The addition of an
FT1/FE1 board enables the radio to operate with a G.703 interface at
speeds up to 768 kbps.
To add the FT1/FE1 Interface Board to an existing LEDR radio transceiver, follow these steps:
1. Remove the top cover of the radio (4 Phillips screws).
2. Identify the installation area for the Interface Board (See Figure 29).
Remove the three Phillips screws on the main PC board which correspond to the mounting holes on the Interface Board.
3. Install the threaded standoff spacers (furnished with the option
board) onto the main PC board in the holes formerly occupied by the
screws. (Note: Washers must not be used between the standoff spacers and either of the PC boards.)
4. Locate connectors J912 and J913 (See Figure 29). These connectors
mate with the plugs on the bottom of the Interface board.
5. Carefully set the optional board into place, making sure to align the
mounting holes with the threaded standoffs on the main PCB. (The
Interface Board’s rear panel connector should align with the rectan-
gular cutout at the radio’s rear panel, and the rear edge of the option
board should be parallel to the main PC board.)
6. Look under the right edge of the Interface board to ensure that J912
is aligned with the mating connector on the option board. With the
board properly aligned, push down firmly in the area directly above
J913 and then over J912 at the edge. A distinct “locking” action will
be felt as the connectors engage.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide119
7. Install the Phillips mounting screws with lockwashers on the top of
the FT1 board.
For pr otected versions only: Install the plastic clip, if supplied, at the
right rear corner of the Interface board. It slips over the edge of the
main PC board and the option board. Gently tighten the hex screw to
secure the clamp.)
CAUTION
POSSIBLE
EQUIPMENT
DAMAGE
The Interface board must be properly seated onto the LEDR radio’s
motherboard before powering up the radio chassis. Failure to properly
install the board could result in permanent damage to the motherboard
and the optional PCB.
8. Re-install the radio’s top cover. This completes the Interface Board
120LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
Invisible place holder
REAR PANEL OF LEDR RADIO
Installation Area
for Interface Board
PC Board Clamp
(Some Versions)
J912J913
Figure 29. View of Radio PC Board
Showing Installation Details for FT1/FE1 Interface Board
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide121
15.0 INCREASE BANDWIDTH BY
CHANGING TRANSMITTER AND
RECEIVER FILTERS
15.1 Introduction
It is possible for qualified service personnel to upgrade LEDR Series
radios in the field to increase the radios RF bandwidth. Listed in Table
30 are five upgrade kits. Each kit consists of three RF filters; one is used
in the transmitter section and two are used in the receiver section. In
addition, there is a unique software key that will allow the data circuitry
to handle the higher data bandwidth. This key is based on the radio’s
serial number and can only be used with that radio.
Each kit consists of a set of 3 filters (transmitter 1; receiver 2), software
activation key and instructions for converting radio’s occupied bandwidth. The radio serial number must be provided to the factory for issue
of authorization key.
Table 30. Hardware Upgrade Kits for Increased RF Bandwidth
For Subrate RadiosFor Fullrate Radio
25 kHz to 50 kHz500 kHz to 1.0 MHz
25 kHz to 100 kHz500 kHz to 2.0 MHz
25 kHz to 200 kHz1.0 MHz to 2.0 MHz
50 kHz to 100 kHz
50 kHz to 200 kHz
100 kHz to 200 kHz
To realize the full benefit of the increased RF bandwidth, it may be necessary to upgrade the radio’s data interface. Table 1 on Page 1 provides
a simplified listing of radio bandwidth and compatible data interfaces.
15.2 Filter Removal and Replacement
These instructions describe the removal and replacement of filter modules inside a LEDR Transceiver, as well as the software commands necessary to authorize the new bandwidth.
CAUTION: This upgrade involves the removal of small, delicate parts.
It must be performed by experienced personnel only, using
proper tools and equipment to preserve the factory warranty.
Precautions must be taken to prevent damage to components
due to static discharge and other risks.
1. Remove the radio from service and disconnect all cabling from the
rear panel.
122LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
2. Remove the top cover of the radio (four Phillips head screws).
3. Remove the Transmitter and Receiver section’s RF shields
(Figure 30). It will be necessary to unplug the ribbon cables that
cross over the shields—record their locations as you remove them.
4. Locate and remove Filter FL700 from the transmitter section. In its
place, install the replacement filter furnished with the upgrade kit.
Ensure that the new filter is installed in the same orientation as the
original unit.
Invisible place holder
LEDR RADIO PC BOARD
FL700
FL601
FL600
Transmitter Section
Receiver Section
Figure 30. Location of Bandwidth Filters FL600, FL601 and FL700
5. Locate and remove Filters FL600 and FL601 from the Receiver
module. In their place, install the replacement filters furnished with
the upgrade kit. Ensure that the new filters are installed in the same
orientation as the original units.
6. This completes the required hardware changes. Fasten the top cov er
and re-connect all cables to the rear panel.
7. Power up the radio and proceed to “Software Commands” below.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide123
15.3 Software Commands
To activate the new filter bandwidth, it is necessary to enter an authorization key provided by Microwave Data Systems. This key is based
upon the radio serial number and will authorize the new bandwidth of
the radio. Contact the factory if you do not already have an authorization
number.
1. Initiate a NMS terminal session with the LEDR radio. (Refer to
Page 25 for login details.)
2. At the
LEDR> prompt, type: auth add <authorization number>, where
<authorization number> is the number provided to you by the factory.
Press
ENTER.
3. This completes the required software changes. If desired, the auth
show
command may be entered to display all of the current options
for the LEDR radio.
4. Check for alarms on the front panel LED display. If no alarms are
present, the basic functionality of the radio can be confirmed. If an
alarm is present, double check all cable connections and radio settings.
16.0 BENCH TESTING OF RADIOS
In some cases, it may be necessary to test the operation of the equipment
in a bench setting. Figure 31 shows a simple arrangement for bench
testing using RF attenuators between the two units under test.
For weak signal tests (weaker than –80 dBm), additional physical separation between Radio 1 and Radio 2 may be required to prevent unintentional coupling between the radios.
On protected radio configurations, a weak received signal will cause the
radio transceivers to switch.
DATA PORT
EQUIPMENT
RADIO
#1
DIGITAL
OR BER
TESTER
ANT
Connector
POWER ATTENUATOR
• 30 dB
• 1W Rating
Adjustable: For Sensitivity Tests (100–140 dB Required)
LOW LOSS COAXIAL LINES
SWITCHED OR VARIABLE
ATTENUATOR
• 0–110 dB (1 dB Steps)
JFW 50DR-001 or Equivalent
• Required only for receiver sensitivity test.
TOTAL ATTENUATION
Fixed: 80 dB Minimum for Basic Checks
POWER ATTENUATOR
• 30 dB
• 1W Rating
Figure 31. Back-to-Back Link Test
124LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
ANT
Connector
RADIO
#2
DATA PORT
DIGITAL
EQUIPMENT
OR BER
TESTER
You can perform an over-the-air BER test on the bench or in the field.
In this case, attach a separate piece of BER test equipment and feed it
into one or more of the T1/E1 ports. At the other end of the link, you use
another BER test box, or attach a loopback plug to the CPE data I/O
port. This tests the quality of the radio link itself with regard to the user
payload data. Such a bench, or over-the-air, test does not use the LEDR
bert command.
NOTE: It is important to avoid over-driving the receiver as it can be
damaged by strong signals. Signals stronger than -20 dBm
should be avoided to protect the receiver.
NOTE: User BERT test equipment connected to a LEDR T1 data
interface my yield different BERT results than the radio’s ber
command. This is likely when less than the channel's capacity
is utilized by the timeslot command configuration.
17.0 TECHNICAL REFERENCE
17.1 Specifications—
Models: LEDR 400S, LEDR 900S & LEDR 1400S
General
Frequency Ranges:330–512 MHz (LEDR 400S)
RF Occupied Bandwidth:25, 50, 100 and 200 kHz
User Data Rates:64, 128, 256, 384, 512 & 768 kbps
Permitted Data Throughput:Channel Size
Modulation Type:32 QAM, 16 QAM, QPSK
Forward Error Correction (FEC):Reed-Solomon
Acquisition Time— Typical:From power up, 10 seconds
Voltage Range:24 Vdc or 48 Vdc (±20%)
Power Consumption:Less than 60 watts (non-protected configuration)
Temperature Range:– 5° to 50° C
Humidity:≤ 90% non-condensing @ 40° C
Size:1 RU; 19 Inch rack mount compatible
RF Occupied Bandwidth:500 kHz, 1 MHz & 2 MHz
User Data Rates:1 x E1 (2.048 Mbps)
Permitted Data Throughput:Channel Size
Modulation Type:32 QAM, 16 QAM, QPSK
Forward Error Correction (FEC):Reed-Solomon
Acquisition Time (Typical):From power up, 10 seconds
Voltage Range:24 Vdc or 48 Vdc (±20%)
Power Consumption:Less than 60 watts (non-protected configuration)
Temperature Range:–5° to 50° C
Humidity:≤ 90% non-condensing @ 40° C
Size:1RU, 19 Inch rack mount compatible
14 RTC_TESTReal-time clock errorNONEINFORM
15 BBRAM_TESTNV-RAM test failedNONEINFORM
16 BATTERY_LOWNV-RAM battery is lowALARMMAJOR
17 TX_SYNTH_LOCKTransmit Synthesizer
out-of-lock
18 RX_SYNTH_LOCKReceive Synthesizer
out-of-lock
19 DIG_POWER_REFDigital Power Reference
is out of specified range
20 TEMPERATURETemperature sensor
reads over 80 degrees
Celsius
21 TX_POWER_LOOPTransmit Power Loop is
out-of-lock
22 DEMOD_SNR_LOWDemodulator
Signal-to-Noise ratio is
unacceptably low
LED
ALARMCRITICAL
ALARMCRITICAL
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
TXALARMCRITICAL
RXALARMCRITICAL
ALARMCRITICAL
ALARMCRITICAL
TXALARMMAJOR
NONEMINOR
SNMP
TRAP
LEVEL
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide133
Table 32. Event Codes (Continued)
IDEVENT NAMEDESCRIPTIONDEFAULT
23 DEMOD_AGC_RSSIDemodulator Automatic
Gain Controlled RSSI too
low
24 DEMOD_FEC_RECOVERFEC circuitry has detected
and corrected one or more
errors
25 DEMOD_FEC_UNRECOVERFEC circuitry has detected
one or more uncorrectable
errors
26 DEMOD_MULTIPATHExcessive multipath
distortion detected
27 DEMOD_ACQUISITIONDemodulator lost sync.
lock on received signal
28 TX_TO_REMOTE_RXProblem with link between
the local transmitter &
remote Rx
29 REDUNDANT_ALARMProblem with redundant
unit
30 WDOG_TIME_OUTProcessor watchdog has
expired and reset the
processor
31 RX_OFFRadio is not receiving due
to a weak signal or
equipment failure
32 SOFTWARE_TX_OFFSoftware command has
unkeyed the radio
33 RTC_NOT_SETThe real time clock is not
programmed
34 IO1_DIG_LOC_lOOPBACKThe radio’s 530 or TELCO
I/O port is in Digital local
loopback mode
35 IO2_DIG_LOC_lOOPBACKThe radio’s 2nd TELCO
I/O port is in Digital local
loopback mode
36 IO3_DIG_LOC_lOOPBACKThe radio’s 3rd TELCO
I/O port is in Digital local
loopback mode
37 IO4_DIG_LOC_lOOPBACKThe radio’s 4th TELCO
I/O port is in Digital local
loopback mode
38 RF_LOCAL_LOOPBACKThe radio is in Local RF
loopback test mode
39 IO1_DIG_REM_LOOPBACKThe radio’s 530 or TELCO
I/O port is in Digital
Remote loopback mode
40 IO2_DIG_REM_LOOPBACKThe radio’s 2nd TELCO
I/O port is in Digital
Remote loopback mode
LED
NONEMINOR
NONEMINOR
NONEMINOR
NONEMINOR
RXALARMCRITICAL
ALARMCRITICAL
ALARMCRITICAL
ALARMCRITICAL
RXALARMCRITICAL
TXALARMCRITICAL
NONEMINOR
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
SNMP
TRAP
LEVEL
134LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
Table 32. Event Codes (Continued)
IDEVENT NAMEDESCRIPTIONDEFAULT
41 IO3_DIG_REM_LOOPBACKThe radio’s 3rd TELCO
I/O port is in Digital
Remote loopback mode
42 IO4_DIG_REM_LOOPBACKThe radio’s 4th TELCO
I/O port is in Digital
Remote loopback mode
43 RAW_SERVICE_CHANNEL The Raw Service Channel
data frame is exhibiting
error
44 ATOD_REFERENCEA fault is detected with the
Analog to Digital converter
45 NEW_CONFIG_REVA new revision of
configuration data
structure has been
detected
46 FPGA_LOADFPGA is not loaded
correctly
47 DATE_TIME_CHANGEThe date or time is been
modified
48 HARDWARE_TX_OFFThe transmitter key
hardware is in an unkeyed
state
49 INACTIVE_ONCurrent radio transceiver
is in standby mode when
in protected radio chassis
50 NO_OPTION_UNITNo Option Card is
detected
51 VOCODER_INIT_ERRThe voice processor
initialization failed
52 VOCODER_ERRORThe voice processor is
reporting a problem
53 POWER_ON_RESETThis indicates PowerOn
Reset Cycle
54 EXT_HARD_RESETThis indicates last
Power-Up Cycle was due
to External Hard Reset
55 EXT_SOFT_RESETThis indicates last
Power-Up Cycle was due
to External Soft Reset
56 INACT_CONFIG_SYNCProtected 1+1 mode
Active to Inactive
Configuration data sync.
error
57 NEW FIRMWARE LOADEDNew firmware has been
downloaded from flash
memory.
58CONFIG_CHANGEDThe radio transceiver
configuration has been
modified
LED
NONEINFORM
NONEINFORM
ALARMMAJOR
ALARMCRITICAL
NONEINFORM
NONEINFORM
NONEINFORM
TXALARMCRITICAL
ALARMMAJOR
NONEINFORM
ALARMMAJOR
ALARMMAJOR
NONEINFORM
NONEINFORM
NONEINFORM
ALARMCRITICAL
NONEINFORM
NONEINFORM
SNMP
TRAP
LEVEL
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide135
Table 32. Event Codes (Continued)
IDEVENT NAMEDESCRIPTIONDEFAULT
59SELFTEST_COMPLETEA self test has completed
execution
60PERFORM_DEGRADEDA performance
degradation threshold has
been exceeded
61DUPLICATE_UNIT_IDAnother unit with the
same unit ID has been
detected
62LINK_UNAVAILABLEThe G821 status indicates
that the link is unavailable
63EVENT_LOG_CLEAREDThe event log has been
cleared
64FAN1_TROUBLEThere is a problem with
the fan
65Reserved for future use———
66USER_REBOOTThe user has rebooted the
radio
67MODEM_LOCAL_LOOPBACKModulator data path is
locally looped back to
Demodulator
68MODEM_REMOTE_LOOPBACKDemodulator data path is
looped back to modulator
for remote radio loopback
application
69OPT_MUX_LOOBACKOption card multiplexed
data path from Line(s) is
looped back
70IO1_REM_LOOPBACK_SERVRadio is server for remote
radio loopback mode with
its payload data at Line IO
#1 looped back to the
commanding local radio
71IO2_REM_LOOPBACK_SERVRadio is server for remote
radio loopback mode with
its payload data at Line IO
#2 looped back to the
commanding local radio
72IO3_REM_LOOPBACK_SERVRadio is server for remote
radio loopback mode with
its payload data at Line IO
#3 looped back to the
commanding local radio
73IO4_REM_LOOPBACK_SERVRadio is server for remote
radio loopback mode with
its payload data at Line IO
#4 looped back to the
commanding local radio
74IO1_RECVR_LOFLine IO #1 receiver
Loss-of-framing alarm.
LED
NONEINFORM
ALARMINFORM
ALARMINFORM
NONEINFORM
NONEINFORM
ALARMINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
NONEINFORM
I/O ALARMCRITICAL
SNMP
TRAP
LEVEL
136LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
Table 32. Event Codes (Continued)
IDEVENT NAMEDESCRIPTIONDEFAULT
75IO1_RECVR_LOSLine IO #1 receiver
Loss-of-signal alarm
76IO1_RECVR_ALOSLine IO #1 receiver
Loss-of-analog-signal
alarm
77IO1_RECVR_AISLine IO #1 receiver
detected AIS alarm
78IO1_RECVR_RAILine IO #1 receiver
detected RAI (yellow)
alarm
79IO1_RECVR_MRAILine IO #1 receiver
detected multi-framed RAI
(yellow) alarm
80IO1_RECVR_SEFLine IO #1 receiver
detected Severely Errored
Frames
81IO1_RECVR_COFALine IO #1 receiver
detected
Change-of-FrameAlignment alarm
82IO1_RECVR_MAISLine IO #1 receiver
detected multi-framed AIS
alarm
83IO1_RECVR_FEBELine IO #1 receiver
detected E1
Far-End-Block-Errors
alarm
84IO1_RECVR_LCVLine IO #1 receiver
detected Line-CodeViolation alarm
85IO1_RECVR_CRCLine IO #1 receiver
detected CRC alarm
86IO1_RECVR_FBITLine IO #1 receiver
detected Frame Bit Error
87IO2_RECVR_LOFLine IO #2 receiver
Loss-of-framing alarm
88IO2_RECVR_LOSLine IO #2 receiver
Loss-of-signal alarm
89IO2_RECVR_ALOSLine IO #2 receiver
Loss-of-analog-signal
alarm
90I02_RECVR_AISLine IO #2 receiver
detected AIS alarm
91IO2_RECVR_RAILine IO #2 receiver
detected RAI (yellow)
alarm
92IO2_RECVR_MRAILine IO #2 receiver
detected multi-framed RAI
(yellow) alarm
LED
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMINFORM
I/O ALARMINFORM
I/O ALARMINFORM
I/O ALARMINFORM
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
SNMP
TRAP
LEVEL
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide137
Table 32. Event Codes (Continued)
IDEVENT NAMEDESCRIPTIONDEFAULT
93IO2_RECVR_SEFLine IO #2 receiver
detected Severely Errored
Frames
94IO2RECVR_COFALine IO #2 receiver
detected
Change-of-FrameAlignment alarm
95IO2_RECVR_MAISLine IO #2 receiver
detected multi-framed AIS
alarm
96IO2_RECVR_FEBELine IO #2 receiver
detected E1
Far-End-Block-Errors
alarm
97IO2_RECVR_LCVLine IO #2 receiver
detected
Line-Code-Violation alarm
98IO2_RECVR_CRCLine IO #2 receiver
detected CRC alarm
99IO2_RECVR_FBITLine IO #2 receiver
detected Frame Bit Error
100IO3_RECVR_LOFLine IO #3 receiver
Loss-of-framing alarm
101IO3_RECVR_LOSLine IO #3 receiver
Loss-of-signal alarm
102IO3_RECVR_ALOSLine IO #3 receiver
Loss-of-analog-signal
alarm
103IO3_RECVR_AISLine IO #3 receiver
detected AIS alarm
104IO3_RECVR_RAILine IO #3 receiver
detected RAI (yellow)
alarm
105IO3_RECVR_MRAILine IO #3 receiver
detected multi-framed RAI
(yellow) alarm
106IO3_RECVR_SEFLine IO #3 receiver
detected Severely Errored
Frames
107IO3_RECVR_COFALine IO #3 receiver
detected
Change-of-FrameAlignment alarm
108IO3_RECVR_MAISLine IO #3 receiver
detected multi-framed AIS
alarm
109IO3_RECVR_FEBELine IO #3 receiver
detected E1
Far-End-Block-Errors
alarm
LED
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMINFORM
I/O ALARMINFORM
I/O ALARMINFORM
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMINFORM
SNMP
TRAP
LEVEL
138LEDR Series II Installation and Operation GuideMDS 05-3627A01, Rev. C
Table 32. Event Codes (Continued)
IDEVENT NAMEDESCRIPTIONDEFAULT
110IO3_RECVR_LCVLine IO #3 receiver
detected Line-CodeViolation alarm
111IO3_RECVR_CRCLine IO #3 receiver
detected CRC alarm
112IO3_RECVR_FBITLine IO #3 receiver
detected Frame Bit Error
113IO4_RECVR_LOFLine IO #4 receiver
Loss-of-framing alarm
114IO4_RE CVR_LOSLine IO #4 receiver
Loss-of-signal alarm
115IO4_RECVR_ALOSLine IO #4 receiver
Loss-of-analog-signal
alarm
116IO4_RECVR_AISLine IO #4 receiver
detected AIS alarm
117IO4_RECVR_RAILine IO #4 receiver
detected RAI (yellow)
alarm
118IO4_RECVR_MRAILine IO #4 receiver
detected multi-framed RAI
(yellow) alarm
119IO4_RECVR_SEFLine IO #4 receiver
detected Severely Errored
Frames
120IO4_RECVR_COFALine IO #4 receiver
detected
Change-of-FrameAlignment alarm
121IO4_RECVR_MAISLine IO #4 receiver
detected multi-framed AIS
alarm
122IO4_RECVR_FEBELine IO #4 receiver
detected E1
Far-End-Block-Errors
alarm
123IO4_RECVR_LCVLine IO #4 receiver
detected
Line-Code-Violation alarm
124IO4_RECVR_CRCLine IO #4 receiver
detected CRC alarm
LED
I/O ALARMINFORM
I/O ALARMINFORM
I/O ALARMINFORM
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMCRITICAL
I/O ALARMINFORM
I/O ALARMINFORM
I/O ALARMINFORM
SNMP
TRAP
LEVEL
139LEDR Series II Installation and Operation GuideMDS 05-3627A01, Rev. C
Table 32. Event Codes (Continued)
IDEVENT NAMEDESCRIPTIONDEFAULT
125IO4_RECVR_FBITLine IO #4 receiver
detected Frame Bit Error
126DIG_REM_LOOPBACKFor EIA-530, local radio is
in remote loopback mode
127SERV_REM_LOOPBACKFor EIA-530, local radio
(as remote server) is
serving remote loopback
mode
128BAD_CLKMODELine framers detected bad
clock mode configuration
LED
I/O ALARMINFORM
NONEINFORM
NONEINFORM
NONEINFORM
19.0 IN CASE OF DIFFICULTY
MDS products are designed for long life and trouble-free operation.
However, this equipment, as with all electronic equipment, may have an
occasional component failure. The following information will assist you
in the event that servicing becomes necessary.
19.1 FACTORY TECHNICAL ASSISTANCE
SNMP
TRAP
LEVEL
Assistance for MDS products is available from our Technical Services
group during business hours (8:00 A.M.–5:30 P.M. Eastern Time).
When calling, please give the complete model number of the radio,
along with a description of the trouble symptom(s) that you are experiencing. In many cases, problems can be resolved over the telephone,
without the need for returning the unit to the factory.
Please use the following telephone numbers for product assistance:
716-241-5510 (Phone)
716-242-8369 (FAX)
19.2 FACTORY REPAIRS
Component level repair of radio equipment is not recommended in the
field. Many components are installed using surface mount technology,
which requires specialized training and equipment for proper servicing.
For this reason, the equipment should be returned to the factory for any
PC board repairs. The factory is best equipped to diagnose, repair and
align your radio to its proper operating specifications.
140LEDR Series II Installation and Operation GuideMDS 05-3627A01, Rev. C
If return of the equipment is necessary, you will be issued a Returned
Material Authorization (RMA) number. The RMA number will help
expedite the repair so that the equipment can be repaired and returned to
you as quickly as possible. Please be sure to include the RMA number
on the outside of the shipping box, and on any correspondence relating
to the repair. No equipment will be accepted for repair without an RMA
number.
A statement should accompany the radio describing, in detail, the
trouble symptom(s), and a description of any associated equipment
normally connected to the radio. It is also important to include the name
and telephone number of a person in your organization who can be
contacted if additional information is required.
The radio must be properly packed for return to the factory. The original
shipping container and packaging materials should be used whenever
possible. All factory returns should be addressed to:
Microwave Data Systems Inc.
Customer Service Department
(RMA No. XXXX)
175 Science Parkway
Rochester, NY 14620 USA
When repairs have been completed, the equipment will be returned to
you by the same shipping method used to send it to the factory. Please
specify if you wish to make different shipping arrangements.
141LEDR Series II Installation and Operation GuideMDS 05-3627A01, Rev. C
142LEDR Series II Installation and Operation GuideMDS 05-3627A01, Rev. C
GLOSSARY
AMI—Alternate Mark Inversion. A bipolar
format where consecutive marks (ones) have
the polarity inverted. Spaces (ones) are represented by zero volts. This technique prevents
long sequences of positive or negative voltages.
Analog—Signals with a continuously varying
amplitude, such as the human voice.
BERT—Bit-error rate test. The results of a
BERT are normally expressed as a ratio (power
of 10) of the number of bits received in error
compared to the total number received.
BER—Bit-error rate. See also BERT.
Bit—Binary digit. The smallest unit of digital
data, often represented by a one or a zero. Eight
bits usually comprise a byte.
bps—Bits-per-second. A measure of the infor-
mation transfer rate of digital data across a
communication channel.
Byte—A digital “word” usually made up of
eight bits.
dBi—Decibels of gain relative to an isotropic
radiator. (A hypothetical antenna which radiates equally in all directions.) Used to express
antenna gain.
dBm—Decibels relative to one milliwatt. An
absolute unit used to measure signal power, as
in transmitter power output, or received signal
strength.
DTR—Data Terminal Ready. A control signal
sent from the radio indicating that it is ready to
transmit data.
CPE—Customer premise (provided) equip-
ment.
DCE— Data (circuit terminating) Communi-
cations Equipment. In data communications
terminology, this is the “modem” side of a
computer-to-modem connection. The transceiver is a DCE device which is designed to
connect to a DTE device.
Decibel (dB)—A measure of the ratio between
two signal levels. Frequently used to express
the gain or loss of a system.
DSP—Digital Signal Processing. A processing
technique that uses software algorithms to
filter, shape, or otherwise modify the characteristics of a given signal. In the LEDR radio, DSP
is used primarily in modulation and demodulation functions.
E1—An international telephony standard that
operates at 2.048 megabits-per-second (Mbps).
This transmission speed is commonly used
throughout the world except for North America
(which uses T1 1.544 Mbps). Framed E1 consists of 30 digitized telephone channels and two
64 Kbps control channels.
EIRP—Effective Isotropic Radiated Power.
Commonly used to express the power radiated
from a gain antenna. It is equal to the power
transmitted (minus feedline loss) plus the
antenna gain.
Fade Margin—The maximum tolerable reduction in received signal strength which still provides an acceptable signal quality. This
compensates for reduced signal strength due to
multipath, slight antenna movement or
changing atmospheric losses. Expressed in
decibels.
FEC—Forward Error Correction. Extra data is
added to the transmitted signal to allow for
detection and correction of some transmission
errors.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide143
Frame—A segment of data that adheres to a
specific data protocol and contains definite
start and end points. It provides a method of
synchronizing transmissions.
Fresnel Zone—A point of maximum width or
girth of the transmitted radio signal. Obstructions in this region (the “first Fresnel zone”)
can have a detrimental effect on reception
quality. As a general rule, 60 percent of the first
Fresnel zone should be free of obstructions in a
well designed system. (Additional considerations are also required when planning a microwave path.
G.703—The ITU standard defining the charac-
teristics of digital interfaces (pulse shape,
voltage levels, etc.). This applies to high-speed,
three-level data being sent over coaxial or
twisted pair lines.
G.821—The ITU standard by which data trans-
mission quality is measured. The analysis considers available vs. unavailable time.
Half-Power Beamwidth—The customary
way of measuring the width of a directional
antenna’s radiation pattern. This beamwidth is
measured in degrees between the half-power
points (the point at which the power is reduced
3 dB with respect to the main beam).
HDB3—High density bipolar order of 3. A line
interface standard for E1 transmission that
employs coding to eliminate data streams with
four or more consecutive zeros.
Hitless Switching Operation—Refers to the
practice of switching between receive signal
paths without introducing bit errors or timing
slips. This feature is required for space or frequency diversity applications.
Hot Standby—Refers to a state of the inactive
(standby) transceiver in a Protected or Redundant configuration. In a Hot Standby configuration, the standby transceiver is actively
transmitting.
ITU—International Telecommunications
Union.
kbps—Kilobits-per-second.
Linecode—Refers to the data coding format
used by the radio for the line interface. (It does
not pertain to the radio’s modulation coding.)
The available linecode selections are HDB3
and AMI.
Mbps—Megabits-per-second.
MIB—Management Information Base. The
MIB stores SNMP messages that are directed
to the management console. This can include
Server events, statistical data and system queries.
Multipath Fading—Signals arriving at the
receiver out of phase which have a tendency to
cancel each other. It is caused by reflections of
the transmitted wave and results in distortion at
the receiver or weak received signal strength.
Multiplexer—A signal processing unit that
combines multiple streams of data into one for
transmission across a single data channel.
NMS—Network Management System. A software application used to configure, diagnose
and monitor a communication network. The
LEDR radio’s SNMP program is an example of
an NMS.
Protected Radio—A radio configuration
where there are redundant modules that automatically become active in the event of a
failure.
Protected Operation—Refers to the practice
of providing redundant transmit and receive
signal paths through the radio (antenna to customer payload interface) so that no single point
of failure in a single radio will interrupt the
link. This feature is also referred to as 1+1
Operation and is usually provided by operating
the system using Hot Standby.
PSC—Protected Switch Chassis. Chassis
holding data and RF control/switch circuitry in
a redundant/protected configuration.
144LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
QAM—Quadrature Amplitude Modulation.
Uses phase shifts and amplitude changes to
send high-speed data in a comparatively
narrow RF channel. See also QPSK.
QPSK—Quadrature Phase Shift Keying. Uses
four levels of phase shift to send high-speed
data with a higher system gain than QAM modulation. See also QAM.
Redundant Switching—Refers to the practice
of switching between transmit signal paths
when a fault condition occurs on the currently
active radio.
RSSI—Received signal strength indication.
Expressed in dBm.
SNMP—Simple Network Management Protocol. A common network management system
(NMS) protocol used to monitor and control a
communications network
SNR—Signal-to-noise ratio. Expressed in
decibels (dB).
SWR—Standing Wave Ratio. A parameter
related to the ratio between forward transmitter
power and the reflected power from the antenna
system. As a general guideline, reflected power
should not exceed 10% of the forward power
(2:1 SWR).
TFTP—Trivial File Transfer Protocol. A standard network protocol used to send and receive
files between two devices.
Warm Standby—Refers to a state of the inactive (standby) transceiver in a Protected or
Redundant configuration. In a Warm Standby
configuration, the standby transceiver is not
transmitting and must be keyed after switching.
MDS 05-3627A01, Rev. CLEDR Series Installation & Operation Guide145
146LEDR Series Installation & Operation GuideMDS 05-3627A01, Rev. C
• The unit IP address are factory configured with a unique address based on the last three digits of the
unit serial number.
• Use IP command to change the IP address, set netmask, gateway and IP Port as necessary. In a
protected radio, change the RDNT settings to match the user-assigned IP addresses.
8. Assign user configurable fields (As required)
Many items are user configurable, to ease customer use. These include, but are not limited to the following.
See the NMS command description in the manual for more detail:
• Set user information fields using INFO command (Page 62).
• Set alarms and alarm mappings using the ALARM (Page 49) and EVMAP (Page 57) commands.
• Set alarm thresholds using the THRESHOLD command (Page 83).
• Set the SNMP community using the SNMPCOMM command (Page 81).
9. Perform bench tests to verify the performance of the radio
The data performance and NMS should be verified. Use the LOOPBACK commands (Page 69) to verify
data throughput. (See “BENCH TESTING OF RADIOS” on Page 124.)
10.Install the link
Peak the antennas for maximum RSSI using the continuously updated RSSI command (Page 80) through
the front panel screen or the TREND command (Page 86) via the NMS.
11. Verify proper operation by observing the LED display
• Refer to “Front Panel” on Page 13 for a description of the status LEDs.
• Aim directional antenna for maximum receive signal strength using the RSSI Screen.
12. Configure the SNMP Manager software
• Refer to the SNMP Handbook (Part No. 05-3532A01). (This manual is published by MDS in paper
form, or may be downloaded from our web site at www.microwavedata.com.
End of Quick Start Guide
175 Science Parkway, Rochester, New York 14620
General Business: +1 (716) 242-9600
FAX: +1 (716) 242-9620
www.MicrowaveData.com
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.