Channel Selective Repeater PDF

channel selective
Repeaters
© Axell Wireless Ltd

Channel Selective Repeaters
PRODUCT DESCRIPTION AND USER’S MANUAL

Operating on 850, 900, 1800,
1900 and 2200 MHz
Product Description and User’s Manual
This manual is valid for Firmware release version

Common Commands and Attributes v 1.3.0
GSM-UMTS Commands and Attributes v 1.0.1
This document is valid for the following repeater models
Off Air Repeaters Fibre Fed

Repeaters
On-Frequency, On-Frequency, Frequency Band Shifting, GSM
GSM WCDMA Translating, GSM
CSR 822/4 CSR 822/4W CSFT 822/4 CSFT 91822/4 (R,E) CSF 922/4 (R,E)
CSR 922/4 (R,E,H) CSR 922/4W CSFT 922/4 (R,E) CSFT 18922/4 CSF 1822/4
CSR 1822/4 CSR 2222/4 CSFT 1822/4 CSFT 81922/4 CSF 1922/4
CSR 1922/4 CSFT 1922/4 CSF 2222/4
Copyright © 2009 Axell Wireless Ltd

All rights reserved.
No part of this document may be copied, distributed, transmitted, transcribed, stored in a retrieval system, or
translated into any human or computer language without the prior written permission of Axell Wireless Ltd.
The manufacturer has made every effort to ensure that the instructions contained in this document are
adequate and free of errors and omissions. The manufacturer will, if necessary, explain issues which may not
be covered by this document. The manufacturer's liability for any errors in the document is limited to the
correction of errors and the aforementioned advisory services.
This document has been prepared to be used by professional and properly trained personnel, and the customer
assumes full responsibility when using them. The manufacturer welcomes customer comments as part of the
process of continual development and improvement of the documentation in the best way possible from the
user's viewpoint. Please submit your comments to the nearest Axell Wireless sales representative.
© Axell Wireless Ltd A1019300, rev B 1 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL
Table of Contents
Safety Instructions and Warnings................................................................................................. 4
References .................................................................................................................................... 7
Contact Information ..................................................................................................................... 8
Definitions, Abbreviations and Acronyms ................................................................................... 9
1 Repeater Technology ................................................................................................................ 11
1.1 Basic Features.................................................................................................................... 11
1.2 Repeater Types .................................................................................................................. 11
1.3 Repeater Applications ....................................................................................................... 14
2 Software Overview.................................................................................................................... 17
2.1 Repeater Firmware ............................................................................................................ 17
2.2 The RMC, Repeater Maintenance Console ....................................................................... 17
2.3 The AEM, Axell Element Manager................................................................................... 17
3 Product Descriptions ................................................................................................................ 18
3.1 Repeater Models................................................................................................................ 18
3.2 Characteristics ................................................................................................................... 18
3.3 Casing................................................................................................................................ 22
3.4 Connections ....................................................................................................................... 23
3.5 Power and Back-up Battery............................................................................................... 24
3.6 Building Blocks................................................................................................................. 25
3.7 Internal Connections.......................................................................................................... 31
3.8 Signal Diagrams ................................................................................................................ 34
3.9 OMU-Repeater System ..................................................................................................... 38
4 Monitoring and Control ........................................................................................................... 40
4.1 Software Features - Overview ........................................................................................... 40
4.2 Alarm System .................................................................................................................... 41
4.3 Repeater Heartbeat ............................................................................................................ 55
4.4 RF Parameters ................................................................................................................... 57
4.5 Hardware Identification..................................................................................................... 62
4.6 Tag and ID......................................................................................................................... 63
4.7 User Access ....................................................................................................................... 64
4.8 Integration into AEM ........................................................................................................ 64
4.9 Upgrading Firmware ......................................................................................................... 65
5 Installation................................................................................................................................. 66
5.1 Site Installation Advice ..................................................................................................... 66
5.2 Engineering Considerations............................................................................................... 76
5.3 Prepare the Site.................................................................................................................. 78
5.4 Install the Repeater ............................................................................................................ 82
5.5 Start-up the Repeater ......................................................................................................... 94

5.6 Initiate Local Communication ........................................................................................... 98

5.7 Install the OMU and Set up OMU-Repeater System....................................................... 100
5.8 Configure the Repeater.................................................................................................... 100
5.9 Set Up Remote Communication ...................................................................................... 107
5.10 Integration into the AEM................................................................................................. 118
6 Maintenance ............................................................................................................................ 119
6.1 General ............................................................................................................................ 119
6.2 Preventive Maintenance .................................................................................................. 119
6.3 Trouble Shooting............................................................................................................. 119
6.4 Component Replacement................................................................................................. 119
6.5 Product Disposal.............................................................................................................. 119
7 Specifications ........................................................................................................................... 120
7.1 On-Frequency Repeaters, GSM....................................................................................... 120
7.2 On-Frequency Repeaters, WCDMA................................................................................ 125
7.3 Frequency Translating Repeaters .................................................................................... 128
7.4 Band Shifting Repeaters .................................................................................................. 134
7.5 Fibre Fed Repeaters......................................................................................................... 140

Safety Instructions and Warnings

Guarantees
All antennas must be installed with lightning protection. Damage to power modules, as a result of lightning are
not covered by the warranty.
Switching on AC or DC power prior to the connection of antenna cables is regarded as faulty installation
procedure and therefore not covered by the Axell Wireless warranty.
The repeater box should be closed using the two screws. The screws must be fully tightened. Failure to do so
may affect the IP65 compliancy and therefore any warranty.
Safety to Personnel
Before installing or replacing any of the equipment, the entire manual should be read and understood. The user
needs to supply the appropriate AC or DC power to the repeater. Incorrect power settings can damage the
repeater and may cause injury to the user.
Caution
Please be aware that the equipment may, during certain conditions become very warm
and can cause minor injuries if handled without any protection, such as gloves.
Throughout this manual, there are "Caution" warnings. "Caution" calls attention to a procedure or practice,
which, if ignored, may result in injury or damage to the system, system component or even the user. Do not
perform any procedure preceded by a "Caution" until the described conditions are fully understood and met.
Caution
This notice calls attention to a procedure or practice that, if ignored,
may result in personal injury or in damage to the system or system component.
Do not perform any procedure preceded by a “Caution” until described
conditions are fully understood and met.
Caution
(Valid for repeater CSFT 1922/4 only)
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to
part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This equipment generates, uses, and
can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may
cause harmful interference to radio communications. Operation of this equipment in a residential area is likely
to cause harmful interference in which case the user will be required to correct the interference at his own
expense.
Class 1 Laser
Some of the repeaters described in this manual is equipped with class 1 lasers, as per definition in
EN 60825-1.
Caution
Un-terminated optical receptacles may
emit laser radiation. Do not stare into beam
or view with optical instruments.

Optical transmitters in the fibre optic converter can send out high energy invisible laser radiation. There is a risk
for permanent damage to the eye.
Always use protective cover on all cables and connectors which are not connected. Never look straight into a
fibre cable or a connector. Consider that a fibre can carry transmission in both directions.
During handling of laser cables or connections ensure that the source is switched off. Regard all open
connectors with respect and direct them in a safe direction and never towards a reflecting surface. Reflected
laser radiation should be regarded as equally hazardous as direct radiation.
Safety to Equipment
When installing, replacing or using this product, observe all safety precautions during handling and operation.
Failure to comply with the following general safety precautions and with specific precautions described
elsewhere in this manual violates the safety standards of the design, manufacture, and intended use of this
product. Axell Wireless assumes no liability for the customer's failure to comply with these precautions. This
entire manual should be read and understood before operating or maintaining the repeater.
Electrostatic Sensitivity
Observe electrostatic precautionary procedures.
Caution
ESD = Electrostatic Discharge Sensitive Device
Semiconductor transmitters and receivers provide highly reliable performance when operated in conformity
with their intended design. However, a semiconductor may be damaged by an electrostatic discharge
inadvertently imposed by careless handling.
Static electricity can be conducted to the semiconductor chip from the centre pin of the RF input connector, and
through the AC connector pins. When unpacking and otherwise handling the repeater, follow ESD
precautionary procedures including use of grounded wrist straps, grounded workbench surfaces, and grounded
floor mats.

References
This document covers both GSM and WDCMA repeaters.
These references are valid for respective repeater type.
ETSI TS 25.106 Universal Mobile Telecommunications System (UMTS); UTRA repeater

radio transmission and reception 3GPP TS 25.106 version 5.8.0 Release 5)
ETSI TS 25.143 Universal Mobile Telecommunications System (UMTS); UTRA repeater

conformance testing (3GPP TS 25.143 version 5.8.0 Release 5)
ETSI EN 301 908-3 Electromagnetic compatibility and Radio spectrum Matters (ERM);
ElectroMagnetic Compatibility (EMC) standard for radio equipment and
services; Part 1: Common technical requirements
ETSI EN 301 489-23 Electromagnetic compatibility and Radio spectrum Matters (ERM);
ElectroMagnetic Compatibility (EMC) standard for radio equipment and
services; Part 23: Specific Conditions for IMT-2000 CDMA Direct Spread
(UTRA) Base Station (BS) radio, repeater and ancillary equipment
EN 60 950 Information technology equipment - Safety - Part 1: General requirements
EN 301 502 Harmonized EN for Global System for Mobile communications (GSM);
Base station and Repeater equipment covering essential requirements
under article 3.2 of the R&TTE directive (GSM 13.21 version 8.1.2.
Release 1999)
ETS 300 342-3 Radio Equipment and Systems (RES); Electro-Magnetic Compatibility
(EMC) for European Digital Cellular Telecommunications systems. Base
Station Radio and ancillary equipment and Repeaters meeting phase 2
GSM requirements.
R & TTE Directive: Harmonized EN for Global System for Mobile communications (GSM);
ETS EN 301 502 Base Station and Repeater equipment covering essential requirements
(ETS EN 300 609- under article 3.2 of the R&TTE directive
4/GSM 11.26)
ETS EN 301 489-8 Electromagnetic Compatibility (EMC) Standard For Radio Equipment
And Services; Part 8: Specific Conditions For GSM Base Stations
ETS 300 342-3 Electromagnetic Compatibility (EMC) For European Digital Cellular
Telecommunications System (GSM 900 MHz and DCS 1 800 MHz); Part
3: Base Station Radio and Ancillary Equipment And Repeaters Meeting
Phase 2 GSM Requirements

Contact Information
Headquarters Axell Wireless
Aerial House
Asheridge Road
Chesham
Buckinghamshire HP5 2QD
United Kingdom
Tel: +44 1494 777000

Fax: +44 1494 777002
Commercial inquiries info@axellwireless.com
Web site www.axellwireless.com
Support issues support@axellwireless.com
Technical Support Line, English speaking +44 1494 777 777
Contact information for Axell Wireless offices in other countries can be found on our web site,
www.axellwireless.com

Definitions, Abbreviations and Acronyms

AEM Axell Element Manager, a software tool for operation and monitoring a network
consisting of Axell Wireless products.
ALC Automatic Limit Control
ARFCN Absolute Radio Frequency Channel Number. A channel numbering scheme used to
identify specific RF channels in a GSM radio system
Base station The central radio transmitter/receiver that maintains communications with a mobile
radio equipment within a given range
BCCH Broadcast Control Channel
BTS Base Transceiver Station, one part of a base station.
A base station is composed of two parts, a Base Transceiver Station (BTS) and a
Base Station Control Module (BSC). A base station is often referred to as BTS.
The BTS is also sometimes called an RBS or Remote Base Station.
Carrier-to- The ratio of power in an RF carrier to the interference power in the channel
interference ratio,
C/I
Carrier-to-noise The ratio of power in an RF carrier to the noise power in the channel
ratio, C/N
Channel In all Axell Wireless documentation a channel is the same as a carrier.
Coverage area The geographical reach of a mobile communications network or system
Coverage hole An area within the radio coverage footprint of a wireless system in which the RF
signal level is below the design threshold. Coverage holes are usually caused by
physical obstructions such as buildings, foliage, hills, tunnels and indoor parking
garages
dB Decibel, A technique for expressing voltage, power, gain, loss or frequency in
logarithmic form against a reference.
dBi Decibels referenced to an isotropic antenna. A technique for expressing a power gain
measurement in logarithmic form using a theoretical isotropic antenna as a reference
dBm Decibels referenced to 1 mW. A technique for expressing a power measurement in
logarithmic form using 1 mW as a reference.
Dead spot An area within the coverage area of a wireless network in which there is no coverage
or transmission falls off. Dead spots are often caused by electronic interference or
physical barriers such as hills, tunnels and indoor parking garages.
Distributed A type of antenna system that is distributed or remotely located away from the
antenna system transmitter. Such an antenna or series of antennas can be connected via coaxial
cable, leaky feeder or optical fibre link.
DL, Downlink The transmission path from the base station down to the mobile station
EAM External Alarm Messaging
EDGE Enhanced Data for Global Evolution. A technology that gives GSM and TDMA
similar capacity to handle services for the third generation of mobile telecom. EDGE
was developed to enable the transmission of large amounts of data at a high speed of
384 kilobit per second, or more.
EMC Electromagnetic Compatibility. The ability of a device or system to function in its

intended electromagnetic environment

ERP Effective Radiated Power
ETSI European Telecommunications Standard Institute. The European standardization

body for telecommunications
GND Ground
Hand-over The passing of a call signal from one base station to the next as the user moves out
of range or the network software re-routes the call
LED Light Emitting Diode
Link budget A calculation involving the gain and loss factors associated with the antennas,
transmitters, transmission lines and propagation environment used to determine the
maximum distance at which a transmitter and receiver can successfully operate.
LMT Local Maintenance Terminal
LNA Low Noise Amplifier. A receive preamplifier having very low internal noise
characteristics.
Logical channel A communications channel derived from a physical channel. A physical channel, i.e.
RF channel, typically carries a data stream that contains several logical channels.
These usually include multiple control and traffic channels.
LOS Line of Sight. A description of an unobstructed radio path or link between the
transmitting and receiving antennas of a communications system
MCPA Multi Carrier Power Amplifier
MS Mobile Station (e.g. mobile phone)
MTBF Meantime Between Failures
NA Not Applicable
NC Not Connected
NF Noise Figure
Node B UMTS base station
Noise figure A figure of merit for receivers and preamplifiers representing the amount of excess
noise added to the signal by the amplifier or receiving system itself. The lower the
noise figure, the less excess noise is added to the signal
OFR On-Frequency Repeater
ODF Optical Distribution Frame, used for connection and patching of optical cables
OMC Operations and Maintenance Centre. A location used to operate and maintain a
wireless network
OMU Optical Master Unit, translates between RF signals and optical signals so that fibre
fed repeaters can be used.
PA Power Amplifier. A device for taking a low or intermediate-level signal and
significantly boosting its power level. A power amplifier is usually the final stage of
amplification in a transmitter.
PSTN Public Switched Telephone Network, standard domestic and commercial phone
service
Radio link The equipment and transmission path (propagation channel) used to carry on
communications. It includes the transmitting system, the propagation channel and

receiving system
Repeater A bi-directional Radio Frequency (RF) amplifier that can amplify and transmit a
received Mobile Station (MS) signal in the MS transmit band. Simultaneously it
amplifies and transmits a received Base Transceiver Station (BTS) RF signal in the
BTS transmit band.
RF Radio Frequency, 9 kHz – 300 GHz
Designation Abbreviation Frequencies
Very Low Frequency VLF 9 kHz - 30 kHz
Low Frequency LF 30 kHz - 300 kHz
Medium Frequency MF 300 kHz - 3 MHz
High Frequency HF 3 MHz - 30 MHz
Very High Frequency VHF 30 MHz - 300 MHz
Ultra High Frequency UHF 300 MHz - 3 GHz
Super High Frequency SHF 3 GHz - 30 GHz
Extremely High Frequency EHF 30 GHz - 300 GHz
RMC Axell Wireless Repeater Maintenance Console. Software tool to monitor and control
Axell Wireless repeaters via local or remote access
RS232 Serial interface standard
RS485 Serial Interface standard
Service area The specified area over which the operator of a wireless communications network or
system provides services
Signal-to- The ratio of power in a signal to the interference power in the channel. The term is
interference ratio, usually applied to lower frequency signals, such as voice waveforms, but can also be
S/I used to describe the carrier wave. See also carrier-to-interference ratio.
Signal-to-noise The ratio of power in a signal to the noise power in the channel. This term is usually
ratio, S/N, SNR applied to lower frequency signals, such as voice waveforms. See also carrier-to-
noise ratio
SDS Short Data Service. Group messaging system for TETRA.
SMSC Short Messaging Service Centre
TCH Traffic Channel. A logical channel that allows the transmission of speech or data. In
most second generation systems, the traffic channel can be either full or half-rate
Transceiver A transmitter and receiver contained in one package. A 2-way radio or cell phone is
an example of a transceiver
Transmitter Equipment which feeds the radio signal to an antenna, for transmission. It consists of
active components such as the mixer, driver and PA and passive components such as
the TX filter. Taken together, these components impress a signal onto an RF carrier
of the correct frequency by instantaneously adjusting its phase, frequency, or
amplitude and provide enough gain to the signal to project it through the ether to its
intended target
UL, Uplink The transmission path from the mobile station up to the base station
WDM Wavelength Division Multiplexing. A technology that uses optical signals on

different wavelengths to increase the capacity of fibre optic networks in order to
handle a number of services simultaneously
VSWR Voltage Standing Wave Ratio

1 Repeater Technology
1.1 Basic Features
A basic feature of a mobile communication system is to transmit RF signals between base stations and mobile
radio equipment. If there is a blocking object such as a mountain or a building preventing the base station signal
to reach the mobile equipment, a repeater can be used to extend the base station’s coverage area.
Server antenna
Donor antenna
Repeater
BTS/ BTS/
Node B MS/UE Node B MS/UE
Undisturbed transmission Obstacle creating a coverage hole
In the downlink path the repeater will pick up the signal from the existing transmitter via the donor antenna,
amplify it and re-transmit it into the desired coverage area via the server antenna. In the uplink path the repeater
will receive signals from mobile transmitters in the covered area and re-transmit them back to the base station.
Other repeater applications are indoor coverage, tunnel coverage, coverage extension in low traffic areas and the
possibility to install capacity in new locations without installing a new base station.
1.2 Repeater Types

1.2.1 Channel Selective Repeaters
Channel selective repeaters are mainly used for coverage of dead zones, shadows, in-building coverage or other
areas with inadequate signal strength. The output power of a channel selective repeater is sufficient to cover an
area shadowed by a building or other obstacle.
In a channel selective repeater each carrier is separately filtered, amplified and retransmitted.
Server antenna
Donor antenna
F1 F1
F1
Repeater
BTS/Node B MS/UE
A channel selective repeater system consists of one repeater unit complemented with one antenna facing the
donor base station, and another antenna directed towards the coverage area. The repeater site needs to be located
where the base station signal strength is large enough to be usable by the system. Ideally the repeater’s donor
antenna should have line of sight (LOS) contact with the base station antenna. If the signal strength is high
enough, LOS may in some cases not be necessary.

The signal generated by the base station is picked up at the repeater site via the donor antenna. The repeater
filters and amplifies the signal before retransmitting it at the same frequency over the server antenna.
The isolation between the antennas at the repeater site has to be high in order to prevent degradation of signal
quality and risk of oscillation. Ways to achieve this can be large physical separation between the antennas,
usage of highly directional antennas with good front-to-interference ratio or external shielding between the
antennas. Another option is to use a Frequency Translating or a Band Shifting repeater (see descriptions below).
1.2.2 Band Selective Repeaters

Band selective repeaters have the same functionality as channel selective repeaters. The difference is that band
selective repeaters do not separate out specific carriers but amplify and retransmit all signals within a defined
frequency band.
1.2.3 Frequency Translating Repeaters

A frequency translating repeater provides output power levels comparable to a base station. The concept allows
for high gain without the high antenna isolation required for channel selective repeaters.
The frequency translating repeater consists of two units; one donor unit and one remote unit.
Link antennas
Server antenna
F1
F4 RF Link Path F4
F1
Donor unit Remote unit
Donor Cell Repeater units

Base Station
The donor unit is mounted at the base station site where the signal enters the repeater via a directional coupler.
In the donor unit, the signal is translated into another frequency, the link frequency, amplified and transmitted
via a link antenna. At the remote site, a link antenna picks up the signal and feeds it to the remote unit. The
signal is translated back into the original frequency and retransmitted over the server antenna.
Only 2 guard channels are needed between the radio frequency and the link frequency.
The isolation between antennas at the remote site seldom needs to be more than 75dB. This value that can be
achieved with a limited antenna displacement, often as low as 3 meters. The relatively modest isolation
requirement allows the use of omni-directional antennas for the service area.
Important applications for frequency translating repeaters are road coverage, rural coverage or for transferring
capacity from a base station to another area.
1.2.3.1 Donor Unit

There are two types of donor units – single donor (SD) and double donor (DD).
A single donor (SD) unit has one input connector. The input signal from the BTS is split in two within the
repeater unit. In the opposite direction – in the uplink – the signals are combined within the repeater before
being sent to the BTS.
A double donor (DD) unit has dual inputs. This can be used in combination with a BTS that uses air combining,
and hence has a separate antenna for each TRU. A double donor unit can alternatively handle two signals from
two separate BTS.

1.2.3.2 Remote Unit

There are two types of remote units – internal combining (IR) and external combining (ER).
In an internal combining (IR) remote unit output from the power amplifiers in the downlink is combined and
filtered before being passed on to the server antenna. In the uplink the signal is separated within the remote unit.
An external combining remote (ER) unit has two server antenna ports and the signal is combined in the air.
Since the ER model needs no combiner the output signal and gain is 3dB higher than in the IR model.
1.2.4 Band Shifting Repeaters

Band shifting repeaters are based on the same concept as frequency translating repeaters described above.
In contrast to a frequency translating repeater, which uses another frequency within the same band for the link, a
band shifting repeater uses another band. For instance can a repeater operating on the 900MHz band use the
1800MHz band for the link and vice versa. Other combinations are also possible.
Link and server antenna on the

remote site can often be combined
Link antennas
Server antenna
Band 2 Band 1
Band 1 RF Link Path Band 2
Donor unit Remote unit
Donor Cell Repeater units

Base Station
By using another band for the link, the isolation between antennas at the remote site becomes very low. It might
in some applications even be possible to use the same antenna for both the link and the service area.
1.2.5 Fiber Fed Repeaters

The fibre fed repeaters are primarily designed for coverage of tunnels and large buildings.
Leaky feeders
(can be replaced by antennas)
Tunnel
Directional OMU OMU Directional

Coupler Coupler
BTS/Node B BTS/Node B
Optic Fiber Fiber Fed Repeaters
A fibre fed repeater can be either channel selective or band selective. It receives the RF signals from the base
station via a unit which translates the RF signal to an optical signal and sends it to the repeater via a fibre optic
cable. The repeater unit can be installed up to 4 km away from the base station.
Inside the tunnel leaky feeders or antennas can be used for transmission to the user equipment.

1.3 Repeater Applications

1.3.1 Channel Selective Repeaters
1.3.1.1 Shadow Coverage and Gap Filling

When there are coverage holes caused by buildings or mountains, a channel selective repeater can be used to
extend coverage into the “dead zone”. The building can sometimes be used as physical shield to create the
necessary antenna isolation.
Repeater
Repeater
MS/UE
BTS/Node B MS/UE
The terrain is often seen as a limiting factor when striving for flawless radio coverage. The gap-filler repeaters
can be used as a complement to the network of base stations.
1.3.2.1 Low Traffic Coverage

The example shows coverage extension in an area with low traffic by using frequency translating repeaters.
A two sector base station is extended with two frequency translating repeaters. Both donor units are mounted at
the base station site and connected to the base station via directional couplers.
Each repeater has a different link frequency and transmits the frequency of the opposite base station sector, thus
minimizing interference or multi-path propagation problems. A normal handover is performed between the
repeater coverage area and the neighboring base station coverage area.
F1
RF Link Paths
F4 F2
F8
Remote unit
Remote unit
F4 F8
F2 F1
Donor unit Donor unit
BTS/Node B
Since the installation of frequency translating repeaters requires moderate antenna isolation, remote site
requirements are very moderate.

1.3.2.2 Highway Coverage

One two-sector base station feeds two frequency translating repeaters, each covering an area comparable to the
base station. This is a way to get maximum coverage out of the one base station, with one connection point for
transmission.
BTS/Node B
Since antenna isolation requirements are low for frequency translating repeaters, omni-directional antennas can
be used at the remote sites to achieve good coverage.
1.3.2.3 “Fake site” – Moving Capacity

In this application the base station is upgraded with an additional “sector” used for feeding a frequency
translating repeater to cover an area up to 20km away from the base station. This is an effective alternative
when no transmission point is available in the area to be covered. The frequency translating repeater “moves”
capacity from the base station site to the new location.
Fake Site
Remote
unit
Donor
unit
BTS/Node B
This type of installation takes full advantage of the high output power and high sensitivity of the frequency
translating repeater.

A band shifting repeater can be used in the same way as a frequency translating repeater if the user has access to
frequencies on two different bands.

1.3.4 Fiber Fed Repeaters
1.3.4.1 Tunnel Coverage

Fiber optic fed repeaters makes it possible to cover long tunnels from one or two base station sites nearby. The
OMU unit at the base station site can feed up to 24 repeaters. The repeaters distribute the signal in the tunnel
with antennas or radiating cables (leaky feeders).
Using leaky feeders is normally the most effective way to cover a tunnel, since the signal is evenly distributed
along the tunnel. Achieving good coverage in a train tunnel, for instance, using antennas can be difficult as the
trains tend to block signal propagation.
1.3.4.2 Open Area Coverage

A fibre optic fed repeater can be used in combination with an OMU to move the repeater away from the base
station to avoid antenna isolation problems.
Omnidirectional
Antenna
Directional Coupler
Fiber Fed
Repeater
BTS/Node B Optical Fiber
OMU
In this example an OMU is placed at the base station site. The RF signal is tapped from the antenna by a
directional coupler, translated into an optical signal and sent to the repeater over a fibre optic link. At the
repeater site a fibre fed repeater receives the signal, translates it back to RF and sends it to the antenna. This
antenna can be for instance omni-directional because the distance to the base station is no longer a problem.

2 Software Overview
Axell Wireless mainly supplies three different types of software; Repeater firmware, Repeater Maintenance
Console and Axell Element Manager.
2.1 Repeater Firmware

The repeater firmware is the software inside the Control Module of the repeater. It is command line based, with
simple SET and GET commands. A rich variety of commands are available to control and monitor all
subsystems of the repeater from a normal VT100 terminal emulation program, such as MiniCom (Linux/Unix)
or HyperTerminal (Windows). This also means that any standard laptop is able to control a repeater without
additional software installed.
The repeater firmware has three main tasks:
Set and configure parameters in the repeater, such as channel numbers, gain, power levels, and different
report configurations
Monitor and measure alarm sources, alarm parameters and repeater utilization
Send reports and alarms to the repeater OMC
Communication with the repeater can be performed either locally on site or remotely via a built in modem. For
local communication a terminal with RS232 interface is needed. For remote communication a computer with a
modem is needed as well as a serial communications program such as HyperTerminal™.
2.2 The RMC, Repeater Maintenance Console

RMC is an online software program with an intuitive graphical interface that simplifies control and installation
of the repeater. The RMC is a graphical shell for the repeater’s Control Module. It reads commands and
attributes from the repeater’s Control Module and displays them in an intuitive layout. This eliminates the need
to learn commands and attributes for controlling the repeater.
Login to the repeater can be made locally via the LMT port or remotely via a modem. As soon as the RMC is
connected it constantly polls the repeater for parameters such as power supply levels, in and out levels,
temperature, traffic, etc.
The RMC program can be installed from a CD. It is a Windows based application that runs on Windows 2000,
Windows 2003 Server, Windows XP and Windows Vista.
The Repeater Maintenance Console is available for all Axell Wireless repeaters.
2.3 The AEM, Axell Element Manager

AEM is a complete operations and maintenance centre for Axell Wireless repeater networks.
The AEM takes control of the repeater once the installation at site is completed. The repeater gets integrated
into the network and will be controlled by the Element Manager. During integration all repeater parameters and
statuses are downloaded into a database. The database is regularly updated with all incoming alarms and
reports, and will hence contain a copy of the repeater configuration so that current repeater information will be
accessible without setting up communication with the repeaters.
Communication between the AEM and the repeaters are message based. This means that the operator does not
have to await message delivery, but will be informed when the message is delivered to the repeater
The Axell Element Manager is a Windows™ based application that runs on Windows 2000 server, Windows
2003 Server, Windows XP and Windows Vista.
For more information please refer to the separate AEM User’s Manual.

3 Product Descriptions
3.1 Repeater Models
There are several channel selective repeater models that operate on the frequency bands 850, 900, 1800 and
2100 in the Axell Wireless program. This table provides an overview.
Off Air Repeaters Fibre Fed

Repeaters
On-Frequency, On-Frequency, Frequency Band Shifting, GSM
GSM WCDMA Translating, GSM
CSR 822/4 CSR 822/4W CSFT 822/4 CSFT 91822/4 (R,E) CSF 922/4 (R,E)
CSR 922/4 (R,E,H) CSR 922/4W CSFT 922/4 (R,E) CSFT 18922/4 CSF 1822/4
CSR 1822/4 CSR 2222/4 CSFT 1822/4 CSFT 81922/4 CSF 1922/4
CSR 1922/4 CSFT 1922/4 CSF 2222/4
3.2 Characteristics
These are some of the most important characteristics of the Axell Wireless channel selective repeaters. For
detailed information please refer to chapter 7, Specifications.
3.2.1 On-Frequency Repeaters, GSM

CSR 822/4
System GSM 850
Output Power DL, 2 channels + 37 dBm GSM/GMSK; + 34 dBm EDGE / 8-PSK average power
Gain 60 – 90 dB, adjustable in 1 dB steps
CSR 922/4 (R, E)
System GSM/EDGE P-GSM900, E-GSM900, GSM-R
Output Power DL, 2 channels + 37 dBm GSM/GMSK; + 34 dBm EDGE / 8-PSK average power
CSR 924 H
System GSM/EDGE P-GSM900, E-GSM900

Output Power DL, (4 channels) + 36 dBm GSM/GMSK / + 34 dBm EDGE / 8-PSK average power
CSR 1822/4
System GSM/EDGE 1800 MHz (DCS 1800)

Output Power, DL (2 channels) + 37 dBm GSM/GMSK; + 34 dBm EDGE / 8-PSK average power
CSR 1922/4

System GSM/EDGE 1900 MHz (PCS 1900)

3.2.2 On-Frequency Repeaters, WCDMA

CSR 822/4
System WCDMA 850
Output Power, DL (2 channels) +31 ± 1 dBm (using 3GPP TS 25.106 TM 1/64)
CSR 922/4
System WCDMA 900
Output Power, DL(2 channels) +31 ± 1 dBm (using 3GPP TS 25.106 TM 1/64)
CSR 2222/4
System WCDMA 2100

CSFT 922/4 (R)
System GSM/EDGE P-GSM900, E-GSM900 or GSM-R
Output Power (2 channels) Donor unit per carrier, DL Remote Unit per carrier, DL
+ 37 dBm GSM/GMSK IR: + 40 dBm GSM/GMSK / + 37 dBm
EDGE / 8-PSK average power
+ 34 dBm EDGE / 8-PSK
average power ER: + 43 dBm GSM/GMSK / + 40 dBm
Gain Remote Unit (2 channels) IR: 75 - 105 dB / ER: 78 - 108 dB, adjustable in 1 dB steps
CSFT 1822/4

CSFT 1922/4



CSFT 91822/4 (operates on 900 MHz, uses 1800 MHz for the link)
System GSM/EDGE P-GSM900, E-GSM900
Link Frequency Range GSM/EDGE 1800 MHz (DCS 1800)


Link Frequency Range GSM/EDGE E-GSM900

Link Frequency Range GSM/EDGE 1900 MHz (PCS 1900)

3.2.5 Fibre Fed Repeaters

CSF 922/4 (R)
System GSM/EDGE P-GSM900, E-GSM900 or GSM-R
Output Power DL, (2 channels) + 37 dBm GSM/GMSK; + 34 dBm EDGE / 8-PSK average power
CSF 1822/4

CSF 1922/4

CSF 2222/4
System WCDMA 2100

3.3 Casing
Axell Wireless repeaters are relatively small and have low power consumption (see table below). They are
housed in a die cast aluminum box which makes them light and offers good heat conduction and waterproofing.
Cooling is accomplished by convection.
The housing conforms to IP65 and NEMA 4 standards.
Dimensions and Weight

2-channel repeaters Dimensions 540 x 350 x 150 mm
Weight 22 kg
4-channel repeaters Dimensions 540 x 350 x 220 mm
Weight 33 kg
2-channel models consist of a box with a lid attached by hinges. 4-channel models consist of two identical
boxes, attached by hinges, where one box serves as a lid.
2-channel box 4-channel box
2-channel off air repeater 4-channel off air repeater

2-channel fibre fed repeater 4-channel fibre fed repeater
The repeaters are closed with two hex screws. As a

complement the repeaters can be locked with a key.
Note! The two screws must be fully tightened.
Failure to do so may affect the IP65 compliancy and
therefore any warranty.
The external connections at the bottom of the repeater
Screws
can be protected with a cover which is screwed in
place.
Lock
Connectors
The repeaters are designed to be mounted on a wall, on a pole or in a 19” rack. They should always be mounted
in a vertical position with the connectors facing downwards.
3.4 Connections
All connections are placed at the bottom of the repeater. Depending on type of repeater there are connections for
antennas, directional coupler, fibre cable, power and external alarms.
These are some examples of repeater connection layout.
Power Donor Ground Server External

antenna antenna alarms
2-channel On-Frequency repeater

Power Link Ground Server Server External

antenna antenna 2 antenna 1 alarms
2-channel, Frequency Translating or Band Shifting repeater.

Remote unit with external combiner
Power Fiber input Ground Server External

antenna alarms
2 channel Fibre Fed repeater
Antenna connections are DIN 7/16” connectors, female

Fiber connector is FC/APC. It is placed on the repeater’s casing or on the fibre optic converter inside the
repeater. In the latter case there is an inlet for the fibre cable that can be sealed to maintain the IP
classification of the box
Power is connected on a plinth inside the repeater
External alarms are connected on a plinth inside the repeater
Note!
For fibre fed repeater APC connectors need to be used
throughout the whole link between the OMU and the repeater.
Also all ODF connections need to be of the same type.
3.5 Power and Back-up Battery

The repeaters can be fed by 110/230 VAC, 50/60 Hz or -48 VDC (to be specified on order). The input is
equipped with a surge, EMI, EMC suppression filter.
Battery On/off switches
Power Supply
There is a back-up battery. In the event of a power disruption this battery will supply the modem and the
Control Module with power during enough time for the repeater to send out an alarm. The battery can be
separately switched off.

3.6 Building Blocks

All repeaters contain the same basic modules. Below are simplified illustrations of the different types of 2-
channel repeaters. 4-channel repeaters are built up of two similar units linked by hinges to form one repeater
box. In each part of a 4-channel repeater there is a splitter/combiner to distribute the signals between the
LIMPAs.
The building blocks are:

Control Module
LIMPA, Leveling Intermediate frequency Module with Power Amplifier
FDM, Filtering and Distribution Module
RefGen, Reference Generator
EAIM, External Alarm Interface Module
PSUP, Power Supply Module
Fibre Optic Converter (only for fibre fed repeaters)
PSUP PSUP
EAIM
EAIM
Ref gen
Ref gen
Control Module Control Module

Opto Interface
FDM Opto Module FDM

FDM FDM
LIMPA LIMPA LIMPA LIMPA
Power Antenna External Power Fiber input or Server External

Connectors Alarms fiber connector antenna Alarms
Layout of a 2-channel off air repeater Layout of a 2-channel fibre fed repeater
3.6.1 Control Module

The Control Module manages and controls the repeater and handles alarms. The Control Module keeps track of
all modules in the repeater based on serial numbers. Data is collected from modules within the repeater such as
MCPA, Radio Module and Fibre Optic Converter. The collected data is processed and if an error is detected the
Control Module may send an alarm via a built in modem or via Ethernet to an Operations and Maintenance
Center (OMC).
In addition to collecting data from all modules, the Control Module can also collect status of four external alarm
inputs connected to the External Interface board. The summary alarm status of the repeater can be indicated on a
relay port, available on the external interface connector. This relay can be used to indicate to external equipment
if the repeater is functioning properly.

The Control Module includes a Real Time Clock (RTC). The RTC keeps track of at what time alarms and
events occur. This RTC has its own backup battery in order to keep up proper time keeping even during long
power failures.
The Control Module contains a RS232 port used for local access to the repeater.
The Control Module can be configured in two different modes:
Stand-alone Mode – in this mode all communication is made directly with the unit – either locally or
remotely via a modem or Ethernet. The communication with the Axell Element Manager is performed
using a modem or Ethernet.
Systems Slave – being a systems slave means all communications with the Axell Element Manager is
handled by the Control module in the OMU.
The Control Module has four LEDs which give information regarding the
U S
AT
DM R
status of the repeater and if someone is logged on to the repeater.
PW
ST
US
IN
AT
DM
G
LO
ST
If the repeater is configured as a system slave the two LEDs Modem Power
M
M
and Modem Status do not fill any function and can be disregarded.
Blue LED - Login
Quick flash Control Module switched on, someone logged in locally and/or
remotely
Off (except for a quick flash every 10th second) Control Module switched on, no one logged in
Off (permanent) Control Module switched off
Red LED - Status

Quick flash Control Module switched on, one or more errors/alarms detected
Off (except for a quick flash every 10th second) Control Module switched on, status OK
Off (permanent) Control Module switched off
Green LED – Modem Power

On Modem Power is on
Off Modem Power is off
Green LED – Modem Status

On Depending on type of call:
Voice call: Connected to remote party
Data call: Connected to remote party or exchange of parameters while
setting up or disconnecting a call
Flashing Indicates GPSR data transfer. When a GPRS transfer is in progress the
LED goes on within 1 second after data packets were exchanged. Flash
duration in approximately 0.5s.
(irregular)
75ms on/75ms off/75ms on/3s off One or more GPRS contexts activated

75ms on/3s off Logged to network (monitoring control channels and user interactions).
No call in progress
600ms on/600ms off No SIM card inserted, or no PIN entered, or network search in
progress, or ongoing user authentications, or network login in progress
Off Modem is off
3.6.1.1 Modem
The repeater can be equipped with a wireless modem or a PSTN modem for remote control and supervision.
Different wireless modem types are supported – GSM, EDGE, GPRS, TETRA, etc. If the repeater is equipped
with a wireless modem a SIM card holder is mounted on the Control Module.
The repeater can also be accessed via Ethernet.
Wireless modems are placed on the Control Module inside the repeater.
A PSTN modem is placed in a separate module within the repeater.
3.6.2 LIMPA, Leveling Intermediate frequency Module with Power

Amplifier
The module named LIMPA, Leveling Intermediate frequency Module with Power Amplifier, consist of 4 main
components:
Power Amplifier (PA)
Channelizer
Synthesizer
Microcontroller for communications with the Control Module
The PA is designed using linear temperature-compensated gain
blocks and discrete RF-power transistors which are capable of
delivering the required output power.
The channelizer part consists of a down-converter with IF SAW filters, an up-converter and a post amplifier.
The channelizer also contains a power level and gain control unit.
3.6.3 FDM, Filtering and Distribution Module

The module named FDM, Filtering and Distribution Module, consists of several parts:
LNA, Low Noise Amplifier
Splitter that divides the signal in two parts
Combiner with high power capability that combines two
signals into one
Duplex filter for separation of the uplink and downlink RF
signals with the given duplex distance. The filters consist of
band-pass filters that provide excellent rejection of out-of-
band signals.
VSWR 1 detectors to monitor reflected power level on antenna port (downlink)
Microcontroller for communications with the Control Module
1
Voltage standing wave ratio

3.6.4 Fibre Optic Converter

A single band MBF repeater has only one Fibre Optic Converter. A dual or tri band repeater can have one, two
or three converters depending on the mixture of frequency bands and the requirements from the customer.
The Fibre Optic Converters contain both a receiver and a transmitter. The two optical signals are combined
utilizing WDM technology (Wavelength Division Multiplexing). Hence only one fibre is necessary for
transmission. The module also contains a function for the internal communication over the fibre.
The Fibre Optic Modules work in pairs in the system – one in the OMU and one in the repeater. One of these is
a master (Optical Master Unit) and one is a slave (Optical Slave Unit).
The Fibre Optic Converter has a pilot tone generator that is used for detecting the optical path loss in the fibre.
This information can be used for compensation of this loss. Optical loss compensation is always initiated from
the Optical Master Unit. In the Optical Slave Unit the pilot tone is normally disabled, and only enabled upon
request (from for example the Optical Master Unit).
The Fibre Optic Converter contains two optical alarm sources. These are alarms for transmitted and received
optical signal level. The levels of the received optical signals can be monitored on-line via the RMC. This is
convenient during installation and tuning of the system. The module also has two alarm sources for the
communication between the master and the slave.
O ata
ta
Rx
Tx
Da
R
o
R
pt
pt
PW
ER
DL
UL
There are 6 LEDs on the

O
module to indicate the status.
LED 1, Power, Green

On Unit is powered on
Off Unit has no power
LED 2, Error, Red
On Error detected
Off No error
LED 3, UL Data, Yellow
On Communication is ongoing in the uplink direction
Off No communication
LED 4, DL Data, Yellow
On Communication is ongoing in the downlink direction
LED 5, Opto Rx, Green
On Received RF signal on fiber channel is above threshold
Off Input level below threshold
LED 6, Opto Tx, Green
On Transmitted RF signal on fiber channel is above threshold
Off Output level below threshold

3.6.5 RefGen, Reference Generator Module

The Reference Generator generates a stable reference frequency which is distributed to the radio modules of the
system. It is used as a reference signal in the synthesizer in the repeater and also in the microcontrollers in the
MCPA and Radio Module.
3.6.6 EAIM, External Alarm and Interface Module

Four external alarm sources can be connected to the alarm module, EAIM. These sources must generate a
voltage between 12 and 24 VDC. The presence or absence of this voltage will trigger the alarm depending on
how alarm thresholds have been configured in the controller software.
The module can also supply +15V to external alarm sources. The maximum allowed load on this supply is
100mA.
One relay contact closure is provided to reflect the status of the repeater. This can be used as a sum alarm.
For installation of external alarms see 5.4.7 Connect External Alarms
3.6.7 PSUP, Power Supply

The PSUP is fed by 110/230 V AC, 50/60 Hz or -48 V DC. The PSUP generates secondary DC voltages for the
repeater modules. The input is equipped with a surge, EMI, EMC suppression filter.
The -48VDC version of the power supply is designed to turn off if the supply voltage falls below -36V (±1V). It
will turn on again as the supply voltage reaches -43V (± 1V).
On the Power Supply unit a rechargeable battery pack in mounted. This part also includes charging and
supervision electronics. The backup battery will provide the Control Module and modem with enough capacity
to send an alarm in case of input power failure.
The power supply module is connected to all other electronic modules via the distribution board.
The power supply has a switch which allows it to be set in “on” position or in “stand by”.
The battery can be switched on and off.
Battery On/off switches

The power supply has 4 LEDs to Input +6V +15V +28V

indicate the status. Power
LED 1, Input Power, Green

Slow flash Power supply unit operating on AC or DC
OFF Power supply unit not operating
LED 2, +6V, Red

Slow flash (every 10 seconds) +6V power supply operating
Quick flash +6V power supply not operating or operating with malfunction
LED 3, +15V, Red

LED 4, +28V, Red

3.6.8 Distribution Board

The distribution board serves as a distributor for power and
internal communication within the repeater.
3.6.9 Split/Combiner
In 4-channel repeaters there are four LIMPAs. The split/combiners split and distribute the signals to the extra
two LIMPAs as well as combine the signals from the extra LIMPAs.

3.7 Internal Connections

3.7.1 On-Frequency Repeaters
LIMPA LIMPA
DL2 DL1 UL2 UL1
FDM FDM
IN/OUT
IN/OUT
UL2 UL1 DL2 DL1
Donor Antenna Server Antenna
RF connections for an on-frequency 2-channel repeater
UL 3+4
DL 3+4
LIMPA LIMPA
DL 1+2 UL 1+2
Splitter/
LIMPA Splitter/ LIMPA
FDM Combiner FDM
Combiner
IN/OUT
IN/OUT
UL 1+2 DL 1+2
UL 3+4
DL 3+4
Donor Antenna Server Antenna
RF connections for an on-frequency 4-channel repeater

3.7.2 Frequency Translating or Band Shifting Repeaters
LIMPA LIMPA LIMPA

LIMPA
DL2 DL1 UL2 UL1
DL2 DL1 UL2 UL1
FDM FDM FDM

IN/OUT
IN/OUT
FDM FDM
UL2 UL1 DL2 DL1

DL2 DL1
IN/OUT
IN/OUT
UL2 UL1
IN/OUT
Directional Coupler Link Antenna Directional Couplers Link Antenna
RF connections for a 2-channel Single Donor (SD) RF connection for a 2-channel Double Donor (DD)
LIMPA LIMPA
LIMPA LIMPA
DL2 DL1 UL2 UL1 DL2 DL1 UL2 UL1
FDM FDM
FDM FDM FDM
IN/OUT
IN/OUT
UL2 UL1 DL2 DL1

IN/OUT
UL2 UL1 DL2 DL1

IN/OUT
IN/OUT
Link Antenna Server Antenna Donor Antenna Server Antennas
RF connections for a 2-channel remote unit with RF connection for a 2-channel remote unit with
Internal Combiner (IR) External Combiner (ER)
Frequency Translating and Band Shifting repeaters with 4-channels have splitters mounted in the same way as
the channel selective repeaters. In DD and ER type repeaters the splitter is mounded under the FDMs.

LIMPA LIMPA
DL2 DL1 UL2 UL1
Opto Interface
Fiber FDM
Optic
Converter
DL2 DL1
UL2 UL1
IN/OUT
IN/OUT
Fiber Server Antenna
RF connections for a 2-channel fibre fed repeater
UL 3+4
DL 3+4
LIMPA LIMPA LIMPA LIMPA

DL 1+2
UL 1+2
Opto Interface
Fiber
Optic Splitter/ FDM
Splitter/ Combiner
Combiner Converter
IN/OUT
DL 1+2
IN/OUT
UL 1+2
UL 3+4
DL 3+4
Fiber Server Antenna
RF connections for a 4-channel fibre fed repeater

3.8 Signal Diagrams

LIMPA, Downlink
Channelizer DL Power Amplifier DL

Chain 1
~
~
Donor Antenna
Server Antenna
FDM FDM
Ref
~ ~
S C
Channelizer and amplifier, chain 2
D D
C S
Power Amplifier UL Channelizer UL
~
~
C
~ Chain 1
Combiner
Ref
~ ~
S Splitter
D Duplex Filter
LIMPA, Uplink
The signal from the antenna comes in to a duplex filter that separates and filters the uplink and downlink
signals. The signal is amplified in a LNA, split and fed to the channelizers in the LIMPAs.
In the channelizer the signal is mixed down to an intermediate frequency. Each channelizer is configured to
operate on a unique narrow frequency band.
After filtering, the signal is mixed back up to the original desired frequency and amplified in the power
amplifier. It is then fed to the combiner and further on via a duplex filter to the antenna.
4-channel repeaters have the same layout, but the signals are split into four parallel flows.
3.8.2 Frequency Translating and Band Shifting Repeaters
3.8.2.1 Donor Unit, Single Donor and Double Donor
Single Donor
LIMPA, Downlink
Coupler connected to the base station

Chain 1
~
~
~ FDM
FDM Ref
Link Antenna
~ ~
S C
D D

C S
Channelizer UL
~ Chain 1
C ~
~
Combiner
Ref
S Splitter ~ ~
D Duplex Filter
LIMPA, Uplink
In the single donor the signal from the base station is split and fed into the two chains in the downlink.

In the double donor the base station uses air combining which means that two signals are fed into the repeater.
In the downlink the signal is mixed in the channelizer with a reference signal and transformed into another
frequency – the link frequency. In the uplink the original RF frequency is restored and fed back to the base
station.
There is no power amplifier in the uplink. The signal is fed directly into the base station via a 30dB coupler
and hence doesn’t need a high output power.
Double Donor
LIMPA, Downlink
FDM Channelizer DL Power Amplifier DL

Chain 1
Coupler connected to the base station
~
~
~
Link Antenna
Ref
~ ~ FDM
D
Channelizer and amplifier, chain 2 C
Channelizer and amplifier, chain 2 S

D
Channelizer UL
Chain 1
~
~
~
FDM Ref
~ ~
C Combiner
S Splitter LIMPA, Uplink
D Duplex Filter

3.8.2.2 Remote Unit, Internal and External Combining
Internal Combining
LIMPA, Downlink

Chain 1
~
~
~ FDM
Server Antenna
FDM
Ref
Link antenna
~ ~
S C
D D
C S
~ Chain 1
~
~
C Combiner Ref
~ ~
S Splitter
D Duplex Filter LIMPA, Uplink
Internal combining means that in the downlink the output of the power amplifiers are combined, filtered
and sent to the antenna.
For external combining, as below, the output from each amplifier is filtered separately and transmitted out
on one antenna port each.
The output power in a –ER (external combiner) is roughly 3dB higher than in an –IR (internal combiner),
since the combiner causes a 3dB loss.
External Combining
LIMPA, Downlink
Channelizer DL Power Amplifier DL FDM

Chain 1 ~
FDM ~
~
Ref
Link antenna
~ ~
S
D
Server Antennas

C
Power Amplifier UL Channelizer UL D
~
~
~
C Combiner Chain 1
~ ~ FDM
S Splitter Ref
D Duplex Filter LIMPA, Uplink

LIMPA
Downlink ~
~
~
To Server Antenna
Ref
~ ~
Fibre Optic
Converter FDM
To/from OMU
S C
O
E D
C S
LIMPA
D Duplex Filter ~
~
~
S Splitter Ref
~ ~ Uplink
C Combiner
The signal from the OMU comes in to a fibre optic converter that translates the optical signal to RF. The signal
goes to a splitter which distributes the signal equally to the channelizers.
The signal is amplified in the power amplifier. It is then fed to the combiner and further on via a duplex filter
to the antenna.
In the uplink the same sequence is performed. At the end of the chain the signal is translated to an optical
signal and fed back to the OMU.

3.9 OMU-Repeater System

This section is only relevant for fibre fed repeaters.
Server
Fibre Fed Antenna
Repeater
OMU
Directional RF
Couplers RF
FiberOptic
Converters
Opto Fiber
Base station
Standard OMU-Repeater application
A standard application for fibre fed repeaters, as illustrated above, consists of one or more Optical Master Units
and one or several fibre fed repeaters. The input signal to the OMU-Repeater system is tapped off a base
station 2 via a directional coupler. In the OMU the RF signal is converted into an analogue optical signal and
transported via optic fibre to the fibre fed repeater. The repeater converts the optical signal back into an RF
signal which is then amplified and transmitted via a server antenna. In the uplink direction the OMU receives
the signal from the repeater via the fibre optical cable, converts it to an RF signal and sends it back to the base
station via the coupler.
An OMU-Repeater system can be expanded to handle up to 24 repeaters, and cover a distance of to up to 20 km
of fibre between the OMU and the most distant repeater.
An Optical Master Unit, OMU, can be equipped with up to 6 fibre optic converters. If more than 6 repeaters are
needed in the network there are two ways of expanding the system.
Link several OMUs together. Up to 4 OMUs can be cascaded in this manner, and operate up to 24
repeaters as one system. When OMUs are cascaded only one is equipped with a Control Module and that
one manages the other OMUs.
Base
Station
OMU Units Repeaters
Four OMUs cascaded in one system
A laser system with two colors can operate one repeater for each fibre optic converter in an OMU-Repeater
system – one color is used for the uplink and one for the downlink. A laser system with up to six colors can
operate up to five repeaters per fibre optic converter. One color is used for the downlink which is the same
2
An OMU-Repeater system can also be fed from a repeater. In this case the signal is tapped from the repeater’s
server antenna port. This repeater in its turn can be linked to an antenna that picks up the signal off air.

for all repeaters, and in the uplink each repeater uses its own color. The connection from one repeater to
the next is done via so called add-drop couplers. If needed these couplers can be designed to balance the
downlink signal to compensate for different distances to the repeaters.
OMU Slave 1 Slave 2
1550 nm 1510 nm
1310 nm Add-drop
Coupler
Two repeaters are connected to the same converter in the OMU via the same fibre but the wavelength for the
uplink differs between the units. Slave 1: 1550 ± 3 nm, Slave 2: 1510 ± 3 nm. The downlink signal is the same
for both repeaters.
3.9.1 Access to the OMU-Repeater System

Axell Wireless repeaters and OMUs can be configured in three different ways as regards communication and
control. They can be “stand-alone units”, “node masters” or “slaves”.
Stand-alone units do not control any other unit or take control from any other unit. All communication with
a stand-alone unit needs to be made directly with the unit – either locally or remotely via a modem or
Ethernet. Most stand-alone units are equipped with Ethernet and/or a modem for this purpose.
Node Masters keep track of the slaves that are connected to it. It is the single point of contact for alarm
reports and for heart beats in the entire system, and communicates with the AEM. All configuration and
control of all units in the network go through this Node Master. Most Node Masters are equipped with
Ethernet and/or a modem for this purpose.
Slaves are linked to a Node Master and contain a slave interface allowing for a Node Master to
communicate with the slave.
An OMU-Repeater system can be designed using repeaters that operate as slaves to the OMU or as stand alone
units regarding communication, configuration, alarms etc. Either all communication is handled by the OMU
that acts as a node master and the repeaters are slaves, or each repeater (and the OMU) handles this
communications and reporting separately.
The most common configuration is the master-slave set up which has several advantages:
All nodes can be reached from any node in the system. An operator can log in from any node in the system
and access all parameters in all nodes, including those in the OMU
Only one modem is needed for remote communication and configuration of the whole system
Since the communication runs on the same fibre as the RF, this arrangement gives a reliable supervision of
the radio link. If communication between the OMU and a repeater is broken, an alarm can be generated
immediately.
Several users at a time can be logged on to the system, for instance one locally via the RS232 interface and one
remotely via modem or Ethernet. Only one user at a time can be logged in remotely.
Note! If the network has an OMU from an earlier generation 3, there are some limitations of what can be
accessed via a local login to a slave repeater.
3
The earlier versions of the OMU where called HUB.

4 Monitoring and Control

The repeater can be accessed on site via the Local Maintenance Terminal (LMT) port or remotely over a built in
modem or Ethernet in the repeater.
When an RS232 cable is plugged in to the LMT port, there are two options for communication; terminal mode
or RMC mode.
Terminal mode is accessed by using a terminal emulation software, such as MiniCom (Linux/Unix) or
HyperTerminal (Windows). 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 repeater is controlled using the Repeater Maintenance
Console, RMC.
For use of the terminal mode please refer to the documents “Common Commands and Attributes” and “GSM-
UMTS Commands and Attributes” which contain detailed description of all attributes and commands.
Firmware Documentation Structure

The attached documents “Common Commands and Attributes” and “GSM-UMTS Commands and Attributes”
together describe all functionality in the repeater. The Common part contains functionality that is common for
most Axell Wireless repeaters of the latest generation and the GSM-UMTS part contains functionality that is
specific for this repeater type.
Help Functions
When being logged in to a unit using the terminal mode the command
HELP
will list all attributes and their modes of operation and display them in alphabetic order on the screen.
Further help regarding specific commands can be had by typing
INF <command>
The INF attribute gives detailed information about a specific attribute.
4.1 Software Features - Overview

The firmware in the repeater controls and monitors all repeater parameters. 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 repeater. If the repeater is controlled by the AEM, the alarm is
also transmitted to the AEM. The repeater 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 repeater 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 repeater can send a heartbeat report to the AEM to confirm that the repeater is
functioning. The heartbeat message contains information about the RF-configuration and the alarm sources. It
ensures that the data communication from the repeater to the AEM is working properly. The latest 2 000
heartbeats (approximately) are stored in a log.
The Control Module keeps track of the exact repeater type it is controlling, and its performance parameters,
including maximum uplink and downlink gain, serial number of repeater, software version in Control Module,
controller hardware version, as well as hardware version of all included components.
The repeater can be equipped with a wireless modem (GSM, GSM-R, HSPA/UMTS, TETRA, GPRS) or a
PSTN modem mounted inside the repeater. The repeater is also equipped with Ethernet.

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 repeater is controlled by the Axell Element Manager, the AEM will automatically time synchronize
repeaters, to ensure that the time is always set correctly in the entire repeater network.
4.2 Alarm System

The Axell Wireless repeaters contain a number of different alarm sources, both analogue and digital, to ensure
that the repeater works with desired performance.
Some alarms are only relevant for certain types of repeaters. For more detailed information about the alarms
please refer to GSM-UMTS Commands and Attributes.
4.2.1 Alarm Sources
Temperature Related Alarms
Alarm Code Description Trigger

Temperature TEM Measures the temperature in the Control Temperature too high or too
Module low
Power Supply PTM Measures the temperature in the power Temperature too high or too
Temperature supply low
Radio Board RBT Measures the temperature in the LIMPA Temperature too high or too
Temperature and/or fibre optic converter low
Power Related Alarms

Power Supply Level PSL Monitors the input voltage level to the Level too high or too low
repeater
Power Supply 1 PW1 Measures the +28V out from the power Level too high or too low
supply, and in to some active modules
Power Supply 2 PW2 Measures the +15V out from the power Level too high or too low
Power Supply 3 PW3 Measures the +6.45 V out from the power Level too high or too low
Power Supply 4 PW4 Measures the backed up +6.45 V out from Level too high or too low
the power supply
Battery Level BAT Measures the power level in the battery. Level too high or too low
Repeater Performance Related Alarms

Antenna Isolation AIM An antenna isolation measurement with a Isolation too low
Measurement too low isolation between the input and
output antennas
Amplifier Chain AMD The repeater measures the input signal Expected output power too
Downlink level in the downlink chain and compares it high or too low compared to
to expected output power with regards to

attenuation in repeater. If the output power calculated level

is too high or too low something might be
failing in the amplifier chain.
Amplifier Chain AMU The repeater measures the input signal Expected output power too
Uplink level in the uplink chains and compares it high or too low compared to
to expected output power with regards to calculated level
the attenuation in repeater. If the output
power is too high or too low something
might be failing in the amplifier chain and
hence an amplifier chain alarm is triggered.
Amplifier Saturation ASD Measures saturation in the amplifier chain Saturation enters defined
Downlink downlink. level
An amplifier chain going into saturation
means that the repeater input signal level
and/or gain is not set correctly. An
amplifier going too deep into saturation
might cause the signal quality to be
decreased.
Amplifier Saturation ASU Measures saturation in the amplifier chain Saturation enters defined
Uplink uplink. level
An amplifier chain going into saturation
means that the repeater input signal level
and/or gain is not set correctly. An
amplifier going too deep into saturation
might cause the signal quality to be
decreased.
Synthesizer Downlink SZD Detects if a synthesizer in the downlink is Synthesizer unlocked
unlocked
Synthesizer Uplink SZU Detects if a synthesizer in the uplink is Synthesizer unlocked
unlocked
Synthesizer Pilot SZP Measures the pilot tone frequency Error on pilot tone
Tone Generator
BCCH/Pilot Tone PDL Measures the output power of the BCCH or Output power level too low
Downlink Pilot Tone in the downlink. If it drops
below the configured threshold an alarm is
generated.
Input Overload IOD Input overload alarms are triggered when Signal too high
Downlink there is a risk that the low noise amplifier
might be blocked by a very strong signal.
Input Overload IOU Input overload alarms are triggered when Signal too high
Uplink there is a risk that the low noise amplifier
might be blocked by a very strong signal.
VSWR alarm WRD The return loss alarm, or VSWR alarm, is Reflected signal too high
triggered when the reflected signal in the
antenna port of the repeater is too high.
Opto Related alarms

Received Optical RXO Measures the received optical signal level Optical signal level too low
Level

Pilot Tone Status RXP Measures the pilot tone level Level too high or too low
Transmitted Optical TXO Measures the transmitted optical signal No transmission

Level level
Communication Related Alarms

Communication with COM Detects errors in the communication Errors in the communication
Active Devices between Control Module and other active
module such as LIMPA, Power supply and
active FDM
EEPROM CRC check CRC Controls checksum of EEPROM to detect a Checksum wrong
in active devices corrupt memory bank.
User Related Alarms

Valid Login to VLI Detects a login to the unit, either locally or A successful login
repeater via remote connection.
User logged out from LGO Detects a logout from the repeater. A logout
repeater
Changes made by CLR Detects all changes made to repeater Changes made by a user
logged in user settings by a user logged in to the repeater.
Firmware upgraded FWU Detects when a successful firmware Upgrade successful
upgrade has been made
Firmware Upgrade FWF Detects failure in the upgrade Upgrade failed
Failure
User Administration Alarms

User Added UAD Detects when a user is added to the system User added
User Deleted UDE Detects when a user is deleted from the User deleted
system
User Promoted UPM Detects when a user gets escalated user User promoted
privileges
User Demoted UDM Detects when a user gets downgraded user User demoted
privileges
User Password UPW Detects when a password is changed Changed password
Door Alarm

Door DOO Checks if the repeater’s door is open or Door is open
closed

External Alarms

External Alarm 1 -4 EX 1-4 Monitors any alarm source, for example Error from alarm source
fire alarms or external door sensors
connected to the external interface.
Relay Output for Sum Alarm

The module for external alarms contains a relay output. The relay can be used to indicate the summary status of
the repeater. Each alarm source can be configured to be affecting the relay or not.
4.2.2 Alarms and End of Alarms

When the Control Module detects a failure in the repeater, an alarm is transmitted to the Axell Element
Manager, informing the operator about the error condition. When the alarm has ceased, an end of alarm is sent
to the AEM, stating that the alarm source is now OK.
Each “alarm” and “end of alarm” updates the AEM database with the latest status of the alarm source, ensuring
that the AEM operator always has the correct repeater status in the system.
To generate an alarm a number of consecutive measurements must first show an error state. This can be
configured for each alarm source separately.
To generate an end of alarm only one OK measurement is needed.
Alarm level
Alarm is sent after three End of alarm is sent as

seconds above threshold soon as status is OK
Alarm threshold
Time
If an alarm should constantly toggle between OK and ERROR the communications interface might be blocked.
To prevent this there is a parameter called Minimum Alarm Repetition Cycle. This parameter defines how many
minutes must elapse before a new alarm can be transmitted from the same alarm source.
Alarm level
Initial alarm End of Alarm
Three minutes have elapsed and a

new alarm is transmitted
Alarm Threshold
Minimum alarm
repetition
Time
This illustration shows an alarm source with an upper threshold, and a fluctuating level around the alarm
threshold. In this example, the first alarm will be sent as indicated. The next alarm will be transmitted after
three minutes, when the minimum alarm repetition period has elapsed.

Set Minimum Alarm Repetition Cycle

Select
“Configuration “ and
“Reports”
4.2.3 Alarm Retransmissions and Acknowledgements

As soon as the repeater detects an alarm or an end of alarm, a connection to the Axell Element Manager is
established and the alarm event is reported.
The 2 000 latest alarms and end of alarms are stored in the repeater’s local alarm log. In case an alarm is not
acknowledged the alarm will be retransmitted to the AEM after a configurable number of minutes. Allowed
values are 0 to 999. Default retransmit interval is 10 minutes.
The retransmission will be repeated a configurable number of times. This variable can be set from 0 to 99.
Default number of retries is three
Set Number of Retransmissions and Repetition Cycle for Non-acknowledged

Alarms
Select
“Reports”
4.2.3.1 Alarm Acknowledgement using the RMC

Each alarm can be manually acknowledged using the Repeater Maintenance Console. However, if the repeater
is controlled by the Axell Element Manager, a manual acknowledgement of the alarm means that the AEM will
not be aware of the change in the repeater status.
4.2.3.2 Alarm Acknowledgement using the Axell Element Manager

If the repeater is integrated to and controlled by the Axell Element Manager (via an OMU or directly), an alarm
is considered acknowledged when the alarm has been delivered to the AEM. Once delivered to the AEM, the
acknowledgement of the event is taken care of locally at the AEM, why no dial-back needs to be performed to
acknowledge the alarms in the repeater.
4.2.3.3 Alarm Acknowledgement using SMS

Note! SMS functionality is not implemented in this SW release.
If the repeater is configured to send alarms using SMS, alarm acknowledgement can be made in two different
ways.

the alarm is acknowledged as soon as the alarm SMS is successfully received by the Short Message
Service Centre
or
the alarm is acknowledged by sending a special alarm acknowledgement SMS back to the repeater from
the alarm destination.
Set Acknowledgement Type for SMS Alarms

Select
“Reports”
Pick one alternative

from the drop-down
menu
All alarms transmitted from the repeater contain a message number. Acknowledgement of an alarm is done by
sending an SMS to the repeater containing this message number.
Note! Only the defined “Primary SMS address” can acknowledge alarms.
The table below displays the format of alarm acknowledgement messages.
Message field Format Description

Repeater ID XX-YY-ZZZZ ID of the repeater that the message is intended for
Message number NNNNN Message number set by originator
Command ACT Action command
Argument ACK Acknowledge action
Argument MMMMM Message number of the alarm message to acknowledge
The message fields are separated with blanks.

For example, sending an SMS to the repeater with the text
01-42-4711 00242 ACT ACK 00023
will acknowledge alarm number 00023 from repeater 01-42-4711.

4.2.4 Alarm Format

Each alarm transmitted from the repeater contains a number of fields, in detail describing the event that caused
the alarm. The alarm is transmitted as an ASCII text string, each field separated by a blank/white space.
Using the Axell Element Manager to control the repeater, the alarm string is delivered to the transceiver for
further processing in the AEM system.
When SMS is used to control the repeater, the string is sent as clear text to the alarm address (main address).
Note! The SMS functionality is not implemented in repeaters with this SW release.
Message Format # of Description

field char.
Repeater XX-YY- 10 ID of the repeater causing the alarm. When monitoring the repeater
ID ZZZZ using the AEM, this repeater ID is set by the AEM during the repeater
installation phase. Using SMS, this repeater ID should be modified to
uniquely identify the repeater in the network.
Message # N 1 to 10 This integer value uniquely identifies this message from the repeater
and may be from 0 to 2147483648 (231).
Message ALARM 5 This text string identifies the message as being an alarm (or end of
type alarm)
Date DDMMYY 6 Day, month and year when the alarm was detected
Time HHMMSS 6 Hour, minute and second when the alarm was detected
Alarm CCC 3 Identifies the alarm type (e.g. PW1, SZU, PDL, etc)
Name
Alarm CC 2 Abbreviation for severity of the alarm. This severity varies between the
Severity different alarm sources.
CR = critical
MA = major
MI = minor
WA = warning
CL = cleared
When an and of alarm is sent, the severity is CL = cleared
Alarm CC 2 Abbreviation for kind of alarm

Class
CO = communication alarm
EN = environmental alarm
QS = quality of service alarm
PR = processing alarm
EQ = equipment alarm
Status C 1 This status identifier is 0 if end of alarm and 1 if alarm.
Hardware CCCC 1 to 5 Denotes what hardware module the alarm originates from. If not used, a
Enumerati '-' (dash) is replied.
on
Position CCCCCCCC 1 to 12 Gives detailed information about certain alarm sources. For some
Identifier CCCC alarms, such as VLI, LGO and CLR, this may contain user information.
If not used, a '-' (dash) is replied.
Additiona <Text> 60 This quoted string contains additional alarm information, such as
l text measured levels when the alarm condition was detected.

4.2.5 Alarm Class

Each alarm belongs to a class. The defined classes are:
Class Description
CO Communications
QS Quality of service
PR Software or processing
EQ Hardware equipment
EN Environment (enclosing or surrounding equipment)
All alarms are configured to a class at delivery but can be changed by the user. The external alarms do not have
a classification at delivery, but can be set by the user.
4.2.6 Alarm Severity

Alarms can be of five different severity levels.
Severity Level Description
Critical A critical error has occurred which affects the functionality of the repeater. This type
of alarm requires immediate action.
Major A major error has occurred. This type of alarm should be investigated within a short
time.
Minor A minor error has occurred. This type of alarm should be investigated, but is not
urgent.
Warning Something has occurred that does not affect the operation of the repeater but may be
important to notice. For example, someone has logged on to the repeater.
Cleared A cleared alarm. This is the end of alarm.
The severity can be defined for each alarm source in the Alarm Configuration screen in the RMC. It is
recommended not to change the default settings.

4.2.7 Alarm Configuration

A number of different parameters can be configured for how the alarms are transmitted to the repeater OMC.
Each alarm source can also be individually configured in a number of different ways.
Select
“Alarms”
Alarm
Class
Severity
Sum alam
Alarm transmission
to OMC enabled
Requires
acknowledgement
Lower and upper

thresholds
Seconds in error
before an alarm is
triggered
Class – Each alarm can be linked to one of the following classes: Common, Quality, Process, Equipment or
Environment. The class is used when the information is presented in the AEM
Severity – Each alarm can be classified regarding severity - Critical, Major, Minor or Warning
Note! It is recommended not to change the default settings.
Enabl. – If this box is ticked the alarm is transmitted to the repeater OMC (AEM)
Note! This only affects the transmission of the alarm. The alarm is still measured, and corresponding alarm
status is still displayed in the repeater status screen and in the heartbeat reports transmitted to the repeater
OMC.
Ack. – All alarms will by default be transmitted to the repeater OMC (AEM) requiring acknowledgement
(the box is checked). Disabling this checkbox removes this requirement, which means that an alarm will
only be transmitted once, regardless if an acknowledgement is received or not.
Upper and lower thresholds can be set for some of the alarms. Please refer to BSR421 Command and
Attribute Summary for details on the usage of thresholds for each alarm source.
Note! The default settings should normally not be changed.
Time – Defines how many seconds an alarm source should be in ERROR before an alarm is triggered.

External Alarms
Four external alarm sources can be connected to the External Alarm module in the repeater. These can be for
instance fire alarms or external door sensors.
The alarm sources must generate a voltage between 12 and 24 VDC. The presence or absence of voltage will
trigger the alarm depending on how alarm thresholds have been configured in the controller software. Each
alarm can also be given a unique name.
The external alarms can be set as “active high” or “active low”
As for all alarm sources a delay can be set that defines how many seconds an alarm should be in error state
before an alarm is generated.
To define names and polarity of the external alarms use the lower part of the Alarm Configuration screen.
Set the dip-switches

to configure the
external alarms
Name the alarms
The external alarms

can be given
individual names of
up to 19 characters.
Click on Edit and
insert the new
names.
For more information about external alarms see 5.4.7 Connect External Alarms
Sum Alarm
The module for external alarms contains a relay output. The relay can be used to indicate the summary status of
the repeater. Each alarm source can be configured to be affecting the relay or not.
Note! The relay status is not affected by the login / logout alarm parameters.
For installation testing purposes, it is possible to test the open / close function of the relay. This test procedure
makes sure the relay is closed for 3 seconds, then opens for 10 seconds, and finally closes for 3 seconds before
going back to original state.
The relay can be set to close or open to indicate an alarm. This can be changed by changing the polarity.
Click on Relay Test

Relay polarity

4.2.8 Alarm Monitoring

The alarms can be monitored via the RMC. Each alarm has an indicator that is either green or red.
All alarms are not valid in all repeater types. For this example a fibre fed repeater is used.
Select “RF/Status”
Amplifier, AMU
Synthesizer, SZU
Saturation Status,
ASU
Amplifier, AMD
Synthesizer, SZD
Saturation Status,
ASD
Power Level/BCCH,
PDL
Uplink Related Alarms

Amplifier, AMU The repeater measures the input and output signal levels in the uplink and compares
it with expected values. Set attenuation and ALC levels are taken into account
Synthesizer, SZU Detects if a synthesizer in the uplink is unlocked
Saturation Status, ASU The amplifier chain in the uplink has gone into saturation (gain is too high)
Downlink Related Alarms

Amplifier, AMD The repeater measures the input and output signal levels in the downlink and
compares it with expected values. Set attenuation and ALC levels are taken into
account.
Synthesizer, SZD Detects if a synthesizer in the downlink is unlocked
Saturation, ASD The amplifier chain in the downlink has gone into saturation
Power Level, PDL Measures power level of the BCCH/Pilot tone in the downlink path (disabled if the
Power/BCCH Measurement Configuration is set to Skip)

General
Door, DOO Door to repeater open
Controller Temp, TEM Temperature in Control Module too high or too

low
External Alarms, EX1-4 Alarm from external sources
Power Supply
Com, COM Error in communication with Power Supply
Temperature, PTM Temperature in Power Supply too high or too low
Power Supply Input, PSL Input power to the repeater too high or too low
Battery, BAT Power level in battery too high or too low
Power P1-4, PW1-4 +28VDC, +15VDC, +6,45VD and backed up

+6,45 VDC too high or too low
LIMPA UL
Com, COM Error in communication with module
Power P1-3, PW1-3 Relevant power input to module too high or too
low
Temperature UL, RBT Temperature in LIMPA too high or too low
Input Overload, IOU Input RF level to module too high
LIMPA DL
Power P1-3, PW1-3 Relevant power input to module too high or too
low
Temperature DL, RBT Temperature in LIMPA too high or too low
Input Overload, IOD Input RF level to module too high
Reference Generator
Power P3, PW3 Relevant power to module too high or too low
FDM Server Side
Return Loss DL, WRD The reflected signal in the antenna port is too high
Fibre Optic Unit
Temperature, RBT Temperature in Fibre Optic Converter too high or

too low
Transmitter, TXO No detectable transmitted optical signal

Received Level, RXO Received optical level too low
Pilot Tone Gen Synth, Pilot tone frequency faulty

SZP
Received Pilot Tone Pilot tone level too high or too low
Level, RXP
EEPROM CRC, CRC Faulty checksum in Opto Module
Additional Alarms
Additional power levels
and alarms is monitored
by clicking this icon
Additional temperature
levels and alarms is
monitored by clicking
this icon
Additional RF levels can

be monitored by clicking
this icon

4.2.9 Alarm Log

Recent alarms can be viewed in an alarm log that shows details about the alarms.
Select “Log” and

“Alarm Log”
Message No
Date/Time
Description
Attribute/Alarm
Source
Severity
Class
Alarm acknowledged
Acknowledgement
using RMC

4.3 Repeater Heartbeat

On regular intervals, the repeater sends a heartbeat report to the AEM to confirm that the repeater is
functioning. The heartbeat message contains information about the RF-configuration and the alarm sources. It
ensures that the data communication from the repeater to the AEM is working properly.
The heartbeat interval can be set from 1 to 1440 minutes. Setting the heartbeat to 0 disables the transmission of
heartbeats.
Slave repeaters in OMU-repeater system send the heartbeat messages to the OMU. The heartbeats are sent on to
the AEM by the OMU.
4.3.1 Heartbeat Tasks

With the heartbeat reports, a number of tasks are carried out.
4.3.1.1 Ensuring Repeater to AEM Communications path

By configuring the repeater to regularly establish a connection to the AEM, the functionality of the data
communications path between the repeater and the AEM is verified. This ensures that for instance the alarms
will be transmitted properly.
If an expected heartbeat is not received by the AEM, an alarm is generated to the AEM operator. Reasons for a
heartbeat message failing to be delivered can be:
No power – the repeater site might experience a power failure, and the battery backing up the Control
Module and modem is empty
Broken donor antenna – If the repeater antennas have been tampered with, the repeater might not get
adequate signal to establish a connection to the AEM
Failing BTS – If the feeding BTS for some reason goes down, the repeater will loose its network
connection, and hence fail to establish a connection to the Axell Element Manager.
4.3.1.2 AEM Database Synchronization

The Axell Element Manager stores all repeater parameters in a database. This database is populated during the
repeater integration into the AEM, when the AEM downloads all the repeater parameters. If the AEM operator
wants to monitor the configuration of the repeater, 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 repeater failed
to deliver the alarm to the AEM, there will be a discrepancy between the repeater configuration and the
configuration in the database. Furthermore, if a technician at site makes changes to the RF-configuration of the
repeater, the configuration will differ from the AEM configuration.
For this reason, each heartbeat report contains all the relevant RF-parameters and status of all the alarm sources
in the repeater. This means that each heartbeat report will update the AEM with all status and RF parameters.
Note! Once the repeater 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 repeater 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 repeater synchronization where all repeater parameters will be updated.
4.3.1.3 Time Synchronization

Each heartbeat message transmitted to the AEM contains a time stamp of the local time inside the repeater.
Upon reception in the AEM, the time stamp is compared to the Axell Element Manager time. If the difference
between the repeater and AEM time is too big, time synchronization is initiated by the AEM, adjusting the time
in the repeater. In this ways, we ensure that a repeater 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 repeater, once the user logs out, a heartbeat is sent to the
AEM to ensure that the time is correctly synchronized.

4.3.2 Configuring the Heartbeat

The Heartbeat is configured to be transmitted on a regular interval. As soon as the report is successfully
delivered, the repeater will wait the configured interval before transmitting the report again. The interval can be
set from once per minute to once every 1440 minutes (24 hours). Setting the heartbeat interval to zero disables
transmission of the heartbeat reports.
If the heartbeat report was not successfully transmitted, it will be retransmitted again after a configurable
number of minutes. The Control Module will try a configurable number of times to transmit the report to the
Axell Element Manager / repeater OMC.
Default retransmit interval is one minute, and three retries will be made to transmit the report. In this example a
heartbeat is sent every 24 hours and the number of retransmits has been set to 2 with a one minute interval.
Select “Configuration
“ and “Reports”
Repetition cycle
Retransmissions
Repetition cycle for
retransmission
Note! When monitoring the repeater using the Axell Element Manager, the heartbeat interval is decided by the
AEM operator as a part of the repeater to AEM integration procedure.
4.3.3 Heartbeat Format

The heartbeat report is transmitted as an ASCII text string, with a number of fields representing the RF-
configuration and status parameters, each field separated by a blank/white space.
Using the Axell Element Manager to control the repeater, the heartbeat report is delivered to the Transceiver for
further processing in the AEM system.
For detailed Heartbeat format please refer to GSM-UMTS Commands and Attributes.
4.3.4 Heartbeat Log

Recent heartbeats can be viewed in a log..
Select “Alarm
Log” and
“Heartbeat Log”
Message No
Date/Time
Description
Retransmissions
Message

4.4 RF Parameters
4.4.1 Channel Assignments
Assigning channels to a repeater is easy using the Repeater Maintenance Console. Depending on the repeater’s
configuration there are different channel assignment options. If some channels in the repeater are not used, these
need to be switched off.
Channels are configured using the standard ARFCN and UMTS conventions.
Click on the box

next to the Channel
and a list will come
up.
These are examples

from one GSM and
one UMTS repeater
Note for GSM repeaters! To ensure signal quality in the coverage area, it is important that all channels and
link channels are separated by two guard channels. For example, if channel 34 is used, next allowed channel or
link channel is 37.
Note for GSM repeaters! It is recommended that the BCCH channel is configured as chain one (1) in the
repeater. It is though possible to configure the BCCH alarm monitoring to any channel.

4.4.2 Repeater Gain

Setting the gain in the repeater plays an important role in the
repeater configuration. Since the gain affects the coverage
area of the repeater, it is in many cases desired to have as high
gain as possible. However, since incorrect gain settings might
cause the repeater to oscillate it is important to configure the
gain carefully. In fibre optic systems where several repeaters
are connected to one OMU there is also an issue with noise in
the uplink. Please refer to the OMU Manual for more
information.
The gain is adjusted by changing the attenuation of the
repeater. The setting is done for the uplink and downlink
separately.
The attenuation can be changed in 1 dB steps. If the

attenuation for example is set to 15 dB, the repeater is
downgraded 15 dB from its maximum performance.
Maximum gain in the repeater can be read from the Product
Information menu (choose Configuration/Product).
4.4.3 Power Level

The repeaters have constant gain in both uplink and downlink paths. The gain is set by defining the attenuation
as described above.
The maximum output power level from the repeater can be set. If the input signal amplified by the set gain
exceeds the set output limit, an ALC (Automatic Level Control) loop is activated. This ALC ensures that the
amplifier does not add distortion to the radio signal.
Output Power Level
ALC
Max output power
Max output power

before the ALC kicks in
Input Signal
Signal level that
generates max
output power

The maximum output power level is set in this RMC window. There
are a number of preset values to choose from. The maximum power
level can be set individually for uplink and downlink of each
channel. The power level can also be set to OFF, meaning that no
output power is transmitted out in the chain.
The power level in the downlink should be adjusted not to send

radio signals too far into neighboring cells, but yet be enough to
cover the service area. In the uplink a signal from a user close to the
repeater should not cause a transmit of too high power into the base
station antenna.
In channel selective repeaters, the uplink and downlink power levels
are normally set to the same value, while the values in the frequency
translating or band shifting repeaters depend on the link budgets for
the installation.
For frequency translating or band shifting repeaters the signal
strength of the link channel should not be set too high – just enough
to reach between the donor and the remote site.
In fibre fed repeaters the uplink should be configured to obtain a
transparent feedback to the base station.
Note! Chains not used in the repeater must have power level set to
OFF.
4.4.4 Amplifier Saturation

If the output power reaches a certain limit in the repeater the ALC is activated, as described above. In the same
RMC window as above there is an Amplifier Saturation indicator and a saturation status alarm. The saturation
indicator detects problems with the system setup or environment and can also be used during repeater
installation and configuration.
The indicator has 2 levels for WCDMA repeaters:
Linear: green
Saturated: red
The indicator has 4 levels for GSM repeaters:
Low: below optimum settings
Ok: working in the optimum range
High: going into saturation
Critical: well into saturation
When the repeater is configured the gain in the downlink should be increased until the saturation indicator
reaches the optimum range. This ensures that the repeater has optimized gain settings. For GSM repeaters the
chain with the BCCH should be used.
Note! If possible check the activity level of the base station at the time for the repeater set up. The base station
output can vary a lot. If the repeater is set up during a low activity period it might be run into ALC when the
base station activity becomes higher.

4.4.5 Input / Output Levels

The input and output power levels to and from the repeater are
constantly monitored for each chain separately. The input level is
measured directly at the input of the LIMPA. The output power is
measured directly before the output of the LIMPA.
The measurable input power to the repeater ranges from -110 dBm to
about -25 dBm. The output power level varies depending on repeater
model. The dynamic range on the output power is roughly 25 dB,
meaning that a repeater with a maximum output power of 30dBm
can detect output power levels down to approximately 5 dBm. If the
output power level is lower than lowest detectable level, the RMC
reports a dash.
By using these values together with the gain settings in the repeater it
is possible to monitor the functionality of the amplifier chains. A too
low output power in a chain might for instance indicate some
problem with the LIMPA.
These measurements can also be useful during installation of the repeater, for example by monitoring the input
signal level constantly while aiming antennas towards the donor unit detecting the direction for the maximum
signal level. Monitoring the output level is helpful in determining how much the gain must be increased to reach
maximum output power.
Note! The uplink power levels will only be displayed when there is a user in the repeater coverage area
generating traffic. For GSM repeaters also, DTX (Discontinuous Transmission Mode) enabled networks will
cause the mobiles to generate traffic only when the subscriber is actually talking. This will cause the uplink
meters to fluctuate a lot. The same applies to the downlink channels not configured as BCCH, since RF is only
transmitted in the traffic channels if a call is handled by this TRX.
4.4.6 Return Loss (VSWR)

The server FDMs contains circuitry to measure the reflected power levels back from the connected server
antenna cables. A too high level on the reflected power generates an alarm.
Typical reasons for a high reflected power level can be an antenna connector being improperly tightened, a
broken cable or a broken antenna.
Frequency Translating and Band Shifting –ER (external combining) repeaters contain two server FDM’s, one
for each server antenna, and hence two reflected power levels are measured. All other repeater types contain
only one server FDM.
The level for when to generate an alarm is configurable as number of dB’s difference between forward and
reflected power levels. Default level is 10 dB, and normally this value should not be changed.
The return loss is displayed in the same window as the power levels.

4.4.7 BCCH Configuration for GSM Repeaters

The BCCH channel can be configured on any chain. The most common though, is to configure the BCCH on
chain 1. This is also how the repeater is configured when it is delivered.
The repeater monitors the BCCH output power in the downlink to ensure that the power level stays above a
configurable threshold. If the level drops below the threshold, for example if an obstacle is raised between the
feeding base station and the repeater, an alarm is generated. The threshold level is set in the Alarm
Configuration window.
In each chain the BCCH can be configured in three different ways:

Required: the output power must be present on this chain
Either: the output power must be above the threshold on this or
any of the other chains configured
Skip: the output power is not measured on this chain
By default, the repeater is configured with “Required” in chain 1,
and “Skip” in the other chains. This means that if the BCCH drops
in chain 1, an alarm is generated.
Examples of how to use the BCCH configuration:

Two 1-channel sectors are to be transmitted through a
frequency translating –ER repeater, where each sector is
transmitted out via separate antennas. Both channels need to
have a constant output power above the threshold. In this case
both chains should be configured as ”Required”.
The base station supports BCCH “fall-over”, where the BCCH
will automatically switch over to TRX 2 in case the default
BCCH TRX fails. Configuring the repeater as “Either” will
cause the repeater to require output power on chain 1 or 2. In
this case the BTS will generate an alarm, why we do not need
an alarm in the repeater OMC as well.

4.5 Hardware Identification

A repeater contains a number of different modules. Some of these are active devices meaning that they contain a
micro controller used for monitoring module parameters. Some are passive devices, for example the external
alarm interface.
The Control Module communicates with the active devices using a master/slave configuration, where the
Control Module is the master and the active devices are slaves. Each active device uses its serial number as an
address. A slave only replies to requests with the correct address information.
During manufacturing the repeater is configured with all the serial numbers of all the devices in the system. For
passive devices, the article number of the device is added. Once the system is configured, the Control Module
polls all the active devices for article numbers and production information as well as software versions and
statistics of the active devices.
Via the RMC the full repeater inventory can be read, including statistics of the active devices.
When a login to a repeater is made using the Repeater Maintenance Console, the RMC detects the repeater type
and adjusts the user interface correspondingly. The same RMC can be used for all repeater types.
Via the RMC basic information about the repeater configuration can be monitored.
Select
“Configuration” and
“Product”
General repeater
information
Hardware devices
installed
Active devices
installed
Control Module
information
More details regarding

selected active item
RP Parameters

4.5.1 Replacing/Reconfiguring Hardware Modules

If a module needs to be changed it is important to update the repeater with the new hardware information. For
active devices this is crucial to ensure communication between the new module and the Control Module. For all
devices it gives an up-to date inventory of the entire network.
The hardware is reconfigured by logging in to the repeater via the RMC and switching to Terminal Mode. If the
change concerns an active or passive device the command syntax varies slightly.
Format for replacing Active devices:
HARDWARE REPLACE <Old Serial> <New Serial>
where <Old Serial> is the serial number of replaced module, and <New Serial> is the serial number of the new
module.
Example:
HARDWARE REPLACE 4711 56AR
replaces serial number of active device with serial number 4711 with a new hardware having serial number
56AR.
Format on replacing Passive devices:
HARDWARE REPLACE <Old Serial> <New Serial> <New Article Number>
where <Old Serial> is the serial number of replaced module, and <New Serial> is the serial number of the new
module and <New Article Number> is article number of new hardware.
Example:
HARDWARE REPLACE 540R 56UU J691030A
Each change of hardware is kept in a log. In order to read out the log, use command
HARDWARE LOG
which displays all hardware changes that has been made to the system, including local time point for
replacement.
Example:
HARDWARE LOG
Reply:
2007-10-12 14:45:35 Replaced active device serial 4711 with 56AR. Device type:
Reference Generator
2007-10-12 14:50:03 Replaced passive device serial 540R with 56UU article number
J691030A. Device type: External Alarm Interface
Note! In order to read out current hardware configuration, refer to attributes HDC, HDI, ADC and DDI.
4.6 Tag and ID

When the repeater is integrated into the Axell Element Manager the repeater is assigned a repeater ID, which is
a unique identifier in the repeater network. This ID is used by the AEM to keep track of the repeaters in the
AEM database.
The repeater Tag can be used to give the repeater a more logical name, such as the site or installation place. If
Tag is set during site installation, this can easily be read by the AEM during AEM integration, giving the AEM
operator a clear identification of the site.
The repeater tag can be locked so that the tag can not be accidentally changed from the AEM.
Refer to section 5.8.2 Set Repeater Name (TAG) for information about how to set the repeater Tag.

4.7 User Access

Several users at a time can be logged on to a Repeater, for instance one locally via the RS232 interface and one
remotely via modem. There is one default user name and password defined for the repeater.
User Name Password

avitec AvitecPasswd
Note! Both the user name and the password are case sensitive.
The password can be changed and new accounts be added once a logon has been made. This is made in terminal
mode. Please refer to the GSM-UMTS Commands and Attributes.
A user will be logged out after a configurable number of minutes of inactivity. This time can be defined via the
RMC.
4.7.1 Configure Automatic Logout

Select “Configuration”
and “Communication”
Note! A password for the repeater’s communication with the AEM can be set in the box above but it is
recommended that it is done from the AEM, and NOT from here.
4.7.2 Local Access

Local access is achieved via a RS232 interface to the LMT port in the repeater. This port is accessible inside the
repeater. The USB connector is not activated in this version of the repeaters and cannot be used.
4.7.3 Remote Access

Remote access is achieved via modem or via Ethernet. Different types of modems are supported, for example
GSM, GSM-R, HSPA/UMTS, TETRA, GPRS and PSTN.
The modem is either placed on the Control Module or as a separate unit. Ethernet connection is available on the
Control Module.
4.8 Integration into AEM

When the repeater has been installed at site and the remote communication has been enabled, either through the
repeater’s own modem or via an OMU, the repeater can be integrated to the Axell Element Manager. This is
done by the operator of the AEM. After entering the telephone number to the repeater, the AEM dials up the
repeater, downloads all the repeater parameters and statuses into a database. When all parameters have been
downloaded, the AEM configures the repeater with the telephone number where alarms and reports should be
sent, and optionally with a secondary telephone number where the repeater can dial in case connection to
primary number fails.
When heartbeat reports and alarms are sent from the repeater to the AEM also the latest information about the
status and RF-configuration is included. This means that the AEM operator always has information about the
current status in the AEM database (and do not need to call the repeater to find this out).
Note! Once the repeater is integrated into the AEM, all changes to the repeater should preferably be done from
the Axell Element Manager in order to ensure that the database always contains correct information.

4.9 Upgrading Firmware

The firmware can be upgraded via a terminal emulation program or z-modem protocol. For instructions please
see Common Commands and Attributes, section 15 Firmware Upgrade.

5 Installation
5.1 Site Installation Advice
This section (5.1) is foremost relevant for GSM repeaters.

In an on-frequency repeater there are two antennas – one donor antenna to pick up the signal from the base
station and one server antenna to serve the coverage area.
Donor Antenna
Recommended isolation is minimum 15dB

higher than the repeater gain (typically 25m)
Server Antenna
Coaxial cable diameter of ½” or

more is recommended
Repeater
Site installation for an on-frequency repeater
Example
This example illustrates the various signal levels and antenna gains needed to form a properly functioning
repeater system
Received signal level -72 dBm

Donor antenna (4 ft dish) +25 dBi
Cable loss (100 ft of 7/8 inch) -2 dB
Input to repeater -49 dBm
Gain of repeater (example) +86 dB
Output from repeater +37 dBm
Server antenna gain +13 dBi
Repeater ERP +48 dBm

The donor antenna faces the base station. Free line of sight is desirable but not necessary if the signal strength at
the exact location of the antenna is strong enough.
The server antenna may be mounted above or below the donor antenna depending on the site conditions.
Important is the vertical separation needed to achieve adequate isolation between antennas. The isolation has to
be at least 10-25 dB higher than the repeater gain (the higher number for EDGE). This may well be in the region
of 20 meters or more. Other alternatives are metal screening with wire mesh or horizontal antenna separation.
A high gain antenna will help in minimizing the overall path loss to achieve the desired output power. Donor
antenna gains are typically 20 to 25 dBi, while server antennas are often 10 to 15 dBi. The server antenna
normally has a horizontal beam of 60° to 120°. Donor antennas should have a horizontal and vertical beam
width of less than 30° to correctly select the donor base station (instead of other nearby base stations).
This table can be used as a guideline for antenna separation. Antennas are assumed to be highly directional and
pointed in the opposite direction.
Vertical Antenna separation Horizontal Antenna Separation

Separation (m) Isolation (dB) Separation (m) Isolation (dB)
5 75 5 45.5
10 87.1 10 51,7
20 99,1 50 65,5
30 106.2 100 71.5
40 111,2 150 75,1
50 115 250 77,6
The table demonstrates that vertical separation is much more effective
The physical separation between the donor and server antennas has been calculated using the following
formulas.
Vertical Separation: I (dB) = 28 + 40 log (D/λ)
Horizontal Separation: I (dB) = 22 + 20 log (D/λ) – (Gd – Gs)
I = Isolation
D = Distance between donor and server antennas (m)
λ = Wavelength (m)
Gd = Gain of donor antenna facing server antenna (dB)
Gs = Gain of server antenna facing donor antenna (dB)

5.1.2 Frequency Translating and Band Shifting Repeaters

A Frequency Translating or Band Shifting Repeater consists of two parts – a donor unit and a remote unit. The
donor unit is installed at the base station site and connected to the base station through a 30 dB RF coupler.
Base
Station
Antenna
Link
Antenna
Coaxial cable diameter of ½” or more

is recommended
Coupler Single Donor Unit
Base Station
Site Installation for a frequency translating or band shifting repeater – Single Donor Unit
Base
Station
Antennas
Link
Antenna
Tx/Rx 1 Tx/Rx 2
Coaxial cable diameter of ½” or

more is recommended
Couplers Double Donor Unit
One or two
base stations
Site Installation for a frequency translating or band shifting repeater – Double Donor Unit
A separation of at least 2 carrier bands (600 kHz) is necessary between the link frequencies and the Broadcast
Frequencies. In the illustration below the link carriers are F6 and F7 and the Broadcast Carrier Frequencies are
F1 and F2 which gives more separation than is needed.

F1 and F2
F6 and F7
Link Antenna
Server Antenna
Link Antenna
F1 and F2
16mm2 Repeater Donor Repeater

Coupler Unit Remote 16mm2
Ground Ground
Cable Unit
Cable
Base Station
It is important to remember that a whole sector must be used when installing a this type of repeater. The base
station sector using F1 and F2 is transmitted to the repeater. The base station sector used must have the same
number of carriers as the repeater. At the remote site an input signal greater than -75dBm is desired. An input of
-65 dBm is necessary to deliver an output of +40dBm.
Example
This example illustrates the signal levels and antenna gains needed to form a properly functioning repeater
system.
Received signal level -87 dBm
Donor antenna (4 ft dish) +25 dBi
Input to repeater -64 dBm
Gain of repeater (example) +105 dB
Output from repeater +41 dBm
Server antenna gain +13 dBi
Repeater ERP +52 dBm
The isolation between antennas at the remote site seldom needs to be more than 75dB. This value can be
achieved with a limited antenna displacement, often as low as 3 meters. The relatively modest isolation
requirement allows the use of omni-directional antennas for coverage. By using another band for the link the
isolation requirement between antennas at the remote site becomes very low. It might in some applications even
be possible to use the same antenna for both the link and the service area.
A high gain antenna will help in minimizing the overall path loss to achieve the desired output power. Donor
antenna gains are typically 20 to 25 dBi, while server antennas are often 10 to 15 dBi. The coverage antenna
normally has a horizontal beam of 60° to 120°. Donor antennas should have a horizontal and vertical beam
width of less than 30° to correctly select the donor base station (instead of other nearby base stations).
This table can be used as a guideline for antenna separation. Antennas are assumed to be highly directional and
pointed in the opposite direction.
Vertical Antenna separation Horizontal Antenna Separation

Separation (m) Isolation (dB) Separation (m) Isolation (dB)
5 75 5 45.5

10 87.1 10 51,7
20 99,1 50 65,5
30 106,2 100 71,5
40 111,2 150 75,1
50 115 250 77,6
The table demonstrates that vertical separation is much more effective
The physical separation between the donor and server antennas has been calculated using the following
formulas.
Vertical Separation: I (dB) = 28 + 40 log (D/λ)
Horizontal Separation: I (dB) = 22 + 20 log (D/λ) – (Gd – Gs)
I = Isolation
D = Distance between donor and server antennas (m)
λ = Wavelength (m)
Gd = Gain of donor antenna facing server antenna (dB)
Gs = Gain of server antenna facing donor antenna (dB)

A fibre fed repeater needs to be fed from an OMU which translates the RF signal to an optical signal. The server
antenna is often replaced by a leaky feeder.
Base Station
Antenna
Server Antenna
(or leaky feeder)
Coaxial cable
diameter of
Fiber Fed
½” or more is
Repeater
OMU recommended
Base Station
Fiber Cable
Site installation for fibre fed repeaters
For more information about OMU-Repeater systems please see the OMU Product Description and User’s
Manual.
Note!
FC/APC connectors need to be used
throughout the whole link between the HUB/OMU and the repeater.
Also the ODF connections need to be the same type.

5.1.4 Link Budget

It is important to make a link budget before the installation is completed. This budget will give the necessary
input for tuning the system and to ensure good system performance.
This is and example based on a frequency translating repeater.
Parameters
These fixed parameters are used
base station sensitivity (without diversity gain) -106 dBm

base station output Power +41 dBm
Donor unit output power +33 dBm
Remote unit output power +40 dBm
5.1.4.1 Downlink Path

The Downlink path is quite straightforward to set up in a repeater installation, and also gives a good indication
of the actual path loss between the donor and the remote unit. The gain in the units is simply adjusted until the
desired output levels are achieved. This procedure is simplified by the built in monitoring functions in the Axell
Wireless repeaters.
Remember though, that the repeater is not a piece of measurement equipment, and has a limited accuracy when
presenting input and output levels. (+/-3dB and +/-2dB respectively)
Here two different link path losses will be analyzed, representing two extremes regarding the distance between
the donor and remote unit: 6.5 and 26 kilometers. Free space path loss is assumed in both cases. (Feeder losses
are varied to get further extreme values).
Total Link loss (6.5km):

-0.5 + 15 -108 +15 - 0.5 = - 79dB
| | | | |
| | | | --------- Feeder loss between Remote unit and Link antenna
| | | ---------------- Link antenna at Remote site 15dBi
| | ----------------------Free space path loss at 925MHz / 6.5km
| ---------------------------Link antenna at Donor site 15dBi
---------------------------------Feeder loss between Donor unit and link antenna
Total Link loss (26km):

-2.5 + 15 -120 +15 - 2.5 = - 95dB
| | | | |
| | | | -------- Feeder loss between Remote unit and Link antenna
| | | ----------------Link antenna at Remote site 15dBi
| | ---------------------Free space path loss at 925MHz / 26km
| --------------------------Link antenna at Donor site 15dBi
---------------------------------Feeder loss between Donor unit and link antenna

The downlink path based on the above link loss calculation for 6.5 and 26 kilometers.
BTS Coupler Donor Unit Link Path Remote Unit
G=xdB G=-30dB G=22dB G=-79dB G=86dB
P=+41dBm P=+33dBm P=-46dBm P=+40dBm
BTS Coupler Donor Unit Link Path Remote Unit
G=xdB G=-30dB G=22dB G=-95dB G=102dB
P=+41dBm P=+33dBm P=-62dBm P=+40dBm
Note that the shorter link distance gives the opportunity to reduce the donor downlink gain and increase the
remote downlink gain. This will reduce the output power in the link antenna and minimize interference caused
by the link, and thereby simplify frequency planning.
The longer link distance is probably close to the maximum useful distance, since timing advance will only allow
a repeater cell radius of 5-6 kilometers in this case. (The delay through the repeater chain is typically 2 x 6 us,
equal to an increase of timing advance by 6-7 units)
In the case of a base station with extended range capability longer link paths are possible, but then link antennas
with more gain should be considered. 20dBi antennas have been used in some installations, reducing total link
loss by 10dB compared to the above numbers. Keeping everything else constant, this would allow for another
23km of link distance.
5.1.4.2 Uplink Path

The settings of the Repeater Uplink path requires much more careful planning than the Downlink. Very
different results can be obtained depending on the Repeater Uplink gain setting, and there will always be a trade
off situation between the Repeater cell sensitivity and base station cell sensitivity. Low Repeater Uplink gain
will result in poorer Repeater cell sensitivity but only a small base station cell sensitivity degradation. The
opposite is also true; high Repeater Uplink gain will result in good repeater cell sensitivity but a larger reduction
in base station cell sensitivity.
The calculations to determine the sensitivity in the Repeater cell and the base station cell is based on the
formula for determining the total noise figure for a cascade of amplifiers and attenuators:
NF1 NF2 NF3 NF4

G1 G2 G3 G4
NFtot = NF1 + (NF2-1)/G1 + (NF3-1)/(G1*G2) + (NF4-1)/(G1*G2*G3 ) + … (units, not dB’s)

This equation is basically used to find the total noise figure at two points in the cascade made up by the repeater
installation. Note that if there is a device in the chain that is affected by thermal noise from an antenna, the
equation has to be modified for that device. E.g. if device 3 is connected via an aerial connection, its

contribution to the total gain is

NF3/(G1*G2).
1. The first point is the entire chain including the base station receiver noise figure. This value is then directly
used to calculate the repeater cell sensitivity.
2. The second point is the same cascade excluding the base station receiver and coupler noise figure. This
noise figure is, in combination with the gain to this point, converted to an equivalent noise floor. This is
then added to the base station receiver equivalent noise floor. The sum of the noise is then converted back
to a noise figure used to calculate the base station cell sensitivity.
First the equivalent base station noise figure corresponding to the base station sensitivity must be calculated
from the following equation:
Eq. BTS noise figure = -106 - ( -174 + 54 + 8 ) dB = 6 dB
C/N for 0.4% BER (ETSI ETR 103)

10 x log(BW) BW=251kHz (ETSI ETR 103)
Thermal noise floor
BTS sensitivity
This value is used in all calculations below.
Example 1
“Rule-of-thumb” setup with 26 km link
As a starting point (”rule of thumb”) the uplink gain can be set equal to the downlink gain settings.
For the -95dB link this will give the situation shown in the figure below:
Remote Donor
Link path Coupler BTS
Unit Unit
G=102dB G=-95dB G=22dB G=-30dB G=xdB

NF=3dB NF=95dB NF=5dB NF=30dB NF=6dB
NFtot=8,9dB
Gtot = -1dB
NFtot=4,2dB
The 8.9dB noise figure through the repeater chain corresponds to a sensitivity of
-174 + 54 + 8 + 8.9 dBm = -103.1 dBm

| | | |
| | | ---------------- Repeater chain total noise figure with base station
| | --------------------- C/N for 0.4% BER (ETSI ETR 103)
| ---------------------------- 10 x log (BW) BW = 251kHz
---------------------------------- Thermal noise floor
The noise floor from the repeater chain at the base station receiver input is:
-174 + 54 + 5.5 - 1 dBm = -115.5 dBm

| | | |
| | | ---------------- Total gain in Repeater chain
| | --------------------- Repeater chain total noise figure without base station &
coupler
| ---------------------------- 10 x log (BW) BW = 251 kHz
This must now be added to the base station receiver noise floor, which is:
-174 + 54 + 6 dBm = -114.0 dBm

| | |
| | --------------------- base station receiver noise figure
| ---------------------------- 10 x log (BW) BW = 251 kHz
And when they are added the total noise floor at the base station receiver input becomes:
10 * LOG [10^(-115.5/10) + 10^(-114.0/10) ] = -111.7 dBm
This is a 2.3dB higher base station receiver noise floor compared to the starting value (114-111.7=2.3), which
means that the base station receiver sensitivity has degraded from -106 dBm to -103.7dBm without diversity.
Summary of example 1:
The calculations in example 1 used a very simple setup technique for the uplink path. The gain in the Uplink
was simply set equal to the Downlink gain in both the Donor and Remote unit. This resulted in:
Sensitivity in Repeater cell = -103.1 dBm
Sensitivity in base station cell = -103.7 dBm without diversity, a reduction of 2.3dB.
Note that the base station Diversity receiver will maintain its original sensitivity of -106dBm since no Repeater
noise it emitted into its input. However, the diversity gain will be lower than normal because of the Repeater
noise emitted into the base station main receiver input.
Also note that all traffic through the Repeater will only enter the base station main receiver input, NOT the
diversity receiver input. This may cause a ”Diversity alarm” on some types of base station’s. This is normal and
should be a simple matter of configuring the alarms in the base station.
Example 2
26 km link with high repeater cell sensitivity
To get good Repeater cell sensitivity, the Uplink gain must be increased compared to example 1. If the gain
from the Repeater server cell antenna to the base station receiver antenna input is positive (larger than 0 dB), the
Repeater can in fact be considered to be Tower Mounted Amplifier (TMA). The major difference is of course
that the antenna is located 26km from the base station in this case. The sensitivity of the original base station
cell will be degraded more than in example 1 because the noise floor will be higher at the base station receiver
input.
The example 2 setup looks like the figure below:

Remote Donor
Unit Unit

NF=3dB NF=95dB NF=4.5dB NF=30dB NF=6dB
NFtot=5.3dB
Gtot = +6dB
NFtot=4.2dB
Doing the calculations yields:

It is obvious that the increased Uplink gain has improved Repeater cell sensitivity on the cost of the base station
cell sensitivity.
Example 3
6.5 km link with 2dB lower gain in the downlink compared to uplink
Remote Donor
Unit Unit

NFtot=10.5dB
Gtot = -3dB
NFtot=5.2dB

This example shows a relatively small reduction in the base station cell sensitivity on the cost of a rather poor
Repeater cell sensitivity. In this case however, it is possible to increase the Uplink gain in the Remote unit and
reduce it equally much in the Donor unit. This will improve the overall noise figure as dictated by the NFtot
equation on page 3. This is examined in the next example.
Example 4
6.5 km link with high base station sensitivity and optimized repeater sensitivity
The Donor Uplink gain in example 3 was 22dB. Since the minimum configurable gain in the Donor unit is
12dB, it can be reduced by 10dB. This is compensated for in the Remote unit and this setup looks like:
Remote Donor
Unit Unit

NFtot=10.1dB
Gtot = -3dB
NFtot=3.7dB


Although the improvement compared to Example 3 is only a few tens of a dB, the ”cost” of the improvement is
just a few moments of calculations. With more total Uplink gain the improvement is larger. See the next
example.
Example 5
6.5 km link with optimized repeater sensitivity
Remote Donor
Unit Unit

NFtot=6.1dB
Gtot = +3dB
NFtot=3.2dB

Compared to example 4, the repeater sensitivity has been improved by 4dB but the base station sensitivity has
been reduced by 2dB.
Summary
It has been shown by several calculation examples that some care is needed when the Uplink gain is configured
in a CSFT installation if optimum sensitivity is desired. However, ”rule of thumb” setup will only cause a small
base station sensitivity degradation with a typical base station, but Repeater cell sensitivity will not be optimum.
Note that feeder looses between Repeater server antenna and Remote unit are not included in the calculations.
5.2 Engineering Considerations

This section is foremost relevant for GSM repeaters.
5.2.1.1 Minimum Channel Separation

Axell Wireless recommends a minimum spacing of two GSM channels between the carriers in the amplifier
chains. These two "guard channels" create a centre-to-centre separation of 600 kHz.
Decreasing the spacing may lead to degraded performance.
5.2.1.2 Minimum Link Channel Spacing

When setting up a frequency translating repeater Axell Wireless recommends a spacing of two GSM channels
between the link frequency and the radio frequency. These two "guard channels" create a centre-to-centre
separation of 600 kHz.
Decreasing the spacing may lead to degraded performance.
5.2.1.3 Gain Adjustment

Use only the required power to cover blind spots or coverage areas, to minimize border overlap with the donor
base station
Optimize repeater gain levels to achieve system path balance and an acceptable noise level contribution

Reflections, phase fluctuations and other variables can all affect the quality of radio traffic and on site
adjustments and measurement will always have to be carried out to ensure reliable radio communication.
5.2.1.4 Overlapping Coverage

Ideally, the repeater system will be engineered with minimal overlapping coverage between the donor base
station and the repeater. However, the mobile unit will occasionally receive signals from both the donor and the
repeater at similar levels. This situation is comparable to a mobile receiving multiple signals at varying times
due to multi-path propagation.
The GSM standards require that systems must accommodate up to 16μs of multi-path delay for two received
signals that are less than or equal to 10dB apart. The CSR922 repeater contributes a maximum signal delay of
6μs.
5.2.1.5 How to use the Link in Frequency Translating Repeaters

Calls cannot be connected via the link frequencies for the following reasons.
The mobile station (MS) searches for the Broadcast Control Channel (BCCH) beamed from the Base
Transceiver Station (base station) Even though the MS may find the frequency translated link signal BCCH
transmission; it will not be possible to initiate a call through it.
When a call is initiated, the base station switches from BCCH to the Stand Alone Control Channel which (apart
from other information) instructs the MS which frequency (ARFCN) to use during the call. This makes the MS
switch back to the non-frequency translated ARFCN (base station frequency), where it will find no base station
signal and the call is aborted. The same is true when logging into the network.
Note! The BCCH, SDCCH, and TCH channels are logical GSM channels, not to be confused with Absolute
Radio Frequency Channels (ARFCN). Only the latter are associated with specific frequencies.
5.2.1.6 Frequency Hopping and Repeaters

Frequency hopping usually means that the input baseband traffic at frame level is switched between fixed
frequency RF-channels. The Axell Wireless channel selective repeater with appropriate number of channels can
function with this kind of hopping.
However, frequency hopping can also mean that the frequency of each transceiver is changed in phase with
transmission frames. This is usually called synthesized hopping. Being more complex than the baseband type, it
has not been widely implemented in GSM networks.
When GSM is evolving into EDGE, traffic will be IP-packet based. IP-traffic studies show that frequency
hopping does not improve the capacity or performance of the channel. A tendency is that frequency hopping
will not be frequently used in EDGE networks.

5.3 Prepare the Site

5.3.1 Site Selection
Site selection is one of the most critical decisions affecting the overall performance of the system.
Repeater locations
These are examples of common repeater locations.
roofs of buildings adjacent to the affected area with the antennas mounted to the penthouse or building
sides
top of a hill that is obstructing the donor site’s coverage, with the antennas mounted on poles at ground
level
a water tower with antennas mounted at the top
an existing utility pole with equipment and antennas mounted below any existing power lines
a newly installed pole or tower
Important Issues
There are a few important considerations to be made while choosing the best possible site for a repeater:
Ensure access to commercial power (sun-panels is an option)
Ensure adequate signal strength. For example: to obtain the maximum output, e.g. +37 dBm, from an on-
frequency repeater an input signal of approximately -53 dBm is needed into the repeater4. To obtain the
maximum output from a Frequency Translating Repeater’s remote site, e.g. +40 dBm, an input signal of -
65 dBm is needed.
A conventional channel selective repeater must be located where the base station signal strength is strong
enough to be recognized by the system. It should also be located no more than 15 km from the donor site
and 5 km from the furthest area to be served.
Ensure line of sight (LOS) between the base station antenna and the repeater’s donor antenna for channel
selective repeaters, and between the link antennas for frequency translating repeaters. If the signal strength
is adequate, line of sight may in some cases not be necessary.
5.3.2 Antennas
Select antennas for the system with the proper directivity and high front-to-back ratio in order to optimize
repeater coverage and system noise performance. Ensure adequate antenna isolation for the chosen repeater
type.
Link antennas typically have a narrow horizontal and vertical beam width (less than 35 degrees) and high gain
(15 – 25 dBi). The narrow horizontal beam width will keep interference from the repeater link channel to a
minimum. Parabolic disc antennas which offer beam widths of <10 degrees are ideal for both donor and remote
link antennas.
Server antennas are determined by the type of area to be covered. For a conventional repeater it can be any
standard GSM base station antenna that has a good front to back ratio (>=25 dB) and between 30 and 120
degrees horizontal beam width, depending on the desired coverage area. For a frequency translating antenna it
may be an omni antenna.
Use compass or planning tool to get the exact direction and tilt of the antenna
4
The input signal to the antenna needs to be -71 dBm if the antenna gain is 18dBi

Antenna Types
For server antenna purposes panel antennas are suitable for On-Frequency repeaters and omni antennas or
directional antennas for Frequency Translating Repeaters.
Link antennas and pick-up antennas are often narrow beam panel antennas with high gain for On-Frequency
repeaters and narrow beam antennas with gain depending on distance for Frequency Translating Repeaters
Antenna Direction
Direct repeater coverage away from the donor cell to minimize RF signal coverage overlap. If the base station
has different sectors (in a frequency translating installation) always choose to use the carriers used in the sector
facing away from the remote site in order to avoid inter symbol interference (ISI).
5.3.3 Antenna Isolation Test

The antenna isolation is the difference between the output signal on the server antenna and the signal leaking
into the donor or link antenna.
At a conventional installation with an on-frequency repeater the antenna isolation needs to be large enough not
to cause any signal distortion. For EDGE-signals (8-PSK) as much as 25 dB of margin (antenna isolation –
repeater gain) may be required to maintain signal quality. At the remote site of a frequency translating repeater
installation the antenna isolation needs to be approximately 75dB.
Signal leaking over to

the donor/link antenna
Donor or link antenna
Repeater Server antenna
Local or remote
connection
Computer
with RMC
The antenna isolation can be measured through the use of a function in the RMC. The measurement can be
made at the time the repeater is comissioned as well as regularly when the repeater is up and running. The
measurement can be made when the repeater is operational.
Note! The measurement only takes a few seconds, but if the repeater is operational at the time of the
measurement there is a risk of loosing calls during the time the parameters are changed.
5.3.4 Single Measurement

Prepare for the Ensure that the BCCH is in chain 1 or change the setup so that the measurement is
measurement done on the chain that contains the BCCH. Use a “silent” channel in the other
chain. This channel will be used for detecting the leaking signal and needs to be
free of traffic.
If the BCCH is not

on chain 1:
Select

“Configuration” and Define the channel that contains the BCCH as the Listener channel.
“Antenna Isolation
Measurement”
Go back to
“RF/Status”.
Use the Actions drop
down menu and
select “Force
Antenna Isolation
Measurement”
Click on to
monitor the result
5.3.5 Regular Measurements

The RMC can initiate regular antenna isolations measurements.
Select
“Antenna Isolation
Measurement”
Enable the
measurement
Define the time
point

5.3.6 Alternative method for antenna isolation measurement

The antenna isolation can also be measured by use of a signal generator and a spectrum analyzer. Use a signal
generator to generate a carrier wave signal on the server antenna, and a spectrum analyzer to measure the signal
leaking over to the donor antenna.
Note! The repeater does not need to be connected.
Signal leaking
over to donor
antenna
Repeater
Measurement of Input to
leaking signal server
antenna
Spectrum Signal
Analyzer Generator

5.4 Install the Repeater

5.4.1 Unpack the Repeater
Unpack the Inspect the shipped material before unpacking the equipment, document any visual
repeater damage and report according to routines.
A delivery of a repeater from Axell Wireless contains:
Checklist with delivered items
Repeater
Mounting brackets
Cable cover
Keys to repeater and hex tool for bolts
Hose for fibre inlet (for fibre fed repeaters)
CD containing User’s Manual and RMC
Any other specifically ordered item
5.4.2 Mount the Repeater

Mount the Mount the repeater in an accessible location and in a location that fulfils the
repeater on a wall, environmental requirements.
on a pole or in a The box repeater can be mounted on the wall or in a 19 inch rack. The Repeater is
rack delivered with mounting brackets.
The repeater needs to be mounted tightly to eliminate vibrations
Mounting bracket position for wall Mounting bracket position for rack
mounting mounting
Ensure proper Mount the repeater so that heat can be dispersed from it. The repeater wall mounting
ventilation kit ensures an optimum airflow between the wall and the repeater itself. Do not
block this air channel as it will cause the MTBF of the repeater to drop dramatically,
or even in the worst case cause the repeater to fail completely.
If possible use a wall in the shadow to minimize the overall sun loading. If sufficient
shielding cannot be obtained, an additional sun shield should be mounted.

Example of a sun shield
IP65 Casing Note! The repeater box should be closed using the two screws. The screws must be
fully tightened. Failure to do so may affect the IP65 compliancy and therefore any
warranty.
5.4.3 Ensure Proper Grounding

Connect the Ensure that good grounding protection measures are taken to create a
grounding reliable repeater site. Make sure to use adequately dimensioned
protection grounding cables. The minimum recommended conductive area for a
grounding cable is 16mm2.
The antenna cabling should be connected to ground every 10m by a
reliable grounding kit.
Make sure the grounding product used is suitable for the kind and size
of cable being used.
Connect the repeater box bolt to the same ground.
Ground connector on repeater

5.4.4 Ensure Good EMV Protection

Caution
If insufficient Electromagnetic Protection is provided,
or if EMV measures are not taken, warranties issued by Axell Wireless are not valid.
Connect the The lightning hazard to electric and electronic equipment consists in the
lightning interferences of direct lightning current infections and high surge voltages induced
protection by the electromagnetic field of nearby lightning channels or down conductors.
Amplitudes from cloud-to-earth lightning amounts to several 10kA and may last
longer than 2 ms. The damage caused depends on the energy involved and on the
sensitivity of the electronics systems.
Ensure that lightning protection measures are taken to create a reliable repeater site.
Protect all coaxial cables and power cables from the transients caused by lightning.
Fit all cables with suitable lightning protection devices.
Base Station area Repeater area
The top of
the mast
must be Antenna
higher than
the antennas
and be Primary
grounded Protective
properly Device
Equipotential
Grounding Bar
The
Repeater
grounding
path must OMU
have reliable
continuity
-30dB
and be
Coupler
dimensioned
correctly Protective
Device
Base Fiber
Station
230VAC/
-48VDC
Example of EMV protection for a repeater system
For detailed information please refer to IEC 61024-1 and 61312-1 for international
standards for protection of information systems against LEMP, Lightning
Electromagnetic Pulse, including radio transmitters. They define proper planning,
installation and inspection of effective lightning protection systems.
The repeaters comply with the EN standard ETS 301 498-8 which stipulates
demands on lightning/surge protection for typical infrastructure telecom equipment
installations.
Several lightning protection devices should be used in series with declining
threshold voltages to help attenuate the pulse component which makes it through the
first layer of protection.

The primary protective device is part of the site installation and is not supplied by
Axell Wireless. Coaxial lightning protection is normally one of these three types:
Gas capsule, High-pass and Band pass.
There also need to be a protective device installed on the power supply cord.
Protective device installed in connection with the power supply
5.4.5 Attach Cabling

The different repeater models have different connections.
Power Donor Ground Server External

antenna antenna alarms
2-channel on frequency repeater
Power Link Ground Server Server External

antenna antenna 2 antenna 1 alarms
2-channel, frequency translating or band shifting repeater.

Remote unit with external combiner
Power Fiber input Ground Server External

antenna alarms
2 channel fibre fed repeater

5.4.5.1 Attach Server Antenna Cables
Attach the antenna Server, donor and link antenna connection are DIN 7/16” connectors, female.
cables to the
Make sure that cable and connector are compatible. Using cables and connectors
repeater’s server,
from the same manufacturer is helpful.
donor and/or link
connections All connectors must be clean and dry
Waterproof all Waterproof all outdoor connections using silicone, vulcanizable tape or other
outdoor suitable substance as moisture and dust can impair RF characteristics.
connections
Make sure enough room has been allocated for the bending radius of the cable. RF
cables must not be kinked, cut or damaged in any way
Connect the RF cable to the antenna tightly but without damaging threads
Fasten cables tight to cable ladder or aluminum sheet
For short length of feeder cables use ½ “, for longer feeder cables use 7/8”. Chose
thicker coax cables for lower attenuation. Minimize the length of the coax cables to
reduce the attenuation
Use jumper cable for easy installation. The RF Coaxial cable can be substituted at
each end with a jumper cable.
5.4.5.2 Mount the Coupler (for frequency translating or band shifting repeaters only)
Caution!
When the coupler is connected the affected base station sector needs to be taken out of service. Turn the base
station off before detaching the cable to the base station cell antenna. It might shut down the whole network –
chose an off-peak time for this installation.
Mount the coupler The connection between the donor unit and the BTS is made using an Axell
Wireless Coupler. The attenuation from the BTS to the repeater is -30 dB. The
attenuation through the coupler from the BTS to the antenna is minimal.
Coupler
The coupler is connected in series with the BTS antenna. J1 and J2 are used for the
connection of the coupler in-between the BTS and the cable to the BTS antenna.

To Antenna
7/16 type Link Antenna

connector
N-type connector,
Cap female
RF Coaxial cable
7/16 type
-30dB Coupler
connector
Base Station
N-type connector, 7/16 type connector,
female female
Coupler connections
J3 or J4 is connected to the repeater donor unit depending on the orientation of the

coupler. If J1 is connected to the BTS; J3 is used for connection with the repeater, if
J2 is connected to the base station; J4 is used for connection with the repeater. The
connector not used (J3 or J4) must be sealed with a cap to prevent the ingression of
dust and water.
J1 and J2 are DIN 7/16 connectors, one male and one female
J3 and J4 are N-type connectors, female
1. Disconnect the antenna from the base station
2. Decide whether to connect a filter in series with the antenna cable (between the
coupler and the antenna) to prevent any disturbances from the repeater to reach
the antenna
3. Attach the coupler in-between the base station and the antenna cable. (J1 and
J2).
4. Attach the coupler connector closest to the base station to the repeater donor
antenna connector
5. Attach a cap to the connector closest to the antenna connection
6. Turn the base station back on and verify that it is operational.
7. Seal the coupler with rubber tape. Start on the base station antenna cable and
wrap to the base station port cable. Wrap in a circular motion downwards.
Cover the coupler and its connecting parts completely. This will provide a
weather resistant seal. Complete by adding three layers of PVC tape for UV
protection.

5.4.5.3 Attach Fiber Cable (for fibre fed repeaters only)

Fibre fed repeaters are equipped with class 1 lasers, as per definition in EN 60825-1.
Caution
Note!
Angled connectors, APC, need to be used throughout the whole link between
the OMU and the repeater. The angle needs to be 8 degrees.
Also the ODF connections need to be APC type.
The fibre must be monomode type.
Select fibre Recommended fibre cable is single mode 9/125.
Connect the fibre The casing of the box repeater is equipped with an inlet. The inlet is designed to go
with a corrugated hose, which is included in the shipment.
The hose, together with the rubber seal meet the protection standard IP65.
1. Run the 2. Run the

fibre through fibre through
the hose the inlet in
the repeater
3. Connect the 4. Place the

fibre to the fibre in the
Fibre Optic rubber seal
Converter
inside the
repeater
5. Adjust the 6. Attach the

fibre length hose to the
inside the inlet
repeater and
insert the seal
into the inlet

Note! Make
sure the fibre
is not bent too
sharply inside LIMPA LIMPA
the repeater.
There is room
under the
optic module Fibre Optic
to allow for Converter Duplex
some slack of Filter
the fibre.
Fiber Input
Note! To
insert and
extract the
hose from the
inlet press the
side levers.
Make necessary Make necessary measurements to ensure a correct installation.

measurements
When the cable has been installed, the quality of the optical path should be checked
for optical path loss and magnitude and location of any reflections. This can be done
with an Optical Time Domain Reflectometer (OTDR). The total return loss should be
> 45 dB.
Optical reflections can degrade the noise and linearity of a fibre optic link. In
particular, reflections that reach the laser can be a problem. Keep all discrete
reflections to > 60 dB. The SC/APC connectors are polished to a return loss >60 dB.
Attach the fibre Note! Clean the fibre connector before it is connected, see instruction below.
to the fibre optic
converter inside Cleaning Optical Connectors
the repeater.
Optical reflections from a discontinuity such as a poor connector interface appear on
an RF spectrum analyzer trace as stable variations in the noise floor amplitude that are
periodic with RF frequency. If the reflection is bad enough, it could impact the system
performance. By far, the most common cause for a large discrete reflection is a dirty
optical connector. A bit of dust or oil from a finger can easily interfere with, or block
this light. Fortunately, it is very easy to clean the connector.
Be sure to use the correct procedure for the given connector. When disconnected, cap
the FC/APC connector to keep it clean and prevent scratching the tip of the ferrule.
Alternative 1
Swipe the tip of the ferule 2-3 times with a cotton
swab soaked in alcohol. Let it air dry.

Alternative 2
Use a product specially designed for the purpose.
5.4.6 Supply Power to the Repeater

Caution!
The antenna cables must be connected to the repeater before mains power is switched on. Alternatively the
antenna connections on the repeater can be terminated with 50ohm termination plugs.
Note! The repeater can be fed by 230 VAC 50 Hz, 115 VAC 60 Hz or -48 VDC.
Ensure that the right voltage is used.
Connect the Power is connected to the repeater via a plinth inside the repeater.
repeater to the The strain relief fitting is a Pg 13.5 suitable for a 6-12 mm cable diameter.
power supply
230 VAC Power Supply
Connect the power cable to the plinth with the phase linked to the brown cable,
neutral linked to the blue and ground to the yellow/green. See illustration below.
Phase
/Live
Neutral
Ground
L
N
Strain Relief Fitting Connection Plinth
-48 VDC Power Supply

Connect the power cable to the plinth with negative (-48V) to the uppermost
connection and positive (0V) to the lower connection. Leave the middle connection
empty. See illustration below.

Negative
Positive
-48V
0V
Strain Relief Fitting Connection Plinth
Recommended cable areas for 48VDC
Distance Cable Area

0 - 10 meters between repeater and 2,5 mm²
power supply
10 – 50 meters between repeater and 4 mm²
power supply
Over 50 meters between repeater and Recommendation is to reconfigure the
power supply installation, or to make special
arrangements to increase cable area
Requirements on 48 V DC power supply

The 48VDC power supply must comply with SELV requirements, as defined in
EN60950, which implies double isolation. The output power needs to be 48VDC
+25%/-15%. The maximum input current is 8A.
Turn Off level

The -48VDC version of the power supply is designed to turn off if the supply
voltage falls below -36V (±1V), not to drain the feeding battery. It will turn on again
as the supply voltage reaches -43V (± 1V).
Back-up battery Backup Battery

There is a back-up battery installed in connection with the power supply. If there is a
power failure the battery will supply enough power to the Control Module and the
Fibre Optic Converter in the repeater to send information about the power failure.
The backup battery can be switched on and off separately. The switch is placed
adjacent to the main power switch on the power supply.
At delivery the back-up battery is connected.
The battery is replaced by lifting the battery pack out of the crate and disconnecting
the cable.

Connector
5.4.7 Connect External Alarms

Connect external The repeater is equipped with an external alarm interface card. The connector plinth
alarms for the external alarms is located at the bottom of the repeater.
The strain relief fitting in is a Pg 13.5 suitable for a 6-12 mm cable diameter.
Connect the alarm cords to the plinth according to the pin layout below (in the
standard version pins 14 – 18 are not used).
Pin # Signal
1 External alarm 1A
2 External alarm 1B
3 External alarm 2A
4 External alarm 2B
5 External alarm 3A
6 External alarm 3B
7 External alarm 4A
8 External alarm 4B
9 Alarm +15V
10 Alarm 0V
11 Relay Output 1A
12 Relay Output 1B
13 GND
14 NC
15 NC
16 NC
Pin 1 17 NC
18 NC
External Alarm
Four external alarm sources can be connected to the repeater. These alarms operate on
a voltage between 12 and 24VDC. The presence or absence of this voltage will trigger
the alarm depending on how the alarm polarity has been configured.
The alarms can be configured active-low or active-high, so that the alarm is given
either in the presence or absence of applied power. Active high means that an applied
voltage of between 12 and 24 V will cause the external alarm indicator to turn red.
Active low means that when there is no voltage the alarm indicator will turn red. The
repeater can supply +15 VDC to an external alarm source through pin 9 and 10. The
maximum allowed load is 100mA.
The repeater contains a relay (pin 11 and 12) that can be connected to an external
device to indicate an alarm. The relay can be configured to trigger on any number of
internal and external alarms. The maximum current that can be supplied is 100mA.

5.4.8 Close Repeater

Close repeater Close lid and lock repeater, or continue with section 4.4 Start up the Repeater.
Note! The two screws must be fully tightened. Failure to do so may affect the IP65
compliancy and therefore any warranty.

5.5 Start-up the Repeater

Caution!
Make sure the antenna cables or 50 ohm terminations are connected to the repeater’s antenna connectors before
the repeater is turned on.
Switch the repeater Switch the repeater on by using the power switches on the power supply.
on Note! See caution above!
Power Switch
There are two switches. One is for the battery and one is for the power
The rightmost switch is the one that switches the main power. The leftmost is for
turning the battery on/off.
Note! The power switch has two positions; “on” and “stand by”. In the stand by
position the repeater is still connected to the power supply but not operational.
Note! On 4-channel models both power supplies need to be switched on.
Check power supply Check the LEDs on the Power unit to ensure that normal operation conditions have
LEDs been attained.
Note! On the rack
type repeater these Input +6V +15V +28V
LEDs are not Power
accessible
LED 1, Input Power, Green
Slow flash Power supply unit operating on AC or DC
OFF Power supply unit not operating
LED 2, +6V, Red
Quick flash +6V power supply not operating or operating
with malfunction
LED 3, +15V, Red
with malfunction
LED 4, +28V, Red
with malfunction

Examples
LED 1 is flashing slowly, LED 2 – 4 are
flashing slowly (once every 10 seconds)
Input +6V +15V +28V => power supply unit is operating without
Power problem
LED 1 is flashing slowly, one or two of the

red LEDs are flashing quickly
Input +6V +15V +28V => Input power is operating but there is a
Power problem with some of the other voltages
LED 1 is flashing slowly, all of the red

LEDs are flashing quickly
Input +6V +15V +28V
=> Input power is out and unit is operating
Power on backup battery
Check Control The Control Module has four LEDs which give information regarding the status of
Module LEDs the repeater and if someone is logged on to the repeater.
If the repeater is configured as a system slave the two LEDs MDM Power and
MDM Status do not fill any function and can be disregarded.
U S
AT
DM R
PW
ST
U S
IN
AT
DM
G
LO
ST
M
M
Blue LED - Login

Quick flash Control Module switched on,
someone logged in locally
and/or remotely
Off Control Module switched on, no
(except for a quick flash every one logged in
10th second)
Off Control Module switched OFF
(permanent)
Red LED - Status

Quick flash Control Module switched on,
one or more errors/alarms
detected
Off Control Module switched on,
(except for a quick flash every status OK
10th second)
Off Control Module switched off
(permanent)
Green LED – Modem Power

On Modem Power is on


Voice call: Connected to
remote party
Data call: Connected to
remote party or exchange of
parameters while setting up or
disconnecting a call
Flashing Indicates GPSR data transfer.
When a GPRS transfer is in
progress the LED goes on
(irregular)
within 1 second after data
packets were exchanged. Flash
duration in approximately
0.5s.
75ms on/75ms off/75ms on/3s off One or more GPRS contexts
activated
75ms on/3s off Logged to network

(monitoring control channels
and user inRadio
Modulections). No call in
progress
600ms on/600ms off No SIM card inserted, or no
PIN entered, or network
search in progress, or ongoing
user authentications, or
network login in progress
Off Modem is off
For Fibre Fed Repeaters only
Check the LEDs on The Fibre Optic Converter contains two optical alarm sources. These are alarms
the Fibre Optic for transmitted and received optical signal level. The levels of the received optical
Converter signals can be monitored on-line via the RMC. This is convenient during
installation and tuning of the system.
There are 6 LEDs on the module to indicate the status.
pt a
Rx
ta
Tx
t
Da
Da
R
o
R
pt
PW
ER
DL
UL
LED 1, Power, Green

On Unit is powered on
Off Unit has no power
LED 2, Error, Red
On Error detected

LED 3, UL Data, Yellow

On Communication via the opto module is ongoing in the uplink direction
LED 4, DL Data, Yellow
On Communication via the opto module is ongoing in the downlink
direction
LED 5, Opto Rx, Green
On Input opto level OK
Off Input opto level below threshold
LED 6, Opto Tx, Green
On Output opto level OK
Off Output opto level below threshold

5.6 Initiate Local Communication

5.6.1 RMC Communication
Connect to the LMT Connect the computer to the LMT port via a DB9 male connector with serial RS232
port interface.
LMT Port
On the rack version the LMT port is on the front panel of the control module.
The communication parameters are set automatically by the RMC.
Select “Cable”
connection and
communication port
Enter user name and

password
Several users at a time can be logged on to a Repeater, for instance one locally via
the RS232 interface and one remotely via modem or Ethernet.
There is one default user name and password defined for the repeater.
User Name Password

avitec AvitecPasswd
Note! Both the user name and the password are case sensitive.
Note! Do not use the number pad when entering numbers.

5.6.2 RMC Work Views

There are three different work views to choose from in the RMC
Console mode
The console mode displays a large number of repeater parameters and contains
a number of console pages. It adjusts its user interface to adapt to the features of
the connected repeater.
Terminal mode
The terminal mode is used for communication with the repeater using its native
command line interface. This interface follows the VT100 standard. For some
special actions and error tracing, this mode gives an enhanced availability of the
repeater.
Firmware mode
The firmware mode is used for monitoring the currently installed software and
for uploading new software to the repeater.
Note! The description in this manual is based on using the Consol work view.

5.7 Install the OMU and Set up OMU-Repeater

System
Fibre fed repeaters only. For information about how to install the OMU which will supply the input signal to the
repeater please refer to the OMU Manual. In the OMU Manual there is also information about how to calculate
link budgets for a whole OMU-Repeater system.
5.8 Configure the Repeater

The following pages will guide you through the configuration of a repeater utilizing the Repeater Maintenance
Console (RMC) software. Configuration of a repeater is made partially on site and partially remotely through
the AEM. At site the RF parameters are set and verified, the repeater is given a name (a tag) and the remote
communication is set and verified. All other configuration can, and should be made from the AEM.
5.8.1 Set up RF Configuration

For fibre fed repeaters: If the repeater is connected to an OMU the configuration can also be made via this
OMU. See OMU User’s Manual.
Ensure online
communication with
the repeater Select “RF/Status” window
Chain 1
Channel number
Uplink
Attenuation
Power level
Saturation level
Downlink
Attenuation
Power level
Saturation level
This shows a 4 channel GSM repeater
Set all power levels Set “Power Level” in uplink and downlink to “OFF” in all chains
to “OFF”
In the “Power Level” menu the output power can be limited to a specific value or the
output power can be switched off completely by choosing “OFF”.

Set attenuation level Choose the maximum attenuation value from the drop down menu. In this example
in downlink and the maximum value is 30dB.
uplink to a maximum
30
Set channel numbers Set the channel numbers for all chains that are to be used in the installation.
GSM Repeaters WCDMA repeaters
Note! The duplex distance is set to 950
Set BCCH/ Power Set Required/Either or Skip to the chain that holds the BCCH/Pilot Tone.
measurement If a chain is configured as required then an alarm will be generated upon loss of signal
Configuration in the downlink .If a chain is configured as skip, then this chain will never trigger this
alarm. If a chain is configured as "either" then all chains configured as "either" are
checked and if none of them contains a downlink signal the alarm be triggered.

Fibre Fed Repeaters
Check that the fibre Make sure there are no alarms relating to the fibre. Select and in the
is OK right column.
Initiate fibre loss This is done from the OMU by sending a pilot tone to the repeater and calculating the
compensation loss in the fibre link. This loss is compensated for automatically. The system will
behave as if there is no loss at all in the fibre link.
This procedure is described in more detail in the OMU manual section 4.9 Initiate
Fibre Loss Compensation.
All Repeaters
Check the Return
Loss value
Select and in the right column.
The Return Loss measures the reflected signal on the server antenna port of the
repeater.
If the value is approximately 3dB the port is open or there is something wrong with
the antenna installation. If the antenna is correctly installed the value should be
approximately 20dB.
Configure the Note! Start with the chain that contains the BCCH/Pilot Tone. This chain has a stabile
downlink power level.
Set “Power Level” in downlink to the desired value, in this example +37 dBm. This
value should be based on a link budget.
+37
View the power meter in the top right corner of the screen
RF levels icon
Desired output
- XX dBm 37 dBm power
Adjust the attenuation step by step until the desired output power is reached. Zero
attenuation is the same as maximum gain.
Also use the saturation level indicator. The saturation level is indicated with plain text
as well as with LEDs.


For GSM repeaters the saturation level For WCDMA repeaters the saturation
can be: Low (green), Ok (green), High level can be: Linear (green) and
(yellow) or Critical (red). Saturated (red)
The optimal level is Ok/Linear. To reach this value lower the attenuation step by step
until the saturation reaches High/Saturated. Then raise the attenuation one step. The
saturation should now be back on Ok/Linear.
- XX dBm 37 dBm The current output power level

is displayed in this box
Note! The accuracy of this

measure is ± 2dBm
17 The attenuation is adjusted in this box
+37 The desired power level is set in this box
Saturation level indicator
Note! Since the repeater has an ALC function (Automatic Level Control), the repeater
will not transmit more power even if you continue to lower the attenuation.
Note! For WCDMA repeaters: The repeater gain should be configured so that there is
a margin from pilot tone to full traffic of 7-10 dB. For example, if a maximum output
power of 30dBm is desired at full traffic, the pilot tone alone should deliver an output
level of 20-23dBm. This setting will allow for the power variations. If possible check
the activity level of the base station at the time for the repeater set up. The base station
output can vary a lot – up to 13dB. If the repeater is set up during a low activity
period it might be run into ALC when the base station activity becomes higher.
Note! For Fibre Fed Repeaters: Please also consult section 6 Installation in the
HUB/OMU Product Description and User’s Manual.
Configure the Apply the same Power Level and Attenuation in the other chains.
downlink in the other If the BCCH/Pilot tone is in Chain 1 this chain will show a stable power level whereas
chains
downlink and uplink power levels in the other chains depend on the amount of traffic.
This will make these chains appear unstable.
Note! All channels that are not to be used should always be switched off. (Set Power

Level to “OFF”.)
GSM and WCDMA Repeaters

Configure the uplink Set the Power Level for the uplink in all chains to the same value as for the downlink
in all chains or to any other level decided in the link budget.
Set the Attenuation 2dB higher than in the downlink.
Since the base station is more sensitive than a mobile unit there may be less signal
gain from the mobile unit in to the base station (UL) than in the opposite direction.
The uplink attenuation can be adjusted more accurately later on, once the drive test
signal measurements have been completed.
Make an antenna See 5.3.3 Antenna Isolation

isolation test
Fibre Fed Repeaters

Configure the uplink In the uplink direction the attenuation needs to be set based on a measurement of a
in all chains known signal which is transmitted through the repeater and the OMU as well as the
fibre. There are two ways of performing this measurement.
Alternative 1
Use a signal generator to insert a signal of approximately -70dBm into the repeater’s
server antenna port. Measure the signal level on the base station or on the coupler and
adjust the attenuation so that the total gain in the uplink is close to 0dB. (At 0dB gain
the signal level at the coupler should be -40dBm and on the base station -70dBm in
this example.)
-40dBm Repeater
OMU
-30dB
Coupler
Signal
Fiber Generator
-70dBm -70dBm
BTS
Alternative 2: Use the RMC to
measure the uplink at the OMU
Alternative 2
Use a signal generator to insert a signal of approximately -70dBm into the repeater’s
server antenna port. Log into the OMU and monitor the uplink via the RMC. This
measurement is not as accurate as alternative 1.
Note! If several repeaters are connected to the same OMU the total gain in each chain
should be slightly lower than 0dB not to insert too much noise into the base station.
Note! For in-depth instructions for commissioning of an OMU-Repeater system
please contact your Axell Wireless representative.

Frequency Translating or Band Shifting Repeaters

The above description is valid for the donor unit. Now continue with the remote unit, which is almost identical
to the configuration of the donor apart from the gain and output power settings.
Set all power levels See instruction above

to “OFF”
Set all Attenuation See instruction f above

levels to a max
Set channel numbers Set the same channel numbers as for the donor unit
Set link channel Set the same link channel numbers as for the donor unit
numbers
Configure the Set “Power Level” downlink to the desired value, in this example
downlink in the +43 dBm. This value can be based on a link budget, or be the maximum output the
channel that repeater can generate.
contains the BCCH
+43
Adjust attenuation in Lower the attenuation level step by step until the desired output power is reached.
the downlink See instruction for donor unit above
Configure the Apply the same Power Level and Attenuation in all chains.
downlink in all other
The presence of the BCCH will ensure stable power levels in this chain whereas
chains downlink and uplink power levels in other chains will depend on the amount of
traffic. This will make these chains appear unstable.
Note! All channels that are not to be used should always be switched off. (Set Power
Level to “off”.)
Configure the uplink Set the Power Level in the uplink in all chains the same as for downlink in the donor
in all chains unit.
Set the Attenuation 2dB higher than in the downlink.
5.8.2 Set Repeater Name (TAG)

The TAG can be chosen freely to give the repeater a name that is linked to the location, the site name, etc. The
TAG may contain up to 30 characters including spaces.
Select
“Product”

Insert the repeater’s

name (TAG) in this
box.
Note! Do not assign an ID. The AEM will do this automatically when the repeater
is integrated in the AEM.
5.8.3 Configure Alarms

See section 4.2.7Alarm Configuration.
5.8.4 Configure Reports

This configuration should be left unchanged. If changes to the default settings are to be made these are done
when the repeater is integrated into the AEM.
Select
“Reports”
Set report data
Heartbeat
Alarms
Note! For repeaters that are to be used as slaves in an OMU-Repeater system all report configurations are done
from the OMU.

5.9 Set Up Remote Communication

Note! If the repeater is fibre fed and is set up as a slave- this section is not relevant since the remote
communication is handled by the node master – in most cases an OMU.
The repeaters can be configured with a wireless modem, a PSTN modem or Ethernet for the remote
communication.
5.9.1 Communication via Modem

The Control Module is responsible for enabling the power to the modem, unlocking the SIM-card, using the
configured PIN-code and making sure the modem is logged in to the network correctly. Depending on network
configuration and modem usage, the modem might require different modem initialization strings to work
properly. This modem initialization string is set and verified during repeater setup.
5.9.1.1 Modem Initialization

After a power failure, or upon user request, the Control Module performs a full initialization of the modem.
This consists of three steps:
If the SIM-card in the modem has the PIN code enabled, the Control Module unlocks the PIN code. In case
wrong PIN-code is configured, the Control Module will not try to unlock the SIM again until the PIN-code
is changed. This avoids the SIM card being locked by a Control Module repeatedly trying to unlock the
SIM with the wrong PIN code.
Once the SIM is unlocked, the Control Module waits for the SIM to log in to the network. Depending on
signal quality and network configuration this might take a while. The Control Module will wait a
configurable number of seconds (default 50 seconds) for the modem to login to the network. In case no
network is found, a modem power cycle will be initiated.
When the modem is successfully logged in to the network, the Control Module configures the modem with
the modem initialization string as configured when setting up the remote configuration. The modem
initialization string is a network dependent string. The default string is suitable for most networks, but
some networks might require some tweaking of this string.
5.9.1.2 Monitoring Modem Connection

The Control Module constantly monitors the status of the modem connection to ensure that it is working
properly, and that the modem is logged in to the network.
In case the modem is not registered to the network, or the Control Module cannot properly communicate with
the modem, a power cycling of the modem is initiated, after which the modem will reinitialized.
5.9.1.3 Scheduled Modem Power Cycling

In addition to polling the modem to ensure the repeater online status, the Control Module can be configured to
perform an automatic power cycling on a scheduled time of the day. Power cycling the modem ensures the
latest network configuration for the modem, such as the HLR Update Interval etc.
Note! By default, the scheduled modem power cycling is disabled.
5.9.2 Communication via Wireless Modem

There are two different ways of communication for a wireless (GSM) modem:
Using data call / modem connection.
Note! This requires the SIM-card in the modem to be configured with data service.
Using SMS to configure the repeater with simple text messages
Note! SMS functionality is not implemented in this SW release.
The Axell Element Manager always uses data call communication with the repeater, why all repeaters being
controlled by the AEM must have data service enabled on the SIM card.
Configuring the repeater to send alarms and reports via SMS it is still possible to establish data calls to the
repeater, as long as the SIM card is data service enabled.

5.9.2.1 Modem Configuration, not using GPRS

Select
“Communication”
Select Data Call
Initialization string
Connect times
2004-01-01
AEM addressed are

set via the AEM
Select Data Call

Set the modem initialization string. This string differs between networks. Primary
recommendation is AT+CBST=71,0,1;\Q3. If remote communication cannot be
established try 7,0,1 or 0,0,1 or 7,0,3. For more information please refer to the
section on Troubleshooting Remote Communication.
Tick “Enable Automatic Modem Power Cycling” for the modem to be power
cycled once every 24 hours. Set the time at which the modem should be tested. This
function ensures that the repeater always is logged in to the network.

5.9.2.2 Modem Configuration, using GPRS

Select
“Communication”
Select GPRS
Connect times
AEM addressed are

set via the AEM
Configure GPRS
Select GPRS
Set the modem initialization string. This string differs between networks. Primary
recommendation is AT+CBST=71,0,1;\Q3
Tick “Enable Automatic Modem Power Cycling” for the modem to be power cycled
once every 24 hours. Set the time at which the modem should be tested. This
Click on Configure…

Each parameter is described in Common Commands and Attributes, section 14

GPRS Configurations.
Set the Access Point Name. It needs to be defined by the telecom operator
Set Maximum Receive Unit and maximum Transmission Unit. These differ
depending on access type: 576 for GSM, 1476 for EDGE and 1500 for WCDMA.
Click on Close, and then on “Yes”.
Wait for the modem to restart. This can take a few minutes.
When the modem settings are ready the LED turn green.
5.9.2.3 AEM Addresses

The Control Module can be configured with two different addresses (telephone numbers) to which alarms and
reports are delivered. In case the repeater cannot deliver alarms and reports to the primary address, the next call
will be made to the secondary address.
A fallback functionality is available, which means that the Control Module falls back to the primary address
after a configurable number of minutes. If this interval is set to 0, the fallback will not be performed. A user can
always force the Control Module to fall back to the primary address.
Note! When the repeater is integrated to the Axell Element Manager system, these addresses are set by the
AEM, why they need not be configured during site installation.
5.9.2.4 Modem Verification

When the remote configuration has been set up the communication can be verified using the modem feature of
the RMC and dialling the data number. The remote communication is verified as soon as a successful remote
login to the repeater has been performed.
However, as a first step, it is recommended to verify that the modem is initialized correctly. After configuring
the modem using the RMC, make sure to initiate a power cycling of the modem. This is done from the RMC
menu.

Click on the drop-down menu

Actions, choose Power Cycle
Modem on Logout
An immediate power cycling is initiated after which the modem is initialized and registered onto the network.
The modem is now ready for remote access.
Ensure a successful configuration by observing the modem LED as described below.
Note! This LED behaviour is valid only for GSM modems. Other modem types will be added in later editions.

Voice call: Connected to remote party
Data call: Connected to remote party or exchange of
parameters while setting up or disconnecting a call
Flashing Indicates GPSR data transfer. When a GPRS transfer is

in progress the LED goes on within 1 second after data
packets were exchanged. Flash duration in
(irregular) approximately 0.5s.
75ms on/75ms off/75ms on/3s off One or more GPRS contexts activated
75ms on/3s off Logged to network (monitoring control channels and

user interactions). No call in progress
600ms on/600ms off No SIM card inserted, or no PIN entered, or network

search in progress, or ongoing user authentications, or
network login in progress
Off Modem is off
Verify the remote communication either by having someone attempting to integrate the repeater from the Axell
Element Manager, or by dialling the repeater using the Repeater Maintenance Console.
Note! It is very important to dial the data number of the SIM. In case the voice number is dialled, the call is
answered, but almost immediately the call will be hung up.
5.9.2.5 SIM-card Using Single Numbering Scheme

If the network is configured using Single Numbering Scheme (SNS), some special considerations apply.
The repeaters are by default configured so that networks using SNS always will have calls routed to the data
service in the modem. When dialling from within the network to a repeater having an SNS-configured SIM will
operate normally, since the call originator informs the system that the bearer is of type DATA. However, when
dialling from outside the network trying to connect to the repeater can be difficult. Depending on the interface
to the roaming network or to the PSTN network if an analogue modem is used, the bearer type can default to
voice. If the bearer is set to voice, the data service cannot be converted to DATA, and a call setup cannot be
completed.
Note! This is not a repeater related problem; the solution is to verify how the external network interfaces
handles the VOICE vs. DATA bearer type.

5.9.3 Configuration via PSTN (Fixed) Modem

Also for PSTN modems data call shall be used.
Select
“Communication”
Select Data Call
ATE0S0=0
Connect times
2004-01-01
AEM addressed are

set via the AEM
Tick “Enable Automatic Modem Power Cycling” for the modem to be power
cycled once every 24 hours. Set the time at which the modem should be tested. This

5.9.4 Communication via TCP/IP and Ethernet

A TCP/IP communication is run over a company’s network. Therefore each company needs to define the details
regarding the configuration, IP addresses, etc. For more information please refer to Common Commands and
Attributes, section 13 Network Configurations.
Select
“Communication”
Set IP address and

other relevant
information here
In these screens the

Ethernet and/or DNS
Gateway parameters
can be set
5.9.5 Troubleshooting Remote Communication

Please also refer to the document Common Command and Attributes for guidance.
Since many networks have their own “personality”, performing first time configuration of the remote
communication sometimes requires tweaking of the modem parameters.
This section describes some trouble shooting techniques if configuring the repeater for remote access fails.
The illustration below is a simplified schematic of the remote communication between a GSM modem in a
repeater and an analogue modem. The analogue modem in the computer communicates with the Interworking
Function Unit (IFU), which is the GSM network analogue network interface. The call is routed via the switch
centre over the air interface to the data call number in the SIM-card of the GSM module.
The Control Module is responsible for establishing connections with the Axell Element Manager, and to answer
incoming calls to the repeater.
As described in previous sections, the Control Module only accepts one login at a time, either via Local
Maintenance port (LMT) or modem connection. Hence, when verifying the remote access of the repeater, it is
important to log out from the repeater locally before trying to access the repeater remotely.

Radio Laptop
LinkProtocol
(RLP)
Modem RS232
Base Station
Control module in
Interworking Axell Wireless
Function Unit Switch Repeater
(IFU) Centre
5.9.5.1 Direct Modem Access

To allow for advanced trouble shooting of the communications, it is possible to access the modem directly via
the Control Module from a laptop computer.
LMT Port
RS232 cable
GSM Control Module

Module
Laptop
Log in to the repeater, either with RMC, or with a terminal emulation program, such as HyperTerminal™.
When the login is completed, select Terminal Mode, this will give access to the repeater command prompt in
the same way as with HyperTerminal.
When the repeater prompt is accessible, type in the command
ACCESS MODEM <Enter>.
When typing ACCESS MODEM, the controller will send all the characters that are typed directly out to the
modem port. All characters replied back from the modem will go directly to the LMT port and back to the
computer.
To abort an ACCESS MODEM session, press three ‘-‘ in a row (all three within one second) to come back to
the repeater command prompt.
Note! When accessing the modem port the modem might be configured with “echo off”, meaning that the
characters entered will not be echoed back to the screen. In order to enable “echo”, press Enter.
Type
ATE1 <enter>
(invisible)
The modem replies with
OK
indicating that the echo is enabled. All characters entered will now be echoed back to the terminal program.
5.9.5.2 Trace Modem

For troubleshooting purposes it is possible to trace the actual progress of initializing the modem. This trace is
useful when having problems with the modem initialization.
Go to Terminal Mode and type
TRACE MODEM

To end session type CTRL-Z
5.9.5.3 Manually Answering Incoming Calls

It is possible to manually answer incoming calls without involving the repeater software at all, to verify that the
remote access and the network itself works as intended. In order to verify the remote communication, make sure
to have someone stand by to dial up the repeater with a terminal emulation program, for example
HyperTerminal™.
Go in to Direct Modem Access as described earlier. When in direct access mode, ask the person standing by to
dial up the repeater.
As soon as a call is received, the text
RING
will repeatedly be displayed on the screen.
Type
ATA <enter>
This will inform the modem to answer (ATtention Answer).
When the connection is established, a connect message will be displayed including the connection speed.
Sometimes the information comes together with some miscellaneous information, such as error correction
protocols etc.
Note! Make sure the remote peer dials the Data Call number
If the voice number is dialled instead of the data number, or if the modem contains an illegal modem
initialization string, the message
OK
or
NO CARRIER
will be displayed almost immediately.
Try to change the modem initialization string. The modem initialization string mainly used to configure the
remote communication is AT+CBST.
Successful modem initialization strings used by Axell Wireless includes (most common first):
AT+CBST=71,0,1;\Q3
AT+CBST=7,0,1;\Q3
AT+CBST=0,0,1;\Q3

AT+CBST=0,0,1;\Q3
AT+CBST=7,0,3;\Q3
Once the modem initialization string is entered, try again to dial up the repeater. For details on the different
modem initialization strings, please refer to the modem’s user guide.
If the setup is successful, the connect message will be brought up;
CONNECT 9600
This means that an online connection is established to the remote peer. From now on, all characters typed on the
keyboard will end up on the remote peer’s screen. Similarly, all characters typed by the remote peer will be
displayed on the screen.
In the example, the incoming call was

successfully answered, and the remote
user entered the text message.
In order to come back to modem command mode, press +++ (three pluses) rapidly (within one second).
Receiving
OK
means that the modem is back in command mode.
Type
ATH <enter>
This terminates the connection to the remote peer. The message
NO CARRIER
will be displayed.
5.9.5.4 Common Problems
Problem 1
When enabling the remote access for the repeater, the modem fails to log in to the network.
Solution
Signal strength from the donor site is too low. The signal strength can be read directly from the modem. Go in
to Direct Modem Access as described earlier. Use the command AT+CSQ (documented below) to read out the
signal strength.
In order to have good signal quality, Axell Wireless recommends that the signal strength should be better than -
95 dBm. If signal strength is lower, try to adjust the antennas to get a better signal strength from the donor.

Documentation of +CSQ command from a modem’s manual.
In the example the reply to AT+CSQ is

0,7 meaning 7*2 dB above -113 dBm;
the modem detects a signal level of -99
dBm.
Problem 2a
Repeater is configured properly, and answers the incoming call, but when trying to dial the repeater using an
analogue mode, no modem handshaking is heard from the dialling modem.
Problem 2b
When dialling the repeater, the repeater answers the incoming call, but no connection is established, and after a
while the repeater disconnects the call.
Solution
The most common cause is that the number called is the voice number of the SIM, not the data number.
Therefore, make sure to dial the data number.

If data call is used, the problem probably is an illegal modem initialization string.
In order to change the modem string, go to the repeater command prompt. Try changing the modem
initialization string and log out to let the controller reinitialize the modem.
If problem remains, try a few different modem initialization strings. Axell Wireless has been successful with the
following modem initialization strings:
AT+CBST=71,0,1;\Q3
AT+CBST=7,0,1;\Q3
AT+CBST=0,0,1;\Q3
AT+CBST=0,0,1;\Q3
AT+CBST=7,0,3;\Q3
Please refer to the modem manual for detailed description of the modem initialization strings.
Problem 3
It is possible to call the repeater from another GSM mobile, but not from an analogue modem.
Solution
This problem is most likely related to the modem configuration and/or the configuration of the IFU unit. Try to
decrease the communications speed and make sure that the modem error correction is supported by the IFU.
Verify the IFU configuration to see if there are any known problems with the modem connections.
Problem 4
When dialling the repeater, or when the repeater is dialling the Element Manager, the connection is terminated
before the handshaking is completed.
Solution
When a repeater is answering an incoming modem call, or calling up the OMC to deliver an alarm or a report,
the repeater will wait a configurable number of seconds for the call to be established. If no communication is
established within this time, the call will be hung up. If this interval is set too low, the handshaking is
terminated too fast. In the RMC, verify the Modem Connect Time to see that it is set to at least 30 seconds.
5.10 Integration into the AEM

When the repeater has been installed at site and the remote communication has been enabled, the repeater can
be integrated to the Axell Element Manager. This is done by the operator of the AEM. After entering the
telephone number to the repeater, the AEM dials up the repeater, downloads all the repeater parameters and
statuses into a database. When all parameters have been downloaded, the AEM configures the repeater with the
telephone number where alarms and reports should be sent, and optionally with a secondary telephone number
where the repeater can dial in case connection to primary number fails.
When heartbeat reports and alarms are sent from the repeater to the AEM also the latest information about the
status and RF-configuration is included. This means that the AEM operator always has information about the
current status in the AEM database (and do not need to call the repeater to find this out).
Note! Once the repeater is integrated to the AEM, all changes to the repeater should preferably be done from
the Axell Element Manager in order to ensure that the database always contains correct information.

6 Maintenance
Caution
Please be aware that the equipment may, during certain conditions become very warm and can
cause minor injuries if handled without any protection, such as gloves.
Caution
Risk of explosion if battery is replaced by an incorrect type.
Dispose of used batteries according to local laws and instructions.
This product is equipped with class 1 lasers, as per definition in EN 60825-1.
Caution
6.1 General
The system normally operates without any operator intervention or maintenance. If in the unlikely event of any
unit failure, the faulty repeater should be replaced. A failed unit can be removed and replaced with a spare while
the rest of the system (other repeaters) is still operating. However, the power supply of the failed repeater
should be isolated from the power before anything is replaced.
In the event of a malfunction in the system, the status of the antenna systems as well as the continuity of the
cabling should be checked before replacing any modules within the repeater.
6.2 Preventive Maintenance

The BSF 424 repeater does not require preventative maintenance.
6.3 Trouble Shooting

In the event of a failure Axell Wireless’s support service should be contacted for advice on a possible module
replacement or other action to be taken.
6.4 Component Replacement

None of the modules in the repeater can be replaced without removing the repeater from its mounting and
opening the cover of the repeater.
6.5 Product Disposal

Disposal of this product must be handled according to all national laws and regulations. For detailed
information regarding materials, please refer to Axell Wireless Ltd.

7 Specifications
7.1 On-Frequency Repeaters, GSM
7.1.1 CSR 822/4
Electrical Specification
Frequency range, UL/DL 824 – 849 MHz / 869 – 894 MHz
Operational bandwidth 25 MHz
Number of channels 1- 4
Channel programming 200 kHz Channel spacing
Selectivity > 60 dB at 400 kHz

> 65 dB at 600 kHz
Ripple in passband < 2 dB
Noise figure, 2/4 channels 2.5 dB typical, < 3 dB at max gain / 3 dB typical, < 3.5 dB at max gain
Maximum input level, no damage + 10 dBm
Propagation delay 5.8 μs typical
Output power per carrier, 2 channels, UL&DL + 37 dBm GSM/ GMSK; + 34 dBm EDGE / 8-PSK average power
Output power per carrier, 4 channels, UL&DL + 34 dBm GSM/ GMSK; + 31 dBm EDGE / 8-PSK average power
Modulation Accuracy at full output power GSM / GMSK < 2.5 ° RMS and < 10 ° peak
EDGE / 8-PSK < 3.5 % EVM RMS
Intermodulation < -36 dBm (two carriers at full output power DL, 600 kHz spacing)
Spurious emissions < - 36 dBm for 9 kHz – 1 GHz

< - 30 dBm for 1 GHz – 13 GHz
Gain 60 -90 dB adjustable in 1 dB steps
Gain Flatness (200 kHz BW) ± 1 dB

Gain Flatness (operational bandwidth) ± 1.5 dB, at constant temperature
System impedance 50 ohm

Antenna connectors DIN 7/16
Electrical ratings 110/230 VAC, 50/60 Hz or -48 VDC
Power Consumption, 2/4 channels 160 W / 270 W typical
Mechanical Specifications
Dimensions, 2/4 channels 540 x 350 x 150 mm / 540 x 350 x 220 mm
Enclosure Aluminum (IP 65)
Weight, 2/4 channels 22 kg / 33 kg
Environmental Specifications
EMC See compliance below
Operating Temperature - 25 to + 55 ° C
Storage - 30 to + 70 ° C
Humidity ETSI EN 300 019-2-4 (see compliance below)
MTBF > 100 000 hrs

Complies with R& TTE Directive including
ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.1.2 CSR 922/4 (R)
Electrical Specifications
Frequency range UL/DL 880 – 915 MHz (E-GSM900) / 925 – 960 MHz (E-GSM900)
Frequency range UL/DL 890 – 915 MHz (P-GSM900) / 935 – 960 MHz (P-GSM90
Frequency range UL/DL 876 – 880 MHz (GSM-R) / 921 – 925 MHz (GSM-R)
Operational bandwidth 35 MHz (E-GSM) / 25 MHz (P-GSM) / 4 MHz (GSM-R)
Number of channels 1–4
Channel programming 200 kHz channel spacing

> 65 dB at 600 kHz
Ripple in pass band < 2 dB
Noise figure, 2/4 channels 2.5 dB typical, < 3 dB / 3 dB typical, < 3.5 dB at max gain
Maximum input level, non destructive + 10 dBm
Output power per carrier, 2 channels UL&DL + 37 dBm GSM/GMSK; + 34 dBm EDGE / 8-PSK average power
Output power per carrier, 4 channels UL&DL + 34 dBm GSM/GMSK; + 31 dBm EDGE / 8-PSK average power
Intermodulation < - 36 dBm (two carriers at full output power, 600 kHz spacing)

Gain 60 – 90 dB, adjustable, in 1 dB steps

Power Consumption, 2/4 channels 160 W / 270 W typical (traffic dependent)
MTBF > 100 000 hrs
Complies with R&TTE Directive including
ETS EN 301 502 (ETS EN 300 609-4/GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.1.3 CSR 924 H
Frequency range UL/DL 890 – 915 MHz (P-GSM900) / 935 – 960 MHz (P-GSM900)
Number of channels 1-4

> 65 dB at 600 kHz
Noise figure 3 dB typical, < 3.5 dB at max gain
Output power per carrier, UL + 34 dBm GSM/ GMSK; + 31 dBm EDGE / 8-PSK average power
Output power per carrier, DL + 36 dBm GSM/ GMSK; + 33 dBm EDGE / 8-PSK average power
Modulation Accuracy at dull output power GSM / GMSK < 2.5 ° RMS and < 10 ° peak
EDGE / 8-PSK < 4 % EVM RMS
Intermodulation < - 36 dBm (two carriers at + 36 dBm, 600 kHz spacing)

Gain 63 – 93 dB, adjustable, in 1 dB steps
System impedance 50 Ω
Power Consumption 240 W typical (traffic dependant)
Dimensions 540 x 350 x 220 mm
Weight 33 kg
MTBF > 100000 hrs
ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.1.4 CSR1822/4
Frequency range UL/DL 1710 - 1785 MHz (DCS-1800) /1805 - 1880 MHz (DCS-1800)

> 70 dB at 600 kHz
Propagation delay 5.8 µs typical
Output power per carrier 2 channels UL&DL + 37dBm GSM/ GMSK; + 34 dBm EDGE / 8-PSK average power
Output power per carrier 4 channels UL&DL + 34dBm GSM/ GMSK; + 31 dBm EDGE / 8-PSK average power
Spurious emissions < - 36 dBm for 9 kHz - 1 GHz

< - 30 dBm for 1 GHz - 13 GHz
Gain 60 - 90 dB, adjustable, in 1 dB steps

MTBF > 100 000 hrs
ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26 )
ETS EN 301 498-8
EN 60 950

7.1.5 CSR1922/4
Frequency range UL / DL 1850 - 1910 MHz (PCS-1900) / 1930 - 1990 MHz (PCS-1900)

> 70 dB at 600 kHz
Output power per carrier 2 channels UL&DL + 37 dBm GSM/ GMSK; + 34 dBm EDGE / 8-PSK average power
Output power per carrier 4 channels UL&DL + 34 dBm GSM/ GMSK; + 31 dBm EDGE / 8-PSK average power


MTBF > 100 000 hrs
ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26 )
ETS EN 301 498-8
EN 60 950

7.2 On-Frequency Repeaters, WCDMA

7.2.1 CSR 822/4W
Channel Spacing, Raster and Number According to ETSI TS 25.106 chapter 5.3
Channel programming 200 kHz
Selectivity > 45 dB at 2.7 MHz

> 60 dB at 3.5 MHz
> 65 dB at 7.5 MHz
> 70 dB at 12.5 MHz

Gain 60 - 90 dB, adjustable, in 1 dB steps.
Out of band gain Compliant to ETSI TS 25.106 chapter 8
Output power per carrier, TM1/64 with 61% clipping (PAR = 8.3dB)
2 channels, UL / DL +30 dBm ± 1dB average power / +31 dBm ± 1dB average power
Output Intermodulation According to ETSI TS 25.106 chapter 12

Noise figure 3 dB typical, < 3.5 dB at max gain
Input Intermodulation According to ETSI TS 25.106 chapter 11
Modulation Accuracy
EVM < 12.5 % RMS (composite according to ETSI TS 25.106 with TM 1 / 64
DPCH), < 6% RMS typical
PkCDE < - 33 dB (according to ETSI TS 25.106 with TM 1 / 64 DPCH and
spreading factor 256)
Frequency Stability According to ETSI TS 25.106 chapter 7

Unwanted emission According to ETSI TS 25.106 chapter 9, using TM1/64 @ 61% clipping
Intermodulation < - 36 dBm (two carriers at full power, 5 MHz spacing)
Return loss at antenna connections > 16 dB
Power Consumption 220 W typical (traffic dependent)
MTBF > 100000 hrs
Complies with ETSI TS 25.106, ETSI TS 25.143
ETSI EN 301 498-23, EN 60 95C

7.2.2 CSR 922/4 W
Frequency range Uplink, UL/DL 880 – 915 MHz (E-GSM900) / 925 – 960 MHz (E-GSM900)
Frequency range Uplink, UL/DL 890 – 915 MHz (P-GSM900) / 935 – 960 MHz (P-GSM900)
Operational bandwidth 25/35 MHz

> 60 dB at 3.5 MHz
> 65 dB at 7.5 MHz
> 70 dB at 12.5 MHz


Noise figure 2.5 dB typical, < 3 dB at max gain
Modulation Accuracy

Intermodulation < - 36 dBm (two carriers at full power, 5 MHz spacing)
MTBF > 100000 hrs
ETSI EN 301 498-23
EN 60 95C

7.2.3 CSR 2222/4
Frequency range Uplink, UL/DL 1920 - 1980 MHz / 2110 - 2170 MHz

> 60 dB at 3.5 MHz
> 65 dB at 7.5 MHz
> 70 dB at 12.5 MHz

2 channels, UL&DL +33 dBm ± 1dB average power,
4 channels, UL&DL +30 dBm ± 1dB average power

Modulation Accuracy
Intermodulation < - 36 dBm (two carriers at + 33 dBm, 5 MHz spacing)

MTBF > 100000 hrs
ETSI EN 301 498-23
EN 60 95C

7.3 Frequency Translating Repeaters

7.3.1 CSFT 922/4 (R)
Frequency range UL/DL 876 – 880 MHz (GSM-R) / 921 – 925 MHz (GSM-R)
Selectivity, donor unit, SD and DD > 60 dB at 400 kHz

> 65 dB at 600 kHz
Selectivity, remote unit, IR and ER > 60 dB at 400 kHz
> 70 dB at 600 kHz
Noise figure, 2 channels

Donor unit, SD and DD, UL 2.5 dB typical, < 3 dB at max gain
Remote unit, IR and ER, UL&DL 2.5 dB typical, < 3 dB at max gain
Donor unit, SD and DD, UL 3 dB typical, < 3.5 dB at max gain
Remote unit, IR and ER, UL&DL 3 dB typical, < 3.5 dB at max gain
Maximum input level, no damage

Donor unit, SD and DD, UL/DL + 10 dBm / + 23 dBm
Remote unit, IR and ER, UL&DL + 10 dBm
Output power per carrier, 2 channels

UL DL
Donor unit, SD - 10 dBm GSM/ GMSK + 37 dBm GSM/ GMSK
- 13 dBm EDGE / 8-PSK average power + 34 dBm EDGE / 8-PSK average power
Donor unit, DD - 7 dBm GSM/ GMSK + 37 dBm GSM/ GMSK
Remote unit, IR + 37 dBm GSM/ GMSK + 40 dBm GSM/ GMSK
+ 34 dBm EDGE / 8-PSK average power + 37 dBm EDGE / 8-PSK average power
Remote unit, ER + 37 dBm GSM/ GMSK + 43 dBm GSM/ GMSK
Output power per carrier, 4 channels All values 3 dB less than above;
Gain
2 channels 4 channels
Donor unit, SD max 42 dB, adjustable, in 1 dB steps max 42 dB, adjustable, in 1 dB steps
Donor unit, DD max 45 dB, adjustable, in 1 dB steps max 45 dB, adjustable, in 1 dB steps
Remote unit, IR 75 - 105 dB, adjustable, in 1 dB steps 69 - 99 dB, adjustable, in 1 dB steps
Remote unit, ER 78 - 108 dB, adjustable, in 1 dB steps 72 - 102 dB, adjustable, in 1 dB steps

Input to Link Channel Frequency Error < 1 x 10-9
Modulation Accuracy at full output power

Donor unit, SD and DD, UL GSM / GMSK < 2.5 ° RMS and < 10 ° peak

Donor unit, SD and DD, DL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Remote unit, IR, UL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Remote unit, IR, DL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Remote unit, ER, UL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Remote unit, ER, DL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Intermodulation
Donor unit, SD and DD < -36 dBm (two carriers at full output power DL, 600 kHz spacing)
< -70 dBm (two carriers at full output power UL, 600 kHz spacing)
Remote unit, IR < -36 dBm (two carriers at full output power DL, 600 kHz spacing)
Remote unit, ER < -36 dBm (two carriers at full output power DL, 600 kHz spacing)

Power Consumption
Donor unit, SD and DD, 2/4 channels 110W / 240W typical
Remote unit, IR and ER, 2/4 channels 200W / 240W typical
MTBF > 100 000 hrs
ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.3.2 CSFT 1822/4
Frequency range, UL/ DL 1710 - 1785 MHz (DCS 1800) / 1805 - 1880 MHz (DCS 1800)

Selectivity, donor unit SD and DD > 60 dB at 400 kHz / > 65 dB at 600 kHz
Selectivity, remote unit, IR and ER > 60 dB at 400 kHz / > 70 dB at 600 kHz

Remote unit, IR and ER UL&DL 2.5 dB typical, < 3 dB at max gain
Remote unit, IR and ER UL&DL 3 dB typical, < 3.5 dB at max gain

Remote unit, IR and ER, UL&DL + 10 dBm

UL DL
Gain



Intermodulation

Power Consumption
Donor unit, SD and DD, 2/4 channels 150W / 240W typical
Remote unit, IR and ER, 2/4 channels 240W / 270W typical
MTBF > 100 000 hrs
ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.3.3 CSFT 1922/4
Frequency range UL/DL 1850 - 1920 MHz (PS 1900) / 1930 - 1990 MHz (PS 1900)
Selectivity, donor unit (SD and DD) > 60 dB at 400 kHz / > 65 dB at 600 kHz
Selectivity, remote unit (IR and ER) > 60 dB at 400 kHz / > 70 dB at 600 kHz
Noise figure, 2channels


Remote unit, IR and ER UL&DL + 10 dBm

UL DL
Gain

Link to output Channel Frequency Error < 1 x 10-9


Intermodulation


Power Consumption
Donor unit SD and DD, 2/4 channels 150W / 240W typical
Remote unit (IR and ER), 2/4 channels 240W /270 W typical
MTBF > 100 000 hrs
ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.4 Band Shifting Repeaters

7.4.1 CSFT 81922/4
Link Frequency range, UL /DL 1850 – 1910 MHz / 1930 – 1990 MHz
Operational bandwidth 25 MHz / 60 MHz
Number of channels 1- 4

> 65 dB at 600 kHz
> 70 dB at 600 kHz


Remote unit, IR and ER UL/DL + 10 dBm

UL DL
Gain



Intermodulation, 2 channels


Power Consumption, 2/4 channels
Donor unit, SD and DD 150 W / 240 W typical
Remote unit, IR and ER 220 W/ 240 W typical
MTBF > 100 000 hrs

ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.4.2 CSFT 91822/4
Frequency range UL/UL 880 – 915 MHz (E-GSM900) / 925 – 960 MHz (E-GSM900)
Link Frequency range UL/DL 1710 - 1785 MHz (DCS-1800) / 1805 - 1880 MHz (DCS-1800)
Operational bandwidth 35 MHz (E-GSM) / 25 MHz (P-GSM)

> 65 dB at 600 kHz
> 70 dB at 600 kHz

Remote unit, IR and ER, UL&DL 2.5 dB typical, < 3 dB at max gain
Remote unit, IR and ER, UL&DL 3 dB typical, < 3.5 dB at max gain

Donor unit SD and DD, UL/DL + 10 dBm / + 23 dBm
Remote unit IR and ER UL&DL + 10 dBm

UL DL
Gain


Donor unit SD and DD, UL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Donor unit SD and DD), DL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Remote unit IR, UL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
EDGE / 8-PSK < 3.5 % EVM RMS a

Remote unit IR, DL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Remote unit ER, UL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Remote unit ER, DL GSM / GMSK < 2.5 ° RMS and < 10 ° peak
Intermodulation
Donor unit SD and DD < -30 dBm (two carriers at full output power DL, 600 kHz spacing)
Remote unit IR < -36 dBm (two carriers at full output power DL, 600 kHz spacing)
Remote unit ER < -36 dBm (two carriers at full output power DL, 600 kHz spacing)

Power Consumption,
Donor unit 2/4 channels SD and DD 150 W /240 W typical
Remote unit 2/4 channels (IR and ER) 220 W /240 W typical
MTBF > 100 000 hrs

ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.4.3 CSFT 18922/4
Frequency range, UL/DL 1710 - 1785 MHz (DCS 1800) / 1805 - 1880 MHz (DCS 1800)
Link Frequency Range UL/DL 880 – 915 MHz (E-GSM 900) / 925 – 960 MHz (E-GSM 900)

> 65 dB at 600 kHz
> 70 dB at 600 kHz


Donor unit SD and DD, UL/DL + 10 dBm / + 23 dBm
Remote unit IR and ER UL/DL + 10 dBm

UL DL
Gain



Intermodulation
Donor unit SD and DD < -36 dBm (two carriers at full output power DL, 600 kHz spacing)
Remote unit IR < -30 dBm (two carriers at full output power DL, 600 kHz spacing)
Remote unit ER < -30 dBm (two carriers at full output power DL, 600 kHz spacing)


Power Consumption, 2 channels

Donor unit, 2/4 channels (SD and DD) 110 W / 200 W typical
Remote unit, 2/4 channels (IR and ER) 220 W / 270 W typical
MTBF > 100 000 hrs
ETS EN 301 502 (ETS EN 300 609-4 / GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.5 Fibre Fed Repeaters

7.5.1 CSF 922/4 (R)
Frequency range (UL/DL) 880 – 915 MHz (E-GSM900) / 925 – 960 MHz (E-GSM900)
Frequency range (UL/DL) 890 – 915 MHz (P-GSM900) / 935 – 960 MHz (P-GSM900)
Frequency range (UL/DL) 876 – 880 MHz (GSM-R) / 921 – 925 MHz (GSM-R)

> 65 dB at 600 kHz
Maximum input level, non destructive +10 dBm
Output power per carrier, 2 channels, DL +37 dBm GSM/ GMSK

+34 dBm EDGE / 8-PSK average power

GSM / GMSK DL < 2.5 ° RMS and < 10 ° peak
GSM / GMSK UL < 2.5 ° RMS and < 10 ° peak
EDGE / 8-PSK DL < 3.5 % EVM RMS
EDGE / 8-PSK UL < 3.5 % EVM RMS

Antenna connectors DIN 7/16, FC/APC
Power Consumption , 2/4 channels 110 W /170 W typical (traffic dependent)
MTBF > 100 000 hrs

ETS EN 301 502 (ETS EN 300 609-4/GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.5.2 CSF 1822/4
Frequency range, UL/DL 1710 - 1785 MHz (DCS-1800) / 1805 - 1880 MHz (DCS-1800)

> 65 dB at 600 kHz




Power Consumption, 2/4 channels 150 W / 290W typical (traffic dependent)
MTBF > 100 000 hrs

ETS EN 301 502 (ETS EN 300 609-4/GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.5.3 CSF 1922/4
Frequency range, UL/DL 1850 - 1910 MHz (PCS-1900) / 1930 - 1990 MHz (PCS-1900)

Selectivity > 60 dB at 400 kHz / > 65 dB at 600 kHz





Power Consumption, 2/4 channels 150 W / 290W typical (traffic dependent)
MTBF > 100 000 hrs

ETS EN 301 502 (ETS EN 300 609-4/GSM 11.26)
ETS EN 301 498-8
EN 60 950

7.5.4 CSF 2222/4
Frequency Bands According to ETSI TS 25.106 chapter 5.1 operating band 1
Uplink/ downlink 1920 - 1980 MHz / 2110 - 2170 MHz
UTRA / FDD UL/ DL separation 134.8 - 245.2 MHz

> 60 dB at 3.5 MHz
> 65 dB at 7.5 MHz
> 70 dB at 12.5 MHz

Output power per carrier, 2 channels DL +33 dBm ± 1dB average power, TM1/64 with 61% clipping (PAR =
8.3dB)
Output power per carrier, 4 channels DL +30 dBm ± 1dB average power, TM1/64 with 61% clipping (PAR =
8.3dB)
Maximum input level , non destructive + 13 dBm
Modulation Accuracy
Intermodulation < - 36 dBm (two carriers at full output power, 5 MHz spacing)

MTBF > 100000 hrs
ETSI EN 301 498-23
EN 60 950

REPEATER MAINTENANCE CONSOLE
Repeater Maintenance Console

Short Guide
Valid from RMC version 2.2
Copyright © 2008 Axell Wireless Ltd

No part of this document may be copied, distributed, transmitted, transcribed, stored in a retrieval system,
or translated into any human or computer language without the prior written permission of Axell Wireless
Ltd.
The manufacturer has made every effort to ensure that the instructions contained in this document are
adequate and free of errors and omissions. The manufacturer will, if necessary, explain issues which may
not be covered by this document. The manufacturer's liability for any errors in the document is limited to
the correction of errors and the aforementioned advisory services.
This document has been prepared to be used by professional and properly trained personnel, and the
customer assumes full responsibility when using them. The manufacturer welcomes customer comments as
part of the process of continual development and improvement of the documentation in the best way
possible from the user's viewpoint. Please submit your comments to the nearest Axell Wireless sales
representative.
© Axell Wireless Ltd SW 022 93 00 rev E 1 (7)

1 Installation
1.1 Requirements
CPU Pentium, 200 MHz (Pentium III, 500 MHz recommended)
RAM 64 MB (128 MB recommended)
Hard Drive 10 MB free disk space
CD-ROM Required for installation
Video resolution 800 x 600 with at least 15 bit color depth (approx. 32000 colors)
24 bit color depth (16.7 million colors) recommended
It is possible to run the program in 256 or 16 color modes, but colors
will appear distorted
Operating system Windows 98SE/NT/2000/XP
1.2 Installation Procedure

1. Ensure the computer and operation system complies with the requirements above.
2. Insert the CD-ROM into your CD-ROM reader. This will in most cases auto-start the setup program. If
not select your CD-ROM drive and double-click the file “Setup.exe”.
3. Follow the setup program guide through the installation process. Specify where the program should be
installed.
4. When the installation is finished, start the RMC from the” Start” menu (no reboot is needed)
1.3 Connection Setup

The RMC opens in Console
mode.
The repeater connection can be
made via serial cable, TCP/IP or
Modem.

1.3.1 Cable Connection Set up

Select “Serial Cable” and
“Next”
Select the serial port to be used.

Select “Connect”
1.3.2 TCP/IP Connection Set up

Select “TCP/IP” and “Next”
Enter the IP address and port or

choose one from the phone book.
1.3.3 Modem Connection Set up

Select “Modem” and “Next”
Select the modem to use.

Select “Next”
The RMC automatically receives a list of available modems from the

Windows operation system.
Note! It is important that the modem is installed in Windows according to

the manual provided by the modem manufacturer.

Enter the phone number.

Type the number or choose one
from the phone book.
Select “Connect” and wait for the

connection to be established
1.3.4 Login
Enter username and password (in
terminal mode the login prompt
is text based).
Select “Next”
Default usernames and passwords differ for different repeater

generations. Please consult the manual for the repeater that is to be
connected.
User name and password structure 1
User Name Password Authority

USERNAM1 PASSWRD1 read/write
USERNAM2 PASSWRD2 read/write

USERNAM3 PASSWRD3 read only

USERNAM4 PASSWRD4 read only
User name and password structure 2
User Name Password

avitec AvitecPasswd
1.4 How to Change a Parameter

There is a two step procedure to change a parameter in RMC.
Change the value A value can be changed by typing it or by choosing a value from a
drop down menu
In this case there is a drop down menu. Click on ”b” to the right of
the box and chose a value.
Apply or cancel the change As soon as a change is made or a value is inserted this symbol appears
The change is applied by clicking the green “accept button”

The change is canceled by clicking the red cross (or by pressing Esc)
1.5 How to Use the Phone Book

Modem phone numbers and /or IP addresses can be stored in the RMC phone book. Each computer user is
allocated an individual RMC phonebook which is stored in the windows registry.
Select Modem during login.

Initial screen

Select TCP/IP during login.

Initial screen
1.5.1 Add a Phone Number or TCP/IP Address

Type the number in the edit box
Click “Add”
This brings up a dialog box
Enter a description of the
phonebook entry
Click “Ok”
1.5.2 Edit a Phone Number or TCP/IP Address

Select a number in the list
Select “Edit”
This brings up a dialog box
Make the changes
Select “Ok”

1.5.3 Delete a Phone Number or TCP/IP Address

Select a n entry in the list
Select “Delete”
Confirm
1.5.4 Import/Export Phonebook Data

Select “Phonebook Options”
Choose between the options:
Save
Restore
Synchronize
The file extension is RPF.
Files can be used in RMC
versions 2.00 and later.
Phonebook data from RMC
version 1.xx (INI-files) can also
be imported.

AXELL WIRELESS
GSM-UMTS Commands and Attributes
v1.0.1
GSM-UMTS Commands and Attributes v1.0.1
File Name: Document Number: Version: Pages:

GSM-UMTS Commands and Attributes v1.0.1 v1.0 -- 1.4 96
Last Revision: Subject:
24/01/09 Commands and Attributes
Author: Checked: Approved:
Anders Pettersson MW, AP MW
Change Log
Version Change by Date Description
1.0 AP 2008-06-08 Initial version released.
1.1 AP 2008-06-11 Changed the ACx and ALx descriptions to match the target specification updates.
Added the HBT format chapter 10.
Added alarm attributes chapter 11.
Removed document information from first page, put it on second.
Changed footing throughout the document.
Updated attributes AC4-AC7 and AL6-AL9.
Updated RSP, IHU, WRD, PSD, PW2, PW3, PW4, TEL, FOC, CRC, COM
Added opto related attributes Type I. Changed the other attribs to Type II,
different chapter.
Fixed errors in ASD/ASU
HBT updated!!!
Alarm overview table updated.
MNP attribute added.
1.2 AP 2008-06-13 Updated from target specification 1.2:
- RSP attribute updated.
- Heartbeat format updated.
1.3 AP 08-07-15 MGA attribute removed (not implemented in this target).
TEM attribute added to the specification, similar as from the BSF target.
PW4 status added to HBT and DOO moved to bit 0 in same byte as before.
MNP changed to NMP as it was wrong.
OMP changed to OSP for optical modules type I. Please note that the format of
OSP is different in type I and type II optical modules.
ASU added to AL4 description, was missing for some reason. Example updated.
CRC attribute description updated for COMMUX.
1.4 AP 08-09-30 6.5 Updated AC6 with WRD attribute.
6.11 Updated AL8 with WRD attribute.
6.14 changed format of RSP with regard to the WRD attribute.
11.2 heartbeat is now changed slightly. PW3 for COMMUX removed and WRD
added as a ninth byte to existing block.
Alarm table updated with Minor Environment for WRD attribute.
1.5 MW 09-01-24 Added chapter Axell versus Avitec
Commands and Attributes 2/96

Contact Information
For further information about this document, please contact
support@axellwireless.com.
AXELL WIRELESS
Mailing address:
Axell Wireless
Aerial House
Asheridge Road
Chesham
United Kingdom
Tel: +44 1494 777000

Fax: +44 1494 777002
Web: http://www.axellwireless.com/
Legal Information
© COPYRIGHT AXELL WIRELESS 2009
translated into any human or computer language without the prior written permission of AXELL WIRELESS.
The manufacturer has made every effort to ensure that the instructions contained in the documents are adequate and
free of errors and omissions. The manufacturer will, if necessary, explain issues which may not be covered by the
documents. The manufacturer's liability for any errors in the documents is limited to the correction of errors and the
aforementioned advisory services.
assumes full responsibility when using them. The manufacturer welcomes customer comments as part of the process
of continual development and improvement of the documentation in the best way possible from the user's viewpoint.
Please submit your comments to the nearest AXELL WIRELESS sales representative.

TABLE OF CONTENTS
1 Overview...................................................................................................................7
2 Axell Wireless versus Avitec.........................................................................................8
3 Version Compatibility..................................................................................................9
4 Using Commands and Attributes.................................................................................10
5 Built-in Help System..................................................................................................11
5.1 HELP command..................................................................................................11
5.2 INF command....................................................................................................11
6 GSM-UMTS Commands..............................................................................................12
6.1 STATUS.............................................................................................................12
7 Compressed Alarms and Statuses...............................................................................13
7.1 AC2 – Compressed alarm severity and alarm class configurations............................13
7.6 AC7 – Compressed alarm format..........................................................................15
7.7 AL4 – Compressed alarm format..........................................................................15
7.10 AL7 – Compressed alarm format........................................................................16
7.13 ALL – Compact Message for getting Status and RF Parameters from Repeater..........17
7.14 RSP – Repeater Status Parameters.....................................................................18
8 RF Related Parameters and Settings............................................................................20
8.1 AMD – Status of amplifier chain downlink..............................................................20
8.2 AMU – Status of amplifier chain uplink..................................................................21
8.3 ASD – Amplifier chain saturation downlink.............................................................22
8.4 ASL – Amplifier saturation level...........................................................................23
8.5 ASU – Amplifier chain saturation uplink.................................................................25
8.6 ATD – Attenuation downlink.................................................................................27
8.7 ATU – Attenuation Uplink....................................................................................28
8.8 CHA – Channel configuration...............................................................................28
8.9 CHD – Channel Configuration Downlink.................................................................30
8.10 CHL – Channel configuration limits.....................................................................32
8.11 CLN – Serving Channel and Link Channel Configuration.........................................33
8.12 CRC – Status of EEPROM checksum....................................................................36
8.13 IHU – Installed Hardware Units..........................................................................36
8.14 IOD – Input overload downlink...........................................................................37
8.15 IOU – Input overload uplink...............................................................................38
8.16 IPL – Input power level.....................................................................................38
8.17 LNK – Link channel...........................................................................................40
8.18 LVD – Peak power output level downlink..............................................................41
8.19 LVU – Peak power output level uplink..................................................................43
8.20 NCH – Number of channels................................................................................46
8.21 OPL – Output power levels.................................................................................46
8.22 PDC – Power downlink level configuration............................................................47
8.23 PDL – Status of power downlink level..................................................................49
8.24 RFP – RF Parameters........................................................................................51
8.25 SZD – Status of synthesizer downlink.................................................................52

8.26 SZU – Status of synthesizer uplink.....................................................................53

8.27 VLD – Valid peak limiting levels downlink............................................................55
8.28 VLU – Valid peak limiting levels uplink.................................................................55
8.29 WRD – Return Loss Downlink alarm....................................................................56
8.30 WRL – Return Loss Measurement.......................................................................56
9 Miscellaneous Attributes............................................................................................58
9.1 BAT – Status of battery charge............................................................................58
9.2 COM – Status of Communications with Active Devices............................................59
9.3 FDC – FDM count...............................................................................................59
9.4 PLV – Power Supply Levels..................................................................................60
9.5 PSC – Power Supply Count..................................................................................61
9.6 PSL – Status of Power Supply Level......................................................................61
9.7 PTM – Status of Power Supply Temperature...........................................................62
9.8 PSD – Power Supply Distribution..........................................................................63
9.9 PW1 – Power 1..................................................................................................63
9.10 PW2 – Power 2.................................................................................................64
9.11 PW3 – Power 3.................................................................................................65
9.12 PW4 – Power 4.................................................................................................66
9.13 RBT – Radio Board Temperature.........................................................................66
9.14 TEL – Temperature Levels..................................................................................67
9.15 TEM – Status of Controller Temperature..............................................................67
10 Opto Related Attributes (Type I)...............................................................................68
10.1 OLA – Optical Link Adjustments.........................................................................68
10.2 OLC – Optical Link Compensation ......................................................................68
10.3 OLV – Optical Levels.........................................................................................68
10.4 OSP – Opto Module Parameters..........................................................................69
10.5 RXO – Status of Received Optical Level...............................................................69
10.6 TXO – Status of Transmitted Optical Level...........................................................70
11 Opto related attributes (Type II)...............................................................................72
11.1 FOC – Fiber-Optic Capabilities............................................................................72
11.2 OLA – Optical Loss Adjustment .........................................................................73
11.3 OLC – Optical Loss Compensation.......................................................................74
11.4 OLV – Optical Level...........................................................................................75
11.5 OSP – Opto Slave Parameters............................................................................75
11.6 PTE – Pilot Tone Enabled...................................................................................76
11.7 PTL – Pilot Tone Level.......................................................................................77
11.8 PTN – Pilot Tone Nominal Level..........................................................................77
11.9 RXO – Status of Received Optical Level...............................................................78
11.10 RXP– Status of Received Pilot Tone Level..........................................................79
11.11 SZP – Status of Pilot Tone Generator Synthesizer...............................................79
11.12 TXO – Status of Transmitted Optical Level.........................................................80
12 Heartbeat Format....................................................................................................82
12.1 Hex encoded values, a quick description..............................................................82
12.2 Heartbeat table................................................................................................82
13 Alarm Sources........................................................................................................87
13.1 AIM – Antenna isolation measurement................................................................88
13.2 AMD – Amplifier chain downlink.........................................................................88
13.3 AMU – Amplifier chain uplink.............................................................................88
13.4 ASD – Amplifier saturation downlink...................................................................89
13.5 ASU – Amplifier chain uplink..............................................................................90
13.6 BAT – Battery level...........................................................................................90
13.7 COM - Communication......................................................................................91
13.8 CRC – EEPROM Error........................................................................................91

13.9 IOD – Input overload downlink...........................................................................91

13.10 IOU – Input overload uplink.............................................................................92
13.11 NMP – Node communications path....................................................................92
13.12 PDL – BCCH/Pilot tone downlink.......................................................................92
13.13 PSL – Power supply level.................................................................................92
13.14 PTM – Power supply temperature......................................................................93
13.15 PW1 – Power 1...............................................................................................93
13.16 PW2 – Power 2...............................................................................................93
13.17 PW3 – Power 3...............................................................................................93
13.18 PW4 – Power 4...............................................................................................94
13.19 RBT – Radio board temperature........................................................................94
13.20 RXO – Receive level optical..............................................................................94
13.21 RXP – Pilot tone status....................................................................................94
13.22 SZD – Synthesized downlink............................................................................94
13.23 SZP – Synthesizer pilot tone............................................................................95
13.24 SZU – Synthesizer uplink.................................................................................95
13.25 TXO – Transmission level optical.......................................................................95
13.26 WRD – VSWR alarm........................................................................................96

1 OVERVIEW
Axell network elements1 equipped with a controller contains a Local Maintenance
Terminal (LMT) port, and optionally a modem. This allows for configuration of the
element locally and optionally remotely.
Using a terminal emulation software, such as HyperTerminal (Windows) or MiniCom

(Linux/Unix) it is possible to configure the equipment using a simple command
structure (terminal emulation should be set to VT100 or ANSI).
Axell Repeater Command and Attributes documentation consists of two parts;
– the Common part defines all functionality available for all Axell repeaters with
the new generation of controllers (H40 and H50 series).
– the Target part defines all commands and attributes available for the specific
repeater type in a separate document.
This document specifies the functionality for all commands and attributes available
in the GSM-UMTS target implementation.
This is valid for CSR, CSFT and CSF repeaters of the following characteristics:
● 850, 900, 1800, 900 and 2200 MHz bands.
● SD/DD/ER/IR versions of frequency- and band-shifting repeaters.
● Fibre fed channel selective repeaters for GSM and UMTS.
● 2 or 4 channel versions.
We would appreciated if any errors and omissions in this document was reported to
your closes Axell Wireless representative or sent directly to
support@axellwireless.com for inclusion in future releases.
1 Network elements are for instance repeaters, Fiber Optic HUB units, etc.

2 AXELL WIRELESS VERSUS AVITEC

Summer of 2007 Avitec AB (Sweden) and Aerial Facilities Ltd (UK) joined forces to
form Europe's largest manufacturer of coverage solution equipment.
During winter 2008 the companies were brought together under one common
name, Axell Wireless.
However, since the base of this firmware was designed before companies were
merged, certain places in the firmware still mentions Avitec, such as the login
screen and the prompt. Yet, the product is sold, marketed and supported via Axell
Wireless and it's sales and support organisation.

3 VERSION COMPATIBILITY
Commands and attributes described in this document refers to GSM-EDGE
repeaters with Target firmware version GSM-EDGE 1.0.1.
Firmware version of the controller can be obtained (once logged in) by using the
attribute SWV.

4 USING COMMANDS AND ATTRIBUTES

When logged in to the repeater, a number of different commands and attributes are
available. Commands have interaction with the user, or displays the reply on
multiple rows, while attributes are worked on using GET, SET or ACT syntax which
gives a reply normally on a maximum of one row.
Read-only attributes are read using GET.
Example:
AVITEC AB> GET MDL
CSFT91822-ER
AVITEC AB>
Read and write attributes are either read or written

Example:
AVITEC AB> GET TAG
Repeater Name: Earl
AVITEC AB> SET TAG Site at Sundbyberg Centrum
AVITEC AB> GET TAG
Site at Sundbyberg Centrum
AVITEC AB>
Actions are used to perform actions.

Example:
AVITEC AB> ACT RCD
AVITEC AB>
which resets the communications device/modem.

5 BUILT-IN HELP SYSTEM
5.1 HELP command

By entering the command
HELP
a list of all attributes and their modes of operation are displayed in alphabetic order.
Three different columns are displayed. First column is the actual attribute. Second
column displays valid attribute access methods.
r – this means attribute can be GET
w – this means attribute can be SET
x – means attribute can be worked on with ACT (action).
Each row ends with a brief description of the attribute.
Example:
AVITEC AB>help
AC1 r Displays alarm severity and class for a number of alarm sources.
ACK x Acknowledges alarm log entries.
ACL rw Displays and changes default alarm classes.
ADC r Returns number of active devices in the system.
ADD rw Configures SMS access list to communicate with the repeater.
AGC r This displays status of the AGC in uplink and downlink.
AL1 r Displays alarm configurations for EX1, EX2, EX3, EX4 and DOO.
AL2 r Displays alarm configurations for VLI, LGO, CLR, FWU and FWF.
ALA rw Used for reconfiguration of the alarm settings / thresholds.
ALL r Replies with the same information as in the heartbeat sent to the
AEM.
...
5.2 INF command

The INF attribute gives detailed information about a specific attribute (similar to
information in this document).
Example:
AVITEC AB> INF DOO
This read-only attribute displays the status of the door, 0=OK, 1=ERROR.
Reply format:
X
X=0 means status is OK
X=1 means status is ERROR
X=- (dash) means status is indeterminable, or alarm source is not measured.
Example:
GET DOO
Replies:
0
meaning status is OK.

6 GSM-UMTS COMMANDS
6.1 STATUS
The STATUS command gives an overview of the entire repeater RF-configuration
and status of all alarm sources in the system.
Example of a status screen:

Column
Row 01234567890123456789012345678901234567890123456789012345678901234567890123456789
1 ---LIMPA--------1-UL--DL-2-UL--DL-3-UL--DL-4-UL--DL | PSUP–Comm1: OK Comm2: OK
2 Attenuation 15 10 15 10 15 10 15 10 | Input: 241.1 V OK
3 Output Power 43 OFF 43 OFF 43 OFF 43 OFF | PW1: 28.1 V OK 28.1 V OK
4 Sat UL/DL OK OK OK OK OK OK OK OK | PW2: 14.9 V OK 18.0 V ERR
5 Amplifier Chain ERR OK ERR OK ERR OK ERR OK | PW3: 6.40 V OK 6.40 V OK
6 DL Level(dBm) 10.0 ERR 10.0 ERR 10.0 ERR 10.0 ERR | PW4: 6.40 V OK
7 COM OK OK OK OK OK ERR OK OK | Bat: 9.6 V OK
8 PW1/PW2/PW3 OK/ER OK/OK/OK ER/OK/OK OK/OK/OK | Tem: +76.5C ERR +76.5C ERR
9 Last antenna isolation: OK: 120 dB |---------------------------
10 | Temperature: -30.7 C (ERR)
11 ---FIBER OPTIC MODULE--1--------2--------3--------4 | Door: Open (ERR)
12 RXOpto(mW/Stat) 1.20/ OK 1.20/ OK 1.20/ OK 1.20/ OK | Relay Status: Open (ERR)
13 TX Opto OK OK OK OK |-CRC STATUS---1---2---3---4
14 Pilot Synth Status OK ERR OK OK | Opto: OK ERR OK OK
15 RX Pilot Lvl (dBm) -28.1 -35.1 -26.1 -100.0 | CommMux: OK
16 Temp (C/Stat) -9.0/ERR -9.0/ERR -9.0/ERR -9.0/ERR | -SYSTEM SLAVE-------------
17 ---EXTERNAL ALARM INPUTS----------------------------| RX Data Qual: 100.0% (OK)
18 1 OK 2 OK 3 OK 4 OK

7 COMPRESSED ALARMS AND STATUSES

This chapter contains alarm attributes that returns information in a compressed
format. This is normally used by the RMC and Element Manager softwares.
● Lists of alarm severities and classes.
● Lists of alarm statuses in compressed formats.
7.1 AC2 – Compressed alarm severity and alarm class

configurations
This attribute returns the alarm severity and class configurations for a number of
alarm sources.
Usage
Attribute type: Read Only
This is a compact message to retrieve Severity and Class of miscellaneous alarm

sources in the repeater. The alarm sources returned are the following:
Sources:
AIM AMD AMU ASD ASU
Format:
<SevAIM> <ClassAIM> <SevAMD> <ClassAMD> ... <SevASU> <ClassASU>
Example
GET AC2
Reply:
MA EN MA EQ MA EQ MI EN MI EN

configurations
alarm sources.
Usage

Sources:
IOD IOU SZD SZU
Format:
<SevIOD> <ClassIOD> <SevIOU> <ClassIOU> ... <SevSZU> <ClassSZU>
Example:

GET AC3
Reply:
MA EN MA EN CR EQ CR EQ

configurations
alarm sources.
Usage

Sources:
COM CRC TEM PTM RBT
Format:
<SevCOM> <ClassCOM> <SevCRC> <ClassCRC> <SevRBT> <ClassRBT>
Example:
GET AC4
Reply:
CR CO CR EQ MA EN MA EN MA EN

configurations
alarm sources.
Usage

Sources:
NMP RXO RXP SZP TXO
Format:
<SevNMP> <ClassNMP> <SevRXO> <ClassRXO> ... <SevTXO> <ClassTX0>
Where all severities are described ass
Example:
GET AC5
Reply:
MA EN MA EQ MI EQ MA EQ CR EQ


configurations
alarm sources.
Usage

Sources:
BAT PDL PSL WRD
Format:
<SevBAT> <ClassBAT> <SevPDL> <ClassPDL> ... <SevWRD> <ClassWRD>
Example:
GET AC6
Reply:
MI EQ MA EN MA EN MI EN
7.6 AC7 – Compressed alarm format

alarm sources.
Usage

Sources:
PW1 PW2 PW3 PW4
Format:
<SevPW1> <ClassPW1> <SevPW2> <ClassPW2> <SevPW3> <ClassPW3> <SevPW4> <ClassPW4>
Example:
GET AC7
Reply:
CR EQ CR EQ CR EQ CR EQ
7.7 AL4 – Compressed alarm format

A compact message to retrieve alarm configurations.
Usage:

Same as AL1 but replies with the configuration for the following alarm sources:
Sources:
AIM AMD AMU ASD ASU
Example:
GET AL4
Reply:
2 0 2 75 0 5 2 0 1 60 60 5 2 0 1 60 60 5 2 0 4 0 0 5 2 0 4 0 0 5

Usage:
Sources:
IOD IOU SZD SZU
Example:
GET AL5
Reply:
2 0 4 0 0 5 2 0 4 0 0 5 2 0 4 0 0 5 2 0 4 0 0 5

Usage:
Sources:
COM CRC TEM PTM RBT
Example:
GET AL6
Reply:
2 0 4 0 0 3 2 0 4 0 0 3 2 0 1 -25 65 5 2 0 1 -25 65 5 2 0 1 -25 65 5

Usage:

Sources:
NMP RXO RXP SZP TXO
Example:
GET AL7
Reply:
0 0 4 0 0 3 2 0 2 -15 0 5 2 0 1 30 30 5 2 0 4 0 0 5 2 0 4 0 0 5

Usage:
Sources:
BAT PDL PSL WRD
Example:
GET AL8
Reply:
2 0 1 75 120 5 2 0 2 33 0 5 2 0 1 2150 2650 5 2 0 2 12 0 30

AL9 – Compressed alarm format
Usage:
Sources:
PW1 PW2 PW3 PW4
Example:
GET AL9
Reply:
2 0 1 260 300 5 2 0 1 140 160 5 2 0 1 620 660 5 2 0 1 620 660 5
7.13 ALL – Compact Message for getting Status and RF

Parameters from Repeater
A compact message of all status and RF configuration in the repeater.
Usage
Attribute type: Read only

This attribute replies with the same information as in the heartbeat sent to the Axell
Element Manager, except the header information (Repeater ID, STATE, Message # ,
Time and Date ).
Please refer to chapter Heartbeat Reports format.
7.14 RSP – Repeater Status Parameters

This attribute replies with status of all alarm sources in the repeater.
Usage:
This attribute replies with status of all alarm sources in the repeater and is used to
get a quick overview of the entire repeater status.
Format:
<AIM> <AMD> <AMU> <ASD> <ASU> <BAT> <COM> <CRC> <DOO> <EX1-4> <IOD> <IOU> <PDL> <PSL>
<PTM> <PW1> <PW2> <PW3> <PW4> <RBT> <RXO> <RXQ> <SZD> <SZP> <SZU> <TEM> <TXO> <WRD>
where
Attrib Field Explanation
description
AIM N is antenna Isolation Measurement
AMD NNNN is status for amplifier chain in downlink.
AMU NNNN is status for amplifier chain in uplink.
ASD NNNN is amplifier saturation status in downlink.
ASU NNNN is amplifier saturation status in uplink.
BAT N is status of Battery Charge for controller and modem backup.
COM See COM attrib is status of communication with active devices. See COM attribute.
CRC NNNNN is status of EEPROM CRC in FO-slaves (only type 2) and COMMUX if
present.
DOO N is door status.
EX1 – NNNN is status of external alarms 1 – 4.
EX4
IOD N is input overload downlink alarm
IOU N is input overload uplink alarm
PDL NNNN is Power Level Downlink statuses.
PSL N is status of Power Supply input level.
PTM NN is status of Power Supply Temperature.
PW1 NNNNNN is status of Power Supply 1 as measured in PSUPs and LIMPAs.
PW2 NNNNNNN is status of Power Supply 2 as measured in PSUPs and LIMPAs.
PW3 NNNNNNNNN is status of Power Supply 3 as measured in PSUPs, LIMPAs, REFGEN,
COMMUX and FO-slaves (type 1 only).
PW4 N is status of Power Supply 4 as measured in PSUP1.
RBT NNNNNNNN is Radio Board Temperature as measured in LIMPA and FO-Slaves type 2.
RXO NNNN is status of Received Optical Levels.
RXP NNNN is status of received Pilot Tone Level.

RXQ N is status of received data quality.

SZD AABBCCDD is synthesizer lock status for LIMPA downlink.
SZP NNNN is synthesizer lock status for Pilot Tone Generators.
SZU AABBCCDD is synthesizer lock status for LIMPA uplink.
TEM N is temperature status as measured in controller.
TXO NNNN is status of Transmitted Optical Levels.
WRD NM is status of the VSWR alarm. N is always present for VSWR status FDM
server 1 and M is present in repeaters using 2 server FDM's such as ER
type repeaters. If FDM server 2 is not present it is reported as “-”.
Value can be:

0 means status is OK
1 means status is ERROR
- (dash) means module is not installed or data is not available (not yet measured).
Example:
GET RSP
Reply from a CSR922 repeater:

0 00-- 00-- 00-- 00-- 0
AIM AMD AMU ASD ASU BAT
0-00-0------0- ----- 0 0000 0 0
COM CRC DOO EX1-EX4 IOD IOU
00-- 0 0- 0-0-0- 0-0-0-- 0-0-0-0--
PDL PSL PTM PW1 PW2 PW3
0 0 ---- ---- ----
PW4 RBT RXO RXP RXQ
0000---- ---- 0000---- 0 ---- 0-
SZD SZP SZU TEM TXO WRD
0 00-- 00-- 00-- 00-- 0 0-00-0------0- ----- 0 0000 0 0 00-- 0 0- 0-0-0- 0-0-0-- 0-0-
0-0-- 0 0 ---- ---- ---- 0000---- ---- 0000---- 0 ---- 0-

8 RF RELATED PARAMETERS AND SETTINGS

This chapter contains attributes related to the Radio Frequency (RF) performance
and settings of the eqipment including the following functions:
● Input and output RF levels, settings and readings
● Amplifier functions and settings
● Frequency settings
● Repeater RF Parameters
● Return loss monitoring
8.1 AMD – Status of amplifier chain downlink

This replies with the status of the amplifier chains in the downlink.
Attribute Type: Read-Only
This attribute replies with the status of the amplifier chain in the downlink path.
Amplifier chains are monitored by measuring the input signal level and comparing it
to the expected output power with respect to the attenuation settings. If output
power is not within expected interval (as configured with ALA AMDinstalled Radio
Units in the downlink path. Amplifier chains are monitored by measuring the input
signal level and comparing it to the expected output power with respect to the
attenuation settings. If output power is not within expected interval (as configured
with ALA AD1 – ALA AD4), an alarm is triggered.
Format for 2 carrier repeaters:

XY
where
X is status for downlink amplifier chain 1.
Y is status for downlink amplifier chain 2.
and values are
0 means status is OK.
1 means status is in ERROR.
- means not configured or not communicating.
Example:
GET AMD
Reply:
10
meaning that downlink one reports error while downlink two is OK.
Format for 4 carrier repeaters:

XYZW
where
X is status for downlink amplifier chain 1.
Y is status for downlink amplifier chain 2.
Z is status for downlink amplifier chain 3.
W is status for downlink amplifier chain 4.
and values are
0 means status OK.
1 means status is ERROR.
- means no communication or not configured.
Example:
GET AMD
Reply:
01--
meaning that chain 1 downlink is OK, chain 2 is in error and chain 3 and 4 either
are not installed or there is a communications alarm with corresponding module.
8.2 AMU – Status of amplifier chain uplink

This replies with status of the amplifier chains for the installed radio units.
This attribute replies with the status of the amplifier chain in the uplink path. Ampli-
fier chains are monitored by measuring the input signal level and comparing it to
the expected output power with respect to the attenuation settings. If output power
is not within expected interval (as configured with ALA AMU), an alarm is triggered.
Format in 2 carrier repeaters:

XY
where
X is status for chain 1
Y is status for chain 2
and values are
Example:
GET AMU
Reply:
01
meaning that chain 1 downlink is OK, chain 2 is in error.


XYZW
where
X is status for Radio Unit 1.
Y is status for Radio Unit 2.
Z is status for Radio Unit 3.
W is status for Radio Unit 4.
and values are
Example:
GET AMU
Reply:
01--
meaning that chain 1 downlink is OK, chain 2 is in error and chain 3 and 4 either
are not installed or there is a communications alarm with corresponding module.
8.3 ASD – Amplifier chain saturation downlink

Displays status of the amplifier saturation status in downlink.
Amplifier Saturation indicates that the amplifier chain in downlink has gone into sat-
uration and hence does not work in an optimal way.
An amplifier chain going into saturation means that gain in downlink is too high
with respect to input signal level. This can be an indicator that the repeater is oscil-
lating due to insufficient isolation between pick-up and serving antennas. If this
happen reduce gain in the repeater by increasing attenuation both downlink and
uplink. Other tell-tale signs of oscillation are full output power all the time in all
downlink and uplink channels.
With WCDMA signals this may happen due to the dynamic regulation of the base
station downlink output power. As traffic in the cell increases, so does the base sta-
tion output power. This may lead to a higher input signal than when the repeater
was commissioned and therefore trigger this alarm. In this case, increase the
downlink attenuation in the affected chain 1-2 dB, observe and see if the alarm dis-
apperas. If not, then increase another 1-2 dB.
This alarm normally indicates that gain in downlink should be decreased.
Format in 2 carrier repeater:

XY
where

X is amplifier saturation status in downlink chain 1.

Y is amplifier saturation status in downlink chain 2.
Value is
0 if status is OK/Not saturated.
1 if statis is ERROR/Saturated.
- means module is not configured or there is a communications error with the
module.
Example:
GET ASD
Reply:
10
indicating that amplifier chain one is saturated / in error, and that gain should be
decreased. Chain 2 works as expected.
Format in 4 carrier repeater:

XYZW
where
X is amplifier saturation status in downlink chain 1.
Y is amplifier saturation status in downlink chain 2.
Z is amplifier saturation status in downlink chain 3.
W is amplifier saturation status in downlink chain 4.
Value is
0 if status is OK/Not saturated.
1 if statis is ERROR/Saturated.
- means module is not configured or there is a communications error with the
module.
Example:
GET ASD
Reply:
100-
indicating that amplifier chain one is saturated / in error, and that gain should be
decreased. Chain 2-3 works as expected while chain 4 either is not configured, or
there is a communications error with the radio board.
8.4 ASL – Amplifier saturation level

Displays current saturation status in uplink and downlink paths.
An amplifier going into saturation means that system does not work in an optimal
way, and that the Automatic Level Control (ALC) decreases system gain.

In downlink path, input signal level should be fairly constant, why downlink satura-
tion normally indicates that input signal level to the system has increased or that
the system is not properly commissioned.
In uplink path, input signal level will normally vary, why a mobile station being
close to the server antenna is likely to cause the amplifier to go into saturation. Up-
link saturation is hence a normal system behavior.
Format for 2 carrier repeaters

KLXY
where
K indicates current saturation in uplink 1.
L indicates current saturation in uplink 2.
X indicates current saturation in downlink 1.
Y indicates current saturation in downlink 2.
Saturation is indicated by a number from 0-3 in EDGE-GSM repeaters and 0-1 in

WCDMA repeaters. Below is a description on what the different numbers means:
EDGE-GSM type repeaters

0 means amplifier is below optimum setting and attenuation could be decreased.
1 mean amplifier is working at the optimum setting.
2 means amplifier is going into saturation and that attenuation should be
increased.
3 means amplifier is well into saturation and signal quality may be affected.
WCDMA type repeaters

0 means amplifier works in linear range.
1 means amplifier is in non-linear (saturated) mode and that attenuation needs
to be increased. If the saturation is too high then the signal quality may be
adversely affected by this leading to lower quality than expected.
All repeater types
- (dash) means there is a communications error with the LIMPA module.
Example:
GET ASL
Reply:
0010
indicating that downlink amplifier in chain 1 is saturated. If this is the BCCH (GSM)
or pilot tone frequency (WCDMA) then it probably means the downlink attenuation
should be adjusted, the input signal is a little too high for the gain of the repeater.

JKLMXYZW
where

J indicates current saturation in uplink 1.

K indicates current saturation in uplink 2.
L indicates current saturation in uplink 3.
M indicates current saturation in uplink 4.
X indicates current saturation in downlink 1.
Y indicates current saturation in downlink 2.
Z indicates current saturation in downlink 4.
W indicates current saturation in downlink 4.
Saturation is indicated by a number from 0-3 in EDGE-GSM repeaters and 0-1 in

WCDMA repeaters. Below is a description on what the different numbers means:
EDGE-GSM type repeaters

0 means amplifier is below optimum setting and attenuation could be decreased.
1 mean amplifier is working at the optimum setting.
2 means amplifier is going into saturation and that attenuation should be
increased.
3 means amplifier is well into saturation and signal quality may be affected.
WCDMA type repeaters

0 means amplifier works in linear range.
1 means amplifier is in non-linear (saturated) mode and that attenuation needs
to be increased. If the saturation is too high then the signal quality may be
adversely affected by this leading to lower quality than expected.
All repeater types
- (dash) means there is a communications error with the LIMPA module.
Example:
GET ASL
Reply:
00010000
indicating that uplink amplifier in chain 4 is saturated. This probably means that a
user is using the mobile station in the proximity of the repeater server antenna for
this radio service.
8.5 ASU – Amplifier chain saturation uplink

Displays status of the amplifier saturation status in the uplink.
Amplifier Saturation indicates that the amplifier chain in uplink has gone into
saturation and hence does not work in an optimal way.

An amplifier chain going into saturation means that gain in uplink is too high with
respect to input signal level. This may be caused due to mobile stations very close
to the repeater serving antenna or other interference.
If this alarm happens only occasionally it is usually safe to leave the repeater as it
is. If it is something that occurs often then uplink attenuation should be increased a
few dB to lower the repeater gain in the uplink.

XY
where
X amplifier saturation status uplink 1.
Y amplifier saturation status uplink 2.
Values allowed are

0 amplifier saturation status is OK.
1 amplifier is saturated.
- no connection with amplifier or other error.
Example:
GET ASU
Reply:
10
indicating that uplink amplifier chain one is saturated and that gain should be de-
creased. Chain 2 is working as expected.

XYZW
where
X amplifier saturation status uplink 1.
Y amplifier saturation status uplink 2.
Z amplifier saturation status uplink 3.
W amplifier saturation status uplink 4.
Values allowed are

0 amplifier saturation status is OK.
1 amplifier is saturated.
- no connection with amplifier or other error.
Example:
GET ASU
Reply:
1000

indicating that uplink amplifier chain one is saturated and that gain should be de-
creased. Chain 2-4 works as expected.
8.6 ATD – Attenuation downlink

This attribute is used to read and configure attenuation/gain settings in the down-
link path.
Attribute type: Read and Write
This attribute is used to read and configure the attenuation/gain in the downlink
paths. Attenuation configures how much the chain should be degraded from max-
imum gain / performance.
Format on setting parameter:

SET ATD K X [L Y] [M Z] [N W]
K is the chain selector, and X is the attenuation in downlink chain K. Optionally at-
tenuation in chain L, M, N can be set in the same command.
The chain selector from 1 to 4, and the attenuation is settable in 1 dB steps from 0
to 30 dB.
Example:
SET ATD 2 7
sets attenuation in downlink chain 2 to 7 dB.
Example:
SET ATD 2 11 3 11
sets attenuation in downlink chains 2 and 3 to 11 dB.
Format on getting parameters:

GET ATD
Reply in 2 carrier repeaters:

1 X 2 Y
X is attenuation in chain one downlink, Y attenuation in downlink 2. If a chain is not

communicating a dash '-' may be returned indicating the error.

1 X 2 Y 3 Z 4 W
X is attenuation in chain one downlink, Y attenuation in downlink 2, Z attenuation in

downlink 3 and W in downlink 4. If chain is not responding, a '-' (dash) is replied.
Example:
GET ATD
Reply:
1 10 2 10 3 -8 4 -
means that attenuation in downlink 1 and 2 is 10 dB, chain 3 and chain 4 is not in-
stalled.

8.7 ATU – Attenuation Uplink

This attribute is used to read and configure attenuation/gain settings in the uplink
path.
This attribute is used to read and configure the attenuation/gain in the uplink
paths. Attenuation configures how much the chain should be degraded from max-
imum gain / performance.

SET ATU K X [L Y] [M Z] [N W]
K is the chain selector, and X is the attenuation in uplink chain K. Optionally attenu-
ation in chain L, M, N can be set in the same command.
The chain selector from 1 to 4, and the attenuation is settable in 1 dB steps from 0
to 30 dB.
Example:
SET ATD 2 7
sets attenuation in downlink chain 2 to 7 dB.
Example:
SET ATD 2 11 3 11
sets attenuation in downlink chains 2 and 3 to 11 dB.

GET ATD

1 X 2 Y
X is attenuation in chain one downlink, Y attenuation in downlink 2. If a chain is not

communicating a dash '-' may be returned indicating the error.

1 X 2 Y 3 Z 4 W
X is attenuation in chain one downlink, Y attenuation in downlink 2, Z attenuation in

downlink 3 and W in downlink 4. If chain is not responding, a '-' (dash) is replied.
Example:
GET ATD
Reply:
1 10 2 10 3 -8 4 -
means that attenuation in downlink 1 and 2 is 10 dB, chain 3 and chain 4 is not in-
stalled in this example.
8.8 CHA – Channel configuration

This attribute sets the channel configuration of the channel selective repeater.
Attribute type: Read and Write.

This attribute is used to control the operating frequency of the amplifiers in the re-
peater. The attribute takes standard channel numbers for the system involved. For
an EDGE-GSM type repeater this is the ARFCN as defined by the channel lists for
GSM-P GSM-R and E-GSM bands as well as GSM 850, DCS 1800 and PCS 1900 de-
pending on what band the repeater is produced for.
For the WCDMA repeaters the channel number is determined using the following
formula:
Ch= f c⋅5
Channel number is the centre frequency of the downlink of the carrier wave in MHz
multiplied by 5. Channels are divided in steps of 200 kHz just as in GSM.
Note!
√ For EDGE-GSM no channels in LNK or CHA attributes should be closer than

600 kHz from each other. This may cause interference and serious degradation of
the signal quality as well as causing alarms in the repeater. 600 kHz channel
spacing corresponds to 3 channels of separation or 2 guard channels.
Example: If you are using channel 10 then you may not use channels 8 or 9 and
11 or 12 for any other frequency in this repeater.
√ For WCDMA repeaters channels in use should be spaced a minimum of 4.8 MHz
from each other to avoid intra-channel interference in the repeater.
√ In WCDMA repeaters when you change the channel number both uplink and
downlink frequencies are affected as you would normally expect.
√ If you wish to change them separately which is a feature that WCDMA system
must allow, then you need to check the attributes CHD and CHU for setting down-
link and uplink channel numbers separately, or alternatively, you can use DUS to
modify the duplex spacing between uplink and downlink.
√ If changes to this parameter is done in a remote repeater that is using its own
signal to provide coverage for the modem it is possible that the call is dropped.
Usually the call can be re-established just by dialling in to the repeater again but
some caution is advised when changing channel frequencies remotely.
√ If the repeater is a frequency translating repeater, CSFT type, and you are doing
remote reconfiguration of channels, please use the CLN attribute instead. This
will set all chains in the repeater with new serving channel and link channel
numbers in one command. This is to prevent the repeater modem from losing
connection with the network after having changed only one set of
parameters.then change the frequencies in the following order:
Format on setting channel:

SET CHA X Y [ J K ] [ L M ] [ N O ]
Where
X Chain number 1-4.
Y Channel number for chain X.
J Chain number 1-4.

X Chain number 1-4.

K Channel number for chain J.
L Chain number 1-4.
M Channel number for chain L.
N Chain number 1-4.
O Channel number for chain N.
Allowed channel numbers depends on the band configuration of the repeater.
Example (EDGE-GSM type repeater):

SET CHA 1 32 2 48
Sets the channel in chain 1 to 32 and in chain 2 to 48
Example (WCDMA type repeater):

SET CHA 1 10500 2 12000
Sets the downlink channel in chain 1 to 10620 and in chain 2 to 10570. Assuming
the normal duplex distance of 950 channels the corresponding uplink channels will
be set to 9670 and 9620
Format on getting attribute:

GET CHA
Format on reply:
1 J 2 [ K 3 L 4 M ]
Where
J is the channel number in the first chain
K is the channel number in the second chain
L is the channel number in the third chain if installed
M is the channel number in the fourth chain if installed
Reply for 2 carrier repeater:
1 32 2 68
Meaning that the channel number in chain 1 is set to 32 and in chain 2 to 68.
Reply for 4 carrier repeater:

1 32 2 68 3 48 4 120
Meaning that channel number in chain 1 is set to 32, chain 2 to 68, chain 3 to 48
and chain 4 to 120.
Reply from WCDMA type repeater:

1 10620 2 10570
Meaning that the downlink channel number in chain 1 is 10620 and in chain 2 is
10570. Uplink channel numbers can be calculated by subtracting the duplex
distance which by default is 950 channels.
8.9 CHD – Channel Configuration Downlink

Used to set repeated channel independently from the uplink in WCDMA repeaters.

This attribute is used to configure and determine the repeated channels in the
downlink path in WCDMA repeaters.
Note!
√ This attribute sets the downlink channel independently from the uplink channel.
To set the downlink channel and uplink channel simultaneously using configured
duplex spacing, please refer to attribute CHA. To set uplink channel separately,
refer to attribute CHU. To modify the duplex spacing (and at the same time up-
link channel), please refer to attribute DUS.
√ In EDGE-GSM repeaters this attribute will return an error if used.
Format on setting channel:

SET CHD K X [L Y] [M Z] [N W]
K is the chain selector

X is the repeater channel in chain K downlink
L is the chain selector (used when setting 2 chains at the same time)
Y is the repeated channel in chain L downlink
M is the chain selector (used when setting 3 chains at the same time in a 4
carrier repeater)
Z is the repeated channel in chain M downlink
N is the chain selector (used when setting 4 chains at the same time in a 4
carrier repeater)
W is the repeated channel in chain N downlink
Channel limits can be determined by using the attribute CHL to find out the lowest
and highest possible channel numbers for this repeater.
Example:
SET CHD 2 10620
Sets downlink channel in chain two to 10620.
Example:
SET CHD 1 10600 3 10850
Sets downlink channel one to 10600 and 2 to 10850.
Format on getting parameters in 2 channel repeaters:

GET CHD
Replies:
1 X 2 Y
X is downlink channel 1, Y is downlink channel 2.
Example:
GET CHD
Reply:
1 10747 2 10611

means that downlink channel in chain 1 is 10747 and chain 2 is set to 10611.
Format on getting parameters in 4-channel repeaters:

GET CHD
Replies:
1 X 2 Y 3 Z 4 W
X-W is downlink channel 1-4.
Example:
GET CHD
Reply:
1 10610 2 10650 3 10700 4 10750
means that downlink channel in chain 1 is 10610, chain 2 is set to 10650, 3 is set
to 10700 and downlink channel four is set to 10750.
8.10 CHL – Channel configuration limits

Displays the possible channel range the repeater can work on.
Attribute type: Read only.
This attribute work slightly different in band shifting repeaters compared to non-
band shifting repeaters due to the fact that band shifting repeaters have 2 ranges
of channel numbers to use.
Note!
√ For some bands the lowest possible channel number, also known as the Absolute
Radio Frequency Channel Number or ARFCN can actually be a higher number
than the highest possible frequency. This is true for the E-GSM band for ex-
ample.
√ For WCDMA repeaters things are a little different because channels are calcu-
lated in a different way. The channel number here is the frequency in MHz multi-
plied by a factor 5. It is also possible in WCDMA to change the duplex distance,
wherefore the uplink and downlinks will have different channel numbers. There-
fore this attribute works differently in WCDMA repeaters, see below.
Format on Non-Band Shifting EDGE-GSM Repeaters:

X Y
X is the lowest possible frequency's channel number

Y is the highest possible frequency's channel number
Example:
GET CHL
Reply:
1 124

meaning that the lowest possible frequency has channel number 1 and the highest
possible frequency has channel number 124. This is the normal setting for the
P-GSM band.
Format on Band-Shifting EDGE-GSM Repeaters:

X Y Z W
X is the lowest possible frequency's service channel number

Y is the highest possible frequency's service channel number
Z is the lowest possible frequency's link channel number
W is the highest possible frequency's link channel number
Example:
GET CHL
Reply:
1 124 740 810
meaning that for the service channels (the repeated channels from the base sta-
tion) we have channel 1 as the lowest and channel 124 for the highest useable fre-
quency in this repeater. For the link we have channel 740 for the lowest frequency
in the link band (DCS 1800 band) and 810 for the highest frequency this repeater
can use on the link.
Format on WCDMA repeaters

A B X Y
where
A Lowest channel in the uplink band

B Highest channel in the uplink band
X Lowest channel in the downlink band
Y Highest channel in the downlink band
Example:
GET CHL
Reply:
9650 9850 10600 10800
meaning that the uplink band ranges from channel numbers 9650 to 9850 and the
downlink band ranges from channel numbers 10600 to 10800.
8.11 CLN – Serving Channel and Link Channel Configuration

Sets both the serving channels and link channels in the same command.
This command have similar effects to sending CHA and LNK commands in
succession to the repeater. During certain circumstances however it is a good idea
to change both link channel settings and serving channel settings at the same time.

This is especially true when reconfiguring the network for new frequencies because
when doing a change like this in a remote repeater it is possible that the repeater
modem loses connection with the network temporarily and thus the call is dropped.
To avoid this problem the attribute CLN is used instead of CHA/LNK attributes.
Note!
√ This command is only relevant for frequency translating repeaters (CSFT type)
since other models do not employ link channels. Using this command on a non-
translating repeater returns an error.
Format on setting attribute:

SET CLN <N1> <C1> <L1> <N2> <C2> <L1> ...
where N1 is the first chain to change frequency on, C1 is the serving channel
number in chain N1 and L1 is the link channel number in chain N1. N2 is the second
chain to change frequency on, C2 is the new channel number for chain N2 and L2 is
the new link channel number for chain N2.
The chain specification (N1, N2 ...) can be any chain and in any order. It is thus
possible to input only the chains that should be changed and in whatever order is
convenient.
Example:
SET CLN 1 64 32 2 108 22
which in a GSM900 type repeater will change the frequencies of the repeater in
chain 1 to serving channel 64 with a link on channel 32, the second chain will be set
to serving channel 108 with the link on channel 22.
This command is the same as sending the following two commands:

SET CHA 1 64 2 108
SET LNK 1 32 2 22
Example:
SET CLN 1 64 32 4 38 44
which in a GSM900 type repeater will change the frequencies of the repeater in
chain 1 to serving channel 64 with a link on channel 32, chain number 4 will be set
to serving channel 108 with the link on channel 22.
This will be equivalent to sending the following commands:

SET CHA 1 64 4 38
SET LNK 1 32 4 44
Example:
Assuming we have a repeater with the following channel settings:
Chain 1 Chain 2
Serving channel Link Channel Serving Channel Link Channel
32 68 108 22
Under certain circumstances it can be valuable to swith both chains around, for
example if there is an alarm in the repeater it could be checked to see if the alarm
relates to the signal or the hardware.
SET CLN 1 108 22 2 32 68

would then in one single command produce these settings with a minimum of
downtime when the LIMPA change frequencies inside the repeater:
Chain 1 Chain 2
Serving channel Link Channel Serving Channel Link Channel
108 22 32 68
Format on getting parameter 2 carrier repeater:

1 X L 2 Y M
where
X is chain 1 serving channel number

L is chain 1 link channel number
Y is chain 2 serving channel number
M is chain 2 link channel number
Example:
GET CLN
Reply:
1 32 68 2 19 108
meaning that in chain 1 the serving channel is 32 and the link channel is 68 while in
the second chain the serving channel is 19 and the link is on 108.
Format on getting parameter 4 carrier repeater:

1 X L 2 Y M 3 Z N 4 W O
where
X is chain 1 serving channel number

L is chain 1 link channel number
Y is chain 2 serving channel number
M is chain 2 link channel number
Z is chain 3 serving channel number
N is chain 3 link channel number
W is chain 4 serving channel number
O is chain 4 link channel number
Example:
GET CLN
Reply:
1 32 68 2 19 108 3 2 18 4 120 55
meaning that in chain 1 the serving channel is 32 and the link channel is 68 while in
the second chain the serving channel is 19 and the link is on 108, for the 3rd chain
the serving channel is 2 and the link is on 18 and for the 4th chain the serving
channel is 120 and link is on 55.

8.12 CRC – Status of EEPROM checksum

Displays status of the EEPROM CRC in active devices.
Usage
Each active device stores all settings and configurations in its own EEPROM memory
so that an immediate startup can be performed after power outage, and so that
radio coverage works as intended even if controller malfunctions.
On regular intervals the controller requests a checksum calculation of the EEPROM
in the active devices.
If a failure is detected, the CRC error is flagged in the EEPROM of the active device
so that alarm status is known even after a power failure. This status is checked in
EEPROM of the Radio Units, FiberOptic Slaves and Communications Multiplexer.
CRC alarms normally indicates a failing EEPROM and that module should be
replaced.
This attribute replies with CRC status of the polled devices.
Note!
√ Only the latest revision of the optical module in the fibre-fed repeater, CSF type
supports CRC. To know if the repeater is equipped with this module the attribute
FOC – Fiberoptic Capabilities can be queried. See this attribute for more
information.
Format:
<FO1><FO2><FO3><FO4><COMMUX>
where
FO1 – FO4, COMMUX is the status of each optical module CRC in the repeater and
the communications multiplexer.
Value can be:
Example:
GET CRC
Reply:
1----
meaning that a CRC error has been detected in the optical module and it should be
replaced.
8.13 IHU – Installed Hardware Units

Contains information on what hardware units are installed in the system.
Usage:

This attribute replies with all active devices installed in the system.
Format:
<PSUP1><PSUP2><LIMPA1UL><LIMPA2UL><LIMPA1DL><LIMPA2DL><REFGEN><FO1><FO2><FO3><FO4>
<COMMUX><FDM-S1><FDM-S2>
where
PSUP1 Master power supply. All repeaters have this.
PSUP2 Slave power supply. Only mounted in 4 carrier versions of the repeater.
LIMPA1UL–LIMPA2UL 2 carrier repeaters have 2 LIMPA units, one uplink one downlink.
LIMPA1DL-LIMPA2DL 4 carrier repeaters have 2 UL LIMPA units and 2 DL LIMPA units.
REFGEN Reference generator board in the repeater.
FO1 – FO4 Fibre-optical units. In GSM-UMTS repeaters of the CSF type there is nomally
just one optical module, FO1. FO2-FO4 are included for future expansion.
FDM-S1 Filtering and distribution module server 1. This unit is present in all GSM and
UMTS repeaters including fibre fed units.
FDM-S2 Filtering and distribution server 2. This unit is only present in ER type
repeaters with external combination of the signals.
COMMUX Communication Multiplexer board. Normally not used in this repeater but
provided for future expansion.
The values returned by the attribute can be:
0 means module is not installed.

1 means module is installed.
Example 2 channel non-fiberoptic repeater:

GET IHU
Reply:
101010100000010
meaning Master Power Supply is installed but no slave PSUP. Reference generator,
LIMPA1 and LIMPA2 are installed, one donor FDM and two serving FDM. This would
be the expected result quering i.e. a CSFT922-ER repeater.
8.14 IOD – Input overload downlink

Reports the status of the input overload alarm in the downlink path of the repeater.
Attribute type: Read-Only.
The input circuitry contains a a function to detect if there is a too strong input
signal in the downlink that may cause the amplifier to not work in an optimum way.
The measurement is always performed in downlink 1 chain but it is a wide band

detector and the channel settings of the repeater does not affect this measurement.
The alarm is triggered around the level of -25 to -20 dBm when the input signal is
considered to be so strong that it is possible that blocking and other effects may
happen on the receiver side of the amplifier chain.
This attribute is mainly used to see if there are other equipment in the repeater
area interfering with the repeater. Other such equipment may be broadcast radio

and TV transmitters or other repeaters and base stations if they are in the same
band as the repeater.
Format:
X
where X is 1 indicating input overload error or 0 indicating state OK.
Example:
GET IOD
Reply:
1
Meaning that a radio source is injecting a signal strong enough to cause

degradation of the repeater performance.
8.15 IOU – Input overload uplink

Reports the status of the input overload alarm in the uplink path of the repeater.
Attribute type: Read-Only.
The input circuitry contains a a function to detect if there is a too strong input
signal in the uplink that may cause the amplifier to not work in an optimum way.
The measurement is always performed in uplink 1 chain but it is a wide band

detector and the channel settings of the repeater does not affect this measurement.
The alarm is triggered around the level of -25 to -20 dBm when the input signal is
considered to be so strong that it is possible that blocking and other effects may
happen on the receiver side of the amplifier chain.
This attribute is mainly used to see if there are other equipment in the repeater
area interfering with the repeater. In the uplink the interference generally comes
from mobile equipment very close to the repeater or possibly broadcast stations for
radio and TV signals that are very close.
Format:
X
where X is 1 indicating input overload error or 0 indicating state OK.
Example:
GET IOU
Reply:
1
Meaning that a radio source is injecting a signal strong enough to cause

degradation of the repeater performance.
8.16 IPL – Input power level

Reports the input power in both uplink and downlink in the repeater.
Attribute type: Read-Only

Displays a list of the radio chains input power levels. The input power levels in the
last sampled frame. The input powers are sampled continuously and the highest
value each second is presented on an amplifier chain-by-chain basis.
Note!
√ The detector is factory tuned but the precision is over the entire frequency band,
temperature and input level range about ±2 dB. Therefore if you need more
accurate measurements you should not rely on this indicator.
The attribute first reports all uplink chains, then all downlink chains.
Reply format for 2 carrier repeaters

X Y Z W
where
X is the input power in uplink chain 1 measured in dBm.

Y is the input power in uplink chain 2 measured in dBm.
Z is the input power in downlink chain 1 measured in dBm.
W is the input power in downlink chain 2 measured in dBm.
Reply format for 4 carrier repeaters
X Y A B Z W C D
where
X is the input power in uplink chain 1 measured in dBm.
Y is the input power in uplink chain 2 measured in dBm.
A is the input power in uplink chain 3 measured in dBm.
B is the input power in uplink chain 4 measured in dBm.
Z is the input power in downlink chain 1 measured in dBm.
W is the input power in downlink chain 2 measured in dBm.
C is the input power in downlink chain 3 measured in dBm.
D is the input power in downlink chain 4 measured in dBm.
All values are given in dBm with one decimal precision.
If a value is below what the repeater can measure, the value of "-110.0 dBm" is
reported.
Example in a 2 carrier repeater:

GET IPL
Reply:
-110.0 -77.3 -59.1 -110.0
meaning that uplink 1 reports an input level of -110 dBm meaning it can not detect
a signal, uplink 2 has a signal that is -77 dBm, downlink one has an input signal of
-59 dBm and downlink 2 reports no signal (not detectable or very low) on
-110 dBm.
Example in a 4 carrier repeater:

GET IPL
Reply:
-110.0 -82.3 -110.0 -110.0 -45.6 -43.3 -110.0 -110.0
Uplink 1 reports no signal, uplink 2 has input signal of -82.3 dBm, uplink 3 and 4
has no input signal, downlink 1 has a good input signal of -45.6 dBm and downlink
2 reports a similar signal of about -43.3 dBm while downlink 3 and 4 reports no
signal.
This scenario would indicate a BCCH/Pilot Tone signal in chain 1 and a connected
call in progress on chain 2.
8.17 LNK – Link channel

Sets or display the link channels in a frequency translating repeater.
This attribute only applies to frequency shifting repeaters. It is not present in

WCDMA repeaters and conventional EDGE-GSM repeaters. If your repeater
implements this attribute it must be of the CSFT2 repeater type. Repeaters of the
types CSR and CSF does not implement this attribute.
The attribute is used to set the link channel in a frequency translating repeater. The
link channels in a donor and remote repeater should be set to the same channel.
Channel numbers follow the same convention as the CHA attribute does.
Note!
√ For EDGE-GSM no channels in LNK or CHA attributes should be closer than

600 kHz from each other. This may cause interference and serious degradation of
the signal quality as well as causing alarms in the repeater. 600 kHz channel
spacing corresponds to 3 channels of separation or 2 guard channels.
Example: If you are using channel 10 then you may not use channels 8 or 9 and
11 or 12 for any other frequency in this repeater.
√ For WCDMA repeaters channels in use should be spaced a minimum of 4.8 MHz
from each other to avoid intra-channel interference in the repeater.
√ If changes to this parameter is done in a remote repeater that is using its own
signal to provide coverage for the modem it is possible that the call is dropped.
Usually the call can be re-established just by dialling in to the repeater again but
some caution is advised when changing channel frequencies remotely.
√ If the repeater is a frequency translating repeater, CSFT type, and you are doing
remote reconfiguration of channels, please use the CLN attribute instead. This
will set all chains in the repeater with new serving channel and link channel
numbers in one command. This is to prevent the repeater modem from losing
connection with the network after having changed only one set of
parameters.then change the frequencies in the following order:

SET LNK K X [ L Y ] [ M Z ] [ N W ]
where
2 Channel Selective Frequency Translating

K Specifies the chain 1-4.

X Specifies the link channel number for chain K.
L Specifies the chain 1-4.
Y Specifies the link channel number for chain L.
M Specifies the chain 1-4.
X Specifies the link channel number for chain M.
N Specifies the chain 1-4.
W Specifies the link channel number for chain M.
Example:
SET LNK 2 64
Sets the link channel for chain 2 to channel number 64.

SET LNK 1 10 2 26 3 38 4 18
Sets the link channels for chain 1 to 10 and chain 2 to 26, chain 3 to 38 and in
chain 4 to channel 18.
Format on getting parameter:

GET LNK
Reply from 2 carrier repeater:

1 X 2 Y
Reply from 4 carrier repeater:

1 X 2 Y 3 Z 4 W
where
X Is the link channel in in chain 1.
Y Is the link channel in chain 2.
Z is the link channel in chain 3.
W is the link channel in chain 4.
8.18 LVD – Peak power output level downlink

Get or set the peak power limiting feature in the downlink.
The LVD attribute can be used to change or check the peak power limit of the re-
peater downlink output power. When the amplifier chain is turned off (set to
-100 dBm output power) the service will be interrupted.
Note!
√ When using this command remotely with a repeater it is possible that you may
lose connection if you are using a wireless modem connection to the repeater. In
some case the modem requires the output signal from the repeater to get net-
work and if the output power is lowered substantially or turned off it is possible
that it may prove difficult to dial back in to the repeater.

SET LVD A X [ B Y ] [ C Z ] [ D W ]

where
A is the chain number 1-4.

X is the peak power limit for chain A.
B is the chain number 1-4.
Y is the peak power limit for chain B.
C is the chain number 1-4.
Z is the peak power limit for chain C.
D is the chain number 1-4.
W is the peak power limit for chain D.
Depending on repeater model there are various levels that are allowed:
EDGE-GSM Repeater types

Model High Medium Low Off
2-carrier conventional EDGE-GSM 37 34 31 -100
2-carrier frequency translating EDGE-GSM ER 43 40 37 -100
2-carrier frequency translating EDGE-GSM IR 40 37 34 -100
2-carrier frequency translating EDGE-GSM SD 37 34 31 -100
2-carrier frequency translating EDGE-GSM DD 37 34 31 -100
4-carrier frequency translating EDGE-GSM ER 40 37 34 -100
4-carrier frequency translating EDGE-GSM IR 37 34 31 -100
4-carrier frequency translating EDGE-GSM SD 34 31 28 -100
4-carrier frequency translating EDGE-GSM DD 34 31 28 -100
2-carrier fibre fed EDGE-GSM 37 34 31 -100
4-carrier fibre fed EDGE-GSM 34 31 28 -100
WCDMA Repeater types
2-carrier conventional WCDMA repeater 33 30 27 -100
2-carrier fibre fed WCDMA repeater 33 30 27 -100
4-carrier fibre fed WCDMA repeater 30 27 24 -100
Output power setting of -100 dBm means that output power is turned off.
Example:
SET LVD 1 33 2 33 3 -100 4 -100
meaning to set chains 1 and 2 for 33 dBm maximum output power in the downlink
while chains 3 and 4 will have their downlinks turned off.
SET LVD 3 43 1 -100
meaning that chain 3 downlink will be set to 43 dBm output power while chain 1
downlink will be turned off.

Format on getting parameters in 2 carrier repeater

1 X 2 Y
where
X is the peak power limit for chain 1.
Y is the peak power limit for chain 2.
Example
GET LVD
Replies:
1 43 2 -100
meaning downlink peak power control is set for 43 dBm in chain 1 but turned off in
chain 2.
Format on getting parameter in 4 carrier repeater

1 X 2 Y 3 Z 4 W
where
Example
GET LVD
Replies:
1 43 2 43 3 43 4 -100
meaning that all chains are set to 43 dBm peak output power except chain 4 which
has been turned off.
8.19 LVU – Peak power output level uplink

Get or set the peak power limiting feature in the uplink.
The LVD attribute can be used to change or check the peak power limit of the re-
peater uplink output power. When the amplifier chain is turned off (set to -100 dBm
output power) the service will be interrupted.
Note!
√ When using this command remotely with a repeater it is possible that you may
lose connection if you are using a wireless modem connection to the repeater. In
some case the modem requires the output signal from the repeater to get net-

work and if the output power is lowered substantially or turned off it is possible
that it may prove difficult to dial back in to the repeater.

SET LVU A X [ B Y ] [ C Z ] [ D W ]
where

Depending on repeater model there are various levels that are allowed:
EDGE-GSM Repeater types

2-carrier frequency translating EDGE-GSM ER, IR 37 34 31 -100
2-carrier frequency translating EDGE-GSM SD -10 -13 -16 -100
2-carrier frequency translating EDGE-GSM DD -7 -10 -13 -100
4-carrier frequency translating EDGE-GSM ER, IR 34 31 28 -100
4-carrier frequency translating EDGE-GSM SD -7 -10 -13 -100
4-carrier frequency translating EDGE-GSM DD -10 -13 -16 -100
3
2-carrier fibre fed EDGE-GSM -1 -4 -7 -100
4-carrier fibre fed EDGE-GSM -4 -7 -10 -100
WCDMA Repeater types
2-carrier fibre fed WCDMA repeater -5 -8 -11 -100
4-carrier fibre fed WCDMA repeater -5 -8 -11 -100
Output power setting of -100 dBm means that output power is turned off.
When configuring a donor type repeater, CSFT -DD or -SD, the uplink peak power
limit is normally set to the lowest value because this protects the base station if
there is a sudden extremely strong signal or interference coming in on the link. The
other two values are used when there are combiners or couplers with a higher
3 This value is not a recommended setting for this repeater type if more than one carrier is being in use! Normal
setting should be -4 dBm for a 2-carrier repeater and -7 dBm for a 4-carrier repeater.

coupling factor than the normally used 30 dB coupler between the donor and the
base station transceiver.
Setting the peak power limit to -16 dBm in the uplink means that the maximum in-
put to the BTS can ever be
−16 dBm−30 dBcoupler =−46 dBm

Since most base stations can handle signal levels up to around -40 dBm gracefully
it is not recommended to use a higher peak power limit in the uplink on a donor.
Example:
SET LVU 1 33 2 33 3 -100 4 -100
meaning to set chains 1 and 2 for 33 dBm maximum output power in the uplink
while chains 3 and 4 will have their uplinks turned off.
SET LVD 3 37 1 -100
meaning that chain 3 uplink will be set to 37 dBm output power while chain 1 uplink
will be turned off.
Format on getting parameters in 2 carrier repeater

1 X 2 Y
where
X is the peak power limit for chain 1.
Y is the peak power limit for chain 2.
Example
GET LVU
Replies:
1 43 2 -100
meaning downlink peak power control is set for 43 dBm in chain 1 but turned off in
chain 2.
Format on getting parameter in 4 carrier repeater

1 X 2 Y 3 Z 4 W
where
Example
GET LVD
Replies:

1 37 2 37 3 37 4 -100
meaning that all chains are set to 37 dBm peak output power except chain 4 which
has been turned off.
8.20 NCH – Number of channels

Number of carriers in the repeater.
This attribute responds with the number of carriers being employed in the repeater.
Not all of them has to be used, but the number reported is the maximum that this
hardware are able to use at any time.
Format on get parameter:

N
where N is the number of carriers in the repeater that can be utilized simultan-
eously.
Example
GET NCH
Reply:
4
meaning this is a 4-carrier repeater.
8.21 OPL – Output power levels

Displays the maximum power of the last measurement.
This attribute displays the last maximum output power in the last measurement
frame. The output power is continuously sampled and the highest value each
second is saved in the controller on a chain by chain basis.
Reply format in 2 carrier repeaters

X Y K L
where the value is output levels in dBm with one decimal precision.
X is the output power in uplink chain 1.
Y is the output power in uplink chain 2.
K is the output power in downlink chain 1.
L is the output power in downlink chain 2.
Example:
GET OPL
Reply
<12.0 26.3 33.3 33.1

This means there is no output signal in the uplink 1 chain but there is traffic in up-
link chain 2, a BCCH/Pilot Tone signal most likely in chain 1 downlink and traffic in
chain 2 downlink also.
Reply format in 4 carrier repeaters

X Y Z W K L M N
where the value is output levels in dBm with one decimal precision.
Example:
GET OPL
Reply:
<12.0 26.3 <12 <12 33.3 33.6 <12 <12
This means there is an uplink signal in chain 2 with output power of 26.3 dBm,
there is a downlink signal in chain 1 of 33.3 dBm and another signal in chain 2 with
output power 33.6 dBm.
Chains showing <(number) means that the measured output power is lower than
the lowest detectable power. In the above12 (or similar) means that the measured
output power is lower than the lowest detectable power. In this example the lowest
limit is 12 dBm and any signal lower than this will be represented as <12.0.
Note!
√ See the attribute RFP to determine the lowest detectable levels and other RF
parameters for a particular model of repeater.
8.22 PDC – Power downlink level configuration

This attribute is used to configure how the power level in the BCCH or Pilot Tone
channel is measured.
Attribute type: Read and Write.
This attribute is used to configure or get information about the way the repeater
performs BCCH or Pilot Tone (PT) detection and alarms.
By default all repeaters measure the BCCH / PT only in chain one. By changing this
attribute the BCCH / PT can be measured on other channels as well, or not at all.
When BCCH / PT is measure on more than one chain, the repeater will always make
sure that at least one of the chains have an output power above threshold con-
figured with the ALA PDL attribute.
This attribute can be used to maintaint BCCH/PT monitoring in network where BTS
or Node B uses the second TRX as a fall back option if something happens to the
TRX which is normally the BCCH/PT. Furthermore the attribute can be used to con-
figure the system to monitor more than one chain if the repeater is fed from more
than one BTS/Node B, for example in the case where a 4 carrier repeater is used it
would be possible to repeat two different 2-carrier cells in the same repeater.
Measurement of the BCCH/PT is done to ensure that there is a repeatable signal in

the system and that the base station is working properly including the repeater's
own amplifier system. If the output power from the repeater in the configured

chains in the downlink drops below the threshold set forth in the ALA PDL attribute
an alarm is given.
Note!
√ By changing this attribute all PDL alarm sources will be reset. If a PDL alarm was
detected and end of alarm will be generated and if BCCH/PT still is too low a new
PDL alarm after the configured time.
√ Setting required on a non installed/available channel will have no effect.
Format in 2-carrier repeaters

XY
where X represents chain 1 and Y represents chain 2.
Possible values of X and Y:
S Skip this chain will not be monitored by the repeater for a loss of
BCCH/PT.
R Required this chain required a signal in the downlink at all times that is higher
or equal to the ALA PDL threshold.
E Either this is used when the BCCH/PT may move to a second chain after a
failure at the BTS/Node B. In this case two chains are configured as
either and the repeater will then monitor the first chain for a BCCH/-
PT first. If one is found then status is OK. If there is no signal found
in the first chain then the next chain configured as either will be
monitored. Only if all chains configured as either are missing an out-
put level higher than ALA PDL threshold will the alarm be generated.
Example:
GET PDC
Reply:
RS
meaning that the first chain is set to contain BCCH/PT signal and will alarm if there
is a loss of signal. The second chain will not be checked.
Example:
GET PDC
Reply:
EE
meaning that the repeater will generate an OK message if there is a signal in either
chain 1 or chain 2. An alarm will be generated if none of the chains contains a
BCCH/PT signal.
Format in 4-carrier repeaters:

XYZW
where X represents chain 1, Y represents chain 2, Z represents chain 3 and W rep-

resents chain 4.
The values are as described in the 2-carrier case.
Example:

GET PDC
Reply:
RSSS
meaning the repeater will look only in chain 1 for the presence of a BCCH/PT carri-
er.
Example:
GET PDC
Reply:
RSRS
meaning the repeater will monitor both chains 1 and 3 for the presence of a BCCH/
PT carrier and give alarm if any one of these disappears.
Example:
GET PDC
Reply:
EEEE
meaning that the repeater will monitor all 4 chains for the presence of a BCCH/PT
carrier in any one of them. The alarm will only be generated if none of the four
chains contains a BCCH/PT carrier above the threshold set forth in the attribute ALA
PDL.
Format for setting power downlink monitoring configuration

SET PDC RSSS
will set the repeater to monitor only the first chain out of four for a BCCH/PT signal
in the downlink. Existing alarms will be reset and end of alarms transmitted if the
repeater was in a state of alarm before changing the attribute.
8.23 PDL – Status of power downlink level

Status of BCCH/Pilot Tone output power measurement in the downlink chains.
Displays the status of the BCCH/Pilot Tone power measurement in the downlink
chains of the repeater.
Format in 2 carrier repeaters

XY
where X represents the status in downlink 1 and Y represents the status in down-
link 2.
The status can have the following values
1 means the output power is lower than the configured threshold that can be
set using the attribute ALA PDL.
0 means that the output power is normal as configured.
- means there is no communication with the LIMPA unit or measurement is not
configured.

Example:
GET PDL
Reply:
00
meaning power downlink BCCH/Pilot Tone is OK in both chains in the repeater.
Format in 4 carrier repeaters

XYZW
where X represents the status in downlink 1, Y is the status in downlink 2, Z is the

status in downlink 3, W is the status in downlink 4.
Example:
GET PDL
Reply:
0-1-
meaning that status is okay in chain 1, not measured in chain 2 and 4, while an er-
ror is being reported in chain 3.
Associated Attributes
There are two other attributes associated with this command. The first is the BCCH/
Pilot Tone alarm configuration attribute PDC. This attribute can be set for each indi-
vidual chain to one of three functions:
2 carrier system
SET PDC RS
This would in a 2 carrier repeater configure the BCCH/Pilot Tone alarm in a way that
a signal is required in chain 1 but chain 2 will not be checked. A third option is to
set both to "E" which means that either chain should contain a BCCH/Pilot Tone sig-
nal.
4 carrier system
SET PDC EESS
This would mean that the repeater is looking for a signal in either chain 1 and 2 but
does not care about chain 3 and 4.
Valid settings for PDC attribute
R Required. This chain should have a BCCH or pilot tone at all times. Should the
signal disappear then the alarm will be triggered.
S Skip – this means that the repeater will not check this chain for the presence
of a BCCH or pilot tone signal.
E Either – this is used when base stations may swap BCCH or pilot tone to a
different channel. If two chains are set to "E" then the repeater will first check
the first chain for a presence of a BCCH or pilot tone. If it is found then
everything is OK. If no signal is found then it will check the next chain set to
"E". If all chains set to E does not have a BCCH or pilot tone signal then the
alarm will be generated.
The second attribute associated with the BCCH / pilot tone detection is the ALA PDL
attribute. This attribute can be used to set the level of which a signal is considered

to be present. Normally this level is set up so that a drop of the BCCH in an EDGE-
GSM system with say 6-10 dB would trigger it immediately.
Note!
√ In a WCDMA system more consideration is needed because of the downlink

power regulation that goes on at the base station. Normally a pilot tone only is
8-12 dB below the maximum output power of the base station. When traffic
moves in to the cell the Node B will increase the output power depending on the
volume of traffic. Therefore in order to use this feature in WCDMA repeaters it is
recommended to set it at least 15 dB lower than the normal output level of the
repeater.
√ Refer to the attributes IPL and OPL for input- and output power measurements
when setting this.
8.24 RFP – RF Parameters

Shows various RF parameters of this particular repeater.
The attribute shows several important RF parameters in the repeater that has to do
with amplification and ranges of the meters implemented.
Format:
<Maximum Gain UL> <Maximum Gain DL> <PreAmp UL> <PreAmp DL> <Loss after PA UL> <Loss
after PA DL> <LDO UL> <LDO DL>
Maximum Gain UL This is the maximum amplification in the downlink given

in dB. It is the same amplification as you expect when the
repeater attenuation in the uplink is set to 0 dB.
Maximum Gain DL This is the maximum amplification in the downlink given
in dB. It is the same amplification as you expect when the
repeater attenuation in the uplink is set to 0 dB.
PreAmp UL This is the gain in the repeater from the input port of the
repeater to the connector of the LIMPA module. This gain
contains the Low Noise Amplifier gain minus losses.
PreAmp DL This is the gain in the repeater from the input port of the
repeater to the connector of the LIMPA module. This gain
contains the Low Noise Amplifier gain minus losses.
Loss after PA UL This is the loss in the path from the output of the LIMPA
module to the repeater antenna port.
Loss after PA DL This is the loss in the path from the output of the LIMPA
module to the repeater antenna port.
LDO UL This is the lowest detectable signal level in the uplink.
Specifically this sets a range for the uplink power meter
indicators. Any output power lowe than this value will be
shown as being less than this value. If the LDO value is
12 dBm then a signal of 10 dBm will be shown as <12.
LDO DL This is the lowest detectable signal level in the downlink.

Specifically this sets a range for the uplink power meter

indicators. Any output power lowe than this value will be
shown as being less than this value. If the LDO value is
12 dBm then a signal of 10 dBm will be shown as <12.
Example:
GET RFP
Reply:
45.0 45.0 17.1 -25.1 2.1 4.9 -15.1 17.2
meaning that maximum gain in the repeater both uplink and downlink is 45 dB and
the gain before the RSSI is 17.1 dB while gain in the downlink is -25.1 dB (an at-
tenuationof 25.1 dB). Loss after the PA in uplink is 2.1 dB and in downlink 4.9 dB.
The lowest detectable output power in the uplink is -15.1 dBm and in the downlink
17.2 dBm.
8.25 SZD – Status of synthesizer downlink

Status of synthesizers in downlink chains.
This attribute returns the status of the synthesizer in the downlink path of the re-
peater. Each path contains two synthesizers one for mixing the original radio fre-
quent signal down to the intermediate frequency used in the channelizer and anoth-
er synthesizer to mix the intermediate frequency back to the original frequency
again. The reply of this attribute depends on the number of installed carriers /
LIMPA units in the repeater.
The first synthesizer is also called the input synthesizer while the second is called
the output synthesizer.
There is a corresponding attribute, SZU for the uplink synthesizers.
A failing synthesizer most likely results in there being no output power at all from
the repeater and that the coverage from the repeater may be severely reduced and
in most cases non-existent. This indicated a serious problem with the LIMPA module
in the repeater.

XYZW
where
X status of input synthesizer downlink chain 1

Y status of output synthesizer downlink chain 1
Z status of input synthesizer downlink chain 2
W status of output synthesizer downlink chain 2
Possible values are
0 status is OK, synthesizer operates as normal.

1 status is ERROR, synthesizer is NOT operating as normal.

- No communication with LIMPA unit or unable to determine state of
(dash) synthesizer.
Example
GET SZD
Reply
0010
meaning that all synthesizers in the downlink are OK with the exception of the input
synthesizer in chain 2 which reports an error.

XYZWKLMN
where
X status of input synthesizer downlink chain 1

Y status of output synthesizer downlink chain 1
Z status of input synthesizer downlink chain 2
W status of output synthesizer downlink chain 2
K status of input synthesizer downlink chain 3
L status of output synthesizer downlink chain 3
M status of input synthesizer downlink chain 4
N status of output synthesizer downlink chain 4
Example
GET SZD
Reply
00000000
meaning that all synthesizers are okay.
8.26 SZU – Status of synthesizer uplink

Status of synthesizers in uplink chains.
This attribute returns the status of the synthesizer in the uplink path of the repeat-
er. Each path contains two synthesizers one for mixing the original radio frequent
signal down to the intermediate frequency used in the channelizer and another syn-
thesizer to mix the intermediate frequency back to the original frequency again.
The reply of this attribute depends on the number of installed carriers / LIMPA units
in the repeater.
The first synthesizer is also called the input synthesizer while the second is called
the output synthesizer.
There is a corresponding attribute, SZD for the downlink synthesizers.

A failing synthesizer most likely results in there being no output power at all from
the repeater and that the coverage from the repeater may be severely reduced and
in most cases non-existent. This indicated a serious problem with the LIMPA module
in the repeater.

XYZW
where
X status of input synthesizer uplink chain 1

Y status of output synthesizer uplink chain 1
Z status of input synthesizer uplink chain 2
W status of output synthesizer uplink chain 2
Possible values are
0 status is OK, synthesizer operates as normal.

1 status is ERROR, synthesizer is NOT operating as normal.
- No communication with LIMPA unit or unable to determine state of
(dash) synthesizer.
Example
GET SZU
Reply
0010
meaning that all synthesizers in the uplink are OK with the exception of the input
synthesizer in chain 2 which reports and error.

XYZWKLMN
where
X status of input synthesizer uplink chain 1

Y status of output synthesizer uplink chain 1
Z status of input synthesizer uplink chain 2
W status of output synthesizer uplink chain 2
K status of input synthesizer uplink chain 3
L status of output synthesizer uplink chain 3
M status of input synthesizer uplink chain 4
N status of output synthesizer uplink chain 4
Example
GET SZU
Reply
00000000

meaning that all synthesizers are okay.
8.27 VLD – Valid peak limiting levels downlink

Returns the valid limits that can be used with the LVD attribute.
This attribute returns a list of valid peak power limiting values in the downlink of
the repeater. These values can be used with the LVD attribute to set the Automatic
Level Control (ALC) feature in the repeater, limiting the maximum peak output
power from the unit.
Format:
[Value 1] [Value 2] ... [Value N]
where the different values are expressed in dBm. A value of -100 is the same as
turning the output power OFF.
Example:
GET VLD
Reply:
-100 31 34 37
meaning that the different peak output power levels in the downlink can be set to -
100 dBm meaning that the output power is turned off, 31 dBm, 34 dBm or 37 dBm.
See the attribute LVD for more information on setting the downlink peak power lim-
its in the repeater.
8.28 VLU – Valid peak limiting levels uplink

Returns the valid limits that can be used with the LVU attribute.
This attribute returns a list of valid peak power limiting values in the uplink of the
repeater. These values can be used with the LVU attribute to set the Automatic
Level Control (ALC) feature in the repeater, limiting the maximum peak output
power from the unit.
Format:
[Value 1] [Value 2] ... [Value N]
where the different values are expressed in dBm. A value of -100 is the same as
turning the output power OFF.
Example:
GET VLU
Reply:
-100 31 34 37
meaning that the different peak output power levels in the uplink can be set to
-100 dBm meaning that the output power is turned off, 31 dBm, 34 dBm or
37 dBm.
See the attribute LVU for more information on setting the uplink peak power limits
in the repeater.

8.29 WRD – Return Loss Downlink alarm

This attribute responds with the alarm status for the return loss measurements of
the FDM:s in the repeater.
Usage
The WRD attribute reports the status of the reflected power alarms for each FDM in
the system capable of measuring return loss.
Format:
X[Y]
Where
X is the status of downlink server port (all repeaters).
Y is the status of downlink server 2 port (ER type repeaters).
0 means the status is OK.
1 means the status is ALARM.
- Means there is a communications error with the module.
Example:
GET WRD
Reply:
1
Meaning there is a return loss alarm in the downlink. The ER type repeaters
responds with an additional number:
10
Meaning there is a return loss alarm in DL 1 but not in DL 2.
Note!
√ The FDC attribute can be used to find out the number of downlink FDMs in the
system.
8.30 WRL – Return Loss Measurement

This replies with the current return loss measurement in dB.
Usage
The repeater constantly monitors the reflected power level on the downlink antenna
ports. If reflected power level is too high, it might indicate that connector is not
properly tightened or it might be the cause of a broken server antenna. This

attribute returns the currently measured value of the calculated return loss level,
which is defined as the difference between the forward and reflected power.
The attribute returns one or two numbers depending on the configuration of the
actual hardware in the repeater.
Format:
X [ Y ]
Where
X is the return loss value of the first active FDM with one decimal resolution.
Y is the return loss value of the optional active FDM with one decimal resolution.
If the return loss can not be measured or there is no communication with the
alarm, a dash “-“ is reported instead of a value.
If the forward power is too low to perform VSWR measurements at all then the
value is reported as “<“ instead.
Example:
GET WRL
Reply:
12.3 14.2
Meaning that active FDM 1 reports a return loss figure of 12.3 dB and active FDM 2
reports a return loss figure of 14.2 dB.
< 14.2
Meaning that the first active FDM has a too low forward output power to be able to
measure the VSWR but the second reports 14.2 dB in return loss.
12.3 -
Meaning that the first active FDM reports 12.3 dB return loss and the second may
not be answering, have a COM alarm or other fault.

9 MISCELLANEOUS ATTRIBUTES
This chapter contains attributes that deals with the following aspects of the
equipment:
● External voltage monitoring
● Internal voltage monitoring
● Communication status between controller and hardware
● Temperature alarms
● Various hardware counters and parameters
9.1 BAT – Status of battery charge

Displays status of the battery charge.
Usage
The repeater is equipped with a battery backup, which feeds controller and the
modem and in some configurations the fiber optic module, with power during a
power failure. This battery backup ensures that the repeater is able to inform the
Avitec Element Manager that the repeater coverage is out.
This attribute replies with the status of the battery charge. A too low battery charge
probably means that the repeater is back from a power failure and that the battery
is not fully charged yet, while a too high battery voltage might indicate that the
battery pack needs replacement.
Current battery level can be read out with attribute PLV, while battery level
configurations are manipulated with attribute ALA BAT.
Format:
<BAT>
where
<BAT> is battery status.
0 if status is OK
1 if status is ERROR
- (dash) if measured data is not available (communications error or improperly
configured system).
Example:
GET BAT
Reply:
1
indicating that battery status is in error.

9.2 COM – Status of Communications with Active Devices

Displays status of communication between controller and active devices in the
repeater.
Usage:
Format:
<PSUP1><PSUP2><LIMPA1UL><LIMPA2UL><LIMPA1DL><LIMPA1DL><RefGen><FO1><FO2><FO3><FO4>
<COMMUX><FDM-S1><FDM-S2>
where
PSUP1 is the communication status of power supply 1, master power supply. This unit
is always installed in all repeaters.
PSUP2 is the communication status of power supply 2 which is used only in 4 carrier
repeaters.
LIMPA1UL-LIMPA2UL is the communication status with LIMPA 1-4.
LIMPA1DL-LIMPA2DL
RefGen is the communication status with the reference generator.
FO1 – FO4 Fibre-optical modules.
COMMUX Communications multiplexer. Normally not used in this kind of repeater but may
be used in the future. A dash is reported if the hardware do not support the
COMMUX.
FDM-S1, FDM-S2 Server FDM and Server2 FDM (only ER type repeaters).
Example for 2 channel CSR repeater:

GET COM
Reply:
0-0-0-0-----0-
meaning all communications is working fine.
Example for 4 channel CSR repeater:

GET COM
Reply:
0000001-----0-
meaning that LIMPA2DL has a problem with the communication.
9.3 FDC – FDM count

Reports the number of uplink passive and active FDM:s and downlink active and
passive FDM units in the repeater.
Usage
The FDC reports the number of uplink FDM units in the system and the number of
downlink FDM units in the system.

Only active FDM units measure VSWR at so this attribute can be used to find out
the format for the return values of the attributes WRL and WRD.
Format:
UP UA DP DA
where:
UP is the number of passive uplink FDM units.
UA is the number of active uplink FDM units.
DP is the number of passive downlink FDM units.
DA is the number of active downlink FDM units.
Example:
GET FDC
Reply:
1 0 0 1
Meaning that there is 1 passive uplink FDM and one active downlink FDM. This
would be the normal reply for an IR type of repeater. A conventional stand-alone off
air repeater would report:
1 0 0 2
Meaning there is one passive uplink FDM and two active downlink FDM units.
The total number of FDM units in the system is given by the following relation:
N FDM =U AU P D AD P

The number of active FDM units, that also reports return loss can be found by the
following relation:
N FDM =U A D A
A
9.4 PLV – Power Supply Levels

Displays levels as measured in power supply(-ies).
Usage
Depending on repeater type, one or more power supplies can be mounted. This
attribute displays a number of voltages and temperatures as measured in the
power supply (-ies).
Levels are displayed for all power supplies configured in the system (number of
power supplies can be read with attribute PSC).
Format:
<PW1:1> .. <PW1:N> <PW2:1> .. <PW2:N> <PW3:1> .. <PW3:N> <PW4:1> <PTM:1> ..
<PTM:N> <BAT:1> <PSL:1>
where
<PW1:1> .. <PW1:N> is the +28.0 V levels with one decimal resolution and a leading +
sign as measured in power supply 1 to power supply N.

<PW2:1> .. <PW2:N> is the +15.0 V levels with one decimal resolution and a leading +
sign as measured in power supply 1 to power supply N.
<PW3:1> .. <PW3:N> is the +6.45 V levels with two decimals resolution and a leading +
sign as measured in supply 1 to power supply N.
<PW4:1> is the +6.45 backup power level with two decimals resolution and a leading +
sign as measured in power supply 1.
<PTM:1> .. <PTM:N> is the temperature with one decimal resolution and a leading + or
minus sign.
<BAT:1> is the battery level with one decimal resolution and a leading + sign as
measured in power supply 1.
<PSL:1> is the power supply input level with one decimal resolution as measured in
power supply 1.
Example (assuming system is equipped with two power supplies):
GET PLV
Reply:
+28.1 +28.0 +15.0 +15.0 +6.41 +6.43 +6.46 +44.6 +38.7 +11.1 235.0
Note!
√ If value is not available (such as communications error with power supply), a '-'
(dash) is replied in corresponding position.
9.5 PSC – Power Supply Count

Displays how many power supplies are used in this configuration.
Usage
This attribute displays number of power supplies configured in this repeater.
Format:
N
where N identifed how many power supplies are installed.
Example:
GET PSC
Reply:
2
means that this repeater contains two power supplies.
9.6 PSL – Status of Power Supply Level

Reports status of power supply input level measurements.
Usage
The Power Supply constantly monitors the mains input power level. This can be
used to generate an alarm if repeater is experiencing a power brownout or a
blackout.
In order to read out current power supply level, refer to attribute PLV. To configure
allowed thresholds, refer to attribute ALA PSL.
Power Supply input level is only measured in first power supply (Master Power
Supply).
Format:
<PSL>

<PSL>=0 means mains power level is within configured thresholds.

<PSL>=1 means power level is outside allowed interval (too low or too high).
If there is a communications error with master power supply, a ‘-‘ (dash) is

reported.
Example:
GET PSL
Reply:
1
meaning input power supply level is outside allowed interval.
9.7 PTM – Status of Power Supply Temperature

Reports status of power supply temperature levels.
Usage
The Power Supply temperature is continuously monitored, and if temperature is

outside configured interval, an alarm is triggered. This attribute shows the status of
the power supply temperatures for all power supplies configured in the repeater
(number of power supplies can be determined by reading attribute PSC).
Format:
<PTM:1>..<PTM:N>

1 means power supply temperature is outside allowed interval.
If communication with power supply is in error, a ‘-‘ (dash) is reported.
Example:
GET PTM
Reply:
01
means that temperature in Power Supply 1 is OK, while temperature in Power

Supply 2 is outside allowed range.
Note!
√ In order to read out current power supply temperature, please refer to attribute
PLV.
√ In order to read and configure power supply temperature alarm thresholds, refer
to ALA PTM.

9.8 PSD – Power Supply Distribution

Displays power supply distribution in the repoeater.
Usage:
This returns the current power supply levels throughout the entire repeater from all
modules capable of measuring the input voltage.
All voltages are given with three significant digits and a sign (+ or -). Therefore
voltages in the range of 0-9 are given as SN.MM and voltages in the range of 10-99
volts are given as SNN.M and voltages in the range 100-999 volts are given without
decimal on the format SNNN.
Format:
<PW1:PSUP1> <PW1:PSUP2> <PW1:LIMPA1UL> <PW1:LIMPA2UL> <PW1:LIMPA1DL> <PW1:LIMPA2DL>
<PW2:FO>
<PW3:REF> <PW3:COMMUX> <PW3:FO>
<PW4:PSUP1> <PSL:PSUP1>
where the voltages are as:
PW1 is the +28 VDC power supply.

PW2 is the +15 VDC power supply.
PW3 is the +6.45 VDC power supply.
PW4 is the digital +6.45 VDC power supply.
and the measuring points are:
PSUP1 Master power supply unit. This measuring point is installed in all repeaters.
PSUP2 Slave power supply unit. This unit is only installed in 4 carrier repeaters.
LIMPA1UL-LIMPA2UL these refers to the LIMPA modules in the repeater. 2 carrier repeater use one
LIMPA1DL-LIMPA2DL uplink one downlink LIMPA units, while 4 carrier repeaters use 4 LIMPA units,
2 UL and 2 DL. Not supported LIMPAs just report "-" (dash).
REF Reference generator can also measure the voltage and report it.
COMMUX Communications multiplexer.
FO Fiberoptic unit
Example:
GET PSD
Reply:
+28.0 - +28.0 - +28.0 - +15.0 - +15.0 - +15.0 - - +6.46 - +6.46 - +6.46 - +6.46 - -
+6.45 230
9.9 PW1 – Power 1

Gives status of the power supply 1 distribution to the different modules in the
repeater.

Usage:
This attribute replies with status of the Power Supply 1 (+28 V) in the different
modules in the repeater.
Format:
<PSUP1><PSUP2><LIMPA1UL><LIMPA2UL><LIMPA1DL><LIMPA2DL>
where
<PSUP1> is status of the +28 V as measured in the Master Power Supply.
<PSUP2> is status of the +28 V as measured in the Slave Power Supply.
<LIMPA1UL>-<LIMPA2UL> and <LIMPA1DL>-<LIMPA2DL> is status of the +28 V
as measured in the different LIMPA units.
Example:
GET PW1
Reply:
0-0-0-
meaning that power supply 1 is measured as being okay in PSU1, LIMPA1UL,

LIMPA1DL.
9.10 PW2 – Power 2

repeater.
Usage:
This attribute replies with status of the Power Supply 2 (+15 V) in the different
Format:
<PSUP1><PSUP2><LIMPA1UL><LIMPA2UL><LIMPA1DL><LIMPA2DL><FO>
where
PSUP1 Master power supply, installed in all repeater models.
PSUP2 Slave power supply, installed in 4-carrier repeaters.
LIMPA1UL LIMPA 1 uplink.
LIMPA2UL LIMPA 2 uplink, installed in 4-carrier repeaters.
LIMPA1DL LIMPA 1 downlink.
LIMPA2DL LIMPA 2 downlink, installed in 4-carrier repeaters.
FO fibre-optical module (but only type 1 reports this). If the repeater does not have a FO
module or the FO module is of type 2 or there is no communications with the module
then a dash, "-", is reported. Check the attribute FOC to find out which type is
installed.

Example:
GET PW1
Reply:
0-0-0--
meaning that PSU1, LIMPA1UL and LIMPA1DL reports power 2 OK.
9.11 PW3 – Power 3

repeater.
Usage:
This attribute replies with status of the Power Supply 3 (+6.45 V) in the different
Format:
<PSUP1><PSUP2><LIMPA1UL><LIMPA2UL><LIMPA1DL><LIMPA2DL><REFGEN><COMMUX><FO>
where
PSUP1 Master Power Supply

PSUP2 Slave Power Supply (only used in 4 carrier repeaters)
LIMPA1UL LIMPA 1 uplink
LIMPA2UL LIMPA 2 uplink (only in 4 carrier repeaters)
LIMPA1DL LIMPA 1 downlink
LIMPA2DL LIMPA 2 downlink (only in 4 carrier repeaters)
REFGEN Reference generator
COMMUX Communications multiplexer
FO Only if FO module is of type 1. Type 2 do not report PW3.
Example:
GET PW3
Reply:
1-0-0-0--
meaning that power supply 1 is measured as not being within allowed interval in
the LIMPA1DL unit.

9.12 PW4 – Power 4

repeater.
Usage:
This attribute replies with status of the Power Supply4 (+15 V) in the different
Format:
<PSUP1>
where
<PSUP1> is status of the backup power supply as measured in the PSU.
Example:
GET PW4
Reply:
0
no error on the power supply 4.
9.13 RBT – Radio Board Temperature

Gives the status of the radio board temperatures throughout the repeater.
Usage:
Attribute type: Rad only
This attribute replies with the status of the radio board temperatures in the
repeater. Each radio board (LIMPA unit) has a single point of measure for the
temperature.
Format:
<LIMPA1UL><LIMPA2UL><LIMPA1DL><LIMPA2DL><FO1><FO2><FO3><FO4>
Modules that are not installed or has not measured yet reports "-" (dash).
Otherwise status is 0 for OK and 1 for ERROR.
RBT is only reported for variant 2 of optical modules, not variant 1.
Example:
GET RBT
Reply:
0-0-----
meaning that LIMPA 1 UL and LIMPA 1 DL reports no error.

9.14 TEL – Temperature Levels

Displays temperatures as measured throughout the repeater.
Usage:
This attribute displays all temperatures as measured in the different boards of the
repeater. Temperature levels for fiber optic units are only shown if they are of type
2.
Format:
<CTRL> <PSUP1> <PSUP2> <LIMPA1UL> <LIMPA2UL> <LIMPA1DL> <LIMPA2DL> <FOSLAVE1>
<FOSLAVE2> <FOSLAVE3> <FOSLAVE4>
Temperature for each of the devices are presented with one decimal resolution and
a leading + or minus sign.
If data is not available (communications error or module not configured), a '-'

(dash) is presented in corresponding position.
Example:
GET TEL
Reply:
+31.4 +45.1 - +36.0 - +36.8 - - - - -
indicating the different temperature levels throughout the repeater.
9.15 TEM – Status of Controller Temperature

Displays status of temperature as measured in the repeater controller.
Usage
This attribute replies with status of the temperature as measured in the repeater
controller.
Format:
<TEM>
where
- (dash) means data is not available (not yet measured).
Example:
GET TEM
Reply:
1
indicating that temperature as measured in controller is outside allowed interval (as

configured with attribute ALA TEM). Current temperature can be read out using
attribute TEL.

10 OPTO RELATED ATTRIBUTES (TYPE I)

This chapter contains attributes that relates to:
● Optical transmission equipment
Note!
√ Use the attribute FOC to determine which optical module type this is.
10.1 OLA – Optical Link Adjustments

Fiber Optic module in repeater does not support pilot tone.
Usage:
Attribute type: Read and Action
This attribute is available for compatibility reasons and always replies with an error
message.
Example:
ACT OLA
Reply:
Error: Fiber Optic module in repeater does not support Optical Link Adjustments.
10.2 OLC – Optical Link Compensation

Fiber Optic module in repeater does not support pilot tone.
Usage:
This attribute is available for compatibility reasons and always replies with an error
message.
Example:
ACT OLA
Reply:
Error: Fiber Optic module in repeater does not support Optical Link Adjustments.
10.3 OLV – Optical Levels

Replies with optical signal level as measured in the opto module.
Usage

Knowing the fixed optical transmission level of the opto master and measuring the
received optical level, it is possible to calculate optical loss between master and
slave unit.
This attribute displays the received optical level in dBm.
Format:
<Rx Level> <TxLevel>
where level is represented in dBm with one decimal resolution. If level is lower than
lowest detectable, '<[LowDet]' is replied.
Example:
GET OLV
Reply:
-7.1 2.5
meaning that received optical level is -7.1 dBm and transmitted optical level is 2.5
dBm. In this example, knowing that optical transmitted level is 3 dBm, optical loss
is calculated to 10.1 dB.
Note!
√ If value is not available (such as communications error with FiberOptic Module),

two dashes '- -' are reported.
10.4 OSP – Opto Module Parameters

Displays parameters related to performance of the opto module.
Usage:
This attribute replies with lowest detectable transmitted and received optical levels.
This used to be the OMP attribute but has been replaced with OSP in both Type I
and Type II optical modules. The format are different however.
Format:
<Lowest Detectable Rx> <Lowest Detectable Tx>
where reply is lowest detectable value in dBm with one decimal resoultion.
Example:
GET OSP
Reply:
-15.0 -15.0
meaning that the opto module can detect received and transmitted optical levels
down to -15.0 dBm.
10.5 RXO – Status of Received Optical Level

This attribute replies with the status of the Received Optical Level alarm source.

Usage:
The Opto Module constantly monitors received optical level. A too low optical input
level might indicate that there is something wrong with the transmitter, a bad
optical connection (poor soldering or cleaning) or a broken fiber.
A drop in received optical level most likely means that received RF-signal level also
has dropped and that repeater coverage area is affected / decreased.
Format:
<RXO>
0 if status is OK.
1 if status is ERROR.
configured system).
Example:
GET RXO
Reply:
1
indicating that received optical level is lower than expected level, and that reason
for the dropped input signal level should be investigated.
10.6 TXO – Status of Transmitted Optical Level

This attribute replies with the status of the transmitted optical level alarm source.
Usage:
Transmitted optical power level is constantly monitored to ensure functionality of

the system. In case the optical transmitter for some reason fails (hardware failure),
an alarm is triggered.
Format:
<TXO>
where reply is
0 if status is OK.
configured system).
Example:
GET TXO
Reply:
1

indicating that something is malfunctioning with the optical transmitter. Reason for
failure should be investigated.

11 OPTO RELATED ATTRIBUTES (TYPE II)

This chapter contains attributes that relates to:
● Optical transmission equipment
● Automated Optical Link Adjustment feature (OLA)
Note!
√ Use the attribute FOC to determine which optical module type this is.
11.1 FOC – Fiber-Optic Capabilities

Fiber-optic capabilities.
Usage:
Retrieve the current optical module capabilities.
Format:
<FO1><FO2><FO3><FO4>
where
FO1 is the first optical module, FO2 is the second and so on for FO3 and FO4.
Normally a GSM-UMTS repeater has normally just one optical module so this is
offered for future expansion.
where N can be one of the following:

0 No optical capabilities. Optical module not installed or non-fibre fed repeater type.
1 First generation optical module without pilot tone capability. Module reports analogue voltages
using optical interface module.
2 Second generation optical module that includes pilot tone generation capability supporting
automatic optical link adjustment. Active unit with embedded processor on board.
Example:
GET FOC
Reply:
1000
meaning that this repeater has an optical module capable of reporting the analogue
values but no pilot tone capability.
Example for a non-fibre fed unit:

GET FOC
Reply:
0000
Example for a fibre fed unit with second generation optic module:
GET FOC

Reply:
2000
11.2 OLA – Optical Loss Adjustment

This attribute is used to read and adjust link between master and optical slave unit.
Usage
Attribute type: Read and Action
This attribute is used to perform an automatic adjustment of the fiber optic link to
compensate for losses, and to read status of last performed adjustment.
Adjustments are made to get a well balanced and optimized system, maintaining
desired gain over the entire link from input of Optical Master Unit to output of
repeater. When performing the adjustment from master to slave, a pilot tone with a
well defined level is sent form the master to the slave (always enabled in master).
Format on ACT:
ACT OLA [-v]
performs automatic adjustment of the opto link from the optical master unit to the
Fiber Optic Slave.
If supplying parameter -v (as verbose) progress information is printed out on the

screen as the adjustments proceed.
Example:
ACT OLA
performs an optical link adjustment of link from opto master to repeater.
Reading OLA replies with status of last performed adjustments.
Format on GET:
GET OLA
reads last fiber optic adjustment for link from slave repeater to opto module in rack
<Rack>, slot <Slot>.
Reply:
<Status> <Start Time> <Stop Time> <Initial Attenuation> <Resulting
Attenuation> <Resulting Pilot Tone Level> <Number of Iterations> <Result
String>
where
<Status> is status of last measurement, 0 means adjustments were successfully

completed, 1 means adjustments failed.
<Start Time> is on the format HHMMSS DDMMYY, where HHMMSS is the time with
24 hours notation, and DDMMYY is the date for when last measurement started.
<Stop Time> is on the format HHMMSS DDMMYY, where HHMMSS is the time with
24 hours notation, and DDMMYY is the date for when last measurement finished.
<Initial Attenuation> is the attenuation set before starting the adjustment routine.

<Resulting Attenuation> is the attenuation that was set when routine was
completed.
<Resulting Pilot Tone Level> indicates the received pilot tone level in dBm * 10
when adjustment was completed (for optimal performance, pilot tone should be
adjusted to -32.0 dBm).
<NumberOfIterations> indicates number of iterations (Set Attenuation- Read Pilot

Tone Level) that was needed to complete adjustment.
<Result String> is a quoted string containing additional information about

measurement or reason for failure.
Example:
GET OLA
Reply:
0 144503 220507 144511 220507 23 25 -314 3 “Pilot tone adjusted to -31.4
dBm, procedure completed.”
indicating result for last adjustment.
If no adjustment has been performed, a '-' (dash) is reported instead.
11.3 OLC – Optical Loss Compensation

Displays (and optionally configures) compensation for optical loss.
Usage
During automatic optimization of the FiberOptic link, the node master reads the
received pilot tone level and compensates for the optical loss. This is to ensure that
the input RF level from the Optical Master Unit is at the correct level to obtain the
correct system gain.

<OLC>
where OLC indicates attenuation in dB configured by the Optical Master Unit to
obtain optimal performance of the system.
Example:
GET OLC
Reply:
20
indicating that the optical loss attenuation.
Note!
√ This parameter should normally be adjusted by the node master. Changing this
parameter incorrectly might cause RXP (Received Pilot Tone) alarm to be
triggered since optical link will be mis-configured. However, under certain
circumstances it might be necessary to adjust this manually, such as during
integration with the old generation Opto HUB units.


SET OLC <Atten>
where <Atten> is the desired attenuation in dB. Valid range is 0 to 25 dB.
Example:
SET OLC 18
adjusts the attenuation to 18 dB.
11.4 OLV – Optical Level

Replies with optical signal level as received from the optical master unit.
Usage
Knowing the fixed optical transmission level of the optical master unit and
measuring the received optical level, it is possible to calculate optical loss between
master and slave unit.
This attribute displays the received optical level in dBm.
Format:
<OLV>
where OLV replies in received optical level in dBm with one decimal resolution. If
level is lower than lowest detectable, '<[LowDet]' is replied.
Example:
GET OLV
Reply:
-7.1
meaning that received optical level is -7.1 dBm. In this example, knowing that
optical transmitted level is 3 dBm, optical loss is calculated to 10.1 dB.
Note!
√ If value is not available (such as communications error with FiberOptic Slave), a

'-' (dash) is reported.
11.5 OSP – Opto Slave Parameters

Displays different parameters on the optical slave.
Usage
This attribute replies with parameters and constants of the FiberOptic Slave. Values
are used by the repeater to perform calculations and to present user with opto
slave performance data.
Format:

<Rx Opto LowDet> <Pilot Offset Attenuation> <Pilot LowDet> <PilotARFCN>
where
<Rx Opto LowDet> is the lowest detectable received opto signal in dBm with one
decimal resolution.
<Pilot Offset Attenuation> is a frequency offset in dB set during production of the

repeater, and is used to compensate for frequency variations in the opto slave.
<Pilot LowDet> is the lowest detectable pilot tone level in dBm with one decimal
resolution.
<PilotARFCN> is the channel used for the pilot tone.
Example:
GET OSP
Reply:
-15.0 3 -50.0 500
indicating that lowest detectable optical level is -15.0 dBm, pilot tone offset is 3 dB,
lowest detectable pilot tone is -50.0 dBm and ARFCN used for generated pilot tone
is 500.
11.6 PTE – Pilot Tone Enabled

This attribute is used to enable or disable pilot tone from slave to master.
Usage
When commissioning an Avitec Repeater System it is essential that all fiber optic
links are optimized and RF-limits adjusted accordingly. To accomplish this, a pilot
tone is transmitted from Optical Master Units to the Fiber Optic Slaves. By
transmitting with a known level, it is possible to read out the path loss by
monitoring the received pilot tone level. Also, in order to fine tune optical loss from
slave to master the slave pilot tone can be enabled.
Once repeater system is commissioned, monitoring the pilot tone level ensures that
the signal level stays within expected levels.
This attribute is used to enable and disable the pilot tone from the slave to the
master (uplink pilot tone).

GET PTE
Reply:
<PTE>
where
PTE = 0 means pilot tone is disabled.
PTE = 1 means pilot tone is enabled.
Format on setting parameters:

SET PTE <val>

where
<val> = 0 means output power should be turned off.

<val> = 1 means output power should be turned on.
Example:
GET PTE
Reply:
1
meaning that pilot tone is enabled.
Example:
SET PTE 0
disables the pilot tone
Note!
√ Normally, enabling and disabling Pilot Tone is performed from the node master
as a part of the automatic optical loss adjustment procedure, why altering this
parameter normally should be avoided.
√ During startup of the system, slave pilot tone is always disabled.
11.7 PTL – Pilot Tone Level

This attribute replies with received pilot tone level from optical master unit.
Usage
This attribute replies with received pilot tone level from optical master unit. This
value is used during automatic optical loss compensations to ensure that the
repeater system is commissioned with optimal performance.
Format:
<PTL>
where <PTL> is the received pilot tone level in dBm with one decimal resolution. If
lower than lowest detectable pilot tone level, a <[Lowest Detectable Pilot Tone
Level] is presented.
Example:
GET PTL
Reply:
-22.1
indicating that level of received pilot tone is -22.1 dBm.
11.8 PTN – Pilot Tone Nominal Level

This attribute replies with the nominal level for the received pilot tone level.

Usage
Attribute type: Read and write
This attribute replies with the nominal pilot tone level that should be received from
the master node when a system is properly commissioned. This value serves as the
value that received pilot tone should be adjusted to in order to have an optimized
system. It also serves as the reference value used when performing PTL alarm
measurements.

GET PTN
Reply:
<PTN>
where <PTN> is nominal level in dBm * 10. If node is not yet commissioned, this
replies as -110.0

SET PTN <PTN>
where <PTN> is the nominal level in dBm * 10.
Example:
GET PTN
Reply:
-1100
meaning that nominal pilot tone level is -110.0 dBm (not commissioned).
Example:
SET PTN -250
sets nominal pilot tone level to -25.0 dBm.
11.9 RXO – Status of Received Optical Level

Usage
The Fiber Optic Slave constantly monitors received optical level. A too low optical
input level might indicate that there is something wrong with the transmitter, a bad
optical connection (poor soldering or cleaning) or a broken fiber.
A drop in received optical level most likely means that received RF-signal level also
has dropped and that repeater coverage area is affected / decreased.
Format:
<RXO>
0 if status is OK.


configured system).
Example:
GET RXO
Reply:
1
indicating that received optical level is lower than expected level, and that reason
for the dropped input signal level should be investigated.
11.10 RXP– Status of Received Pilot Tone Level

This attribute replies with status for the Received Pilot Tone Level alarm source.
Usage
transmitting with a known level and measuring received pilot tone level it is
possible to calculate path loss and hence compensate system gain accordingly.
Once repeater system is commissioned, monitoring the pilot tone level ensures that
the signal level stays within expected levels.
This attribute replies with status for the Received Pilot Tone Level alarm source.
Format:
<RXP>
where reply is
0 if status is OK.
configured system).
Example:
GET RXP
Reply:
1
indicating that received pilot tone level is lower than configured level, and that
reason for the dropped input signal level should be investigated.
11.11 SZP – Status of Pilot Tone Generator Synthesizer

Replies with the status of the Pilot Tone Generator Synthesizer.
Usage

transmitting with a known level and measuring received pilot tone level it is
possible to calculate the path loss and hence compensate system gain accordingly.
To generate the correct pilot tone frequency, a synthesizer is used. If there is a

failure generating the correct pilot tone frequency, an Synthesizer Pilot Tone
generator alarm is triggered.
This attribute replies with the status of the Pilot Tone Generator Synthesizer.
Format:
<SZP>
where reply is
0 if status is OK/Synthesizer locked onto desired frequency.

1 if status is ERROR/Synthesizer not locked onto desired frequency.
configured system).
Example:
GET SZP
Reply:
1
indicating that synthesizer is unlocked, and that reason for failure should be
investigated.
11.12 TXO – Status of Transmitted Optical Level

Usage
Transmitted optical power level is constantly monitored to ensure functionality of

the system. In case the optical transmitter for some reason fails (hardware failure),
an alarm is triggered.
Format:
<TXO>
where reply is
0 if status is OK.
configured system).
Example:
GET TXO

Reply:
1
indicating that something is malfunctioning with the optical transmitter. Reason for
failure should be investigated.

12 HEARTBEAT FORMAT
The heartbeat report is transmitted to the Avitec Element Manager on configurable
intervals (0-99 999 min). In case the heartbeat report is not received by the Avitec
Element Manager within expected interval, an alarm is triggered at the AEM.
If repeater is a Repeater System Slave, heartbeats are collected by the the node
master for transmission to the Avitec Element Manager.
In the heartbeat report, all fields are separated by space.
12.1 Hex encoded values, a quick description

In the new heart beat format some values have been hex coded. These values are
therefore representing bitwise status for several units. The attributes that has been
such coded are marked with an asterisk "*" in the "Field" column of the table.
An example of this is the CRC-alarm part of the heart beat message. Here there are
three bytes that can represent up to 24 units by assigning one bit as a status bit for
each unit. The way it works is that the bits are added together, bit3 is worth 8, bit 2
is worth 4, bit 1 is worth 2 and bit 0 is worth 1. If bit3 to bit0 represents fibre-optic
unit 1-4 and if there is a problem with unit 2 and unit 3, then the resulting code
would be represented by 4+2 = 6.
Numbers ranging from 10-15 are represented by the letters A-F. This is normal
hexadecimal encoding and thus if units 1 and 2 has a problem this means that their
added value is 8+4 = 12 which is represented by a "C" in the status byte.
Bit stuffing is also used combining several attributes in the same byte in order to
cut down the length of the HBT message.
12.2 Heartbeat table

Field Format Description Size
Repeater ID XX-YY-ZZZZ XX is AEM number, YY is region number for the repeater, ZZZZ is the 10
repeater ID which is a running number for all repeaters that are not
system slaves. System slaves use their serial number instead of a running
number to ID.
Message no NNNNNNNNN 9
State "HBT" The letters "HBT" is replacing the state word. 3

Date DDMMYY 6
Time HHMMSS 6
IHU, FOC* HHHHHH Installed hardware units. 6
0 = not installed
1 = installed
Byte 1
Bit 3 Bit 2 Bit 1 Bit 0
PSUP1 PSUP2 LIMPA1UL LIMPA2UL

Byte 2
LIMPA1DL LIMPA2DL REFGEN FO1
Byte 3
FO2 FO3 FO4 COMMUX
Byte 4
FDM-S1 FDM-S2
Fiberoptic capabilities (bit1/bit0):

00 = Not installed
01 = RTX Optical module
10 = FO Slave with pilot tone adjustment
11 = N/A
Byte 5
FOC 1 Bit 1 FOC 1 Bit 0 FOC 2 Bit 1 FOC 2 Bit 0
Byte 6
FOC 3 Bit 1 FOC 3 Bit 0 FOC 4 Bit 1 FOC 4 Bit 0
CHA/LNK AAAABBBBCCCC Hexadecimal coding of the channels used in the repeater. This field reads 32
CHD/CHU* DDDDXXXXYYYY differently depending on repeater model.
ZZZZWWWW
In GSM-EDGE repeaters the first part (AAAA-DDDD) is the four possible
channels and the second part are the four possible link channels (XXXX-
WWWW). If this is a conventional (CSR) type repeater the second part is
not used and set to zero.
In WCDMA repeaters the first part (AAAA-DDDD) are the downlink channel
numbers (CHD) and the later part (XXXX-WWWW) are the uplink channel
numbers (CHU). The way this is encoded we can cover channel numbers
between 0 to 65535.
ATD/ATU XXYYZZWWAABB Attenuation in downlink for all chains then uplink for all chains. Zero 16
CCDD padded. If module not installed, two dashes are replied.
The order of this is DL1 DL2 DL3 DL4 UL1 UL2 UL3 UL4 .
LVD/LVU* AABBCCDDXXYY Output peak power level. 16
ZZWW
This is a signed hex-encoded number signifying the set output level. The
possible range are -128 to +127. The order of the attribute is DL1 DL2
DL3 DL4 and UL1 UL2 UL3 UL4.
Examples
-100D = 9CH
43D = 2BH
-10D = F6H

AMD, AMU, HHHHHHHHH Amplifier statuses 9

ASD, ASU, SZD,
SZU,WRD* Amplifier chain status and amplifier saturation status.
Byte 1
Status for AMD 1 Status for AMD 2 Status for AMD 3 Status for AMD 4
Byte 2
Status for AMU 1 Status for AMU 2 Status for AMU 3 Status for AMU 4
Byte 3
Status of ASD 1 Status of ASD 2 Status of ASD 3 Status of ASD 4
Byte 4
Status of ASU 1 Status of ASU 2 Status of ASU 3 Status of ASU 4
Synthesizer statuses
Synthesizer staus for all LIMPA synthesizers in the repeaters. The order is
L1 U C1 I means LIMPA 1 Uplink Chain 1 IN synthesizer. L2DC2O means
LIMPA 2 DL Chain 2 OUT synthesizer.
Byte 5 – LIMPA 1 Downlink

L1 D C1 I L1 D C1 O L1 D C2 I L1 D C2 O
Byte 6 – LIMPA 2 Downlink

L2 D C1 I L2 D C1 O L2 D C2 I L2 D C2 O
Byte 7 – LIMPA 1 Uplink

L1 U C1 I L1 U C1 O L1 U C2 I L1 U C2 O
Byte 8 – LIMPA 2 Uplink

L2 U C1 I L2 U C1 O L2 U C2 I L2 U C2 O
Byte 9 – WRD status for FDM1 and FDM2 server

WRD FDM S1 WRD FDM S2
COM NNNNNNNNNNN Status of communication between controller and active devices. 14

NNN

CRC, BAT, AIM, HHHHHHHHHHH Status of CRC Status for target firmware. Status of battery. Status of 12
PDL, PW1, PW2, H antenna isolation measurement. Status of Power Downlink.
PW3, PW4, PSL,
TEM, PTM, RXQ Byte 1
DOO, RBT* Bit 3 Bit 2 Bit 1 Bit 0
CRC FO1 CRC FO2 CRC FO3 CRC FO4
Byte 2
CRC COMMUX BAT AIM PSL
Power downlink status bits.
Byte 3
PDL DL1 PDL DL2 PDL DL3 PDL DL4
Power supply statuses.

Internal DC voltages statuses and power supply level status. The door
attribute is also contained in this part.
Byte 4
PW1 PSU1 PW1 PSU2 PW1 LIMPA1UL PW1 LIMPA2UL
Byte 5
PW1 LIMPA1DL PW1 LIMPA2DL PW2 PSU1 PW2 PSU2
Byte 6
PW2 LIMPA1UL PW2 LIMPA2UL PW2 LIMPA1DL PW2 LIMPA2DL
Byte 7
4
PW2 FO PW3 PSU1 PW3 PSU2 PW3 LIMPA1UL
Byte 8
PW3LIMPA2UL PW3 LIMPA1DL PW3 LIMPA2DL PW3 REFGEN
Byte 9
4
PW3 FO1 PW4 DOO
Various temperature and other status bits.

Temperature measure points statuses throughout the repeater unit.
Byte 10
4 Only type 1 optical modules reports this. Check the FOC attribute to find out if this is relevant.

TEM RXQ PTM PSU1 PTM PSU2
Byte 11
RBT LIMPA UL1 RBT LIMPA UL2 RBT LIMPA DL1 RBT LIMPA DL2
Byte 12
RBT FO1 RBT FO2 RBT FO3 RBT FO4
RXO, RXP, SZP, HHHHHN Optical statuses. 6

TXO, EX1-4,
NMP* Status of Received Optical Level, status of pilot tone level, status of pilot
tone synthesizer, status of optical transmitter and external alarm status
bits.
Byte 1
RXO FO1 RXO FO2 RXO FO3 RXO FO4
Byte 2
RXP FO1 RXP FO2 RXP FO3 RXP FO4
Byte 3
SZP FO1 SZP FO2 SZP FO3 SZP FO4
Byte 4
TXO FO1 TXO FO2 TXO FO3 TXO FO4
Byte 5
EX1 EX2 EX3 EX4
Byte 6
NMP (not hex encoded, just plain 0-9)
RCH HHHHH Repetition Cycle for Heartbeat reports in minutes. 5
This is an unsigned hexadecimally coded word that ranges from 00000 to
FFFFF, or in decimal 0 to 1 048 575.

13 ALARM SOURCES
This section defines alarm sources in the GSM-UMTS target.
The following alarms are NOT described in this chapter, but are generated by the
repeater:
 External Alarm Interface board alarms EX1-EX4 and DOO. are not described.
 User activity alarms VLI, LGO and CLR.
 User administration alarms (UAD, UDE, UPM, UDM and UPW).
 Firmware upgrade / fallback alarms (FWU and FWF).
Alarm overview table:

Attrib Description Class Severity
AIM Antenna isolation measurement Environment Major
AMD Amplifier chain downlink Equipment Major
AMU Amplifier chain uplink Equipment Major
5
ASD Amplifier saturation downlink (GSM) Environment Minor
5
ASD Amplifier saturation downlink (UMTS) Environment Major
5
ASU Amplifier saturation uplink (GSM) Environment Minor
5
ASU Amplifier saturation uplink (UMTS) Environment Major
BAT Battery Equipment Minor
COM Communications alarm Communication Critical
CRC EEPROM Cyclic redundancy check Equipment Critical
TEM Controller temperature Environment Major
DOO Door open Equipment Warning
EX1 External Alarm 1 Equipment Major
IOD Input overload downlink Environment Major
IOU Input overload uplink Environment Major
6
NMP Node communications path . Equipment Warning
PDL BCCH / Pilot Tone level Environment Major
PSL Power supply level Environment Major
PTM Power supply temperature Environment Major
PW1 Power 1 Equipment Critical
5 There are some alarms which have different severity depending on the specific repeater they are reported from.
These alarms have been marked with * and are therefore listed twice in the table above.
6 This is reserved for future use and not implemented in this version.

Attrib Description Class Severity

RBT Radio board temperature Environment Major
RXO Receive level optical Equipment Major
RXP Receive level pilot tone Equipment Minor
SZD Synthesizer downlink Equipment Critical
SZP Synthesizer status pilot tone Equipment Major
WRD VSWR alarm status Environment Minor
13.1 AIM – Antenna isolation measurement

This alarm means that the last antenna isolation measurement has detected a too
low isolation between the input and output antennas and therefore the repeater risk
severely degraded performance and even oscillation.
Isolation should be increased by arranging the antennas in a more optimum

position.
Upper threshold: N/A

Lower threshold: CSFT: 75 dB, CSR: 15 dB+GAIN, CSF: N/A
Time: 5 seconds.
13.2 AMD – Amplifier chain downlink

The amplifier chain in the repeater consists of the Low Noise Amplifier, the
channelizer and its amplifiers, settable attenuator, and the power amplifier. The
repeater monitors the input and output power and knows it's own settings.
Therefore it is possible to calculate the expected output power with a given input
signal and compare this with the actual measured output power.
If the measured signal deviates from the calculated with more than a few dB then
the alarm is triggered. It is important to not set the thresholds too tight because
the input and output meters have a limited accuracy which is about ±2 dB. The
gain flatness over the band is also ±1 dB meaning that a setting lower than 6 dB
may yield false alarms.
This alarm has also been known to be triggered by outside interference, i.e.
another base station using a frequency close to the repeated frequency or the link
frequency.
If the channels in the repeater is not properly spaced to allow the channel filters to
reject the unwanted signals properly this alarm may be falsely triggered.
Upper threshold: 60 (meaning 6 dB)

Lower threshold: 60 (meaning 6 dB)
Time: 5 seconds
13.3 AMU – Amplifier chain uplink

The amplifier chain in the repeater consists of the Low Noise Amplifier, the
channelizer and its amplifiers, settable attenuator, and the power amplifier. The
repeater monitors the input and output power and knows it's own settings.

Therefore it is possible to calculate the expected output power with a given input
signal and compare this with the actual measured output power.
If the measured signal deviates from the calculated with more than a few dB then
the alarm is triggered. It is important to not set the thresholds too tight because
the input and output meters have a limited accuracy which is about ±2 dB. The
gain flatness over the band is also ±1 dB meaning that a setting lower than 6 dB
may yield false alarms.
This alarm has also been known to be triggered by outside interference, i.e.
another base station using a frequency close to the repeated frequency or the link
frequency.
If the channels in the repeater is not properly spaced to allow the channel filters to
reject the unwanted signals properly this alarm may be falsely triggered.
Upper threshold: 60 (meaning 6 dB)

Lower threshold: 60 (meaning 6 dB)
Time: 5 seconds
13.4 ASD – Amplifier saturation downlink

When the gain setting in the repeater is too high for a given input signal the
amplifier saturation alarm may be triggered. This alarm means that the repeater is
over-amplifying the signal which may have adverse effects on the signal quality.
To alleviate the problem the gain in the repeater should be reduced by increasing
the attenuation in the relevant amplifier.
It is particularly important to not saturate a WCDMA repeater since the signal

quality can become very poor quickly if the repeater saturates.
On rare occasions the input power to the repeater can become so high that the
settable attenuator in the repeater is not enough to fix the problem. Should this
occur an external attenuator may be mounted on the repeater antenna port.
Reasonable values are 10-20 dB for such an attenuator.
If this problem occurs in a remote repeater of the CSFT type then the output power
of the donor unit should be reduced.
Upper threshold: Uses a pre-defined value

Lower threshold: N/A
Time: 5 seconds.
In GSM repeater the saturation indicator seen in the RMC has four different levels.
The levels are: LOW, OK, HIGH and CRITICAL. If the saturation of the repeater
reaches critical then this alarm is triggered. The alarm indicates possible reduction
in signal quality because of high saturation in the amplifiers. This is mostly a
problem when using EDGE signals since GMSK modulation is more robust in this
aspect.
In WCDMA repeaters the saturation indicator seen in the RMC only has two levels,
linear and non-linear. It is vital for good signal quality to keep the repeater in the
linear range as much as possible because when the repeater reaches saturation the
amplitude component of the signal will be compressed creating a distortion of the

signal that adversely affects the signal quality. The farther the repeater goes into
saturation the more problematic this is.
13.5 ASU – Amplifier chain uplink

When the gain setting in the repeater is too high for a given input signal the
amplifier saturation alarm may be triggered. This alarm means that the repeater is
over-amplifying the signal which may have adverse effects on the signal quality.
To alleviate the problem the gain in the repeater should be reduced by increasing
the attenuation in the relevant amplifier.
This alarm is rare in the uplink because the mobiles are generally power regulated
from the base station.
Upper threshold: Uses a pre-defined value

Time: 5 seconds.
In GSM repeater the saturation indicator seen in the RMC has four different levels.
The levels are: LOW, OK, HIGH and CRITICAL. If the saturation of the repeater
reaches critical then this alarm is triggered. The alarm indicates possible reduction
in signal quality because of high saturation in the amplifiers. This is mostly a
problem when using EDGE signals since GMSK modulation is more robust in this
aspect.
In WCDMA repeaters the saturation indicator seen in the RMC only has two levels,
linear and non-linear. It is vital for good signal quality to keep the repeater in the
linear range as much as possible because when the repeater reaches saturation the
amplitude component of the signal will be compressed creating a distortion of the
signal that adversely affects the signal quality. The farther the repeater goes into
saturation the more problematic this is.
13.6 BAT – Battery level

Some models of repeaters have a backup battery located in the master power
supply unit of the repeater. The purpose of this battery is to run the controller and
modem long enough to be able to report loss of power alarms to the Element
Manager. In normal case the repeaters controller can run about 15 minutes on this
battery.
This battery does NOT keep the RF amplifiers running in the repeater wherefore a
loss of service is expected.
The BAT alarm is triggered when the charge level of the battery is either too high
indicating a serious problem with the battery pack or too low indicating a battery
that can not charge.
Upper threshold: 120 (meaning 12.0 V)

Lower threshold: 75 (meaning 7.5 V
Time: 5 seconds.

13.7 COM - Communication

This alarm is reported when the controller is unable to communicate with any of the
active modules in the repeater. There are several sources for this alarm including
any of the following modules: Master power supply, slave power supply, LIMPA
modules, active FDM units, reference generator, fiber optical unit (type 2),
communications multiplexer (if present).

Time: 3 seconds
13.8 CRC – EEPROM Error

CRC – EEPROM Error
This alarm is triggered when the micro controllerinside a module detects a corrupt
memory bank. To alleviate the problem the module reporting the error should be
replaced.

Time: 3 seconds
13.9 IOD – Input overload downlink

Input overload alarms are triggered when there is a risk that the low noise amplifier
(LNA) might be blocked by a very strong signal. Since the LNA is located before the
channelization and is therefore full band it is possible that a signal elsewhere in the
band is causing this.
Input overload triggers generally when the signal is higher than -25 dBm. In fiber
optic equipment (CSF repeaters) the optical module should make sure that this
alarm do not happen in the downlink because the input of the repeater is protected
by the FO slave module which can not generate a strong enough signal to cause
this. For this reason if you see the alarm in a CSF type repeater consider the FO
Slave module or the LIMPA affected faulty.
In off-air repeaters (CSR, CSFT) it is possible that a signal from another repeater or
base station in the same band can trigger this. Also consider other RF sources, such
as TV band transmitters since they have extremely high output powers in some
cases. If the repeater is co-located with a TV transmitter it may be required to
mount an external filter to block the strong TV signals.
Repeaters not using antennas or radiating cables (leaky feeders) are generally not
in danger of receiving this levels unless there are multiple systems feeding the
same radiating cable.
Input overload may seriously degrade the repeater's performance.

Time: 5 seconds.

13.10 IOU – Input overload uplink

Input overload alarms are triggered when there is a risk that the low noise amplifier
(LNA) might be blocked by a very strong signal. Since the LNA is located before the
channelization and is therefore full band it is possible that a signal elsewhere in the
band is causing this.
In the uplink this may be caused by a mobile station very close to the repeater
transmitting at full output power.
Repeaters not using antennas or radiating cables (leaky feeders) are generally not
in danger of receiving this levels unless there are multiple systems feeding the
same radiating cable.
Input overload may seriously degrade the repeater's performance.

Time: 5 seconds.
13.11 NMP – Node communications path

This attribute is reserved for future use only.
13.12 PDL – BCCH/Pilot tone downlink

When the repeater is configured to look for a BCCH or Pilot Tone in the downlink it
will monitor its own output power in this amplifier chain. Should the signal
disappear for some reason this alarm may trigger.
Each amplifier chain in the repeater can be configured in three different ways, skip,
required or either. If a chain is configured as skip, then this chain will never trigger
this alarm. If a chain is configured as required then alarm will be generated upon
loss of signal in the downlink. If the chain is configured as "either" then all chains
configured as "either" are checked and if none of them contains a downlink signal
only then will the alarm be triggered.

Lower threshold: Varies with repeater model.
Time: 5 seconds.
13.13 PSL – Power supply level

This alarm is triggered if the input voltage to the repeaters power supply unit (PSU)
is too high or too low. The actual settings of the alarm depends on the type of PSU
in the repeater.
If a PSU is changed from one type to another type this alarm can be triggered when
the new PSU reports a different voltage. In this case the alarm thresholds should
just be adjusted to reflect the new power supply levels.
Limits for 240 VAC power supply

Upper threshold: 2650 (meaning 265 VAC)

Lower threshold: 2150 (meaning 215 VAC)
Time: 3 seconds.
Limits for 115 VAC power supply
Upper threshold: 1300 (meaning 130 VAC)

Lower threshold: 1000 (meaning 100 VAC)
Time: 3 seconds.
Limits for -48 VDC power supply
Upper threshold: -420 (meaning -42 VAC)

Lower threshold: -580 (meaning -58 VAC)
Time: 3 seconds.
13.14 PTM – Power supply temperature

Inside the PSU modules are temperature sensors. When the temperature is too high
or too low the alarm is triggered.
Upper threshold: 650 (meaning +65°C)

Lower threshold: -200 (meaning -20°C)
Time: 15 seconds
13.15 PW1 – Power 1

Power supply units and LIMPA units contains measurement points for power 1. This
alarm is triggered if the input +28 VDC power to the LIMPA is too high or too low.
Upper threshold: 300 (V*10) = 30.0 VDC

Lower threshold: 260 (V*10) = 26.0 VDC
Time: 3 seconds.
13.16 PW2 – Power 2

Power supply units and LIMPA units contains measurement points for power 2. This
alarm is triggered if the input +15 VDC power to the LIMPA is too high or too low.
Type 1 fibre optical modules also contains a measurement point for PW2.

Time: 3 seconds.
13.17 PW3 – Power 3

The Power 3 is measured in power supply units, LIMPA units, optical slave units of
type 1, reference generator. The alarm is triggered when any of these units reports
a deviation from the set thresholds.


Time: 3 seconds.
13.18 PW4 – Power 4

The PSU unit contains voltage meters on the DC side. This alarm is triggered if the
voltage is too high or too low. This is only reported from power supply 1, the
master power supply.

Time: 3 seconds.
13.19 RBT – Radio board temperature

Inside the LIMPA modules and fibre optic modules of type 2 are temperature
sensors. When the temperature is too high or too low the alarm is triggered.
Upper threshold: 750 (meaning +75°C)

Lower threshold: -200 (meaning -20°C)
Time: 15 seconds
13.20 RXO – Receive level optical

This alarm is triggered if the fibre-optical level in a fibre fed repeater is too low. The
alarm indicated a possible problem with the fibre, the receiver (FO Slave in
repeater) or the transmitter (FO Master in the HUB/OMU).

Lower threshold: -90 (meaning -9.0 dBm optical)
Time: 5 seconds.
13.21 RXP – Pilot tone status

Alarm is triggered when the received pilot tone level is too low to perform optical
link adjustment (OLA) between repeater and HUB/OMU. This alarm can be triggered
if the fibre is not properly connected, has too high loss or there is a problem with
either the fibre-optical transmitter or receiver.
Upper threshold: 30 (meaning 3.0 dB deviation from normal pilot tone level)
Lower threshold: 30 (meaning 3.0 dB deviation from normal pilot tone level)
Time: 5 seconds
13.22 SZD – Synthesized downlink

Each RF chain in the LIMPA (2 per LIMPA unit) are equipped with one input and out
output synthesizer. These synthesizers generate the frequency necessary to
perform the frequency shift to the intermediate frequency in the LIMPA and then

back to the original frequency again after filtering and selecting the frequency the
RF chain is set to.
If a synthesizer can not lock or produce the correct mixing frequency then the
alarm is triggered. For each uplink or downlink there are two such alarms, input
and output synthesizer.
In most cases this means a complete loss of the output signal from the LIMPA and
that the radio coverage from the repeater is down. This should be considered a
serious error of the repeater and is cause for sending the repeater in for repair.

Time: 3 seconds.
13.23 SZP – Synthesizer pilot tone

The pilot tone synthesizer is vital in the generation of a pilot tone to perform the
automatic optical link adjustment (OLA) between the repeater and HUB. If the
synthesizer can not lock to the correct frequency this alarm is generated. Normally
this only means that the OLA can not be performed but the rest of the repeater
should work well.

Time: 3 seconds.
13.24 SZU – Synthesizer uplink

Each RF chain in the LIMPA (2 per LIMPA unit) are equipped with one input and out
output synthesizer. These synthesizers generate the frequency necessary to
perform the frequency shift to the intermediate frequency in the LIMPA and then
back to the original frequency again after filtering and selecting the frequency the
RF chain is set to.
If a synthesizer can not lock or produce the correct mixing frequency then the
alarm is triggered. For each uplink or downlink there are two such alarms, input
and output synthesizer.
In most cases this means a complete loss of the output signal from the LIMPA and
that the radio coverage from the repeater is down. This should be considered a
serious error of the repeater and is cause for sending the repeater in for repair.

Time: 3 seconds.
13.25 TXO – Transmission level optical

This alarm is triggered if the FO slave in the repeater reports it can not transmit
over the fibre. If this happens there is likely a fault in the FO slave module and it
should be replaced.


Time: 3 seconds.
13.26 WRD – VSWR alarm

The return loss alarm, also known as VSWR alarm, is triggered when the reflected
signal in the antenna port of the repeater is too high. This value can be customized
by the user and in certain situations it needs to be changed from the default value.
Upper threshold: Not used

Lower threshold: 14 dB
Time: 5 seconds.
When the return signal to the repeater is less than 14 dB lower than the forward
signal the alarm is triggered.

AXELL WIRELESS
Common Commands and Attributes
v1.3.0
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2
Change Log
Version Change by Date Description
1.0 MW 29/01/09 Changes from 1.2.0 and 1.2.1 to 1.3.0
13.4.2 Added comment on DHCP via GPRS

13.7.2 Added Note 2 reagarding GPRS interface.
13.7.8 Added Note 5 regarding setting of GPRS parameters.
13.8.2 Added Note 4 regarding restarting of GPRS interface.
Added chapter 14 – GPRS Configurations
1.1 MW 17/03/09 14.1.5.2 Changed behavior of GET GPR ASC attribute.
1.2 MW 19/03/09 14.1.8.2 Added comments on ACT GPR APPLY
Legal Information
© COPYRIGHT AXELL WIRELESS 2009
translated into any human or computer language without the prior written permission of AXELL WIRELESS.
The manufacturer has made every effort to ensure that the instructions contained in the documents are adequate and
free of errors and omissions. The manufacturer will, if necessary, explain issues which may not be covered by the
documents. The manufacturer's liability for any errors in the documents is limited to the correction of errors and the
aforementioned advisory services.
assumes full responsibility when using them. The manufacturer welcomes customer comments as part of the process
of continual development and improvement of the documentation in the best way possible from the user's viewpoint.
Please submit your comments to the nearest AXELL WIRELESS sales representative.
Common Commands and Attributes 2/123

Contact Information
For further information about this document, please contact .
AXELL WIRELESS
Mailing address:
Axell Wireless
Aerial House
Asheridge Road
Chesham
United Kingdom
Tel: +44 1494 777000

Fax: +44 1494 777002
Web: http://www.axellwireless.com/

TABLE OF CONTENTS
1 Overview.................................................................................................................14
2 Axell Wireless Versus Avitec.......................................................................................14
3 Version Compatibility.................................................................................................14
4 Using Commands and Attributes.................................................................................14
5 Built in Help System..................................................................................................15
5.1 HELP command..................................................................................................15
5.2 INF command....................................................................................................15
6 External Alarms, DOOR and Controller Temperature......................................................16
6.1 CTM – Controller Temperature.............................................................................16
6.1.1 Overview....................................................................................................16
6.1.2 Usage........................................................................................................16
6.2 DOO – displays status of the door alarm source.....................................................17
6.2.1 Overview....................................................................................................17
6.2.2 Usage........................................................................................................17
6.3 DST – displays status of the door.........................................................................17
6.3.1 Overview....................................................................................................17
6.3.2 Usage........................................................................................................17
6.4 EAC – External alarm configuration......................................................................17
6.4.1 Overview....................................................................................................17
6.4.2 Usage........................................................................................................18
6.5 EAD – External alarm description.........................................................................18
6.5.1 Overview....................................................................................................18
6.5.2 Usage........................................................................................................18
6.6 EST – External Input Status................................................................................19
6.6.1 Overview....................................................................................................19
6.6.2 Usage........................................................................................................19
6.7 EX1 – status of external alarm input 1..................................................................20
6.7.1 Overview....................................................................................................20
6.7.2 Usage........................................................................................................20
6.8 EX2 – displays status of external alarm input 2......................................................20
6.8.1 Overview....................................................................................................20
6.8.2 Usage........................................................................................................20
6.9 EX3 – displays status of external alarm input 3......................................................20
6.9.1 Overview....................................................................................................20
6.9.2 Usage........................................................................................................21
6.10 EX4 – displays status of external alarm input 4....................................................21
6.10.1 Overview..................................................................................................21
6.10.2 Usage......................................................................................................21
6.11 EXT – External alarm pin configuration................................................................21
6.11.1 Overview..................................................................................................21
6.11.2 Usage......................................................................................................21
7 Alarm Configurations.................................................................................................22
7.1 ACL – Alarm Class Configuration..........................................................................22
7.1.1 Overview....................................................................................................22
7.1.2 Usage........................................................................................................22
7.2 AC1 – Compressed Alarm Severity and Alarm Class Configurations...........................23
7.2.1 Overview....................................................................................................23
7.2.2 Usage........................................................................................................23
7.3 AL1 - Compressed Alarm Format ........................................................................23
7.3.1 Overview....................................................................................................23
7.3.2 Usage........................................................................................................24

7.4.1 Overview....................................................................................................24
7.4.2 Usage........................................................................................................24
7.5.1 Overview....................................................................................................24
7.5.2 Usage........................................................................................................25
7.6 ALA – Configuring the alarm parameters...............................................................25
7.6.1 Overview....................................................................................................25
7.6.2 Usage........................................................................................................25
7.7 ASE – Alarm Severity Configuration......................................................................26
7.7.1 Overview....................................................................................................26
7.7.2 Usage........................................................................................................26
7.8 LIT – Alarm Log Item..........................................................................................27
7.8.1 Overview....................................................................................................27
7.8.2 Usage........................................................................................................27
7.9 LLN – Alarm Log Length......................................................................................28
7.9.1 Overview....................................................................................................28
7.9.2 Usage........................................................................................................29
7.10 MAR – Minimum Alarm Repetition Cycle..............................................................29
7.10.1 Overview..................................................................................................29
7.10.2 Usage......................................................................................................29
7.11 MNR – Maximum Number of Alarm Retransmissions.............................................30
7.11.1 Overview..................................................................................................30
7.11.2 Usage......................................................................................................30
7.12 NUA – Next Unacknowledged Alarm....................................................................30
7.12.1 Overview..................................................................................................30
7.12.2 Usage......................................................................................................31
7.13 RCA – Repetition Cycle for Alarms......................................................................32
7.13.1 Overview..................................................................................................32
7.13.2 Usage......................................................................................................32
7.14 RLY – Relay Status...........................................................................................33
7.14.1 Overview..................................................................................................33
7.14.2 Usage......................................................................................................33
7.15 RPL - Relay Polarity..........................................................................................33
7.15.1 Overview..................................................................................................33
7.15.2 Usage......................................................................................................33
7.16 RTN – Relay Test On Interval ............................................................................34
7.16.1 Overview..................................................................................................34
7.16.2 Usage......................................................................................................34
7.17 RTF – Relay Test Off Interval .............................................................................34
7.17.1 Overview..................................................................................................34
7.17.2 Usage......................................................................................................34
7.18 ACT ACK – Acknowledge Alarm..........................................................................35
7.18.1 Overview..................................................................................................35
7.18.2 Usage......................................................................................................35
7.19 ACT CLO – Clear Alarm Log...............................................................................35
7.19.1 Overview..................................................................................................35
7.19.2 Usage......................................................................................................35
7.20 ACT TRE – Test relay.........................................................................................36
7.20.1 Overview..................................................................................................36
7.20.2 Usage......................................................................................................36
7.21 LOGDUMP ALARM.............................................................................................36
7.21.1 Overview..................................................................................................36
7.21.2 Usage......................................................................................................36
8 Modem and Communication Settings...........................................................................37
8.1 ADD – SMS Access List.......................................................................................37

8.1.1 Overview....................................................................................................37
8.1.2 Usage........................................................................................................37
8.2 ASC – Address of Service Center .........................................................................38
8.2.1 Overview....................................................................................................38
8.2.2 Usage........................................................................................................38
8.3 CDE – Communications Device Enabled................................................................38
8.3.1 Overview....................................................................................................38
8.3.2 Usage........................................................................................................39
8.4 CSL – Communications Support List ....................................................................39
8.4.1 Overview....................................................................................................39
8.4.2 Usage........................................................................................................39
8.5 DEV – Device type and Communications Method....................................................40
8.5.1 Overview....................................................................................................40
8.5.2 Usage........................................................................................................40
8.6 DDS – Device Description....................................................................................40
8.6.1 Overview....................................................................................................40
8.6.2 Usage........................................................................................................40
8.7 CMD – Communications Method Description..........................................................41
8.7.1 Overview....................................................................................................41
8.7.2 Usage........................................................................................................41
8.8 LPC – Last Power Cycling of modem.....................................................................41
8.8.1 Overview....................................................................................................41
8.8.2 Usage........................................................................................................41
8.9 MAD – Main Address...........................................................................................42
8.9.1 Overview....................................................................................................42
8.9.2 Usage........................................................................................................42
8.10 MCT – Modem Connect Time..............................................................................43
8.10.1 Overview..................................................................................................43
8.10.2 Usage......................................................................................................43
8.11 MIS – Modem Initialization String.......................................................................43
8.11.1 Overview..................................................................................................43
8.11.2 Usage......................................................................................................43
8.12 MPE – Automatic Power Cycling Enabled..............................................................44
8.12.1 Overview..................................................................................................44
8.12.2 Usage......................................................................................................44
8.13 MPT – Automatic Power Cycling Timepoint...........................................................44
8.13.1 Overview..................................................................................................44
8.13.2 Usage......................................................................................................44
8.14 NCT – Network Connect Time............................................................................45
8.14.1 Overview..................................................................................................45
8.14.2 Usage......................................................................................................45
8.15 PIN – PIN-code for communications device..........................................................46
8.15.1 Overview..................................................................................................46
8.15.2 Usage......................................................................................................46
8.16 PIS – PIN-code Supported by device...................................................................46
8.16.1 Overview..................................................................................................46
8.16.2 Usage......................................................................................................46
8.17 PPO – Primary Port Number...............................................................................47
8.17.1 Overview..................................................................................................47
8.17.2 Usage......................................................................................................47
8.18 ROP – Repeater to OMC password......................................................................47
8.18.1 Overview..................................................................................................47
8.18.2 Usage......................................................................................................47
8.19 SAC – SMS Acknowledge Configuration...............................................................48
8.19.1 Overview..................................................................................................48

8.19.2 Usage......................................................................................................48
8.20 SFT – Secondary Fallback Timer.........................................................................48
8.20.1 Overview..................................................................................................48
8.20.2 Usage......................................................................................................49
8.21 SMC – Address of SMS Service Center................................................................49
8.21.1 Overview..................................................................................................49
8.21.2 Usage......................................................................................................49
8.22 SPO – Primary Port Number...............................................................................50
8.22.1 Overview..................................................................................................50
8.22.2 Usage......................................................................................................50
8.23 SSC – Secondary Service Center........................................................................50
8.23.1 Overview..................................................................................................50
8.23.2 Usage......................................................................................................50
8.24 ACT MDS - Poll for Modem Status .....................................................................51
8.24.1 Overview..................................................................................................51
8.24.2 Usage......................................................................................................51
8.25 ACT RCD – Reset Communications Device...........................................................51
8.25.1 Overview..................................................................................................51
8.25.2 Usage......................................................................................................51
8.26 ACT UPA – Use Primary Address.........................................................................52
8.26.1 Overview..................................................................................................52
8.26.2 Usage......................................................................................................52
8.27 ACCESS MODEM...............................................................................................52
8.27.1 Overview..................................................................................................52
8.27.2 Usage......................................................................................................53
8.28 MODEM...........................................................................................................53
8.28.1 Overview..................................................................................................53
8.28.2 Usage......................................................................................................53
8.29 MP – Modem Power..........................................................................................54
8.29.1 Overview..................................................................................................54
8.29.2 Usage......................................................................................................54
8.30 TRACE MODEM.................................................................................................54
8.30.1 Overview..................................................................................................54
8.30.2 Usage......................................................................................................54
9 Heartbeat Report Configurations.................................................................................55
9.1 HIT – Heartbeat Log Item...................................................................................55
9.1.1 Overview....................................................................................................55
9.1.2 Usage........................................................................................................55
9.2 HLN – Heartbeat Log Length................................................................................56
9.2.1 Overview....................................................................................................56
9.2.2 Usage........................................................................................................56
9.3 HOS – Heartbeat on System Startup...................................................................56
9.3.1 Overview....................................................................................................56
9.3.2 Usage........................................................................................................56
9.4 MRR – Maximum Report Retransmission................................................................57
9.4.1 Overview....................................................................................................57
9.4.2 Usage........................................................................................................57
9.5 RCH – Repetition Cycle for Heartbeats..................................................................57
9.5.1 Overview....................................................................................................57
9.5.2 Usage........................................................................................................58
9.6 RCR – Repetition Cycle for Reports.......................................................................58
9.6.1 Overview....................................................................................................58
9.6.2 Usage........................................................................................................58
9.7 ACT HBT – Request Heartbeat Transmission...........................................................59
9.7.1 Overview....................................................................................................59

9.7.2 Usage........................................................................................................59
9.8 ACT CHB – Clear Heartbeat Log...........................................................................59
9.8.1 Overview....................................................................................................59
9.8.2 Usage........................................................................................................59
9.9 LOGDUMP HEARTBEAT........................................................................................60
9.9.1 Overview....................................................................................................60
9.9.2 Usage........................................................................................................60
10 System ADMINISTRATION and Inventory Management................................................61
10.1 ADC – Active Devices Count...............................................................................61
10.1.1 Overview..................................................................................................61
10.1.2 Usage......................................................................................................61
10.2 DAT – System Date..........................................................................................61
10.2.1 Overview..................................................................................................61
10.2.2 Usage......................................................................................................61
10.3 DDI – Detailed Device Information.....................................................................62
10.3.1 Overview..................................................................................................62
10.3.2 Usage......................................................................................................62
10.4 HDC – Hardware Device Count...........................................................................63
10.4.1 Overview..................................................................................................63
10.4.2 Usage......................................................................................................63
10.5 HDI – Hardware Device Item.............................................................................63
10.5.1 Overview..................................................................................................63
10.5.2 Usage......................................................................................................63
10.6 HWV - Hardware Version...................................................................................64
10.6.1 Overview..................................................................................................64
10.6.2 Usage......................................................................................................64
10.7 LTG – Lock Tag.................................................................................................64
10.7.1 Overview..................................................................................................64
10.7.2 Usage......................................................................................................65
10.8 MDL – Target Model Identification.......................................................................65
10.8.1 Overview..................................................................................................65
10.8.2 Usage......................................................................................................65
10.9 MDD – Target Model Description.........................................................................66
10.9.1 Overview..................................................................................................66
10.9.2 Usage......................................................................................................66
10.10 MSG - Message Counter..................................................................................66
10.10.1 Overview................................................................................................66
10.10.2 Usage.....................................................................................................66
10.11 RID – Repeater ID..........................................................................................67
10.11.1 Overview................................................................................................67
10.11.2 Usage.....................................................................................................67
10.11.3 XX-YY-ZZZZ............................................................................................67
10.12 SHW – Supported Hardware.............................................................................67
10.12.1 Overview................................................................................................67
10.12.2 Usage.....................................................................................................67
10.13 SIS – System Information String......................................................................68
10.13.1 Overview................................................................................................68
10.13.2 Usage.....................................................................................................68
10.14 SIT – System Initialization Timepoint................................................................69
10.14.1 Overview................................................................................................69
10.14.2 Usage.....................................................................................................69
10.15 SUT – System Uptime.....................................................................................69
10.15.1 Overview................................................................................................69
10.15.2 Usage.....................................................................................................69
10.16 SWV – Software Versions.................................................................................70

10.16.1 Overview................................................................................................70
10.16.2 Usage.....................................................................................................70
10.17 TAG – Repeater Tag........................................................................................71
10.17.1 Overview................................................................................................71
10.17.2 Usage.....................................................................................................71
10.18 TIM – System Time.........................................................................................71
10.18.1 Overview................................................................................................71
10.18.2 Usage.....................................................................................................71
10.19 ACT RHW – Action Reset Hardware...................................................................72
10.19.1 Overview................................................................................................72
10.19.2 Usage.....................................................................................................72
10.20 HARDWARE REPLACE .....................................................................................72
10.20.1 Overview................................................................................................72
10.20.2 Usage.....................................................................................................72
10.21 SYSADMIN – Log in as system administrator......................................................73
10.21.1 Overview................................................................................................73
10.21.2 Usage.....................................................................................................74
10.22 REBOOT – Reboot the system..........................................................................74
10.22.1 Overview................................................................................................74
10.22.2 Usage.....................................................................................................74
11 User Administration and Session Configurations..........................................................75
11.1 LIU – Logged In Users......................................................................................75
11.1.1 Overview..................................................................................................75
11.1.2 Usage......................................................................................................75
11.2 LMT – Login Timeout.........................................................................................75
11.2.1 Overview..................................................................................................75
11.2.2 Usage......................................................................................................75
11.3 MNU – Maximum Number of Users.....................................................................76
11.3.1 Overview..................................................................................................76
11.3.2 Usage......................................................................................................76
11.4 UAC - User Account Count.................................................................................76
11.4.1 Overview..................................................................................................76
11.4.2 Usage......................................................................................................76
11.5 UAI - User Account Item...................................................................................77
11.5.1 Overview..................................................................................................77
11.5.2 Usage......................................................................................................77
11.6 ACT USERADD ................................................................................................77
11.6.1 Overview..................................................................................................77
11.6.2 Usage......................................................................................................77
11.7 ACT USERDEL .................................................................................................78
11.7.1 Overview..................................................................................................78
11.7.2 Usage......................................................................................................78
11.8 ACT USERPROMOTE .........................................................................................79
11.8.1 Overview..................................................................................................79
11.8.2 Usage......................................................................................................79
11.9 ACT USERDEMOTE ...........................................................................................79
11.9.1 Overview..................................................................................................79
11.9.2 Usage......................................................................................................80
11.10 ACT PASSWORD ............................................................................................80
11.10.1 Overview................................................................................................80
11.10.2 Usage.....................................................................................................80
11.11 USERADMIN...................................................................................................81
11.11.1 Overview................................................................................................81
11.11.2 Usage.....................................................................................................81
11.12 EXIT.............................................................................................................82

11.12.1 Overview................................................................................................82
11.12.2 Usage.....................................................................................................82
12 AXELL WIRELESS Repeater System Settings...............................................................82
12.1 System Node Identification................................................................................83
12.2 Node Addressing..............................................................................................83
12.2.1 Numeric Addressing...................................................................................83
12.2.2 Serial Number Addressing...........................................................................83
12.2.3 Node ID Addressing...................................................................................84
12.3 Master Slave Common Configurations.................................................................84
12.3.1 DNA – Direct Node Access..........................................................................84
12.3.1.1 Overview...........................................................................................84
12.3.1.2 Usage................................................................................................84
12.3.2 MID – Master ID........................................................................................85
12.3.2.1 Overview...........................................................................................85
12.3.2.2 Usage................................................................................................85
12.3.3 NIN – Node Information.............................................................................85
12.3.3.1 Overview...........................................................................................85
12.3.3.2 Usage................................................................................................85
12.3.4 NNO – Node Number..................................................................................86
12.3.4.1 Overview...........................................................................................86
12.3.4.2 Usage................................................................................................86
12.3.5 NON – Number Of Nodes............................................................................86
12.3.5.1 Overview...........................................................................................86
12.3.5.2 Usage................................................................................................87
12.3.6 NST – Node Status....................................................................................87
12.3.6.1 Overview...........................................................................................87
12.3.6.2 Usage................................................................................................87
12.3.7 SNI – System Node Identification................................................................88
12.3.7.1 Overview...........................................................................................88
12.3.7.2 Usage................................................................................................88
12.3.8 NODES ....................................................................................................88
12.3.8.1 Overview...........................................................................................88
12.3.8.2 Usage................................................................................................88
12.4 Slave Specific Configurations.............................................................................88
12.4.1 DSA – Direct Slave Access..........................................................................88
12.4.1.1 Overview...........................................................................................88
12.4.1.2 Usage................................................................................................88
12.4.2 NLS – Network Login Status........................................................................89
12.4.2.1 Overview...........................................................................................89
12.4.2.2 Usage................................................................................................89
12.4.3 NMC – Node Master Capabilities..................................................................90
12.4.3.1 Overview...........................................................................................90
12.4.3.2 Usage................................................................................................90
12.4.4 RXQ – Status of Received Data Quality.........................................................90
12.4.4.1 Usage................................................................................................90
12.4.5 RQL – Received Data Quality Level...............................................................91
12.4.5.1 Overview...........................................................................................91
12.4.5.2 Usage................................................................................................91
12.4.6 ACT SSP – System Slave Pause...................................................................92
12.4.6.1 Overview...........................................................................................92
12.4.6.2 Usage................................................................................................92
12.4.7 SST – System Slave Statistics.....................................................................92
12.4.7.1 Overview...........................................................................................92
12.4.7.2 Usage................................................................................................92
12.5 Node Master Configurations...............................................................................93

12.5.1 NCO – Node Communications Status............................................................93

12.5.1.1 Overview...........................................................................................93
12.5.1.2 Usage................................................................................................93
12.5.2 NLU – Nodes With Logged In Users..............................................................94
12.5.2.1 Overview...........................................................................................94
12.5.2.2 Usage................................................................................................94
12.5.3 NST – Node Statuses.................................................................................95
12.5.3.1 Overview...........................................................................................95
12.5.3.2 Usage................................................................................................95
12.5.4 NSC – Node Status Configuration ................................................................95
12.5.4.1 Overview...........................................................................................95
12.5.4.2 Usage................................................................................................95
12.5.5 ACCESS NODE..........................................................................................96
12.5.5.1 Overview...........................................................................................96
12.5.5.2 Description ........................................................................................96
12.5.6 NODE .....................................................................................................97
12.5.6.1 Overview...........................................................................................97
12.5.6.2 Description ........................................................................................97
13 Network Configurations............................................................................................98
13.1 DAS – Dynamic Address Status..........................................................................98
13.1.1 Overview..................................................................................................98
13.1.2 Usage......................................................................................................98
13.2 DNS – DNS Address Configurations....................................................................99
13.2.1 Overview..................................................................................................99
13.2.2 Usage......................................................................................................99
13.3 EEN – Ethernet Enabled....................................................................................99
13.3.1 Overview..................................................................................................99
13.3.2 Usage.....................................................................................................100
13.4 GWY – Default Gateway..................................................................................100
13.4.1 Overview................................................................................................100
13.4.2 Usage.....................................................................................................100
13.5 MAC – MAC address........................................................................................101
13.5.1 Overview................................................................................................101
13.5.2 Usage.....................................................................................................101
13.6 NID – Network Interface Descriptions...............................................................101
13.6.1 Overview................................................................................................101
13.6.2 Usage.....................................................................................................101
13.7 NIL – Network Interface List............................................................................102
13.7.1 Overview................................................................................................102
13.7.2 Usage.....................................................................................................102
13.8 NIC – Network Interface Configuration .............................................................102
13.8.1 Overview................................................................................................102
13.8.2 Usage.....................................................................................................102
13.9 NRS – Network Restart....................................................................................104
13.9.1 Overview................................................................................................104
13.9.2 Usage.....................................................................................................104
13.10 SSR – Supported Services..............................................................................104
13.10.1 Overview..............................................................................................104
13.10.2 Usage...................................................................................................104
13.11 SRV – Service Configurations.........................................................................105
13.11.1 Overview..............................................................................................105
13.11.2 Usage...................................................................................................105
13.12 IFCONFIG....................................................................................................106
13.12.1 Overview..............................................................................................106
13.12.2 Usage...................................................................................................106

13.13 PING...........................................................................................................106
13.13.1 Overview..............................................................................................106
13.13.2 Usage...................................................................................................106
13.14 TRACEROUTE...............................................................................................107
13.14.1 Overview..............................................................................................107
13.14.2 Usage...................................................................................................107
13.15 NETWORK ...................................................................................................107
13.15.1 Overview..............................................................................................107
13.15.2 Usage...................................................................................................107
14 GPRS CONFIGURATIONS........................................................................................107
14.1 GPR – GPRS attribute......................................................................................107
14.1.1 GPR AAD – Authorization address..............................................................107
14.1.1.1 Overview.........................................................................................107
14.1.1.2 Usage..............................................................................................108
14.1.2 GPR ACL – Authorization Client..................................................................108
14.1.2.1 Overview.........................................................................................108
14.1.2.2 Usage..............................................................................................108
14.1.3 GPR APN – Access Point Name...................................................................109
14.1.3.1 Overview.........................................................................................109
14.1.3.2 Usage..............................................................................................109
14.1.4 GPR APPLY – Apply changes made to the GPRS configurations.......................109
14.1.4.1 Overview.........................................................................................109
14.1.4.2 Usage..............................................................................................109
14.1.5 GPR ASC – Authorisation Secret.................................................................110
14.1.5.1 Overview.........................................................................................110
14.1.5.2 Usage..............................................................................................110
14.1.6 GPR ASV – Authorization server.................................................................111
14.1.6.1 Overview.........................................................................................111
14.1.6.2 Usage..............................................................................................111
14.1.7 GPR ATH – Authentication method.............................................................111
14.1.7.1 Overview.........................................................................................111
14.1.7.2 Usage..............................................................................................111
14.1.8 GPR CHANGES – Changes made in GPRS configuration ................................112
14.1.8.1 Overview.........................................................................................112
14.1.8.2 Usage..............................................................................................112
14.1.9 GPR CPI – CHAP Interval..........................................................................113
14.1.9.1 Overview.........................................................................................113
14.1.9.2 Usage..............................................................................................113
14.1.10 GPR CTY – GPRS connection type.............................................................113
14.1.10.1 Overview........................................................................................113
14.1.10.2 Usage............................................................................................113
14.1.11 GPR EXF – GPRS extra flags....................................................................114
14.1.11.1 Overview........................................................................................114
14.1.11.2 Usage............................................................................................114
14.1.12 GPR MDS – GPRS modem dial string.........................................................115
14.1.12.1 Overview........................................................................................115
14.1.12.2 Usage............................................................................................115
14.1.13 GPR MDT – Modem timeout.....................................................................115
14.1.13.1 Overview........................................................................................115
14.1.13.2 Usage............................................................................................115
14.1.14 GPR MRU – Maximum Receive Unit...........................................................116
14.1.14.1 Overview........................................................................................116
14.1.14.2 Usage............................................................................................116
14.1.15 GPR MTU – Maximum Transmission Unit....................................................117
14.1.15.1 Overview........................................................................................117

14.1.15.2 Usage............................................................................................117
14.1.16 GPR PTR – Persistence timer....................................................................118
14.1.16.1 Overview........................................................................................118
14.1.16.2 Usage............................................................................................118
14.1.17 GPR RTE – Default route enable...............................................................118
14.1.17.1 Overview........................................................................................118
14.1.17.2 Usage............................................................................................118
14.1.18 GPR STATUS – Reports status of GPRS interface ........................................119
14.1.18.1 Overview........................................................................................119
14.1.18.2 Usage............................................................................................119
14.1.19 GPR RESTART – Restart GPRS .................................................................119
14.1.19.1 Overview........................................................................................119
14.1.19.2 Usage............................................................................................119
14.2 GPRS – Handle GPRS functionality....................................................................120
14.2.1 Overview................................................................................................120
14.2.2 Usage.....................................................................................................120
14.2.2.1 GPRS CONFIGURE – GPRS Configurations Wizard..................................120
14.2.2.2 GPRS DOWN – Perform a GPRS detatch...............................................120
14.2.2.3 GPRS UP – Perform a GPRS attach .....................................................120
14.2.2.4 GPRS APPLY – Apply changes made to GPRS settings.............................121
14.3 TRACE GPRSDEBUG – Debug GPRS attach ........................................................121
14.3.1 Overview................................................................................................121
14.3.2 Usage.....................................................................................................121
15 Firmware Upgrade.................................................................................................121
15.1 Overview.......................................................................................................121
15.2 Upgrade Procedure.........................................................................................122
15.3 Upgrading Fibre Optic Repeaters ......................................................................123
15.4 Firmware Command Reference.........................................................................123

1 OVERVIEW
Axell Wireless network elements* equipped with a controller contains a Local
Maintenance Terminal (LMT) port, and optionally a modem. This allows for
configuration of the element locally and optionally remotely.
Using a terminal emulation software, such as HyperTerminal (Windows) or MiniCom

(Linux/Unix) it is possible to configure the equipment using a simple command
structure (terminal emulation should be set to VT100 or ANSI).
Axell Repeater Command and Attributes documentation consists of two parts;
– the Common part defines all functionality available for all Axell repeaters with
the new generation of controllers (H40 and H50 series).
– the Target part defines all commands and attributes available for the specific
repeater type in a separate document.
This document specifies the functionality for all commands and attributes available
in the H40 and H50 controllers common parts, i.e. the functionality that is common
to all repeaters and nodes, regardless of the target implementation.
* Network elements are for instance repeaters, Optical Master Units etc.
2 AXELL WIRELESS VERSUS AVITEC

Summer of 2007 Avitec AB (Sweden) and Aerial Facilities Ltd (UK) joined forces to
form Europe's largest manufacturer of coverage solution equipment.
During winter 2008 the companies were brought together under one common
name, Axell Wireless.
However, since the base of this firmware was designed before companies were
merged, certain places in the firmware still mentions Avitec, such as the login
screen and the prompt. Yet, the product is sold, marketed and supported via Axell
Wireless and it's sales and support organisation.
3 VERSION COMPATIBILITY
Commands and attributes described in this document refers to Common firmware
1.2.1.
Firmware version of the controller can be obtained (once logged in) by using the
attribute SWV.
4 USING COMMANDS AND ATTRIBUTES

When logged in to the repeater, a number of different commands and attributes are
available. Commands have interaction with the user, or displays the reply on
multiple rows, while attributes are worked on using GET, SET or ACT syntax which
gives a reply normally on a maximum of one row.
Read-only attributes are read using GET.

Example:
AVITEC AB> GET MDL
MBF-D-9-18
AVITEC AB>
Read and write attributes are either read or written

Example:
AVITEC AB> GET TAG
Repeater Name: Earl
AVITEC AB> SET TAG Site at Sundbyberg Centrum
AVITEC AB> GET TAG
Site at Sundbyberg Centrum
AVITEC AB>
Actions are used to perform actions.

Example:
AVITEC AB> ACT RCD
AVITEC AB>
which resets the communications device/modem.
5 BUILT IN HELP SYSTEM
5.1 HELP command

By entering the command
HELP
a list of all attributes and their modes of operation are displayed in alphabetic order.
Three different columns are displayed. First column is the actual attribute. Second
column displays valid attribute access methods.
r – this means attribute can be GET
w – this means attribute can be SET
x – means attribute can be worked on with ACT (action).
Each row ends with a brief description of the attribute.
Example:
AVITEC AB>help
ACK x Acknowledges alarm log entries.
ACL rw Displays and changes default alarm classes.
ADC r Returns number of active devices in the system.
ADD rw Configures SMS access list to communicate with the repeater.
AGC r This displays status of the AGC in uplink and downlink.
AL1 r Displays alarm configurations for EX1, EX2, EX3, EX4 and DOO.
AL2 r Displays alarm configurations for VLI, LGO, CLR, FWU and FWF.
ALA rw Used for reconfiguration of the alarm settings / thresholds.
ALL r Replies with the same information as in the heartbeat sent to the
AEM.
...
5.2 INF command

The INF attribute gives detailed information about a specific attribute (similar to
information in this document).

Example:
AVITEC AB> INF DOO
This read-only attribute displays the status of the door, 0=OK, 1=ERROR.
Reply format:
X
Example:
GET DOO
Replies:
0
6 EXTERNAL ALARMS, DOOR AND CONTROLLER

TEMPERATURE
Depending on configuration, the repeater might be equipped with an external alarm
interface, allowing to monitor external alarm inputs and optionally the door status.
This section documents attributes related to that functionality.
6.1 CTM – Controller Temperature
6.1.1 Overview
This read-only attribute replies with current temperature in Celsius, and can be
used for production verification. A comprehensive reply for each target is
implemented in the target specific ALV attribute.
6.1.2 Usage
Reply format:
X
where X is reply in degrees Celsius with one decimal point.

Example:
GET CTM
Reply:
-23.7
meaning that current temperature is -23.7 degrees Celsius

Reply:
42.8
means current temperature is +42.8 degrees Celsius.

6.2 DOO – displays status of the door alarm source
6.2.1 Overview
This read-only attribute displays the status of the door, and is read from the alarmd
shared memory.
6.2.2 Usage
Reply format:
X

Example:
GET DOO
Replies:
0
6.3 DST – displays status of the door
6.3.1 Overview
This read-only attribute displays the current status of the door, and can be used to
speed up testing of the repeater or to show actual door status in the RMC as
opened or closed, regardless of if door status is in error.
6.3.2 Usage
Format:
X
where
X is actual door status.
Reply = 0 means door is closed, while 1 means door is open.
Example:
GET DST
Reply:
1
means door is currently open.
6.4 EAC – External alarm configuration
6.4.1 Overview
This read and write attribute displays and configures usage of the external alarm

descriptions.
6.4.2 Usage
The External Alarm Configuration is used in conjunction with the EAD attribute to
configure what additional text is transmitted together with alarms EX1-EX4.

GET EAC
Replies:
XYZW
where
X is configuration for EX1
Y is configuration for EX2
Z is configuration for EX3
W is configuration for EX4
X, Y, Z, W = 0 means that default text will be attached to alarms EX1-EX4, and
X, Y, Z, W = 1 means that text entered in corresponding External Alarm Description
will be attached to the alarm message transmitted to the Axell Element Manager.
Example:
GET EAC
Replies:
0010
means that default alarm message is used in external alarm 1,2 and 4, while
external alarm three will have text as configured with SET EAD 3 attached to the
alarm message.
SET EAC XYZW
where X, Y, Z, W configures the usage for alarm description for external pin 1,2, 3
or 4.
Example:
SET EAC 1100
configures EX1 and EX2 to attach alarm description as configured with SET EAD to
the alarms transmitted to the Axell Element Manager.
6.5 EAD – External alarm description
6.5.1 Overview
This read and write attribute displays and configures the external alarm
descriptions.
6.5.2 Usage
The External Alarm Description allows for giving each external alarm input a unique
tag. This allows for easier information about what is connected to each alarm input.
Optionally (as configured using attribute EAC), this tag can be included in the
additional text field for the alarms transmitted to the repeater OMC.


GET EAD X
where X indicates the alarm description for external pin 1,2, 3 or 4.

Example:
GET EAD 3
Replies:
UPS Power Failure
meaning that external alarm 3 description is “UPS POWER FAILURE”.

SET EAD X [Alarm Pin Description]
where X indicates the alarm description for external pin 1,2, 3 or 4.

[Alarm Pin Description] is the actual description for this alarm source. Maximum
length of string is 35 characters including any spaces.
Example:
SET EAD 4 Radio Hut Door
sets the alarm description for external alarm pin 4 to Radio Hut Door
Note! Any extra spaces between words will be removed, ensuring that only one
space separates each word in the alarm pin description. If extra spaces are required
between words, the description can be put in double quotes, such as
SET EAD 2 “Description with many spaces”
6.6 EST – External Input Status
6.6.1 Overview
This read-only attribute displays the current status of the external alarm input pins,
and is mainly used for advanced trouble shooting and production test. The actual
levels are displayed without any mapping to the EXT attribute.
6.6.2 Usage
Format:
X Y Z W
where
X is level on external alarm pin 1.
Y is level on external alarm pin 2.
Z is level on external alarm pin 3.
W is level on external alarm pin 4.
Reply = 0 means input on pin is 0, while 1 means input is high.
Example:
GET EST
Reply:
0 1 1 0
means that pins 3 and 4 have high inputs while pin 1 and 4 have low inputs.

6.7 EX1 – status of external alarm input 1
6.7.1 Overview
This read-only attribute displays the status of the external alarm input 1.
6.7.2 Usage
Reply format:
X

Example:
GET EX1
Replies:
0
6.8 EX2 – displays status of external alarm input 2
6.8.1 Overview
6.8.2 Usage
Reply format:
X

Example:
GET EX2
Replies:
0
6.9.1 Overview

6.9.2 Usage
Reply format:
X

Example:
GET EX3
Replies:
0
6.10.1 Overview
6.10.2 Usage
Reply format:
X

Example:
GET EX4
Replies:
0
6.11 EXT – External alarm pin configuration
6.11.1 Overview
This read and write-attribute configures if absence or presence of signal should
cause an alarm on the external alarm inputs.
6.11.2 Usage
This read and write attribute configures the polarity of the external alarm inputs.
Format:
X Y Z W
X is configuration for alarm pin 1

Y is configuration for alarm pin 2

Z is configuration for alarm pin 3

W is configuration for alarm pin 4
0 means that no voltage is the OK state, i.e. a voltage applied to the pin generates
an alarm
1 means that applied voltage is the OK state, i.e. absence of voltage generates an
alarm
Note! If the pin is not used for alarm input, the configuration should be ‘0’.
Example:
GET EXT
Replies:
0 0 1 0
means that pin 3 normally should have a voltage applied, and that the other pins
either normally should NOT have a voltage applied, or are not in use.
Example:
SET EXT 0 0 1 1
Configures alarm pins 1 and 2 to report OK if no voltage is available, and pin 3 and
4 to require a voltage applied in order to be in OK state.
7 ALARM CONFIGURATIONS
This section defines all attributes used to configure each individual alarm source. It
also describes attributes related to the relay output / summary alarm which is used
in certain repeaters.
7.1 ACL – Alarm Class Configuration
7.1.1 Overview
This attribute allows for reconfiguration of the default alarm classes.
7.1.2 Usage
This attribute allows for reconfiguration of the default alarm classes.
Format on setting alarm class:

<attribute> <class>
<attribute> is the alarm attribute to configure, such as DOO, EX1 etc

<class> is one of the X.733 and X.721 alarm classification, and can be any of the
following
CO – meaning that this is a communications related command.
QS – indicates that the alarm affects quality of service.
PR – this alarm class is normally associated with software or processing faults.
EQ – equipment alarms means that something is wrong with the actual hardware.
EN – environmental alarm types indicates that the alarm is related to the enclosing
or surroundings of the equipment.
Examples:
SET ACL DOO EN

configures the door alarm to be an environmental alarm.

SET ACL PW1 EQ
configures the PW1 alarm source to be an alarm related to equipment failure.

GET ACL PDL
Reply:
QS
means that PDL alarm affects quality of service on the equipment.
Note! Axell Wireless equipment is always delivered with recommended alarm

configurations, why reconfiguring the alarm class should only be performed under
special circumstances, except for the EX1-EX4 alarms, which are implementation
specific.
7.2 AC1 – Compressed Alarm Severity and Alarm Class

Configurations
7.2.1 Overview
A compact message retrieving alarm severity and alarm class for a number of alarm
sources.
7.2.2 Usage
This is a compact message to retrieve Severity and Class of the different alarm
sources EX1, EX2, EX3, EX4, DOO, VLI, LGO, CLR, FWU, FWF, UAD, UDE, UPM,
UDM, UPW and RXQ.
Format:
<SevEX1> <ClassEX1> <SevEX2> <ClassEX2> .. <SevRXQ> <ClassRXQ>
Example:
GET AC1
Replies:
CR EN CR EN CR EN CR EN WA EN WA EN WA EN MI EN WA PR WA PR WA PR WA PR WA PR WA EN
which are the severities and classes for the alarm sources EX1..RXQ.
Note! The alarm severities and alarm classes can also be read and set with
commands
GET/SET ASE
and
GET/SET ACL
7.3 AL1 - Compressed Alarm Format
7.3.1 Overview
A compact message retrieving alarm configurations for EX1, EX2, EX3, EX4 and

DOO.
7.3.2 Usage
This is a compact message of the alarm configuration strings. This attribute replies
with the configuration of the alarm sources EX1, EX2, EX3, EX4 and DOO.
The use of the attribute is mainly to increase the speed of repeater installations into
the Axell Element Manager and to present parameters in the Repeater Maintenance
Console.
Example:
GET AL1
Replies:
2 0 4 0 0 3 2 0 4 0 0 3 2 0 4 0 0 3 2 0 4 0 0 3 2 0 4 0 0 3 10 2 0 1 -30 60 3
which are the alarm configuration strings received as if using the commands
GET ALA EX1
GET ALA EX2
GET ALA EX3
GET ALA EX4
GET ALA DOO
GET ALA TEM
For a detailed description of the different alarm attributes and alarm strings, please
refer to attribute ALA.
7.4.1 Overview
A compact message retrieving alarm configurations for VLI, LGO, CLR, FWU, FWF
and RXQ.
7.4.2 Usage
Same as attribute AL1, but replies with configuration for alarm sources VLI, LGO,
CLR, FWU, FWF and RXQ.
7.5.1 Overview
A compact message retrieving alarm configurations for UAD, UDE, UPM, UDM and
UPW.

7.5.2 Usage
Same as attribute AL1, but replies with configuration for alarm sources UAD, UDE,
UPM, UDM and UPW.
7.6 ALA – Configuring the alarm parameters
7.6.1 Overview
This attribute allows for reading and writing of the alarm configurations.
7.6.2 Usage
This attribute configures the alarm measurements and alarm handling on an

attribute by attribute basis.
Format:
<attribute> <enab> <ack> <usage> <lower> <upper> <time>
<attribute> is the alarm source to configure, such as TEM, EX1 etc.

<enab> has double functionality. It determines whether an alarm should be send if
error is detected, and it also configures whether the alarm relay should be affected
by the alarm source.
<enab> = 0 means alarm transmission enabled, but alarm doesn’t affect the relay
output
<enab> = 1 means alarm transmission disabled, and does not affect the relay.
<enab> = 2 means alarm transmission is enabled, and alarm affects the relay
output.
<enab> = 3 means alarm transmission is disabled, but alarm affects relay output
<ack> determines whether an alarm requires to be acknowledged or not.

<ack> = 0 means Acknowledge required
<ack> = 1 means No acknowledge required
When using circuit switched data, an alarm is considered acknowledged when the
repeater has successfully logged in to the OMC, and delivered the alarm. In case of
SMS, an alarm is considered acknowledged when an acknowledge message is
received from the main address or when delivered to the SMSC, depending on
configuration in the SAC attribute. The alarms can also be acknowledged with the
command ACT ACK when logged in locally or remotely. If an alarm is not
acknowledged, it will be retransmitted up to MNR (maximum number of
retransmissions) times, with RCA (repetition cycle for alarms ) minute’s interval.
Refer to attributes MNR and RCA on how to configure these settings.
<usage> is a threshold indicator, indicating how thresholds are used for this
particular alarm source.
<usage> = 1 means that both thresholds are used for alarm calculation.
<usage> = 2 means that lower threshold is used
<usage> = 3 means that upper threshold is used
<usage> = 4 means that thresholds are ignored, i.e. digital measurement.

Note! Changing <usage> parameter will change the way the alarm source is
measured. In order to avoid erroneous system behaviour, this parameter should
never be changed.
<lower> is the value of the lower threshold used for alarm calculation.
<upper> is the value of the upper threshold used for alarm calculation.
<time> is the time an alarm has to be in erroneous state before an alarm is

triggered.
Example:
GET ALA TEM
Returns:
0 0 1 -15 60 5
This means that alarm is enabled and acknowledge required. Both thresholds are
used in measuring the alarm, lower threshold is -15 (degrees), 60 (degrees) is the
upper threshold and that the temperature has to be higher than 60 for 5 seconds
before an alarm is triggered.
Example:
SET ALA TEM 0 0 1 0 60 20
Modifies the above alarm source to generate an alarm when the temperature has
been above 60 degrees or below 0 degrees for more than 20 seconds.
7.7 ASE – Alarm Severity Configuration
7.7.1 Overview
This attribute allows for reconfiguration of the alarm severity.
7.7.2 Usage
This attribute allows for reconfiguration of the default alarm severity on an attribute
by attribute basis..
Format on setting alarm severity:

<attribute> <severity>
<attribute> is the alarm attribute to configure, such as DOO, EX1 etc

<severity> is one of the X.733 specified alarm severities, and can be any of the
following:
CR – A Critical alarm is an alarm which affects the functionality of the equipment.

This type of alarm requires immediate action.
MA – A Major alarm can cause degradation of the equipment functionality and

should be investigated within a short time.
MI - A Minor alarm should be investigated but is not urgent.
WA – The Warning severity level indicates that something has occurred that does
not affect the operation of the equipment but may be important to notice. For

example, someone has logged on to the system.
Examples:
SET ASE DOO WA
configures the door alarm to have severity level Warning

SET ASE PW1 CR
configures the PW1 alarm to be a Critical alarm.

GET ASE EX1
Reply:
MI
means that EX1 alarm severity level is configured as Minor.
Note! Axell Wireless equipment is always delivered with recommended alarm

configurations, why reconfiguring the alarm severity should only be performed
under special circumstances, except for the EX1-EX4 alarms, which are
implementation specific.
7.8 LIT – Alarm Log Item
7.8.1 Overview
This attribute returns information about entries in the alarm log.
7.8.2 Usage
This attribute returns an entry in the alarm log,

Format:
GET LIT <ItemNo>
Reads alarm log entry number <ItemNo> from the alarm log, where the oldest
entry in the alarm is number 1. <ItemNo> might be from 1 to value replied by GET
LLN.
Reply format in NON Node Masters:
<Alarm Time> <Alarm Date> <System Event Number> <Attribute> <Hardware Enum> <Position
Identifier> <Alarm Status> <Severity> <Class> <Ack> <Retransmissions Left>
<Completed At Time> <Completed At Date> <Additional Text>
<Alarm Time> - Time on the format HHMMSS when alarm occurred.

<Alarm Date> - Date on the format DDMMYY when alarm occurred
<System Event Number> - Unique identifier for the system event in the interval
0..231.
<Attribute> - Attribute name identifying alarm type, i.e. DOO, TEM, EX1 etc.
<Hardware Enum> - Unique identifier for the hardware being the originator of the
alarm, such as HIB1, LUL2, FDM1 etc. If not used, a '-' (dash) is reported.
<Position Identifier> - Unique identifier for the position within hardware being the
originator of the alarm. Can also contain user information in case of alarms VLI,
LGO, CLR and ILI.
<Alarm Status> - this determines the actual status of the measurement. 0 means
OK, 1 means ERROR. If parameter is not used, a '-' (dash) is reported.
<Severity> - Alarm Severity, which is one of CR (Critical), ID (Indeterminate), WA
(Warning), MA (Major), MI (Minor), CL (Cleared / Alarm Ceased).

<Class> - Alarm Class, which is one of EN (Environmental), EQ (Equipment), CO

(Communications), PR (Processing) or QS (Quality of Service)
<Ack> - Indicates whether alarm is acknowledged or not. 0 = No, 1 = Yes
<Retransmissions Left> - Number of Retransmissions Left before giving up to try
transmitting alarm to the AEM.
<Completed At Time> - Time on the format HHMMSS when alarm was successfully
transmitted to the OMC. If alarm is not yet delivered, a '-' (dash) is replied.
<Completed At Date> - Date on the format DDMMYY when alarm was successfully
<Additional Text> - A quoted string containing additional information about the
alarm, such as “Current out level is +26 dBm”.
Reply format in Node Masters:

<Originating Node> <Alarm Time> <Alarm Date> <System Event Number> <Attribute>
<Hardware Enum> <Position Identifier> <Alarm Status> <Severity> <Class> <Ack>
<Retransmissions Left> <Completed At Time> <Completed At Date> <Additional Text>
<Originating Node> - indicates node that alarm was generated on. Node Master is
always node zero.
0..231.
LGO, CLR and ILI.
Note! If no log entry exists in log at this position, a single '-' (dash) is replied.
7.9 LLN – Alarm Log Length
7.9.1 Overview
This replies with number of alarms in alarm log at the moment.

7.9.2 Usage
Format:
<Number of alarm log entries>
where <Number of alarm log entries> is an integer indicating how many alarms are
currently in the alarm log.
Example:
GET LLN
Returns:
89
meaning that there are 89 alarms that can be read out from the alarm log, starting
with log item 1.
7.10 MAR – Minimum Alarm Repetition Cycle
7.10.1 Overview
This attribute defines minimum time that must elapse between two concurrent
alarms from the same alarm source.
7.10.2 Usage
If there is an alarm toggling between OK and ERROR, the controller will

continuously send alarms to the Axell Element Manager, with the new alarm
detected, and then directly end of alarm, causing the communications interface
between the controller and the AEM to be blocked for a long time. If lots of alarms
are received at the AEM, the operator must be able to send a message to disable
the particular alarm at the controller until service of the unit has been performed.
The Minimum Alarm Repetition Cycle takes care of this problemby defining a
minimum time between two consecutive alarms from the same alarm source.
Typically the MAR should be set to a minimum of two or three times the time it
takes for the controller to report the alarm to the OMC.
Format:
<Minimum Alarm Repetition>
<Minimum Alarm Repetion> is an integer representing number of minutes between

each alarm. Allowed interval is from 0 (disabling this functionality) to 99 minutes.
Example:
GET MAR
Reply:
3
meaning that the minimum time between two consecutive alarms is three minutes.
Example:
SET MAR 4
changes this interval to four minutes.

Note! The first error will always be detected with the normal threshold time, only
the repeated alarms will be blocked/delayed.
7.11 MNR – Maximum Number of Alarm Retransmissions
7.11.1 Overview
This attribute defines how many consecutive retransmissions will be attempted
when trying to transmit alarms to the Axell Element Manager.
7.11.2 Usage
Format:
<Max Retransmissions>
where <Max Retransmission> indicates maximum number of retransmissions for

each alarm. When using circuit switched data, an alarm is considered acknowledged
when the repeater has successfully logged in to the OMC, and delivered the alarm.
In case of SMS, an alarm is considered acknowledged when an acknowledge
message is received from the main address or when delivered to the SMSC,
depending on configuration in the SAC attribute. Every alarm is sent to the OMC up
to MNR number of times, or until it is acknowledged. The alarms are retransmitted
with RCA minutes intervals. The alarms can also be acknowledged with the
command ACT ACK when logged in locally or remotely.
Example:
GET MNR
Reply:
3
means that each alarm will be retransmitted up to three times.

Example:
SET MNR 4
changes maximum number of retransmissions to 4.
Note! When setting the MNR parameter, all non acknowledged alarms have their
corresponding alarm retransmission counter cleared, i.e no more attempts will be
made to transmit alarms from the alarm log.
7.12 NUA – Next Unacknowledged Alarm
7.12.1 Overview
This attribute returns information about the first/oldest non-acknowledged alarm in
the alarm log, still having retransmissions left before giving up trying to transmit
the alarm.

7.12.2 Usage
This attribute returns an entry in the alarm log on the same format as the LLN
attribute, with an additional leading Alarm Log Item number, identifying at what
position in the alarm log this item is available.
Format:
GET NUA
Reads alarm log for the oldest entry not being acknowledged.
Reply format for NON-Node Masters:
<Log Item#> <Alarm Time> <Alarm Date> <System Event Number> <Attribute> <Hardware
Enum> <Position Identifier> <Alarm Status> <Severity> <Class> <Ack> <Retransmissions
Left> <Completed At Time> <Completed At Date> <Additional Text>
<Log Item#> - Position in the alarm log where this alarm message currently is
available (this might vary over time, as new alarms might arrive during the login
session).
0..231.
LGO, CLR and ILI.
Reply format for Node Masters:

<Log Item#> <Originating Node> <Alarm Time> <Alarm Date> <System Event Number>
<Attribute> <Hardware Enum> <Position Identifier> <Alarm Status> <Severity> <Class>
<Ack> <Retransmissions Left> <Completed At Time> <Completed At Date> <Additional
Text>
<Log Item#> - Position in the alarm log where this alarm message currently is
available (this might vary over time, as new alarms might arrive during the login
session).
<Originating Node> - indicates node that alarm was generated on. Node Master is
always node zero.

0..231.
LGO, CLR and ILI.
Note! If no log entry exists in log, a single '-' (dash) is replied.
7.13 RCA – Repetition Cycle for Alarms
7.13.1 Overview
This attribute configures the interval in minutes between each consecutive attempt
to send non-acknowledged alarms to the Axell Element Manager.
7.13.2 Usage
Every alarm is sent to the OMC up to MNR number of times, or until it is

acknowledged. The alarms are retransmitted with RCA minutes intervals. When
using circuit switched data, an alarm is considered acknowledged when the
repeater has successfully logged in to the OMC, and delivered the alarm. In case of
SMS, an alarm is considered acknowledged when an acknowledge message is
received from the main address or when delivered to the SMSC, depending on
configuration in the SAC attribute. Every alarm is sent to the OMC up to MNR
number of times, or until it is acknowledged. The alarms are retransmitted with
RCA minutes intervals. The alarms can also be acknowledged with the command
ACT ACK
when logged in locally or remotely.

Format:
<Repetition Cycle>
<Repetition Cycle> is the interval in minutes between each consecutive attempt to

send alarms to the Axell Element Manager.

Example:
GET RCA
Reply:
10
meaning that the interval between retransmissions is 10 minutes.

Example:
SET RCA 12
sets the interval to 12 minutes
7.14 RLY – Relay Status
7.14.1 Overview
This attribute can be used to readout what system status the relay reflects.
7.14.2 Usage
By reading this attribute, the system status as reported according to relay

configurations can be read out.
Format:
<Status>
<Status> is 0 or 1
0 means no alarms configured to activate relay is detected.
1 means that ne or more of the alarms configured to activate the relay is detected.
Please refer to attribute attribute RPL for details on configuration of relay polarity
(active open or active closed).
7.15 RPL - Relay Polarity
7.15.1 Overview
This attribute configures whether one or more error conditions in the system should
open or close the relay circuitry.
7.15.2 Usage
This attribute is used to configure how the relay circuitry should treat an error
condition.
Format:
N
N is 0 or 1
0 means that a detected error closes the relay circuit (relay is active closed)
1 means that a detected error opens the relay circuit (relay is active open)
Example:

SET RPL 1
configures the controller to open the relay circuit in case a failure is detected.
SET RPL 0
configures the controller to close the relay circuit in case a failure is detected.
7.16 RTN – Relay Test On Interval
7.16.1 Overview
This parameter is used for special test purposes and configures the On time during
relay testing.
7.16.2 Usage
In order to test the external relay output it is possible to force a test procedure,
causing the relay to be turned off for a while, then turned on and finally turned off
again during a configured interval before going back to the original state. This
attribute configures number of seconds the relay should be in ON-state during the
test phase.
Format:
<On-time>
where <On-time> is the number of seconds in on state.

Example:
GET RTN
Reply:
10
means that the relay is in on state for 10 seconds.

Example:
SET RTN 5
changes this value to 5 seconds.
7.17 RTF – Relay Test Off Interval
7.17.1 Overview
This parameter is used for special test purposes and configures the Off time during
relay testing.
7.17.2 Usage
In order to test the external relay output it is possible to force a test procedure,
causing the relay to be turned off for a while, then turned on and finally turned off
again during a configured interval before going back to the original state. This
attribute configures number of seconds the relay should be in OFF-state during the

test phase.
Format:
<Off-time>
where <Off-time> is the number of seconds in off state.

Example:
GET RTF
Reply:
3
means that the relay is in off state for 3 seconds.

Example:
SET RTF 2
changes this value to 2 seconds.
7.18 ACT ACK – Acknowledge Alarm
7.18.1 Overview
This action acknowledges alarm log entries, causing them not to be transferred to
the Axell Element Manager.
7.18.2 Usage
Attribute type: Write-Only Action
This action acknowledges entries in the alarm log and requires Read and Write
access when logged in. Via SMS, this can only be performed by the Main Address.
Format:
ACT ACK <SysEvent>
X is alarm log entry having system event numberssage number <SysEvent>, which
might be a number in the interval 0..231.
Example:
ACT ACK 197
acknowledges alarm with system event number 197
Note! No reply is given to this action (unless a illegal command or system failure
occurs). This means that acknowledging non existing alarms or alarms already
being acknowledged is possible.
7.19 ACT CLO – Clear Alarm Log
7.19.1 Overview
Executing this action clears the alarm log.
7.19.2 Usage

This action clears all alarms from the alarm log, and requires Read and Write access
when logged in. Via SMS, this can only be performed by the Main Address.
7.20 ACT TRE – Test relay
7.20.1 Overview
This action initiates a procedure to test the relay circuit.
7.20.2 Usage
For installation testing purposes, it is possible to test the open / close function of
the relay. This test procedure makes sure the relay is closed for a configurable
number of seconds seconds, then opens for a configurable number of seconds, and
finally closes for configurable seconds before going back to original state. Please
refer to attribbutes RTF and RTN for configuratio details.
This action requires Read and Write access when logged in. Via SMS, this can only
be performed by the Main Address.
Example:
ACT TRE
will initiate a relay circuit test, where default values are OFF for 3 seconds, ON for
10 seconds and finally OFF for 3 seconds again.
Note! During this test interval, the relay connection will be unaffected by all
alarms.
7.21 LOGDUMP ALARM
7.21.1 Overview
This command generates a list of alarms.
7.21.2 Usage
By using the command LOGDUMP ALARM, it is possible to read out alarms from the
alarm logs. The format of each line is the same as read out using the LIT attribute.
Format:
LOGDUMP ALARM <Start> <Stop>
where
<Start> is the first entry that should be read from the log, <Start> must be
greater than 0.
<Stop> is the last entry that should be read from the log, and must be greater
than or equal to <Start>.
Example:
LOGDUMP ALARM 15 20
Reply:

040820 020100 375 EX1 CTRL - 1 WA EN 0 -1 000001 010170 "Error on external alarm 1"
033023 020100 374 UDE - testing 1 WA PR 0 3 000001 010170 "User testing deleted from
system."
032932 020100 373 LGO - useradmin 1 WA EN 0 3 000001 010170 "User logged out"
032910 020100 372 VLI - useradmin 1 WA EN 0 3 000001 010170 "User logged in from IP
126.1.24.163"
032854 020100 371 UPW - useradmin 1 WA PR 0 3 000001 010170 "Password changed for
useradmin by user root"
032643 020100 370 VLI - avitec 1 WA EN 0 3 040813 020100 "User logged in from IP
126.1.24.163"
Note 1! A maximum of 100 log items can be read out at a time. If item does not
exist, no reply is given.
Note 2! If this is a node master, LIT will contain a leading node number, indicating
what node this alarm was originated on. Node master is always node number zero.
8 MODEM AND COMMUNICATION SETTINGS

This section describes all attributes related to modem settings and remote
communication parameters.
8.1 ADD – SMS Access List
8.1.1 Overview
This attribute configures what numbers are allowed to communicate with the
repeater using SMS.
8.1.2 Usage
When SMS is used for communication, addresses 1 to 4 indicates addresses that

are allowed to read and write attributes from the controller. All addresses have read
access to the controller, but only address one and two can set parameters and
perform ACT commands.
Reply format:
1 X 2 Y 3 Z 4 W
X is address 1, Y address 2, Z address 3 and W is address 4. If no address is

available, a ‘-‘(dash) is replied.
Example:
GET ADD
Reply:
1 +46705511125 2 – 3 +46705521334 4 –
Format on setting address:

SET ADD N <MSISDN>
where N denotes which of the addresses from 1-4 that should be configured, and
<MSISDN> is the telephone number to set. Max length of<MSISDN> is 20
characters.
Example:
SET ADD 3 +46705511125
Configures address number three to be +46705511125. When data call

communication is used, this attribute is obsolete.

Note! Using the attribute MAD it is possible to configure which of these four
addresses should receive alarms and reports.
8.2 ASC – Address of Service Center
8.2.1 Overview
This defines the address (MSISDN or IP-address) where to send alarms and reports.
8.2.2 Usage
The address to the service center is where to send alarms and reports, and can be
either a telephone number, or if TCP/IP is used (GPRS or Ethernet), the IP address
or host name of the Axell Element Manager.
Format:
<Address>
where address is a number or server name (if using TCP/IP or GPRS) with a
maximum length of 30 characters.
Example:
GET ASC
Reply:
+46705008999
means that the controller will connect to MSISDN +46705008999 to deliver alarms
and reports (assuming data call is used for remote communication). The controller
can optionally call a secondary OMC address in case message is undeliverable to
the ASC address. Please refer to attribute SSC attribute for details.
Example:
SET ASC axell_element_manager
uses the address axell_element_manager address for delivery of alarms and

reports (assuming TCP/IP or GPRS communication and that DNS is configured
properly).
Note! Setting the address to an empty string will disable the sending of alarms to
the Axell Element Manager, while the controller is still available for remote login.
Example:
SET ASC
disables the sending of alarms and reports.
8.3 CDE – Communications Device Enabled
8.3.1 Overview
This attribute enables and disables the remote communication (both incoming and
outgoing).

8.3.2 Usage
Format:
<Enabled>
where <Enabled> = 1 means that remote communication is enabled, and

<Enabled> = 0 means remote communication is disabled.
Example:
GET CDE
Reply:
0
means remote communication is disabled.

Example:
SET CDE 1
enables remote communication with method as configured by attribute DEV.
8.4 CSL – Communications Support List
8.4.1 Overview
This presents a list of all communication devices and corresponding supported
communication methods available in the controller.
8.4.2 Usage
This attribute produces a reply with all communication methods available over each
device.
Format:
<Dev1:Method1> <Dev1:Method2> ... <DevM:MethodN>
where Dev1..DevM enumerates all the modem types supported by the system, and
Method1..MethodN denotes the different communication methods supported by this
is one token, and each field is separated by space. If no modems supporting data
call are available, a '-' (dash) is replied.
Example:
GET CSL
Reply:
MC45:DTC MC45:SMS MC45:GPRS ETH:TCP
means that the modem MC45 available on this controller supports DataCall, SMS,
GPRS, and that the controller contains an Ethernet device, which can transmit
alarms and reports using a normal TCP connection to the AEM. By using the
attribute DDS, a textual description of the device type can be obtained, and by
using the attribute CMD a textual description of the communications method can be
obtained.

8.5 DEV – Device type and Communications Method
8.5.1 Overview
This determines and configures the device type and communications method for
remote communications to and from the controller.
8.5.2 Usage
This attribute handles the device and method used for remote communication to
the Axell Element Manager.
Format:
<Device>:<Method>
where <Device> denotes what communications device should be used, and

<Method> informs about the communications method used.
Example:
GET DEV
Reply:
MC55:SMS
meaning that communications device used is the MC55 module, and that SMS is
used for alarm and report transmission.
Example:
SET DEV MC55:DTC
changes this to use Data Call over the MC55 module.
Note! Use attribute CSL to determine all combinations of <Device> and <Method>
supported by the system.
8.6 DDS – Device Description
8.6.1 Overview
This returns a string with a textual description of the device type as supplied in the
GET message.
8.6.2 Usage
This attribute replies with a textual description of a device type. This can be used to
get more detailed information about the current modem / device type used for
remote communication.
Format:
GET DDS <Device>
Reply:
<Device Description>

where <Device> is a valid device type supported by the system and <Device
Description> is a textual description of the device.
Example:
GET DDS TRM-1
Reply:
TrioRail GSM-R Module
which in detail describes the device type.
8.7 CMD – Communications Method Description
8.7.1 Overview
This returns a string with a textual description of the communication method as
supplied in the GET message.
8.7.2 Usage
This attribute replies with a textual description of a communications method. This

can be used to get more detailed information about the current communications
method used for remote communication.
Format:
GET CMD <Method>
Reply:
<Method Description>
where <Method> is a valid communications method supported by the system and

<Method Description> is a textual description of the method.
Example:
GET CMD DTC
Reply:
DataCall/Circuit Switched Data using modem connection.

which in detail describes the communications method.
8.8 LPC – Last Power Cycling of modem
8.8.1 Overview
This attribute is used to determine last power cycling of the modem.
8.8.2 Usage
The controller can be configured to automatically turn off and turn on the modem
once per day. This feature can be used to ensure that the modem parameters when
using for example GSM modems contain the latest network parameters such as HLR
update interval etc.

This attribute displays when last power cycling of the modem was performed.
Format:
HHMMSS DDMMYY
HHMMSS is the time point, with 24 hours notation, and DDMMYY is the date when
last modem power cycling (more precisely last modem power ON) was performed.
Example:
GET LPC
Reply:
201300 110503
indicating that the modem was last power cycled on 11’th of May 2003 at 20:13.
Attribute MPE is used to configure if automatic modem power cycling should be
enabled. Timepoint for when to power cycling the modem can be set with attribute
MPT.
In order to perform an instant modem power cycling, please refer to attribute ACT
RCD.
8.9 MAD – Main Address
8.9.1 Overview
Main address configures which address from the SMS access list should receive
alarms and reports.
8.9.2 Usage
When SMS is used for communication, the controller contains a list of four
addresses that are allowed to read and write attributes from the controller (refer to
attribute ADD for a description of how to modify the list). All addresses have read
access to the controller, but only address one and two can set parameters and
perform ACT commands. However, alarms and reports are always sent to the main
address.
Main Address select which one of the four addresses in the list is the main address.
Format:
<Main Address>
<Main Address> is a selector from 1 to 4.

Example:
GET MAD
Reply:
3
means that address number three is the main address.

Example:
SET MAD 2
changes main address to two.

Note! When communication is done via Data Call (refer to attribute DEV), attribute
MAD is obsolete.

8.10 MCT – Modem Connect Time
8.10.1 Overview
Used to configure timeout when attempting to setup a modem connection.
8.10.2 Usage
When a repeater is dialling the OMC to deliver an alarm or a report, the controller
will wait up to MCT seconds for the call to be established. If no communication is
established within this time, the call will be hung up.
Format:
<Timeout>
<Timeout> is the maximum connection time in seconds.

Example:
GET MCT
Reply:
45
meaning that the repeater will wait up to 45 seconds for a call to be established.
Example:
SET MCT 50
changes the timeout to 50 seconds.
8.11 MIS – Modem Initialization String
8.11.1 Overview
This is used to configure the modem initialization string.
8.11.2 Usage
In order for some modems to work correctly in a network, they might require
different configurations. The configuration is modified with this attribute.
Format:
<String>
<string> is the actual modem initialization string.

Example:
GET MIS
Reply:
AT+CBST=7,0,1
which is the modem specific modem initialization string.

Example:
SET MIS AT+CBST=71,0,1

modifies the modem initialization string.
Note 1! Modem string must NOT contain any white space (blanks).
Note 2! If logged in remotely, the changes will not take effect until the user logs
out from the controller. As soon as the user logs out and disconnects, the
initialization of the modem will be initiated.
8.12 MPE – Automatic Power Cycling Enabled
8.12.1 Overview
By configuring this, the modem can be automatically power cycled once per day.
8.12.2 Usage
update interval etc. This attribute configures whether automatic power cycling
should be enabled or not.
Format:
<Enabled>
<Enabled> = 1 means modem power cycling is enabled

<Enablde> = 0 means modem power cycling is disabled
Example:
GET MPE
Reply:
1
means that the modem power cycling is enabled.

Example:
SET MPE 0
disables the automatic modem power cycling.

Timepoint for when to power cycling the modem can be set with attribute MPT. In
order to read out modem Power Cycling timepoint, use attribute LPC. In order to
perform an instant modem power cycling, please refer to attribute ACT RCD.
8.13 MPT – Automatic Power Cycling Timepoint
8.13.1 Overview
Configures at what time of the day automatic modem power cycling should be
performed.
8.13.2 Usage

update interval etc. This attribute configures at what timepoint the modem power
cycling should be performed.
Format:
HHMMSS
HH is the hours (in 24 hour notation), MM is minutes and SS is seconds specifying

the modem power cycling timepoint.
Example:
GET MPC
Reply:
010000
means that the modem power cycling is performed att one in the morning.
Example:
SET MPC 160000
configures modem power cycling to be performed at 4 in the afternoon. Enabling /

Disabling of the automatic power cycling can be configured with attribute MPE.
Timepoint for when to power cycling the modem can be set with attribute MPT. In
order to read out Last modem Power Cycling timepoint, use attribute LPC. In order
to perform an instant modem power cycling, please refer to attribute ACT RCD.
8.14 NCT – Network Connect Time
8.14.1 Overview
This configures how long to wait for modem initialization after a modem power up.
8.14.2 Usage
This attribute is used to configure how long to wait before trying to initialize a
modem after power up or a modem power cycle.
Format:
<Timeout>
<Timeout> is in seconds.
Example:
GET NCT
Reply:
15
meaning modem connect time is set to 15 seconds.

Example:
SET NCT 30
sets this time to 30 seconds.

8.15 PIN – PIN-code for communications device
8.15.1 Overview
This configures the PIN code used to unlock the communications equipment.
8.15.2 Usage
Attribute type: Write-Only
This attribute is used to configure the PIN code used to unlock the communications
equipment (GSM modems etc).
Format:
SET PIN XXXXXXXX
XXXXXXXX is a number, up to 8 characters long, representing the PIN code of the

SIM card.
Note! If wrong PIN code is entered, the controller will only try to open it up once.
After that it will not try to lock it up again until the PIN code is changed. This is to
avoid that the SIM card is blocked if wrong PIN code is configured.
8.16 PIS – PIN-code Supported by device
8.16.1 Overview
This attribute is used to determine if configured modem supports SIM PIN-code.
8.16.2 Usage
Reading this attribute displays if the configured modem supports SIM PIN-code. If
PIN-code is supported it can be configured using the attribute SET PIN.
Format:
<Supported>
where <Supported> = 0 means no PIN-code is supported and <Supported> = 1

means modem type does not support PIN-code.
Example:
GET PIS
Reply:
1
means that this modem type supports PIN-code.
Note! Supporting PIN-code does not mean that PIN-code necessarily is required by
SIM, since this can be configured on a SIM by SIM basis.

8.17 PPO – Primary Port Number
8.17.1 Overview
This configures what port number to use on primary address when using TCP/IP.
8.17.2 Usage
This attribute is used together with ASC to build complete connection parameters
when using TCP/IP to connect to the Axell Element Manager.
Attribute configures what port number on the Axell Element Manager should be
connected to.
GET PPO
Reply:
<Port>
where <Port> is the port number that Axell Element Manager on IP address as
defined by attribute ASC is listening on. Valid <Port> values are 1-65 535.
Example:
GET PPO
Reply:
23
meaning that controller will attempt to connect on port 23 on the Axell Element
Manager when delivering alarms and reports.
Example:
SET PPO 4711
changes this port number to 4711.
8.18 ROP – Repeater to OMC password
8.18.1 Overview
This configures what password the controller should use when logging in to the
OMC.
8.18.2 Usage
Attribute type: Write-Only
When the controller is configured for data call, and alarms or reports are to be
transmitted to the repeater OMC / Axell Element Manager, the controller needs to
supply a user name and password. The user name is the equipment ID (attribute
RID), and the password is set with this attribute, ROP.
Format:
<Password>

<Password> is the password, up to 8 characters, no space allowed.

Example:
SET ROP REPEATER
sets the password to REPEATER.
Note! This password should normally be changed from the Element Manager, since
a wrong configured password will cause the login to the Element Manager to fail.
8.19 SAC – SMS Acknowledge Configuration
8.19.1 Overview
This configures in what way alarms sent via SMS should be acknowledged.
8.19.2 Usage
This command affects controllers using SMS for alarm transmission. SAC configures
how the controller determines whether an alarm is acknowledged or not.
Format:
<Val>
<Val> = 0 means that the alarm is considered acknowledged when an acknowledge

message is received from the OMC.
<Val> = 1 means that an alarm is considered acknowledged when the alarm is
successfully transmitted to the Short Message Service Center (SMSC), i.e. when the
message is successfully delivered to the network.
Example:
GET SAC
Reply:
0
meaning that the controller requires an acknowledge message back from the OMC
(if the individual alarm source is configured for that).
Example:
SET SAC 1
changes the behavior to consider the alarm acknowledged when the message is
sent successfully to the SMSC.
Note! This configuration will work in conjunction with the other alarm attributes
(ALA XXX, RCA and MNR). If for example SAC is set to “1”, and RCA is set to 3 and
MNR 3, the controller will try to send the message to the SMSC center up to 3 times
with 3 minute intervals. If the individual alarm source is configured to not require
an acknowledge, it will only try to send it once to the SMSC.
8.20 SFT – Secondary Fallback Timer
8.20.1 Overview
This defines after how long the controller should fall back primary AEM address in

case switched over to secondary address.
8.20.2 Usage
This configures how many minutes the controller will wait before going back to the
primary address again after calling the secondary OMC address. If this parameter is
set to zero, no fallback will be done, i.e., the controller will toggle between the
addresses for every failure to deliver messages.
See also attributes SSC, ASC and command ACT UPA.
Format:
<Time>
<Time> is number of minutes to wait before fall back to primary OMC address, and
allowed interval is from 0 to 1440 minutes.
Example:
GET SFT
Reply:
15
meaning that the controller will use the secondary address for 15 minutes before
going back to primary/normal OMC address.
Example:
SET SFT 10
changes this value to 10 minutes.
8.21 SMC – Address of SMS Service Center
8.21.1 Overview
This configures the address of the SMS Center when using SMS for remote
communication.
8.21.2 Usage
When using SMS for alarming purposes, it is necessary to configure the address of
the Short Message Service Center, which is a network node to which all messages
are sent before being transmitted to its final destination. The SMSC is an MSISDN
number which is written to the communications equipment during initialization.
Format:
<Address>
where address is a number with a maximum length of 20 characters.

Example:
GET SMC
Reply:
+46705008990
meaning that the secondary address is set to +46705008990.

Example:

SET SMC +46705008999
changes the SMSC address to +46705008999.
8.22 SPO – Primary Port Number
8.22.1 Overview
This configures what port number to use on secondary address when using TCP/IP.
8.22.2 Usage
This attribute is used together with SSC to build complete connection parameters
when using TCP/IP to connect to the Axell Element Manager.
Attribute configures what port number on the Axell Element Manager should be
connected to.
GET SPO
Reply:
<Port>
where <Port> is the port number that Axell Element Manager on IP address as
defined by attribute SSC is listening on. Valid <Port> values are 1-65 535.
Example:
GET SPO
Reply:
1025
meaning that controller will attempt to connect on port 1025 on the Axell Element
Manager when delivering alarms and reports.
Example:
SET SPO 8087
changes this port number to 8087.
8.23 SSC – Secondary Service Center
8.23.1 Overview
Used to configure the backup OMC address in case it is not possible to contact
primary address.
8.23.2 Usage
When controller is configured for data call or if TCP/IP is used (GPRS or Ethernet),
and the controller fails to connect to the primary service center (configured with the
attribute ASC), the controller will automatically switch over to the secondary service

center address. If secondary address is not set, it will be neglected. Furthermore, if

controller experiences problems connecting to secondary address, it will switch
back to primary address. A fallback timer can be configured so that the controller
goes back to primary address after a specified interval (please refer to attribute SFT
for details).
Format:
<Address>
where address is a number or server name (if using TCP/IP or GPRS) with a
maximum length of 30 characters.
Note! The controller will always check if first address is set. If not, the secondary
address will be ignored.
Example:
GET SSC
Reply:
118118
meaning that the secondary address is set to 118118.

Example:
SET ASC backup_aem_address
uses the address backup_aem_addres for delivery of alarms and reports (assuming
TCP/IP or GPRS communication and that DNS is configured properly).
Example:
SET SSC
Disables the use of a secondary address.
8.24 ACT MDS - Poll for Modem Status
8.24.1 Overview
This command is used to poll the modem with pre-configured modem strings.
8.24.2 Usage
To be implemented in later versions.
8.25 ACT RCD – Reset Communications Device
8.25.1 Overview
This command forces a power cycling of the communications device / modem.
8.25.2 Usage
This command is used to perform a power cycle of the modem. In case command is
launched when logged in remotely, the power cycling will be performed after after
the next logout.
Format:

ACT RCD [Delay]
where the optional delay parameters denotes how many seconds from entering the
command the modem should be power cycled. If Delay is left out, an immediate
power cycling of the modem will be performed (assuming local login).
Example:
ACT RCD
will, if logged in locally, perform an immediate power cycling of the modem.
Note! The controller can also be configured to automatically turn off and turn on
the modem once per day. This feature can be used to ensure that the modem
parameters when using for example GSM modems contain the latest network
parameters such as HLR update interval etc. Attribute MPE is used to configure if
automatic modem power cycling should be enabled. Time point for when to power
cycling the modem can be set with attribute MPT. In order to read out Last modem
Power Cycling time point, use attribute LPC.
8.26 ACT UPA – Use Primary Address
8.26.1 Overview
This forces an immediate fall back to dial primary AEM address in case of alarms or
reports.
8.26.2 Usage
The controller can be configured to use both primary and the backup address (as
configured with attribute ASC and SSC) for delivery of alarms and reports to the
Axell Element Manager. In case connection to the first address fails, the controller
automatically attempts to connect to the secondary address instead. Using the
attribute SFT (Secondary fall back Timer) it is possible to configure after how long
the controller will go back to the primary address again. By using this attribute it is
possible to force an immediate fall back to the primary address again. This can for
example be used if the primary address has been down for any reason to force all
network elements to go back to primary address again.
Format:
ACT UPA
causes the immediate fall back to the primary address.
Note! Executing this action when controller is already dialing primary address has
no effect.
8.27 ACCESS MODEM
8.27.1 Overview
This command can be used for advanced trouble shooting of the modem
configurations.

8.27.2 Usage
When typing ACCESS MODEM, the controller will send all the characters typed
directly out the modem port. All characters replied back from the modem will be
presented directly to the user. This command is useful for advanced remote
communication trouble shooting issues.
Format:
ACCESS MODEM [-B Baud Rate]
where the optional switch -B allows to connect to the modem using any of the
standard baud rates 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 or
230400.
Using other baud rates than the default will only work if modem is configured for
this speed or is using auto bauding.
If the modem is busy dialing to the Axell Element Manager, or if someone is logged
in remotely to the repeater, the controller will attempt to access the modem for a
limited amount of time before giving up. This might also happen if the controller is
busy initializing the modem. If this is the case, it is normally possible to access the
modem again after a short while.
To abort an ACCESS MODEM session, press three ‘-‘ in a row (all three within one
second) to come back to the repeater command prompt.
Note 1! When accessing the modem port the modem might be configured with
“echo off”, meaning that the characters entered will not be echoed back to the
screen. In order to enable “echo”, press Enter. After that, type
ATE1
(invisible), followed by Enter. The modem should then reply with

OK
indicating that the echo is enabled. All characters entered will now be echoed back
to the user.
Note 2! Command will not work when logged in to the controller remotely over the
modem connection, since modem is busy communicating.
8.28 MODEM
8.28.1 Overview
This command gives an overview of the actual modem settings.
8.28.2 Usage
By launching the command MODEM, all modem configuration settings are
displayed.

8.29 MP – Modem Power
8.29.1 Overview
This command enables or disables the modem power.
8.29.2 Usage
For trouble shooting purposes it is possible to disable or enable the power to the
modem by using the commands
MP OFF
and
MP ON
Note 1! Since controller regularly polls the status of the modem, it will power up
and initialize the modem in case it is left without powered.
Note 2! Use this command with extreme caution, since it will kick out any remotely
logged in users, or disconnect any remote connections to the Axell Element
Manager.
8.30 TRACE MODEM
8.30.1 Overview
This command gives a trace of the modem initialization procedure.
8.30.2 Usage
For troubleshooting purposes it is possible to trace the actual progress of initializing
the modem. This trace is useful when having problems with the modem
initialization.
For example, when remote initialization is enabled (SET CDE 1), it is useful to see
that modem registers properly onto the network.
To abort TRACE MODEM session, press Ctrl-C.
Example:
AVITEC AB>set mis at+cbst=71,0,1
AVITEC AB>trace modem
Starting modem trace.
To abort, press Ctrl-C.
------------------------------------------------------
Modem initialization completed successfully!
Modem initialization string changed, re-initializing modem.
Initializing modem...
Disabling modem echo...
Modem echo successfully disabled.
Checking PIN status...
SIM already unlocked.
Checking Network Registration...
Registered on home network.
Initializing modem specific parameters....
Sending modem initialization string at+cbst=71,0,1
Modem initialization completed successfully!

9 HEARTBEAT REPORT CONFIGURATIONS

This section defines all attributes related to the heartbeat transmissions of the
repeater.
9.1 HIT – Heartbeat Log Item
9.1.1 Overview
This attribute returns information about entries in the heartbeat log.
9.1.2 Usage
This attribute returns an entry in the heartbeat log,

Format:
GET HIT <ItemNo>
Reads heartbeat log entry number <ItemNo> from the heartbeat log, where the
oldest entry in the heartbeat log is number 1. <ItemNo> might be from 1 to value
replied by GET HLN.
Reply format in NON Node Masters:
<Heartbeat Time> <Heartbeat Date> <System Event Number> <Retransmissions Left>
<Completed At Time> <Completed At Date> <Heartbeat Message>
<Heartbeat Time> - Time on the format HHMMSS when message was generated.
<Heartbeat Date> - Date on the format DDMMYY when message was generated.
0..231.
<Completed At Time> - Time on the format HHMMSS when heartbeat was
successfully transmitted to the OMC. If heartbeat is not yet delivered, a '-' (dash) is
replied.
<Completed At Date> - Date on the format DDMMYY when heartbeat was
replied.
<Heartbeat Message> - A quoted string containing the actual heartbeat message.
Reply format in Node Masters:

<Originating Node> <Heartbeat Time> <Heartbeat Date> <System Event Number>
<Retransmissions Left> <Completed At Time> <Completed At Date> <Heartbeat Message>
<Originating Node> - indicates node that heartbeat was generated on. Node Master
is always node zero.
<Heartbeat Time> - Time on the format HHMMSS when message was generated.
<Heartbeat Date> - Date on the format DDMMYY when message was generated.
0..231.
<Completed At Time> - Time on the format HHMMSS when heartbeat was

replied.
<Completed At Date> - Date on the format DDMMYY when heartbeat was
replied.
<Heartbeat Message> - A quoted string containing the actual heartbeat message.
9.2 HLN – Heartbeat Log Length
9.2.1 Overview
This replies with number of heartbeats in the heartbeat log at the moment.
9.2.2 Usage
Format:
<Number of heartbeat log entries>
where <Number of heartbeat log entries> is an integer indicating how many

heartbets are currently in the heartbeat log.
Example:
GET HLN
Returns:
42
meaning that there are 42 heartbeats that can be read out from the log, starting
with log item 1.
9.3 HOS – Heartbeat on System Startup
9.3.1 Overview
This configures whether an heartbeat should be sent on system startup.
9.3.2 Usage
When the controller is integrated to the Axell Element Manager it sends heartbeat
reports on regular intervals to let the AEM know the repeater is up and running. In
case of a long power failure, or when the equipment has been down for
maintenance, the controller can be configured to send a heartbeat directly on
power on, to ensure that the Axell Element Manager is aware that the system is
back online. In most cases this is handled by the controller sending an end of power
supply alarm, but in certain applications it might be useful to have the controller
sending a heartbeat on system boot.
Format:

<Enabled>
where <Enabled> = 0 means that no heartbeat will be transmitted on startup, and

<Enabled> = 1 means heartbeat will be transmitted on startup.
Example:
GET HOS
Reply:
0
means that no heartbeat will be transmitted on startup.
Example:
SET HOS 1
configures the heartbeat to be transmitted on system startup.
9.4 MRR – Maximum Report Retransmission
9.4.1 Overview
This defines maximum number of retransmissions that will be attempted when
sending reports to the AEM.
9.4.2 Usage
Every report is sent to the Axell Element Manager up to MRR number of times, or
until it is successfully delivered. The reports are retransmitted with RCR minutes
intervals. When using data call, report is considered successfully delivered when the
controller has successfully logged in to the AEM, and delivered the report. In case
of SMS, report is considered successfully delivered when it has been successfully
transmitted to the SMSC.
Format:
<Attempts>
where <Attempts> denotes maximum number of attempts that will be made to

deliver the report. Allowed interval is from 0 to 9 retransmissions.
Example:
GET MRR
Reply:
3
meaning that the repeater will try to retransmit a report 3 times.

Example:
SET MRR 2
sets maximum number of retransmissions to 2.
9.5 RCH – Repetition Cycle for Heartbeats
9.5.1 Overview
The repetition cycle for heartbeats defines with what interval the reports should be

transmitted to the AEM.
9.5.2 Usage
Sets the interval for how often the heartbeat reports are sent to the Axell Element
Manager. The heartbeat report is a report containing all relevant status parameters
of the system. If a report fails to be sent, attempts will be made to retransmit the
reports with a settable interval. Refer to attributes RCR and MRR for information on
how to change the number of retransmissions and retransmit interval.
Format:
<Interval>
<Interval> is the heartbeat interval in minutes. Valid values are from 0 to 100 000
minutes. Setting the interval to 0 (zero) means no heartbeat reports will be
transmitted.
Example:
GET RCH
Reply:
1440
meaning that a heartbeat will be sent to the Axell Element Manager every 1440
minutes (once per day), starting from when last report was successfully transmitted
to the AEM.
Example:
SET RCH 10080
changes this interval to 10080 minutes (once per week)

Note! As soon as the heartbeat interval is changed, and the user is logged out, a
new heartbeat will be sent to the Axell Element Manager in order to cause
resynchronization of the heartbeat intervals between the controller and the AEM.
9.6 RCR – Repetition Cycle for Reports
9.6.1 Overview
This configures with what intervals the controller will attempt to retransmit reports
to the AEM.
9.6.2 Usage
Every report is sent to the Axell Element Manager up to MRR number of times, or
until it is successfully delivered. The reports are retransmitted with RCR minutes
intervals. When using data call, report is considered successfully delivered when the
controller has successfully logged in to the OMC, and delivered the report. In case
of SMS, report is considered successfully delivered when it has been successfully
transmitted to the SMSC.
Format:
<Interval>
where <Interval> is the retransmit interval in minutes. Valid intervals range from 1

to 20 minutes.
Example:
GET RCR
Reply:
3
meaning that after a failed report transmission, a new attept will be made after 3
minutes.
Example:
SET RCR 2
sets the time between retransmissions to 2 minutes.
9.7 ACT HBT – Request Heartbeat Transmission
9.7.1 Overview
This command forces a transmission of a heartbeat report.
9.7.2 Usage
This command is used to transmit heartbeat reports to the Axell Element Manager.
This can be used to force a heartbeat synchronization.
Format:
ACT HBT
caused the heartbeat report to be transmitted as soon as the configured

communications interface is available.
Example:
ACT HBT
will, if logged in locally, perform an immediate connection to the Axell Element

Manager, and the heartbeat report to be delivered.
9.8 ACT CHB – Clear Heartbeat Log
9.8.1 Overview
This command is used to clear all the entries in the heartbeat log.
9.8.2 Usage
This action clears all heartbeats from the heartbeat log, and requires Read and
Write access when logged in. Via SMS, this can only be performed by the Main
Address.

9.9 LOGDUMP HEARTBEAT
9.9.1 Overview
This command generates a list of heartbeat reports.
9.9.2 Usage
By using the command LOGDUMP HEARTBEAT, it is possible to read out heartbeat
report log entries. The format of each line is exactly the same as for the HIT
attribute.
Format:
LOGDUMP HEARTBEAT <Start> <Stop>
where
<Start> is the first entry that should be read from the log, <Start> must be
greater than 0.
<Stop> is the last entry that should be read from the log, and must be greater
than or equal to <Start>.
Example:
LOGDUMP HEARTBEAT 1 5
Reply:
040843 221206 379 -1 000001 010170 "17 14 0 0 0 0 0 0 0 0 0 0 0 0 1111 1440"
030120 231206 367 3 030617 020100 "17 14 0 0 - - - - - 0 - - - - ---- 1440"
030105 241206 366 3 030546 020100 "17 14 0 0 0 0 0 0 0 0 0 0 0 0 1111 1440"
025740 251206 365 0 025916 020100 "17 14 0 0 0 0 0 0 0 0 0 0 0 0 1111 1440"
025718 261206 364 1 025914 020100 "17 14 0 0 0 0 0 0 0 0 0 0 0 0 1111 1440"
which are the 5 latest heartbeat reports.

Note 1! A maximum of 100 log items can be read out at a time. If item does not
exist, no reply is given.
Note 2! If this is a repeater system node master, HIT will contain a leading node
number, indicating what node this heartbeat was collected from. Node master is
always node number zero.

10 SYSTEM ADMINISTRATION AND INVENTORY

MANAGEMENT
This section defines attributes related to system configuration and inventory
management, such as hardware lists and software versions.
10.1 ADC – Active Devices Count
10.1.1 Overview
This attribute returns number of active devices in the system, and is used for
inventory management.
10.1.2 Usage
Active Device Count indicates how many active devices configured in and monitored
by the controller. An active device is a hardware device containing a microprocessor
which is polled by the controller, such as a Power Supply, Reference Generator or
different interface boards.
Format:
<Device Count>
where <Device Count> returns number of active devices in the system .

Example:
GET ADC
Replies:
4
meaning that there are 4 active devices configured in the system. Please refer to
attribute HDI and DDI on how to retrieve information about the different devices.
10.2 DAT – System Date
10.2.1 Overview
Used to get and set the system date.
10.2.2 Usage
The controller contains a real time clock, which is used to keep track of when
certain events occurs, and to be able to send reports on configurable times of the
day. This attribute reads and sets the date of the system clock.
Format:

DDMMYY
where DD=Date, MM=Month, YY=Year

Example:
GET DAT
Replies:
181005
means the repeater date is set to 18’th of October, 2005.

Example:
SET DAT 241205
sets the repeater date to 24’th of December, 2005.

Note! When setting the date, a heartbeat will be sent immediately (or if logged in
via modem, as soon as user logs out), the traffic / uplink activity logs (if supported)
will be cleared and all alarms in the log will have the number of retransmissions of
non-acknowledged alarms set to the value MNR.
10.3 DDI – Detailed Device Information
10.3.1 Overview
This is used to read out details of a device / node that is monitored by the
controller, and is used for inventory management.
10.3.2 Usage
Each node monitored by the controller contains a number of parameters that are
common between all the nodes. This attribute displays all common parameters.
Format:
GET DDI <Device No>
where <Device No> is a number from 1 to max number of attributes (as read out
by ADC attribute).
Format on reply:
<Serial Number> <ArtNo> <SWV> <SW Build Time> <SW Build Date> <Manufacturing Info>
<Module Init Time> <Module Init Date> <Uptime> <HW Reset Counter> <WD Reset Counter>
<Device Description>
where
<Serial Number> is the Serial Number of the device
<ArtNo> is Article Number / Hardware Revision
<SWV> is a string delimited by “ (double quote) signs, containing software version
of the device/node.
<SW Build Time> is a string delimited by “(double quote) signs, containing
software build time.
<SWBuildDate> is a string delimited by “(double quote) signs, software build date.
<ManufacturingInfo> is a string delimited by “(double quote) signs, containing
manufacturing specific information. If no information is available, a ‘-‘is reported.
<ModuleInitTime> contains the repeater initialization time on the format HHMMSS,
with 24 hours notation. If no information is available, a ‘-‘(dash) is reported.
<ModuleInitDate> contains the repeater initialization date on the format DDMMYY.
If no information is available, a ‘-‘(dash) is reported.
<Uptime> shows how many seconds the device has been up and running since last

reset.
<HWResetCounter> shows how many times the device has been started since
device was initialized.
<WDResetCounter> shows how many times the watchdog has forced the device to
reset since device initialization
<Device Description> is a string delimited by “(double quote) signs, containing a
textual description of the hardware device.
Note! If <Device No> is greater than ADC, a single '-' (dash) will be reported.
10.4 HDC – Hardware Device Count
10.4.1 Overview
This attribute returns number of hardware devices in the system, and is used for
inventory management.
10.4.2 Usage
Hardware Device Count indicates how many hardware items are configured in the
system monitored by the controller.
Format:
<Device Count>
where <Device Count> returns number of hardware devices in the system

(including controller itself).
Example:
GET HDC
Replies:
12
meaning that there are 12 hardware devices (both active and passive) configured in
the system. Please refer to attribute HDI on how to retrieve information about the
different devices.
10.5 HDI – Hardware Device Item
10.5.1 Overview
This attribute gives information about the different hardware devices in the system,
and is used for inventory management.
10.5.2 Usage
This command returns device information about a specific device.

Format:
GET HDI <Device No>

<Device No> is from 1 to HDC.
Reply format:
<Serial> <ArticleNo> <Device Information String>
<Serial> is 4 characters containing the device serial number.

<ArticleNo> is the Axell Article Number, up to 12 characters.
<Device Information String> contains a quoted textual description of the hardware
device. String can be up to 40 characters wide.
Example:
GET HDI 1
Reply:
4711 H411001A "Control Module"
which indicates that this is a control module with serial number 4711 and article
number H411001A.
Note! If <Device No> doesn't exist, a dash '-' is replied.
Example:
GET HDI 4000
Reply:
-
10.6 HWV - Hardware Version
10.6.1 Overview
This attribute returns hardware version of the controller.
10.6.2 Usage
Using this attribute it is possible to determine the hardware version of the control
module.
Format:
<Hardware Version>
which is a string identifying hardware version and revision.

Example:
GET HWV
Replies:
H421001C
meaning that the controller version is H121001C.
10.7 LTG – Lock Tag
10.7.1 Overview
This configures if the TAG should be possible to modify or not.

10.7.2 Usage
When commissioning the repeater, the actual site ID is often of high importance,
and is normally configured by using the attribute TAF. During integration of the
repeater into the Axell Element Manager, it is possible to set the TAG from the AEM
itself. By using the attribute LTG (Lock Tag) it is possible to lock the tag from
accidently being modified.
Format:
<Locked>
where <Locked> = 0 means that it is possible to modify the tag, and <Locked> =
1 means that the Tag is locked from modification.
Example:
GET LTG
Reply:
0
means that no tag is unlocked and that it is possible to change the tag.
Example:
SET LTG 1
disables the possibility to change the tag.
10.8 MDL – Target Model Identification
10.8.1 Overview
This attribute returns a string containing the equipment type being monitored by
the controller.
10.8.2 Usage
The model identification string is a unique identifier indicating exactly what kind of
equipment is monitored by the controller. This information is essential for the
Repeater Maintenance Console and for the Axell Element Manager integration to
know exactly what parameters are supported by the controller.
Format:
<Model Identification String>
uniquely identifying the equipment type.

Example:
GET MDL
Reply:
CSFT922-ER
indicating that this is a Channel Selective Frequency Translating 2-channel repeater

for the 900 band of Remote type with External combining.
For a textual description of the equipment model, please refer to attribute MDD.
Note! For detailed information on the different models and their interpretation,
refer to corresponding product manual.

10.9 MDD – Target Model Description
10.9.1 Overview
This attribute returns a textual string, describing the type of equipment being
controlled.
10.9.2 Usage
The target model description replies with a verbose output of the type of equipment
being monitored by this controller.
Format:
<Textual Model Description>
being a string with a maximum length of 140 characters.

Example:
GET MDD
Reply:
Channel Selective EDGE/GSM 4-channel Repeater on 900 MHz band

being a detailed description of the actual equipment type.
10.10 MSG - Message Counter
10.10.1 Overview
This displays the value of the system event counter.
10.10.2 Usage
For each report or alarm being transmitted to the Axell Element Manager, a
message counter is increased, giving each alarm and report a unique system event
number in the system. This attribute displays current value of the counter.
Format:
<Message Counter>
where the <Message Counter> value is from 0 to 231.

Example:
GET MSG
Reply:
16471
indicating that the value of the system event counter currently is 16471.

10.11 RID – Repeater ID
10.11.1 Overview
The repeater ID is a unique identifier for the element within the network, and is set
by the AEM.
10.11.2 Usage
The repeater ID gives the Axell Element Manager a way to give the each network
element a unique number in the network.
Format:
10.11.3 XX-YY-ZZZZ
XX,YY,ZZZZ are unique numbers to identify the element. The length of the repeater
ID is exactly 10 characters.
Example:
GET RID
Reply:
01-01-0334
which is the unique ID for this element.

Example:
SET RID 02-01-0077
Modifies the repeater ID.

Note! If the element is installed into and controlled by the Axell Element Manager,
this attribute should NEVER be modified. This ID is unique in the Element Manager
database. Changing this ID will cause the Axell Element Manager database to be
corrupted, and monitoring of the network element to fail.
10.12 SHW – Supported Hardware
10.12.1 Overview
This attribute informs about some of the supported hardware in the system.
10.12.2 Usage
This attribute displays if certain system functionality is supported by the hardware

configurations. This function is mainly used by Repeater Maintenance Console and
Axell Element Manager to adjust user interface depending on configurations.
Format:
<EX1><EX2><EX3><EX4><DOO><RLY>
where each field can be

0 – meaning that corresponding functionality is not supported by target.

1 – meaning that corresponding functionality is supported by target.
Example:
GET SHW
Reply:
111101
meaning that EX1-EX4 and RLY are supported by target, while DOO is not
supported.
10.13 SIS – System Information String
10.13.1 Overview
This attribute displays miscellaneous information about the controller.
10.13.2 Usage
This compact string containing various controller and system versions and system
dates. The string contains the following data, separated by spaces:
<Boot Ver> <Controller Serial Number> <Ctrl HW Version> <Equipment Serial Number>
<Equipment Art No> <Controller Initialization Time> <Controller Initialization Date>
<System Initialization Time> <System Initialization Date> <Manufacturing specific
information>
<Boot Ver> is a string delimited by “ (double quote) signs, containing the controller
Boot version. If no information is available, an empty string (“”) is replied.
<Controller Serial Number> reports the serial number of the controller (4
characters). If no information is available, a ‘-‘ (dash) is reported.
<Ctrl HW Version> is a string delimited by “ (double quote) signs, containing the
controller hardware version.
<Equipment Serial Number> reports the serial number of the equipment being
controlled (4 characters). If no information is available, a ‘-‘ (dash) is reported.
<Equipment ArtNo> contains the article number of the product in which the
controller is mounted.
<Controller Initialization Time> contains the controller initialization time on the
format HHMMSS, with 24 hours notation. If no information is available, a ‘-‘ (dash)
is reported.
<Controller Initialization Date> contains the controller initialization date on the
format DDMMYY. If no information is available, a ‘-‘ (dash) is reported.
<System Initialization Time> contains the equipment initialization time on the
format HHMMSS, with 24 hours notation. If no information is available, a ‘-‘ (dash)
is reported.
<System Initialization Date> contains the equipment initialization date on the
format DDMMYY. If no information is available, a ‘-‘ (dash) is reported.
<Manufacturing specific information> is a string delimited by “ (double quote)
signs, containing information entered during manufacturing.
Example:
GET SIS
Reply:
“AviBoot 1.02” 42JG H501001A 4JF3 A1013410A 120333 051101 174200 051220 “MWTST”

indicating that Boot version is “AviBoot 1.02”, control module has the serial number
4JG5 and hardware version H501001A, the equipment serial is 4JF3 and article
number A1013410A, the controller was initialized at 12:03.33 on Nov 1, 2005 the
system (equipment) was initialized at 17:42.00 on Dec 20, 2005,. Finally, factory
information is “MWTST”.
10.14 SIT – System Initialization Timepoint
10.14.1 Overview
This displays the time point for initialization when controller/system was first
initialized.
10.14.2 Usage
Returns a string containing the system initialization time, i.e. when the controller
was initialized for the first time.
Format:
HHMMSS DDMMYY
where HHMMSS is the time point, with 24 hours notation, and DDMMYY is the date
of the initialization.
Example:
GET SIT
Reply:
135207 211005
indicating that the controller was initialized on Oct 21 2005, 13:52:07

Note! By supplying the switch -n a numeric reply is given where the time point is
represented in seconds from the 00:00:00 1970-01-01.
Example:
GET SIT -N
Reply:
1129895527
which indicates number of seconds that elapsed from 00:00:00 1970-01-01 until
the system was initialized (which converts to Oct 21 2005, 13:52:07).
10.15 SUT – System Uptime
10.15.1 Overview
This displays the system uptime, which is defined as the time elapsed since last
system startup.
10.15.2 Usage

The system uptime is defined as the time that has elapsed since last system
startup.
Format:
<Uptime>
where <Uptime> is the number of seconds that has elapsed since last system
reset, or since last power up.
Example:
GET SUT
Reply:
10987735
meaning that the system booted up 10 987 735 seconds ago.

Note! By supplying the switch -f a formatted reply is given where the elapsed time
is converted to format
Example:
GET SUT -F
Reply:
127 days, 4:08.55
which indicates an uptime of 127 days, 4 hours, 8 minutes and 55 seconds.
10.16 SWV – Software Versions
10.16.1 Overview
This attribute replies with the different software versions in the system.
10.16.2 Usage
The software system consists of three different software versions.

Format:
<System Version> <Common Version> <Target Version>
where
<System Version> is a quoted string indicating what version of the core system.
<Common Version> is a quoted string displaying the version for the so called
common libraries used.
<Target Version> indicates the version of the target software is configured on the
system.
Example:
GET SWV
Reply:
“1.0.1” “1.1.1” “OnBoard1.1.3”
indicating that system version is 1.0.1, common version is 1.1.1 and the target
version being OnBoard1.1.3.

10.17 TAG – Repeater Tag
10.17.1 Overview
The TAG allows to give each Axell element a textual name in the network.
10.17.2 Usage
The TAG allows for giving each Axell element an easy to understand name within
the network. This can for example be the network site ID or the name of the
location where equipment is installed. By using the attribute LTG (Lock Tag) it is
possible to lock the tag from accidently being modified during for example the AEM
integration.
Format:
<Tag>
where <Tag> is a text string up to 30 characters long.

Example:
GET TAG
Replies:
SiteID:VF37 Sundbyberg Metro
identifying the TAG.
Example:
SET TAG SiteID:VF3777 Sumpan Metro
modifies the tag.

Example:
SET TAG Testing Tag Lock
Reply:
Error: Cannot modify tag, tag locked (unlock using LTG attribute).
Note! Any extra spaces between words will be removed, ensuring that only one
space separates each word in the tag. If extra spaces are required between words,
the description can be put in double quotes, such as
SET TAG “Tag with many spaces”
10.18 TIM – System Time
10.18.1 Overview
Used to get and set the system time.
10.18.2 Usage
The controller contains a real time clock, which is used to keep track of when
certain events occurs, and to be able to send reports on configurable times of the
day. This attribute reads and sets the time of the system clock.

Format:
HHMMSS
where HH is 24-hour representation of the hours, MM is minutes, and SS is

seconds.
Example:
GET TIM
Reply:
145000
meaning the repeater time is 10 minutes to three in the afternoon.

Example:
SET TIM 150542
modifies the time to 15:05.42.

Note! When changing the time, a heartbeat will be sent immediately (or if logged
in via modem, as soon as user logs out), the traffic / uplink activity logs (if
supported) will be cleared and all alarms in the log will have the number of
retransmissions of non-acknowledged alarms set to the value MNR.
10.19 ACT RHW – Action Reset Hardware
10.19.1 Overview
This is used to perform a reset of all active modules monitored by the controller.
10.19.2 Usage
By executing ACT RHW, a hard reset of all active devices monitored by the system
is performed.
Example:
ACT RHW
will cause the software in all active devices to be reset immediately.

Note! Reset of the hardware devices will be almost immediate, and certain radio
devices might cause a short disruption of service, why this command should only be
used with caution.
10.20 HARDWARE REPLACE
10.20.1 Overview
This command is used to reconfigure a system after replacing a physical hardware
device.
10.20.2 Usage
This command is used to change the configuration in a system when a hardware
device has been changed. This is normally performed when replacing a failing
module to ensure that inventory list matches the devices, and to get the
communication between the controller and the hardware to work properly.
Hardware can be of two different kinds:

- Active devices. These devices contains a microprocessor for monitoring of

parameters. Active devices contain the article number and hardware revision in the
device. Typical active devices are radio boards, opto modules, reference generators
etc. The controller communicates with active devices using the device serial number
as an address, why it is important to configure the exact serial number for the
communication to work.
- Passive devices. These do not have a microprocessor, and hence article number
and hardware revision has to be configured manually.
Serial Numbers are always exactly four characters long. Letter 'o' is not used (to
avoid confusion between letter 'o' and digit zero).
Article Numbers are between 8 and 12 characters long. Letter 'o' is not used (to
avoid confusion between letter 'o' and digit zero).
Format on replacing Active devices:

HARDWARE REPLACE <Old Serial> <New Serial>
where <Old Serial> is the serial number of replaced module, and <New Serial> is
the serial number of the new module.
Example:
HARDWARE REPLACE 4711 56AR
replaces serial number of active device with serial number 4711 with a new
hardware having serial number 56AR.
Format on replacing Passive devices:

HARDWARE REPLACE <Old Serial> <New Serial> <New Article Number>
where <Old Serial> is the serial number of replaced module, and <New Serial> is
the serial number of the new module and <New Article Number> is article number
of new hardware.
Example:
HARDWARE REPLACE 540R 56UU J691030A
Each change of hardware is kept in a log. In order to read out the log, use
command
HARDWARE LOG
which displays all hardware changes that has been made to the system, including
local time point for replacement.
Example:
HARDWARE LOG
Reply:
2007-10-12 14:45:35 Replaced active device serial 4711 with 56AR. Device type:
Reference Generator.
2007-10-12 14:50:03 Replaced passive device serial 540R with 56UU article number
J691030A. Device type: External Alarm Interface
Note! In order to read out current hardware configuration, refer to attributes HDC,
HDI, ADC and DDI.
10.21 SYSADMIN – Log in as system administrator
10.21.1 Overview
Enters System Administration mode with full user access to all system aspects

10.21.2 Usage
Certain operations on the controller, such as installing new firmware and rebooting
the system requires system administration privileges.
In order to enter system administration mode, enter command

SYSADMIN
This will prompt for the System Administration password. If entered correctly,
system administration mode is entered.
In order to leave system administration mode, use command

exit
10.22 REBOOT – Reboot the system
10.22.1 Overview
Reboot the controller
10.22.2 Usage
This command is used when rebooting the system. Only system administrator is
allowed to do this, so run command
sysadmin
and enter system administrator password. After this, enter

reboot
to reboot the system.
Rebooting the system normally leaves the system non accessible for roughly 45
seconds. However, RF performance of the equipment will remain fully operational
during that time.
In order to reset hardware devices in the system, please refer to attribute ACT RHW
(reset hardware).

11 USER ADMINISTRATION AND SESSION

CONFIGURATIONS
This chapter defines all commands, attributes and actions related to user
administration and repeater access.
11.1 LIU – Logged In Users
11.1.1 Overview
Gives a list of all users currently logged in to the controller.
11.1.2 Usage
The LIU attribute replies with all list of all users currently logged in to the system.
Format:
<user 1> <user 2> ... <user N>
where all users are separated by a space. If no user is logged in, a '-' is reported.
Example:
GET LIU
Reply:
omcuname zaphod
indicating that users omcuname and zaphod are logged in to the system.
11.2 LMT – Login Timeout
11.2.1 Overview
Indicates after how long inactivity a logged in user should be logged out from the
system.
11.2.2 Usage
If a logged in user does not perform any activity within LMT minutes, the controller
will initiate an automatic logout of the user. This attribute configures the automatic
interval.
Format:
<LMT>
where <LMT> is the interval in minutes of inactivity. Allowed interval is from 1 to

99 minutes.
Example:

GET LMT
Reply:
20
meaning that the user will be logged out after 20 minutes of inactivity.
Example:
SET LMT 15
changes this time to 15 minutes of inactivity before user is automatically logged

out.
11.3 MNU – Maximum Number of Users
11.3.1 Overview
This attribute defines maximum number of users allowed to add to the system.
11.3.2 Usage
This attribute displays maximum numbers of users accounts that can be added to
the system (excluding the omcuname and useradmin account).
Format:
<MaxNo>
where <MaxNo> is an integer defining maximum number of user accounts allowed.

Example:
GET MNU
Reply:
10
meaning that a maximum of 10 user accounts can be added to the system.
11.4 UAC - User Account Count
11.4.1 Overview
This defines number of user accounts that are added to the system.
11.4.2 Usage
Using the UAC attribute it is possible to read out how many user accounts are
currently configured in the system, not including the omcuname and useradmin
accounts.
Format:
<AccountCount>
indicates current number of accounts in the system.

Example:
GET UAC
Reply:

meaning that there are 3 user accounts currently configured in the system, not
including the useradmin and omcuname accounts.
11.5 UAI - User Account Item
11.5.1 Overview
This gives information about a certain user account in the system, including access
level.
11.5.2 Usage
Reading the User Account Items it is possible to get information about all users
added to the system.
Format:
GET UAI <ItemNo>
reads user account entry number <ItemNo> from the user account list, where first
account is 1. <ItemNo> might be from 1 to value replied by GET UAC.
Reply format:
<User Name> <Access Level>
where <User Name> is the login username and <Access Level> replies ReadOnly or
ReadWrite, depending on user previleges.
Example:
GET UAI 5
Reply:
Arthur ReadWrite
which means that user Arthur has ReadWrite access to the system.
11.6 ACT USERADD
11.6.1 Overview
This attribute is used to add users to the system.
11.6.2 Usage
This attribute is used to add a user to the system. Only users “useradmin” and
“omcuname” are allowed to administer users on the system.
Any other user will be prompted for the “useradmin” password when launching
ACT USERADD.
The system has an upper limit for how many user accounts can be added to the
system. Please refer to attribute MNU (Max Number of Users) for details.
Format:
ACT USERADD [-rw] <user name>

where <user name> must be at least 6 characters long. <user name> is case
sensitive, meaning that it is important to differ between upper and lowercase.
Valid user names follow these rules:
* First character must be a letter (a-z, A-Z)
* Allowed characters in the rest of the user name are a-z, A-Z, 0-9 and special
characters '-' (dash), '_' (underscore) and '.' (dot).
* Length of user name must be from 6 is 32 characters.
If command switch -rw is used, the user will be added with read and write access,
otherwise user will be added with read-only access.
In order to escalate user to read and write access at a later stage, use
ACT USERPROMOTE. [user name].
Example 1 , user is not useradmin:
AVITEC AB> ACT USERADD Marvin
Password: *********
User Marvin added.
AVITEC AB>
Example 2, user is useradmin (see USERADMIN command for details):

USERADMIN> ACT USERADD Marvin
Error: User already exists.
USERADMIN> ACT USERADD Zaphod
User Zaphod added.
USERADMIN>
Note 1! When adding the user to the system, the password is not set, and the user
cannot login. In order to activate the account, use command ACT PASSWORD.
Note 2! Adding a user to the system will cause an alarm to be posted to the Axell
Element Manager informing about this new user (except for when omcuname adds
the user).
11.7 ACT USERDEL
11.7.1 Overview
This attribute is used to delete a current user from the system.
11.7.2 Usage
Only users “useradmin” and “omcuname” are allowed to administer users on the
system.
ACT USERDEL.
Format:
ACT USERDEL <user name>
where <user name> is one of the users in the system. <user name> is case
sensitive, meaning that the system differs between uppercase and lowercase
characters.
Users currently logged in to the system cannot be deleted.
Note! Users omcuname and useradmin cannot be deleted from the system.
AVITEC AB> ACT USERDEL Trillian
Password: *********
User Trillian deleted.
AVITEC AB>


USERADMIN> ACT USERDEL zaphod
Error: User does not exist.
USERADMIN> ACT USERDEL Zaphod
User Zaphod deleted.
USERADMIN>
Note! Deleting a user to the system will cause an alarm to be posted to the Axell
Element Manager informing about the removed user (except for when omcuname
deletes the user).
11.8 ACT USERPROMOTE
11.8.1 Overview
Promoting a user means to increase user access from read-only to read-write
access.
11.8.2 Usage
system.
ACT USERPROMOTE.
Format:
ACT USERPROMOTE <user name>
characters.
Note! Users omcuname and useradmin cannot be promoted within the system.
AVITEC AB> ACT USERPROMOTE Arthur
Password: *********
User Arthur promoted to read and write access.
AVITEC AB>

USERADMIN> ACT USERPROMOTE Slartibartfast
USERADMIN> ACT USERPROMOTE slartibartfast
User slartibartfast promoted to read and write access.
USERADMIN>
Note! Promoting a user in the system will cause an alarm to be posted to the Axell
Element Manager informing about this new user access level (except for when
omcuname promotes the user).
11.9 ACT USERDEMOTE
11.9.1 Overview
Demoting a user means to decrease user access from read and write to read-only
access.

11.9.2 Usage
system.
ACT USERDEMOTE.
Format:
ACT USERDEMOTE <user name>
characters.
Users currently logged in to the system cannot be demoted.
Note! Users omcuname and useradmin cannot be promoted within the system.
AVITEC AB> ACT USERDEMOTE Ford
Password: *********
User Ford demoted to read-only access.
AVITEC AB>

USERADMIN> ACT USERDEMOTE FordPerfect
USERADMIN> ACT USERDEMOTE Ford_Perfect
User Ford_Perfect demoted to read-only access.
USERADMIN>
Note! Demoting a user in the system will cause an alarm to be posted to the Axell
Element Manager informing about this new user access level(except for when
omcuname demotes the user).
11.10 ACT PASSWORD
11.10.1 Overview
This is used to change passwords of a user.
11.10.2 Usage
Format on changing own password:

ACT PASSWORD
which will prompt for old password and new password.

Passwords may include any printable characters, but must be at least 5 characters
long.
Example (assuming user Rutger):
AVITEC AB> ACT PASSWD
Changing password for Rutger
Old password:
New password should be at least 5 characters long, and preferably contain a
combination of upper and lower case letters and numbers.
Enter new password:
Re.enter new password:
Password changed.
AVITEC AB>

Format on changing other users password:

ACT PASSWORD [user name]
which will change the password for [user name]. If [user name] is the same as
currently logged in user, this will behave in the same way as changing own
password.
If not being logged in as useradmin, the useradmin password will first be prompted
for, after which the password can be changed.
Example (assuming user is not useradmin):
AVITEC AB> ACT PASSWORD Rutger
User Admin Password: ******
Enter new password:
Re-enter new password:
Password changed.
AVITEC AB>
Example (user is useradmin):

USERADMIN> ACT PASSWORD Rutger
Enter new password:
Re-enter new password:
Password changed.
Note! For user account omcuname, changing passwords have slightly different
behavior.
Format on changing password when user is omcuname:
ACT PASSWORD [user name] [password]
This will change password of the [user name] instantly.

Example (user is omcuname):
AVITEC AB> ACT PASSWORD Rutger Wibba45Res
Password for Rutger changed successfully.
AVITEC AB>
Note! Changing a user password in the system will cause an alarm to be posted to
the Axell Element Manager informing about the changed password. Alarm message
will not include the password itself, but only inform about the change (except for
when omcuname changes the password).
11.11 USERADMIN
11.11.1 Overview
This command is used to escalate rights and run the system with useradmin rights.
11.11.2 Usage
This command is used to enter the system in as user administrator. Running the
controller with useradmin rights is especially useful when configuring many user
accounts in a row to avoid having to enter the useradmin password for each
administration task being performed.
Format:
USERADMIN
will prompt the user for the useradmin password.

Example:

AVITEC AB> USERADMIN

Password:
USERADMIN>
where the prompt indicates that escalating to useradmin was successful.

Note! In order to leave user administration mode use command EXIT.
11.12 EXIT
11.12.1 Overview
This command is used to leave user administration mode.
11.12.2 Usage
This command is used to leave the user administration mode.
Note! Being in user administration mode is indicated by having the prompt
USERADMIN>
rather than the normal

AVITEC AB>
Format:
EXIT
leaves the user administration mode.

Executing the exit command when being in normal user mode will cause an error.
Example:
USERADMIN> EXIT
AVITEC AB>
where the Avitec prompt indicates that the function is exited.

Note! Command LOGOUT might also be used to leave the user administration
mode.
12 AXELL WIRELESS REPEATER SYSTEM

SETTINGS
This chapter defines commands and attributes related to repeaters being masters
or slaves in an Axell Wireless Repeater System.
An Axell Wireless Repeater System contains two different node types:
Node Master is the node containing the communications interface towards the Axell
Element Manager. The node master is responsible for polling all slave nodes for new
alarms and events that should be transmitted to the Axell Element Manager.
Slaves are nodes that does not have an interface towards the Axell Element
Manager. Slaves contain a slave interface allowing for a node master to
communicate with the system slave.
A typical example of an Axell Wireless Repeater System is an Optical Master Unit

(OMU) containing a remote communications device such as a modem, and which
monitors a number of fiber optic fed repeaters using the fiber as a data
communications channel (using a sub carrier in the fiber).

12.1 System Node Identification

Node Masters and Repeater System Slaves can always be identified using the GET
MDL command, where node masters always replies with a trailing -M and system
slaves always replies with a trailing -S.
Example 1:
GET MDL
Reply:
OMU-M
indicating that this is an optical master unit, also being a node master in an Axell
Wireless Repeater System.
Example 2:
GET MDL
Reply:
BSF424-S
indicating that this is BSF424 (Band Selective FiberOptic Fed 400MHz repeater)
acting as a repeater system slave.
As an exception to the above identification, the first generation of Axell Node

Masters, the HUB-unit always replies as:
GET MDL
Reply:
HUB
even though the HUB unit is a node master.
12.2 Node Addressing

When addressing nodes in a Axell Wireless Repeater System, three different
methods can be used:
12.2.1 Numeric Addressing

Each node in the network gets a unique ID-number in the Node List as they are
added to the system. Node 0 is always the master node.
Addressing is on the format
@K
where K is from 0 to N where N is number of nodes.

Reading a parameter from node 3 is entered as:
AVITEC AB> @3 GET ATD
14
AVITEC AB>
12.2.2 Serial Number Addressing

Node can be accessed using the serial number of the node.
Example:
AVITEC AB> @3J34 GET MDL
BSF414
AVITEC AB>

12.2.3 Node ID Addressing

Node can also be addressed using the full Node ID.
Example:
AVITEC AB> @01-01-5S45 GET TAG
SITE3_TUNNEL_OPENING
AVITEC AB>
12.3 Master Slave Common Configurations
12.3.1 DNA – Direct Node Access
12.3.1.1 Overview
Sets the user interface in direct node access to another node in a repeater system.
12.3.1.2 Usage
Attribute type: Write only
This attribute is only used in repeaters / elements being a part of an Axell Wireless
repeater system (this can be determined with command GET SNI).
When many attributes are sent to another node, the user can enter Direct Node
Accessing mode, where the node where the user is logged in redirects all
commands to another node. This mode is configured by sending the command:
SET DNA [Node Address]
where node address can be any of the following addressing modes:

* Numeric Addressing using the node number, such as @3
* Serial Addressing using node serial number, such as @5TTR
* Full Node ID Addressing using the complete node ID, such as @01-10-5TTR
When going into direct node access, the destination address is displayed in the
prompt in the same way as they where addressed, for example
AVITEC AB@5TTR>
Leaving the direct access node is done using the SET DNA command with the node
address left out, or by entering the command EXIT.
AVITEC AB>SET DNA @01-10-5TTR
AVITEC AB@01-10-5TTR>GET DOO
1
AVITEC AB@01-10-5TTR>SET DNA
AVITEC AB>
Other nodes can still be addressed when using the Direct Node Addressing mode.
For example, being at node 3 and having direct node access to node 0, node 5 can
still be accessed:
AVITEC AB>SET DNA @0
AVITEC AB@0>GET ASC
+46705008999
AVITEC AB@0>@3 GET DOO
1
AVITEC AB@0>EXIT
AVITEC AB>

12.3.2 MID – Master ID
12.3.2.1 Overview
If part of an Axell Wireless Repeater System, this displays ID of the master node.
12.3.2.2 Usage
If node is part of an Axell Wireless Repeater System, this attribute replies with the
ID of the master node of the entire system.
Format:
XX-YY-ZZZZ
where XX, YY and ZZZZ are numbers. These numbers are assigned by the Axell
Element Manager during integration of the repeater system to the Axell Element
Manager.
Example:
GET MID
Reply:
01-17-0042
meaning that the node ID for the master unit is 01-17-0042.
Note 1! On node masters, Master ID (MID) is always the same as Repeater ID

(RID).
Note 2! If node is not part of a repeater system, an error message will be

produced:
“Error: Node not part of a repeater system, parameter not supported.”
12.3.3 NIN – Node Information
12.3.3.1 Overview
Displays information about a certain node in an Axell Wireless Repeater System.
12.3.3.2 Usage
This is a read only parameter, returning information about a certain node.

Format:
GET NIN N
N is one of the Node Addressing Modes without the leading @ sign.

Reply format:
<Node Status> <Node Serial Number> <Node Repeater Model> <Node Tag> <Node Software
Version>
<Node Status> is 0 if node is OK, or 1 if node has one or more errors. If node
communication is in error, a ‘-‘ (dash) is reported, indicating that node status is

unknown.
<Node Serial Number> is the serial number of the node / repeater.
<Node Repeater Model> is the repeater model identifier, as replied by attribute
MDL.
<Node Tag> is the name of the node site, as replied by attribute TAG, wrapped in
two “”.
<Node Software Version> replies with the software version of the node controller,
as replied in SWV attribute. This consists of three tokens, all wrapped in two ‘”’.
Example:
GET NIN 1
gets information about node 1.

Reply:
1 56FR BSF424-S “Emergency exit 7” “1.1.0” “1.0.2” “BSF424 1.0.0”
Note! If node is not part of a repeater system, an error message will be produced:
12.3.4 NNO – Node Number
12.3.4.1 Overview
Displays node number for this node in an Axell Wireless Repeater System.
12.3.4.2 Usage
This is a read only parameter determining the node number for this node in an Axell
Wireless Repeater System.
Format:
GET NNO
Reply:
N
N determines this node’s number in the node list

Note 1! For master nodes, this will always reply '0' (zero).
Note 2! If this parameter is read from a slave node and the master has not yet
updated the node, a ‘-‘ is replied.
produced:
12.3.5 NON – Number Of Nodes
12.3.5.1 Overview
This attribute displays number of nodes configured in an Axell Wireless Repeater
System.

12.3.5.2 Usage
This attribute is used in Axell Repeater systems to determine how many nodes are
configured in the Repeater System.
Format:
GET NON
Reply:
N
where N determines the number of nodes configured in the system, including the
master.
Note 1! If this parameter is read from a slave node, and the master has not yet
updated the node, 0 is replied.
produced:
12.3.6 NST – Node Status
12.3.6.1 Overview
Displays summary status for each node configured in an Axell Wireless Repeater
System.
12.3.6.2 Usage
Node status attribute is used to give an overview of the status for all nodes in the
network, including the master unit.
Format:
<Master Status><N1><N2>…<N24>
<Master Status> is the summary status for the Master unit. Status is 0 if node is
OK,or 1 if node has one or more errors.
<Nk> is status for node k. Status is 0 if node is OK or 1 if node has one or more
errors. If node is not installed, or node status is unknown (such as communications
alarm between node master and slave), a ‘-‘ is reported.
Example:
GET NST
Reply:
000100-------------------
This means that the system is configured with 6 nodes, and that slave node number
3 is in error.

12.3.7 SNI – System Node Identification
12.3.7.1 Overview
This parameter can be used to identify if this is a node in an Axell Wireless Repeater
System.
12.3.7.2 Usage
This is a read only parameter that can be used to identify if this is part of an Axell
Wireless Repeater system, or if this is a standalone node.
Format:
GET SNI
Reply:
N
N = ‘-‘ means that this node is NOT part of a repeater system

N = ’M’ means that this node acts as a Master node in a repeater system
N = ‘S’ means that his node acts as a Slave node in a repeater system
12.3.8 NODES
12.3.8.1 Overview
Prints information about all nodes configured in an Axell Wireless repeater system.
12.3.8.2 Usage
nodes is a command printing out configuration for all repeaters in the network.
The Node Master is responsible for informing all repeaters in the repeater system
about status, model and firmware version of all other nodes in the network.
Executing this command on a slave that is not yet integrated to the repeater
network, or that is recently started might report some nodes to be unkown.
12.4 Slave Specific Configurations
12.4.1 DSA – Direct Slave Access
12.4.1.1 Overview
Enables direct access to the slave from the node master.
12.4.1.2 Usage
Attribute Type: Action-Only

When performing advanced configurations on a node, it is sometimes desirable to

have a direct access mode to the node, where all commands are available rather
than just GET, SET and ACT commands.
This attribute pauses the slave from listening to data packets from the master and
launches a login prompt on the slave interface instead.
Format:
ACT DSA
causes the controller to pause the slave interface and launch a login session via the
slave interface instead.
Example:
ACT DSA
Reply:
Direct Slave Access initiated.
displaying that Direct Slave Access is initiated.
Note 1! When running direct access, no alarm polling is made from the master to
any of the slave nodes connected to this bus.
Note 2! If launching the login prompt via slave interface and no login have been
made within one minute, the controller goes back to normal operations again.
Note 3! The inactivity timeout for idle activity when accessing the slave from the
node master is three minutes, meaning that if no activity has been detected during
this time, the slave will go back to normal operation.
Note 4! Please refer to command DIRECT ACCESS on how to obtain direct access
from the node master to the slave.
12.4.2 NLS – Network Login Status
12.4.2.1 Overview
Determines if it is possible to send commands to other nodes in a repeater system.
12.4.2.2 Usage
This attribute determines if Node Master has detected login to this node and
granted access to read and set parameters on other nodes in the repeater network.
Format:
N
where
N=0 means node master has not yet granted us network access, or, if node master
is the HUB unit, someone else is logged in to the network either from a HUB or
from elsewhere in the network. It is not possible to read or write parameters from
other parts of the network.
N=1 means node has granted us access to the network, and it is possible to read or
write parameters from other nodes in the network.
Example:

GET NLS
Reply:
1
means that we have full access to the repeater network, and can get and set
parameters on other nodes.
12.4.3 NMC – Node Master Capabilities
12.4.3.1 Overview
Display capabilities of the Node Master from a communications point of view.
12.4.3.2 Usage
This attribute determines if master unit is a HUB (old) or a new generation Node
Masters with enhanced performance and functionality.
This parameter is used by System Slave to adjust certain parameters and behaviors
to the capabilities of the Node Master.
Format:
N
where
N=0 indicates that Node Master is a HUB unit with first version of controller.
N=1 indicates that Node Master is the enhanced Node Master with capabilities
matching the capabilities of the System Slave.
Example:
GET NMC
Reply:
1
meaning that node master has the full capabilities.
12.4.4 RXQ – Status of Received Data Quality

Displays status of the RXQ alarm source.
12.4.4.1 Usage
The system slave constantly runs statistics on the last 1000 data packets received
from the Node Master, and once per second calculates number of packets with
errors (such as CheckSum errors or illegal length of received data packets). If
percentage of correctly received packets decreases below a configurable threshold,

an RXQ alarm is triggered.
This attribute reply with status of the Received Data Quality alarm source.
Format:
<RXQ>
where
<RXQ> is status of the received data quality.
0 if status is OK
- (dash) if measured data is not available (for example, not sufficient data
available).
Example:
GET RXQ
Reply:
1
indicating that received data packets contains a too high percentage of errors.
12.4.5 RQL – Received Data Quality Level
12.4.5.1 Overview
Displays quality of the received data packets from node master.
12.4.5.2 Usage
The system slave constantly runs statistics on the last 1000 data packets received
from the Node Master, and once per second calculates number of packets with
errors (such as CheckSum errors or illegal length of received data packets). If
percentage of correctly received packets decreases below a configurable threshold,
an RXQ alarm is triggered.
This attribute replies with the last measured level of the Received Data Quality.
Format:
N
where N is the value in % * 10 for valid data packets received.

Example:
GET RQL
Reply:
998
meaning that 99.8% of data packets were error free/correctly received.

12.4.6 ACT SSP – System Slave Pause
12.4.6.1 Overview
This action causes a temporary stop in accepting packets from node master.
12.4.6.2 Usage
This command is used to temporarily stop handling data packets from the node
master, and is mainly used for testing purposes.
Format:
ACT SSP [N]
where the optional parameter N determines number of seconds that the interface
should pause the remote communications.
N is from 1 to 120 seconds. If N is not provided, slave will pause communications
for 5 seconds.
Example:
ACT SSP 12
will pause the system slave interface for 12 seconds.
Note 1! When executing this command, no communication with other nodes in the
network will be possible.
produced:
12.4.7 SST – System Slave Statistics
12.4.7.1 Overview
Displays detailed statistics of the system slave interface.
12.4.7.2 Usage
This attribute replies with statistics on the System Slave, and is mainly intended for
troubleshooting during system setup.
Two different packets can be received by the node, a broadcast, which is sent to all
nodes in the system and a data packet, which his intended for a specific node.
Broadcasts never requires replies back to the master, while all data packets expects
a reply to be transmitted back to the node master (assuming packet destination
was this slave node). For each packet received, a number of error checks are
performed to see that data packets are not corrupted, such as Checksum Errors
and Length Errors.
Format:
<Rx Bytes> <Tx Bytes> <Rx Broadcast> <Rx Data Packets> <Rx Data to me> <CSUM Errors>

<Length Errors> <Other Errors> <Unknown Broadcasts> <Unknown Packets> <Tx Packets>
<Tx Fail> <Throughput> <Last Valid Rx Packet> <Last Tx Packet>
where
<Rx Bytes> is total number of received bytes since slave started.
<Tx Bytes> is total number of transmitted bytes since slave started.
<Rx Broadcast> is total number of received valid broadcasts.
<Rx Data Packets> is total number of valid data packets.
<Rx Data to me> is total number of received data packets addressed to this node.
<CSUM Errors> is total number of packets received, where a checksum error is
detected.
<Length Errors> is total number of packets received where length did not match
expected length.
<Other Errors> is total number of packets received with unspecified errors.
<Unknown Broadcasts> is number of received error free broadcasts where actual
packet format is unknown (typically this is where node master contains a newer
software version with enhanced command structure that slave doesn't understand).
<Unknown Packets> is number of received error free data packets where actual
packet format is unknown.
<Tx Packets> is total number of packets transmitted to the node master.
<Tx Fail> is total number of packets that for some reason failed to be transmitted
to the node master.
<Throughput> is number of packets / second sent by the master with one decimal
resolution.
<Last Valid Rx Packet> is time point of last error free received packet. Time point is
on the format HHMMSS DDMMYY, where time is on 24 hours notation.
<Last Tx Packet> is time point of last successfully transmitted packet to the node
master. Time point is on the format HHMMSS DDMMYY, where time is on 24 hours
notation.
For any parameter not detectable, a '-' is presented in corresponding position,

except time points, which are displayed as 000000 010170.
Example:
123444 10023 1234 2233 839 2 0 0 0 0 839 0 3.4 122334 070507 122331 070507
displaying all statistics as described above.
12.5 Node Master Configurations

This section describes attributes only available when configuring the repeater /
element as a Node Master, monitoring a number of slave nodes in an Axell Wireless
Repeater System
12.5.1 NCO – Node Communications Status
12.5.1.1 Overview
Displays status of communication with nodes.
12.5.1.2 Usage

This attribute replies with status of communication with all nodes in the repeater
system.
Format:
<Node1><Node2>..<Node24>
<NodeX> is the status for communication with node X.

0 means communication is OK
1 means communication failure with node (ERROR).
- (dash) means node is not configured.
Example:
GET NCO
Reply:
00100000----------------
meaning that the system is configured for 8 remote nodes, and that communication
with node 3 is in ERROR state (no contact with node).
Note! If node is not configured as a node master, an error message will be

produced:
“Error: Node not a System Node Master, parameter not supported.”
12.5.2 NLU – Nodes With Logged In Users
12.5.2.1 Overview
Displays what nodes have a user currently logged in to the repeater system.
12.5.2.2 Usage
This attribute gives information about what nodes in the repeater system that
currently has a user logged in.
Format:
<Node1><Node2>..<Node24>
<NodeX> is the login status for node X.
0 means no user is logged in to node.
1 means user logged in to node.
- (dash) means node is not configured or status unknown (communications error
with node).
Example:
00100000----------------
meaning that the system is configured with 8 remote nodes, and that a user is
logged in to node 3.

produced:

12.5.3 NST – Node Statuses
12.5.3.1 Overview
Displays status of all nodes in the network.
12.5.3.2 Usage
Node status attribute is used to give an overview of the status for all nodes in the
network, including the Node Master.
Format:
<Master><Node1><Node2>..<Node24>
<Master> is the summary status for the Master unit and <NodeX> is status for
node X.
0 if status is OK
- (dash) if measured data is not available, or there is a communications error with
node.
Example:
GET NST
Reply:
000100-------------------
This means that the system is configured with Master plus 5 nodes, and that slave
node number 3 is in error.

produced:
12.5.4 NSC – Node Status Configuration
12.5.4.1 Overview
Configures if an error in node status should affect relay and/or LED in Node Master.
12.5.4.2 Usage
Attribute type: Read and write
This attribute is used to configure if status of slave nodes should be reflected in

controller Error LED and / or in controller relay status.
Format:
<LED><Relay>
where
<LED> is 0 means that slave node errors not should be reflected in LED, and 1
means that an error in a slave node should cause the controller Error LED to
indicate an error.
<Relay> is 0 means that slave node errors not should affect the relay output, and 1

means that an error in a slave node should cause the controller relay output to
indicate an error.
Example 1:
GET NSC
Reply:
00
meaning that neither the LED or Relay will affect status in the slave nodes.
Example 2:
SET NSC 01
reconfigures the settings so that an error in a slave node will cause the controller
relay to indicate an error.

produced:
12.5.5 ACCESS NODE
12.5.5.1 Overview
This is used to get a direct access to a system slave such as a fiber optic repeater.
12.5.5.2 Description
Communications between the master and a slave is normally performed using GET,
SET and ACT attribues that are sent between the nodes.
For more advanced troubleshooting and in order to perform firmware upload, it is
required to get a transparent channel between the node master and the system
slave, for example between the OMU and the fiberoptic fed repeater in a fiber optic
repeater system.
Format:
ACCESS NODE <Node Number>
where <Node Number> is any of the node addressing modes (list position, serial or
RepeaterID).
An ACCESS NODE session can always be aborted using the escape sequence
Wait 1 s, three dash within one second and Wait 1 s, which will bring the standard
userprompt back.
However, if logging in is completed into the remote node it is recommended to

perform a logout from the remote node instead. Otherwise the remote node might
stay logged in and cause the node to be unavailable for a while.
Note 1! ACCESS NODE is only available from master nodes to system slaves.
Note 2! When having direct access to a system slave, no communication will occur
to slaves on the same bus, meaning that no alarms will be monitored in the system
until logged out from the system slave.
Example of an ACCESS NODE session

AVITEC AB>access node 2
Use escape sequence <Wait 1s>---<Wait 1s> to abort.
Entering Direct Access mode.

Avitec Controller
Repeater ID: 01-10-624T
1/23/2009 23:43:23
login: avitec
Password:
You are now logged in to the Avitec Control Module.
Time: 23:43:30 Date: 2009-01-23 RID: 01-10-624T Tag: Repeater/Site Name
SYSEVENT: User logged in with full access
AVITEC AB>get mdl
MBF-S-9-S
AVITEC AB>
AVITEC AB>exit
User logged out from Control Module.
Remote node logged out, aborting.

Shutting down connection.
Over and out.
AVITEC AB>access node 2
12.5.6 NODE
12.5.6.1 Overview
Command node is used to add or remove nodes from a master slave system, and
can only be ran on node masters.
12.5.6.2 Description
When setting up a repeater system, the node master needs to have information on
all the nodes in the network.
By using the node command, nodes can be added to or removed from the repeater
system. In order to get an overview of configured nodes in the network, refer to
command nodes.
Format on adding nodes:

NODE ADD <Node Serial> <Bus> <Rack>:<Slot> <Capabilities> [Baud Rate]
where
<Node Serial> is the serial number of the node (controller or repeater / element
serial number) that should be added. Serial Numbers are always exactly four
characters long. Letter 'o' is not used (to avoid confusion between letter 'o' and
digit zero).
<Bus> determines which one of the two data communication channels in the
controller that should be used (refer to target documentation for details). Valid
values are 0 and 1.
<Rack> is used in some targets (such as Optical Master Unit) to specify what
communications device is used for communication with remote node. If not used, a
'-' (dash) should be entered instead.
<Slot> is used in some targets (such as Optical Master Unit) to specify what
communications device is used for communication with remote node.
<Capabilities> is used to determine what kind of network element is to be
monitored. This should be set to 1 for H40/H50-controller based slaves, and 0 for
older slave types (H30/H12-controller based).
[Baud Rate] is an optional parameter that defines what baud rate to use on
communication between node master and actual nodes / slaves. If not supplied,
57600 is assumed. Baud rate is normally configured when adding nodes with
<Capabilities> set to 0, where data rate between node master and slaves is lower.
Example on adding node:

NODE ADD 60FY 0 -:- 1

which adds node 60FY on bus zero. <Slot> and <Rack> are ignored, and
<Capabilities> is set to 1, meaning that node is probably using a H40 or H50 based
controller.
Format on deleting nodes:

NODE DEL | DELETE <Node Identifier>
where <Node Identifier> identifies the node using one of the node addressing
methods (serial number, node number or full Node ID)
Example on deleting node:

NODE DELETE 12
deletes the 12'th node in the node list.
Note 1! Command NODES gives an overview of all commands configured in the

system.
Note 2! If node is not configured as a node master, an error message will be
produced:
“Error: Node not a System Node Master, command not supported.”
13 NETWORK CONFIGURATIONS
Depending on hardware configuration, the controller might be equipped with an
Ethernet interface.
This section describes commands and attributes configure and trouble shoot IP
settings and how to get remote communication to the controller via the network up
and running.
13.1 DAS – Dynamic Address Status
13.1.1 Overview
Determines if an address has been received from the DHCP server or not.
13.1.2 Usage
When configuring an interface for dynamic IP-address (using DHCP), this parameter
indicates if an IP address has been received.
Format:
GET DAS <Interface>
Reply:
<Status>
<Status> = 0 means no address has been received yet.

<Status> = 1 means address is received (and can be read using NIC attribute).
<Status> = '-' (dash) means that interface is not configured for DHCP.
Example:
GET DAS
Reply:

which means that no address has yet been received from the DHCP server.
Note! In order to re-request an IP-address, refer to attribute NRS.
13.2 DNS – DNS Address Configurations
13.2.1 Overview
This displays and configures the DNS server(s).
13.2.2 Usage
Attribute Type: Read and Write
This attribute is used to read and configure the DNS servers for the controller.
Note! If using DHCP for address configuration (as configured using the NIC
attribute), the DNS servers are normally supplied from the DHCP server.

GET DNS
Reply:
<DNS 1> <DNS 2> ... <DNS N>
where
<DNS x> is the IP address to the DNS servers.
Example:
GET DNS
Reply:
192.168.1.45 192.168.1.46
which are the IP-addresses for the two configured DNS addresses.
SET DNS [DNS 1] [DNS 2] [DNS 3]
where
[DNS x] are IP-addresses for the DNS servers on the format X.Y.Z.W
0<X<255, 0<=Y<=255, 0<=Z<=255, 0<W<255.
Up to three different DNS servers can be configured.
Example 1:
SET DNS
clears all DNS server addresses.

Example 2:
SET DNS 192.168.4.177 192.168.4.178 192.168.4.179
configures IP addresses of three DNS servers.
13.3 EEN – Ethernet Enabled
13.3.1 Overview
This attribute enables or disables the Ethernet Interface.

13.3.2 Usage
This attribute configures whether Ethernet interface should be enabled or disabled.

GET EEN
Reply:
<Enabled>
where
Enabled = 0 means Ethernet interface is disabled.
Enabled = 1 means Ethernet interface is enabled.
SET EEN <Enabled>
where
Enabled = 0 disables the Ethernet Interface.
Enabled = 1 enables the Ethernet Interface.
Example:
GET EEN
Reply:
0
meaning that Ethernet Interface is disabled and that no communication can be

established using Ethernet interface.
Example:
SET EEN 1
enables the Ethernet Interface.

Note! Enabling the Ethernet interface still requires proper IP configuration in order
to be able to communicate with the controller over the network.
13.4 GWY – Default Gateway
13.4.1 Overview
This configures the default gateway to use for the controller.
13.4.2 Usage
This attribute is used to configure the default gateway for the system.

GET GWY
Reply:
<Gateway>
where <Gateway> is the IP address for the default gateway.

SET GWY <Gateway>

where <Gateway> is the IP address on the format X.Y.Z.W, where

0<X<255, 0<=Y<=255, 0<=Z<=255, 0<W<255.
Example:
SET GWY 192.168.1.1
configures the default gateway.
Note! If network interface is configured using DHCP, such as via GPRS, gateway is
normally configured by the DHCP reply.
13.5 MAC – MAC address
13.5.1 Overview
This attribute replies with the MAC-address of the controller Ethernet interface.
13.5.2 Usage
This attribute replies with the MAC address of the controller Ethernet interface.
Format:
XX:XX:XX:XX:XX:XX
is the 48 bit MAC address.

Example:
GET MAC
Reply:
00:14:B1:01:03:E5
which is the MAC address for the Ethernet interface of the controller.
13.6 NID – Network Interface Descriptions
13.6.1 Overview
This attribute replies with a textual description of an interface.
13.6.2 Usage
This attribute replies with a textual description of the supplied interface.
Format:
GET NID <Interface>
replies with a textual description of the actual interface.
Example:
GET NID ETH0
Reply:

Ethernet Interface 10/100 Mbit/s
describing the requested interface.
Note! Attribute NIL gives a list of all available interfaces.
13.7 NIL – Network Interface List
13.7.1 Overview
This attribute replies with the different interfaces supported in the controller.
13.7.2 Usage
This attribute replies with a list of supported interfaces supported in the controller.
For a textual description of each of the interfaces, refer to attribute NID.
Format:
GET NIL
Reply:
<Interface 1> <Interface 2> .. <Interface N>
where interfaces is the list of available interfaces.
Example:
GET NIL
Reply:
lo eth0
indicating that the controller supports a Loopback and an Ethernet interface.

Note 1! What interfaces are available mainly depends on hardware version of the
controller.
Note 2! The GPRS interface will be added dynamically once the GPRS attach is
performed successfully.
13.8 NIC – Network Interface Configuration
13.8.1 Overview
This attribute displays and configures the IP settings for a certain interface.
13.8.2 Usage
This attribute is used to configure IP address of a certain interface. Depending on

interface type, both dynamic and static IP can be configured.

GET NIC <Interface>

where <Interface> is the network interface to read configuration for.

Reply:
<Method> <IP Address> <Net mask> <Broadcast>
where
<Method> is DYNAMIC for interfaces using DHCP, and STATIC for interfaces using
static IP-address assignment.
<IP Address> is the IP address of the interface (0.0.0.0 if not configured or not
received by DHCP) on the format X.Y.Z.W, where 0<X<255, 0<=Y<=255,
0<=Z<=255, 0<W<255.
<Net mask> is the net mask for the interface on the format X.Y.Z.W
0<X<255, 0<Y<255, 0<Z<255, 0<W<255.
<Broadcast> is the broadcast address for the interface on the format X.Y.Z.W
0<X<255, 0<Y<255, 0<Z<255, 0<W<255.
Format on setting dynamic IP:

SET NIC <Interface> DYNAMIC
causing <Interface> to automatically attempt to retrieve an IP address from the

DHCP server.
Format on setting static IP:

SET NIC <Interface> STATIC <IP Address> <Net mask> <Broadcast>
configuring <Interface> to use the static IP address

where
<IP Address> is the on the format X.Y.Z.W, where 0<X<255, 0<=Y<=255,
0<=Z<=255, 0<W<255.
<Net mask> is the net mask on the format X.Y.Z.W
0<X<255, 0<Y<255, 0<Z<255, 0<W<255.
<Broadcast> is the broadcast address for the interface on the format X.Y.Z.W
0<X<255, 0<Y<255, 0<Z<255, 0<W<255.
Example on configuring dynamic IP address:

SET NIC ETH0 DYNAMIC
will cause ethernet interface to attempt to retrieve address from the DHCP server
immediately. Refer to attribute DAS for details on when IP address is received.
Example on configuring static IP address:
SET NIC ETH0 STATIC 192.168.1.52 255.255.255.0 255.255.255.255
configures ethernet interface for static IP address 192.168.1.52 and associated net
mask and broadcast address.
Note 1! Loop back interface cannot be configured using the NIC attribute.
Note 2! For each change in NIC parameters, corresponding interface will, if

enabled, be shut down and then started again so that all parameters are initialized
correctly.
Note 3! When configuring DYNAMIC IP addressing, parameter DAS determines if an

address has been received from the DHCP server.
Note 4! If this controller should access addresses outside this subnet, default
gateway must be configured using the GWY attribute.
Note 5! Addresses for GPRS may not be altered using this attribute. Please refer to
attribute GPR for altering GPRS settings.

13.9 NRS – Network Restart
13.9.1 Overview
This action is used to cause a refresh of the network interface.
13.9.2 Usage
Attribute Type: Write-Only Action
Performing this action causes a refresh of the interface. This can for example be
used to retrieve a refresh of the address from a DHCP-server.
Format:
ACT NRS <Interface>
where <Interface> is one of the supported interfaces (attribute NIL can be used to
display all available interfaces).
Example:
ACT NRS ETH0
restarts the ethernet interface.
Note 1! It is not possible to perform a restart of the loopback interface.

Note 2! If interface is disabled, no restart will be performed.
Note 3! If dynamic address is used, status of interface can be obtained using
attribute DAS.
Note 4! Refer to attribute GPRS RESTART of restarting of GPRS interface.
13.10 SSR – Supported Services
13.10.1 Overview
This displays a list of supported network services in the system.
13.10.2 Usage
This attribute displays all supported network services in the system.

Format:
<service 1> .. <service N>
were <service X> is a textual description of the network service ( defined in

RFC1700 ).
Example:
GET SSR
Reply:
ssh telnet
indicating that network services supported are Secure Shell and Telnet.

In order to configure the use of the services, refer to attribute SRV.
13.11 SRV – Service Configurations
13.11.1 Overview
This reads and configures usage of network services in the system.
13.11.2 Usage
This attribute can be used to enable or disable the different network service in the
controller, and also to change port numbers.
Format on getting service configurations:

GET SRV <Service>
where <Service> is the network service to display configuration for.

Reply:
<Enable> <Port Number>
where
<Enable> is 0 if this service is disabled, and 1 if service is enabled.
<Port Number> is the port that this service is listening on.
Format on setting / configuring service:

SET SRV <Service> <Enable> <Port Number>
where
<Service> is the service to reconfigure (must be one of the services as displayed
using attribute SSR).
<Enable> is 0 if this service should be disabled, and 1 if service should be enabled.
<Port Number> is the port that this service should be listening on.
Example on getting parameter:
GET SRV SSH
Reply:
0 22
indicating that the service is disabled, and that if it was enabled should listen on
port 22 (which is the standard SSH port).
Example on setting parameter:
SET SRV TELNET 1 16455
enables the telnet service but reconfigures it to listen on port 16455.
Note 1! In order for the system to work with the Axell Element Manager, the telnet
service must be enabled (but not necessarily on default port 23).
Note 2! Port numbers 10 000 and 10 001 are used by internal systems in the
controller, why they cannot be used for network services.
Note 3! If performing these configurations remotely, connection might be lost when

applying changes to the system.

13.12 IFCONFIG
13.12.1 Overview
Displays an overview of configured network interfaces.
13.12.2 Usage
This command gives an overview of configured interface(s), and can be used for
advanced IP trouble shooting.
Format:
ifconfig [interface]
where the optional [interface] is one of the network interfaces in the system. If no
parameter is supplied, all interfaces are printed.
Example:
AVITEC AB> ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:14:B1:01:03:E5
inet addr:126.1.24.131 Bcast:126.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:61833 errors:0 dropped:0 overruns:0 frame:0
TX packets:15743 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:24 Base address:0xc000
AVITEC AB>
13.13 PING
13.13.1 Overview
Tool to verify that communications path to remote peer is operational.
13.13.2 Usage
This command is used to ping (send an ICMP packet) to other addresses, and can
be used during connection troubleshooting. For example, successfully pinging the
configured IP address of the Axell Element Manager is a good way of knowing that
communication between controller and AEM is set up correctly, and that the AEM
hardware is up and running.
Format:
ping [-c Count] <destination>
where <destination> is either the IP address or the host name to ping.

The optional parameter -c can be used to provide number of pings.
Note! If parameter -c is not provided, ping will proceed until Ctrl-C is pressed.
Example:
AVITEC AB> ping -c 5 192.168.1.42
Pinging 192.168.1.42 5 times. Press <Ctrl-C> to abort.
PING 192.168.1.42 (192.168.1.42): 56 data bytes
64 bytes from 192.168.1.42: icmp_seq=0 ttl=64 time=1.4 ms
--- 192.168.1.42 ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max = 0.7/0.8/1.4 ms
AVITEC AB>
13.14 TRACEROUTE
13.14.1 Overview
Tool to trouble shoot connection problems with remote peers.
13.14.2 Usage
This command can be used for troubleshooting when there is a problem
establishing a connection between the controller and the Axell Element Manager. By
running a traceroute it is possible to see where communications link is broken.
Format:
traceroute <destination>
where <destination> is either the IP address or the host name to run a trace to.
Note! Trace can be aborted by pressing <Ctrl-C>.
13.15 NETWORK
13.15.1 Overview
Command to get an overview of network settings.
13.15.2 Usage
This command displays an overview of network configurations in the system.
Format:
network
displays miscellaneous information related to the network configurations.
14 GPRS CONFIGURATIONS
14.1 GPR – GPRS attribute

This attribute is used to configure all parameters in the GPRS functionality.
14.1.1 GPR AAD – Authorization address
14.1.1.1 Overview
This lists the IP-addresses that are acceptable for the clients named in the ACL
parameter.

14.1.1.2 Usage
Attribute Type: Read / Write
The addresses may be given in dotted quad notation or as hostnames that are
looked up with the resolver.
Usage for setting parameter:

SET GPR AAD <address1> [<address2> ... <addressN>]
This will sett the acceptable address list to the addresses indicated. To allow ANY
address use an asterisk instead “*”.
Example:
SET GPR AAD 126.1.24.1 126.1.24.2
Sets the accebable addresses to 126.1.24.1 and 126.1.24.2.
Usage for getting parameter :

GET GPR AAD
Reply:
126.1.24.1 126.1.24.2
Indicating the acceptable addresses set.
14.1.2 GPR ACL – Authorization Client
14.1.2.1 Overview
Controls the client authorization parameter.
14.1.2.2 Usage
This should be the name of the controller if it is used. In most cases an asterisk “*”
is used to indicate that ANY name is acceptable. Setting this to the wrong name will
make the authentication process to fail.
This name is only used in the CHAP/PAP negotiation process. If authorization

method is set to None it does not matter.

SET GPR ACL <name>
This will set <name> as the client name for the CHAP/PAP negotiation
Example:
SET GPR ACL voyager.local.system
Sets the client name to voyage.local.system.
Usage for getting parameter:

GET GPR ACL
Reply:
*
Indicating that ANY name should be acceptable.

14.1.3 GPR APN – Access Point Name
14.1.3.1 Overview
Sets the Access Point Name to attach to when negotiating a GPRS attach.
14.1.3.2 Usage
Attribute Type: Read / Write.
IMPORTANT: This parameter is different from network to network and operator to

operator. Make sure this string is correct, otherwise the GPRS modem will not
attach to the network properly!
This information should be given by the operator of the network.

SET GPR APN <name>
Where <name> should be the APN (Access Point Name) given by the network
operator to get a GPRS attach properly.
Example:
SET GPR APN internet.provider.com
This will set the APN to “internet.provider.com”.
Format in getting parameter:
GET GPR APN
Reply:
<name>
Where <name> is the currently configured Access Point Name.
Example:
GET GPR APN
Reply:
network.bbdb.com
Indicating that the current APN is set to “network.bbdb.com”.
14.1.4 GPR APPLY – Apply changes made to the GPRS configurations
14.1.4.1 Overview
Used to apply changes made to the GPRS configurations.
14.1.4.2 Usage
Attribute Type: Action
When configuring the GPRS interface, lots of changes normally needs to be made at
the same time without having to restart the GPRS interface for every configuration.

Running command
ACT GPR APPPLY
means that all changes are stored to the system and that they will be used with the
next GPRS detach/attach cycle
14.1.5 GPR ASC – Authorisation Secret
14.1.5.1 Overview
Sets the “secret” for negotiating CHAP/PAP authentication.
14.1.5.2 Usage
Attribute Type: Read -Only
This sets the authorization “secret” for negotiating a PAP or CHAP authentication
with the server. This is also known as “password” or “passphrase”.
To set a blank secret use a dash “-” instead of the secret.

SET GPR ASC <secret>
Where <secret> is the secret enclosed in quotes if it is more than one word.
Example:
SET GPR ASC secret
Sets the PAP/CHAP secret to the word “secret”.
Example:
SET GPR ASC “another day in paradise”
Sets the PAP/CHAP secret to the phrase “another day in paradise”.

GET GPR ASC
Reply:
<Reply>
The command replies with 10 '*' if a passphrase is set and a '-' if no passphrase is
set.
Example:
GET GPR ASC
Reply:
**********
meaning that passphrase is configured in the controller.
14.1.6 GPR ASV – Authorization server
14.1.6.1 Overview
Controls the server authorization parameter.

14.1.6.2 Usage
This should be the name of the server to authenticate with if it is used. In most
cases an asterisk “*” is used to indicate that ANY name is acceptable. Setting this
to the wrong name will make the authentication process to fail.
This name is only used in the CHAP/PAP negotiation process. If authorization

method is set to None it does not matter.

SET GPR ASV <name>
This will set <name> as the client name for the CHAP/PAP negotiation
Example:
SET GPR ASV voyager.local.system
Sets the client name to voyage.local.system.

GET GPR ASV
Reply:
*
Indicating that ANY name should be acceptable.
14.1.7 GPR ATH – Authentication method
14.1.7.1 Overview
Sets the GPRS authentication method to be used.
14.1.7.2 Usage
Attribute type: Read / Write
This attribute is used to set the authentication method used to authenticate the
PPP/LCP connection with the server. There are three possible settings for this
attribute, none, PAP and CHAP. They are represented by a single letter (N, P, C)
describing the authentication method.
Usage for setting parameter

SET GPR ATH <method>
Where <method> can be one of the following:
N: None, no authentication method will be used when negotiating a PPP connection

with the server.
P: PAP authentication mechanism will be used when negotiating a PPP connection

with the server.
C: CHAP authentication mechanism will be used when negotiating a PPP connection.

This is probably the default setting that most networks will use today.
Example:

SET GPR ATH C
Sets the authentication method to CHAP.

GET GPR ATH
Reply:
<method>
Where <method> is either N, P or C. N means no authentication method will be

used, C indicated CHAP authentication will be used and P indicates PAP
authentication method should be used.
Example:
GET GPR ATH
Reply:
C
Indicating that CHAP is the method to be used when negotiating a PPP connection
with the peer server.
14.1.8 GPR CHANGES – Changes made in GPRS configuration
14.1.8.1 Overview
Indication if there are parameters changed in the GPRS configurations
14.1.8.2 Usage
Attribute Type: Read-only
This parameter indicates if there has been changes made to the GPRS interface that
requires the parameters to be applied and interface to be restarted
Format:
<Changes>
where <Changes> = 0 means that no changes made and <Changes> = 1 means

that changes are made to the GPRS configuration and that ACT GPR APPLY and ACT
GPR RESTART should be performed to get the new parameters operational.
Example:
GET GPR CHANGES
Reply:
1
indicating that changes have been made to the GPRS configuration and that they
need to be applied and GPRS interface to be restarted.
Note! This will be cleared by the ACT GPR APPLY command, but some changes
might require a restart of the connection why it is recommended to perform the
restart after each ACT GPR APPLY.

14.1.9 GPR CPI – CHAP Interval
14.1.9.1 Overview
Set the CHAP interval timer.
14.1.9.2 Usage
Attribute type: Read / Write.
This attribute is used to set a timer that can be used to force a re-negotiation of the
CHAP authentication every <interval> seconds. This is used for two reasons, if
there is not traffic the GPRS can be detached so it serves as a keep-alive function.
It also checks that the connection is actually valid and working. If the negotiation
fails for whatever reason the PPP is dropped.
If the GPRS functionality is started as “PERSISTENT” it will then restart and attempt
to re-negotiate the whole PPP link with the server.
A good starting point for this parameter is to set it somewhere between 1-3
minutes (60-180 seconds).

SET GPR CPI <value>
Where <value> should be in the interval of 10-300 seconds.
Example:
SET GPR CPI 90
Sets the CHAP renegotiation interval to 90 seconds.

GET GPR CPI
Reply:
90
Indicating that the interval has been set to 90 seconds previously.
Example:
GET GPR CPI
Reply:
90
14.1.10 GPR CTY – GPRS connection type
14.1.10.1 Overview
Sets the connection type of GPRS to either PPP or IP.
14.1.10.2 Usage
The link to the GPRS network can use different type of protcols. Normally the

protocol used is “IP” but in rare cases it may be necessary to change this to “PPP”
in order to connect. This information should be given by the network operator.
Format on setting the parameter:

SET GPR CTY <type>
Where <type> can be one of either IP or PPP determining the connection type.
Default is IP which should work in most networks.
Example:
SET GPR CTY IP
Sets the connection type to “IP”.

GET GPR CTY
Reply:
<format>
Where format may be either PPP or IP in the reply.
Example:
GET GPR CTY
Reply:
PPP
Indicating that the current method of communicating is PPP.
14.1.11 GPR EXF – GPRS extra flags
14.1.11.1 Overview
This sets any extra flags for the GPRS negotiations.
14.1.11.2 Usage
If you need this please contact Axell Wireless for more information on the various
flags that can be used.
Usage for setting parameter :

SET GPR EXF [“<flag1> ... <flagN>”]
where <flag1> and so on are the various flags.
Example:
SET GPR EXF noauth
Which will set set use no authorization with the peer when connecting (CHAP/PAP
disabled).

GET GPR EXF
Reply:
<flag1 flag2 ... flagN>
Returns any flags set or blank if there are none.

Example:
GET GPR EXF
Reply:
noauth
Meaning that the noauth flag has been set.
14.1.12 GPR MDS – GPRS modem dial string
14.1.12.1 Overview
Sets / displays the current modem dial string for GPRS attach.
14.1.12.2 Usage
This attribute sets the dialstring used to attach to the GPRS network with the
proper PDP context. This should normally not have to be changed. It is by default
set to “ATDT*99***1#” which indicated PDP Context #1 which is always the
context used by this controller.
Do not change the profile number 1 to something else unless you know exactly
what you are doing.

SET GPR MDS <string>
Where <string> is the new string replacing the old one.
Example:
SET GPR MDS ATDT*99#
Will set the dial string to the “short form” of attaching with the default profile.
Normally the dialstring should be “ATDT*99***1#” to indicate the we are using
profile number 1.

GET GPR MDS
Reply:
ATDT*99***1#
Meaning that the dial string is set to “*99***1#” currently.
14.1.13 GPR MDT – Modem timeout
14.1.13.1 Overview
This set the communication timeout with the modem.
14.1.13.2 Usage
Attribute type: Read / Write

This attribute handles the communication timeout with the modem. It is not the
connection timeout with the network but the time allowed for the modem to
respond to an settings command. Normally this is set to 10 seconds which should
be fine for most environments.

SET GPR MDT <seconds>
Where <seconds> range from 5-30 seconds.
Example:
SET GPR MDT 15
This will sett the timeout to 15 seconds.

GET GPR MDT
Reply:
<timeout>
Where the <timeout> is the current modem timeout setting.
Example:
GET GPR MDT
Reply:
15
Meaning the current timeout is set to 15 seconds.
14.1.14 GPR MRU – Maximum Receive Unit
14.1.14.1 Overview
Configures maximum receive unit for the GPRS interface.
14.1.14.2 Usage
Attribute Type: Read/Write
The maximum receive unit is a part of the configuration that determines largest
data packet that can be sent over the GPRS interface before defragmentation is
required. In certain cases this can be used to optimize communications interface
speeds.
Providing value zero normally works, but some networks might require some
tweaking.
Recommended values for the various communication types are
GPRS over GSM/GMSK: 576
GPRS over GSM/EDGE: 1476
GPRS over UMTS/WCDMA: 1500
<MRU>
where <MRU> is the maximum receive unit, <MRU> >= 0.

Example:
GET GPR MRU
Reply:
576
indicates that default value is used.

SET GPR MRU <MRU>
Example:
SET MRU 0
changes Maximum Transmission Unit to 0.
14.1.15 GPR MTU – Maximum Transmission Unit
14.1.15.1 Overview
Configures maximum transmission unit for the GPRS interface.
14.1.15.2 Usage
Attribute Type: Read/Write
The maximum transmission unit is a part of the configuration that determines

largest data packet that can be sent over the GPRS interface before
defragmentation is required. In certain cases this can be used to optimize
communications interface speeds.
Providing value zero normally works, but some networks might require some
tweaking.
Recommended values for the various communication types are
GPRS over GSM/GMSK: 576
GPRS over GSM/EDGE: 1476
GPRS over UMTS/WCDMA: 1500
<MTU>
where <MTU> is the maximum transmission unit, <MTU> >= 0.
Example:
GET GPR MTU
Reply:
0
indicates that default value is used.

SET GPR MTU <MTU>
Example:
SET MTU 1500
changes Maximum Transmission Unit to 1500.

14.1.16 GPR PTR – Persistence timer
14.1.16.1 Overview
Sets the timer on how often the system should check for a GPRS interface.
14.1.16.2 Usage
This timer sets the time how often the system should check that the network is
enabled and operational.
Valid values are between 5 seconds to 600 seconds.

SET GPR PTR <time>
Where <time> is 5 to 600 indicating the check timer interval in seconds.
Example:
SET GPR PTR 90
Sets the timer to 90 seconds (1½ minute) intervals.

GET GPR PTR
Reply:
<time>
Where time is the current time of the interval to check for the existence of a GPRS
interface.
Example:
GET GPR PTR
Reply:
35
Indicating that the system should check for an existing interface every 35 seconds.
14.1.17 GPR RTE – Default route enable
14.1.17.1 Overview
This tells the system to use network default route to GPRS or not.
14.1.17.2 Usage

SET GPR RTE <enable>
Where <enable> is 1 to enable default route through this interface and 0 is to

disable the default route through this interface.

Example:
SET GPR RTE 1
This will enable default route through the interface as soon as it is connected to the
GPRS network.
Format on getting parameter :

GET GPR RTE
Reply:
<enable>
Where <enable> is either 1 for default route enable or 0 for no default route
through this interface.
14.1.18 GPR STATUS – Reports status of GPRS interface
14.1.18.1 Overview
Indication if GPRS interface is operational.
14.1.18.2 Usage
Attribute Type: Read-only
This attribute is used to see if the GPRS interface is operational and that the GPRS
attach has been successfully made.
Format:
<Status>
where <Status> = 0 means GPRS is not up and running and <Status> = 1 that
GPRS is operational.
Example:
GET GPR STATUS
Reply:
0
meaning that GPRS interface is not operational.
Note! If interface is configured and supposed to work, the system will poll the
status every 15 seconds and then try to reattach again.
14.1.19 GPR RESTART – Restart GPRS
14.1.19.1 Overview
Restarts the GPRS interface.
14.1.19.2 Usage
Attribute Type: Action
When changing parameters to the GPRS configuration, the GPRS interface normally

have to be restarted for the parameters to take effect.
Running the command

ACT GPR RESTART
will cause a GPRS detach followed by a GPRS attach session.
14.2 GPRS – Handle GPRS functionality
14.2.1 Overview
Commands to alter the GPRS interface.
14.2.2 Usage
14.2.2.1 GPRS CONFIGURE – GPRS Configurations Wizard

The GPRS CONFIGURE simplifies the GPRS configuration by providing a simple text
based wizard.
The configrations dialog is issued by entering command

GPRS CONFIGURE
which will guide through the configuratioins process. Once the configuration is
completed, the settings are stored and will be activated on next GPRS attachs.
Note 1! All parameters can configured with the GPR attributes, but this guide
simplifies the setup.
Note 2! In order to perform a new attach to the GPRS network, please refer to
attribute ACT GPR RESET.
14.2.2.2 GPRS DOWN – Perform a GPRS detatch

Will perform a temporary detach from the GPRS network. The GPRS interface will
be brought up again when the modem processing daemon performs a new modem
check, which normally happens within one minute.
Format:
GPRS DOWN
This will initiate the GPRS detach procedure.
14.2.2.3 GPRS UP – Perform a GPRS attach

This will perform an attach to the GPRS network with the settings currently
configured.
Format:
GPRS UP
brings up the interface. In order to read out GPRS status, please refer to attribute
GPR STATUS.

14.2.2.4 GPRS APPLY – Apply changes made to GPRS settings

When configuring GPRS parameters using attribute GPR, these parameters are
stored in the system. However, in order to make them permanent, they need to be
applied, meaning that the parameters will be used in the next GPRS attach
procedure.
Format:
GPRS APPLY
applies the currently changed parameters.
Note 1! In order to determine if there are parameters that needs to be applied

refer to attribute GPR CHANGES.
Note 2! This functionality is also available by executing ACT GPR APPLY.
Note 3! In order to perform a GPRS detach/attach procedure to run the new

parameters, refer to attribute ACT GPR RESTART.
14.3 TRACE GPRSDEBUG – Debug GPRS attach
14.3.1 Overview
Command used to perform advanced debugging of the GPRS attach procedure.
14.3.2 Usage
If problems arise when attempting to get the GPRS attach to work properly, it is
possible to reconfigure the interface to provide debug output on the PPP connection
setup between the controller and the GPRS network.
In order to enable the debugging, add the parameter DEBUG to the GPR EXF
attributes, apply changes using ACT GPR APPLY and then restart the GPRS attach
procedure using ACT GPR RESTART.
After this, issuing the command

TRACE GPRSDEBUG
will provide detailed information about progress of the GPRS attach procedure.
Note! Once debugging is completed, make sure to disable debugging. Leaving

debugging enabled can cause the system to fill up with files and to slow down. Run
GPRS CONFIGURE
or reconfigure using attribute GPR EXF, remove debug flag and perform
ACT GPR RESTART
15 FIRMWARE UPGRADE
15.1 Overview
From Common firmware version 1.2.0 of the controller, it is possible to upload and

install firmware into the controller using normal terminal emulation programs and
Z-modems protocols.
Axell Firmware Upload files have the file extension .arf2, and the name should
normally reveal upgrade information such as
OMU-1.0.1_to_OMU-1.0.2.arf2
The firmware package itself contains all information on version compatibilities,

meaning that it is not possible to install firmware unless criterias on current
software versions and available memory in the controllers are met.
Normally, the firmware upgrade consists of uploading the firmware using Z-modem,
and then issue an installation of the firmware.
The installer reads through the packet and calculates the checksums to ensure that
the uploaded packet is valid for installation. It also checks a number of
prerequisites prior to installing the firmware, such as correct System, Common and
Target firmwares version for this upgrade packet and enough space to install the
packet.
Once the installation procedure is started, the system will reboot after completing
the installation procedure, successful or unsuccessful.
Once booting up again, the new controller will if firmware upgrade was successful
be executed, and a FWU (Firmware Upgraded) alarm posted to the Axell Element
Manager containing information about the new firmware version.
If firmware upgrade failed, a FWF (Firmware Upgrade Failure) alarm is posted to the
Axell Element Manager informing about the upgrade failure.
15.2 Upgrade Procedure
The firmware upgrade procedure consists of a few different steps
1. Log in to the controller using any terminal emulation program supporting Z-

modem such as HyperTerminal for Windows or minicom for Unix/Linux/OS X.
2. Initiate firmware upload by issuing the command

firmware upload
and then start the file transmission from the terminal emulation program.
HyperTerminal: Menu item Transfer->Send file, browse to correct arf2 file.
MiniCom: File transfer dialog normally is brought up automatically.
3. Once file is uploaded correctly, switch to System Administrator mode using

command
sysadmin
and provide the sysadmin password.
4. Enter
firmware list
to get a list of all uploaded packages.
5. Issue installation of desired packet by issuing

firmware install <package>
such as
firmware install OMU-1.0.1_to_OMU-1.0.2.arf2

6. Wait for installation procedure to complete. After this the controller will
reboot and start executing the new firmware.
Firmware upgrade completed.
15.3 Upgrading Fibre Optic Repeaters

In order to perform a firmware upgrade to a fibre optic repeater over the fibre, a
direct access to the node has to be performed. This is done by issuing the
command
ACCSS NODE <Node ID>
which will establish a transparent channel to the node. Log in to the controller as
usual and perform the standard firmware upload / firmware install procedure as
described in previous chapter.
Please refer to ACCESS NODE command for details on the direct access over fibre.
15.4 Firmware Command Reference

The following firmware command options are available
firmware - replies with current firmware version.
firmware help – prints help text on the screen.
firmware cleanup – performs cleanup of the system, removes old packages and
log files. This command can be issued if the installer informs that there is not
enough memory to install file.
change - change versions of common and/or target from current to older or to new
version. Fallback functionality.
Note! This functionality is only for testing purposes and might severely destroy the
entire system.
delete - removes a specific upgrade package. This command is to be used if a

package was not possible to install due to checksum errors in the package.
upload - starts a Z-Modem transfer in order to facilitate uploading of a new

firmware to the controller using any type of terminal software such as Microsoft
Windows Hyper Terminal.
status - displays status of controller resources available for firmware upgrade such
as application and system free flash memory and free RAM.
list - displays uploaded firmware packages currently available for installation.
verify - validates that this is a firmware that can be installed.

Note! This will also be performed prior to performing an installation. It is not
possible to install an invalid/broken firmware packet.
version - displays current firmware version (running version).
install <packet> - installs the firmware pointed to by <packet> on the target.

Install also verifies the packet so it is not necessary to run both verify and install in
the same session.

Channel Selective Repeater PDF

Uploaded by

Document Information

Original Title

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

Channel Selective Repeater PDF

Uploaded by

Copyright:

Available Formats

channel selective

© Axell Wireless Ltd

PRODUCT DESCRIPTION AND USER’S MANUAL

Channel Selective Repeaters

This manual is valid for Firmware release version

This document is valid for the following repeater models

Off Air Repeaters Fibre Fed

CSR 1922/4 CSFT 1922/4 CSF 2222/4

Copyright © 2009 Axell Wireless Ltd

© Axell Wireless Ltd A1019300, rev B 1 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

© Axell Wireless Ltd A1019300, rev B 2 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

5.6 Initiate Local Communication ........................................................................................... 98

© Axell Wireless Ltd A1019300, rev B 3 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

Safety Instructions and Warnings

© Axell Wireless Ltd A1019300, rev B 4 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

© Axell Wireless Ltd A1019300, rev B 5 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

ETSI TS 25.106 Universal Mobile Telecommunications System (UMTS); UTRA repeater

ETSI TS 25.143 Universal Mobile Telecommunications System (UMTS); UTRA repeater

EN 60 950 Information technology equipment - Safety - Part 1: General requirements

© Axell Wireless Ltd A1019300, rev B 6 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

Tel: +44 1494 777000

Commercial inquiries info@axellwireless.com

Web site www.axellwireless.com

Support issues support@axellwireless.com

Technical Support Line, English speaking +44 1494 777 777

© Axell Wireless Ltd A1019300, rev B 7 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

Definitions, Abbreviations and Acronyms

Coverage area The geographical reach of a mobile communications network or system

EAM External Alarm Messaging

© Axell Wireless Ltd A1019300, rev B 8 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

intended electromagnetic environment

ETSI European Telecommunications Standard Institute. The European standardization

MS Mobile Station (e.g. mobile phone)

MTBF Meantime Between Failures

Node B UMTS base station

© Axell Wireless Ltd A1019300, rev B 9 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

Very Low Frequency VLF 9 kHz - 30 kHz

Low Frequency LF 30 kHz - 300 kHz

Medium Frequency MF 300 kHz - 3 MHz

High Frequency HF 3 MHz - 30 MHz

Very High Frequency VHF 30 MHz - 300 MHz

Ultra High Frequency UHF 300 MHz - 3 GHz

Super High Frequency SHF 3 GHz - 30 GHz

Extremely High Frequency EHF 30 GHz - 300 GHz

RS485 Serial Interface standard

SMSC Short Messaging Service Centre

WDM Wavelength Division Multiplexing. A technology that uses optical signals on

© Axell Wireless Ltd A1019300, rev B 10 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

Undisturbed transmission Obstacle creating a coverage hole

1.2 Repeater Types

© Axell Wireless Ltd A1019300, rev B 11 (143)

PRODUCT DESCRIPTION AND USER'S MANUAL

1.2.2 Band Selective Repeaters