GE Enterprise Access OPS Manual

GE Healthcare
Enterprise Access System

Service Manual
Enterprise Access
English
2032088-002 (cd)
2032087-002C (paper)
© 2008 General Electric Company.
All rights reserved.
NOTE
Due to continuing product innovation, specifications in this manual are subject to change without notice.
NOTE
For technical documentation purposes, the abbreviation GE is used for the legal entity name, GE Medical Systems
Information Technologies.
Listed below are GE Medical Systems Information Technologies trademarks. All other trademarks contained herein are the
property of their respective owners.
ApexPro, CARESCAPE, CIC Pro, and Unity Network are trademarks of GE Medical Systems Information Technologies.
T-2 Enterprise Access 2032086-003C

15 October 2008
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Manual information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Illustrations and names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Manufacturer’s responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Safety statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
2 Equipment overview . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

System overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Enterprise Access wideband antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
SMUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
SMU-MS (WMTS + 802.11a/b/g + mobile services) . . . . . . . . . . . . . . . . . 2-5
SMU bracket assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
RHUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
MA 1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
MA 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
MA 1000/MA 2000 RHU monitoring and configuration. . . . . . . . . . . . . . . 2-13
MA 1200 Add-on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
WMTS RHU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
SHUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
AP to antenna distribution patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
WMTS-SHU-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
BUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
BU front and rear panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
BU monitoring and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
RIUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
2032086-003C Enterprise Access i

RIU front and rear panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
Powering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
RF signal connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Control signal connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
RIU monitoring and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Fault detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
RIM Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
RIM Main front and rear panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
RIM Main monitoring and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
RIM 1400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
RIM 1400 front and rear panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
RIM 1400 monitoring and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
RIM Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
RIM Expansion front and rear panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
MA 330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71
System operation and capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
MA 330 Main unit description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74
MA 330 Main front and rear panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75
MA 330 Remote unit description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
MA 330 Remote front and rear panels . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
MA 330 Expansion unit description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80
Network Management System (NMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80
NMS 410 and NMS 430 controller description . . . . . . . . . . . . . . . . . . . . . 2-81
Controller front and rear panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83
NMS controller monitoring and configuration . . . . . . . . . . . . . . . . . . . . . . 2-85
Enterprise Access service software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-89

Service Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-89
CARESCAPE Systems Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-89
3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Performance characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Antenna placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Safety requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Antenna installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
ii Enterprise Access 2032086-003C

Remote closet installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Main closet installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Interconnecting Enterprise Access components . . . . . . . . . . . . . . . . . . . . 3-6
NMS software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
4 NMS System Management . . . . . . . . . . . . . . . . . . . . 4-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
NMS MCT client software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Installing and configuring NMS system management . . . . . . . . . . . . . . . . . 4-2

430 controllers IP address configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Server setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Client setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Launching and login to the NMS Manager . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
NMS Manager main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Topology configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Defining nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Defining domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
5 CARESCAPE Systems Manager . . . . . . . . . . . . . . . 5-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Service software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Configure the service software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Uninstall CARESCAPE Systems Manager software . . . . . . . . . . . . . . . . 5-15
Uninstall OpenNet Expert software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
6 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Controlling electrostatic discharge damage . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Ventilation ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
2032086-003C Enterprise Access iii

Checkout procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
About the checkout procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Check for valid network connections to NMS 430/410 . . . . . . . . . . . . . . . . 6-4
Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
RIM 1400 Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Receiver calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Transmitter calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Maintenance checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Checkout procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Repair log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Antenna system troubleshooting tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Antenna system troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Drop-out determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
ApexPro CH system troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
ApexPro FH antenna system (yellow drop-out condition) . . . . . . . . . . . . . 7-7
Enterprise Access infrastructure troubleshooting. . . . . . . . . . . . . . . . . . . 7-21

Troubleshooting tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
General fault isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
NMS System troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
MA 330 System troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
WMTS-SHU-4 system troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Component troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
8 Replaceable parts . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Enterprise Access models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Other parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
A Technical specifications . . . . . . . . . . . . . . . . . . . . . . A-1

Environmental specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Power specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Standards and approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
iv Enterprise Access 2032086-003C

B Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
C Firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Upgrade kit contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Equipment setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Pre-upgrade procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5

Install the Atmel Flip application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Install the Cerberus FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Install the Lantronix DeviceInstaller application . . . . . . . . . . . . . . . . . . . . . C-6
Install Version Update Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Upgrading MA 410/430 controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Install the MA 410 controller card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Upgrade the communications micro-controller . . . . . . . . . . . . . . . . . . . . . C-7
Upgrade the basic micro-controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Replace the MA 430 controller card . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Upgrade MA 430 controller agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Upgrading RHUs (MA 1000, MA 2000, and WMTS) and MA 1200 add-on units
C-16
General upgrade procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
Verify the upgrade procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-18
Upgrading the WMTS-SHU-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19
Connect the WMTS-SHU4 to the network . . . . . . . . . . . . . . . . . . . . . . . . C-19
Perform auto-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19
Upgrade the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
Upgrading base units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20

General upgrade procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
Upgrading RIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-22

General procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-22
Upgrading RIM mains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-25
Upgrading the RIM 1400s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27
2032086-003C Enterprise Access v

vi Enterprise Access 2032086-003C
1 Introduction
2032086-003C Enterprise Access 1-1

Introduction
Manual information
Revision history
Each page of this manual has the document part number and revision letter at the
bottom of the page. The revision letter identifies the document’s update level. The
revision history of this document is summarized below.
Revision Comment
A Initial Release
B Updated for site feedback.
C Updated for calibration schedule.
Conventions
Style Definition
bold Indicates hardware items such as keys, labels, or text entered by the
user.
bold italic Indicates software terms such as menu items or screen text.
+ Indicates keyboard keys to select simultaneously.
> Indicates menu options to select consecutively.
Illustrations and names

All illustrations in this manual are provided as examples only. They may not
necessarily reflect your setup or data displayed on your system.
In this manual, all names appearing in examples and illustrations are fictitious. The
use of any real person's name is purely coincidental.
Intended audience
This manual is intended for service representatives and technical personnel who
install, configure, maintain, administer, troubleshoot, or repair this equipment.
Ordering manuals
A paper copy of this manual will be provided upon request. Contact your local GE
representative and request the part number on the first page of the manual.
1-2 Enterprise Access 2032086-003C

Introduction
Related manuals
ApexPro Telemetry System CH Operator’s Manual
ApexPro Telemetry System CARESCAPE Telemetry T14 Operator’s Manual
ApexPro FH Operator’s Manual
CIC Pro Clinical Information Center Service Manual
Frequency Hopping Telemetry System Implementation Guide
ApexPro Telemetry System Frequency Chart Reference Manual
OpenNet User’s Guide
ApexPro Antenna Infrastructure, Transmitter and Receiver Technical Manual
Design documentation provided by ND & I
Safety information
Manufacturer’s responsibility
GE is responsible for the effects of safety, reliability, and performance only if:
Assembly operations, extensions, readjustments, modifications, or repairs are

carried out by persons authorized by GE;
The electrical installation of the relevant room complies with the requirements of
the appropriate regulations; and
The device is used and maintained in accordance with the instructions for use.
Intended use
The GE Enterprise Access system is not intended for home use.
Enterprise Access current offering includes (but is not limited to):
ApexPro Dual Band CH

ApexPro FH
Cellular/PCS
ISM (2.4 and 5.1-5.8 GHz)
800/900 MHz 2-way radio
WiFi (802.11 a/b/g)
Paging (900 MHz band)
Contact GE for information before connecting any devices to the GE Enterprise
Access system that are not recommended.
Safety statements
The safety statements presented in this chapter refer to the equipment in general and,
in most cases, apply to all aspects of the device. There are additional safety statements
in other chapters which are specific to that chapter content.

Introduction
The order in which safety statements are presented in no way implies the order of
importance.
Dangers
Danger statements identify an imminent hazard which, if not avoided, will result in
death or serious injury. No danger statements apply to this system.
Warnings
Warning statements identify a potential hazard or unsafe practice which, if not
avoided, could result in death or serious injury.
The following warning statements apply to this system.
WARNING
LOSS OF DATA — Proper system design and configuration is
critical to performance and should only be attempted by qualified
personnel according to approved processes.
WARNING
LOSS OF DATA — Shut down of Enterprise Access components
causes a disruption of data flow between the Unity Network MC
network devices and the hospital enterprise network. Notify the
affected users relying upon this data flow before shutting down the
Enterprise Access, or if the Enterprise Access components shut
down for any reason.
WARNING
THERMAL HAZARD — Internal components, especially power
supplies, get extremely hot when the Enterprise Access components
are in operation. Shut down the components and allow to cool before
touching any internal components.
WARNING
EXPLOSION HAZARD — Do not use this equipment in the
presence of flammable anesthetics, vapors or liquids.
WARNING
SHOCK HAZARD — The Enterprise Access and all peripheral
equipment must be adequately grounded or a shock hazard may
exist.

Introduction
WARNING
PERSONAL INJURY/EQUIPMENT DAMAGE — The Enterprise
Access components are installed in a rack; observe the following
guidelines associated with rack stability:
Ensure both the top and bottom of the rack are securely fastened
to a suitable and substantial building support.
Ensure the rack weight is supported by the leveling jacks and
that the rack leveling jacks are in contact with the floor.
If it is a single rack installation, ensure stabilizers are attached.
If it is a multiple rack installation, ensure the racks are tightly
secured together.
Do not extend more than one component outside the rack at a
time.
WARNING
To comply with FCC RF exposure compliance requirements.
antennas used for this product must be fixed mounted on indoor
permanent structures, providing a separation distance of at least 20
cm from all persons during normal operation and that the antenna
must not be co-located with any other antenna.
WARNING
The design of the antenna installation needs to be implemented in
such a way so as to ensure RF radiation safety levels and non-
environmental pollution during operation.
Cautions
Caution statements identify a potential hazard or unsafe practice which, if not
avoided, could result in minor personal injury or product/property damage.
The following caution statements apply to this system.
CAUTION
U.S. Federal law restricts this device to sale by or on the order of a
physician.
This CAUTION applies when the Enterprise Access system is used

to transmit medical information.

Introduction
CAUTION
LOSS OF FUNCTION/EQUIPMENT DAMAGE — Do not load
any software other than that specified/approved by GE onto the
Enterprise Access components. Installation of software not specified
by GE may cause damage to the Enterprise Access components or
loss or corruption of data.
CAUTION
REGULATION COMPLIANCE/ENVIRONMENTAL
CONTAMINATION — At the end of its service life, the Enterprise
Access components, as well as accessories, must be disposed of in
compliance with the guidelines regulating the disposal of such
products. If you have questions concerning disposal of the product,
contact GE or its representatives.
CAUTION
EQUIPMENT DAMAGE — Use an anti-static strap when cleaning
the internal components. The Enterprise Access components are
extremely static sensitive and should be handled using electrostatic
discharge procedures.
CAUTION
INSTRUCTIONS FOR USE — For continued safe use of the
Enterprise Access components, it is necessary that the listed
instructions are followed. However, instructions listed in this manual
in no way supersede established medical practices concerning
patient care.
CAUTION
LOSS OF FUNCTION — Make sure that all external devices
operated in the vicinity of the equipment comply with the relevant
EMC requirements. X-ray equipment or MRI devices are a possible
source of interference as they may emit higher levels of
electromagnetic radiation. Magnetic and electrical fields are capable
of interfering with the proper performance of the device.

Introduction
CAUTION
LOSS OF FUNCTION/EQUIPMENT DAMAGE — Only external
devices specifically designed to be connected to the Enterprise
Access components, or approved by GE for use with the Enterprise
Access components should be connected, as specified in this manual
or as otherwise specified by the manufacturer. External equipment
must be connected to the system only by qualified biomedical
engineering personnel. Connecting external devices not approved
for use with the Enterprise Access components may cause loss of
function or equipment damage.
CAUTION
LOSS OF FUNCTION — All external cabling used with the
Enterprise Access components must be routed so as not to interfere
with access or operation of the system and must be installed to
protect against accidental disconnection of the cables.
CAUTION
EQUIPMENT DAMAGE/DATA LOSS — Follow the maintenance
instructions in this manual. GE does not assume responsibility for
damage to the equipment caused by improperly loaded software,
failure or data loss due to not using a UPS, and/or current or future
conditions of the equipment due to improper care and maintenance.
CAUTION
EQUIPMENT/DATA DAMAGE/LOSS — The Enterprise Access
components must only be used by persons who have received
adequate training in the use of its software and who are capable of
applying it properly.
Notes
Note statements provide application tips or other useful information.
The following note statements apply to this system.
Keep all packing material until you have completed the inspection.
Compliance with RF safety requirements:
Enterprise Access products have no inherent significant RF radiation.
The RF level on the downlink is very low at the remote unit downlink ports.
Therefore, there is no dangerous RF radiation when the antenna is not
connected.

Introduction
Laser safety
WARNING
To avoid eye injury never look directly into the optical ports, patch
cords or optical cables. Do not stare into beam of view directly with
optical instruments. Always assume that optical outputs are on.
Fiber optic ports of the following Enterprise Access equipment emit invisible laser
radiation at the specified wavelets windows:
WMTS RHU, MA 1000, and MA 2000 - 1310 nm wavelength window

MA 330 - 1310/1550 nm wavelength window
Only technicians familiar with fiber optic safety practices and procedures should
perform optical fiber connections and disconnections of the Enterprise Access
equipment and the associated cables.
The WMTS RHU, MA 1000, MA 2000, and MA 330 comply with 21 CFR 1040.10
and 1040.11 except for deviation pursuant to Laser notice No. 50 (July 26, 2001) and
IEC 60825-1, Amendment 2 (Jan. 2001).
Care of fiber optic connectors

Do not remove the protective covers on the fiber optic connections until a
connection is ready to be made. Do not leave connectors uncovered when not
connected.
The tip of the fiber optic connection should not come into contact with any object
or dust.
Refer to the cleaning procedure for information on cleaning the fiber tip.

2 Equipment overview

Equipment overview
This chapter describes each of the system elements, their configurable options, and
their individual connections.
System overview
The Enterprise Access system allows a single coaxial and broadband antenna
infrastructure to be used to provide coverage for mobile services (Cell800, LMR800,
SMR900, and PCS1900), ApexPro telemetry (ApexPro, ApexPro dual band CH or
ApexPro FH), and WiFi (802.11a/b/g). The following are some additional features of
this system:
All active components are located in the Main closet/head-end or in one of the
remote closets
Remote and onsite monitoring and configuration of equipment is provided by the
Network Management System (NMS) and the Service Gateway.
The following is a block diagram of a typical Enterprise Access system with mobile
services, ApexPro dual band CH telemetry, and WiFi. The area inside the shaded box
represents the Enterprise Access system. The devices outside the shaded box are not
part of the Enterprise Access system.
203

Equipment overview
The following is a block diagram of a typical Enterprise Access system with mobile
services, ApexPro FH telemetry, and WiFi. The area inside the shaded box represents
the Enterprise Access system. The devices outside the shaded box are not part of the
Enterprise Access system.
291B

Equipment overview
The Enterprise Access system consists of the following main elements:
Element Function
Service Multiplexer Unit Enables the convergence of WMTS, mobile services, and
(SMU) WiFi (802.11a/b/g) services. See SMUs on page 2-5.
Antenna The Enterprise Access wideband antenna can support

WMTS, mobile services, and 802.11a/b/g services. See
Antennas on page 2-5.
Mobile Services Remote Performs RF to optic signal conversion at the remote closet
Hub Unit (RHU) MA 1000/ (antenna) side for up to two services. A third service can be
2000 added by connecting an add-on remote hub unit (MA 1200) to
the RHU. See Mobile services RHUs on page 2-6.
WMTS Remote Hub Unit Performs RF to optic signal conversion at the remote closet
(RHU) (antenna) side for the Wireless Medical Telemetry Services
(WMTS). See WMTS RHUs on page 2-7.
WMTS Switching Hub Unit Provide a single point connection for up to four ApexPro FH
(SHU) APs and distributes the signals over up to four antennas.
Base Unit (BU) Performs RF to optical conversion in the Main closet/head-

end. See BUs on page 2-45.
Radio Interface Unit (RIU) Provides interfaces for up to three BTS/BDA signals and
automatically adjusts the output signal in response to input
signal level to provide optimal coverage. See RIUs on page
2-49.
Receiver Interface Module Conditions the ApexPro CH 608-614 MHz WMTS signal. It
(RIM) Main can interface with up to two RIM Expansions. See RIM Main
on page 2-57.
Receiver Interface Module Used in conjunction with the RIM Main to enable the ApexPro
(RIM) 1400 CH 1395 - 1400 MHz WMTS signal.
Receiver Interface Module Provides interfaces to up to 16 ApexPro CH receiver sub-

(RIM) Expansion systems. See RIM Expansion on page 2-69.
NMS controller A component of the Network Management System. This

device allows for configuration and monitoring of the
Enterprise Access system. See Network Management
System (NMS) on page 2-80.
Service Gateway Provides central monitoring and remote serviceability
Elements that are not part of the Enterprise Access system, but which interface
directly with it, include the following:
BTS/BDA - Represents the signal source from the mobile service providers
ApexPro CH receiver sub-system
WiFi (802.11a/b/g) AP
ApexPro FH AP

Equipment overview
Antennas
Enterprise Access wideband antennas
Enterprise Access wideband antennas can support WMTS, mobile services, and
802.11a/b/g services. The antennas are distributed throughout the coverage areas.
They interface with the remote modules (RHUs, SHUs and SMUs) in the remote
closet via coaxial cables.
202A
SMUs
Overview
The SMU enables convergence of WMTS, mobile services, and 802.11a/b/g services,
so that all services can be included on a single antenna infrastructure.
On one side of each SMU are the inputs from the services to be converged, and on the
other side the coaxial connection to the antenna run.
SMU-MS (WMTS + 802.11a/b/g + mobile services)

The following figure shows an individual SMU-MS that is used to converge mobile
services, 802.11a, 802.11 b/g services and WMTS services for distribution through a
single antenna.
NOTE
SMU-MS provides separate interfaces for 802.11a and for 802.11 b/g.

Equipment overview
SMU-MS
WMTS 802.11b/g 802.11a MS
204 & 151
SMU bracket assemblies

An SMU bracket is available for mounting multiple SMUs. Several configurations
are available to suit various installation types. The SMU bracket can be mounted on a
standard 19” rack or it can be wall mounted.
Each bracket can support up to 3 SMU-MSs.
RHUs
Overview
Remote Hub Units, corresponding to the service types, perform the optical to RF
conversion of each service at the individual building floors (remote closets). The
RHU types can be divided broadly into two classes:
Mobile services
WMTS
Mobile services RHUs

These RHUs interface via the Base Unit with the RIU. They consist of the MA 1000,
MA 2000, and MA 1200 modules. The following table shows the frequency ranges
that are supported:
Frequency range (MHz)

Service description
Uplink Downlink
Cell800 824-849 869-894
LMR800 806-824 851-869
SMR900 896-902 935-941
PCS1900 1850-1910 1930-1990
The MA 1000 and MA 2000 RHUs are dual band. The following table shows the MA
1000 and MA 2000 modules that are available:

Equipment overview
RHU name First band Second band
Cellular/PCS Cell800 PCS1900
IDEN/SMR/Paging LMR800 SMR900
All MA 1000 and MA 2000 RHUs can be connected to an MA 1200 Add-on module
which provides a PCS1900 band.
Technologies that are supported include TDMA, CDMA, WCDMA, and GSM.
The choice between using an MA 1000 and an MA 2000 is based on the number of
mobile services installed and desired future expandability. See the detailed
descriptions of these modules for more information.
WMTS RHUs
These RHUs interface via the Base Unit with the RIM Main. This module supports
608-614MHz.
MA 1000
Overview
The MA 1000 system provides an entry-level solution that can be upgraded to the MA
2000 solutions as required. The MA 1000 solution supports one RHU and one
optional MA 1200 Add-on module. This allows for a maximum of three mobile
service bands to be present on the system.
209
MA 1000 System Overview
Features
Modular and scalable – additional remote units can easily be installed
Software programmable parameters including output power, AGC (on/off and
levels), and system gain
MA 1000 front and rear panels
RHU 1000 front panel

The RHU 1000 front panel contains the fiber optic connections to the BU, four
coaxial connections to the antennas, power connections and status indicators.

Equipment overview
If RHU 1000 and MA 1200 Add-on units are installed, then the combined services are
fed to the coaxial infrastructure through the RHU 1000 antenna ports.
NOTE
Only specific configurations allow antenna sensing, refer to the design

documents to determine if your configuration applies.
213
LED Description
COMM Active communication detected
LINK Optical link to BU detected
PWR DC power connected
RHU 1000 rear panel

The RHU 1000 rear-panel provides the control, RF interface and optic interface ports
that enable connecting an MA 1200 Add-on unit to the RHU 1000 module.
Connector Description
Add-on control Transmits the control signals from MA 1200 Add-on module
to the RHU 1000 module. Connected to the MA 1200 Add-on
Control From port.
High Band Connects to the 1200 Add-on HIgh Band port. Provides the
interface to the Add-on RF service which is combined with
the RHU services and distributed through the common
coaxial infrastructure.
DL, UL Transmits the RF signals to and from the MA1200 Add-on

module. These ports are connected to the corresponding
ports on the MA 1200 rear panel: DL to DL, UL to UL.
External filter ports (not Enables the insertion of an external filter.

shown)

Equipment overview
MA 2000
Overview
The MA 2000 system provides scalable in-building coverage for multiple wireless
data and voice services. There are two MA 2000 configurations available:
MA 2000 Modular Remote Cabinet (MRC) - The MRC is a cabinet in which up

to five MA 2000 RHUs and MA 1200 Add-on modules can be contained. The
MRC contains power, filtering, and combining functionality.
MA 2000 Lite - The MA 2000 Lite solution combines the signals from up to two
MA 2000 RHUs. Additionally, each MA 2000 RHU can be connected to an MA
1200 Add-on. Unlike the MRC configuration, the RHU and add-on modules are
installed externally to the enclosure.
217
MA 2000 MRC
The MRC can house various combinations of up to five RHU 2000 and MA 1200
Add-on modules. The number of modules depends on the models, required filtering,
etc. The MRC provides the combining, power interface and antenna interface
functions. The optic connection from the BUs are connected directly to the
corresponding RHU 2000 module.
The MRC is provided in an integrated power supply configuration. A power supply is

integrated into the cabinet and fed from an external AC power source. The individual
modules are internally connected to the power supply. This model includes a battery
connection as well.
The cabinet may be mounted on a wall or in a 19” rack. The appropriate brackets are
provided with each type of installation.
The MRC is illustrated below:

Equipment overview
220
The following figure shows an open MRC, integrated power supply model, with four
RHU 2000 modules and four filters. (For clarity, the internal connections are not
included.)
221
The following image shows the MRC with the cabling. Note that the antenna ports of
the individual modules are connected to the internal RF connections (under the
antenna ports) and the filters as required. The PS connections of each module are also
connected to cables that are internally routed to the integrated PS.
NOTE
The fiber optic connections are not displayed.
222

Equipment overview
MA 2000 Lite
The MA 2000 Lite provides interfaces and filtering required to support up to two MA
2000 RHUs. An MA 1200 Add-on module can be connected to each MA 2000 RHU
if desired.
The dedicated power supplies, MA 2000 RHUs, and optional MA 1200 Add-on
modules are connected externally to the MA 2000 Lite.
The following figure illustrates the MA 2000 Lite connected to two MA 2000 RHUs.
223
8 x 4 combiner
The 8 x 4 combiner is contained in both the MA 2000 MRC and MA 2000 Lite
solutions. The combiner merges the signals from multiple MA 2000 RHUs and
outputs the signal through four ports to a common coaxial antenna infrastructure.
The 8 x 4 combiner enables combining eight inputs: four high-band and four low-
band. It provides low RF loss and high isolation for the input devices.
The front panel of the unit contains the four antenna interface ports, LEDs and control
port.
224
The following table describes the front panel connectors.
Ant-1 to Ant-4 (N-type) coaxial connections to corresponding antennas
The rear panel of the unit contains four low-band and four high-band ports as well as
the control port.

Equipment overview
225
SMA connectors Description
Low Band Four connectors for the low-band outputs of the

corresponding remote unit.
High Band Four connectors for the high-band outputs of the

corresponding remote unit.
RHU 2000 front panel

The RHU 2000 front panel contains the fiber optic connections to the BU, four
coaxial connections to the antennas, power connections and status indicators.
RHU 2000 front panel indicators
LED Description
COMM Active communication detected
RHU 2000 front panel connection
RS232 Receives antenna status from MRC
RHU 2000 rear panel

The RHU 2000 rear panel provides the control, RF interface and optic interface ports
that enable connecting an MA 1200 Add-on unit to the RHU 2000 module.

Equipment overview
219
RHU 2000 rear panel connectors
Add-on control Transmits the control signals from MA 1200 Add-on module
to the RHU 2000 module. The Add-on Control port is
connected to the MA 1200 Add-on From port.
DL, UL Transmit the RF signals to and from the MA 1200 Add-on

ports on the MA 1200 rear panel: DL to DL, UL to UL.
MA 1000/MA 2000 RHU monitoring and configuration

The MA 1000/MA 2000 RHU can be monitored and configured using NMS. See
NMS System Management on page 4-1 for more information on using NMS.
The following are the tabs that an MA 1000/MA 2000 RHU has when viewed in
NMS.

Equipment overview
General tab
100

Equipment overview
Advanced tab
101

Equipment overview
Adjustments tab
102

Equipment overview
RHU Alarms tab
103
MA 1200 Add-on
Overview
The MA 1200 Add-on module is a high power module that supports the PCS1900
band. It is designed to be integrated with a host MA 1000 or MA 2000 RHU and
MRC. The MA 1000 or 2000 provides the following functionality for both units:
Optical interface to the BU

RF interface to the antennas

Equipment overview
MA 1200 front panel

The RHU 1200 front panel contains the power connection and status LEDs. (The
RS232 connector is reserved for Enterprise Access service personnel.)
215
LED Description
RUN When blinking, indicates that the RHU is in normal operating

mode.
PWR Power on.
MA 1200 rear panel

The RHU 1200 rear panel contains the connections to the RHU 1000 and RHU 2000.
216
Add-on Control Transmits the control signals between the MA 1200 module
and the RHU 1000 or RHU 2000 modules.
From – receives control signals from the RHU 1000/RHU

2000. Connected to the RHU 1000/RHU 2000 Add-on
Control connector.
DL, UL Transmit the RF signals to and from the MA 1200 Add-on

ports on the MA 1000/MA 2000 rear panel: DL to DL, UL to
UL.
High RF service output port connected to the RHU 1000 rear-panel

High port or to combiner/splitter to be combined with other
services supported by the MA 2000 system.

Equipment overview
Connecting to an MA 1000 or MA 2000

The MA 1200 is integrated to an MA 1000 or MA 2000 through a simple external
cable connection between corresponding ports.
MA 1200 monitoring and configuration

The MA 1200 Add-on can be monitored and configured using NMS. See NMS
System Management on page 4-1 for more information on using NMS. The following
are the tabs that an MA 1200 Add-on has when viewed in NMS.
General tab
104

Equipment overview
Advanced tab
105

Equipment overview
Adjustments tab
106

Equipment overview
RHU Alarms tab
107
WMTS RHU
Overview
The WMTS RHU enables ApexPro Dual Band CH WMTS telemetry on the

Equipment overview
WMTS RHU front and rear panels
RHU front panel

The RHU front panel contains the fiber optic connections to the BU, four coaxial
connections to the antennas (and SMU), power connections and status indicators.
NOTE
The RS232 service connector is for the use of service personnel.
229
WMTS RHU Front Panel Indicators
LED Description
COMM Internal communication Ok
WMTS rear panel
275
WMTS RHU Rear Panel
Add-on control N/A
External Filter 1, External To be used with external filtration if required. Refer to design
Filter 2 documents.
WMTS RHU monitoring and configuration
The WMTS RHU can be monitored and configured using NMS. See NMS System
Management on page 4-1 for more information on using NMS. The following are the
tabs that an WMTS RHU has when viewed in NMS.

Equipment overview
General tab
108

Equipment overview
Advanced tab
109

Equipment overview
Adjustments tab
110

Equipment overview
RHU Alarms tab
111

Equipment overview
SHUs
Overview
Switching Hub Units provide a single point connection to up to four APs and
distributes the signals over up to four antennas. This unit is installed in the
communication closet at each remote location.
The SHU hub consists of the following functional modules:
Software controlled RF switching – provides interface to the APs and determines

(according to the user configuration) the antenna outputs to which each of the
APs will be routed.
Tx/Rx amplifier and filter – filters and amplifies the WMTS signals in both
downlink and uplink.
Control and communication – provides the access to remote SNMP monitoring
and configuration options.
Remote
Management
Control and Communication GE

Wideband
Antennas
AP 1 TX/RX Amp
and Filter
SW Switched
AP 2 RF Matrix TX/RX Amp
and Filter
AP 3 TX/RX Amp
and Filter
AP 4 TX/RX Amp
and Filter
SHU
276

Equipment overview
AP to antenna distribution patterns

The SHU provides a number of AP to antenna distribution patterns that optimize
coverage for each remote location. The distribution varies according to the number of
connected APs and the user configuration. For example, if a single AP is connected,
its signal is distributed over four antennas, whereas if two APs are connected, the user
may choose the optimal distribution pattern for the specific remote location.
The configuration is selected via a remote Web connection.
It is required to connect the APs to specific ports, according to the number of

connected APs: for example a single AP is connected to Port-1 and the signal is
distributed over four antenna ports, while two APs are connected to Ports 1 and 2 and
a number of antenna distribution configurations to choose from are available.
Following are the available configurations. Note that several antenna distribution
options are available for a two AP configuration.
Single AP Configuration
Connect the AP to Port-1. The signal is distributed over all connected antennas.
277
Two AP Configuration
Connect the AP to ports 2 and 3. Choose the antenna distribution configuration that
provides optimum coverage for the remote site.

Equipment overview
In the following configuration, AP2 signals are distributed over antennas connected
to ports 1 and 2, while AP3 signals are distributed over antennas 3 and 4.
277
to ports 2, 3 and 4, while AP3 signals are distributed over antenna 1.
279

Equipment overview
280
281

Equipment overview
282
Three AP Configuration
Connect the APs to ports 1, 2 and 3. The signals are distributed as follows:
AP1 to Antenna 1
AP2 to Antenna 2
AP3 to Antenna 3 and 4
283

Equipment overview
Four AP Configuration
Connect the APs to ports 1, 2, 3 and 4. The signals are distributed as follows:
AP1 to Antenna 1
AP2 to Antenna 2
AP3 to Antenna 3
AP4 to Antenna 4
284
WMTS-SHU-4
Overview
WMTS-SHU-4 provides a remotely manageable, secure, single point connection for
ApexPro FH APs operating in the 608-614 MHz band.
In this type of implementation, passive broadband antennas provide signals coverage

while the APs are used only to provide capacity. By de-coupling “coverage” from
“capacity”, WMTS-SHU-4 AP hub enables clustering the active APs in the telecom
closets, providing a more secure and cost effective infrastructure.
To further optimize site coverage, the AP switching hub can be programmed by two
direct signals from the attached APs to selected antennas.
Features
Frequency range: 608 to 614 MHz band
Single-band, bidirectional half-duplex operation switched for Rx or Tx
Supports up to four ApexPro FH APs
Provides connections to four EA wideband antennas
Remote SNMP management through direct LAN connection
Eight user defined (via GUI) distribution configurations for optimal site coverage
Scalable and future-safe – more APs can be connected as needed

Equipment overview
WMTS-SHU-4 front and rear panels
WMTS-SHU-4 front panel

The front panel contains the antenna, local management port, and power connections.
Two LEDs provide power and general indication of the unit status.
285
Front panel ports Description
Antenna ports Four N-type female antenna connections
RS-232 RS232 connection to local configuration and management
DC Power connection: 20 to 48 VDC (20 Watts max)
Front panel LEDs Description
Status Internal operation and channel operation status:
Green blinking – unit ok
Off – fault detected in unit
Red blinking – failure in an AP, channel or antenna
PWR Power connection indication
WMTS-SHU-4 rear panel

The rear panel contains the ApexPro FH AP connections, Ethernet connection for
remote management and LED indicators per AP connection.

Equipment overview
286
Rear panel ports Description
WMTS-SHU-4 ApexPro FH Connection to up four ApexPro FH APs, where an LED

APs indicator is associated with each port
NOTE
It is required to connect the APs to specific ports
according to the number of connected units. For
example, a single AP is connected to port-1, two APs are
connected to port-1 and port-2, etc. Only one AP can be
attached to each AP port. However, fewer than 4 APs
may be attached to the WMTS-SHU-4.
Ethernet Connection to the network for remote Web management via a

standard Web browser
From Add On Control Not used
The rear panel LEDs indicate status or connection point of corresponding ApexPro
FH AP. Indication changes according to channel configuration status.
Rear panel LEDs Description
AP1 ACT- AP4 ACT Blinking green - Functional AP detected at this port
Red - Missing or faulty AP at this port
WMTS-SHU-4 monitoring and configuration
Setting the IP address

To be able to assign IP addresses to the WMTS-SHU-4 units, Lantronix
DeviceInstaller v4.1.0.3 or higher and Microsoft .Net Framework must be installed on
a PC/laptop. These are provided on a CD that is shipped with the WMTS-SHU-4 unit.
NOTE
The WMTS-SHU-4 units come shipped from the factory with a static IP address
(192.168.1.1/16). It is necessary to set an IP address assigned by the ND&I team.
1. On the PC/laptop, select Start > Connect To > Show all connections to open the
Network Connections window.
a. Disable all network connections except for the connection used for the
WMTS-SHU-4.

Equipment overview
b. Set a static IP address and subnet mask to the NIC connection that will be
used to connect to WMTS-SHU-4 unit. The IP address assigned to the PC/
laptop should be on the same subnet as the default IP address assigned to the
WMTS-SHU-4.
i. Right-click on the network connection and select Properties.
ii. In the General tab, select Internet Protocol (TCP/IP) and click
Properties.
iii. On the General tab, select Use the following IP address.
iv. Type the static IP address and subnet mask (for example, 192.168.1.10/
16).
v. Click Ok.
vi. Click Close.
2. Disable all firewall applications running on the laptop. As an example, on GE

issued laptops:
a. Right-click on the task bar and select Task Manager.
b. Select the Processes tab.
c. Click on Image Name to sort by name.
d. End Process on blackd.exe and blackice.exe.
NOTE
Be sure to end both processes, as one running will restart the other.

Equipment overview
292
3. Connect the WMTS-SHU-4 to the laptop using a crossover cable.
4. Power on the WMTS-SHU-4 unit.
NOTE
If the unit was already powered on, reboot the WMTS-SHU-4.
5. Start the Lantronix DeviceInstaller application on the PC/laptop.
6. Your network connection should appear in the left frame.
293
7. In the toolbar, click Search to perform an auto-discovery action. The currently
connected WMTS-SHU-4 units in the network will be identified and listed in the
right frame.
NOTE
The MAC address of the WMTS-SHU-4 is located on a label on the right

rear side of the unit.
8. Select the WMTS-SHU-4 unit and click the Assign IP icon.

Equipment overview
9. Select Assign a specific IP address and click Next.
10. Type the IP address, Subnet mask, and Default gateway values.
NOTE
The assigned IP address is provided by the GE ND&I team with the site
network design.
NOTE
When assigning an IP address to a WMTS-SHU-4 that is set to DHCP, you

will not be on the same subnet as the device (the WMTS-SHU-4 unit will be
assigned a default IP address of 169.254.xxx.xxx). As a result, you will only
be able to initially set the IP address (the Subnet mask and Default gateway
will be grayed out). In the case, perform the following
Set only the IP address and finish the remaining steps in this section.
Go back to step 8 and repeat the steps. You should now be able to set the
Subnet mask and Default gateway.
11. Click Next.
12. Click Assign to assign the WMTS-SHU-4 unit the defined parameters.
Once the parameters have been assigned, the message Completed Successfully
appears and the Finish button is enabled.
13. Click Finish. The Device Installer main window reappears and the installed unit
will be listed in the window.
14. Repeat the procedure for each WMTS-SHU-4 unit in the network.
15. Once all WMTS-SHU-4 units are set, disconnect the laptop from the WMTS-
SHU-4. Restore the network connections to their initial state and restart the
firewall applications. Reboot GE issued laptops.
Recovering the WMTS-SHU IP address

If the WMTS-SHU unit has already been assigned an IP address, but you are unable
to access the WMTS-SHU at a later time because the IP address was not noted, you
can use Address Resolution Protocol (ARP) method from UNIX and Windows-based
systems to assign a temporary IP address.
To assign a temporary IP address, perform the following steps:
1. Assign a static IP address and subnet mask to the PC/laptop that will be used to
configure the WMTS-SHU.
a. Select Start > Control Panel > Network Connections.
b. Right-click on the network connection and select Properties.
c. In the General tab, select Internet Protocol (TCP/IP) and click Properties.
d. On the General tab, select Use the following IP address.
e. Type the static IP address 192.168.1.1 and subnet mask 255.0.0.0

Equipment overview
NOTE
The IP address assigned to the PC/laptop should be on the same subnet

as the default IP address assigned to the WMTS-SHU-4.
f. Click OK.
g. Click Close.
2. Connect a crossover cable between the PC/laptop and the WMTS-SHU.
3. Cycle the power on the WMTS-SHU.
4. Turn off BlackICE or any other firewall applications.
a. Right-click on the Windows task bar and select Task Manager.
b. Select the Processes tab.
c. Click on Image Name to sort by name.
d. Select blackd.exe and click End Process.
e. When prompted, click Yes.
f. Select blackice.exe and click End Process.
g. When prompted, click Yes.
NOTE
Be sure to end both blackd.exe and blackice.exe processes, as one

running will restart the other.
h. Close the Task Manager window.
5. Create an entry in the PC/laptop ARP table using an IP address that is in the same
subnet as the PC/laptop IP address and the hardware address of the WMTS-SHU.
a. Select Start > Run.
b. Type cmd and click OK.
c. At the prompt, add the MAC address of the WMTS-SHU (found on the label
on the back of the unit next to the ethernet port) by typing
arp -s 192.168.1.2 00-20-4A-xx-xx-xx
where 00-20-4A-xx-xx-xx is the MAC address
NOTE
If you are using a Unix based host, type the following:
arp -s 192.168.1.2 00:20:4a:xx:xx:xx
d. Press Enter.

Equipment overview
296
e. To test that the hardware address of the WMTS-SHU was correctly added to
the arp table as a static entry, type: arp -a and press Enter.
f. If added correctly, the IP address will appear in the table with static in the
type column.
297
6. Open a Telnet connection to port 1 by typing the following in the command
prompt:
telnet 192.168.1.2 1
7. The connection fails quickly, but the unit temporarily changes its IP address to
the one designated in this step.
8. Open a Telnet connection to port 9999, by typing the following in the command
prompt.
telnet 192.168.1.2 9999
9. Press Enter within five seconds to go into Setup Mode. If you wait longer than
five seconds, the unit reboots
10. Type 0 and press Enter to select Server configuration.
11. Enter the new IP address, subnet mask, and gateway (if applicable) for the
WMTS-SHU.
12. Type 9 and press Enter to save and exit Setup Mode. The unit performs a power
reset.
Configuring the SNMP Parameters

Configure the SNMP community and trap destination addresses. See Configure the
WMTS SHU trap destination on page 5-5.

Equipment overview
NOTE
The required communication parameters are pre-set for each WMTS-SHU-4

unit. However, if connecting to the Telnet application in unsuccessful, verify the
serial communication parameter.
Web browser management

Overview
After the unit has been assigned an IP address and connected to the network, it can be
remotely monitored and its configuration modified by opening a direct session from a
standard Web browser application.
The Web browser application can be used to:
Set the unit identification parameters

Modify the AP to antenna distribution pattern according to installation changes
Configure the Tx power and Rx gain for each channel
Monitor the unit
To login to the WMTS-SHU-4 configuration application

1. Run a Web browser application (i.e. Internet Explorer).
2. Type the IP address of the WMTS-SHU-4 unit. (for example, http://

192.168.10.127)
3. To make the required changes, select Field Eng from the User Name dropdown
box and type the default password, engineer or eng, in the password textbox.
NOTE
The password is case sensitive – use lowercase letters. For security reasons,
it is recommended to change the password.
4. Click Login.
Navigating the WMTS-SHU-4 Web browser

After logging in, the WMTS-SHU-4 Web browser main window appears, displaying
the Control window, General tab by default.
287
The main window of the Web browser provides access to three dialogs:

Equipment overview
Control – provides access to unit’s general and identification information, as well

as configuration and monitoring options.
Installation – used for defining WMTS-SHU-4 unit name and location.
Security – enables the authorized user (Field Eng level and higher) to change
passwords for security purposes.
Viewing general information of WMTS-SHU-4 unit

The General tab of the Control window displays the general information on the
currently viewed WMTS-SHU-4 unit. The name and location are defined via the
Installation dialog. The other parameters (Serial Number, MAC Address, revision,
etc.) cannot be modified.
Defining WMTS-SHU-4 unit name and location

Use this dialog to assign the unit an identifiable name and link it to its current
location. The information is displayed in the Control dialog along with other data
specific to the unit.
To define/modify name or location

1. Click the Installation button on the left-hand side of the window. The following
window appears, displaying the IP and MAC address of the currently viewed
WMTS-SHU-4 unit.
288
2. Type the unit name and click Set to update the name. The updated name will
appear in the General tab of the Control window.
3. Type the location of the unit (i.e. building and floor number) and click Set to
update the location. The updated location will appear in the General tab of the
Control window.
Changing the AP configuration

The Advanced button in the Main window is used to reconfigure the WMTS-SHU-4
unit according to changes in the physical connections of the APs.
NOTE
Only the two AP connection configuration provides options for distributing the
signals to various antenna combinations. All other connections (1, 3 and 4 APs)
have a set antenna routing pattern.
Physical connections:

Equipment overview
1 APs: connection to port-1

2 APs: connections to ports 2 and 3
3 APs: connections to ports 1, 2 and 3
4 APs: connections to ports 1, 2, 3 and 4
To change the AP configuration

1. In the Advanced tab of the Control window open the Set Configuration
dropdown list.
2. Click ok the desired configuration.
3. Click Send to upload the new configuration to the WMTS-SHU-4 unit.
Changing the Tx power and Rx gain

WMTS-SHU-4 enables the authorized user (Field Eng level) to adjust the Tx power
and Rx gain for every channel according to the site requirements.
To change the Tx power and Rx gain of a channel

1. Click the Control option and select the Advanced tab. The Tx pout and Rx gain
options are displayed individually for each channel (Antenna port 1...4).
289
2. To change the Tx pout for the relevant channel:
In the Set Tx Pout field, select the desired power: Default = 14dBm.
Click Send. The actual Tx pout is displayed in the adjacent field (Tx Pout).
3. To change the Rx gain for the relevant channel:
In the Set Rx Gain field, select the desired gain value: Default = 12dB.
Click Send. The actual gain is displayed in the adjacent field (Rx Gain).
User levels and changing password

The Web management application provides supports two user levels, implemented by
the corresponding passwords. It is recommended to change these passwords for
security reasons. This section describes the options available to the user levels, and
how to change the passwords.
User levels:

Equipment overview
Field Eng level (default password = eng): user is authorized to make

configuration and password changes.
Operator level (default password = oper): user can view the displayed
information. Used for monitoring only.
To change the password

1. Click the Security option.
2. Type currently used password of the user to be changed in the Old Password
field.
3. Select corresponding User Name.
4. Type new password.
5. Re-type the new password in the Verify Password field.
6. Click Apply.
Monitoring alarms and disabling unused antenna ports

WMTS-SHU-4 provides the following alarms, which may be viewed by clicking the
Alarms tab in the Control window.
Antenna sense – senses connected antennas. This option can be disabled for
antennas that are not connected
AP sense – senses the connection of configured APs
Amplification – internal channel operation status
NOTE
It is recommended to disable unused antenna ports so that irrelevant antenna

sense alarms will not be displayed.
290
Disable an antenna
To disable an antenna
In the Antenna area, select Disable for each port where an antenna is not connected.

Equipment overview
Monitoring function Description
Antenna connection status Antenna Sense for the corresponding channel, where:
Green – antenna connection detected

Red – antenna not detected
Grey – antenna is set to Disable
AP status Green – AP detected

Red – AP not detected at a port designated for an AP
connection according to the configuration
Grey – configuration does not require an AP at that port
AMP status Status for the corresponding channel:
Green – channel Ok
Red – channel failure
BUs
Overview
The BUs perform RF to optical conversion of the signal on the communication closet/
head-end side. Each can support up to two services (provided by the same operator).
Two models of Enterprise Access BUs are available: 4-port unit supporting four
RHUs, and 8-port unit supporting up to eight RHUs.
The BU (and all the corresponding remote units) may be remotely monitored and
managed via the NMS.
RF ports on the rear panel provide an interface to the RIU or RIM (through
connection to RIU or passive interface), while optic ports on the front panel provide
an interface to the RHUs (remote units).
BU front and rear panels

BU front panel
The front panel contains the optical connections and indicators. The BU is available
in two configurations: 4-port and 8-port BUs. The 8-port BU consists of two 4-port
elements, where each 4-port element has a dedicated set of indicators (PWR, LSR
and Link 1 to Link 4 or Link 5 to Link 8).
TO TO TO TO TO TO TO TO
RS-232
FROM FROM FROM FROM FROM FROM FROM FROM

PWR LSR PWR LSR
LINK 1 LINK 2 LINK 3 LINK 4 LINK 1 LINK 2 LINK 3 LINK 4

Base Unit – 8Links
230
TO TO TO TO
RS-232
FROM FROM FROM FROM

PWR LSR
LINK 1 LINK 2 LINK 3 LINK 4

Base Unit – 4Links

Equipment overview
231
LED Description
PWR Power input detected for the corresponding unit
LSR Laser
ON — laser circuitry for the corresponding element (group of

four ports) is functioning correctly
Link 1-4, 5-8 ON — the optical link to/from the connected remote
functions within the specification in both directions
Blinking — optical power from remote is lower than expected

by at least 2 dB
BU rear panel
The BU rear panel contains the RF, Alarms, NMS and power connections. Note that
there are two uplink and two downlink RF connections. Each individual uplink and
downlink connection corresponds to a 4-port BU element. For a 4-port BU, one
uplink and one downlink port is connected; for an 8-port BU, two uplink and two
downlink ports are connected.
For systems that include 430 controllers, the RS 485 port is connected to the 410/430
controller to enable remote monitoring and management of the BU from a central
location.
232
Uplink output Uplink connectors to be connected to RIU or RIM
Downlink input Downlink connectors to be connected to RIU or RIM
COM Port RS485 Connection to 410/430 controller
PWR Power connection
Alarms Dry-contact connections to BTS/BDA (normally closed).

Relevant only for system without 410/430 controllers
BU monitoring and configuration

The BU can be monitored and configured using NMS. See NMS System
tabs that a BU has when viewed in NMS.

Equipment overview
General tab
112

Equipment overview
Advanced tab
113

Equipment overview
OPTM Alarms tab
114
RIUs
Overview
Enterprise Access intelligent Radio Interface Units (RIUs) provide a remotely
manageable interface between Enterprise Access BUs and BTS/BDA/Repeaters RF
signal sources. The signal can be monitored and controlled, providing a constant
conditioned RF signal to Enterprise Access indoor coverage systems.
Remote management functions, which includes AGC (Automatic Gain Control)

configuration, enable service operators to control the RF signals and to quickly source
faults, minimizing downtime.
RIU devices are designed to complement Enterprise Access indoor coverage and
signal distribution systems and provide effective, flexible solutions for a range of
installations. RIU products provide bidirectional RF signal transfer between the BTS/
BDA and the Enterprise Access BUs.
The RIU is an operator dedicated unit that interfaces to up to three BTS sources and
automatically adjusts the signal output according to changing environmental

Equipment overview
conditions in order to provide optimal coverage for the site. The RIU is remotely
monitored and managed.
Each RIU can support up to three BTS Conditioner (BTSC) sub-modules or three
BDA Conditioner (BDAC) sub-modules, or some combination, where each sub-
module provides an interface to a BTS or BDA of the same type of service.
Each RIU can be connected to four 8-port BUs (rear panel connections) or to eight 4-
port BUs.
Additional BUs can be supported by using splitters and combiners connected to the
front panel Expansion connectors.
The following figure shows an RIU with three BTSC sub-modules.
240
NOTE
All rear connections are via RG223 coaxial cables with 1/2” N-type male
connectors.
NOTE
In order to operate properly, an ADJUSTMENT process is required in the field

prior to a carrier going live.
Any unused input and output connectors MUST be terminated with 50 ohm
terminators. Otherwise, the ADJUSMENT procedure results may be affected.
The following figure shows an installation in which RIU provides an interface to

three BTS/BDA services. Remote management is available through connections to
NMS consisting of 410/430 controllers and NMS software. RIU supports up to four
8-port BUs. The number of BUs can be doubled using an external 8-way splitter.

Equipment overview
242
RIU products highlights

Supported BTS/BDA services:
RIU - Interface to up to three BTS/BDA services - module dependent
Supported BUs
RIU - up to four 8-port BUs (or eight 4-port BUs), where the number of
supported BUs can be doubled using a special splitter
Automatic conditioning of BTS/BDA signals
Remote setup, adjustments and monitoring through NMS system connections
Monitoring right up to the on-site carrier’s equipment
Programmable Noise Level reduction parameter
Configurable AGC
Allows monitoring of receive and transmit signals from the carrier’s BTS/BDA
equipment
Simplex and duplex interface to BTS/BDA
Intuitive management GUI
A range of products to meet various installation topologies
Simple installation and configuration procedure
Local monitoring is provided through front panel LEDs and a local RS232 connection
to the MCT GUI application. Remote configuration, management and monitoring is
available through connections to a 410/430 controller.
RIU front and rear panels

RIU front panel
The RIU front panel contains the indicators and expansion connectors for the
connection of additional BUs.
The RIU front panel contains the LED indicators. In addition, the RIU front panel
provides an optional connection for an interface to additional BUs and an RS232
service connection. The following figure shows the front panel and the location of
each module.

Equipment overview
NOTE
The UL and DL SMA front panel connections, between the modules, are not
shown for clarity purposes.
P.S. Unit BTS Conditioner BTS Conditioner BTS Conditioner
RUN RUN RUN
PWR DL OVERLOAD DL OVERLOAD DL OVERLOAD
DL LOW SIGNAL DL LOW SIGNAL DL LOW SIGNAL Radio Interface Unit
EXPANSION
RS-232
1 2 3
D/L D/L D/L D/L DOWNLINK
U/L U/L U/L U/L UPLINK
1 2 3
245
LED Description
P.S UNIT PWR ON — input signal is at the required level
RUN Flashing — CPU is running and software loaded
Green Flashing — Corresponding BTSC/BDAC module is

operational
RF OVERLOAD Continuous Red — RF switch is disconnected to protect the

system. This may be due to:
Input power exceeds the allowed range

Unpredicted power rise for which the attenuation
response was insufficient to compensate and reduce
the power to the required level
Software problem was detected
Flashing — When the BTSC DL output power is more than
3dB of the calibrated value (allowed range)
RF OFF Continuous Red — if the BTSC DL power is at least 15 dB

lower than the calibrated BTSC max power level. This
condition also triggers an event.
RIU front panel connections
EXPANSION Connection to an 8-way splitter for interface to additional

BUs. Connection for up to four 8-port BUs is provided on the
rear panel.
RS232 Service connection. Only for service personnel.
RIU rear panel

The rear panel provides all the connections on the BTS/BDA side and on the BU side
as well as connections to the 410/430 controller and the power connection. Two types
of BTS/BDA side connections are available for each BTS/BDA conditioner: simplex
and duplex.

Equipment overview
The RIU rear panel contains the RF, control and power connections. The BTS/BDA
side connections correspond to the number of installed modules. The following figure
shows an example of an RIU with three installed modules, providing connections to
three BTS/BDA systems.
246
RIU rear panel connectors
UPLINK/DOWNLINK BU side connections. Each pair of UL/DL connections (i.e.,

Uplink 1 and Downlink 1) connects to the corresponding
RF connections on a BU module.
NOTE
An 8-port BU consists of two modules and therefore
would require two pairs of connections.
DL UL DUP BTS/BDA side connections. Each panel provides both

simplex (UL/DL) and duplex (DUP) connections to the
corresponding BTS/BDA system.
COM Connections to 410/430 controller rear panel RS485

connector (either port 1 or 5 on the controller).
All installed BTSC/BDAC modules communicate through a

single COM port but are displayed at the monitoring station
as separate modules.
POWER DC power connection: 20 to 48 VDC
Mounting
RIU is designed for 19” rack-mount applications. When installed, the RIU front panel
is flush with the front of the rack.
Powering
The RIU is powered by a 48 VDC power, which is supplied through a power
connection to the rear panel.

Equipment overview
RF signal connections
The RF signal connections between the BTS/BDA and corresponding RIUs are
supported through N-type female connectors on the RIU rear panels.
Control signal connections

To be remotely controlled, the RIU must be connected to a 410/430 controller. The
connection is implemented through an RJ45 RS485 CAT5 cable connection on the
RIU rear panels.
RIU monitoring and configuration

The RIU can be monitored and configured using NMS. See NMS System
tabs that an RIU has when viewed in NMS.
General tab
115

Equipment overview
Advanced tab
116

Equipment overview
Adjustments tab
117

Equipment overview
Alarms tab
118
Fault detection
The RIU provides the following types of fault detection:
Front panel LEDs whose status provides fault indication

Local GUI monitoring and remote GUI monitoring through the NMS system
RIM Main
Overview
The Enterprise Access RIM Main controls the signal received from the BUs and
forwards it to the 1:16 RIM Expansion, where the RIM Expansion interfaces to the
ApexPro CH receiver sub-systems. The RIM Main supports only UL service
distribution.
NOTE
A RIM 1400 is required to enable the 1395-1400 MHz band.

Equipment overview
Each RIM Main supports inputs from up to four 8-port BUs (or up to eight 4-port
BUs) and outputs to two 1:16 concentrators.
Enterprise Access RIM Main can be remotely managed and controlled through 430
connections.
The following figure shows the RIM back panel.
233
RIM Main front and rear panels

RIM Main front panel
The RIM Main front panel contains the LED indicators and RS232 connection for
service personnel. The following figure shows the front panel. The indicators are
described in the table.
234
RIM Main front panel indicators
LED Description
PWR ON — power input is at the required level
RUN Unit processor is running
RIM Main rear panel

The rear panel provides the connections to:
Up to four 8-port BUs, or up to eight 4-port BUs

Two 1:16 RIM Expansions
430 controller
Filter option
Power connections
The following figure shows the rear panel connections.

Equipment overview
1 2 3 4 5 6 7 8 OUTPUT INPUT POWER INPUT COM L BAND INTERFACE

20-48V DC LINK CONTROL
EXT TO
L BAND FILTER CONCEN
BASE UNIT UPLINK INTERFACE
INTERFACE
235
Enterprise Access RIM rear panel connections
BASE UNIT UPLINK Uplink connectors to BUs:

INTERFACE
one connection for every 4-port (OPTM) group on a BU
two connections for every 8-port BU
L-BAND INPUT AND To and From RF connection to RIM 1400 (if present)
OUTPUT
L-BAND INTERFACE Communication connection to RIM 1400 (if present)

CONTROL
EXT FILTER Enables connection to an external filter to counter

interference from TV channels where this is relevant
TO CONCENTRATOR Connections to two 1:16 RIM Expansions
COM PORT RS485 Connection to Enterprise Access 430 controller
PWR Power connection
RIM Main monitoring and configuration

The RIM Main can be monitored and configured using NMS. See NMS System
tabs that an RIM Main has when viewed in NMS.

Equipment overview
General tab
119

Equipment overview
Advanced tab
120

Equipment overview
Adjustments tab
121

Equipment overview
Alarms tab
122
RIM 1400
Overview
The Enterprise Access RIM 1400 is used in conjunction with the RIM Main to enable
the use of the 1395-1400 MHz WMTS band. The RIM 1400 down-converts the 1395-
1400 MHz band to 563-568 MHz (1395.025 MHz is down-converted to 567.975
MHz, 1399.975 MHz is down-converted to 563.025MHz, etc.). The RIM 1400
supports only UL service distribution.
When RIM 1400s are utilized, one is required per RIM Main. Additionally, the RIM
1400 units in a system are interconnected.

Equipment overview
NOTE
A RIM 1400 must be powered up for 48 hours prior to it functioning as a Master

to ensure frequency stabilization. If a RIM 1400 has been previously running for
more than 48 hours, and powered off for less than 10 hours, the RIM 1400 has
maintained frequency stabilization and can function as master if desired.
Frequency stabilization is not required for a RIM 1400 to operate in slave mode.
Therefore, a RIM 1400 can operate in slave mode immediately upon being
powered up.
RIM 1400 front and rear panels

RIM 1400 front panel
The RIM 1400 front panel contains the LED indicators for service personnel. The
following figure shows the front panel. The indicators are described in the table.
294
RIM 1400 front panel indicators
LED Description
PWR ON — power input is at the required level
RUN Unit processor is running
MASTER – CONFIG Indicates that the unit is currently configured to be the

master.
MASTER – ACTIVE Indicates the unit is currently acting as Master.
RIM 1400 front panel connectors
LO OUTPUT 1963 MHz output for calibration.
RIM 1400 rear panel

The following figure shows the rear panel connections.
295

Equipment overview
Enterprise Access RIM rear panel connections
L-BAND INPUT AND To and From connections to RIM Main

OUTPUT
REF INPUT AND OUTPUT To and From connections to other RIM 1400s
POWER INPUT 20-48 VDC Power connection
L-BAND INTERFACE Communication connection to the RIM Main

CONTROL
RIM 1400 monitoring and configuration

The RIM 1400 can be monitored and configured using NMS. See NMS System
Management on page 4-1.
The following are the tabs that a RIM 1400 has when view in NMS.

Equipment overview
General tab
133b

Equipment overview
Advanced tab
131b

Equipment overview
Synchronization tab
130b

Equipment overview
Alarms tab
132
RIM Expansion
Overview
The 1:16 RIM Expansion is a passive unit. It provides the interface between the RIM
and up to 16 receiver sub-systems. Two RIM Expansions can be connected to each
RIM for a total of 32 connections to receiver sub-systems. The RIM Expansion is a
1U unit designed for a 19” rack mount.

Equipment overview
RIM Expansion front and rear panels

RIM Expansion front panel
The concentrator front panel provides a test connection.
-20 db
TEST
Concentrator Module
237
RIM Expansion rear panel

The concentrator rear panel provides the connections to the RIM and up to 16 receiver
sub-systems.
1 2 3 4 5 6 7 8
TO RECEIVERS FROM RIM

9 10 11 12 13 14 15 16
238
FROM RIM RF input from RIM. Connection to one of the concentrator

connectors on the RIM rear panel.
TO RECEIVER RF output distributed over 16 connectors. Connections to up

to 16 receiver sub-systems.
MA 330
Overview
The MA 330 provides a cost effective solution for extending RF services and control
signals from one main building to other buildings, up to 20 Km away, over fiber optic
connections. Each MA 330 system can distribute services from a single RIU or RIM
Main and control signals from an 430 controller to two remote locations.
The system can support two separate links, where each link is completely
independent of the other:
Each link can support a different (or the same) service

Each link supports one sector - two links are required for two sectors of the same
service
The MA 330 system is based on the following elements:
MA 330 Main — An MA 330 Main unit is installed at the main site, adjacent to
the RIU or RIM Main location. It performs the RF to optic signal conversion at
the RIU or RIM Main and transmits the services together with control signals
from an 430 controller to the remote location(s) where MA 330 Remote units are

Equipment overview
installed. The MA 330 Main unit attaches to an uplink and downlink connection
on the back of the RIU or RIM Main.
MA 330 Remote — An MA 330 Remote is installed at each remote location.
This unit reconverts the signals received over the optic fiber to RF and distributes
the services to the connected BUs. The control signals are distributed to the BUs,
either directly or through an 410 controller, depending on the installation
configuration.
MA 330 Expansion Box — optional unit. A passive RF distribution unit that
interfaces to the MA 330 Remote unit and enables doubling the number of BUs
supported at the remote site.
MA 330 GUI Tool — Intuitive GUI used for setting up, adjusting and monitoring
the MA 330 system.
The following figure shows an MA 330 system supporting two remote links. The
system consists of an MA 330 Main unit (bottom) and two MA 330 Remote units.
257
MA 330 system highlights:

Supported services - 100MHz to 2.2GHz, including licensed services such as
Cellular, PCS, iDEN, SMR, GSM, and UMTS as well as unlicensed services
such as UHF and VHF.
Each MA 330 Main unit can support either one or two remote locations
depending on the model.
Each MA 330 Remote unit can support up to two 8-port, or four 4-port BUs.
MA 330 Expansion Box enables doubling the number of BUs supported by each
MA 330 Remote.
Intuitive GUI enables end-to-end setup, adjustment and monitoring of the
system.
Eliminates the need for a controller at remote sites in which only one BU is
installed.
Easily adaptable to conform to in-building capacity redesign requirements.
Simple installation and configuration procedure.
Uses a single fiber for both uplink and downlink transmission.
System architecture
The MA 330 system provides flexible solutions for various site requirements.

Equipment overview
At the main building, the MA 330 Main interfaces to the RIU and 430 controller. It
converts the RF signal received from the RIU to an optic signal, combines it with the
430 control signals and transmits it, via RS232, over optic fiber to the MA 330
Remote.
At the remote buildings, the MA 330 Remote reconverts the received RF signal to an
optic signal, routes the RF signals to the BUs and the control signals to the controller.
The optic signal is reconverted to RF and transmitted to the connected Base Units to
be distributed over the remote location.
Remote Building 1 shows an installation with two BUs.

NOTE
The configuration applies for the maximum number of BUs that can be
supported by the MA 330 Remote with or without an MA 330 Expansion
Box.
The MA 330 Remote unit forwards the (BTS/BDA) service signals to the BUs
and the control signals from the 430 Master controller at the main site to the 410
Slave controller at the remote site. The BUs are controlled through the 410
controller.
Remote Building 2 shows a special installation consisting of a single BU. The
MA 330 Remote unit forwards both the service and the control signals from the
main building directly to the BUs. Note that an 410 controller is not required in
this type of installation. The BU is controlled through the MA 330 Remote.
258
System operation and capabilities

Commissioning
The MA 330 system can be configured and adjusted according to the specific
installation. The procedure is performed through intuitive GUI run via a local
connection to either the MA 330 Main or corresponding MA 330 Remote unit.

Equipment overview
NOTE
The setup and adjustment procedures are end-to-end, meaning that both MA 330
Main and the MA 330 Remote on the corresponding link can be adjusted by
connecting to either unit.
Fault detection and alarm reporting

The MA 330 units provides the following types of fault detection:
Front Panel LED.

Dry-contact auxiliary - MA 330 Main only. Two normally closed connections
used for reporting to an external alarm system when the optic signal level is not
within the required range.
GUI monitoring on each link, through a local connection to either the MA 330
Main or MA 330 Remote unit of the corresponding link.
RF signal connections
MA 330 Main - The RF signal connections between the MA 330 Main and the RIU or
RIM Main are supported through N-type female connectors mounted on the MA 330
Main rear panel: one connector for each forward path coaxial cable and one for each
reverse path coaxial cable (two connectors for one link, four connectors for two
links).
MA 330 Remote - The RF signal connections between the MA 330 Remote and the
BUs are supported through four pairs of N-type female connectors mounted on the
MA 330 Main rear panel. One connector is used for connecting the forward path
coaxial cable and one connector for connecting the reverse path coaxial cable. An
additional pair of N-type connectors is used for the (optional) connections of an MA
330 Expansion Box.
Optical signal connections

MA 330 Main - one or two optical connections on the front panel, corresponding
to the number of links supported by the MA 330 model
MA 330 Remote signal optical link on the front panel
Control signal connections

The MA 330 Main connects to the 430 controller through RJ45 COM connectors on
the rear panel (one connector per link) and routes the controller signals to the remote
locations.
Optical signal level adjustment

The MA 330 Main and remote units are equipped with digital attenuators for
adjusting the forward and reverse optic signal level. The attenuators are adjusted
through the GUI.

Equipment overview
Powering
The MA 330 is powered by a 48 VDC power which is supplied through a standard
power connection to the rear panel.
Mounting
The MA 330 front panel is specifically designed for 19” rack-mount installations.
When installed, the MA 330 front panel is flush with the front of the rack.
MA 330 Main unit description

The MA 330 Main is installed at the main site. It is available in two models:
Single link supports a single remote location

Dual link supports two remote locations
The following figure shows the MA 330 Main two links model.
259
Primary functions
The MA 330 Main unit performs the following main functions:
Interfaces to the service signal source (BTS) through either RIU or passive
interface setup configuration
Interfaces to the 410/430 controller in the main building
Performs RF to optic (and vice versa) signal conversion at the main building
Transmits the service and control signals over optic fiber to the remote
location(s)
Enables gain adjustment on the downlink and on the uplink
MA 330 Main dry-contact alarms

The Alarms connector on the MA 330 Main rear panel provides two dry-contact
connections. These enable monitoring the optical level of each remote link and
reporting to an external alarm system when the optic link signal is not within range.
The connections are normally closed.

Equipment overview
Alarms connector
Pin Number Description
4,5 Link-1: Closed — Ok, Open — fault
16, 17 Link-2: Closed — Ok, Open — fault
MA 330 Main front and rear panels

330 Main front panel
The MA 330 Main front panel contains the optical connections, RS232 connection to
GUI and the LED indicators. The following figures show the front panel for both
single link and dual link models of the MA 330 Main.
The ports are described in the following tables.
LINK 1
PWR LSR RUN LOCAL RX REMOTE RX COM

LINK LINK RS-232
Main Unit – 1Link
260
LINK 1 LINK 2
PWR LSR RUN LOCAL RX REMOTE RX COM PWR LSR RUN LOCAL RX REMOTE RX COM
LINK LINK RS-232 LINK LINK
Main Unit – 2Links
261
Port Description
Link 1/ Link 2 Fiber optic connection to MA 330 Remotes installed at remote sites.
Each link (1/2) corresponds to a remote location.
RS232 COM port Local RS232 connection to a computer on which the MA 330 GUI
(setup and monitoring application) has been installed.
LED Description
PWR DC power status
ON — Ok
OFF — no power
LSR Laser condition:
ON — normal (laser locked)
OFF — faulty (laser unlocked)

Equipment overview
LED Description
RUN Status of optic adjustment procedure as well as unit processor condition:
Green blinking — normal. Successful adjustment and processor running.
Orange blinking — adjustment failed or not performed
Not blinking (Green, Orange, OFF) — unresponsive unit
Local RX link Optic signal received from the remote:
Green ON — optical signal within range
Green blinking — optical signal out of range
Red — no signal received from the MA 330 Remote
Remote RX Optic signal received at the remote

link
Green ON — optical signal within range
Green blinking — optical signal out of range
Red — no signal received at the remote
OFF — no communication between the local and remote unit
COM Status of link communication:
Green — normal communication
Red — faulty communication
OFF — no communication
MA 330 Main rear panel

The MA 330 Main rear panel contains the connections to the RIU or RIM Main to the
430 controller and power connections. The following figures show the rear panel for
the MA 330 Main single link and MA 330 Main dual link units. A description of the
connections follows.
NOTE
Each COM port supports controller connections to one link: two COM ports are
available in MA 330 Main rear panels supporting two links.
262
263

Equipment overview
Port Description
Uplink RF Output Uplink RF connections to the RIU or RIM Main for the
corresponding remote location.
Downlink RF Input Downlink RF connections to the BTS interface (RIU or

passive) for the corresponding remote location.
Alarms port Dry contact alarms port connections.
COM LINK(s) Connection to 430 rear panel RS232 or RS485 RJ45 ports.
Provides two types of connections:
Connection to remote controller - Master/Slave

topology implementation RS232 connection
Independent controller topology configuration RS485
connection
COM PORT RS485 This port will provide control of the MA 330 system through
connection to the MA 330 Main unit and NMS/MCT
applications.
Power Input Power Input 48VDC
MA 330 Remote unit description

The MA 330 Remote unit is installed at the remote location and interfaces to the BUs
and 410 controller.
264
Primary functions
The MA 330 Remote unit performs the following main functions:
Performs optic to RF (and vice versa) service signal conversion at the remote site
Interfaces to the BU(s) and 410 Slave controller at the remote location
Distributes the RF and control signals to the BUs
Provides AGC of the uplink signal from the BUs adjustable through local
connection from either the Main or Remote units and the MA 330 GUI
MA 330 Remote front and rear panels

MA 330 Remote front panel
The MA 330 Remote front panel contains the optic connection, setup and
configuration RS232 connection and LEDs.

Equipment overview
The following figure show the MA 330 Remote front panel. The ports and the
indicators are described in the following tables.
LINK 1
PWR LSR RUN LOCAL RX REMOTE RX COM

LINK LINK RS-232
Remote Unit
265
Port Description
Link Fiber optic connection to MA 330 Main installed at the main

site.
RS232 COM port Setup and configuration connection. Local RS232

connection to a computer on which the MA 330
Configuration application has been installed.
LED Description
PWR DC power status:
ON — Ok
OFF — no power
LSR Laser condition:
ON — Normal (laser locked)
Off — Faulty (laser unlocked)
RUN Status of optic adjustment procedure as well as unit

processor condition:
Green blinking — normal. Adjustment completed

successfully and processor is running.
Orange blinking — adjustment failed or not performed
Not blinking (either green or orange or off) — processor is

not running properly (unit is not responding)
Local RX Link Optic signal received from the Main:
Green ON — optic signal within range
Blinking — signal out of range

Equipment overview
LED Description
Remote RX Link Optic signal received at the Main:
Green ON — optic signal within range
Blinking — optical signal out of range
Red — no signal received at remote
Off — no communication between the local and remote unit
COM Status of link communication:
Green — communication is normal
Red — faulty communication
OFF — no communication
MA 330 Remote rear panel

The MA 330 Remote rear panel contains the connections to the power, RF (BU and
Expansion Box) and 410/430 controller.
266
WARNING
Be sure to connect BUs only to the Uplink and Downlink
connectors. DO NOT connect BUs to the EXP IN OUT connectors,
since this may cause damage to the BUs.
Port Description
COM Link Communication connection to Slave controller.
Power Power input: 20 - 48 VDC.
SW PRG Software Programming — Service Personnel use this port

(in addition to the RS232 front panel port) to upgrade the
software.
Downlink 1-4 Connection to BU rear panel. Downlink RF Output port.
Uplink 1-4 Connection to BU rear panel. Uplink RF Input port.
EXP IN One of the Expansion Box connections — the other is EXP

OUT.
Connection to Expansion Box rear panel, EXP OUT port.
EXP OUT For Expansion Box connections — the other is EXP IN.
Connection to Expansion Box rear panel, EXP IN port.

Equipment overview
MA 330 Expansion unit description

The MA 330 Expansion Box enables doubling the number of BUs connected to the
MA 330 Remote. It interfaces to the MA 330 Remote.
The MA 330 Expansion Box connections are all located on the rear panel that is
shown below.
267
WARNING
Be sure to connect BUs only to the Uplink and Downlink
connectors. DO NOT connect BUs to the EXP IN OUT connectors,
since this may cause damage to the BUs.
Port Description
EXP OUT Connection to MA 330 Remote rear panel, EXP IN port
EXP IN Connection to MA 330 Remote rear panel, EXP OUT port
Downlink 1-4 Connection to BU rear panel, Downlink RF Input port
Uplink 1-4 Connection to BU rear panel, Uplink RF Output port
Network Management System (NMS)

Overview
The Enterprise Access Network Management System (NMS) is a suite of tools used
to monitor and configure the Enterprise Access system. The NMS consists of the
following tools:
410/430 controller – The controller provides the interface between the MS and
ApexPro CH system elements and the management and control mechanism. Two
controller models are available:
MA 410 – enables management of the connected devices through a local
(RS232) or point-to-point dial-up (DSPN phone lines) connection. It can be
remotely managed through a connection to the Enterprise Access 430
controller.
MA 430 – enables management of all connected elements and all connected
410 controllers and the corresponding elements. Supports SNMP (Simple
Network Management Protocol) over TCP/IP connection.
430 may be managed through the Network Operator Center (NOC) through
Manager of Managers element such as HP OpenView via SNMP.
NMS server software – can be accessed remotely or onsite at the site server. This
is used to monitor and configure the Mobile Services (MS) and ApexPro CH

Equipment overview
telemetry portions of the Enterprise Access infrastructure and presents a nearly

identical GUI as the NMS MCT application.
NMS MCT application – used when connecting a laptop directly to the NMS
controller using a serial cable. This is used to monitor and configure the MS and
APexPro CH telemetry portions of the Enterprise Access infrastructure and
present a nearly identical GUI as the NMS server software.
MA330 GUI application – used when connecting a laptop directly either to the
MA330 main or MA330 remote unit. This is used to monitor and configure the
MA330 main and remote units.
WMTS-SHU-4 Web GUI – used to monitor and configure the ApexPro FH
WMTS-SHU-4 units. This should be accessed from the site server on the IX
network. If the site server is down, this application can be run from a laptop.
Connect the laptop directly to the WMTS-SHU-4 unit using a crossover cable.
Do not put the laptop on the IX network as this could introduce viruses onto the
network.
NMS server software provides the following features and capabilities:
Remote SNMP management from a single location

Client/server management capability over a TCP/IP network with enhanced
monitoring and control capabilities
Intuitive GUI that enables end-to-end fault sourcing from RIU to antennas. The
GUI includes:
System status at a glance through multi-color tree with upward propagation
of fault indications
Graphical view of system elements including LED status displays and
auxiliary connections
Multi-color event monitoring display
RF Connections
NMS 410 and NMS 430 controller description

Overview
The Enterprise Access controllers enable managing and controlling the Enterprise
Access system elements.
Two Enterprise Access controller configurations are provided: Enterprise Access 410
and Enterprise Access 430. The models differ in their remote access capabilities:
Enterprise Access 410 provides point-to-point connectivity implemented via

either direct RS232 connection or via connection to a DSPN phone line.
Enterprise Access 430 provides client/server management capability over a TCP/
IP network with enhanced monitoring and control capabilities (in addition to the
connectivity options provided by Enterprise Access 410). Access from client
stations is provided via a server on which the Enterprise Access NMS Software
package is installed (or any other SNMP management software).
NOTE
The Enterprise Access 430 front panel is differentiated from the Enterprise
Access 410 front panel by the SNMP Agent Card that provides TCP/IP
management capabilities.

Equipment overview
The Enterprise Access 410 and Enterprise Access 430 controllers provide the
interface between the devices to be managed and the management applications. The
RIUs, RIM Mains and BUs are directly connected to the controllers; the RHU and
add-on units are managed through the BUs.
The management applications, MCT and NMS Manager (if acquired), are then used
to connect to each Master controller and perform the relevant configuration,
adjustment, monitoring and management operations.
Both 410 and 430 controllers have the same rear-panel connectors as well as the same
LCD alarm and LED front panel displays. They differ in the type of connections they
provide: 430 provides TCP/IP connection in addition to RS232 and dial-up
connection, while 410 provides only RS232 and dial-up connection.
Controller LCD fault indications

The LCD display corresponds to the Major/Minor LEDs. The display differs in the
Master/Standalone controllers and in the remote controllers. In the Master/Standalone
controller two rows (upper and lower) appear, while in the remote controllers only the
top row appears.
Upper row – shows status of locally connected devices (LCL = local), where
status is indicated by the following messages:
LCL AUX Major (auxiliary faults are always major), or
LCL RHU Major/Minor
NOTE
If both types of problems were identified, the display toggles between the
two messages.
Lower row – shows status of up to 8 remote slaves whose status is indicated by

the following letters:
E — communication Error
N — Normal
m — minor malfunction at the remote site
M — Major malfunction at the remote site
NOTE
A Slave controller only shows the top row and a Master controller shows
both rows.
Following is an example of a display:
272
Where the message in the lower row should be interpreted as follows:
Slave #1 = normal (Ok)

Slave #2 = not configured in the system (_)
Slave #3 = communication error

Equipment overview

Slave #6 = minor malfunction
Slave #8 = major malfunction
Controller front and rear panels

Controller front panel
The front panel contains the RS232 and TCP/IP management connection ports, the
monitoring and status LEDs, and LCD displays.
There are two types of displays on the controller front-panel: LEDs showing
controller status and LCD display providing additional information on any fault
status. The following figures show the 410 and 430 front panels and the tables
describe the LED indicators on both panels.
410 RS232 front panel connector - The 410 controller contains only one front panel
connector – RS232. This connector is used for Slave (410) to Master (430 rear panel)
configuration connections, MCT configuration, adjustments and point-to-point
management.
STATUS LOCAL
410 ALARM MODE
MAJOR MINOR MASTER SLAVE RUN PWR
RS-232
SITE
NMS Controller Unit
269
The figure below shows the 430 front panel and the following tables describe the
LED indicators and connections.
STATUS LOCAL
430 ALARM MODE
MAJOR MINOR MASTER SLAVE RUN PWR
RS-232 Network
SITE
ACT LINK
NMS Controller Unit
270
LED Description
Network Connection For 430 only
Active LED – Blinks during TCP/IP communication.
Link LED - ON as long as a TCP/IP network connection

exists.
PWR ON green - indicates correct power level.
Run ON green - flickers continuously indicating the controller is

initialized and running.

Equipment overview
LED Description
Mode Controller Master or Slave mode
Master green – lit if the controller is installed as a stand-

alone or is configured as a Master.
Slave green – lit if the controller is configured as a Slave.
Failure Indicates whether the alarm is Major or Minor type of

alarms.
430 front panel connectors
RS232 Used for setting up the network parameters (IP address,

community names, etc.) and for MCT (Enterprise Access
configuration tool) connection. The configuration tool is used
for preliminary setup.
Network Ethernet TCP/IP connection to network. Enables remote

management of the 430 controller and all connected
devices. Access provided from client stations via a server on
which the Enterprise Access NMS software package is
installed (or any other SNMP management software).
Controller rear panel

The rear panels of the controllers provide all the connections to the system elements
(BUs, RIMs), dial-up MCT connection, dry-contact auxiliary inputs, auxiliary outputs
(to base station or repeater) and power.
The controller rear panel connections are described below.
NOTE
The rear panels for the Enterprise Access 410 and Enterprise Access 430 are the
same.
NOTE
A single controller can support either Legacy BUs or Enterprise Access BUs and
RIUs — a mix of both is not supported by the same controller. Note that Legacy
and Enterprise Access BUs are connected to different connectors.
RS 485 1 2
RS 485
1 4 1 4
FROM
AUX ALARM EXTERNAL
BUS INTERNAL MODEM PWR
ALARMS OUTPUT MODEM
3 4
- +
5 8 5 8
271

Equipment overview
RS485 Enterprise Access BUs, RIU, and RIM connections. NMS-

RJ45 cables. Connection limitations:
Up to eight Enterprise Access BUs on any of the ports

Up to two RIUs connected only to ports 1 and 5
From BU Four Legacy BU connections using NMS-BU/DB25 cables.
RS232 Eight connections to Slave controllers. Active only in

controllers configured as Master.
Auxiliary Alarms Eight inputs for alarms from auxiliary devices.
Alarm Output BTS/repeater dry-contact alarms. NMS-BTS/DB15-open

cables.
Internal Modem Used for dial-up connection to the controller for the purpose
of MCT configuration and MCT monitoring.
PWR DC power input: 20 to 48VDC, 0.5A max
NMS controller monitoring and configuration

See NMS System Management on page 4-1 for more information on using NMS. The
following are the overall view of the network topology and the tabs that an NMS
controller has when viewed in NMS.
Network topology - overall view 1
127

Equipment overview
Network topology - overall view 2
128

Equipment overview
General tab
123
Auxiliary tab
124

Equipment overview
MA tab
125
Dial Up tab
126

Equipment overview
Slave Controllers Configuration
129
Enterprise Access service software

Service Gateway
The Service Gateway is the server hardware that is provided with the Enterprise
Access system. The Service Gateway hosts the NMS software and the CARESCAPE
Systems Manager software. The Service Gateway resides on the IX Network, and
optionally, also on the RX network.
CARESCAPE Systems Manager

The CARESCAPE Systems Manager software provides remote access to the
Enterprise Access system. In addition, the service software provides a mechanism to
monitor the system for faults and generate an alert to the GE backoffice for critical
system failures. OpenNet Expert software is provided on the same CD, which can be
used to configure the various ApexPro FH components. Information about the
installation and configuration of the service software is described in CARESCAPE
Systems Manager on page 5-1.

Equipment overview

3 Installation

Installation
Equipment required
The following equipment will be needed to install this system.
Software/Tool
Cable stripper and drill or manual stripper
Fiber cable (CAT 5/6) tester
Fiber connector cleaning kit
Spectrum analyzer (minimum 3.0 GHz)
Signal generator
10 ft. N to N cable
Laptop with Enterprise Access Manager software
Serial cable
Digital volt meter
802.11 a/b/g laptop analyzer tool
Performance characteristics
Antenna placement
Each antenna shall be placed to provide adequate coverage in its individual intended
coverage area for all services to which it is attached as follows:
WMTS services
ApexPro dual band CH service

All locations in ApexPro dual band CH coverage areas shall have adequate coverage
from at least two antennas belonging to independent antenna fields as follows:
608-614 MHz WMTS

Antennas designated to support ApexPro 608-614 MHz CH service shall be placed
such that the expected uplink signal power at the antenna port from all ApexPro CH
transmitters in its individual intended coverage area shall be at least -90 dBm.
Antennas designated to support ApexPro CH service in the 608-614 MHz WMTS

band shall be placed such that the expected 99th percentile maximum uplink signal
power at the antenna port from any other 608-614 MHz in-band radiators, including
any other non-ApexPro transmitters, shall be at most -48 dBm.
NOTE
This requirement will usually preclude ApexPro CH coverage in the 608-614

MHz band from coinciding with areas that will also be occupied by Corometrics,
ApexPro FH or most other WMTS devices that output higher power.

Installation
1395-1400 MHz WMTS

Antennas designated to support ApexPro 1395-1400 MHz CH service shall be placed
such that the expected uplink signal power at the antenna port from all CARESCAPE
Telemetry T14 transmitters in its individual intended coverage area shall be at least -
80 dBm.
Antennas designated to support ApexPro CH1400 service in the 1395-1400 MHz

WMTS band shall be placed such that the expected 99th percentile maximum uplink
signal power at the antenna port from any other 1395-1400 MHz in-band radiators,
including any other non-ApexPro transmitters, shall be at most -38 dBm.
ApexPro FH service
All locations in ApexPro FH coverage areas shall have adequate coverage from at
least two antennas belonging to independent antenna fields as follows:
Antennas designated to support ApexPro FH service shall be placed such that the
expected uplink signal power at the antenna port from all ApexPro FH transceivers in
its individual intended coverage area shall be at least -80 dBm.
NOTE
ApexPro FH coverage areas cannot, in general, coincide with areas that will also
be occupied by Corometrics, ApexPro CH or most other WMTS devices that
output higher power.
Cellular/PCS
All locations in cellular/PCS coverage areas shall have adequate coverage from at
least one antenna as follows:
Antennas designated to support cellular/PCS service shall be placed so that the

expected received downlink signal power per carrier at any mobile device in its
individual intended coverage area shall be at least -85 dBm and 6 dBm above the
ambient signal power.
WiFi
All locations in WiFi coverage areas shall have adequate coverage from at least one
antenna. It is suggested that antennas designated to support WiFi service shall be
placed so that the expected received downlink signal power at any mobile device in
its individual intended coverage area shall be at least:
-67dB for 802.11b/g

-67dB for 802.11a VoIP
-75dB for 802.11a data
Safety requirements
All coaxial cabling (both horizontal and jumpers) installed in an air plenum space
shall be specifically rated for plenum use.

Installation
Installation
Antenna installation
Overview
General cable installation procedures

Observe the general cable installation procedures that comply with the building codes
in your area. The building code requires that all cabling be installed above ceiling
level (where applicable). Each length of cable from the risers to each antenna must be
concealed above the ceiling.
The cable must be properly supported and maintained straight using tie-wraps, cable
trays and clamps or hangers every 10 feet (where practical above ceiling level).
Where this is not practical, the following should be observed:
When bending coaxial cables, verify that the bending radius does not exceed the
coaxial specifications.
The minimum bending radius of the supplied ½” coaxial cable should be 7".
Cable that is kinked or has been bent tighter than the bending radius must be
replaced.
Cable runs should be secured to suitably located mechanical structures.
The cables should be supported only from the building structure.
Use coaxial, 50ohm, male-to-male N-type, (6-7dB for 1 GHz, 11dB for 2 GHz)
and attenuation of less than 2dB/100ft at 800 MHz for connecting to RHU ports.
Use coaxial RG223, 50ohm, male-to-male N-type for RF connections from the
BUs to the RIU.
When using the Enterprise Access system in an environment in which other
indoor coverage systems are installed, it is recommended (where possible) that
the antennas are placed at least two meters apart.
Use wideband antennas supporting a range of 600 MHz to 5800 MHz.
Use a VSWR meter (i.e., Site Master or equivalent) for checking coaxial cables,
including the antennas (<2). The VSWR must be measured prior to terminating
the RHUs in the remote communication rooms.
Terminate all unused RHU, RIU, and SHU ports with a 50 ohm load.
General fiber cabling rules

Use only single mode fiber for indoor applications.
Use only 8-degree SC/APC connectors (green color).
Use only fusion splice for connecting two fibers.
Use minimum splicing/connectors to achieve minimum losses on the fibers
(<0.5dB).
Use precaution while installing, bending, or connecting fiber optic cables.
Use an optical power meter and Optical Time-Domain Reflectometry (OTDR)
for checking the fiber optic cables.
Make sure the environment is clean while connecting/splicing fiber optic cables.

Installation
All fiber optic connections should be cleaned prior to attaching to termination

points using a dry cleaning device (i.e., Cletop or equivalent).
Fiber connector protective caps should be installed on all non-connected fibers
and removed just before they are connected.
Verify the fiber optic connections.
Pay special attention while connecting the SC/APC connectors - you must hear
the “click” when the connection is made.
Installation
NOTE
Refer to the antenna mounting instructions that were shipped with the antenna for
installation instructions.
Remote closet installation

Overview
Hardware to support specific services within a surrounding coverage area (e.g., a
building floor or a wing) is housed in remote closets.
The remote closets need to be built by the contractor at the locations indicated by the
rack layout diagram provided by ND&I. Follow the procedures below for more detail
on building the remote closets.
Remote closet rack installation

Although the remote closet equipment can be wall mounted, it is highly
recommended to mount the equipment on a rack to achieve a clean install and cable
management. Verify that the rack height can support all the units to be installed,
where you may also want to consider future expansions.
The components that should be installed in the rack at the remote closet and the space
required for each component are shown in the table below:
Component name Rack space
MA2000 cabinet 8 U (13.97 in.)
RHUs 1 U (shelf)
Access points (APs) 1 U (shelf)
Power supplies 2 U (shelf)
Fiber optic patch panel and splice tray 1 U (shelf)
SHU 1 U (shelf)

Installation
CAUTION
The MA2000 cabinet weighs approximately 77 lbs. It is
recommended that a team of at least 2 installation personnel be
utilized to mount the cabinet.
Alternatively, if an MA2000 cabinet is not used at a particular site, the MA2000 Lite
and the MA1000 and MA1200 RHUs can be wall mounted.
Main closet installation

Overview
The Main closets (a.k.a. head-end closet) need to be built by the contractor at the
location indicated by the rack layout diagram provided by ND&I. Follow the
procedures below for more detail on building the Main closet.
The components that should be installed in the rack at the Main closet and the space
required for each component are shown in the table below:
Component name Rack space
Radio Interface Unit (RIU) 3U
Receiver Interface Module Main (RIM Main) 1U
Receiver Interface Module Expansion (RIM Expansion) 1U
Receiver Interface Module 1400 (RIM 1400) 1U
Base Unit (BU) 1U
Network Management System controllers (NMS controller) 1U
Fiber optic patch panel and splice tray 1U
Power supplies 3U (shelf)
For any field-replaced RIM 1400, determine and record the date of last calibration
from the removable calibration sticker that ships on the device. If the installation is
not within 30 months of the date shown on the manufacturer calibration sticker,
calibrate before installation. See Calibration on page 6-5.
Interconnecting Enterprise Access components

The installation contractor must complete the following interconnections between the
various GE Enterprise Access components. This section also describes the
appropriate power supplies that should be connected to the GE Enterprise Access
components.

Installation
RIU to BU connections
1. Connect each BU to the corresponding RF Uplink and Downlink connectors on
the RIU rear panel using RG223 or similar, 50ohm, male-to-male N-type
connector. Note that one uplink and one downlink RIU rear-panel ports are used
to connect one 4-port BU. Two uplink and two downlink ports are used to
connect an 8-port BU.
2. Connect each BTS/BDA to the corresponding rear panel BTSC/BDAC

connectors. For each BTSC/BDAC connection, both simplex and duplex
connections are available:
For a duplex connection, connect to the BTSC/BDAC DUP port

For a simplex connection, connect to the BTSC/BDAC UL and DL ports
NOTE
This step is performed only after commissioning of the system. The
BTS/BDA is generally connected at a later time when the mobile
service provider installs their equipment.
3. Connect the Power connection on the RIU and BU rear panels.
4. Connect the RS485 port on the RIU rear panel to the NMS controller.
NOTE
Only controller ports RS485 Port-1 and Port-5 can be used to connect the
RIU. BUs can be connected to any of the RS485 ports on the NMS
controller.
5. Terminate all unused RIU and BU ports with a 50 ohm load.

Installation
BTS/BDA simplex BTS/BDA duplex

connections connections
Power
RIU
BU
NMS controller connection
306
RIM Main to BU connections

1. Connect the RIM rear panel Uplink N-type connectors to the BU rear panel
Uplink connector using RG232 or similar, 50 ohm, male-to-male N-type
connector. Note that one uplink RIM rear-panel port is used to connect one 4-port
BU. Two uplink RIM rear panel ports are used to connect an 8-port BU.
2. Connect the Power connection on the RIM and BU rear panels.
3. Terminate all unused RIM Main and BU ports with a 50 ohm load.

Installation
To NMS controller RS485

rear panel connector
Enterprise Access 8-port BU
Enterprise Access RIM
307
RIM Main to RIM 1400 connections

NOTE
The RIM 1400 is only present if the system was designed to support the 1395-
1400 MHz WMTS frequencies. There will be one RIM 1400 for each RIM Main
present. The system will be designed with two to four RIM Mains (each RIM
Main and the corresponding equipment is typically denoted as Field A, Field B,
Field C and Field D).
1. Connect the L-BAND OUTPUT on the RIM Main to the L-BAND INPUT on
the RIM 1400.
2. Connect the L-BAND INPUT on the RIM Main to the L-BAND OUTPUT on
the RIM 1400.

Installation
3. Connect the L-BAND INTERFACE CONTROL on the RIM Main to the L-

BAND INTERFACE CONTROL on the RIM 1400. The L-Band Interface
Control cable is pn 705A009901.
4. The RIM 1400s must be linked together. Connect the REF OUTPUT on the first
RIM 1400 to the REF INPUT on the next RIM 1400.
5. Repeat this connection chain until the last RIM 1400 REF OUTPUT is
connected to the REF INPUT on the first RIM 1400.
316
RIM Main to RIM Expansion connections

1. Connect the RIM Expansion rear panel From RIM port to the RIM Main rear
panel To RIM Expansion port using 75 ohm coaxial cable (RG 59, RG-6, or
similar).
2. If the installation includes two RIM Expansions, connect both RIM Expansions
to the RIM Main.
3. Terminate all unused RIM Expansion ports with a 75 ohm load.

Installation
Enterprise Access RIM Main
Enterprise Access RIM Expansion

308
RIM Expansion to ApexPro CH receiver sub-system connections

1. Connect the RIM Expansion rear panel To Receiver port to either Field A or
Field B port of the ApexPro CH receiver sub-systems (there will be four ports
designated for fields A, B, C, D).
2. Each RIM Main represents a different ApexPro Field (Field A, B, C, and D) and
a total of four RIM Mains can exist in the same system. Each ApexPro CH
receiver sub-system has four 75ohm coaxial connections, one for each of the four
fields. To connect the RIM modules to the ApexPro receiver sub-systems, do the
following:
a. Start with the RIM Main designated as Field A. Find the Rim Expansion
module(s) that is connected the RIM Main. Connect the To Receiver ports
of the RIM Expansion to all of the ApexPro CH receiver sub-systems Field
A connection point.
b. Repeat for the other fields. It is important that each RIM Main is connected
to all ApexPro CH receiver sub-systems (via the RIM Expansion).
NOTE
Systems will have between two and four fields based on design.
c. Terminate all unused RIM Expansion and ApexPro receiver sub-system

ports with a 75 ohm load.
NOTE
During the installation of the GE Enterprise Access system, the connection from
the RIM Expansion units to the ApexPro CH receiver sub-systems may happen at
a later time during the installation. Up to 16 ApexPro CH receiver sub-systems
could be connected to a single RIM Expansion. The ApexPro receiver sub-
systems are connected to the GE Enterprise Access system only after the GE
Enterprise Access system has been commissioned.

Installation
315
BU fiber optic and power connections

NOTE
It is assumed that the patch panel cabinet (SC/APC adaptors) for fiber optic cable
connections is installed in the rack near the BUs.
1. Connect SC/APC jumpers between the corresponding BU and patch panel.
2. Connect the Power connection on the BU rear panel.
Connections to F/O Patch panel
309
802.11a/b/g AP connections
1. Connect the AP to the SMU using a short 50-Ohm cable.
If an SMU is not present, connect the AP directly to the antenna run.
The SMU (or antenna run if no SMU is present) requires an N-type connection.
RHU connections
1. Connect fiber optic cable to splice box and to SC/APC connectors on the RHU.
2. Connect the fiber optic cables from the BU to the RHUs through the patch panel
cabinet.
3. For the downlink, connect the fiber optic cable pigtails from the splice box
coming from the BU port to the corresponding RHU From Base port.

Installation
4. For the uplink, connect the fiber optic cable pigtails from the splice box from the
RHU to the uplink port that connects to the BU UL port.
5. Connect the RHU antenna connector ports to the wideband antennas (coaxial
cable runs) either directly or through the SMU and/or splitter inputs according to
the design provided by the Network Design team.
6. Connect the power to each RHU according to power design document provided
by the Network Design team.
7. Verify that 50 ohm terminators are placed on the unused antenna ports and SMU/
splitter ports.
WMTS-SHU-4 connections
1. Connect the ApexPro FH AP to the WMTS AP ports on the WMTS-SHU-4
using one of the following:
a. If the AP only has one antenna output (i.e., does not have diversity), use a 2
foot 50-Ohm cable SMA to SMA coaxial cable.
b. If the AP has two antenna outputs (i.e., has diversity), use a 1 foot 50-Ohm
SMA to SMA coaxial cable to connect the WMTS AP port on the WMTS-
SHU-4 to a 2:1 SMA combiner. Use a 1 foot 50-Ohm SMA to SMA coaxial
cable to connect each antenna output on the ApexPro FH AP to the SMA 2:1
combiner.
2. Connect the SHU antenna ports to the wideband antennas either directly or
through the SMU according to the design documentation.
3. Connect the power to each WMTS-SHU-4 according to power design

documentation provided.
4. Verify that 50 Ohm terminators are placed on the unused antenna ports, SMU
ports, and AP ports.
NMS connections
1. Connect the Power connection to the NMS controllers (410/430).
2. Connect the RIM Main's rear panel COM port to either the RS485 port-1 or
port-5 of the NMS controller as shown in the illustration below. The RIM Main
cannot be connected to any port other than port-1 or port-5.

Installation
NOTE
430 The RIM can only be connected to port 1 or port 5.
Enterprise Access RIM
310
3. Connect the COM port on the rear panel of every BU to the RS485 ports of the
NMS controller as shown in the illustration below.
311
4. Connect the RIU's rear panel COM port to either the RS485 port-1 or port-5 of
the NMS controller as shown in the illustration below. The RIU cannot be
connected to any port other than port-1 or port-5.
312
5. To connect the NMS Slaves (MA410) to the NMS Master controller (430),
connect the 9-pin RS232 connector on the NMS Slave (410) front panel (RS232
slide-in card) to the RS232 9-pin RJ45 connector in the NMS Master (430) rear
panel using DB9 to RJ45 cables.

Installation
410 Slave
410 Slave
430 Master
313
MA330 connections
The following figure shows the physical connections to the MA 330 Main. The
figures are followed by instructions.
314
MA 330 Main Connections

1. Connections to RIU - using N-type cables connect the uplink and downlink ports
on the 330 Main rear panel to the parallel ports on the RIU panel.
2. Connections to 410/430 controller - connect the COM LI NK 1/2 port on the 330
Main rear panel to any two RS232 ports on the 430 rear panel.

Installation
3. Alarms (optional) connect to an external monitoring system.
4. Power connect to the DC power.
MA 330 Remote connections
WARNING
Be sure to connect BUs only to the MA 330 Remote Uplink and
Downlink connectors. DO NOT connect BUs to the EXP IN OUT
connectors by mistake - this may cause damage to the BUs.
1. BU connections - connect the MA 330 Remote uplink and downlink N-type

coaxial connections to the corresponding uplink and downlink connections on the
BUs.
2. Slave controller connections - connect the MA 330 Remote rear panel COM
Link port to the RS232 port on the 410 Slave front panel.
NMS software
See Installing and configuring NMS system management on page 4-2.

4 NMS System
Management

NMS System Management
Overview
The GUI and many of the features of the NMS application are similar to that of the
MCT application that is described in the Troubleshooting section. See Chapter 7.
Following are the main differences between the two applications:
NMS management application enables simultaneous management of a number of

controller sites over TCP/IP protocol
NMS management can be run as a service
It can be run from any client running JAVA VM
Events can continuously be viewed in real-time. The events can be filtered
according to various user defined criteria such as source, time, etc., and can be
acknowledged or unacknowledged.
The initial configuration procedure differs since the network definitions (IP
address) of each 430 controller must be defined
Refer to Chapter 2 for examples of the NMS tabs for each module. These tabs are the
same, regardless of which NMS application you are using.
NMS MCT client software

The MCT software must be downloaded to the service laptop in order to access the
NMS remotely.
1. Open Internet Explorer and go to http://www.mobileaccess.com/filedownload.
2. Click the here link to download MCT v3.15sp01 or later.
3. Save the .zip file to the local system. Extract the .zip file to run the .exe file.
4. Follow the on screen prompts to complete the installation.
Installing and configuring NMS system management

The installation and setup of the system consists of the following steps: 430 controller
IP address configuration, server setup, client setup and manager setup.
NOTE
Make sure you have install privileges to the server and at least one of the client
computers and acquire the IP Address for the 430 controller and for the server.
430 controllers IP address configuration

In order to be monitored, a static IP address must be assigned to each 430 controller
using a local connection and a terminal emulation application such as HyperTerminal.
Configuring the IP communication parameters

This procedure describes how to set the 430 controllers IP Address parameters.

1. Connect the laptop (or any computer) on which a terminal application (such as
HyperTerminal) is installed, to the 430 controller RS232 front panel connector.
2. Set the communication parameters as follows: 9600 baud rate, 8 data bits, 1 start
bit, 1 stop bit, No parity, No flow control.
3. Reset the controller by removing and reinserting the power connector at the on
the controller rear panel. The terminal application will be initialized.
4. Press any key within 5 seconds in order to access the CLI command prompt.
5. At the password prompt, type the default password ma and change the password
if desired.
6. Respond to the IP Address prompts by entering the IP Address, Subnet mask and
Default Gateway address.
7. Respond to the Community name prompts, make any necessary changes (default
Get = Public, default Set = Private).
8. At the Boot Operation [1:Download, 2:Run] prompt, select Run to reboot the
card and activate the new settings.
CAUTION
Do not select Download, as this will erase the flash.
9. Close HyperTerminal.
10. Connect the controller to the network.
Server setup
The NMS server software should be installed on a computer that meets the following
minimum requirements:
Processor Pentium IV 2.4GHz

Memory 512 MB RAM
Disk 1GB free disk space
Operating System MS Windows 2000 / XP-Pro / 2003
1. Insert the NMS server application CD in the computer/server and start the
installation of the NMS server application software.
a. An install wizard is launched. Use the installation wizard to installation the

NMS server application.
b. Select the check-box to install the NMS server icon on the desktop
c. Click Next on the install wizard until the NMS server installation is
complete
2. Assign the server a static IP address given by the network administrator.
3. Install the Apache HTTP server application onto the server. Follow the steps
below to install the Apache web server.
a. Download application from the Apache site: http://www.apache.org/.

b. On the left side of the screen, under Apache Projects, select HTTP Server.
c. Under Want to try out the Apache HTTP Server?, select download page.
d. Under Apache HTTP Server 2.0.xx is also available, select the option
Win32 Binary (MSI Installer) File. Save the file.
e. Start installing the Apache web server by launching the .msi package. A
install wizard will run through the rest of the installation steps.
f. Click Next on the install wizard (with default installation settings) until the
Apache web server is successfully installed.
g. Perform a quick check to ensure that Apache is properly installed by opening

a web browser on the server and browsing to http://127.0.0.1. A web page
similar to the one shown below is displayed if the web server installation
was successful.
701
h. Launch the MA NMS server application by double clicking on its icon on
the server's desktop.
NOTE
This text window running in the background is the normal status of the
application. Closing it closes the NMS server application.
Client setup
Verify that Java VM is installed on the intended clients. This can be either
downloaded from the Web site http://java.sun.com/ or installed from the supplied CD.
Launching and login to the NMS Manager

Introduction
The Enterprise Access system is controlled from any client by connecting to the
server on which the NMS server application is installed. For the connection to be
implemented, the NMS server application must be launched on the server.

Launching and login to the NMS Manager from a client

The system can be monitored from any client connected to the network on which the
server running the NMS server application.
1. Run a Web Browser (be sure Java VM is installed on the client) and type the IP
Address of the server (i.e., http://192.168.10.65). It typically takes about 30
seconds to download the application to the client.
2. In the User Name drop-box, select the access level and type the corresponding
Password. Three access levels with default passwords are provided. (The
password can be changed from the Security menu.) The login levels are:
Operator (default password oper) – provides read-only options of all the

fields
Field Engineer (default password eng) – enables full customer read-write
control in all fields.
Technical Support – access restricted to GE technical support.
3. Click Connect. A connection to the NMS Manager application on the server will
be established.
NMS Manager main window

The NMS Manager main window is divided into two panes: the left pane on which
the system Network Topology is displayed, and the right pane corresponding to a
selected device or option.
Once the initial setup has been performed, the status of the monitored devices is then
indicated by the colors of the tree branches, where the status of lower levels is
reflected in the higher tree levels.
Detailed information can then be viewed by clicking on individual elements on the

tree, invoking a dialog specific to the element.
NOTE
For optimal response time, it is recommended to open the minimum required

windows and close windows that are no longer necessary. A window that is not
edited for five minutes will be automatically closed. A window acceleration
mechanism accelerates the responses when adjustments are made by temporarily
refreshing only the active window (events, Topology View, Device View, etc.,
will not be updated).

706B
Topology configuration
Overview
In order to control and monitor the Enterprise Access system, the system topology
must first be configured in the NMS Manager network topology. The procedure
consists of the following steps:
1. Configuring system nodes. These are logical definitions used to visually organize
the site locations.
2. Configuring the controller connection parameters and slaves (if relevant).

Defining the static IP Address assigned to each 430 controller and the
community parameters. This enables the system to connect to each controller
site. Additional identification parameters may be defined as well.
If this is a Master controller, then the slaves are also assigned in the same dialog.
3. Controller configuration. For each defined controller, define its topology

(Master/Standalone or Slave), type of connected devices (Enterprise Access or
Legacy), Auxiliary Inputs, and other information.
4. For Enterprise Access devices – set the BaseLine.
5. For Legacy Devices – configure the devices.
Defining nodes
The node definitions are optional. They are used only to organize the visual display so
the location of the sites can be easily identified. In the example in the following
figure, three sites were created: Red Zone, Green Zone and Blue Zone. Any number
of branches (nodes) may be added to each node.

NOTE
The 430 controller information (domains) may then be defined anywhere in the
the Network Topology tree according to the following section.
To add nodes:
1. Under the Network Topology section, select the zone level and click Add.
2. In the Select element type dropdown menu, select Node and click Ok.
702
3. Assign the node a Name describing the specific node.
4. All other parameters are optional and their description is as follows:
Location – name of the location where the node is found.

Contact – contact person and/or number
URL – displays an image when the node is selected.
Remark - type any additional information

Files stored in the

HTTP server.
703
NOTE
You may add any number of additional sub-nodes in the tree, creating the
desired hierarchy.
5. Define the 430 controller network information (Domain) and configuration

according to the following section.
Defining domains
Every 430 controller must be configured in the topology tree according to its pre-
assigned static IP Address and community parameters. The definitions may be in any
level in the Topology Tree.
To define the 430 controller network parameters (Domain):
1. Select the node in the Network Topology tree, according to the physical location
or logical association of the controller to be added and click Add.
2. Select the Domain option and click Ok.
3. Define the controller identification and contact information: Name, Location and
Contact.

704
4. If an image needs to be associated with the controller, assign a URL.
5. Define the controller IP Address.
6. If needed, assign the controller a GET Community (default = public) and SET
Community (default = private).
7. Under Slave Mask, check the ports to which Slave controllers are connected.
8. Set the Rate to Slow for ports to which Slave controllers connected through MA
300 systems (remote locations). Otherwise, the default data rate is set to Normal.
9. To stop the controller devices from being polled continuously, uncheck the
Continuously Poll Domain option (default = enabled).
10. Click Ok.
11. Repeat the procedure for every 430 controller in the network.
12. The new domain and corresponding slave controllers will be displayed in the
Network Topology as illustrated in the following example of a Master controller
and four slaves.
705


5 CARESCAPE
Systems Manager

Overview
The CARESCAPE Systems Manager Software CD is provided with the Enterprise
Access systems. The service software is meant to be a complimentary tool to the
NMS software. The service software provides the following functions:

provides remote service access to the Enterprise Access system through
InSite ExC
monitors the system and generates alerts for critical component faults or
failures that comprise the system
OpenNet Expert software
configures the ApexPro FH system components (e.g. access points, device
master, transceivers, etc.)
Hardware requirements
The NMS software and the service software are to be installed on the same server
hardware. The software should be installed on a computer that meets the following
requirements:
Processor Pentium IV 2.4GHz

Memory 512 MB RAM
Disk 1GB free disk space
Operating System MS Windows 2000 / XP-Pro / 2003
Installation
Pre-installation
1. Connect the server to a keyboard, mouse and display.
NOTE
The server does not need to be rack-mounted at this time.
2. Power on the server and log in.
3. Assign an IP address to the server on the IX network and connect the configured
interface on the server to the IX network.
NOTE
IP addresses will have to be provided or approved by the GE Network

Design and Implementation (ND&I) team to ensure there are no IP address
conflicts.

Service software installation

CARESCAPE Systems Manager installation
1. Insert the CARESCAPE Systems Manager CD into the optical media drive of
the server.
2. Open Windows Explorer and navigate to the optical media drive.
3. To install the CARESCAPE Systems Manager software, double-click on

GEHC_EA_Installer.exe.
4. At the Welcome screen, click Next.
5. At the License Agreement screen, read the agreement and click I Agree.
6. The installation will complete automatically. When prompted to reboot, click

Yes.
7. Log in to the server.
OpenNet Expert installation (optional)

This component provides the functionality to configure the ApexPro FH components.
If it is required at a later time, the Service Software CD can be used to install this
component at that time.
1. If needed, insert the Service Software CD into the optical media drive of the
server.
2. In Windows Explorer, navigate to the optical media drive.
3. Double-click on dotnetfx.exe to install .NET v1.1.
NOTE
.NET v1.1 is required for the OpenNet Expert software. If the dotnetfx.exe
is not installed first, then the OpenNet Expert software will not install.
4. Once .NET has been successfully installed, navigate to the optical drive again in
Windows Explorer and double-click on GEHCTools.msi.
5. Follow the on-screen prompts to complete the installation.
6. Once the installation is complete, click Close.
Configuration
Configure the service software
To ensure the Service Gateway IP address is accessible over the network, this
procedure will use a VNC remote desktop approach.

Configure remote access

1. From a computer on the IX network, open a web browser.
2. Connect to Webmin by typing the following URL in the browser.
http://[IP address of the Service Gateway]:8080
3. Log in to Webmin using the appropriate username and password.
Customer GE service
Username biomed service
Password Change Me —
4. Select Remote Service > Configuration.
5. Set the HTTP Proxy Server Configuration as follows:
a. If the site uses an http proxy server, type the address and port in the
appropriate text boxes. If a proxy server is not used, select None.
b. If the http proxy server requires authorization, type the username and
password in the appropriate textboxes and enter the authorization scheme. If
proxy server authorization is not used, select None.
6. Set the Remote Service Configuration as follows:
a. In the Serial Number textbox, type the serial number shown on the
CARESCAPE Systems Manager Software CD.
b. In the System ID textbox, retype the serial number.
c. In the Enterprise URL textbox, verify that the path is:
https://us1-ws.service.gehealthcare.com:443
NOTE
This address should never be changed unless specifically instructed as

this is the address of the GE backoffice servers with which the service
agents communicate.
d. In the Enterprise Tunnel URL textbox, verify that the path is
https://us1-rd.service.gehealthcare.com:443
NOTE
This address should never be changed unless specifically instructed as

this is the address of the GE backoffice servers with which the tunneling
agent communicates.
e. Check that the Protocol is pre-specified as https.
7. Click Save. Once the configuration is saved, the software will automatically be
shut down, configuration files will be updated and the software will restart.
8. Once the software restart completes, select Remote Service > Control.

9. For the Service Agent component, select Enable.
NOTE
Do NOT click Enable for the Event Notification component at this time.
Additional configuration is required before event notification can be
enabled.
10. The Service Gateway should now start to communication with the GE backoffice
servers.
NOTE
The GE ND&I team needs to configure the routing and enable the
appropriate network traffic to connect through a router in order to ensure
communication.
Configure the EA components

There are primarily two components in the Enterprise Access system that generate
Simple Network Management Protocol (SNMP) traps. These components are the
MA430 NMS Controller and the WMTS SHU. One function of the Service Software
is to monitor the traps (faults) generated by these components. However, the MA-430
Controller and the WMTS-SHU have to be configured to send the traps to the IP
address of the Service Gateway. This process of configuring the target IP address into
the Enterprise Access components is also referred to as configuring the trap
destination.
Configure the WMTS SHU trap destination

NOTE
All WMTS-SHUs at a site must be configured.
NOTE
The following items are required to configure the WMTS SHU trap destination:
PC/laptop with MS Windows 2000/XP-Pro/2003 operating system

A cross-over Cat-5 network cable
Lantronix DeviceInstaller software (provided with the Enterprise Access
system along with the NMS Server Software)
1. Install Lantronix DeviceInstaller on the PC/Laptop using the CD provided with
the NMS software.
2. Ensure that BlackIce or any other firewall software is turned off on the PC/
laptop. To ensure that BlackIce is turned off, it is necessary to stop all related
processes by using the Task Manager.
3. Disable the wireless network interface card on the PC/laptop.
4. Configure only one NIC port on the PC/laptop to be active. Configure the active
NIC with a static IP address.

NOTE
The static IP address to be assigned to the PC/Laptop depends on the

WMTS-SHU that is being configured. For example, if the WMTS-SHU
being configured is 192.168.10.10/16, then setup the static IP address of the
PC/laptop to be 192.168.10.11/16.
NOTE
Ensure that the subnet mask of the WMTS-SHU matches that of the PC/
laptop. Refer to the IP address and subnet sticker on the WMTS-SHU.
5. Connect a Cat-5 cross-over network cable between the WMTS-SHU and the PC/
laptop.
6. Connect a power supply to the WMTS-SHU to power it on.
7. On the PC/laptop, select Start > All Programs > Lantronix > DeviceInstaller >
DeviceInstaller.
8. When the DeviceInstaller starts, the XPort should be visible.
511
NOTE
If the XPort is not visible as shown, it means that the PC/laptop cannot
communicate with the WMTS-SHU. Ensure that the IP address assigned is
in the same subnet as the WMTS-SHU. Also, ensure that the subnet mask is
the same as that of the WMTS-SHU.
9. Double-click on the XPort.
10. Select the Telnet Configuration tab.
11. Click Connect.
12. Press Enter.
13. Type 3 and press Enter. This will select the SNMP Configuration option.
14. At the SNMP community name for read prompt, press Enter.
15. At the SNMP community name for write prompt, press Enter.
16. Ensure the default entries of public and private respectively are preserved.

512
17. At the Enter IP addresses for SNMP traps prompt, type the IP address of the
Service Gateway’s IX IP address.
NOTE
For more information on the Service Gateway, See Service Gateway on page
2-89.
NOTE
The WMTS SHU allows up to three destinations IP addresses to be entered.

Only entering the Service Gateway's IP address is sufficient.
18. Press Enter through the other prompts to skip entering more than one trap
destination IP address.
19. Type 9 and press Enter to save and exit.
20. Perform the above configuration for each of the WMTS SHUs present in the
NOTE
Make sure that the IP address of the Service Gateway is configured as the
trap destination for each of the WMTS SHUs.
Configure the MA430 trap destination

NOTE
This configuration does not apply to MA410 controllers.
1. If not already, log in to Webmin.
2. In the Configuration tab, select NMS 430 Trap Destination.
3. In the IP Address textbox, type the IP address of the MA 430 controller.

NOTE
The default Get Community String and Set Community String values do not
need to be changed. Only change these settings if the site has been
specifically configured to have a different community string (not
recommended).
4. Click Retrieve.
5. In the Trap Destination table for the MA 430, type the IX IP address of the
Service Gateway and click Add.
6. Verify the updated Trap Destination Table has the correct destination IP address.
NOTE
If the IP address is incorrect, click Remove next to the IP address and repeat
steps 5 and 6.
Configure monitored component list

1. In the Configuration tab, select Monitored Component List.
2. In the IP Address textbox, type the IP address of the WMTS SHU and click Add.
NOTE
The default SNMP Get Community string is already provided. Do not

change this string unless the MA 430 and WMTS SHUs have been
specifically configured for a different community string.
3. If the device isn’t found, click Yes when prompted to add the device to the
Monitored Component List.
NOTE
If the device is reachable, the device is added to the Monitored Component

List and the SNMP System Description of the device is displayed.
If the device is not communicating, or has not been installed, it is still

possible to add the IP address to the list by clicking Yes.
NOTE
Repeat steps 2 and 3 until all WMTS SHUs are added.
4. In the IP Address textbox, type the IP address of the MA 430 and click Add.
5. Click Yes when prompted to add the device to the Monitored Component List.
6. Verify that all IP address entered in the list are correct.
NOTE
If the IP address is incorrect, click Remove next to the IP address and repeat
the steps to add the correct IP address.
7. Once all IP address are entered correctly, reboot the server.

Configure Event Viewer

1. Select Start > Control Panel.
2. Double-click Administrative Tools.
3. Double-click Event Viewer.
4. Right-click Application and select Properties.
5. Increase the Maximum log size to 6400 KB.
6. Select the Overwrite events as needed option and click Apply.
7. Click OK.
8. Right-click Security and select Properties.
10. Click OK.
11. Right-click System and select Properties.
13. Click OK.
Configure firewall
Configure general firewall

1. Select Start > Control Panel >Windows Firewall.
2. In the General tab, ensure the firewall is turned off. The firewall will be turned
on once the configuration is complete.
3. Ensure that the Don’t Allow Exceptions checkbox is NOT checked.
4. In the Exceptions tab, leave all default settings. If there are programs listed that
are checked ON by default, leave the settings.
5. In the Advanced tab, check the checkboxes for LAC1 and LAC2 according to
which NICs are connected to the Unity Network IX and Unity Network RX
networks. (e.g. LAC1 = Unity Network IX, LAC2 = Unity Network RX)
NOTE
The CARESCAPE Network Manager software will handle the SNMP traffic
via any NIC; therefore, the networks can be connected to any NIC.
Configure Unity Network IX firewall

NOTE
For the following steps, LAC1 will be used for Unity Network IX NIC as an
example.
1. In the Advanced tab, highlight LAC1 and click Settings.

2. To allow Webmin, perform the following:
a. In the Services tab, click Add.
b. Enter the following
Description of service: type Webmin.

Name or IP address: type *
NOTE
An asterisk must be typed in the textbox for the configuration to be
successful.
External Port number: type 8080

Internal Port number: type 8080
c. Select the TCP radio button.
d. Click OK.
NOTE
If either the Webmin port number is changed from 8080, the connection
will be refused.
3. To allow VNC, perform the following:
Description of service: type VNC.

NOTE
successful.

d. Click OK.
4. To allow VNC connection through the Web browser, perform the following:
Description of service: type WebVNC.

NOTE
successful.


d. Click OK.
5. To allow ICMP, perform the following:
a. In the ICMP tab, check Allow incoming echo request.
NOTE
Outbound pings (ICMP) are allowed by default.
b. Click OK.
6. To allow NTP, perform the following:
Description of service: type NTP.

NOTE
successful.

c. Select the UDP radio button.
d. Click OK.
7. To allow SNMP, perform the following:
Description of service: type SNMPTrap-UDP.

NOTE
successful.

c. Select the UDP radio button.
d. Click OK.
8. To allow NMS server to NMS client traffic, perform the following:
Description of service: type NMS-Server-Client.


NOTE
successful.

d. Click OK.
9. To allow HTTP, perform the following:
a. In the Services tab, check Web Server (HTTP).
b. Click Edit.
c. In the Name or IP address textbox, type *
NOTE

successful.
d. Click OK.
Configure Unity Network RX firewall

NOTE
Before configuring the firewall to allow OpenNet Expert on the Unity Network
RX network, ensure that the OpenNet Expert software is installed on the server.
1. To allow the OpenNet Monitor program, perform the following:
a. On the Windows Firewall window, in the Exceptions tab, click Add

Program.
b. Click Browse.
c. Browse to C:/Program Files/GE Healthcare Tools/1.0/bin.
d. Select gepts_one_onm and click Open.
e. Click Change Scope, ensure Any computer is selected, and click Ok.
f. At the Add a Program window, click Ok.
g. In the Windows Firewall window, ensure that the gepts_one_onm is

checked On.
2. To allow the OpenNet AP Configuration program, perform the following:

Program.
b. Click Browse.
d. Select gepts_one_apcfg and click Open.

g. In the Windows Firewall window, ensure that the gepts_one_apcfg is

checked On.
3. To allow the Transmit-Configuration program, perform the following:

Program.
b. Click Browse.
d. Select gepts_one_txcfg and click Open.
g. In the Windows Firewall window, ensure that the gepts_one_txcfg is

checked On.
Enable the firewall

1. On the Windows Firewall window, in the General tab, click the ON
(recommended) radio button.
2. Click Ok.
The firewall is now enabled.
NOTE
If the OpenNet Expert programs are not functioning as expected, disable the
firewall for the duration of the OpenNet Expert usage. Ensure that the firewall is
enabled once the work in OpenNet Expert has finished.
Event notification
NOTE
Once the Event Notification feature is enabled, all EA system component failures
will generate an alert to the GE backoffice and an email notification to GE Tech
Support. If the EA system is not ready for implementation and all the
configuration of the EA components is not yet complete, then the Event
Notification feature should NOT be enabled at this time.
Test the configuration

1. Ensure the MA 430 trap destination is properly configured.
a. Disconnect the power to an RHU.
b. Verify that a RHU disconnected SNMP event is logged in the site server
Event Viewer.

NOTE
The Event Viewer may need to be refreshed for the event to appear.
c. If the event appeared, the MA 430 trap destination is properly configured.

Reconnect power to the RHU.
2. Ensure all the WMTS SHU trap destination tables are properly configured.
a. Disconnect an AP from a WMTS SHU.
b. Verify that a wmtsfhAPDisconnectedNotify SNMP event is logged in the

site server Event Viewer.
NOTE
c. If the event appeared, the WMTS SHU trap destination tables are properly
configured. Reconnect the AP to the WMTS SHU.
3. Ensure the MA 430 is in the Monitored Component List.
a. Disconnect the MA 430 from the IX network for three to four minutes.
b. Verify that a MA 430 disconnection error is logged in the site server Event
Viewer.
NOTE
c. If the event appeared, the MA 430 is in the Monitored Component List.

Reconnect the MA 430 to the network.
4. Ensure the WMTS SHUs are in the Monitored Component List.
a. Disconnect all the WMTS SHU from the IX network for three to four
minutes.
b. Verify that WMTS SHU disconnection errors are logged in the site server
Event Viewer.
NOTE
c. If the events appeared, the WMTS SHUs are in the Monitored Component
List. Reconnect all the WMTS SHUs to the network.
5. If all tests passed, proceed to Enable event notification.
Enable event notification

1. Log in to Webmin.
2. Select Remote Service > Control.
3. In the Remote Service Controls window, select Enable for the Event
Notification component.
4. Click Save.

5. Reboot the server.
NOTE
At this point, all EA system component failures will generate an alert to the GE
backoffice and an email notification to GE Tech Support. If the EA system is not
ready for implementation and all the configuration of the EA components is not
yet complete, then the Event Notification feature should NOT be enabled at this
time. Disable the feature and enable it when the system is ready.
NOTE
At this point, the server can be rack mounted if applicable.
Configure OpenNet Expert

Please refer to the OpenNet Expert User Guide for information about configuring and
using the OpenNet Expert software.
Configure user passwords

Follow these steps to change the Webmin access password for the biomed user.
1. In Webmin, select the Configuration tab.
2. Click Passwords.
3. In the Password and Confirm Password textboxes, type the new password.
4. Click Save.
NOTE
The service user passwords cannot be changed. The biomed password can be
changed by both the service user and the biomed user.
Uninstall
If there is a need to uninstall the software perform these steps.
Uninstall CARESCAPE Systems Manager software

1. Navigate to the folder at C:\GEservice.
2. Double-click the uninstaller.exe to begin uninstalling.
3. Click Ok to confirm the request to uninstall the software.
4. The uninstaller will proceed with removing the software.

Uninstall OpenNet Expert software

1. On the Service Gateway server, select Start > Control Panel > Add or Remove
Programs.
2. Select GE Healthcare Tools and click Remove.
3. Click Ok to confirm the request to uninstall the software.
4. The uninstaller will proceed with removing the software.

6 Maintenance

Maintenance
Schedule
CAUTION
EQUIPMENT DAMAGE/LOSS OF FUNCTION/PERSONAL
INJURY— The manufacturer does not in any manner, assume the
responsibility for performing the recommended maintenance
schedule, unless an Equipment Maintenance Agreement exists. The
sole responsibility rests with the individuals, hospitals, or
institutions utilizing the device. Failure on the part of all responsible
individuals, hospitals or institutions, employing the use of this
device, to implement the recommended maintenance schedule may
cause equipment failure and possible health hazards.
WARNING
SHOCK HAZARD/EQUIPMENT DAMAGE— If fluids are spilled
on the equipment, shut down the unit, remove power and disconnect
all components. Perform the maintenance procedures listed in this
section and document the incident in the repair log. Do not use the
equipment if it has been damaged by the fluid. Fluids spilled on the
equipment can cause an electrical shock hazard and may damage the
equipment.
WARNING
LOSS OF DATA—The manufacturer requires that calibration be
performed by service personnel as follows:
1395-1400 MHz systems calibrate the following every 2 years:
T14 transmitter
RIM 1400
Receiver subsystem
To make sure the Enterprise Access hardware remains in proper operational and
functional order, a good maintenance schedule must be adhered to. The manufacturer
recommends the following to be performed once a year:
Checkout procedure: Should be performed by qualified service personnel upon

receipt of the equipment, one time per year thereafter, and each time the unit is
serviced.
Visual inspection: Should be performed by service personnel upon receipt of the
equipment and prior to servicing the unit.
Cleaning: Should be performed by service personnel each time the unit is
serviced.

Maintenance
Controlling electrostatic discharge damage

All external connector inputs and outputs of the device are designed with protection
from electrostatic discharge damage (ESD). However, if the interior of the device
needs to be accessed for any reason, internal components and assemblies are
susceptible to ESD. This includes human hands, non-ESD protected work stations
and/or improperly grounded test equipment.
The following guidelines help make a service workstation more resistant to the ESD:
Discharge any static charge you may have built up before handling
semiconductors or assemblies containing semiconductors. This can be done by
touching any bare metal on the Enterprise Access equipment chassis or cable
connector jacks on the back of the unit. Do this frequently and repeatedly while
working on the unit.
Wear a grounded, anti-static wristband (3M part number 2046 or equivalent) or
heel strap at all times while handling or repairing assemblies containing
semiconductors.
Use properly grounded soldering and test equipment.
Use a static-free work surface (3M part number 8210 or equivalent) while
handling or working on assemblies containing semiconductors.
Keep the work surface free of nonconducting materials such as ordinary plastic
assembly aids and foam packing.
Semiconductors and electrical/electronic assemblies should be stored only in
antistatic bags or boxes.
Do NOT remove semiconductors or assemblies containing semiconductors from
antistatic containers (Velo-stat bags) until they arrive at the work surface and
until absolutely necessary.
Make sure power to an assembly is turned off before removing or inserting a
semiconductor.
Do NOT touch semiconductor leads, pins or circuitry unless absolutely
necessary.
These guidelines cannot guaranty a 100% static-free workstation, but greatly reduce
the potential for failure of any electrical/electronic assemblies due to electrostatic
discharge.
Visual inspection
CAUTION
EQUIPMENT DAMAGE— Follow the procedures in Controlling
electrostatic discharge damage on page 6-3. The Enterprise Access
equipment is extremely static sensitive. If the proper ESD
precautions are not followed, damage to the unit could result.
Carefully inspect the Enterprise Access equipment and its components prior to
installation, one time each year thereafter, and each time the equipment is serviced.
To perform a complete visual inspection of the equipment, follow these steps:

Maintenance
1. General inspection: Inspect the external surfaces of the Enterprise Access

equipment components for obvious physical damage. Do NOT use the device if
physical damage is evident. Refer damaged equipment to qualified service
personnel for repair.
2. Connectors: Inspect all external connectors for damaged pins, prongs and
connector housings. Refer damaged equipment to qualified service personnel for
repair. Ensure that all connections are properly seated and secure.
3. Cable insulation: Inspect all cables, insulation, strain-reliefs and connectors for
damage, cracks or degradation. Refer damaged equipment to qualified service
personnel for repair.
Cleaning
Ventilation ports
Make sure all dust and debris is cleared away from the ventilation ports on the front
and back of the Enterprise Access equipment.
Checkout procedure
About the checkout procedure
The checkout procedure process provides a method of verifying operational and
functional performance without having to disassemble the unit. Failure to attain the
prescribed results indicates a need for configuration or repair.
Perform the checkout procedures upon receipt of the equipment, every year thereafter,
and each time a component is removed or replaced.
The checkout procedure process is based on the assumption that the equipment being
tested is using known, good cables. It also requires that the user be familiar with the
operation of the system.
Perform all of the checkout procedures included in this section to completely test the
system for proper function and operation.
Check for valid network connections to NMS 430/410

Check for remote connectivity (NMS)
NOTE
The remote computer must be configured properly before accessing the system
through Webmin and VNC.
Using a remote computer, logon to the Enterprise Access equipment.

Maintenance
LED status indicators

The Enterprise Access equipment is equipped with several LED status indicators,
which function to indicate component operation status.
A steady green LED indicates normal operation.

A blinking green LED indicates an active link.
An amber LED indicates system health has degraded (except on the power LED,
which indicates standby), contact GE and schedule a service check-up or planned
maintenance.
A red LED indicates that there is a problem. Call GE Technical Support at 1-
800-558-7044 IMMEDIATELY.
Calibration
WARNING
LOSS OF DATA—The manufacturer requires that calibration be
performed by service personnel as follows:
1395-1400 MHz systems calibrate the following every 2 years:
T14 transmitter
RIM 1400
Receiver subsystem
RIM 1400 Calibration

NOTE
Turn off InSite Exc before executing this procedure.
NOTE
The Rohde & Schwarz FSH3 spectrum analyzer is used for the following steps. If
a different spectrum analyzer is being used, the detailed sub-steps may be
different.
NOTE
A RIM 1400 must be powered up for 48 hours prior to it functioning as a Master

to ensure frequency stabilization. If a RIM 1400 has been previously running for
more than 48 hours, and powered off for less than 10 hours, the RIM 1400 has
maintained frequency stabilization and can function as master if desired.
Frequency stabilization is not required for a RIM 1400 to operate in slave mode.
Therefore, a RIM 1400 can operate in slave mode immediately upon being
powered up.

Maintenance
Calibrate the RIM 1400 master
Determine frequency offset

1. Confirm that only one RIM 1400 is running as master by checking the Master-
Active LED on the front of each RIM 1400.
2. Using an N-type to SMA 50 Ohm coaxial cable, connect the spectrum analyzer to
the LO Output connector on the RIM 1400 master.
3. Press PRESET.
4. Connect the external 10 MHz reference to the EXT TRIG IN/EXT REF IN.
NOTE
The external reference must be accurate to 0.0083ppm. Ensure that you

allow the external reference to stabilize (Refer to the external reference
operators manual).
5. Set the analyzer for external 10MHz reference mode.
a. Press SETUP.
b. Press F3- HARDWARE SETUP.
c. Select BNC I/O MODE and press ENTER.
d. Select EXT REF IN and press ENTER.
6. Ensure the preamplifier is off.
a. Press SETUP.
b. Press F3 - HARDWARE SETUP.
c. Select PREAMP and press ENTER.
d. Select OFF and press ENTER.
7. Set the center frequency to 1963 MHz.
a. Press FREQ.
b. Type 1963, press MHz and press ENTER.
8. Set the reference amplitude to 10 dBm.
a. Press AMPT.
b. Type 10, press dBm and press ENTER.
9. Set the span to 50 kHz.
a. Press SPAN.
b. Type 50, press kHz and press ENTER.
10. Set the marker to the peak signal.
a. Press MARKER.

Maintenance
b. Press F3 - SET MARKER.
c. Select Peak and press ENTER.
d. The peak should be selected.
11. If necessary, set the center frequency so that it is the same as the marker
frequency.
a. Press MARKER.
c. Select CENTER=MKR FREQ and press ENTER.
a. Press SPAN.
13. Set the resolution bandwidth to 100 Hz.
a. Press BW.
b. Press F1 - MANUAL RES BW.
c. Type 100, press Hz and press Enter.
14. Reset the marker to the peak signal.
a. Press MARKER.
d. The center maximum peak should be selected.
15. Record the frequency of the marker:
Measured frequency: __________________
16. Subtract the LO target frequency (1963 MHz) from the measured frequency (step
15) and record the value:
_______________ - __1963000000 Hz___ = _____________
Measured frequency - Target frequency = Frequency difference
NOTE
Multiply MHz by 1000000 to convert to Hz.
17. If the difference is less than or equal to ±50 Hz, no adjustment is required as the
RIM 1400 is within specifications. If the difference is greater, proceed to Adjust
frequency.

Maintenance
Adjust frequency
NOTE
The frequency should be adjusted to the minimum frequency error attainable by

adjusting the Ref Tune value.
1. Connect a computer that has NMS MCT installed to the NMS 430 at the site
using a serial cable.
2. From the computer, open the NMS MCT software. See Chapter 4.
3. Log in to NMS MCT using the username Field Eng and password eng.
4. Double-click the picture of the RIM 1400 master (has Master-Active LED lit).
509A
5. In the Synchronization tab, click the ... button to adjust the Ref Tune.

Maintenance
510A
6. If the difference calculated (See page 6-7.) is positive, decrease the Ref Tune
value by one. If the difference is negative, increase the Ref Tune value by one.
CAUTION
Do not move the Ref Tune setting by more than one value at a time
to prevent moving the intended set point/frequency too far, which
could cause signal dropout.
NOTE
The change will take 30 - 60 seconds to take effect.
7. Check the frequency on the spectrum analyzer. If the frequency is not within 50
Hz of the target frequency, repeat by either further increasing or decreasing the
Ref Tune value by one.
8. Once the RIM 1400 master is within specification, select the Synchronization
tab for the RIM 1400 and adjust the Maintenance timer to 24 months.

Maintenance
616
9. Proceed to Calibrate the RIM 1400s in slave mode.
Calibrate the RIM 1400s in slave mode

NOTE
This section must be performed only AFTER calibrating the master RIM 1400
and must be completed for each RIM 1400 in slave mode present in the system.
Rough adjust
1. Double-click the picture of a RIM 1400 that is not currently master.
2. In the Synchronization tab, click Adjust in the Reference section.
3. Repeat for all RIM 1400s in slave mode.
Force RIM 1400 to be master

1. Force one of the RIM 1400s to operate as master.
a. Double-click the picture of a RIM 1400 that is not currently master.
b. In the Synchronization tab, change the following settings in the Master/

Slave Selection:
Define: Master
Auto Mode: Forced
2. Wait approximately one minute and confirm the new RIM 1400 is operating as
master by checking the LEDs (it is acceptable to have more than one RIM 1400
operating as master during the calibration procedure). Proceed to Determine
frequency offset.
Determine frequency offset

1. Using an N-type to SMA 50 Ohm coaxial cable, connect the spectrum analyzer to
the LO Output connector on the RIM 1400 master.

Maintenance
2. Press PRESET.
3. Connect the external 10 MHz reference to the EXT TRIG IN/EXT REF IN.
NOTE
The external reference must be accurate to 0.0083ppm. Ensure that you

allow the external reference to stabilize (Refer the external reference
operators manual)
4. Set the analyzer for external 10MHz reference mode.
a. Press SETUP.
c. Select BNC I/O MODE and press ENTER.
d. Select EXT REF IN and press ENTER.
5. Ensure the preamplifier is off.
a. Press SETUP.
c. Select PREAMP and press ENTER.
d. Select OFF and press ENTER.
6. Set the center frequency to 1963 MHz.
a. Press FREQ.
b. Type 1963, press MHz and press ENTER.
7. Set the reference amplitude to 10 dBm.
a. Press AMPT.
b. Type 10, press dBm and press ENTER.
a. Press SPAN.
9. Set the marker to the peak signal.
a. Press MARKER.
d. The peak should be selected.
10. If necessary, set the center frequency so that it is the same as the marker
frequency.
a. Press MARKER.

Maintenance
c. Select CENTER=MKR FREQ and press ENTER.
a. Press SPAN.
12. Set the resolution bandwidth to 100 Hz.
a. Press BW.
b. Press F1- MANUAL RES BW.
c. Type 100, press Hz and press Enter.
13. Reset the marker to the peak signal.
a. Press MARKER.
d. The center maximum peak should be selected.
14. Record the frequency of the marker:
Measured frequency: __________________
15. Subtract the LO target frequency (1963 MHz) from the measured frequency (step
14) and record the value:
_______________ - __1963000000 Hz___ = _____________
Measured frequency - Target frequency = Frequency difference
16. Proceed to Adjust frequency.
Adjust frequency
NOTE
The frequency should be adjusted to the minimum frequency error attainable by

adjusting the Ref Tune value.
1. Connect a computer that has NMS MCT installed to the NMS 430 at the site
using a serial cable.
2. From the computer, open the NMS MCT software. See Chapter 4.
3. Log in to NMS MCT using the username Field Eng and password eng.
4. Double-click the picture of the RIM 1400 master (has Master-Config and
Master-Active LED lit).

Maintenance
509A
5. In the Synchronization tab, click the ... button to adjust the Ref Tune.
510A
6. If the difference calculated (See page 6-12.) is positive, decrease the Ref Tune
value by one. If the difference is negative, increase the Ref Tune value by one.
CAUTION
Do not move the Ref Tune setting by more than one value at a time
to prevent moving the intended set point/frequency too far, which
could cause signal dropout.
NOTE
The change will take 30 - 60 seconds to take effect.

Maintenance
7. Check the frequency on the spectrum analyzer. If the frequency is not within 50
Hz of the target frequency, repeat by either further increasing or decreasing the
Ref Tune value by one.
8. Once the RIM 1400 is within specification, perform the following steps to set it
back to slave mode.
a. Double-click the picture of a RIM 1400 that is currently master.
b. In the Synchronization tab, change the following settings in the Master/

Slave Selection:
Define: Slave
Auto Mode: Automatic
9. In the Synchronization tab, adjust the Maintenance timer to 24 months
10. Repeat the following sections for each of the remaining RIM 1400s operating in
slave mode:
Rough adjust on page 6-10

Force RIM 1400 to be master on page 6-10
Determine frequency offset on page 6-10
Adjust frequency on page 6-12
11. After the calibration of all the RIM 1400s is complete, verify that only one RIM
1400 is operating as master. If not repeat step 8 for each RIM 1400.
Receiver calibration
Refer to the ApexPro Antenna Infrastructure, Transmitter and Receiver Technical
Manual for detailed calibration procedures.
Transmitter calibration
Refer to the ApexPro Antenna Infrastructure, Transmitter and Receiver Technical
Manual for detailed calibration procedures.
Maintenance checklist
Use the following checklist to ensure maintenance completion.
Visual inspection
Visual inspection on page 6-3
General
Connectors
Cable insulation

Maintenance
Cleaning
Cleaning on page 6-4
Ventilation ports
Checkout procedure
Checkout procedure on page 6-4
Check for valid network connections

Check for remote connectivity
LED status indicators
Repair log
A repair log is included for your convenience to record the repair history of this
product.
Unit serial number:
Institution name:
Date Maintenance/Repair Technician

Maintenance

7 Troubleshooting

Troubleshooting
For technical support and to order replacement parts, please contact GE Technical
Support at 1-800-558-7044.
Antenna system troubleshooting tree
3UREOHP
HQFRXQWHUHGLQ
QHWZRUN
,VWKH
SUREOHPZLWK7HOHPHWU\
&HOOXODURU:L)L"
3HUIRUPWKH(QWHUSULVH
$FFHVV,QIUDVWUXFWXUH
WURXEOHVKRRWLQJSURFHGXUHV
7HOHPHWU\ :L)LRU&HOOXODU LQWKLVPDQXDO

,VWKH
SUREOHPD
FOLQLFDOLVVXHZLWKD(QWHUSULVH
$FFHVVFRPSRQHQWRUZLWKD (QWHUSULVH$FFHVV 'RHVWKLVIL[WKH 1R
:RUNZLWKFOLQLFDO 7HOHPHWU\&RPSRQHQWVHHWKH &RPSRQHQW LVVXH"
&OLQLFDO &,&3UR$76HYHQWORJHUURU
WHFKQLFLDQ
PHVVDJHV"
8QVXUH <HV
7HOHPHWU\FRPSRQHQW
'RQH
:KLFK
$SH[3UR)+$3 WHOHPHWU\ 5HFHLYHURU&,&
FRPSRQHQW"
&DOO*(WHFKQLFDO
$SH[3UR)+ $SH[3UR&+ VXSSRUWDW
7UDQVFHLYHU 7UDQVPLWWHU
*RWRWKH$SH[3UR *RWRWKH$SH[3UR *RWRWKH$SH[3UR %HJLQGURSRXWGHWHUPLQDWLRQ

)+$3 )+7UDQVFHLYHU &+7UDQVPLWWHU 7XUQRQGURSRXWIODJVRQWKH
7URXEOHVKRRWLQJ 7URXEOHVKRRWLQJ 7URXEOHVKRRWLQJ &,&WRFKHFNWKHFRORURIDQ\
7UHHVLQWKLV 7UHHVLQWKLV 7UHHLQWKLV GURSRXW6HHGURSRXW
PDQXDO PDQXDO PDQXDO GHWHUPLQDWLRQ
:KDW
FRORULVWKH &RORURWKHUWKDQ
/LJKWRU'DUN%OXH
GURSRXWRQWKH <HOORZRU%OXH
&,&"
<HOORZ
7URXEOHVKRRWWKHQHWZRUN
LVVXHVWKLVLVQRW5) 3HUIRUPWKH$QWHQQD
6\VWHPWURXEOHVKRRWLQJ 6HHWKH&,&6HUYLFH
UHODWHGGURSRXW6HHWKH
SURFHGXUHVLQWKLVPDQXDO 0DQXDOIRUPRUH
&,&6HUYLFH0DQXDOIRU
IRUHLWKHU$SH[3UR&+RU LQIRUPDWLRQWKLVLVQRW5)
PRUHLQIRUPDWLRQ
$SH[3UR)+ UHODWHGGURSRXW
'RHVWKLVIL[WKH 1R
LVVXH"
<HV
'RQH
600b

Troubleshooting
Antenna system troubleshooting

Drop-out determination
Turn on drop-out flags on the CIC Pro center to check the color of any drop-out on the
patient signal lead waveform at the CIC Pro patient view.
1. At the bottom of the CIC Pro screen, select the Setup CIC button.
2. Select the Service Password tab.
3. Type the password mms_com and then select Ok. A DOS command prompt
window is displayed.
4. Type setflags<Space>-mark<Space>all and press Enter on the keyboard to

turn on drop-out flags.
If the color is yellow, suspect RF drop-out on the transmitter, the antenna

system or the receiver sub-system.
If the color is light blue or dark blue, suspect a network issue, not an RF-
related drop-out.
If it is another color, refer to the CIC Pro Clinical Information Center
Service Manual for the cause since this indicates that it is not RF drop-out.
5. Type setflags<Space>-mark<Space>off and press Enter on the keyboard to
turn off drop-out flags.
6. Close the DOS window and the CIC Setup window.
ApexPro CH system troubleshooting

ApexPro CH system troubleshooting procedure (yellow drop-out condition)
1. Verify the patient/transmitter is in the coverage area. If not, the system is not at
fault.
2. Check the transmitter lead wire status. If the status is in Fail condition, correct
the condition. Refer to the ApexPro CH Operator’s manual.
3. On the CIC Pro, ensure that you are viewing all leads for the patient/transmitter.
NOTE
If a shorted-lead set is used, an asystole alarm will sound if the transmitter is

admitted.
4. Verify lead prep. If possible, connect a shorted-lead set or simulator to the

transmitter to see if that corrects the condition.
5. Check the transmitter battery status. If the status is in Fail condition, correct the
condition by replacing the batteries with new ones. If needed, See ApexPro CH/
CARESCAPE T14 transmitter troubleshooting tree on page 7-6.

Troubleshooting
6. Isolate whether the drop-out is related to single or multiple patients in the same
coverage area by verifying if more than one transmitter is dropping out in that
coverage area.
a. If multiple transmitters drop out in the same coverage area, suspect the
antenna system. See Enterprise Access infrastructure troubleshooting on
page 7-21.
b. If only one transmitter is dropping out, suspect the transmitter or receiver

sub-system. Following the steps below for specific troubleshooting
techniques:
i. Duplicate the transmitter on another receiver sub-system.
ii. From the main CIC Pro screen, select the Setup CIC button.
iii. Select the Service Password tab.
iv. Type the password mms_com and then click Ok. A command prompt
window is displayed.
v. Type setflags<space>-dup<space>on and press Enter to allow

duplicate transmitters.
NOTE
Once this option is selected, you have five minutes to type the
duplicate TTX numbers. If that is not enough time, select this
option again and continue entering TTX numbers.
vi. Type setflags<space>-dup<space>off and press Enter to turn off

duplicate TTX.
vii. Close the command prompt window and the CIC Setup window.
c. If drop-out continues on both receiver sub-systems, suspect the transmitter.

Swap the transmitter with a known good transmitter. Drop-out should go
away.
d. If drop-out does not go away, suspect an antenna coverage problem. See

Enterprise Access infrastructure troubleshooting on page 7-21.
e. If drop-out is on one receiver sub-system and not on the other, suspect the
receiver sub-system. Use the ApexPro Telemetry Server Service Manual to
complete the following:
i. Isolate which receiver sub-system is attached to the CIC Pro being

viewed by using the service diagnostic tool PTSCONFIG at the CIC
Pro and the command blink patient unit|bed* in order to associate a
care unit/bed number to a receiver sub-system in a given rack.
ii. Once the receiver sub-system is known, check all LEDs for proper
operation. Verify their status with Check LEDs drop-out chart on page
7-7.
iii. If all LEDs appear to have normal operation status, find the suspect
receiver card by using the service diagnostic tool PTSCONFIG at the
CIC Pro and the command blink patient unit|bed* in order to associate
a care unit/bed number to a receiver sub-system in a given rack

Troubleshooting
iv. Swap a known good receiver card in place. Drop-out should go away.
v. If drop-out does not go away, suspect an antenna coverage problem. See

Enterprise Access infrastructure troubleshooting on page 7-21.

Troubleshooting
ApexPro CH/CARESCAPE T14 transmitter troubleshooting tree
$SH[3UR5HFHLYHURU6XEV\VWHPRU$QWHQQD6\VWHP :KDWV\VWHP $SH[3UR7UDQVPLWWHU

FRPSRQHQWDUH\RX
KDYLQJSUREOHPV
ZLWK"
,QVWDOO 3UREOHP 1R
3OHDVHXWLOL]H FRUUHFWO\ VROYHG"
WKH6\VWHP
7URXEOHVKRRWLQJ
<HV
VHFWLRQRIWKLV *22'
GRFXPHQW 1R
:KHQ
$UHWKH
<HV 1R 1R IUHVKEDWWHULHVDUHILUVW
EDWWHULHV
'RDQ\/('V LQVWDOOHGLQWKHXQLWGR
LQVWDOOHG
IODVK" WKH/('VIODVKDV
FRUUHFWO\"
H[SHFWHG"
<HV
$UH/('V <HV
<HV 1R 5$RU/$
IODVKLQJ
RQO\"
FRQVWDQWO\"
:KHQ
WUDQVPLWWHULV
<HV FRQQHFWHGWRWKH
1R SURJUDPPLQJER[GRHV
1R
WKHPHVVDJHER[RQWRS
'RZQORDGWUDQVPLWWHU$SS RIWKHWUDQVPLWWHU
DQG0IJFRGHVRQFH SURJUDPPLQJVFUHHQ
,I\RXDUULYHKHUHDVHFRQG DFNQRZOHGJH
WLPH2%)LIXQLWTXDOLILHV FRPPXQLFDWLRQ"
RWKHUZLVHVHQGWRUHSDLU
<HV
:KHQ
WUDQVPLWWHULV
FRQQHFWHGWRWKH
3URJUDPWUDQVPLWWHU 1R SURJUDPPLQJER[GRHV
77;QXPEHUWR WKH77;QXPEHURQWKH
UHTXLUHGQXPEHU WUDQVPLWWHUPDWFKWKH
77;QXPEHU
'RHV 1R GLVSOD\HGRQ
WKHXQLWTXDOLI\ WKHVFUHHQ"
DVD2%)"
<HV <HV
6HQGWR
5HSDLU
:KHQ
(QWHU6XSHU8VHUPRGHDQG WUDQVPLWWHULV
2%) SUHVV&OHDU)DLOXUHVEXWWRQ 1R FRQQHFWHGWRWKH
,I\RXDUULYHKHUHDVHFRQGWLPH SURJUDPPLQJER[
FDOO7HFKQLFDO6XSSRUWDW GRDOOSRZHUXS
VHOIWHVWV
SDVV"
<HV
3HUIRUPWKHVWHSVRXWOLQHGLQWKH$SH[3UR
7UDQVPLWWHU&DUULHU,PSDLUPHQW <HV $UH\RXVXUH
0HDVXUHPHQW3URFHGXUHVHFWLRQ WKHSUREOHPLV
,I\RXDUULYHKHUHDVHFRQGWLPH2%)LIXQLW WKHWUDQVPLWWHU"
TXDOLILHVRWKHUZLVHVHQGWRUHSDLU ,VWKH
<HV SUREOHPUHODWHGWR
GURSRXWRULQWHUPLWWHQW
1R FRPPXQLFDWLRQZLWKWKH
$SH[3URV\VWHP"
1R
&DOO7HFKQLFDO6XSSRUWDW
601

Troubleshooting
Check LEDs drop-out chart
LED Solid green Flashing green Solid yellow Flashing yellow Blank
System Status Normal operation System initialization System error – Software updating or Power off
system halted Blink rack command at CIC
Pro
Receiver 1 Normal operation Module 1 initialization Module 1 error Single receiver error on Not installed
Module 1 or
Blink rack command at CIC
Pro
Module 2 or
Pro
Module 3 or
Pro
Module 4 or
Pro
Link/Collision Link established N/A N/A Ethernet collision occurred Not connected to host
Transmit/ N/A Ethernet transmission N/A Ethernet reception No transmit or receive

Receive
ApexPro FH antenna system (yellow drop-out condition)

General
OpenNet Expert is used throughout this troubleshooting procedure.

Troubleshooting
'HWHUPLQHWKH
WUDQVFHLYHU
ORFDWLRQ
,VWKH
,VWKH
$3UHSRUWLQJ$FWLYH
WUDQVFHLYHU
6\QF2NDQGKDV <HV
DWWDFKHGWRWKH
RWKHUWUDQVFHLYHUV
³LGHDO´$3"
<HV DWWDFKHG"
1R
1R
7KLVPD\EHDQ$3LVVXH ,VWKHLGHDO
See Access $3UHSRUWLQJ$FWLYH
1R 6\QF2NDQGKDVRWKHU
point WUDQVFHLYHUV
troubleshooting $WWDFKHG"
<HV
,VWKH 3RVVLEOH³URDP
WUDQVFHLYHUDWWDFKHG WUDS´5HVHWWKH
WRDQ$3RXWVLGHRIWKH <HV WUDQVFHLYHUWRVHH
LPPHGLDWH LIWKHSUREOHPLV
YLFLQLW\" UHSURGXFLEOH
1R
,VWKH
SDWLHQW
DPEXODWLQJ 6PDOOGURSRXWVDUH
LQWKHVKRZHURU <HV OLNHO\WRRFFXULQ
PRYLQJDZD\IURPWKH WKHVHVLWXDWLRQV
FRYHUDJH
DUHD"
1R
5HSODFHWKH
WUDQVFHLYHUZLWKD
NQRZQJRRGXQLW
See
$UHWKHUH
Transceiver 1R
GURSRXWV"
on page 7-9.
<HV
&RQWDFW*(
WHFKQLFDOVXSSRUW
DW
The “ideal” Access Point (AP) is determined by the relative proximity between the transceiver and an AP.
A roam trap occurs when a transceiver has linked with an AP that does not belong to the neighbor table of any of the APS that can be
considered “better” candidates for the link. Thus, that transceiver will not find a path back to its ideal AP.
603

Troubleshooting
Transceiver
No signal from transceiver
,VWKH
5HSODFHUHVHW
1R EDWWHU\IXOO\
WKHEDWWHU\
FKDUJHG"
<HV
$UHDOO
,VWKHUH
1R WKH/('V 1R
ZDYHIRUP"
EOLQNLQJ"
<HV
<HV
(QG
7KHXQLWLVLQ
'HDFWLYDWHG
PRGH
5HSURJUDPWKH
XQLWZLWKD
GLIIHUHQW77;,'
5HWHVWWKH
WUDQVFHLYHU
5HIHUWRWKH&,&3UR
,VWKH
<HV FRORUVFKHPHWR
UHWHVW 1R
GHWHUPLQHWKHW\SHRI
RN"
GURS
See Antenna
:KDW system
,QVSHFWWKHOHDGVHW <HOORZ5) FRORULVWKH 2WKHU
GURSRXW"
troubleshooting
tree on page 7-2.
,VWKH
5HSODFHWKH
OHDGVHWSURSHUO\
OHDGVHWDQG 1R
LQVWDOOHGDQGLQJRRG
UHWHVW
FRQGLWLRQ"
<HV
3UHVVWKH
$WWHQGDQW
3UHVHQWEXWWRQV
DQGYLHZWKH5)
/('VWDWXV
8VLQJ7UDQVPLW
&RQILJYHULI\WKH 'RDQ\
DSSURSULDWH5)DQG 1R /('V <HV
PDLQERDUGILUPZDUH LOOXPLQDWH"
YHUVLRQV 5)/(' 5)/('LV
5)/('
LV QRW
LVVROLG
IODVKLQJ LOOXPLQDWHG
$UHWKH
5HSODFHWKH
<HV YHUVLRQV
WUDQVFHLYHU 7UDQVFHLYHULV 7UDQVFHLYHULV
FRUUHFW" 7UDQVFHLYHULV
FRQQHFWHGWRDQ QRWFRQQHFWHG
DGPLWWHGWR
$3EXWQRWWR WRHLWKHUWKH$3
1R WKH&,&3UR
WKH&,&3UR RUWKH&,&3UR
5HORDG5)
ILUPZDUHDQG
VHTXHQFHWDEOH &RQWDFW*( See RF LED
DQGUHWHVW
See RF LED
WHFKQLFDOVXSSRUW
DW flashing on not illuminated
page 7-10. on page 7-11.
604

Troubleshooting
RF LED flashing
5HPRYHDQG
UHSODFHEDWWHU\
WRUHVHWWKH
WUDQVFHLYHU
:DLWDIHZPLQXWHV
WRYHULI\
ZDYHIRUPV
$UHWKHUH
ZDYHIRUPV <HV (QG
SUHVHQW"
1R
2QWKH
&,&3URGRHV
7\SHWKHFRUUHFW WKHDGPLWWHGEHG
77;,'GHYLFH,' 1R FRQWDLQWKHFRUUHFW77;
DQGRUGHYLFHW\SH ,'GHYLFH,'DQGRU
GHYLFH
W\SH"
<HV
$UHWKHUH
'LVFKDUJHDQG
ZDYHIRUPV 1R
127(,I\RXKDYH UHDGPLWWKHEHG
SUHVHQW"
UHDFKHGWKLVIORZ
WZLFHFRQWDFW*(
WHFKQLFDOVXSSRUW
DW
<HV
,VWKH
(QG <HV SUREOHP
IL[HG"
1R
8VH7UDQVPLW&RQILJWR
FKHFNWKH77;DQG
GHYLFH,'VHWWLQJVRQ
WKHWUDQVFHLYHUPDWFK
WKH,'VRQWKH&,&3UR
605

Troubleshooting
RF LED not illuminated
5HPRYHDQGUHSODFH
WKHEDWWHU\WRUHVHW
WKHWUDQVFHLYHU
'RHV
WKH5)/('
LOOXPLQDWH
GXULQJUHVHW
PRGH"
1R
,VWKH
<HV EDWWHU\ 1R
RN"
<HV
$UHWKHUH
(QG <HV ZDYHIRUPV
SUHVHQW"
1R
8VLQJ7UDQVPLW&RQILJYHULI\
WKHWUDQVFHLYHU¶V5)DQG
PDLQERDUGILUPZDUHYHUVLRQV
DJDLQVWWKHGHVLJQSDFNDJH
$UHWKH 'RZQORDGWKH
YHUVLRQ 1R FRUUHFWILUPZDUH
FRUUHFW" YHUVLRQV
<HV
5HORDGWKH
GHIDXOWYDOXHV
6HWVLWHVSHFLILF
SDUDPHWHUVHJ
1HWZRUNNH\
$UHWKHUH 'HWHUPLQHWKH
ZDYHIRUPV 1R WUDQVFHLYHU
SUHVHQW" ORFDWLRQ
<HV
,VWKH
WUDQVFHLYHU
(QG 1R ZLWKLQWKH
FRYHUDJH
DUHD"
<HV
$UH
7KLVPD\EHDQ$3LVVXH
WKHUHRWKHU
5HSODFHWKH
See Access point WUDQVFHLYHUV
1R <HV WUDQVFHLYHU
OLQNHGWRD
troubleshooting on DQGUHWHVW
QHDUE\
$3"
606

Troubleshooting
Access point troubleshooting
General
,GHQWLI\WKH$3
,VWKHUH
QXPEHULQWKH$76
DQ$3HUURU
ORJILOHDQGSURFHHG
PHVVDJHRQWKH <HV
WRWKHDSSURSULDWH
&,&3UR
WURXEOHVKRRWLQJWUHH
GLVSOD\"
LQWKLVPDQXDO
1R
8VH:HEPLQWR
FKHFNLIWKH$3LV
DFWLYH6\QFDQG
FRGHYHUVLRQ
&KHFNIRU
DFFHSWDEOH
SDUDPHWHUV
5HORDGWKH$3
,VWKH FRQILJXUDWLRQE\
FRQILJXUDWLRQ 1R8QNQRZQ F\FOLQJSRZHUWRWKH
FRUUHFW" $3:DLWDIHZ
PLQXWHVDQGUHWHVW
<HV
,QVSHFWWKH$3
DQWHQQDFRQQHFWLRQV ,VWKH
SUREOHP
<HV (QG
FRUUHFWHG"
,VWKH
&RQQHFWDQG 1R
1R DQWHQQDILUPO\
UHWHVWWKH$3
FRQQHFWHG"
5HIHUWRWKHGHVLJQ
SDFNDJHDQGUHORDG
WKH$3ILUPZDUH
XVLQJ$3&RQILJ
<HV
,VWKH ,QVSHFWWKH$3 5HWHVWWKH$3

SUREOHP (WKHUQHWDQG6\QF
(QG <HV 1R
FRUUHFWHG" FRQQHFWLRQVIRU
LQWHUPLWWHQWEHKDYLRU
,VWKH
SUREOHP
<HV (QG
FRUUHFWHG"
1R
<HV
,VWKHUH
LQWHUPLWWHQW 1R 5HSODFHWKH$3
EHKDYLRU"
<HV
,VWKH 5HSODFHWKH
SUREOHP 5- ,VWKHUH6\QF
(WKHUQHW
FRUUHFWHG" FRQQHFWRU (KWHUQHW"
DQGUHWHVW
1R 6\QF
See AP error See Sync Errors on

message - No page 7-17.
response from AP
607

Troubleshooting
AP error message - No response from AP
'LVSOD\WKH$36WDWLVWLFV
VFUHHQXVLQJWKH:HEPLQ
LQWHUIDFH/RRNIRURQHRU
PRUH1HQWULHVLQWKH$3
$FWLYHFROXPQ
&RPSDUHWKH$3 $UH
OLVWZLWKWKHGHYLFH WKHUHRQHRU
1R
PDVWHUOLVWWRILQG PRUH1V
WKHPLVVLQJ$3V IRXQG"
5HFRUGWKH
ORFDWLRQRIWKH <HV
IDXOW\$3V
$UH *RWRWKHDFFHVV
'R
,V DOO$3VFRQQHFWHG FORVHWWR
WKHVZLWFK 5HVHWWKHVZLWFK
RQO\RQH$3 1R WRWKHVDPHVZLWFK <HV LQYHVWLJDWHWKH 1R
/('VVKRZ DQGUHWHVW
IDXOW\" FORVHWRUSRZHU DSSOLFDEOH
DFWLYLW\"
VXSSO\" FRPSRQHQW
<HV <HV
1R
*RWRWKHDFFHVVFORVHW
DQGUHVHWSRZHUWRWKH
$3E\GLVFRQQHFWLQJ
DQGUHFRQQHFWLQJWKH
DSSURSULDWHSDWFKFDEOH
WRWKHSDWFKSDQHO:DLW
DWOHDVWWZRPLQXWHV
7HVWWKHWZRSDWFK
FRUGVWKDWFRQQHFWWKH
,V VZLWFKDQGWKHSDWFK
5HPRYHDQG &KHFNWKH'&
WKHHUURU SDQHOV,QDGGLWLRQWHVW
UHSODFHWKHIDXOW\ SRZHUDWWKHFORVHW
PHVVDJH 1R WKHFDEOHUXQIURPWKH
$3:DLWDWOHDVW DQGDWWKH$3HQG
FOHDUHG" SDWFKSDQHOWRWKH$3
WZRPLQXWHV
$OVRFKHFNWKHVZLWFK
SRUWE\SOXJJLQJLQWRWKH
EDFNXSSRUW
<HV
(QG %HVXUHWRXSGDWH
'R
WKHGHYLFHPDVWHU ,VWKH'&
WKHFDEOHVSDVV <HV
<HV ZLWKWKHQHZ$3,' SRZHURN"
WKH&$7
QXPEHUV
WHVW"
1R 1R
,V
WKHHUURU
,VRODWHDQGUHSDLURU 5HSODFHWKH
PHVVDJH 1R
UHSODFHWKHIDXOW\ SRZHUVXSSO\
FOHDUHG"
FDEOHVHJPHQW
<HV
,V ,V
WKHHUURU WKHHUURU &RQWDFW*(
PHVVDJH 1R (QG <HV PHVVDJH 1R WHFKQLFDOVXSSRUW
FOHDUHG" FOHDUHG" DW
<HV
6080

Troubleshooting
AP error message - AP Config mismatch
5HERRWWKH
$3
,V
&RQWDFW*(
WKHSUREOHP
(QG <HV 1R WHFKQLFDOVXSSRUW
IL[HG"
DW
609

Troubleshooting
AP error message - No valid sequence table/sequence table

mismatch
5HERRWWKH
$3
,VWKH
,V
VHTXHQFHWDEOHRQ
(QG <HV WKHSUREOHP 1R
WKH'HYLFHPDVWHU
IL[HG"
YDOLG"
<HV 1R
&KHFNWUDQVFHLYHUVDQG
UHORDGWKH5)ILUPZDUH
DQGVHTXHQFHWDEOHRQ
WKHRIIHQGLQJWUDQFHLYHU
,V &RQWDFW*(
WKHSUREOHP 1R WHFKQLFDOVXSSRUWDW
IL[HG"
<HV
(QG
The device master refers to the Device Master in the OpenNet Expert application.
Refer to the OpenNet User’s Guide for details. See Related manuals on page 1-3.
610

Troubleshooting
AP error message - AP hardware type mismatch
$UHWKH
YHUVLRQV
1R <HV
)LUPZDUH
DQG5)"
5HORDG 5HERRWWKH
ILUPZDUH $3
,V
(QG <HV WKHSUREOHP
IL[HG"
1R
5HSODFHWKH
$3
<HV
,V
WKHSUREOHP
IL[HG"
1R
&RQWDFW*(
WHFKQLFDOVXSSRUW
DW
The AP hardware type mismatch error is displayed with a V on he AP Diagnostics screen.
Refer to the OpenNet User’s Guide for details. See Related manuals on page 1-3.
The device master refers to the Device Master in the OpenNet Expert application.
611

Troubleshooting
Sync Errors
AP error - No sync on AP error
'LVSOD\WKH$36WDWLVWLFV
VFUHHQLQ:HEPLQRUWKH
$3'LDJQRVWLFVVFUHHQLQ
3DWLHQW1HW9HULI\LIWKHUH
LVRQHRUPRUH1VLQWKH
$3V\QFFROXPQ
$UHWKHUH &RQWDFW*(
RQHRUPRUH1V 1R WHFKQLFDOVXSSRUW
IRXQG" DW
<HV
*RWRWKHGLVWULEXWLRQ
FORVHWWKDWFRQWDLQVWKH
6\QFPDVWHU9HULI\WKDW 'RDOO ,VWKH See No sync - A
DOOFRQQHFWLRQVDUHLQWDFW <HV $3V\QFHQWULHV 1R HUURULQRQO\ <HV (One AP) on
DQGWKDWWKHSRZHULVRQ VKRZ1" RQH$3"
WKHQUHF\FOHSRZHUWRWKH page 7-18.
6\QFPDVWHU
1R
,VWKH ,VWKHUHD
See No Sync - B
HUURUPHVVDJH <HV (QG SDWWHUQPRUH <HV (Multiple APs) on
FOHDUHG" WKDQRQH" page 7-19.
1R
1R
6ZLWFKWRWKH
EDFNXS6\QF
PDVWHU
,VWKH &RQWDFW*(
HUURUPHVVDJH 1R WHFKQLFDOVXSSRUW
FOHDUHG" DW
<HV
(QG
A branch of the AP Sync tree is a group of one to six APs that are connected to the same Sync Out group of ports on a particular Sync
Distribution point.
Refer to the system design package to determine if the failing group of APs are connected to the same AP Sync tree.
613

Troubleshooting
No sync - A (One AP)
5HYLHZWKHV\VWHP
GHVLJQSDFNDJHRU
GHYLFHPDVWHUGDWDEDVH
WRGHWHUPLQHWKH
ORFDWLRQRIWKH
DSSOLFDEOH$3DQGLWV
FORVHWIHHG
,QWKHFORVHWWKDWIHHGVWKH$3LQ
TXHVWLRQUHVHDWDOOSDWFKSDQHO
FRQQHFWLRQVE\GLVFRQQHFWLQJDQG
UHFRQQHFWLQJWKHSDWFKFDEOH5H
VHDWWKH(WKHUQHWFRQQHFWLRQV
ODVWZKLFKUHVHWVWKH$3
:DLWRQHPLQXWH
5HSODFHWKH ,VWKH
DSSOLFDEOHSDWFK 1R HUURUPHVVDJH
FRUGV FOHDUHG"
<HV
,VWKH
HUURUPHVVDJH <HV (QG
FOHDUHG"
1R
5XQDFDEOHVFDQ
ZLWKDFDEOH
DQDO\]HUDQG
UHSDLUDVQHHGHG
,VWKH
HUURUPHVVDJH <HV
FOHDUHG" <HV
1R
8SGDWHWKHGHYLFH ,VWKH
5HPRYHDQGUHSODFH
PDVWHUZLWKWKH HUURUPHVVDJH
WKHIDXOW\$3
QHZ$3,'QXPEHU FOHDUHG"
1R
&RQWDFW*(
WHFKQLFDOVXSSRUW
DW
614

Troubleshooting
No Sync - B (Multiple APs)
5HYLHZWKHV\VWHPGHVLJQ
SDFNDJHRUGHYLFHPDVWHU
GDWDEDVHWRGHWHUPLQHWKH
FORVHWDQGV\QFGLVWULEXWLRQ
SDQHOSRUWVWKDWVHUYHWKH
$3VWKDWDUHGLVSOD\LQJ1
*RWRWKHFORVHWDQGIROORZ
WKH$3WURXEOHVKRRWLQJ
SURFHGXUH
:DVWKH$3
See No sync - A
SUREOHPVRXUFH <HV (One AP) on
ORFDWHG" page 7-18.
1R
5HPRYHDQGUHSODFH
WKHPHGLDFRQYHUWHU
DQGSRZHUVXSSO\WKDW
VHUYHVWKHIDXOW\$3
V\QFEUDQFK
,VWKH
HUURUPHVVDJH <HV
FOHDUHG"
1R
5HPRYHDQGUHSODFHWKH
FRQQHFWLQJPHGLD
FRQYHUWHULQWKH
GLVWULEXWLRQFORVHWWKDW
VHUYHVWKHIDXOW\$3V\QF
EUDQFK
,VWKH
HUURUPHVVDJH <HV (QG
FOHDUHG"
1R
5HPRYHDQGUHSODFH
WKHV\QFGLVWULEXWLRQ
SDQHORUV\QFEXVDV
DSSURSULDWH
&RQWDFW*( ,VWKH
WHFKQLFDOVXSSRUW 1R HUURUPHVVDJH <HV
DW FOHDUHG"

Troubleshooting
CIC Pro or ATS
No device master found
*RWRWKH&,&3UR
RUWKH$76WKDWLV
DFWLQJDVWKH
GHYLFHPDVWHU
'LVDEOHWKHGHYLFH ,VWKH
,VWKH (QDEOHWKH
PDVWHU&,&3UR$76 &,&3UR$76
&,&3UR$76 GHYLFHPDVWHU
*RWRDQRWKHUV\VWHP 1R8QNQRZQ <HV HQDEOHGDVWKH 1R
ZRUNLQJ RQWKH&,&
DQGHQDEOHWKHGHYLFH GHYLFH
SURSHUO\" 3UR$76
PDVWHUVHWWLQJ PDVWHU"
<HV
5HDVVLJQWKH
9HULI\WKHFRUUHFW ,VWKH
SDWLHQWVRQWKH
,3DGGUHVVHVRQ 1R HUURUPHVVDJH
IDLOHG&,&3UR$76
DOORIWKH&,&3URV FOHDUHG"
WRWKHQHZV\VWHP
<HV
'LVDEOHWKHGHYLFHPDVWHU (QG
VHWWLQJRQWKHEDFNXS&,&
3UR$765HWXUQWRWKH
RULJLQDOV\VWHPDQG $UHDOO
HQDEOHWKHGHYLFHPDVWHU RIWKH,3
VHWWLQJ <HV
DGGUHVV
FRUUHFW"
1R
,VWKH
&RQWDFW*(
HUURUPHVVDJH 1R
7\SHWKHFRUUHFW,3 WHFKQLFDOVXSSRUW
FOHDUHG"
DGGUHVVHVRQDOORI DW
WKH&,&3URV
<HV
(QG
,VWKH
HUURUPHVVDJH 1R
FOHDUHG"
<HV
(QG
To access the device master status, start the Webmin interface, select the Others tab, and select Master Designation.
612

Troubleshooting
CIC Pro event log error messages

Event Log Messages for ApexPro FH Telemetry Systems (VTOR)
Message
Error Log Message Displayed Text Description
Code
1 EC_DEV_MASTER_DUP Multiple Device Masters Displayed when more than one Device Master
is configured on the network.
2 EC_DEV_MASTER_NONE No Device Master Displayed when no Device Master is

configured on the network.
3 EC_AP_ERROR Access Point Error IP Displayed when an AP sends a packet that

contains invalid formatting or invalid
protocol versions.
4 EC_AP_NO_SYNC No Sync on Access Displayed when any AP on the network reports

Point that it is not synchronized.
5 EC_DEV_MASTER_VER Device Master Version Displayed when a Device Master protocol

Mismatch version is mismatched.
6 EC_AP_NO_RESPONSE No Response from Displayed when a status message from the AP

Access Point has not been received within the
AP_NO_RESPONSE_TIMEOUT.
7 EC_AP_NO_CONFIG AP not configured Displayed when an AP is detected on the

network, but it is not configured to the Device
Master.
8 EC_DEFAULT_IPADDR Default IP Address Displayed when the CIC Pro has an IP

Address that matches the default IP Address.
9 EC_DM_HARDWARE_MISMAT AP Hardware type Displayed when an AP reports its hardware

CH mismatch type to be something that is different than the
hardware type that is configured in the Device
Master.
10 EC_DM_CONFIG_MISMATCH AP Config Displayed when an AP reports a sequence

mismatch table crc that is different than the one that is set
by the Device Master.
11 EC_DM_NO_SEQUENCE_TBL NO valid sequence table Displayed when the Device Master detects that
at least one sequence table does not exist.
12 EC_INCOMPATIBLE_DEVICE Incompatible Device Displayed when an incompatible device is

detected on the OpenNet LAN.
Enterprise Access infrastructure troubleshooting

NOTE
Start with the Antenna system troubleshooting tree on page 7-2.
Perform the following procedure on the Enterprise Access equipment.

Troubleshooting
Troubleshooting tree
Problem isolated
to the Enterprise
Access
Infrastructure
Perform the
General Fault
Isolation
procedure in this
chapter.
Refer to the appropriate

Is the
module in the
problem with a Does this solve
Yes Component Yes Done!
particular the problem?
Troubleshooting section
module?
of this chapter.
No No
Perform the Visual

Call Technical Support at
Inspection
1-800-558-7044.
procedure in this
chapter.
Does this solve

Yes Done!
the problem?
No
Call Technical Support

at 1-800-558-7044.
602
General fault isolation

Perform the following steps:
1. Log into the NMS to perform a quick check of the GE Enterprise Access system.
(The NMS will provide a snapshot of the system and any potential component
failures will be immediately visible.)
a. Check if there are any minor or major alarms.

Troubleshooting
If there is a minor or major alarm, drill down to determine which component

is alarming and refer to the troubleshooting table for that particular
component.
b. Click on Events at the top right of the NMS GUI to display a list of events.
See Events on page 7-27 for a description of the events.
2. If MA 330 modules are present in the install, use the MA 330 GUI application to
log into the MA 330 system. See MA 330 System troubleshooting on page 7-29.
3. Perform the Visual inspection on page 7-33.
For additional assistance, call GE Technical Support at 1-800-558-7044.
NMS System troubleshooting

Connecting to the NMS server application
The Enterprise Access system is controlled from any client (PC/laptop) by connecting
to the server on which the NMS Server application is installed. For the connection to
be implemented, the NMS Server application must be launched on the server. Launch
the NMS 430 Server application by double-clicking on its icon.
NOTE
The text window running in the background is the normal status of the
application. Closing it closes the Server application.
The system can be monitored from any client (PC/laptop) connected to the network
on which the server is running the NMS server application.
Run a Web Browser (be sure Java VM is installed on the client PC/laptop) and
type the IP Address of the server. It typically takes about 30 seconds to download
the application to the client. The Login dialog appears.
In the User Name drop-box, select the access level and type the corresponding
Password. Three access levels with default passwords are provided. The login
levels are:
504
Operator (default password oper) - provides read-only options of all the
fields.

Troubleshooting
Field Engineer (default password eng) - enables full customer read-write

control in all fields.
Technical Support - access restricted to GE engineering personnel.
Click Connect. You will be connected to the NMS Manager application on the
server.
Alternatively, a PC/laptop can be directly connected to the NMS controller and the
NMS MCT can be used to access the GE Enterprise Access system.
Serial connection to the NMS controller via the MCT

To connect to the controller locally, follow this procedure.
1. Connect the computer on which the MCT application is installed to the RS232
card connector using a 9-pin male serial cable, as illustrated below.
505
2. Launch the MCT application by double-clicking on the MCT icon on the
desktop.
3. To access the MCT screen select the User Name Operator and type the default
password oper.
4. Select the Comm Port according to the communication port to which your
computer is connected.
5. Click Connect. The MCT main window appears.
NMS System health check - NMS server and NMS MCT application
Once the connection to the GE Enterprise Access system is made using the NMS
server or NMS MCT application, it is possible to check the general health of the MS
and ApexPro CH systems.

Troubleshooting
506
In the above illustration, notice that base of the tree is red. In this particular example,
this has occurred because an RHU at the upper level of the tree has disappeared. Prior
to completing the commissioning of the system a base line is set. This records the
hardware present in the system. Hardware that is later not sensed is displayed in gray.
Invoking configuration dialogs from the topology tree

All device configuration dialogs may be invoked from the topology tree by clicking
on the appropriate items. This includes the configuration dialogs for the 410/430
controller, BTSC (RIU), OPTM (BU), RHU and Add-on unit (MA1200).
Tree colors
Faults are propagated only through an arrow shown in the GUI tree so that the faulty
device can be quickly identified by its color. The tree colors indicate the status of the
elements:
Color Indicates
Green Ok
Yellow Minor error
Red Major error
Gray No communication to a (Enterprise Access) device set in

Base-Line. If communication to a device that was not set in
Base-Line is lost, the device disappears from the display.
Blue Version incompatibility (device version 3.0 and host

controller version 3.1)
NOTE
If components appear gray in the GUI, ensure that they are properly connected
before proceeding with troubleshooting.
If components do not appear at all, the baseline may not have been configured.
Proceed with troubleshooting and once finished and components appear set a
baseline for future use.

Troubleshooting
Error logs
Communication with hardware can be lost due to a fiber break or malfunctioning
hardware. Click on the Events link on the GUI to check the error logs for the system.
507
Sort the events by Time & Date in descending order. The most recent events are
probably related to your system failure.
508
The errors and problems commonly encountered by each of the GE Enterprise Access
components is described in the troubleshooting tables that follow.

Troubleshooting
Events
The following table gives a brief description of the events that may be encountered.
Trap name Severity Description
NMS 430 or NMS 410 controller
controllerFirstRun Notify The controller has started up for the first time.
controllerPowerUp Notify The controller has been powered up.
controllerSlaveLost Major The master controller has lost communication with a slave controller.
controllerSlaveRecovered Notify The master controller has re-established communication with a slave controller.
auxiliaryInputNormal Notify There are no abnormal conditions for the auxiliary inputs.
auxiliaryInputAlarm Major An auxiliary input alarm has been triggered.
tunnlingAgentStarted Notify The NMS MCT application has started communicating with the controller.
tunnlingAgentEnded Notify The NMS MCT application has stopped communicating with the controller.
BTS or BDA conditioner
btscDetected Notify A BTSC has been detected in the system.
btscDisconnected Major A BTSC is no longer detected by the system.
btscRfLow Major The RF downlink signal inputted into the BTSC is too low to detect.
btscRfNormal Notify The RF downlink signal inputted into the BTSC is within the allowable range.
btscRfOverload Minor The RF downlink signal inputted into the BTSC is above the allowable range.
btscRfNoOverload Notify The RF downlink signal inputted into the BTSC has gone from overload to within the
allowable range.
btscRfSwOff Major The BTSC amplifier is off and will not output downlink signal.
btscRfSwOn Notify The BTSC amplifier is on.
btscWetAdjust Notify The BTSC was last adjusted with a live downlink signal.
btscDryAdjust Notify The BTSC was last adjusted with an emulated signal.
btscAdjustFailed Minor The last adjustment on the BTSC failed.
btscRestoreFacDef Notify The BTSC settings were set to factory default.
Base Unit (BU)
optmDetected Notify A BU has been detected in the system.
optmDisconnected Major A BU is no longer detected by the system.
optmRfLow Major The RF downlink signal inputted into the BU is below the allowable range.
optmRfNormal Notify The RF downlink signal inputted into the BU is within the allowable range.
optmRfHigh Minor The RF downlink signal inputted into the BU is above the allowable range.
optmRestoreFacDef Notify The BU settings were set to factory default.

Troubleshooting
optmUILock Minor The BU uplink communication with the RHUs has been established.
optmUIUnlock Major The BU uplink communication with the RHUs has been lost.
optmDlLock Major The BU downlink communication with the RHUs has been established.
optmDlUnlock Major The BU downlink communication with the RHUs has been lost.
WMTS or Mobile Service RHU
rhuDetected Notify An RHU has been detected in the system.
rhuDisconnected Major An RHU is no longer detected by the system.
rhuAntennaChanged Major The status of an antenna on the RHU has changed.
rhuFirstBandAdjust Notify The last adjustment on the RHU first band succeeded.
rhuFirstBandAdjustFailed Minor The last adjustment on the RHU first band failed.
rhuSecondBandAdjust Notify The last adjustment on the RHU second band succeeded.
rhuSecondBandAdjustFailed Minor The last adjustment on the RHU second band failed.
rhuFirstBandOff Major The first band in the RHU has been turned off.
rhuFirstBandOn Notify The first band in the RHU has been turned on.
rhuSecondBandOff Major The second band in the RHU has been turned off.
rhuSecondBandOn Notify The second band in the RHU has been turned on.
rhuNoOpticalLevelOnUL Major There is no optical uplink connection.
rhuLowOpticalLevelOnUL Minor The quality of the optical uplink connection is poor.
rhuNormalOpticalLevelOnUL Notify The quality of the optical uplink connection is within the allowable range.
rhuNoOpticalLevelOnDL Major There is no optical downlink connection.
rhuLowOpticalLevelOnDL Minor The quality of the optical downlink connection is poor.
rhuNormalOpticalLevelOnDL Notify The quality of the optical downlink connection is within the allowable range.
MA 1200 Add-on
addonDetected Notify A MA-1200 Add-on has been detected in the system.
addonDisconnected Major A MA-1200 Add-on is no longer detected by the system.
addonAdjust Notify The last adjustment on the MA-1200 Add-on succeeded.
addonAdjustFailed Minor The last adjustment on the MA-1200 Add-on failed.
addonBandOff Major The band in the MA-1200 Add-on has been turned off.
addonBandOn Notify The band in the MA-1200 Add-on has been turned on.
RIM 1400
rim1400Detected Notify A RIM 1400 has been detected in the system.

Troubleshooting
rim1400Disconnected Major A RIM 1400 is no longer detected by the system.
rim1400SynthUnlock Major The synthesizer in the RIM 1400 is not locked.
rim1400SynthLock Notify The synthesizer in the RIM 1400 is locked.
rim1400intRefFailure Major The internal reference signal in the RIM 1400 is not within the allowable range.
rim1400intRefOk Notify The internal reference signal in the RIM 1400 is within the allowable range.
rim1400extRefMissing Minor There is no external reference signal detected by the RIM 1400.
rim1400extRefExist Notify The external reference signal is detected by the RIM 1400.
rim1400maintRequired Minor The maintenance time of the RIM 1400 has expired - if set appropriately, the
calibration procedure for the RIM 1400 should be performed.
rim1400mainDone Notify The maintenance time of the RIM 1400 has been reset.
rim1400adjFail Minor The rough adjustment of the internal reference frequency of the RIM 1400 has failed.
rim1400adjSuccess Notify The rough adjustment of the internal reference frequency of the RIM 1400 has
succeeded.
rim1400multiMasters Minor More than one RIM 1400 is functioning as master.
rim1400configOK Notify The RIM 1400 configuration is okay.
rim1400driftDetected Major The internal reference of the RIM 1400 has drifted out of the allowable range.
rim1400refAligned Notify The internal reference of the RIm 1400 is now within the allowable range.
WMTS-SHU-4
wmtsshuSystemOnNotify Notify The WMTS-SHU-4 is powered up.
wmtsshuAntenaConnectedNotify Notify An antenna has been connected to the WMTS-SHU-4.
wmtsshuAntenaDisconnectedNotify Notify An antenna has been disconnected from the WMTS-SHU-4.
wmtsshuAPConnectedNotify Notify An AP has been connected to the WMTS-SHU-4.
wmtsshuAPDisconnectedNotify Notify An AP has been disconnected to the WMTS-SHU-4.
wmtsshuAMPRecoveredNotify Notify One of the AMPs has recovered.
wmtsshuAMPFailedNotify Notify One of the AMPs has failed.
MA 330 System troubleshooting

The MA 330 Setup and Adjustment Tool is an intuitive GUI-based software
application that enables end-to-end configuration and monitoring of the MA 330
system through a local connection to either the MA 330 Main or MA 330 Remote unit
of the same link.
The application is supplied on a CD with your installation kit.

Troubleshooting
Installing the MA 330 GUI application

There are four directories on your Installation CDs. In the Customer GUI directory,
double-click MA 330_x_x_x.exe and follow the installation instructions.
Connecting to the MA 330 GUI application

To connect to the MA 330 modules, follow this procedure:
1. Using the supplied Installation CD, install the MA 330 GUI on the computer
(usually a laptop) from which the adjustment procedure will be performed.
2. Connect a standard RS232 cable between the RS232 port on the MA 330 Main or
Remote front panel and the RS232 port on your computer.
620
3. Launch the MA 330 GUI application by double-clicking on the MA 330 icon on
your desktop.
4. To access the MA 330 GUI, select Field Eng from the User Level drop-down
list, and type the default password eng.
5. Select the Comm. Port according to the communication port to which your
computer is connected.
6. Click Login. The MA 330 GUI main window appears.
MA 330 System health check

The MA 330 setup application may be used to monitor the fiber link and connectivity
status.

Troubleshooting
621
Parameter Description
Device Status Unit operational status and error indication:
Normal - No errors detected

Minor - minor error detected
Major - major error detected
Opt. Adj. Status Status of optical adjustment procedure:
Success - Procedure performed successfully

Fail - Adjustment procedure failed
Default - Adjustment procedure not performed
COMM Status Corresponds to COM LED on the front panel. Status of

communication between Remote and Main measured
according to the (MER) Message Error Rate:
OFF - No communication detected

ON - Communication Ok
Partial - Communication fault
Pdet Band Shows the band at which the RF power readings (power
detection) are performed
If there are any minor or major errors, or the COMM status for live fiber links are not
ON, contact GE Technical Support at 1-800-558-7044.

Troubleshooting
WMTS-SHU-4 system troubleshooting

Overview
The WMTS-SHU-4 web GUI is an intuitive interface that allows remote or onsite
configuration and monitoring of the WMTS-SHU-4 units.
NOTE
This should be accessed from the site server on the IX network. If the site server
is down, this application can be run from a laptop. Connect the laptop directly to
the WMTS-SHU-4 unit using a crossover cable. Do not put the laptop on the IX
network as this could introduce viruses onto the network.
Connecting to the WMTS-SHU-4 web GUI

For information on how to logon to the WMTS-SHU-4, See WMTS-SHU-4
monitoring and configuration on page 2-35. An IP address must first be assigned to
the unit before you will be able to connect to it.
WMTS-SHU-4 system health check

The WMTS-SHU-4 provides the following alarms, which may be viewed by clicking
the Alarms tab of the Control window.
Monitoring function Description
Antenna connection status Antenna sense for the corresponding channel, where:
Green – antenna connection detected

Red – antenna not detected
Grey – antenna is set to Disable
AP status Green – AP detected

Red – AP not detected at a port designated for an AP
connection according to the configuration
Grey – configuration does not require an AP at that port
AMP status Status for the corresponding channel:
Green – channel ok
Red – channel failure

Troubleshooting
290
Visual inspection
A thorough visual inspection of the equipment can save time. Small things -
disconnected cables, foreign debris on circuit boards, missing hardware, loose
components - can frequently cause symptoms and equipment failures that may appear
to be unrelated and difficult to track.
It is highly recommended that the following steps be performed to remove these

failures as causes of problems.
1. Ensure that power cords are properly plugged into working wall outlets and
securely connected to all the GE Enterprise Access components.
2. If UPS devices are used, ensure the UPS devices are functioning properly, are
plugged into working wall outlets, and are properly connected to all the GE
Enterprise Access components.
3. The green power LED on the RIU, BU, RHU and MRC should be lit, indicating
that the components are powered ON.
4. Ensure that proper cabling is used (coaxial, fiber and network) and that all cables
are properly connected to the RIU, BU, RHU, NMS 430/410 and MRC
(MA2000).
See Interconnecting Enterprise Access components on page 3-6.
5. Verify that there are no fault LEDs in the ON state. If a fault LED is on, refer to
the troubleshooting tables for that particular component.
Take the time to make all the recommended visual checks (refer to the visual
inspection table below) before starting any detailed troubleshooting procedures.

Troubleshooting
Visual inspection table
Area Look for the following problems
I/O Connectors and Interface Cables

Fraying or other damage
Bent prongs or pins
Cracked housing
Loose screws in plugs
Excessive cable tension or wear
Secure mounting hardware
Loose connection
Strain reliefs out of place
Ground Wires/Wiring Loose wires or ground strap connections
Faulty wiring
Wires pinched or in vulnerable position
Mounting Hardware
Loose or missing screws or other hardware fasteners
Components mounted loosely or near vibration
Power Source
Faulty wiring, especially AC outlet
Circuit not dedicated to system
Static discharge, resetting problems, and noise resulting from power source problems
Component troubleshooting
In each troubleshooting section for the different Enterprise Access components, the
corrective actions are listed in the order in which they are recommended to be
performed.
RIU troubleshooting
Refer to this section if the problems being experienced are related to mobile services
(cell phone coverage, SMR/Paging services, etc.).

Troubleshooting
Problem/ observation Possible cause/ corrective action
The Power LED is not lit on

the RIU
Troubleshoot the power source.
If 20 - 48 VDC is measured at the green power

connector, then the power source is not the issue.
Replace the RIU Unit.
If power is low or not registering on the voltage meter,

replace/check the power wiring.
Continue to troubleshoot this problem until the module

in question has a green power LED indication.
BTS Conditioners do not

have a flashing Green “run”
LED
If permission can be obtained to cycle power on the

RIU, recycle power to the RIU.

If recycling power to the RIU does not fix the problem,

reseat the BTS conditioner.
If reseating the BTSC does not fix the issue and if the
power source does not seem to be the problem, then
replace the BTSC unit that does not have a flashing
green LED.

The RED DL overload LED

is flashing on any one of the
Verify with an RF power meter that the input into the
BTS conditioner BTS conditioner is between 10 - 36 dBm.
If the signal is greater than 36 dBm, use a high power

RF attenuator to reduce the power level of the signal.
Contact the GE Technical Support.
If the signal as measured is below 36 dBm, replace the

BTS conditioner.

Troubleshooting
The RED DL Low signal is

flashing on any one of the
For the conditioner that is displaying a RED LED
remove the RF input and verify with an RF power meter
BTS conditioner
that the input into the BTS conditioner is between 10 -
36 dBm.
If the signal is less than 10 dBm, the problem is related

to the Cellular Service Provider's equipment or signal.
Contact the appropriate Cellular Service Provider.
If the signal as measured is between 10 - 36 dBm,

replace the BTS conditioner.
The system is experiencing

mobile services uplink
Using your RF power meter, start working every RF
uplink cable towards the BTS in order to determine
issues
where the loss of RF is occurring.
Suspect a bad RF cable or jumper or a bad BTS

conditioner. Verify the RF cable between the BTS
conditioner uplink port and the BTS.
If the RIU or one of the BTSCs is replaced, a re-commissioning of the system may be
required. Contact the GE Technical Support.
RIM Main and WMTS troubleshooting

Refer to this section if the problems being experienced are related specifically to
WMTS (ApexPro CH) coverage.
Power LED is not lit on the

RIM Main

Replace the RIM Main.


WMTS issues are being

experienced in the entire
Issue is potentially a faulty RIM Main (or RIM 1400 if
designated WMTS only the 1395-1400 MHz band is affected). Check for
the uplink signal coming out of the back of the RIM
coverage area
(before it feeds into the RIM Expansion). If the BU is
working and receiving an uplink signal and the RIM
Main is not, consider replacing the RIM Main.
Check the ApexPro CH receiver sub-system that is

servicing the coverage area. Refer to the ApexPro
troubleshooting information to isolate the problem.
Check RIM Main Power LED and RUN LED status.

Troubleshooting
Only certain areas of the

designated WMTS
Check for a potentially faulty antenna in the area that is
experiencing WMTS issues. See Antenna and RF
coverage areas are
experiencing issues troubleshooting on page 7-42.
The problem could also be due to a faulty RHU that is

covering the coverage area in question. See RHU
troubleshooting on page 7-40.
If the problem is specific to a transmitter, try swapping

to a different transmitter. Refer to the ApexPro CH
troubleshooting information to further troubleshoot
transmitter issues.
Run LED is not flashing Indicates that the RIM Main Unit processor is not running.
RIM 1400 troubleshooting
Power LED is not lit on the

RIM 1400



The MASTER-CONFIG Two RIM 1400s may be forced to master. Using NMS, verify
LED is lit on more than one that the Auto Mode on the Synchronization tab for each
RIM 1400 and/or the RIM 1400 is set to Automatic. Also, verify that only one RIM
rim1400mulitMasters 1400 has Master in the Define field.
event has been recorded in
the NMS application.
The MASTER-CONFIG Using NMS, verify that the Auto Mode on the
LED is not lit on any of the Synchronization tab for each RIM 1400 is set to
RIM 1400s Automatic. Also, verify that only one RIM 1400 has Master
in the Define field.
A rim1400driftDetected One or more of the RIM 1400s has drifted out of the
event has been recorded in specified frequency range. Perform the RIM 1400 calibration
the NMS application. procedure on all of the RIM 1400s. See RIM 1400
Calibration on page 6-5.
A rim1400maintRequired It is time to calibrate the RIM 1400s, ApexPro CH receiver

event has been recorded in sub-systems, and the CARESCAPE T14 transmitters.

Troubleshooting
A rim1400SynthUnlock
The RIM 1400 with this event should not be functioning
as master. Verify that this is the case and then cycle
power to the unit.
If the event does not clear, replace the RIM 1400

module. The event clearing is determined by seeing a
rim1400SynthLock event for the RIM 1400.
A rim1400intRefFailure
power to the unit.

rim1400intRefOk event for the RIM 1400.
A rim1400extRefMissing
Verify that the REF INPUT and OUTPUT connections
the NMS application. are correct on all the RIm 1400s. Swap cables to check
for a bad jumper.

power to the unit.

rim1400extRefOk event for the RIM 1400.
A rim1400adjFail event has This indicates that a rough adjustment of the internal
been recorded in the NMS frequency reference on the RIM 1400 failed. Consider
application. performing the RIM 1400 calibration procedure on all of the
RIM 1400s. See RIM 1400 Calibration on page 6-5.
BU troubleshooting
(cell phone coverage, SMR/paging services, etc.) or to WMTS (ApexPro CH) issues
that are experienced over a large part of the designated coverage area.

Troubleshooting

the BU

Replace the BU.


Is the LSR LED green for a If one or both LEDs are out, replace the BU.
4-port BU, or both LSR
LEDS green for an 8-port
BU?
The NMS controller is

reporting a “RF Low on the
Verify that an RF downlink signal is entering the BU.
This can be done using a network controller.
OPTM” alarm
An RF analyzer can also be used to verify that the
cable attaching to the DL port of the BU is carrying an
active RF signal.
If your RF DL signal is missing at the input to the BU,

start working backward using your RF power meter.
If the DL low signal red LED on the front of the BTS

conditioner was not illuminated (as described in the
RIU Troubleshooting table previously), then the
problem is between the BTS conditioner cables on the
front of the RIU and the BU.
The system is experiencing

mobile services or WMTS
Using an RF power meter, verify if you are getting an
uplink issues RF uplink signal out the back of the BU.
Use a spare uplink and downlink port on the BU to

switch the RHU that is causing the loss in coverage. If
switching to a different port fixes the issue, consider
ordering a spare BU to replace the BU with the bad
uplink/downlink ports.
The Link LED is flashing

periodically on the BU
The LED will flash on and off when the optical loss is
too high but still have a laser input powerful enough to
be detected.
Loss should be measured using a source and Optical

Power Meter (OPM). Fiber loss from end to end should
not exceed 3.0 dB.
If the fiber loss is too high, cleaning the male and

female portions of the fiber often fixes this problem.

Troubleshooting
The RHU Link LED and BU

Link LED (for the respective
The fibers are likely not properly connected (swapped).
port) both are not green

Clean and swap the fibers on one side of the link.
The Link LED on the BU is

not on for a particular RHU
Verify the fiber is good between the BU and RHU.
connection
Clean the fiber from the RHU.
If the fiber from the RHU has a signal on it, then the
problem is potentially due to a faulty BU; consider
replacing the BU.
RHU troubleshooting
(cell phone coverage, SMR/paging services, etc.) or to WMTS (ApexPro CH) issues
that are experienced only in a certain parts of the designated coverage areas.
An RHU that was present

earlier (set in the baseline)
Power cycle the RHU. Check to see if the NMS can
now communicate with the RHU.
is no longer visible from the
NMS (displayed in “grey”
color) Clean the uplink and downlink fiber from the problem
RHU to the BU. Clean both the fiber bulkhead and the
single-mode connectors at the end of each cable.
Check to see if the NMS can now communicate with
the RHU.
With permission from the hospital staff, power cycle the

BU that is connected to the problem RHU.
If this does not fix the problem, test both the uplink and
downlink fiber optic cable with an optical power meter
to ensure that the end-to-end loss is no more than
2.5db.

the RHU

Replace the RHU.



Troubleshooting
The Link LED is flashing

periodically on the RHU
The LED will flash on and off when the optical loss is
too high but still have a laser input powerful enough to
be detected.
Loss should be measured using a source and Optical

Power Meter (OPM). Fiber loss from end to end should
not exceed 3.0 dB.
If the fiber loss is too high, cleaning the male and

female portions of the fiber often fixes this problem.
The RHU Link LED and BU

Link LED (for the respective
The fibers are likely not properly connected (swapped).
port) both are not green

Clean and swap the fibers on one side of the link.
The COMM port on the

RHU is not green
Verify the fiber is good between the BU and RHU.
Clean the fiber from the BU.
If the fiber from the BU has a signal on it, the RHU

could be potentially faulty. Consider replacing the RHU.
The COMM LED on the

RHU is periodically flashing
Reset power on both the BU and RHU.
green
If there is a spare port on the BU, switch the RHU to the
spare BU port.
If switching to a different BU port fixes the problem,

consider ordering a spare BU to eventually replace the
BU with the bad uplink/downlink ports.
If switching to a different BU port does not fix the

problem, it could potentially be a faulty RHU; consider
replacing the RHU.

Troubleshooting
WMTS-SHU-4 troubleshooting
Problem/observation Possible cause/ corrective action

the SHU
If 20-48 VDC is measured at the green power

Replace the SHU unit.


The Status LED is not

green on the SHU
For an overview of the alarms in the WMTS-SHU-4
web GUI, refer to WMTS-SHU-4 system health check
on page 7-32. This will be used for the remaining
troubleshooting steps.
Antenna connection
status is red in the WMTS-
Check in the installation documentation to verify that an
SHU-4 web GUI antenna should be connected to the port. If no antenna

is connected to the port per the design documents,
disable the antenna sensing for that port.
Verify that the antenna run has not been compromised

and all cable connection are tight. If the alarm is still
present, suspect the antenna run continuity.
AP status is red in the

WMTS-SHU-4 web GUI
Verify that the AP is powered on and functioning.
Verify that the correct AP to antenna mapping

configuration has been set on the Advanced tab of the
Control window as shown in the design documentation.
AMP status is red in the

WMTS-SHU-4 web GUI
Replace the WMTS-SHU-4 unit.
Antenna and RF troubleshooting

(cell phone coverage, SMR/paging services, etc.), WMTS (ApexPro CH) issues and
WiFi coverage issues that are experienced only in a certain parts of the designated
coverage areas.
This section will aid users in troubleshooting the section from the Remote Hub Unit
(RHU) to the antennas. Since there are multiple combinations of equipment in the
remote locations (i.e., EA-1000 with potential EA-1200 Add-ons in addition to EA-
2000 and Modulite hardware), the troubleshooting procedure will attempt to follow
the signal from the antenna to the RHU. The intent of this section is to use the
downlink signal as a source to isolate the point of failure.

Troubleshooting
Loss of coverage is being

experienced in only certain
Look for loose cables/connectors, as this could be your
problem.
areas
Using an RF spectrum analyzer, identify if any signals

are presently radiating out of the antenna. Stand
directly under the antenna.
Check to see that the spectrum analyzer can detect the

expected signals out of the antenna at greater than -50
dBm of power.
Since you are detecting the RF signals out the

antenna, this antenna appears to be functioning as
expected. Repeat the previous test until you find the
antenna that is not working.
If the coverage area that is experiencing problems has

issues with all services, consider replacing the
antenna.
Coverage area
experiencing problems has
If you have some signals but not others, the coaxial
cable and antennas are likely fine. While a piece of
some of the expected
signals missing coaxial cable could be damaged in such a way to
attenuate some bands but not others, this is unlikely.
Antennas are passive elements. It is unlikely that only
one element of an antenna would fail.
Disconnect the antenna and attach the spectrum

analyzer directly to the RF connector. If signals are
present out of the cable, but are not radiating from the
antenna, then consider replacing the antenna.
If no signals are present on the coaxial cable either,

connect the RHU antenna port at the other end of the
RF cable to the spectrum analyzer. A strong RF signal
(greater than -5 dBm) should be visible at this antenna
port. If the expected signal is present, then replace the
coaxial cable. Otherwise, that particular antenna port of
the RHU could be faulty; consider replacing the RHU or
refer to the RHU Troubleshooting table above to further
troubleshoot the RHU.
Look for loose cables/connectors, as this could be your

problem.

Troubleshooting
All of the signals are The fact that you are missing all of the RF signals out of the
missing in a certain RHU appears to indicate that the RHU has failed. Since
coverage area many different configurations are available, it is important to
work backwards to determine where the RF does exist.
Whatever active component exists between the point of
signal and the lack of signal will be the failed module.
Only some of the signals

are missing in the entire
Use an RF analyzer to determine if you are missing
only WiFi or High Band signals such as PCS, or low
coverage area
band signals such as Cellular and iDEN/Paging.
If you are missing WiFi only, suspect the AP.
If you are missing only high band signals and an EA-

1200 is installed, suspect the EA-1200. Otherwise,
suspect the EA-1000. Low band signals are provided
by the EA-1000.

8 Replaceable parts

Replaceable parts
Enterprise Access models
GE WMTS units
GE FRU part number GE part number Description
2032300-001 EA-WMTS-RU-GECH-4 Dual band WMTS RHU 4-ports
2032300-002 EA-WMTS-RIM-MAIN RX interface module for WMTS SB, 600 Mhz supporting 4 BU 8-ports
2032300-003 EA-WMTS-RIM-EXP-16 16 port WMTS UHF Receiver Interface Module Expansion
2032300-004 EA-ANT-600-6G-OMN Multi-band Antenna 600-5800 MHz
2032300-006 EA-SMU-WM-WF-CL-1 Service Mux Unit for WMTS, Cellular, PCS, WiFi b/g and a 1-port
2032300-008 EA-WMTS-RIM-1400 Receiver interface module that enables the 1395-1400 MHz band
Enterprise Access universal Base Units (1000, 1200, 2000 support)
2029841-001 EA-WB-B8U Wide Band Base 8 Unit supporting 8 RHUs
2029841-002 EA-WB-B4U Wide Band Base 4 Unit supporting 4 RHUs
Enterprise Access 1000 RHUs (ready for add-on units)
2029844-009 EA-1000D-IDEN-SMR4 Dual band- iDEN/SMR, 4-ports
2029844-010 EA-1000-SMR-FILTER Filter kit for SMR 900
2029844-012 EA-1000-CELL-PCS4E Dual band-Cell/PCS, 4-ports
Enterprise Access 1200 RHU
2029869-001 EA-1200-PCS-AO Add-on RHU supporting a PCS service for 1000
2029869-003 EA-1200-PCS-AO-CB Add-on RHU supporting a PCS service for 2000 cabinet
2029869-005 EA-1200-PCS-AO-LT Add-on RHU supporting a PCS service for 2000 Lite

Replaceable parts
Enterprise Access 2000 RHUs (ready for add-on units)
2029871-002 EA-2000-RC-LP Remote Cabinet all services
2029871-003 EA-2000-MINI-ENC 2000 enclosure supporting 2 modules
2029871-006 EA-2000-IDEN-SMR Dual band iDEN/SMR page1 for cabinet
2029871-007 EA-2000-CELL-PCSE Dual Band Cell/PCS 1-port for cabinet
2029871-016 EA-2000-IDEN-SMR-L Dual band iDEN/SMR-Page 1 for Lite
2029871-017 EA-2000-CELL-PCSEL Dual band Cell/PCS 1-port for Lite
Enterprise Access SHU
2032300-007 EA-WMTS-SHU-4 WMTS SHU 4-ports
Enterprise Access 330 system units
2029877-001 EA-330-MB-1 One-link Main Building Unit
2029877-002 EA-330-MB-2 Two-link Main Building Unit
2029877-003 EA-330-RB-1 Remote Building Unit 1 link supporting two BU
2029877-004 EA-330-EXP-BOX Enables support of additional BUs at the Remote location: up to four
8-port BUs, or up to eight 4-port BUs
Enterprise Access network controller models
2029878-001 EA-410 Network controller — Serial Interface (dial-up)
2029878-002 EA-430 Network controller — Ethernet/IP Interface
Enterprise Access Network Management System
2029879-001 EA-NMS-SW-SERVER GUI and server SW package (one per site)

Replaceable parts
Enterprise Access Radio Interface Units (RIU)
2029880-001 EA-RIU-IM Radio Interface Unit
2029880-002 EA-RIU-BTSC-CELL BTS Conditioner for Cellular
2029880-003 EA-RIU-BTSC-IDEN BTS Conditioner for iDEN
2029880-004 EA-RIU-BTSC-PCS BTS Conditioner for PCS
2029880-005 EA-RIU-BTSC-SMR BTS Conditioner for SMR-Paging
2029880-006 EA-RIU-BDAC-CELL BDA Conditioner for Cellular
2029880-007 EA-RIU-BDAC-IDEN BDA Conditioner for iDEN
2029880-008 EA-RIU-BDAC-PCS BDA Conditioner for PCS
2029880-009 EA-RIU-BDAC-SMR BDA Conditioner for SMR-Paging
Other parts
AC/DC converters
2029881-002 EA-LPS-48V-100W Local AC/DC Converter 100W
2029881-001 EA-LPS-48V-66W Local AC/DC Converter 66W
Service Software
2039070-001 CARESCAPE Systems Manager Software CD

A Technical
specifications
2032086-003C Enterprise Access A-1

Technical specifications
Environmental specifications
All Enterprise Access system modules have the following environmental
specifications:
Operating temperature 41º F to 104º F (5º C to 40º C)
Storage temperature -4º F to 122º F (-20º C to 50º C)
Operating humidity 15% to 90%, non-condensing
Storage humidity Up to 90%, non-condensing
Power specifications
The operating voltage and power consumption for the powered Enterprise Access
system modules are listed in the following table.
Operating Power
Module
voltage consumption
WMTS RHU and MA 1000 RHU 20 to 48 VDC 29 watts maximum
MA 2000 RHU 20 to 50 VDC 29 watts maximum
MA 2000 MRC enclosure 90 to 260 VAC 380 watts maximum

@ 47 to 63 Hz
MA 1200 25 to 50 VDC 50 watts maximum
Base Unit 4 and Base Unit 8 20 to 48 VDC 15 watts maximum
RIU (BTSC/BDAC) 20 to 48 VDC 12 watts maximum
RIM Main 20 to 48 VDC 15 watts maximum
RIM 1400 20 to 48 VDC 16 watts maximum
NMS 410/NMS 430 20 to 48 VDC 10 watts maximum
MA 330 MB-1/MB-2 20 to 48 VDC 20 watts maximum
MA 330 RB 20 to 48 VDC 20 watts maximum
SHU 20 to 48 VDC 20 watts maximum
SMU2 port loss

The following table lists the SMU2 loss per port.
600 MHz 800/900 MHz 1400 MHz 1900 MHz 2.4 GHz 5 GHz
2.9 dB 3.8 dB 4.2 dB 4.4 dB 1.9 dB 2.7 dB
A-2 Enterprise Access 2032086-003C

Standards and approvals

The following powered Enterprise Access system modules comply with UL 60950-
1:2003 and FCC part 15:
WMTS RHU, MA 2000 RHU, and MA 1000 RHU

MA 1200
Base Unit 4 and Base Unit 8
RIU (BTSC/BDAC)
RIM Main
RIM 1400
NMS 410/NMS 430
MA 330 MB-1/MB-2
MA 330 RB
WMTS-SHU-4
The following modules comply with FCC part 95 subpart H:
WMTS-SHU-4
2032086-003C Enterprise Access A-3

A-4 Enterprise Access 2032086-003C

B Definitions
2032086-003C Enterprise Access B-1

Definitions
Acronyms
Acronym Definition
AGC Automatic Gain Control
AP Access Point
BDA BiDirectional Amplifier
BDAC BiDirectional Amplifier Conditioner
BDACL BiDirectional Amplifier Conditioner for RIU Lite
BTS Base Transceiver Station
BTSC Base Transceiver Station Condition
BU Base Unit
DL Downlink
EA Enterprise Access
GUI Graphical User Interface
LCL Local
LSR Laser
MCCP Main Closet Connection Points
MRC MA2000 Remote Cabinet
MS Mobile services
NMS Network Management System
OTDR Optical Time-Domain Reflectometry
RHU Remote Hub Unit
RIU Radio Interface Unit
RIM Receiver Interface Module
SHU Switching Hub Unit
SMU Service Multiplexer Unit
SNR Signal to Noise Ratio
UL Uplink
VDC Volts Direct Current
WiFi Wireless Fidelity
WMTS Wireless Medical Telemetry Services
B-2 Enterprise Access 2032086-003C

C Firmware upgrade
2032086-003C Enterprise Access C-1

Firmware upgrade
Purpose
This section provides GE service representatives and technical personnel instructions
to upgrade the firmware for all the required elements and devices within the
Enterprise Access NMS architecture.
It is recommended that you read this entire upgrade procedure first in order to fully
understand the upgrade process.
WARNING
LOSS OF DATA — Shut down of Enterprise Access components
causes a disruption of data flow between the Unity Network MC
network devices and the hospital enterprise network. Notify the
affected users relying upon this data flow before shutting down the
Enterprise Access, or if the Enterprise Access components shut
down for any reason.
Firmware versions
3.18 Service Pack 2

Product Firmware version
Firmware versions
MA 1200 Add-on 3.2B04 3.4B00
BTSC / BDAC / RIM 3.0B04 3.0B04
NMS Controller:
Basic Controller 5.3B01 5.5B00
COM Controller 4.6B00 4.7B00
430 Interface MA167.bin MaApp_208.bin
NMS Server SW 22.01.12 22.03.15
MCT Client SW 10.21.06 10.23.03
GE_WMTS RHU 4.2B00 4.2B00
Base Unit 3.8B01 4.0B01
MA 1000/2000 RHU 3.6B00 3.7B00
RIM 1400 n/a 1.4B00
EA-WMTS-SHU-4 maWMTS_Ver6_1.hex
C-2 Enterprise Access 2032086-003C

Firmware upgrade
Upgrade kit contents
Name Description Version Type Location
Atmel Flip application Kernel Upload 1.8.8 Software Upgrade CD

Configuration Utility
HyperTerminal Microsoft 4.0 Software Upgrade CD

HyperTerminal
Cerberus FTP server FTP file server 2.16 Software Upgrade CD
Install Version Update Used for upgrading 10.2 Software Upgrade CD

Tool RIM 1400
MA upgrade module Used for upgrading the -- Hardware Upgrade kit

card MA 430
RS232 cable Standard RS232 cable -- Hardware Upgrade kit
Programming cable Used for selecting the -- Hardware Upgrade kit

(PN 705A000501) BU OPTM (1 or 2) to
be programmed
BTSC PS connection Used to connect the -- Hardware Upgrade kit

cable (PN 705A000601) BTSC to be
programmed to the PS
Crossover cable Ethernet 802.3 -- Hardware Upgrade kit

crossover cable
Equipment setup
See the following diagram for information on setting up the programming cable, PN
705A000501.
4
001A

Firmware upgrade
Item Description
1 Connect to front panel RS232 connector of the remote device (RHU or 1200 add-
on) to be upgraded.
2 Connect to BU rear panel auxiliary connector.
3 Switch, used in BU upgrade to select the OPTM to be programmed.
4 Connect to standard RS232 cable that is connected to the computer.

Firmware upgrade
Pre-upgrade procedures
Microsoft Windows NT4, 2000, or XP is the required operating system for the
Enterprise Access firmware upgrade process. Install and configure the following
required applications prior to upgrading Enterprise Access firmware components.
Install the Atmel Flip application on page C-5

Install the Cerberus FTP server on page C-5 (only required for upgrading the
NMS 430 agent)
Configure the Microsoft HyperTerminal
Install the Lantronix DeviceInstaller application on page C-6 (only required for
upgrading the WMTS-SHU-4)
Install the Atmel Flip application

Use the Enterprise Access Upgrade CD to install the Atmel Flip application.
1. Navigate to the Utilities folder and access the FLIP 1.8.8 directory within the
upgrade CD.
2. Double-click Setup.exe to begin the installation process.
3. On the Welcome screen, select Next.
4. On the Software License Agreement screen, accept the terms of the agreement
and select Next.
5. On the Select Installation Folder Destination screen, determine where you want
to install the application files:
a. Select the default location (c:\Program Files\ATMEL\FLIP 1.8.8) or

Browse to the location where you want to install the files.
b. Select Next.
6. Select Finish.
Install the Cerberus FTP server

1. Navigate to the Utilities folder and access the FTP Server directory within the
upgrade CD.
2. Double-click CerberusInstall.exe to begin the installation process.
3. On the Software License Agreement screen, accept the terms of the agreement
and select Next.
4. On the Select Installation Folder Destination screen, determine where you want
to install the application files:
a. Select the default location (c:\Program Files\Cerberus) or Browse to the

location where you want to install the files.
b. Select Next.
5. On the Confirm Installation screen, select Next.

Firmware upgrade
6. On the Installation Complete screen, select Close.
Install the Lantronix DeviceInstaller application

1. Navigate to the Utilities folder and access the DeviceInstaller directory within
the upgrade CD.
2. Double-click setup.exe to begin the installation process.
3. Follow the screen prompts to complete the installation.
Install Version Update Tool

1. Navigate to the Version Update Tool folder within in the upgrade CD.
(Utilities>Version Update Tool.)
2. Double-click Setup.exe.
3. On the Welcome screen, click Next.
4. Select the installation location and click Next.
5. Click Next to start the installation.
6. Once the installation is complete, click Close.
Upgrading MA 410/430 controllers

This section describes the installation process required to upgrade the MA NMS 410
and 430 controllers.
NOTE
Some sections are only relevant for the NMS 430 controller.
Summary
Both the NMS 410 and 430 controllers require upgrades for the two onboard micro-
controllers: communication micro-controller and basic micro-controller. The
following procedure defines the upgrade process. Refer to the sections that follow to
perform the actual upgrade.
NOTE
The communication micro-controller must be upgraded prior to the basic micro-

controller or the 430 NMS controller card.
1. If you are upgrading an MA NMS 430 controller, insert the 410 MA controller
card supplied within the upgrade kit. Otherwise, validate that the 410 controller
card is installed.
2. Upgrade the communications micro-controller on page C-7.
3. Upgrade the basic micro-controller on page C-10.

Firmware upgrade
4. Verify the upgrade procedure.
5. If you are upgrading an MA NMS 430 controller, re-install the original 430
controller card and follow the upgrade instructions for the NMS 430 controller.
Install the MA 410 controller card

This procedure is only required when upgrading the NMS 430 controller. Follow this
procedure to replace the MA 430 card:
1. Remove the power plug to power off the MA NMS controller.
2. Remove the two side screws and remove the MA 430 communication card.
3. Install the supplied RS232 (MA 410) upgrade card.
002A
NOTE
The supplied RS232 (MA 410) slide-in card is needed for each upgrade
procedure executed on the MA 430 controller units.
Upgrade the communications micro-controller

1. Verify that the 410 controller card is installed according to Install the MA 410
controller card on page C-7.
2. Connect the cables as shown in the following diagram:
a. Connect the MA programming cable (PN 705A000501) DB-9 male

connector to the controller RS232 front panel port.
b. Connect the DB-9 female connector to the PC.

Firmware upgrade
DB-9 female RS232 cable
MA programming cable
PN 705A000501
Not used
003A
3. Reset the controller.
a. Remove and then re-insert the power connector at the rear of the controller.
b. Verify that the device is in programming mode. The LCD screen should be
blank. (The top row has a black checkered bar across it.)
4. Launch the Atmel Flip application version 1.8.8.
5. Select Device > Select, select T89C51RC2 from the dropdown list and select OK.
004A
6. Configure the interface in which the serial port is linked.
a. Select Settings > Communication > RS232.
b. On the RS232 window, make the selections as indicated in the following

figure.
005A

Firmware upgrade
c. Select Connect.
Upon a successful connection, the Operations Flow and T89C51RC2

sections of the Flip main window become active.
If you receive a timeout error, validate that the Atmel’s RS232
communications port matches the port assigned to the PC’s RS232 port.
Select Settings > Communication > RS232 to view the current
configuration.
7. Verify that the Erase, Program, and Verify boxes are checked in the Operations
Flow section of the Flip main window as shown in the following figure.
006A
8. Load the appropriate firmware image into the Flip application.
a. Select File > Load HEX.
b. On the upgrade CD, navigate to the following location:
Upgrade to 3.17 CD SP 1.1\Release 3.17 SP 1.1\Embedded plus Eng

Gui\Embedded\Controller
c. Select the CtrlCom_v46_b00.hex firmware image file.
9. On the Flip main window, validate that the following settings were retained:

Firmware upgrade
Field Value
Device T89C51RC2
HEX File CtrlCom_v46_b00.hex
Operations Flow Checked

fields:
Erase
Program
Verify
10. Select Run. When the upgrade procedure is complete, the Erase, Program, and
Verify check boxes in the Operations Flow window are filled with green check
marks.
11. Select File > Exit to close the Atmel Flip application.
12. Remove the communication cable.
13. Reboot the NMS controller and verify that the NMS front panel LCD displays
the updated COMM version (i.e., 4.6:X.X) within the boot process.
Upgrade the basic micro-controller

Use the Microsoft HyperTerminal application to set the basic micro-controller in
programming mode, and the Flip application to download the program to the micro-
controller. Follow these steps:
1. Power on the NMS controller.
2. Verify that the NMS front panel LCD displays the updated COMM version (i.e.,
4.6:X.X) within the boot process.
If the communications controller has not been updated, refer to Upgrade the
communications micro-controller on page C-7.
3. Verify that the 410 controller card is installed according to Install the MA 410
4. Connect the standard RS232 cable between the computer and the NMS controller
front panel RS232 connector.
5. Access the DOS command prompt:
a. Select Start > Run.
b. Type cmd and select OK.
6. At the DOS prompt, type the following commands:
Mode ><communication port>:38400,n,8,1

Echo [FFFFFFFFD2ZZ] > <communication port>
For example, if the serial communication port is on Com 1, you enter the
following commands:

Firmware upgrade
Mode Com1:38400,n,8,1
Echo [FFFFFFFFD2ZZ] > Com1
7. Verify that the NMS controller’s LCD screen says Programming Mode Local
Basic.
8. Launch the Atmel Flip 1.8.8 application.
9. Select Device > Select, select AT89C51ED2 from the Device dropdown list and
select OK.
008A
b. On the RS232 window, verify the following:
Port = COM1
Baud = 38400
c. Select Connect.
Upon a successful connection, the Operations Flow and AT89C51ED2

sections of the Flip main window become active.
configuration.
Flow section of the Flip main window as shown in the following figure.

Firmware upgrade
009A
b. On the upgrade CD, navigate to the following location:
Upgrade to 3.17 CD SP 2\Release 3.17 SP 2\Embedded plus Eng

Gui\Embedded\Controller
c. Select the CtrlBas_v53_b01.hex firmware image file.
Field Value
Device AT89C51ED2
HEX File CtrlBas_v53_b01.hex

fields:
Erase
Program
Verify

Firmware upgrade
marks.
15. Select File > Exit to close the Atmel Flip application.
16. Remove the communication cable.
17. Reboot the NMS controller and verify that the NMS front panel LCD displays
the updated COMM version (i.e., X.X:5.3) within the boot process.
18. If you have just upgraded the MA 430, continue to Replace the MA 430
Replace the MA 430 controller card

This procedure is only required when upgrading the NMS 430 controller. Follow this
procedure to replace the MA 410 card:
1. Remove the power plug to power off the MA NMS controller.
2. Remove the two side screws and remove the MA 410 communication card.
3. Install the original MA 430 controller card.
002A
NOTE
The supplied RS232 (MA 410) slide-in card is required to upgrade the basic
and comm firmware for the NMS controller.
4. Store the MA 410 upgrade card for future use.
Upgrade MA 430 controller agent

This procedure requires an FTP application to upgrade the MA 430 controller card. If
you have not already loaded the FTP application, refer to Install the Cerberus FTP
server on page C-5.
1. Validate that the 430 controller card has been installed in the NMS controller. See
Replace the MA 430 controller card on page C-13.
2. Save the new agent software locally.
a. Access the following file on the upgrade CD:

Firmware upgrade

Gui\Snmp Agent\maApp_167.bin
b. Save the file to c:\ MobileAccess\.
3. Establish a local connection to the RS232 port on the MA 430 controller card.
4. Launch the Microsoft HyperTerminal application and set the communication

settings as follows:
Setting Value
Baud-Rate 9600
Data Bits 8
Parity None
Stop Bit 1
Flow Control None
5. Remove and re-insert the power connection on the rear panel to power-cycle the
NMS controller.
6. In the HyperTerminal application, press any key to stop the boot sequence on the
NMS 430 card.
7. At the password prompt, type the password. The default password is ma.
NOTE
Do not change the password.
8. Press Enter to accept the values for IP Address, Netmask, and Default Gateway.
9. Record the IP address, subnet mask, and default gateway of the NMS 430 card in
the following table.
Field Value
IP Address
Subnet Mask
Default Gateway
10. Select [C] Continue.
11. Configure your laptop NIC card with an IP address on the same subnet as the
NMS 430 card (use the same subnet mask and default gateway):
a. Select Start > Control Panel > Network Connections.
b. Right-click Local Area Connection.
c. Select Properties.
d. On the General tab, select Internet Protocol (TCP/IP).

Firmware upgrade
e. Select Properties.
f. On the General tab, select Use the following IP address.
g. Type the IP address, subnet mask, and default gateway that you recorded in
step 9.
12. Connect the crossover cable provided with the upgrade kit directly from the
computer to the NMS 430 controller Ethernet port.
13. Launch the Cerberus FTP Server application and perform the following steps:
a. In the FTP server application, select Configuration > User Manager >
Users > New.
b. Type ge for the user.
c. In the Property window, select Password.
d. Type ge for the password.
e. Assign the root directory to c:\ MobileAccess\:
i. Under Virtual Root Directory, select and navigate to

c:\ MobileAccess\.
ii. Select Add to Root.
iii. Under Property, check the Download and Upload check boxes, and
verify that the value for each field is True.
011A
f. Close the User Manager window.
14. From the HyperTerminal window, enter the new boot parameters as follows:
a. At the SNMP Get Community prompt, press Enter to accept the defaults.
b. At the SNMP Set Community prompt, press Enter to accept the defaults.
c. At the FTP server address prompt, type the IP address of your laptop NIC
card.
d. At the FTP User prompt, type ge as the user name.
e. At the FTP Password prompt, type ge as the password.

Firmware upgrade
f. At the FTP file prompt, type the path of the FTP root directory where the
upgrade file resides.
\MobileAccess\maApp_167.bin
NOTE
Be sure to enter this path exactly. You cannot delete or backspace, as

these characters will be recorded as part of the path.
g. If you have entered everything correctly, select 1:Download to begin the

download. Otherwise, select 2:Run and return to the beginning of step 14 to
reconfigure the parameters.
h. Select [C] continue.
15. Validate the upgrade process. The following messages indicate that the software
has been loaded successfully.
012A
16. Resume normal operation on the MA 430 card. Perform the following steps:
a. At the SNMP Get Community prompt, press Enter.
b. At the SNMP Set Community prompt, press Enter.
c. At the FTP server address prompt, press Enter.
d. At the FTP User prompt, press Enter.
e. At the FTP Password prompt, press Enter.
f. At the FTP file prompt, press Enter.
g. Select 2: Run.
h. Select [C] continue.
i. Under Current Boot Parameters, verify that the filename is

maApp_167.bin.
17. Disconnect the RS232 cable and crossover cable.
Upgrading RHUs (MA 1000, MA 2000, and WMTS) and MA 1200

add-on units
General upgrade procedure

a. Connect the RS232 cable to the PC.

Firmware upgrade
b. Connect the MA programming cable (PN 705A000501) DB-9 male

connector to the RS232 front panel port of the device to be upgraded.
c. Connect the DB-9 female connector to the RS232 cable.
DB-9
female RS232
cable
Programming cable PN 705A000501
Not used
013A
2. Remove and re-insert the power connector to reset the MA device (RHU or Add-
on).
3. Launch the Atmel Flip 1.8.8 application.
4. Select Device > Select and select the applicable flip device from the dropdown
list and select OK.
Module Flip device
MA 1200 add-on T89C51RC2
RHUs (MA 1000, MA 2000, WMTS) AT89C51ED2
Port = COM1
Baud = 38400
c. Select Connect.
Upon a successful connection, the Operations Flow and Device sections

of the Flip main window become active.
configuration.
Flow section of the Flip main window.
b. On the upgrade CD, navigate to the applicable location:

Firmware upgrade
Module CD location
MA 1200 Upgrade to 3.17 CD SP 1.1\Release 3.17 SP 1.1\Embedded plus

Eng Gui\Embedded\AddOn
RHU Upgrade to 3.17 CD SP 1.1\Release 3.17 SP 1.1\Embedded plus

Eng Gui\Embedded\RHU
c. Select the applicable firmware image file:
Module HEX file
MA 1200 add-on addon_v32_b04.hex
RHUs (MA 1000, MA 2000, WMTS) RHU_v36b00_New_PA.hex
Module Field Value
Device T89C51RC2
HEX File addon_v32_b04.hex

MA 1000 add-on fields:
Erase
Program
Verify
Device AT89C51ED2
HEX File RHU_v36b00_New_PA.hex

RHU fields:
Erase
Program
Verify
marks.
10. Power-cycle the device to exit Programming mode.
11. If you are upgrading additional devices of the same type, do not close the Flip
application.
Verify the upgrade procedure

1. Use a standard RS232 cable to connect to the device RS232 front panel
connector.

Firmware upgrade
2. Launch the Microsoft HyperTerminal application.
3. Set the baud rate to 19,200.
4. Run the device-specific macro for verification:
a. From the Control menu, select Macro.
b. Select the device-specific verification file, which is in the format

verifybuild.device (e.g., verifybuild.optm). The device type and file
information are displayed, as shown in the following example:
015A
Upgrading the WMTS-SHU-4

Summary
1. Install and launch the Lantronix DeviceInstaller application. See Install the
Lantronix DeviceInstaller application on page C-6.
2. Connect the WMTS-SHU4 to the network on page C-19.
3. Perform auto-discovery on page C-19.
4. Upgrade the unit on page C-20.
Connect the WMTS-SHU4 to the network

It is recommended that you record the location of each WMTS-SHU-4 unit according
to the MAC addresses on the sticker near the Ethernet port at the rear of the unit.
1. Connect each WMTS-SHU-4 unit to the network.
2. Connect each WMTS-SHU-4 unit to the power cable.
Perform auto-discovery
Make sure the installed version of the WMTS-SHU-4 unit is 4.1.0.3 or higher.
1. If necessary, Install the Lantronix DeviceInstaller application on page C-6.
2. Launch the Lantronix DeviceInstaller application.
3. On the toolbar of the Lantronix DeviceInstaller main window, select the Search
icon. The currently connected WMTS-SHU-4 units in the network are identified
and listed in the window according to the following:
Type: communication hardware version

Firmware upgrade
IP Address - currently defined IP address

Hardware Address - MAC address
Additional identification parameters, as available
Upgrade the unit

1. From the list in the Lantronix DeviceInstaller main window, select the WMTS-
SHU-4 unit to be upgraded.
2. On the toolbar of the Lantronix DeviceInstaller main window, select the

Upgrade button.
3. On the Device Upgrade Wizard screen, select the Use a specific installation file
(LXI) (previously saved by user) option and select Browse.
4. Navigate to the Upgrade\MA-WMTS-SHU XPort Ver X_X directory and locate

the *.LXI file.
5. Select the *.LXI file and select Next. A log of the uploaded files and the
procedure status are displayed.
6. Wait until the status of all uploaded file logs is Succeeded.
7. Select Close to exit the DeviceInstaller application.
Upgrading base units

General upgrade procedure
The upgrade procedure is repeated for each OPTM in the BU. The programming cable
(PN 705A000501) includes the OPTM plug switch used to switch between the
OPTMs being upgraded.

d. Connect the OPTM switch-plug to the Alarms port on the BU rear panel.

Firmware upgrade
BU rear panel
DB-25 connector
and OPTM switch
BU front panel
DB-9
DB-9 male
female
Programming cable
PN 705A000501
RS232
cable
016A
2. Remove and re-insert the power connector to reset the BU.
3. Launch the Atmel Flip application.
004A
Port = COM1
Baud = 38400
c. Select Connect.

configuration.
b. On the upgrade CD (MA 1200), navigate to the following location:

Firmware upgrade

Gui\Embedded\OPTM - BaseUnit
c. Select the optm_v38_b01.hex firmware image file.
Field Value
Device T89C51RC2
HEX File optm_v38_b01.hex

fields:
Erase
Program
Verify
Verify check boxes in the Operations Flow section are filled with green check
marks.
10. Disconnect and re-insert the power cable to reset the BU.
11. Switch the OPTM plug-switch to program the second OPTM and repeat steps 8-
9.
12. Power-cycle the device to exit Programming mode.
13. If you are upgrading additional base units, do not close the Flip application.

connector.

verifybuild.device. The device type and file information are displayed.
Upgrading RIUs
General procedure
The BTSC upgrade procedure requires you to disassemble the individual BTSCs and
power supply from the RIU chassis.

Firmware upgrade
1. Remove the RIU power connection.
2. Disassemble the BTSCs and the RIU power supply.
3. Connect the RIU power supply to the BTSC, using the BTSC-PS connection
cable (PN 705A000601).
4. Connect the power source to the RIU PS.

Power
RIU PS connection
BTSC to PS
cable
PN 501A000601
BTSC
DB-9
female
Programming cable
PN 705A000501
RS232 cable
018A
004A
Port = COM1
Baud = 38400
c. Select Connect.

Firmware upgrade

configuration.

Gui\Embedded\BTSC - RIM
c. Select the BTSC_RIM_V30_B05.hex firmware image file.
Field Value
Device T89C51RC2
HEX File BTSC_RIM_V30_B05.hex
Operations Flow fields: Checked
Erase
Program
Verify
marks.
13. Disconnect and re-insert the power cable to reset the BTSC.
14. If you are upgrading additional RIUs, do not close the Flip application.

connector.

verifybuild.device. The device type and file information are displayed.

Firmware upgrade
Upgrading RIM mains

1. Connect the cables as follows:

2. Disconnect the cable connecting the RIM Main to the RIM-L, if present.
3. Remove and re-insert the power connector to reset the RIM Main. The run light
on the front of the unit should be solid, indicating the unit is in programming
mode.
004A
Port = COM1
Baud = 38400
c. Select Connect.

configuration.

Firmware upgrade

Gui\Embedded\BTSC - RIM
c. Select the BTSC_RIM_V30_B05.hex firmware image file.

Firmware upgrade
Field Value
Device T89C51RC2
HEX File BTSC_RIM_V30_B05.hex
Operations Flow fields: Checked
Erase
Program
Verify
marks.
11. If applicable, reconnect the RIM Main to the RIM-L.
12. Disconnect and re-insert the power cable to reset the BTSC.
Upgrading the RIM 1400s

1. If not already installed, install the Lantronix DeviceInstaller application.
2. Navigate to the folder C:\Program Files\Mobile Access\VersionUpdate tool.
3. Copy both the Release_x_y.cfg and RimL vx.y.hex files (where x_y is the
version of the files) to the folder C:\Program Files\MobileAccess\Version
Update Tool.
NOTE
The Release_x_y.cfg and RimL.vx.y.hex files must be in the same directory.
4. Right-click config.General and select Open With > Notepad (or WordPad).
5. Type the full path to the directory containing the Release_x_y.cfg and
RimL.vx.y.hex files after <Release Config File>.
019B
6. Right-click Release_x_y.cfg and select Open With > Notepad (or WordPad).
7. Type the name of the hex file in the LocalRIML section after <New Version
File>: if it is not already there.

Firmware upgrade
0120A
8. Connect the PC with standard serial cable to RIM Main that is associated with
the RIM 1400. The RIM 1400 does not have to be in a particular mode (slave or
master).
9. Run the Version Update Tool. The following screen will appear once there is a
successful connection.

Firmware upgrade
021A
10. On the Connected to screen, click Ok.
11. In the Local Device tab, select RimL from the dropdown box.
022A
12. Click Connect. After a few seconds, the Unit #, Active Version #, and Inactive
Version # should be displayed in the Swap frame.
13. Click Configure.
14. Browse to the Release_x_y.cfg file.
15. Verify that the rest of the settings match the following figure and click Save.

Firmware upgrade
023A
16. Click Download. The Download frame should display an In Progress message,
wait until a Success message appears before continuing.
NOTE
This is downloading the file to the inactive version on the RIM 1400. You
must activate this file.
17. Click Swap Versions to swap the inactive version with the active version. Wait
until a Success message appears in the Swap frame before continuing.
18. Click Disconnect.
19. Exit the Version Update Tool and disconnect the serial cable.

Asia Headquarters
GE Medical Systems
GE Medical Systems Information Technologies Asia; GE (China) Co., Ltd.
Information Technologies, Inc. 24th Floor, Shanghai MAXDO Center,
8200 West Tower Avenue 8 Xing Yi Road, Hong Qiao Development Zone
Milwaukee, WI 53223 USA Shanghai 200336, P.R. China
Tel: + 1 414 355 5000 Tel: + 86 21 5257 4650
1 800 558 5120 (US only) Fax: + 86 21 5208 2008
Fax: + 1 414 355 3790
GE Medical Systems Information Technologies, a General Electric Company, going to market as

GE Healthcare.
www.gehealthcare.com

GE Enterprise Access OPS Manual

Uploaded by

Copyright:

Available Formats

GE Enterprise Access OPS Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GE Enterprise Access OPS Manual

Uploaded by

Copyright:

Available Formats

GE Healthcare

Enterprise Access System

T-2 Enterprise Access 2032086-003C

Safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

2 Equipment overview . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2032086-003C Enterprise Access i

RIM Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

RIM 1400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63

RIM Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69

Network Management System (NMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80

Enterprise Access service software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-89

Performance characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Safety requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

ii Enterprise Access 2032086-003C

4 NMS System Management . . . . . . . . . . . . . . . . . . . . 4-1

NMS MCT client software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Installing and configuring NMS system management . . . . . . . . . . . . . . . . . 4-2

Topology configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

5 CARESCAPE Systems Manager . . . . . . . . . . . . . . . 5-1

Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Controlling electrostatic discharge damage . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

2032086-003C Enterprise Access iii

Maintenance checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Repair log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

Antenna system troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Enterprise Access infrastructure troubleshooting. . . . . . . . . . . . . . . . . . . 7-21

8 Replaceable parts . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Other parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

A Technical specifications . . . . . . . . . . . . . . . . . . . . . . A-1

Power specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Standards and approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

iv Enterprise Access 2032086-003C

C Firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Upgrade kit contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

Equipment setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

Pre-upgrade procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5

Upgrading MA 410/430 controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6

Upgrading the WMTS-SHU-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19

Upgrading base units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20

Upgrading RIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-22

Upgrading RIM mains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-25

Upgrading the RIM 1400s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27

2032086-003C Enterprise Access v

2032086-003C Enterprise Access 1-1

B Updated for site feedback.

C Updated for calibration schedule.

+ Indicates keyboard keys to select simultaneously.

> Indicates menu options to select consecutively.

Illustrations and names

1-2 Enterprise Access 2032086-003C

 Assembly operations, extensions, readjustments, modifications, or repairs are

Enterprise Access current offering includes (but is not limited to):

 ApexPro Dual Band CH

2032086-003C Enterprise Access 1-3

The following warning statements apply to this system.

1-4 Enterprise Access 2032086-003C

The following caution statements apply to this system.

This CAUTION applies when the Enterprise Access system is used

Assembly operations, extensions, readjustments, modifications, or repairs are

ApexPro Dual Band CH

WMTS RHU, MA 1000, and MA 2000 - 1310 nm wavelength window

MA 2000 Modular Remote Cabinet (MRC) - The MRC is a cabinet in which up