USER MANUAL

FOX61x
LEDS1, leds1_r2g
TDM Data Interfaces, 4 DCE Ports,
1 Ethernet Port
LEDS1 User Manual
Document ID 1KHW002478

Document edition FOX61x System Release: R1/R2/R3/R14/R15

Revision: H
Date: 2022-01-11

Copyright and confidentiality Copyright in this document vests in Hitachi Energy.

Manuals and software are protected by copyright. All rights reserved. The copying,
reproduction, translation, conversion into any electronic medium or machine
scannable form is not permitted, either in whole or in part. The contents of the
manual may not be disclosed by the recipient to any third party, without the prior
written agreement of Hitachi Energy.
An exception is the preparation of a backup copy of the software for your own use.
For devices with embedded software, the end-user license agreement on the
enclosed CD applies.
This document may not be used for any purposes except those specifically
authorized by contract or otherwise in writing by Hitachi Energy.

Disclaimer ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Manufactured by/for a Hitachi Energy company.
Hitachi Energy Switzerland Ltd (hereinafter referred to as Hitachi Energy) has taken
reasonable care in compiling this document, however Hitachi Energy accepts no
liability whatsoever for any error or omission in the information contained herein and
gives no other warranty or undertaking as to its accuracy.
Hitachi Energy can accept no responsibility for damages, resulting from the use of
the network components or the associated operating software. In addition, we refer to
the conditions of use specified in the license contract.
Hitachi Energy reserves the right to amend this document at any time without prior
notice.
The product/software/firmware or the resulting overall solution are designed for data
processing and data transmission and may therefore be connected to communication
networks. It is your sole responsibility to provide and continuously ensure a secure
connection between the product/software/firmware or the resulting overall solution
and your network or any other networks (as the case may be). You shall establish
and maintain any appropriate measures (such as but not limited to the installation of
firewalls, application of authentication measures, encryption of data, installation of
anti-virus programs, etc.) to protect the product/software/firmware or the resulting
overall solution, the network, its system and all the interfaces against any kind of
security breaches, unauthorized access, interference, intrusion, leakage and/or theft
of data or information. Hitachi Energy and its affiliates are not liable for damages and/
or losses related to such security breaches, any unauthorized access, interference,
intrusion, leakage and/or theft of data or information.
Although Hitachi Energy provides functionality testing on the products including
related firmware and software that we release, you should institute your own testing
program for any product updates or other major system updates (to include but not
limited to firmware/software changes, configuration file changes, third party software
updates or patches, hardware exchanges, etc.) to ensure that the security measures
that you have implemented have not been compromised and system functionality in
your environment is as expected.

Copyright 2022 Hitachi Energy. All rights reserved. 2

FOX61x | LEDS1

Contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1 Precautions and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Symbols and Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Interfaces and Circuit Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.6 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Unit View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3 Functions and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1 Feature Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Summary of Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 DCE functions and Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.4 DCE physical Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.5 MAC Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6 General Functions and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2 Slots and Deployment Scenarios for the LEDS1 Unit. . . . . . . . . . . . . . . . . . . . . . . 24
4.3 Interoperability and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.3.1 FOX61x Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.3.2 FOX51x Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3.3 Previous ESW Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4 Connections and Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4.1 Connectors and Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4.2 DCE Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.4.3 Ethernet Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.4.4 Fixing the Cables to the Cable Tray . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.1 Data Interface Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.1.1 DCE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.1.2 RS485 2-wire Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.1.3 Transport Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.1.4 Transmission Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.1.5 MAC Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.2 Network Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2.1 Point-to-Point (P2P). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2.2 Point-to-Multipoint (P2MP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2.3 Multipoint-to-Multipoint (MP2MP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3 Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.3.1 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.3.2 Local Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.3.3 Conferences in the P2MP Application . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.3.4 Conferences in the MP2MP Application . . . . . . . . . . . . . . . . . . . . . . . . 53
5.3.5 Conference Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.4 Data Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.4.1 Port Data Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.4.2 Conference Data Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.5 Control Signal Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.5.2 Subrate Framing Signaling Transport. . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.5.3 CAS Signaling Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.5.4 Port Control Signal Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Copyright 2022 Hitachi Energy. All rights reserved. 3

FOX61x | LEDS1

5.5.5 Conference Control Signal Handling . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.6 Timing Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.6.1 DTE Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.6.2 Port Timing Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.6.3 Conference Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.7 Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.7.1 Subnetwork Connection and linear Trail Protection . . . . . . . . . . . . . . . . . . 77
5.7.2 Equipment Protection (EQP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.1 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.1.2 LEDS1 Profile Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.2 Commissioning of a DCE Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2.2 Configuration of a DCE Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.3 Commissioning of a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.3.2 Configuration of a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.1 Unit optical Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.2 Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.2.1 Loop 2b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
7.2.2 Loop 3b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.2.3 Loop 3c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.3 DCE Interface Line State Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.4 DTE send and idle Time Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
7.5 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.5.1 Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.5.2 Unit ESW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.5.3 ESW Upgrade with EQP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8 User Interface Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.2 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.2.1 QoS Mapping Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.3 AP: / unit-x: LEDS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.3.1 AP: / unit-x, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.3.2 AP: / unit-x, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.3.3 AP: / unit-x, Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.3.4 AP: / unit-x, Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
8.3.5 AP: / unit-x, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.4 AP: / unit-x / port-y, y = 1 … 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.4.1 AP: / unit-x / port-y, Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.4.2 AP: / unit-x / port-y, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.4.3 AP: / unit-x / port-y, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.4.4 AP: / unit-x / port-y, Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . 124
8.4.5 AP: / unit-x / port-y, Performance Management . . . . . . . . . . . . . . . . . . . . 125
8.4.6 AP: / unit-x / port-y, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
8.5 AP: / unit-x / port-y, y = 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
8.5.1 AP: / unit-x / port-y, Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
8.5.2 AP: / unit-x / port-y, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
8.5.3 AP: / unit-x / port-y, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.5.4 AP: / unit-x / port-y, Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . 136
8.5.5 AP: / unit-x / port-y, Performance Management . . . . . . . . . . . . . . . . . . . . 137
8.5.6 AP: / unit-x / port-y, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
8.6 AP: / unit-x / conf-z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.6.1 AP: / unit-x / conf-z, Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.6.2 AP: / unit-x / conf-z, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Copyright 2022 Hitachi Energy. All rights reserved. 4

FOX61x | LEDS1

8.6.3 AP: / unit-x / conf-z, Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

8.7 AP: / unit-x / conf-z / part-a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.7.1 AP: / unit-x / conf-z / part-a, Overview . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.7.2 AP: / unit-x / conf-z / part-a, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.7.3 AP: / unit-x / conf-z / part-a, Configuration . . . . . . . . . . . . . . . . . . . . . . . 143
8.7.4 AP: / unit-x / conf-z / part-a, Fault Management . . . . . . . . . . . . . . . . . . . . 147
8.7.5 AP: / unit-x / conf-z / part-a, Performance Management . . . . . . . . . . . . . . . . 148
8.7.6 AP: / unit-x / conf-z / part-a, Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
9 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
9.1 Associated FOX61x Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Copyright 2022 Hitachi Energy. All rights reserved. 5

FOX61x | LEDS1 PREFACE

1 Preface

1.1 Precautions and Safety

Before you handle any equipment you must comply with the safety advices.
Adherence to the safety instructions ensures compliance with the safety requirements as
defined in EN 60950 (Safety of Information Technology Equipment).
Please refer to the following document:
[1KHW002497] Operating Instruction “Precautions and safety”.

1.2 Symbols and Notations

This User Manual uses the following symbols:

Risk of operating trouble!

Indicates that an action may lead to operating trouble or loss of data.
→ Possible actions are given.

Please note:
Shows significant information.
→ Possible actions are given.

1.3 Interfaces and Circuit Categories

Table 1: Electrical interfaces and circuit categories
LEDS1 interface Circuit category accord- Max. rating
ing to EN 60950-1 Voltage Current
Local power supply TNV2 < 72 VDC < 0.2 A
V.35 / Appendix II SELV <1V < 10 mA
V.35 / V.28 SELV < 25 V < 100 mA
X.24 / V.11 TNV1 <6V < 150 mA
V.24 / V.28 SELV < 25 V < 100 mA
RS485 TNV1 <6V < 200 mA
Ethernet SELV <3V < 10 mA

1.4 Document History

Table 2: Document history
Document ID FOX61x Rev. Date Changes since previous version
Release
1KHW002478 R15B H January 2022 Updated to current system release.
1KHW002478 R15A G June 2021 - Support in the system release R15.

Copyright 2022 Hitachi Energy. All rights reserved. 6

FOX61x | LEDS1 PREFACE

Table 2: Document history (continued)

Document ID FOX61x Rev. Date Changes since previous version
Release
1KHW002478 R14A F November 2020 - Maximum bandwidth for data transport increased
to 2048 kbit/s.
- Inversion of transmit and receive data signals can
be configured individually.
- Inversion of the control signal 105 (RTS, C) configu-
rable.
- Update copyright statement.
1KHW002478 R14A E June 2020 - Support in system release R14.
1KHW002478 R3B_SP01 D December 2019 - Update of references to the synchronization user
manual.
- Slot 13 is usable independent of the core unit type
plugged in slot 11.
1KHW002478 R3B C September 2019 - Update of the Ethernet cables specification.
- Slot 13 is only usable if the core unit plugged in slot
11 is a CESM1 or CESM2 unit.
1KHW002478 R3A B November 2018 - New Hitachi Energy branding.
- New P12 transport unit SAMO5.
1KHW002478 R2D 2 December 2017 - Note added about cross connection creation with
EQP.
1KHW002478 R2C 1 December 2016 - Transition coding mode for 64 kbit/s.
- Reference to Quick Guides removed.
1KHW002478 R1C 2 August 2014 - Minor editorial changes.
1KHW002478 R1A 1 December 2012 - First revision for the FOX61x system release R1A

1.5 Target Audience

This User Manual is targeted at persons who are entrusted with the installation, provisioning,
operation and administration of the system.
The persons targeted are
• the installation personnel, and/or
• the provisioning personnel, and/or
• the operation and administration personnel

Please note:
Only trained and skilled personnel (maintenance staff as per EN 60950) may install
and maintain the system.

1.6 Definition of Terms

Table 3: Specific terms
Term Explanation
CESM1 Designates the core and control unit CESM1 or CESM1-F of FOX61x.
CESM2 Designates the core and control unit CESM2 or CESM2-F of FOX61x.
Core Unit Designates the core and control unit CESM1, CESM1-F, CESM2, CESM2-F or
CESM3 of FOX61x.
Where certain features or characteristics apply to a specific core unit only, the
CESM1, CESM1-F, CESM2, CESM2-F or CESM3 is named explicitly.

Copyright 2022 Hitachi Energy. All rights reserved. 7

FOX61x | LEDS1 PREFACE

Table 3: Specific terms (continued)

Term Explanation
Receive direction Direction from the DCE interface (LEDS1) towards the DTE
transmit
LEDS1
DTE
receive (DCE)

Transmit direction Direction from the DTE towards the DCE interface (LEDS1)

Copyright 2022 Hitachi Energy. All rights reserved. 8

FOX61x | LEDS1 INTRODUCTION

2 Introduction

2.1 General
This document describes the architecture and functions of the LEDS1 unit and shows, how this
unit is commissioned and operated as part of the FOX61x.
The LEDS1 unit is a 1-slot wide service unit of FOX61x. It supports four data interfaces and one
Ethernet bridge port.
Each data interface is independently configurable as DCE interface type
• V.24/V.28,
• V.35 (Appendix II),
• X.24/V.11, or
• RS485.
The DCE interfaces support the following transmission modes:
• Asynchronous mode for subrates from 0.6 kbit/s to 38.4 kbit/s.
• Synchronous mode for subrates from 0.6 kbit/s to 56 kbit/s.
• Synchronous mode for nx64 data rates from 1x64 kbit/s to 31x64 kbit/s.
• Oversampling mode for data rates from 0 kbit/s to 600 kbit/s.
• Transition Coding mode for data rates from 0 kbit/s to 19.2 kbit/s.
The synchronous nx64 transmission modes provide the codirectional or contradirectional timing
operation.
The Ethernet bridge port is implemented as 10BASE-T/100BASE-TX interface according to
IEEE Std. 802.3-2002.
Beside the data access LEDS1 offers the possibility to establish data conferences with partici-
pants from the LEDS1 unit or any data circuit available in the FOX61x.
FOX61x FOX61x

LEDS1 TDM data

Network
LEDS1 DTE
Data
Confer-
ence
FOX61x
data TDM LEDS1
data
DTE Network DTE

P12 transport unit

Figure 1: DTEs connected in a star network, with conference

The LEDS1 unit as a FOX61x TDM unit provides PBUS (FOX61x TDM bus) access.
LEDS1 has an access capacity of 32 x 2 Mbit/s towards the FOX61x internal cross connection
backplane, PBUS, allowing access of the four data user ports, the Ethernet bridge port and of
up to 212 data conferences with up to 848 participants in total.
The following network features will help to enhance the systems availability:
• 1+1 linear trail protection switching.
• 1+1 linear subnetwork connection protection switching.
A more economical use of the network resources can be achieved by the features like:
• Point-to-multipoint linear networks (P2MP)
• Multipoint-to-multipoint linear networks (MP2MP)

Copyright 2022 Hitachi Energy. All rights reserved. 9

FOX61x | LEDS1 INTRODUCTION

The multipoint networks are using the data conferences.

LEDS1 is connected to a TDM transport unit as e.g. a SAMO1 unit via the PBUS in the back-
plane of FOX61x.

2.2 Unit View

Figure 2: LEDS1 unit view

Figure 2 shows the LEDS1 unit hardware. On the front plate are two LEDs for the unit- and traf-
fic failure indication. The connectors for the four data interfaces are of type Metral ® with 4x6
male contacts.
The Ethernet interface uses a standard RJ-45 connector.

Copyright 2022 Hitachi Energy. All rights reserved. 10

FOX61x | LEDS1 INTRODUCTION

2.3 Block Diagram

PBUS Access
Cross 1 x P12 nx64 kbit/s Ethernet
Connect - 1+1 protection interface

Front Connectors
DCE interface 1
PBUS Access

nx64 kbit/s - X.24/V.11 2

Cross 4 x P12
- CAS time slot - V.35 3
Connect
- 1+1 protection Subrate - V.24/V.28 4
< 64 kbit/s - RS485
PBUS Access

Cross 27 x P12 Conferencing

Connect - 1+1 protection

Host processor
Backplane access

Subrack internal
communication

Power

Figure 3: LEDS1 functional block diagram

Copyright 2022 Hitachi Energy. All rights reserved. 11

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

3 Functions and Specifications

The LEDS1 unit uses the following feature licenses, provides the functions listed below and con-
forms to the corresponding standards and recommendations (conformance to applicable parts
of the standards).

3.1 Feature Licenses

Part of the FOX61x functionality is subject to feature licenses. For more information on feature
licenses please refer to [1KHW028777] Release Note “FOX61x” and to [1KHW028776] Product
Description “Feature Licenses for FOX61x”.

3.2 Summary of Standards

Table 4: Standards
Feature Standard
Data transport - ETSI EN 300 417-5-1 V1.2.1, 2001-10 r1a
Transmission and Multiplexing (TM); Generic
requirements of transport functionality of
equipment; Part 5-1: Plesiochronous Digital
Hierarchy (PDH) path layer functions
- ETSI EN 300 417-2-1 V1.2.1, 2001-10
Transmission and Multiplexing (TM); Generic
requirements of transport functionality of
equipment; Part 2-2: Synchronous Digital Hier-
archy (SDH) and Plesiochronous Digital Hierar-
chy (PDH) physical section layer functions
- ETSI EN 300 417-1-1 V1.2.1, 2001-10
Transmission and Multiplexing (TM); Generic
requirements of transport functionality of
equipment; Part 1-1: Generic processes and per-
formance
- ITU-T I.460, 02/99 r2e
Multiplexing, rate adaptation and support of
existing interfaces
- ITU-T V.14, 03/93
Transmission of start-stop characters over syn-
chronous bearer channels
- ITU-T V.110, 02/2000
Support by an ISDN of data terminal equip-
ments with V-Series type interfaces
- ITU-T X.30, 03/93
Support of X.21, X.21bis and X.20bis based Data
Terminal Equipments (DTEs) by an Integrated
Services Digital Network (ISDN)
- ITU-T R.111, 03/93
Code and speed independent TDM system for
anisochronous telegraph and data transmis-
sion

Copyright 2022 Hitachi Energy. All rights reserved. 12

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 4: Standards (continued)

Feature Standard
Data interfaces - ITU-T V.11, X.27, 10/96 r1a
Electrical characteristics for balanced double-
current interchange circuits operating at data
signaling rates up to 10 Mbit/s
- ITU-T V.24, 02/2000
List of definitions for interchange circuits
between data terminal equipment (DTE) and
data circuit-terminating equipment (DCE)
- ITU-T V.28, 03/93
Electrical characteristics for unbalanced dou-
ble-current interchange circuits
- ITU-T V.35, 10/84
Data transmission at 48 kilobits per second
using 60-108 kHz group band circuits
- ITU-T X.21, 09/92
Interface between Data Terminal Equipment
and Data Circuit-terminating Equipment for
synchronous operation on public data net-
works
- ITU-T X.21bis, 11/88
Use on public data networks of Data Terminal
Equipment (DTE) which is designed for inter-
facing to synchronous V series modems
- ITU-T X.24, 11/88
List of definitions for interchange circuits
between Data Terminal Equipment (DTE) and
Data Circuit-terminating Equipment (DCE) on
public data networks

- TIA/EIA-485-A, 1998
Electrical characteristics of generators and
receivers for use in balanced digital multipoint
systems
- ITU-T X.20, 11/88 r2e
Interface between Data Terminal Equipment
(DTE) and Data Circuit-terminating Equipment
(DCE) for start-stop transmission services on
public data networks
- ITU-T X.20bis, 11/88
Use on public data networks of Data Terminal
Equipment (DTE) which is designed for inter-
facing to asynchronous duplex V-Series
modems
Synchronization and timing - ISO/IEC 9543, 1989-04-01 r1a
Information processing systems – Information
exchange between systems – Synchronous
transmission signal quality at DTE/DCE inter-
faces
- ISO/IEC 7480, 1991-12-15 r2e
Information technology – Telecommunications
and information exchange between systems –
Start-stop transmission signal quality at DTE/
DCE interfaces

Copyright 2022 Hitachi Energy. All rights reserved. 13

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 4: Standards (continued)

Feature Standard
Ethernet transport - ISO/IEC 13239 r2a
Information technology -- Telecommunications
and information exchange between systems --
High-level data link control (HDLC) procedures

- ANSI/IEEE Std 802.1D, 1998

IEEE Standard for Information technology.
Telecommunications and information
exchange between systems. Local and metro-
politan area networks. Common specifications
Part 3: Media Access Control (MAC) Bridges
- IEEE Std 802.3-2002
IEEE Standard for Information technology —
Telecommunications and information
exchange between systems — Local and metro-
politan area networks — Specific requirements
Part 3: Carrier sense multiple access with colli-
sion detection (CSMA/CD) access method and
physical layer specifications
Ethernet management - RFC1493 r2a
Definitions of Managed Objects for Bridges
- RFC2131
Dynamic Host Configuration Protocol
- RFC2132
Dynamic Host Configuration Protocol
- RFC2674
Definitions of Managed Objects for Bridges
with Traffic Classes, Multicast Filtering and Vir-
tual LAN Extensions
- RFC3396
Encoding Long Options in the Dynamic Host
Configuration Protocol (DHCPv4)
- RFC3442
The Classless Static Route Option for Dynamic
Host Configuration Protocol (DHCP) version 4
- RFC3942
Reclassifying Dynamic Host Configuration Pro-
tocol version 4 (DHCPv4) Options
Performance parameters and limits - ITU-T G.826, 12/2002 r1a
End-to-end error performance parameters and
objectives for international, constant bit-rate
digital paths and connections
Maintenance functions - ITU-T V.54, 11/88 r1a
Loop test devices for modems
- ITU-T X.150, 11/88
Principles of maintenance testing for public
data networks using Data Terminal Equipment
(DTE) and Data Circuit terminating Equipment
(DCE) test loops

Copyright 2022 Hitachi Energy. All rights reserved. 14

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

3.3 DCE functions and Specifications

Table 5: DCE functions and specifications
Feature Rating or standard Release
Number of available DCE interfaces 4 r1a
Type of interfaces individually selectable by the configuration man-
agement:
X.24/V.11
V.24/V.28
V.35
RS485 4-wire
RS485 2-wire
User data rates of < 64 kbit/s synchronous r2e
0.6 to 56 kbit/s (X.30 or V.110)

Note: With 0.6 kbit/s according to V.110, only

the 40 ms frame is supported.
With 56 kbit/s a frame according to table 7b/
V.110 or 7c/V.110 can be used. The alternative
structure (table 7c/V.110) offers additional tim-
ing and control information.
User data rates of < 64 kbit/s asynchronous r2e
0.6 to 38.4 kbit/s (X.30 or V.110)

Note: Bit rates below 600 bit/s and between the

offered standard bit rates can be transported
using oversampling or transition coding.
Oversampling mode Sampling of the user data signal with the config- r1a
ured synchronous transmission rate: nx64
kSamples/s
Transition Coding mode Sampling of the user data signal with 256 kSam- r2f
ples/s and transport with 64 kbit/s according to
Annex A of ITU-T R.111.
User data rate up to 19.2 kbit/s.
R.111 framing and service bits are not sup-
ported.
Selection between X.30 and V.110 framing according to the selected DCE interface type: r2e
X.24/V.11 → X.30
V.24/V.28 → V.110
V.35 → V.110
User data rates of nx64 kbit/s synchronous r2g
nx64 kbit/s, n = 1 to 32, without CAS
nx64 kbit/s, n = 1 to 30, with use of CAS for con-
trol signal transport
Synchronization r1a
- DCE interface synchronous mode Synchronized to the network element (NE) tim-
ing source.
With X.24/V.11, V.24/V.28 and V.35 type inter-
faces:
Contradirectional or codirectional timing
- DCE interface asynchronous mode Asynchronous subrate DCE signals adjusted to r2e
the network element (NE) timing source by
manipulating the stop bits.

Copyright 2022 Hitachi Energy. All rights reserved. 15

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 5: DCE functions and specifications (continued)

Feature Rating or standard Release
DCE output jitter, < 64 kbit/s, synchronous (data, in accordance with ISO 9543 r2e
control and timing signals)
- jitter peak to peak S, 114, 115 ≤ 30%
- duty cycle of S, 114, 115 50 ± 10%
- timing displacement of the receive data and con- ≤ 20%
trol signals (peak) in relation to S, 115 (OFF to ON)
DCE output jitter, < 64 kbit/s, asynchronous in accordance with ISO 7480 r2e
(data signals)
- minimum duration of any start or data or parity ≥ 60%
signal element
- average character interval (CI), averaged over 2 ≥ CI - 20% UI
characters
- minimum character interval (CI) ≥ CI - 40% UI
DCE output jitter, nx64 kbit/s r1a
- Intrinsic jitter peak-peak on the clock signals ≤ 50 ns in the frequency range of 20 Hz to
100 kHz
- timing accuracy better than 50 ppm peak
DCE output jitter, nx64 kbit/s in accordance with ISO 9543 r1a
(data, control and timing signals)
- jitter peak-peak S, 114, 115 ≤ 30%
- duty cycle S, 114, 115 50 ± 10%
DCE jitter tolerance, < 64 kbit/s, synchronous in accordance with ISO 9543 r2e
(data, control and timing signals)
- jitter peak-peak X, 113 (ON to OFF) ≤ 1%
- duty cycle X, 113 50 ± 10%
- timing displacement of the transmit data and con- ≤ 45%
trol signals (peak, codirectional timing) in relation
to X, 113 (ON to OFF)
- timing displacement of the transmit data and con- ≤ 30%
trol signals (peak, contradirectional timing) in rela-
tion to 114 (OFF to ON)
DCE jitter tolerance, < 64 kbit/s, asynchronous in accordance with ISO 7480. r2e
(data signals)
- minimum duration of any start or data or parity ≥ 90%
signal element
- average character interval (CI), averaged over 2 ≥ CI - 8% UI
characters
- minimum character interval (CI) ≥ CI - 16% UI
DCE jitter tolerance, nx64 kbit/s in accordance with ISO 9543 r1a
(data, control and timing signals)
- jitter peak-peak X, 113 (ON to OFF) ≤ 1%
- duty cycle X, 113 50 ± 10%
- timing displacement of the transmit data and con- ≤ 45%
trol signals (peak, codirectional timing) in relation
to X, 113 (ON to OFF)
- timing displacement of the transmit data and con- ≤ 30%
trol signals (peak, contradirectional timing) in rela-
tion to S, 114 (OFF to ON)
DCE to DCE transfer delay Maximum one way transfer delay from DCE r1a
interface to DCE interface excluding any net-
work delays

Copyright 2022 Hitachi Energy. All rights reserved. 16

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 5: DCE functions and specifications (continued)

Feature Rating or standard Release
- < 64 kbit/s, synchronous maximum one way transfer delay from DCE r2e
interface to DCE interface excluding any net-
work delays
600 bit/s:≤ 60 ms
1200 bit/s:≤ 25 ms
2400 bit/s:≤ 15 ms
4800 bit/s:≤ 8 ms
9600 bit/s:≤ 4 ms
19200 bit/s:≤ 1.9 ms
38400 bit/s:≤ 1.4 ms
48000 bit/s:≤ 1.2 ms
56000 bit/s:≤ 1.2 ms
- < 64 kbit/s, asynchronous maximum transfer delay from DCE interface to r2e
DCE interface excluding any network delays
600 bit/s:≤ 60 ms
1200 bit/s:≤ 25 ms
2400 bit/s:≤ 15 ms
4800 bit/s:≤ 8 ms
9600 bit/s:≤ 4 ms
19200 bit/s:≤ 2.5 ms
38400 bit/s:≤ 1.4 ms
- nx64 kbit/s, contradirectional timing ≤ 600 μs with fixed transmit timing. r1a
≤ 600 μs + 250/n μs with phase adaptive trans-
mit timing
- nx64 kbit/s, codirectional timing ≤ 600 μs + 250/n μs r1a

3.4 DCE physical Layers

Table 6: V.24/V.28 DCE physical layer functions and specifications
Feature Rating or standard Release
Interface circuits V.24 - 102 GND signal ground or common return r1a
(unused circuits are kept in the OFF state) - 103 TxD transmitted data
- 104 RxD received data
- 105 RTS request to send
- 106 CTS ready for sending
- 107 DSR data set ready
- 108 DTR data terminal ready
- 109 DCD data channel rec. line sig. det.
- 113 TT transmitter signal element timing
- 114 ST transmitter signal element timing
- 115 RT receiver signal element timing
- 141 LL local loopback
- 142 TM test indicator
- Signal direction to DCE circuits 103, 105, 108, 113, 141
- Signal direction from DCE circuits 104, 106, 107, 109, 114, 115, 142
Electrical characteristics r1a
- circuits 103, 105, 108, 113 and 141 as receivers according to V.28
- circuits 104, 106, 107, 109, 114, 115 and 142 as according to V.28
transmitters
Polarities r1a
- 103, 104 = 0 - UA > 3 V (system logic: level low)
- 103, 104 = 1 - UA < -3 V (system logic: level high)
- all other circuits = ON - UA > 3 V (system logic: level low)
- all other circuits = OFF - UA < -3 V (system logic: level high)

Copyright 2022 Hitachi Energy. All rights reserved. 17

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 6: V.24/V.28 DCE physical layer functions and specifications (continued)

Feature Rating or standard Release
User data rates available nx64 kbit/s synchronous, n = 1 to 2 r2g
nx64 kbit/s oversampling 1, n = 1 to 30, with CAS
nx64 kbit/s oversampling 1, n = 1 to 32, without CAS
< 64 kbit/s synchronous r2e
≤ 38.4 kbit/s asynchronous
64 kbit/s transition coding 2 r2f
Maximum line length at the maximum available 15 m r1a
data rate

1. The effective user data rate should be at least three to four times lower than the oversampling frequency.
2. The effective user data rate should be at most 19.2 kbit/s.

Table 7: X.24/V.11 DCE physical layer functions and specifications

Feature Rating or standard Release
Interface circuits X.24 - G signal ground or common return) r1a
(unused circuits are kept in the OFF state) - T transmit
- R receive
- C control
- I indication
- S signal element timing
- B byte timing
- F frame start indication
- X DTE transmit signal element timing
- Signal direction to DCE circuits T, C, X
- Signal direction from DCE circuits R, I, S, B, F
Electrical characteristics r1a
- Circuits T, C and X as receivers according to V.11 (X.27)
- Equivalent terminating resistor 125 Ω ± 10%.
- Circuits R, I, S, B and F as transmitters according to V.11 (X.27)
Polarities r1a
- R, T = 0 - UA-UB≥ 0.3 V(system logic: level low)
- R, T = 1 - UA-UB≤ -0.3 V(system logic: level high)
- C, I, S, B, F, X = ON - UA-UB≥ 0.3 V(system logic: level low)
- C, I, S, B, F, X = OFF - UA-UB≤ -0.3 V(system logic: level high)
User data rates available nx64 kbit/s synchronous, n = 1 to 30, with CAS r2g
nx64 kbit/s synchronous, n = 1 to 32, without CAS
nx64 kbit/s oversampling 1, n = 1 to 30, with CAS
nx64 kbit/s oversampling 1, n = 1 to 32, without CAS
< 64 kbit/s synchronous r2e
≤ 38.4 kbit/s asynchronous
64 kbit/s transition coding 2 r2f
Maximum line length at the maximum available 15 m with contradirectional timing r1a
data rate 50 m with codirectional timing

1. The effective user data rate should be at least three to four times lower than the oversampling frequency.
2. The effective user data rate should be at most 19.2 kbit/s.

Copyright 2022 Hitachi Energy. All rights reserved. 18

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 8: V.35 DCE physical layer functions and specifications

Feature Rating or standard Release
Interface circuits V.35 - 102 GND signal ground or common return r1a
(unused circuits are kept in the OFF state) - 103 TxD transmitted data
- 104 RxD received data
- 105 RTS request to send
- 106 CTS ready for sending
- 107 DSR data set ready
- 108 DTR data terminal ready
- 109 DTR data terminal ready
- 113 TT transmitter signal element timing.
- 114 ST transmitter signal element timing
- 115 RT receiver signal element timing
- 141 LL local loopback
- 142 TM test indicator

Note: The signal list is according to ITU-T V.36, i.e.

the signals 113, 141 and 142 are added to the signal
list of V.35. The signal 108 has been added from the
V.24 signal list.
- Signal direction to DCE circuits 103, 105, 108, 113, 141
- Signal direction from DCE circuits 104, 106, 107, 109, 114, 115, 142
Electrical characteristics r1a
- Circuits 103 and 113 as receivers according to V.35
- Circuits 105, 108 and 141 as receivers according to V.28
- Circuits 104, 114 and 115 as transmitters according to V.35
- Circuits 106, 107, 109 and 142 as transmitters according to V.28
Polarities r1a
- 103, 104 = 0: - UA-UB> 0 V (system logic: level low)
- 103, 104 = 1: - UA-UB< 0 V (system logic: level high)
- 113, 114, 115 = ON: - UA-UB> 0 V (system logic: level low)
- 113, 114, 115 = OFF: - UA-UB< 0 V (system logic: level high)
- all other circuits = ON: - UA > 3 V (system logic: level low)
- all other circuits = OFF: - UA < -3 V (system logic: level high)
User data rates available nx64 kbit/s synchronous, n = 1 to 30, with CAS r2g
nx64 kbit/s synchronous, n = 1 to 32, without CAS
nx64 kbit/s oversampling 1, n = 1 to 30, with CAS
nx64 kbit/s oversampling 1, n = 1 to 32, without CAS
< 64 kbit/s synchronous r2e
≤ 38.4 kbit/s asynchronous
64 kbit/s transition coding 2 r2f
Maximum line length at the maximum available 15 m with contradirectional timing r1a
data rate 50 m with codirectional timing
20 m if V.28 signals are used

1. The effective user data rate should be at least three to four times lower than the oversampling frequency.
2. The effective user data rate should be at most 19.2 kbit/s.

Copyright 2022 Hitachi Energy. All rights reserved. 19

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 9: RS485 DCE physical layer functions and specifications

Feature Rating or standard Release
Interface circuits RS485 4-wire - 102 GND signal ground or common return r1a
(unused circuits are kept in the OFF state) - 103 TxD transmitted data
- 104 RxD received data

The signal 103 acts as a single receiver with multiple

drivers (DTEs).
The signal 104 acts as a single driver with multiple
receivers (DTEs).

Note: The signals 103 and 104 shall not be con-

nected together outside LEDS1.
Interface circuits RS485 2-wire - 102 GND signal ground or common return r1a
(unused circuits are kept in the OFF state) - 103/104TxD/RxD transmitted/received data

The signal 103 acts as a single receiver with multiple

drivers (DTEs).
The signal 104 acts as a single driver with multiple
receivers (DTEs).
- Signal direction to DCE circuits 103
- Signal direction from DCE circuits 104
Electrical characteristics r1a
- Circuit 103 as receivers according to RS485
- Bus terminating resistor of the circuit 103 125 Ω ± 10%

Note: It is assumed, that a second bus terminating

resistor with the same value as above is placed at
the end of the bus cables.
- Circuit 104 as transmitters according to RS485
Polarities r1a
- 103, 104 = 0: - UA-UB> 0.2 V(system logic: level low)
- 103, 104 = 1: - UA-UB< -0.2 V(system logic: level high)
User data rates available 0 to 600 kbit/s in oversampling mode r2g
nx64 kbit/s oversampling 1, n = 1 to 30, with CAS
nx64 kbit/s oversampling 1, n = 1 to 32, without CAS
Maximum line length at the maximum available 50 m r1a
data rate

1. The effective user data rate should be at least three to four times lower than the oversampling frequency.

3.5 MAC Bridging

Table 10: MAC bridging functions and specifications
Feature Rating or standard Release
Ethernet ports r2a
- Number of Ethernet ports 1
electrical
- Interface type 10BASE-T/100BASE-TX
- Interface mode Auto - MDI/MDI-X
- Electrical connection Connector RJ-45
Impedance 100 ± 15 Ω for the frequency band
from 1 to 100 MHz

Copyright 2022 Hitachi Energy. All rights reserved. 20

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 10: MAC bridging functions and specifications (continued)

Feature Rating or standard Release
Ethernet traffic layers r2a
- Ethernet modes - 10BASE-T half duplex
- 10BASE-T full duplex
- 100BASE-TX half duplex
- 100BASE-TX full duplex
- Autonegotiation
- Bridging Transparent MAC bridging according to IEEE
802.1D, using one bridge instance.
Note: The spanning tree protocol is not sup-
ported.
- Packet forwarding Packets are forwarded from the LAN to the WAN
port and vice versa, i.e. between the Ethernet
interfaces and the P0-nc or P12 channel.
Packets that can not be forwarded are dis-
carded:
- filtered according to the information in the
bridge hash table.
- lack of system resources
- MAC learning Dynamic MAC address table, 4000 entries.
- Frame format IEEE Std. 802.3-2005
- Frame size up to 1600 Bytes
- Ingress buffer sizes (towards TDM port) 4x 64 frames
- Egress buffer size (towards Ethernet port) 128 frames
- Number of ingress queues 4
- Number of egress queues 1
- Support of profiles for the ingress queue mapping
- Throughput over P0-31c, frame size 64 to 1’518 1.9 Mbit/s r2a
bytes
WAN protocols r2a
- HDLC HDLC is used as logical link control protocol as
underlying layer of the MAC frames.

3.6 General Functions and Specifications

Table 11: General functions and specifications
Feature Rating or standard Release
Front connectors data interface Metral ® r1a
4x6 male contacts
Front connector Ethernet interface RJ-45 r1a
No hardware settable options on the unit All unit parameters are software settable with r1a
the element manager
Hot swapping You can replace a LEDS1 unit without interfering r1a
with any other units. No actions on powering, con-
figuration or commissioning need to be taken if you
remove/replace a LEDS1 unit
PBUS access 32 x P12 r1a
Cross connections Flexible cross connections to any other FOX61x r2g
TDM unit on the P0_nc or P12 traffic layer

Copyright 2022 Hitachi Energy. All rights reserved. 21

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 11: General functions and specifications (continued)

Feature Rating or standard Release
Conferences Logical addition of the data signals: r1a
- Wired-AND
Logical addition of the CAS signaling signals:
- Wired-AND
- Conference type Multipoint-to-multipoint,
Point-to-multipoint
Conferences nx64 kbit/s r1a
- Maximum number of conferences per unit 212 with up to 4 participants, 1x64 kbit/s
106 with up to 8 participants, 1x64 kbit/s
53 with up to 16 participants, 1x64 kbit/s
- Maximum number of participants per conference 16, 1 … 31x64 kbit/s
- Maximum bandwidth per participant 31x64 kbit/s
- Maximum bandwidth per conference 496x64 kbit/s
- Maximum bandwidth per unit 848x64 kbit/s
Conferences subrate In addition to the nx64 kbit/s conferences r2e
- Maximum number of conferences per unit 3 with up to 4 participants
1 with up to 8 participants
1 with up to 12 participants
- Maximum number of participants per conference 12
Equipment protection r1a
- Switching type 1:1 equipment protection
- Protection mode non revertive
- Switching time 1 conference:
< 6 s with removal of the active unit
< 1 s with manual or forced switching
212 conferences:
< 60 s
Traffic protection r1a
- Linear trail protection 1+1 unidirectional, revertive
1+1 unidirectional, non revertive
- SNC/I protection 1+1 unidirectional, revertive
1+1 unidirectional, non revertive
- Switching time < 50 ms
Performance monitoring G.826 parameters r1a
Octet slips
Protection switchover events
MIB-2 statistics r2a
Alarm reporting ITU-T X.733 (1992) r1a
Information technology – open systems inter-
connection – systems management: Alarm
reporting function
Maintenance r1a
- Test pattern insertion Per user port and conference participant
- Out of service Per user port and conference participant
Loops Data and signaling r1a
- Loop 2b Remote loop, back-to-back
- Loop 3b Local loop, front-to-front
- Loop 3c Local loop, front-to-front

Copyright 2022 Hitachi Energy. All rights reserved. 22

FOX61x | LEDS1 FUNCTIONS AND SPECIFICATIONS

Table 11: General functions and specifications (continued)

Feature Rating or standard Release
Power consumption r1a
- Power supply range VBAT refer to [1KHW002460] System Description “FOX-
61x”
- Maximum current consumption, IVBAT 115 mA
VBAT = -48 V
- Maximum total power requirement from battery, 5.5 W
PTOT
VBAT = nominal voltage
Mechanical parameters r1a
- Construction practice 19 inch
- Height of unit (1 HU = 44.45 mm) 6 HU
- Width of unit (1 TE = 5.08 mm) 4 TE (1 slot)
- Size of the PCB (H x D) 233 mm x 220 mm
- Weight 400 grams
- RoHS Directive 2011/65/EU of the European Parlia-
ment and of the Council of 8 June 2011 on the
Restriction of the use of certain hazardous sub-
stances in electrical and electronic equipment
- WEEE Directive 2012/19/EU of the European Parlia-
ment and of the Council of 4 July 2012 on waste
electrical and electronic equipment
Reliability r1a
- Calculated MTTF at 35 °C (MIL-HDBK-217F) 77 years
Emission refer to [1KHW002460] System Description “FOX- r1a
61x”
Immunity refer to [1KHW002460] System Description “FOX- r1a
61x”
Safety refer to [1KHW002460] System Description “FOX- r1a
61x”
Ambient conditions refer to [1KHW002460] System Description “FOX- r1a
61x”

Copyright 2022 Hitachi Energy. All rights reserved. 23

FOX61x | LEDS1 INSTALLATION

4 Installation

4.1 Prerequisites
Before installing a LEDS1 unit take care to follow the safety advice as listed in [1KHW002497]
Operating Instruction “Precautions and safety”.
Valid combinations of hardware (HW) and embedded software (ESW) versions are given in
[1KHW028777] Release Note “FOX61x”.
For the installation of FOX61x HW
refer to [1KHW002461] Installation Instruction “FOX615 R2 and FOX615 Installation”, or
refer to [1KHW002462] Installation Instruction “FOX612 Installation”.

4.2 Slots and Deployment Scenarios for the LEDS1 Unit

The LEDS1 unit uses one slot in the FOX61x subrack.
In a FOX61x, the LEDS1 unit can be operated in any of the following slots:
• FOX615 R2 and FOX615: 1 … 10, 12 … 21.
• FOX612: 7 … 10, 12 … 14.
Slot 11 is reserved for the working core unit.
In maximum 20 LEDS1 units (without network connection) can be operated in a FOX615 R2 or
FOX615. The number of LEDS1 units is reduced when using TDM transport units as connection
to the TDM network.
FOX615 R2 and FOX615
Slot Slot Slot
1 11 21

L L L L L L L L L L C L L L L L L L L L S TDM
E E E E E E E E E E U E E E E E E E E E A
Network
D D D D D D D D D D D D D D D D D D D M
S S S S S S S S S S S S S S S S S S S O
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

n x 2 Mbit/s

Figure 4: FOX615 R2 or FOX615 subrack with 19 LEDS1 units and 1 SAMO1 unit

The example above shows a FOX615 R2 or FOX615 subrack equipped with 19 LEDS1 units,
i.e. 76 user data ports, which can be transported over a number of 2 Mbit/s links over the TDM
network. CU is the core unit.

Copyright 2022 Hitachi Energy. All rights reserved. 24

FOX61x | LEDS1 INSTALLATION

FOX612
Slot Slot Slot
7 11 14

L L L L C L L L
E E E E U E E E TDM
D D D D D D D Network
S S S S S S E
1 1 1 1 1 1 1

n x 2 Mbit/s

Figure 5: FOX612 subrack with 6 LEDS1 units and 1 LEDE1 unit

The example above shows a FOX612 subrack equipped with 6 LEDS1 units, i.e. 24 user data
ports, which can be transported over a number of 2 Mbit/s Pseudo Wires through a packet net-
work to another TDM network. CU is the core unit.

4.3 Interoperability and Compatibility

4.3.1 FOX61x Units

The deployment of a LEDS1 unit in FOX61x is compatible with any other FOX61x unit.

4.3.1.1 Interoperability of LEDS1 configured as DCE

Table 12: Interoperability with DATI1 + DTM-M CPE

Interworking Criteria Interworking units
DATI1 + DTM-M CPE
DCE interfaces X.24/V.11 Yes (X.21)
V.35 Yes
V.24/ V.28 Yes (n ≤ 2)
RS485 No 1
Interface rates n x 64 kbit/s Yes (n ≤ 31)
Subrates Yes
Network SNCP/I Yes (n ≤ 31)
functions LTP No
Point to multipoint No 2
Control signal Yes
transport 105 →
109
Control signal No
transport 108 →
107

1. Interoperability is possible if the remote side DCE interface is not RS485.

2. It is possible to connect a DTE attached to a DATI1 port to a LEDS1 con-
ference.

Copyright 2022 Hitachi Energy. All rights reserved. 25

FOX61x | LEDS1 INSTALLATION

4.3.1.2 Interoperability of LEDS1 configured as MAC bridge

Table 13: Interoperability with EPSI1, DATI1 + DTM-M CPE

Interworking Interworking units
Criteria EPSI1 DATI1 + DTM-M
CPE
LAN-WAN bridge Supported Supported
HDLC
WAN-WAN bridge Supported Not supported
Maximum frame 1500 1600
length
WAN interface n ≤ 31 n ≤ 31
nx64 kbit/s

4.3.2 FOX51x Units

4.3.2.1 Interoperability of LEDS1 configured as DCE

Table 14: Interoperability with DATAx, UNIDA, SULIC + NTU, STICx + DTM-M CPE
Interworking Criteria Interworking units
DATAx UNIDA SULIC + STICx +
431 - 438 NTU DTM-M CPE
DCE interfaces X.24/V.11 DATAS, DATAT, 433/436/438 Yes Yes (X.21)
DATA1, DATA5
V.35 DATAS, DATAV, 432/437 Yes Yes
DATA3, DATA5
V.24/ V.28 DATAS, DATAR, 431 Yes (n ≤ 2) Yes (n ≤ 2)
DATA4, DATA5
RS485 DATAS, DATA5 No 1 No 1 No 1
Interface rates n x 64 kbit/s Yes (n ≤ 31) Yes (n ≤ 31) Yes (n ≤ 2) Yes (n ≤ 31)
Subrates Yes Yes Yes Yes
Network SNCP/I DATAS, DATAR, 431, 432/437, Yes (n ≤ 2) Yes (n ≤ 31)
functions DATAT, DATAV 433/436
LTP DATAS, DATAR, 431, 432/437, Yes (n ≤ 2) No
DATAT, DATAV 433/436
Point to multi- DATAS, DATAR, 431, 432/437, Yes (n ≤ 2) Yes (n ≤ 31)
point DATAT, DATAV 433/436
Control signal Yes Yes Yes 2 Yes
transport 105
→ 109
Control signal Yes 2 Yes 2 Yes 2 No
transport 108
→ 107

1. Interoperability is possible if the remote side DCE interface is not RS485.

2. Control signal transport is available for subrates only.

Copyright 2022 Hitachi Energy. All rights reserved. 26

FOX61x | LEDS1 INSTALLATION

4.3.2.2 Interoperability of LEDS1 configured as MAC bridge

Table 15: Interoperability with DATAx, ETER1, LAWA4, LEMU6, STICx + DTM-M CPE
Interworking Criteria Interworking units
DATAx ETER1 LAWA4, STICx +
LEMU6 DTM-M CPE
LAN-WAN bridge HDLC Supported Supported Not supported Supported
WAN-WAN bridge Not supported Supported Supported Not supported
Maximum frame length 1600 1500 1500 1600
WAN interface nx64 kbit/s n ≤ 31 n ≤ 31 n ≤ 31 n ≤ 31

4.3.3 Previous ESW Revisions

The LEDS1 unit with ESW release leds1_r2g is compatible to the previous ESW release. New
configuration parameters get their default values.
For the compatibility information with the FOX61x system releases please refer to
[1KHW028777] Release Note “FOX61x”.

4.4 Connections and Cables

4.4.1 Connectors and Signals

The LEDS1 unit provides individual connectors for each of the five front interfaces. The four
DCE interface connectors use a 24 pin Metral connector, the Ethernet interface uses a RJ-45
connector.
The pin assignment of the five front panel connectors is shown in Figure 6 and in Table 16
below.
The Ethernet interface connector exhibits 2 LEDs indicating the status of the Ethernet connec-
tion:
• Upper LED (yellow): Blinking when a packet is received (activity LED).
• Lower LED (green): Steady light when the link is up and running (link LED).
There is no difference in the indications if the link is half or full duplex or if the link speed is
10BASE-T or 100BASE-TX.

Copyright 2022 Hitachi Energy. All rights reserved. 27

FOX61x | LEDS1 INSTALLATION

R1A Connector port-5

37900358
untiltet front view

pin 1

pin 8

port-5

Connectors port-1 to port-4

port-4 untiltet front view

A B C D
1
port-3
2

4
port-2
5

6
port-1
Notch for the cable
latching clip

Figure 6: Front view of the front panel connectors

Please note:
The connectors of port-1 to port-5 are tilted by 39°.
The pin assignment of the DCE connector is dependent of the configured interface type:

Table 16: DCE interface connectors

Pin X.24/V.11 V.35 V.24/V.28 RS485
A1
A2 103a 1
A3 103b 1
A4 Ta 103a 103

Copyright 2022 Hitachi Energy. All rights reserved. 28

FOX61x | LEDS1 INSTALLATION

Table 16: DCE interface connectors (continued)

Pin X.24/V.11 V.35 V.24/V.28 RS485
A5 Tb 103b
A6 Ground Ground Ground Ground
B1 141 141
B2 X/B/Fa 113a 113
B3 X/B/Fb 113b
B4 Ra 104a 104 104a 2
B5 Rb 104b 104b 2
B6 Ground Ground Ground Ground
C1 Ca 105 105
C2 Cb
C3 Ia 109 109
C4 Ib
C5 114a 114
C6 114b
D1 107 107
D2 108 108
D3 106 106
D4 142 142
D5 Sa 115a 115
D6 Sb 115b

1. In the RS485 2-wire mode this pin is used for transmit and receive.
2. In the RS485 2-wire mode this pin is not used.

The pin assignment of the Ethernet connector is as follows:

Table 17: Ethernet interface connector

Pin MDI MDI-X
1 Tx+ Rx+
2 Tx- Rx-
3 Rx+ Tx+
4 - -
5 - -
6 Rx- Tx-
7 - -
8 - -

4.4.2 DCE Cables

For each interface type, cables are available which provide the adaptation of the universal unit
connector to the dedicated interface type connector:
Since no DCE connector is standardized for RS485 only the unterminated cable, i.e. without
connector, is offered for the RS485 interface type.
Cables are also offered without the dedicated interface connector, i.e. unterminated.
For details on LEDS1 cables, please refer to [1KHW002498] Product Guide “FOX61x cables”.

Copyright 2022 Hitachi Energy. All rights reserved. 29

FOX61x | LEDS1 INSTALLATION

Please note:
The latching clips of the unit side connectors must be positioned to the left side to
insert the connector correctly.

4.4.2.1 Cable for X.24/V.11 interfaces

• Terminated cable
A terminated cable is used to connect the X.24/V.11 data interface to the DTE. The DCE end
of the X.24/V.11 cable uses a 15-pole D-sub female connector, according to ISO 4903.
• Unterminated cable
An open ended or unterminated cable with 8 pairs is used to connect the X.24/V.11 data
interface to the MDF or can be equipped with a customer specific connector.

4.4.2.2 Cable for V.35 interfaces

• Terminated cable
A terminated cable is used to connect the V.35 data interface to the DTE. The DCE end of
the V.35 cable uses a 34-pole female connector, according to ISO 2593.

Please note:
The signal list of the V.35 interface is according to ITU-T V.36, i.e. the signals 113,
141 and 142 are added to the signal list of V.35. The circuit 108 has been added
from the V.24 signal list.
• Unterminated cable
An open ended or unterminated cable with 12 pairs is used to connect every pin of the data
interface connector to the MDF or can be equipped with a customer specific connector.

4.4.2.3 Cable for V.24/V.28 interfaces

• Terminated cable
A terminated cable is used to connect the V.24/V.28 data interface to the DTE. The DCE end
of the X.24/V.11 cable uses a 25-pole D-sub female connector, according to ISO 2110.
• Unterminated cable
An open ended or unterminated cable with 12 pairs is used to connect every pin of the data
interface connector to the MDF or can be equipped with a customer specific connector.

4.4.2.4 Cable for RS485 interfaces

• Unterminated cable
An unterminated cable with 4 pairs is used to connect the RS485 data interface to the MDF
or can be equipped with a customer specific connector.
Since no DCE connector is standardized for RS485 only the unterminated cable, i.e. without
connector, is offered for the RS485 interface type
It is up to the customer to attach the desired type of connector.

4.4.2.5 Cable accessing every connector pin

• Unterminated cable
An open ended or unterminated cable with 12 pairs is used to connect every pin of the data
interface connector to the MDF or can be equipped with a customer specific connector.

4.4.3 Ethernet Cables

The Ethernet interface layout is per default according to the host layout, but implements auto-
matic crossover functionality (MDI/MDI-X), i.e. it can adapt itself automatically to work with a
host or a switch. The interface therefore works with crossover and straight cables.

Copyright 2022 Hitachi Energy. All rights reserved. 30

FOX61x | LEDS1 INSTALLATION

The following media types are supported:

Table 18: Ethernet media types

IEEE standard Distance Media type
10BASE-T 100 m Category 5 SF/UTP or better
100BASE-TX 100 m Category 5 SF/UTP or better

Please note:
A straight Ethernet cable is available from Hitachi Energy.

4.4.4 Fixing the Cables to the Cable Tray

The cables must be attached to the cable tray of the FOX615 R2 and FOX615 or the corre-
sponding device of the FOX612.
The figure below shows the cable/cable tray assembly of the FOX615 R2 and FOX615.

Copyright 2022 Hitachi Energy. All rights reserved. 31

FOX61x | LEDS1 INSTALLATION

285 mm

Number
Length
Interface type

Number
Length
Interface type

235 mm

Number
Length
Interface type

205 mm

Number
Length
Interface type

175 mm

Figure 7: Side view of the FOX615 R2 and FOX615 cable tray and cables

Please note:
The cable route on the cable tray should follow approximately the projection of the
unit slot on the cable tray.
With the FOX612 the cable tray functionality is implemented differently and depends on the type
of installation (rack-, wall-mounted).
For more information on fixing the cables with the FOX612 refer to [1KHW002462] Installation
Instruction “FOX612 Installation”.

Copyright 2022 Hitachi Energy. All rights reserved. 32

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

5 Functional Description
This chapter gives the detailed functional description of the LEDS1 unit in the FOX61x subrack.

5.1 Data Interface Functions

5.1.1 DCE Interfaces

Each data port of the LEDS1 unit is individually configurable to one of the following DCE inter-
face types:
• X.24 / V.11
• V.35
• V.24 / V.28
• RS485 4-wire
• RS485 2-wire
The following data, control and timing signals are available, depending of the interface type and
the transmission mode:

Table 19: Data, control and timing signals with their electrical characteristics 1
Signal description Signal Signal DCE interface type DCE interface type
X.24 / V.24 type direc- synchronous asynchronous or oversam-
tion pling or transition coding
X.24/ V.35 2 V.24/ RS485 X.24/ V.35 2 V.24/ RS485
V.11 V.28 V.11 V.28
Signal ground or com- - - G 102 102 - G 102 102 102
mon return - - - - - - -
Transmit / Transmitted Data to T 103 103 - T 103 103 103
data DCE (V.11) (V.35) (V.28) (V.11) (V.35) (V.28) (RS485)
Receive / Received data Data from R 104 104 - R 104 104 104
DCE (V.11) (V.35) (V.28) (V.11) (V.35) (V.28) (RS485)
Control / Request to Control to C 105 105 - C 105 105 -
send DCE (V.11) (V.28) (V.28) (V.11) (V.28) (V.28)
- / Ready for sending Control from - 106 106 - - 106 106 -
DCE (V.28) (V.28) (V.28) (V.28)
- / Data set ready Control from - 107 107 - - 107 107 -
DCE (V.28) (V.28) (V.28) (V.28)
- / Data set to line Control to - 108 108 - - 108 108 -
DCE (V.28) (V.28) (V.28) (V.28)
Indication / Data channel Control from I 109 109 - I 109 109 -
received line signal detec- DCE (V.11) (V.28) (V.28) (V.11) (V.28) (V.28)
tor
DTE transmit signal ele- Timing to X 3, 4 113 4 113 4 - - - - -
ment timing / Transmit- DCE (V.11) (V.35) (V.28)
ter signal element timing
(DTE)
Signal element timing / Timing from S 114 114 - - - - -
Transmitter signal ele- DCE (V.11) (V.35) (V.28)
ment timing (DCE)
Signal element timing / Timing from S 115 115 - - - - -
Receiver signal element DCE (V.11) (V.35) (V.28)
timing (DCE)

Copyright 2022 Hitachi Energy. All rights reserved. 33

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Table 19: Data, control and timing signals with their electrical characteristics 1 (continued)
Signal description Signal Signal DCE interface type DCE interface type
X.24 / V.24 type direc- synchronous asynchronous or oversam-
tion pling or transition coding
X.24/ V.35 2 V.24/ RS485 X.24/ V.35 2 V.24/ RS485
V.11 V.28 V.11 V.28
Byte timing, Frame start Timing from B/F 3, 5 - - - - - - -
identification / Transmit- DCE (V.11)
ted character timing
- / Local loopback Control to - 141 141 - - 141 141 -
DCE (V.28) (V.28) (V.28) (V.28)
- / Test indicator Control from - 142 142 - - 142 142 -
DCE (V.28) (V.28) (V.28) (V.28)

1. Table entries in brackets designate the electrical interface characteristics.

2. The signal list of the V.35 interface is according to ITU-T V.36, i.e. the signals 113, 141 and 142 are added to the signal
list of V.35. The circuit 108/1 has been added from the V.24 signal list.
3. Only one of the X.24 signals X, B and F can be used at the same time since they all use the same connector pin.
4. Not available with subrates
5. With subrates only B is available.

Risk of operating trouble!

The byte and frame timing signals should only be used with user signals with a bit
rate ≤ 4x64 kbit/s. With higher user data rates the probability of timing problems is
increased.

Please note:
The transmit data or timing signals can not be used to synchronize the network ele-
ment.
The following table shows which functions are available in which combinations:

Table 20: Function relationship

Transmission User data rate Timing signal Transport DCE interface type
mode [kbit/s] [kHz] mode V.35 V.24/V.28 RS485
X.24/V.11
Asynchronous 0.6 … 38.4 0.6 … 38.4 Subrate yes yes no
Synchronous 0.6 … 56 0.6 … 56 Subrate yes yes no
Synchronous nx64 nx64, n ≤ 2 nx64 kbit/s yes yes no
Synchronous nx64 nx64, n ≤ 32 1 nx64 kbit/s yes no no
1, 2
Oversampling 0 … 128 nx64, n ≤ 32 nx64 kbit/s yes yes yes
1, 2
Oversampling 0 … 600 nx64, n ≤ 32 nx64 kbit/s yes no yes
Transition coding 0 … 19.2 256 2 64 kbit/s yes yes no

1. With CAS enabled the timing signal is n ≤ 30.

2. This signal is only used internally to sample the data signal. On the DCE interface none of the timing interchange circuits
will be activated.

The V.11 and RS485 receivers are terminated with a 125 Ω resistor.
The RS485 interface can be configured to 4-wire (full duplex mode) or to 2-wire (half duplex
mode). In the 4-wire mode the circuit 103 and circuit 104 must be connected to separate wire
pairs. In the 2-wire mode the connector pins of the transmit interface (103) are used:

Copyright 2022 Hitachi Energy. All rights reserved. 34

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

LEDS1 LEDS1
RS485 2-wire RS485 4-wire

Transmit 103 Transmit 103

Receive 104 Receive 104

Figure 8: RS485 2-wire and 4-wire modes

5.1.2 RS485 2-wire Control

With the RS485 2-wire interface type the receive and transmit data signals share the same wire
pair. Only half duplex transmission mode is allowed for the DTE and the DCE.
As a consequence the receive data driver (R/104) is active only when receive data has to be
applied to the line. During the receive idle phases the receive data driver is inactive, i.e. not driv-
ing.
The LEDS1 unit offers two possibilities to control the receive data driver:
• RTS controlled mode,
• Data controlled mode.
In order to avoid flow back of receive data to the transmit direction, the transmit data signal in
the DCE is fixed to “1” as long as the receive data driver is active.

5.1.2.1 RTS controlled mode

In the RTS controlled mode the receive data driver is kept active as long as the control signal
RTS (C, 105) from the remote end is active (“0”). The receive data driver is set to inactive as
long as the control signal RTS from the remote end is inactive (“1”).
The RTS (C, 105) from the remote end is transported in the CAS bit a, i.e. control signal trans-
port with CAS must be available and enabled.

Please note:
Control signal transport via CAS bits is a Hitachi Energy proprietary feature.

Please note:
The data port at the remote end must be configured to interface type X.24-V.11,
V.24-V.28 or V.35, since the interface type RS485 does not support the control sig-
nal interfaces.

5.1.2.2 Data controlled mode

In the data controlled mode the receive data driver is kept active as long as the data is 0 and for
a configurable timer period after the 0 to 1 data transition. After the expiry of the timer the
receive data driver is set to inactive.

Receive data R/104

timer period

Receive data driver enabled

timer expired

Figure 9: RS485 2-wire receive data driver control

Copyright 2022 Hitachi Energy. All rights reserved. 35

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

The timer period is configurable between 20 and 1500 samples of the oversampling clock rate.
The timer has to be set at least to the duration of the maximum continuous “1” period of the data
signal, during which the driver must be kept enabled.
Example:
Assume a data signal structure with a maximum of 9 consecutive “1” data bits. The data sig-
nal has a data rate of 64 kbit/s, the oversampling rate is 320 kbit/s.
The timer has to be set at least to 320/64 * 9 = 45 samples

Please note:
The data controlled mode requires knowledge of the data signal structure, i.e.
about the maximum length of “1” periods.

5.1.3 Transport Modes

5.1.3.1 Subrate transport mode

The LEDS1 DCE ports support synchronous and asynchronous subrates, i.e. user bit rates < 64
kbit/s, according to ITU-T V.110 and ITU-T X.30.
The subrate framing format is automatically set by LEDS1 according to the interface type config-
uration:
• With the V.35 and V.24/V.28 type interface, the subrate framing format is according to ITU-T
V.110.
• With the X.24/V.11 type interface, the subrate framing format is according to ITU-T X.30.

Please note:
The mapping of the user data to the X.30 frame is only byte synchronous if the byte
timing signal B is used.

Table 21: Supported subrates and framing formats

User data Synchronous Asynchro- ITU-T V.110 ITU-T X.30
rate nous
[bit/s]
600 yes yes yes yes
1’200 yes yes yes yes 1
2’400 yes yes yes yes
4’800 yes yes yes yes
9’600 yes yes yes yes
19’200 yes yes yes yes 1
38’400 yes yes yes yes 1
48’000 yes no yes yes
56’000 yes no yes yes 1

1. X.30 does not specify the user bit rate 1’200 bit/s, 19’200 bit/s, 38’400 bit/s and
56’000 bit/s. Nevertheless these user bit rates can be used with the LEDS1 unit also
for the X-type interfaces.

For the transport over the TDM network the subrate data signals are mapped to a synchronous
frame according to ITU-T V.110 for the V-type interfaces and according to ITU-T X.30 for the X-
type interfaces. The framed subrate signals have an intermediate signaling rate expressed by 2k
x 8 kbit/s, where k = 0, 1, 2 or 3.

Copyright 2022 Hitachi Energy. All rights reserved. 36

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Risk of operating trouble!

The user data rates 600, 1’200, 2’400 and 4’800 bit/s use all the same V.110 or
X.30 subrate frame format.
→ A mismatch of the user data rates configured for two connected user ports or
conference participants cannot be detected.
In a second step the X.30/V.110 frame is mapped into a 64 kbit/s time slot. Depending on the
user data rate 1, 2, 4 or 8 bits within the 64 kbit/s time slot are used.

Table 22: User data rate and bits used within a 64 kbit/s time slot
User data Intermedi- Frame length User data Time slot
rate ate rate [ms] bits per bits used
[bit/s] [kbit/s] frame
600 8 10 / 40 1 6 / 24 1
1’200 8 10 12 1
2’400 8 10 24 1
4’800 8 10 48 1
9’600 16 5 48 1-2
19’200 32 2.50 48 1-4
38’400 64 1.25 48 1-8
48’000 64 0.50 24 1-8
56’000 64 1.00 56 1-8

1. In order to maintain compatibility with the X.30 / 600 bit/s user rate, E7 is set to bi-
nary 0 in every fourth 80-bit frame, providing a frame length of 40 ms.

Please note:
The user bit rate 1’200 bit/s with X-type interfaces cannot provide the byte timing.
The X.30/V.110 frame contains overhead bits named S bits, E bits and X bit which are used to
transport control signal states, the actual user data rate indication and a remote alarm indica-
tion. For further information please refer to section 5.5.2 Subrate Framing Signaling Transport
(on page 62).

5.1.3.2 nx64 kbit/s transport mode

The LEDS1 DCE ports support synchronous nx64 kbit/s user data rates.
For the transport over the TDM network the nx64 kbit/s (n < 32) data signals are mapped to n
time slots in a G.704 framed 2048 kbit/s signal.
Depending on the usage of CAS up to 30 time slots or up to 31 time slots are available for the
user data transport.
For the transport over the TDM network the nx64 kbit/s (n = 32) data signals are mapped to a
“clock master P12 (2048 kbit/s) signal.

Please note:
The LEDS1 clock master signal must be connected to another clock master signal
on a P12 transport unit.
→ A connection to a P12 signal in transparent mode does not work.

5.1.4 Transmission Modes

5.1.4.1 Asynchronous mode

With subrates up to 38.4 kbit/s, LEDS1 supports the asynchronous mode according to ITU-T
V.14.

Copyright 2022 Hitachi Energy. All rights reserved. 37

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

The following start-stop character formats are supported:

Table 23: Asynchronous start-stop character formats

1 start 7 or 8 data bits 0 or 1 parity bit 1 or 2 stop bits
bit

Please note:
The parity bit is not evaluated in LEDS1, it is transported transparently.
In transmit direction, the asynchronous user data rate is adapted to the network element timing
(PETS) by deleting and adding stop bits. The maximum allowed frequency deviation is
• -2.5% to +1.0% with the basic range configuration, and
• -2.5% to +2.3% with the extended range configuration.
In receive direction, deleted stop bits are detected and regenerated by generating eight (basic
range) or four (extended range) stop bits with a reduced length.
Start-stop characters can follow each other without a gap or with a gap. Gaps are filled with stop
bits.
With the asynchronous mode, no timing signals (S/114/115, X/113, B, F) are available at the
DCE interface.

5.1.4.2 Synchronous mode

The synchronous mode is supported by LEDS1 for all subrates from 0.6 kbit/s to 56 kbit/s and
for the nx64 kbit/s user data rates.
In transmit direction, LEDS1 expects that the incoming user signal at the DCE interface is syn-
chronous to the network element timing (PETS).
The incoming subrate user data is mapped directly into the V.110/X.30 frame, i.e. without any
bit rate adaptation. The V.110/X.30 frame occupies 1 to 8 bits in a 64 kbit/s time slot.
The incoming nx64 kbit/s (n < 32) user data is mapped directly to n 64 kbit/s time slots, i.e. with-
out any bit rate adaptation.
The incoming nx64 kbit/s (n = 32) user data is mapped directly to a 2048 kbit/s signal, i.e. with-
out any bit rate adaptation.
In receive direction, the user data rate is derived from the network element timing. The data,
control and clock signals are fed to the DCE interface with this user data rate.
With the interface type X.24/V.11 and subrate user data, LEDS1 supports the byte timing signal
(B) at the DCE interface.
With the interface type X.24/V.11 and nx64 kbit/s user data, LEDS1 supports the byte timing (B)
or frame timing (F) signal at the DCE interface.

Please note:
Since the same DCE connector pins are used for the byte timing (B), the frame tim-
ing (F) and the codirectional transmit signal element timing (X), only one of these
three signals can be active at the same time.

5.1.4.3 Oversampling mode

The oversampling mode can be used to transport DCE signals with user data rates not corre-
sponding to the configurable subrates or nx64 kbit/s data rates. The user data signals can be
asynchronous (start-stop) signals or synchronous signals.
This mode can also be used to have low and constant delays with low user data rate signals.
In transmit direction, the data and control signals at the DCE interface are oversampled with a
(synchronous) clock, which is the configured interface clock rate. The oversampling frequency
has to be at least three to four times higher than the user data rate. The resulting isochronous
distortion corresponds to the relation of the user data rate to the oversampling frequency, e.g.
19.5% with a 25 kbit/s user data rate, oversampled with 2x64 kHz = 128 kHz (25/128 = 0.195).

Copyright 2022 Hitachi Energy. All rights reserved. 38

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

In receive direction, the data and control signals are output at the DCE interface with the over-
sampling clock.
The oversampling mode can be used in point-to-point, point-to-multipoint and multipoint-to-mul-
tipoint network applications. Refer to section 5.2 Network Applications (on page 42).

Please note:
With the V.24/V.28 interface, the data signal rate is limited to 128 kbit/s.

Please note:
In oversampling mode, no clock signal is available at the DCE interface.
If the DTE is working in synchronous mode, i.e. with clock signals, two cases must be consid-
ered:
1 The DTE delivers a clock signal (X, 113): A second DCE interface must be used to oversam-
ple and transport the clock signal to the remote DTE in parallel to the data signal. The clock
signal is handled the same as a data signal.
LEDS1 A LEDS1 B

Transmit T/104 Receive R/103

TDM
oversampling
Receive R/103 Network Transmit T/104

DTE A
DTE B
Clock X/113 Clock S/115
TDM
oversampling
Clock S/115 Network Clock X/113

Figure 10: Oversampling when DTE delivers a clock signal

2 The DTE requires a clock signal (S, 114, 115): A second DCE interface must be used to
oversample and transport the clock signal to the remote DTE. A third DCE interface must be
used to generate the required user clock signal.
This application is limited to the configurable user data rates of LEDS1 (0.6, 1.2, 2.4 …nx64
kbit/s).
LEDS1 A LEDS1 B

Transmit T/104 Receive R/103

over-
Receive R/103 sampling Transmit T/104
TDM
DTE A Network DTE B

Clock S/114/115 oversampling Clock S/114/115

user data rate

Figure 11: Oversampling when DTE delivers no clock signal

Copyright 2022 Hitachi Energy. All rights reserved. 39

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Please note:
Specifically tailored cables have to be used for the above applications.

5.1.4.4 Transition coding mode

The transition coding mode can be used to transport DCE signals with user data rates not corre-
sponding to the configurable subrates data rates. The user data signals can be asynchronous
(start-stop) signals or synchronous signals.
This mode can also be used to have low and constant delays with low user data rate signals.
In transmit direction, the data and control signals at the DCE interface are sampled with a (syn-
chronous) clock, which is four times the configured interface clock rate. Each signal transition is
coded with a three bit coding character in the transport signal:
• The first bit indicates the transition polarity.
• The second and third bits indicate the sampling position of the transition in the transport sig-
nal bit.
sampled in the sampled in the
2nd quarter 3rd quarter
Transmit user data signal

Sampling (256 kbit/s)

repeat the signal polarity repeat the signal polarity

Transport signal (64 kbit/s)

coding character coding character

Receive user data signal

regenerated in regenerated in
the 2nd quarter the 3rd quarter

Figure 12: Transition coding

Table 24: Transition coding characters

Transition Sampling position Coding character
Bit 1 Bit 2 Bit 3
0 to 1 1. quarter 1 1 1
2. quarter 1 0
3. quarter 0 1
4. quarter 0 0
1 to 0 1. quarter 0 0 0
2. quarter 0 1
3. quarter 1 0
4. quarter 1 1

The interface clock rate has to be at least three to four times higher than the user data rate. The
resulting isochronous distortion corresponds to the relation of the user data rate to the sampling
frequency, e.g. 7.5% with a 19.2 kbit/s user data rate, sampled with 256 kHz (19.2/256 = 0.075).
In receive direction, the data and control signals are output at the DCE interface with the sam-
pling clock.

Copyright 2022 Hitachi Energy. All rights reserved. 40

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Please note:
The transition coding mode is only supported for the 64 kbit/s interface clock rate:
→ Sampling frequency = 256 kHz
→ Maximum user data rate = 19.2 kbit/s

Please note:
The ITU-T R.111 framing and the transport of service bits are not supported by the
LEDS1 unit.
→ The transition coding mode supports the coding of the user data signal only.
The transition coding mode can be used in point-to-point, point-to-multipoint and multipoint-to-
multipoint network applications. Refer to section 5.2 Network Applications (on page 42).
If the DTE is working in synchronous mode, i.e. with clock signals, the clock handling is the
same as with the oversampling mode. Refer to section 5.1.4.3 Oversampling mode (on
page 38).

5.1.5 MAC Bridging

5.1.5.1 LAN modes

The port-5 on the front of the LEDS1 unit is a 10BASE-T/100BASE-TX Ethernet port supporting
the following LAN modes:
• Auto-negotiation
• 10 Mbit/s, Half duplex
• 10 Mbit/s, Full duplex
• 100 Mbit/s, Half duplex
• 100 Mbit/s, Full duplex

Risk of operating trouble!

The LAN mode of the host connected to the LEDS1 Ethernet port must be config-
ured to the same PHY mode as the LEDS1 Ethernet port, e.g. both ports config-
ured to “auto-negotiation” or both ports configured to “100 Mbit/s full duplex”.
→ Mixed configurations result in a non operational state of the Ethernet interface.

5.1.5.2 WAN mode

The Ethernet frames are mapped to a nx64 kbit/s transport signal, constituting the WAN port to
the TDM network.
Depending on the usage of CAS up to 30 time slots or up to 31 time slots are available for the
user data transport.
The WAN port encapsulates the MAC frames from the Ethernet port into HDLC frames.

HDLC encapsulation at the

flag MAC frame FCS flag
WAN port

Figure 13: WAN encapsulation

5.1.5.3 Queues and priority mappings

In direction from the Ethernet port to the WAN port the LEDS1 unit offers four queues with a
size of 64 frames each. The queues can be used for the prioritisation of the user traffic accord-
ing to the 802.1p priority (VLAN priority) or the DSCP value.
In direction from the WAN port to the Ethernet port the LEDS1 unit offers one queue with a size
of 128 frames.

Copyright 2022 Hitachi Energy. All rights reserved. 41

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

LEDS1
Q1

Q2 priority to
PBUS
queue
Q3 mapping
TDM Ethernet
WAN port Q4 port

Figure 14: WAN encapsulation

The assignment of priorities to the four queues is controlled by a QoS mapping profile. Please
refer to section 6.1 Profiles (on page 83) for information about the profile handling and refer to
section 8.2 Profiles (on page 102) for the configuration of the profile parameters.
The LEDS1 unit supports four algorithms for the priority to queue mapping:
• IP
The DSCP field of the IP header determines the packet priority.
• MAC
The 802.1p priority bits of the MAC header determine the packet priority. Untagged packets
get the default priority assigned. The default priority value is configurable.
• IP Then MAC
The DSCP field of the IP header, if it exists, determines the packet priority. Otherwise the
802.1p priority bits determine the packet priority. Untagged packets get the default priority
assigned.
• MAC Then IP
The 802.1p priority bits of the MAC header, if they exist, determine the packet priority. Other-
wise the DSCP field of the IP header determines the packet priority.
The scheduling of the frames in the queues towards the TDM WAN interface uses the strict pri-
ority algorithm.
Packets in the higher priority queues are handled first. Packets in lower priority queues are only
processed when there are no packets left in the higher priority queue. Q1 is the highest priority
queue, Q4 is the lowest priority queue.

Please note:
The priority mechanism does not modify the Ethernet frames.

5.2 Network Applications

The main network applications with the LEDS1 unit are
• LEDS1 in a point-to-point application.
• LEDS1 in a point-to-multipoint application.
• LEDS1 in a multipoint-to-multipoint application.

5.2.1 Point-to-Point (P2P)

The point-to-point application connects one data interface (data and signaling) with another data
interface through a TDM network.
The connection can be protected with 1+1 SNC protection on the transport layer.

Copyright 2022 Hitachi Energy. All rights reserved. 42

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Network element 1 Network element 2

TDM
Network

data data
interface interface

P12 transport unit

LEDS1 unit

Figure 15: Point-to-point application with LEDS1

5.2.2 Point-to-Multipoint (P2MP)

In the point-to-multipoint mode of operation a master data terminal equipment (master DTE)
communicates via a data interface to several subordinated DTEs, the so called slave DTEs
through a TDM network.
Communication is established in the polling mode. The data signal from the master DTE is sent
simultaneously to all slave DTEs. The master DTE addresses one specific slave DTE. This
addressed DTE activates its transmit interface to respond to the polling request. After the com-
plete message transfer the slave DTE deactivates its transmit interface.
Collisions must be prevented by using suitable communication protocols between the DTEs.
The slave DTEs can be distributed across several FOX61x sites. The maximum number of
slave DTEs is therefore practically limited only by the communication protocol applied.
Using the RS485 interface type up to 32 RS485 unit loads can be connected to one LEDS1 user
port simultaneously.
Using the V.35, X.24/V.11 or V.24/V.28 interface type only one DTE can be connected to one
LEDS1 user port simultaneously.
The connection in the TDM network can be protected with 1+1 SNC protection on the transport
layer.
The combination of the data signals and the signaling is accomplished with one central confer-
ence (preferred solution for a star network) or with several conference circuits placed at all net-
work elements with connected slave DTEs (preferred solution for a linear network).

Please note:
The point-to-multipoint network setup supports the multi-master type network topol-
ogy.

5.2.2.1 Linear network setup

The point-to-multipoint application in a linear network connects one master data interface
located at one end of the linear network with several slave data interfaces through a TDM net-
work.
When the master terminal sends, it sends in direction towards the slaves, and all slave terminals
can receive the sent signal.
When a slave terminal sends, it sends in direction towards the master, and only the master can
receive the sent signal.

Copyright 2022 Hitachi Energy. All rights reserved. 43

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

The connection between any two network elements can be protected with 1+1 SNC protection
on the transport layer
It is also possible to implement a shared protection ring (SPR) for the protection of the complete
LEDS1 network. For further information please refer to [1KHW002467] User Manual “TDM Ser-
vices”.
to to
Master master Intermediate slave slave Tail end slave

Network element 1 Network element k Network element n

TDM TDM
Network Network

data data
interface local
interface
master data
interface
P12 transport unit

Conference on
LEDS1 unit

LEDS1 unit

Figure 16: Point-to-multipoint linear application with LEDS1

5.2.2.2 Star network setup

The point-to-multipoint application in a star network connects one master data interface with
several slave data interfaces through a TDM network.
When the master terminal sends, it broadcasts towards the slaves, and all slave terminals can
receive the sent signal.
When a slave terminal sends, it sends in direction towards the master, and only the master can
receive the sent signal.
In case that more than one DTE is connected to a slave network element a local conference can
be setup at this location. This is shown in the Figure 17 below at the Slave 3 network element.
The connection between any two network elements can be protected with 1+1 SNC protection
on the transport layer

Copyright 2022 Hitachi Energy. All rights reserved. 44

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

to master Slave 1
to slave
Master or local

TDM data
1 1
Network interface

2
to master Slave 2
3

TDM data
1
Network interface

to
to master Slave 3
data master
interface TDM
master Network to slave
or local

P12 transport unit

1 2
Conference on
LEDS1 unit
data
interface
LEDS1 unit

data
interface

Figure 17: Point-to-multipoint star application with LEDS1

5.2.3 Multipoint-to-Multipoint (MP2MP)

The multipoint-to-multipoint mode of operation is very similar to the point-to-multipoint mode of
operation. Differences are outlined below.

Please note:
The multipoint-to-multipoint network setup supports the multi-master type network
topology.

5.2.3.1 Linear network setup

In the multipoint-to-multipoint application, when a slave terminal sends, it sends in direction
towards the master and towards the tail end slave, and all master and slave terminals can
receive the sent signal.

Please note:
At an intermediate slave in the multipoint-to-multipoint application the differentiation
between “to master” and “to slave” is done from a protocol point of view. The con-
ferencing is the same for all participants, irrespective if they are “local”, “to master”
or “to slave”.

Copyright 2022 Hitachi Energy. All rights reserved. 45

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

to to
Master master Intermediate slave slave Tail end slave

Network element 1 Network element k Network element n

TDM TDM
Network Network

data data
interface interface
master
local
data
P12 transport unit interface

Conference on
LEDS1 unit

LEDS1 unit

Figure 18: Multipoint-to-multipoint linear application with LEDS1

5.2.3.2 Star network setup

In the multipoint-to-multipoint application, when a slave terminal sends, it sends in direction
towards the master and towards the locally connected slaves, and the master forwards the
received signal to all other slaves. All the master and slave terminals can receive the sent sig-
nal.

Copyright 2022 Hitachi Energy. All rights reserved. 46

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

to
master Slave 1
to slave
Master or local

TDM data
1 1
Network interface

2
to
master Slave 2
3

TDM data
1
Network interface

to
to master Slave 3
data master
interface TDM
master Network to slave
or local

P12 transport unit

Conference on
1 2
LEDS1 unit

data
LEDS1 unit
interface

data
interface

Figure 19: Multipoint-to-multipoint star application with LEDS1

5.3 Conferencing

5.3.1 Resources

5.3.1.1 nx64 kbit/s conference resources

The LEDS1 unit has a fixed amount of resources available for nx64 kbit/s data conferences.
Each conference that is created consumes resources according to the maximum number of
conference participants and to the participants bandwidth.
• The maximum number of conference participants must be configured when the conference is
created. The following values are available:
− Maximum number of participants p = 4, or
− Maximum number of participants p = 8, or
− Maximum number of participants p = 16.
If later on a higher number of participants is required the conference must be deleted and
newly created with the appropriate maximum number of participants.
• The conference participants bandwidth must be configured when the conference is created.
The following values are available:
− Rate = 64 kbit/s, i.e. number of time slots n = 1, to

Copyright 2022 Hitachi Energy. All rights reserved. 47

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

− Rate = 1984 kbit/s, i.e. number of time slots n = 31.

The conference participants bandwidth can’t be modified.
The resources consumed by a conference is calculated with
RC = p x n, where
− p = number of participants
− n = number of time slots per participant
Example:
A conference with 8 participants and a participant bandwidth of 6x64=384 kbit/s requires
conference resources of
RC = 8 x 6 = 48 time slots.
The sum of all conference resources is restricted to 848 time slots per LEDS1 unit:
RU = Σ RC ≤ 848 time slots.
The maximum number of conferences with 4 participants is
C4max = 848/4 = 212.
The maximum number of conferences with 8 participants is
C8max = 848/8 = 106.
The maximum number of conferences with 16 participants is
C16max = 848/16 = 53.
Due to the fact that the building block for data conferences is a 16 participant conference with a
bandwidth of 1 time slot, one building block can be used to create
• one conference with 16 participants, or
• two conferences with 8 participants, or
• four conferences with 4 participants.
The following formulas apply for the calculation of the used conference resources, where np is
the number of time slots used in conferences with p participants:
• Number of conferences with 4 participants =
C4 = Σ n4 + Σ 2xn8 + Σ 4xn16
• Number of conferences with 8 participants =
C8 = round-up (Σ n4/2) + Σ n8 + Σ 2xn16
• Number of conferences with 16 participants =
C16 = round-up ((Σ n4/4) + (Σ n8/2)) + Σ n16
Example:
Assume four conferences:
− conference 1 with 4 participants and 192 kbit/s (n=3),
− conference 2 with 4 participants and 640 kbit/s (n=10),
− conference 3 with 8 participants and 320 kbit/s (n=5),

Copyright 2022 Hitachi Energy. All rights reserved. 48

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

− conference 4 with 16 participants and 1984 kbit/s (n=31),

The used resources are as follows:
C4 = Σ n4 + Σ 2xn8 + Σ 4xn16
= (3+10) + 2x5 + 4x31 = 147
C8 = round-up (Σ n4/2) + Σ n8 + Σ 2xn16
= round-up ((3+10)/2) + 5 + 2x31 = 74
C16 = round-up ((Σ n4/4) + (Σ n8/2)) + Σ n16
= round-up ((3+10)/4) + 5/2) + 31 = 37
The remaining resources are as follows:
C4 = 212 - 147 = 65, or
C8 = 106 - 74 = 32, or
C16 = 53 - 37 = 16.
conference 1, 3 time slots conference 2, 10 time slots
1
2 conference 3, 5 time slots
3
4
5
6 conference 4, 31 time slots
7

10

15
number of building blocks

20

25

30

35 remaining resources
37

40

45

50

53

building block (16 participants)

Legend:
conference, 4 participants, 1 time slot
conference, 8 participants, 1 time slot
conference, 16 participants, 1 time slot

Figure 20: Conference resource usage example with 4 conferences

Please note:
The remaining conference resources can be read from the LEDS1 unit status dia-
log.

Copyright 2022 Hitachi Energy. All rights reserved. 49

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

5.3.1.2 Subrate conference resources

In addition to the nx64 kbit/s conferences the LEDS1 unit offers subrate conferences. Also with
subrate conferences the amount of resources available is fixed. Each conference that is created
consumes resources according to the maximum number of conference participants.
• The maximum number of conference participants must be configured when the conference is
created. The following values are available:
− Maximum number of participants p = 4, or
− Maximum number of participants p = 8, or
− Maximum number of participants p = 12.
If later on a higher number of participants is required the conference must be deleted and
newly created with the appropriate maximum number of participants.

Please note:
The conference participants bandwidth must be configured when the conference is
created. The conference participants bandwidth can’t be modified.
The sum of all subrate conference participants is restricted to 12 per LEDS1 unit:
RU = Σ RC ≤ 12 participants
The following subrate conference configurations are possible:
• 1 conference with 12 participants, or
• 1 conference with 8 participants plus 1 conference with 4 participants, or
• 3 conferences with 4 participants.

Please note:
The remaining conference resources can be read from the LEDS1 unit status dia-
log.

5.3.1.3 PBUS resources

The LEDS1 unit accesses the PBUS (FOX61x TDM bus) with a maximum capacity of 32 P12
signals, each having 32 time slots. Five P12 signals are reserved for the user ports and 27 P12
are reserved for the conference participants.
Each participant can only access one P12 signal, i.e. it is not possible to split the participants
data signal to more than one P12 signal. This has the consequence that depending of the par-
ticipants bandwidths not the full available PBUS bandwidth can be used.
In the example below the remaining PBUS resources are:
• 7 participants with maximum 31x64 = 1984 kbit/s,
• 1 participant with maximum 27x64 = 1728 kbit/s,
• 2 participants with maximum 4x64 = 256 kbit/s,
• 24 participants with maximum 1x64 = 64 kbit/s.

Copyright 2022 Hitachi Energy. All rights reserved. 50

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

P12 TS
0 4 9 14 19 24 29 31
P12-0
5 x P12 reserved for user ports
P12-4

conference 1,
P12-9 4 participants,
3 time slots,
conference 2,
P12-14 4 participants,
10 time slots,
conference 3,
P12-19
8 participants,
5 time slots,
P12-24
conference 4,
16 participants,
31 time slots,
P12-29
P12-31 remaining resources

Legend:
conference participant with 31 time slots
conference participant with 10 time slots
conference participant with 5 time slots
conference participant with 3 time slots

Figure 21: PBUS resource usage example with 4 conferences

Please note:
A P12 resource with 32 free timeslots is shown as two remaining resources:
→ 1 participant with maximum 31x64 = 1984 kbit/s, and
→ 1 participant with maximum 1x64 = 64 kbit/s.
To make best use of the available PBUS bandwidth, the resource usage strategy must be taken
into account when creating conferences. The resource usage strategy is as follows:
• The P12 resources for conferences are grouped, according to the PBUS line usage. Each
PBUS line multiplexes 4 P12 resources:
− group 1: P12-5 to P12-7 (only 3 P12 resources),
− group 2: P12-8 to P12-11,
− group 3: P12-12 to P12-15,
− group 4: P12-16 to P12-19,
− group 5: P12-20 to P12-23,
− group 6: P12-24 to P12-27,
− group 7: P12-28 to P12-31.
• The groups are populated with participants from group 1 to group 7. A new group is
accessed when there are no remaining resources left for a participant.
• Each group is populated with participants
− first from the lowest numbered timeslot on any of the groups P12 to the highest numbered
timeslot, and
− second from the groups lowest numbered P12 to the highest numbered P12.
Example with conference 3 (8 participants, 5 timeslots):
• The group 1 is occupied with conference 1 and conference 2 as follows:
− P12-5: timeslot 0 to timeslot 15,
− P12-6: timeslot 0 to timeslot 22,
− P12-7: timeslot 0 to timeslot 12.

Copyright 2022 Hitachi Energy. All rights reserved. 51

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

• Participant-1 of conference-3 is placed on timeslots 13 to 17 of P12-7.

• Participant-2 of conference-3 is placed on timeslots 16 to 20 of P12-5.
• Participant-3 of conference-3 is placed on timeslots 18 to 22 of P12-7.
• Participant-4 of conference-3 is placed on timeslots 21 to 25 of P12-5.
• Participant-5 of conference-3 is placed on timeslots 23 to 27 of P12-6.
• Participant-6 of conference-3 is placed on timeslots 23 to 27 of P12-7.
• Participant-7 of conference-3 is placed on timeslots 26 to 30 of P12-5.
• Participant-8 of conference-3 has to be placed in group 2 since the maximum available
resource in group 1 is 4 timeslots in P12-6 and P12-7. It is placed on timeslots 0 to 4 of P12-
8.

Please note:
Only created participants make use of PBUS resources.
→ The parameter “maximum number of participants” of a conference does not
influence the PBUS resource usage.

Please note:
The remaining PBUS resources usable for additional participants can be read from
the LEDS1 unit status dialog.

5.3.2 Local Conferences

Conferences are accessible for local participants, i.e. from LEDS1 ports or any other data unit in
the network element. The conferences include also the participants from the “to master” and “to
slave” direction, i.e. from other network elements, transported via the TDM network.
The data conference function performs the addition of the data signals. The data signals are
combined with a wired-AND operation. The wired-AND requires all inactive terminals to send a
continuous “1”-signal.
It is possible to control the data access of a participant to the conference by the associated C/
105 control signal. Refer to section 5.3.5 Conference Control (on page 54) for further informa-
tion.
The control signals transported in the CAS a and b bits or in the subrate frame bits S, SA and
SB of all participants are combined in a wired-AND function, i.e. if any of the participants exhib-
its an active state (CAS-bit = 0 or S, SA, SB bit = 0), this active state is inherited to the com-
bined CAS signal.

Copyright 2022 Hitachi Energy. All rights reserved. 52

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Data
Data
Data
AND
64 kbit/s subrate
master/ slave
P12 transport, participants 1+1 prot ection Control Control
e.g. LEDE1 switching,
cross connect
subrate AND 64 kbit/s

CAS CAS
P12 transport, remote
participants AND
e.g. LEDE1 conference

PBUS
LEDS1
local
LEDS1 participants

local
participants
1
local
DTM-M CPE DATI1 participants
nx64 kbit/s DCE
processing interface
Subrate 4
< 64 kbit/s

Figure 22: Local conference on LEDS1

5.3.3 Conferences in the P2MP Application

Conferences in the point-to-multipoint application add the data and control signals of the local
participants to the signal going towards the master. The Σ symbol stands for the wired-AND
function.
There is no addition in the direction to the last slave or towards the local participants.

to master to slave
PBUS

PBUS

local local
1 n

Figure 23: Conference in the P2MP application

5.3.4 Conferences in the MP2MP Application

Conferences in the multipoint-to-multipoint application consist of a number of sub-conferences.
The number of sub-conferences corresponds to the number of participants. The sub-conference
of each participant adds the data and control signals of all participants except the own signal.
The designation “to master” or “to slave” has no relevance for the conference itself, since the
setup is symmetrical in relation to the network directions. The “to master” and “to slave” partici-
pants are nevertheless required for the setup of the transport cross connections.

Copyright 2022 Hitachi Energy. All rights reserved. 53

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

to master to slave
PBUS

Σ Σ
1 2 3 4 n 1 2 3 4 n

1
2 2
3
4
n
Σ 1
3
4 Σ n

PBUS

local 2 3 4 local
1 n

Figure 24: Conference in the MP2MP application

5.3.5 Conference Control

In a conference all inactive participants must access the conference with a constant “1” signal
state. Only the active participant is allowed to access the conference with “1” and “0” signal
states.
There are two methods to have the inactive participants in the constant “1” state:
• Intrinsic access:
− In the inactive state the connected DTEs must send constantly a “1” state.
− If a slave DTE is polled from the master DTE it immediately can start to send.
• Controlled access:
− In the inactive state the connected DTEs must set the C/105 control signal to OFF. The
state of the C/105 control signal must be forwarded to the conference, i.e.
- the ports control signal “105 (RTS, C)” must be set to “From-DTE”,
- the ports “signaling to network” parameter must be set to “Yes”,
- the participants “signaling to conference” parameter must be set to “Yes”,
- the participants “signaling from conference” parameter must be set to “Yes”,
- the participants “conditional interconnection” parameter must be set to “Yes”.
The participants data signal entering the conference is set to “1”.
− If a slave DTE is polled from the master DTE it sets the C/105 control signal to ON. The
DCE (i.e. LEDS1 port) responds by setting the I/109 control signal to ON with a configu-
rable delay. Now the DTE can start to send. The participants data signal enters the con-
ference transparently.
To permit the master DTE to synchronize it is recommended to transmit a short bit sequence
(e.g. flag stream or idle code) from the slave DTE prior to the user data.

Please note:
The controlled access of a participant to a conference is only available if CAS is
available (nx64 kbit/s data rate) or if the subrate frame bits S or SB are available
(subrate).

Copyright 2022 Hitachi Energy. All rights reserved. 54

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Risk of operating trouble!

With subrates the LEDS1 at the master site has to resynchronize its V.110/X.30
frame every time a slave DCE starts its transmission (e.g. at 0.6 kbit/s it takes more
than a second to synchronize). This introduces a delay, depending of the user data
rate and can lead to problems since during resynchronization the data sent to the
master DTE is undefined.
→ Use the oversampling or the transition coding mode instead.

Risk of operating trouble!

There is a risk with subrates that data sent from the slave DTE to the master DTE
will be lost if a slave DTE switches its control signal 105/C to OFF simultaneously
with the last data byte. This is due to the delay in the V.110/X.30 subrate converter.
→ Use the oversampling or the transition coding mode instead.

Please note:
If using the control signal 109/I to enable the DTE transmitter the delay time in the
LEDS1 at the slave DTE location from control signal 105/C = ON to control signal
109/I = ON must be configured to at least 20 ms when using the oversampling or
the transition coding mode. With subrate transport the delay must be correspond-
ingly longer.
The DCE interfaces of LEDS1 are able to supervise the send time and idle time of the DTE and
to detach it from the connection point if the corresponding limits are exceeded. This prevents
that the system will be locked by a slave DTE which continuously sends data. Refer to section
7.4 DTE send and idle Time Restrictions (on page 96).

5.4 Data Handling

5.4.1 Port Data Handling

With each of the 4 user ports the LEDS1 unit offers a DCE interface with data, control and tim-
ing signals. The data signals are the transmit signal T/103 and the receive signal R/104.

Signal Signal Consequen t Out of

Squelch Loop 3c Loop 2b Loop 3b
monitor inver sion action service

T/103 1
1
0
0
1 Data signal
01
1 1 0
01 Processing 1 to PBUS

2-wire / Signal Signal Te st patt ern Out of Consequen t Prote ction

Loop 3c Loop 2b Loop 3b
4-wire monitor inver sion inser tion service action switch

1 Working data signal

Processing 0
fro m PBUS
R/104 1 1 Prote cting data signal
1
0 fro m PBUS
01
01

Figure 25: Data transport

The data handling can be configured with the following control and maintenance mechanisms:

Copyright 2022 Hitachi Energy. All rights reserved. 55

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

• Interface mode 2-wire or 4-wire:

The RS485 interface type can be configured to 2-wire mode, i.e. half duplex mode of the
RS485 bus, or to 4-wire mode, i.e. full duplex mode of the RS485 bus.
With the 2-wire mode the squelch function inserts a “1” signal in transmit direction as long as
the driver in receive direction is active.
All other interface types use the full duplex mode with separate transmit and receive signals.

Please note:
The signal monitoring status on the receive data signal shows the signal status
before the buffer in receive direction.
→ With the RS485 2-wire interface type and RTS controlled mode there can be
activity on the data signal also when the buffer in receive direction is disabled.
The activity is shown in the port status “To DTE” parameters.
• Data signal inversion (transmit signal T/103 and receive signal R/104):
In order to be compatible with DTEs using inverted logic, the transmit and the receive data
signal can be inverted individually.
• Consequent action (transmit signal T/103):
On a detected failure in the transmit data signal T/103 or the transmit timing signal X/113,
the data is replaced with a “1” or “0” signal. The consequent action can be disabled.
On a detected send or idle time filter violation the data is replaced with a “1” signal. The con-
sequent action can be disabled.

Please note:
The level detection on the transmit data signal T/103 is not available for the RS485
2-wire interface type.
• Loop 3c:
The maintenance function “Loop 3c” loops the transmit data signal back to the receive direc-
tion. For details please refer to section 7.2.3 Loop 3c (on page 94).
• Loop 2b:
The maintenance function “Loop 2b” loops the receive data signal back to the transmit direc-
tion. For details please refer to section 7.2.1 Loop 2b (on page 92).
• Loop 3b:
The maintenance function “Loop 3b” loops the transmit data signal back to the receive direc-
tion. For details please refer to section 7.2.2 Loop 3b (on page 93).
• Interface line state “out of service”:
The maintenance function “out of service” of an interface replaces the transmit signal going
to the PBUS by a “1” signal.
In receive direction the data signal from the PBUS is replaced by a “1” signal.
• Interface line state “test pattern insertion”:
The maintenance function “test pattern insertion” replaces in receive direction the data signal
by a continuous test pattern “1010”.
• Protection switching:
In receive direction a working and a protecting channel can be configured. Switching criteria
are “trail signal fail” and “trail signal degrade” from the P12 transport unit. With CAS enabled
in the CTP configuration, CAS AIS is an additional switching criterion.
• Consequent action (receive signal R/104):
On a detected failure in the receive signal the data is replaced with a “0” or “1” signal.

5.4.2 Conference Data Handling

The LEDS1 unit offers conferences with a maximum of 16 participants per nx64 kbit/s confer-
ence or a maximum of 12 participants per subrate conference. The transmit data signals of all

Copyright 2022 Hitachi Energy. All rights reserved. 56

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

participants are combined in a wired-AND function, i.e. if any of the participants exhibits an
active state (“0”), this active state is inherited to the combined data signal.
With subrates the data signals are extracted from the X.30 or V.110 frame before the addition.
The combined signal is reinserted into the X.30 or V.110 frame.
With X-interface type conferences the byte and frame timing is maintained.
In the multipoint-to-multipoint (MP2MP) application, all participants are handled identically. Each
participant has its own sub-conference. The sub-conference of each participant adds the data
signals of all participants except the own signal.

Te st patt ern Set out of Cond itional Signaling to Consequen t Prote ction
inser tion service interconnection conferen ce action switch

C/105

0 1 Working data signal

01
P1 1 from PBUS
Protecting data signal Part icipant 1:
1
1 from PBUS local or
to master or
P2
to slave
Σ
P3
data signal
Pn 1 to PBUS

Te st patt ern Set out of Cond itional Signaling to Consequen t Prote ction
inser tion service interconnection conferen ce action switch

C/105

0 1 Working data signal

01
P2 1 from PBUS
Protecting data signal Part icipant 2:
1
1 from PBUS local or
to master or
P1
to slave
Σ
P3
data signal
Pn 1 to PBUS

Te st patt ern Set out of Cond itional Signaling to Consequen t Prote ction
inser tion service interconnection conferen ce action switch

C/105

0 1 Working data signal

01
P3 1 from PBUS
Protecting data signal Part icipant 3:
1
1 from PBUS local or
to master or
P1
to slave
Σ
P2
data signal
Pn 1 to PBUS

Te st patt ern Set out of Cond itional Signaling to Consequen t Prote ction
inser tion service interconnection conferen ce action switch

C/105

0 1 Working data signal

01
Pn 1 from PBUS
Protecting data signal Part icipant n:
1
1 from PBUS local or
to master or
P1
to slave
Σ
P2
P3 data signal
1 to PBUS

Figure 26: Conference data transport, MP2MP

In the point-to-multipoint (P2MP) application, only the participant “to master” has a sub-confer-
ence, adding the data signals of all other participants except the own signal. The other partici-
pants (“local” or “to slave”) receive their data signal from the “to master” participant.

Copyright 2022 Hitachi Energy. All rights reserved. 57

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Te st patt ern Set out of Cond itional Signaling to Consequen t Prote ction
inser tion service interconnection conferen ce action switch

C/105

0 1 Working data signal

01
P1 1 from PBUS
Protecting data signal
1
1 from PBUS Part icipant 1:
to master
P2

Σ
P3
data signal
Pn 1 to PBUS

Te st patt ern Set out of Cond itional Signaling to Consequen t Prote ction
inser tion service interconnection conferen ce action switch

C/105

0 1 Working data signal

01
P2 1 from PBUS
Protecting data signal
1 Part icipant 2:
1 from PBUS
local or
to slave
P1 data signal
1 to PBUS

Te st patt ern Set out of Cond itional Signaling to Consequen t Prote ction
inser tion service interconnection conferen ce action switch

C/105

0 1 Working data signal

01
P3 1 from PBUS
Protecting data signal
1 Part icipant 3:
1 from PBUS
local or
to slave
P1 data signal
1 to PBUS

Te st patt ern Set out of Cond itional Signaling to Consequen t Prote ction
inser tion service interconnection conferen ce action switch

C/105

0 1 Working data signal

01
Pn 1 from PBUS
Protecting data signal
1 Part icipant n:
1 from PBUS
local or
to slave
P1 data signal
1 to PBUS

Figure 27: Conference data transport, P2MP

The data handling can be configured with the following control mechanisms:
• Participant configuration “signaling to conference”:
The “signaling to conference” parameter allows to control the forwarding of control signals
towards the conference. This parameter influences also the forwarding of the data signal in
case of the conditional interconnection (see below). If “signaling to conference” is set to “No”
the “conditional interconnection” parameter set to “Yes” disables the forwarding of the data
signal.
• Participant configuration “conditional interconnection”:
The conditional interconnection function allows to control the access of a participants data
signal to the conference by the signal state of the control signal C/105, which has to be avail-
able at the conference input, i.e. the port configuration must enable the forwarding of control
signals to the network (“signaling to network” = “Yes”) and the participant configuration must
enable the forwarding of control signals to the conference (“signaling to conference” = “Yes”.

Copyright 2022 Hitachi Energy. All rights reserved. 58

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

• Participant line state “out of service”:

The maintenance function “out of service” of a participant replaces the transmit signal going
to the PBUS by a “1” signal.
In receive direction the data signal from the PBUS is replaced by a “1” signal.
• Participant line state “test pattern insertion”:
The maintenance function “test pattern insertion” replaces in receive direction the data signal
by a continuous test pattern “1010”.
• Protection switching:
In receive direction a working and a protecting channel can be configured. Switching criteria
are “trail signal fail” and “trail signal degrade” from the P12 transport unit. With CAS enabled
in the CTP configuration, CAS AIS is an additional switching criterion.
• Consequent action (receive direction):
On a detected failure in the receive signal the data is replaced with a “1” signal.

5.5 Control Signal Handling

5.5.1 Overview
Depending on the interface type used different control signals are available. Refer to Table 19:
"Data, control and timing signals with their electrical characteristics" (on page 33).
• C/105 (to DCE)
In normal operation the control signal C/105 is used by the DCE as an indication that the
DTE is ready to transmit data.
With subrates, the state of the control signal C/105 is transported to the remote DCE in the
SB bit of the V.110 frame or S bit of the X.30 frame. Alternatively the state of the control sig-
nal 105 can be transported in the SA bit and the SB bit of the V.110 frame.
When using CAS the state of the control signal C/105 can be transported to the remote DCE
in the CAS a bit.
In order to be compatible with DTEs using inverted logic, the control signal can be inverted.
• 106 (from DCE)
The control signal 106 informs the DTE that it can start to send data.
The state of the control signal 106 can be controlled by the local control signal 105 with vari-
ous delay settings. The delay time can be configured to
− 0, 10, 20 or 40 ms.
The delay is active for the OFF to ON and ON to OFF state transitions.
With subrates the state of the control signal 106 can be controlled by the remote DCE via the
X bit of the V.110 or X.30 frame (loss of frame synchronization alarm). As long as the remote
DCE has no synchronization failure the control signal 106 is in the ON state and the local
DTE can transmit data.
• 107 (from DCE)
The control signal 107 informs the DTE that the remote DTE is in fault free operation.
With subrates the state of the control signal 107 can be controlled by the remote DTE via the
SA bit of the V.110 frame which transports the remote state of the control signal 108.
When using CAS the state of the control signal 107 can be controlled by the remote DCE via
the CAS b bit which transports the remote state of the control signal 108.

Copyright 2022 Hitachi Energy. All rights reserved. 59

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

• 108 (to DCE)

The control signal 108 is used to inform the DCE that the DTE is fault free and in operation.
With subrates and V-type interfaces, the state of the control signal 108 can be transported to
the remote DCE in the SA bit of the V.110 frame.
When using CAS the state of the control signal 108 can be transported to the remote DCE in
the CAS b bit.
• I/109 (from DCE)
The control signal I/109 is used to ready the DTE for receiving data from the DCE.
The state of the control signal I/109 can be controlled by the local control signal C/105 with
various delay settings. The delay time can be configured to
− 0, 10, 20 or 40 ms.
The delay is active for the OFF to ON and ON to OFF state transitions.
With subrates the state of the control signal I/109 can be controlled by the remote DCE via
the SB bit of the V.110 frame or the S bit of the X.30 frame which transports the remote state
of the control signal C/105.
When using CAS the state of the control signal 109/I can be controlled by the remote DCE
via the CAS a bit which transports the remote state of the control signal C/105.
LEDS1 Signal
inver sion

1 from DTE
C/105
ON
CAS a bit
OFF
V.110/SB bit
X.30/S bit

108 from DTE

ON
CAS b bit
OFF

V.110/SA bit

ΔT
TDM
DTE CAS b bit
Network
107
ON
OFF V.110/SA bit

CAS a bit
I/109
ON
V.110/SB bit
OFF X.30/S bit

106 V.110/X bit

ON
OFF

Figure 28: Control signal handling overview

The control signals can be configured according to the table below:

Copyright 2022 Hitachi Energy. All rights reserved. 60

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Table 25: Control signal handling

Control signal X.24 V.35 V.24
C/105 from DTE from DTE from DTE
ON, fixed ON, fixed ON, fixed
OFF, fixed OFF, fixed OFF, fixed
1 OFF, from defect 1 OFF, from defect 1
OFF, from defect
106 - from local 105 from local 105
from X bit (V.110) from X bit (V.110)
ON, fixed ON, fixed
OFF, fixed OFF, fixed
2 OFF, from defect 2
OFF, from defect
107 - from SA bit (V.110) from SA bit (V.110)
from b bit (CAS) from b bit (CAS)
ON, fixed ON, fixed
OFF, fixed OFF, fixed
2 OFF, from defect 2
OFF, from defect
108 - from DTE from DTE
ON, fixed ON, fixed
OFF, fixed OFF, fixed
1
OFF, from defect OFF, from defect 1
I/109 from local C from local 105 from local 105
from S bit (X.30) from SB bit (V.110) from SB bit (V.110)
from a bit (CAS) from a bit (CAS) from a bit (CAS)
ON, fixed ON, fixed ON, fixed
OFF, fixed OFF, fixed OFF, fixed
2 OFF, from defect 2 OFF, from defect 2
OFF, from defect

1. The control signal towards the network is set to OFF as a consequent action when
a defect is detected in the transmit data or clock signal from the DTE.
2. The control signal is set to OFF as a consequent action when a defect is detected
in the receive signal from the network and the signal is not fixed to ON.

Please note:
The S bit, SA bit, SB bit and X bit are only available with subrates. The 56 kbit/s
user data rate must use the V.110 framing with signaling.

Please note:
The a bit and the b bit are only transmitted to the PBUS when CAS is enabled, i.e.
when the “signaling to network” parameter is set to “yes”.

Please note:
With active loops the control signals are controlled according to the specific loop.
→ Refer to section 7.2 Loops (on page 91).

Please note:
The RS485 interface type supports no control signals.

Copyright 2022 Hitachi Energy. All rights reserved. 61

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

5.5.2 Subrate Framing Signaling Transport

The X.30 and the V.110 frames contain overhead bits named S bits, E bits and X bit which are
used to transport control signal states, the actual user data rate indication and a remote alarm
indication.

5.5.2.1 S bit usage

S bits are used to transport the status of selected DCE interface signals from the local DCE to
the remote DCE.
In transmit direction, in a first step the status of a control signal is mapped to an SA or SB indi-
cation (V.110) or to an S indication (X.30). In a second step the SA and SB indications are
mapped to the S1 to S9 (= Sx) bits in the V.110 frame or the S indication is mapped to the SP,
SQ and SR bits in the X.30 frame.
In receive direction the opposite procedure is used to control the corresponding DCE interface
signal.
For interoperability of a V-type DCE with a X-type DCE the control signal 105 can be mapped to
both the SA and SB indications.

Table 26: Control signal status to SA, SB and S mapping

DCE signal V.110 V.110 X.30 X.30
mapped to mapped mapped to mapped
from from
105 SB or
SB + SA
107 SA
108 SA
109 SB
C S
I S

LEDS1 A LEDS1 B
105 SB SB 109
DTE V.110 V.110 DTE
TDM
A 108 SA Network SA 107 B

LEDS1 A LEDS1 B

DTE C S X.30 X.30 S I DTE

TDM
A Network B

LEDS1 A LEDS1 B
105 SB
DTE V.110 X.30 S I DTE
TDM
A 108 SA Network B

Figure 29: Control signal status to SA, SB and S mapping

The number of available Sx bits depends of the bit rate:

Copyright 2022 Hitachi Energy. All rights reserved. 62

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Table 27: SA, SB and S to Sx mapping

SA/SB/S V.110 V.110 V.110 X.30
up to 38’400 48’000 bit/s 56’000 bit/s
bit/s
SA S1, S3, S6, S8 S1, S3 S3
SB S4, S9 S4 S4
S SP, SQ, SR

The frame formats of X.30 and V.110 are compatible. The S1 to S9 bits of the V.110 frame
occupy the places of the SP, SQ and SR bits of the X.30 frame.

Risk of operating trouble!

The S bit usage of the X-type interfaces is not compatible with the V-type inter-
faces.
→ Use the compatibility mode with the mapping of the control signal 105 to both
the SA and SB bits.

5.5.2.2 E bit usage

With the user data rates up to 38’400 bit/s, the E1 to E3 bits are used to indicate the local user
data rate to the far end. The transport of network independent clocking information in the E-bits
E4 to E6 is not supported.

Table 28: E bit usage

User data rate [bit/s] E1 to E3
600 100
1’200 010
2’400 110
4’800 011
9’600 011
19’200 011
38’400 011
48’000 not available
56’000 not available

With the 600 bit/s user data rate the E7 bit is always used for the multiframe alignment accord-
ing to ITU-T V.110, Table 5, Note 2.

5.5.2.3 X bit usage

The X bit in the V.110 and X.30 frame is used to transport the status of the X.30/V.110 frame
synchronization to the remote DCE:
− Frame synchronization OK: X bit = 0.
− Frame synchronization failed: X bit = 1.
The received X bit can control the status of the DCE signal 106.

Copyright 2022 Hitachi Energy. All rights reserved. 63

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

LEDS1 A LEDS1 B

DTE X V.110 V.110 X 106 DTE

A TDM B
Network
frame
alignment

LEDS1 A LEDS1 B

DTE X X.30 X.30 X DTE

A TDM B
Network
frame
alignment

Figure 30: Frame alignment status to X mapping

5.5.3 CAS Signaling Transport

The CAS provides the four signaling bits abcd. The bits a and b can be used to transport the
control signal status from the local DCE to the remote DCE.

Table 29: CAS bits usage

CAS bits abcd Description
1101 CAS bits not used (idle)
1xxx Control signal transport C to I (X-type),
Control signal transport 105 to 109 (V-type),
signal state OFF
0xxx Control signal transport C to I (X-type),
Control signal transport 105 to 109 (V-type),
signal state ON
x1xx Control signal transport 108 to 107 (V-type),
signal state OFF
x0xx Control signal transport 108 to 107 (V-type),
signal state ON
xx01 Default value
1111 Forward alarm indication (AIS)

LEDS1 A LEDS1 B
105 a bit a bit 109
DTE CAS CAS DTE
c TDM
A 108 b bit Network b bit 107 B

LEDS1 A LEDS1 B

DTE C a bit CAS CAS a bit I DTE

TDM
A Network B

Figure 31: Control signal status to a-bit and b-bit mapping

Copyright 2022 Hitachi Energy. All rights reserved. 64

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

The abcd bits of a time slot are sampled every 2 ms in the P12 transport signal.

Please note:
The control information is transported in the abcd bits only with the nx64 kbit/s
transport mode.
→ With subrate signals the S bit or the SA and SB bits of the X.30/V.110 frame are
used instead.

5.5.4 Port Control Signal Handling

With each of the 4 DCE interfaces the LEDS1 unit offers up to 3 control signal inputs and up to
4 control signal outputs, refer to Table 19: "Data, control and timing signals with their electrical
characteristics" (on page 33).

Fa ilure o n V/X Signaling Out of

Loop 3c Loop 2b Configuratio n Loop 3b
T/ 103 compa- to netw ork service
tibility

C/105
OFF
OFF
ON
OFF
108 X.30 frame, S bit
OFF V.110 frame, SB bit
OFF to PBUS
OFF
OFF
OFF
ON
OFF V.110 frame, SA bit
OFF
OFF to PBUS
OFF

CAS signaling
1101
1111 to PBUS
ΔT
Te st patt ern Consequen t Prote ction
Config Loop 3c Loop 2b Loop 3b Subra te
Out of service action switch

Working data signal

from PBUS
V.110/SA Protecting data
107 1111 signal from PBUS
ON OFF CAS b bit
OFF OFF

V.110/SB
I/109 X.30/S
ON OFF CAS a bit
OFF OFF

V.110/X

106 OFF
OFF
ON OFF
OFF

141 Loop
3c

Configur atio n

Loop state
142
ON
OFF

Figure 32: Control signal transport

The control signal handling can be configured with the following control and maintenance mech-
anisms:
• Consequent action on a failure of the T/103 data signal or of the X/113 timing signal:
On a detected failure in the transmit signal the control signals C/105 and 108 towards the
network are set to OFF.

Copyright 2022 Hitachi Energy. All rights reserved. 65

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

• Configuration in transmit direction:

The incoming control signals C/105 and 108 can be replaced by a fixed ON or OFF value.
• Loop 3c:
The maintenance function “Loop 3c” loops the control signal 108 back to the control signal
107 and loops the control signal C/105 back to the control signal I/109. In transmit direction
the control signals C/105 and 108 are set to OFF. The loop is near the DCE interface. For
details please refer to section 7.2.3 Loop 3c (on page 94).
• Loop 2b:
If the control signals C/105 or 108 are configured to “from DTE”, the maintenance function
“Loop 2b” loops the control signal I/109 received from the network back to the control signal
C/105 and loops the control signal 107 received from the network back to the control signal
108. If the control signals C/105 or 108 are not configured to “from DTE”, the control signals
C/105 and 108 towards the network remain unchanged.
In receive direction the control signals 107, I/109 and 106 are set to OFF. The loop is near
the DCE interface. For details please refer to section 7.2.1 Loop 2b (on page 92).
• Loop 3b:
The maintenance function “Loop 3b” loops the control signal 108 back to the control signal
107 and loops the control signal C/105 back to the control signal I/109. In transmit direction
the control signals C/105 and 108 are set to OFF. The loop is near the PBUS interface. For
details please refer to section 7.2.2 Loop 3b (on page 93).
• Control signal transport, transmit direction:
With subrates the state of the control signal C/105 is transported to the remote DCE via the
SB bit of the V.110 frame or the S bit of the X.30 frame.
In order to be compatible with a remote DCE of X-type, the state of the control signal C/105
can in addition also be transported via the SA bit of the V.110 frame. This is enabled with the
“V/X compatibility mode” parameter set to “Yes”.
With subrates the state of the control signal 108 is transported to the remote DCE via the SA
bit of the V.110 frame.
If CAS is used in the nx64 kbit/s mode the state of the control signal C/105 is transported to
the remote DCE via the CAS a bit and the state of the control signal 108 is transported to the
remote DCE via the CAS b bit. The CAS pattern is inserted in all positions of the used time
slots.
The transport of signaling information towards the network can be disabled with the “signal-
ing to network” parameter set to “No”:
− With subrates the SA and SB bits of the V.110 frame or the S bit of the X.30 frame are set
to OFF (“1”).
− In the nx64 kbit/s mode the CAS abcd pattern is the idle pattern “1101”.
• Interface line state “out of service”, transmit and receive direction:
In transmit direction the maintenance function “out of service” of an interface activates the
SD and SF signals. SF and SD are the FOX61x internal failure signals used to control the
protection switching.
With subrates the complete X.30 or V.110 frame is replaced by a “1” signal, i.e. the control
signals C/105 and 108 in the X.30 and V.110 frame are set to OFF.
If CAS is used the AIS-CAS pattern (1111) is inserted in all positions of the used time slots
In receive direction the control signals 106, 107 and I/109 are all set to OFF.
• Protection switching:
In receive direction a working and a protecting channel can be configured. Switching criteria
are “trail signal fail” and “trail signal degrade” from the P12 transport unit. With CAS enabled
in the CTP configuration, CAS AIS is an additional switching criterion.

Copyright 2022 Hitachi Energy. All rights reserved. 66

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

• Consequent action (receive control signals):

On a detected failure in the receive signal the data is replaced with a “1” or “0” signal (refer
to section 5.4.1 Port Data Handling (on page 55)). The CAS is replaced with the CAS-AIS
pattern. Consequently all control signals are set to OFF.
• Control signal transport, receive direction:
With subrates the state of the control signal I/109 can be controlled from the remote DCE via
the SB bit of the V.110 frame or the S bit of the X.30 frame.
With subrates the state of the control signal 107 can be controlled from the remote DCE via
the SA bit of the V.110 frame.
With subrates the state of the control signal 106 can be controlled from the remote DCE via
the X bit of the V.110 frame, indicating a loss of the V.110 frame alignment.
If CAS is used in the nx64 kbit/s mode the state of the control signal I/109 can be controlled
from the remote DCE via the CAS a bit and the state of the control signal 107 can be con-
trolled from the remote DCE via the CAS b bit. The CAS pattern of the first used time slot is
evaluated.
• Interface line state “test pattern insertion”:
The maintenance function “test pattern insertion” sets in receive direction the control signals
106, 107 and I/109 to OFF.
• Configuration in receive direction:
The outgoing control signal 106 can be replaced by a fixed ON or OFF value.
The outgoing control signal 107 can be replaced by a fixed ON or OFF value or can be con-
trolled by the control signal 108.
The outgoing control signal I/109 can be replaced by a fixed ON or OFF value or can be con-
trolled by the control signal C/105 with a configurable delay.

Please note:
The nx64 kbit/s mode not using CAS provides no means for the transport of control
signals to the remote DCE.
→ Use CAS to enable control signal transport. This is a Hitachi Energy proprietary
feature.
→ CAS is enabled when the configuration parameter “Signaling to network” is set
to “Yes”

Please note:
If a port requires CAS for the control signal transport CAS must be enabled on the
P12 transport signal.
→ The termination mode of the P12 transport signal must be set to “PCM30” or
“PCM30C”.

Risk of operating trouble!

It is possible to create a cross connection from a LEDS1 port using CAS to another
CTP not using CAS.
→ This would result in a non operational control signal transport.

5.5.5 Conference Control Signal Handling

The LEDS1 unit offers conferences with a maximum of 16 participants per nx64 kbit/s confer-
ence or a maximum of 12 participants per subrate conference. The transmit control signals of all
participants are combined in a wired-AND function, i.e. if any of the participants exhibits an
active state (ON), this active state is inherited to the combined control signal.
With subrates the control signals are extracted from the X.30 or V.110 frame before the addi-
tion. The combined signal is reinserted into the X.30 or V.110 frame.

Copyright 2022 Hitachi Energy. All rights reserved. 67

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

With nx64 kbit/s the control signals are extracted from the CAS a and b bits of the first used time
slot. The combined signal is reinserted into the CAS a and b bits in all positions of the used time
slots.
With X-interface type conferences the byte and frame timing is maintained.
In the multipoint-to-multipoint (MP2MP) application, all participants are handled identically. Each
participant has its own sub-conference. The sub-conference of each participant adds the control
signals of all participants except the own signal.

Copyright 2022 Hitachi Energy. All rights reserved. 68

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Te st patt ern Cond itional Signaling to Consequen t Prote ction

Subra te
Out of service interconnection conferen ce action switch

Working data signal

C/105 from PBUS
V.110/SB
0
X.30/S Protecting data
1111 signal from PBUS
CAS a bit
OFF
CB1 OFF
CA1
V.110/SA
OFF
X.30/S
CAS b bit
OFF
OFF
Participant 1:
Subra te Signaling fr om Out of local or
fra ming conferen ce service to master or
to slave

CB2 X.30 frame, S bit

&
CB3 OFF V.110 frame, SB bit
to PBUS
OFF
CBn V.110 frame, SA bit
OFF
CA2 to PBUS

&
CA3
CAS signaling
CAn
1101
1111 to PBUS

Te st patt ern Cond itional Signaling to Consequen t Prote ction

Subra te
Out of service interconnection conferen ce action switch

Working data signal

C/105 from PBUS
V.110/SB Protecting data
0
X.30/S 1111 signal from PBUS
CAS a bit
OFF
CB2 OFF
CA2
V.110/SA
OFF
X.30/S
CAS b bit
OFF
OFF
Participant 2:
Subra te Signaling fr om Out of local or
fra ming conferen ce service to master or
to slave

CB1 X.30 frame, S bit

V.110 frame, SB bit
&
CB3 OFF
to PBUS
OFF
CBn V.110 frame, SA bit
OFF to PBUS
CA1

&
CA3
CAS signaling
CAn
1101
1111 to PBUS

Te st patt ern Cond itional Signaling to Consequen t Prote ction

Subra te
Out of service interconnection conferen ce action switch

Working data signal

C/105 from PBUS
V.110/SB
0
X.30/S
Protecting data
1111 signal from PBUS
CAS a bit
OFF
CBn OFF
CAn
V.110/SA
OFF
X.30/S
CAS b bit
OFF
OFF
Participant n:
Subra te Signaling fr om Out of local or
fra ming conferen ce service to master or
to slave

CB1 X.30 frame, S bit

&
CB2 OFF
V.110 frame, SB bit
to PBUS
OFF
V.110 frame, SA bit
OFF
CA1 to PBUS

&
CA2
CAS signaling
1101
1111 to PBUS

Figure 33: Conference control signal transport, MP2MP

Copyright 2022 Hitachi Energy. All rights reserved. 69

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

In the point-to-multipoint (P2MP) application, only the participant “to master” has a sub-confer-
ence, adding the control signals of all other participants except the own signal. The other partici-
pants (“local” or “to slave”) receive their control signal from the “to master” participant.

Copyright 2022 Hitachi Energy. All rights reserved. 70

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Te st patt ern Cond itional Signaling to Consequen t Prote ction

Subra te
Out of service interconnection conferen ce action switch

Working data signal

C/105 from PBUS
V.110/SB
0 Protecting data
X.30/S
1111 signal from PBUS
CAS a bit
OFF
CB1 OFF
CA1
V.110/SA
OFF
X.30/S
CAS b bit
OFF
OFF

Subra te Signaling fr om Out of Participant 1:

fra ming conferen ce service to master

CB2 X.30 frame, S bit

&
CB3 V.110 frame, SB bit
OFF
to PBUS
OFF
CBn V.110 frame, SA bit
OFF to PBUS
CA2

&
CA3
CAS signaling
1101 to PBUS
CAn 1111

Te st patt ern Cond itional Signaling to Consequen t Prote ction

Subra te
Out of service interconnection conferen ce action switch

Working data signal

C/105 from PBUS
V.110/SB
0
X.30/S Protecting data
1111 signal from PBUS
CAS a bit
OFF
CB2 OFF
CA2
V.110/SA
OFF
X.30/S
CAS b bit
OFF
OFF
Participant 2:
Subra te Signaling fr om Out of local or
fra ming conferen ce service
to slave

X.30 frame, S bit

OFF V.110 frame, SB bit
CB1 to PBUS
OFF
V.110 frame, SA bit
OFF
to PBUS
CA1 CAS signaling
1101
1111 to PBUS

Te st patt ern Cond itional Signaling to Consequen t Prote ction

Subra te
Out of service interconnection conferen ce action switch

Working data signal

C/105 from PBUS
V.110/SB Protecting data
0
X.30/S
1111 signal from PBUS
CAS a bit
OFF
CBn OFF
CAn
V.110/SA
OFF
X.30/S
CAS b bit
OFF
OFF
Participant n:
Subra te Signaling fr om Out of local or
fra ming conferen ce service
to slave

X.30 frame, S bit

V.110 frame, SB bit
OFF
CB1 to PBUS
OFF
V.110 frame, SA bit
OFF to PBUS

CA1 CAS signaling

1101 to PBUS
1111

Figure 34: Conference control signal transport, P2MP

Copyright 2022 Hitachi Energy. All rights reserved. 71

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

The control signal handling can be configured with the following control mechanisms:
• Protection switching:
In receive direction a working and a protecting channel can be configured. Switching criteria
are “trail signal fail” and “trail signal degrade” from the P12 transport unit. With CAS enabled
in the CTP configuration, CAS AIS is an additional switching criterion.
• Consequent action:
On a detected failure in the receive signal the data is replaced with a “1” or “0” signal (refer
to section 5.4.2 Conference Data Handling (on page 56)). The CAS is replaced with the
CAS-AIS pattern. Consequently all control signals are set to OFF.
• Control signal transport, receive direction:
With subrates the SA and SB bits are demapped from the V.110 frame or the S bits are
demapped from the X.30 frame.
Note that with the X.30 frame the S bits are interpreted as if they were SA and SB bits of a
V.110 frame. This allows the interconnection with participants connected to a V.110 type
interface. It is up to the operator to configure the control signal 107 output at the data port
correspondingly, e.g. set it to OFF.
If CAS is used in the nx64 kbit/s mode the a and b bits are demapped from the CAS. The
CAS pattern of the first used time slot is evaluated.
The CAS a bit is alternatively used to the S or SB bit, the CAS b bit is alternatively used to
the SA bit.
Control signals can be blocked from accessing the conference circuit with the “signaling to
conference” parameter set to “No”. In this case the control signals are set to OFF.
If the “conditional interconnection” parameter is set to “Yes”, the control signals are only for-
warded to the conference if the SB bit or CAS a bit, corresponding to the control signal C/
105, is ON.
• Participant state “out of service”:
The maintenance function “out of service” of a participant simulates a failure of the partici-
pant in receive and transmit direction.
In transmit direction the maintenance function “out of service” of a participant activates the
SD and SF signals. SF and SD are the FOX61x internal failure signals used to control the
protection switching.
With subrates the control signals S, SA and SB are set to OFF in both directions.
In the nx64 kbit/s mode the a and b bits are set to OFF in receive direction. In transmit direc-
tion the CAS-AIS pattern (1111) is inserted in all positions of the used time slots.
• Participant state “test pattern insertion”:
With subrates the control signals S, SA and SB are set to OFF in receive direction.
If CAS is used in the nx64 kbit/s mode the a and b bits are set to OFF in receive direction.
• Control signal transport, transmit direction:
With subrates the SA and SB bits are mapped to the V.110 frame or the S bit is mapped to
the X.30 frame. In order to be compatible with a remote DCE of X-type, the state of the SB
bit can in addition also be mapped to the SA positions of the V.110 frame. This is controlled
with the Subrate framing” parameter set to “X.30”.
If CAS is used in the nx64 kbit/s mode the a and b bits are mapped to the CAS. The CAS
pattern is inserted in all positions of the used time slots.
Control signals can be blocked from accessing the network with the “signaling from confer-
ence” parameter set to “No”:
− With subrates the S, SA and SB bits are set to OFF.
− In the nx64 kbit/s mode the CAS pattern in transmit direction is replaced by the default
pattern (1101).

Copyright 2022 Hitachi Energy. All rights reserved. 72

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Please note:
The nx64 kbit/s mode not using CAS provides no means for the transport of control
signals to the remote DCE.
→ Use CAS to enable control signal transport. This is a Hitachi Energy proprietary
feature.
→ CAS is enabled with the following configuration parameters set to “Yes”:
“Signaling to conference”,
“Signaling from conference”.

Please note:
If a conference participant requires CAS for the control signal transport CAS must
be enabled on the P12 transport signal.
→ The termination mode of the P12 transport signal must be set to “PCM30” or
“PCM30C”.

Please note:
The X bit of the V.110 subrate frame is not logically added in the conference func-
tion.
→ The X bit is set according to the frame loss state in the participants termination
function.

Risk of operating trouble!

It is possible to create a cross connection from a LEDS1 conference participant
using CAS to another CTP not using CAS.
→ This would result in a non operational control signal transport.

5.6 Timing Handling

5.6.1 DTE Synchronization

In the connection to a DTE, LEDS1 acts as a DCE.

5.6.1.1 Codirectional timing

With codirectional timing the data signal is in both directions, to and from the DTE, accompanied
by its corresponding clock signal. The source for the receive timing signal is the DCE, the
source for the transmit timing signal is the DTE.
Since the LEDS1 expects the transmit data signal to be synchronous to the network element
timing (PETS), the transmit timing signal must be synchronized to the receive timing signal
inside the DTE (loop timing).

Transmitted data 103

Transmitter signal element timing (DTE) 113 LEDS1
DTE DCE
V-type Received data 104 V-type
Receiver signal element timing 115

Transmit T
DTE transmit signal element timing X LEDS1
DTE DCE
X-type Receive R X-type
Signal element timing S

Figure 35: Codirectional timing

Copyright 2022 Hitachi Energy. All rights reserved. 73

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

5.6.1.2 Contradirectional timing

With contradirectional timing the DCE is the source for the transmit and the receive timing sig-
nals.
With the X.24/V.11 interface type, the byte timing or frame start identification signal is available.

Transmitted data 103

Transmitter signal element timing (DCE) 114 LEDS1
DTE DCE
V-type Received data 104 V-type
Receiver signal element timing 115

Transmit T
LEDS1
DTE Receive R DCE
X-type Signal element timing S X-type
Byte timing B or frame start identification F

Figure 36: Contradirectional timing

Please note:
Contradirectional timing is problematic with higher user data rates, i.e. when the
delay time on the interconnection from the DCE to the DTE and back to the DCE is
in the range of a half unit interval (UI) of the user data rate. In this case the correct
sampling of the data signal can not be guaranteed with the fixed timing configura-
tion. The adaptive timing configuration should be used instead.

Please note:
The adaptive timing configuration should not be used together with the byte timing
since the timing relationship between signal element timing and byte timing is then
no more defined.

5.6.2 Port Timing Signals

Timing signals are used in the synchronous mode of the DCE interface. With the asynchronous,
oversampling and transition coding modes the timing signals are not used and are correspond-
ingly disabled.
All timing signals generated by the LEDS1 unit, i.e. 114, 115, S, B and F are synchronous to the
network element timing source, i.e. the PETS. The nx64 kHz and subrate timing signals are
derived with appropriate dividers from the PETS.
The frame timing signal F is synchronous to the G.704 frame on the PBUS. Frame timing is only
available for nx64 kbit/s signals.
The byte timing signal B is synchronous to the octet boundaries of the receive data signal.
Frame timing and byte timing are only available with the X-type DCE interfaces. They are exclu-
sively used with the DTE transmit timing signal X.

Please note:
Byte timing is not available with the user bit rate 1200 bit/s.

Copyright 2022 Hitachi Energy. All rights reserved. 74

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Signal Consequent Transmit

Loop 2b
monit or act ion timing

X/113

T/103
Δφ

B/ F Loop 2b B or F
Subrate
timing Configuration timing

X/B/F/113 B/F OFF Frame

timing

Byte
114 timing 1x64

S/115 subrate PBUS

timing
Timing from PBUS
nx64

Figure 37: Port timing signals

The timing signals can be configured with the following control and maintenance mechanisms:
• Signal monitor and consequent action:
The transmit timing signal X/113 is supervised for a loss of signal.
A missing clock signal X/113 is detected when LEDS1 counts at least 4xn (n ≤ 10, i.e. rate ≤
640 kbit/s) octet slips in 2.5 seconds. This corresponds to a clock offset of ± 200 ppm in rela-
tion to the network element timing. With n > 10, the number of octet slips to be counted is
fixed to 40.
As a consequent action a missing clock signal X/113 is replaced by the LEDS1 internal tim-
ing signal S/114.
The consequent action on the transmit data signal can be enabled or disabled.
If the consequent action is enabled
− the data signal T/103 is replaced by “1” or “0”,
− the control signals C/105 and 108 towards the network are set to “1” (i.e. “OFF”).
• B or F timing:
With X-type interfaces with synchronous user data rates the B/F/X timing signal can be dis-
abled, used as an input (X/113) or used as an output (B/F):
− None (B/F):
The B/F timing signal output is disabled or configured as an input to the LEDS1 and used
for the transmit signal synchronization.
− Byte Timing (B):
The B/F/X timing signal is configured as an output to the DTE and signals the last bit of
each data byte sent to the DTE on the receive user data signal.
− Frame Timing (F):
The B/F/X timing signal is configured as an output to the DTE and signals the beginning
of each frame of data bytes sent to the DTE on the receive user data signal.
• Transmit Timing

Copyright 2022 Hitachi Energy. All rights reserved. 75

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

DTE R/104
Q D LEDS1
S/115
S/114
T/103
D Q
Δφ
1 1 = contradirectional adaptive
2 2 = contradirectional fix
X/113 3 3 = codirectional

Figure 38: Transmit timing

The timing signal used for the LEDS1 internal sampling of the transmit user data signal T/
103 can be configured to the following modes:
− Contradirectional fix:
The transmit user data signal (T/103) is sampled with the timing signal S/114. The nomi-
nal delay from clocking out the receive data signal (R/104) to the sampling of the transmit
data signal (T/103) is half a bit width.
In this mode the signal X/113 is not used and the corresponding connector pins can be
used as byte/frame timing (B/F) signal output.
− Contradirectional adaptive:
The transmit user data signal (T/103) is sampled with a phase adjusted timing signal S/
114. The sampling phase is adjusted to the signal state changes of the transmit signal T/
103. The transmit user data signal can have any phase in relation to the transmit timing
signal (S/114).
In this mode the signal X/113 is not used.
This mode is used for relatively long lines and high user data rates where the signal delay
is of the same order of magnitude as the half bit width or more.

Please note:
The byte or frame timing (B/F) signal output can not be used since the phase rela-
tionship between the transmit data signal and the B/F timing signal can not be
determined by LEDS1.
− Codirectional:
The transmit user data signal (T/103) is sampled with the transmit timing signal received
from the DTE (X/113). Note that the receive timing signal (S/115) must be looped in the
DTE so that the transmit timing signal (X/113) is synchronous to the network element tim-
ing.
In this mode the signal X/113 is used and the corresponding connector pins are config-
ured as inputs. The timing circuit B/F can’t be used, i.e. the X.24 timing circuits must be
configured to “None (B/F)”.

Please note:
With subrates the “contradirectional adaptive” and “codirectional” transmit timing
modes are not available.
• Loop 2b:
The maintenance function “Loop 2b” loops the receive timing signal S/115 back to the trans-
mit direction where it replaces the transmit timing signal from the DTE X/113. With an active
loop 2b the B or F timing signal can be set to OFF. For details please refer to section 7.2.1
Loop 2b (on page 92).

5.6.3 Conference Timing

All conference participants are synchronous to the network element timing source, i.e. the
PETS.

Copyright 2022 Hitachi Energy. All rights reserved. 76

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

There are no participant specific timing signals used in a conference.

5.7 Protection

5.7.1 Subnetwork Connection and linear Trail Protection

LEDS1 supports 1+1 linear trail protection and 1+1 inherently monitored subnetwork connection
protection (SNCP/I). 1+1 protection is available for the DCE interfaces and for the conference
participants.
The difference between the two protection scenarios lies in the availability of CAS.
• If CAS is available the CAS AIS failure can be detected, which represents then the 1+1 linear
trail protection. Linear trail protection protects against server failures and disconnected
matrix connections (via CAS AIS detection).
• If CAS is not available only the server layer defects can be detected, which represents then
the 1+1 SNCP/I protection. SNCP/I protects against server failures.
1+1 protection provides the 1+1 unidirectional protection. The operation type can be configured
to revertive or non-revertive.

Please note:
Non-revertive operation is only available for subrates and for n=1 (64 kbit/s).
The switching of the working and the protecting channel is done in sink direction only. On the
source side a fixed bridge is used.

Please note:
The loss of subrate frame alignment is not used as protection switching criterion.

working working
TDM
protecting Network protecting

P12 P12 P12 P12

transport transport transport transport

P-12 P-12 P-12 P-12

PBUS PBUS

P12 P12 P12

P0-nc P0-nc P0nc

LEDS1 Data Data LEDS1

Figure 39: Unidirectional 1+1 protection for P0-nc

Copyright 2022 Hitachi Energy. All rights reserved. 77

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

5.7.1.1 Protection configuration

P0-nc and P12 protection switching takes place in the LEDS1 cross connect function.
Protection switching action can be driven by two different request types:
• Traffic signal requests:
− Signal fail (SF)
The SF state is activated if the analysis of the incoming server signal on the transport unit
reports a signal failure, e.g. loss of signal.
− CAS-AIS
The CAS signaling pattern abcd of the received signal exhibits an AIS, i.e. abcd = 1111.
− Signal degraded (SD)
The SD state is activated if the analysis of the incoming server signal on the transport unit
reports a degraded signal, e.g. BER 10-6.
• External command requests
− Forced switch to working
− Forced switch to protecting
− Manual switch to working
− Manual switch to protecting
Note that a forced switch is executed even when there is a failure on the target signal. A manual
switch is executed only if the target signal exhibits no degradation or a less severe degradation
than the active signal.
The external command requests are maintenance functions, i.e. they are not stored in the units
database.
It is possible to check the status of the protection switch (working, protecting circuit) via the CTP
status function.
For more information on cross connections and protection switching please refer to
[1KHW002467] User Manual “TDM Services”.

5.7.2 Equipment Protection (EQP)

5.7.2.1 EQP features

To protect the LEDS1 functions against a failure on the LEDS1 unit, FOX61x offers the possibil-
ity to equip the subrack with a second LEDS1 unit as a protecting unit.
EQP protects the conference function. The DCE interfaces can not be protected. If protection of
the DCE interfaces is required, external equipment performing the switching of the interface sig-
nals between the working and the protecting unit must be used. Refer to section 5.7.2.5 DTE
cabling for 1:1 equipment protection (on page 81).
In case of a failure on the active (working or protecting) unit the user traffic is rerouted from the
failed LEDS1 unit to the standby LEDS1 (protecting or working) unit.
The working and the protecting LEDS1 units can be plugged in any free slot of the FOX61x sub-
rack.

Please note:
The protection switching is non revertive, i.e. after the repair of a failed LEDS1 unit,
the currently active LEDS1 unit remains the active unit irrespective if it is the work-
ing or protecting unit.

Please note:
During a protection switching event the user traffic is interrupted for up to 6 s.

Copyright 2022 Hitachi Energy. All rights reserved. 78

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

5.7.2.2 EQP prerequisites

To enable equipment protection for the LEDS1 unit some prerequisites must be met:
• The protecting LEDS1 unit must be in the unassigned state. Otherwise the unit will not be
selectable in the EQP configuration in AP: /unit-x, Configuration - EQP: Create Group…,
EQP Group Creation, Protecting Unit.
• The protecting unit must be hardware compatible with the working unit. Check the hardware
compatibility status after the EQP group configuration in the AP: /unit-x, Status - EQP: Units
Status, HW Compatible.
The following requirements must be fulfilled that the two units are stated as hardware com-
patible:
− Identical unit function. The unit function is composed of the 5 first characters of the unit
name, e.g. LEDS1. The unit name is available at the AP: /unit-x, Main - Equipment, Unit.
− Identical board identification, e.g. 349. The board identification is available at the AP: /
unit-x, Main - Inventory, Board ID.
− Identical hardware variant. The hardware variant is the truncation of the hardware key
divided by 256, e.g. 1/256 = 0. The hardware key is available at the AP: /unit-x, Main -
Inventory, Hardware Key.
• The protecting unit must be software compatible with the working unit. Check the software
compatibility status after the EQP group configuration in the AP: /unit-x, Status - EQP: Units
Status, SW Compatible.
The following requirements must be fulfilled that the two units are stated as software compat-
ible:
− Identical unit function. The unit function is composed of the 5 first characters of the soft-
ware name, e.g. leds1. The software name is available at the AP: /unit-x, Main - Equip-
ment, Software.
In order to guarantee the full compatibility of all features it is strongly recommended to use
the same software on the working and on the protecting unit.
The compatible software must be installed on the LEDS1 unit before the EQP group cre-
ation.
• The unit configuration of an equipment protection group is always done on the active unit.
The configuration on the standby unit is not possible.

Risk of operating trouble!

The configuration of an equipment protection group must be saved (FOXCST NE
menu or FOXCST tool bar: Save to NE).
→ Otherwise, in case of a protection switch event, the NE will load an outdated
configuration from the internal configuration database and the NE configuration
will be corrupted.

5.7.2.3 EQP configuration

The working LEDS1 unit of an EQP group is assigned and configured the same way as a stand
alone LEDS1 unit.
The protecting LEDS1 unit is running with the same ESW as the working unit and must be in the
unassigned state.
The 1:1 equipment protection group is configured on the working unit:
• AP: /unit-x, Configuration - EQP.
− Execute the command “Create Group…”.
− Select the Protecting unit, e.g. /unit-18.
− Execute “OK”.
• Save the NE configuration.

Copyright 2022 Hitachi Energy. All rights reserved. 79

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Further on any changes on the LEDS1 configuration must be done on the active unit. To find
out which unit is the active unit check the AP tree or the unit status of the working or protecting
LEDS1 unit.

Please note:
The TDM cross connections on the LEDS1 unit can only be created on the work-
ing unit. If the working unit is the standby unit, the CTPs of the standby working
unit are only visible in the “Create Cross Connection” dialog if the A-End or Z-End
“Unit” parameter is set to “All”.

5.7.2.4 EQP status

The unit status of the working and protecting units shows the actual status of the units belonging
to the equipment protection group. The unit status offers also the commands for the EQP
manipulation:
• Manual switch
The currently standby unit is set as active unit and the currently active unit is set as standby
unit. This requires that the currently standby unit is in operational state, i.e.
− has no failure,
− is not isolated.
A manual switch is possible if it is indicated with the “Manual Switch-Over Allowed” parame-
ter.
Note that this command can only be activated on the working unit status window.
• Forced switch
The currently standby unit is set as active unit, independent of the failure state of the cur-
rently standby unit.
Note that there is a risk that the user traffic will be permanently interrupted if the currently
standby unit is in a failure state.
The currently active unit is set as standby unit.
Note that this command can only be activated on the working unit status window.
• Isolate unit
To be able to perform a maintenance action, e.g. update of the embedded software, on an
active unit without activating a protection switch-over, the working unit can be isolated. This
means that the protection switching state machine is frozen and no protection switch will be
done until the isolation of the unit is removed.
Note that the isolate unit command can only be applied to the working unit.
• Join unit
Remove the isolation of a previously isolated unit.
Note that the join unit command can only be applied to the working unit.
The table in the EQP status window displays the following items:
• Unit
MO address of the unit belonging to the EQP group.
• EQP unit mode
The working unit is the unit where the protection group has been configured.
The protecting unit is the unit that has been set to the unassigned state before configuring
the protection group.
• Active
Active true means the unit is the active unit, i.e. it is the operational unit.
Active false means the unit is the standby unit, i.e. it is not the operational unit.
The active state can be changed with the “Manual Switch” and “Forced Switch” commands.

Copyright 2022 Hitachi Energy. All rights reserved. 80

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

• Failure
Failure true means the unit is in a failure state.
Failure false means the unit is not in a failure state.
The failure state can not be changed manually.
• Substituted
Substituted true on the working unit means the unit has been substituted by the protecting
unit. A substituted unit is also in the “active false” state.
Substituted false on the working unit means the unit has not been substituted, i.e. it is the
active unit or it has been isolated.
The substituted state of the protecting unit is always false.
• Isolated
Isolated true means the unit has been isolated with the “Isolate Unit” command.
Isolated false means the unit is not isolated.
The isolation state can be changed with the “Isolate Unit” and “Join Unit” commands.
The isolated state of the protecting unit is always false.
• HW Compatible
HW compatible true means the working HW unit is compatible with the protecting HW unit.
HW compatible false means the working HW unit is not compatible with the protecting HW
unit. Equipment protection is not possible.
• SW Compatible
SW compatible true means the working unit embedded software (ESW) is compatible with
the protecting unit ESW.
SW compatible false means the working unit ESW is not compatible with the protecting unit
ESW. Equipment protection is not possible.
• DB Saved
DB saved true means the current configuration of the working or protecting unit has been
saved to the FOX61x internal database.
DB saved false means the current configuration of the working or protecting unit has not
been saved to the FOX61x internal database. A protection switching event will load an out-
dated configuration and traffic will be disturbed.

5.7.2.5 DTE cabling for 1:1 equipment protection

Due to the fact that LEDS1 has front interfaces that are doubled when using the 1:1 equipment
protection function, the DTE cabling must be set up accordingly.
1:1 equipment protection with LEDS1 works only with V.24/V.28, V.35 or X.24/V.11 type DTEs
providing two separate interfaces. One of the interfaces is the working interface while the other
is in standby mode.

DTE LEDS1
working

active
PBUS

LEDS1
protecting

standby

Figure 40: 1:1 equipment protection

Copyright 2022 Hitachi Energy. All rights reserved. 81

FOX61x | LEDS1 FUNCTIONAL DESCRIPTION

Risk of operating trouble!

When connecting a V.24/V.28, V.35 or X.24/V.11 type DTE to a working and pro-
tecting LEDS1 port in parallel the electrical interface parameters will be violated.
1:1 equipment protection with a RS485 type DTE is possible as long as the electrical interface
parameters are not violated.
When using the Ethernet port of LEDS1 with 1:1 protection switching, the Ethernet cabling must
be connected with an external switch box or a hub.
Great care should be taken when using additional switch boxes, as these devices must be con-
sidered as single points of failure in the sensitive path of the 1:1 equipment protection scheme.

Copyright 2022 Hitachi Energy. All rights reserved. 82

FOX61x | LEDS1 COMMISSIONING

6 Commissioning
In this section, you will find a commissioning example for the LEDS1 unit, a LEDS1 interface
and a LEDS1 conference.
Please refer to [1KHW002466] User Manual “FOXCST” for details on the general GUI aspects,
and to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611” for specific char-
acteristics of the FOX61x.

6.1 Profiles

6.1.1 General
A profile is a set of configuration parameters that can be applied to a certain managed object.
Profiles are created offline with the CPS & Profile tool contained in the FOXCST GUI (Menu:
Tools / CPS & Profile …) and then downloaded to the network element in order to make the pro-
files applicable.
For more information concerning profile handling please refer to [1KHW002466] User Manual
“FOXCST”.

Please note:
The creation of profiles is based upon templates that are provided with the ESW
versions.
→ The templates are available only after importing the respective service unit’s
ESW in FOXCST

Please note:
Make sure that you only use profiles from templates that have been installed with
the ESW running on the respective unit. If you use profiles from other ESW ver-
sions, you may get an error message when trying to apply the profile to the unit’s
configuration.

Risk of operating trouble!

Applying a new profile will lead to a service interruption.

6.1.2 LEDS1 Profile Handling

The LEDS1 unit supports one profile type:
• QoS mapping profile
The QoS mapping profile defines the mapping of incoming frames to the four ingress queues
according to the VLAN priority or the DSCP value

Please note:
LEDS1 supports the provisioning of up to 8 different QoS mapping profiles.
The profile is applicable to the managed objects according to the following table.

Table 30: Profile applicability to managed objects

Profile Profile type Applicable to MO
QoS mapping QoSMappingProfile_1.00.00 unit-x/port-5: 10/100BASE-TX

Copyright 2022 Hitachi Energy. All rights reserved. 83

FOX61x | LEDS1 COMMISSIONING

6.2 Commissioning of a DCE Interface

6.2.1 Prerequisites
Before starting the commissioning of a DCE interface on the LEDS1 unit, the following prerequi-
sites need to be fulfilled.

6.2.1.1 Core unit

In a FOX61x, a core needs to be in operation in slot 11 of the FOX61x subrack.

6.2.1.2 LEDS1 unit

The LEDS1 service unit is inserted into a slot of the FOX61x subrack. Available slots are listed
in section 4.2 Slots and Deployment Scenarios for the LEDS1 Unit (on page 24).
A valid ESW is installed on the LEDS1 unit. For the management of ESW, refer to
[1KHW002466] User Manual “FOXCST”. For details about compatible ESW versions, refer to
[1KHW028777] Release Note “FOX61x”.
Port-y of the LEDS1 unit is connected to a DTE with the matching interface type.

6.2.1.3 TDM transport unit (optional)

A TDM transport unit is inserted in the FOX61x and is running with a proper ESW:
− LEDE1,
− DATI1,
− SAMO1,
− SAMO5,
− SAMO2,
− SAMO3.

6.2.1.4 FOXCST
FOXCST needs to be installed on a PC, and a management connection from the FOXCST to
the FOX61x needs to be up and running. For details about the installation and operation of the
FOXCST, please refer to [1KHW002466] User Manual “FOXCST”.
The amount and accessibility of operations depend on the user profile with which you are
logged in. For more information, please refer to [1KHW028522] User Manual “Management
Communication”.

6.2.1.5 PETS
The PETS on the FOX61x network element must be configured to an appropriate synchroniza-
tion clock source, i.e. a clock source traceable to a PRC. For the PETS configuration refer to
[1KHW029105] User Manual “Synchronization”.

6.2.2 Configuration of a DCE Interface

For the configuration of the user port, the following steps have to be performed.

Port configuration
This action list shows step by step how to configure a user port. The given example uses mostly
the default values.
The following assumptions and identifiers are used:
- The LEDS1 unit is assumed to be plugged in slot 7 of a FOX615.
- The LEDS1 unit is assigned.
- The port to be configured has the identifier port-1.

Copyright 2022 Hitachi Energy. All rights reserved. 84

FOX61x | LEDS1 COMMISSIONING

- The interface type is V.35 with a synchronous transmission rate of 64 kbit/s.

→ Configure the port general parameters. Proceed as follows:

1. Navigate to the general parameters:
- AP:/unit-7/port-1, Configuration - General.
2. Select the interface type:
- Interface Type = V.35.
3. Select the transmission mode:
- Transmission = Synchronous.
4. Select the interface rate:
- Rate = 64 kbit/s.
5. Disable the data signal and control signal inversion:
- Signal Inversion, 103 (TXD, T) = false.
- Signal Inversion, 104 (RXD, R) = false.
- Signal Inversion, 105 (RTS, C) = false.
6. Execute “Apply”.

→ Configure the port signal structure parameters. Proceed as follows:

1. Navigate to the signal structure parameters:
- AP:/unit-7/port-1, Configuration - Signal Structure.
2. Select the synchronous timing mode with contradirectional timing:
- Timing = Contradirectional-Fix.
3. Execute “Apply”.

→ Configure the port control signal parameters. Proceed as follows:

1. Navigate to the control signal parameters:
- AP:/unit-7/port-1, Configuration - Control Signals.
2. Select the control signal parameters from DTE, all control signals set to ON, with control sig-
nal transport:
- 105 (RTS,C) = ON,
- 108 (DTR) = ON,
- Signaling To Network = “Yes”.
3. Select the control signal parameters to DTE, all control signals set to ON or OFF:
- 106 (CTS) = ON,
- 107 (DSR) = ON,
- 109 (DCD, I) = ON,
- 142 (Loopback Indication) = OFF.
4. Select the delay time for the control signals:
- 105 (RTS,C) -> 106 (CTS) / 109 (DCD, I) = 0 ms,
5. Execute “Apply”.

→ Configure the port error handling parameters. Proceed as follows:

1. Navigate to the error handling parameters:
- AP:/unit-7/port-1, Configuration - Error Handling.
2. Select the receive failure error handling:
- Consequent Action 104 (RXD, R) = 1.
3. Select the transmit failure error handling, no level detection:
- Level Detection 103 (TXD, T) = False,
- Consequent Action 103 (TXD, T) = None.

Copyright 2022 Hitachi Energy. All rights reserved. 85

FOX61x | LEDS1 COMMISSIONING

4. Select the transmit send time filter parameters, no send or idle time filters:
- DTE Max Send Time Filter = false.
- DTE Max Idle Time Filter = false.
- Execute “Apply”.

→ Configure the port test loops parameters. Proceed as follows:

1. Navigate to the test loops parameters:
- AP:/unit-7/port-1, Configuration - Test Loops.
2. Select the loop activation device, activation by the element manager:
- Activation By = EM.
3. Select the transmit signal during loop 3c and loop 3b:
- 103 (TXD, T) = 1.
4. Select the receive signal during loop 2b:
- 104 (RXD, R) = 1.
5. Execute “Apply”.

→ Configure the port CTP parameters. Proceed as follows:

1. Navigate to the CTP parameters:
- AP:/unit-7/port-1, Configuration - CTP.
2. The CTP parameters are implicitly set and fixed. All displayed parameters are read-only.
3. Configure the z-End:
- Enable the Revertive Protection Switching = true.
- Disable the CAS AIS Supervision = false.
- Disable the Switch-Over Logging = false.
- Execute “Apply”.
Result: The user port is completely configured.

→ Create the cross connection. Proceed as follows:

1. Configure the cross connection from the user port to a time slot on a LEDE1 unit. It is
assumed that the connection termination point (CTP) on the LEDE1 unit has been created
before on port-8, time slot 1. Please note that the termination mode of the LEDE1 port must
be configured to PCM30 or PCM30C, i.e. using CAS.
2. Select the “Cross Connections” tab of the FOXCST “TDM Services” view.
- Click on the “Connection Wizard” button:
- The “Create TDM Connection” dialog opens.
3. Set the connection parameters:
- Layer Rate = P0-nc.
- Directionality = Bidirectional.
- Protected = No.
- Label 1 = <anyName>.
- Label 2 = <anyName>.
- Number = 1.
4. Execute “Next ->”.
5. Select the Z-End CTP:
- Select the LEDS1 unit, port-1.
6. Execute “Next ->”.
7. Select the A-End CTP:
- Select the LEDE1 unit, port-8/chan-1.
8. Execute “Create”.
Result: The bidirectional cross connection from the LEDE1 channel to the LEDS1 port is
created.

Copyright 2022 Hitachi Energy. All rights reserved. 86

FOX61x | LEDS1 COMMISSIONING

→ Activation. Proceed as follows:

1. Set the administrative state of the port-1 to up
AP:/unit-7/port-1, Main - Admin And Oper Status:
- Set Administrative Status to “Up”.
2. Execute “Apply”.
→ The “Operational Status” changes to “Up”.
Result: The port is activated.
End of instruction

6.3 Commissioning of a Conference

6.3.1 Prerequisites
Refer to section 6.2.1 Prerequisites (on page 84).

6.3.2 Configuration of a Conference

For the configuration of a conference, the following steps have to be performed.

Conference configuration
This action list shows step by step how to configure a conference. The given example uses
mostly the default values.
The following assumptions and identifiers are used:
- The LEDS1 unit is assumed to be plugged in slot 7 of a FOX615.
- The LEDS1 unit is assigned.
- The conference to be configured has the identifier conf-1.
- The maximum number of participants is 4.
- The initial number of participants is 3.
- The rate is 64 kbit/s.
- The conference is of the multipoint-to-multipoint type.
- The conference has one “local” participant, one participant “to master” and one participant
“to slave”.
- The participants use CAS for the control signal transport.
- The participants data and control signals are interconnected without conditional control.

→ Configure the unit parameters. Proceed as follows:

1. Navigate to the conferencing parameters:
- AP:/unit-7, Configuration - Conferencing.
2. Create a data conference:
- Execute “Create Conference…”.
- The “Create Conference” dialog opens.
3. Enter the conference parameters:
- Index = 1.
- Maximum Number Of Participants = 4.
- Initial Number Of Participants = 3.
- Rate = 64 kbit/s.
- Type = MP2MP.
4. Execute “OK”.
Result: The unit parameters are configured.

Copyright 2022 Hitachi Energy. All rights reserved. 87

FOX61x | LEDS1 COMMISSIONING

→ Configure the participant 1 general parameters. Proceed as follows:

1. Navigate to the general parameters:
- AP:/unit-7/conf-1/part-1, Configuration - General.
2. Enable the control signals towards the conference:
- Signaling To Conference = Yes.
3. Enable the control signals from the conference:
- Signaling From Conference = Yes.
4. Select the participants role:
- Role = To Master.
5. Disable the conditional interconnection:
- Conditional Interconnection = No.
6. Execute “Apply”.

→ Configure the participant 1 CTP parameters. Proceed as follows:

1. Navigate to the CTP parameters:
- AP:/unit-7/conf-1/part-1, Configuration - CTP.
2. The CTP parameters are implicitly set and fixed. All displayed parameters are read-only.
3. Configure the z-End:
- Enable the Revertive Protection Switching = true.
- Disable the CAS AIS Supervision = false.
- Disable the Switch-Over Logging = false.
- Execute “Apply”.
Result: The participant 1 is completely configured.

→ Configure the participant 2 . Proceed as follows:

1. Configuration analog to participant 1, but with the participants role set to “To Slave”.

→ Configure the participant 3 . Proceed as follows:

1. Configuration analog to participant 1, but with the participants role set to “Local”.

→ Create the cross connection for participant 1. Proceed as follows:

1. Configure the cross connection from the participant 1 to a time slot on a LEDE1 unit. It is
assumed that the connection termination point (CTP) on the LEDE1 unit has been created
before on port-1, time slot 1. Please note that the termination mode of the LEDE1 port must
be configured to PCM30 or PCM30C, i.e. using CAS.
2. Select the “Cross Connections” tab of the FOXCST “TDM Services” view.
- Click on the “Connection Wizard” button:
- The “Create TDM Connection” dialog opens.
3. Set the connection parameters:
- Layer Rate = P0-nc.
- Directionality = Bidirectional.
- Protected = No.
- Label 1 = <anyName>.
- Label 2 = <anyName>.
- Number = 1.
4. Execute “Next ->”.
5. Select the Z-End CTP:
- Select the LEDS1 unit, part-1 of conf-1.
6. Execute “Next ->”.
7. Select the A-End CTP:
- Select the LEDE1 unit, port-1/chan-1.

Copyright 2022 Hitachi Energy. All rights reserved. 88

FOX61x | LEDS1 COMMISSIONING

8. Execute “Create”.
Result: The bidirectional cross connection between LEDS1 and LEDE1 is configured.

→ Create the cross connection for participant 2. Proceed as follows:

1. Configure the cross connection from the participant 2 to a time slot on a LEDE1 unit. It is
assumed that the connection termination point (CTP) on the LEDE1 unit has been created
before on port-2, time slot 1. Please note that the termination mode of the LEDE1 port must
be configured to PCM30 or PCM30C, i.e. using CAS.
2. Select the “Cross Connections” tab of the FOXCST “TDM Services” view.
- Click on the “Connection Wizard” button:
- The “Create TDM Connection” dialog opens.
3. Set the connection parameters:
- Layer Rate = P0-nc.
- Directionality = Bidirectional.
- Protected = No.
- Label 1 = <anyName>.
- Label 2 = <anyName>.
- Number = 1.
4. Execute “Next ->”.
5. Select the Z-End CTP:
- Select the LEDS1 unit, part-2 of conf-1.
6. Execute “Next ->”.
7. Select the A-End CTP:
- Select the LEDE1 unit, port-2/chan-1.
8. Execute “Create”.
Result: The bidirectional cross connection between LEDS1 and LEDE1 is configured.

→ Create the cross connection for participant 3. Proceed as follows:

1. Configure the cross connection from the participant 3 to a user port on the same LEDS1 unit
(port-1).
2. Select the “Cross Connections” tab of the FOXCST “TDM Services” view.
- Click on the “Connection Wizard” button:
- The “Create TDM Connection” dialog opens.
3. Set the connection parameters:
- Layer Rate = P0-nc.
- Directionality = Bidirectional.
- Protected = No.
- Label 1 = <anyName>.
- Label 2 = <anyName>.
- Number = 1.
4. Execute “Next ->”.
5. Select the Z-End CTP:
- Select the LEDS1 unit, part-3 of conf-1.
6. Execute “Next ->”.
7. Select the A-End CTP:
- Select the LEDS1 unit, port-1.
8. Execute “Create”.
Result: The bidirectional cross connection between LEDS1 port and conference participant
is configured.

Copyright 2022 Hitachi Energy. All rights reserved. 89

FOX61x | LEDS1 COMMISSIONING

→ Activation. Proceed as follows:

1. It is assumed that the administrative state of the port-1 has been set to up before.
The conference and the participants don’t need any activation.
End of instruction

Copyright 2022 Hitachi Energy. All rights reserved. 90

FOX61x | LEDS1 OPERATION

7 Operation
This section describes the operation functions of the LEDS1 unit.

Please note:
The operation functions described in this section assume a correctly configured
and operational LEDS1 unit.

7.1 Unit optical Indicators

LEDs on the front of the LEDS1 unit are used to indicate to the user the alarm status summary
of the unit and of the network traffic signals.

XXXXx R1B
37900374

UNIT TRAFFIC

Figure 41: Fault indication LEDs on the LEDS1 unit

Table 31: LED signaling on LEDS1

LED name Color State Meaning
UNIT Red Failure Unit is not in service.
The unit is not able to provide the requested function due to
- equipment failure (total breakdown),
- mismatch of HW and SW.
Recovery from this error situation is done usually by replace-
ment of unit HW or ESW.
Green / Red Booting or Unit has not been taken in service yet or the unit has not been
(blinking 1 Hz) waiting provisioned.
Recovery from this situation is done by taking this unit into
service with FOXCST.
Green Running Unit is up and running, it is ready to provide the required ser-
vice.
Off Failure System is not powered or outage of power supply on unit or
outage of LED.
TRAFFIC Red Failure One or more active failures on the unit, independent of the
severity.
More detailed information is provided by FOXCST.
Off Normal Normal (error free) operation.

7.2 Loops
For maintenance purposes LEDS1 offers for the DCE interfaces three different types of diag-
nostic loops.

Copyright 2022 Hitachi Energy. All rights reserved. 91

FOX61x | LEDS1 OPERATION

LEDS1

R/104

PBUS
DTE Loop 3c Loop 2b Processing Loop 3b

T/103

Figure 42: Loops 2b, 3b and 3c

• Loop 2b (remote loop)

The loop 2b redirects the received data from the network back to the network. The network
connection between the local DCE and the remote DCE can be tested.
• Loop 3b (local loop)
The loop 3b sends the user data transmitted by the DTE back to the DTE. The connection
between DTE and local DCE can be tested.
• Loop 3c (local loop)
The loop 3c sends the user data transmitted by the DTE back to the DTE without processing
of the data signal. The connection between DTE and local DCE can be tested.
The loop signal conditions are according to ITU-T X.150. With V-type interfaces the loops are
according to ITU-T X.20bis, X.21bis and V.54. With X-type interfaces the loops are according to
ITU-T X.20 and X.21.
Only one loop 2b or 3b or 3c can be active at the same time per port.
All loops can be activated by the element manager FOXCST. The loop 3c can also be activated
from the DTE via the control signal 141. Loops can only be activated by the FOXCST or the
DTE. This is done to prevent two users performing maintenance functions at the same time.

Please note:
An active loop 2b, 3b or 3c is traffic disturbing.

Please note:
An active loop generates the alarm “Maintenance Function Active”.

Please note:
There are no diagnostics loops available with MAC bridging.

7.2.1 Loop 2b
The loop 2b is the so called remote loop. The loop selector is located close to the DCE inter-
face.

LEDS1 A, LEDS1 B,
local remote
T/103
R/104

DTE TDM Processing Loop 2b DTE

A Network B
T/103
R/104
fixed pattern

Figure 43: Loop 2b

The loop 2b at location B can be activated from the FOXCST at location B.

During an active loop 2b the signals towards the DTE A are as follows:

Copyright 2022 Hitachi Energy. All rights reserved. 92

FOX61x | LEDS1 OPERATION

• The transmit data signal T/103 is replaced by the receive data signal R/104.
• The control signal C/105 is replaced by the received control signal I/109 if the control signal
C/105 is configured to “From-DTE”. With another configuration the control signal is not modi-
fied.
• The control signal 108 is replaced by the received control signal 107 if the control signal 108
is configured to “From-DTE”. With another configuration the control signal is not modified.
• The transmit timing signal X/113, if used, is replaced by the receiver timing signal S/115.
During an active loop 2b the signals towards the DTE B are as follows:
• The receive data signal R/104 is a fixed pattern, configurable to “1, “0” or “0101”
• The control signals I/109, 106 and 107 are all set to OFF.
• The control signal 142 is set to ON, indicating to the DTE that a test function is active.
• The timing signals S/114 and S/115 remain active.
• The timing signal B/F remains active or can be set to OFF.

7.2.2 Loop 3b
The loop 3b is the so called local loop. The loop selector is located close to the PBUS interface
of the LEDS1 unit.

LEDS1 A, LEDS1 B,
local remote
T/103
R/104

DTE Processing Loop 3b TDM DTE

A T/103 Network B
R/104
fixed pattern

Figure 44: Loop 3b

The loop 3b at location A can be activated from the FOXCST at location A.

During an active loop 3b the signals towards DTE A are as follows:
• The receive data signal R/104 is replaced by the transmit data signal T/103.
• The control signal I/109 is replaced by the transmitted control signal C/105 if the control sig-
nal I/109 is configured to “Remote-105”. With another configuration the control signal is not
modified.
• The control signal 107 is replaced by the transmitted control signal 108 if the control signal
107 is configured to “Remote- 108”. With another configuration the control signal is not modi-
fied.
• The control signal 106 is not modified by a loop 3b.
• The control signal 142 is set to ON, indicating to the DTE that a test function is active.
• The timing signals S/114, S/115 and B/F remain active.
During an active loop 3b the signals towards the DTE B are as follows:
• The transmit data signal T/103 is a fixed pattern, configurable to “1, “0” or “0101”
• The control signal C/105 is set to OFF.
• The control signal 108 is set to OFF.

Please note:
With subrates the transmit data signal towards the DTE B is not the fixed pattern,
but the unchanged user data signal from DTE A.
→ The loop 3b with subrates is transparent.

Copyright 2022 Hitachi Energy. All rights reserved. 93

FOX61x | LEDS1 OPERATION

7.2.3 Loop 3c
The loop 3c is the so called local loop. The loop selector is located close to the DCE interface of
LEDS1.

LEDS1 A, LEDS1 B,
local remote
T/103
R/104

DTE Loop 3c Processing TDM DTE

A Network B
T/103
R/104
fixed
pattern

Figure 45: Loop 3c

The loop 3c at location A can be activated

• from the FOXCST at location A
• from the DTE at location A with the control signal 141 = ON with V-type interfaces.
The data, control and timing signals towards DTE A and DTE B are the same as with the loop
3b.

Please note:
With higher user data rates and long cables, the timing condition of the data sam-
pling in the DTE can not be fulfilled anymore since the looped data signal is not
resampled in LEDS1.
→ Use loop 3b instead.

7.3 DCE Interface Line State Maintenance

The port and participant line state maintenance functions allow to take a DCE interface or a con-
ference participant out of service or to insert a test pattern towards the front port or towards the
conference.
The line state maintenance function provides the following parameters:
• In service:
This parameter restores the normal operating state of the front port or of the conference par-
ticipant.
• Out of service:
Take a front port or a conference participant out of service, i.e. replace the data signal by an
all-1 signal in receive and transmit direction, set all control signals towards the DTE to OFF,
set the S, SA and SB bits in the X.30/V.110 frame to OFF and replace the signaling towards
the network by an AIS (abcd = 1111) and activate the SD and SF signals. SF and SD are the
FOX61x internal failure signals used to control the protection switching.
The timing signals remain active.
− Port maintenance:
This parameter can be used to simulate a failed path towards the front port.
− Participant maintenance:
This parameter can be used to test the protection switching in a point-to-multipoint or mul-
tipoint-to-multipoint application due to a failed LEDS1 unit.

Please note:
The line states of both the “to master” and the “to slave” participants must be set to
“out of service” to check the correct protection switching.

Copyright 2022 Hitachi Energy. All rights reserved. 94

FOX61x | LEDS1 OPERATION

• Test pattern insertion:

Replace the receive data signal at the front port or a conference participants data signal by a
test pattern 0101, set all control signals towards the DTE to OFF. The CAS signaling of a
conference participant is set to OFF. The subrate S, SA and SB bits of a conference partici-
pant are set to OFF.
The timing signals remain active.
− Port maintenance:
This parameter provides an easy way to check the connection from the LEDS1 unit to a
connected DTE.
To insert a test pattern towards the TDM network, a loop 2b or an external hardware loop
must be applied at the corresponding interface.
− Participant maintenance:
This parameter provides an easy way to check the connection from the LEDS1 unit to any
other conference participant.
In a point-to-multipoint application a test pattern inserted at the “to master” participant is
sent to all “local” and the “to slave” participants. A test pattern inserted at a “local” or “to
slave” participant is sent to the “to master” participant.
In a multipoint-to-multipoint application a test pattern inserted at any participant is sent to
all other participants.
When applying a maintenance function the following signals are sent towards the front port or
the conference and towards the PBUS:

Table 32: Maintenance function signal replacement

Function Signal Towards front port Towards PBUS
or conference
Out of service Data signal 1111’1111 1111’1111
Control signals OFF -
CAS - 1111
Failure signal - SF, SD 1
Insert test pat- Data signal 0101’0101 -
tern Control signals OFF -
CAS - -
Failure signal - -

1. SF and SD are the FOX61x internal failure signals used to control the protection
switching

For the location of the signal insertion points please refer to the figures in section 5.4.1 Port
Data Handling (on page 55), section 5.4.2 Conference Data Handling (on page 56), section
5.5.4 Port Control Signal Handling (on page 65) and section 5.5.5 Conference Control Signal
Handling (on page 67).

Please note:
Active maintenance functions generate the MFA alarm (maintenance function
active).

Please note:
Only one maintenance functions can be active at the same time on a port or con-
ference participant.

Copyright 2022 Hitachi Energy. All rights reserved. 95

FOX61x | LEDS1 OPERATION

7.4 DTE send and idle Time Restrictions

A supervision circuit of the DTEs send and idle times helps to improve the network’s availability
by preventing the network from remaining blocked as a result of a defective DTE. This function
is mainly used in the point-to-multipoint and multipoint-to-multipoint applications.
The activity check of a DTE is done by checking the logic content of the transmit data signal T/
103: A “0” means an active state, a “1” means an inactive state.
The send time supervision checks the number of consecutive seconds with observed activity of
the DTE, i.e. each second containing a data bit with a logic “0” counts as a “send time second”.
If the number of “send time seconds” exceeds the configured limit an alarm is activated.
The send time limit can be configured from 1 s to 255 s.
The idle time supervision checks the number of consecutive seconds with no observed activity
of the DTE, i.e. each second containing only data bits with a logic “1” counts as an “idle time
second”. If during the observation period the number of “idle time seconds” is below the config-
ured limit an alarm is activated.
The idle time limit can be configured from 1 s to 255 s. The observation period for the idle time
can be configured from 2 s to 65’535 s. The idle time limit is required to be smaller than the
observation period.

Interface out of service

Send time OK
Idle time OK
Cs = 0 Cs: Counter for the send time seconds
Ci = 0 Ci: Counter for the idle time seconds
Co = 0 Co: Counter for the idle time observation period

Interface in service

Check activity for

1s
Co = Co + 1

N Y
Activity

Cs = 0 Cs = Cs + 1
Ci = Ci + 1 Ci = 0

Send time OK

N N N
Ci ≥ limit Co ≥ limit Cs ≥ limit

Y Y Y

Ci = 0 Ci = 0
Cs = 0
Co = 0 Co = 0

Idle time OK Idle time violated Send time violated

Figure 46: Send time and idle time supervision

Copyright 2022 Hitachi Energy. All rights reserved. 96

FOX61x | LEDS1 OPERATION

When one of the send time or idle time limits is violated the interface can be taken out of service
(refer to section 8.4.3.4 AP: / unit-x / port-y, Configuration - Error Handling (on page 119)). All
DTEs connected to this port will be detached in this case. The DTEs remain detached until the
interface is taken into service again 30 s after the defect clearing or with the corresponding port
status command, refer to section 8.4.6.2 AP: / unit-x / port-y, Status - Maintenance (on
page 130).

7.5 Maintenance

7.5.1 Inventory Data

It is possible to read inventory data from the LEDS1 unit via the FOXCST with the following
access point:
AP: /unit-x, Main - Inventory.

7.5.2 Unit ESW Download

It is possible to update the embedded software (ESW) of the LEDS1 unit via software download.
Please refer to [1KHW002466] User Manual “FOXCST” for the description of the ESW down-
load.

Risk of operating trouble!

The assignment of new embedded software restarts the LEDS1 unit.
Thus, the installation of new ESW on the unit affects all traffic functions of the
LEDS1 unit.

7.5.3 ESW Upgrade with EQP

When upgrading the ESW on 1:1 equipment protected LEDS1 units, care must be taken con-
cerning the traffic interruptions and which unit will finally be the active unit. At the end of the
upgrade procedure the working unit shall be the active unit.
The examples below assume that the working unit is plugged in slot 7 and the protecting unit is
plugged in slot 18 of the FOX615 subrack.

ESW upgrade procedure 1

The following procedure provides the upgrade process with one traffic interruption of about 60 s.

Please note:
A typical ESW upgrade will interrupt the traffic for a duration as indicated above.
→ The ESW upgrade procedure 2 provides two shorter interruptions.

→ ESW download and start. Proceed as follows:

1. Configure the new ESW file for the working LEDS1 unit:
- FOXCST menu Tools - Software Download ….
- Click on the table row with ID “/unit-7”.
- In the “Software to install” column select the software to be downloaded.
- Tick the “Delete unused Software” box.
2. Configure the new ESW file for the protecting LEDS1:
- Click on the table row with ID “/unit-18”.
- In the “Software to install” column select the software to be downloaded.
- Tick the “Delete unused Software” box.

Copyright 2022 Hitachi Energy. All rights reserved. 97

FOX61x | LEDS1 OPERATION

3. Execute the “Download and Start …” command.

- The “Parameters for command Download and Start” dialog opens.
- Select the “Upgrade Units Only” algorithm.
- Click “OK”.
- The new ESW is downloaded and becomes active on the working and the protecting
units.
- Traffic will be interrupted for about 60 s.
Result: The new ESW is active on the working and the protecting LEDS1 units. The work-
ing LEDS1 unit in slot 18 remains the active unit.
End of instruction

ESW upgrade procedure 2

An alternative procedure requires two short interruptions of about 1 s instead of one long inter-
ruption. 1

→ ESW download. Proceed as follows:

1. Configure the new ESW file for the working LEDS1 unit:
- FOXCST menu Tools - Software Download ….
- Click on the table row with ID “/unit-7”.
- In the “Software to install” column select the software to be downloaded.
- Tick the “Delete unused Software” box.
2. Configure the new ESW file for the protecting LEDS1:
- Click on the table row with ID “/unit-18”.
- In the “Software to install” column select the software to be downloaded.
- Tick the “Delete unused Software” box.
3. Execute the “Download” command.
Result: The new ESW is downloaded to the working and protecting LEDS1 units.

→ ESW upgrade on the protecting unit. Proceed as follows:

1. Configure the new ESW file for the protecting LEDS1:
- FOXCST menu Tools - Software Download ….
- Click on the table row with ID “/unit-18”.
- In the “Software to install” column select the new software.
2. Execute the “Start …” command.
- In the “Parameters for command Start” select the algorithm “Upgrade Units Only”.
- Click “OK”.
- The protecting LEDS1 unit starts with the configured ESW.
- This takes about 60 s.
Result: The protecting LEDS1 unit is now running with the correct ESW.

→ Manual switch to protecting unit. Proceed as follows:

1. Navigate to the EQP status dialog on the working unit:
- AP: /unit-7, Status - EQP
2. Perform a manual switch-over from the working to the protecting LEDS1 unit:
- Execute the “Manual Switch-Over” command.
- Traffic will be switched to the protecting unit.
- Traffic will be interrupted for about 1 s.
Result: The protecting LEDS1 unit is active.

1. The 1 s interruption time is valid for configurations with up to 1 conference only. With 212 conferences
the interruption is up to 60 s.

Copyright 2022 Hitachi Energy. All rights reserved. 98

FOX61x | LEDS1 OPERATION

Risk of operating trouble!

The upgrade procedure 2 with sequential ESW upgrade must follow two different
approaches for the ESW upgrade process on the working unit, depending if the
databases of the running ESW and the new ESW are compatible or not.
→ If the new ESW is a hotfix or a customer specific ESW, e.g. ESW leds1_r2g03 -
> leds1_r2g03_03, the databases are compatible.
If the databases are compatible please proceed with → "ESW upgrade on the
working unit (compatible databases)".
→ In any other case, i.e. if the release number or the release alphabetic character
changes, please contact the Hitachi Energy technical support for information
about compatibility between ESW releases.
If the databases are compatible please proceed with → "ESW upgrade on the
working unit (compatible databases)".
If the databases are not compatible please proceed with → "ESW upgrade on
the working unit (non compatible databases)".

→ ESW upgrade on the working unit (compatible databases). Proceed as follows:

1. Configure the new ESW file for the working LEDS1:
- FOXCST menu Tools - Software Download ….
- Click on the table row with ID “/unit-7”.
- In the “Software to install” column select the new software.
2. Execute the “Start …” command.
- In the “Parameters for command Start” select the algorithm “Upgrade Units Only”.
- Click “OK”.
- The working LEDS1 unit starts with the configured ESW.
- This takes up to 60 s.
Result: The working LEDS1 unit is now running with the correct ESW. Proceed with →
"Manual switch to working unit".

→ ESW upgrade on the working unit (non compatible databases). Proceed as follows:
1. Navigate to the equipment handling dialog on the working LEDS1:
- AP: /unit-7, Main - Equipment
2. Start the unit in the bootloader application:
- Execute the “Stop In Boot” command.
3. Wait until the working unit has rebooted.
- This takes about 60 s.
4. Navigate to the software dialog on the working LEDS1:
- AP: /unit-7, Main - Software
5. Delete all softwares from the “Software On Unit” table except the new ESW.
6. Start the new ESW:
- In the “Configuration, Software” parameter select the new ESW.
- Execute the “Start Software” command.
7. Wait until the working unit has rebooted.
- This takes up to 60 s.
- If the databases of the previously running ESW and of the new ESW are not compatible
there will be a software mismatch (SWM) alarm.
8. Start the new ESW again:
- In the “Configuration, Software” parameter select the new ESW.
- Execute the “Start Software” command.
- The SWM alarm is cleared.
Result: The working LEDS1 unit is now running with the correct ESW.

Copyright 2022 Hitachi Energy. All rights reserved. 99

FOX61x | LEDS1 OPERATION

→ Manual switch to working unit. Proceed as follows:

1. Navigate to the EQP status dialog on the working unit:
- AP: /unit-7, Status - EQP
2. Perform a manual switch-over from the protecting to the working LEDS1 unit:
- Execute the “Manual Switch-Over” command.
- Traffic will be switched to the working unit.
- Traffic will be interrupted for about 1 s.
Result: The ESW upgrade is complete and the working LEDS1 unit is active.
End of instruction

Copyright 2022 Hitachi Energy. All rights reserved. 100

FOX61x | LEDS1 USER INTERFACE REFERENCE

8 User Interface Reference

This section gives a complete reference of the managed objects, properties, and commands of
the LEDS1 service unit as far as these are not covered in the generic descriptions in
[1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
For a description on how to configure and bring into operation the LEDS1 unit and its main func-
tions, please refer to section 6 Commissioning (on page 83).

8.1 Introduction
Below, you will find a detailed description of all the configuration parameters and operations
belonging to the managed objects model (MOM) for the LEDS1 service unit.
The Figure 47 shows the access point (AP) tree for the LEDS1 unit with its managed objects.

<a p>
FOX61x

0...20 <a p>

unit-x: LEDS1

5 <a p>
port-y

0...212 <a p>

conf-z

0...16 <a p>

part-a

Figure 47: MOM (managed object model) of the LEDS1 unit

With these managed objects (MOs) the following functions are covered:

Table 33: Managed objects (MOs) for LEDS1

MO Description of the management functions
unit-x: LEDS1 Rxx Restart of the unit, management of the unit ESW, labeling, indication of equip-
(leds1_r2g) ment status, read of inventory data, access to logbooks. Configuration of unit
parameters and equipment protection parameters, creating or deleting of data
conferences.
The detailed properties are described in section 8.3 AP: / unit-x: LEDS1 (on
page 104).
port-y Management of the DCE and Ethernet interface related functions, like the inter-
face type, transmission mode, user bit rate and maintenance functions.
The detailed properties are described in section 8.4 AP: / unit-x / port-y, y = 1 … 4
(on page 111)
conf-z Management of a data conference. Creating or deleting of conference partici-
pants.
The detailed properties are described in section 8.6 AP: / unit-x / conf-z (on
page 142)
part-a Management of a participant of a data conference. Parameters as e.g. partici-
pant role, signaling handling, maintenance functions.
The detailed properties are described in section 8.7 AP: / unit-x / conf-z / part-a (on
page 143)

For each of the managed objects, properties and commands, the GUI “Tree Views” are given.

Copyright 2022 Hitachi Energy. All rights reserved. 101

FOX61x | LEDS1 USER INTERFACE REFERENCE

This reference section comprises the management functions:

• Overview,
• Main,
• Configuration,
• Fault Management,
• Performance Management, and
• Status.
Most of the APs only offer a part of the management functions listed above.
The order of appearance of the management function descriptions is in accordance with the
APs in the FOXCST AP tree and the availability of the management functions of each AP.
In the tables of the sections below, the parameter default values for properties are underlined.

Please note:
For better legibility of numbers in this User Manual, inverted commas are used
when the number’s size exceeds three digits (e.g. 40’000). In parameter entry
fields of the FOXCST, these inverted commas must not be entered. Instead, the
numbers are entered without these inverted commas (e.g. 40000).

Please note:
Screenshots presented in this reference are examples and show configurations or
data that may not correspond to the view you see when managing your FOX61x
equipment.

8.2 Profiles
For a detailed description of the profile creation and download to the NE please refer to
[1KHW002466] User Manual “FOXCST”.

Please note:
The profile templates are only available if the ESW of the LEDS1 unit has been
imported into the FOXCST.

Copyright 2022 Hitachi Energy. All rights reserved. 102

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.2.1 QoS Mapping Profile

Table 34: QoS mapping profile

Operation Name Parameter Name Range Description / Details
Profile Templates Template QoSMappingPro- Select the QoS mapping profile template as a
file_1.00.00 base for the parameter editing.
Profile, Informa- Name 3 … 64 characters User editable name for the profile.
tion Valid characters are a-z, A-Z, 0-9 and _.
Description 0 … ∞ characters User editable description for the profile.
Valid characters are a-z, A-Z, 0-9 and _.
Profile, Data, Map- VLAN Tag Priority 0…7 Priority of a VLAN tagged packet or priority
ping Profile, tagged MAC frame.
802.1q Mapping Priority Queue Q1 … Q4 Queue number for the ingress traffic.
Q1 is the lowest priority queue,
Q4 is the highest priority queue.
Profile, Data, Map- DSCP Priority 0 … 63 Priority of an IP packet given by the Differen-
ping Profile, DSCP tiated Services Codepoint (DSCP).
Mapping Priority Queue Q1 … Q4 Queue number for the ingress traffic.
Q1 is the lowest priority queue,
Q4 is the highest priority queue.

Copyright 2022 Hitachi Energy. All rights reserved. 103

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.3 AP: / unit-x: LEDS1

8.3.1 AP: / unit-x, Overview

For a description of the
− “Overview - Alarms”, and
− “Overview - Cross Connections”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

8.3.2 AP: / unit-x, Main

For a description of the
− “Main - General”,
− “Main - Equipment”,
− “Main - Inventory”,
− “Main - Logbooks”, and
− “Main - Software”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

8.3.3 AP: / unit-x, Configuration

8.3.3.1 AP: / unit-x, Configuration - Conferencing

“Create Conference” and “Delete Conference” dialogs:

Please note:
The maximum number of subrate conference participants is limited to 12.

Table 35: AP: / unit-x, Configuration - Conferencing

Operation Name Parameter Name Range Description / Details
Create Confer- Open the dialog to create a confer-
ence … ence.

Copyright 2022 Hitachi Energy. All rights reserved. 104

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 35: AP: / unit-x, Configuration - Conferencing (continued)

Operation Name Parameter Name Range Description / Details
Create Conference Index 0 … 255 Select the conference index number.
0 is a reserved value used for the auto-
assignment of a conference index: The
auto-assigned index is the lowest
available index number.
In the FOXCST GUI the default value is
the autoassigned index number.
Maximum Number 4 Maximum number of participants that
Of Participants 8 can be assigned to the data confer-
ence.
12 This maximum number is used for the
16 unit internal resource handling.
If the number of conference partici-
pants has to be increased above the
configured maximum number the con-
ference must be deleted and newly cre-
ated.
The maximum number of subrate con-
ference participants is limited to 12.
Initial Number Of 0 … 3 …16 Number of participants initially
Participants assigned to the data conference. The
initial number of participants must be
smaller or equal than the maximum
number of participants.
Note that the total number of partici-
pants per LEDS1 unit is limited.
Please refer to section 5.3.1.1 nx64 kbit/s
conference resources (on page 47) for a
description of the available resources for
conferences.
Rate 0.6 … 64 …1984 kbit/s Data rate of the conference in kbit/s.
All participants of the conference are
set up with this data rate.
When using CAS the maximum data
rate is limited to 1920 kbit/s.
Note that the rate value influences the
conference resource handling.
Please refer to section 5.3.1.1 nx64 kbit/s
conference resources (on page 47) for a
description of the conference resource
handling on the LEDS1 unit.
Type MP2MP The conference type can be config-
P2MP ured to point-to-multipoint (P2MP) or
multipoint-to-multipoint (MP2MP) in
linear network applications.
Please refer to section 5.5.5 Conference
Control Signal Handling (on page 67) and
section 5.4.2 Conference Data Handling
(on page 56) for a description of the data
and signaling transport in the point-to-
multipoint and multipoint-to-multipoint
applications.
Delete Conference Open the dialog to delete a confer-
… ence.
Delete Conference Conference All Delete all or a specific conference.
conf-1 … conf-n

Copyright 2022 Hitachi Energy. All rights reserved. 105

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.3.3.2 AP: / unit-x, Configuration - EQP

“Create EQP Group” and “Delete EQP Group” dialogs:

Table 36: AP: / unit-x, Configuration - EQP

Operation Name Parameter Name Range Description / Details
Create EQP Group Open the dialog for the creation of an equip-
… ment protection (EQP) group.
A unit must be in the unassigned state to be
selectable as a protecting unit.
EQP Group Cre- Group Type 1:1 Type of the EQP group.
ation Working Unit /unit-x MO address of the working unit, e.g. /unit-4.
In the FOXCST GUI the working unit MO
address is read-only.
Protecting Unit - List of the MO addresses of all HW compati-
/unit-y ble units which are not assigned, e.g. /unit-
20.
Default is no unit selected.
Delete EQP Group Open the dialog for the deletion of an exist-
ing equipment protection (EQP) group.
Traffic on the protecting unit will be inter-
rupted and services will be re-established on
the working unit.
The protecting unit will become unassigned.

Please note:
With equipment protection of a LEDS1 unit it is only possible to protect the confer-
ences on the unit.
→ Equipment connected to user ports can not be protected.

8.3.4 AP: / unit-x, Fault Management

For a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”. The following table lists the fault causes of the current AP.

Copyright 2022 Hitachi Energy. All rights reserved. 106

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 37: AP: / unit-x, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
EQM Equipment Malfunc- Equipment Critical The LEDS1 controller detects any anom-
tion Alarm alies on the unit, e.g. a voltage is miss-
ing, a chip does not respond, etc.
EQPHWI EQP Hardware Incom- Equipment Major The actual hardware is not compatible
patible With Configu- Alarm with the hardware of the protecting
ration unit.
This alarm is available on the working
unit of an EQP group only.
EQPNPR EQP Group Not Pro- Equipment Major The working or the protecting unit is
tected Alarm not available, i.e. not plugged in or has
an equipment failure.
This alarm is available on the working
unit of an EQP group only.
EQPSWI EQP Software Incom- Equipment Major The running software (ESW) is not
patible With Configu- Alarm compatible with the software on the
ration protecting unit.
This alarm is available on the working
unit of an EQP group only.
EQPUNA EQP Working Unit Not Equipment Major An automatic protection switch or a
Active Alarm “manual switch” or a “forced switch”
to the protecting unit has been done.
EQPUNV EQP Unit Not Avail- Equipment Major The standby unit is not available, i.e.
able Alarm not plugged in or has an equipment
failure.
This alarm is available on the working
and the protecting unit of an EQP
group.
EQPWUI EQP Working Unit Iso- Equipment Major The working unit has been isolated
lated Alarm with the “Isolate Unit” status com-
mand.
No protection is available in this state.
This alarm is available on the working
unit of an EQP group only.
GSW General Software Equipment Major An ESW internal error has been
Alarm Alarm detected that might inhibit the ESW
from running correctly.
HWIC Hardware Incompati- Equipment Major The plugged HW is not compatible
ble With Configura- Alarm with the unit configuration HW stored
tion in the database. You may need to
change the HW or re-create the con-
figuration for the unit.
MFA Maintenance Func- Communica- Warning A maintenance function has been acti-
tion Active tion Alarm vated by the operator from the unit
status dialog.
NSW No Application Soft- Equipment Major There is no application ESW installed
ware Alarm on the unit, or the application ESW has
not yet finished its boot process.
PRC PBUS Resource Con- Processing Major Unit has been plugged into a slot
flict Error Alarm which conflicts with another unit, e.g.
when using an outdated ESW on an
ISDN-BA linecard.
SSWNA Scheduled Software Equipment Minor The ESW that is scheduled for installa-
Not Available Alarm tion is not available on the unit. Make
sure that the ESW is downloaded to
the unit.

Copyright 2022 Hitachi Energy. All rights reserved. 107

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 37: AP: / unit-x, Fault Management (continued)

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
SWIC Software Incompati- Equipment Major The ESW running on the unit is not
ble With Configura- Alarm compatible with the unit configura-
tion tion stored in the database. You may
need to upgrade, or downgrade the
ESW, or re-create the configuration
with the currently running ESW.
SWIN Software Incompati- Equipment Major The running ESW is not compatible
ble With Network Ele- Alarm with the version required by the NE
ment type or version.
SWM Software Mismatch Equipment Minor The running ESW does not match the
Alarm assigned ESW.
UIC Unit Incompatible Equipment Major The inserted unit is not compatible
Alarm with the assigned unit.
UNAS Unit Not Assigned Equipment Warning The unit is not assigned and cannot be
Alarm configured. To assign the unit, exe-
cute the “Assign” command in the
“Main” function of the unit.
UNAV Unit Not Available Equipment Critical The unit that is configured is either
Alarm not plugged or not recognized due to
a failure.

8.3.5 AP: / unit-x, Status

8.3.5.1 AP: / unit-x, Status - Conferences

Table 38: AP: / unit-x, Status - Conferences

Operation Name Parameter Name Range Description / Details
Number Of Avail- Number Of Avail- 0 … 53 Available number of 64 kbit/s conferences
able Conferences 1 able 16 Partici- with 16 participants on the LEDS1 unit.
pants Conferences

Copyright 2022 Hitachi Energy. All rights reserved. 108

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 38: AP: / unit-x, Status - Conferences (continued)

Operation Name Parameter Name Range Description / Details
Number Of Avail- 0 … 106 Available number of 64 kbit/s conferences
able 8 Partici- with 8 participants on the LEDS1 unit.
pants Conferences
Number Of Avail- 0 … 212 Available number of 64 kbit/s conferences
able 4 Partici- with 4 participants on the LEDS1 unit.
pants Conferences
Number Of Avail- 0…1 Available number of subrate conferences with
able 12 Partici- 12 participants on the LEDS1 unit.
pants Subrate
Conferences
Number Of Avail- 0…1 Available number of subrate conferences with
able 8 Partici- 8 participants on the LEDS1 unit.
pants Subrate
Conferences
Number Of Avail- 0…3 Available number of subrate conferences with
able 4 Partici- 4 participants on the LEDS1 unit.
pants Subrate
Conferences
Available Partici- Max Participant 64 … 1984 Maximum participant rate available on the
pant Resources, Rate (kbit/s) PBUS resources.
Participant It is only possible to create conference partic-
Resource Table 2 ipants with the maximum or a smaller rate.
Available 0 … 27 Available number of participants with the cor-
responding maximum participant rate.
It is only possible to create conference partic-
ipants with the maximum rate up to the avail-
able number.
Note that when creating conferences with
smaller rates also the resources with higher
rates can be used.

1. The number of available conferences shows the number of available conferences with 16 OR 8 OR 4 participants. The
number of available subrate conferences shows the number of available conferences with 12 OR 8 OR 4 participants.
2. The participant resource table shows all available resources, it is NOT an OR operation.

Please note:
Refer to section 5.3.1.1 nx64 kbit/s conference resources (on page 47) and to sec-
tion 5.3.1.2 Subrate conference resources (on page 50) for a description of the
conference resource handling on the LEDS1 unit.

Please note:
Refer to section 5.3.1.3 PBUS resources (on page 50) for a description of the
PBUS resource handling on the LEDS1 unit.

Copyright 2022 Hitachi Energy. All rights reserved. 109

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.3.5.2 AP: / unit-x, Status - EQP

Table 39: AP: / unit-x, Status - EQP

Operation Name Parameter Name Range Description / Details
EQP Group Manual Switch- Indication that the standby unit, i.e. the work-
Over Allowed ing or the protecting unit is operational and
can take over the service.
Indication that the standby unit, i.e. the work-
ing or the protecting unit is not operational
due to a failure or to isolation or that the
database has not been saved. A manual pro-
tection switching with the “Manual Switch-
Over” command is not possible.
EQP Group - Units Unit <MO address> MO address of the unit belonging to the EQP
Status group.
EQP Unit Mode Undefined Mode Mode of a unit in the EQP group.
Working Unit
Protecting Unit
Active The unit is active (operational).
The unit is standby (not operational).
Failure The unit has detected failure(s).

Substituted The working unit has been substituted by the

protecting unit.

Isolated The working unit has been isolated with the

“Isolate Unit” command.

HW Compatible The working unit is hardware compatible with

the protecting unit in the EQP group.
Please refer to section 5.7.2.2 EQP prerequisites
(on page 79).
SW Compatible The working unit is embedded software com-
patible with the protecting unit in the EQP
group.
Please refer to section 5.7.2.2 EQP prerequisites
(on page 79).
DB Saved The configuration of the unit has been saved.

Copyright 2022 Hitachi Energy. All rights reserved. 110

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 39: AP: / unit-x, Status - EQP (continued)

Operation Name Parameter Name Range Description / Details
Manual Switch- Manual switch of the unit in the EQP group.
Over A switch over is performed only when the
other unit is error free and is not isolated and
the database has been saved.
Refer to the “Manual Switch-Over Allowed”
property above.
Note: The traffic will be interrupted for about
1 s. 1
Forced Switch- Forced switch of the unit in the EQP group.
Over A switch over is performed independent of
the error state of the other unit, but the unit
must not be isolated.
Note: The traffic will be interrupted for about
1 s. 1
Note: Traffic will remain interrupted if the
active unit is not operational.
Isolate Unit Isolate the working unit from the EQP group.
An isolated working unit will not perform any
protection switch action. The protection
switching state of the unit is frozen.
Join Unit Join the isolated working unit to the EQP
group, i.e. remove the isolation.

1. The 1 s interruption time is valid for configurations with up to 1 conference only. With 212 conferences the interruption
is up to 60 s.

Please note:
Automatic, manual and forced protection switching is available from the working to
the protecting unit and vice versa.
→ Please refer to section 5.7.2 Equipment Protection (EQP) (on page 78).

8.4 AP: / unit-x / port-y, y = 1 … 4

8.4.1 AP: / unit-x / port-y, Overview

For a description of the
− “Overview - Alarms”,
− “Overview - Cross Connections”, and
− “Overview - CTP”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

8.4.2 AP: / unit-x / port-y, Main

8.4.2.1 AP: / unit-x / port-y, Main - General

For a description of the
− “Main - General”
management function, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

Copyright 2022 Hitachi Energy. All rights reserved. 111

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.4.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status

Table 40: AP: / unit-x / port-y, Main - Admin And Oper Status
Operation Name Parameter Name Range Description / Details
Administrative State Up Set the IETF administrative status of the port
Status Down (RFC 2863).

Operational Status State Up Display of the IETF operational status of the

Down port (RFC 2863).

Testing
Unknown
Dormant
Not Present
Lower Layer Down

8.4.3 AP: / unit-x / port-y, Configuration

Please note that the fields for some of the configuration parameters are context sensitive. Con-
figuration parameters that are not available due to a higher-ranking configuration parameter are
indicated as “NA” (not available).
The steering parameters for the port configuration are
• Interface Type
• Interface Transmission Mode
• Interface Rate
• Synchronous B/F Signal Usage
• CAS Usage
The configuration strategy to be followed is from the uppermost tab (General) to the lowermost
tab (CTP), and on the tabs from the top parameter downwards.
After completing the parameter configuration of a tab press the “Apply” button to assign the
applicable values to the lower-ranking parameters.

Copyright 2022 Hitachi Energy. All rights reserved. 112

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.4.3.1 AP: / unit-x / port-y, Configuration - General

Table 41: AP: / unit-x / port-y, Configuration - General

Operation Name Parameter Name Range Description / Details
Interface Interface Type V.35 Select the interface type of the DCE port.
X.24-V.11 For valid combinations of the interface
type and other configuration parameters
V.24-V.28 refer to Table 20: "Function relationship" (on
RS485-2-wire page 34).
RS485-4-wire
Transmission Asynchronous Select the interface transmission mode.
Synchronous Please refer to section 5.1.4 Transmission
Modes (on page 37) for a description of this
Oversampling parameter.
Transition Coding
Rate 0.6 … 64 … 2048 kbit/s Select the interface clock and data rate in
steps of 64 kbit/s.
The rates 64 to 1984 kbit/s correspond to
the number of time slots used, i.e. 1 … 31
time slots in a P0-nc signal.
The rate 2048 kbit/s corresponds to a P12
(clock master mode) signal.
Rates below 64 kbit/s use the subrate
framing according to V.110 or X.30.
Interface, Signal 103 (TXD, T) Invert the logical state of the receive data
Inversion signal.

104 (RXD, R) Invert the logical state of the transmit

data signal.

105 (RTS, C) Invert the logical state of the 105 (RTS, C)

control signal.
The location of the inverter in the signal
path is shown in Figure 28: "Control signal
handling overview" (on page 60).

Please note:
The V.24-V.28 interface type in Synchronous transmission mode only supports
interface rates up to 128 kbit/s.

Please note:
The RS485 interface types only support the Oversampling transmission mode.

Copyright 2022 Hitachi Energy. All rights reserved. 113

FOX61x | LEDS1 USER INTERFACE REFERENCE

Please note:
The Oversampling transmission mode is only available for interface rates at 64 kbit/
s and above.

Please note:
The Transition Coding transmission mode is only available for the interface rate 64
kbit/s.

Please note:
The Asynchronous transmission mode is only available for subrates up to 38.4 kbit/
s.

8.4.3.2 AP: / unit-x / port-y, Configuration - Signal Structure

Table 42: AP: / unit-x / port-y, Configuration - Signal Structure

Operation Name Parameter Name Range Description / Details
Signal Structure Synchronous, Tim- Contradirectional-Fix Use the contradirectional interface timing
ing with fixed phase alignment.
Only available with the Synchronous trans-
mission mode.
Please refer to section 5.6.2 Port Timing Sig-
nals (on page 74).
Contradirectional-Adaptive Use the contradirectional interface timing
with adaptive phase alignment.
Only available with the Synchronous trans-
mission mode and with interface rates at
64 kbit/s and above.
Codirectional Use the codirectional interface timing.
Only available with the Synchronous trans-
mission mode and with interface rates at
64 kbit/s and above.
NA NA (not available) is the only configurable
value if the transmission mode is Over-
sampling, Transition Coding or Asynchro-
nous.

Copyright 2022 Hitachi Energy. All rights reserved. 114

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 42: AP: / unit-x / port-y, Configuration - Signal Structure (continued)

Operation Name Parameter Name Range Description / Details
Synchronous, B/F None Use no byte (B) or frame (F) timing signal.
Only available with the X.24-V.11 interface
type and the Synchronous transmission
mode.
Please refer to section 5.6.2 Port Timing Sig-
nals (on page 74).
Byte-Timing Use the byte (B) timing signal.
Only available with the X.24-V.11 interface
type and the Synchronous transmission
mode and interface rates up to 256 kbit/s.
Frame-Timing Use the frame (F) timing signal.
Only available with the X.24-V.11 interface
type and the Synchronous transmission
mode and interface rates between 64 and
256 kbit/s.
NA NA (not available) is the only configurable
value
- if the interface type is not X.24-V.11 or
- if the transmission mode is not Synchro-
nous or
- if the interface rate is above 256 kbit/s
or
- if the interface rate is 1.2 kbit/s.
Asynchronous, 7 Use 7 or 8 data bits in the start-stop char-
Data Bits 8 acter.
Please refer to section 5.1.4.1 Asynchro-
nous mode (on page 37).
NA NA (not available) is the only configurable
value if the transmission mode is not
Asynchronous
Asynchronous, 1 Use 1 or 2 stop bits in the start-stop char-
Stop Bits 2 acter.
Please refer to section 5.1.4.1 Asynchro-
nous mode (on page 37).
NA NA (not available) is the only configurable
value if the transmission mode is not
Asynchronous
Asynchronous, No Use or don’t use a parity bit in the start-
Parity Bit Yes stop character.
Note that the parity bit is not evaluated in
LEDS1, it is transported transparently.
Please refer to section 5.1.4.1 Asynchro-
nous mode (on page 37).
NA NA (not available) is the only configurable
value if the transmission mode is not
Asynchronous
Asynchronous, Sig- Basic Use the basic or extended rate adapta-
naling Rate Range Extended tion range for the start-stop characters.
Please refer to section 5.1.4.1 Asynchro-
nous mode (on page 37).
NA NA (not available) is the only configurable
value if the transmission mode is not
Asynchronous

Copyright 2022 Hitachi Energy. All rights reserved. 115

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 42: AP: / unit-x / port-y, Configuration - Signal Structure (continued)

Operation Name Parameter Name Range Description / Details
104 Control RTS-Control The CAS bit a, set by the control signal
(RS485 2-wire), RTS (C/105) at the remote end, controls
Control Mode the transmitter circuit at the RS485 inter-
face.
The CAS usage limits the maximum inter-
face rate to 1920 kbit/s.
Refer to section 5.1.2.1 RTS controlled mode
(on page 35).
Data-Control The activity of the receive data signal con-
trols the transmitter circuit at the RS485
interface.
Refer to section 5.1.2.2 Data controlled mode
(on page 35).
NA NA (not available) is the only configurable
value if the interface type is not RS485 2-
wire.
104 Control 20 … 1500 samples Time to keep the transmitter circuit active
(RS485 2-wire), after the last 0 to 1 transition.
Hold Active Time

Please note:
The B/F signal output is only available with the Contradirectional timing modes.

8.4.3.3 AP: / unit-x / port-y, Configuration - Control Signals

Copyright 2022 Hitachi Energy. All rights reserved. 116

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 43: AP: / unit-x / port-y, Configuration - Control Signals

Operation Name Parameter Name Range Description / Details
Control Signals, 105 (RTS, C) ON Set the local control signal C/105 to 0.
From DTE Please refer to section 5.5 Control Signal
Handling (on page 59).
OFF Set the local control signal C/105 to 1.
From-DTE Set the local control signal C/105 accord-
ing to the control signal state received
from the DTE.
The signal can be inverted or non-inverted,
see section 8.4.3.1 AP: / unit-x / port-y, Con-
figuration - General (on page 113)
NA NA (not available) is the only configurable
value if the interface type is RS485.
108 (DTR) ON Set the local control signal 108 to 0.
Please refer to section 5.5 Control Signal
Handling (on page 59).
OFF Set the local control signal 108 to 1.
From-DTE Set the local control signal 108 according
to the control signal state received from
the DTE.
NA NA (not available) is the only configurable
value if the interface type is X.24-V.11 or
RS485.
Signaling To Net- No Set the CAS a and b bits or the subrate
work frame S bit (X.30) or SA and SB bits (V.110)
to 1 (OFF).
Please refer to section 5.5.4 Port Control Sig-
nal Handling (on page 65).
Yes Set the CAS a and b bits or the subrate
frame S bit (X.30) or SA and SB bits (V.110)
according to the C/105 and 108 control
signal state.
NA NA (not available) is the only configurable
value
- if the interface type is RS485 or
- if the interface rate is 1984 or 2048 kbit/
s (no CAS available) or
- if the interface rate is 56 kbit/s without
signaling.
V/X Compatibility No Set the subrate frame SA and SB bits
Mode (V.110) according to the C/105 and 108
control signal state.
Please refer to section 5.5 Control Signal
Handling (on page 59).
Yes Set both the subrate frame SA and SB bits
(V.110) according to the C/105 control sig-
nal state.
NA NA (not available) is the only configurable
value
- if the interface type is X.24-V.11 or RS485
or
- if the interface rate is 64 kbit/s or above
or
- if the interface rate is 56 kbit/s without
signaling.

Copyright 2022 Hitachi Energy. All rights reserved. 117

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 43: AP: / unit-x / port-y, Configuration - Control Signals (continued)

Operation Name Parameter Name Range Description / Details
Control Signals, To 106 (CTS) ON Set the control signal 106 to ON.
DTE Please refer to section 5.5 Control Signal
Handling (on page 59).
OFF Set the control signal 106 to OFF.
Local-105 Set the control signal 106 according to the
local control signal state C/105.
The activation and deactivation of the
control signal 106 can be without delay or
with a configurable delay. Refer to the
“105 (RTS, C) -> 106 (CTS) / 109 (DCD, I)”
parameter below.
Remote-LFA Set the control signal 106 according to the
received” remote loss of frame alignment”
indication, transported in the X bit of the
V.110 subrate frame.
NA NA (not available) is the only configurable
value if the interface type is X.24-V.11 or
RS485.
107 (DSR) ON Set the control signal 107 to ON.
Please refer to section 5.5 Control Signal
Handling (on page 59).
OFF Set the control signal 107 to OFF.
Local-108 Set the control signal 107 according to the
local control signal state 108.
Remote-108 Set the control signal 107 according to the
received CAS b bit or the subrate frame SA
bit (V.110).
Not available if the interface rate is 1984
or 2048 kbit/s (no CAS available)
NA NA (not available) is the only configurable
value if the interface type is X.24-V.11 or
RS485.
109 (DCD/I) ON Set the control signal I/109 to ON.
Please refer to section 5.5 Control Signal
Handling (on page 59).
OFF Set the control signal I/109 to OFF.
Local-105 Set the control signal I/109 according to
the local control signal state C/105.
The activation and deactivation of the
control signal I/109 can be without delay
or with a configurable delay. Refer to the
“105 (RTS, C) -> 106 (CTS) / 109 (DCD, I)”
parameter below.
Remote-105 Set the control signal I/109 according to
the received CAS a bit or the subrate
frame S bit (X.30) or SB bit (V.110).
Not available if the interface rate is 1984
or 2048 kbit/s (no CAS available)
NA NA (not available) is the only configurable
value if the interface type is RS485.

Copyright 2022 Hitachi Energy. All rights reserved. 118

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 43: AP: / unit-x / port-y, Configuration - Control Signals (continued)

Operation Name Parameter Name Range Description / Details
142 (Loopback ON Set the control signal 142 to ON.
Indication) Please refer to section 5.5 Control Signal
Handling (on page 59).
OFF Set the control signal 142 to OFF.
From-DCE Set the control signal 142 according to the
local loop state, i.e.
- Back-To-Back-2b or
- Front-To-Front-3b or
- Front-To-Front-3c.
NA NA (not available) is the only configurable
value if the interface type is X.24-V.11 or
RS485.
Control Signals, 105 (RTS, C) -> 106 0 ms Propagation delay between the local con-
Delay Local Con- (CTS) / 109 (DCD, 10 ms trol signal C/105 and the control signals
trol Signals I) 106 and I/109, if they are configured to
20 ms “Local-105”.
40 ms Please refer to section 5.5 Control Signal
Handling (on page 59).

8.4.3.4 AP: / unit-x / port-y, Configuration - Error Handling

Table 44: AP: / unit-x / port-y, Configuration - Error Handling

Operation Name Parameter Name Range Description / Details
Error Handling, Consequent Action 0 Replace the receive data signal R/104 by a
Receive Failure 104 (RXD, R) 1 0 or a 1 in case of a downstream failure
(server-layer) or with a local subrate loss
of frame alignment.

Copyright 2022 Hitachi Energy. All rights reserved. 119

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 44: AP: / unit-x / port-y, Configuration - Error Handling (continued)

Operation Name Parameter Name Range Description / Details
Consequent Action OFF Set the byte-timing or frame-timing signal
B/F to OFF in case of a downstream failure
(server-layer) or with a local subrate loss
of frame alignment.
Active Keep the byte-timing or frame-timing sig-
nal active also in case of a downstream
failure.
NA NA (not available) is the only configurable
value if the interface type is not X.24-V.11
or the B/F parameter is not configured to
byte-timing or to frame-timing.
Error Handling, Level Detection False Supervise the electrical signal levels on the
Transmit Failure 103 (TXD, T) True transmit data signal T/103.
Please refer to section 5.4.1 Port Data Han-
dling (on page 55).
NA NA (not available) is the only configurable
value if the interface type is RS485 2-wire.
Consequent Action None Apply no consequent action in case of a
103 (TXD, T) detected failure on the transmit data sig-
nal T/103 or transmit clock signal X/113.
0 In case of a detected failure on the trans-
1 mit data signal T/103 or transmit clock
signal X/113 set the local transmit data
signal to 0 or 1 and set the local control
signals C/105 and 108 to OFF.
The consequent action on the control sig-
nals affects only the control signal trans-
port via the CAS or the subrate frame S bit
(X.30) or SA and SB bits (V.110).
Note that the “Level Detection 103 (TXD,
T)” must be set to “True”.
NA NA (not available) is the only configurable
value if the interface type is RS485 2-wire.
Error Handling, DTE Max Send Supervise the maximum send time on the
Transmit Send Time Filter transmit data signal T/103, i.e. check for
Time Filter 103 activity on the data signal.
(TXD, T) Please refer to section 7.4 DTE send and idle
Time Restrictions (on page 96)
DTE Max Send 1 … 10 … 255 s Maximum allowed number of consecutive
Time seconds with observed activity on the
transmit data signal T/103.
DTE Min Idle Time Supervise the minimum idle time on the
Filter transmit data signal T/103, i.e. check for
inactive periods on the data signal.
Please refer to section 7.4 DTE send and idle
Time Restrictions (on page 96)
DTE Min Idle Time 1 … 10 … 255 s Minimum required number of consecutive
seconds with no activity during the obser-
vation period on the transmit data signal
T/103.
DTE Idle Time Win- 2 … 20 … 65’535 s Observation period for the minimum idle
dow time.
Note that the “DTE Idle Time Window”
must be higher than “DTE Min Idle Time”.

Copyright 2022 Hitachi Energy. All rights reserved. 120

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 44: AP: / unit-x / port-y, Configuration - Error Handling (continued)

Operation Name Parameter Name Range Description / Details
Consequent Action None Apply no consequent action in case of a
On Port detected send or idle time failure on the
transmit data signal T/103.
Persistent In case of a detected send or idle time fail-
Auto-Reset ure on the transmit data signal T/103
- set the local transmit data signal T/103
to 1,
- set the local control signals C/105 and
108 to OFF,
With “Persistent” the consequent action
must be removed manually in the port sta-
tus maintenance dialog. Refer to section
8.4.6.2 AP: / unit-x / port-y, Status - Mainte-
nance (on page 130).
With “Auto-Reset” the consequent action
is automatically reset 30 s after the clear-
ing of the failure.
Note that the “DTE Max Send Time Filter”
or the “DTE Min Idle Time Filter” must be
set to “true” to be able to configure “Per-
sistent” or “Auto-Reset”.

Please note:
The consequent action in case of a detected send or idle time failure overrides the
consequent action in case of a detected signal level failure.

8.4.3.5 AP: / unit-x / port-y, Configuration - Test Loops

Table 45: AP: / unit-x / port-y, Configuration - Test Loops

Operation Name Parameter Name Range Description / Details
Test Loops, Loop Activation By EM All loops can be activated by the element
Activation manager (EM).
The loop activation by the control signal
141 is blocked.
DTE The front-to-front loop 3c can be acti-
vated by the control signal 141.
The loop activation of all loops by the ele-
ment manager (EM) is blocked.

Copyright 2022 Hitachi Energy. All rights reserved. 121

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 45: AP: / unit-x / port-y, Configuration - Test Loops (continued)

Operation Name Parameter Name Range Description / Details
Test Loops, Signal 103 (TXD, T) 1 Replace the transmit data signal T/103 by
States When Loop 0 a 0, a 1 or a 01 signal in case of an active
Active, Loop 3b, 3c loop 3b or loop 3c.
01
NA NA (not available) is the only configurable
value if the interface type is RS485 2-wire.
Test Loops, Signal 104 (RXD, R) 1 Replace the receive data signal R/104 by a
States When Loop 0 0, a 1 or a 01 signal in case of an active
Active, Loop 2b loop 2b.
01
B/F OFF Set the byte-timing or frame-timing signal
to OFF in case of an active loop 2b.
Active Keep the byte-timing or frame-timing sig-
nal active also in case of an active loop 2b.
NA NA (not available) is the only configurable
value if the interface type is not X.24-V.11
or the B/F parameter is not configured to
byte-timing or to frame-timing.

8.4.3.6 AP: / unit-x / port-y, Configuration - CTP

Please note:
All layer rate, number of time slots and time slot allocation parameters are read
only.
→ To change a parameter the port has to be deleted and newly created with the
modified parameters.

Copyright 2022 Hitachi Energy. All rights reserved. 122

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 46: AP: / unit-x / port-y, Configuration - CTP

Operation Name Parameter Name Range Description / Details
CTP Configuration Layer Rate P0_nc Layer rate of the connection termination
P12 point is P0_nc, i.e. n x 64 kbit/s or P12, i.e.
2048 kbit/s.
n 0 … 2 characters Number of timeslots in case of P0_nc. The
possible range is from 1 to 32.
The number of time slots of a LEDS1 port is
fixed in the range 1 to 31.
Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 in case of
P0_nc, e.g. 1 … 31.
The timeslot(s) property of a LEDS1 port is
empty.
Connected to Remote CTP <MO address> Address string of a connections remote end.
CTPs Without a connection the parameter is empty
Connection Index 0 … 65’535 Index of a connection assigned to the port.
Without a connection the parameter is empty
Directionality Bidirectional Directionality of the connection.
Unidirectional
Local Role z-End The port is the ending point of a connection.
Please refer to [1KHW002467] User Manual
“TDM Services”
a-End Working The port is the working starting point of a
protected or unprotected connection.
a-End Protecting The port is the protecting starting point of a
protected connection.
Remote Role z-End The CTP at the connections remote end is the
ending point of a connection.
Please refer to [1KHW002467] User Manual
“TDM Services”
a-End Working The CTP at the connections remote end is the
working starting point of a protected or
unprotected connection.
a-End Protecting The CTP at the connections remote end is the
protecting starting point of a protected con-
nection.
z-End Configura- Revertive Protec- Enable revertive protection switching.
tion tion Switching The z-End will preferably select the working a-
End.
Non-revertive protection switching is only
available for ports with the number of
timeslots n=1.
Non-revertive protection switching for n>1
will be available in a future release,
CAS AIS Supervi- Use CAS AIS as protection switching criterion.
sion The CAS AIS supervision can be disabled in
the shared protection ring application, where
the closed protection ring can have an AIS in
the CAS, to prevent an alarm during normal
operation.
Switch-Over Log- Enable the logging of the protection switch-
ging over events.

Please note:
The z-End of a protected connection shows two entries in the “Connected to CTPs”
table, one for the working and one for the protecting path.

Copyright 2022 Hitachi Energy. All rights reserved. 123

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.4.4 AP: / unit-x / port-y, Fault Management

For a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”. The following table lists the fault causes of the current AP.

Table 47: AP: / unit-x / port-y, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
DTEIL DTE Idle Time Below Communica- Major The connected DTE idle time period is
Limit tion Alarm shorter than allowed during the obser-
vation period.
Only available if the idle time limit
supervision is enabled in the port con-
figuration dialog.
If the consequent action is set to “Per-
sistent” the consequent action must
be removed manually in the port sta-
tus maintenance dialog.
DTESL DTE Send Time Limit Communica- Major The connected DTE send time period
Exceeded tion Alarm is longer than allowed.
Only available if the send time limit
supervision is enabled in the port con-
figuration dialog.
If the consequent action is set to “Per-
sistent” the consequent action must
be removed manually in the port sta-
tus maintenance dialog.
LOC Loss Of Clock Communica- Major Loss of the incoming transmit clock
tion Alarm signal, evaluated from the physical
interface state and from octet slips.
LOF Loss Of Frame Communica- Major Loss of the V.110 or X.30 frame align-
tion Alarm ment.
LOS Loss Of Signal Communica- Major Loss of the incoming transmit data
tion Alarm signal.
Only available if the transmit data sig-
nal level detection is enabled in the
port configuration dialog.
MFA Maintenance Func- Communica- Warning A maintenance function has been acti-
tion Active tion Alarm vated by the operator from the port
status dialog.
NDPF Near End Degraded Quality Of Warning SES ≥ 22 over a 24 hour interval at the
Performance Service Alarm near end.
The alarm status is reset after a 24
hour interval with SES = 0.
SES is a second with an active LOS or
LOC fault cause.
The alarm can be cleared by resetting
the corresponding PM alarm counter.
NUPF Near End Unaccept- Quality Of Warning SES ≥ 15 over a 15 min. interval at the
able Performance Service Alarm near end.
The alarm status is reset after a 15
min. interval with SES = 0.
SES is a second with an active LOS or
LOC fault cause.
The alarm can be cleared by resetting
the corresponding PM alarm counter.

Copyright 2022 Hitachi Energy. All rights reserved. 124

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 47: AP: / unit-x / port-y, Fault Management (continued)

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
RLOF Remote Loss Of Communica- Minor Loss of the V.110 or X.30 frame align-
Frame tion Alarm ment at the remote equipment. The
alarm indication is transported in the
X bit of the V.110 or X.30 frame.
RTSF Redundant Trail Sig- Communica- Minor Trail signal fail (TSF) from the P12
nal Failure tion Alarm transport unit is active, or
CAS AIS active (only available if CAS is
enabled), or
LOF is active.
In a protected connection the work-
ing OR the protecting path has failed.
In an unprotected connection this
fault cause is not applicable.
TSF Trail Signal Failure Communica- Major Trail signal fail (TSF) from the P12
tion Alarm transport unit is active, or
CAS AIS active (only available if CAS is
enabled), or
LOF is active.
In a protected connection the work-
ing AND the protecting path have
failed.

Please note:
The monitoring of the TSF and RTSF alarms is disabled by default.

Risk of operating trouble!

With the V.24-V.28 interface type and synchronous transmission mode, there can
be crosstalk on the connected cable from the clock to the transmit data signal.
→ The “Loss Of Signal” alarm is possibly not detected.

Risk of operating trouble!

The user data rates 600, 1’200, 2’400 and 4’800 bit/s use all the same V.110 or
X.30 subrate frame format.
→ A mismatch of the user data rates configured for two connected user ports or
conference participants cannot be detected. The “Loss Of Frame” alarm is not
activated.

8.4.5 AP: / unit-x / port-y, Performance Management

For a description of the general aspects of the performance management (PM) functions,
please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
The PM parameters are presented in different groups. The following counter groups are avail-
able for the LEDS1 ports:
• “Protection” group, see section 8.4.5.1 AP: / unit-x / port-y, Performance Management - Pro-
tection (on page 126),
• “G.826” group, see section 8.4.5.2 AP: / unit-x / port-y, Performance Management - G.826
(on page 126),
• “Unfiltered Events” group, see section 8.4.5.3 AP: / unit-x / port-y, Performance Management
- Unfiltered Events (on page 126),
The following counter intervals are available, depending of the counter group:

Copyright 2022 Hitachi Energy. All rights reserved. 125

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 48: PM counter interval availability

Counter interval Protection G.826 Unfiltered
Events
User Counter yes yes yes
History 15min yes yes yes
History 24h yes yes yes
Alarm 15min no yes no
Alarm 24h no yes no

8.4.5.1 AP: / unit-x / port-y, Performance Management - Protection

Table 49: PM group: Protection

PM parameter Description
Switch-Over The protection switch-over count gives informa-
tion about the number and distribution of pro-
tection switching events.

8.4.5.2 AP: / unit-x / port-y, Performance Management - G.826

Table 50: PM group: G.826

PM parameter Description
Near End SES Near end count of Severely Errored Seconds.
A second with a defect signal (LOS or LOC) and
not part of unavailable time (UAT).
Near End UAT Near end count of Unavailable Time.
Unavailable time starts with 10 consecutive SES
(included in UAT) and ends with 10 consecutive
error free seconds (not included in UAT).

8.4.5.3 AP: / unit-x / port-y, Performance Management - Unfiltered Events

Table 51: PM group: Unfiltered Events

PM parameter Description
Positive Slips Count of the positive octet slips between the
incoming X/113 timing and the local S/114 tim-
ing.
The DTE source clock is higher than the DCE
source clock.
Negative Slips Count of the negative octet slips between the
incoming X/113 timing and the local S/114 tim-
ing.
The DTE source clock is lower than the DCE
source clock.

Please note:
The octet slip count is limited to 150 slips per second. If the timing deviation of the
transmit data signal is more than 1200 bit/s, i.e. more than 600 ppm, 150 octet slips
are counted per second.

Copyright 2022 Hitachi Energy. All rights reserved. 126

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.4.6 AP: / unit-x / port-y, Status

8.4.6.1 AP: / unit-x / port-y, Status - General

Table 52: AP: / unit-x / port-y, Status - General

Operation Name Parameter Name Range Description / Details
From DTE 103 (TXD, T) 1 Signal state of the transmit data signal T/
0 103.
Note that the state at the interface circuit is
displayed. The data signal inversion configu-
ration does not influence the status indica-
tion.
Activity On 103 Yes Observed activity on the transmit data signal
(TXD, T) No T/103 since the last status refresh.

105 (RTS,C) On Signal state of the control signal C/105.

Off
NA NA (not available) is the displayed if the inter-
face type is RS485.

Copyright 2022 Hitachi Energy. All rights reserved. 127

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 52: AP: / unit-x / port-y, Status - General (continued)

Operation Name Parameter Name Range Description / Details
108 (DTR) On Signal state of the control signal 108.
Off
NA NA (not available) is displayed if the interface
type is X.24-V.11 or RS485.
141 (LL) On Signal state of the control signal 141 (loop
Off command).

NA NA (not available) is displayed if the interface

type is X.24-V.11 or RS485.
To Network CAS 0000 … 1111 CAS abcd pattern sent towards the network.
With a P0-nc data signal the CAS abcd pattern
is sent with every time slot.
The a bit can be controlled by the control sig-
nal C/105.
The b bit can be controlled by the control sig-
nal 108.
Note: With a P0-nc data signal with n=31
(1984 kbit/s) or with a P12 signal (2048 kbit/
s) it is not possible to transport this CAS abcd
pattern in a P12 transport signal.
S 0 Signal state of the sent subrate frame S bit
1 (X.30).
The S bit can be controlled by the control sig-
nal C.
NA NA (not available) is displayed if the interface
rate is at 64 kbit/s or above, i.e. without sub-
rates, or with the subrate 56 kbit/s without
signaling or when the interface type is not
X.24-V.11.
SA 0 Signal state of the sent subrate frame SA bit
1 (V.110).
The SA bit can be controlled by the control
signal 108.
NA NA (not available) is the displayed if the inter-
face rate is at 64 kbit/s or above, i.e. without
subrates, or with the subrate 56 kbit/s with-
out signaling or when the interface type is
X.24-V.11.
SB 0 Signal state of the sent subrate frame SB bit
1 (V.110).
The SB bit can be controlled by the control
signal 105.
NA NA (not available) is the displayed if the inter-
face rate is at 64 kbit/s or above, i.e. without
subrates, or with the subrate 56 kbit/s with-
out signaling or when the interface type is
X.24-V.11.
X 0 Signal state of the sent subrate frame X bit
1 (X.30 or V.110).
The X bit is controlled by the state of the sub-
rate frame alignment.
NA NA (not available) is the displayed if the inter-
face rate is at 64 kbit/s or above, i.e. without
subrates or with the subrate 56 kbit/s with-
out signaling.

Copyright 2022 Hitachi Energy. All rights reserved. 128

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 52: AP: / unit-x / port-y, Status - General (continued)

Operation Name Parameter Name Range Description / Details
From Network CAS 0000 … 1111 CAS abcd pattern received from the network.
With a P0-nc data signal the CAS abcd pattern
of the lowest numbered time slot is dis-
played.
The a bit can control the control signal I/109.
The b bit can control the control signal 107.
S 0 Signal state of the received subrate frame S
1 bit (X.30).
The S bit can control the control signal I.
NA NA (not available) is the displayed if the inter-
face rate is at 64 kbit/s or above, i.e. without
subrates, or with the subrate 56 kbit/s with-
out signaling or when the interface type is
V.24-V.28 or V.35.
SA 0 Signal state of the received subrate frame SA
1 bit (V.110).
The SA bit can control the control signal 107.
NA NA (not available) is the displayed if the inter-
face rate is at 64 kbit/s or above, i.e. without
subrates, or with the subrate 56 kbit/s with-
out signaling or when the interface type is
X.24-V.11.
SB 0 Signal state of the received subrate frame SB
1 bit (V.110).
The SB bit can control the control signal 109.
NA NA (not available) is the displayed if the inter-
face rate is at 64 kbit/s or above, i.e. without
subrates, or with the subrate 56 kbit/s with-
out signaling or when the interface type is
X.24-V.11.
X 0 Signal state of the received subrate frame X
1 bit (X.30 or V.110).
The X bit can control the control signal 106.
NA NA (not available) is the displayed if the inter-
face rate is at 64 kbit/s or above, i.e. without
subrates or with the subrate 56 kbit/s with-
out signaling.
To DTE 104 (RXD, R) 1 Signal state of the receive data signal R/104.
0 Note that the state before the interface cir-
cuit is displayed.
Activity On 104 Yes Observed activity on the receive data signal
(RXD, R) No R/104 since the last status refresh.

106 (CTS) On Signal state of the control signal 106.

Off
NA NA (not available) is the displayed if the inter-
face type is X.24-V.11 or RS485.
107 (DSR) On Signal state of the control signal 107.
Off
NA NA (not available) is displayed if the interface
type is X.24-V.11 or RS485.

Copyright 2022 Hitachi Energy. All rights reserved. 129

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 52: AP: / unit-x / port-y, Status - General (continued)

Operation Name Parameter Name Range Description / Details
109 (DCD/I) On Signal state of the control signal 109.
Off
NA NA (not available) is displayed if the interface
type is RS485.
142 (TM) On Signal state of the control signal 142 (loop
Off indication).

NA NA (not available) is displayed if the interface

type is X.24-V.11 or RS485.

8.4.6.2 AP: / unit-x / port-y, Status - Maintenance

Table 53: AP: / unit-x / port-y, Status - Maintenance

Operation Name Parameter Name Range Description / Details
Line Status State In-Service Restore the normal operating state of the
front port.
Test-Pattern-Insertion Insert a test pattern “01” towards the
front port.
Note that in the oversampling and transi-
tion coding modes the test pattern is gen-
erated with the interface clock rate.
For more information refer to section 7.3
DCE Interface Line State Maintenance (on
page 94).
Out-Of-Service Simulate a failed LEDS1 unit.
For more information refer to section 7.3
DCE Interface Line State Maintenance (on
page 94).
Loop Status State None Deactivate any loop.
Back-To-Back-2b Activate the back-to-back loop 2b.
For more information refer to section 7.2
Loops (on page 91).
Front-To-Front-3b Activate the front-to-front loop 3b.
For more information refer to section 7.2
Loops (on page 91).
This loop is not available for the interface
type RS485 2-wire.
Front-To-Front-3c Activate the front-to-front loop 3c.
For more information refer to section 7.2
Loops (on page 91).
This loop is not available for the interface
type RS485 2-wire.

Copyright 2022 Hitachi Energy. All rights reserved. 130

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 53: AP: / unit-x / port-y, Status - Maintenance (continued)

Operation Name Parameter Name Range Description / Details
Reset Send Time Reset the consequent action from a viola-
Filter Consequent tion of the transmit signal send time or
Action idle time filter condition.
The consequent action can be reset if the
consequent action mode is set to “Per-
sistent” or to “Auto-Reset”.

Risk of operating trouble!

When resetting the send time filter consequent action while the input signal still vio-
lates the filter conditions, traffic can be disturbed.

Please note:
The front-to-front loop 3b with subrates is transparent.

8.4.6.3 AP: / unit-x / port-y, Status - CTP

Table 54: AP: / unit-x / port-y, Status - CTP

Operation Name Parameter Name Range Description / Details
Trail Status Working Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0-nc or
P12 signal is connected to, e.g. /unit-21/port-
1/chan-1.
Working Trail, Sta- OK No failure on the received signal at the
tus remote CTP.
SF Signal Fail status on the received signal at the
remote CTP.
CAS AIS CAS AIS status in the received signal at the
remote CTP, i.e. an all ‘1’ signal in time slot 16.
SD Signal Degraded status on the received signal
at the remote CTP.
Not Available The status of the received signal is not avail-
able at the remote CTP, e.g. when the local
CTPs role is a-end in a unidirectional connec-
tion.
Protecting Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0-nc or
P12 signal is connected to, e.g. /unit-21/port-
2/chan-1.

Copyright 2022 Hitachi Energy. All rights reserved. 131

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 54: AP: / unit-x / port-y, Status - CTP (continued)

Operation Name Parameter Name Range Description / Details
Protecting Trail, OK No failure on the received signal at the
Status remote CTP.
SF Signal Fail status on the received signal at the
remote CTP.
CAS AIS CAS AIS status in the received signal at the
remote CTP, i.e. an all ‘1’ signal in time slot 16.
SD Signal Degraded status on the received signal
at the remote CTP.
Not Available The status of the received signal is not avail-
able at the remote CTP, e.g. when the local
CTPs role is a-end in a unidirectional connec-
tion.
Active Trail Working The trail from the a-end working remote CTP
has been selected.
Protecting The trail from the a-end protecting remote
CTP has been selected.
Not Available There is no active trail.
External Request Request Release Automatic trail selection.
Force Working Force the selector to use the trail from the a-
end working remote CTP.
Force Protecting Force the selector to use the trail from the a-
end protecting remote CTP.
Manual Working Prefer the trail from the a-end working
remote CTP. Use this trail only if the fault sta-
tus is not worse than the fault status of the
protecting trail.
Manual Protecting Prefer the trail from the a-end protecting
remote CTP. Use this trail only if the fault sta-
tus is not worse than the fault status of the
working trail.

8.5 AP: / unit-x / port-y, y = 5

8.5.1 AP: / unit-x / port-y, Overview

For a description of the
− “Overview - Alarms”,
− “Overview - Cross Connections”, and
− “Overview - CTP”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

8.5.2 AP: / unit-x / port-y, Main

8.5.2.1 AP: / unit-x / port-y, Main - General

For a description of the
− “Main - General”
management function, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

Copyright 2022 Hitachi Energy. All rights reserved. 132

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.5.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status

Table 55: AP: / unit-x / port-y, Main - Admin And Oper Status
Operation Name Parameter Name Range Description / Details
Administrative State Up Set the IETF administrative status of the port
Status Down (RFC 2863).

Operational Status State Up Display of the IETF operational status of the

Down port (RFC 2863).

Testing
Unknown
Dormant
Not Present
Lower Layer Down

8.5.3 AP: / unit-x / port-y, Configuration

8.5.3.1 AP: / unit-x / port-y, Configuration - QoS

Table 56: AP: / unit-x / port-y, Configuration - QoS

Operation Name Parameter Name Range Description / Details
QoS, Mapping Pro- Name <List of downloaded QoS Select the appropriate profile
file mapping profiles> from the drop down list.
Preview This command opens a window displaying
the parameters of the actually selected
profile. The contents are identical to those
described in section 8.2 Profiles (on
page 102).
QoS Default Priority 0…7 Default 802.1p priority for untagged pack-
ets

Copyright 2022 Hitachi Energy. All rights reserved. 133

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 56: AP: / unit-x / port-y, Configuration - QoS (continued)

Operation Name Parameter Name Range Description / Details
Priority Source IP Check the DSCP field of the IP header to
determine the priority of the packet.
MAC Check the 802.1p priority bits of the MAC
header to determine the priority of the
packet.
IP Then MAC Check the DSCP field if it exists, otherwise
check the 802.1p priority bits to determine
the priority of the packet.
MAC Then IP Check the 802.1p priority bits if they exist,
otherwise check the DSCP field to deter-
mine the priority of the packet.

8.5.3.2 AP: / unit-x / port-y, Configuration - PHY

Table 57: AP: / unit-x / port-y, Configuration - PHY

Operation Name Parameter Name Range Description / Details
PHY Mode PHY Mode Autonegotiation Select the LAN mode of the Ethernet inter-
10 Mbit/s Full Duplex face.

10 Mbit/s Half Duplex

100 Mbit/s Full Duplex
100 Mbit/s Half Duplex

Risk of operating trouble!

The LAN mode of the host connected to the LEDS1 Ethernet port must be config-
ured to the same PHY mode as the LEDS1 Ethernet port, e.g. both ports config-
ured to “auto-negotiation” or both ports configured to “100 Mbit/s full duplex”.
→ Mixed configurations result in a non operational state of the Ethernet interface.

8.5.3.3 AP: / unit-x / port-y, Configuration - TDM

Copyright 2022 Hitachi Energy. All rights reserved. 134

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 58: AP: / unit-x / port-y, Configuration - TDM

Operation Name Parameter Name Range Description / Details
TDM Rate 64 … 2048 kbit/s Select the transport rate of the TDM WAN
interface.
Values can be selected in steps of 64 kbit/
s.
The rates 64 to 1984 kbit/s correspond to
the number of time slots used, i.e. 1 … 31
time slots in a P0-nc signal.
The rate 2048 kbit/s corresponds to a P12
(clock master mode) signal.

8.5.3.4 AP: / unit-x / port-y, Configuration - CTP

Please note:
All layer rate, number of time slots and time slot allocation parameters are read
only.
→ To change a parameter the port has to be deleted and newly created with the
modified parameters.

Table 59: AP: / unit-x / port-y, Configuration - CTP

Operation Name Parameter Name Range Description / Details
CTP Configuration Layer Rate P0_nc Layer rate of the connection termination
P12 point is P0_nc, i.e. n x 64 kbit/s or P12, i.e.
2048 kbit/s.
n 0 … 2 characters Number of timeslots in case of P0_nc. The
possible range is from 1 to 32.
The number of time slots of a LEDS1 Ethernet
port is fixed in the range 1 to 31.
Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 in case of
P0_nc, e.g. 1 … 31.
The timeslot(s) property of a LEDS1 port is
empty.
Connected to Remote CTP <MO address> Address string of a connections remote end.
CTPs Without a connection the parameter is empty
Connection Index 0 … 65’535 Index of a connection assigned to the port.
Without a connection the parameter is empty

Copyright 2022 Hitachi Energy. All rights reserved. 135

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 59: AP: / unit-x / port-y, Configuration - CTP (continued)

Operation Name Parameter Name Range Description / Details
Directionality Bidirectional Directionality of the connection.
Unidirectional
Local Role z-End The port is the ending point of a connection.
Please refer to [1KHW002467] User Manual
“TDM Services”
a-End Working The port is the working starting point of a
protected or unprotected connection.
a-End Protecting The port is the protecting starting point of a
protected connection.
Remote Role z-End The CTP at the connections remote end is the
ending point of a connection.
Please refer to [1KHW002467] User Manual
“TDM Services”
a-End Working The CTP at the connections remote end is the
working starting point of a protected or
unprotected connection.
a-End Protecting The CTP at the connections remote end is the
protecting starting point of a protected con-
nection.
z-End Configura- Revertive Protec- Enable revertive protection switching.
tion tion Switching The z-End will preferably select the working a-
End.
Non-revertive protection switching is only
available for ports with the number of
timeslots n=1.
Non-revertive protection switching for n>1
will be available in a future release,
CAS AIS Supervi- Use CAS AIS as protection switching criterion.
sion The CAS AIS supervision can be disabled in
the shared protection ring application, where
the closed protection ring can have an AIS in
the CAS, to prevent an alarm during normal
operation.
Switch-Over Log- Enable the logging of the protection switch-
ging over events.

Please note:
The z-End of a protected connection shows two entries in the “Connected to CTPs”
table, one for the working and one for the protecting path.

8.5.4 AP: / unit-x / port-y, Fault Management

For a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”. The following table lists the fault causes of the current AP.

Copyright 2022 Hitachi Energy. All rights reserved. 136

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 60: AP: / unit-x / port-y, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
LOSETH Ethernet Link Down Communica- Major Loss of the incoming Ethernet signal.
tion Alarm
LOSTDM TDM Link Down Communica- Major Loss of the incoming TDM data signal.
tion Alarm The alarm is activated if no activity is
detected in the TDM signal.
Note: The alarm is also activated if the
remote station sends no HDLC-flags
in the idle state. In this case disable
the alarm monitoring.
RTSF Redundant Trail Sig- Communica- Minor Trail signal fail (TSF) from the P12
nal Failure tion Alarm transport unit is active, or
CAS AIS active (only available if CAS
AIS supervision is enabled).
In a protected connection the work-
ing OR the protecting path has failed.
In an unprotected connection this
fault cause is not applicable.
TSF Trail Signal Failure Communica- Major Trail signal fail (TSF) from the P12
tion Alarm transport unit is active, or
CAS AIS active (only available if CAS
AIS supervision is enabled).
In a protected connection the work-
ing AND the protecting path have
failed.

Please note:
The monitoring of the TSF and RTSF alarms is disabled by default.

8.5.5 AP: / unit-x / port-y, Performance Management

For a description of the general aspects of the performance management (PM) functions,
please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
The PM parameters are presented in different groups. The following counter groups are avail-
able for the LEDS1 Ethernet port:
• “Protection” group, see section 8.5.5.1 AP: / unit-x / port-y, Performance Management - Pro-
tection (on page 138),
• “MIB-2 Ethernet Interface” group, see section 8.5.5.2 AP: / unit-x / port-y, Performance Man-
agement - MIB-2 Ethernet Interface (on page 138).
• “MIB-2 TDM Interface” group, see section 8.5.5.3 AP: / unit-x / port-y, Performance Manage-
ment - MIB-2 TDM Interface (on page 138).
The following counter intervals are available, depending of the counter group:

Table 61: PM counter interval availability

Counter interval Protection MIB-2 Ethernet MIB-2 TDM Inter-
Interface face
User Counter yes yes yes
History 15min yes yes yes
History 24h yes yes yes
Alarm 15min no no no
Alarm 24h no no no

Copyright 2022 Hitachi Energy. All rights reserved. 137

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.5.5.1 AP: / unit-x / port-y, Performance Management - Protection

Table 62: PM group: Protection

PM parameter Description
Switch-Over The protection switch-over count gives informa-
tion about the number and distribution of pro-
tection switching events.

8.5.5.2 AP: / unit-x / port-y, Performance Management - MIB-2 Ethernet Interface

Table 63: PM group: MIB-2 Ethernet Interface

PM parameter Description
In Octets The total number of octets received on the interface, including fram-
ing characters
In Unicast Packets The number of unicast packets, i.e. packets with a single address
delivered to a higher-layer protocol.
In Non-unicast Packets The number of multicast or broadcast packets delivered to a higher-
layer protocol.
In Discards The number of inbound packets which were chosen to be discarded
even though no errors had been detected to prevent their being
deliverable to a higher-layer protocol. One possible reason for dis-
carding such a packet could be to free up buffer space.
In Errors The number of inbound packets that contained errors preventing
them from being deliverable to a higher-layer protocol.
Out Octets The total number of octets transmitted out of the interface, includ-
ing framing characters.
Out Unicast Packets The total number of unicast packets that higher-level protocols
requested to be transmitted, including those that were discarded or
not sent.
Out Non-unicast Packets The total number of multicast or broadcast packets that higher-level
protocols requested to be transmitted, including those that were
discarded or not sent.
Out Discards The number of outbound packets which were chosen to be discarded
even though no errors had been detected to prevent their being
transmitted. One possible reason for discarding such a packet could
be to free up buffer space.
Out Errors The number of outbound packets that could not be transmitted
because of errors.

8.5.5.3 AP: / unit-x / port-y, Performance Management - MIB-2 TDM Interface

Table 64: PM group: MIB-2 TDM Interface

PM parameter Description
In Octets The total number of octets received on the interface, including fram-
ing characters
In Unicast Packets The number of unicast packets, i.e. packets with a single address
delivered to a higher-layer protocol.
In Non-unicast Packets The number of multicast or broadcast packets delivered to a higher-
layer protocol.
In Discards The number of inbound packets which were chosen to be discarded
even though no errors had been detected to prevent their being
deliverable to a higher-layer protocol. One possible reason for dis-
carding such a packet could be to free up buffer space.
In Errors The number of inbound packets that contained errors preventing
them from being deliverable to a higher-layer protocol.

Copyright 2022 Hitachi Energy. All rights reserved. 138

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 64: PM group: MIB-2 TDM Interface

PM parameter Description
Out Octets The total number of octets transmitted out of the interface, includ-
ing framing characters.
Out Discards The number of outbound packets which were chosen to be discarded
even though no errors had been detected to prevent their being
transmitted. One possible reason for discarding such a packet could
be to free up buffer space.
Out Errors The number of outbound packets that could not be transmitted
because of errors.

8.5.6 AP: / unit-x / port-y, Status

8.5.6.1 AP: / unit-x / port-y, Status - PHY

Table 65: AP: / unit-x / port-y, Status - PHY

Operation Name Parameter Name Range Description / Details
PHY State Speed Link Down Speed state of the Ethernet port.
100 Mbit/s
10 Mbit/s
Unknown
Duplex Link Down Duplex state of the Ethernet port.
Full Duplex
Half Duplex
Unknown
IEEE 802.3 Flow State of the flow control configuration.
Control

8.5.6.2 AP: / unit-x / port-y, Status - TDM

Copyright 2022 Hitachi Energy. All rights reserved. 139

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 66: AP: / unit-x / port-y, Status - TDM

Operation Name Parameter Name Range Description / Details
Link Status State Up The TDM link status is up if there is activity on
Down the TDM link.
The TDM link status is down if there is no
Unknown activity on the TDM link.
Note that the port operational state follows
the link status.

8.5.6.3 AP: / unit-x / port-y, Status - Bridge

Table 67: AP: / unit-x / port-y, Status - Bridge

Operation Name Parameter Name Range Description / Details
MAC Table MAC Address 00:00:00:00:00:00 … Shows the MAC address of the remote port.
ff:ff:ff:ff:ff:ff
Ingress Interface TDM Shows the local bridge ingress interface.
Ethernet
Expires In 0 … 300 [s] MAC address expiration time in seconds.
The MAC address aging timer has a fixed
value of 300 s.

8.5.6.4 AP: / unit-x / port-y, Status - CTP

Copyright 2022 Hitachi Energy. All rights reserved. 140

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 68: AP: / unit-x / port-y, Status - CTP

Operation Name Parameter Name Range Description / Details
Trail Status Working Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0-nc or
P12 signal is connected to, e.g. /unit-21/port-
1/chan-1.
Working Trail, Sta- OK No failure on the received signal at the
tus remote CTP.
SF Signal Fail status on the received signal at the
remote CTP.
CAS AIS CAS AIS status in the received signal at the
remote CTP, i.e. an all ‘1’ signal in time slot 16.
SD Signal Degraded status on the received signal
at the remote CTP.
Not Available The status of the received signal is not avail-
able at the remote CTP, e.g. when the local
CTPs role is a-end in a unidirectional connec-
tion.
Protecting Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0-nc or
P12 signal is connected to, e.g. /unit-21/port-
2/chan-1.
Protecting Trail, OK No failure on the received signal at the
Status remote CTP.
SF Signal Fail status on the received signal at the
remote CTP.
CAS AIS CAS AIS status in the received signal at the
remote CTP, i.e. an all ‘1’ signal in time slot 16.
SD Signal Degraded status on the received signal
at the remote CTP.
Not Available The status of the received signal is not avail-
able at the remote CTP, e.g. when the local
CTPs role is a-end in a unidirectional connec-
tion.
Active Trail Working The trail from the a-end working remote CTP
has been selected.
Protecting The trail from the a-end protecting remote
CTP has been selected.
Not Available There is no active trail.
External Request Request Release Automatic trail selection.
Force Working Force the selector to use the trail from the a-
end working remote CTP.
Force Protecting Force the selector to use the trail from the a-
end protecting remote CTP.
Manual Working Prefer the trail from the a-end working
remote CTP. Use this trail only if the fault sta-
tus is not worse than the fault status of the
protecting trail.
Manual Protecting Prefer the trail from the a-end protecting
remote CTP. Use this trail only if the fault sta-
tus is not worse than the fault status of the
working trail.

Copyright 2022 Hitachi Energy. All rights reserved. 141

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.6 AP: / unit-x / conf-z

8.6.1 AP: / unit-x / conf-z, Overview

For a description of the
− “Overview - Alarms”, and
− “Overview - Cross Connections”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

8.6.2 AP: / unit-x / conf-z, Main

8.6.2.1 AP: / unit-x / conf-z, Main - General

For a description of the
− “Main - General”
management function, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

8.6.3 AP: / unit-x / conf-z, Configuration

8.6.3.1 AP: / unit-x / conf-z, Configuration - General

“Create Participant” and “Delete Participant” dialogs:

Table 69: AP: / unit-x / conf-z, Configuration - General

Operation Name Parameter Name Range Description / Details
Create Participant Open the dialog to add a participant to a
… conference.
Create Participant Index 0 … 255 Select the participant index number.
0 is a reserved value used for the auto-
assignment of a participant index: The
auto-assigned index is the lowest avail-
able index number.
In the FOXCST GUI the default value is the
autoassigned index number.
Delete Participant Open the dialog to delete a conference
… participant.
Delete Participant Participant All Delete all or a specific conference partici-
part-1 … part-n pant.

Copyright 2022 Hitachi Energy. All rights reserved. 142

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.7 AP: / unit-x / conf-z / part-a

8.7.1 AP: / unit-x / conf-z / part-a, Overview

For a description of the
− “Overview - Alarms”,
− “Overview - Cross Connections”, and
− “Overview - CTP”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

8.7.2 AP: / unit-x / conf-z / part-a, Main

8.7.2.1 AP: / unit-x / conf-z / part-a, Main - General

For a description of the
− “Main - General”
management function, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”.

8.7.2.2 AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status

Table 70: AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status
Operation Name Parameter Name Range Description / Details
Operational Status State Up Display of the IETF operational status of the
Down participant (RFC 2863).
The operational status is up when a cross
Testing connection to another CTP is configured.
Unknown
Dormant
Not Present
Lower Layer Down

8.7.3 AP: / unit-x / conf-z / part-a, Configuration

Please note that the fields for some of the configuration parameters are context sensitive. Con-
figuration parameters that are not available due to a higher-ranking configuration parameter are
indicated as “NA” (not available).
The steering parameters for the participant configuration are
• Conference Rate,
• CAS usage.

Copyright 2022 Hitachi Energy. All rights reserved. 143

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.7.3.1 AP: / unit-x / conf-z / part-a, Configuration - General

Table 71: AP: / unit-x / conf-z / part-a, Configuration - General

Operation Name Parameter Name Range Description / Details
Participant Signaling To Con- Yes The control signal processing of a partici-
ference No pant at the conference input can be
enabled or disabled.
Please refer to section 5.5.5 Conference
Control Signal Handling (on page 67) for a
description of this parameter.
NA NA (not available) is the only configurable
value if the participant rate is 1984 kbit/s
(no CAS available) or 56 kbit/s without
signaling.
Signaling From Yes The control signal processing of a partici-
Conference No pant at the conference output can be
enabled or disabled.
Please refer to section 5.5.5 Conference
Control Signal Handling (on page 67) for a
description of this parameter.
NA NA (not available) is the only configurable
value if the participant rate is 1984 kbit/s
(no CAS available) or 56 kbit/s without
signaling.
Role Local In the point-to-multipoint and multipoint-
to-multipoint linear network applications
the conferences used in the different net-
work elements (NE) have local connec-
To-Master
tions, a connection towards the master
NE head end and a connection towards
the slave NE tail end.
To-Slave The connection role of a participant must
be configured according to the NE type.
Please refer to section 5.2 Network Applica-
tions (on page 42) for a description of the dif-
ferent NE types’ connections.
Conditional Inter- Yes This parameter allows to disconnect par-
connection No ticipants from a conference input if the
control signal C/105 is in the inactive
state.
Please refer to section 5.5.5 Conference
Control Signal Handling (on page 67) for a
description of this parameter.
NA NA (not available) is the only configurable
value if the participant rate is 1984 kbit/s
(no CAS available) or 56 kbit/s without
signaling.

Copyright 2022 Hitachi Energy. All rights reserved. 144

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.7.3.2 AP: / unit-x / conf-z / part-a, Configuration - Subrate

Table 72: AP: / unit-x / conf-z / part-a, Configuration - Subrate

Operation Name Parameter Name Range Description / Details
Subrate Subrate Framing V.110 Defines the subrate framing format.
X.30 Please refer to section 5.5.5 Conference
Control Signal Handling (on page 67) for a
description of this parameter.
NA NA (not available) is the only configurable
value if the participant rate is at 56 kbit/s
without signaling or at 64 kbit/s or higher.

8.7.3.3 AP: / unit-x / conf-z / part-a, Configuration - CTP

Please note:
All layer rate, number of time slots and time slot allocation parameters are read
only.
→ To change a parameter the conference has to be deleted and newly created
with the modified parameters.

Copyright 2022 Hitachi Energy. All rights reserved. 145

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 73: AP: / unit-x / conf-z / part-a, Configuration - CTP

Operation Name Parameter Name Range Description / Details
CTP Configuration Layer Rate P0_nc Layer rate of the connection termination
point is P0_nc, i.e. n x 64 kbit/s.
The layer rate property of a LEDS1 conference
participant is fixed to P0_nc.
n 0 … 2 characters Number of timeslots in case of P0_nc. The
possible range is from 1 to 32.
The number of time slots of a LEDS1 conference
participant is fixed in the range 1 to 31.
Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 in case of
P0_nc, e.g. 1 … 31.
The timeslot(s) property of a LEDS1 conference
participant is empty.
Connected to Remote CTP <MO address> Address string of a connections remote end.
CTPs Without a connection the parameter is empty
Connection Index 0 … 65’535 Index of a connection assigned to the partici-
pant. Without a connection the parameter is
empty
Directionality Bidirectional Directionality of the connection.
Unidirectional
Local Role z-End The participant is the ending point of a con-
nection.
Please refer to [1KHW002467] User Manual
“TDM Services”
a-End Working The participant is the working starting point
of a protected or unprotected connection.
a-End Protecting The participant is the protecting starting
point of a protected connection.
Remote Role z-End The CTP at the connections remote end is the
ending point of a connection.
Please refer to [1KHW002467] User Manual
“TDM Services”
a-End Working The CTP at the connections remote end is the
working starting point of a protected or
unprotected connection.
a-End Protecting The CTP at the connections remote end is the
protecting starting point of a protected con-
nection.
z-End Configura- Revertive Protec- Enable revertive protection switching.
tion tion Switching The z-End will preferably select the working a-
End.
Non-revertive protection switching is only
available for participants with the number of
timeslots n=1.
Non-revertive protection switching for n>1
will be available in a future release,
CAS AIS Supervi- Use CAS AIS as protection switching criterion.
sion The CAS AIS supervision can be disabled in
the shared protection ring application, where
the closed protection ring can have an AIS in
the CAS, to prevent an alarm during normal
operation.
Switch-Over Log- Enable the logging of the protection switch-
ging over events.

Copyright 2022 Hitachi Energy. All rights reserved. 146

FOX61x | LEDS1 USER INTERFACE REFERENCE

Please note:
The z-End of a protected connection shows two entries in the “Connected to CTPs”
table, one for the working and one for the protecting path.

8.7.4 AP: / unit-x / conf-z / part-a, Fault Management

For a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
management functions, please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/
FOX612/FOX611”. The following table lists the fault causes of the current AP.

Table 74: AP: / unit-x / conf-z / part-a, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
LOF Loss Of Frame Communica- Major Loss of the V.110 or X.30 frame align-
tion Alarm ment
MFA Maintenance Func- Communica- Warning A maintenance function has been acti-
tion Active tion Alarm vated by the operator from the partic-
ipant status dialog.
RLOF Remote Loss Of Communica- Minor Loss of the V.110 or X.30 frame align-
Frame tion Alarm ment at the remote equipment. The
alarm indication is transported in the
X bit of the V.110 or X.30 frame.
RTSF Redundant Trail Sig- Communica- Minor Trail signal fail (TSF) from the P12
nal Failure tion Alarm transport unit is active, or
- CAS AIS active (only available if CAS
is enabled), or
- LOF is active.
In a protected connection the work-
ing OR the protecting path has failed.
In an unprotected connection this
fault cause is not applicable.
TSF Trail Signal Failure Communica- Major Trail signal fail (TSF) from the P12
tion Alarm transport unit is active, or
- CAS AIS active (only available if CAS
is enabled), or
- LOF is active.
In a protected connection the work-
ing AND the protecting path have
failed.

Please note:
The monitoring of the TSF and RTSF alarms is disabled by default.

Risk of operating trouble!

The user data rates 600, 1’200, 2’400 and 4’800 bit/s use all the same V.110 or
X.30 subrate frame format.
→ A mismatch of the user data rates configured for two connected user ports or
conference participants cannot be detected. The “Loss Of Frame” alarm is not
activated.

Copyright 2022 Hitachi Energy. All rights reserved. 147

FOX61x | LEDS1 USER INTERFACE REFERENCE

8.7.5 AP: / unit-x / conf-z / part-a, Performance Management

For a description of the general aspects of the performance management (PM) functions,
please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
The PM parameters are presented in different groups. The following counter group is available
for the LEDS1 conference participants:
• “Protection” group, see section 8.7.5.1 AP: / unit-x / conf-z / part-a, Performance Manage-
ment - Protection (on page 148),
The following counter intervals are available:

Table 75: PM counter interval availability

Counter interval Protection
User Counter yes
History 15min yes
History 24h yes
Alarm 15min no
Alarm 24h no

8.7.5.1 AP: / unit-x / conf-z / part-a, Performance Management - Protection

Table 76: PM group: Protection

PM parameter Description
Switch-Over The protection switch-over count gives information about the num-
ber and distribution of protection switching events.

8.7.6 AP: / unit-x / conf-z / part-a, Status

8.7.6.1 AP: / unit-x / conf-z / part-a, Status - General

Copyright 2022 Hitachi Energy. All rights reserved. 148

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 77: AP: / unit-x / conf-z / part-a, Status - General

Operation Name Parameter Name Range Description / Details
To Conference Data 0 Logical state of the data signal going to the
1 conference.

Activity On Data Yes Activity on the user data signal going to the
No conference since the last status refresh.

CAS 0000 … 1111 Signaling bits abcd going to the conference.

NA NA (not available) is displayed if CAS is dis-
abled.
S 0 Logical state of the subrate frame S bit (X.30)
1 going to the conference.

NA NA (not available) is displayed if the rate is at

64 kbit/s or above, i.e. without subrates, or
when the subrate framing is V.110.
SA 0 Logical state of the subrate frame SA bit
1 (V.110) going to the conference.

NA NA (not available) is displayed if the rate is at

64 kbit/s or above, i.e. without subrates, or
when the subrate framing is X.30.
SB 0 Logical state of the subrate frame SB bit
1 (V.110) going to the conference.

NA NA (not available) is displayed if the rate is at

64 kbit/s or above, i.e. without subrates, or
when the subrate framing is X.30.
X 0 Logical state of the subrate frame X bit (X.30
1 or V.110) going to the conference.

NA NA (not available) is displayed if the rate is at

64 kbit/s or above, i.e. without subrates.
From Conference Data 0 Logical state of the data signal coming from
1 the conference.

Activity On Data Yes Activity on the data signal coming from the
No conference since the last status refresh.
With subrates the activity is checked on the
user data signal.
CAS 0000 … 1111 Signaling bits abcd coming from the confer-
ence.
NA NA (not available) is displayed if CAS is dis-
abled.
S 0 Logical state of the subrate frame S bit (X.30)
1 coming from the conference.

NA NA (not available) is displayed if the rate is at

64 kbit/s or above, i.e. without subrates, or
when the subrate framing is V.110.
SA 0 Logical state of the subrate frame SA bit
1 (V.110) coming from the conference.

NA NA (not available) is displayed if the rate is at

64 kbit/s or above, i.e. without subrates, or
when the subrate framing is X.30.

Copyright 2022 Hitachi Energy. All rights reserved. 149

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 77: AP: / unit-x / conf-z / part-a, Status - General (continued)

Operation Name Parameter Name Range Description / Details
SB 0 Logical state of the subrate frame SB bit
1 (V.110) coming from the conference.

NA NA (not available) is displayed if the rate is at

64 kbit/s or above, i.e. without subrates, or
when the subrate framing is X.30.
X 0 Logical state of the subrate frame X bit (X.30
1 or V.110) coming from the conference.

NA NA (not available) is displayed if the rate is at

64 kbit/s or above, i.e. without subrates.

8.7.6.2 AP: / unit-x / conf-z / part-a, Status - Maintenance

Table 78: AP: / unit-x / conf-z / part-a, Status - Maintenance

Operation Name Parameter Name Range Description / Details
Line Status State In-Service Restore the normal operating state of the
participant.
Test-Pattern-Insertion Insert a test pattern “01” towards the partici-
pants conference.
For more information refer to section 7.3 DCE
Interface Line State Maintenance (on page 94).
Out-Of-Service Simulate a failed LEDS1 unit.
For more information refer to section 7.3 DCE
Interface Line State Maintenance (on page 94).

8.7.6.3 AP: / unit-x / conf-z / part-a, Status - CTP

Copyright 2022 Hitachi Energy. All rights reserved. 150

FOX61x | LEDS1 USER INTERFACE REFERENCE

Table 79: AP: / unit-x / conf-z / part-a, Status - CTP

Operation Name Parameter Name Range Description / Details
Trail Status Working Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0-nc sig-
nal is connected to, e.g. /unit-21/port-1/chan-
1.
Working Trail, Sta- OK No failure on the received signal at the
tus remote CTP.
SF Signal Fail status on the received signal at the
remote CTP.
CAS AIS CAS AIS status in the received signal at the
remote CTP, i.e. an all ‘1’ signal in time slot 16.
SD Signal Degraded status on the received signal
at the remote CTP.
Not Available The status of the received signal is not avail-
able at the remote CTP, e.g. when the local
CTPs role is a-end in a unidirectional connec-
tion.
Protecting Trail, <MO Address> Managed object address of the CTP (connec-
Remote CTP tion termination point) where the P0-nc sig-
nal is connected to, e.g. /unit-21/port-2/
chan-1.
Protecting Trail, OK No failure on the received signal at the
Status remote CTP.
SF Signal Fail status on the received signal at the
remote CTP.
CAS AIS CAS AIS status in the received signal at the
remote CTP, i.e. an all ‘1’ signal in time slot 16.
SD Signal Degraded status on the received signal
at the remote CTP.
Not Available The status of the received signal is not avail-
able at the remote CTP, e.g. when the local
CTPs role is a-end in a unidirectional connec-
tion.
Active Trail Working The trail from the a-end working remote CTP
has been selected.
Protecting The trail from the a-end protecting remote
CTP has been selected.
Not Available There is no active trail.
External Request Request Release Automatic trail selection.
Force Working Force the selector to use the trail from the a-
end working remote CTP.
Force Protecting Force the selector to use the trail from the a-
end protecting remote CTP.
Manual Working Prefer the trail from the a-end working
remote CTP. Use this trail only if the fault sta-
tus is not worse than the fault status of the
protecting trail.
Manual Protecting Prefer the trail from the a-end protecting
remote CTP. Use this trail only if the fault sta-
tus is not worse than the fault status of the
working trail.

Copyright 2022 Hitachi Energy. All rights reserved. 151

FOX61x | LEDS1 ANNEX

9 Annex

9.1 Associated FOX61x Documents

[1KHW028777] Release Note “FOX61x”

[1KHW002460] System Description “FOX61x”

[1KHW002497] Operating Instruction “Precautions and safety”

[1KHW002461] Installation Instruction “FOX615 R2 and FOX615 Installation”

[1KHW002462] Installation Instruction “FOX612 Installation”

[1KHW029142] Installation Instruction “FOX611 Installation”

[1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”

[1KHW028522] User Manual “Management Communication”

[1KHW002466] User Manual “FOXCST”

[1KHW002467] User Manual “TDM Services”

[1KHW029105] User Manual “Synchronization”

[1KHW002469] User Manual “CESM1, CESM1-F”

[1KHW028642] User Manual “CESM2, CESM2-F”

[1KHW028774] User Manual “CESM3”

[1KHW002473] User Manual “LEDE1”

[1KHW002476] User Manual “SAMO1”

[1KHW002498] Product Guide “FOX61x cables”

[1KHW028776] Product Description “Feature Licenses for FOX61x”

Copyright 2022 Hitachi Energy. All rights reserved. 152

Hitachi Energy Switzerland Ltd
Bruggerstrasse 72
5400 Baden - Switzerland

Phone: please refer to https://www.hitachienergy.com/contact-us/Customer-Connect-Center

(Customer Connect Center)
Email: [email protected]

www.hitachienergy.com/communication-networks

Document ID: 1KHW002478

Copyright 2022 Hitachi Energy. All rights reserved.

Specifications subject to change without notice.