User Manual

Table Of Contents
Optical Master Unit
PRODUCT DESCRIPTION AND USER’S MANUAL
© Axell Wireless Ltd A1829300 rev H 44 (86)
3.5.1.2 AEM Database Synchronization
The Axell Element Manager stores all OMU parameters in a database. This database is populated during the
OMU integration into the AEM when the AEM downloads all the OMU parameters. If the AEM operator wants
to monitor the configuration of the OMU, the parameters can be read from the database without having to
connect to the repeater.
In case of an alarm, the AEM updates the database with the status of the alarm source. In case the OMU fails to
deliver the alarm to the AEM there will be a discrepancy between the OMU configuration and the configuration
in the database. For this reason, each heartbeat report contains all the relevant parameters and status of all the
alarm sources in the OMU. This means that each heartbeat report will update the AEM with all status and RF
parameters.
Note! Once the OMU is integrated to the Axell Element Manager, it is recommended that all reconfigurations
are made from the AEM.
Note! If a user logs in to the OMU making changes, as soon as the user logs out, an alarm will be transmitted to
the AEM informing the operator that a change has been made. When this alarm is received, the operator can
initiate OMU synchronization where all OMU parameters will be updated.
3.5.1.3 Time Synchronization
Each heartbeat message transmitted to the AEM contains a time stamp of the local time inside the OMU. Upon
reception in the AEM, the time stamp is compared to the Axell Element Manager time. If the difference
between the OMU and AEM time is too big, time synchronization is initiated by the AEM, adjusting the time in
the OMU. In this way it is ensured that an OMU integrated to the Axell Element Manager always contains the
correct time information.
Note! If the time is adjusted by a user logged in to the OMU, once the user logs out, a heartbeat is sent to the
AEM to ensure that the time is correctly synchronized.
3.5.2 Heartbeat Format
The heartbeat report is transmitted as an ASCII text string, with a number of fields representing the status
parameters, each field separated by a blank/white space.
Field Format Description # of chars
Repeater ID XX-YY-ZZZZ 10
Message no NNNNNNNNN 9
State STATE 5
Date DDMMYY 6
Time HHMMSS 6
BAT N Status of Battery Charge 1
COM-RCB NNNN Status of communication with Rack Communication Boards 4
COM-FO Rack 1 NNNNNN Status of communication with FiberOptic Modules in Rack 1 6
COM-FO Rack 2 NNNNNN Status of communication with FiberOptic Modules in Rack 2 6
COM-FO Rack 3 NNNNNN Status of communication with FiberOptic Modules in Rack 3 6
COM-FO Rack 4 NNNNNN Status of communication with FiberOptic Modules in Rack 4 6
CRC KLMNXYZ Status of CRC in the different modules.
These values are Hex Coded, and should be used in conjunction with
COM status for actual device.
7