User Manual

Table Of Contents
Optical Master Unit
PRODUCT DESCRIPTION AND USER’S MANUAL
© Axell Wireless Ltd A1829300 rev H 27 (86)
3 Monitoring and Control
The Optical Master Unit, OMU as well as the whole OMU-Repeater system can be accessed locally on site
through a Local Maintenance Terminal (LMT) port on any of the units in the system, or remotely via modem or
Ethernet.
When an RS232 cable is plugged in to the LMT port or a remote access has been established, there are two
options for communication; terminal mode or RMC mode.
Terminal mode is accessed by using a terminal emulation software, such as HyperTerminal™ or MiniCom
(Linux/Unix) Settings should be ANSI or VT100 emulation, baud rate 9600, 8 data bits, 1 stop bit, No
parity and No flow control. A simple command language is used to control the repeater in this mode.
Repeater Maintenance Console (RMC) mode allows configuration and control of the repeater via a user
friendly Windows software.
Note! All instructions in this chapter assumes that the OMU is controlled using the Repeater Maintenance
Console, RMC.
For terminal mode commands please refer to the documents “Common Commands and Attributes” and “OMU
Commands and Attributes” which contain detailed description of all attributes and commands.
Firmware Documentation Structure
The documents “Common Commands and Attributes” and “OMU Commands and Attributes” together describe
all functionality in the OMU. The Common part contains functionality that is common for all Axell Wireless
repeaters as well as the OMU, and the OMU part contains functionality that is specific for the OMU. For
repeaters there are corresponding documents available.
Help Functions
When being logged in to a unit using the terminal mode the command
HELP
lists all attributes and their modes of operation and displays them in alphabetic order on the screen.
Further help regarding specific commands can be obtained by typing
INF <command>
The INF attribute gives detailed information about a specific attribute.
3.1 Software Features - Overview
The firmware in the Control Module controls and monitors all parameters in the unit. If the OMU is configured
as a node master it also handles alarms and heartbeats from slave repeaters connected to it. Statuses and
measured levels can be read online via the RMC. This includes for instance voltage levels, RF-levels and
temperatures.
In the event of a failure, an alarm is logged in the OMU. If the OMU is intergraded in the AEM, the alarm is
also transmitted to the AEM. The OMU can be configured to handle alarms concerning a number of different
parameters. Each alarm can also be individually configured in a number of ways. The OMU stores
approximately 2 000 alarms in a local alarm log. The data stored regarding each alarm is the time at which an
alarm occurred and the alarm information which consists of alarm source, alarm severity, alarm attributes and in
some cases an additional alarm description.
On regular intervals, the OMU can send a heartbeat report to the AEM to confirm that the unit is functioning.
The heartbeat message contains information about the RF-configuration and the alarm sources. It ensures that
the data communication from the OMU to the AEM is working properly. The latest 2 000 heartbeats
(approximately) are stored in a log.
The Control Module contains a battery backed-up real time clock, which will stay active even during a power
failure. The real time clock is used for instance to keep track of when an alarm occurred, when to retransmit an
alarm and at what time of the day to send traffic report to the AEM. If the OMU is controlled by the Axell