User's Manual

MDS 05-2708A01, Rev. A MDS TransNET I/O Guide 37
8.3 Troubleshooting Chart
Table 10 provides suggestions for resolving system difficulties that may be
experienced in the radio system. If problems persist, contact the factory for
further assistance. Refer to the inside back cover of this guide for contact
information.
9.0 TECHNICAL REFERENCE
The following section contains material that is not essential to using the radio,
but may prove helpful in diagnosing performance problems or in gaining a
better understanding of the unit’s operation.
9.1 Technical Specifications
GENERAL
Frequency Hopping Range: Up to 1028 frequencies within:
MDS TransNET 900
™: 902–928 MHz,
configurable in 3.2 MHz zones
Hop Pattern: Based on network address
Frequency Stability: ±1.5 ppm
Simplex Operation: User selectable
Half-Duplex Operation: MDS TransNET 900
™: ±1.6 MHz TX/RX split
Network Addresses: 65,000
Temperature Range: –30°C to +60°C
Humidity: <95% at +40°C; non-condensing
Table 10. Troubleshooting chart
Difficulty Recommended System Checks
Unit is
inoperative.
a. Check for the proper supply voltage at the power connector.
b. The transceiver’s internal resettable fuse may have tripped. To
reset it, momentarily remove and re-apply power to the radio.
Interference is
suspected.
a. Verify that the system has a unique network address. Nearby
systems with the same address will cause interference.
b. Check for interference by locking out affected zone(s) using the
SKIP command (
Page 33).
c. If omnidirectional antennas are used on remote stations, consider
changing to directional antennas. This will often limit interference
to and from other stations.
No
synchronization
with master, or
poor overall
performance.
a. Check for secure interface connections at the radio and the
connected device.
b. Check the antenna, feedline and connectors. Reflected power
should be less than 10% of the forward power reading
(SWR
≈2:1 or lower).
c. If the remote radio is in synchronization, but performance is poor,
check the received signal strength using the RSSI command
(
Page 30). If RSSI is low, it may indicate antenna problems, or
misalignment of directional antenna headings.
d. Verify proper programming of system parameters: mode, network
address, data interface baud rate, transmitter power, CTS delay,
etc.
e. Check for alarms using the STAT command (
Page 34)