Sted User Manual

User Manual
MT 653610108-A0-GB Ed.2.5 stedPC
User Manual
stedPC
Document Code: MT 653610108-A0-GB

Edition: 2.5
Date: Oct,20 2010
© SELTA S.P.A. All right reserved. Passing on and copying of this document, use and communication of its contents forbidden without authorization.
written authorization.
1 / 91
User Manual
stedPC MT 653610108-A0-GB Ed.2.5
Edition change Date

1.0 First Issue Dec,02 2004
2.0 First Review Mar,05 2007
2.1 Added chap.10, changed par. 5.6.5 and 5.6.6. Added Mar,28 2007
parameter Enhanced Modulation in par. 6.1.1.
2.2 Added Fig. 5.7, 8.5, added section 4.4, expanded sec- 11-Feb-2008
tion 10.2. In par. 6.1.1 removed parameters ’Modula-
tion’ and ’Dce Type’. Added par.5.5.2, modified para-
graph 5.6.6. Changed Tab. 5.16 and 6.1. Added chap-
ter 12.
2.3 Added TPU-BF card, added chapter 11. Oct,13 2008
2.4 Moved the section 4.4, updated tab.5.17. Added the May,20 2009
parameter ’Card Attenuation’ to Tab. 6.1.
2.5 Updated Table 9.1. Changed paragraphs 5.6.6, 6.1.1, Oct,20 2010
10.2, 5.6.3, 5.6.6 and 6.1.3. Added LFU card, sec.6.1.2
and sec.9.4.
© SELTA S.p.A. All right reserved. Passing on and copying of this document, use and communication of its contents non permitted without
2 / 91
User Manual
Contents
1 Introduction 17
1.1 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.1.1 CheckBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.1.2 ComboBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.1.3 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.1.4 Radio button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.1.5 ListBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.1.6 Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.1.7 Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.2 Graphic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3 Textual Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2 Introduction 21
2.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3 System Description 23
3.1 Remind about STED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.2 Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4 Quick Start 25
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.2 Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.3 STED Setup from HyperTerminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.4 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.4.1 IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4.2 Routing Table of STED1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4.3 Routing Table of STED2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.4.4 Routing Table of PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.5 stedPC Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.5.1 Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.5.2 Modem Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.5.3 Smux Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.6 Off-Line configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5 Management of HW resources 31
5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2 Equipment Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.1 STED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.2 Board Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.2.3 Port Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.3 Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.3.1 Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.4 Status Informations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.5 Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
CONTENTS 3 / 91
User Manual
5.5.1 DPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.5.2 DPUv2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.5.3 CMU - 64Kb/s interface side . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.5.4 CMU - equipment side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.5.5 DIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.5.6 SIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.5.7 TPU-POF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.5.8 TPU-BF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.5.9 LFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.6 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.6.1 FXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.6.2 FXO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.6.3 E&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.6.4 DIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.6.5 IL64K line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.6.6 HV port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.6.7 TPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.6.8 Port Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6 System Management 45
6.1 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1.1 General Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1.2 Working mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.1.3 Bandwidth parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.1.4 Identification Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.1.5 Sync Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.1.6 Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.2 Firmware Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.2.2 FW Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.2.3 FW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.2.4 Possible download problems . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.2.5 FW database purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.2.6 Batch Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.3 System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7 Channels 55
7.1 Ports and Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2 Channel types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.1 Channels creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.2 Channel framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.2.3 ADPCM channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8 Connections 61
8.1 Connection types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.1.1 Bidirectional point to point . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.1.2 Bidirectional point to multipoint . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.2 Connection roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
9 Alarms 65
9.1 Active Alarms List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.1.1 Alarm Reminder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.1.2 Alarm Reminder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.1.3 Object Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
9.2 Alarms Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.3 Alarms Legenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4 / 91 CONTENTS
User Manual
9.3.1 Alarm Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

9.3.2 Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
9.3.3 Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
9.4 Local Event Log Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
10 On-Line Operations 71
10.1 Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
10.1.1 Tx Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
10.1.2 Line hybrid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
10.2 Performance measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
11 Local Event Log 75

11.1 Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
11.2 Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
11.3 eView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
11.3.1 View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
11.3.2 Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
11.3.3 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
11.4 eView Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
11.5 Standard Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
11.6 Advanced Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
12 Performance Measurements 81
12.1 Current Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.2 PM data upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.3 PM data view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.4 Reset counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.5 Interval size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
13 Usage of tty terminal 83

13.1 Useful Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
13.1.1 Viewing the UC status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
13.1.2 Change of IP Address of a STED port (ETH) . . . . . . . . . . . . . . . . . 84
13.1.3 Add an entry to the routing table . . . . . . . . . . . . . . . . . . . . . . . . 84
13.1.4 Remove an entry from the routing table . . . . . . . . . . . . . . . . . . . . 84
13.1.5 Viewing the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
13.1.6 Set date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
13.1.7 Download Firmware UC (Boot in flash) . . . . . . . . . . . . . . . . . . . . 85
13.1.8 Download Firmware UC (regime) . . . . . . . . . . . . . . . . . . . . . . . . 85
13.1.9 Download Firmware UP from Hyperterminal . . . . . . . . . . . . . . . . . 85
13.1.10 Erasing a FW from FLASH EPROM . . . . . . . . . . . . . . . . . . . . . . 85
13.1.11 Viewing status of an UP board . . . . . . . . . . . . . . . . . . . . . . . . . 85
13.1.12 Viewing id parameters of an UP board . . . . . . . . . . . . . . . . . . . . . 86
13.1.13 Viewing the status of an UP Port . . . . . . . . . . . . . . . . . . . . . . . . 86
13.2 Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
13.2.1 View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
13.2.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
14 Other Informations 87
14.1 Assistance through Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
CONTENTS 5 / 91
User Manual
Page intentionally left blank.
6 / 91 CONTENTS
User Manual
List of Figures
1.1 CheckBox and ComboBox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.2 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3 Radio button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.4 ListBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5 Two pages wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.6 Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1 Block diagram of STE-D. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2 Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.1 TCP/IP network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.2 Example of HyperTerminal connected to a STED. . . . . . . . . . . . . . . . . . . . 26
4.3 Operation Flow for provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4 Network sync source selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1 Board Creation (slot 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5.2 Status of a board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3 Creation of an FXS port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4 Port Parameter Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.5 Port Parameter Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.6 Local Loop 2b on CMU card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.7 Configuration dialog of HV port (DPU edition 1). . . . . . . . . . . . . . . . . . . . . 42
5.8 Loop 2b remote on DPU card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.9 Configuration dialog of HV port (DPUv2 or edition 2). . . . . . . . . . . . . . . . . . 43
5.10 Port Identifier set as ’p-1.1 ’. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1 Generic parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.2 Generic parameters (stedPC 1.6.0). . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.3 Mode Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.4 Actual Sync Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.5 FW import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.6 FW file selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.7 RN file selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.8 Selection of FW to be downloaded. . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.1 Relationship between ports and channels . . . . . . . . . . . . . . . . . . . . . . . 56

7.2 Show Group Command-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.3 Show Group Command-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.4 Channel creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.5 X.50d3 subchannels creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.6 ADPCM subchannel creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7.7 Envelopes selection for an ADPCM channel. . . . . . . . . . . . . . . . . . . . . . . 58
7.8 Envelopes used by just created channel (2,3,4,5,7,8). . . . . . . . . . . . . . . . . . 59
7.9 ADPCM channel in channels tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.1 Creating connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
LIST OF FIGURES 7 / 91
User Manual
8.2 Connections menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

8.3 Connection types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.4 Roles in the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.5 Connections view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
9.1 Active Alarms List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

9.2 Alarm Reporting on equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
9.3 Alarm Reminder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
9.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
9.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
10.1 Tx filter tuning indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

10.2 Insert the hypotetical connection attenuation. . . . . . . . . . . . . . . . . . . . . . 72
10.3 Values of 𝐴𝑓𝑡𝑜𝑡 and 𝐴𝑠𝑡 read from equipment. . . . . . . . . . . . . . . . . . . . . . 72
10.4 How to see Link Status on HV port. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
10.5 Window just opened (data are not yet valid). . . . . . . . . . . . . . . . . . . . . . . 73
10.6 Window with valid values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
11.1 Logic architecture of the Event Log feature. . . . . . . . . . . . . . . . . . . . . . . 75

11.2 How to upload events from stedPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
11.3 eView main window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
11.4 Standard filter by severity or system name. . . . . . . . . . . . . . . . . . . . . . . . 79
11.5 Where to read system name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
11.6 Standard filter by alarm type or alarm text. . . . . . . . . . . . . . . . . . . . . . . . 80
11.7 Standard filter by date / time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
12.1 View of current values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

12.2 Performance data example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
14.1 Activation of Connection to teamviewer.com. . . . . . . . . . . . . . . . . . . . . . . 87

14.2 Connection activated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8 / 91 LIST OF FIGURES
User Manual
List of Tables
2.1 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.2 Supported Operating systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.1 Possible management interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.2 IP addresses of sample network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.3 Sync source configuration sample. . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.1 Compatibility list card/slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.2 Hardware code list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.3 Led of card DPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.4 Led of card DPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.5 Led of card CMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.6 Led of card CMU card - equipments side. . . . . . . . . . . . . . . . . . . . . . . . . 36
5.7 Led of card DIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.8 Led of card SIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.9 Led of card TPU-POF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.10 Led of card TPU-BF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.11 Led of card LFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.12 Parameters of port FXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.13 Parameters of port FXO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.14 Parameters of port E&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.15 Parameters of port DIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.16 Parameters of port IL64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.17 Parameters of port HV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.19 Parameters of port TPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.1 System generic parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6.2 Interface Type possible values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.3 Bit rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.4 Identification parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.5 Sample of OH Intel record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.6 Sample of Motorola S19 record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.7 Sample of Selta Release Notes file . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.8 Possible failure reasons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
9.1 Probable Cause List of STED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

9.2 Legenda about STED objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
9.3 Alarm severity legenda. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
9.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
10.1 Link status parameters description. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
11.1 Field list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
13.1 Serial port settings for Hyperterminal . . . . . . . . . . . . . . . . . . . . . . . . . . 83
LIST OF TABLES 9 / 91
User Manual
10 / 91 LIST OF TABLES
User Manual
Bibliography
[1] Internet site teamviewer. http://www.teamviewer.com.

[2] Selta spa. STED - Equipment Technical Description - 720011088-A0-EN, 2006.
[3] Selta spa. SNMS - Manuale Utente - MT 653600106-B1-IT, 1.3 edition, 2008.
[4] Selta spa. STED - Installation Manual - MI-GB 620204040 Ed.5, 2008.
[5] Selta spa. STED - Technical General Description - 620204040-A0-EN Ed.6, 2008.
BIBLIOGRAPHY 11 / 91
User Manual
12 / 91 BIBLIOGRAPHY
User Manual
Glossary
CMU
Control and Management Unit.
DIU
Data Interface Unit.
DNS
Domain Name System.
DPLC
Digital Power Line Carrier description
DPU
Digital Processing Unit.
DPU
Line Interface.
E1
E1 is the European format for digital transmission. E1 carries signals at 2 Mbps (32 channels
at 64Kbps, with 2 channels reserved for signaling and control).
EOC
Embedded Operation Channel.
Ethernet
Ethernet is standardized as IEEE 802.3. Ethernet is the most common implemented LAN
standard. Supports data transfer rates of Mpbs, where 10, 100 or 1000 Mbps is supported.
GUI
Graphical User Interface.
gzip
Gnu ZIP. Open source tool to compress files.
HTTP
HyperText Transport Protocol. Transmits HTML documents between servers and clients on
an IP network (i.e. the internet).
HV
High Voltage.
Glossary 13 / 91
User Manual
ICMP
Internet Control Message Protocol. Allows gateway or destination host to communicate with
a source host, for example, to report a processing error.
IETF
Internet Engineering Task Force (www.ietf.org).
IL
Line Interface.
IP
Internet Protocol. Specifies the format of packets and the addressing method.
IP Address
Internet Protocol Address. A unique address assigned to any interface of a Network Element
belonging to a layer 3 IP network.
LAN
Local Area Network. A network contained within a single room, building, campus or other
limited geographical area.
MAC Address
Media Access Control Address. The MAC Address is a hardware specific address that iden-
tifies each network node.
PAU
Power Amplifier Unit.
Ping
Packet Internet Network Groper. Verifies if a specific IP address is available. A packet is sent
to another IP address and waits for a reply. This utility is essentially a System Administrator
tool used to verify if network connections are intact. PING uses the Internet Control Message
Protocol (ICMP) Echo function.
PLC
Power Line Carrier description
PSU
Power Supply Unit.
Router
A module that connects two or more separate networks. Routers forward packets between
two or more networks. Routers operate at a Layer 3 level.
SIU
Speech Interface Unit.
SNMP
Simple Network Management Protocol. SNMP based software communicates with Network
Elements with embedded SNMP agents. SNMP agents gather network activity and NE status
information, and send the information back to a workstation.
14 / 91 Glossary
User Manual
SQL
Structured Query Language, language used for the retrieval and management of data in
relational database management systems (RDBMS).
Subnet
Sub-network. Subnets are portions of a network that share a common address component.
On TCP/IP networks, Ethernet switch modules that share a prefix are part of the same sub-
net.
Subnet Mask
Used to mask all or part of an IP address used in a subnet address.
Switch
A module that connects two or more LAN segments. Switches support any packet protocol
type.
tar
Tape ARchive. Tool and format for enclosing a group of files into a single file.
TCP
TCP is one of the main protocols in TCP/IP networks. Whereas the IP protocol deals only
with packets, TCP enables two hosts to establish a connection and exchange streams of
data. TCP guarantees delivery of data and also guarantees that packets will be delivered in
the same order in which they were sent.
TCP/IP
Group of protocols that enables two hosts to communicate and exchange data streams. Main
protocols are IP, UDP and TCP.
TFTP
Trivial File Transfer Protocol. Uses UDP without security features to transfer files.
TPU
TeleProtection Unit.
TRAP
For SNMP protocol, the spontaneous messages are called traps.
UDP
A connectionless protocol that, like TCP, runs on top of IP networks. Unlike TCP, UDP
provides very few error recovery services, offering instead a direct way to send and receive
datagrams over an IP network. It’s used primarily for broadcasting messages over a network.
Glossary 15 / 91
User Manual
16 / 91 Glossary
User Manual
1. Introduction
1.1 Conventions
For customers not familiar with Windows terminology, follows some examples of possible controls.
1.1.1 CheckBox
It selects one or more options from a list (see Figure 1.1(a)).
(a) —WinCheckBox (b) ComboBox
Figure 1.1: CheckBox and ComboBox.
1.1.2 ComboBox
It selects a single option from a list (see Figure 1.1(b)).
1.1.3 Menu
It allows to introduce a command with the rigth key of the mouse.
See an example in Figure 1.2.
Figure 1.2: Menu
1.1.4 Radio button

It allows to select single choice between N (see Figure 1.3).
CHAPTER 1. INTRODUCTION 17 / 91
User Manual
Figure 1.3: Radio button
1.1.5 ListBox
It allows to select one or more option from a list (Figure 1.4).
Figure 1.4: ListBox
1.1.6 Wizard
Procedure for a step-by-step data insertion (Figure 1.5).

The user must fill forms in a sequence and move forward and backward.
(a) step 1 (b) step 2
Figure 1.5: Two pages wizard.
18 / 91 CHAPTER 1. INTRODUCTION
User Manual
1.1.7 Context Menu

Pointing mouse on an object (slot, connector etc..) and clicking with right key of mouse a context
menu will opened with commands related to pointed object (Figure 1.6).
Figure 1.6: Context Menu
1.2 Graphic Conventions

Near the text could be present some icons, to indicate that the text is particularly relevant for some
topic, see the following table for key.
Suggestion for the user.
This section requires particular attention.
The text describes a procedure potentially dangerous.
Text describes a procedure where the user is requested to
take a note about some data.
Reference to external manuals, books or similar.
Text describes a procedure for which is required a software
package (i.e. an installation CD etc.).
Text describes a procedure for which additional hardware
is required.
1.3 Textual Conventions

Following conventions are used when describing textual commands (if any):
AaBbCc123 system output.
AaBbCc123 command typed by the user.
AaBbCc123 Variables to be substituted by real values.
<parameter> single mandatory parameter.
{par1∣par2∣par3} a parameter choosen between par1, par2 and par3 (mutually exclusives).
[parameter] optional parameter.
enter press the key ’enter’.
b step where data input could be required.
User Manual
User Manual
2. Introduction
2.1 System Requirements

Minimum and suggested System requirements are described in table 2.1.
Table 2.1: System requirements

min suggested
Processor PII-133 PII-233
RAM (MB) 32 64
Disk space (MB) 10 15
Video adapter 800x600, 256 col. 1024x768, 65536 col.
2.2 Supported Operating Systems
Table 2.2: Supported Operating systems.

Operating system supported
Windows XP Home ✓
Windows XP Professional ✓
Microsoft® Windows Vista Business™ ✓(1)
Microsoft® Windows 7™ -
✓ = supported.
- = non supported.
(1) = from version 1.4.0.
User Manual
User Manual
3. System Description
Present document gives basic information about management architecture of STED equipments.
Management functions are done via SNMP protocol (using UDP transport over Ethernet or SLIP).
For file transfer the TFTP protocol is used. Use of TCP/IP allows to use any kind of IP connection:
Internet, any company LAN etc.
3.1 Remind about STED

STED system is a power line carrier terminal for Digital Transmission of data and compressed
speech on High Voltage lines (H.V.). This equipment can be divided in three functional sections,
how you can see in figure 3.1.
Figure 3.1: Block diagram of STE-D.
3.2 Operating Modes

The stedPC system may work On Line and Off Line:
in the first case, at startup, the set of STED SNMP variables is loaded in RAM (’upload’ operation)
and a user-friendly view is presented to the user.
User may change the configuration and/or save it to a file.
When Off Line, the configuration DB may be blank or fetched from a file, the user may save it
again on a file or send it to the STED (the IP Address is given). Following flowchart depicts what
described above.
CHAPTER 3. SYSTEM DESCRIPTION 23 / 91

User Manual
Figure 3.2: Operating Modes
24 / 91 CHAPTER 3. SYSTEM DESCRIPTION

User Manual
4. Quick Start
4.1 Introduction
Present section provides a minimal quick start page to get up and running a network of STED
nodes, in the hipothesis that stedPC product is already installed.
For detailed description, please see specific chapters.
The example network has 2 STED (see Fig.4.1).
Figure 4.1: TCP/IP network.
4.2 Management Interfaces

STED has 3 management interfaces (see Tab.4.1): 2 of them are directly accessible and one is
embedded in the transmission medium. Those 3 interfaces supports TCP/IP: each one has its
Table 4.1: Possible management interfaces.

Acronym Description Position
LT Local Terminal RJ-45 (8 contacts, female) connector on the front
of CMU card, labelled with ’PC’. Supports TCP/IP
(SLIP) and ASCII terminal interfaces (in alternative).
EOC Embedded Opera- It uses some free bits on the HV vector.
tion Channel
ETH Ethernet 10BaseT Ethernet port (labelled with ’Eth’) on card CMU card.
(IEEE 802.3)
CHAPTER 4. QUICK START 25 / 91

User Manual
own IP Address and STED has a static routing table.

LT port supports an ASCII interface (to be used with HyperTerminal) necessary to change IP ad-
dresses or routing table entries.
4.3 STED Setup from HyperTerminal

Some parameters are needed for communication with stedPC, hence they must be set with the
terminal (see an example in Figure 4.2).
Figure 4.2: Example of HyperTerminal connected to a STED.
4.4 Operations
Fig. 4.3 describes a schematic flow for provisioning. Some operations are optional. Follows a
description of each single step.
1.1 IP addressing is required for management, if you plan to manage STE-D through a network
you must plan carefully IP and routing. See details in chapters 4.3 and 13.
2.1 This step is mandatory and fixes fundamental parameters such as station role (Master or
Slave). Details are in the chapter 6.1.1.
2.2 This step is necessary if you plan to use SMUX section. Details in section 5.1.
2.3 Mandatory step for enabling transmission on High Voltage line (details in sections 5.6.6, 5.6.5
and 4.5.1).
3.1 Operation on stedPC side is described in section 10.1, details on the procedure are in [4].
4.1 Optional step if you use the SMUX section, see details in chapter 5.6 (ports FXS, FXO etc.).
4.2 Like point 4.1, see details in chapter 8.
26 / 91 CHAPTER 4. QUICK START

User Manual
Figure 4.3: Operation Flow for provisioning.
4.4.1 IP Addresses
First of all, is necessary to configure the IP addresses of management interfaces and routing table
of STED. Table 4.2 gives IP addresses of nodes of example network.
Also the PC is part of the network, please note that it doesn’t need the peer address.
The asterisk in the column ’Default Gateway’ means that this interface is used to reach nodes not
peer of the STED interfaces.
Table 4.2: IP addresses of sample network.

Node IP Address / peer Default gateway
PC connected with ETH 10.13.1.2/255.255.255.0 -
interface
STED 1 (ETH) 10.13.1.55/255.255.255.0 *
STED 2 (ETH) 10.0.2.244/255.255.255.0 -
STED 1 (EOC) 192.168.12.1/192.168.12.254 -
STED 2 (EOC) 192.168.12.2/192.168.12.254 *
4.4.2 Routing Table of STED1

It’s the only node connected to PC and the only thing it needs is the addition of a route on how to
reach nodes of network 192.168.12.x. The command is:
CFG>route add 192.168.12.0 MASK 255.255.255.0 192.168.12.254

User Manual
4.4.3 Routing Table of STED2

The key information is the gateway used to reach the PC (the EOC interface of STED Gateway).
The command is:
CFG>route add 10.13.1.2 192.168.12.254
The routing table should look as follows:
Network Address Netmask Gateway Address Interface

0.0.0.0 0.0.0.0 192.168.12.254 2
127.0.0.1 127.0.0.1 127.0.0.1 6
192.168.12.254 0.0.0.0 192.168.12.1 3
4.4.4 Routing Table of PC

The PC needs to know that network 192.168.12 is ’seen’ through interface 192.168.11.253.
Below there is a fragment of routing table (normally a PC is also inserted in a company LAN, hence
there are a lot of other entries and default gateway - the 0.0.0.0 entry - is often used for Internet
Access).
Network Address Netmask Gateway Address Interface Metric

0.0.0.0 0.0.0.0 ....... ..
.................... ..
192.168.12.0 255.255.255.0 10.13.0.55 10.13.0.2 1

This route must be explicitly added from a DOS window with the command:
C:\>route add -p 192.168.12.0 MASK 255.255.255.0 10.13.1.55
Figure 4.4: Network sync source selection.

User Manual
4.5 stedPC Setup

4.5.1 Synchronization
For synchronization feature there is an ad-hoc command (”System - Select External Sync Src”)
that allows to (see picture above):
1. Select the sync strategy (free running, from network, from an external source not part of the
network).
2. If strategy is ’From Network’, is necessary to specify which interfaces can be selected and
their priorities (from the top in window ’selected sources’).
3. Selectable sources are both ports of type DF64.

4. If strategy is Free Running or External, controls for source selection are disabled.
Table 4.3: Sync source configuration sample.

Node ’Sync Source’ variable Interface providing sync
STED 1 Free Running -
STED 2 From Network DF64 (IL64K) card=7, port=2
In case of analog working mode, the sync mode can be only ’Free Running’.
4.5.2 Modem Section

This section includes parameters related to how to transmit data on the HV (High Voltage) section.
Part of the settings are in the ’Generic Parameters’ section ( Menu System → Edit System
Generic Parameters , details in section 6.1.1) and part are in the settings of DPU port (section
5.6.6). This last chapter contains fundamental parameters like Output Power and Tx/Rx Frequen-
cies.
4.5.3 Smux Section

After enabling the HV section, a D64 channel is available to the user. The user can enable the
IL64k port integrated in CMU (port 1.6.1 see details in sec. 5.6.5) to transport a whole 64 Kb/sec
channel or enable speech/data ports (FXS, FXO, DIU etc.) and connect them with subchannels
created below HV port.
4.6 Off-Line configuration

It is possible to transfer a whole configuration to a STE-D. First of all, it’s necessary to cleanup the
new CMU, from Hyperterminal do the following:
NRML> startcfg
CFG> erasecfg
CFG> write
CFG> ...
Then it’s necessary to program the new IP addresses and routing table entries.
CFG> stedafnaddress eoc 192.168.12.1 192.168.12.2
CFG> stedafnaddress eth 10.13.0.100 255.255.255.0
CFG> route del 0.0.0.0 mask 0.0.0.0 192.168.11.254
CFG> route add 0.0.0.0 mask 0.0.0.0 Router
CFG> localportmode terminal

User Manual
CFG> write
CFG> stedaddress eoc 192.168.12.2 192.168.12.1
CFG> stedaddress eth 10.0.2.244 255.255.255.0
CFG> route add 0.0.0.0 mask 0.0.0.0 192.168.12.2 CFG> localportmode terminal
CFG> write
Then:
• on stedPC open a configuration from file.
• menu Configuration-On Line Actions opens a dialog, insert the correct name or IP address,
check the connection with the ’Test’ button and download the configuration with the ’Down-
load’ command.

User Manual
5. Management of HW resources
5.1 Introduction
The present document gives some basic information about equipments of STED family. For details,
please check [2].
5.2 Equipment Management

Follows a reminder on HW information (rack types etc.)
5.2.1 STED
Table 5.1: Compatibility list card/slot.

Slot Possible cards
1 DIU, SIU, LFU
2 DIU, SIU
3 DIU, SIU
4 DIU, SIU
5 DIU, SIU, TPU
6 CMU / IL64K
7 DPU
8 RXF
9 TXF
10 PAU
11 PAU
12 PSU
Board Numbering
STE-D rack has 12 slot, table 5.1 shows the possibilities. Peripheral units can be created or deleted
(slots from 1 to 4). The operation can be carried out only if the control of the equipment has been
taken. Figure 5.1 shows a demo window for the board creation on the slot 1 (notice that control
key is disabled).
CHAPTER 5. MANAGEMENT OF HW RESOURCES 31 / 91

User Manual
Figure 5.1: Board Creation (slot 1)
5.2.2 Board Status

It’s possible to know the operational state of a board simply selecting it and give the command
Right Mouse Status . The output is a set of status bits with their own LED indicator. For status
bits indicating an alarm, the LED is Red, for bits indicating ’normal behaviour’ the LED is Green
(see Fig.5.2).
Figure 5.2: Status of a board
32 / 91 CHAPTER 5. MANAGEMENT OF HW RESOURCES

User Manual
5.2.3 Port Creation

The creation of a board makes available phisical resources (ports) that are disabled at the be-
ginning. When this operation is done, if the creation is succesfully completed, a related logical
resource is created: the channel. The figure 5.3 shows the parameters set that are listed one for
each line together their value and the access indicator, in this case:
• The label ’rw’ at the left indicates that parameters are read/write
• All variables are followed by a suffix, for instance ’1.6.1’ means rack=1, board=6, port=1.
• The button ’...’ allows the user to modify the parameter value
Figure 5.3: Creation of an FXS port
Clicking on the button ’...’ opens a new window that apears different depending on the variable
type. That window permits to modify the variable, and to access the documentation from the
’DESCRIPTION’ of MIB (button ’Help’) or to exit (’Cancel’ button).
Figure 5.4: Port Parameter Edit

User Manual
Figure 5.5: Port Parameter Help
5.3 Code List

5.3.1 Boards
Table 5.2: Hardware code list.

Board Acronym Selta Code Description
DPU DPU 643304005-A0-IT Digital Processing Unit
DPUv2 DPUv2 643304009-A0-IT Digital Processing Unit version 2
CMU CMU 640904005-A0-IT Control Management Unit
TXF TXF 641384201-A0-IT Transmission Filter
RXF RXF 640404008-A0-IT Reception Filter
SIU SIU 640704005-A0-IT Speech Interface Unit
DIU DIU 640704006-A0-IT Data Interface Unit
UAP UAP 642204002 Power Amplifier Unit
PSU PSU 645134105 DC/DC 85W, 100W Converter
TPU TPU 640704007-A0-IT Teleprotection Interface Unit
TPU-BF TPU-BF 640704008-A0-IT Analog Teleprotection Interface Unit
LFU LFU 640075010-A0-IT Analog Interface Unit (Low Frequency
Unit)
5.4 Status Informations

Each board has status informations, shown in a graphic panel with LED indicators, accessible with
the command Right Mouse Status on selected board. Les informations sont:
• regimeRunning: led on (green) tells that regime FW is running.
• hardwareFault: led on (red) indicates the presence of an HW fault.

• badRegime: led on (red) indicates that a bad FW regime.
• badConfigCRC: led on (red) indicates that the configuration has a wrong CRC.
• missingConfig: led on (red) indicates that configuration is missing.

User Manual
• missingRegime: led on (red) indicates that FW regime is missing.
• upAlarm: led on (red) indicates the presence of a generic alarm.

• Board not Present: led on (red) indicates that the board is not present or it does not answers
(i.e. in Watchdog).
5.5 Boards
Follows a brief description of boards (LED on frontplate, ports etc.) and ports (configuration pa-
rameters and alarms, if any). Board with *(n) has the indicated LED for each port and n is the
number of that ports.
If not differently indicated, the terms port and interface are equivalent.
5.5.1 DPU
Table 5.3: Led of card DPU

LED Color Description
LINE Green On: HF link running
Blinking: HF link starting
IND Yellow Off: equipment active
Blinking: local or remote loop active
On: remote terminal alarm
WD Red On: DPU damaged (serious failure)
5.5.2 DPUv2
Table 5.4: Led of card DPU

LINE Green On: HF link running
Blinking: HF link starting
IND Yellow Off: equipment active
Blinking: local or remote loop active
On: remote terminal alarm
WD Red On: DPU damaged (serious failure)
5.5.3 CMU - 64Kb/s interface side
Table 5.5: Led of card CMU

FAIL Red On: 64 Kb/s interface serious failure
RTS Green On: V11 interface active
MIR / LOS Red On: loss of signals received on the 64 Kb/s
interface

User Manual
5.5.4 CMU - equipment side
Table 5.6: Led of card CMU card - equipments side.

URG Red On: OR of the equipment urgent alarms (loss
of service)
IND Yellow On: OR of the equipment indicative alarms
LOC AL Red On: OR of all the equipment alarms
READY Green Slow blinking: board up and running Fast
blinking: download in progress
WD Red On: processor in Watch Dog
5.5.5 DIU
Table 5.7: Led of card DIU

CTS-x *(5) Green On: presence of C106 interface criterion
(Clear To Send)
DCD-x *(5) Yellow On: presence of C109 interface criterion
(Data Carry Detected)
AL-x *(5) Red On: channel x failure
’x’ is the port identifier (A .. E).
5.5.6 SIU
Table 5.8: Led of card SIU

CH1 Green On: speech channel 1 confogured and active
CH2 Green On: speech channel 2 confogured and active
WD Red On: board failure
5.5.7 TPU-POF
Table 5.9: Led of card TPU-POF

READY Green card up and running
LOS Red LOS alarm present
WD Red Card in watchdog mode
The TPU-POF can be created only in slot 5.

Contains a port of type TPU.
5.5.8 TPU-BF

User Manual
Table 5.10: Led of card TPU-BF

LOS Red LOS alarm present
The TPU-BF can be created only in slot 5.

Contains a port of type TPU.
5.5.9 LFU
Table 5.11: Led of card LFU

The LFU can be created only in slot 1.

Contains a port of type LFU (without parameters).
5.6 Ports
5.6.1 FXS
Table 5.12: Parameters of port FXS

Parameter ReadOnly Description
Tx Level - Transmission level, range: 0dB .. 2dB, de-
fault: 0dB
Rx Level - Receiving level, range: -8dB .. 0dB, default:
-8dB
Connected to - This variable must be true if on the other side
another FXS of the connection there is another FXS inter-
face
A FXS port has associated a G.729 channel.
5.6.2 FXO
Table 5.13: Parameters of port FXO

Tx Level - Transmission level, range: -7dB .. +4.5dB,
default: 0dB
Rx Level - Receiving level, range: -10dB .. +1.5dB, de-
fault: -2dB
A FXO port has associated a G.729 channel.

User Manual
5.6.3 E&M
Table 5.14: Parameters of port E&M

Tx Level - Transmission level, range: -8dB..+7.5dB (def:
0dB) for 2 wires interface, -14dB..+1.5dB (def:
0dB) for 4 wires interface
Rx Level - Receiving level, range: -11.5dB..+4dB (def: -
2dB) for both interfaces
Interface Type - Type of interface (2/4 wires)
ADPCM en- - true, false
abled (1)
Compression - G.729, ADPCM16, ADPCM24, ADPCM32,
(2) ADPCM40
E1 - Type of signaling
E2 - Type of signaling
M1 - Type of signaling
M2 - Type of signaling
An E&M port has associated a G.729 or ADPCM channel.

(1) required stedPC 1.6.x, FW CMU x.x.x and FW DPU x.x.x.
(2) G.729 if ADPCM enabled = false.

User Manual
5.6.4 DIU
Table 5.15: Parameters of port DIU

Bit Rate ✓ Speed of the channel
Data Format - Data format (included start and parity) - Possible op-
tions:
∙ 8 bit
∙ 9 bit
∙ 10 bit
∙ 11 bit
Flags - Channel DCE (DBV) operation options:
∙ Async
∙ C105 forced
∙ C108 forced
∙ C140 forced
∙ Net Out of Service Detection
∙ V.14 Extended
Antistreaming - Transmission time out (in seconds); it is related to
the device which transmits by DIU card. If it is set
on 0, it is disabled
A DIU port has associated a DCE (DBV) channel.

User Manual
5.6.5 IL64K line interface

It’s the port with fixed coordinates 1.6.1, it is named also ’Network Port’ because it is normally
connected to a network element such an external router. This port is integrated in CMU card.
Table 5.16: Parameters of port IL64

Interface Type - Interface type: { ITU-T G.703 ∣ RS422 - ITU-
(2) T V.11 ∣ Internal G.703 (1) ∣ Ethernet - IEEE
802.3 - Routing ∣ Ethernet - IEEE 802.3 -
Bridging }
The V.11 is allowed only when flag ’Framed’
of parameter ’STED System Flags’ is
unchecked see par.6.1.1
Loop - It makes active the local loop (L2b, Fig-
ure 5.6).
Port State ✓ Possible port alarms:
Hardware Alarm
Missing Firmware
Bad Configuration.
Line Alarms ✓ Line alarms of the channel (active only with
G.703 interface):
LOS (lost of signal)
AIS (Alarm Indicator Signal)
LOF (lost of frame; it is present only in case
of ITU-T X.50 division 3 frame)
RAI (Remote Alarm Indicator; it is present
only in case of ITU-T X.50 division 3 frame)
NETWORK (network alarm)
Slip (synchronism skew).
Equipment ✓ Equipment alarm:
Alarm MIT (loss of transmission impulse).
(1) Internal G.703 means that the port 1.6.1 is not available to the user.
(2) In case of analog mode, the only possibility is ’Internal G.703’.
Referring to Figure 5.6, the loop is related to the 1.6.1 (IL64k line interface) of the B system, con-
nected with the user terminal. It is necessary to configure the CMU card on the local equipment.
5.6.6 HV port
HV means ’High Voltage’, this port is named also ’Modem Port’, it has fixed coordinates 1.7.1 and
resides on DPU card.
Referring to Figure 5.8, the loop is related to the IL64k port (1.6.1) of the ’A’ system.
The stedPC is connected with the ’B’ equipment; it is necessary to configure the DPU card so that
it sends to ’A’ the remote loop command.

User Manual
Figure 5.6: Local Loop 2b on CMU card.
Table 5.17: Parameters of port HV

Output power (1) - 40W if two power amplifiers have been in-
serted 2W, 20W or 10W if only one power
amplifier has been inserted.
Output power (DPU V2) - Output power, expressed in dBm and in W.
(2)
Interface Type - LineHybrid or Line Repeater, see also [4].
Rx Gain (DPU V2) (2) - Rx gain (in dB).
Tx Band (3) - Transmission band.
Rx Band (3) - Reception band
L2b remote loop - It makes active the L2b remote loop (Fig-
ure 5.8)
BER threshold - BER threshold; if exceeded, the link breaks
down
(1) only on DPU ed.1.

(2) only on DPU ed.2.
(3) with FW DPU 4.1.0, FW CMU 2.1.0 e stedPC 1.5.0 (variant 653610108-A1-xx) it’s possible to
have 1 kHz steps.

User Manual
Figure 5.7: Configuration dialog of HV port (DPU edition 1).
Figure 5.8: Loop 2b remote on DPU card.

User Manual
Figure 5.9: Configuration dialog of HV port (DPUv2 or edition 2).
Table 5.18:
Variant Range Step
Standard 40 .. 500 KHz 4 KHz
Special applications (1) 40 .. 500 KHz 1 KHz
Special applications (2) 40 .. 1000 KHz 1 KHz
(1) Works on DPUv1 and DPUv2, requires stedPC (653610108-A0-GB) 1.6.0 or newer plus FW
CMU 2.1.1 and FW DPU 4.1.0.
(2) Requires DPUv3.
5.6.7 TPU
Table 5.19: Parameters of port TPU

TPU Address - Address of connected TPS-NU. This parame-
ters is useful to prevent cabling errors.
5.6.8 Port Id
There is the possibility of assigning a label (8 characters) to each port. The text is free, a possible
convention could be the following:
• for the user (tributary) ports: an identifier of the equipment connected to STED
• for network (aggregate) ports: an identifier of the cable connecting 2 STED
with this convention, a Network management system could put all informations together and un-
derstand which STED are connected one each other.

User Manual
Figure 5.10: Port Identifier set as ’p-1.1 ’.

User Manual
6. System Management
6.1 Parameters
6.1.1 General Parameters
With menu command ’System → Edit System Generic Parameters’ a dialog for setting system
generic parameters is opened (see Fig.6.1 and 6.2). Parameters are listed in Tab.6.1.
Table 6.1: System generic parameters.

Parameter Description
Mode of LT port Working mode of LT port, following options are allowed:
∙ Always SLIP: only TCP/IP protocol over SLIP (hence communicates
with stedPC).
∙ Always Terminal: only serial communication with Hyperterminal.
∙ Terminal / back to SLIP at next reboot: at next reboot will support
terminal interface then at next reboot TCP/IP will be supported, this
option may be useful when the user wants to change some parame-
ters from Hyperterminal (i.e. IP Address of a port) and back to stedPC
at next reboot.
Important: changes of this parameter will take effect at next re-
boot.
NE Flags Working options of STED:
∙ bit ’S’ active high
∙ bit ’D’ normal
STED System Flags ∙ bit ’Framed’: D64 channel is framed into X.50d3 envelopes (2).
∙ bit ’Enhanced Modulation’: modulation will work in an improved
mode.
∙ bit ’Adaptive Gain’: enables the adaptive gain feature.
∙ bit ’Step 1 KHz on DpuV2’: checking this bit is possible to set tx/rx
frequency with steps of 1 kHz instead of 4 kHz. In order to have this
feature working is required Fw 2.1.0 or later on CMU, 4.1.0 or later on
DPU and stedPC 1.5.0 or later (2).
Station Role Role (Master or Slave) of STED in the connection.
Bandwidth Bandwidth used by STED {16 ∣ 8 ∣ 4} KHz.
Bit Rate Speed of the channel
Interface Type Interface type (see Tab.5.16) { G.703 ∣ V.11 ∣ Internal G.703 ∣ ethernet
}
Analog Mode ON (1) Analog mode active
Card Attenuation This value has no physical effect but is used only to allow reading from
remote the card attenuation, obtained with jumpers. Any time the
user changes the jumpers settings, he must change this parameter
accordingly. Range: 0 .. 47 dB
(1) Required stedPC 1.6.0 or later, FW CMU 2.2.3 and LFU card created in slot 1, see par.6.1.2.
(2) Can be changed only when port Hv is disabled.
CHAPTER 6. SYSTEM MANAGEMENT 45 / 91

User Manual
Figure 6.1: Generic parameters
Figure 6.2: Generic parameters (stedPC 1.6.0).
6.1.2 Working mode

The default working mode is digital, if slot 1 contains an LFU card and the parameter ’Analog Mode
ON’ is ’true’, the equipment works in analog mode (in toolbar is shown the icon in fig.6.3(b)).
(a) Digital (b) Analog
Figure 6.3: Mode Indicator
6.1.3 Bandwidth parameters

Bandwith parameters can’t change in indipendent way. This paragraph gives a description of
constraints between variables.
A Sted System Flags (bit 0: Framed or Unframed). This is an indipendent parameter.
B Bandwidth of the system, indipendent parameter.
C Interface Type, see Tab.6.2.
D Bit Rate, see Tab.6.3.
46 / 91 CHAPTER 6. SYSTEM MANAGEMENT

User Manual
Table 6.2: Interface Type possible values.

Bandwidth(B) Framed(A) Unframed(A)
16 KHz RS422-ITU-T V.11, ITU-T G.703,
Ethernet-IEEE 802.3-Routing, Internal G.703
Ethernet-IEEE 802.3-Bridging
Table 6.3: Bit rate

Bandwidth(B) Unframed(A) Framed(A)
16 KHz 64, 32, 16 64(20), 32(10), 16(5)
8 KHz 32, 16 32(10), 16(5)
4 KHz 16 16(5)
Number in parenthesis means the maximum number of transported X.50 envelopes.
6.1.4 Identification Data

Parameters used to identify the system. There aren’t fixed rules on how to use them, follows typical
usages of those parameters.
Table 6.4: Identification parameters.

sysName.0 Name of the system, supplied by equipment.
sysContact.0 Person responsible of the system.
sysLocation.0 Place where system is installed.
6.1.5 Sync Management

For the selection of sync source, please refer to section 4.5.1. In the toolbar is costantly showed
the actual sync source provided by STED (figure 6.4).
6.1.6 Date and Time

With the command Menu System → Set Date and Time is possible to change system date
and time of STED.
6.2 Firmware Management

6.2.1 Introduction
A FW release, normally, consists of two files:
• The firmware file itself, that may be an OH intel or Motorola S-record format, depending on
the processor on which it runs.

User Manual
Figure 6.4: Actual Sync Source
Table 6.5: Sample of OH Intel record.
:1051B900402823295341464E5F303038373030304C
• An optional ’Release Notes’ file: an ASCII text file with information about the related FW
(features, solved bugs, workarounds to known bugs etc.).
Table ?? contains a sample of a Release Notes file.
6.2.2 FW Import
Before downloading a FW, is necessary to import it. This means that stedPC must read and
cross-check FW and RN files in order to avoid any error in file manipulation: if the wrong RN is
associated to a FW, the import operation will fail. Furthermore, the user will identify a FW with its
identifier (assigned by Selta) and not with a filename (that can be changed by everyone, could give
truncation problems in case of long names and so on). If the Release Notes file is not available,
select ’Cancel’ on the related file selection box. After the Import operation, FW and RN files are
stored in a proper directory.
6.2.3 FW Download
To download the FW, is necessary to be in On Line mode and to have a privilege level <= 2. After
taking the control, select the board you want to upgrade and give the command Right Mouse
FW Download , a new dialog box is created: the user is asked to select the ID of the desired
FW. A click on ’OK’ button will start the download operation, the ’Rel.Notes’ button will open the
Release Notes of selected entry with notepad editor. For downloading regime FW of UC board
from stedPC, the 1 MB RAM expansion is required, otherwise the operation must be done with
hyperterminal.
6.2.4 Possible download problems

If download doesn’t work, make following checks:
• Check that there isn’t another TFTP server running. If yes, stop it and restart stedPC.
• The software stedPC sends its own IP address to the equipment, if the PC has more than
one interface (also virtual) is possible that stedPC chooses the wrong one. To solve it, disable
undesired interfaces and restart stedPC.
Table 6.6: Sample of Motorola S19 record.
S319008200005341464E5F5F5F520015000082004800820000006C

User Manual
Table 6.7: Sample of Selta Release Notes file
@(#)STED_cmu____r-1.4.0
Manufacturer : Selta S.p.A.
Network Element: STED
Card(s) : cmu
Release Date : 28-Mar-2000
--------------------------------------------------------------
Requirements:
at least stedPC 1.x.x
--------------------------------------------------------------
Release Notes:
* solved bug 00xxx (missing XXX alarm in case of ...)
* improved xxx functionality
* added feature xxxxx (please see MTA xxxxxxxxx)
--------------------------------------------------------------
Hints:
feature XXX works not properly if ....
--------------------------------------------------------------
support: commerciale@selta.it
web : www.selta.com
Figure 6.5: FW import
Figure 6.6: FW file selection

User Manual
Figure 6.7: RN file selection
Figure 6.8: Selection of FW to be downloaded.

User Manual
Table 6.8: Possible failure reasons.

cause effect
The board in the slot is not present stedPC waits 50 sec and then goes to
the next FW
The FW is incompatible with the board in the se- the operation is skipped
lected slot
The FW is not imported the operation is skipped
The rack number or slot number are out of range the operation fails
or non-existing
6.2.5 FW database purge

Obsoletes FW may be removed from FW database with command: Menu System → Purge
FW .
6.2.6 Batch Download

This feature allows to download in sequence a list of FW files to a STE-D with a single GUI
operation.
The operation must be done on-line with opened session (green semaphore) and is allowed to
users with at least privilege 2, you need a text file with the following format:
FW identifier,rack,slot
available identifiers are listed in FW selection window like one in Fig. 6.8, here is an example:
XXXXXXXR-1.21.3,1,15
2Nx64__r-1.0.3,1,6
fwplat_r-3.0.4,1,4
4l2m___r-1.5.6,1,8
Select Menu System → Batch Download , you will be asked for a .txt file containing the list
of FW to be downloaded. The program informs with a window about execution of operations and
prints a report at the end of list processing.
In table 6.8 there is a list of possible failures:
6.3 System Reports

In complex plants, is difficolut to keep track of topology, the print feature may help for having idea
about the ’map’ of the plant. The printing output has 3 sections:
• System Configuration: general informations about the system, equipped boards and their
FW, enabled ports.
• Channels Configuration: informations about channels (associated port and number of con-
nection).
• Connections Informations: list of connections and their channels (with role).
Follows an example (data may be not real):
System configuration
%
Location: MASTER 280KHz
Working Mode: Off Line
....
%
Rack Type: STE-D

User Manual
Slot 1: Not equipped.

Slot 2: DIU
Slot 3: SIU
Slot 6: IL64k
Slot 7: DPU
Slot 8: RXF
Slot 9: TXF
Slot 10:
Slot 12: PSU
Slot 13:
%
%
Slot 2: DIU
DIU port A: enabled Related Channel: ch3
Slot 3: SIU
FXS port A: enabled Related Channel: ch4
Slot 6: IL64k
Network port A: enabled Related Channel: ch1
Slot 7: DPU
High Voltage port A: enabled
Network port A: enabled Related Channel: ch2
Slot 8: RXF
Slot 9: TXF
Slot 10:
Slot 12: PSU
Slot 13:
Channels configuration
%
Ch1--D64 Related Board: 6 Related Port: Network port A
Ch6--X50-9.6 Kb/s [1stE: 1] Connection Index: 1
Ch2--D64 Related Board: 7 Related Port: Network port A
Ch5--X50-9.6 Kb/s [1stE: 1] Connection Index: 1
Ch3--Dce Related Board: 2 Related Port: DIU port A Connection Index: 1
Ch4--Speech-G.729 (FXS) Related Board: 3 Related Port: FXS port A
%
Connections Information
%
Connection Index: 1 Connection type: Point To Multipoint Bidirectional
ch: 6 Connection Role: Remote Site
ch: 5 Connection Role: Central Site
ch: 3 Connection Role: Remote Site
How to read the report Who is connected to channel X.50 of D64 of port A of board in slot 6 ?
1. locate the channel associated to port A of board in slot 6 (in this case: ch1)
2. locate under ch1 the X.50 (ch6)
3. if ch6 is connected, the connection index is cited (in this case: 1)
4. looking in connection 1, it is possible to see that ch6 is connected to ch5 and ch3

User Manual
5. back to channels list, you see that ch5 is a channel X.50 under ch2, which is associated to
Network port A of board in slot 7, while ch3 is associated to DIU port A of board in slot 2.

User Manual

User Manual
7. Channels
7.1 Ports and Channels

A port is a physical resource representing an interface of STED.
A channel is a logical concept, associated with a port, representing the traffic carried by the port.
The association between port and channel is done by the bkp object: a logical entity not seen by
the user.
Ports and channels are related through a ’Bkp’ (Protection Block).
A channel may be connected to one or more compatible channels through the switching matrix,
this action is defined ’connection’.
A channel may be framed (case ’b’: broken into subchannels) or unframed (case ’a’).
On STED the relationship port:channel is always 1:1.
7.2 Channel types

STED allows following type of channels:
• D64, may be structured in X.50 channels following standard ITU-T X.50 (speed from 1200
bps to 19200 bps).
If ’Bandwidth’ (see sec. 6.1.1) is 8 KHz, available X.50 envelopes are 10 instead of 20.
• G.729, compressed speech channel, in compliance with G.729A recommendation, this chan-
nel occupies 3 X.50 envelopes following a predefined pattern.
• Dce: data channel with speed from 1200 to 19200 bps.

• ADPCM: compressed analog channel with speed in range range 16, 24, 32, 40 kb/s. Such
channel needs 6, 9, 12 or 15 envelopes (depending on the speed) with a manually selected
pattern (see par.7.2.3).
7.2.1 Channels creation

Communication channels, identified in this document as ”Channels” are created when a commu-
nication port has been enabled. We remind the user of taking the control of the equipment to
make a configuration (green semaphore). If this operation has not been done, only visualization
commands are available.
Selecting a disabled port and performing a Right Mouse Port Enable a window is opened, and
configuration parameters may be set.
Selecting the Ok button, if the operation has been succesfully carried out, the channel is created
and displayed into the main tree. Each created channel is identified by a label that contains the
following information:
1. A number (unique identifier of the channel)
2. A field that identifies the type of channel
3. Additional information field
CHAPTER 7. CHANNELS 55 / 91
User Manual
Figure 7.1: Relationship between ports and channels
Figure 7.2: Show Group Command-1
Example:
Ch22-Dce-2.4 kb/s
means: Dce channel at 2.4 kb/s, channel identification number = Ch22. This number is the same
used to identifie the channel within connections and printed reports.
Each channel is therefore associated to a port. A ”show-group” command is implemented to show
the port and the related channel. This command is available by selecting a port or a channel.
The same command is available by selecting a channel.
7.2.2 Channel framing

D64 channels, may be framed, but the operation is not allowed if this channel is already connected.
To frame a channel select it and make a Right Mouse Create SubChannels .
A data channel D64 can be framed creating X.50 channels with the command Right Mouse
Create SubChannels . A D64 framed channel places at user’s disposal 20 envelopes that can
be grouped to create X.50 channels. An X.50 channel is characterized by the number of the first
envelope and the channel speed, values selectable on the combo boxes related that appears into
the dialog window. Modifying this parameters, X.50 envelopes are higlighted.
56 / 91 CHAPTER 7. CHANNELS
User Manual
Figure 7.3: Show Group Command-2
Figure 7.4: Channel creation.
Figure 7.5: X.50d3 subchannels creation.
User Manual
Figure 7.6: ADPCM subchannel creation.
Figure 7.7: Envelopes selection for an ADPCM channel.
7.2.3 ADPCM channel

In the ADPCM case it’s necessary to select the speed (see Fig.7.6 and used envelopes (Fig.7.7
and 7.8).
In the channel tree, it’s indicated only the number of first envelope (Fig.7.9).
User Manual
Figure 7.8: Envelopes used by just created channel (2,3,4,5,7,8).
Figure 7.9: ADPCM channel in channels tree.
User Manual
User Manual
8. Connections
The connection of channels is done using a drag&drop mechanism. A channel related to a port
can be highlighted, by selecting the port and performing a Right Mouse ShowGroup .
The steps to make a connection are the following:
1. Select the connection type with the combo box ’Connection Type’ above the Edit Connection
subwindow.
2. Drag the icons of Channels to be connected, into the Edit Connections subwindow.
3. If the connection is a multipoint, select proper channels roles with right click of the mouse.
4. Click on the button ”Connect”.
If the connection operation fails, an error message is displayed.
Figure 8.1: Creating connections.
If the connection operation is succesfully carried out, a tree is displayed into the ”Show Connec-
tions” subwindow. This tree shows a root icon that identifies the connection type, a left click on
this icon highlights channels and related ports, on the contrary a context menu is available by right
clicking there.
Figure 8.2: Connections menu
CHAPTER 8. CONNECTIONS 61 / 91
User Manual
8.1 Connection types

8.1.1 Bidirectional point to point
Often indicated with ’PtP’, see Fig. 8.3(a).
8.1.2 Bidirectional point to multipoint

Bidirectional Multipoint: the Central talks to all peripherals and receives the sum of what peripher-
als transmitted. A peripheral can’t receve transmission of another peripheral.
Indicated also with ’PmP’.
(a) Point To Point (b) Point To Multipoint
Figure 8.3: Connection types.
In case of point-to-multipoint connections, channels role is by default ’peripheral’. Central points

must be selected with the right click mouse.
8.2 Connection roles

When a channel is connected, the corresponding icon is modified to show the new channel status,
according to its role.
Bmp 1 :multipoint connection, ”peripheral” role
Bmp 2 :point to point connection, ”peer” role
Bmp 3 :point to multipoint connection, ”central” role
Figure 8.4: Roles in the connection
62 / 91 CHAPTER 8. CONNECTIONS
User Manual
Figure 8.5: Connections view.
Referring to Fig.8.5, the STE-D has 5 connections. The currently selected is connection 1 (type
’point to point’ or PtP), which joins channels 1 and 4.
CHAPTER 8. CONNECTIONS 63 / 91
User Manual
64 / 91 CHAPTER 8. CONNECTIONS
User Manual
9. Alarms
Alarm classification took inspiration from TMN architecture (ITU-T M.3100).

The system is seen as a collection of objects (boards, ports etc.) and each object can generate
one or more alarms.
A network is a set of Network Elements (NE), a NE contains one or more rack, a rack contains
boards and a board contains zero or more ports.
Some boards have also some software (sfwr) running on board, also sfwr can have alarms (miss-
ing, bad CRC and so on).
9.1 Active Alarms List

Using Menu System - Alarms Report - Show the alarms list on the current node is enabled.
It’s important to know that alarms are calculated from stedPC reading variations in status variables
of objects. Date and time of alarm could be meaningless if connection to STED is done when
alarms are already present. Alarms on boards are shown also on board view.
Figure 9.1: Active Alarms List
9.1.1 Alarm Reminder

In the toolbar there are two alarm-relate icons:
• an alarm indicator with 2 states:

– blinking red: new alarms from last acknowledge
– green: no new alarms
• a light bulb for the acknowledge of new alarms
9.1.2 Alarm Reminder Configuration

The behaviour of the system in case of alarm is configurable through the menu menu Options -
Alarm Configuration (see Figure 9.3).
CHAPTER 9. ALARMS 65 / 91
User Manual
Figure 9.2: Alarm Reporting on equipment view
Figure 9.3: Alarm Reminder Configuration
9.1.3 Object Classification

An object belonging to a class is univocally located with an instance (a sequence of numbers).
To be compatible with network alarm collection, there are 4 digits (the first is always the number of
NE):
• Ne (Network Element): NE/-/-/-

• Board: NE/Rack/Board/-
• Sfwr (Software): NE/Rack/Board/-
• Port: NE/Rack/Board/Port
66 / 91 CHAPTER 9. ALARMS
User Manual
For example: a hw problem on the board inserted in slot 4 will be related to object: Board 1/1/4/0,
while a software problem on the same board will be related to object: Sfwr 1/1/4/0, if the alarm is
on port 5 of the same board: Port 1/1/4/5.
9.2 Alarms Classification

In standard M.3100, an alarm is described by following values:
• Alarm Type: category of the alarm, it may be COMMUNICATION, EQUIPMENT, PROCESS-

ING, ENVIRONMENT
• Perceived Severity: how the system is affected by the alarm.
• Probable Cause: probable cause of the alarm.
• Time: date and time of the alarm.

The standard ETSI 461-2 has a further info: Managed Function, related to functional area affected.
At present this info is not supported.
9.3 Alarms Legenda

9.3.1 Alarm Type
COMMUNICATIONS Problems related to transmissione medium.
EQUIPMENT Problems due to power supply, faults of boards.
PROCESSING Problems related to memory management, errors in software (i.e. download),

mismatch in database versions etc.
User Manual
9.3.2 Probable Cause

Table 9.1 contains the list of probable causes of STE-D.
Table 9.1: Probable Cause List of STED
Probable Cause Severity Obj Description

NE link CRITICAL n Impossible to talk with the node.
replaceableUnitMissing MAJOR b The board in the indicated slot is missing or
not answering
Bad Board Type MAJOR b The board in the indicated slot is missing has
a type different from configured one.
HW Fault MINOR b Generic fault on indicated board.
Bad SW MAJOR b -
Bad Config CRC MAJOR b -
softwarePartMissing MAJOR b One or more necessary software components
are missing.
lossOfSignal MAJOR d No signal received.
replaceableUnitProblem MINOR b Generic fault on indicated board.
aIS MINOR d Alarm indication on the remote system (all ’1’
sent by remote).
lossOfConnection WARNING v The other end of the connection has not been
recognized as a working DCE terminal. In
some documents may be indicated as ’RFS’
(acronyms of italian words meaning Network
Out of Service).
Ext Indication Alarm WARNING n OR of indication line alarms: AIS, RAI
networkOutOfService WARNING ad -
Table 9.2: Legenda about STED objects.
Legenda for column ’Objects’ Description

a Ports of SIU card (FXS, FXO, E&M)
b All cards
d DF64-G.703 port
n NE
v Dce-V.24 ports (DIU card)
9.3.3 Severity
See table 9.3.
9.4 Local Event Log Configuration
User Manual
Table 9.3: Alarm severity legenda.

Severity Description
Critical (1) Severe loss of service, immediate action is required
Major (2) Loss of service, urgent action is required
Minor (3) No loss of service, corrective action suggested to
avoid more severe alarms
Warning (4) Potential problem detected
Cleared (5) Previously notified alarm has been cleared
Table 9.4:
Alarm Class
cfgReset (1)
cfgErase (1)
extSyncKO B
powerFailure B
cardGenAlarm B
cardHwAlarm B
cardSwAlarm B
cardCfgAlarm B
cardMissing B
portHwAlarm B
portSwAlarm A
portCfgAlarm A
netOutOfSvc B
los A
ais A
lof A
ber A
rai A
txFailure B
loopOpen A
antiStreaming A
dpuAlarm B
linkDown A
powerAmplifierFailure B
txFilterFailure B
rxFilterFailure B
netOutOfSvc B
(1) : event, always logged.
User Manual
Figure 9.4:
Figure 9.5:
User Manual
10. On-Line Operations
This chapter describes operations available only on-line (connected with the STE-D).
10.1 Tuning
10.1.1 Tx Filter
According with [4] (par. 3.8.1, Tx Filter Setting, the option Menu Tuning - Tx Filter Tuning set
the working mode of STED to such operation.
During this procedure the icon in Figure 10.1 is shown to inform the user that equipment is in a
tuning phase.
To quit this mode select: Menu Tuning - Normal Operations .
Figure 10.1: Tx filter tuning indicator.
10.1.2 Line hybrid

According with [4] (par. 3.8.2, Line Hybrid Regulation), the option Menu Tuning - Line Bal-
ance Tuning set the working mode of STED to such operation.
At the beginning of the procedure is necessary to insert the hypothetical connection attenuation
(see Figure 10.2 item 1). After that, is opened a new window showing two values (Figure 10.3):
𝐴𝑓𝑡𝑜𝑡 : hybrid gain, to be maximised adjusting the potentiometer on the front of the RX Filter
board.
𝐴𝑠𝑡 : additional attenuation value.
To leave the procedure close this window with the ’Close’ button. While the procedure is active,
the toolbar shows the icon in Figure 10.2, item 2.
CHAPTER 10. ON-LINE OPERATIONS 71 / 91

User Manual
Figure 10.2: Insert the hypotetical connection attenuation.
Figure 10.3: Values of 𝐴𝑓𝑡𝑜𝑡 and 𝐴𝑠𝑡 read from equipment.
10.2 Performance measurements

This feature is fundamental for viewing the quality of a link between two STE-D.
It contains 4 parameters, each one as seen on local side (the STE-D which we are connected) and
on remote side. Table 10.1 gives an explanation of each group.
72 / 91 CHAPTER 10. ON-LINE OPERATIONS

User Manual
Table 10.1: Link status parameters description.

Line Attn Estimation Estimation of line attenuation plus card
attenuation (in dB).
S/N ratio estimation Estimation of S/N ratio. It can be ex-
pressed in dB or in case of degraded
link the indication ’High Noise’ is re-
ported. If the quality of the link is good,
the indication ’> 30𝑑𝐵’ is reported.
Instantaneous Ber Instantaneous value of Ber counted on
the indicated terminal.
Hourly Errors Errors in the last hour counted on indi-
cated terminal.
Figure 10.4: How to see Link Status on HV port.
Figure 10.5: Window just opened (data are not yet valid).
CHAPTER 10. ON-LINE OPERATIONS 73 / 91

User Manual
Figure 10.6: Window with valid values.
74 / 91 CHAPTER 10. ON-LINE OPERATIONS

User Manual
11. Local Event Log
For STE-D is required CMU FW 2.0.78 or later and stedPC 1.3.6 or later.
This feature allows to read the local event log of a STE-D (who support it). The local event log
(hereafter ’Log’) is a binary file stored in non-volatile memory of STE-D containing all relevant
events/alarms, tagged with time of NE.
With stedPC (running on PC) is possible to upload the Log from one or more NE, decode and
analyze the informations with a viewer.
Fig. 11.1 shows the logic architecture of the feature.
Figure 11.1: Logic architecture of the Event Log feature.
Let’s define:
• PC : PC where runs stedPC
• 𝑁 𝐸1 , 𝑁 𝐸2 , ... 𝑁 𝐸𝑛 : Network elements supporting Local event logging
• 𝑆1 , 𝑆2 , ... 𝑆𝑛 : State of the NE (as the sum of states of created objects: cards, ports, etc.)
• 𝐿𝑜𝑔1 , 𝐿𝑜𝑔2 , ... 𝐿𝑜𝑔𝑛 : Log of a NE
• V1: state-based view, traditional view where alarms are detected as a state-transition after
a polling (i.e. when an alarm bit becomes on, the alarm is detected by stedPC). Updated
immediately when detected. Alarms with duration shorter than polling period may be missing
from this view, depending on the alarm state when the polling occurs.
CHAPTER 11. LOCAL EVENT LOG 75 / 91

User Manual
• V2: log-based view: obtained as sum of logs of all the NE logs. Can be updated when NE is
connected, it contains all alarms as viewed from NE (included timestamp).
The view V1 is the classic view of stedPC, view V2 should be seen as the black box of a plane:
after a fault, the user can upload the registration and analyze the data in an off-line mode.
11.1 Upload
To upload events from STE-D, go to stedPC menu and choose ’Options - Upload EventLog’ (Fig.
11.2).
The upload from a gateway node (both SAFN or STE-D) works only using the ethernet address.
Figure 11.2: How to upload events from stedPC.
11.2 Deletion
The user can delete 2 different items:
• Delete events on STE-D memory: ’Options - Cleanup Event Log (on STE-D)’.
Events are entered in memory when they occur, if you delete event memory with some
alarms active, they will not re-entered.
• Delete events on PC: ’Options - Cleanup Evt Database (on PC)’.
11.3 eView
Once uploaded in a database, data can be analyzed and archived with the ad-hoc viewing tool
’eView’.
First of all, the STE-D stores in a table each event separately (alarm on and alarm off are 2 distinct
entries), the viewer makes a processing in order to show a single row for alarm, keeping track of
source events (alarm on and alarm off).
For each event, 9 fields are shown, see Table 11.1 for description.
Opened alarms have only start time and have a non-green color, closed alarms are green and
have both start and stop time, events are green and have only stop time.
76 / 91 CHAPTER 11. LOCAL EVENT LOG

User Manual
The color of a row is green if the alarm is closed or a different color 1 if the alarm is still pending.
The software eView is an external application called by stedPC.
When eView is running, stedPC must wait the retmination of eView.
Table 11.1: Field list.

F
ield Description
Start Time start time of alarm/event
Stop Time stop time of alarm/event
Id On internal identifier of the ’Alarm On’
event
Id Off internal identifier of the ’Alarm Off’
event
Hostname Hostname or IP address of the system
who stored the event
Obj Object related to the event (NE, Card,
Port etc.)
Text Text of the alarm
Ack/Nack Acknowledge state, this is just a flag
that can be turned on/off and use to
viev anly unacknowledged alarms.
Father Id Number of father alarm (it must be set
manually), useful in root cause analy-
sis.
Figure 11.3: eView main window.
11.3.1 View Options

It is possible to exclude from the list alarms that have been acknowledged (or vice-versa) and
alarms already assigned to a father alarm (for root cause analysis).
11.3.2 Filtering
See sections 11.5 and 11.6 for details.
1 With usual meaning: red=critical, orange=major, yellow=minor, cyan=warning, white=event.

User Manual
11.3.3 Advanced Options

Ack/Nack
To acknowledge an alarm, select one or more alarms and click ’Menu - Operations - Ack Selected
Record(s)’ (or F5)
Father event
The user who knows the system can make association between alarms telling that ”Alarm X is
present because of alarm Y (father alarm)”, in such way is possible to exclude from list alarms
which are induced by other alarms and find out root causes.
11.4 eView Menu

• File
– Open Query Load and executes a previously saved query (prepared from ’Custom Filter’
menu).
– Save Last Query Saves to file a query (prepared with ’Custom Filter’ menu).
• View
– View Ack Records If checked shows also the records with the ’Ack’ flag ON.
– View Childs Records If checked shows also the records connected to a father event.
• Operations
– Ack Selected Record(s) (F5) Set the ’Ack’ flag ON.
– Nack Selected Record(s) (F6) Set the ’Ack’ flag OFF.
– Delete Selected Record(s) (F4) Delete the record from the database.
– Connect to Father Event Connects the record to another one, specified by its Id On
number.
– Delete Connection with Father Event Removes the connection to father event.
– Filter Allows the use to specify a standard filter (F7, see section 11.5) or a custom filter
(F10, see 11.6).
A custom filter is needed when standard filter is not enough.
To specify a custom filter you must write a valid SQL condition which extracts a set of
records.
To write a condition is necessary to know field names and a little bit of SQL.
• Alarms
– Show only active alarms Shows only alarm who doesn’t have a closing match.
– Show only alarms not active Shows only alarm who have a closing match.
11.5 Standard Filter

It is possible to filter alarms with a set of standard filters (Menu ’Operations - Filter - Standard’ or
F7) using various criterions:
• Severity (see Fig.11.4(a))
• System name (see Fig.11.4(b)). The system name is assume the name configured in the
’Location’ field (see Fig.11.5).

User Manual
• Alarm type (see Fig.11.6(a))
• Alarm text (see Fig.11.6(b))

• Date/time (see Fig.11.7) The filter is referred to start or stop time (*TBD*)
(a) (b)
Figure 11.4: Standard filter by severity or system name.
Figure 11.5: Where to read system name.
11.6 Advanced Filter

If standard filters are not enough, is possible to define customized filters, writing directly the SQL
condition to extract desired data. The query can also be saved to a file and reloaded on request.

User Manual
(a) (b)
Figure 11.6: Standard filter by alarm type or alarm text.
Figure 11.7: Standard filter by date / time.

User Manual
12. Performance Measurements
This feature requires stedPC release 1.3.6 or later and CMU firmware 2.0.78 or later.
12.1 Current Values

In on-line mode, the menu command: Performance → Current Values will show link quality param-
eters as seen by the equipment related to current interval (see Figure 12.1). The current interval
is not yet stored in equipment memory.
Figure 12.1: View of current values.
12.2 PM data upload

The command Performance → Upload History will upload (from equipment to PC) performance
data, decode and store them in a database.
At the end of this procedure, the user can see data in a html table.
12.3 PM data view

The ’View History’ operation builds an html page (see Fig. 12.2) with the data of the last 7 days (if
available).
12.4 Reset counters

The command Performance → Reset Counters will reset counters in the equipment memory. A
new data upload will read data starting from the reset time, previously read data remain in the PC
database.
12.5 Interval size

By default, the interval size is 15 minutes, as defined by ITU-T G.821. Anyway is possible to
change the size of such intervals to 30 minutes, 1 or 2 hours. In such way, even if the number of
intervals remains the same (96), is possible to store a period of 192 hours (about 8 days).
A change of scale will reset counters.
CHAPTER 12. PERFORMANCE MEASUREMENTS 81 / 91

User Manual
Figure 12.2: Performance data example.
82 / 91 CHAPTER 12. PERFORMANCE MEASUREMENTS

User Manual
13. Usage of tty terminal
In some cases, is necessary to work on the STED with a character connection (’HyperTerminal’).
Note: On STED system some firmware parts (fully compatible) of SAFN equipment has been
reused hence is possible to find some commands/indications containing the word ’SAFN’.
Table 13.1: Serial port settings for Hyperterminal

Parameter Value
Phone number Connect to COMx
Bits per second 38400
Data Bits 8
Parity none
Stop Bits 1
Flow Control none
Other Settings
Terminal Keys
ANSI Emulation
ASCII Settings
Row Interval: 0 mSec
Character Interval 0
Automatic Line Feed
The prompt is:

NRML>
for other session types:
DWNLD = download session (command dwnld )
CFG = configuration session (command startcfg )
CI = plant control session (command startci )
13.1 Useful Operations

Except for IP address and routing table, usage of character terminal is for Lab usage, hence sys-
tem output is in italian. Some conventions:
IND UP = card address (1..5)
ID FW = firmware name, the last letter tells the type: b = boot, r = regime, l = LCA, d = dsp etc.
NUM PORTA = port number (1..N, depending on card)
13.1.1 Viewing the UC status

NRML> getstatus
Stato UC:
Friday the 05 of May, 00 10:31:51
Fw di regime (attivo): XXXXXX R V. X.Y.Z
Fw di bootstrap in FLASH: XXXXXX B V. A.B.C
Fw di bootstrap in E2PROM assente
CHAPTER 13. USAGE OF TTY TERMINAL 83 / 91

User Manual
Tipo Subtelaio: STED

Posizione: UC2
Stato: ATTIVA
Num. Programmazioni LCA: 3
Fw LCA: XXXXXX l V. x.y.z
Fw DSP CAS: XXXXXX d V. x.y.z
Fw DSP X50: XXXXXX d V. x.y.z
13.1.2 Change of IP Address of a STED port (ETH)

NRML> startcfg
CFG> stedaddress ETH 10.0.12.2 255.255.255.0
Write Cfg and Restart to activate the new IP addresses
CFG> write
Configuration succesfully written
CFG> startci
CI> reset uc card
Resetting ....
13.1.3 Add an entry to the routing table

NRML> startcfg
CFG> route add 10.13.0.0 mask 255.255.255.0 172.16.2.254
CFG> write
CFG> startci
CI> reset uc card
Resetting ....
13.1.4 Remove an entry from the routing table

NRML> startcfg
CFG> write
CFG> startci
CI> reset uc card
Resetting ....
13.1.5 Viewing the IP Address

NRML> get uc stedaddress
STED LT IP address: 192.168.10.1
Peer LT IP address: 192.168.10.254
STED DCN IP address: 192.168.11.1
Peer DCN IP address: 192.168.11.254
STED EOC IP address: 192.168.12.1
Peer EOC IP address: 192.168.12.254
Remember that Peer IP address is the address of the RAS on PC (address of the serial port).
Addresses above are default values.
84 / 91 CHAPTER 13. USAGE OF TTY TERMINAL

User Manual
13.1.6 Set date and time

NRML> startci
CI> datetime day-of-week dd mm tt hh mm ss
example:
CI> datetime tuesday 27 5 8 9 1 0
set date/time to tuesday 27 may 2008 09:01:00
13.1.7 Download Firmware UC (Boot in flash)

NRML> dwnld
DWNLD> select regimeuc
Wait the reset and press the uppercase letter related to the action, in this case: F,
then select ’send text file’ from Hyperterminal
during the download the led ’Master’ blinks very fast.
At the end, the FW must be activated with letter A
13.1.8 Download Firmware UC (regime)

NRML> dwnld
DWNLD> select regimeuc
Wait the reset and press the uppercase letter related to the action, in this case: M,
then select ’send text file’ from Hyperterminal
during the download the led ’Master’ blinks very fast
at the end, the FW must be activated with letter A
13.1.9 Download Firmware UP from Hyperterminal

NRML> dwnld
DWNLD> format intel
DWNLD> select fwup IND UP ID FW OFFSET
DWNLD> start
• OFFSET firmware offset

From Hyperterminal select Send Text File and select the desired file.
13.1.10 Erasing a FW from FLASH EPROM

NRML> dwnld
DWNLD> erase fwup IND UP ID FW
DWNLD> exit
13.1.11 Viewing status of an UP board

NRML> get up IND UP status
Fw Regime attivo
Allarme UP assente
Fw di regime presente
Configurazione presente
CRC Configurazione OK
Fw di regime OK
Guasto Hw assente
CHAPTER 13. USAGE OF TTY TERMINAL 85 / 91

User Manual
13.1.12 Viewing id parameters of an UP board

NRML> get up IND UP paramid
Identificativo Fw 0: xxxxxxxb Versione: 1.1.0
Identificativo Fw 1: 8clg r Versione: 1.0.1
Identificativo Fw 2: clg l Versione: 1.0.0
Identificativo Fw 3: Versione: 255.255.255
13.1.13 Viewing the status of an UP Port

NRML> get port IND UP NUM PORTA allitem
13.2 Command Reference

13.2.1 View
get
Synopsis get object data

Description Shows required parameters
Operands object {UC ∣ UP}
data {stedaddress ∣ status ∣ param ...}
Examples get uc stedaddress

Exit status -
Notes -
13.2.2 Configuration
stedaddress
Synopsis stedaddress <port> <address> <peer>

Description Changes IP address of a STED port. With SLIP encapsulation, also the
counterpart (peer) address is necessary, with ethernet the netmask will be
specified.
Operands ∙ port {DCN ∣ EOC ∣ ETH}
∙ IP address
∙ {peer IP address ∣ netmask}
Examples stedaddress EOC 192.168.33.15 192.168.33.254
stedaddress ETH 10.0.1.1 255.255.255.0
Exit status -
Notes -
86 / 91 CHAPTER 13. USAGE OF TTY TERMINAL

User Manual
14. Other Informations
14.1 Assistance through Internet

In case of need, it’s possible to ask assistance from Selta SpA (if this is foreseen by commercial
agreements).
To give access to Selta SpA people on your PC through the Internet you need:
• An Internet connection on system where stedPC runs.
• A TeamViewer client [1] 1 on stedPC.

• Run the software TeamViewerQS.exe and wait for credentials from site teamviewer.com, dur-
ing the connection, the output will be as in Fig.14.1, when connected as in Fig.Figure14.2.
Those credentials grant safe access to your PC.
• Tell to Selta SpA people through phone or e-mail safe access credentials (both ID and Pass-
word).
• At the end of the assistance session close the software TeamViewerQS.exe.
Figure 14.1: Activation of Connection to teamviewer.com.
1 Can be downloaded from http://seltatransfer.advcom.it/index.php?dir=Mgmt-Tools/, copy the file
TeamViewerQS.exe on your PC, no installation required.
CHAPTER 14. OTHER INFORMATIONS 87 / 91

User Manual
Figure 14.2: Connection activated.
88 / 91 CHAPTER 14. OTHER INFORMATIONS

User Manual
Index
𝐴𝑠𝑡 , 71 Local Event Log

𝐴𝑓𝑡𝑜𝑡 , 71 upload, 75
Bandwidth, 45 Measurements, 72
BER Modulation, 45
Instant value, 72
threshold, 40 Output Power, 40
Bit Rate
IL64k, 40 PAU, 15
Performance measurements, 72
Card Attenuation, 45 PLC, 15
CMU, 15 PmP, 62
port
date and time DIU, 39
setup from tty, 85 E&M, 38
DCE Type, 45 enabling, 32
DIU, 15 EOC, 25
DNS, 15 ETH, 25
DPLC, 15 FXO, 37
DPU, 15 FXS, 37
HV, 40
EOC, 15 IL64K, 40
LT, 25
HTTP, 15 TPU, 43
HV, 15 PSU, 15
Hyperterminal, 83 PtP, 62
ICMP, 15 Routing table, 84
Interface Type, 40 Rx Band, 40
HV, 40
IP, 15 S/N estimation, 72
IP Address SIU, 15
change, 84 SNMP, 15
view from console, 84 SQL, 79
Station Role, 45
L2b local loop STED System Flags, 45
IL64K, 40 sysContact, 47
L2b remote loop, 40 sysLocation, 47
Line sysName, 47
Attenuation estimation, 72
Line Hybrid, 40 TCP, 15
Line hybrid TFTP, 15
tuning, 71 TPU, 15
Line Repeater, 40 TRAP, 15
Link Tuning
Quality, 72 Line hybrid, 71
Status, 72 Tx Filter, 71
INDEX 89 / 91
User Manual
Tx Band, 40
Tx Filter
tuning, 71
UDP, 15
90 / 91 INDEX
User Manual
End of Document
Selta spa
- Via Emilia 231 ∙ I-29010 Roveleto di Cadeo (PC) ∙ Italy
T +39 0523/50161 ∙ v +39 0523/5016333
k info@selta.it ∙ Ï www.selta.com
INDEX 91 / 91

Sted User Manual

Uploaded by

Copyright:

Available Formats

You might also like

Sted User Manual

Uploaded by

Document Information

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

Sted User Manual

Uploaded by

Copyright:

Available Formats

User Manual

MT 653610108-A0-GB Ed.2.5 stedPC

Document Code: MT 653610108-A0-GB

Edition change Date

9.3.1 Alarm Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

11 Local Event Log 75

13 Usage of tty terminal 83

Page intentionally left blank.

1.1 CheckBox and ComboBox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.1 Block diagram of STE-D. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.1 TCP/IP network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.1 Board Creation (slot 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

6.1 Generic parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

7.1 Relationship between ports and channels . . . . . . . . . . . . . . . . . . . . . . . 56

8.1 Creating connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

8.2 Connections menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

9.1 Active Alarms List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

10.1 Tx filter tuning indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

11.1 Logic architecture of the Event Log feature. . . . . . . . . . . . . . . . . . . . . . . 75

12.1 View of current values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

14.1 Activation of Connection to teamviewer.com. . . . . . . . . . . . . . . . . . . . . . . 87

2.1 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.1 Possible management interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.1 Compatibility list card/slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6.1 System generic parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

9.1 Probable Cause List of STED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

10.1 Link status parameters description. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

11.1 Field list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

13.1 Serial port settings for Hyperterminal . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Page intentionally left blank.

[1] Internet site teamviewer. http://www.teamviewer.com.

Page intentionally left blank.

Page intentionally left blank.

(a) —WinCheckBox (b) ComboBox

Figure 1.1: CheckBox and ComboBox.

Figure 1.2: Menu

1.1.4 Radio button

Figure 1.3: Radio button

It allows to select one or more option from a list (Figure 1.4).

Figure 1.4: ListBox

Procedure for a step-by-step data insertion (Figure 1.5).

(a) step 1 (b) step 2

Figure 1.5: Two pages wizard.

1.1.7 Context Menu

Figure 1.6: Context Menu

1.2 Graphic Conventions

1.3 Textual Conventions

Page intentionally left blank.

2.1 System Requirements

Table 2.1: System requirements

2.2 Supported Operating Systems

Table 2.2: Supported Operating systems.

(1) = from version 1.4.0.

Page intentionally left blank.

3.1 Remind about STED

Figure 3.1: Block diagram of STE-D.

3.2 Operating Modes

CHAPTER 3. SYSTEM DESCRIPTION 23 / 91

Figure 3.2: Operating Modes