OMU optical Master unit © Axell Wireless Ltd
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Optical Master Unit, OMU Product Description and User’s Manual This manual is valid for Firmware release version Common Commands and Attributes v 1.3.0 OMU Commands and Attributes v 1.0.0 Copyright © 2009 Axell Wireless Ltd All rights reserved.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Table of Contents Safety Instructions and Warnings.................................................................................................. 4 References ..................................................................................................................................... 5 Contact Information.......................................................................................................................
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4.13 Installation Examples ........................................................................................................ 83 5 6 Maintenance .............................................................................................................................. 85 5.1 General .............................................................................................................................. 85 5.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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 charge inadvertently imposed by careless handling.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL References References to standards apply as relevant to the repeater type being connected to the OMU. Please see respective repeater manual for details.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Definitions, Abbreviations and Acronyms AEM Axell Element Manager A software tool for operation and monitoring a network consisting of Axell Wireless elements such as OMUs and repeaters. ALC Automatic Limit Control 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 Controller (BSC).
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL RMC 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 Repeater Maintenance Console Software tool to monitor and control Axell Wi
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 1 Repeater Technology 1.1 Basic Repeater Features A basic feature of a mobile communication system is to transmit RF signals between base stations and mobile radio equipment. When 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 1.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 or OMU. The RMC is a graphical shell for the repeater’s Control Module. It reads commands and attributes from the Control Module and displays them in an intuitive layout. This eliminates the need to learn commands and attributes for controlling the repeater or OMU.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2 Product and System Description 2.1 Overview The Axell Wireless OMU is a product used in combination with fibre fed repeaters. An OMU can be equipped to be used for frequency ranges from 88MHz to 2 170MHz. An OMU’s basic function is to translate RF signals to light to be sent over an optical fibre, and vice versa.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL A laser system with two colors can operate one repeater for each fibre optic converter in a OMU-Repeater system – one color is used for the uplink and one for the downlink. A laser system with three or more colors can operate two or more repeaters per fibre optic converter. One color is used for the downlink which is the same for all repeaters, and in the uplink each repeater has its own color.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.1.1 Access to the System Important Generic Information 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.1.2 SW for Configuration and Control There are two SW tools for configuration and control of the Axell Wireless OMU-Repeater system. The RMC, Repeater Maintenance Consol and the AEM, Axell Wireless Element Manger. The RMC is an on-line tool that can be used locally or remotely for configuration and monitoring of all parameters in the system.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.2 Building Blocks The OMU is built in a 19” sub rack. PWR ERR ERR ERR ERR UL DATA DL DATA UL DATA DL DATA UL DATA DL DATA UL DATA DL DATA UL DATA DL DATA UL DATA DL DATA OPTO Rx OPTO Tx OPTO Rx OPTO Tx OPTO Rx OPTO Tx OPTO Rx OPTO Tx OPTO Rx OPTO Tx OPTO Rx OPTO Tx SC/APC 1 UL DATA DL DATA LinkOK SC/APC 2 SC/APC SC/APC 1 .... .... .
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.2.1 Fibre Optic Converter The Fibre Optic Converters are placed in slots 1, 2, 3 and 6, 7, 8. A Fibre Optic Converter translates back and forth between RF and optical signals. The optical signals are analogue. Each module contains both an optical receiver and a transmitter. The optical signals for downlink and uplink are combined utilizing WDM technology (Wavelength Division Multiplexing).
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.2.2 UL Combiner and DL Splitter 2 The UL Combiner and DL Splitters are placed in slots 4 and 5. These two modules contain the combiners and splitters that combine and distribute the RF signals between the OMU’s RF port and the Fibre Optic Converters. They also contain attenuators that are used for setting the master signal levels in the downlink and uplink.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.2.3 Control Module The Control Module is placed in slot 9 or 11. Note! If there is a wireless modem mounted in the Control module it has to be placed in slot 11 to access the modem antenna. See section 2.2.8 Modem Antenna Connection. Modem Status Status Modem Power LMT Port The Control Module can collect the status of 4 external alarm sources connected to the External Alarm and Battery Module.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.2.4.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.2.6 Rack Communication Board The Rack Communication Board is placed in slot 12. This module serves as a communications link between the Control Module and the Fiber Optic Converters. The unit is also used when several OMUs are to be linked together. The cables for cascading OMUs are provided by Axell Wireless in case these are needed. The connections are RJ45. How to link the OMUs to one another is described in section 6 Installation.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.2.8 Modem Antenna Connection If a wireless modem is installed din the OMU, an antenna is needed. Either a separate antenna is connected to the modem antenna port, or the connection is be made via a coupler connected to the RF input to the OMU. The latter alternative can only be used if the OMU runs on the same frequency as the wireless modem and is equipped with a duplex filter. 2.2.8.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Alternative 2 The OMU and the wireless modem operate on different bands (for example an OMU for TETRA with a GSM modem) In this case the OMU will have one port where an external antenna can be connected. Modem ANT The connector is SMA type. 2.3 To external antenna Block Diagram An OMU can be configured in many different ways. These are two examples.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Example 2 In the example below there are separate inputs for Rx and Tx and no duplex filter. An external modem antenna is connected and linked to the modem on the Control Module.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 2.5 Radio Signal and Data Communication Paths In the downlink the radio signal is tapped from a BTS using a coupler installed in series with the BTS’s antenna cable. The Fibre Optic Converter in the OMU converts the RF signal to an optical signal and sends it to the repeater over a fibre. In the uplink the Fibre Optic Converter receives the optical RF signal from the repeater, converts it to electrical RF signal and sends it to the BTS.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3 Monitoring and Control The Optical Master Unit, OMU as well as the whole OMU-Repeater system can be accessed locally on site through a Local Maintenance Terminal (LMT) port on any of the units in the system, or remotely via modem or Ethernet. When an RS232 cable is plugged in to the LMT port or a remote access has been established, there are two options for communication; terminal mode or RMC mode.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Element Manager, the AEM will automatically time synchronize repeaters, to ensure that the time is always set correctly in the entire repeater network. Slave repeaters are synchronized from the OMU. 3.2 Network Nodes Note! The description in this section is based on a master-slave set-up of the system, where the OMU is the node master and the repeaters are the slaves.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL AVITEC AB> @2J34 GET MDL BSF424-I AVITEC AB> Node ID Addressing A node can also be addressed using the full Node ID. Example: AVITEC AB> @01-01-2J34 GET TAG SITE3_TUNNEL_OPENING AVITEC AB> Direct Node Addressing When many attributes are intended for another node, the user can enter Direct Node Access mode, where the node the user is logged in redirects all commands to the destination node.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Node detailes: number, ID, Model Node name Node status Select a node by clicking on . The RMC will connect to the selected node. The OMU unit polls the connected repeaters / nodes regularly and keeps control of login requests. If a user at a repeater site wants to log in to the system, the OMU Control Module is responsible for granting / denying the login request.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.4 Alarm System The OMU monitors a number of parameters to see that the unit works as intended. Furthermore, the Control Module constantly polls all the nodes for new alarms. If a new alarm is detected, it is stored in the OMU alarm log. If the OMU is integrated to the Axell Element Manager, the OMU dials up the AEM using the built in modem and delivers the alarm. 3.4.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Opto Related Alarms Alarm Code Description Trigger Received Optical Level RXO Measures the received optical signal level Optical signal level too low Transmitted Optical Level TXO Measures the transmitted optical signal level No transmission Synthesizer Pilot Tone Generator SZP Measures the pilot tone frequency Error on pilot tone Input Signal Level Downlink ILD Measures the signal level in to the fibre optic converters in the down
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Relay Output for Sum Alarm The External Alarm and Battery Module contains a relay output. The relay can be used to indicate the summary status of the OMU. Each alarm source can be configured to affect the relay or not. 3.4.2 Alarms and End of Alarms When the Control Module detects a failure, an alarm is transmitted to the Axell Element Manager, informing the operator about the error condition.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Set Minimum Alarm Repetition Cycle Select “Configuration “ and “Reports” 3.4.3 Alarm Retransmissions and Acknowledgements As soon as the OMU 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 OMU’s local alarm log.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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 “Configuration “ and “Reports” Pick one alternative from the drop-down menu All alarms transmitted from the OMU contain a message number.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.4.4 Alarm Format Each alarm transmitted from the OMU 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 OMU, the alarm string is delivered to the transceiver for further processing in the AEM system.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.4.5 Alarm Class Each alarm belongs to a class. 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. 3.4.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.4.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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL External Alarms Four external alarm sources can be connected to the External Alarm and Battery Module. 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.4.8 Alarm Monitoring The alarms can be monitored via the RMC. Each alarm has an indicator on the screen that is either green or red. See also reference to section 3.4.1 Alarm Sources. Ensure online communication with the OMU Select “HUB Status” for this window Control Module related alarms Power supply related alarms Control Module Related Alarms EEPROM CRC, CRC Faulty checksum in Rack Communication Board or Fibre Optic Converter.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Com, COM Error in communication between Fibre Optic Converter and Control Module Received Level, RXO Received optical level too low Transmitter, TXO No detectable transmitted optical signal Temperature, RBT Temperature in Fibre Optic Converter too high or too low Pilot Tone Gen Synth, SZP Pilot tone frequency faulty Com, COM Error in communication between Combiner or Splitter and Control Module Level after attenuator, ILD Signal level in
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.4.9 Alarm Log The logged alarms can be viewed in an alarm log.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.5 OMU Heartbeat The OMU and connected repeaters can be configured to transmit heartbeat reports to the Axell Element Manager, AEM with regular intervals. If the AEM does not receive a heartbeat report within expected interval, an alarm can be generated and displayed to the operator. In this way, the AEM is ensured that the communication with the OMU works as intended.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.5.1.2 AEM Database Synchronization The Axell Element Manager stores all OMU parameters in a database. This database is populated during the OMU integration into the AEM when the AEM downloads all the OMU parameters. If the AEM operator wants to monitor the configuration of the OMU, the parameters can be read from the database without having to connect to the repeater.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL For example, the Byte 1 status is sent as Hex ‘8’, which is extracted to 1000.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL NCO for node 5 NCO for node 6 NCO for node 7 NCO for node 8 Bit 1 Bit 2 Bit 3 Bit 4 NCO for node 9 NCO for node 10 NCO for node 11 NCO for node 12 Bit 1 Bit 2 Bit 3 Bit 4 NCO for node 13 NCO for node 14 NCO for node 15 NCO for node 16 Bit 1 Bit 2 Bit 3 Bit 4 NCO for node 17 NCO for node 18 NCO for node 19 NCO for node 20 Bit 1 Bit 2 Bit 3 Bit 4 NCO for node 21 NCO for node 22 NCO for node 23 NCO for node 24 Byte
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Slot 3 Slot 4 Slot 5 Slot 6 Bit 1 Bit 2 Bit 3 Bit 4 RBT for Rack 3 Slot 1 RBT for Rack 3 Slot 2 RBT for Rack 3 Slot 3 RBT for Rack 3 Slot 4 Bit 1 Bit 2 Bit 3 Bit 4 RBT for Rack 3 Slot 5 RBT for Rack 3 Slot 6 RBT for Rack 4 Slot 1 CRC for Rack 4 Slot 2 Bit 1 Bit 2 Bit 3 Bit 4 RBT for Rack 4 Slot 3 RBT for Rack 4 Slot 4 RBT for Rack 4 Slot 5 RBT for Rack 4 Slot 6 Byte 5 Byte 6 Byte 7 RXO KLMNXY Status of received optic
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL RXO for Rack 4 Slot 3 SZP KLMNXY RXO for Rack 4 Slot 4 RXO for Rack 4 Slot 5 RXO for Rack 4 Slot 6 6 Synthesizer in Pilot Tone Generator. These values are Hex Coded, and should be used in conjunction with COM status for actual device. For example, the Byte 1 status is sent as Hex ‘8’, which is extracted to 1000.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Byte 2 Bit 1 Bit 2 Bit 3 Bit 4 TXO for Rack 1 Slot 5 TXO for Rack 1 Slot 6 TXO for Rack 2 Slot 1 TXO for Rack 2 Slot 2 Bit 1 Bit 2 Bit 3 Bit 4 TXO for Rack 2 Slot 3 TXO for Rack 2 Slot 4 TXO for Rack 2 Slot 5 TXO for Rack 2 Slot 6 Bit 1 Bit 2 Bit 3 Bit 4 TXO for Rack 3 Slot 1 TXO for Rack 3 Slot 2 TXO for Rack 3 Slot 3 TXO for Rack 3 Slot 4 Bit 1 Bit 2 Bit 3 Bit 4 TXO for Rack 3 Slot 5 TXO for Rack 3 Slot 6 TXO for Rac
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.5.3 Heartbeat Log Recent heartbeats can be viewed in a log that shows details about the heartbeats. Each heartbeat event contains information from all nodes that are connected to the OMU. The first row is the OMU itself and the following rows are the repeaters. The information follows the heartbeat format described in the previous section.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.6 Hardware Identification An OMU contains a number of different modules. Some of these are active devices containing a micro controller, and some are passive devices. 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL The TAG can be used to give the OMU a more logical name. If the 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 Tag can be locked so that the tag can not be accidentally changed from the AEM. Refer to section 4.7.1 Set OMU Name (TAG) for information about how to set the Tag. 3.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 3.9 Integration into AEM When the OMU has been installed at site and the remote communication has been enabled the OMU can be integrated to the Axell Element Manager. This is done by the operator of the AEM. After entering the telephone number to the OMU, the AEM dials up the OMU, downloads all the OMU parameters and statuses into a database.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4 Installation 4.1 Unpack the OMU Unpack the OMU Inspect the shipped material before unpacking the equipment, document any visual damage and report according to routines. A delivery of an OMU from Axell Wireless contains: 4.2 Checklist with delivered items OMU CD containing RMC and User’s Manual Any other specifically ordered item Mount the OMU The OMU is designed to be mounted in a 19” sub rack.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4.4 Attach Cabling Supply Power to the OMU The power feed to the OMU is attached via plinths found on the inside of the back cover. Power connection plinths Each OMU unit can be equipped with one or two power supplies. Either two of the same type or two of different voltage. There are power supplies for 115 - 230VAC 50/60 Hz and 24 - 48VDC. . Note! Be careful to get the polarity right.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL A Band Selective Filter can be installed between the coupler and the antenna to prevent signal disruptions from the OMU. Connect the modem If the OMU is equipped with a wireless modem an antenna for the modem is necessary. This can be realized either via a separate antenna or via a coupler on the RF in/out port in the OMU.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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. Connect external alarms Four external alarm sources can be connected to the External Alarm and Battery Module via the patch panels. These sources must generate a voltage between 12 and 24VDC.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL OMU 1 IN OUT 1 OUT 2 OMU 2 IN OUT 1 OUT 2 OMU 3 IN OUT 1 OUT 2 OMU 4 IN OUT 1 OUT 2 Link pattern for cascaded OMUs. OMU 1 and OMU 3 is on “bus “0 and OMU 2 and OMU 4 in on” bus 1”.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4.5 Start-up the OMU Caution! Make sure the antenna cables or 50 ohm terminations are connected to the OMU’s antenna connectors before the OMU is switched on. Switch the OMU on Switch on the OMU using the switches on the Power modules. The modules operate in parallel and are independent of each other. Also switch on the battery. When the battery is switched on it will be recharged and ready to use when needed.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL every 10th second) 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
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4.6 Initiate Local Communication 4.6.1 RMC Communication Connect to the LMT port Connect the computer to the LMT port on the Control Module via a DB9 male connector with serial RS232 interface.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4.7.3 Configure Reports In this screen the reports from the OMU can be configured. Select “Configuration” and “Reports” Heartbeat reports Alarms reports 4.8 Set Up OMU-Repeater System Install the repeaters Install the fibre fed repeaters. See the User’s Manual for the repeaters. Install the fibers to the repeaters Make sure the fibre link between the OMU and all of the repeaters are working. Add all nodes to the OMU-Repeater System.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Serial number The serial number consists of 4 letter and/or digits. It is printed on the yellow label on the repeater Bus number When OMUs are cascaded they run on different buses. OMU 1 and OMU 3 is on “bus “0 and OMU 2 and OMU 4 in on” bus 1”. See 4.4 Attach Cabling. Controller type Select the correct repeater controller based on the illustrations Baud rate The default value changes when the controller type is selected.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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 via the opto module is ongoing in the uplink direction Off No communication LED 4, DL Data, Yellow On Communication via the opto module is ongoing in the downlink direction Off No communication LED 5, Opto Rx, Green On Input opto level OK Off Input opto level below threshold LED
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4.9 Balance the System To get an appreciation of the signal levels, a link budget should be prepared before the system is made operational. This is one example with a BTS at the OMU site.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Select “HUB Status” Seet the attenuation in the downlink in this box. The level in position F can be monitored in the RMC Fiber Loss Compensation Activate the fibre loss compensation in both the downlink (from the OMU) and in the uplink (from the repeaters) paths. See 4.10 Initiate Fibre Loss Compensation. Uplink Path In the uplink direction the system should be transparent, i.e.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Consider the noise situation Another issue that needs to be taken into account is the noise figures. If several repeaters are connected to the same base station the aggregated noise level in relation to the signal level will become too high – the sensitivity of the base station is decreased. A way to deal with this problem is lower the output power from the base station.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL In the response above the Status is “OK” (6 lines from the bottom). If the system responds with an error message the fibre link need to be checked. If there is nothing wrong with the link it is possible that the fibre loss is too big for the system to be able to compensate for it. Go through all racks and all fibre optic converters one by one and initiate the compensation process.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL repeaters The system will respond with a description as below. Note! © Axell Wireless Ltd This command does not exist in repeaters with the earlier type of fibre optic converters, equivalent to the note above regarding OLC. For these repeaters disregard this step.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4.11 Set up Remote Communication The OMU can be configured with a wireless modem, a PSTN modem or an Ethernet link for the remote communication. 4.11.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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4.11.2.1 Modem Configuration, not using GPRS Select “Configuration” and “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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Select GPRS Initialization string 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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. 4.11.2.3 AEM Addresses The Control Module can be configured with two different addresses (telephone numbers) to which alarms and reports are delivered.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Select Data Call Initialization string 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 function ensures that the repeater always is logged in to the network. 4.11.4 Communication via TCP/IP and Ethernet A TCP/IP communication is run over a company’s network.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL In these screens the Ethernet and/or DNS Gateway parameters can be set 4.11.5 Troubleshooting Remote Communication 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 OMU for remote access fails.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Log in to the OMU, 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 OMU command prompt in the same way as with HyperTerminal. When the OMU prompt is accessible, type in the command ACCESS MODEM . When typing ACCESS MODEM, the controller will send all the characters that are typed directly out to the modem port.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL To end session type CTRL-Z Manually Answering Incoming Calls It is possible to manually answer incoming calls without involving the OMU 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 OMU with a terminal emulation program, for example HyperTerminal™. Go in to Direct Modem Access as described earlier.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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 OMU. 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.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 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 OMU is configured properly, and answers the incoming call, but when trying to dial the OMU using an analogue mode, no modem handshaking is heard from the dialling modem.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL In order to change the modem string, go to the OMU 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
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 4.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL Server Antenna Donor Antenna ODF ODF AEM Antenna or Leaky feeder Modem Coupler Channel Selective Repeater Fiber Fed Repeater Power Unit for -48 V DC optional Back-up Battery An example of a site installation where the FR signal to the OMU is tapped off a repeater © Axell Wireless Ltd A1829300 rev H 84 (86)
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 5 5.1 Maintenance General The system normally operates without any operator intervention or maintenance. Should the system malfunction, the condition of the antenna systems as well as the continuity of the cabling should be checked before replacing any of the OMU units. In the unlikely event of a unit failure, the field replaceable components (antenna unit, cables, etc.) should be checked and replaced if faulty and the system restored.
Optical Master Unit PRODUCT DESCRIPTION AND USER’S MANUAL 6 Specifications RF Parameters Frequency Response 88-960 / 1710-2170 MHz Gain Flatness Typical 2 (p-p) dB Nominal RF input power +10 dBm composite power Maximum RF input power +23 dBm composite power Fibre optic loss compensation Implemented Optical Modules Number of optical modules 1-6 Laser class Class 1 Wavelength 1310 ± 10 nm or 1330 ± 10 nm Optical output power +5 ± 2 dBm Maximum Optical Input Power +5 dBm Output Power (T
REPEATER MAINTENANCE CONSOLE Repeater Maintenance Console Short Guide Valid from RMC version 2.2 Copyright © 2008 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.
REPEATER MAINTENANCE CONSOLE 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 1.
REPEATER MAINTENANCE CONSOLE 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.
REPEATER MAINTENANCE CONSOLE 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.
REPEATER MAINTENANCE CONSOLE USERNAM3 PASSWRD3 read only USERNAM4 PASSWRD4 read only User name and password structure 2 1.4 User Name Password avitec AvitecPasswd 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.
REPEATER MAINTENANCE CONSOLE 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.
REPEATER MAINTENANCE CONSOLE 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 Common Commands and Attributes v1.3.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 Change Log Version Change by 1.0 MW Date 29/01/09 Description 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 Contact Information For further information about this document, please contact . AXELL WIRELESS Mailing address: Axell Wireless Aerial House Asheridge Road Chesham Buckinghamshire HP5 2QD United Kingdom Tel: +44 1494 777000 Fax: +44 1494 777002 Web: http://www.axellwireless.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 TABLE OF CONTENTS 1 2 3 4 5 Overview.................................................................................................................14 Axell Wireless Versus Avitec.......................................................................................14 Version Compatibility.................................................................................................14 Using Commands and Attributes......................
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 7.4.1 Overview....................................................................................................24 7.4.2 Usage........................................................................................................24 7.5 AL3 - Compressed Alarm Format ........................................................................24 7.5.1 Overview.....................................................................................
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 8.1.1 Overview....................................................................................................37 8.1.2 Usage........................................................................................................37 8.2 ASC – Address of Service Center .........................................................................38 8.2.1 Overview..................................................................................
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 8.19.2 Usage......................................................................................................48 8.20 SFT – Secondary Fallback Timer.........................................................................48 8.20.1 Overview..................................................................................................48 8.20.2 Usage.......................................................................................
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 9.7.2 Usage........................................................................................................59 9.8 ACT CHB – Clear Heartbeat Log...........................................................................59 9.8.1 Overview....................................................................................................59 9.8.2 Usage......................................................................................
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 10.16.1 Overview................................................................................................70 10.16.2 Usage.....................................................................................................70 10.17 TAG – Repeater Tag........................................................................................71 10.17.1 Overview................................................................................
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 11.12.1 Overview................................................................................................82 11.12.2 Usage.....................................................................................................82 12 AXELL WIRELESS Repeater System Settings...............................................................82 12.1 System Node Identification........................................................................
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 13.13 PING...........................................................................................................106 13.13.1 Overview..............................................................................................106 13.13.2 Usage...................................................................................................106 13.14 TRACEROUTE............................................................................
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 1 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 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.3 DST – displays status of the door 6.3.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 descriptions. 6.4.2 Usage Attribute type: Read and Write The External Alarm Configuration is used in conjunction with the EAD attribute to configure what additional text is transmitted together with alarms EX1-EX4.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 Format on getting parameter: 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”. Format on setting parameter: 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 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 EX1 Replies: 0 meaning status is OK. 6.8 EX2 – displays status of external alarm input 2 6.8.
Document Name: Common Commands and Attributes v1.3.0 6.9.2 Revision: 1.2 Usage 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 EX3 Replies: 0 meaning status is OK. 6.10 EX4 – displays status of external alarm input 4 6.10.1 Overview This read-only attribute displays the status of the external alarm input 4. 6.10.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.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’.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 DOO. 7.3.2 Usage Attribute type: Read only 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.
Document Name: Common Commands and Attributes v1.3.0 7.5.2 Revision: 1.2 Usage Attribute type: Read only 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 Attribute type: Read and Write This attribute configures the alarm measurements and alarm handling on an attribute by attribute basis.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 Note! Changing parameter will change the way the alarm source is measured. In order to avoid erroneous system behaviour, this parameter should never be changed. is the value of the lower threshold used for alarm calculation. is the value of the upper threshold used for alarm calculation.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 - Alarm Class, which is one of EN (Environmental), EQ (Equipment), CO (Communications), PR (Processing) or QS (Quality of Service) - Indicates whether alarm is acknowledged or not. 0 = No, 1 = Yes - Number of Retransmissions Left before giving up to try transmitting alarm to the AEM. - Time on the format HHMMSS when alarm was successfully transmitted to the OMC.
Document Name: Common Commands and Attributes v1.3.0 7.9.2 Revision: 1.2 Usage Attribute type: Read only Format: where 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 7.12.2 Usage Attribute type: Read only 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 - Unique identifier for the system event in the interval 0..231. - Attribute name identifying alarm type, i.e. DOO, TEM, EX1 etc. - Unique identifier for the hardware being the originator of the alarm, such as HIB1, LUL2, FDM1 etc. If not used, a '-' (dash) is reported. - Unique identifier for the position within hardware being the originator of the alarm.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Read only By reading this attribute, the system status as reported according to relay configurations can be read out.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 test phase. Format: where 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Write-Only Action For installation testing purposes, it is possible to test the open / close function of the relay.
Document Name: Common Commands and Attributes v1.3.0 040820 020100 375 033023 020100 374 system." 032932 020100 373 032910 020100 372 126.1.24.163" 032854 020100 371 useradmin by user 032643 020100 370 126.1.24.163" Revision: 1.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 8.3.2 Revision: 1.2 Usage Attribute type: Read and Write Format: where = 1 means that remote communication is enabled, and = 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Read and Write This attribute handles the device and method used for remote communication to the Axell Element Manager.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 where is a valid device type supported by the system and 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 8.10 Revision: 1.2 MCT – Modem Connect Time 8.10.1 Overview Used to configure timeout when attempting to setup a modem connection. 8.10.2 Usage Attribute type: Read and Write 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 configures at what timepoint the modem power cycling should be performed.
Document Name: Common Commands and Attributes v1.3.0 8.15 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 8.17 Revision: 1.2 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 Attribute type: Read and Write 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 case switched over to secondary address. 8.20.2 Usage Attribute type: Read and Write 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Read and Write This attribute is used together with SSC to build complete connection parameters when using TCP/IP to connect to the Axell Element Manager.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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).
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 8.29 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 9 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 replied. - Date on the format DDMMYY when heartbeat was successfully transmitted to the OMC. If heartbeat is not yet delivered, a '-' (dash) is replied. - A quoted string containing the actual heartbeat message. Note! If no log entry exists in log at this position, a single '-' (dash) is replied. 9.2 HLN – Heartbeat Log Length 9.2.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 where = 0 means that no heartbeat will be transmitted on startup, and = 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 transmitted to the AEM. 9.5.2 Usage Attribute type: Read and Write 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 9.9 LOGDUMP HEARTBEAT 9.9.1 Overview Revision: 1.2 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 where is the first entry that should be read from the log, must be greater than 0.
Document Name: Common Commands and Attributes v1.3.0 10 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 reset. shows how many times the device has been started since device was initialized. shows how many times the watchdog has forced the device to reset since device initialization is a string delimited by “(double quote) signs, containing a textual description of the hardware device. Note! If is greater than ADC, a single '-' (dash) will be reported. 10.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 is from 1 to HDC. Reply format: is 4 characters containing the device serial number. is the Axell Article Number, up to 12 characters. contains a quoted textual description of the hardware device. String can be up to 40 characters wide.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 10.7.2 Usage Attribute type: Read and Write 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.
Document Name: Common Commands and Attributes v1.3.0 10.9 Revision: 1.2 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 Attribute type: Read only The target model description replies with a verbose output of the type of equipment being monitored by this controller. Format: being a string with a maximum length of 140 characters.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Read and Write 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 The system uptime is defined as the time that has elapsed since last system startup. Format: where 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Read and Write 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 - 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 11 Revision: 1.2 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 Attribute type: Read only The LIU attribute replies with all list of all users currently logged in to the system. Format: ...
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 3 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 where must be at least 6 characters long. 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 Example 2, user is useradmin (see USERADMIN command for details): 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 11.9.2 Usage Attribute type: Write-Only Action 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 USERDEMOTE. Format: ACT USERDEMOTE where is one of the users in the system. is case sensitive, meaning that the system differs between uppercase and lowercase characters.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 12.1 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Read only 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 unknown. is the serial number of the node / repeater. is the repeater model identifier, as replied by attribute MDL. is the name of the node site, as replied by attribute TAG, wrapped in two “”. replies with the software version of the node controller, as replied in SWV attribute. This consists of three tokens, all wrapped in two ‘”’.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 12.3.5.2 Usage Attribute type: Read only 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Read only 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 GET NLS Reply: 1 means that we have full access to the repeater network, and can get and set parameters on other nodes. Note! 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.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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 an RXQ alarm is triggered. This attribute reply with status of the Received Data Quality alarm source. Format: where is status of the received data quality. 0 if status is OK 1 if status is ERROR - (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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Write-Only Action This command is used to temporarily stop handling data packets from the node master, and is mainly used for testing purposes.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 where is total number of received bytes since slave started. is total number of transmitted bytes since slave started. is total number of received valid broadcasts. is total number of valid data packets.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 This attribute replies with status of communication with all nodes in the repeater system. Format: .. 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 12.5.3 NST – Node Statuses 12.5.3.1 Overview Displays status of all nodes in the network. 12.5.3.2 Usage Attribute type: Read only Node status attribute is used to give an overview of the status for all nodes in the network, including the Node Master. Format: .. is the summary status for the Master unit and is status for node X.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 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 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. Revision: 1.2 Tag: Repeater/Site Name Remote node logged out, aborting. Shutting down connection. Over and out.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 NODE ADD 60FY 0 -:- 1 which adds node 60FY on bus zero. and are ignored, and is set to 1, meaning that node is probably using a H40 or H50 based controller.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 0 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 13.3.2 Usage Attribute Type: Read and Write This attribute configures whether Ethernet interface should be enabled or disabled. Format on getting parameter: GET EEN Reply: where Enabled = 0 means Ethernet interface is disabled. Enabled = 1 means Ethernet interface is enabled. Format on setting parameter: SET EEN where Enabled = 0 disables the Ethernet Interface. Enabled = 1 enables the Ethernet Interface.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 where is the IP address on the format X.Y.Z.W, where 0
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute type: Read only This attribute replies with a list of supported interfaces supported in the controller.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 where is the network interface to read configuration for. Reply: where is DYNAMIC for interfaces using DHCP, and STATIC for interfaces using static IP-address assignment. 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
Document Name: Common Commands and Attributes v1.3.0 13.9 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 [ ... ] 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 14.1.6.2 Usage Attribute Type: Read / Write 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 SET GPR ATH C Sets the authentication method to CHAP. Usage for getting parameter: GET GPR ATH Reply: Where 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Where 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”.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute Type: Read / Write. 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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. Format on setting parameter: SET GPR MDT Where range from 5-30 seconds. Example: SET GPR MDT 15 This will sett the timeout to 15 seconds.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 Example: GET GPR MRU Reply: 576 indicates that default value is used. Format on setting parameter: SET GPR 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 Attribute Type: Read / Write 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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: Where 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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.
Document Name: Common Commands and Attributes v1.3.0 Revision: 1.2 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 which will establish a transparent channel to the node.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 Axell Wireless OMU Commands and Attributes Document Revision: 1.0 Firmware Version: OMU 1.0.0 Document Release Date: 2007-10-23 Note! Avitec and AFL have merged to form the new company Axell Wireless. In this manual the name Avitec still appears in prompts etc.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 REVISION LOG Revision Date 1.0 07-10-23 Author MW Description First release. Copyright © 2008 Axell Wireless 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.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 INDEX 1OVERVIEW......................................................................................................................................................................7 2VERSION COMPATIBILITY........................................................................................................................................7 3USING COMMANDS AND ATTRIBUTES......................................................................
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 6.18.1Usage................................................................................................................................................................20 7OPTO INTERFACE CONFIGURATIONS................................................................................................................ 21 7.1OLA – Optical Loss Adjustment ..........................................................................................
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 11.2.3Time................................................................................................................................................................. 31 11.2.4Upper................................................................................................................................................................31 11.2.5Lower...................................................................................
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 11.12SZP – Synthesizer Pilot Tone Generator...................................................................................................... 36 11.12.1Description..................................................................................................................................................... 36 11.12.2Threshold Usage.....................................................................................................
Document name: OMU Commands and Attributes 1.0.0 v1.0 1 Version: 1.0 OVERVIEW All 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.
Document name: OMU Commands and Attributes 1.0.0 v1.0 4 Version: 1.0 BUILT IN HELP SYSTEM 4.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).
Document name: OMU Commands and Attributes 1.0.0 v1.0 5 Version: 1.0 OMU COMMANDS 5.1.1 Overview NODEPNP command is used to automatically identify new nodes in the network. 5.1.2 Usage The OMU communicates with slave repeaters over the optical fibers, and all communication is master/slave based where the OMU is the master polling all slave nodes/FiberOptic repeaters. When communicating with the repeaters, the serial number of the repeater (or repeater controller) is used as an address.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 Example 3: NODEPNP 1:4 Reply: Failure to find nodes in rack 1, slot 3, probably more than one node answering. Try again! This probably means that two or more nodes answered at the same time, giving corrupt data back. Running this command again, optionally with a longer delay, might cause the nodes not to answer at the same time.
Document name: OMU Commands and Attributes 1.0.0 v1.0 6 Version: 1.0 ALARM CONFIGURATIONS The following commands and attributes are implemented for the OMU target alarm configurations, as an add-on to the Common part. 6.1 AC2 – Compressed Alarm Severity and Alarm Class Configurations A compact message retrieving alarm severity and alarm class for a number of alarm sources. 6.1.1 Usage Attribute type: Read only This is a compact message to retrieve Severity and Class of the different alarm sources.
Document name: OMU Commands and Attributes 1.0.0 v1.0 6.5 Version: 1.0 ALL - Compact Message Status Parameters in Optical Master Unit A compact message of all RF and status parameters in the repeater. 6.5.1 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 Heartbeat Reports format. 6.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 .. is status on communication with Combiner Board 1 to 4. .. is status on communication with Fiber Optic Modules 1 to 6 in rack 1. .. is status on communication with Fiber Optic Modules 1 to 6 in rack 2. .. is status on communication with Fiber Optic Modules 1 to 6 in rack 3. ..
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 0 means status is OK 1 means status is ERROR. - (dash) means module is not available. Example: GET CRC Reply: 00-- 00-- 00-- 000000 0100-- ------ ------ meaning that two racks are installed with 6 modules in first rack and two in second. CRC error is detected in FiberOptic module 2 in rack 2, while CRC status in all other modules is OK. 6.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 1 means status is ERROR - (dash) means data is not available (not yet measured or communications error with RCB). Example: GET PW2 Reply: 010- meaning that power supply 2 is in error in second rack, and that fourth error is not installed, or there is a communications error with fourth rack. 6.11 PW3 - Status of Power Supply 3 Gives status of the power supply 3 as measured in the different racks. 6.11.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 meaning that there are three racks installed, power supply 3 in Rack Communications Board second rack is in error, and that all other measured power supplies are OK. 6.12 PW4 - Status of Power Supply 4 Gives status of the power supply 4 as measured in the first rack. 6.12.1 Usage Attribute type: Read only This attribute replies with status of the Power Supply 4 (+6.45 V) as measured in the first rack (master rack).
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 Value can be: 0 means status is OK 1 means status is ERROR. - (dash) means module is not available. Example: GET RBT Reply: 00-- 000010 0000-- ------ ------ meaning that two racks are installed with 6 modules in first rack and two in second. Temperature error is detected in FiberOptic module 5 in rack 1, while temperature status in all other modules is OK. 6.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 ... Byte 6: is status of Power Supply 1 as measured in Rack Communication Boards is status of Power Supply 2 as measured in Rack Communication Boards is status of Power Supply 3 as measured in Rack Communication Boards and OMU Splitters.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 Example: GET RSP Reply: 0 000- 000- 000- 000000 000000 00000- ------ 000000000 000000 000- 000000 0 0000000 000000 000000 1 000000 000- 0000 which indicates that all alarm statuses are OK, except temperature, which is in error. 6.15 RXO – Status of Received Optical Level This attribute replies with the status of the Received Optical Level alarm sources. 6.15.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 Example: GET SZP Reply: 000000000010000--------- indicating that synthesizer in rack 2, slot 4 is unlocked, and that reason for failure should be investigated. 6.17 TEM – Status of Controller Temperature Displays status of temperature as measured in the repeater controller. 6.17.1 Usage Attribute type: Read only This attribute replies with status of the temperature as measured in the repeater controller.
Document name: OMU Commands and Attributes 1.0.0 v1.0 7 Version: 1.0 OPTO INTERFACE CONFIGURATIONS This section describes attributes used to read out and configure settings related to the FiberOptic modules and corresponding pilot tone functionality. 7.1 OLA – Optical Loss Adjustment This attribute is used to read and adjust link between master and optical slave unit. 7.1.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 Level) that was needed to complete adjustment. is a quoted string containing additional information about measurement or reason for failure. Example: GET OLA 1:6 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.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 where OLC1:1..OLC4:6 replies with received optical level in dBm with one decimal resolution for fiber optic masters in .. . If level is lower than lowest detectable, '<[LowDet]' is replied. If value is not available (such as not FiberOptic Master not installed or configured, or communications error with FiberOptic Master), a '-' (dash) is reported. Example: GET OLV Reply: -7.1 -7.5 -8.3 -6.2 -6.6 - -11.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 If value is not available (such as not FiberOptic Master not installed or configured, or communications error with FiberOptic Master), a '-' (dash) is reported. Example: GET PTL Reply: <-50.0 <-50.0 <-50.0 <-50.0 - - -27.1 - - - - - - - - - - - - - - - - - indicating that level of received pilot tone for the different modules are lower than lowest detectable, except for module in position rack 1, slot 1, which has a level of-27.1 dBm.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 6 6 9 - indicating that rack 1 and 2 have attenuation set to 6 dB, rack three to 9 dB and fourth rack is not configured. Format on setting parameters: SET ATD [ ] [ ] [ ] where is the rack selector (1..4) is downlink attenuation to set in rack K. Interval is 0 to 21 dB in 3 dB steps.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 Format: where is status of the input signal level as measured in the Splitter Board of the first rack (Master Rack). is status of the input signal level as measured in the Splitter Board of the second rack (Slave Rack). is status of the input signal level as measured in the Splitter Board of the third rack (Slave Rack).
Document name: OMU Commands and Attributes 1.0.0 v1.0 8.5 Version: 1.0 RFC – Radio Frequency Parameters for Combiner Displays Radio Frequency related parameters of the combiner board. 8.5.1 Usage Attribute type: Read only This attribute displays Radio Frequency related parameters of the combiner board. Format on getting parameters: GET RFC reads status from combiner installed in rack N (1..4).
Document name: OMU Commands and Attributes 1.0.0 v1.0 9.1.1 Version: 1.0 Usage Attribute Type: Read-Only Depending on configuration, an optical master unit can consist of one to four racks, where rack 1 is the master rack and rack 2 to 4 are slave racks. This attribute displays a number of voltages as measured in the configured racks. Levels are displayed for all racks configured in the system, and if rack is not available, a '-' (dash) is reported in corresponding position. Format: ..
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 10 DATA COMMUNICATION SETTINGS This section describes attributes used to configure and read out misc data communication settings. 10.1 NCP – Node Communications Path This attribute reads and configures node communications path. 10.1.1 Usage Attribute type: Read and write This attribute is used to read and configure what rack position the fiber optic repeater / slave node is connected.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 indicating that all installed opto links have data communications enabled, exept for module in position rack 1:slot 5. Format on setting parameter: SET OCP : where indicates rack number from 1 to 4, and indicates slot from 1 to 6 within rack. configures if data communications should be enabled (1) or disabled (0).
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 11 ALARM ATTRIBUTE THRESHOLDS This section defines alarm sources in the Optical Master Unit target. The following alarms are NOT described in this chapter, but are optionally generated by the repeater: * External Alarm Interface board alarms EX1-EX4. * User activity alarms VLI, LGO and CLR. * User administration alarms (UAD, UDE, UPM, UDM and UPW). * Firmware upgrade / fall back alarms (FWU and FWF). 11.1 BAT – Battery Level 11.1.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 11.2.5 Lower Not used. 11.3 CRC – EEPROM CRC Check in Active Devices 11.3.1 Description On a regular interval, the controller polls the active devices for the Checksum of the EEPROM (where all radio parameters are stored). If CRC differs from expected CRC, an alarm is triggered. This status is checked in EEPROM of the Rack Communication Boards (RCB), Splitter Boards (SPLIT), Combiner Boards (COMB) and FiberOptic Modules (FOMASTER).
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 11.5 NCO – Node Communications Status 11.5.1 Description If Optical Master Unit is configured as a node master monitoring a number of slave repeaters over the optical fiber, this alarm is used to indicate status of the actual communication. A communications alarm might indicate that fiber connection is unplugged or that repeater is down. 11.5.2 Threshold Usage This is a status measurement, either OK or ERROR.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 11.7.2 Threshold Usage By default, both upper and lower thresholds are used in the PW2 alarm. 11.7.3 Time Time threshold defines how many seconds the alarm should be measured as in error before an alarm is triggered. 11.7.4 Upper Upper threshold is maximum voltage level * 10 of the power supply before an alarm is triggered. For example, configuring the upper level as 155 means that if voltage level exceeds 15.5 V, an alarm is triggered.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 11.9.3 Time Time threshold defines how many seconds the alarm should be measured as in error before an alarm is triggered. 11.9.4 Upper Upper threshold is maximum voltage level * 100 of the power supply before an alarm is triggered. For example, configuring the upper level as 660 means that if voltage level exceeds 6.60 V, an alarm is triggered. 11.9.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 11.11.4Upper Not used. 11.11.5Lower Defines the lowest acceptable optical level in dBm * 10 before an alarm is triggered. For example, setting Lower alarm threshold to -20 means that if optical input level drops below -2.0 dBm, an alarm is triggered. 11.12SZP – Synthesizer Pilot Tone Generator 11.12.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 11.13.5Lower Defines below what temperature in Celsius * 10 that an alarm is triggered. For example, by defining lower threshold as -250, an alarm is triggered if temperature in controller drops below -25.0 C. 11.14TXO – Transmitted Optical Level 11.14.1Description Transmitted optical power level is constantly monitored to ensure functionality of the system.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 12 HEARTBEAT FORMAT The heartbeat report is transmitted to the Axell Element Manager on configurable intervals (0-99 999 min). In case the heartbeat report is not received by the Axell Element Manager within expected interval, an alarm is triggered at the AEM. If optical master unit is configured as a node master, heartbeats are collected from all slaves for transmission to the Axell Element Manager.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.
Document name: OMU Commands and Attributes 1.0.0 v1.0 NCO KLMNXY Version: 1.0 Status of communication with the node 6 slaves. These values are Hex Coded, and should be used in conjunction with NON attribute to know how many nodes are installed. For example, the Byte 1 status is sent as Hex ‘8’, which is extracted to 1000.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 be used in conjunction with COM status for actual device. For example, the Byte 1 status is sent as Hex ‘8’, which is extracted to 1000.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 for Rack 3 Slot 1 for Rack 3 Slot 2 for Rack 3 Slot 3 for Rack 3 Slot 4 Bit 3 Bit 2 Bit 1 Bit 0 RXO for Rack 3 Slot 5 RXO for Rack 3 Slot 6 RXO for Rack 4 Slot 1 RXO for Rack 4 Slot 2 Bit 3 Bit 2 Bit 1 Bit 0 RXO for Rack 4 Slot 3 RXO for Rack 4 Slot 4 RXO for Rack 4 Slot 5 RXO for Rack 4 Slot 6 Byte 5 Byte 6 SZP KLMNXY Status of Synthesizer in Pilot Tone 6 Generator.
Document name: OMU Commands and Attributes 1.0.0 v1.0 Version: 1.0 Rack 3 Slot 5 Rack 3 Slot 6 Rack 4 Slot 1 Rack 4 Slot 2 Bit 3 Bit 2 Bit 1 Bit 0 SZP for Rack 4 Slot 3 SZP for Rack 4 Slot 4 SZP for Rack 4 Slot 5 SZP for Rack 4 Slot 6 Byte 6 TEM TXO N KLMNXY Status of Controller Temperature 1 Status of Optical Transmitter 6 These values are Hex Coded, and should be used in conjunction with COM status for actual device.
Document name: OMU Commands and Attributes 1.0.0 v1.0 ILD NNNN EX1/EX2/EX3/ EX4 NON RCH Version: 1.0 4 NNNN Status of Input Level Downlink as measured in Splitters 1-4 Status of external alarm inputs NN NNNNNN Number of nodes monitored.
