Eads Tetra System Release 5.5: Commissioning The Dxtip and Dxttip

Commissioning the DXTip and DXTTip
EADS TETRA System Release 5.5

DN0575507-04en
(TRADXTAPP00090) 01/2011
The content of this document and its appendices and any information provided (all together "document") is for information purposes
only and is subject to change without notice. The document only specifies the products and services identified in the document. The
document is confidential and contains legally privileged information.
The document is only intended for the use of the recipient and the customer whose representative the recipient is, and may only be used
for the purposes for which the document is submitted. The document or any part of it may not be reproduced, disclosed or transmitted
without the prior written permission of Airbus Defence and Space.
Airbus Defence and Space will reasonably ensure that the information provided in the document is free from material errors and
omissions. However, the suggestions, directions, comments and statements made in the document (e.g. regarding the compatibility,
performance and functionality of mentioned hardware and software) are not intended to be and cannot be considered as binding. The
customer assumes full responsibility for using the document or any part of it. All comments and feedback are welcomed by Airbus
Defence and Space and are used as part of the continuous development and improvement of Airbus Defence and Space’s products,
services and the document.
Airbus Defence and Space disclaim and exclude all representations, warranties and conditions whether express, implied or statutory,
including but not limited to the correctness, accuracy or reliability of the document, or otherwise relating to the document. Airbus Defence
and Space’ total liability for any errors in the document is limited to the documentary correction of errors. Airbus Defence and Space will
not be liable for any direct or indirect damages arising from the use of the document or otherwise relating to the document.
Airbus Defence and Space® is a registered trademark of Airbus Defence and Space. Other product names, trademarks or other
identifiers mentioned in the document may be trademarks of their respective companies and are mentioned for information purposes only.
Copyright © 2014–2015 Airbus DS SAS, all rights reserved.
DN0575507-04en EADS TETRA System Release 5.5
2/113 This document and its contents are the property of Airbus DS SAS and must not be copied or circulated without authorisation
Contents
1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2 Instructions before starting the commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.1 Safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.1 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.2 Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Fault reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.3 Measurement devices and tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4 Visual checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.1 General site inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.2 Installation checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.3 Site documentation checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.5 General prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.5.1 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.5.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 Test arrangements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1 General inspection information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.2 Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4 Inspection of hardware functioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.1 Checking interchangeability version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.2 Checking plug-in unit positions and message bus interface (MBIF) . . . . . . . . . . . . . . . . . . . . . . 21
4.2.1 Inspecting message bus connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.3 Checking the jumper connectors, DIP-switches and EPROM versions . . . . . . . . . . . . . . . . . . . . 26
4.4 Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.5 Supply voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.6 Peripheral units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.6.1 Visual display units (VDUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.6.2 Line printers (LPTs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5 Inspections of the software, I/O system and start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5.1 DXT(T)ip cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2 DXT(T)ip start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
EADS TETRA System Release 5.5 DN0575507-04en
This document and its contents are the property of Airbus DS SAS and must not be copied or circulated without authorisation. 3/113
5.2.1 Following DXT(T)ip start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.2 Preparatory steps before DXT(T)ip start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3 Monitoring the start-up of the whole system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.4 Opening the first MML session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.5 Inspecting the software versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.5.1 Installing customer-specific PRFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.5.2 Installing change releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.6 Inspecting the I/O system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.7 Checking the clock equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.7.1 Testing CL3TG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.7.2 Testing CLAB units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.8 Testing the processor units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.9 Verifying the message bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.10 Checking the ESB26 LAN ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6 Inspection of the maintenance system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6.1 Alarm system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1.1 Wired alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.1.2 External alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.2 Power breaks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.2.1 Complete power break in the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.3 State transitions and unit diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.3.1 State transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.3.2 Unit diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.4 Connecting external PCMs to ET4C cartridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.5 Spare plug-in units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7 Inspection of clock synchronisation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

7.1 Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.2 Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
7.2.1 Changeover to back-up connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.2.2 Changeover to internal oscillators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.2.3 Synchronisation with external clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.2.4 Faults correctable with MML commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8 Real-time clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9 Test logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.1 DXT(T)ip specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.2 Summary of the DXT(T)ip commissioning tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.3 Test log forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
9.3.1 Test 4.1: Interchangeability versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
9.3.2 Test 4.3: Checking the jumper connectors, DIP-switches and EPROM versions . . . . . . . 70
9.3.3 Test 4.4: Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
9.3.4 Test 4.5: Supply voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
9.3.5 Test 4.6: Peripheral units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
9.3.6 Test 5.2: DXT(T)ip start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
9.3.7 Test 5.4: MML session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
9.3.8 Test 5.5: Software versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
9.3.9 Test 5.6: I/O system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
9.3.10 Test 5.7: Clock equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
9.3.11 Tests 5.8 / 5.9: Processor units and message bus connections . . . . . . . . . . . . . . . . . . . 76
9.3.12 Test 5.10: ESB26 LAN ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
9.3.13 Test 6.1.1: Wired alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
9.3.14 Test 6.2.1: Complete power break in the system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
9.3.15 Test 6.3.1/6.3.2: State transitions and unit diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . 85
9.3.16 Test 6.4: Connecting external PCMs to ET4C cartridge . . . . . . . . . . . . . . . . . . . . . . . . . 86
9.3.17 Test 6.5: Spare plug-in units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
9.3.18 Test 7: Clock synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
A Execution instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . .......................... . . . . 91

A.1 Booting (reset) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .......................... . . . . 91
A.2 Starting the software and loading the files . . . . . . . . . . .......................... . . . . 93
A.3 Monitoring the start-up of OMU . . . . . . . . . . . . . . . . . . .......................... . . . . 96
A.4 Monitoring the start-up of CM . . . . . . . . . . . . . . . . . . . .......................... . . . . 99
A.5 Monitoring the start-up of other computers (ACU, STU, CCC, CCSU, EDU, SIPU, PDCU,
CCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .......................... . . . 102
A.6 Monitoring the start-up of the system . . . . . . . . . . . . . . .......................... . . . 104
List of Tables.
Table 1 DIP-switch settings of SW128B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 2 MBIF-CRs in the DXTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 3 MBIF-CRs in the DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 4 .................................................... . . . . . . . . . . . . . . . 25
Table 5 Supply voltage requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 6 Settings of the VDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 7 Settings of the LPTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 8 Message bus addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 9 Command groups for alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 10 Synchronization inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Table 11 ET2E-TB/ET2E-TCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 12 ECE2 and ET2E/ET4E index table: GSWB 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 13 ET4E/ET4E-C: Synchronisation cabling from PCM 128 – 191 (ET4C 0) . . . . . . . . . . . . . . . 60
Table 14 DXT(T)ip specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 15 Summary of the DXT(T)ip commissioning tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 16 .................................................... . . . . . . . . . . . . . . . 68
Table 17 Jumper connectors (Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Table 26 Jumper connectors (Part 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 27 Jumper connectors (Part 11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 34 Bridge connectors signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 35 EPROM versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 36 Inspection of the I/O system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 37 Processor units and message bus connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Table 38 Testing the alarm groups in the DXT(T)ip DXTA cabinet (CLS 0,1) . . . . . . . . . . . . . . . . . . . 81
Table 39 Testing the alarm groups in the DXT(T)ip DXTA cabinet (CLAB 0,1) . . . . . . . . . . . . . . . . . . 82
Table 40 ................................................. . . . . . . . . . . . . . . . . . . 83
Table 41 Testing the alarm groups in the DXTTip DXTB cabinet (CLAB 2, 3) . . . . . . . . . . . . . . . . . . 83
Table 42 Testing the alarm groups in the DXTTip DXTB cabinet (CLAB 4, 5) . . . . . . . . . . . . . . . . . . 84
Table 43 Complete power break in the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 44 Unit test: computer units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 47 Spare units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 48 ................................................. . . . . . . . . . . . . . . . . . . 97
Table 49 ................................................. . . . . . . . . . . . . . . . . . 100
Table 50 ................................................. . . . . . . . . . . . . . . . . . 102
Table 51 ................................................. . . . . . . . . . . . . . . . . . 105
List of Figures.
Figure 1 Sign for electrostatic sensitive devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 2 Contents of a plug-in unit ID label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 3 Group switch (GSW1KB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 4 Segment (A) and repeater (B) bus positions in MBIF-CR . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 5 CPRS-A (VDU and line printer connections) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 6 Layout of the DXT(T)ip DXTA cabinet with cabling cabinet . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 7 Layout of the DXTTip DXTB cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 8 Message bus verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 9 Synchronisation inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 10 Connection of an even ET from b13 to b10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 11 LAN ports: CM 0 in the DXTA cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 12 LAN ports: CM 1 in the DXTA cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 13 LAN ports: ACU 0 in the DXTB cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 14 LAN ports: ACU 1 in the DXTB cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
DOCUMENT AMENDMENTS
VERSION DATE COMMENTS CHAPTER

UPDATED
04 01/2011 Information on the synchronisation inputs has been 7.1
updated.
03 03/2009 Instructions for MBIF checking added. 4.2
Some minor corrections.
References
1. Time Management in EADS TETRA System, dn0484132
2. Installing the DXTip and DXTTip, dn063063
3. DXTip and DXTTip Jumper Settings, dn04167806
4. Cabling Instructions for the DXTip and DXTTip, dn04167833
5. DXTip and DXTTip Equipment List, dn04169197
6. PCM Links in DXTip and DXTTip, dn0498139
7. RCBUGG User's Manual, dn9774569
8. Integrated LAN Administration, dn0423824
9. DXT Alarm Reference Manual
10. DXT Command Reference Manual
11. Glossary, dn00126469
PAGE INTENTIONALLY LEFT BLANK
1 About this document
The purpose of the commissioning tests is to ensure that the Digital Exchange for TETRA DXTip and DXTTip
will correctly operate in the EADS TETRA network in its final location. When the commissioning tests have
been performed in an acceptable manner, the DXT(T)ip can be put into operation.
It is important to have an overall view of the commissioning process. Therefore, we recommend that the user
reads this commissioning manual before starting the actions.
This manual provides the information needed for commissioning the Digital Exchange for TETRA DXTip
and DXTTip. The purpose of the commissioning is
• to check that the installation has been performed properly
• to configure the DXT(T)ip so that it is ready for integrating into the system
• to fill in the test logs and give them to the field manager who then stores them on a server
The printouts included in the manual provide examples only, and therefore the actual printouts may differ from
the ones presented in this document.
Note
Some of the features, functionalities and equipment of the EADS TETRA System described in this document
may not be available in all market areas or are separately priced commercial options. Please contact your
EADS Account Manager for further information.
Note
The cabinet of the DXTip exchange is called the DXTip basic cabinet (DXTA). The DXTTip exchange always
includes two cabinets: DXTA and DXTB.
We welcome any suggestions for further improvement of this document. Also, should you find any errors
or ommissions in this document, please forward your comments to the local EADS representative or send
them to the e-mail address tetra.cudo@eads.com.
How to use this document
This manual provides the following information:

• Chapter 1 introduces this manual.
• Chapter 2 deals with issues to be taken into consideration before starting the commissioning procedure.
• Chapter 3 is a short introduction to the arrangements needed for the commissioning testing.
• Chapter 4 specifies how hardware functioning should be inspected in the commissioning tests.
• Chapter 5 tells how to inspect the software versions, the number and states of I/O equipment and the
output controls, and the monitoring of the system start-up. This section also deals with inspections of
clock equipment, message bus and LAN port connections.
• Chapter 6 gives instructions on checking the supervision, alarm, and recovery functions of the system.
• Chapter 7 tells how to check the functionality of the connection between the clock synchronisation units
and the OMU computer unit.
• Chapter 8 tells how to check the correctness of the real time in the exchange during a power failure in
the OMU.
• Chapter 9 lists the test logs and test log forms needed in the commissioning testing.
• Appendix A lists example printouts of the start-up procedures of the exchange.
The Glossary section gives full forms for abbreviations used in this document. The full version of the glossary
is provided as a separate document, Glossary, dn00126469.
An Index is provided at the end of this document.
2 Instructions before starting the commissioning
This chapter includes the following sections:
• Section 2.1 Safety instructions
• Section 2.2 Fault reporting
• Section 2.3 Measurement devices and tools

• Section 2.4 Visual checks
• Section 2.5 General prerequisites
2.1 Safety instructions

This section details the safety precautions to be followed when working with the DXTip and DXTTip.
The safety guidelines are designed so that the Warnings alert the reader to dangers which may cause
physical injury or ill health in any form, potentially including loss of life. Cautions are used to denote possible
damage to equipment but not dangers to personnel.
Note
The commissioning measures concerning the DXT(T)ip may be performed only by properly trained and
authorised personnel.
2.1.1 Warnings
Weight
Care must be taken when handling the racks. Use mechanical lifting equipment to lift a rack. If no lifting
equipment is available, install rack lifting eyelets.
High temperatures
Care must be taken when touching units as they may reach high temperatures.
2.1.2 Cautions
Handling of units containing electrostatic sensitive devices
An electrostatic sensitive device is an electronic component that may be permanently damaged by

electrostatic charges encountered in routine handling, testing, and transportation.
Electrostatic discharge protection
Electrostatic discharge is caused by direct contact or electrostatic field. If a charged body approaches an
electrically conducting surface, the acquired potential is discharged. An equalizing current can then flow in
the associated circuitry and generate permanently damaging voltages by induction.
CAUTION
Always wear a close-fitting earthing hand strap around your uncovered wrist when handling electrosensitive
DXT(T)ip units.
The human body should be earthed at the same potential as the component or equipment being handled.
The hand strap creates an equipotential electrical connection between the object and the human. There is an
earth stud in all DXT(T)ip racks, to which the hand strap must be connected.
Note
Check that a conductive carpet material (ESD) has been used in the floor structures. Also see that the
personnel has conductive ESD footwear.
Electrostatic sensitive devices are labelled as follows:
ATTENTION!
OBSER VE PRECAUTIONS
FOR HANDLING
ELECTROST ATIC
SENSITIVE
ATTENTION
DEVICES
Static Sensitive
Devices dn 00113797 x1x0xen
Figure 1 : Sign for electrostatic sensitive devices
In some units the sign may appear without the warning text.
2.2 Fault reporting

Correct all damages, failures and faults, if possible, and report them to EADS using the Failure Report Form
provided by your nearest EADS Customer Services.
2.3 Measurement devices and tools

The following is a summary of all the tools required when testing a DXT(T)ip.
1. Visual display unit, 1 pc.
• V.24 interface
2. Serial printer, 1 pc.
3. PC, 1 pc.
4. Standard LAN cable (RJ45-/9-pin), 1 pc.
5. Multimeter, 1 pc.
• digital
• accuracy +0.2 % or better
6. Pocket calculator (hex calculator)
7. Wrapping tools (0.25 and 0.40 sire), 1 set
• for making a wrap connection
• for breaking a wrap connection
8. Strapping tools (for example, OK Wire Wrap set)
• strapping wire, 1 pc.
• equipped with Minihook connectors
9. 3.2 mm hexagonal adjustable-torque wrench, 1 pc.
10. Tool set, 1 set
11. Printer paper
12. MO91 optical disk
13. Jumper links
14. Wrap connection wire (black-and-white, yellow, 20 m of both)
15. Release map with new software
2.4 Visual checks
2.4.1 General site inspection

Do the following before the commissioning:
• Check that the site is cleared of any waste material after the installation.
• Check that you can access the DXT(T)ip equipment safely.
2.4.2 Installation checks

Inspect the DXT(T)ip and make sure that the following items are in order:
Power
• The incoming mains AC/DC power is available for the site, the DXT(T)ip and the test equipment.
• The site main power switch and the circuit breakers are clearly labelled.
• The power cables are correctly terminated.
• The power cords of the equipment are connected to a grounded outlet.
Cables and connections
• Outgoing cables (cables connecting the DXT(T)ip to peripheral devices) are connected to the DXT(T)ip.
• Cables are correctly terminated.
• Connection of cables is secure.
• Cables are properly routed and clamped.
Cabinets and units
• The DXT(T)ip and the units have suffered no physical damage.
• Units are correctly jumpered and seated in the DXT(T)ip cabinets.
2.4.3 Site documentation checks

Make sure that all the appropriate documents as determined by the EADS project organisation or the
customer are in the site folder, if applicable.
The site-specific folder normally contains the following documentation:
• a set of customer documents including
– Installing the DXTip and DXTTip, dn063063
– Commissioning the DXTip and DXTTip, dn0575507 (this document)
– Cabling Instructions for the DXTip and DXTTip, dn04167833
– DXTip and DXTTip Jumper Settings, dn04167806
– DXTip and DXTTip Equipment List, dn04169197
• site-specific information.
2.5 General prerequisites

The most important prerequisite for the successful commissioning is that the system has been set up in the
normal configuration in the test field of EADS Networks, and that EADS Networks has made the tests
associated with the configuration.
2.5.1 Files
At least the files associated with the configuration must be ready on the hard disks of the DXT(T)ip.
2.5.2 Software
All the software that belongs to the DXT(T)ip must be ready on the hard disks of the system before starting
the commissioning tests. If there are newer software versions available than those installed on the hard disk,
the exchange must be commissioned using the software on the disk. The newer software versions should
then be installed before integrating the DXT(T)ip into the system.
3 Test arrangements
This chapter describes the arrangements for the commissioning testing of the DXT(T)ip.
3.1 General inspection information

The commissioning testing of the DXT(T)ip can be started when the installation has been checked.
The main phases of the testing are executed in the order presented in this document.
Test logs are filled in during the testing. The test logs are included in this document, see Chapter 9 .
Any detected faults are reported using the EADS Networks failure report, which is then sent to the EADS
Networks Customer Service.
3.2 Personnel
The persons performing the commissioning testing should have a good knowledge of the system and
preferably previous experience in the commissioning testing of the DXTip and DXTTip series exchanges.
4 Inspection of hardware functioning
This chapter specifies how hardware functioning should be inspected in the commissioning tests of the
DXT(T)ip:
• Section 4.1 Checking interchangeability version
• Section 4.2 Checking plug-in unit positions
• Section 4.3 Checking the jumper connectors, DIP-switches and EPROM versions
• Section 4.4 Grounding
• Section 4.5 Supply voltage
• Section 4.6 Peripheral units
4.1 Checking interchangeability version

The purpose of the test is to verify that the cartridges and plug-in units have the correct interchangeability
versions.
Check the interchangeability versions of cartridges and plug-in units by comparing them to the Network
Element HW Revision List of the DXT(T)ip and write them down into the Interchangeability version table
given in Chapter 9 .
The interchangeability code is shown on the unit ID label. Figure 2 shows the items included in this label.
INTERCHANGEABILITY CODE
IDENTIFICATION CODE VERSION BARCODE FOR ELECTRONIC

NUMBER REGISTRATION
UNIT NAME
B MBIF-A 1C889146 ... A01
A MBIF-A SERIAL NO : 1F 984401267

dn05195937x1x0xen
Figure 2 : Contents of a plug-in unit ID label
4.2 Checking plug-in unit positions and message bus interface

(MBIF)
Check that the plug-in units are installed in the correct slots in the cartridges. For instructions, refer to
document Installing the DXTip and DXTTip, dn063063.
You should pay special attention to the correct positions of the following plug-in units:
1. Position of the SW128B card 1
Note
Jumpering of the SW128B card 1 is different from the jumpering of other SW128B cards. Card 1 must
always be located in slot 02 of the GSW1KB.
Table 1 shows the differencies in the DIP-switch settings between the SW128B card 1 and cards 0, 2
and 3. Figure 3 shows the correct position of the SW128B card 1.
Table 1 : DIP-switch settings of SW128B
Cards 0, 2, 3 S2/1–8 OFF

S2/2–7 OFF
S2/3–6 OFF
S2/4–5 OFF
Card 1 S2/1–8 ON
S2/2–7 ON
S2/3–6 OFF
S2/4–5 OFF
SW 10 C-A
S W128B 2
S W128B 0
S W128B 1
S W128B 3
01 02 03 04 05 06 07 08 09
SW 128 B cannot be equipped to slot 09.
Available slots for SW 128 B are 01 ...08.
dn0700914x1xoxen
Figure 3 : Group switch (GSW1KB)
2. Positions of the MBIF-CR cards
Check that the MBIF-CR cards have been installed as follows:
Table 2 : MBIF-CRs in the DXTip
MBIF-CR: CM 0 slot 05 (MBIF-C slot 06)

Table 3 : MBIF-CRs in the DXTTip

MBIF-CR: STU 0 slot 08 (MBIF-C slot 09)
MBIF-CR: STU 1 slot 09 (MBIF-C slot 08)
4.2.1 Inspecting message bus connections
Note
The procedure for measuring the message bus interface described below is necessary only if the connection
is not operating normally.
The power must be switched off in the network element before message bus (MB) inspections are made.
Equipment:
• Multimeter
Inspecting message bus connections in MBIF-C configuration
1) When using MBIF-C, the message bus is divided into a repeater bus and segments at the hardware
level. All segments are connected to each other by repeater bus (by intercabinet cables). Note that all
MBIFs in a segment (cabin) must be pulled out of the cartridge.
1.1 Take measurements of each segment from the track of MBIF- CR. Terminators need not be
removed while measuring a segment.
1.2 Measure the resistance between A and B beams of each signal from the front side of the cartridge.
Pins are presented in the table below.
Measurements are taken in the upper part of the MBIF-CR track, pin rows 10 – 21, as shown in the
figure Segment (A) and repeater (B) bus positions in MBIF-CR below.
Figure 4 : Segment (A) and repeater (B) bus positions in MBIF-CR
Nominal values are 100 Ohm + the resistance of intracabinet cables. Segment resistance
deviations vary between 105 Ohm and 117 Ohm, depending on the number of computer cartridges.
2) Inspecting a repeater bus in MBIF-C configuration.
2.1 Remove the MB terminator TRM9C from the end of MB (on the back side of the track where
MBIF-CR is installed) and pull out all plug-in units from the cartridge. Note that all MBIF-CRs
must be pulled out of their cartridges.
2.2 Measure the resistance between A and B beams of each signal from the front side of the cartridge.
Measurements are taken in the lower part of the MBIF-CR track, pin rows 15 – 1, as shown in
Figure Segment (A) and repeater (B) bus positions in MBIF-CR above.
The nominal values are 100 Ohm + the resistance of intercabinet cables on the bus.
Resistance deviations vary between 100 Ohm and 108 Ohm, depending on the number of
computer cabinets.
Inspecting message bus connections in MBIF-B configuration

1) Remove the MB terminators TRM9B from the end of MB.
2) Measure the resistance between earth behind the cartridge (GND) and pins in the cartridge under the
MB terminator. Pins are presented in the table below.
Note
MBIF plug-in units must be pulled out.
The nominal values are:

• MD0x..MD15x, MDPx, MWRx, PACKEDx = 33 Ohm + (3 Ohm × number of cabinets)
• MREx, MRE2x, MACx, MSYx, MAEx = 47 Ohm + (3 Ohm × number of cabins)
The result cannot deviate more than 2 Ohm in the same network element.
Table 4 :
Cable F E D C B A Z
position
a GND PACKED B PACKED A GND MRE 2 B MRE 2 A GND

GND MD 1 B MD 1 A GND MD 0 B MD 0 A GND
c GND MD 3 B MD 3 A GND MD 2 B MD 2 A GND

e GND MD 7 B MD 7 A GND MD 6 B MD 6 A GND
g GND MD 11 B MD 11 A GND MD 10 B MD 10 A GND

j GND MD 15 B MD 15 A GND MD 14 B MD 14 A GND
GND MAC B MAC A GND MSY B MSY A GND
Table 4: (cont'd.)
l GND MRE B MRE A GND MAE B MAE A GND

GND MDP B MDP A GND MWR B MWR A GND
4.3 Checking the jumper connectors, DIP-switches and EPROM

versions
The purpose of the test is to verify that the plug-in units that include jumper connectors, DIP-switches or
EPROMs are correct.
Check the EPROM versions of the plug-in units by comparing them to the Delivery List.
4.4 Grounding
Check the resistance between the main earth bus bar and the earthing point of the DXT(T)ip with a digital
multimeter. The resistance should be less than 2 ohms.
4.5 Supply voltage

The purpose of the test is to inspect the supply voltage of the DXT(T)ip.
Measure the supply voltage from the DXT(T)ip power supply lines. Table 5 presents the required voltages
and tolerances.
Table 5 : Supply voltage requirements
Voltage Nominal Tolerance

Feed voltage to DC/DC converters -48 V -40 V to -72 V
-60 V -40 V to -72 V
4.6 Peripheral units

The visual display units (VDUs) and line printers (LPTs) are connected to the DXT(T)ip DXTA cabinet.
The purpose of the test is to inspect the strappings and settings made at the factory. The other required
parameters (baud rate, data bits etc.) are set.
Perform internal tests in units which are equipped with test functions. Send faulty units to service.
LPT VDU
0* / 4** 1* / 5** 0* / 4** 1* / 5** LPT2 / VDU2
POWER
ON
2* / 6** 3* / 7** 2* / 6** 3* / 7** LPT3 / VDU3
Alarm
1 8 1 AL0 1 8 1 DTR 1 8 1 TxD+

2 AL1 2 TxD 2 TxD-
3 AL2 3 GND 3 RxD+
4 AL3 V.24 4 GND V.11 4 -
5 - 5 RxD 5 -
6 - 6 DSR 6 RxD-
7 - 7 CTS 7 -
8 - 8 R TS 8 -
* indicates unit index for first panel and
* *indicates unit index for second panel B
A
dn 0292153 x2x0xen
Figure 5 : CPRS-A (VDU and line printer connections)
4.6.1 Visual display units (VDUs)

After you have switched the power on, test the terminal by pressing the TEST switch.
When the power is switched on, the VDU-port serial line parameters are in their initial values. Table 6
shows the default settings of the VDUs.
Table 6 : Settings of the VDUs
VDU mode VDU220

Baud rate 9600
Data bits 7
Stop bits 2
Parity even
Page length 23
Line length 80
Check the interface cable by measuring the resistance with a multimeter.
If the cable is in order, connect the female connector to the VDU and join the male connector to the DXT(T)ip.
Type any text on the keyboard. The terminal is OK if the typed text is echoed to the screen. If no text
is displayed, the VDU unit or the SERO-B plug-in-unit is faulty, or the serial line parameters are not in
their initial values.
4.6.2 Line printers (LPTs)
Check the settings of the line printers. Table 7 shows the default settings of the LPTs.
Table 7 : Settings of the LPTs
Printer type dummy

Baud rate 9600
Data bits 7
Stop bits 2
Parity even
Page length 65
Line length 80
Correct any incorrect settings and perform internal tests on those printers that are equipped with test functions.
5 Inspections of the software, I/O system and
start-up
The sections of this chapter specify how the software, I/O system and start-up should be inspected:
• Section 5.1 DXT(T)ip cabinets
• Section 5.2 DXT(T)ip start-up

• Section 5.3 Monitoring the start-up of the whole system
• Section 5.4 Opening the first MML session
• Section 5.5 Inspecting the software versions
• Section 5.6 Inspecting the I/O system
• Section 5.7 Checking the clock equipment
• Section 5.8 Testing the processor units

• Section 5.9 Verifying the message bus
• Section 5.10 Checking the ESB26 LAN ports
5.1 DXT(T)ip cabinets

The following figures show the location of functional units in the DXTip and DXTTip cabinets.
CABLING
DXTA CABINET
PDFU -B PDFU -B
0 PDFU 0 PDFU 1
CPBP 0
CLAB 0, 1
DC3C-A DC3C-A
CLOC-B
CLS 0, 1
CLAC-B
SIPU PDCU SIPU PDCU
0 0 1 1 CPEA 1
1 0 2 4 6 8 10 CPRS -A 2
SW 10 C-A SW 10 C-A CM2C-A

CPLC 18 3
GSWB GSWB OMU
0 1
FTRB -A 0 FTRB -A 1 CPLAN-A 4
2 0 3 6
CC 4C-A CC 4C-A CC 4C-A CC 4C-A CPLAN-A 5

CCC CCC CM CM
0 1 0 1 CPETS /
CPETC 6
3 0 3 6 9
CPETS /
CPETC 7
CC 4C-A CC 4C-A CC 4C-A CC 4C-A
CCSU CCSU CCSU CCSU CPETS /

0 1 2 3 8
CPETC
FTRB -A 2 FTRB -A 3
4 0 3 6 9 CPETS /
9
CPETC
DC3C-A
ET4C-B
SIPU SIPU CPLA /
CPETS
10
2 3 ET4C 0 CPETC
N
5 0 2 6
dn 0532635 x2x0xen
FRONT SIDE
Figure 6 : Layout of the DXT(T)ip DXTA cabinet with cabling cabinet
DXTB
PDFU-B PDFU-B
PDFU 0 PDFU 1
0
DC3C-A DC3C-A
CLAB 2, 3
CLAB 4, 5
CLAC-B
CLAC-B
SIPUSIPU SIPUSIPU
4 5 6 7
1 0 2 4 6 8 10
CM2C-A CM2C-A
ACU 0 ACU 1
SD 0 ACU SD 1 ACU
FTRB-A 0 FTRB-A 1
2 0 6
CC3C-A CC3C-A DC3C-A
STU 0 STU 1
SD 1 STU CCM 0
SD 0 STU
3 0 4 8 10
DC3C-A DC3C-A DC3C-A
EDU 0 EDU 1 CCM 1
FTRB-A 2 FTRB-A 3
4 0 2 4 6 8 10
CC4C-A CC4C-A
ET4C-B
CCSU CCSU
4 5 ET4C 1
5 0 3 6
dn0532662 x2x0xen
FRONT SIDE
Figure 7 : Layout of the DXTTip DXTB cabinet
5.2 DXT(T)ip start-up

This section describes the monitoring of the system start-up and offers solutions to possible disturbance
situations. Before starting the monitoring of the system start-up, the user should carefully read this section
and the execution instructions in Appendix A because the start-up procedure is very fast.
5.2.1 Following DXT(T)ip start-up
The start-up of the whole system depends on the start-up priorities of the computer units. A unit with a higher
priority is given loading permission before a unit with a lower priority. Within the system, the units are started
up, according to their respective priorities, in parallel. For example, all base stations are given permission to
load simultaneously as they all have the same priority. In the case of doubled units, the working units are
given loading permission first, before the spare units.
The start-up of the whole system begins with the start-up of the maintenance units. The maintenance
units comprise the units where the centralised parts of the recovery and alarm system are located (OMU
and CM). The start-up order of the whole system is:
1. OMU
2. CM
3. STU (not in the DXT(T)ip DXTA cabinet)
4. CCC
5. ACU, EDU (not in the DXT(T)ip DXTA cabinet)
6. Other units
5.2.2 Preparatory steps before DXT(T)ip start-up

1. Connect the MML terminal to the VDU port.
2. Connect the alarm printer to the LPT port.
3. Connect the service terminal to the upper port (J7) of the CP816-A front panel.
5.3 Monitoring the start-up of the whole system

The start-up of the system is monitored from the OMU and from the units being started up. If the state of the
OMU is TE or SE, the start-up is monitored in the CM.
1. Monitor the start-up of the OMU (see Appendix A ). The failure of the OMU to start up could lead to a
similar failure in all the other units. The working state of the OMU should be WO-EX during the start-up
of the system. If the OMU is in the TE or SE state, the maintenance programs will be started up
in the Central Memory (CM).
2. Monitor the start-up of the CM (see Appendix A ). The active CM is started up after the OMU. If the
start-up of the active CM fails, the loading of the other units will not be continued. Most of the files
are loaded from the CM unit memory.
3. Monitor the start-up of the ACU, STU, CCC, PDCU, EDU, SIPU (0,0), SIPU (0,1), CCSU, and CCM
units (see Appendix A ).
Connect the service terminal to the upper port (J7) of the CP816-A front panel.
Note
In one-cabinet DXTip exchanges, SIPU units are optional if the external CDD server has been replaced with
DXT's Integrated Data Distribution Functionality feature.
PDCU computer units in a DXTip are always optional.
First, the start-up of the OMU is monitored at its service terminal. When the MMI system has been started
up, the start-up of the system can also be monitored with command ZUSI of the Working State and Restart
Handling (RCVHAN) MML.
When the start-up of the OMU has reached the stage where the service terminal software is started up, the
Recovery Service Terminal (RCBUGG) extension can be taken into use. The RCBUGG contains commands
that correspond with those of the RCVHAN MML. Even if the start-up of the MMI system fails, the working
states of the units can be controlled with the RCBUGG. A prerequisite for the successful running of the
RCBUGG is that the recovery system itself has been started up (the program blocks RCXPRO, FUZNLM,
and USAPRO have been started up and the file SCDFLE has been loaded, see Appendix A ).
For monitoring the start-up of units with the RCBUGG extension at OMU, use the following commands:
ZLP:U,RCB
to bring the RCBUGG into use,
ZUSI:COMP
to monitor the states of the computer units.
For further information on the use of the RCBUGG, refer to document RCBUGG User's Manual, dn9774569.
5.4 Opening the first MML session

When a system is delivered from EADS, the username of the system has been defined as <SYSTEM> and
the password as <SYSTEM>. These username and password definitions are of a general nature and they are
intended to be used only in factory acceptance testing. The actual authority definitions for the terminals and
users are made with MML commands, for example by the main user of the system or other corresponding
person. The procedure for setting up the first session, and for defining and testing the username and
password is presented in the following section. Examples are also provided.
Steps
1) Check that the display unit is connected to the system as an MML terminal and that the printer has
been connected to the line printer (LPT) port of the system.
2) Connect power to the display terminal and printer. The functioning of the printer is dealt with later in
this section. After power has been connected to the display and the user has pressed a key, the
following text should appear on the screen:
ENTER USERNAME <
3) Enter the username SYSTEM and press <CR>. The following text is displayed:
ENTER PASSWORD <
4) Enter the password SYSTEM and press <CR>.
If the setting up of the session is successful, the following is displayed:
WELCOME TO THE DX200-SERIES DIALOGUE
MAIN LEVEL COMMAND <___>
<
Check the printer interface:

• Check that the printer interface is in order by printing out, for example, the states of the I/O devices.
When printing to the VDU, use command
ZISI;
When printing to a printer, use command
ZISI:::,LPT0;
• If the printing is not successful, proceed as described in Section 5.6 .
Typical faults
The following error messages may appear on the screen when setting up the first MML session:
/*** PASSWORD TOO SHORT ***/
The password is too short (minimum length is six characters). Enter the password again.
/*** USER AUTHORISATION FAILURE ***/
The username entered has not been programmed into the system or the password has been given incorrectly.
Enter the password again.
5.5 Inspecting the software versions

The list of software versions is a separate document within the Release Note. However, take a print-out of the
current software versions, and add it to the site-specific folder.
Start an MML session and print out all software packages installed in the program disks.
When printing to the VDU, use command
ZWQO;
When printing to a printer, use command
ZWQO::,LPT0;
Perform a verification for each software package with command
ZWQB;
During the execution of the command, let the display be printed out on the printer. Check if any faults have
been detected and compare the printout with the delivery documentation.
5.5.1 Installing customer-specific PRFILE

Install the customer-specific PRFILE if the customer has ordered new features. For instructions refer to
the PRFILE installation documentation.
5.5.2 Installing change releases
Install the latest change deliveries into the system. In network cases, check the change delivery level and
install change deliveries up to that level. Instructions for every change delivery can be found in the change
delivery documentation.
5.6 Inspecting the I/O system
The test is used for inspecting the number and states of I/O equipment and the output controls (=
correspondence with the source data).
Numbers and states of the I/O devices
Steps
1) Check that the correct numbers of I/O devices have been packaged for the system.
2) Check their states and state transitions.
3) Connect the MML terminal to the VDU port and display the I/O devices of all the units of the system and
compare the number of the devices with the source data using command
ZISI;
Checking MO91 magneto optical disk
Steps
Before starting this phase make sure that you have a MO91 disk in the drive.
Check that the state of the MO91 disk is WO-ID. Use the following command:
ZISI::FDU,0;
1) Set the paths for the source and destination directories with the following command:
Example for OMU:
ZIWY:S:UNIT=OMU,PATH=-LFILES,DRIVE=WDU-S;
ZIWY:S:UNIT=OMU,PATH=/MB_x_y_z/LFILES,DRIVE=WDU-S;
ZIWY:D:UNIT=OMU,PATH=LFILES,DRIVE=FDU-N0;
2) Copy for example the LFILES directory to the MO91. Check that the files are there using commands
ZIBC:,,%,%,,,,,,DIR::;
ZIWX::F1,NODEF:LFILES:%,%;
The DXT(T)ip system uses the following I/O outputs:
LOADING PROGRAM VERSION 11.4-0
I/O DEVICE WORKING STATE AND SPARE DEVICE
SYSTEM = DXT UNIT = OMU
DEVICE STATE SPARE DEVICE DEVICE STATE TAPE STATE TAPE TYPE
FDU-00 WO-BU - -
WDU-00 WO-BU - -
WDU-01 WO-BU - -
LPT-00 WO-ID DXT OMU LPT-01 -
LPT-01 BL-SY DXT OMU LPT-00 -
LPT-02 BL-SY - -
LPT-03 BL-SY - -
VDU-00 WO-ID - -
VDU-01 BL-SY - -
VDU-02 BL-SY - -
VDU-03 BL-SY - -
VTP-00 BL-SY - -
VTP-01 BL-SY - -
VTP-02 BL-SY - -
VTP-03 BL-SY - -
VTP-04 BL-SY - -
VTP-05 BL-SY - -
VTP-06 BL-SY - -
VTP-07 BL-SY - -
VTP-08 BL-SY - -
VTP-09 BL-SY - -
VTP-10 BL-SY - -
VTP-11 BL-SY - -
VTP-12 BL-SY - -
VTP-13 BL-SY - -
VTP-14 BL-SY - -
VTP-15 BL-SY - -
VTP-16 BL-SY - -
VTP-17 BL-SY - -
VTP-18 BL-SY - -
VTP-19 BL-SY - -
VTP-20 BL-SY - -
VTP-21 BL-SY - -
VTP-22 BL-SY - -
VTP-23 BL-SY - -
VTP-24 BL-SY - -
VTP-25 BL-SY - -
VTP-26 BL-SY - -
VTP-27 BL-SY - -
VTP-28 BL-SY - -
VTP-29 BL-SY - -
VTP-30 BL-SY - -
VTP-31 BL-SY - -
VTP-32 BL-SY - -
VTP-33 BL-SY - -
VTP-34 BL-SY - -
VTP-35 BL-SY - -
VTP-36 BL-SY - -
VTP-37 BL-SY - -
VTP-38 BL-SY - -
VTP-39 BL-SY - -
VTP-40 BL-SY - -
VTP-41 BL-SY - -
VTP-42 BL-SY - -
VTP-43 BL-SY - -
VTP-44 BL-SY - -
VDS-00 WO-BU - -
VDS-01 WO-BU - -
VDS-02 WO-BU - -
VDS-03 WO-BU - -
VDS-04 WO-BU - -
VDS-05 WO-BU - -
VDS-06 WO-BU - -
VDS-07 WO-BU - -
VDS-08 WO-BU - -
VDS-09 WO-BU - -
VDS-10 WO-BU - -
VDS-11 WO-BU - -
VDS-12 WO-BU - -
VDS-13 WO-BU - -
VDS-14 WO-BU - -
VDS-15 WO-BU - -
COMMAND EXECUTED
I/O DEVICE WORKING STATE AND SPARE DEVICE
SYSTEM = DXT UNIT = STU
DEVICE STATE SPARE DEVICE DEVICE STATE TAPE STATE
WDU-00 WO-BU - -
WDU-01 WO-BU - -
VDS-00 WO-BU - -
VDS-01 WO-BU - -
VDS-02 WO-BU - -
VDS-03 WO-BU - -
VDS-04 WO-BU - -
VDS-05 WO-BU - -
VDS-06 WO-BU - -
VDS-07 WO-BU - -
VDS-08 WO-BU - -
VDS-09 WO-BU - -
VDS-10 WO-BU - -
VDS-11 WO-BU - -
VDS-12 WO-BU - -
VDS-13 WO-BU - -
VDS-14 WO-BU - -
VDS-15 WO-BU - -
COMMAND EXECUTED
/O DEVICE WORKING STATE AND SPARE DEVICE
SYSTEM = DXT UNIT = ACU
DEVICE STATE SPARE DEVICE DEVICE STATE TAPE STATE
TAPE TYPE
FDU-00 WO-BU - -
WDU-00 WO-BU - -
WDU-01 WO-BU - -
COMMAND EXECUTED
The disk drives should enter the state WO-BU and remain in it. The printer and the display unit enter the
WO-ID state automatically when they are connected to the system. The printer remains in the state WO-BU
only for the period during which it is printing.
Changing the state of the printer LPT,0
The states of the peripheral devices can be changed with command
ZISC;
This concerns mainly disk drives. An example of changing the state in the disk unit of the OMU is shown
below.
Steps
1) Check the state of LPT,0:
ZISI:,OMU:LPT,0;
2) Change LPT,0 to the BL-US state:
ZISC:,OMU:LPT,0:BL-US;
The execution printout for a successful state transition is:

STATE TRANSITION EXECUTED
SYSTEM = DX220-LAB UNIT = OMU
I/O DEVICE = LPT-01 NEW STATE = BL-US
COMMAND EXECUTED
I/O DEVICE WORKING STATE COMMAND <IS_>
3) Change LPT,0 back to the WO-ID state:
ZISC:,OMU:LPT,0:WO-ID;
Typical faults
Fault:
Some peripheral devices cannot be brought into the WO-BU state.
Checks:
Check the operation and cabling of the peripheral devices. The disk drives have diagnostics of their own. The
printers and display units have been tested in connection with preparatory measures.
5.7 Checking the clock equipment

The purpose of the test is to verify that the Clock and Tone Generator (CL3TG) and the Clock and Alarm
Buffer (CLAB) provide the required clock signals, and that the switchover of the Clock and Synchronisation
Unit (CLS) works.
Note
Before this test, switch power on and wait until the DXT(T)ip is up and running.
5.7.1 Testing CL3TG
Alarms
1. Check if there are CLS alarms in the DXT(T)ip using command

ZAHO:CLS;
2. Check also the CL3TG unit front panels to make sure that the red alarm leds are OFF in both units.
3. Check the states of the CL3TG units with command
ZUSI:CLS;
4. If there are no alarms in the DXT(T)ip, red alarm leds are OFF in CL3TG units and the CL3TGS units
are in WO-EX and SP-EX state, they should be working correctly.
5. If there are alarms in either one or both of the units, or the states are not as mentioned above, the fault
must be in the CL3TG PIU, clock cartridge or in cabling. Correct and check again.
Switchover
The CLS units can be duplicated and they supervise each other: when one detects any serious alarm
condition in another unit, it can activate itself as the master.
If the switchover fails, check the following:
1. Check the operating states of the CLS units:
ZUSI:CLS;
2. Test the switchover:
ZUSC:CLS,<number of CLS in WO-EX state>:SP;
3. Wait until the units are back in the normal states, then change the switchover back by giving command
ZUSC:CLS,<number of CLS in SP state>:WO;
5.7.2 Testing CLAB units

Alarms
Check the alarms as follows:

1. Check if there are CLAB alarms in the DXT(T)ip:
ZAHO:CLAB;
2. Check also all CLAB unit front panels to make sure that the red alarm leds are OFF in all units.
3. Check the states of the CLAB units:
ZUSI:CLAB;
4. If there are no alarms in the DXT(T)ip, red alarm leds are OFF in all CLAB units and each CLAB pair
is in WO-EX and SP-EX state, they should be working correctly.
5. If there are alarms in either one or both of the units, or the states are not as mentioned above, the fault
must be in the CLAB units, clock cartridge or in cabling. Correct and check again.
Switchover
The CLAB units can be duplicated and they supervise each other; when one detects any serious alarm
condition in another unit, it can activate itself as the master.
If the switchover fails, check the following:
1. Check the operating states of the CLAB units:
ZUSI:CLAB;
2. Test the switchover:
ZUSC:CLAB,<number of CLABs in WO-EX state>:SP;
where <number> is the number of the working unit.
3. Wait until the units are back in normal states, then change back the switchover:
ZUSC:CLAB,<number of CLABs in SP state>:WO;
4. Repeat the test for all CLAB unit pairs.
Note
Run these tests first for the active and then for the passive unit. In either case no MBIF alarms should occur.
For example, the clock alarm lights of the MBIFs should not be on.
5.8 Testing the processor units

The purpose of the processor unit test is to verify that
• the computer unit has not been damaged
• the message bus address of the unit has been wired correctly
• the PROMs used for initial loading are in order.
Steps
1) Connect the VDU to the upper service terminal interface (J7) of the processor unit.
2) Press the reset switch of the processor unit for approximately 1 second. The unit will restart, see
Appendix A for typical printout of the CPU unit start-up.
5.9 Verifying the message bus

The message bus (MB) connections are inspected to verify the condition and correct installation of the
message bus cables, and the condition of the MBIF plug-in units. This is done by testing all the MBIF
plug-in units, either by
• making random tests (for example by cartridges), or by
• making one end-to-end test.
The condition of the MBIF units can be verified only by testing them unit by unit. In the procedure below, one
VDU is always connected to the OMU and another VDU or service terminal is connected to another computer
unit and moved from one computer unit to another.
To test the message buses, you can use either Procedure A or Procedure B.
Note
Before these tests, switch the power on and wait until the DXT(T)ip is up and running.
Procedure A
1) Start a service terminal session in the OMU with the MML command
ZDDS;
or alternatively connect the VDU to the upper serial port (J7) and log in with password SYSTEM.
2) Give command
ZZSMTAC:x,a,b,c,d…;
where
x = message bus 0 or 1
a,b,c,d, … = the MB-addresses of the computer units being tested. There can be up to 20 computer
units in this list, see Table 8 ).
For example, to test message bus connections via MB,0 to computer units CM 0 / CM 1 and CCC
0 / CCC 1, give command:
ZZSMTAC:0,4,5,6,7;
The output will be as follows:
TEST ROUND: 10
COMP DATA_ERR TIME_OUT REC_ERR LAST ERROR STATUS
0004 00000000 00000000 00000000
0005 00000000 00000000 00000000
0006 00000000 00000000 00000000
0007 00000000 00000010 00000000 TIME OUT
TOTAL 00000000 00000010 00000000
3) The test will run until you press CTRL-C. The TEST ROUND shows how many times the test has run. If
there are errors, this can be seen as TIMEOUT appearing from that computer (= it does not answer). In
the example above the CCC 1 (CCC 1 has MB address =7) has not answered to the test message,
thus causing TIMEOUT error in all test rounds.
Procedure B
1) Connect one VDU to the upper service terminal interface of the OMU.
2) Connect another VDU to the upper service terminal interface of the first computer unit to be tested,
that is, to the CCC 0 (see Table 8 ).
3) From the service terminal, log into the processor units to which you wish to connect.
4) Send a message from the OMU service terminal to the service terminal process of the computer unit
(first, CCC 0). Then send the message back (from the other VDU to the OMU). The message is
directed to the bus under test according to the first number of the 16-bit-long message bus address.
Number 2 is used to identify the message bus 0 and number 3 identifies message bus 1. For example,
the address of the CM 0 using bus 1 is 3004H and the address of the CM 1 using bus 0 is 2005H. Send
the message by using the debugger program in the following way:
ZOS:*,X0YY,C0,,,,,,,,AA,BB
where
X = message bus,
YY = message bus address,
AA,BB = data bytes to be sent.
The message contents can be checked from the receiving computer by using command ZOT.
The recommended testing order and the message bus addresses of the DXT(T)ip computer units
are listed in Table 8 .
Note
In the exchange software, SIPU computer units are defined in pairs as shown below:
SIPU 0 and SIPU 1 defined as SIPU,0,0 and SIPU,0,1
Table 8 : Message bus addresses
Unit MB address
(Hex)
OMU 00
STU 0 02
STU 1 03
CM 0 04
CM 1 05
CCC 0 06
CCC 1 07
CCM 0 0A
CCM 1 0B
SIPU 0 (0,0) 10
SIPU 1 (0,1) 11
SIPU 2 (1,0) 12
SIPU 3 (1,1) 13
Table 8: Message bus addresses (cont'd.)
Unit MB address
(Hex)
SIPU 4 (2,0) 14
SIPU 5 (2,1) 15
SIPU 6 (3,0) 16
SIPU 7 (3,1) 17
PDCU 0 (DXTip only) 30
PDCU 1 (DXTip only) 31
ACU 0 2A
ACU 1 2B
EDU 0 2C
EDU 1 2D
CCSU 0 50
CCSU 1 51
CCSU 2 52
CCSU 3 53
CCSU 4 54
CCSU 5 55
5) Disconnect the other VDU (from the CCC 0) and move it to the next computer unit (CCSU 0). Then
perform the tasks of step 3 above.
6) Continue in this way until messages have been sent to and from all the computer units.
The idea of the checks is illustrated in Figure 8 .
step 1
VDU 1 OMU
step 2
VDU 2 CCC0
step 3
OMU message CCC0

VDU 1 VDU 2
address message address
00 back 06
step 4
VDU 2 CCC0 CCSU0

VDU 2
step 5
CCSU0
OMU message VDU 2
VDU 1
address message address
00 back 60
dn00117384 x3x0xen
Figure 8 : Message bus verification
5.10 Checking the ESB26 LAN ports

The Ethernet LAN switches are configured to SWU functional unit pairs. One LAN switch, physically an
ESB26 plug-in unit, composes one SWU functional unit.
In the DXT(T)ip, there are two pairs of SWU ESB26 plug-in units providing Ethernet LAN ports; one pair
connects to the CM units of the DXTA and the other to the ACU units of the DXTB cabinet.
According to the redundancy principle there must be an even amount of LAN switches in the DXT(T)ip. The
LAN switches are N+1 redundant and have a pair redundancy rule. The redundancy cables are already
attached at the factory.
Normally, both units of an ESB26 pair are in WO-EX state. Only one of the units in a pair can be set to another
state at a time. Setting both units to a state other than WO-EX is only possible by using the forced mode.
Detailed information on the implementation and maintenance of the LAN switches is given in document
Integrated LAN Administration, dn0423824.
The LAN ports of the DXT(T)ip are listed in the tables in Section 9.3.12 , each table consisting of the
following columns:
• From port shows the number of the ESB26 LAN switch port from software point of view. The numbering
is as follows: 1-2 and 23-26 are LAN ports on the front plate and 3-22 are ports on the back plane.
• Conn. position shows the cartridge and cable position of the cabinet.
• Unit shows the functional unit to which the LAN cable is connected.
• To port shows the number of the LAN port in the CP816-A or ESB26 from software point of view.
• Plug-in unit shows the plug-in unit where the LAN cable is connected.
• Cartridge / slot / conn. position defines the slot of the unit in the cartridge.
• Connector panel / slot defines the slot of the connector panel in the cabling cabinet.
• Note shows any additional information such as the use of the LAN, cabling details of network element
interfaces, or speed of connection for external ports (100/1000 Mbit/s).
• The column OK/NOK is reserved for writing down the results of the commissioning test.
6 Inspection of the maintenance system
The maintenance system is inspected to ensure that the supervision, alarm, and recovery functions of the
system are in order. The supervision functions are mainly system-internal and they are tested in connection
with the inspection of the alarm system.
The alarm system is tested in connection with the other commissioning tests, so the alarm printouts should be
monitored during the entire commissioning testing. It is important to monitor that appropriate alarms and
messages are printed out and that the possible recovery functions are correct.
This chapter defines the inspection of the supervision and alarm systems of the DXT(T)ip in the
commissioning testing as follows:
• Section 6.1 Alarm system
• Section 6.2 Power breaks
• Section 6.3 State transitions and unit diagnostics
• Section 6.4 Connecting external PCMs to ET4C cartridge
• Section 6.5 Spare plug-in units
The outputs presented in this manual are examples only, and therefore the actual outputs may in some cases
differ from the outputs presented here.
Note
A prerequisite for the inspection of the DXT(T)ip maintenance system is that the inspections connected with
the system start-up have been successfully performed.
6.1 Alarm system

The inspection of the alarm system covers the testing of the wired alarms and the external alarms. Software
alarms are monitored during the testing.
If alarms need to be configured, handled or studied at this stage, it can be done by using the MML
programmes listed in Table 9 .
Table 9 : Command groups for alarm handling
Command group Name of the group and definition

AB Blocked alarms handling
For blocking and unblocking alarms, and outputting
blocked alarms.
AC Alarm cancelling
For cancelling alarms.
Table 9: Command groups for alarm handling (cont'd.)
Command group Name of the group and definition

AE Error ratio counter handling
For handling the parameters of error ratio counters.
AH Alarm history handling
For printing out alarm history and alarms which are
currently on.
AL Lamp panel handling
For displaying the states of alarm outputs and the
updating of higher or lower alarms in the system,
and for modifying the alarm states.
AO Alarm operating instruction handling
For handling alarm-specific operating instructions.
AP Alarm parameters handling
For outputting and modifying alarm parameters.
AR Alarm system rulebase handling
For handling the rules in the alarm system rulebase.
AT Alarm printing handling
For blocking and unblocking alarm classes and
changing printing parameters.
6.1.1 Wired alarms
The purpose of the test is to ensure that the alarm files have been correctly packaged and that the wired
alarms have been correctly cabled.
Before the test, do the following:
1. Check that the OMU is in the WO-EX state, and output the defined alarms with command
ZWAP;
2. Compare the data with the configuration.
General
Test the wired alarms by causing a fault situation for all of them, one at a time, and verifying that the correct
alarm number and text will be printed out to the LPT.
Test the following wired alarms:

• clock cartridge alarms
• power supply alarms
• fuse panel alarms
• cartridge power alarms
• cartridge clock alarms
Procedures
Clock cartridge alarms

1) Disconnect the power cable of the spare CL3TG in the clock cartridge or the spare CLAB in the CLAC
cartridge. They are in the back plane of the cartridge (in the middle).
2) Connect the power cable and verify the alarm cancelling.
3) Change to the active unit and repeat the procedure.
Power supply alarms

1) Turn off one power circuit from the front panel of the PDFU and verify the alarm. The unit without
power should be separated from use.
2) Turn the power circuit on and verify the cancelling. The unit state should be returned to the correct
working state.
Fuse panel alarms

1) In any cabinet, switch off a fuse from the PDFU fuse panel (front side, top) and verify the alarm.
2) Insert the fuse and verify the alarm cancelling.
3) Wait until all the recovery actions are completed and repeat the test in the other cabinet.
Cartridge power alarms

1) Switch the power off from one cartridge power unit (PSC6-A) and verify the alarm.
2) Wait until all recovery functions have been completed.
3) Switch the power back on and verify the alarm cancelling.
4) Repeat steps 1 - 3 for every cartridge.
5) Check the results of diagnostics from the printer.
Wired alarms
The purpose of the testing is to ensure that the alarms are correctly created and that the wired alarms are
correctly cabled.
Equipment and instructions:
1. Visual display unit
2. Printer
3. Multimeter
4. Hexadecimal calculator
5. Alarm documentation
6. Equipment list, site documents
7. Exchange source data (external alarms)
8. Alarm administration
Steps
Note
All tests must be repeated using the OMU as WO-EX. Also, the CLAB unit in each cabinet must be switched
on and the test must be repeated to make sure that the redundancy system is working properly, too.
1) Connect the MML terminal and the printer LPT0 to the OMU and check with command
ZIID:,OMU;
that the logical files SWITCH1, OPERMA1, TRANSM1, POWER1, EXTERN1, SWITCH2, OPERMA2,
TRANSM2, POWER2 and EXTERN2 are connected to the printer connector LPT0 of the OMU, which
in turn is connected to a printer in working order. If this is not the case, use command
ZIIS::<LOG_FILE>::DEV=LPT0;
to connect the above-mentioned logical files to the LPT0 printer connector.
2) Check which alarms are currently on with the ZAHO command and correct any problems that may arise.
3) Check that the OMU is in the WO-EX state. Output the alarms with the WAE command. The command
also tests all created alarm groups. Compare data in the lists with the configuration:
ZWAE:<cabinet index>;
Any of the following alarms should not have FAILED flag in the INFO field.
Note
Alarm *2755 CARTRIDGE CLOCK FAILURE is permanently on in a cartridge that has only PSC6-A
plug-in unit configured to feed the MB-terminators.
I/O FILE BACKUP COMMABD>IB_>

< ZWAE:01A;
LOADING PROGRAM VERSION 3.2–0.
DXT DXT1655 2003-10-02 11:35:19
CONNECTION PLUG-IN UNIT: HWAT
MASTER UNIT: OMU 1A002-06
ALARM CARTRIDGE CARTRIDGE INPUTS OF ALARM GROUP INFO
GROUP TYPE COORDINATES 0 1 2 3
-------------------------------------------------------------------
1 PSAD & PSFP 1A 2759 — 2758 –
2 CC4C_A 1A003-00 2757 2755 - -
3 CC4C_A 1A003-03 2757 2755 - -
4 NOT CONFIG – – – - -
6 NOT CONFIG - – – - -
8 DC3CL—A 1A001-00 2757 2755 - -
9 DC3CR_A 1A001-02 2757 2755 - -
10 CM2C_A 1A002-06 2757 2755 – -
11 CC4C_A 1A004-03 2757 2755 - -
12 CC4C_A 1A003-06 2757 2755 - -
13 NOT CONFIG - - - -
14 CC4C_A 1A004-00 2757 2755 - -
15 ET4C-B 1A005-06 – 2755 - -
USED ALARMS:
2755 CARTRIDGE CLOCK FAILURE
2757 CARTRIDGE NON-REDUNDANT POWER SUPPLY FAILURE
2758 POWER SUPPLY ADAPTER FAILURE
2759 POWER SUPPLY FUSE FAILURE
IN FAULT CONDITIONS THE PRINT-OUT CONTAINS INFORMATION AFTER THE
ALARM NUMBER WHETHER THE WIRED ALARM INPUT IS PERMANENTLY "0" OR "1".
COMMAND EXECUTED
4) The alarms are tested as follows:
* POWER SUPPLY FUSE FAILURE
Cabinets to be tested: all
Check by removing one fuse from the fuse unit (PDFU).
* POWER SUPPLY ADAPTER FAILURE
Cabinets to be tested: all
Check by switching off one switch from PDFU from each cabinet.
* CARTRIDGE POWER SUPPLY FAILURE
* CARTRIDGE POWER FAILURE
* CARTRIDGE NON-REDUNDANT POWER SUPPLY FAILURE (in N+1 redundant power supply units)
Cartridges to be tested: all
Check by switching off the power from PSC6-A from each cartridge.
* CARTRIDGE CLOCK FAILURE
Cartridges to be checked: all
* FAN UNIT FAILURE
Units to be tested: all
Check by removing corresponding fuse from the fuse unit.
6.1.2 External alarms
Steps
1) Output the wired alarms with command
ZWAP;
2) Check that the external alarms specified to the exchange have been printed out.
Testing external alarms from cross-connection or from cabling cabinet
The hardware site documents include an illustration about the use of the cross-connection pins.
The cable that comes from the cross connection is removed from the connector D of the CPEA panel so that
the possible fault in it will not cause any disturbancies.
In the Z-pack connector of the CPEA, panel alarms have to be tested one by one. When the pins are
connected to the earth, the alarm is acknowledged. When the earth is disconnected, the alarm is generated.
If testing the alarms is successful, the fault has to be located in the cable between the cross connection and
the CPEA panel or in its connections.
If testing the alarms from the cross connection does not succeed, they must be tested from behind the
OMU cartridge.
If testing the alarms is successful, the fault has to be located in the cable between HWAT-A and CPEA
panel or in its connections.
If testing the alarms from the cross connection does not succeed, the fault has to be located in the HWAT-A.
Expected results
The tested alarm is output on the printer and removed when the situation is back to normal.
Compare the alarms with the Alarm documentation and with the source data of external alarms to check the
• alarm number
• alarm text
• device type
• urgency level
• unit data
• coordinate data
• existence of the alarm
• directing of the alarm to the lamp panel (whether the correct lamp is turned on).
If the cabling is complete, check alarm by alarm that the wiring still allows an external alarm to be detected by
the exchange. This can be done by causing a fault corresponding to an external alarm either through a real
fault or electrically by bringing the alarm contacts to a state equivalent to a fault condition.
TYPICAL FAULTS
1. External alarms are not printed at all to the printer.

Possible reasons:
• The logical files EXTERN1 and EXTERN2 are not connected to the printer. Use ZIID command
to check this and ZIIS command to change if needed.
• The HWTABL (10DH), TEOUTP (1E8H) or TEFORM (125H) file is not in order.
The alarm ALARM SYSTEM FILE ERROR is printed out. Check the existence of the external alarm
with the ZWAT command.
2. One or several external alarms are missing. Possible reason:
• alarms are missing from the HWTABL file
• the HWTABL file is incorrect, faulty or incorrectly packaged (see Section )
• the HWAT-A plug-in unit is faulty.
3. External alarms not belonging to the exchange are printed out.
Possible reason: the HWTABL file is incorrectly packaged. See instructions on removing external
alarms below.
4. The number, the device type or the urgency level of the external alarm (or several alarms) is incorrect.
Possible reason: the HWTABL file is incorrect or incorrectly packaged. Correct the data with the
ZWAM and ZAPM commands.
5. The text of an alarm (or several alarms) is incorrect.
Possible reason: the ALEXTE (113H) file is faulty or incorrect. Correct the text with the ZWAM command.
6. The external alarm is not generated when the alarm circuit is activated.
Possible reasons: the HWAT-A plug-in unit is not in order.
See instructions about the testing of the external alarms from the cross connection.
7. The activation of the alarm circuit for an external alarm results in a CANCEL message and the
deactivation of the alarm circuit generates an alarm.
Possible reason: the polarity data of the alarm in the HWTABL (10DH) file is incorrect. Change the
polarity of the alarm input with the ZWAX command.
8. The coordinating data of a unit suspected faulty is incorrect.
Possible reason: error in EQUIPM database. Correct with commands of the command group WT-
Equipment Management.
Adding external alarms
Check the number and input of the HWAT-A corresponding to the external alarm to be added.
Check that the chosen alarm input of the HWAT-A is not in use by giving command
ZWAP:LOCAL:y;
where
y = number of the alarm input.
1. Define the alarm number (4000 … 5999) and the corresponding textual meaning for it:
ZWAA:4000:EX:”EXAMPLE OF ALARM CONCERNED TEXT”;
2. Using the following command, open the chosen free alarm input and associate the input specific
text for it:
ZWAI:LOCAL:OMU:5,4000,”ALARM TEXT INPUT 5”;
In the example above, the alarm input 5 of the HWAT-A 0 is opened.
When an alarm input is opened with the ZWAI command for an external alarm, the polarity (OK
state) gets the value 1, that is, the earth is disconnected from the alarm input in an alarm situation
(opening contact). If a closing contact is connected to the alarm input, change the polarity with the
ZWAX command
ZWAX:LOCAL:OMU:5:OK=CHA;
The parameters of the alarm can be changed with the ZAPM command.
3. Use the ZIID command to check that the EXTERN 1 and EXTERN 2 alarms are directed to a printer in
operation. When necessary, change the output device with the ZIIS command.
4. The alarm is tested by causing a fault condition corresponding to the external alarm either with a real
fault or electrically by setting the alarm contacts in a state corresponding to a fault condition. After the
change, save the files on the disk with commands
DFC:OMU,0:NBR=10D; and
DFC:OMU,0:NBR=113;
Removing an external alarm
Remove the alarm by closing the alarm input with the ZWAD command:
ZWAD:LOCAL:OMU:5;
In the example, alarm input 176 of the HWAT-A is closed.
After the change, store the files on the disk with commands
DFC:OMU,0:NBR=10D;
DFC:OMU,0:NBR=113;
Fault handling
Check the files suspected faulty both on the disk and in the memory. Check especially that the file is intended
to be used in the type of computer you are commissioning. This can be found out by reading the FID field
(located in block 0 of the disk) of the file.
Fill in a problem report and try to correct the fault by using the command group WA - Wired Alarm
Connections Handling.
If the alarm
* ALARM SYSTEM FILE ERROR
is printed out, it gives the faulty file and the faulty part in the file in question. See the meaning of the additional
data in the Alarm documentation.
Use the MML command ZWAP to print out information about all the alarm inputs and try to give the alarm
directly from the alarm input of the HWAT-A plug-in unit in question.
If the alarm is not generated, change the plug-in unit.
If the alarm is generated from the alarm input of the exchange, the fault is in the cabling. Check the cabling.
6.2 Power breaks

The purpose of the tests is to test the recovery of the system from different power breaks. After a power
break, the system should automatically separate the units without power from use, and start the units in their
correct working state after the power is on again.
To test the recovery from a total power break in the system, do the following:
1. Monitor the system start-up from a state without power.
2. Check that the complete loading of all the computer units from the disks is successful and that the
units are started up in the original working states.
6.2.1 Complete power break in the system
Steps
1) Connect the alarm printer to the LPT port and the MML terminal to the VDU port.
2) Check that the system is in normal state (units are in WO-EX or SP-EX states), with command
ZUSI:ALL;
If a unit is not in the appropriate state, change the state with the ZUSC command.
3) Disconnect the power from the main switch of the system. Leave it in the OFF position for 1 minute to
allow the data to disappear.
4) Connect the power to the system with the main switch.
Expected results
1. The system is started and it starts the loading from the disks.
2. Wait until the Operation and Maintenance Unit (OMU) starts in the WO-EX state.
The following notice is printed out:
0691 AUTOMATIC RECOVERY ACTION WO-RE TO WO-EX
The following text is displayed:

MMI SYSTEM READY
The user can start a session from an MML terminal.

3. During the start-up of the OMU, the recovery system analyses the condition of the DXT(T)ip and
starts the control of the system start-up.
The following notice is printed on the alarm printer:
0689 SYSTEM RESTARTED
After testing
1) Output the working states of the units from the MML terminal and monitor that every unit starts in the
state it had before the power break. Use command
ZUSI:COMP;
2) Monitor the alarm printer. All the starting units should cause a notice:
0691 AUTOMATIC RECOVERY ACTION WO-RE TO WO-EX
or
0691 AUTOMATIC RECOVERY ACTION SP-RE TO SP-UP
or
0691 AUTOMATIC RECOVERY ACTION SP-UP TO SP-EX
3) Print out the states of all the units and check that they are not in an incorrect working state.Use
command
ZUSI:ALL;
to output the working states of the units
or
ZUSL:,INCO;
to output all units whose states are incorrect.
4) Finally update the date and time.Use command
ZDCS:YYYY-MM-DD,HOUR-MIN-SEC:ST=OFF/ON
and set the time zone, for example GMT + 1 h:
ZDCE:PLUS:01-00;
6.3 State transitions and unit diagnostics
Note
The ETs must be created (command ZWTP) and connected (command ZWUC) before testing. See Section 6.4 .
6.3.1 State transitions
Steps
1) Connect the alarm printer to the LPT port and the MML terminal to the VDU port. Print the working
states of the units on the printer with command
ZUSI::::,LPT0;
and check that all the units of the system are on the list (compare with the source data).
2) Change the state of each unit on the ZUSI list to TE, one by one with command
ZUSC:<unit>,<index>:TE;
3) Change the state of each unit on the ZUSI list to SE-OU, one by one with command
ZUSC:<unit>,<index>:SE;
4) Change the state of each unit on the ZUSI list to SE-NH, one by one with command
5) Change the state of each unit on the ZUSI list to SE-OU, one by one with command
6) Change the state of each unit on the ZUSI list to TE, one by one with command
ZUSC:<unit>,<index>:TE;
6.3.2 Unit diagnostics

Note
No diagnostics are provided for the following units: TBC, TTRX, TBS, TDSC, DSC.
Steps
1) Run the diagnostics on the unit with command
ZUDU:<unit>,<index>;
The unit must be in test state, before the diagnostics can be executed. You can change the state with
the ZUSC command.
After starting the diagnostics, you can interrogate the phase of the diagnostics with the UDQ command.
For example:
ZUDQ:;
CURRENT DIAGNOSTIC TESTS:
UNIT TEST INITIAL TIME
CCC-1 GSWB 14:34:23
COMMAND EXECUTED
After having executed the diagnostics you can output the result with the ZUDH command:
ZUDH:CCC,1:;
DXT STEVE 2004-04-02 14:43:22
DIAGNOSTIC REPORT HISTORY

UNIT = CCC-1 REPORT-CLASS = ALL DATE = 2004-04-02 TIME = 00:00:00
DXT STEVE 2004-04-02 14:34:23

PARTIAL DIAGNOSIS EXECUTED CCC-1 POWER
DXT STEVE 2004-04-02 14:34:57
PARTIAL DIAGNOSIS EXECUTED CCC-1 CPU
DXT STEVE 2004-04-02 14:34:58
PARTIAL DIAGNOSIS EXECUTED CCC-1 RAM
DXT STEVE 2004-04-02 14:35:04
PARTIAL DIAGNOSIS EXECUTED CCC-1 SYSB
DXT STEVE 2004-04-02 14:35:05
PARTIAL DIAGNOSIS EXECUTED CCC-1 WAT
DXT STEVE 2004-04-02 14:35:05
PARTIAL DIAGNOSIS EXECUTED CCC-1 GSW
GSW-1
DXT STEVE 2004-04-02 14:41:53
PARTIAL DIAGNOSIS EXECUTED CCC-1 GSWB
GSW-1
DXT STEVE 2004-04-02 14:42:43
PARTIAL DIAGNOSIS EXECUTED CCC-1 AS7
DXT STEVE 2004-04-02 14:42:43
DIAGNOSTIC REPORT
CCC-1
PARTIAL DIAGNOSIS TOTAL
DIAGNOSTIC PROGRAM 0000
DIAGNOSIS 3999
3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK
END OF REPORT
The output report shows each partial diagnostics executed to the unit in question. The diagnostic report
at the end of the printout shows the result (normally UNIT OK).
2) Change the state of each unit on the ZUSI list to SP or WO, one by one with command
ZUSC:<unit>,<index>:WO;
or
ZUSC:<unit>,<index>:SP;
6.4 Connecting external PCMs to ET4C cartridge

The Exchange Terminals (ETs) must be such that they supply synchronisation to the CLS units of the
DXT(T)ip. There are a maximum of 8 ECE2/ET2E plug-in units and 16 ET4E plug-in units in one DXTip and
16 ECE2/ET2E plug-in units and 32 ET4E plug-in units in one DXTTip.
The default unit numbers of the ECE2 and ET2E cards are 34 - 63 in the DXTip and 34 - 63 and 66 - 95 in the
DXTTip. The default unit numbers of the ET4E cards are 128 - 191 in the DXTip and 128 - 255 in the DXTTip.
It is possible to use any other ET for the synchronisation by changing the position of the corresponding
synchronisation cable in the ET cartridge. The switching network is GSWB. The mode of the ET is
non-transparent, that is, the time slot T0 is reserved for fault management signalling.
The DXTip has one ET4C cartridge. The DXTTip has two ET4C cartridges, one in the DXTA cabinet, and
another in the DXTB cabinet. These cartridges belong to the basic configuration and are usually installed
before delivery.
In the following example, a new ET4C cartridge and the external PCMs 128, 129, 130 and 131 provided by an
ET4E card are created in the DXT(T)ip exchange.
Steps
1) Create an ET4C 0 cartridge with the coordinates 1A5-6, if not already created. Use command
ZWTC:ET4C_B,1A5-6:AL=1A1-8-15:;
2) Each ET4E plug-in unit contains four ETs. To define the ETs number 128, 129, 130 and 131 to the
cartridge, use commands
ZWTU:ET,128:1A5-6:;
ZWTU:ET,129:1A5-6:;
ZWTU:ET,130:1A5-6:;
ZWTU:ET,131:1A5-6:;
3) To create the external PCMs to these ETs with index 0 to track 8 with TSL 0 reserved for the supervision
of the ET, use commands
ZWTP:ET,128:ET4E_C,0,8::ETT00,8,128,TSL,0:;
4) To connect the ETs to the WO-EX CCC unit, use commands
ZWUC:ET,128:ET4E_C,0::CCC,0:;
5) To change the states of the ETs to WO-EX, give the following commands:
To change the states to SE-OU, use commands
ZUSC:ET,128:SE;
ZUSC:ET,129:SE;
ZUSC:ET,130:SE;
ZUSC:ET,131:SE;
To change the states to TE-EX, usee commands
ZUSC:ET,128:TE;
ZUSC:ET,129:TE;
ZUSC:ET,130:TE;
ZUSC:ET,131:TE;
To change the states to WO-EX, use commands
ZUSC:ET,128:WO;
ZUSC:ET,129:WO;
ZUSC:ET,130:WO;
ZUSC:ET,131:WO;
To check the states of the ETs, use command
ZUSI:ET;
If the ETs are already connected, they have routed time slots. Check this with commands
ZWTI:P:ET,128;
ZWTI:P:ET,129;
ZWTI:P:ET,130;
ZWTI:P:ET,131;
Note
When using ET2E or ET4E plug-in units, the even-numbered ET must be connected before the
odd-numbered one.
If the controlling CCC is not already in the WO-EX state, the state can be changed to WO-EX. Once the
CCC's state is WO-EX, the state of the ET can be changed to WO-EX, too.
To interrogate the settings of the CRC checking of the ET4E, use commands
ZYEI:ET,128;
ZYEI:ET,129;
ZYEI:ET,130;
ZYEI:ET,131;
Change the CRC checking to the DBLF state with command ZYEC, if needed.
6.5 Spare plug-in units
Equip the DXT(T)ip with the spare plug-in units and perform diagnostics by changing the units to test state,
and by starting the diagnostics for the units equipped with spare plug-in units.
Write a failure report if faulty plug-in units are found.
7 Inspection of clock synchronisation
The purpose of this test is to check the functionality of the connection between the clock synchronisation
units and the OMU. You should also verify that both clock synchronisation units automatically perform
switchover of synchronisation signals if errors occur.
The sections of this chapter define the inspection of the clock synchronisation of the DXT(T)ip in the
commissioning testing as follows:
• Section 7.1 Inputs
• Section 7.2 Testing
Preparations
1. Check the connection between the OMU and the clock synchronisation units using command
ZDRI;
This should not cause any error messages.
2. Check that the OMU is ready for use.
7.1 Inputs
If there are no synchronisation connections to a higher-level exchange, the synchronisation unit should be
in the PLESIOCHRONOUS MODE (command ZDRI). Simulate the synchronisation inputs in the ET2E or
ET4E as follows:
1) Make a loop-back in the front plate of the synchronisation input ETs.
As default, the DXT(T)ip uses the ET2E ports 34 and 35 or ET4E port 128 in the DXTA cabinet.
In the MML commands, they are identified as follows:
34 = 2M1
35 = 2M2
128 = 2M1
Table 10 : Synchronization inputs
Cabling From DXT To DXT Type Use Note

number
FU Position FU Position
DXTA_186 CLOC 1.8B 01R1 ET4C 0 5.6B 08S5*) CF1028 SYNC **)
DXTA_187 CLOC 1.8B 00R3 ET4C 0 5.6B 00S5*) CF1028 SYNC **)
DXTA_188 CLOC 1.8B 00R2 ET4C 0 5.6B 08R5*) CF1028 SYNC **)
Table 10: Synchronization inputs (cont'd.)
DXTA_189 CLOC 1.8B 00R1 ET4C 0 5.6B 00R5*) CF1028 SYNC **)
*) Freely configurable by the customer.
**) Cables DXTA_186 - DXTA_189 are connected to the CLOC cartridge only. The other ends of the cables are routed and tied to cable supporting
shelf 5 to be ready for connecting to ET4C 0.
Connector positions are freely selectable by the customer according to Table 11 and Table 13 :
Table 11 : ET2E-TB/ET2E-TCB
Synchronisation interface 0 ET34-B01R5

ET38-B03R5
ET42-B05R5
ET46-B07R5
ET50-B01S5
ET54-B03S5
ET58-B05S5
ET62-B07S5
The synchronization inputs for ECE2–NTx are: 34/35, 38/39, 42/43, 46/47, 50/51, 54/55, 58/59,
62/63. That is, only every other pair can be used. If DXTB is used, also the following synchronisation
inputs can be used: 66/67, 70/71, 74/75, 78/79, 82/83, 86/87, 90/91 and 94/95. The index numbers
34–95 are used as follows:
• 34–63 in ET4C 0, DXTA
• 66–95 in ET4C 1, DXTB
Table 12 : ECE2 and ET2E/ET4E index table: GSWB 0
UNIT INDEX
ECE2/ET2E 34 35 38 39 42 43 46 47
ECE2/ET2E 50 51 54 55 58 59 62 63
ECE2/ET2E 66 67 70 71 74 75 78 79
ECE2/ET2E 82 83 86 87 90 91 94 95
Table 13 : ET4E/ET4E-C: Synchronisation cabling from PCM 128 – 191 (ET4C 0)
Synchronisation interface 0 B00R5–B15R5

B00S5–B15S5
For ET4E/ET4E-C cards, only the synchronisation interface 0 is possible. In each ET4E card, the first
of the four PCMs is used for synchronisation, in other words, every fourth PCM is used, starting with
128 and, in the ET4C 0 cartridge, ending with 188.
CLOC
CLS 0, 1
00 R1 00 R2 00 R3
CR
')
ET4C 0
dn 02110626 x1x0xen
Figure 9 : Synchronisation inputs
2) Use the following connection to the 120-ohm ETs:
Even ET
b13 -> b10
b12 -> b9
Odd ET
b6 -> b3
b5 -> b2
An example of the connection is shown in Figure 10 .

3) In 75-ohm ETs, connect the receiver and transmitter to each other.
ET4C 0
connector
a b c
ET 128 - ET 132 - ET 136 - ET 140 - .....
ET 131 ET 135 ET 139 ET 143 16
even ET :
pin b 13
to
pin b 10
00 01 02 03 1
..... 15
ET 160 - ET 164 - ET 168 - ET 172 -
ET 163 ET 167 ET 171 ET 175
Key:
ET 128
ET 129
ET 130
ET 131 = ET4E/ET4E-C
plug -in unit
16 17 18 19 ..... 31
dn 05176617 x1x0xen
Figure 10 : Connection of an even ET from b13 to b10
4) Set all synchronisation inputs to the CONNECTED state. Open a new synchronisation input with
command
ZDRC (for example, ZDRC:2M2;)
5) Delete the superfluous synchronisation inputs with command
ZDRD (for example, ZDRD:2M2;)
The synchronisation input 2M1 should be in the CONNECTED state and in use (USED INPUT).
Check this with command
ZDRI;
6) The other synchronisation inputs should also be in the CONNECTED state.
7.2 Testing
The starting point is that on both CL3TG plug-in units, the indicator lamp 1 is lit.
7.2.1 Changeover to back-up connection
1. Disconnect the first loop-back at the front connector of the ET2E/ET4E. The clock synchronisation
unit will change over to the clock input of the next priority within the time TP (see command ZDRS).
The default value of this time is 5 minutes. The LEDs on the CL3TG plug-in units will indicate the
new synchronisation input.
Interrogation with the ZDRI command shows that the 2M1 synchronisation input is in the FAULTY state
and the next input in the CONNECTED state and in use. The following messages will be displayed
on the alarm printer:
FAILURE IN SYNCHRONISATION SIGNAL
and
SYNCHRONISATION SIGNAL CHANGED
2. Disconnect the second loop-back. The procedure and results are the same.
7.2.2 Changeover to internal oscillators
1. Disconnect the loop-back of the last synchronisation input. The clock synchronisation unit should then
switch to plesiochronous operation within the time TP. All synchronisation input indicators on the active
CL3TG unit will be extinguished and all indicators on the passive CL3TG unit will be lit.
2. Give the ZDRI command to print out the mode:

SYNCHRONISATION UNIT WORKING MODE.......PLESIOCHRONOUS MODE
7.2.3 Synchronisation with external clock
1. Return the loop-backs one by one, starting from the lowest priority. The clock synchronisation unit will
switch over to use the input 2M3 first, then 2M2 and then 2M1 within the time TR (command ZDRS). The
default value is 10 minutes. On both CL3TG plug-in units, the indicator lamp for the synchronisation
input in question will be turned on.
2. Change the state of the input to CONNECTED (command ZDRC), so it will be in use (USED INPUT).
7.2.4 Faults correctable with MML commands

1. A CL3TG in PLESIOCHRONOUS state will search for the incoming signal from the entire adjustment
range by forcibly selecting the desired input into use. Correct this with command
ZDRS::U=2M1;
2. When the clock synchronisation unit has been synchronised to this input, remove the forced control
with the ZDRS command, for example
ZDRS::U=OFF;
8 Real-time clock
This chapter describes the procedure for checking that the real time remains correct in the exchange during a
power failure in the OMU.
Real-time backup during OMU power failure
In the DXT(T)ip, the master clock time is provided by the active STU unit (provided STU units are included in
the configuration) and monitored by the OMU. When the OMU restarts after a power failure, it first checks if
both STU units have the same time. If they do, the OMU reads its time from the STU. If the STU units are not
showing the same time or are not in the right state (WO and SP) or the exchange does not include STU units,
the OMU reads the time from its own CPU. If the OMU knows the IP address of the NTP server, it requests
the master time from there and synchronises all computer units in the exchange if needed. Thus the time
provided by the STU or the OMU's CPU is valid only until the response from the NTP arrives.
For further information on the NTP and other aspects of the time management in the EADS TETRA System,
refer to document Time Management in EADS TETRA System, dn0484132.
The procedure for checking the real time after a power failure in OMU is shown below. The prerequisite for
this test is that the master time of the DXTip where the test is performed is not set by any other DXTip in the
network or by the Nokia NetAct for TETRA system.
To perform the test, follow the instructions below:
1) Check the system time and summer time setting. Use the following MML command:
ZDCD;
2) Switch off the power from the OMU.
3) Wait for minimum 10 minutes then switch on the OMU power.
4) Check that the OMU restarts correctly, (refer to the Appendix A ), and that no alarms about the start not
being successful appear on the alarm printer.
5) After the OMU has started, check that it is in the WO-EX state. Give the following command:
ZUSI:OMU;
If the OMU is not in WO-EX state, change the state with the ZUSC command.
6) Check as described in step 1 that the system time and summer time settings are correct.
9 Test logs
This chapter contains the test logs needed in the commissioning testing of the DXT(T)ip. The chapter breaks
down into the following parts:
• Section 9.1 DXT(T)ip specifications
• Section 9.2 Summary of the DXT(T)ip commissioning tests
• Section 9.3 Test log forms
Please record confirmation of test execution and any comments in the test logs. Some of the logs can be
used as check lists while testing.
Each test has been assigned a number equal to the number of the relevant section in this document. For
example: test number 4.3 9.3.2 refers to Section 4.3 .
9.1 DXT(T)ip specifications

Before the tests, fill in the identification data of the exchange as follows:
Table 14 : DXT(T)ip specifications
Change delivery no.

C-number
DXT(T)ip name
Software release
(xx.yy-zz)
Checked by:
Approved by:
Date:
9.2 Summary of the DXT(T)ip commissioning tests

Table 15 : Summary of the DXT(T)ip commissioning tests
Test no. Test name Pass / Fail Fault No. / Note

4.3 Jumper connectors, DIP-switches
and EPROM versions
4.4 Grounding
4.5 Supply voltage
Table 15: Summary of the DXT(T)ip commissioning tests (cont'd.)
Test no. Test name Pass / Fail Fault No. / Note

4.6 Peripheral units
5.2 DXT(T)ip startup
5.4 MML session
5.5 Software versions
5.6 I/O system
5.7 Clock equipment
5.8 Processor units
5.9 Message bus verification
5.10 ESB26 LAN ports
6.1.1 Wired alarms
6.1.2 External alarms
6.1.3 Alarm outputs
6.2.1 Complete power break in system
6.3.1 State transitions
6.4 Connecting external PCMs to
ET4C
6.5 Spare units
7 Clock synchronisation
9.3 Test log forms
9.3.1 Test 4.1: Interchangeability versions

Table 16 :
Cartridge type Plug-in unit type C-number Interchangeability

version
Table 16: (cont'd.)

version
Table 16: (cont'd.)

version
Approved by: Date:
9.3.2 Test 4.3: Checking the jumper connectors, DIP-switches and

EPROM versions
Table 17 : Jumper connectors (Part 1)
CP816-A MBIF-C HWAT-A

OMU
AS7-C SERO-B
OMU
CP816-A MBIF-C(R)
CM 0
CM 1
SW128B
SW10C-C 0
SW10C-C 1
ET2E-TB / ET2E-TCB
ET4E / ET4E-C
ET4C
ECE2
ET4C
CL3TG-S
CLS 0
CLS 1
WDW73
OMU
STU
ACU
CP816-A MBIF-C AS7-C SWCOP-A

CCC 0
CCC 1
CP816-A MBIF-C
ACU 0
ACU 1
CP816-A MBIF-C
EDU 0
EDU 1
CLAB-S
CLAC 0
CLAC 1
CLAC 2
CLAC 3
CLAC 4
CP816-A MBIF-C
SIPU 0 = 0,0
SIPU 1 = 0,1
SIPU 2 = 1,0
SIPU 3 = 1,1
SIPU 4 = 2,0
SIPU 5 = 2,1
SIPU 6 = 3,0
SIPU 7 = 3,1
CP816-A MBIF-C AS7-C

CCSU 0
CCSU 1
CCSU 2
CCSU 3
CCSU 4
CCSU 5
CP816-A MBIF-C(R) AS7-C

STU 0
STU 1
CP816-A MBIF-C AS7-C

PDCU 0
(DXTip only)
PDCU 1
(DXTip only)
CP816-A MBIF-C
CCM 0
CCM 1
Jumper connectors signatures:
Table 34 : Bridge connectors signatures
Checked by: Date:
Table 35 : EPROM versions
Unit Version
CP816-A boot FLASH
ET2E-TB / ET2E-TCB
ET4E / ET4E-C
ECE2-NT / ECE2-NTC
SWCOP-A
CL3TG-S
CLAB-S
Checked by: Date:
9.3.3 Test 4.4: Grounding

DXT(T)ip - bus bar ______________ ohms
Checked by: ____________________Date:______________________
9.3.4 Test 4.5: Supply voltage

Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Checked by: ________________ Date:_______________________
9.3.5 Test 4.6: Peripheral units

Visual display units
Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Printers
Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Checked by: ________________ Date:_______________________
9.3.6 Test 5.2: DXT(T)ip start-up

Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
_____________________________________________________
_____________________________________________________
_____________________________________________________
Checked by:__________________Date:______________________
9.3.7 Test 5.4: MML session

Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
_____________________________________________________
_____________________________________________________
Checked by:___________________ Date:_____________________
9.3.8 Test 5.5: Software versions
Make a printout of the software version and attach it to the site-specific folder.
9.3.9 Test 5.6: I/O system

Table 36 : Inspection of the I/O system
I/O device OK / NOK NOTES

OMU
- WDD 0
- WDD 1
STU
- WDD 0
- WDD 1
ACU
- WDD 0
- WDD 1
VDU 0
VDU 1
LPT 0
LPT 1
OMU
- MO91 0
STU
- MO91 0
ACU
- MO91 0
Output control
Checked by: Date:
9.3.10 Test 5.7: Clock equipment

Alarms not on
_____________________________________________________
_____________________________________________________
_____________________________________________________
Switchover
_____________________________________________________
_____________________________________________________
_____________________________________________________
Checked by:___________________Date:_____________________
9.3.11 Tests 5.8 / 5.9: Processor units and message bus connections
Table 37 : Processor units and message bus connections
Computer Unit OK MB 0 OK MB 1 OK
OMU
CM 0
CM 1
CCC 0
CCC 1
CCSU 0
CCSU 1
CCSU 2
CCSU 3
CCSU 4
CCSU 5
SIPU 0 = 0,0
SIPU 1 = 0,1
SIPU 2 = 1,0
SIPU 3 = 1,1
SIPU 4 = 2,0
SIPU 5 = 2,1
SIPU 6 = 3,0
SIPU 7 = 3,1
STU 0
STU 1
PDCU 0 (DXTip only )
PDCU 1 (DXTip only )
EDU 0
EDU 1
Table 37: Processor units and message bus connections (cont'd.)
Computer Unit OK MB 0 OK MB 1 OK
ACU 0
ACU 1
CCM 0
CCM 1
Checked by: Date:
9.3.12 Test 5.10: ESB26 LAN ports

The LAN ports and cables are checked using the four tables provided below.
The LAN ports are listed separately for the CM units of the DXTA and ACU units of the DXTB cabinets.
Figure 11 : LAN ports: CM 0 in the DXTA cabinet
DXTA / CM 1 / ESB26-1 (slot 02) / SWU 1
From To
Cartridge / slot / OK/
Port Conn. position Unit Port Plug - in unit Note
Conn. position NOK
1 3.9F 02.ETH1 CPLAN-A/B04/12
2 3.9F 02.ETH2 CPLAN-A/B04/13
14 3.9B 02.2G OMU EL 1 CP816 -A CM2C-A /10/2.6B 10.1E CPU LAN 1

15 3.9B 02.2J PDCU 1 EL 1 CP816-A DC3C-A/09/ 1.4B 09.1E CPU LAN 1
16 3.9B 02.2L PDCU 0 EL 1 CP816-A DC3C-A/09/ 1.0B 09.1E CPU LAN 1
17 3.9B 02.2N SIPU 3 EL 1 CP816-A DC3C-A/09/ 5.0B 09.1E CPU LAN 1
18 3.9B 02.2P SIPU 2 EL 1 CP816-A DC3C-A/04/5.0B 04.1E CPU LAN 1
19 3.9B 02.2R SIPU 1 EL 1 CP816-A DC3C-A/04/ 1.4B 04.1E CPU LAN 1
20 3.9B 02.2T SIPU 0 EL 1 CP816-A DC3C-A/04/ 1.0B 04.1E CPU LAN 1
21 3.9B 02.2V CCC 1 EL 1 CP816-A CC4C-A/07/ 3.3B 07.1E CPU LAN 1
22 3.9B 02.2X CCC 0 EL 1 CP816-A CC4C-A/07/ 3.0B 07.1E CPU LAN 1
Panel/connector
23 3.9F 02.ETH23 ESB26 CPLC18/B03/04 Ext. use, 1000 Mbit/s
24 3.9F 02.ETH24 ESB26 CPLC18/B03/05 Ext. use, 1000 Mbit/s
25 3.9F 02.ETH25 ESB26 CPLAN-A/B04/04 Ext. use, 1000 Mbit/s
26 3.9F 02.ETH26 ESB26 CPLAN-A/B04/05 Ext. use, 1000 Mbit/s
3.9F 02.SER ESB26 CPLAN-AB04/28 Ext. use
3 3.9B02.1A ESB26 CM2C-A/05/2.6B05.1A SWU 1 - SWU 3

5 3.9B 02.1E ESB26 CPLAN-A B05/04 Ext. use, 100 Mbit/s
6 3.9B 02.1G ESB26 CPLAN-A B05/05 Ext. use, 100 Mbit/s
7 3.9B 02.1J ESB26 CPLAN-A B05/06 Ext. use, 100 Mbit/s
8 3.9B 02.1L ESB26 CPLAN-A B05/07 Ext. use, 100 Mbit/s
9 3.9B 02.1N ESB26 CPLAN-A B05/12 Ext. use, 100 Mbit/s
10 3.9B 02.1P ESB26 CPLAN-A B05/13 Ext. use, 100 Mbit/s
11 3.9B 02.2A ESB26 CPLAN-A B05/14 Ext. use, 100 Mbit/s
12 3.9B 02.2C CPLAN-A B05/15 Ext. use, 100 Mbit/s
dn05183258x3x0xen
Figure 12 : LAN ports: CM 1 in the DXTA cabinet
Figure 13 : LAN ports: ACU 0 in the DXTB cabinet
Figure 14 : LAN ports: ACU 1 in the DXTB cabinet
9.3.13 Test 6.1.1: Wired alarms

Table 38 : Testing the alarm groups in the DXT(T)ip DXTA cabinet (CLS 0,1)
CLOC-B (CLS 0,1)

Functional Position Connector Alarm OK Note
unit group
CCC 0 *) 3.0 B 02R3 2 CLSU 0
Table 38: Testing the alarm groups in the DXT(T)ip DXTA cabinet (CLS 0,1) (cont'd.)
CLOC-B (CLS 0,1)

unit group
B 02R5 4 CLSU 0
SIPU 2 5.0 B 02R7 6 CLSU 0
SIPU 0 *) 1.0 B 02S1 8 CLSU 0
OMU *) 2.6 B 02S3 10 CLSU 0
CM 0 *) 3.6 B 02S5 12 CLSU 0
CCSU 0 *) 4.0 B 02S7 14 CLSU 0
PDFU-B 0 **) 0.0 B 04R1 1 CLSU 1

CCC 1 *) 3.3 B 04R3 3 CLSU 1
B 04R5 5 CLSU 1
B 04R7 7 CLSU 1
PDCU 0 *) 1.2 B 04S1 9 CLSU 1
CCSU 1 *) 4.3 B 04S3 11 CLSU 1
B 04S5 13 CLSU 1
ET4C 0 *) 5.6 B 04S7 15 CLSU 1
Checked by: Date:
Table 39 : Testing the alarm groups in the DXT(T)ip DXTA cabinet (CLAB 0,1)
CLAC-B (CLAB 0,1)

unit group
FTRB-A 0 **) 21.0 B 02R1 0 CLAB 0
B 02R3 2 CLAB 0
B 02R5 4 CLAB 0
SIPU 3 5.2 B 02R7 6 CLAB 0
B 02S1 8 CLAB 0
B 02S3 10 CLAB 0
SIPU 1 *) 1.4 B 02S5 12 CLAB 0
CCSU 2 *) 4.6 B 02S7 14 CLAB 0
B 03R1 1 CLAB 1
B 03R3 3 CLAB 1
Table 39: Testing the alarm groups in the DXT(T)ip DXTA cabinet (CLAB 0,1) (cont'd.)
CLAC-B (CLAB 0,1)

unit group
B 03R5 5 CLAB 1
B 03R7 7 CLAB 1
B 03S1 9 CLAB 1
PDCU 1 *) 1.6 B 03S3 11 CLAB 1
CM 1 *) 3.9 B 03S5 13 CLAB 1
CCSU 3 *) 4.9 B 03S7 15 CLAB 1
Checked by: Date:
Table 40 :
*) CCC 0 (alarm group 2) AL020 CCC 0 Power alarm

AL021 CCC 0 Clock alarm
AL022
AL023
**) FTRB 0 (alarm group 0) AL000 FTRB 0 Power alarm
AL001
AL002
AL003
Table 41 : Testing the alarm groups in the DXTTip DXTB cabinet (CLAB 2, 3)
CLAC-B (CLAB 2, 3)
unit group
PDFU-B 0 **) 0.0 B 02R1 0 CLAB 2
B 02R3 2 CLAB 2
B 02R5 4 CLAB 2
SIPU 4 *) 1.0 B 03R7 6 CLAB 2
ACU 0+ SD 0 2.0 B 02S1 8 CLAB 2
ACU *)
CCM 0 *) 3.8 B 02S3 10 CLAB 2
CCSU 4 *) 5.0 B 02S7 14 CLAB 2
B 03R1 1 CLAB 3
Table 41: Testing the alarm groups in the DXTTip DXTB cabinet (CLAB 2, 3) (cont'd.)
CLAC-B (CLAB 2, 3)
unit group
B 03R3 3 CLAB 3
B 03R5 5 CLAB 3
SIPU 5 1.2 B 03R7 7 CLAB 3
STU 0 + SD 0 3.0 B 03S1 9 CLAB 3
STU *)
EDU 0 *) 4.2 B 03S5 13 CLAB 3
CCSU 5 *) 5.3. B 03S7 15 CLAB 3
Checked by: Date:
Table 42 : Testing the alarm groups in the DXTTip DXTB cabinet (CLAB 4, 5)
CLAC-B (CLAB 4, 5)
unit group
FTRB-A 0 **) 21.0 B 02R1 0 CLAB 4
B 02R3 2 CLAB 4
B 02R5 4 CLAB 4
SIPU 6*) 1.4 B 02R7 6 CLAB 4
ACU 1 + SD 1 2.6 B 02S1 8 CLAB 4
ACU *)
CCM 1 *) 4.8 B 02S5 12 CLAB 4
B 02S7 14 CLAB 4
B 03R1 1 CLAB 5
B 03R3 3 CLAB 5
B 03R5 5 CLAB 5
SIPU 7 *) 1.6 B 03R7 7 CLAB 5
STU 1 + SD 1 3.4 B 03S1 9 CLAB 5
STU *)
EDU 1 *) 4.6 B 03S3 11 CLAB 5
1 B 03S7 15 CLAB 5
Checked by: Date:
9.3.14 Test 6.2.1: Complete power break in the system
Table 43 : Complete power break in the system
PHASE RECOVERY TIME NOTE

MMI ready
Alarm XXX
Units to WO-EX
Units to SP-EX
Checked by: Date:
9.3.15 Test 6.3.1/6.3.2: State transitions and unit diagnostics

Checking processor units
The processor units tested for the state transitions and unit diagnostics are listed in Table 44 .
The result of the test is marked as OK, NOK or NA.
Characters * in the columns show which MB-CCC combination is being tested.
Table 44 : Unit test: computer units
Unit Active CCC 0 Active CCC 0 Active CCC 1 Active CCC 1

and MB,0 and MB,1 and MB,0 and MB,1
OMU
CM 0
CM 1
MB 0 * *
MB 1 * *
CCC 0 * *
CCC 1 * *
ACU 0
ACU 1
CCSU 0
CCSU 1
CCSU 2
CCSU 3
CCSU 4
CCSU 5
Table 44: Unit test: computer units (cont'd.)
Unit Active CCC 0 Active CCC 0 Active CCC 1 Active CCC 1

and MB,0 and MB,1 and MB,0 and MB,1
SIPU 0,0
SIPU 0,1
SIPU 1,0
SIPU 1,1
SIPU 2,0
SIPU 2,1
SIPU 3,0
SIPU 3,1
PDCU 0
PDCU 1
SBUS 0
SBUS 1
CLS 0
CLS 1
CCM 0
CCM 1
CLAB 0
CLAB 1
CLAB 2
CLAB 3
CLAB 4
CLAB 5
9.3.16 Test 6.4: Connecting external PCMs to ET4C cartridge

The following two tables present all ET index numbers for checking the PCM connections in the ET4C
cartridges. There are separate tables for ET index numbers used in the group switch GSWB 0 and GSWB 1.
The index numbers 34 - 95 are reserved for ECE2-NT/ECE2-NTC or ET2E-TB/ET2E-TCB cards and
numbers 128 - 255 for ET4E/ET4E-C cards, and are used as follows:
• 34–63 in ET4C 0, DXTA
• 66–95 in ET4C 1, DXTB
• 128–191 in ET4C 0, DXTA
• 192–255 in ET4C 1, DXTB
Note that there is no test available for the ECE2 units.
UNIT INDEX
ECE2/ET2E 34 35 38 39 42 43 46 47
ECE2/ET2E 50 51 54 55 58 59 62 63
ECE2/ET2E 66 67 70 71 74 75 78 79
ECE2/ET2E 82 83 86 87 90 91 94 95
ET4E 128 129 130 131 132 133 134 135
ET4E 136 137 138 139 140 141 142 143
ET4E 144 145 146 147 148 149 150 151
ET4E 152 153 154 155 156 157 158 159
ET4E 160 161 162 163 164 165 166 167
ET4E 168 169 170 171 172 173 174 175
ET4E 176 177 178 179 180 181 182 183
ET4E 184 185 186 187 188 189 190 191
ET4E 192 193 194 195 196 197 198 199
ET4E 200 201 202 203 204 205 206 207
ET4E 208 209 210 211 212 213 214 215
ET4E 216 217 218 219 220 221 222 223
ET4E 224 225 226 227 228 229 230 231
ET4E 232 233 234 235 236 237 238 239
Table 45: ECE2 and ET2E/ET4E index table: GSWB 0 (cont'd.)
UNIT INDEX
ET4E 240 241 242 243 244 245 246 247
ET4E 248 249 250 251 252 253 254 255
Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Checked by:___________________Date:_____________________
UNIT INDEX
ECE2/ET2E 34 35 38 39 42 43 46 47
ECE2/ET2E 50 51 54 55 58 59 62 63
ECE2/ET2E 66 67 70 71 74 55 78 79
ECE2/ET2E 82 83 86 87 90 91 94 95
ET4E 128 129 130 131 132 133 134 135
ET4E 136 137 138 139 140 141 142 143
ET4E 144 145 146 147 148 149 150 151
ET4E 152 153 154 155 156 157 158 159
ET4E 160 161 162 163 164 165 166 167
ET4E 168 169 170 171 172 173 174 175
ET4E 176 177 178 179 180 181 182 183
Table 46: ECE2 and ET2E/ET4E index table: GSWB 1 (cont'd.)
UNIT INDEX
ET4E 184 185 186 187 188 189 190 191
ET4E 192 193 194 195 196 197 198 199
ET4E 200 201 202 203 204 205 206 207
ET4E 208 209 210 211 212 213 214 215
ET4E 216 217 218 219 220 221 222 223
ET4E 224 225 226 227 228 229 230 231
ET4E 232 233 234 235 236 237 238 239
ET4E 240 241 242 243 244 245 246 247
ET4E 248 249 250 251 252 253 254 255
Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Checked by:___________________Date:_____________________
9.3.17 Test 6.5: Spare plug-in units

Table 47 : Spare units
INDEX
UNIT 0 1 2 3 4 5 6 7 8
Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Checked by:__________________Date:______________________
9.3.18 Test 7: Clock synchronisation

Preparations (DRI;)
Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Changeover to back-up connection
Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Changeover to internal oscillator
Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Synchronisation with external clock
Observations:
_____________________________________________________
_____________________________________________________
_____________________________________________________
Checked by:___________________Date:_____________________
A Execution instructions
Note
The printouts included in the manual provide examples only, and therefore the actual printouts may differ from
the ones presented in this document.
In the following printouts, the start-up of a computer unit, the passwords of the system and the software
versions are verified.
A.1 Booting (reset)

DMX SYSTEM START-UP TESTS
SELF TEST RESULT = 00000000 PROCESSOR ID & REV = 0606
CPU ID = 61C4 CPU FEATURES = 00 CPU RESET STATUS = 7EFC
SYSTEM RAM OK
NTC PCI Software version 0.2-0 created 24.10.1997
SEARCHING PCI/PCI BRIDGES
BUS 0 DEV 2
BUS 1 DEV 1d
BUS 1 DEV 1f
BUS 0 DEV 1e
BUS 4 DEV 2
REGISTERING DEVICES
BUS 0 DEV 0 FUN 0
BUS 4 DEV 1 FUN 0
BUS 0 DEV 1f FUN 0
BUS 1 DEV 1c FUN 0
BUS 1 DEV 1e FUN 0
CONFIGURING PCI/PCI BRIDGES
BUS 0 DEV 2
BUS 1 DEV 1d
BUS 1 DEV 1f
BUS 0 DEV 1e
BUS 4 DEV 2
CONFIGURING MBIFS
BUS 5 DEV e FUN 0
BUS 5 DEV f FUN 0
MB 00: MBIF-B, MB ADDR 00, FREQ 2MHZ, TRANS.FREQ 16MHZ, WIDTH 16BIT
MB 01: MBIF-B, MB ADDR 00, FREQ 2MHZ, TRANS.FREQ 16MHZ, WIDTH 16BIT
RESET MESSAGE OK
CONFIGURING SCSIS
BUS 3 DEV 1 FUN 0
BUS 3 DEV 1 FUN 1
BOP816GX.PAC 1.4-0 04/08/11
DRAM SIZE = 20000000H BYTES
RESET TYPE = WARM
BLACKBOX FORMING SKIPPED
In the OMU, the BOLERO searches the disks for the correct software package.
CHOOSING PACKET
FOUND PACKET FROM <source>
LOADING NET CONFIGURATION FROM <source>
NET CONFIGURATION LOADED
PACKET <package id.>
The BOLERO loads the BOTTOM file. The BOTTOM contains information on the basis of which the BOLERO
is able to ask for the right load list.
LOADING LOAD LIST FROM <source>
LOAD LIST LOADED
MODULE LOADING STARTS

LOADING MODULES FROM OWN MEMORY
CHAIN NOT OK STATUS = 0000277B
LOADING MODULES FROM LOCAL DISKS
BSP CDS CPV CUR DIP DOF DUC FDS FLL FLL FLL FLL FLL FLL FLL FLL FLL FLL
FLL FLL FLL FLL FLL FLL FLL FLL FSY HWU IOL KDD KDD LAN LGR LMG LPS MEF
MGK MGS NEC PLF POD PXP SXS TMN THP UNF VDS VIP VT1 VPS VTS WDS VID ARN
ALA APP DEE ASY DEB CLU BUE BOM BBO BJO BOS BOX C1R CAT CEP CNY DAE CPY
CP2 COF COK CPS CPF CPU DBS DBV DBU DUD DPA DGT DGX DIA DIS DOC DME DMX
DSK DTC DXH DUF DUM DUZ EHB DXP DYT EDI EDU EFO EFI EHF GEO EPE ELC EID
EKL EIO ENA FLR EXO EQM EQP ETH ERR FFH FDM FCM EXW FAM FED FEM FIZ FIS
FIR FLM FMP FMN FSR FUT FUN FUZ JOR H1R H1S HAP HOK HWA HRU HRL HWO HWI
HWS IOM IOF INV IOT IPB IPD IPQ ISR JAN JAG JAS MAO JUT JUP L3B KGP L3S
LMA LDA LF4 LIB LSE LOG LMX LOM LOS LOT LRM LSU MAS MBD MM2 MTF MRS MMI
MOP MON MOV MTE NET NAS NDV NEO NMC OMO OLD OAZ OAM O45 O54 O7F OCM OCE
OCE OCL ODC OFF OMM OSI ONR ONC ONS OOF OOP PAC OVF OVT OXF PFM PAG PAX
PBL PAY PAZ PBH PBM PIL PGE PLU PO2 PMT PON POM POZ POX PRS PRT PS0 PWG
QMD RDI RAU RCA RCX RCB RCP RE7 REQ REC RME RIZ RIA RFG RFM RIE RIO ROI
SAV RYS RTL SCF SEK SCS SEE SHO STK SOW SOX ST6 SW2 STY SUP SW5 SWF SYF
SYS TAP TOP THE TIS TUK TUT TZI UNC VDI URM USA UTC VDU VTE VIM VSU WFA
WYN WUP WUT XML ZSK YEM ZLI
ALL MODULES LOADED
CONFIGURING OTHER TARGET DEVICES

BUS 2 DEV 1 FUN 0
BUS 2 DEV 1 FUN 1
BUS 2 DEV 2 FUN 0
BUS 2 DEV 2 FUN 1
BUS 3 DEV 2 FUN 0
BUS 5 DEV 9 FUN 0
BUS 5 DEV c FUN 0
BUS 5 DEV d FUN 0
The following output informs that the debugger software has been started:
DEBUGGER READY
The service terminal session is started:

STARTING SERVICE TERMINAL SESSION 2005-05-31 15:33:49.10
ENTER USERNAME < SYSTEM
ENTER PASSWORD < ******
WELCOME TO SERVICE TERMINAL DIALOGUE
00:MAN>
DEFINING UNIT TYPE
PROCESSING FAMILIES FIZ CPU FUZ HWO OAZ DUZ MOP HWS EDI TUK RCX
VDU VDU VDU VDU VDU VDU VDU VDU TAP IOM VTE SOW BOM RDI RME PFM FEM PBL
FED DUM CNY FDM
FILE LOADING ACTIVATED 000F 0001 0000
INITIALIZING WORK FILES
LOADING STARTED 0003 2004 01
PROCESSING FAMILIES FUZ HWO HWS PAX EFO RIE RIA RYS RDI FED SAV
REQ SOW RCX BOM CEP RIZ WYN NDV JAG
READY - PHASE 2
LOADING STARTED 0007 C000 02
PROCESSING FAMILIES DBS EQM
DATABASE LOADING ACTIVATED 000F 0001 01C5
LOADING DATABASES EQM
PROCESSING FAMILIES HWO FIZ HWS
FILE LOADING ACTIVATED 000F 0001 FFFF
LOADING STARTED 1C00 C000 02
PROCESSING FAMILIES PRT PIL
PLUG-IN UNIT LOADING ACTIVATED 000F 0001 FFFF
LOADING STARTED 001E C000 01
PROCESSING FAMILIES HWO NAS LOS HRU PFM
READY - PHASE 3
PROCESSING FAMILIES ALA DPA SCF PS0 PLU RE7 REC JUT PS0 ONR NET
NET NET NET NET NET NET NET NET NET NET NET NET NET NET NET NET NET NET
NET NET NET NET NET NET NET NET NET NET NET NET NET OMM DTC SEE MMI OCL
CPS LSU EHB FCM NMC COF O7F DEE DXH FLM CPY ERR DBV EDU IPQ DYT FFH DGT
FMP JOR LSE EID YEM OOF LMA EKL ELC IPB MTF COK L3B L3S OVT OCM FSR IPD
DUD MM2 EQP OVF SHO TIS ZSK JAS OLD OOP OXF H1S JAN ONC VID EHF LOM HOK
PWG DIS UTC ODC ARN QMD RFG OFF O54 GEO ONS NEO LRM MAO EXW O45 THE ROI
H1R URM TZI SYS SW5 HWA SUP VSU DOC WUP OCL DEE GEO EHB EHF DIA DIA DIA
DIA TIS SYS EID SEE HOK URM CPY LOM MMI RFG ROI ALA HWA SHO DGT DIS HWA
HWO DOC UTC LSU ERR COK COF OCM ONS OOP ODC OOF OVF O7F O45 O54 OVT NMC
VID ONC H1R H1S ZSK MAO OFF OXF FLM SW2 ARN TZI CPS MTF SW5 LMA DBV NEO
FCM JAN IPB YEM IPD FFH JAS LRM MM2 LRM LSU LSE EQP L3B L3S FSR LDA PWG
FMP ELC JOR EXW CPU SUP THE DXH EDU IPQ DYT DUD OLD QMD LDA
RUNNING PACKAGE BB 3.13-0
READY - WO 2005-05-31 15:34:19
The notices inform that all modules have been loaded into the memory and show the status of the cache
memory (in use or not).
A.2 Starting the software and loading the files
After the notice DEBUGGER READY, the operating system creates the Operating System Interface and
Testing Utilities (OSITUS) processes and the USAPRO. Immediately after this the following information is
displayed on the service terminal:
DEFINING UNIT TYPE
PROCESSING FAMILIES FIZ CPU FUZ HWO OAZ DUZ MOP
HWS EDI RCX VDU VDU VDU VDU VDU VDU VDU VDU TAP IOM VTE SOW
BOM RDI RME PFM FEM PBL FED DUM CNY FDM
Library managers, I/O and loading system program blocks are created and started.
Library managers are programs which call the initialisation routines of the libraries and supervise the condition
of the libraries. The starting order is defined accurately, because the libraries can call different libraries when
initialised. The initialisation of some libraries takes place in two phases. The library is first initialised in such a
way that the references to the library (library calls) do not cause interruptions in the program blocks, that is,
the program blocks do not make memory reference errors. The second phase is initialised after the files
used by the library have been loaded.
The initialisation routines are called by the following library managers, for example:
• the FISLIB Library Manager (FIZSLM). The FIZSLM initialises the booted files into the file directory.
After this the references to the files to be booted are operative.
• the FUNLIB Library Manager (FUZNLM). The FUZNLM initialises and updates the unit address table,
the Working State and Configuration file (SCDFLE) and system variables.
• the HWILIB Library Manager (HWOMAN). The HWOMAN initialises the Hardware Configuration Inquiry
Library (HWILIB). The HWILIB comprises services connected with system configuration handling, such
as reading routines of the PCM Configuration File (PCMCON).
• the PMTLIB Library Manager (PRTPGM). The Parameter Library (PMTLIB) takes care of the handling
of the General Parameter File (PRFILE).
• the OAMLIB Library Manager (OAZMLM). The Operation and Maintenance On-line Library (OAMLIB)
serves the other program blocks when they require information about the operation and maintenance
network and the systems accessed through it.
If the unit has been started in a so-called hot start-up, none of the files are loaded. In the hot start-up
• the file directory is not changed, that is, the directory in the data area of the FISLIB is left unchanged
• the USAPRO commands the FIZSLM Library Manager to recover the FISLIB
• the FIZSLM initialises the FISLIB so that the addresses, sizes, and other information of the files loaded
in the previous restart are not changed.
If the hot start-up does not succeed, the type of the start-up is set back to normal (loading).
** RESET TYPE CHANGED
Hot start-up is not possible.
The start-up then continues in a normal manner, that is, the loading of the files is started.
When the FUZNLM is created and started for the first time, it initialises the system variables of the unit into the
original state, for example OWN_UNIT_STATE = RE. At the same time all the LEDs indicating the state of the
unit are switched off in the central processing unit. The unit is in state RESTART (5F). After the initialisation of
the libraries and the starting of the load system, a notice is given about the initialisation of the work files.
INITIALIZING WORK FILES
PROCESSING FAMILIES FUZ HWO HWS PAX EFO RIE RIA RYS RDI FED SAV
REQ SOW RCX BOM CEP RIZ WYN NDV JAG
Although the notice LOADING STARTED is given in the printouts, no actual loading is performed. Instead,
the LOADER initialises the work files mentioned in the File Loading List File (FLLIST). State '0F' indicates
that the working state of the unit is 'working' (state WORKING). The Recovery Program Block (RCXPRO) is
inquired about the working state of the unit.
READY - PHASE 2
The meaning of the notice is that the RCXPRO has been given the notice 'unit restarted' and the unit is ready
to enter phase 2. The RCXPRO gives loading permission or, if a unit with a higher priority is restarting,
asks the USAPRO to wait (see Section 5.2.1 ). A notice is sent to the maintenance computer which may
be either the OMU or the CM.
In case the total time limit expires (approx. 20 minutes), the following is output:
**TIME OUT
A time-out may also occur if no connection is established to the recovery system. The time-out is set in such
a way that the possible starting of the maintenance unit is taken into consideration. In connection with the
loading permission, the unit state is also given and the USAPRO updates this as its own state.
After the loading permission has arrived, the first load group is loaded. The files of the FUNLIB and some
files used by the HWILIB belong to this group. The group is loaded in the working states WO (working), SP
(spare), and TE (test). The output is as follows:
FILE LOADING ACTIVATED <state> <l_type> <rcv_group>
LOADING STARTED <rcv_group> <src_comp> <src_proc>
<state> state of the USAPRO,
here: WO
<1_type> loading type,
here: total loading of the unit (0000)
<rcv_group> file group of the recovery system,
here:0007
<src_comp> source computer,
here: C000
<src_proc> cooperative program block,
here: DUMPER (91H)
The USAPRO checks from the FLLIST file that the load group of the SCDFLE file exists. If the group is not
found, the following is output:
**UNIT START UP STOPPED <proc> <err_code>
<fail_comp> <fail_proc>
<l_group> <file_id>
(output here on different lines)
<proc> program block which detected the failure,
here: USAPRO, A0H
<err_codeA> general DXT error code set by the program
block,
here: 305H, "load group not found"
<fail_comp> computer where the failure is possibly found,
here: message bus of the unit
<fail_proc> program block where the failure is possibly
found,
here: USAPRO, A0H
<l_group> load group,
here: 0002 - 0004
<file_id> file number,
here: SCDFLE,0AH
If the loading is successful, the program blocks are started:

PROCESSING FAMILIES DBS EQM
DATABASE LOADING ACTIVATED 000F 0001 01C5
LOADING DATABASES EQM
PROCESSING FAMILIES HWO FIZ HWS PIL
At this point the FUZNLM initialises the FUNLIB - the SCDFLE file is available. At the same time the FUZNLM
switches on the LEDs in the central processing unit. The LEDs indicate the working state of the unit.
The Boot Management Program Block (BOMBER) is started, and after this the unit can be used as a source
for booting.
The rest of the load groups are then loaded according to the order defined by the Loading Group File
(LGROUP). The order in which the files are loaded within a load group is defined in the FLLIST. In the
case of the OMU, the following is output:
FILE LOADING ACTIVATED 000F 0001 FFFF
LOADING STARTED 1C00 C000 02
000F working state of the USAPRO
and the unit
FFFF the rest of the load
groups are loaded
The state of the USAPRO is defined on the basis of the state given by the recovery system in the loading
permission.
If the state is not to be received, the starting of the unit is stopped. The output is as follows:
**UNIT START UP STOPPED <proc> <err_code>
<fail_comp> <fail_proc>
<l_group> <file_id>
(output here on different lines)
<proc> program block which detected the failure,
here: USAPRO, A0H
<err_code> general DXT error code set by the program
lock,
here: 30FH, "unit in wrong state"
<fail_comp> computer where the failure is possibly found,
here: message bus of the unit
<fail_proc> program block where the failure is possibly found,
here: USAPRO, A0H
<l_group> load group,
here: FFFF
<file_id> file number
here: FFFFFFFF
The preprocessors are also loaded if the Plug-in Unit Software Package Loader (PILOAD) has been loaded in
the software package of the unit. The notice of the loading is given even if no preprocessor unit to be loaded
is included in the unit. In this case the PILOAD acknowledges the load command immediately with OK.
PLUG-IN UNIT LOADING ACTIVATED 000F 0001 FFFF
LOADING STARTED 001E C000 01
PROCESSING FAMILIES PRT HWO NAS LOS HRU TXL PFM
000F: USAPRO working state
FFFF: load group in this case
0001: loader
When all files have been loaded, the starting permission for phase 3 (starting phase of the program blocks) is
asked for:
READY - PHASE 3
The recovery system gives the permission to proceed or asks the USAPRO to wait. The USAPRO continues
to wait if a unit with a higher priority is starting. In case the total time limit expires (approx. 20 minutes),
the following is output:
**TIME OUT
A time-out may also occur if no connection is established to the recovery system. In the case of the OMU,
the following is output:
PROCESSING FAMILIES ALA DPA SCF PS0 PLU RE7 REC JUT PS0 ONR NET
NET NET NET NET NET NET NET NET NET NET NET NET NET NET NET NET NET NET
NET NET NET NET NET NET NET NET NET NET NET NET NET OMM DTC SEE MMI OCL
CPS LSU EHB FCM NMC COF O7F DEE DXH FLM CPY ERR DBV EDU IPQ DYT FFH DGT
FMP JOR LSE EID YEM OOF LMA EKL ELC IPB MTF COK L3B L3S OVT OCM FSR IPD
DUD MM2 EQP OVF SHO TIS ZSK JAS OLD OOP OXF H1S JAN ONC VID EHF LOM HOK
PWG DIS UTC ODC ARN QMD RFG OFF O54 GEO ONS NEO LRM MAO EXW O45 THE ROI
H1R URM TZI SYS SW5 HWA SUP VSU DOC WUP OCL DEE GEO EHB EHF DIA DIA DIA
DIA TIS SYS EID SEE HOK URM CPY LOM MMI RFG ROI ALA HWA SHO DGT DIS HWA
HWO DOC UTC LSU ERR COK COF OCM ONS OOP ODC OOF OVF O7F O45 O54 OVT NMC
VID ONC H1R H1S ZSK MAO OFF OXF FLM SW2 ARN TZI CPS MTF SW5 LMA DBV NEO
FCM JAN IPB YEM IPD FFH JAS LRM MM2 LRM LSU LSE EQP L3B L3S FSR LDA PWG
FMP ELC JOR EXW CPU SUP THE DXH EDU IPQ DYT DUD OLD QMD LDA
The rest of the program blocks are created and started in phase 3. The names of some program blocks often
occur in the phase printouts several times, because the USAPRO outputs the name of the program block
each time it creates or sends start messages (i.e. supervision messages), or warm-up or update commands.
When the starting of the program blocks has been completed the following is output:
RUNNING PACKAGE <package id>
READY - WO Unit in state WO-EX
READY - TE Unit in state TE-EX
READY - SE Unit in state SE-OU
A.3 Monitoring the start-up of OMU

To monitor the start-up of the OMU, you must first reset it in one of the following ways:
• press the RESET button in the computer unit
• give the MML command ZUSU on the VDU
• give command ZAUL from the service terminal
• switch the power off in the PSC6-A plug-in unit
• power up the DXT(T)ip.
Table 48 :
Step Output
1. The first phase output indicating "DMX SYSTEM START-UP TESTS"
the start-up of the BOLERO:
If this is not output, see Fault conditions,
BOLERO start-up failure.
2. Message Bus Interface (MBIF) green LEDs lit.
If the LEDs are not lit (unit is not
connected to the bus), see Fault conditions,
MBIF fault and BOLERO start-up failure.
3. RAM tests successful: "ZERO RAM OK"
"SYSTEM RAM OK”
“DRAM SIZE = 10000000H BYTES "
If tests are not successful, see
Fault conditions,
RAM fault in start-up.
4. Transmission of the RESET message
successful.
If not, see Fault conditions, MBIF fault
(Notice on the unit start-up has not reached
maintenance program blocks.)
5. Choosing software package in the OMU was "CHOOSING PACKET"
successful:
If not, see Fault conditions,
Failure in choosing software package from
OMU disks.
6. Loading of the computer "LOADING NET CONFIG... "
configuration table successful:
If not, see Fault conditions, Computer
configuration table loading failure.
7. Loading of the load list successful. "LOADING LOAD LIST FROM
<source>"
If loading fails, see Fault conditions,
Loading list load failure.
8. Loading of the load modules successful: "LOADING MODULES FROM
<source>"
If loading fails, see Fault
conditions, Loading module load failure
9. Debugger software started up: "DEBUGGER READY"
If the start-up fails, see Fault
conditions, USAPRO start-up failure.
10. First "PROCESSING FAMILIES" "PROCESSING FAMILIES"
notice is output on the terminal:
Table 48: (cont'd.)
Step Output
If not, see Fault conditions, USAPRO start-up
failure and Program block start-up failure
11. The FIZSLM is started up: "PROCESSING FAMILIES FIZ"
Program block start-up failure and
File system initialisation failure.
12. Initialisation of work files OK: "FILE LOADING ACTIVATED 000F.."
"INITIALIZING WORK FILES"
File system initialisation failure.
13. Loading of the first load group OK: "FILE LOADING ACTIVATED 000F.."
"LOADING STARTED 0003.."
If loading fails, see Fault
conditions, Recovery service block
(RCYSEB) file loading failure.
14. Start-up of program blocks OK: "PROCESSING FAMILIES"
Program block start-up failure.
15. The FUZNLM start-up OK: "PROCESSING FAMILIES FUZ"
Recovery service block (RCYSEB) file
loading failure, Program block
start-up failure, and File system
initialisation failure.
16. The USAPRO is given permission to load: "READY - PHASE 2"
"FILE LOADING ACTIVATED 000F.."
Recovery Program Block (RCXPRO)
start-up failure and Computer in
incorrect state.
17. Working state of unit is
WO/TE/SE:
Computer in incorrect state.
18. Loading of a loading group OK: "LOADING STARTED ..."
All remaining load groups are
loaded.
If loading is not OK, see Fault
conditions,
File loading failure and File system
initialisation failure.
Table 48: (cont'd.)
Step Output
19. The USAPRO is given permission to "READY - PHASE 3"
start up program blocks.
If permission is not given, see
Fault conditions, Recovery Program Block
(RCXPRO) start-up failure.
20. Start-up of program blocks OK: "PROCESSING FAMILIES ..."
All remaining program blocks are created and
started up.
If start-up is not OK, see Fault conditions,
21. Start-up of unit is terminated: "READY - WO"
"READY - TE"
"READY - SE"
If start-up is not terminated, see
Fault conditions, Recovery Program Block
(RCXPRO) start-up failure and Computer in
incorrect state.
A.4 Monitoring the start-up of CM

To monitor the start-up of the Central Memory (CM), you must first reset it in one of the following ways:
• power up the DXT(T)ip
Note
If you reset an active CM with the MML command ZUSU, the command will reset the whole system. In this
case, the program asks you to confirm this.
Table 49 :
Step Output
1. The first phase output indicating the start-up of the "DMX SYSTEM START-UP TESTS"
BOLERO
If not successful, see Fault conditions, BOLERO
start-up failure.
2. MBIF green LEDs lit.
If not (unit is not connected to the bus), see Fault
conditions, MBIF fault and BOLERO start-up failure.
"SYSTEM RAM OK"
"DRAM SIZE = 40000000H BYTES"
If not, see Fault conditions, RAM fault in start-up.
4. Transmission of the RESET message
successful.
If not, see Fault conditions, MBIF fault.
(Notice on the unit start-up has not reached
maintenance program blocks.)
5. Loading of the computer configuration table "LOADING NET CONFIG..."
successful:
If not, see Fault conditions, Computer configuration
table loading failure.
6. Loading of the load list successful: "LOADING LOAD LIST"
If not, see Fault conditions, Loading list load failure.
7. Loading of the load modules successful: "LOADING MODULES FROM..."
If not, see Fault conditions, Loading module load
failure.
If not, see Fault conditions, USAPRO start-up
failure.
9. First "PROCESSING FAMILIES" notice "PROCESSING FAMILIES"
output on the terminal:
If not, see Fault conditions, USAPRO start-up failure
and Program block start-up failure.
10. The FIZSLM started up: "PROCESSING FAMILIES FIZ"
If not, see Fault conditions, Program block start-up
failure and File system initialisation failure.
11. Initialisation of work files OK: "FILE LOADING ACTIVATED
005F.." "INITIALIZING WORK
FILES"
If not, see Fault conditions, File system initialisation
failure.
Table 49: (cont'd.)
Step Output
12. Loading of the first load group OK: "FILE LOADING ACTIVATED
005F.." "LOADING STARTED
0002.."
If loading fails, see Fault conditions, Recovery
service block (RCYSEB) file loading failure.
13. Start-up of the FUZNLM OK: "PROCESSING FAMILIES FUZ"
If not, see Fault conditions, Recovery service
block (RCYSEB) file loading failure, Program block
start-up failure, and File system initialisation failure.
"FILE LOADING ACTIVATED
002F.."
If not, see Fault conditions, Recovery Program
Block (RCXPRO) start-up failure and Computer in
incorrect state.
15. Working state of unit is WO/SP/TE/SE.
If not, see Fault conditions, Computer in incorrect
state.
16. Loading of a loading group OK: "LOADING STARTED .."
If not, see Fault conditions, Recovery service block
(RCYSEB) file
loading failure.
17. Start-up of program blocks OK: "PROCESSING FAMILIES .."
18. Loading of a loading group OK: "LOADING STARTED .."
All remaining loading groups are loaded.
If loading fails, see Fault conditions, File loading
19. The USAPRO is given permission to start up "READY - PHASE 3"
program blocks:
Block (RCXPRO) start-up failure.
All remaining program blocks are created and
started up.
If start-up fails, see Fault conditions:
Program block start-up failure
21. Doubled units: Notice on the start of warming-up: "READY FOR WARM UP"
"PROCESSING FAMILIES .."
Table 49: (cont'd.)
Step Output
If no notice, see Fault conditions, Computer
warm-up failure.
22. End of the start-up of unit: "READY - WO"
"READY - SP"
"READY - TE"
"READY - SE"
Block (RCXPRO) start-up failure, and Computer in
incorrect state.
A.5 Monitoring the start-up of other computers (ACU, STU,

CCC, CCSU, EDU, SIPU, PDCU, CCM)
To monitor the start-up of the Authentication Centre Unit (ACU), Statistical Unit (STU), Call Control Computer
(CCC), Common Channel Signalling Unit (CCSU), Enhanced Data Unit (EDU), Server IP Unit (SIPU), Packet
Data Computer Unit (PDCU) or Common Channel Management Unit (CCM) you must first reset the unit
in one of the following ways:
Table 50 :
Step Output
1. The first phase output indicating the start-up of the "DMX SYSTEM START-UP
BOLERO. TESTS"
If not successful, see Fault conditions, BOLERO
start-up failure.
2. MBIF green LEDs lit.
If not (unit is not connected to the bus), see Fault
conditions, MBIF fault and BOLERO start-up failure.
"RAM OK"
If not, see Fault conditions, RAM fault in start-up.
4. Transmission of the RESET message successful.
Table 50: (cont'd.)
Step Output
If not, see Fault conditions, MBIF fault. (Notice on the
unit start-up has not reached maintenance program
blocks.)
5. Loading of the computer "LOADING NET CONFIG..."
configuration table successful:
Computer configuration table loading
failure.
6. Loading of the load list successful: "LOADING LOAD LIST"
If not, see Fault conditions, Loading list load failure.
7. Loading of the load modules successful: "LOADING MODULES
FROM..."
If not, see Fault conditions, Loading module load
failure.
9. First "PROCESSING FAMILIES" notice output on the "PROCESSING FAMILIES"
terminal:
and Program block start-up failure.
10. The FIZSLM started up: "PROCESSING FAMILIES
FIZ"
11. Initialisation of work files OK: "FILE LOADING ACTIVATED
005F.." "INITIALIZING WORK
FILES"
If not, see Fault conditions, File system initialisation
failure.
"FILE LOADING ACTIVATED"
If not, see Fault conditions, Recovery Program Block
(RCXPRO) start-up failure and Computer in incorrect
state.
13. Loading of the first load group OK: "FILE LOADING ACTIVATED
002F.." "LOADING STARTED
0004.."
If loading fails, see Fault conditions, Recovery service
block (RCYSEB) file loading failure.
14. Working state of unit is WO/SP/TE/SE. If not, see Fault conditions,
Computer in incorrect state.
Table 50: (cont'd.)
Step Output
15. Start-up of the FUZNLM OK: "PROCESSING FAMILIES
FUZ"
If not, see Fault conditions, Recovery service block
(RCYSEB) file loading failure, Program block start-up
failure, and File system initialisation failure.
16. Loading of loading groups OK: "LOADING STARTED .."
All remaining loading groups are loaded.
If loading fails, see Fault conditions, File loading
17. Loading of plug in unit OK: PLUG IN UNIT LOADING
ACTIVATED...
If loading failed, see Fault conditions
18. Start-up of program blocks OK: "PROCESSING FAMILIES .."
failure.
19. The USAPRO is given permission to start up program "READY - PHASE 3"
blocks:
(RCXPRO) start-up failure.
All remaining program blocks are created and started
up.
If start-up fails, see Fault conditions: Program block
start-up failure
21. Doubled units: Notice on the start of warming-up: "WARMING FAMILIES"
"PROCESSING FAMILIES .."
If no notice, see Fault conditions, Computer warm-up
failure.
22. End of the start-up of unit: "READY - WO"
"READY - SP"
"READY - TE"
"READY - SE"
(RCXPRO) start-up failure and Computer in incorrect
state.
A.6 Monitoring the start-up of the system

To monitor the start-up of the system, you must first reset it in one of the following ways:
• give the MML command ZUSS on the VDU
Table 51 :
Step Output
1. Monitoring start-up of the OMU.
Execution instruction: Monitoring
start-up of the OMU
When the start-up of the OMU Phase output:
has reached phase 2, the "READY - PHASE 2"
RCXPRO runs a system check
and determines the extent of the
start-up of the system.
If either of the CM units is in the Alarm:
state WO-EX, the start-up of the "SYSTEM RESTARTED"
entire system begins.
The OMU should, when started
up, be in the state WO-EX. If the
OMU is in state TE (test) or SE
(separated), the RCXPRO will not
process subsequent starting-up
impulses from other units. In this
situation the recovery is started
up in the CM and all the recovery
actions are started from there.
If necessary the state of the OMU
is changed to WO with command
ZUSC (either with the RCVHAN or
with the RCBUGG service terminal
extension).
2. The start-up of the system can
be monitored from OMU with
the RCBUGG service terminal
extension.
ZLP:U,RCB - the RCBUGG is
taken to use ZUSIC:COMP - the
states of the computer units are
monitored.
3. When the start-up of the OMU has Phase output:
ended the start-up can also be "MMI SYSTEM READY"
monitored with MML.
ZUSI:COMP;
The alarm printer is monitored.
All the following alarms indicate a
start-up failure:
UNIT RESTART FAILURE
Table 51: (cont'd.)
Step Output
Unit start-up failure and
interruption due to error.
PROGRAM BLOCK START UP
FAILURE
Creation or start-up of program
block unsuccessful.
UNIT WARMUP FAILURE
Disturbance in warm-up of
program block.
WO-EX UNIT FAULTY
Faulty unit.
UNIT RESTARTED
Unit has been re-started. Restart
can also be caused by the
RCXPRO in which case it should
not necessarily be treated as a
fault.
RESTARTED PROGRAM BLOCK
Program block has been
re-started.
4. Remember to supervise that Alarm:
the start-up of the CM units is AUTOMATIC RECOVERY
completed within a reasonable ACTION:
time. Completion time depends WO-RE TO WO-EX
on whether start-up occurred in
a powerless state or on how the
parameters of the ZUSS command
were given.
One of the two CM units is ready. Instruction:
Working state WO-EX. Monitoring the start-up of
the rest of the computer
ZUSI:COMP;
UNIT MB LGA STATE INFO
OMU 00 4002 WO-EX
CM-0 04 4005 WO-EX
CM-1 05 4005 SP-RE RP*1
. SRES
.
.
Table 51: (cont'd.)
Step Output
UNIT = unit type, MB = message
bus address,
LGA = logical address, INFO
= additional information, see
RCBUGG User's Manual.
5. When one of the CM units has
been started up the other one in
state SP is given permission to
load.
ZUSI:COMP;
OMU 00 4002 WO-EX
CM-0 04 4005 WO-EX
CM-1 05 4005 SP-RE RP 2
. SRES
.
.
6. When the CMs are ready, the Alarm:
CCCs get the loading permission. AUTOMATIC RECOVERY
ACTION: WO-RE TO
WO-EX
ZUSI:COMP;
OMU 00 4002 WO-EX
CM-0 04 4005 WO-EX
CM-1 05 4005 SP-EX
CCC-0 06 4019 WO-EX
CCC-1 07 4019 SP-EX
CCSU-0 50 4202 SP-EX
Check that no units have remained
in the start-up phase (RP 1, RP 2,
and RP 3).
If a unit with a higher priority
remains in the start-up state, it can
prohibit the start-up of the units
with lower priority.
7. Finally all units are in their working
states.
Glossary
The meanings of the terms and acronyms used in this document are explained below.
For further information on TETRA definitions, terms and concepts and the meaning of all acronyms and
abbreviations used in EADS TETRA System customer documentation, please see document EADS TETRA
System, Glossary (DN00126469).
Term / acronym Meaning

ACU Authentication Centre Unit
AS7-C Signalling Terminal for Time Slot Based O & M Interfaces
CC4C-A Common Computer Cartridge number 4
CCC Call Control Computer
CCM Common Channel Management Unit
CCSU Common Channel Signalling Unit
CL3TG-S Clock and Tone Generator
CLAB Clock and Alarm Buffer
CLAC Clock and Alarm Cartridge
CLOC Clock and Synchronization Cartridge
CLS Clock and Synchronization Unit
CM Central Memory
CM2C-A Computer and Mass Memory Cartridge number 2
CP816-A Central Processing Unit Pentium
CPLAN-A LAN Connector Panel
CPRS-A Peripheral Device Interface Panel
CRC Cyclic Redundancy Check
DC3C-A Double Computer Cartridge number 3
DSC Dispatcher Station Controller
DXTip Digital Access-layer Exchange for TETRA
DXTTip Digital Transit-layer Exchange for TETRA
EADS European Aeronautic Defence and Space Company
ECE2-NT/-NTC Echo Cancelling Exchange Terminal 2
EC2E Echo Canceller (2 PMC)
EDU Enhanced Data Unit
EPROM Erasable Programmable Read-Only Memory
ESB26 Ethernet switch
ESD Electrostatic Discharge
ET Exchange Terminal
ET2E/ET4E Exchange Terminal Plug-in Units
ET4C Exchange Terminal Cartridge number 4
EX Executing state (of a computer unit)
FNIM ET Fixed Network Interface Module Exchange Terminal
FTRB Fan Tray Unit
FUZNLM FUNLIB Library Manager
GSWB Switching Network Unit (8 kbit/s channels)
HWAT-A Hardware Alarm Terminal
I/O Input/Output
LAN Local Area Network
LED Light Emitting Diode
LPT Line Printer
MB Message Bus
MBIF Message Bus Interface Unit
MMI Man-Machine Interface
MML Man-Machine Language
MO Magneto-Optical Disk
NTP Network Time Protocol
OMU Operation and Maintenance Unit
OU Out of use state (of a computer unit)
PCM Pulse Code Modulation
PDCU Packet Data Computer Unit
PROM Programmable Read-Only Memory
PSA Power Supply Adapter
PSC Power Supply Cartridge
PSFP Power Supply Fuse Panel
RCBUGG Recovery Service Terminal
RCVHAN Working State and Restart Handling MML
RCXPRO Recovery Program Block
SCDFLE Working State and Configuration File
SE Separate state (of a computer unit)
SERO-B Serial Output Buffered Interface
SIPU Server IP Unit
STU Statistical Unit
SW10C-C Switch Cartridge for GSWB
SW128B Group Switch Unit
SWCOP-A Switch Control Processor
TBS TETRA base station
TDSC TETRA Dispatcher Station Controller
TE Testing state (of a computer unit)
TETRA Terrestrial Trunked Radio
USAPRO Unit State Administration Program Block
VDU Visual Display Unit
WDW73 Hard Disk Drive (type)
WDU Disk Unit
WO Working state (of a computer unit)
INDEX
A testing procedure ......................................... 52

computer units
alarm groups CLAB 0,1
resetting for start-up................................... 102
testing in the DXTA cabinet.......................... 82
CPRS-A (VDU and line printer
alarm groups CLAB 2, 3
connections) .................................................. 27
testing in the DXTB cabinet ........................ 84
alarm groups CLAB 4, 5
testing in the DXTB cabinet ......................... 85 D
alarm groups CLS 0,1 DXT(T)ip
testing in the DXTA cabinet ......................... 82 DXTA cabinet ............................................... 31
alarm system DXT(T)ip start-up
coverage of inspection ................................. 45 following of ................................................... 31
monitoring printouts of ................................. 45 priorities ....................................................... 31
table of MML programs for configuring ........ 45 DXTTip
cabinet DXTB............................................... 11
B DXTB cabinet............................................... 31
basic cabinet (DXTip) ................................ 11, 31

booting............................................................. 91 E
electrostatic discharge..................................... 14
C electrostatic sensitive device ........................... 13
EPROM versions
cables
checking of................................................... 26
checking of................................................... 16
ESB26 ............................................................. 43
cabling cabinet................................................. 31
ET index numbers ........................................... 86
cartridge power alarm...................................... 47
Ethernet port.................................................... 43
central memory
exchange terminals
resetting for start-up..................................... 99
amount of ..................................................... 55
clock cartridge alarm ....................................... 47
requirements ................................................ 55
clock equipment
external alarms ................................................ 49
alarm checklist ............................................. 38
switchover failure checklist .................... 38–39
testing of ...................................................... 37 F
clock synchronisation faults
preparations for checking............................. 59 reporting about............................................. 19
clock syncronisation first MML session
simulating inputs in the ET4E ...................... 59 authority definitions ...................................... 33
commissioning testing error messages ............................................ 34
personnel ..................................................... 19 password...................................................... 33
complete power break procedure..................................................... 33
after testing .................................................. 53 floor structures
expected results........................................... 53 material of .................................................... 14
fuse panel alarm .............................................. 47 resetting for start-up..................................... 96
H P
hardware peripheral devices
inspecting the functioning of ........................ 21 changing states of........................................ 37
typical faults and checks .............................. 37
power
I checking of................................................... 15
I/O devices power breaks
checklist of numbers and states................... 35 testing recovery............................................ 52
I/O outputs ....................................................... 35 power supply alarm ......................................... 47
installation processor units
checking of................................................... 15 test procedure .............................................. 39
interchangeability
of cartridges and plug-in units...................... 21 R
RCVHAN MML ................................................ 32
L real time........................................................... 65
LAN switch....................................................... 43 recovery service terminal................................. 33
line printers (LPTs) reporting
connection figure.......................................... 26 faults ............................................................ 14
connection of................................................ 26 resistance
table of settings............................................ 28 checking of................................................... 26
M S
simulating inputs in the ET2E .......................... 59
magneto optical disk........................................ 35
software versions
maintenance system
verification of................................................ 34
example outputs........................................... 45
spare units
inspection of................................................. 45
performing diagnostics to............................. 58
inspection prerequisites ............................... 45
start-up
master time...................................................... 65
monitoring the start-up of CM ...................... 99
MBIF units
monitoring the start-up of OMU.................... 96
verifying condition of .................................... 40
monitoring the start-up of other
message bus (MB)
computers ................................................ 102
checking message contents of..................... 41
monitoring the start-up of the system......... 104
table of addresses........................................ 41
order of......................................................... 32
verification of................................................ 39
starting the software and loading the files........ 93
MO91............................................................... 35
state transitions
testing procedure ......................................... 54
N supervision functions
network time protocol ...................................... 65 inspection of................................................. 45
supply voltage
measurement of ........................................... 26
O system
Operation and Maintenance unit (OMU) resetting for start-up................................... 104
T connection figure.......................................... 26
connection of................................................ 26
test logs table of settings............................................ 27
reference numbering.................................... 67
W
U wired alarms
unit diagnostics list of alarms to be tested ............................. 46
testing procedure ......................................... 54 preparations ................................................. 46
username of the system .................................. 33 testing procedures ....................................... 47
V
visual display units (VDUs)

Eads Tetra System Release 5.5: Commissioning The Dxtip and Dxttip

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Eads Tetra System Release 5.5: Commissioning The Dxtip and Dxttip

Uploaded by

Copyright:

Available Formats

Commissioning the DXTip and DXTTip

EADS TETRA System Release 5.5

Copyright © 2014–2015 Airbus DS SAS, all rights reserved.

DN0575507-04en EADS TETRA System Release 5.5

1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Instructions before starting the commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4 Inspection of hardware functioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5 Inspections of the software, I/O system and start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

EADS TETRA System Release 5.5 DN0575507-04en

6 Inspection of the maintenance system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7 Inspection of clock synchronisation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

DN0575507-04en EADS TETRA System Release 5.5

A Execution instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . .......................... . . . . 91

EADS TETRA System Release 5.5 DN0575507-04en

DN0575507-04en EADS TETRA System Release 5.5

EADS TETRA System Release 5.5 DN0575507-04en

DN0575507-04en EADS TETRA System Release 5.5

VERSION DATE COMMENTS CHAPTER

1. Time Management in EADS TETRA System, dn0484132

2. Installing the DXTip and DXTTip, dn063063

3. DXTip and DXTTip Jumper Settings, dn04167806

4. Cabling Instructions for the DXTip and DXTTip, dn04167833

5. DXTip and DXTTip Equipment List, dn04169197

6. PCM Links in DXTip and DXTTip, dn0498139

7. RCBUGG User's Manual, dn9774569

8. Integrated LAN Administration, dn0423824

9. DXT Alarm Reference Manual

10. DXT Command Reference Manual

11. Glossary, dn00126469

EADS TETRA System Release 5.5 DN0575507-04en

DN0575507-04en EADS TETRA System Release 5.5

How to use this document

This manual provides the following information:

EADS TETRA System Release 5.5 DN0575507-04en

• Appendix A lists example printouts of the start-up procedures of the exchange.

An Index is provided at the end of this document.

DN0575507-04en EADS TETRA System Release 5.5

• Section 2.1 Safety instructions

• Section 2.2 Fault reporting

• Section 2.3 Measurement devices and tools

• Section 2.5 General prerequisites

2.1 Safety instructions

An electrostatic sensitive device is an electronic component that may be permanently damaged by

EADS TETRA System Release 5.5 DN0575507-04en

Electrostatic sensitive devices are labelled as follows:

Figure 1 : Sign for electrostatic sensitive devices

2.2 Fault reporting

2.3 Measurement devices and tools

DN0575507-04en EADS TETRA System Release 5.5

2.4 Visual checks

2.4.1 General site inspection

2.4.2 Installation checks

EADS TETRA System Release 5.5 DN0575507-04en

• The power cables are correctly terminated.

• The power cords of the equipment are connected to a grounded outlet.

Cables and connections

• Cables are correctly terminated.

• Connection of cables is secure.

• Cables are properly routed and clamped.

Cabinets and units

• The DXT(T)ip and the units have suffered no physical damage.

• Units are correctly jumpered and seated in the DXT(T)ip cabinets.