User's Manual
Table Of Contents
- 1.0 INTRODUCTION
- 2.0 MODEL NUMBER CODES
- 3.0 HARDWARE INSTALLATION AND BASIC INTERFACE REQUIREMENTS
- 4.0 INITIAL STARTUP AND CONFIGURATION
- 4.1 Introduction
- 4.2 STEP 1—Power up the LEDR Radios
- 4.3 STEP 2—Establish Communications with the Radio
- 4.4 STEP 3—Make Initial Login to Radio
- 4.5 STEP 4—Change the SUPER Password
- 4.6 STEP 5—Review Essential Operating Parameters
- 4.7 STEP 6—Set TCP/IP Settings to Enable SNMP and/or Telnet Management (if required)
- 4.8 STEP 7—Set User Configurable Fields
- 4.9 STEP 8—Verify Radio Performance
- 4.10 STEP 9—Install the Link
- 4.11 STEP 10—Verify the Link Performance
- 5.0 CONFIGURATION AND CONTROL VIA THE FRONT PANEL
- 6.0 CONFIGURATIONAND CONTROL VIA THE CONSOLE PORT
- 7.0 STANDARDIZING RADIO CONFIGURATIONS
- 8.0 UPGRADING LEDR FIRMWARE
- 9.0 USING ORDERWIRE
- 10.0 USING THE SERVICE CHANNEL
- 11.0 PROTECTED CONFIGURATION
- 12.0 SPACE DIVERSITY OPERATION
- 13.0 SPARE PARTS, UNITS AND ACCESSORIES
- 14.0 Fractional-T1 INTERFACE CARD 03-3846A01 Fractional-E1 INTERFACE CARD 03-3846A02
- 15.0 INCREASE BANDWIDTH BY CHANGING TRANSMITTER AND RECEIVER FILTERS
- 16.0 BENCH TESTING OF RADIOS
- 17.0 TECHNICAL REFERENCE
- 17.1 Specifications— Models: LEDR 400S, 700S, 900S and1400S
- 17.2 Specifications— Models: LEDR 400F, 900F, 1400F
- 17.3 Specifications— Protected Switch Chassis
- 17.4 Optional Equipment (Consult factory for detailed information)
- 17.5 Accessories
- 17.6 I/O Connector Pinout Information
- 17.7 Watts-dBm-Volts Conversion
- 18.0 RADIO EVENT CODES
- 19.0 IN CASE OF DIFFICULTY
58 LEDR Series I/O Guide MDS 05-3627A01, Rev. D
This command allows viewing the pending events (pending), sup-
pressing the notification of particular events (
filter), initializing events
processing (
init) and display of event descriptions (desc). To turn off log-
ging (notification in the event log) for a particular event, the filter count
value should be set to zero.
Events 135-138 are
remote alarm in [1-4], respectively, which reflects the
event state of the
alarm in [1-4] of the remote-located radio at the other end
of the RF link.
Example Response:
events {events}: -DEMOD_ACQUISITION (Event #27)
events: Event#0 Filter count=1
events {init}: The event log has been re-initialized
events {desc}: Event#40 Description-
IO2_DIG_REM_LPBACK
evmap Event Mapping (for Alarm Output and LEDs)
Usage: evmap [subcommand] [event #] [arguments]
This command sets or displays which radio system events cause alarm
indications on the front panel LEDs or the rear panel
ALARM I/O con-
nector. The user can rename the alarm events, but they cannot be
deleted, nor can new ones be created.
The subcommands specify which output will be asserted (
led or aout)
upon occurrence of an
event #. Multiple outputs can be specified with
spaces between them. The
dump option allows determining the current
event mapping for all of the events or, optionally, a specified numeric
range of events.
Events 135-138 are
remote alarm in [1-4], respectively, which reflects the
event state of the
alarm in [1-4] of the remote-located radio at the other end
of the RF link. Use the event filter counter to enable each particular
event. Use
evmap and map to alarm output contact when necessary.
Subcommands are listed below:
led [ioalarm|txalarm|rxalarm|alarm|none]—Maps front panel LED(s)
to an event.
aout [none|1|2|3|4]—Maps an alarm output(s) to an event.
dump [<range>]—Display the LED and alarm output mappings
for all events.
See Figure 8 for reference to the Front Panel LEDs. Refer to Alarm—
Rear Panel on Page 129 for the pinouts of the
ALARM I/O connector and
Disabling the Front Panel Alarm LED for Unused E1 Option Ports on
Page 88 for further information.
fec Forward Error Correction Statistics
Usage:
[fec <clear>]