User's Manual
Table Of Contents
- Eclipse ODU 600 5.8 GHz ISM Band Installation Manual Rev.001
- Copyright & Terms of Use
- Aviat Networks Support
- Eclipse Product Compliance Notes
- Contents
- Volume I: Introduction and Safety
- Volume II: System Overview
- Volume III: Installation
- Chapter 1. Introduction to Installation
- Chapter 2. ODU Installation
- Chapter 3. INU and INUe Installation
- INU/INUe Overview
- Installation Requirements
- Installation Procedure
- Plug-in Installation
- INU/INUe Cable Assemblies
- DAC Trib Connectors and Cables
- NMS Connectors and Cables
- NMS 10/100Base-T Connector
- Maintenance V.24 Connector
- Auxiliary and Alarm Connectors and Cables
- AUX Data Cable: Async, HD26 to Wirewrap, 2 m
- AUX Data Cable: Sync, HD26 to Wirewrap, 2 m
- AUX Data Cable: Async, HD26 to 3 X DB9, 1 m
- AUX Data Cable: Sync, HD26 to 3 X DB9, 1 m
- AUX Data Cable: Async, AUX HD26 to AUX HD26, 1 m
- AUX Data Cable: Sync, AUX HD26 to AUX HD26, 1 m
- AUX Alarm I/O Cable: HD15 to Wirewrap, 2 m or 5 m
ECLIPSE INSTALLATION MANUAL
Routine Inspection and Maintenance
This section overviews required and recommended inspection and maintenance prac-
tices to ensure health and safety of installed equipment is maintained to highest
levels. For more information, refer to the Aviat Networks publication: Best
Practices.
Routine Inspections
All sites must be inspected annually, or more frequently if subject to abnormal oper-
ating conditions such as particularly exposed sites, or sites subject to salt-spray or
heavy snow/ice loading over winter months.
The inspection should cover the physical installation including the antenna, wave-
guide, waveguide pressurization installation, equipment grounding, tower and build-
ing grounds, weatherproofing, and general site integrity.
Selected ground wires should be resistance checked and then compared with pre-
vious checks to ensure there has been no significant change.
The operational performance of the radio and associated equipment should be
checked against their as-built figures using the Portal or ProVision alarm and per-
formance indicators.
Trend Analysis
Use available current and historical Eclipse alarm and performance data to determ-
ine any trend that may lead to a failure - if allowed to continue.
Check for the following trends:
l Reducing receive signal levels
l Gradually increasing bit errors or an increasing errored seconds count
l Changes in transmit power
l Increased frequency of rain fade or other fade conditions
l Increasing occurrence of other weather related changes in performance
l Increasing occurrence of a particular hardware failure
Time spent in conducting such analysis is time well spent. Catching a problem
before it brings down the network is good network management.
260-668066-004 AUGUST 2013 11