Professional Documents
Culture Documents
FOX515
LOMIF 152 & LOMI4 151
User Manual
User Guide LOMIF 152&LOMI4 151 (R8)
User Guide
LOMIF 152 & LOMI4 151
Platform FOX515 Release R8
Copyright and Confidentiality: All rights of this document remain with ABB
Ltd (ABB). This document contains confidential information which is the
property of ABB. It must be held in confidence by the recipient and may not
be used for any purposes except those specifically authorised by contract or
otherwise in writing by ABB. This document may not be copied in whole or in
part, or any of its contents disclosed by the recipient to any third party,
without the prior written agreement of ABB.
Disclaimer: ABB has taken reasonable care in compiling this document, however ABB
accepts no liability whatsoever for any error or omission in the information
contained herein and gives no other warranty or undertaking as to its
accuracy.
ABB reserves the right to amend this document at any time without prior
notice.
ABB Ltd
Power Systems
Bruggerstrasse 72
5400 Baden – Switzerland
Contents i
1 Introduction 7
Summary 7
Front panel 9
2 Architectural description 11
Block diagram 11
Description 12
3 Functional description 15
2 Mbit/s G.703 interfaces 15
4 Installation 17
Prerequisites 17
Slots 17
Connections and cables 17
Fixing the cables to the cable tray 23
5 Configuration 25
Setting the parameters 25
Setting alarm parameters 33
Summary of default UCST parameters 34
6 Operation 35
Status/maintenance 35
Displaying status 36
Setting loops 39
Performance monitoring 47
Protection switching with the LOMI<X> 49
8 Maintenance 57
Inventory data 58
Software download 58
Upgrades 58
9 Summary of Standarts 59
10 Technical Specification 63
Parameters controlled via UCST 63
Modes and traffic signals 65
Performance monitoring 66
Maintenance functions 66
Physical 2 Mbit/s signals 67
Power consumption 67
Mechanical Parameters 68
Reliability 68
Except for the standard precautions for ESD outlined in the installations sec-
tion when handling the unit, there are no special safety precautions to be fol-
lowed in installing and configuring the LOMIF and LOMI4.
For generic information on precautions and safety refer to the Precautions
and Safety User Guide.
Referenced documents
1KHW002000 Precautions and safety
1KHW002057 FOX515 Technical Description
1KHW002058 FOX 12 Technical Description
1KHW002013 COBUX 212, 213 & COBUV 217, 218
COBUX 219, 223 & COBUV 220, 224 User Guide
1KHW002024 User Guide LOMIF 152 & LOMI4 151
1KHW002059 FOX User Guide
1KHW002007 FOX Network Functions
Technical support
E-Mail: utility.communication@ch.abb.com
URL: www.abb.com/utilitycommunications
1 Introduction
Summary
The LOMIF (Low Order 2 Mbit/s InterFace) and LOMI4 functional units pro-
vide G.703 2 Mbit/s interfaces for the FOX515/512.
The LOMIF unit has 8 x 2 Mbit/s Tx/Rx interfaces according to ITU-T G.703
and uses 1 slot in the subrack. The LOMI4 unit is the same width as the
LOMIF unit but provides only 4 x 2 Mbit/s Tx/Rx interfaces.
The UCST R8B SP02 supports the LOMIF and LOMI4 as follows:
LOMIF 152
2 Mbit/s interfaces according to ITU-T G.703 with features as stated in
User Guide LOMIF 152 & LOMI4 151:
Definition of terms
Front panel
Fixing Screw
Pull-out handle
Product label
Pull-out handle
Fixing Screw
2 Architectural description
The LOMI<X> is implemented using the following functional blocks:
G.703 Interfaces
DXC
Peripheral Unit Communication C-LAN interface
CPU block with micro-controller, memory and peripheral logic
Power converter block
Block diagram
Front Panel
Backplane
Fault indication
Unit (SbU0)
CPU
Hardware Control
Fault indication
Traffic (SbU1-k)
r
Peripheral Unit
ICN
Communication
G.703 IF
8
7
6
5
4
2
3
Data Timing
1 PBUS
and PBUS
2 Mbit/s Timing IF PBUS
G.703 DXC
E12 interfaces: k
+3.3 V Power
+5 V
+5 V VCC_BP
0V GND
0V
-5 V
-5 V -VCC_BP
LOMIF: k=8
LOMI4: k=4
Description
G.703 IF
Depending on the LOMIF or LOMI4 unit, this block is repeated once for each
of the
8 interfaces of the LOMIF
4 interfaces of the LOMI4
and provides the following:
galvanic isolation
protection against over-voltage
signal receiver and transmitter
DXC
Depending on the LOMIF and LOMI4 unit this block is implemented with
2 ASICs for the LOMIF:
It provides access to the PBUS Interface and DXC (1/0) functionality for
the 8 x 2 Mbit/s signals.
1 ASIC for the LOMI4:
It provides access to the PBUS Interface and DXC (1/0) functionality for
the 4 x 2 Mbit/s signals.
For 2 Mbit/s signals in Terminated mode, the DXC is on a 64 kbit/s TS level
for TSs 1-31.
For 2 Mbit/s signals in Transparent and Monitored mode the DXC is on a 2
Mbit/s level where all 32 TSs including TS0 are grouped together.
Each ASIC interfaces to any one of the 32 PBUS highways available on the
subrack backplane via the PBUS Interface block. Each PBUS highway car-
ries up to four 2 Mbit/s signals.
An internal PLL is available and takes its reference clock from one of the 2
PBUS timing highways accessed. If both PBUS’s timing highways fail, the
timing signal is taken from the CPU. The 2 Mbit/s outputs that are synchro-
nised to the CPU are disabled (i.e. no signal at output).
The PBUS Interface block provides the connection for data and timing be-
tween the DXC and the PBUS highways on the subrack backplane.
This block is used to access system timing signals, hardware control lines for
reset and unit detection and the ICN that allows the COBU<X>/COBUQ to
communicate with the LOMI<X>.
CPU
The CPU block commands and controls all other functional blocks, and al-
lows communication with the COBU<X>/COBUQ via the ICN. A flash
EPROM for the unit’s ESW, an EEPROM for the inventory data, and a RAM
for the unit's configuration file are available.
Power
This block provides the 3.3 VDC needed by the DXC block. It comprises cir-
cuitry for monitoring the 5 VDC input, and circuitry for converting the 5 VDC
into the 3.3 VDC.
3 Functional description
All the 8 SbUs of the LOMIF and 4 SbUs of the LOMI4 support the following
functions independently:
Termination of G.704 framed signals with or without CAS and/or CRC-4
Transparent handling of G.703 unframed or G.704 framed signals
CRC-4 operation enabled/disabled for framed signals
Use of the TS0 Spare bits (called Sa-modes) for various applications
listed below for framed signals in terminated or monitored mode:
SSI (Synchronisation Status Indication) in Sa5 bit as currently used by
the UBUS units (MEGIF) in order to ensure proper network synchroni-
sation
ECC (Embedded Communication Channel) with TTI (Trail Trace Iden-
tifier) and SSM (Synchronisation Status Messages) uses all 5 bits.
SSM (Synchronisation Status Message) in any Sa bit according to
ITU-T G.704
V5.x application in order to allow the link identification procedure of
V5.2 to take place (Sa7 bit = logical “0“ from 2 of 3 consecutive G.704
frames). The Sa bits are all fixed to logical “1“ for V5.1
Fixed to an operator defined pattern
PRA application that allows you to implement the functional blocks of
the NT1 and the LT in the FOX network:
NT1-T (PRA)
NT1-U (PRA)
LT-V3
LT-U
For details of the PRA application and implementation (the handling of
the Sa-bits and the A-bit), refer to the chapter “E12 and E12/P12 Traf-
fic Signal Layer” in FOX Network Functions.
NT1 Leased Line application that allows you to implement the NT1
Leased Lines functional blocks in the FOX network:
NT1-T (LL)
NT1-U (LL)
For details of the NT1 Leased Line application and implementation
(the handling of the Sa-bits and the A-bit), refer to the chapter “E12
and E12/P12 Traffic Signal Layer” in FOX Network Functions.
Routing table for SSI or SSM data provided with terminated traffic signals.
Control of the TTI (for the ECC Sa-mode only)
Status/Maintenance functions to
Read status information related to the subunit (TTI, Sa-bits, loop
status etc.)
Apply loops in the signal path (front end and back end)
Performance Monitoring
according to G.826
count of frame slips
Maintenance/Status function for the CRC-4 MFA (Multi-Frame Alignment)
AIS Insertion in the 2 Mbit/s signal leaving the LOMI<X> IF B if the 2
Mbit/s input signal on port A fails (port A and B are cross connected via
P0_nc).
Bidirectional protection switching by using the remote defect indication as
switching criterion. This feature is mainly used uniform routing in case of
a unidirectional failure is required, e.g. in case of SPR (shared protection
ring) application.
For a detailed description of the E12/P12 traffic signal layer and correspond-
ing features and implementations, refer to the chapter “E12 and E12/P12
Traffic Signal Layer” in FOX Network Functions.
4 Installation
Prerequisites
Slots
The LOMI<X> takes up 1 slot in the FOX subrack. It can be inserted in all
slots except slot 11 which is reserved for the control unit and slot 21, which
has no PBUS access.
The pin assignment of the front panel connector X1 is shown in the figure
below.
Please note that the
LOMIF connects all 8 subunits (SbU1 … SbU8)
LOMI4 connects the 4 first subunits (SbU1 … SbU4)
The LOMI4 does not connect the pins assigned to the SbU5 …
SbU8.
X1
a b c s
b
32 Output
a
31
s SbU8
b
30 Input
a
For cable 29 s
latching clip b
28 Output
a
s SbU7
b
Input
a
s
b
Output
a SbU6
23
s
b
22 Input
a
21 s
b
20 Output
a
s SbU5
b
Input
a
s
b
Output
a
s SbU4
b
Input
a
12 s
b
12 Output
a
11
s SbU3
X1 b
10 Input
a
s
b
a c Output
32
a
s SbU2
b
Input
a
For cable 5 s
b
latching clip 4 Output
a
3
s SbU1
b Input
2
a
1 1
Depending on the cable used, the wires are connected to the pins for 120
Ohm or a 75 Ohm signal termination:
Signals a, b: 120 Ohm signal termination
Signals a, s: 75 Ohm signal termination
Please note that
LOMIF and LOMI4 use the same cables
LOMIF connects the cables for the SbU1 … SbU8.
LOMI4 connects the cables for the SbU1 … SbU4.
the cables provided by ABB Switzerland are internally con-
nected for 75 Ohm (pins a, s) or 120 Ohm (pins a, b).
the output signal b is available on two pins (row a and c). Avoid
unintentional connections to the pins with the redundant output
signal b.
for the cables specified below the
leads corresponding to inputs are referred as Rx
leads corresponding to outputs are referred as Tx
Do not enable G.703 subunits which are not connected at the re-
mote end of the cable. Cross talk onto such an open-ended cable
can cause spurious alarms.
By default, all the subunits are disabled.
Cables
View B
A
View A B
c a
Rx1
Tx1 View A
Rx2
Tx2
Rx3
Tx3
Rx4
Tx4
Rx5
Tx5
Rx6
Tx6
Rx7
Tx7
Rx8
Tx8
Latching clips MUST be used to secure the cable to the front panel connec-
tor.
View B
A
View A
B
c a
Rx1
View A
Tx1
Rx2
Tx2
Rx3
Tx3
Rx4
Tx4
Rx5
Tx5
Rx6
Tx6
Rx7
Tx7
Rx8
Tx8
line “a” of the cable connects to the centre lead of the coax-
ial connector,
line “s” of the cable connects to the shield of the coaxial ca-
ble.
Due to the mismatching impedances of the termination and ca-
ble you must keep the connection cable as short as possible (a
few metres). This requires that the 75 patch panel installed
close to the FOX (e.g. in the same rack).
If the symmetrical connection cables are longer than a few me-
ters, it is not possible to guarantee a LOMI<X> interface per-
formance according to ITU-T G.703.
Latching clips MUST be used to secure the cable to the front panel connec-
tor.
Cable modules
The cable must be attached to the cable tray of the FOX515 or the corre-
sponding device of the FOX512.
The figure below shows the cable/cable tray assembly of the FOX515.
5 Configuration
Units are automatically initialised when the power is switched on (i.e. when
the unit is plugged into the subrack). The unit obtains the configuration data
from the control unit.
Cross connections (assignment of the channels to the TSs of a transmission
SbU are made as described in FOX User Guide.
Please note that
all the dialogues are shown for the LOMIF unit. The same dia-
logues apply for the SubU1 … SubU4 of the LOMI4 unit.
some of the functions are not available with all unit versions, i.e.
with obsolete function units.
Double click on the unit you want to configure to open the Parameters…
dialogue or click on the LOMI<X> and select the dialogue via the menu Unit
Configuration Parameters….
P12-mode
Sa-mode
For details of the interdependencies, refer to the chapter “E12 and E12/P12
Traffic Signal Layer” in FOX Network Functions.
Enter (up to 16 characters) the name of the SbU. For tracing the signal to its
physical connecting point, the SbU name should be the same as its label on
the Main Distribution Frame.
Setting P12-mode
The selected SbU can be configured for the following types of 2 Mbit/s sig-
nals for the required application:
Transparent
Used for transparent 2 Mbit/s DXC of unframed as well as framed 2
Mbit/s signals.
DXC is only possible on a 2 Mbit/s level. No DXC is possible on a TS
level.
Monitored
Used for transparent DXC of framed 2 Mbit/s signals.
TS0 of the 2 Mbit/s frame and TS16 of the first frame of the G.704
multi-frame are monitored only and remain transparent.
DXC is only possible on a 2 Mbit/s level. No DXC is possible on a TS
level.
Terminated
Used for accessing TSs on 2 Mbit/s signals.
TS0 is terminated and monitored, and no longer transparent. TS0
spare bits are free to be used as specified below under "setting Sa-
mode", and "setting Sa bits".
TS 1-31 can be accessed for DXC or drop and insert applications.
Clock Master
Used for the provisioning of the NE timing as a timing reference via a
2 Mbit/s signal.
The mode is fully transparent for structured and unstructured traffic
signals and preserves all signal data. However the traffic signal leav-
ing the NE is re-timed to the clock of the NE.
Independently of the structure of the traffic signal, the Clock Master
signal must be cross connected in the FOX515 as a 2 Mbit/s traffic
signal.
The 2 Mbit/s signal can be configured for a multi-frame structure and TS16
used for the CAS signalling of the 30 PCM channels carried by the 2 Mbit/s
signal.
Both the local and the remote end must be configured the same.
Setting Sa-mode
For 2 Mbit/s signals configured for Terminated Mode, TS0 can be specified
to be used in one of the following ways:
SSI
Used for Interworking with UBUS units (i.e. MEGIF) .
TS0 bit 5 is used to indicate if the incoming 2 Mbit/s signal can be con-
sidered as a valid system synchronisation source.
The other 4 spare bits are available to be set by the user via the <Sa
bits> dialogue described below under "Setting Sa bits".
ECC
Used for carrying ECC, TTI and SSM.
TS0 bits 5-8 are used as a 16 kbit/s in band channel for managing the
FOX network.
TS0 bit 4 is used for TTI and SSM described below.
SSM G.704
Used for carrying SSM.
Select one of the 5 TS0 spare bits to be used for the SSM signalling. The
signal quality information (QL 1-15) is used in determining timing switch-
over for the FOX network.
You can set the other 4 spare bits via the <Sa bits> dialogue described
below under "Setting Sa bits".
The QL value of a 2 Mbit/s signal is NOT an indication of the signal qual-
ity but only a way to prioritise the signal for use as a synchronisation
source to 15 priority levels.
There are 2 ways that you can set the QL for an outgoing 2 Mbit/s traffic
signal and one automatic mechanism that sets the QL:
via the Timing Sources dialogue described in FOX User Guide. Set-
tings can be QL = 1-15. This option is used for 2 Mbit/s traffic signals
leaving the master FOX where the clock for the FOX network origi-
nates from.
via the Routing Table dialogue described below. Setting can be "Can
be used" and "Do not use" (i.e. QL = 15).
automatically by the FOX whenever it switches over to its internal
clock source. Settings can be defined as QL = 12-14.
For details on QL refer to FOX User Guide.
V5.x appl
Used for the termination of V5.x links and particularly the link for the iden-
tification procedure of V5.2.
All 5 bits in TS0 are used by the V5 application.
Fixed
You can set all 5 bits in the TS0, as described below.
PRA related Sa-modes:
NT1-T (PRA), NT1-U (PRA) (terminated P12-mode only)
LT-V3, LT-U (monitored P12-mode only)
The PRA application affects all 5 Sa bits in the TS0.
NT1 Leased Lines related Sa-modes:
NT1-T (LL), NT1-U (LL) (terminated P12-mode only)
The NT1 Leased Lines application affects all 5 Sa bits in the TS0.
For information on the application and implementation of the PRA and NT1
Leased Line function, refer to the chapter “E12 and E12/P12 Traffic Signal
Layer” in FOX Network Functions.
Both the local and the remote SbU must be configured the same.
Setting Sa bits
You can set the unused (free) Sa bits in TS0 depending on the mode of op-
eration (monitored or terminated).
You can set the 3 free bits of TS16 for Terminated 2 Mbit/s signals with CAS
as required.
The NT1-U (PRA, LL) and the NT1-T (LL) modes (but not the NT1-T (PRA)
mode) allow the selection of the Spare bits dialogue. The dialogue provides
functions as follows:
NT1-U (PRA) and NT1-U (LL) mode
For SbUs operated in the NT1-U mode you can define the Sa4, Sa7 and
Sa8 bit (direction NT2 ET).
NT1-T (LL) mode
For SbUs operated in the NT1-T (LL) mode you can define whether the
NT1-T (LL) inserts AIS when the NT1-U receives Sa6 = 1100:
Press [ ... ] under “Routing table” for the appropriate SbU in the Unit Con-
figuration Parameters dialogue.
Only the SSI, SSM and ECC Sa-modes provide routing tables.
The other Sa-modes do not provide routing tables.
For a FOX network to be able to operate error free, it must operate with a
pre-defined synchronisation plan that ensures that all the FOXs in the net-
work operate with the same clock (synchronously). This clock can be trans-
mitted to other FOXs in the network using 2 Mbit/s signals.
To prevent the entire network from losing synchronisation if one link in the
network fails, each FOX can be programmed with up to 7 back-up timing
sources that are switched to automatically in a pre-programmed order of pri-
ority.
To prevent timing conflicts such as timing loops and timing islands (isolated
FOXs) in the FOX network when one of the FOXs switches to a back-up tim-
ing source, each 2 Mbit/s output signal containing the timing to be transmit-
ted onwards can be tagged as “Do not use” depending on its own timing
source.
2 Mbit/s signals tagged “Do not use” as a timing source force the receiving
FOX using this signal as a timing source to switch over to another timing
source to prevent possible timing conflicts.
Example:
The above dialogue shows that the 2 Mbit/s output signal of the LOMIF
SbU2 is tagged as “Do not use” whenever the NE (with this LOMIF) is
synchronised to the timing source “ESI-2” or "LOMIF <1> 2 Mbit/s - 7".
The output signal is tagged "Can be used" for all the other timing
sources.
For more details, refer to the chapter “E12 and E12/P12 Traffic Signal Layer”
in FOX Network Functions.
This forces neighbouring NEs receiving this signal (if it is using this signal as
its timing source) to switch to a different timing source provided its Sa-mode
of operation is appropriately configured for proper interworking.
For SbUs configured for Sa-mode "ECC", TS0 bit 4 is used to carry a 15
character long trail trace identifier (TTI). At the far end, the received 2 Mbit/s
signal is monitored and the transmitted TTI is compared to an expected TTI
value for that signal.
If the transmitted TTI and the expected TTI are not the same, the non urgent
"Trace identifier mismatch" alarm is raised indicating that there is an uninten-
tional cross over of the 2 Mbit/s somewhere in the network.
Please note that:
According to specification and standards the definition of the
TTI requires the specification of 15 characters for a valuable
TTI.
You can fill up with "_" or " " (space) as filler characters. How-
ever it is not recommended that you use spaces due to poten-
tially faulty comparisons between received and expected TTI.
The AIS Insertion function is only available for SbUs that are configured for
the Terminated P12 mode.
If AIS insertion is enabled you can define which time slot in the P12 signal of
the SbU is monitored for the TSF (Traffic Signal Fail) flag. This flag is avail-
able for any timeslot of the P0_nc entity which is connected via the PBUS to
the source SbU (e.g. some other LOMI<X>).
The UCST allows you to define any TS (0 … 31) for the monitoring of the
TSF flag.
Please note that you can use the
TS0 for TSF monitoring only if you connect 2 SbUs using the
Sa-mode ECC (allows the cross connection of the TS0). For all
the other Sa-modes TS0 is not available on the PBUS.
TS16 for TSF monitoring only if you connect 2 SbUs which do
not use CAS (allows the cross connection of the TS 16). If CAS
is enabled, TS16 is not available for TSF monitoring.
For details of the AIS Insertion function, refer to the chapter “E12 and
E12/P12 Traffic Signal Layer” in FOX Network Functions.
The Bidirectional Switching function is only available for SbUs that are
configured for the Terminated P12 mode.
Bidirectional switching in a 1+1 protection switching configuration means that
a unidirectional failure results in a protection switching action at both ends of
the failed path. Protection switching must therefore be activated in the net-
work element either by locally detected signal failures or by a received re-
mote defect indication.
All locally detected signal failures activating a protection switching action
must also generate a remote defect indication to the far end. Failures not ac-
tivating a protection switching action must not generate a remote defect indi-
cation.
This strict behaviour of the failure handling procedures of LOMI<X> is
achieved by enabling the “bidirectional switching”.
Please note that the switching criteria with “bidirectional switching”
are different from the normal SNC protection switching criteria.
Please refer to section “Protection switching with the LOMI<X>” for
further information.
Unit parameters
Unit alarms
6 Operation
Status/maintenance
Displaying status
State
Active SbUs have the Enabled boxes tagged. Inactive SbUs have empty
boxes.
CRC-4 MFA
The LOMIF and LOMI4 units provide a Status/Maintenance function for the
CRC-4 MFA. It allows you to monitor the CRC-4 MFA for all the interfaces
with CRC-4 and if required trigger a new MFA manually.
Press [Get] to load the dialogue with the cur-
rent status information.
Displaying Sa bits
PRA link
This field is only provided for SbUs with the Sa-mode set for
NT1-T (PRA)
NT1-T (LL)
NT1-U (PRA)
NT1-U (LL)
LT-V3
LT-U
The SbUs with correctly configured NT1 or LT functionalities have their Es-
tablished boxes tagged.
To get the NT and LT functionalities Established you have to cross connect
in your NE
an NT1-T subunit with an NT1-U subunit
an LT-V3 subunit with an LT-U subunit
Established indicates that matching types of NT/LT functionalities
are connected together (e.g. an NT1-T to an NT1-U subunit).
However, Established is not able to detect whether the right part-
ners are cross connected in the signal path!
Setting loops
The figure below provides an overview of the loops provided with the
LOMI<X>.
AIS
64 kbit/s TS Loop
(Front End Loop)
2 Mbit/s Loop
(Back End Loop)
AIS
AIS
2 Mbit/s Loop
LOMI<X> (Front End Loop)
Output Input
2 Mbit/s
Traffic Signal
The following loops can be individually set for each of the 8 SbUs:
TS Loops (front end) (for framed signals only)
Loops individual TSs of the received 2 Mbit/s signal back to the local
CPE (Customer Premises Equipment). The loop is made in the DXC
block. AIS is sent onward on the TS on the 2 Mbit/s to the remote side
and on the relevant signalling bits abcd of the TS16.
Back End Loop
Loops the outgoing 2 Mbit/s signal (all TSs) back to the remote FOX.
AIS is transmitted to the 2 Mbit/s output.
Front End Loop
Loops the received 2 Mbit/s signal (all TSs) back to the local CPE
(Customer Premises Equipment). AIS is transmitted to the remote
CPE. For 2 Mbit/s signals in the terminated mode, AIS is sent on all
data TSs.
Please note that:
Loops are not part of the NE configuration. Due to this the con-
figuration of loops does not require configuration download. In-
stead the loops are set or removed immediately after the com-
To access the loop functions select the line, which corresponds to the sub-
unit and
press […] in the column Loops of the
Status/Maintenance dialogue in
the line of the selected SbU.
To update the loop block diagram in the Loops dialogue with the current
state of the loops
press [Get]
The loop switch boxes show the state of the loop as follows:
Active loops: Box shaded red with switch closed
Open loops: Box shaded green with switch open
Loops not available: Box shaded grey
Loop state not initialised: All boxes are shaded yellow with
switches open.
For SbUs configured for the “Terminated” mode of operation, selected TSs
of the 2 Mbit/s signal can be looped back (as front end loop). When CAS is
enabled, the signalling is also looped back. For TS loops with PRA modes,
refer to the next chapter.
From the Status/Maintenance dialogue
Press […] in the column Loops of the
Status/Maintenance dialogue in
the line of the selected SbU.
[Get] to update the loop block diagram
with the current state of loops.
Clear all 2 Mbit/s loops if there are
any.
It is not possible to apply TS loops if a 2 Mbit/s loop is active.
Loops for SbUs with PRA and NT1 Leased Line modes
The TS loop is not available for the LT modes since the P12 signals are
not terminated.
This mode provides the front and the back end loops on the 2 Mbit/s signal
level. For details on the loops, refer to the corresponding paragraphs above.
To de-activate loops
Loop indication
The fault management of the FOX gives the alarm “maintenance function ac-
tive” for subunits with active loops and indicates the condition via the lower
front panel LED (traffic LED).
Performance monitoring
For the definition of terms and a detailed description of the generic aspects
of the FOX performance monitoring, refer to 902.
The LOMI<X> supports Performance Monitoring (PM) depending on the
P12-mode as follows:
P12 Terminated EB, BBE, ES, SES, UT yes yes SLIP+, SLIP- yes -
Monitored EB, BBE, ES, SES, UT yes yes SLIP+, SLIP- yes -
The PM dialogue
Filtered PM
Unfiltered PM parameters
Principles
LOMI<X> Normal
SbU<n> Path
Tx<n>
Transmission
Network
Rx<s>
LOMI<X> Stand-by
SbU<s> Path
Tx<s>
Switching
criteria
LOMI<X>
SbU<t>
Tx<t> Rx<t>
Legend:
<n> Normal traffic signal path
<s> Stand-by traffic signal path
<t> Termination of the traffic signal path
It can be seen that the protection switching is closely related to the PBUS.
For this reason other PBUS units with the 2 Mbit/s traffic signal layer support
protection switching the same way (e.g. the PCONV, the SYNAC etc.).
For definition of the terminology and details of traffic signal protection with
the FOX, refer to FOX Network Functions.
Switching criteria The LOMI<X> supports various 1+1 protection switching network configura-
tions on both the n x 64 kbit/s TS level (n = 1-30) and 2 Mbit/s transparent
signal level.
Loss of Signal SF X X X
Loss of Frame SF X X -
AIS Received SF X X X
Loss of CRC4 MF 1) SF X X -
1)
Loss of CAS MF SF X X -
Degraded Signal SD X X -
1)
Depending on the settings for CRC4, CAS and TTI supervision.
SF Signal Failed
SD Signal Degraded
With bidirectional switching enabled (P12 terminated mode only), the follow-
ing criteria trigger the protection switch for the traffic signals:
1)
Depending on the settings for CRC4, CAS and TTI supervision.
Switchback
The protection switching is revertive. When the fault that caused the switch-
over clears, the signal path switches back from the protecting path to the
working path.
Failure indication
The FOX alarm system processes failures. The failures are locally indicated
via the front panel LEDs of the unit and the alarm LEDs of the COBU<X> (if
applicable).
The LOMI<X> front panel has two LEDs:
The upper LED indicates a unit failure if the unit no longer responds nor-
mally or if the unit self-test terminated with errors.
The lower LED indicates a traffic failure if the SbU reports a failure.
For the definition of terms (Defects, Fault Causes, Failures etc.) and details
of the FOX fault handling and alarm system, refer to the chapter "Diagnos-
tics, Fault and Alarm Handling" in FOX User Guide.
Board layer
The upper red fault indicator LED is lit in the case of a failure on the unit
level.
Board Unit not available UA This alarm indicates the complete failure of the unit. Hard-
ware and/or software problems can create the complete unit
failure:
- No hardware available (empty slot)
- The unit does not respond (unit failed)
- Wrong hardware in the slot
(with respect to the NE configuration)
- Unit with no or incompatible ESW
To reset the alarm you must eliminate the failure. With the
exception of the ESW based failures, the elimination of the
failure requires manual intervention.
PBUS clock DXC-1 Loss of signal UA Loss of PBUS clock detected via the PBUS access circuit 1 of
the LOMI<X> (ASIC 1).
The circuit monitors both clock buses fed by the control unit in
slot 11 and 12 respectively. The alarm becomes active only if
the clock signals of both buses fail.
PBUS clock DXC-2 Loss of signal UA Loss of PBUS clock detected via the PBUS access circuit 2 of
the LOMIF (ASIC 2).
The circuit monitors both clock buses fed by the control unit in
slot 11 and 12 respectively. The alarm becomes active only if
the clock signals of both buses fail.
PBUS data DXC-1 Loss of signal UA Loss of the data signal which is written by the PBUS highway
access circuit 1 of the LOMI<X> (ASIC 1) to its PBUS line.
PBUS data DXC-2 Loss of signal UA Loss of the data signal which is written by the PBUS highway
access circuit 2 of the LOMIF (ASIC 2) to its PBUS line.
The lower red fault indicator LED is lit in the case of a failure on the E12/P12
layer.
P12 Near End Degraded Per- NA For the LOMF 152 and the LOMI4 151 the ES and SES con-
formance ditions for degraded performance at the near end are:
ES >430 or SES >22 over a 24 hour interval.
The alarm status is reset after a 24 hour interval with ES = 0
and SES = 0.
P12 Near End Unacceptable NA ES>150 or SES>15 over a 15 min. interval at the near end.
Performance The alarm status is reset after a 15 min. interval with ES = 0
and SES = 0.
P12 Loss of Sa Word UA Loss of the framing of the Sa bits when configured for ECC
Mode. For example this alarm is activated when the local and
remote side configuration for Sa-mode are not the same.
P12 Loss of CAS MF NA Loss of multi-frame synchronisation on incoming E12 signal
P12 Loss of Frame UA Loss of frame synchronisation on incoming E12 signal
E12 Loss of signal UA Loss of incoming E12 signal
P12 Non CRC4 Interworking NA CRC monitoring function is disabled due to disabled CRC4 at
remote equipment.
P12 Remote Defect Indication NA Indicates one or more of the following alarms on the E12
signal received at the remote FOX:
Hardware fault, AIS received, BER >10E-3, Loss of frame,
Loss of signal.
P12 Remote Non CRC4 Inter- NA “Non CRC Interworking” alarm at remote equipment.
working
P12 Trace Identifier Mismatch NA Transmitted TTI from remote and expected TTI are not the
same.
P12 Maintenance Function NA This alarm appears if you manually activate a maintenance
Active function, e.g. if diagnostic loops are active.
Additionally, the NE issues this alarm, if a PRA or LL Loop
becomes active (controlled via the Sa6-bit). These loops are
only available with subunits operating in the NT1-T (PRA),
NT1-T (LL) and the LT-U mode.
P12 Far End Degraded Per- NA For the LOMF 152 and the LOMI4 151 the ES and SES con-
formance ditions for degraded performance at the far end are:
ES >430 or SES >22 over a 24 hour interval.
The alarm status is reset after a 24 hour interval with ES = 0
and SES = 0.
P12 Far End Unacceptable NA ES >150 or SES >15 over a 15 min. interval at the far end.
Performance The alarm status is reset after a 15 min. interval with ES = 0
and SES = 0.
Notifications
The LOMI<X> issues the following NE logbook entries for the board layer:
1 Application restarted due to DXC The LOMI<X> subunits are restarted due to degraded clock per-
ASIC formance during switchover between master and slave control
units.
The traffic signal of the affected subunits is interrupted for several
seconds.
8 Maintenance
Under normal use, there are no components on the LOMI<X> unit that need
maintenance.
The following maintenance facilities are available for the LOMI<X> (opera-
tion via the UCST/FOXMAN-UN):
Inventory data
FW Download
Inventory data It is possible to read inventory data from the LOMI<X> via the
UCST/FOXMAN-UN.
Upgrades
You can upgrade your existing LOMI<X> to new functional unit(s) described
with your new UCST release if the new functional unit is compatible with
your hardware and you have the corresponding software licence.
The upgrade of systems with LOMI<X> or PCONV (operating its 2 Mbit/s in-
terfaces) units to the functional units provided with new UCST software re-
quires special attention:
Upgrading the ESW and the functional units can destroy the syn-
chronisation via 2 Mbit/s interfaces if the transmitting LOMI<X> or
PCONV interfaces operate in the SSI mode!
Before you start the update and to avoid the loss of the synchronisation via
LOMI<X> or PCONV interfaces operating in the SSI mode consider:
If you do not upgrade the control unit ESW there is no risk of loss of syn-
chronisation by upgrading the LOMI<X>/PCONV ESW.
However, the LOMI<X>/PCONV ESW upgrade normally also includes the
upgrade of the control unit ESW. ABB Switzerland strongly recommends
upgrading the control unit with new ESW.
If you upgrade the control unit ESW in networks using the Sa5-bit of traf-
fic signals in the LOMI<X>/PCONV interfaces for synchronisation control,
an uncontrolled upgrade could lead to the interruption of the synchronisa-
tion.
To avoid interruptions of the synchronisation while upgrading the
LOMI<X>/PCONV and the control unit ESW proceed as follows:
Connect your PC/computer running the new UCST to the NE that you
want to upgrade.
Upload the NE configuration.
Open the Menu NE Configuration Timing Sources and select the
tab PETS.
Press [Ok] to save the configuration and quit.
Download the configuration to the NE via a partial or a full download.
Now you can update the ESW and the functional units as described in
FOX User Guide.
For detailed information on the upgrade procedures for the FOX core (con-
trol units) and traffic units, refer to the paragraphs "Upgrade procedures" in
FOX User Guide.
9 Summary of Standarts
The LOMI<X> conforms to the following recommendations (conformance to
applicable parts of the standards):
EMC
Refer to FOX515 Technical Description
Emission
Immunity
Safety
Ambient conditions
10 Technical Specification
Unit parameters
Parameters settable for each of the 8 subunits:
- Name (e.g. name of the MDF) : up to 16 characters
- State : enabled, disabled
- P12 mode : Transparent
Monitored
Terminated
Clock Master
- CAS : on, off
- CRC4 : enabled, disabled
- TS0 use of Sa- bits
- Generic modes : SSI
ECC
SSM
V5.x appl.
Fixed
- NT1 and LT modes
- Terminated P12 mode : NT1-T (PRA)
NT1-U (PRA)
NT1-T (LL)
NT1-U (LL)
- Monitored P12 mode : LT-V3
LT-U
- Spare bits
(Sa-bits available depend on use of Sa-bits)
- Sa-spare bits in TS0 : 1, 0
- Spare bits in TS16 : 1, 0
- Synchronisation
- Synchronisation information in output signal
- via routing table (for timing signal quality) :
- indication : “do not use”
“can be used”
- TTI parameters (for ECC mode only)
- TTI supervision : enabled, disabled
- Transmitted TTI : up to 15 characters
- Expected TTI : up to 15 characters
terminated P12 mode:
- AIS Insertion : enable
-.Signal Fail : TS0 … TS 31
- Bidirectional Switching : enable
Unit alarms
Alarm layers : Board
2 Mbit/s
Settable parameters per alarm and subunit:
- Supervision status : monitored (MON)
not monitored (NMON)
- Severity : urgent, non urgent
logbook entry only
- Time filters
- Persist Time : trapped
0.1 … 30 s
- Absent Time : 0.2 … 30 s
Performance Monitoring
Layers with performance monitoring : 2 Mbit/s
Settable parameters for Performance
(availability of parameters depends on evaluation)
- Location : near end / far end
- Evaluation of performance parameters : filtered / unfiltered
- Time interval for evaluation : 15 min / 24 h
- Presentation of results : events / ratios
- Interval presentation : selectable
- 15 min intervals : current
all
recent
1 … 96
- 24 h intervals : current
1
Status/Maintenance function
Layers with maintenance/status functions : E12/P12
Maintenance functions (if applicable)
- E12/P12
- Generic : received TTI
TTI state
Sa bits
Loops
- Status indication : PRA link
- Status and control for : CRC-4 MFA
Number of subunits
- LOMIF : 8
- LOMI4 : 4
Handling of traffic signals on the E12/P12 layer
- Framed signals (G.704 type) : terminated
monitored
transparent
clock master
- Unstructured signals (unknown structure) : transparent
clock master
PRA
PRA function
- Type of access : PRA direct access
- Functional groups of the PRA : NT1
LT
- Implementation of the function blocks
(2 Mbit/s subunits)
- NT1 function (P12-mode terminated) : NT1-T (PRA)
NT1-U (PRA)
- LT function (P12-mode monitored) : LT-V3
LT-U
- Sa4, Sa7 and Sa8-bits
- between ET NT2 : transparent up to
NT1-T (PRA)
- between NT2 ET : set to "1" ( NT2)
- M-channel, AUXP : not supported
specification
- Loop handling and functions : according to NT1 LL
specification
Loop control via Sa6-bit for the NT1-T (LL) : enable/disable
- Reception of Sa6 = 1000 on NT1-T (LL) : selectable
- ignore
- send AIS
V5.x applications
Performance monitoring
Filtered : ITU-T-G.826
Unfiltered : Slip counts
positive/negative
Maintenance functions
Power consumption
LOMIF
Current consumption (typical)
- +5 VCC power rail from POSUS : 460 mA
- -5 VCC power rail from POSUS : 68 mA
- -48 Vbat (direct from battery) : 0 mA
Typical total power requirements from battery
with
- -Nominal voltage Vbat = -48 V
- 71% efficiency of the POSUS
(0.460+0.068) A x 5.1 V / 0.71 : 3.8 W
LOMI4
Current consumption (typical)
- +5 VCC power rail from POSUS : 300 mA
- -5 VCC power rail from POSUS : 38 mA
- -48 Vbat (direct from battery) : 0 mA
Typical total power requirements from battery
with
- -Nominal voltage Vbat = -48 V
- 71% efficiency of the POSUS
(0.300+0.038) A x 5.1 V / 0.71 : 2.5 W
Mechanical Parameters
Construction
Construction practice : 19 inch
Dimensions
Height of unit (1 HU = 44.45 mm) : 6 HU
Width of unit (1 TE = 5.08 mm) : 4 TE (1 slot)
Size of the PCB : 233 mm x 220 mm
Weight
Unit hardware
- LOMIF : 350 g
- LOMI4 : 320 g
Reliability
www.abb.com/utilitycommunications