1KHW000890-En NSD570 Operating Instructions (13th Ed. Aug. 2021)

OPERATING INSTRUCTION S
NSD570
Teleprotection Equipment
HITACHI ABB POWER GRIDS

Document number: 1KHW000890-EN
Document revision: 1st Edition 2002-12-20 7th Edition 2009-12-24

2nd Edition 2003-01-31 8th Edition 2011-02-20
3rd Edition 2003-09-01 9th Edition 2013-04-30
4th Edition 2004-04-16 10th Edition 2014-07-16
13th Edition 2021-08-12
Copyright and confidentiality: Copyright in this document vests in Hitachi Power Grids.
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
Power Grids.
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 Power Grids.
Disclaimer: ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Manufactured by/for a Hitachi Power Grids company.
ABB Power Grids Switzerland Ltd (hereinafter referred to as ABB Power Grids) has
taken reasonable care in compiling this document, however ABB Power Grids accepts
no liability whatsoever for any error or omission in the information contained herein and
gives no other warranty or undertaking as to its accuracy.
ABB Power Grids 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.
ABB Power Grids 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. ABB Power Grids 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 ABB Power Grids 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 2002-2021 Hitachi Power Grids. All rights reserved.

1. Introduction
2. Safety instructions
3. System description
4. User interface program
5. Configuration and settings
6. Installation and wiring
7. Commissioning
8. Operation and maintenance
9. Troubleshooting
10. Storage, decommissioning and disposal
11. Appendices
12. Annex
NSD570 1KHW000890-EN ABB Power Grids Switzerland Ltd
Contents
1. Introduction ............................................................. 1-1

1.1. Using these Operating Instructions .......................................... 1-2
1.2. Personnel qualifications ........................................................... 1-2
1.2.1. Operating personnel ................................................................ 1-2
1.2.2. Service personnel .................................................................... 1-3
1.3. Warranty restriction .................................................................. 1-3
2. Safety Instructions .................................................. 2-1

2.1. Presentation of safety information ........................................... 2-1
2.2. Basic principles ........................................................................ 2-2
2.3. General instructions ................................................................. 2-2
2.4. Product-specific instructions .................................................... 2-3
3. System Description ................................................. 3-1

3.1. Introduction .............................................................................. 3-1
3.1.1. General NSD570 Features ...................................................... 3-2
3.1.2. Features of the NSD570 Analog .............................................. 3-4
3.1.3. Features of the NSD570 Digital ............................................... 3-5
3.1.4. Features of the NSD570 Ethernet ............................................ 3-5
3.2. Communication channels......................................................... 3-7
3.3. System architecture ................................................................. 3-8
3.3.1. System block diagram.............................................................. 3-8
3.3.2. Mechanical design ................................................................. 3-10
3.3.3. External connections.............................................................. 3-11
3.3.4. Front plate Signals and Controls ............................................ 3-12
3.3.5. Service interface (COM 1) ..................................................... 3-12
3.3.6. Power supplies G3LH, G3LI, G3LK ....................................... 3-13
3.3.7. Examples of rack assemblies ................................................ 3-14
3.4. Module descriptions ............................................................... 3-19
3.4.1. Common Interface G3LC ....................................................... 3-19
3.4.1.1. Block diagram G3LC .............................................................. 3-19
3.4.1.2. Short description G3LC.......................................................... 3-20
3.4.2. Analog Line Interface G3LA ................................................... 3-21
3.4.2.1. Block diagram G3LA .............................................................. 3-21
3.4.2.2. Short description G3LA .......................................................... 3-21
3.4.2.3. External interfaces G3LA ....................................................... 3-22
3.4.2.4. Processor environment G3LA ................................................ 3-22
3.4.2.5. Transmitter G3LA .................................................................. 3-23
3.4.2.6. Receiver G3LA ...................................................................... 3-24
3.4.2.7. Boosting output G3LA ............................................................ 3-24
Contents August 2021 1-I

ABB Power Grids Switzerland Ltd 1KHW000890-EN NSD570
3.4.3. Digital Line Interface G3LD .................................................... 3-25

3.4.3.1. Block diagram G3LD .............................................................. 3-25
3.4.3.2. Short description G3LD.......................................................... 3-25
3.4.3.3. External interfaces G3LD ....................................................... 3-26
3.4.3.4. Processor environment G3LD................................................ 3-26
3.4.3.5. External cable and connector G3LD ...................................... 3-27
3.4.3.6. E1/T1 Interface G1LE ............................................................ 3-27
3.4.3.7. Optical Interface G1LO .......................................................... 3-28
3.4.3.8. Optical Interface G1LOa ........................................................ 3-29
3.4.4. Ethernet Line Interface G3LE ................................................ 3-30
3.4.4.1. Block diagram G3LE .............................................................. 3-30
3.4.4.2. Short description G3LE .......................................................... 3-30
3.4.4.3. External Interfaces G3LE ....................................................... 3-30
3.4.4.4. Processor environment G3LE ................................................ 3-31
3.4.4.5. External cable and connector G3LE ...................................... 3-31
3.4.5. Relay Interface G3LR ............................................................ 3-32
3.4.5.1. Block diagram G3LR .............................................................. 3-32
3.4.5.2. Short description G3LR.......................................................... 3-32
3.4.5.3. Inputs G3LR ........................................................................... 3-33
3.4.5.4. Solid state outputs G3LR ....................................................... 3-34
3.4.5.5. Relay contacts G3LR ............................................................. 3-34
3.4.5.6. Input Tripping Voltage G1LR ................................................. 3-35
3.4.5.7. External cable and connector G3LR ...................................... 3-35
3.4.6. GOOSE LAN Interface G3LS ................................................. 3-36
3.4.6.1. Block diagram G3LS .............................................................. 3-36
3.4.6.2. Short description G3LS .......................................................... 3-36
3.4.6.3. External Interfaces G3LS ....................................................... 3-37
3.4.6.4. Processor environment G3LS ................................................ 3-37
3.4.6.5. External cable and connector G3LS ...................................... 3-37
3.4.7. Display Panel G1LC............................................................... 3-38
3.4.7.1. Short description G1LC.......................................................... 3-38
3.4.7.2. How to use the Display Panel G1LC ...................................... 3-38
3.4.7.3. Menu structure Display Panel G1LC ...................................... 3-40
3.4.7.4. Additional features of Display Panel G1LC ............................ 3-44
3.4.8. LAN Interface G3LL ............................................................... 3-46
3.4.8.1. Short description G3LL .......................................................... 3-46
3.4.8.2. Block diagram G3LL .............................................................. 3-47
3.4.8.3. External cables and connectors G3LL ................................... 3-47
3.4.8.4. Restrictions associated with G3LS ........................................ 3-47
3.4.9. Management LAN Interface G3LM ........................................ 3-48
3.4.9.1. Short description G3LM ......................................................... 3-48
3.4.9.2. G3LM Services ...................................................................... 3-49
3.4.9.3. Block diagram G3LM ............................................................. 3-50
3.4.9.4. External Interfaces G3LM ...................................................... 3-50
3.4.9.5. Processor environment G3LM ............................................... 3-50
3.4.9.6. External cables and connectors G3LM .................................. 3-50
1-II August 2021 Contents

3.5. Functional description ............................................................ 3-51

3.5.1. General operating principle .................................................... 3-51
3.5.2. Signal processing .................................................................. 3-51
3.5.3. Analog operating principle ..................................................... 3-52
3.5.3.1. Single-tone principle .............................................................. 3-52
3.5.3.2. Dual-tone principle ................................................................. 3-53
3.5.3.3. Programming of the analog system ....................................... 3-53
3.5.4. Analog operating modes ........................................................ 3-55
3.5.4.1. 1 single tone command A ...................................................... 3-55
3.5.4.2. 2 independent single tone commands A, B............................ 3-56
3.5.4.3. 2 independent dual tone commands A, B .............................. 3-57
3.5.4.4. 3 independent dual tone commands A, B, C.......................... 3-58
3.5.4.5. 4 independent dual tone commands A, B, C, D ..................... 3-59
3.5.5. Processing of unused commands .......................................... 3-61
3.5.6. Digital operating principle....................................................... 3-61
3.5.6.1. Digital code structure ............................................................. 3-62
3.5.6.2. Digital frame structure ............................................................ 3-62
3.5.6.3. Programming of the digital system ......................................... 3-62
3.5.7. Digital operating modes ......................................................... 3-63
3.5.8. Ethernet operating principle ................................................... 3-63
3.5.8.1. Channel supervision .............................................................. 3-63
3.5.8.2. Command handling ................................................................ 3-65
3.5.8.3. Programming of the Ethernet system..................................... 3-65
3.5.9. Ethernet operating modes...................................................... 3-66
3.5.10. GOOSE operating principle ................................................... 3-66
3.5.11. GOOSE operating modes ...................................................... 3-67
3.5.12. Common functions ................................................................. 3-67
3.5.12.1. Command application ............................................................ 3-67
3.5.12.2. Unblocking ............................................................................. 3-68
3.5.12.3. Maximum Tx Input Monitoring ................................................ 3-68
3.5.12.4. Tx Input On-Delay .................................................................. 3-69
3.5.12.5. Transparent Tx Input and Rx Output Duration ....................... 3-70
3.5.12.6. Prolonged Tx Input and Rx Output Duration .......................... 3-70
3.5.12.7. Limited Tx Input and Rx Output Duration ............................... 3-71
3.5.12.8. Fixed Tx Input and Rx Output Duration.................................. 3-72
3.5.12.9. Command acknowledge ........................................................ 3-73
3.5.12.10. Rx Guard ............................................................................... 3-73
3.5.13. Functions of the analog system ............................................. 3-74
3.5.13.1. Transmit level setting / Transmit level monitoring .................. 3-74
3.5.13.2. Receive level setting / Receive level monitoring .................... 3-74
3.5.13.3. Boosting / Boost Output ......................................................... 3-74
3.5.13.4. Embedded Operation Channel (EOC) ................................... 3-75
3.5.14. Functions of the digital system ............................................... 3-76
3.5.14.1. Bit error rate monitoring ......................................................... 3-76
3.5.14.2. Addressing ............................................................................. 3-76
Contents August 2021 1-III

3.5.15. Functions of the Ethernet system .......................................... 3-78

3.5.15.1. Transmission Time and Packet Loss monitoring ................... 3-78
3.5.15.2. Security functions .................................................................. 3-79
3.5.16. Event Recorder ...................................................................... 3-80
3.5.16.1. General .................................................................................. 3-80
3.5.16.2. Command events ................................................................... 3-81
3.5.16.3. Alarm events .......................................................................... 3-81
3.5.16.4. Manipulation events ............................................................... 3-81
3.5.16.5. RTC synchronization from an external clock .......................... 3-82
3.5.17. Counters ................................................................................ 3-82
3.5.18. Test facilities for the Line Interfaces ...................................... 3-83
3.5.18.1. Testing during normal operation ............................................ 3-83
3.5.18.2. Cyclic Loop Test .................................................................... 3-83
3.5.18.3. Manual Loop Test .................................................................. 3-85
3.5.18.4. Local Test Mode .................................................................... 3-86
3.5.18.5. Remote Test Mode ................................................................ 3-86
3.5.19. Test facilities for the GOOSE LAN Interface .......................... 3-87
3.5.19.1. Overview ................................................................................ 3-87
3.5.19.2. Test command acceptance .................................................... 3-87
3.5.19.3. Test command transmission .................................................. 3-88
3.6. NSD570 Applications ............................................................. 3-88
3.6.1. Permissive tripping schemes ................................................. 3-89
3.6.1.1. Permissive underreaching transfer tripping (PUTT) ............... 3-90
3.6.1.2. Permissive overreaching transfer tripping (POTT) ................. 3-91
3.6.2. Blocking schemes .................................................................. 3-91
3.6.3. Unblocking ............................................................................. 3-93
3.6.4. Earth fault protection .............................................................. 3-95
3.6.5. Duplicated main protection .................................................... 3-96
3.6.6. Direct transfer tripping............................................................ 3-98
3.6.6.1. Line protection ....................................................................... 3-99
3.6.6.2. Re-closure lock out ................................................................ 3-99
3.6.6.3. Breaker back-up protection .................................................. 3-100
3.6.6.4. Shunt reactor protection....................................................... 3-100
3.6.6.5. Transformer protection......................................................... 3-101
3.6.6.6. Power system instability....................................................... 3-101
3.6.6.7. Generator shutdown and load shedding .............................. 3-102
3.6.6.8. Typical requirements in direct tripping applications ............. 3-103
3.6.7. Teed lines and tapped lines ................................................. 3-104
3.6.7.1. NSD570 Analog/Digital/Ethernet in “normal” T-operation .... 3-106
3.6.7.2. NSD570 Analog/Digital/Ethernet in “inverse” T-operation .... 3-107
3.6.7.3. Addressing of NSD570 Digital in T-operation ...................... 3-108
3.6.7.4. Tapped lines ........................................................................ 3-110
3.6.8. Phase-Segregated Command Transmission ....................... 3-112
3.6.8.1. Twin Line - Two Systems on Common Towers .................... 3-112
3.6.8.2. Long Single EHV Overhead Line ......................................... 3-113
1-IV August 2021 Contents

4. User interface program ........................................... 4-1

4.1. Introduction .............................................................................. 4-1
4.2. Safety instruction ..................................................................... 4-2
4.3. System requirements and technical data for HMI570 .............. 4-2
4.4. Installation of HMI570 .............................................................. 4-2
4.5. Communication between the HMI570 PC and the NSD570..... 4-2
4.5.1. Local connection ...................................................................... 4-3
4.5.2. Remote connection over (EOC) ............................................... 4-4
4.6. Remote connection over LAN / WAN / Internet ........................ 4-4
4.6.1. Use of LAN Interfaces G3LL / G3LM ....................................... 4-4
4.6.2. Security considerations for connections over Internet.............. 4-5
4.7. Multiple connection .................................................................. 4-6
4.8. Browser front end .................................................................... 4-7
4.8.1. Browser settings ...................................................................... 4-7
4.8.1.1. Additional browser settings for the HMI570 LAN ..................... 4-7
4.9. Starting the program ................................................................ 4-7
4.9.1. HMI570 PC .............................................................................. 4-7
4.9.1.1. Start HMI570 PC Server and Client Simultaneously ................ 4-7
4.9.1.2. Start HMI570 PC Server .......................................................... 4-8
4.9.1.3. Stop HMI570 PC Server .......................................................... 4-8
4.9.1.4. Start HMI570 PC Client............................................................ 4-8
4.9.1.5. Change HMI570 PC Server Settings ....................................... 4-9
4.9.2. HMI570 LAN .......................................................................... 4-10
4.10. Operation ............................................................................... 4-10
4.10.1. Introduction ............................................................................ 4-10
4.10.2. Basic operation principles ...................................................... 4-10
4.10.3. Design.................................................................................... 4-11
4.10.4. Log-in / Log-off ....................................................................... 4-11
4.10.4.1. Connect / Disconnect Device ................................................. 4-13
4.10.4.2. Connect Device ..................................................................... 4-14
4.10.4.3. Error messages and troubleshooting ..................................... 4-15
4.10.4.4. Disconnect Device ................................................................. 4-17
4.10.5. Configuration ......................................................................... 4-17
4.10.5.1. Load From Disk ..................................................................... 4-17
4.10.5.2. View Configuration ................................................................. 4-18
4.10.5.3. Edit Configuration .................................................................. 4-18
4.10.5.4. Save To Disk ......................................................................... 4-25
4.10.5.5. Discard Configuration ............................................................ 4-25
4.10.5.6. Download To Device .............................................................. 4-25
4.10.5.7. Upload From Device .............................................................. 4-26
4.10.6. Event Recorder ...................................................................... 4-26
4.10.6.1. Load From Disk ..................................................................... 4-26
4.10.6.2. View Events ........................................................................... 4-26
4.10.6.3. Save To Disk ......................................................................... 4-26
4.10.6.4. Upload Events ....................................................................... 4-27
Contents August 2021 1-V

4.10.6.5. Clear Event Recorder ............................................................ 4-27

4.10.6.6. Import events into a spreadsheet or word processing tool ..... 4-27
4.10.7. Status / Alarm ........................................................................ 4-27
4.10.7.1. Upload Status ........................................................................ 4-27
4.10.7.2. Upload Alarm ......................................................................... 4-30
4.10.7.3. Trip Counter ........................................................................... 4-31
4.10.8. Maintenance .......................................................................... 4-31
4.10.8.1. Manual Loop Test .................................................................. 4-31
4.10.8.2. Reset Device ......................................................................... 4-31
4.10.8.3. Previous Configuration........................................................... 4-32
4.10.8.4. Set Time and Date ................................................................. 4-32
4.10.8.5. Get Time and Date................................................................. 4-32
4.10.8.6. Device Communication .......................................................... 4-32
4.10.8.7. Set WAN Password (NSD570 Ethernet WAN Interface only) 4-33
4.10.8.8. Firmware Download ............................................................... 4-33
4.10.9. Commissioning ...................................................................... 4-34
4.10.9.1. Line Interfaces ....................................................................... 4-34
4.10.9.2. GOOSE LAN Interface ........................................................... 4-34
4.10.10. Exit HMI570 ........................................................................... 4-35
4.11. Alarm Polling .......................................................................... 4-35
4.11.1. Impact when the Alarm Polling is started ............................... 4-37
4.11.2. Start Alarm Polling ................................................................. 4-38
4.11.3. Stop Alarm Polling ................................................................. 4-38
4.11.4. Configure Alarm Polling ......................................................... 4-38
4.11.5. Graphical View ....................................................................... 4-39
4.11.6. View Entire Logfile ................................................................. 4-40
4.11.7. View Latest 50 Entries ........................................................... 4-40
4.11.8. Clear Entire Logfile ................................................................ 4-40
4.11.9. Refresh Page ......................................................................... 4-40
4.11.10. Stop Refreshing ..................................................................... 4-40
4.11.11. Start Auto Pop-Up .................................................................. 4-40
4.11.12. Stop Auto Pop-Up .................................................................. 4-41
4.11.13. Multiple users (in case of HMI570 LAN version) .................... 4-41
4.12. Network Alarm Polling............................................................ 4-41
4.12.1. Start Network Alarm Polling ................................................... 4-42
4.12.2. Stop Network Alarm Polling ................................................... 4-43
4.12.3. Configure Network Alarm Polling ........................................... 4-43
4.12.3.1. Configure LAN-Interfaces List ................................................ 4-44
4.12.3.2. Configure General Network Alarm Polling Settings ............... 4-45
4.12.4. Graphical View ....................................................................... 4-46
4.12.4.1. Summary information ............................................................. 4-46
4.12.4.2. Detailed polling information.................................................... 4-47
4.12.4.3. Pause Alarm Polling............................................................... 4-48
4.12.5. Starting and Stopping Local Alarm Polling on LAN Interface
during Network Alarm Polling ................................................. 4-49
4.13. Management .......................................................................... 4-49
1-VI August 2021 Contents

4.13.1. User Activity Logging ............................................................. 4-49

4.13.1.1. Load From Disk ..................................................................... 4-50
4.13.1.2. Save To Disk ......................................................................... 4-50
4.13.1.3. View ....................................................................................... 4-50
4.13.1.4. Upload Entries ....................................................................... 4-51
4.13.1.5. Clear Logfile ........................................................................... 4-51
4.13.2. User Administration................................................................ 4-51
4.13.3. SNMPv3 User Management .................................................. 4-52
4.13.4. Certificate Management ......................................................... 4-52
4.13.5. Start SNMP Event Polling ...................................................... 4-53
4.13.6. Stop SNMP Event Polling ...................................................... 4-53
4.14. HMI570 Settings .................................................................... 4-54
4.14.1. User Administration and Permissions .................................... 4-54
4.14.2. Change password .................................................................. 4-55
4.14.3. Device Communication .......................................................... 4-56
4.14.4. LAN Interface ......................................................................... 4-56
4.14.5. Export Settings ...................................................................... 4-56
4.14.6. Import Settings ....................................................................... 4-57
4.14.7. About ..................................................................................... 4-57
5. Configuration and Settings .................................... 5-1

5.1. Introduction .............................................................................. 5-1
5.2. Configuration ........................................................................... 5-2
5.3. Use of HMI570 files.................................................................. 5-2
5.4. Configuration with HMI570....................................................... 5-3
5.4.1. Configure device type .............................................................. 5-3
5.4.2. Configure device parameters ................................................... 5-3
5.5. General configuration notes ..................................................... 5-4
5.5.1. 1+1 Device Operation Mode .................................................... 5-4
5.5.2. Status of the command outputs during a link failure ................ 5-5
5.5.3. Link Propagation Time ............................................................. 5-7
5.6. Configuration notes for NSD570 Analog .................................. 5-8
5.6.1. Analog Channel selection ........................................................ 5-8
5.6.2. Parallel operation of analog NSD570s ..................................... 5-9
5.6.3. 2-wire and 4-wire operation of NSD570 Analog ..................... 5-11
5.6.4. Transmit level and power boosting for NSD570 Analog......... 5-11
5.6.5. Receive level for NSD570 Analog .......................................... 5-13
5.6.6. NSD570 Analog over PLC equipment ETL500 or ETL600 .... 5-13
5.7. Configuration notes for NSD570 Digital ................................. 5-16
5.7.1. Digital channel selection ........................................................ 5-16
5.7.2. G.703 interface application notes .......................................... 5-16
5.7.3. RS-530 (RS-422/V.11) interface application notes ................ 5-17
5.7.3.1. Transmit and receive timing provided by the DCE ................. 5-17
5.7.3.2. Transmit timing provided by the DCE .................................... 5-18
5.7.3.3. Transmit timing for the DCE provided by G3LD ..................... 5-19
Contents August 2021 1-VII

5.7.3.4. Transmit and receive timing generated internally (G3LD) ...... 5-20
5.7.4. E1/T1 Interface application notes .......................................... 5-21
5.7.4.1. E1 Interface ........................................................................... 5-21
5.7.4.2. T1 Interface............................................................................ 5-22
5.7.5. Optical interface application notes ......................................... 5-22
5.7.5.1. Optical Direct Fiber and Optical OTERM/OPTIF Interface ..... 5-22
5.7.5.2. Optical IEEE C37.94 Interface ............................................... 5-23
5.8. Configuration notes common for G3LE, G3LM and G3LS ..... 5-24
5.8.1. General .................................................................................. 5-24
5.8.2. Ethernet interface selection ................................................... 5-24
5.8.3. RJ45 interface configuration .................................................. 5-25
5.8.4. SFP module configuration...................................................... 5-26
5.8.5. GPS synchronization ............................................................. 5-26
5.9. Configuration notes for Ethernet WAN Interface G3LE .......... 5-27
5.9.1. General .................................................................................. 5-27
5.9.2. Ethernet WAN interface configuration .................................... 5-27
5.9.3. Priority settings on transport layer (IPv4 Routing) .................. 5-28
5.9.4. VLAN ID ................................................................................. 5-29
5.9.5. Link layer priority settings ...................................................... 5-29
5.9.6. Supervision and alarm settings .............................................. 5-29
5.9.7. Network configuration hints.................................................... 5-30
5.10. Configuration notes for NSD570 Management ...................... 5-31
5.10.1. General .................................................................................. 5-31
5.10.2. Ethernet LAN interface configuration ..................................... 5-31
5.10.3. VLAN ID ................................................................................. 5-32
5.10.4. Link layer priority settings ...................................................... 5-32
5.10.5. SNMP .................................................................................... 5-32
5.10.5.1. Overview ................................................................................ 5-32
5.10.5.2. Device information ................................................................. 5-33
5.10.5.3. Alarm information ................................................................... 5-34
5.10.5.4. Command and Manipulation Event information ..................... 5-34
5.10.5.5. Trip Counter information ........................................................ 5-36
5.10.5.6. Configuration download counter information.......................... 5-37
5.10.5.7. Traps...................................................................................... 5-38
5.10.5.8. SNMP configuration ............................................................... 5-38
5.10.5.9. SNMPv2-SMI standard MIB configuration ............................. 5-39
5.10.6. SNTP Client ........................................................................... 5-39
5.10.6.1. Overview ................................................................................ 5-39
5.10.6.2. SNTP primary and secondary servers ................................... 5-40
5.10.6.3. SNTP polling interval ............................................................. 5-40
5.10.6.4. Time zone offset from UTC .................................................... 5-40
5.10.6.5. Daylight Saving Time ............................................................. 5-40
5.11. Configuration notes for NSD570 GOOSE LAN interface ....... 5-41
5.11.1. General .................................................................................. 5-41
5.11.2. GOOSE Interface Configuration ............................................ 5-41
5.11.2.1. Number of protection commands ........................................... 5-41
1-VIII August 2021 Contents

5.11.2.2. Network configuration hints.................................................... 5-42

5.11.2.3. GPS synchronization ............................................................. 5-42
5.11.3. IEC 61850 Configuration........................................................ 5-42
5.12. Configuration examples ......................................................... 5-43
5.12.1. Example of NSD570 Analog configuration ............................. 5-43
5.12.2. Example of NSD570 Digital configuration .............................. 5-48
5.12.3. Example of NSD570 Digital configuration for T-operation...... 5-53
5.12.3.1. TPE1 and TPE 2 in T-station ................................................. 5-53
5.12.3.2. TPE1 in station A (connected to TPE1 in T-station) ............... 5-56
5.12.3.3. TPE1 in station B (connected to TPE2 in T-station) ............... 5-59
5.12.4. Example of NSD570 Ethernet configuration .......................... 5-62
5.12.5. Example of NSD570 GOOSE LAN configuration ................... 5-67
5.12.6. Example of NSD570 Management configuration ................... 5-68
5.13. Performance criteria............................................................... 5-70
5.13.1. General .................................................................................. 5-70
5.13.2. Transmission time .................................................................. 5-71
5.13.2.1. Nominal transmission time ..................................................... 5-72
5.13.2.2. Maximum actual transmission time ........................................ 5-73
5.13.2.3. Transmission time with G3LS ................................................ 5-73
5.13.3. Security .................................................................................. 5-74
5.13.4. Security measurements ......................................................... 5-75
5.13.5. Dependability ......................................................................... 5-75
5.13.6. Dependability measurements ................................................ 5-76
6. Installation and wiring ............................................ 6-1

6.1. Introduction .............................................................................. 6-1
6.2. Safety instructions ................................................................... 6-1
6.2.1. General .................................................................................... 6-3
6.3. Unpacking ................................................................................ 6-3
6.3.1. Inspection upon receipt ............................................................ 6-3
6.3.2. What to do if there is transport damage ................................... 6-3
6.3.3. Precautions to avoid transport damage ................................... 6-4
6.4. Installation................................................................................ 6-4
6.4.1. Place of installation and ambient conditions ............................ 6-4
6.4.2. Cabinet .................................................................................... 6-4
6.4.3. Installing racks in cabinets ....................................................... 6-5
6.5. Wiring....................................................................................... 6-5
6.5.1. Introduction .............................................................................. 6-5
6.5.2. Grounding system .................................................................... 6-5
6.5.3. External connections................................................................ 6-5
6.5.3.1. Power Supply ........................................................................... 6-9
6.5.3.2. Station bus and Real Time Clock synchronization ................. 6-10
6.5.3.3. System alarm relays .............................................................. 6-11
6.5.3.4. Relay Interface G3LR ............................................................ 6-13
6.5.3.5. Analog Interface G3LA........................................................... 6-15
Contents August 2021 1-IX

6.5.3.6. Digital Interface G3LD............................................................ 6-17

6.5.3.7. LAN Interface G3LL ............................................................... 6-30
6.5.3.8. Ethernet Interfaces G3LE, G3LM, G3LS................................ 6-33
6.5.4. Connection via Cable for all Interfaces with RJ45 Connector 6-37
6.5.4.1. Patch panel V9OZ with 1 x RJ45 ........................................... 6-38
6.5.5. Internal connections ............................................................... 6-38
6.5.6. Display Panel G1LC............................................................... 6-39
6.6. Photographs .......................................................................... 6-40
7. Commissioning ....................................................... 7-1

7.2. Testing the communication channel ........................................ 7-4
7.3. Commissioning the equipment ................................................. 7-4
7.3.1. Preliminary inspection and checks ........................................... 7-4
7.3.2. Checks according to commissioning instructions ..................... 7-5
7.3.3. HMI570 functions to support commissioning ........................... 7-5
8. Operation and maintenance ................................... 8-1

8.2. Operation ................................................................................. 8-4
8.2.1. Normal operation ..................................................................... 8-4
8.2.2. Equipment failure ..................................................................... 8-4
8.3. Maintenance ............................................................................ 8-5
8.3.1. Periodic functional checks ....................................................... 8-5
8.3.1.1. Check input power supply voltage ........................................... 8-5
8.3.1.2. Checks during operation .......................................................... 8-6
8.3.1.3. Check status data .................................................................... 8-7
8.3.1.4. Check alarm events ................................................................. 8-7
8.3.1.5. Alarm polling for several NSD570 in a substation .................... 8-7
8.3.1.6. Check AF line levels ................................................................ 8-7
8.3.1.7. Check bit error rates ................................................................ 8-8
8.3.1.8. Check Packet Loss Rates and Transmission Times ................ 8-8
8.3.1.9. Removing the equipment from service for testing .................... 8-8
8.3.1.10. Checking the entire link............................................................ 8-9
9. Troubleshooting ...................................................... 9-1

9.2. Fuses ....................................................................................... 9-4
9.3. Alarms...................................................................................... 9-4
9.3.1. Alarm concept .......................................................................... 9-4
9.3.2. Problem localization ................................................................. 9-5
9.3.3. Alarm pick up and hold delay ................................................... 9-6
1-X August 2021 Contents

9.3.4. High level and user alarms ...................................................... 9-6

9.3.5. Low level common alarms and relay interface alarms ............. 9-8
9.3.6. Analog interface alarms ......................................................... 9-12
9.3.7. Digital interface alarms .......................................................... 9-13
9.3.8. Ethernet interface alarms ....................................................... 9-15
9.3.9. Management interface alarms ............................................... 9-16
9.3.10. GOOSE LAN interface alarms ............................................... 9-17
9.3.11. List of low level alarms and corrective actions ....................... 9-18
9.3.12. Alarm event recorder ............................................................. 9-31
9.3.13. Alarm polling .......................................................................... 9-31
9.4. Warnings................................................................................ 9-32
9.5. Some basic checks ................................................................ 9-32
9.6. Frequently asked questions ................................................... 9-33
9.6.1. General .................................................................................. 9-33
9.6.2. Where can I get the latest version of this FAQ? ..................... 9-36
9.7. Replacing faulty modules ....................................................... 9-36
9.8. Returning modules for repair ................................................. 9-36
9.9. Support .................................................................................. 9-37
10. Storage, decommissioning and disposal ........... 10-1

10.1. Safety instructions ................................................................. 10-1
10.2. Storage .................................................................................. 10-2
10.3. Decommissioning .................................................................. 10-2
10.4. Disposal ................................................................................. 10-3
11. Appendices ............................................................ 11-1

11.1. Order numbers ....................................................................... 11-1
11.2. Photographs .......................................................................... 11-7
11.2.1. Front view of NSD570 ............................................................ 11-7
11.2.2. Rear view of NSD570 ............................................................ 11-7
11.3. Dimension Drawing Module Rack G7BI ................................. 11-8
Contents August 2021 1-XI

List of Figures
Fig. 1-1 Front view of NSD570 ........................................................................ 1-1
Fig. 3-1 Communication channels ................................................................... 3-7
Fig. 3-2 System block diagram ........................................................................ 3-8
Fig. 3-3 Mechanical design ........................................................................... 3-10
Fig. 3-4 Front plate signals and controls ....................................................... 3-12
Fig. 3-5 Minimal equipment Analog ............................................................... 3-14
Fig. 3-6 Minimal equipment Digital ................................................................ 3-15
Fig. 3-7 Minimal equipment Ethernet ............................................................ 3-16
Fig. 3-8 Two independent NSD570 in the same rack .................................... 3-17
Fig. 3-9 Fully equipped rack with redundant power supply units ................... 3-18
Fig. 3-10 Block diagram G3LC ........................................................................ 3-19
Fig. 3-11 Block diagram G3LA ........................................................................ 3-21
Fig. 3-12 Block diagram G3LD ........................................................................ 3-25
Fig. 3-13 Block diagram G3LE ........................................................................ 3-30
Fig. 3-14 Block diagram G3LR ........................................................................ 3-32
Fig. 3-15 Block diagram G3LS ........................................................................ 3-36
Fig. 3-16 Display Panel G1LC ......................................................................... 3-38
Fig. 3-17 Disabling reset counters................................................................... 3-45
Fig. 3-18 Connection to the NSD570 devices via G3LL .................................. 3-46
Fig. 3-19 Block diagram G3LL ......................................................................... 3-47
Fig. 3-20 Connection to the NSD570 devices via G3LM ................................. 3-48
Fig. 3-21 Block diagram G3LM ........................................................................ 3-50
Fig. 3-22 Single-tone principle......................................................................... 3-53
Fig. 3-23 Dual-tone principle ........................................................................... 3-53
Fig. 3-24 Channel allocation with analog NSD570 .......................................... 3-54
Fig. 3-25 1 single tone command A................................................................. 3-55
Fig. 3-26 2 independent single tone commands A, B...................................... 3-56
Fig. 3-27 2 independent dual tone commands A, B ........................................ 3-57
Fig. 3-28 3 independent dual tone commands A, B, C .................................... 3-58
Fig. 3-29 4 independent dual tone commands A, B, C, D ............................... 3-59
Fig. 3-30 Channel supervision......................................................................... 3-64
Fig. 3-31 Command handling .......................................................................... 3-65
Fig. 3-32 GOOSE frame flow example ............................................................ 3-66
Fig. 3-33 Tx Input On-Delay ............................................................................ 3-69
Fig. 3-34 Prolonged Tx Input Duration ............................................................ 3-70
Fig. 3-35 Limited Tx Input Duration ................................................................. 3-71
Fig. 3-36 Fixed Tx Input Duration .................................................................... 3-72
1-XII August 2021 Contents

Fig. 3-37 Example G3LS commissioning ........................................................ 3-87

Fig. 3-38 Duplicated line protection and breaker-failure protection of an
important single circuit ..................................................................... 3-97
Fig. 3-39 Duplicated line protection of a twin line, with breaker-failure
protection on each circuit ................................................................. 3-98
Fig. 3-40 T-operation principle ...................................................................... 3-105
Fig. 3-41 Addressing example for normal T-operation .................................. 3-109
Fig. 3-42 Addressing example for inverse T-operation ................................. 3-110
Fig. 3-43 Twin Line - Two Systems on Common Towers .............................. 3-112
Fig. 4-1 Example for local connection ............................................................. 4-3
Fig. 4-2 Remote connection over EOC ........................................................... 4-4
Fig. 4-3 Remote connection over LAN / WAN / Internet .................................. 4-4
Fig. 4-4 Multiple connection from local and remote ......................................... 4-6
Fig. 4-5 Multiple connection via the station bus .............................................. 4-6
Fig. 4-6 Alarm Polling over LAN Interface in an NSD570 network ................ 4-36
Fig. 4-7 Alarm Polling over RS-232 Interface in an NSD570 network ........... 4-36
Fig. 4-8 Network Alarm Polling ...................................................................... 4-42
Fig. 4-9 Inside Network Alarm Polling ........................................................... 4-45
Fig. 5-1 G.703 interface application .............................................................. 5-16
Fig. 5-2 RS-530 interface application with Tx and Rx timing by DCE ........... 5-18
Fig. 5-3 RS-530 interface application with Tx and Rx timing by DCE ........... 5-18
Fig. 5-4 RS-530 interface application with Tx timing by DCE ........................ 5-19
Fig. 5-5 RS-530 interface application with TT for DCE by G3LD .................. 5-19
Fig. 5-6 RS-530 interface application with Tx/Rx timing internally ................ 5-20
Fig. 5-7 Optical or electrical interface selection ............................................. 5-25
Fig. 5-8 IP address configuration .................................................................. 5-27
Fig. 5-9 G3LM MIB Tree................................................................................ 5-33
Fig. 5-10 G3LS transmission time ................................................................... 5-73
Fig. 6-1 Mounting of external cables with cable screen .................................. 6-6
Fig. 6-2 Mounting of external cables with cable screen (G3LL and
G3LMa) .............................................................................................. 6-7
Fig. 6-3 Mounting of external optical cables (G1LOa) ..................................... 6-8
Fig. 6-4 Supply connections ............................................................................ 6-9
Fig. 6-5 Connector for station bus and Real Time Clock synchronization ..... 6-10
Fig. 6-6 Station bus and Real Time Clock synchronization ........................... 6-11
Fig. 6-7 Connector for system alarm relays .................................................. 6-12
Fig. 6-8 G3LC cable for alarm relays ............................................................ 6-12
Fig. 6-9 Connector for relay interface ............................................................ 6-13
Contents August 2021 1-XIII

Fig. 6-10 G3LR cable for relay interface ......................................................... 6-14

Fig. 6-11 Piggyback G1LR Input Tripping Voltage .......................................... 6-14
Fig. 6-12 Connector for analog interface ......................................................... 6-15
Fig. 6-13 G3LA cable for analog interface ....................................................... 6-16
Fig. 6-14 Connector for digital interface (male D-sub 25 poles) ...................... 6-17
Fig. 6-15 G3LD cable with isolating terminals (10 poles) ................................ 6-18
Fig. 6-16 G3LD cable with RS-449 interface (male D-sub connector 37
poles) ............................................................................................... 6-18
Fig. 6-17 G3LD cable with RS-530 interface (male D-sub connector 25
poles) ............................................................................................... 6-19
Fig. 6-18 G3LD cable with X.21 interface (male D-sub connector 15 poles) .. 6-19
Fig. 6-19 Connector for G.703 codirectional interface (RJ45, 8 poles) .......... 6-20
Fig. 6-20 G.703 co-directional interface with cable for all interfaces with
RJ45 connector ................................................................................ 6-21
Fig. 6-21 Connector for E1/T1 interface (RJ45, 8 poles) ................................. 6-21
Fig. 6-22 E1/T1 interface with cable for all interfaces with RJ45 connector .... 6-22
Fig. 6-23 Connectors for optical fibers ............................................................ 6-23
Fig. 6-24 Optical Interface G1LO with optical cable ........................................ 6-24
Fig. 6-25 E-2000 duplex compact mating adapters ..................................... 6-24
Fig. 6-26 E-2000 duplex compact fiber optic connector ............................... 6-25
Fig. 6-27 E-2000 simplex fiber optic connector ............................................ 6-25
Fig. 6-28 Optical SFP module installation ....................................................... 6-27
Fig. 6-29 Duplex LC to ST adapter cable ........................................................ 6-28
Fig. 6-30 Duplex LC to FC/PC adapter cable .................................................. 6-28
Fig. 6-31 Duplex LC to LC adapter cable ........................................................ 6-29
Fig. 6-32 Connector for Ethernet interface (RJ45, 8 poles) ............................. 6-30
Fig. 6-33 Ethernet interface with cable for all interfaces with RJ45
connector ......................................................................................... 6-31
Fig. 6-34 Connector for station bus interface (7 poles) ................................... 6-32
Fig. 6-35 Connectors of the Ethernet interface ............................................... 6-33
Fig. 6-36 Optical SFP module installation ....................................................... 6-35
connector ......................................................................................... 6-36
Fig. 6-38 Ethernet interface with cable for RTC synchronisation .................... 6-37
Fig. 6-39 Patch panel V9OZ with 1 x RJ45 ..................................................... 6-38
Fig. 6-40 Mounting of the Display Panel G1LC ............................................... 6-39
Fig. 6-41 Correct connection of the ribbon cable ............................................ 6-39
1-XIV August 2021 Contents

Fig. 6-42 Front view of the NSD570 module rack, equipped with two line
interfaces - each of them operating four Relay Interfaces G3LR -
and the optional Display Panel G1LC. ............................................. 6-40
Fig. 6-43 Rear view of the NSD570 module rack, equipped with an Analog
Interface G3LA and a Digital Interface G3LD - each of them
operating four Relay Interfaces G3LR, with connecting cables
(rear cover removed). ....................................................................... 6-40
Fig. 9-1 The four major fault location areas of an NSD570 link ....................... 9-5
Fig. 11-1 Front view of NSD570 ...................................................................... 11-7
Fig. 11-2 Rear view of NSD570 ....................................................................... 11-7
Fig. 11-3 Front view......................................................................................... 11-8
Fig. 11-4 Top view ........................................................................................... 11-8
Fig. 11-5 Side view .......................................................................................... 11-9
Contents August 2021 1-XV

List of Tables
Table 3-1 Power supply voltages ..................................................................... 3-13
Table 4-1 RS-232 default interface settings ....................................................... 4-3
Table 4-2 Permissions “View” and “Modify” ..................................................... 4-55
Table 5-1 Minimum frequency gaps between channels ..................................... 5-9
Table 5-2 Relative levels for different bandwidths ............................................ 5-10
Table 5-3 Rx level setting and maximum line level .......................................... 5-13
Table 5-4 List of polled command and manipulation events ............................ 5-36
Table 9-1 Alarm localization with link and hardware alarms .............................. 9-6
Table 9-2 High level alarms................................................................................ 9-8
Table 9-3 Low level common alarms and relay interface alarms ..................... 9-11
Table 9-4 Transmit and receive signal alarm ................................................... 9-12
Table 9-5 SNR alarm threshold ........................................................................ 9-12
Table 9-6 Low level analog interface alarms .................................................... 9-13
Table 9-7 Low level digital interface alarms ..................................................... 9-14
Table 9-8 Low level Ethernet interface alarms ................................................. 9-15
Table 9-9 LAN LEDs ........................................................................................ 9-16
Table 9-10 G3LM alarms and warnings ............................................................. 9-17
Table 9-11 G3LS alarms .................................................................................... 9-18
Table 9-12 Low level alarms with explanation and corrective actions ................ 9-31
Table 11-1 Order numbers ................................................................................. 11-5
Table 11-2 Order numbers accessories ............................................................. 11-6
1-XVI August 2021 Contents

Abbreviations
AC Alternating Current
AF Audio Frequency
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
AWG American Wire Gauge
BER Bit Error Rate
C Common (terminal of switchover relays)
CCF Communication Configuration File (ABB proprietary)
CID Configured IED Description
CPU Central Processing Unit
DC Direct Current
DCE Data Circuit-terminating Equipment
DSP Digital Signal Processor
DSCP Differentiated Services Code Point
DTE Data Terminal Equipment
DST Daylight Saving Time
EMC Electromagnetic Compatibility
EOC Embedded Operation Channel
ESD Electrostatic Discharge
FPGA Field Programmable Gate Array
GOOSE Generic Object Oriented Substation Events
FSK Frequency Shift Keying
GPS Global Positioning System
HF High Frequency
HMI Human Machine Interface
HMI570 NSD570 User Interface Program
HTML Hyper Text Markup Language
HTTP Hyper Text Transfer Protocol
HTTPS Hyper Text Transfer Protocol Secure
ICD IED Capability Description
IEC International Engineering Consortium
ID Identification
IEC International Electrotechnical Commission
Contents August 2021 1-XVII

IED Intelligent Electronic Device

IEDET IED Engineering Tool
IEEE Institute of Electrical and Electronics Engineers
IID Instantiated IED Description
IP Internet Protocol
ITPC LN Interfacing Teleprotection Communication
ITU-T International Telecommunication Union – Telecommunication
Standardization Sector of ITU
LAN Local Area Network
LED Light Emitting Diode
LN Logical Node
LOS Loss Of Signal
MAC Media Access Control
MC / µC Micro Controller
MM Multi-Mode
MMS Manufacturing Message Specification
N.A. / n.a. Not Applicable or Not Available
NC Normally Closed (terminal of switchover relays)
NO Normally Open (terminal of switchover relays)
OSI Open Systems Interconnection
PC Personal Computer
PDH Plesiochronous Digital Hierarchy
PE Protective Earth
PHY Physical Layer (according to the OSI Model)
PLC Power Line Carrier
(communication via the high-voltage line)
PLR Packet Loss Rate
RAM Random Access Memory
RD Receive Data
RF Radio Frequency
RFC Request For Comments
RMS Root Mean Square
RSTP Rapid Spanning Tree Protocol
RT Receive Timing
RT-Bus Real Time Bus
1-XVIII August 2021 Contents

RTC Real Time Clock

Rx Receive(r)
SA Substation Automation
SCD Substation Configuration Description
SCL Substation Configuration Language
SD Send Data
SD-RAM Synchronous Dynamic Random Access Memory
SDH Synchronous Digital Hierarchy
SFP Small Formfactor Pluggable
SM Single-Mode
SMD Surface Mounted Device
SNMP Simple Network Management Protocol
SNR Signal to noise ratio
SNTP Simple Network Time Protocol
SONET Synchronous Optical Network
ST Send Timing
STP Shielded Twisted Pairs or Spanning Tree Protocol
TCP Transmission Control Protocol
TOS Type of Service
TOY Time of Year
TPE Teleprotection Equipment
TT Terminal Timing
Tx Transmit(ter)
UTC Universal Time Coordinated
UDP User Datagram Protocol
UTP Unshielded Twisted Pairs
VLAN Virtual Local Area Network
VLAN ID Virtual Local Area Network Identifier
WAN Wide Area Network
XML Extensible Mark-up Language
Contents August 2021 1-XIX

1. Introduction
The NSD570 teleprotection equipment is used for the dependable and
secure transmission of protection commands in electrical power
systems. In the event of a fault it makes a decisive contribution to
rapidly and selectively isolating the faulty part.
The NSD570 can be used for the transmission of blocking and tripping
signals via analog, digital or Ethernet/IP based communication links.
Analog links include pilot wires, speech channels of power line carrier
equipment and voice channels of analog or digital communication
systems. Digital links include G.703 co-directional (64 kbps), X.21/
RS-449/RS-530 (56 kbps, 64 kbps, electrical RS-422/V.11), E1
(2 Mbps), T1 (1.5 Mbps) interfaces and fiber optic cables (from short
haul till extra long haul, including IEEE C37.94). The Ethernet line
interface can be connected to virtually any Ethernet/IP based packet
switched network.
The conversion from an analog to a digital or an Ethernet system is
possible by exchanging of only one module (the line interface of the
NSD570). If NSD570 needs to be connected to an IEC 61850
compliant protection IED, one contact based relay interface can be
exchanged by a GOOSE LAN Interface.
The NSD570 comprises printed circuit boards with a height of three
standard units (3U) mounted in a 19 inch equipment rack. Two
NSD570 devices with different line interfaces may be plugged in the
rack. The rack itself has a height of four standard units, providing a
cable duct of 1U below the equipment at the rear side and a blanking
1U plate with labeling strip below the equipment at the front side.
Fig. 1-1 Front view of NSD570
Introduction August 2021 1-1

1.1. Using these Operating Instructions

These Operating Instructions are intended for maintenance and
operating personnel responsible for communication in the Electric
Utility. All safety rules in force in the user’s plant must be strictly
observed. Only properly trained personnel may work on the
equipment. The Operating Instructions contain all the information and
instructions needed during the life-cycle of the equipment, i.e.
shipping, storage, commissioning, maintenance, decommissioning and
disposal. Please refer to the respective section for the particular topic
you are dealing with.
The operations in the life of the equipment, i.e. shipping, installation,
testing and commissioning are normally carried out by different people.
For this reason, some of the safety instructions occur several times in
the various sections.
These Operating Instructions distinguish between two groups mainly
concerned with the equipment, service personnel and operating
personnel.
This manual applies to the NSD570 teleprotection system. Actual
hardware, firmware and software versions are to be found in the
document “Compatibility requirements” in Section 12 “Annex”.
1.2. Personnel qualifications
1.2.1. Operating personnel

Operating personnel must:
• have general knowledge of electronic and electrical systems.
• have had basic theoretical and practical training on teleprotection
equipment and its principles.
• be able to work with a PC/notebook, Windows operating systems
and web browsers in order to configure and program the
assemblies.
• be trained and familiar in handling potential sources of danger with
the corresponding caution.
• comprehend and heed warning signs and devices to avoid injury to
persons and damage to the plant.
• not carry out any of the changes or settings described in the
Sections:
Section 6 “Installation and wiring“
Section 7 “Commissioning“
Section 9 “Troubleshooting“
Section 10 “Storage, decommissioning and disposal“
1-2 August 2021 Introduction

1.2.2. Service personnel

Service personnel must:
• have read and understood the Operating Instructions before
commencing work on the NSD570.
• should attend a training course in the handling and operation of the
equipment.
• take the usual ESD precautions when working on the modules of
the NSD570 system.
• take all precautions and observe all warnings to avoid injury and
damage to the plant.
• ensure that in advance to any manipulation on the NSD570, the
equipment has to be set clear or standby and the signaling be
switched into a safe mode, to protect against unwanted tripping
signals.
1.3. Warranty restriction

The manufacturer disclaims any responsibility for hazards and material
damage, if the equipment is operated other than for its intended use as
described in these Operating Instructions or if the equipment is
serviced by non-qualified personnel.
Introduction August 2021 1-3

2. Safety Instructions
2.1. Presentation of safety information

The NSD570 equipment itself is safe and without any risk. This is not
valid for its containment and the peripheral surrounding, like the high
voltage area and lines. Therefore, only properly trained service
personnel may handle the equipment and make settings. Some other
work may be performed by operating personnel (see Section 1
“Introduction“).
In this manual the safety instructions are marked as follows:
Information or dos and don’ts to prevent serious

DANGER personal injury or extensive equipment damage.
Caution Specific information or dos and don’ts to prevent

minor damage and operating problems.
Note: Specific information with regard to the optimum use of

the appliance.
Safety signs marked on the equipment itself:
Hazardous voltage and hazardous energy level.

DANGER Beware of electric shock.
Caution Specific information to prevent minor damage and

operating problems.
Caution Specific information to prevent equipment

ESD damage by electrostatic discharge.
Safety Instructions August 2021 2-1

2.2. Basic principles

The NSD570 is a state-of-the-art equipment that fulfills generally
recognized safety standards. Nevertheless, danger may exist if it is
used improperly.
Only use an NSD570 unit that is in perfect working order and observe
the Operating Instructions.
2.3. General instructions
Personnel qualification
An authorized and properly trained personnel only is

DANGER admitted to carry out installing, programming,
commissioning, maintenance, troubleshooting and
work of the equipment.
Instruction Manual
The Operating Instructions should be read and

DANGER clearly understood before working on the equipment.
Safety and monitoring facilities
Mechanical safety facilities such as cover plates

DANGER must not be removed or by-passed.
Alteration
Alteration of the equipment is not allowed.

DANGER
Warning labels
Precautions and indications to hazardous voltages

DANGER and hazardous energy level must be strictly
observed.
2-2 August 2021 Safety Instructions

2.4. Product-specific instructions
Technical specifications
The equipment must be operated within the

DANGER technical specifications. Failure to do so may result
in personal injuries or equipment damage.
Alteration
Alteration of the equipment is not allowed.

DANGER
Insertion and removal of plug-in modules
Caution Neither removal nor insertion of modules - except for

redundant power supply units - is permitted when
the equipment is powered on. Before plugging
modules in and out, the power supply of the
equipment has to be switched OFF.
Before removal of plug-in modules (except power

DANGER supply unit), disconnect the not energized external
cable.
ESD protection
Caution The modules in this equipment contain devices,

ESD which can be damaged by electrostatic discharges.
Appropriate measures must be taken before
unpacking modules or withdrawing them from
equipment racks. Essential precautions to prevent
ESD damage when handling or working on modules
are grounding straps for technical personnel and the
provision of anti-static workbenches. Modules may
only be shipped either in their original packing or
installed in equipment racks.

Mechanical Installation
The equipment must be mounted in a cabinet.

DANGER
Cabinets, which are not secured to the floor, tip

DANGER forwards when the hinged frame is opened. Do not
open the hinged frame without precautions.
Shipping
Caution To avoid damage while being shipped, note the

instructions in Section 6 “Installation and wiring” in
the Operating Instructions.
Electrical Installation
This is a Class  equipment specified in

DANGER IEC 60950-1. The equipment and the cabinet must
be earthed.
The equipment must be supplied over circuit
breaker.
The circuit breaker for the power supply of the

DANGER equipment must be switched OFF.
The circuit breakers for optional equipment in the
cabinet must be switched OFF.
Do not connect or disconnect energized cables to or

DANGER from the equipment.
The isolating terminals of the external cables must

DANGER be kept open during installation, maintenance and
before storage, decommissioning and disposal.
The Faston supply connectors at the rear of the rack

DANGER must be covered with an isolation sleeve.
The power supply is dangerous (hazardous voltage

DANGER and/or hazardous energy level).
Do not install the equipment with a live supply.

Caution When an analog NSD570 is connected to cables,

pilot wires or leased circuits, the equipment must
only be used in conjunction with barrier transformers
withstanding a 15 kVrms or 20 kVrms test voltage at
50 Hz / 60 Hz for 1 minute, according to national
regulations or to electric utilities' practice.
Caution Connecting a load between terminals NO (normally

open) and NC (normally closed) is not allowed.
Use only one contact set NO or NC.
Fiber optic Installation
Caution Optical connectors

Clean all optical connectors by an approved method
before making any optical connection.
When making an optical connection, do not rotate
the optical connector unnecessarily.
When not connected, fit all optical plugs and
couplings with captive caps.
Caution Damage to optical fibers

When dressing fibers, take care not to exceed the
minimum bend radius (typically 35 mm) and do not
over tighten binders used for dressing as damage
may result.
When connecting other external cables or mounting
the rear cover, ensure that the optical fibers are not
bruised or crimped.
Back cover
Hazardous voltages and/or hazardous energy level

DANGER behind the back cover. Before removing the back
cover, the isolating terminals of the external cables
must be opened or the cables to the terminals must
be disconnected.
Working on the equipment
Do not work on the system or connect or disconnect

DANGER cables during periods of lightning.

Electrical strength test
Do not repeat any electrical strength tests. Improper

DANGER test methods can cause severe damage to the
equipment.
Electric strength and earth continuity tests have
been performed in the factory.
EMC
Caution This is a class A equipment specified in CISPR 22

(EN 55022). In a domestic environment, this
equipment may cause radio interference. In this
case, the user may be required to take adequate
measures.
Power supply for alarm
Caution The alarm power supply must be short current and

over current protected.
Power supply modules G3LI and G3LK
Caution Be aware of the different input voltage ranges of the

NSD570 power supply modules.
Before plug in the module, check the rating label to
assure correspondence with the input voltage.
Common Interface G3LC

DANGER on the module and the cable.
Do not touch the module and the cable leads.
Relay Interface G3LR


LAN Interface G3LL
The LAN Interface G3LL contains a lithium battery.

DANGER
Danger of explosion exists if the lithium battery is
incorrectly replaced. Replace only with the same or
equivalent type recommended by the manufacturer.
For replacing and inserting the battery always use a
potentially-free soldering iron.
Check the polarity before inserting the battery.
Caution For disposal of the lithium battery, the regional and

national regulations for electrical and electronic
waste have to be observed.
Caution Encrypted SSL connections are strongly recommen-

ded for communication channels that are not secure
(e.g. Internet).
Never connect a NSD570 LAN Interface G3LL
directly to the Internet!
Management LAN Interface G3LM

(e.g. Internet).
Never connect a NSD570 Management LAN
Interface G3LM directly to the Internet!
GOOSE LAN Interface G3LS
Caution A G3LS configured to run in “Test command

transmission” mode forwards commands with quality
marked as “test”. This means every command will
be discarded by the protection relay.

Laser / LED
Caution Class 1 Laser/LED Product.

Laser / LED
Commissioning
Caution Do not close/establish the connections to the

protection devices until the NSD570 is properly
commissioned.
Using HMI570
Caution The teleprotection link gets disturbed while using

certain functions offered by the HMI570 for commis-
sioning the equipment (e.g. local test mode, remote
test mode).
However, when a user is logged in with only “view
permission”, it is not possible to disable the device.
Caution During routine tests with the NSD570 in operation

the “Reset Device” link in the Maintenance menu of
the HMI570 should not be activated, as this causes
the NSD570 to be re-initialized and thus be blocked
for approx. 10 seconds.
During this time no commands can be transmitted.

3. System Description
3.1. Introduction
The sizes, complexity and power ratings of high voltage networks
emphasize the need for highly reliable protection systems. Protection
is based on information derived from the power system at one or more
points, and fast selective protection applied to circuits with
geographically separated terminals, such as cables and overhead
lines, requires information interchange between these terminals.
NSD570 is a teleprotection equipment intended for use in protection
systems requiring a communication link. It is designed to convey
qualitative information, i.e. command signals generated by protective
devices in high-voltage electrical power systems. It is suitable for
analog voice-grade communication facilities, such as pilot wires and
speech channels of microwave radios or power line carrier links, for
digital communication facilities, provided by digital multiplexers, for
optical fiber and for Ethernet/IP networks.
Since any communication system is subject to interference and noise
of various forms, the performance of a teleprotection equipment is
commonly described in terms of security, dependability and
transmission time; further characteristics are the bandwidth of analog
equipment and the signaling rate of digital or Ethernet equipment.
Interference and noise on the communication link must neither
simulate a command at the receiving end when no command signal
was transmitted (security), nor impair the ability to convey commands
correctly and promptly (dependability).
Security, dependability, transmission time and bandwidth (or signaling
rate) are interrelated and interchangeable parameters. High security
and high dependability together with short transmission time and
narrow bandwidth (or low signaling rate) are therefore conflicting
requirements, but the emphasis can always be placed on
dependability or security or speed, depending on the application. A
blocking protection scheme, for instance, needs a short transmission
time and a high dependability, while a permissive tripping scheme
needs a short transmission time with good security and a high
dependability; direct transfer tripping schemes, by contrast, require
very high dependability and security, achieved at the expense of a
longer transmission time.
The above mentioned protection schemes are explained at the end of
this section (see Section 3.6 “NSD570 Applications”).
System Description August 2021 3-1

3.1.1. General NSD570 Features

Versatile application
Transmission of command signals in blocking, permissive and direct
transfer tripping schemes via pilot wires, speech channels of
microwave radio systems or PLC links, speech channels of digital
multiplexers, data channels conforming to ITU-T G.703 or to
TIA/EIA-422 / ITU-T V.11 recommendations, E1 or T1 circuits, via
optical fibers or Ethernet/IP networks.
NSD570 may also be used for the transmission of persistent tripping
signals in point-to-point or teed systems.
Compact and flexible design

Standard 19-inch rack for one or two NSD570 units; one unit for up to
4 independent protection commands via analog lines and up to 8
independent commands via digital lines or Ethernet/IP networks; two
independent units for duplicated protection schemes.
Modular structure, few modules, low inventory

The equipment is split up into a signal processing module including an
analog, digital or Ethernet line interface and a relay interface which
can transmit and receive two commands. Additional commands can be
conveyed by simply inserting further relay interfaces (up to four relay
interfaces per NSD570 unit).
The module rack consists of a common front plate, an interface with
shared functions (like alarm relays) and a supply backplane with
connectors for the electrically isolated power supply units.
Robust and reliable

All interfaces and the power supply are DC isolated from all other
circuits and from ground. Duplicated (redundant) power supply units
can be fitted.
Advanced technology, digital signal processing

High equipment availability and reliability due to carefully selected
components which have passed rigorous qualification tests.
Algorithms optimized for protection signal transmission ensure safe
and reliable operation even under extremely difficult conditions.
Browser-based Human-Machine Interface HMI570

The user communicates with the NSD570 via a PC/notebook
connected to the serial interface on the equipment front. A menu-
guided HMI program, installed on the PC, enables various operating
modes to be configured and detailed equipment settings and the
operating or alarm status of the local and remote unit to be viewed.
3-2 August 2021 System Description

Remote access
Two optional LAN/management interfaces are available for remote
access to the equipment via the Internet or a Corporate Network
(Intranet). In a substation, several NSD570 units can be inter-
connected via a two wire serial bus (RS-485 interface), and each
NSD570 is then accessible with a unique equipment address for
remote management.
Embedded operation channel (EOC)

Allows remote NSD570 configuration and monitoring from one end.
In-operation testing
Automatic and manual testing routines enable the integrity of the
communication channel to be tested during normal operation. The
equipment availability is continuously monitored by self-testing
procedures.
Teed lines and tapped lines

Cost-saving schemes for protection of multi-ended circuits.
Redundant path protection, 1 + 1 configuration

Two independent NSD570 line interfaces in a common rack, sharing
their relay interfaces for improved reliability in duplicated protection
schemes.
All combinations of two line interfaces in the same rack are possible
(analog, digital, Ethernet).
Universal relay interface

The relay interfaces provide two opto-coupler inputs and two solid-
state outputs plus two heavy duty (electromechanical) relay outputs.
Each input and output is potential-free and isolated from ground and
all other circuits.
Commands can be individually mapped to any input/output.
Single-pole or double-pole tripping can be arranged, and command
outputs can be clamped to an “off” or “on” state during channel alarm
conditions.
Several additional functions like individual alarms can be mapped to
the remaining outputs.
GOOSE LAN interface

Alternatively or in addition, commands can be exchanged with
protection relays/IEDs via the Ethernet based GOOSE LAN interface,
both connected to a substation network. Tripping commands are
signaled in GOOSE messages according to IEC 61850. This interface

is compatible with protection relays from HITACHI ABB and also with
protection relays from other vendors.
Integrated event recorder and trip counters

More than 7000 command start/stop and alarm events can be
recorded and stored with time stamp in a non-volatile memory. The
event recorder can be synchronized to an external time signal (e.g.
GPS receiver) for accurate time stamping. The display of events is
possible in text view with the HMI570.
In addition to the event recorder, integrated “trip counters” for each
transmitted and received command facilitate investigations in case of
faults or abnormal conditions in the high voltage network.
Optional integrated display panel

For monitoring the equipment status and alarms of the two devices in
a rack and of the devices in their remote stations (if the EOC is
enabled).
3.1.2. Features of the NSD570 Analog

Hardware
The NSD570 is arranged for use on audio-frequency communication
facilities when an analog line interface card is plugged.
Programmable bandwidth and center frequencies

Tx and Rx bandwidth programmable from 120 Hz to 2800 Hz; center
frequencies programmable from 360 Hz to 3900 Hz in 60 Hz steps.
Programmable command configuration

Any command programmable for blocking, permissive tripping or direct
transfer tripping.
Up to 4 independent commands per unit

Suitable for protection of dual-circuit lines. Several NSD570 can be
operated in parallel on one AF channel in frequency-division multiplex
mode.
High speed
Nominal transmission times as low as 4 ms transmitting one
command, or 6 ms transmitting two to four commands, to meet
demanding transmission time requirements.
Level boosting
Command signals can be transmitted at a considerably higher power
level than the guard signal.

3.1.3. Features of the NSD570 Digital

Hardware
The NSD570 is arranged for use on digital communication facilities
when a digital line interface card is plugged.
Programmable signaling rate and data interfaces

Four signaling rates can be programmed via HMI570 (56 kbps,
64 kbps, 1.544 Mbps and 2.048 Mbps), depending on the data
interface in use.

transfer tripping.

One NSD570 can for example handle phase-segregated line
protection and breaker back-up protection of both systems of a dual
circuit line.
High speed
Nominal transmission time < 4 ms, or < 6 ms at the highest security
level.
Addressable
Addresses assigned to the devices indicate for which station the guard
and command signals are intended. This prevents maloperations in
case of inadvertently transposed channels.
Optional integrated optical interface

For optical direct fiber connection or optical connection to digital
multiplexers. Short, medium, long and extra long haul applications as
well as the IEEE C37.94 standard are supported (by means of
exchangeable SFP transceiver modules, to support different range,
wavelength and fiber type requirements).
3.1.4. Features of the NSD570 Ethernet

Hardware
The NSD570 is arranged for use on Ethernet/IP communication
facilities when an Ethernet line interface card is plugged.
Programmable data rate and data interfaces

Two data rates can be programmed via HMI570 (10 Mbps and
100 Mbps, manual or auto negotiation). The standard interface is an
electrical RJ45 connector.


transfer tripping.

One NSD570 can for example handle phase-segregated line
protection and breaker back-up protection of both systems of a dual
circuit line.
High speed
Nominal transmission time < 4 ms.
Addressable
IP addresses assigned to the devices indicate for which station the
guard and command signals are intended.
Cyber/IT security compliant

Complete set of measures against human generated security attacks
implemented.
Optional pluggable optical interface

For optical connection, a cage is mounted on the Ethernet line
interface, where an SFP transceiver module can be inserted.
Supported wavelengths for the optical interface are e.g. 850 nm or
1310 nm in multi mode fiber and 1310 nm in single mode fiber.
For optical direct fiber applications (long and extra long haul), also
1550 nm SFP transceivers are available.

3.2. Communication channels
Fig. 3-1 Communication channels
Analog channels with voice frequency bandwidth:

- pilot wires
- analog leased lines
- voice channels of analog or digital communication systems
- PLC links
Digital channels:
- serial data channels of digital multiplexers
- radio links and optical fiber systems
- leased digital telecommunication circuits
Optical channels:
- optical point-to-point connection
- optical connection to a digital multiplexer
Ethernet channels:
- any IP based network

3.3. System architecture
3.3.1. System block diagram
OUTPUT
BOOST
Alarm 1
Alarm 2
RELAY
(analog)
(WAN)
INPUT
LINE
LAN
PC/Notebook
G3LR (or G3LR/G1LR)

Display Panel G3LR (or G3LR/G1LR)
G1LC Line Interface G3LR (or G3LR/G1LR)
Common
(analog, digital,
Interface
optical or Ethernet) Protection Relay Interface
SYNC (PPS IN)
G3LA or G3LD or G3LE G3LR or G3LS
GPS (IRIG-B IN) (or G3LD/G1LE or G3LD/G1LO) (or G3LR/G1LR)
G3LC
Station
Supply
Bus Backplane
DC /
MAINS 1 Busplane (with Front Cover)
DC /
G1LB G1LA
MAINS 2
G3LH, G3LI or G3LK
G3LH, G3LI or G3LK
Power Supply 1
Power Supply 2
Protection Relay Interface

Line Interface G3LR or G3LS
LAN / Management
(analog, digital, (or G3LR/G1LR)
Interface
optical or Ethernet)
G3LR (or G3LR/G1LR)
G3LA or G3LD or G3LE G3LR (or G3LR/G1LR)
G3LL or G3LM (or G3LD/G1LE or G3LD/G1LO)
G3LR (or G3LR/G1LR)
G7BI
*IRIG-B OUT
LAN
LAN
RELAY
LINE
OUTPUT
(WAN)
(analog)
INPUT
3-System block diagram.vsd
BOOST
* Available only with G3LMa
Fig. 3-2 System block diagram
The Module Rack type G7BI consists of:

1 Rack with Cable Tray
1 Bus Plane with Front Cover, type G1LA
1 Supply Backplane, type G1LB
1 Common Interface, type G3LC
1 Blanking Cover Plate
The NSD570 Analog system consists of:

1 Module Rack, type G7BI
1 Analog Interface, type G3LA
1-4 Relay Interface(s), type G3LR or 1 GOOSE LAN interface, type
G3LS plus 0-3 G3LR
1 Power Supply, type G3LH/G3LI/G3LK

The NSD570 Digital system consists of:

1 Digital Interface, type G3LD
G3LS plus 0-3 G3LR
The NSD570 Ethernet system consists of:

1 Ethernet Interface, type G3LE
G3LS plus 0-3 G3LR
Available options for all NSD570 systems are:

1 Display Panel per Module Rack G7BI, type G1LC
1 LAN Interface per Module Rack G7BI, type G3LL
1 Management LAN Interface per Module Rack G7BI, type G3LM
1 Piggyback per Relay Interface G3LR, providing an internal DC
voltage for tripping the two command inputs by an external dry
contact only, type G1LR
Options available for the NSD570 Digital system are:

1 Piggyback per Digital Interface G3LD with an E1/T1 Interface, type
G1LE
1 Piggyback per Digital Interface G3LD with an Optical Interface,
type G1LO or G1LOa
Only one piggyback per G3LD can be plugged.

3.3.2. Mechanical design
Supply Backplane G1LB
G3LA, G3LD, G3LE
G3LA, G3LD, G3LE
G3LR, G3LL, G3LM

G3LR, G3LS
G3LR, G3LS
G3LH, G3LI or G3LK
G3LH, G3LI or G3LK
G3LR
G3LR
G3LR
G3LR
G3LR
Power Supply
Power Supply
300 mm
Analog Interface G3LA

Digital Interface G3LD
Ethernet Interface G3LE
Relay Interface G3LR, G3LS
LAN Interface G3LL, G3LM
Optional: Blanking Bus Plane with front cover G1LA

Display Panel Cover Plate
G1LC Top view
3-Rack Top View.vsd
Fig. 3-3 Mechanical design
The mechanical design of the NSD570 teleprotection system is as

follows:
- 19 inch rack, housing one or two NSD570 devices, 4 height units
(4U) including 1U for cable tray, blanking 1U plate with labeling
strip, connectors, etc.
- one bus plane with front cover for one or two NSD570 in the same
rack
- 2 slots with 8 HP (horizontal pitch) for single or redundant power
supply
- 1 slot with 6 HP for common interface
- 2 x 5 slots for line interface and relay interfaces (accessible from the
back side of the rack, after removing of the screening cover)
- optional display panel (instead of power supply front cover plate)
- optional LAN Interface instead of 4th Relay interface in the second P P
half of the module rack

3.3.3. External connections

All connections to the equipment, i.e. incoming and outgoing signals,
are made by plug-in connectors at the rear of the unit, which are either
D-sub connectors, RJ45 connectors or spring-cage type of terminal
connectors (2.5 mm2).
By using the optionally available connecting cables, the signals can
then be routed to isolating terminals (4 mm2), to D-sub connectors in
the case of the data interfaces RS-449/RS-530/X.21 or to RJ45
connectors in case of the data interfaces G.703/E1/T1 and the
Ethernet interfaces. The length of the connecting cables is 2.5 meters
(refer to Section 6 “Installation and wiring” for details).
The optical transmit and receive components are mounted on the
Optical Interface type G1LO. It is a piggyback module that can be
plugged on the Digital Interface type G3LD. The fiber optic connectors
used are E2000. The Optical Interface type G1LOa is the latest
piggyback version. It uses optical SFP transceiver modules with
LC/PC connectors.


3.3.4. Front plate Signals and Controls
Fig. 3-4 Front plate signals and controls
Status and alarm LEDs on the front plate:

- light up immediately when a condition is detected (Guard / Trip),
when an Input / Output / Relay is activated or after an alarm source
is detected (light up immediately, i.e. not only after the delay which
is configurable for the alarm outputs)
- One hardware status LED per line interface, relay interface and
LAN interface (green/red signals Ok/Fail)
- One status LED for each input/output and relay contact in case
G3LR is assembled (dark/green)
- Two status LEDs for each group of input GOOSE commands and
output GOOSE commands in case G3LS is assembled (dark/green)
- Two status LEDs for Guard and Trip reception (dark/green)
- Four alarm LEDs per system Transmit, Receive, Local, Remote
Alarm (dark/red)
- One hardware status LED per power supply module (green/red
signals Ok/Fail; “dark” indicates that no module is plugged)
- One status LED for the LAN interface; indicates when the Ethernet
link has established (green/dark)
3.3.5. Service interface (COM 1)

A serial interface is provided on the front plate for service and
diagnostic purposes and as a commissioning aid. By connecting a
PC/notebook to this interface, data on equipment settings, firmware in
use and operating parameters can be accessed without affecting the
normal operation of the NSD570.

It is also possible to configure the equipment and download new

firmware releases via the interface. For these actions the equipment
has to be taken out of service and re-commissioned afterwards.
A serial 1:1 cable (shielded) with 9 pin D-sub connectors is necessary
for connecting the PC/notebook to the equipment. The cable must
have a female (to the PC) and a male (to the NSD570) D-sub
connector.
Via the serial RS-232 interface a 57’600 bps connection to both
NSD570 systems in the same module rack can be obtained. This high
transmission rate can only be achieved when the connecting cable is
not longer than 3 meter. If longer cables have to be used, the
transmission rate has to be reduced (refer to Section 4 “User interface
program”).
3.3.6. Power supplies G3LH, G3LI, G3LK

The rack can be equipped with one single power supply unit type
G3LH, G3LI or G3LK and may have a redundant power supply with
two of these units (mixed operation is possible).
The units differ in their input voltage range:
Type of power supply G3LH 1 G3LI G3LK

DC input voltage range
38 ... 300 18 ... 72 88 ... 300
[VDC]
Nominal DC supply voltages 48, 60, 110, 110, 220,
24, 48, 60
[VDC] (± 20 %) 220, 250 250
AC input voltage range [VAC]
85 ... 264 - 93 ... 253
(47 to 63 Hz)
Nominal AC supply voltages
100 … 240 - 110, 230
[VAC] (-15%, +10%)
Table 3-1 Power supply voltages
The power supply cable is connected to FASTON terminals located on

the back side of the rack (refer to Section 6 “Installation and wiring”).
The power supply modules are hot pluggable.
1 Phased out by end of 2010.

3.3.7. Examples of rack assemblies

Find below a few examples how a 19” rack NSD570 can be equipped.
• Minimal equipment Analog:

Rack assembly comprising of
- one Module Rack type G7BI
- one Analog Interface type G3LA
- one Relay Interface type G3LR and
- a single Power Supply type G3LH, G3LI or G3LK;
capable of transmitting up to two commands.
G7BI
REAR VIEW
(COVER REMOVED) G3LH,
G3LI
or
G3LR G3LA G3LC G3LK G1LB
PS2 PS1
POWER SUPPLY 1
POWER SUPPLY 2
X101
X100
X103
X102
X105 X104
PE PE
84 76 70 64 58 52 46 40 34 28 22 09 01
3-Rear View_Analog.vsd
Fig. 3-5 Minimal equipment Analog

• Minimal equipment Digital:

- one Digital Interface type G3LD
G7BI
REAR VIEW
(COVER REMOVED) G3LH,
G3LI
or
G3LR G3LD G3LC G3LK G1LB
PS2 PS1
X101
POWER SUPPLY 2
POWER SUPPLY 1
X101
X103
X201
X102
X105 X104
PE PE
84 76 70 64 58 52 46 40 34 28 22 09 01
EQUIPMENT 2 EQUIPMENT 1
3-Rear View_Digital.vsd
Fig. 3-6 Minimal equipment Digital

• Minimal equipment Ethernet:

- one Ethernet Interface type G3LE
G7BI
REAR VIEW
(COVER REMOVED)
G3LH,
G3LI
or
G3LR G3LE G3LC G3LK G1LB
PS2 PS1
POWER SUPPLY 2
POWER SUPPLY 1
X103
X101
X103
X102
X102
X105 X104
PE PE
84 76 70 64 58 52 46 40 34 28 22 09 01
3-Rear View_Ethernet.vsd
Fig. 3-7 Minimal equipment Ethernet

• Two independent NSD570 in the same rack:

Rack assembly for transmitting the maximum number of
commands with an analog system (4 commands), a digital system
(8 commands) and a LAN interface in the same module rack.
G7BI
REAR VIEW
(COVER REMOVED)
G3LH,
G1LR G1LR G1LR G1LR G1LR G1LR G1LE G3LI or
G3LM G3LR G3LR G3LA G3LR G3LR G3LR G3LR G3LD G3LC G3LK G1LB
PS2 PS1
X101
POWER SUPPLY 2
POWER SUPPLY 1
X101
X101
X101
X101
X101
X101
X100
X103
X102
X201
X102
X101
X105 X104
PE PE
84 76 70 64 58 52 46 40 34 28 22 09 01
3-Rear View_Mixed_New.vsd
Fig. 3-8 Two independent NSD570 in the same rack

• Fully equipped rack with redundant power supply units:

Rack assembly, providing the maximum number of input (8) and
output (16) circuits per device in the module rack; redundant
power supply units.
G7BI
REAR VIEW
(COVER REMOVED)
G3LH, G3LH,
G1LR G1LR G1LR G1LR G1LE G1LR G1LR G1LR G1LR G3LI or G3LI or
G3LR G3LR G3LR G3LR G3LD G3LR G3LR G3LR G3LR G3LA G3LC G3LK G3LK G1LB
PS2 PS1
X101
POWER SUPPLY 2
POWER SUPPLY 1
X101
X101
X101
X101
X101
X101
X101
X101
X100
X103
X201
X102
X101 X105 X104
PE PE
84 76 70 64 58 52 46 40 34 28 22 09 01
3-Rear View_Fully.vsd
Fig. 3-9 Fully equipped rack with redundant power supply units

3.4. Module descriptions
3.4.1. Common Interface G3LC
3.4.1.1. Block diagram G3LC

RX_DATA2
2-wire communication bus for G1LC LCD-Display
TX_DATA2 12 V X101
SUP1 12.3 V Supply 1 12 V +12 V

SUP2 12.3 V Supply 2
GND GND DC/DC
5 V Supply +5 V
max. 1 A
Check1 Supply supervision

& SUP_AL_1
Check2 plug In check SUP_AL_2
4
Supply1_LED
LED_0..3
ALARM1_LED
Supply2_LED
ALARM2_LED
RS-485 transceiver
RS-485
&
isolated supply
RS-232 COM1 RS-232 transceiver

& 2-wire communication bus RX_DATA1
X901 isolated supply TX_DATA1
SYS_AL_1
Relay 1, X102
SYS_AL_2
Relay 2, X102
extern 2
IRIG-B
IRIG-B
extern 2
GPS_SYNC
GPS_SYNC
TxD_RTB
RTB clock RxD_RTB
RTB & RTB
LOOP_DIS 8.192 MHz
frame sync
FS_RTB
3-Block-diagram-G3LC.vsd
Fig. 3-10 Block diagram G3LC
Signal description legend:

SUP1 (normal)
These signals are led through the PCI connector X100 to the Supply
Backplane G1LB, where the external connector terminals are located.
RS-232, X901 (bold)
These signals are led to other external interfaces, such as the RS-232
interface through X901 (COM 1), the connection to the Display Panel
G1LC through X101 and the additional alarm outputs through X102.

SYS_AL_1 (italic)
These signals are led to the backplane G1LA through the PCI
connector X900 and further on to the line interfaces G3LA/G3LD.
3.4.1.2. Short description G3LC

The Common Interface G3LC comprises all the circuitry that has to be
available to the entire system independently of the number of NSD570
that are equipped in the sub-rack. G3LC is an inherent part of the
combination of rack, bus plane and supply backplane.
Both secondary voltage supplies (12.3 V) are taken from the
redundant power supply modules and de-coupled with serial diodes.
The secondary voltage supplies are separately monitored and their
working conditions are displayed with LEDs on the front as well as
signalized to the line interface.
The 12 V supply voltage is distributed to the bus plane to supply other
modules (line interfaces, relay interfaces, etc.). On G3LC, it also
supplies the DC/DC converter generating 5 V that is led to the bus
plane too. The auxiliary 5 V supply voltage serves the Common
Interface to supply some of its own circuitry and other 5 V circuits in
the system, e.g. the G.703 interface on the Digital Interface G3LD.
The bus clock and frame synchronization signals of the Real Time Bus
(RTB) are generated on G3LC and used by the DSP-Interface on the
Line Interfaces.
The Common Interface G3LC also contains the transceiver and the
isolated power supply of the RS-232 interface (COM 1) that can be
used to configure the NSD570.
The external connection to this serial communication port is available
at the D-sub, 9 pin female connector X901 on the front plate.
The transceiver and the isolated power supply of the RS-485 station
bus are also located on G3LC. The station bus interconnects several
NSD570 racks in a substation. This allows to access several racks
over the COM 1 interface (or the LAN Interface G3LL/G3LM) of one
single rack. Prerequisite for such operation is a different addressing of
every single NSD570 connected to the bus.
The external connection to the RS-485 bus is located on the Supply
Backplane G1LB at the rear side of the rack.
Each of the two possible NSD570 devices that can be fitted in one
rack has a system alarm. SYS_AL 1 is for the TPE 1 and SYS_AL 2 is
for the TPE 2. The Common Interface G3LC offers a “heavy duty”
relay with switchover contacts for each system alarm.

The external connector X102 to the alarm relays is located at the rear
side of the Common Interface.
The external connections of the synchronization inputs (GPS-
synchronization 1 PPS, IRIG-B) for the real time clock (located on the
line interfaces) are also located on Supply Backplane G1LB at the rear
side of the rack. These signals are led over the X100 PCI connector to
the Common Interface where opto-couplers provide electrical isolation.
At last, the Common Interface G3LC contains an internal socket X101
to connect the optional Display Panel G1LC to the equipment.
A detailed description of all module connectors as well as the optional
connecting cables and their pin assignments can be found in Section 6
“Installation and wiring”.
3.4.2. Analog Line Interface G3LA
3.4.2.1. Block diagram G3LA
X100/5 Out
buffer
Boost 8
4W/2W
SDRAM
Rx_Gain
X100/6
32
X100/3
x1 u1
RTC
Z
Rx-AF 50Hz / 60Hz Amplifier 4 kHz Sync_Bus

RB 8
limiter
RA
X100/4 Out LED's

Codec
Tx_Gain
buffer Local Alarm

24
Slot-Coding
X100/1 Digital signal Data bus HW Version G3LC
u1 x1 24
processor In HW Version G1LA
Z
Tx-AF Output Amplifier Smoothing 32 buffer # of G3LH

TB
amplifier filter
TA Alarm on G3LH
X100/2 HW Version G3LA
Tx-Level
u1 x1
Buffer
8
+3.3 V DO
12 V 12 V DI
FS SPORT1 Reset
CLK
WD
3.3 V uC RS-232
SPORT0 Flag RS-485
Reset
+12 V
12 V 12 V
Supply 33 MHz
+12 V monitoring Serial-
Watchdog
-12 V FLASH
-12 V
Loop Test
Clk
RTB
3-Block-diagram-G3LA.vsd
Fig. 3-11 Block diagram G3LA
3.4.2.2. Short description G3LA

The Analog Interface G3LA converts the incoming protection
commands of the Relay Interfaces G3LR or the GOOSE LAN Interface

G3LS into signals that are transmitted over an analog communication

line. Also, the commands that are received by the analog line interface
are passed onto the appropriate protection relay interfaces.
Communication between the G3LA and the G3LR/G3LS takes place
over the Real Time Bus (RT-Bus) which is located on the bus plane.
For signal transmission any transparent analog channel with 4 kHz
bandwidth, equipped with an appropriate standardized two-wire or
four-wire interface with 600 Ohm line impedance can be employed. It
is also possible to operate two NSD570s back-to-back via the Analog
Interfaces G3LA.
3.4.2.3. External interfaces G3LA

The analog line interface includes an electrically isolated interface for
transmitting and receiving analog signals on a four-wire or a two-wire
connection. The bandwidth of the transmitted and received signal is
situated in the range of 300 Hz to 4 kHz. The line termination can be
configured to 600 Ohms or high impedance using jumpers.
Additionally, the analog line interface includes an electrically isolated
boosting output, which can be used for the boosting of the protection
signals in connection with a PLC equipment (e.g. ETL600). The
external signals are provided on the X100 connector (1 - 6; spring-
cage terminals). An external cable can be plugged to the X100
connector, making the signals available over disconnectable terminals.
3.4.2.4. Processor environment G3LA

The processor circuits described here are similar to the ones found on
the Digital Interface G3LD.
The circuits include a signal processor which carries out the necessary
signal generation and signal evaluation for all transmit and receive
functions. The signal processor can access an external 32 bit wide
memory that consists of two 4 Mbit SD-RAM chips.
A buffered Real Time Clock (RTC) provides the system timing. It is
also possible to synchronize the RTC with an external signal that
offers 1 second pulses. Or, alternately, the RTC can be synchronized
with an IRIG-B signal from a GPS receiver. This signal is provided to
the G3LA via the bus plane. The bus plane in turn receives the signal
from the Common Interface G3LC.

The micro-controller contains the interface to a PC/Notebook that has

the User Interface HMI570 installed. The micro-controller controls the
RS-232 interface, fetches the requested data from the DSP and
passes the data onto the HMI570. The micro-controller is also
responsible for the administration of the FLASH EEPROM memory,
which contains the configuration, the firmware and also the data from
the event recorder. Configuration and firmware updates can also be
downloaded from the PC to the FLASH EEPROM memory.
The G3LA comprises two watchdog facilities:
The first one is incorporated in the micro-controller. Should the micro-
controller seize up its arithmetic operations, a reboot is issued to the
micro-controller by its on-board watchdog. Then, a reset signal is
transmitted to the signal processor which consequently will also
restart.
The second external watchdog supervises the signal processor. The
watchdog recognizes when the signal processor ceases from
operating correctly and issues a reset to the micro controller. As
already described above, the micro-controller restarts and initiates a
restart of the signal processor.
To prevent the system against incorrect behavior in the case of a
program or data memory error in the DSP or SD-RAM, a RAM
monitoring is implemented. If an inconsistent RAM content is detected,
an alarm is raised and the device switches to a safe operation mode.
While running in this special mode, command tripping is suppressed,
i.e. no analog samples are processed and no changes on the NSD570
internal bus are executed. If the RAM inconsistency remains after
rebooting, a persistent alarm indicates the fault and the line interface
must be replaced.
3.4.2.5. Transmitter G3LA

In the transmission path there is a D/A converter followed by a
smoothing filter, a level adjuster, an output amplifier and a matching
transformer, which ensures the electrical isolation. The line termination
is set using the TA/TB jumper (TA: 600 Ohm, TB: high-impedance).
The transmitter level is configurable in the range from –24 dBm to
+11 dBm, where the highest level can only be reached by boosting
+9 dB. At the matching transformer, the transmitted signal is also
looped back to the DSP over a second A/D converter in the Codec
(Coder/Decoder). This allows the level monitoring of the transmitter.
Note: Level measurement is only accurate if the external

line impedance matches approx. 600 Ohm.

The transmit signal is available on the external connector X100 (1/2).
3.4.2.6. Receiver G3LA

In the receiver path a transformer that ensures the electrical isolation
of the signal is followed by a 50 Hz highpass filter, a level adjuster, an
anti-aliasing filter and an A/D converter with a resolution of 16 bit.
The receiver is dimensioned for a nominal range from –30 dBm to
+2 dBm. Additionally a dynamic range of 15 dB can be processed.
The line termination is set using the RA/RB jumper (RA: 600 Ohm, RB:
high-impedance).
The receiver signal has to be plugged to the external connector X100
(3/4).
3.4.2.7. Boosting output G3LA

The Analog Interface G3LA features an additional electrically isolated
boosting output which may be used for example to signal a PLC
equipment that speech and superimposed data channels shall be
switched off, allowing the command signal being transmitted with
increased level. This boosting output is always activated when a
command is sent, i.e. the contact is closed. The boosting output is
designed for a maximal switching-power of 60 VDC at 50 mA (current
limited).
The boosting contact is available on the external connector X100 (5/6)
and is polarity independent.

3.4.3. Digital Line Interface G3LD
3.4.3.1. Block diagram G3LD
Connector to
piggy-back
8
SDRAM
DO
DI 32
FS
Signaling
CLK from FPGA
In
buffer
5 24
RTC Sync_Bus
Line interface
Codirectional
Rx Data - T+
T- 8
Signaling to
G.703
G.703
Rx Data + S+ FPGA Out

S- Out LED's
buffer buffer Local Alarm
5 24
Tx Data - GLOS 24
Tx Data + Slot-Coding
FPGA
Data bus HW Version G3LC
24
In HW Version G1LA
SD-A 32 buffer # of G3LH
SD
SD-B Alarm on G3LH
RS-422 / V.11
RD
RD-A HW Version G3LD
Line interface
RD-B ST
RS-422
TT-A RT Digital signal

TT-B
processor Buffer
TT
RT-A
8
RT-B DO
ST-A DI
FS SPORT1 Reset
ST-B CLK
SPORT0 WD
RS-232
uC RS-485
Flag
Reset
16.384 MHz 33 MHz

Serial-
Watchdog
FLASH
RTB
Loop Test
3-Block-diagram-G3LD.vsd
Fig. 3-12 Block diagram G3LD
3.4.3.2. Short description G3LD

The Digital Interface G3LD converts the incoming protection
G3LS into digital data streams that are transmitted over one of two on-
board standard digital line interfaces. Also, the commands that are
received by the digital line interface are passed on to the appropriate
protection relay interfaces. Communication between the G3LD and the
G3LR/G3LS takes place over the Real Time Bus (RT-Bus) which is
located on the bus plane.
For data transmission any transparent digital channel and an
appropriate standardized interface can be employed. It is also possible
to operate two NSD570s back-to-back via the Digital Interfaces G3LD.

The G3LD can be fitted with piggyback modules that provide the
following options:
• E1/T1 Interface G1LE (refer to Section 3.4.3.6 “E1/T1 Interface
G1LE”)
• Optical Interface G1LO (refer to Section 3.4.3.7 “Optical Interface
G1LO”)
• Optical Interface G1LOa (refer to Section 3.4.3.8 “Optical Interface
G1LOa”)
3.4.3.3. External interfaces G3LD

The G3LD comprises two interfaces:
• The TIA/EIA-422 / V.11 interface can be operated at 64 kbps or
56 kbps. It is equipped with a male D-sub 25-pin connector. This
connector X101 is located at the rear of the G3LD and conforms to
TIA/EIA-530.
• The G.703 co-directional interface with a data rate of 64 kbps. The
connector X201 that is located at the rear of the G3LD consists of
an 8-pin RJ45 receptacle.
Only one of the two interfaces can be used at a time.
3.4.3.4. Processor environment G3LD

The processor circuits of the G3LD are similar to the ones on the
Analog Interface G3LA (Section 3.4.2.4 “Processor environment
G3LA”)
The circuits include a signal processor which carries out the necessary
signal generation and signal evaluation for all transmit and receive
functions. The signal processor can access an external 32 bit wide
memory that consists of two 4 Mbit SD-RAM chips.
A buffered Real Time Clock (RTC) provides the system timing. It is
also possible to synchronize the RTC with an external signal that
offers 1 second pulses. Or, alternately, the RTC can be synchronized
with an IRIG-B signal from a GPS receiver. This signal is provided to
the G3LD via the bus plane. The bus plane in turn receives the signal
from the Common Interface G3LC.
The micro-controller contains the interface to a PC/Notebook that has
the User Interface HMI570 installed. The micro-controller controls the
RS-232 interface, fetches the requested data from the DSP and
passes the data onto the HMI570. The micro-controller is also
responsible for the administration of the FLASH EEPROM, which
contains the configuration, the firmware and also the data from the
event recorder. Configuration and firmware updates can also be
downloaded from the PC to the FLASH EEPROM.

The G3LD comprises two watchdog facilities:

The first one is incorporated in the micro-controller. Should the micro-
controller seize up its arithmetic operations, a reboot is issued to the
micro-controller by its on-board watchdog. Then, a reset signal is
transmitted to the signal processor which consequently will also
restart.
The second external watchdog supervises the signal processor. The
watchdog recognizes when the signal processor ceases from
operating correctly and issues a reset to the micro-controller. As
already described above, the micro-controller restarts and initiates a
restart of the signal processor.
program or data memory error in the DSP or SD-RAM, a RAM
i.e. no digital frames are processed and no changes on the NSD570
must be replaced.
3.4.3.5. External cable and connector G3LD

The RS-530 and G.703 signals can be accessed at the back of the
NSD570. In case these signals have to be connected at the back of a
cabinet, special cables can be supplied. The cables are equipped with
terminal blocks that can be mounted on DIN rails. The cable for the
RS-530 interface can be equipped with isolating terminals or
alternately with D-sub connectors that comply with the standards X.21,
RS-449 or again with RS-530.
For the RJ45 connector of the G.703 interface a 1:1 patch cord cable
and a patch panel with RJ45 and LSA Plus Quick Connect (KRONE)
type connectors can be supplied (see Section 6.5.4 “Connection via
Cable for all Interfaces with RJ45 Connector”).
3.4.3.6. E1/T1 Interface G1LE

The E1/T1 Interface G1LE is an optional sub-module (piggyback) that
can be plugged onto the G3LD. It provides an E1 or T1 interface,
depending on the configuration.

The E1/T1 interface permits the transmission via a digital PDH

interface of 2.048 Mbps (PCM30/31 for SDH access) or 1.544 Mbps
(PCM24 for SONET access). Framing, signaling and line coding can
be programmed according to the prevalent standards.
Of the 32/24 transmitted timeslots per frame (125 s), NSD570 data
are transmitted only in the first timeslot (TS1) after the frame
synchronization pulse. With E1, timeslot 0 (TS0) serves for frame
synchronization and signaling; with T1 this information is contained in
only one bit that precedes TS1. Additionally, 0xFF is transmitted on
TS3 to allow loss of signal detection when AMI line coding is used.
When the G1LE is plugged onto the main board, only the interfaces of
G1LE (E1, T1) can be selected and operated.
For the RJ45 connector of the E1/T1 interface a 1:1 patch cord cable
and a patch panel with RJ45 and LSA Plus Quick Connect (KRONE)
type connectors can be supplied (see Section 6.5.4 “Connection via
Cable for all Interfaces with RJ45 Connector”).
3.4.3.7. Optical Interface G1LO

The Optical Interface G1LO 2 is an optional sub-module (piggyback)
that can be plugged onto the G3LD. It complements the interfaces that
are located on the main board with an optical 1310 nm interface.
The optical interface permits the transmission of protection signals via
fiber optic cables at a data rate of 2.048 Mbps. The G1LO can be
programmed to operate with a direct fiber connection or with
FOX515/512 interfaces such as an OTERM or an OPTIF. G1LO
supports a wavelength of 1310 nm. The correct framing, signaling and
line coding is automatically set after choosing the interface type out of
the HMI570 pull down menu.
When G1LO is plugged onto the main board, only one of the available
interfaces (RS-530, G.703, Optical Direct Fiber, Optical OTERM/
OPTIF) can be selected and operated at the same time.
The optical interfaces are equipped with E2000 type connectors that
provide twin connections, one for the Tx and one for the Rx fiber.
With this interface the NSD570 can be utilized in a point to point
application with a maximum distance of 25 km with multi-mode fibers
and 50 km with single-mode fibers.
2 Phased out by end of 2008.

3.4.3.8. Optical Interface G1LOa

The Optical Interface G1LOa is an optional sub-module (piggyback)
that can be plugged onto the G3LD. It complements the interfaces that
are located on the main board with an optical interface, deployable in
applications where wavelengths of 850 nm, 1310 nm or 1550 nm are
needed.
fiber optic cables at a data rate of 2.048 Mbps. G1LOa can be
programmed to operate with a direct fiber connection, with a
FOX515/512 interface such as an OTERM or an OPTIF, with a
FOX615/612 interface such as an OPIC2, as well as with 3rd party
multiplexer equipment that complies with the IEEE C37.94 standard.
The correct framing, signaling and line coding is automatically set after
choosing the interface type out of the HMI570 pull down menu.
Since the G1LOa can be equipped with a replaceable SFP transceiver
module, the wavelength as well as the output power can be chosen
freely to suit the application.
When the G1LOa is plugged onto the main board, only one of the
available interfaces (RS-530, G.703, Optical Direct Fiber, Optical
OTERM/OPTIF, Optical IEEE C37.94) can be selected and operated.
The SFP transceiver modules are equipped with LC/PC connectors
that provide twin connections, one for the Tx and one for the Rx fiber.
Five basic SFP transceiver modules are recommended (refer to
Section 11.1 “Order numbers”):
• 850 nm, multi-mode, 13 dB optical power budget
1 km nominal reach (up to 2 km max.)
• 1310 nm, single-mode, 19 dB optical power budget
• CWDM 1550 nm, single-mode, 50 dB optical power budget
SFP transceiver modules with a wavelength of 850 nm are usually
used for Optical IEEE C37.94 transmission, 1310 nm modules for
transmission over FOX515/512 or FOX615/612 multiplexers and either
1310 nm or 1550 nm modules for Optical Direct Fiber transmission.
Whereas 1550 nm modules are only supported in direct fiber
applications, all combinations of interface types and 850 nm
respectively 1310 nm SFP transceiver modules are allowed.

3.4.4. Ethernet Line Interface G3LE
3.4.4.1. Block diagram G3LE

G3LE
SFP Sync
RTC
Ethernet HW module
10/100 Base T 100 Base cfg.
FX cfg. CPU
HMI
Backplane G1LA with RTB

select LDP
IRIG-B
RJ45 Video PHY MII MAC
Switch LEDs
PHY FPGA
RTB
RAM Flash Power Supply

conv. voltages
Power
superv.
Fig. 3-13 Block diagram G3LE
3.4.4.2. Short description G3LE

The Ethernet Interface G3LE converts the incoming protection
G3LS into Ethernet packets that are transmitted via the on-board
standard Ethernet line interface. Also, the commands that are received
by the Ethernet line interface are passed on to the appropriate
protection relay interfaces. Communication between the G3LE and the
G3LR/G3LS takes place over the Real Time Bus (RT-Bus) which is
located on the bus plane.
Besides the transmission of Teleprotection commands the Ethernet
Interface G3LE supervises the transmission channel continuously. For
details refer to Section 3.5.8 “Ethernet operating principle”.
For data transmission, any Ethernet/IP based channel can be
employed. It is also possible to operate two NSD570s back-to-back via
the Ethernet Interfaces G3LE.
3.4.4.3. External Interfaces G3LE

The Ethernet WAN Interface G3LE provides one fix mounted electrical
10/100BaseT RJ45 connector enabling connection to electrical
Ethernet. In addition there is one SFP cage mounted on G3LE
allowing insertion of optical SFP transceiver modules. The following
SFP module types are recommended:

• 850 nm, multi-mode, 0.5 km nominal reach (up to 1 km max.)

• 1310 nm, multi-mode, 0.5 km nominal reach (up to 1 km max.)
• 1310 nm, single-mode, 30 km nominal reach (up to 50 km max.)
Only one of the two interfaces can be used at a time. To activate the
desired interface, the slider of the small switch between the two
interfaces has to be set into the accordant position. That interface the
slider is positioned to will be activated.
3.4.4.4. Processor environment G3LE

The circuit includes a 400 MHz clocked PowerPC processor which
carries out the necessary signal evaluation, hash code calculation and
protocol conversions. It is connected to an FPGA which carries out all
accesses to the RT-Bus mentioned in 3.4.4.2. A buffered Real Time
Clock (RTC) provides the system timing. It is also possible to
synchronize the RTC with an external signal that offers 1 second
pulses. Or, alternately, the RTC can be synchronized with an IRIG-B
signal from a GPS receiver. This signal is provided to the G3LE via the
bus plane. The bus plane in turn receives the signal from the Common
Interface G3LC.
The PowerPC processor also contains the interface to a PC/Notebook
that has the User Interface HMI570 installed. It controls the RS-232
interface, fetches the requested data from the accordant services,
passes the data onto the HMI570 and controls the event recorder.
Configuration and firmware updates can also be downloaded from the
PC to the Flash EEPROM that is part of the interface.
A watchdog supervises the processor. The watchdog recognizes when
the processor ceases from operating correctly and issues a reset and
re-start of the processor.
program or data memory error in the PowerPC processor, a RAM
i.e. no Ethernet frames are processed and no changes on the NSD570
must be replaced.
3.4.4.5. External cable and connector G3LE

The fix mounted RJ45 socket and the connector of the plugged SFP
transceiver can be accessed at the back of the NSD570.

To connect G3LE to the Ethernet by the RJ45 connector, a Cat5e

Ethernet cable SF/UTP according to ISO/IEC 11801 (electrical) shall
be used.
For the RJ45 connector of the Ethernet interface a 1:1 patch cord
cable and a patch panel with RJ45 and LSA Plus Quick Connect
(KRONE) type connectors can be supplied (see Section 6.5.4).
Connection information of the optional SFP module and a detailed
description of all module connectors as well as the optional connecting
cables and their pin assignments can be found in Section 6
3.4.5. Relay Interface G3LR
3.4.5.1. Block diagram G3LR

12 V 3.3 V 1B
1C
PROM X101 / 2
12 V 1D Tx Input 1
1A
3.3 V 2.5 V
5V X101 / 1
Connector X100 to front plane bus
2B
2C X101 / 4
GND 2D Tx Input 2
3.3 V
2A
Supervision
X101 / 3
X101 / 6
Rx Output 1
Hardware release coding FPGA
3 (Xilinx Spartan II) X101 / 5
Slot coding
X101 / 8
Rx Output 2
4
SPORT0 X101 / 7
12 V
4
Loop disable
X101 / 9
Relay 1
LED X101 / 11
12 V
8 X101 / 10
X101 / 12
Relay 2
X101 / 14
X101 / 13
3-Block-diagram-G3LR.vsd
Fig. 3-14 Block diagram G3LR
Note: G3LRa provides two more jumpers (1E and 2E) to program the
fourth range of the nominal station battery voltage for the inputs.
3.4.5.2. Short description G3LR

The Relay Interface G3LR serves as the binary input/output logic
interface for the NSD570. It provides the link between the line interface
(G3LA, G3LD or G3LE) and the external protection and logic circuits.
Communication with the line interface takes place through the serial
Real Time Bus (RT-Bus) on the bus plane G1LA. The Relay Interface
G3LR comprises two inputs with opto-couplers, two solid-state outputs
and two relay outputs. Each one of these input and output circuits is
electrically isolated from each other as well as from the internal
circuitry and from ground. The command associations (inputs and

outputs) can be programmed by means of the Web-Browser based

user interface program (HMI570).
The G3LR is plugged into the G1LA bus plane from the rear of the
rack G7BI assembly. At the front of the G3LR module, the internal
signals are connected to the bus plane via a PCI connector. The
external signals are accessible by the customer via a Phoenix
connector block with spring-cage terminals (see Section 3.4.4.7). A
pre-terminated cable with fixed length and terminal block with isolation
knives is available as an option with the G3LR module. The terminal
block assembly can be mounted on a DIN rail at the back or sides of
the cabinet.
All LED indicators are mounted on the front plate and are driven by the
G3LR module via the PCI connector. Green LEDs are provided for
each input, output and relay contact. An “OK/Fail” LED will indicate
“Green” for “OK” condition of the G3LR module or “Red” for a “Failed”
condition. Alarms for the various input/output circuits are signaled by
the “Red” indication; for details refer to Section 9 “Troubleshooting”.
All input and output circuits are equipped with over-voltage and
reverse polarity protection.
3.4.5.3. Inputs G3LR

The G3LR has two isolated command input circuits.
The input circuits can be programmed by jumpers to one of three
(G3LR) or four (G3LRa) voltage ranges for the nominal station battery
voltage. Each programming group covers the lower and upper nominal
battery voltage as follows:
G3LR G3LRa
24 V DC and 48 V DC 24 V DC
60 V DC and 110 V DC 48 V DC and 60 V DC
125 V DC and 250 V DC 110 V DC and 125 V DC
220 V DC and 250 V DC
The switching threshold is approximately 60% to 70% of the lower

voltage of the programmed group.
Each input can be programmed freely to any one of the commands.
For example, Input 1 can be programmed to Command A and Input 2
to Command C.
The command signals are sent to the signal processor on the line
interface via the FPGA and the RT-Bus.

Mal-operations of the G3LR module (e.g. failure of an opto-coupler)

are recognized and will prevent the transmission of an unwanted
command. The G3LR signals its status with the dual color “OK/Fail”
LED (green = all hardware circuits okay / red = hardware alarm on the
module).
An optional piggyback module type G1LR “Input Tripping Voltage
NSD570” can be supplied. This auxiliary power supply provides
wetting voltage (internal 24 V DC). When the piggyback module is
installed, the command inputs can be keyed by a dry contact. A single
G1LR module is required for the two inputs of a G3LR module. Please
refer to Section 3.4.5.6 “Input Tripping Voltage G1LR”.
3.4.5.4. Solid state outputs G3LR

The G3LR has two isolated solid-state outputs.
The output command is received via the RT-Bus. This signal is
checked in the FPGA and when it is deemed valid, the semiconductor
in the output loop is switched on.
In order to protect the semiconductor output from excessive currents
(excessively low impedance burden or capacitive discharge from the
connecting cable), the output circuits are equipped with current limiting
and current shutdown electronics. The activation threshold is about
2.6 A. After the current limiting circuit has been in operation for more
than 5 ms, the output is blocked for approximately 1 s. Then, the
output is again turned on and the process is repeated until the fault
condition is cleared. When the current cut-off mechanism is triggered,
an alarm signal is generated.
Each output can freely be assigned to any one of the commands or
other functions (by means of the HMI570 User Interface Program). For
instance, it is possible to assign Output 1 to command A and Output 2
to Unblocking or Output 1 to Command B and Output 2 to a predefined
alarm.
3.4.5.5. Relay contacts G3LR

In addition to the two solid-state outputs, the G3LR has two electro-
mechanical outputs.
The relays receive the switching signals from the RT-Bus. The NO
(normally open), NC (normally closed) and C (common) contacts are
wired to the external terminal blocks. The function of the relays can be
assigned by means of the HMI570 User Interface Program. For
instance, it is possible to assign Relay 1 to Command B and Relay 2 to
a predefined alarm.

3.4.5.6. Input Tripping Voltage G1LR

The Input Tripping Voltage G1LR is an optional sub-module
(piggyback) that can be plugged onto the G3LR. It generates 24 V DC,
automatically selects the lowest wetting voltage range and injects the
voltage to the required locations. This enables the keying of the
command inputs with an external dry contact but without the use of an
external voltage. With the G1LR, both inputs must be keyed with a
dedicated dry contact only. Any number of G3LR can be equipped with
the G1LR and the G3LR that aren’t equipped with the G1LR can be
operated with a contact and the station battery voltage as required by
the design of the control circuits.
3.4.5.7. External cable and connector G3LR

Each G3LR module is furnished with a 14-pin spring-cage terminal
block for external connections. The user can choose to either connect
directly to these terminals at the back of the rack or, alternatively, to
make connections elsewhere via the optional pre-terminated external
cable to isolating terminal blocks. The external cable for the G3LR
consists of a 14 pin knife-disconnect double pole terminal block plus a
ground terminal, a 15 core cable with wires of 0.75 mm2 cross P P
sectional area.
The Phoenix connectors fulfill the necessary requirements for high
voltages (air and creeping distances according to IEC 60950-1) that
can be applied to the terminals (250 V DC ± 20%).
The isolating terminals are required so that the user can disconnect
the NSD570 from the relays during maintenance work on the NSD570.
Transmitting of unwanted commands can therefore be prevented and
maintenance personnel can be protected from dangerous voltages
(with command voltages > 60 V DC). The terminals accept stranded
wires with a cross sectional area of up to 2.5 mm2 or solid wire with a
P P
cross sectional area of up to of 4 mm2. P P


3.4.6. GOOSE LAN Interface G3LS
3.4.6.1. Block diagram G3LS

G3LS
SFP Sync
RTC
Ethernet HW module
FX cfg. CPU
HMI

select LDP
IRIG-B
Switch LEDs
PHY FPGA
RTB

conv. voltages
Power
superv.
Fig. 3-15 Block diagram G3LS
3.4.6.2. Short description G3LS

G3LS is an Ethernet LAN interface handling GOOSE (Generic Object
Oriented Substation Events) messages according to IEC 61850 for
interconnection with protection relays from HITACHI ABB and also
with protection relays from other vendors in a substation LAN.
Protection commands in incoming GOOSE messages are extracted
and passed on to an Analog, a Digital or an Ethernet WAN line
interface. On the remote side the commands received by the line
interface are packed into GOOSE messages and sent to the
substation LAN or IEC 61850 compatible relays respectively.
G3LS is a supplement to the binary I/O Relay Interface G3LR. One
G3LS module can handle up to eight teleprotection commands. The
command associations can be programmed by means of the user
interface program (HMI570) similar to G3LR. Commands can be
assigned flexible to G3LS or to G3LR by software configuration. The
G3LS module is always plugged into the rack slot next to its line
interface, either in slot N34 or N64. The NSD570 devices TPE 1 and
TPE 2 can be filled up with one to three additional G3LR modules.
Depending on the configuration, G3LS virtually occupies physical
slots. Slots which are not virtually occupied by G3LS can be equipped
with G3LR interfaces.
G3LS is plugged into the G1LA bus plane from the rear of the rack
G7BI assembly. Communication with the line interface takes place

through the serial Real Time Bus on the bus plane G1LA. At the front
of the G3LS module, the internal signals are connected to the bus
plane via a PCI connector. The protection relay(s) can be connected
via a LAN to the external interfaces of G3LS.
All LED indicators are mounted on the front plate and are driven by the
G3LS module via the PCI connector.
Green LEDs in the RELAY INTERFACE 1 section of TPE 1 and TPE 2
are provided for the command input and output groups. If just one
command is contained in the GOOSE message, only the first
Input/Output LED will light up. If more than one command are
contained in the GOOSE message, both Input/Output LEDs will light
up.
Warnings and alarms are indicated with the “Relay” LEDs. G3LS does
not provide physical relay outputs where status information provided
by the corresponding line interface can be signaled. Therefore HMI570
does not enable the user to select such a status signal to be assigned
to a Relay output if G3LS is selected. To signal warnings/alarms to the
protection devices, the dataset published by G3LS contains the logical
nodes LPHD PhyHealth and ITPC EEHealth. PhyHealth is derived
from the “HW Warning” status information of the line interface.
EEHealth is derived from the “Local Alarm” information of the line
interface. The same information is also visualized by the “Relay” LEDs
of G3LS. Relay LED 1 represents the “HW Warning” (PhyHealth) and
Relay LED 2 represents “HW Alarm” (EEHealth).
The “OK/Fail” LED will indicate “Green” for “OK” condition of the G3LS
module or “Red” for a “Failed” condition. Alarms are signalized by the
“Red” indication; for details refer to Section 9 “Troubleshooting”.
3.4.6.3. External Interfaces G3LS

Refer to Section 3.4.4.3 “External Interfaces G3LE”.
3.4.6.4. Processor environment G3LS

Refer to Section 3.4.4.4 “Processor environment G3LE”.
3.4.6.5. External cable and connector G3LS


3.4.7. Display Panel G1LC
3.4.7.1. Short description G1LC

The optional Display Panel G1LC provides various information such as
trip counter reading or alarm messages from the NSD570
teleprotection equipment - without having the need of a PC/notebook.
If the manual loop test button of TPE 1 or TPE 2 is pressed on the
front plate, the measured transmission time is immediately displayed
on G1LC.
The Display Panel is assembled to the Module Rack G7BI, replacing
the blanking cover plate, which is mounted in front of the power supply
units. An enclosed ribbon cable connects the Display Panel G1LC to
the adjacent Common Interface G3LC, providing the 12 V supply
voltage and a 2-wire data link to the line interface of the NSD570
teleprotection devices equipped in the Module Rack.
The readout device is a dot matrix LCD display with two lines, 16
characters each, and a yellow/green background LED. The lightness
of the background LED, the contrast of the LCD and the standby time
of the display are adjustable.
Four buttons, which enable the menu-driven handling, are accessible
on the front of the Display Panel.
3.4.7.2. How to use the Display Panel G1LC

The following four buttons are used to navigate through the menu
structure of the Display Panel G1LC:
Up
Back Enter
Down
Fig. 3-16 Display Panel G1LC

3.4.7.2.1. Display Panel activation and standby

Press any button to activate the Display Panel. The background LED
of the LCD-module will light up (if not configured to OFF in the display
settings menu) and the top level menu “SELECT DEVICE” will appear.
If there is no activity on the Display Panel (no button pressed or no
ongoing task), it will be deactivated automatically after the preset
standby time has elapsed.
3.4.7.2.2. Buttons on G1LC

Use the “Back” button to leave a selected menu item and return to the
upper menu level, to leave a display settings menu without saving the
modifications, to interrupt an ongoing task or to select “no” from a
yes/no query.
Use the “Enter” button to select a menu item, to save modified display
settings, to execute a task or to select “yes” from a yes/no query.
Use the “Up” button to scroll through a menu level, to scroll through
listed information (e.g. trip counters, alarm messages) or to increase
the contrast and lighting settings of the LCD-module (in the
corresponding menu).
Use the “Down” button to scroll through a menu level, to scroll through
listed information or to decrease the contrast and lighting settings of
the LCD-module.
3.4.7.2.3. Menu navigation hints

A flashing ““ sign will appear to indicate that the “Up” or “Down”
button may be used to scroll in this menu level. Note that the flashing
““ sign will only appear while scrolling up or down in the different
menu levels, it will not appear while scrolling through listed information
(because all 16 characters are necessary for displaying the required
data).
Some of the device information (like alarm messages or configuration
data) do exceed the available 16 characters of one display line. In this
case, the text is shifted left automatically. To speed up this procedure
press the “Enter” button and this will provide a word shift instead of
character shift. Additionally, a “→“ sign will appear to indicate that the
following words of the text can be obtained by continuing to press the
“Enter” button. The text will start over after it was completely
displayed.
If no characters are visible at all or if the display is totally dark, the
contrast setting of the LCD-module may be incorrect. Pressing the
“Back” and the “Enter” button simultaneously as well as the “Up” or

“Down” button will allow to change the contrast setting directly

(independent of the actual menu level). Note that the “Back” button
has to be released first in order to store the new contrast setting.
3.4.7.2.4. Reset
A Display Panel reset will occur if the Back button is permanently
pressed for more than 6 seconds.
3.4.7.2.5. Display Panel settings

For the Display Panel itself, the following display settings may be
modified:
1. Increase/decrease the contrast setting of the LCD-module
(16 steps); default: 10
2. Increase/decrease the backlight setting of the LCD-Module
(4 steps and OFF); default: 3
3. Change the standby time of the Display Panel
(1 – 60 minutes); default: 10 minutes
If a display setting was accidentally modified, press the “Back” button
to restore the previous setting.
To save the modified display settings in a non-volatile memory, press
the “Enter” button after selecting the new value.
3.4.7.3. Menu structure Display Panel G1LC
3.4.7.3.1. Top level menu

SELECT DEVICE Visible after pressing any button
| (Back, Enter, Up or Down)
|---TPE 1
| |---MAIN MENU
|
|---TPE 2
| |---MAIN MENU
|
|---TPE 1 Remote
| |---MAIN MENU
|
|---TPE 2 Remote
| |---MAIN MENU
|
|---Display
| |---DISPLAY MENU
| | |---Contrast
| | |---Lighting
| | |---Standby time
| | |---FW/HW Version

3.4.7.3.2. Menu tree if connected to a local device

MAIN MENU
|
|---TRIP COUNTER
| |---CMD A TX/RX
| |---CMD B TX/RX
| |---CMD C TX/RX
| |---CMD D TX/RX
| |---CMD E TX/RX Ethernet & Digital Line Interface only
| |---CMD F TX/RX Ethernet & Digital Line Interface only
| |---CMD G TX/RX Ethernet & Digital Line Interface only
| |---CMD H TX/RX Ethernet & Digital Line Interface only
| |---LOOP TX/RX
| |---UNBLOCKING
| |---CLEAR COUNTER ? If enabled, see 3.4.7.4.4
| | |---CLEAR ALL CTR.
| | |---CLEAR CMD CTR.
| | |---CLEAR LOOP CTR.
| | |---CLEAR UNBL. CTR.
|
|---ALARMS Alarm messages according device state
|
|---STATUS
| |---INTERFACE TYPE
| |---1+1 OPERATION If operation mode 1+1 is configured
| |---LOOP TEST STATE
| |---LOOP TEST TIME
| |---LOOP TEST TIME 60s AVG Ethernet Line Interface only
| |---LOOP TEST TIME 4h AVG Ethernet Line Interface only
| |---PKT. LOSS RATE 60s AVG Ethernet Line Interface only
| |---PKT. LOSS RATE 4h AVG Ethernet Line Interface only
| |---RX LEVEL Analog Line Interface only
| |---TX LEVEL Analog Line Interface only
| |---SNR Analog Line Interface only
| |---BER 200 sec AVG. Digital Line Interface only
| |---BER 262 min AVG. Digital Line Interface only
|
|---FIRMWARE
| |---PROCESSOR
| |---CONTROLLER Analog & Digital Line Interface only
| |---CONFIGURATION
|
|---CONFIGURATION
| |---Device Info
| | |---LINE IF TYPE
| | |---LINE IF POSITION
| | |---SERIAL NUMBER
| | |---FW DOWNLOAD COUNTER
| | |---CONFIG DOWNLOAD COUNTER
| |
| |---HW Versions
| | |---COMMON IF G3LC
| | |---LINE IF G3LA Analog Line Interface only
| | |---LINE IF G3LD Digital Line Interface only
| | |---PIGGYBACK @ G3LD Digital Line Interface only
| | |---LINE IF G3LE Ethernet Line Interface only
| | |---REL. IF G3LR/S N34 If connected to TPE 1 the HW
| | |---REL. IF G3LR/S N40 Information of all 8 Relay
| | |---REL. IF G3LR/S N46 Interfaces are visible
| | |---REL. IF G3LR/S N52
| | |---REL. IF G3LR/S N64 If connected to TPE 2
| | |---BUSPLANE G1LA
| | |---SFP VENDOR Ethernet & Digital Line Interface only
| | |---SFP PART NUMBER Ethernet & Digital Line Interface only
| | |---SFP TRANSC. CODE Ethernet & Digital Line Interface only
| |
| |---Device ID
| | |---STATION NAME
| | |---HE NUMBER
| | |---DEVICE ADDRESS
| |
| |---Common Settings
| | |---DEVICE MODE
| | |---CMD OUT LNK FAIL
| | |---EOC
| | |---CYCL. LOOP TEST
| | |---PROPAGATION TIME

| |
| |---Analog Settings Analog Line Interface only
| | |---LINE TYPE
| | |---RX BANDWIDTH
| | |---RX CENTER FREQ.
| | |---TX BANDWIDTH
| | |---TX CENTER FREQ.
| | |---OPERATING MODE
| | |---POWER BOOST
| | |---UNBL. THRESHOLD
| | |---TX LEVEL
| | |---RX LEVEL
| | |---TX ALARM THRES.
| | |---RX ALARM THRES.
| |
| |---Digital Settings Digital Line Interface only
| | |---INTERFACE TYPE
| | |---BER ALARM THRES.
| | |---ADDRESS CHECK
| | |---LOCAL ADDRESS
| | |---REMOTE ADDRESS
| | |---RS530 DATA RATE RS530 Interface Type only
| | |---RS530 RX CLOCK RS530 Interface Type only
| | |---RS530 TX CLOCK RS530 Interface Type only
| | |---RX CLOCK SYNC RS530 Interface Type only
| | |---TX CLOCK SYNC TT RS530 Interface Type only
| | |---TERMINAL TIMING RS530 Interface Type only
| | |---TX CLOCK SYNC G.703 64kbps codir. Interface Type
| | |---LONG HAUL E1 2048kbps, T1 1544kbps
| | | G1LO Optical Direct Fiber and
| | | OTERM/OPTIF Interface Type
| | |---AUTOMATIC LASER G1LOa Optical Direct Fiber,
| | | SHUTDOWN OTERM/OPTIF and Optical IEEE C37.94
| | | Interface Type
| | |---CLOCK MODE G1LOa Optical Direct Fiber
| | | Interface Type
| | |---RX BUFFER E1 2048kbps and T1 1544kbps Interface
| | | Type
| | |---TX BUFFER E1 2048kbps and T1 1544kbps Interface
| | | Type
| | |---E1 CODING E1 2048kbps Interface Type only
| | |---E1 FRAME FORMAT E1 2048kbps Interface Type only
| | |---T1 CODING T1 1544kbps Interface Type only
| | |---T1 FRAME FORMAT T1 1544kbps Interface Type only
| |
| |---Ethernet Setting Ethernet Line Interface only
| | |---AUTO NEGOTIATION
| | |---DATA RATE
| | |---DUPLEX MODE
| | |---LOCAL IP ADDRESS
| | |---SUBNET MASK
| | |---DEFAULT GATEWAY
| | |---REMOTE IP ADDR.
| | |---TYPE OF SERVICE
| | |---VLAN TAGGING
| | |---802.1Q VLAN ID
| | |---802.1Q PRIORITY
| | |---UDP PORT TP PKT.
| | |---UDP PORT EOC PKT
| | |---GUARD PKT INTERV
| | |---TT TEST INTERV.
| | |---PACKET LOSS RATE
| | | ALARM THR
| | |---AUTOMATIC LASER
| | | SHUTDOWN
| |
| |---Command Settings
| | |---COMMAND A
| | |---COMMAND B
| | |---COMMAND C
| | |---COMMAND D
| | |---COMMAND E Ethernet & Digital Line Interface only
| | |---COMMAND F Ethernet & Digital Line Interface only
| | |---COMMAND G Ethernet & Digital Line Interface only
| | |---COMMAND H Ethernet & Digital Line Interface only
| |
| |---Relay Interfaces If connected to TPE 2
| | |---TPE1 INTERFACE 1 (N34) TPE2 INTERFACE 1 (N64)
| | | |---INPUT 1 If Relay Interface 1 = G3LR or G3LS
| | | |---OUTPUT 1 If Relay Interface 1 = G3LR or G3LS
| | | |---RELAY OUTPUT 1 If Relay Interface 1 = G3LR


|
|---MAINTENANCE
| |---Get Time & Date
| | |---TIME
| | |---DATE
| |---Reset TPE x x = 1 or 2
| |---RESET TPE x ? x = 1 or 2
|
|---DEVICE ADDRESS
3.4.7.3.3. Menu tree if connected to a remote device

MAIN MENU
|
|---TRIP COUNTER
| |---CMD A TX/RX
| |---CMD B TX/RX
| |---CMD C TX/RX
| |---CMD D TX/RX
| |---LOOP TX/RX
| |---UNBLOCKING
|
|---ALARMS Alarm messages according device state
|
|---STATUS
| |---INTERFACE TYPE
| |---1+1 OPERATION If operation mode 1+1 is configured
| |---LOOP TEST STATE
| |---LOOP TEST TIME
| |---LOOP TEST TIME 60s AVG Ethernet Line Interface only
| |---LOOP TEST TIME 4h AVG Ethernet Line Interface only
| |---PKT. LOSS RATE 60s AVG Ethernet Line Interface only
| |---PKT. LOSS RATE 4h AVG Ethernet Line Interface only
| |---RX LEVEL Analog Line Interface only
| |---TX LEVEL Analog Line Interface only
| |---SNR Analog Line Interface only
| |---BER 200 sec AVG. Digital Line Interface only
| |---BER 262 min AVG. Digital Line Interface only
|
|---FIRMWARE
| |---PROCESSOR
| |---CONTROLLER Analog & Digital Line Interface only
| |---CONFIGURATION

3.4.7.4. Additional features of Display Panel G1LC
3.4.7.4.1. Requirements
The additional features of the Display Panel G1LC are only available if
the micro controller firmware version of the line interfaces G3LA or
G3LD is greater or equal to Version 1.04 and if the firmware version of
the Display Panel G1LC is greater or equal to Version 1.01.
For details refer to the document “Compatibility requirements NSD570”
(1KHW000902-EN) in Section 12 “Annex”.
3.4.7.4.2. Display device communication baud rate

If the item “Device Address” in the main menu is selected, the
configured baud rate for the RS-232 communication of the connected
line interface is displayed as well.
This may be helpful for quickly finding out to what baud rate the
HMI570 must be configured.
3.4.7.4.3. Reset counters via display panel

If the conditions described in the Section 3.4.7.4.1 “Requirements” are
met, it is possible to reset the counters of the local line interfaces via
the display panel. The user can select “clear all counters”, “clear
command counters”, “clear loop test counters” or “clear unblocking
counter”. The event recorder of the line interface will consequentially
record an event “Trip counter reset”.
It is not possible to reset a single command counter only (e.g. Tx
Counter Command A) via the display panel.
Extended trip counter menu:
MAIN MENU
|
|---TRIP COUNTER
| |---CMD A TX/RX
| |---CMD B TX/RX
| |---CMD C TX/RX
| |---CMD D TX/RX
| |---LOOP TX/RX
| |---UNBLOCKING
| |---CLEAR COUNTER?
| | |---CLEAR ALL CTR.
| | |---CLEAR CMD CTR. Only available if the conditions
| | |---CLEAR LOOP CTR. according to 3.4.7.4.3 apply
| | |---CLEAR UNBL. CTR.

3.4.7.4.4. Disabling reset counters via display panel

If it is not allowed to reset the trip counters via the display panel, this
feature can be disabled via a solder bridge (see Fig. 3-17).
SY300
Reset of the trip

counters via the display
panel is enabled
(default)
SY300
Reset of the trip

counters via the display
panel is disabled
Fig. 3-17 Disabling reset counters
3.4.7.4.5. Automatic display of Tx or Rx commands

If a line interface G3LA, G3LD or G3LE has sent or received a
command, the Display Panel G1LC will automatically switch on and
display the following messages (examples for commands on TPE 1):
TX COMMAND SENT!
ON TPE 1
RX CMD RECEIVED!
ON TPE 1
Usually, if there is no activity on the display panel (no button pressed
or no ongoing task), the display will be deactivated automatically after
the preset standby time has elapsed. In case of an automatically
displayed sent or received command, the display will not be
deactivated after the preset standby time – the last command state will
be displayed until there is any manual activity.
In large substations this feature permits a quick indication of a
NSD570 link that has transferred protection commands.

3.4.8. LAN Interface G3LL
3.4.8.1. Short description G3LL

The NSD570 LAN Interface G3LL 3 is an Ethernet 10/100BaseT
interface. It can be used to connect one or more NSD570 systems to
TCP/IP-networks for configuration, monitoring and maintenance.
The user interface “HMI570 LAN” is embedded on the NSD570 LAN
Interface. This allows to use the HMI570 LAN from every computer
that is connected to the LAN/Intranet. There is no local installation of
an application necessary. A common web browser (Internet Explorer)
is needed on the PC/notebook for using the HMI570 LAN on G3LL.
Substation A
NSD570 Rack
G3LA 0 ... 4 G3LA 0 ... 4

or G3LR or G3LR
G3LD and/or G3LD and/or
or 0 ...1 or 0 ...1
G3LE G3LS G3LE G3LS
Station bus
NSD570 Rack
Ethernet
10/100BaseT
Internet /
Intranet
G3LA 0 ... 4 G3LA 0 ... 3 HMI570
or G3LR or G3LR LAN
LAN
or 0 ...1 or 0 ...1
Interface
G3LE G3LS G3LE G3LS
G3LL
Web Browser
3-LANIFSubstation_G3LL
Fig. 3-18 Connection to the NSD570 devices via G3LL
Note: In order to get access to the station bus via G3LL, a

two wire connection is required from G3LL to the
Supply Backplane G1LB (refer to Sections 3.4.8.3
“External cables and connectors G3LL” and 6.5.3.7.2
“Station bus”).
3 Phased out by end of 2012

3.4.8.2. Block diagram G3LL
NSD570
Bus Plane
Ok/Fail LAN
Isolation
bus driver Link LAN
5V_L DC/DC 12V

PC/104
PC/104
External connections
at rear of equipment
5V_485 DC/DC 12V
RS485
LAN (RJ45)
10/100 BaseT
X201
COM1
HW_COMI
Stationbus (RS485) Isolation Switch Isolation

X500 RS485 driver Logic bus driver
3 BlockDiagramG3LL
Fig. 3-19 Block diagram G3LL
3.4.8.3. External cables and connectors G3LL

For the RJ45 connector X201 of the LAN interface a 1:1 patch cord
cable and a patch panel with RJ45 and LSA Plus Quick Connect
(KRONE) type connectors can be supplied (see Section 6.5.4
“Connection via Cable for all Interfaces with RJ45 Connector”).
The external signals for the RS-485 station bus are provided on the
X500 connector (1 - 7; spring-cage terminals). For proper operation it
is necessary to wire the station bus available on the supply backplane
G1LB to the station bus of the NSD570 LAN Interface. This can be
done using an optional connecting cable, making the signals of G3LL
and G1LB available over disconnectable terminals.
3.4.8.4. Restrictions associated with G3LS

In contrast to PC-based HMI570, IEC 61850 support is not available
for HMI570 “LAN” version running on G3LL. However it is possible to
configure a G3LS device via a G3LL LAN interface if the IEC 61850
configuration is available as ICZ file. HMI570 “PC” version with
optionally installed IEC 61850 support may be used to export
IEC 61850 configurations to files in ICZ format.

3.4.9. Management LAN Interface G3LM
3.4.9.1. Short description G3LM

The NSD570 Management LAN Interface G3LM is an Ethernet
10/100BaseT interface. It can be used to connect one or more
NSD570 systems to TCP/IP-networks for configuration, monitoring and
maintenance.
In contrast to the LAN interface G3LL, no embedded web server and
User Interface software (HMI570 LAN) is running on G3LM. Instead,
Ethernet to serial port conversion (and vice versa) is performed on the
G3LM module to enable HMI570 communication with NSD570
equipment. SSL is used for secure communication over IP networks.
Simple Network Management Protocol (SNMP) allows network
management stations to retrieve events and basic equipment
information of NSD570 equipment connected to the station bus from
G3LM.
Additionally, the Simple Network Time Protocol (SNTP) client can be
enabled on G3LMa and thus synchronize NSD570 equipment via the
IRIG-B output with the UTC time received from an SNTP/NTP server. 4
Substation A
NSD570 Rack
G3LA 0 ... 4 G3LA 0 ... 4

or G3LR or G3LR
or 0 ...1 or 0 ...1
G3LE G3LS G3LE G3LS
SNTP/NTP Server
Station bus
IRIG-B
NSD570 Rack
Ethernet
10/100BaseT
Internet /
Intranet
G3LA 0 ... 4 G3LA 0 ... 3
Mgmt.
or G3LR or G3LR
LAN
Interface
or 0 ...1 or 0 ...1
G3LM
G3LE G3LS G3LE G3LS
IRIG-B HMI570
Output*
3-LANIFSubstation_G3LM * Available only with G3LMa
Fig. 3-20 Connection to the NSD570 devices via G3LM
4 Synchronization of NSD570 via SNTP client on the management interface is

only possible with the use of the appropriate firmware (version 1.14 or
higher), hardware (G3LMa) and cable (G3LMa STATION BUS/SYNC).

Note: In order to get access to the station bus via G3LM, a

Common Interface G3LC with hardware version 2 or
higher is required in the NSD570 rack.
3.4.9.2. G3LM Services

The following services are running on G3LM.
User administration:
For security reasons the user accounts for remote access over the
Management LAN Interface G3LM are located on G3LM and have to
be administrated separately from the HMI570 internal ones.
Access control:
All user activities performed on NSD570 equipment over G3LM are
supervised. The user can only perform activities according to his
permission.
User activity logging:
The most important user activities e.g. log in/out, configuration
up/download are logged. The log file can be accessed by HMI570.
Event Polling:
G3LM is able to poll all NSD570 line interfaces connected to the
station bus. Alarms, commands and manipulation events (for Rel. 3.1
to 3.6: alarms only), as well as basic device information can be
retrieved either by network alarm polling of HMI570 or by SNMP
requests.
SNMP agent:
The SNMP agent processes SNMP requests and sends traps to
network management stations as soon as new events are discovered.
SNTP client:
This client polls NTP/SNTP servers in the network for UTC time and
generates synchronized real time signal provided via IRIG-B output on
G3LMa.

3.4.9.3. Block diagram G3LM

G3LM
SFP Sync
RTC
Ethernet HW module
FX cfg. CPU
HMI

select LDP
IRIG-B IN
Switch LEDs
PHY FPGA
RTB

conv. voltages
Power
IRIG-B OUT* superv.
* Available only with G3LMa
Fig. 3-21 Block diagram G3LM
3.4.9.4. External Interfaces G3LM

Refer to Section 3.4.4.3 “External Interfaces G3LE” for the description
of RJ45 and SFP interfaces.
In addition to this, a 2-pin IRIG-B output interface is available on
G3LMa, which provides accurate timing information when the SNTP
client 5 on G3LMa is synchronized to an NTP/SNTP server.
3.4.9.5. Processor environment G3LM

Refer to Section 3.4.4.4 “Processor environment G3LE”.
In comparison to G3LE there is no RAM monitoring implemented on
G3LM since G3LM is not involved in mission critical data traffic
handling.
3.4.9.6. External cables and connectors G3LM

Station bus access of the G3LM module is provided via the NSD570
Bus Plane. Therefore no additional wiring is required for this. For
synchronizing NSD570 and other devices via G3LMa IRIG-B output,
the cable “G3LMa STATION BUS/SYNC” shall be used.
5 SNTP client on G3LMa is supported starting with the firmware version 1.14.

3.5. Functional description
3.5.1. General operating principle

In the guard state, i.e. when there is no command actuated at the
inputs, the NSD570 transmits a guard signal. The guard signal is
continuously processed by the receiver in the opposite station, which
gives alarm should the signal quality become inadequate.
In the command state, the NSD570 interrupts the guard signal to
transmit the command signal within the chosen communication
channel (analog, digital, optical or Ethernet/IP).
If the continuous command supervision is enabled and the duration of
a command transmission exceeds a predefined value, an alarm will be
given at the transmit end and the guard is switched on again.
As soon as the receiver recognizes the missing guard signal and
simultaneously detects a valid command signal of adequate quality,
the command is relayed to the designated output.
Simultaneous reception or simultaneous loss of a command signal and
the guard signal leads to an alarm. In the latter case, the output(s)
programmed for unblocking function are activated.
An unblocking (deblocking) function is standard on all units, which
closes a contact for 200 ms (default setting; configurable) in the event
of loss of signal. Deblocking is sometimes used in the case of
permissive overreaching schemes.
All interfaces are potential free and DC isolated. A command is usually
transmitted by applying a DC voltage (contact + battery). At the
receiving end, each command may be mapped to a main (solid state)
and an auxiliary (relay) contact on the relay interfaces. Outputs may
also be used to signal various alarm sources or to acknowledge a Tx
or Rx command signal. For IEC 61850 applications, Tx/Rx command
signals can be exchanged with the protection devices via the
substation LAN by means of GOOSE messages.
3.5.2. Signal processing

Signals are processed completely digitally by a signal-processor on
the line interface, i.e. signal generation at the transmitting end and
filtering and evaluation of the guard and tripping signals at the
receiving end.
The only A/D and D/A converters are at the AF inputs/outputs of the
Analog Interface G3LA.

The data interfaces on the Digital Interface G3LD and the Ethernet
WAN Interface G3LE convert the input commands into a line signal
conforming to the interface in use. The digital techniques employed
obviate any need for calibration.
Digital processing eliminates calibrating, as well as the influences of
ageing and temperature fluctuations. Adaptive algorithms especially
developed for this type of teleprotection equipment adjust themselves
continuously to the prevailing channel conditions and achieve even
under worst-case conditions the high degree of security against loss of
genuine, respectively acceptance of false tripping commands, which is
essential for protection signals even if the communications channel is
disturbed.
3.5.3. Analog operating principle

The NSD570 Analog operates according to the frequency shift
principle.
Guard and command signals are transmitted within the selected
frequency band. The guard signal is always represented by a single
tone. Command signals can either be a single-tone or a dual-tone
signal, depending on the operating mode. Command signals can be
transmitted at a higher power than the guard signal (power boosting).
An NSD570 equipped for several commands transmits each signal or
signal combination with the same (full) power so that the maximum
possible signal-to-noise ratio is achieved at the receiver.
Alarm is given at the receiver if the signal-to-noise ratio is too low or if
the signal level is out of a pre-defined level range.
Up to eight pre-set frequencies corresponding to the various
commands or command combinations are provided in the chosen
frequency band.
3.5.3.1. Single-tone principle

A single tone command is represented by a single frequency for
obtaining the best practical signal-to-noise ratio and short command
transmission time. In the command state, with no power boosting
being programmed, a discrete frequency of the same amplitude as the
guard signal is transmitted.

Available
Bandwidth Frequency
Amplitude
Guard Signal
Trip Signal
Trip Test Group Frequency Time

signal signal signal 3-Analog-operating-principle.vsd
Fig. 3-22 Single-tone principle
3.5.3.2. Dual-tone principle

When dual tone command transmission is used, the tripping signal is
represented by two discrete frequencies to give added security against
speech and interference, e.g. an audio frequency generator. In the
command state two discrete frequencies (tones) are transmitted
simultaneously. With no power boosting being programmed, the
multiplex signal has the same amplitude (peak envelope power) as the
guard signal; but since each tone is transmitted at a 6 dB lower level,
the power level of the command signal is 3 dB lower than the power
level of the guard signal.
Available
Amplitude Bandwidth Frequency
Guard Signal
Trip Signal
F1 F2 F3 F4 F5 Frequency Time
3-Analog-operating-principle.vsd
Fig. 3-23 Dual-tone principle
3.5.3.3. Programming of the analog system

A special user interface program, the HMI570 is provided for setting
the unit, i.e. choice of channel frequency, bandwidth, commands and
their application (blocking, permissive or direct tripping), the alarm
threshold and the response of the unit in case of a link alarm.
Being able to program the unit eliminates tuned frequency dependent
components, which simplifies the stocking of spare parts and makes
the units more readily interchangeable.
The ability to program the unit enables the best use to be made of the
available bandwidth and the operation to be adapted to the different
requirements of the various protection schemes.

For example, the bandwidth can be set by means of the HMI570 in

accordance with the specified transmission time. NSD570s equipped
for one command only permit the fastest transmission time to be
obtained in the selected bandwidth. If more than one command is to
be transmitted in the same bandwidth, a slightly higher transmission
time has to be accepted.
The frequency band is used in the same way as for a narrow band
data channel with signaling speeds between 50 Bd and 1200 Bd. The
channel center frequencies (center of the band) can be selected in
steps of 60 Hz.
The levels of security and dependability are given after the application
for the specific command is chosen.
The basic version of the NSD570 Analog is designed to transmit two
independent commands. By inserting an additional Relay Interface
G3LR or just one GOOSE LAN Interface G3LS, it can be expanded to
handle up to four independent commands. An NSD570 with two
commands is ideal, for example, for protecting a dual-circuit line.
The AF interfaces on the Analog Interface G3LA can be programmed
for a rated impedance of 600 Ohms or for high-impedance termination,
which enables units to be connected in parallel for frequency
multiplexed operation. The following diagram shows a few typical
examples of how channels can be allocated when using the analog
NSD570, where the numbers in the shaded boxes denote the
respective center frequencies:
1) SPEECH 2000 Hz 2760
1200
2) 960 1920 2880
960 960 960
3) 1500 3480
2400 960
0 0.3 0.5 1.0 1.5 2.0 2.5 3.0 3.4 3.96 kHz
3-Example_channel_allocation.vsd
Fig. 3-24 Channel allocation with analog NSD570

Example 1) shows a PLC application. An NSD570 channel 1200 Hz

wide with a center frequency of 2760 Hz is superimposed on a PLC
speech channel with a bandwidth limited to 2000 Hz.
Example 2) shows how three NSD570, each set to a bandwidth of
960 Hz, can be accommodated in one AF channel limited to 3400 Hz.
Example 3) shows two NSD570 in an AF speech channel if the whole
frequency range of 300 Hz put to 3960 Hz may be used. One NSD570
with a bandwidth of 2400 Hz ensures extremely short transmission
times, whereas the other with a bandwidth of 960 Hz, for example, can
be used for direct transfer tripping.
In all three cases, each of the NSD570, i.e. each of the frequency
bands shown, can handle one or up to four commands. Example 2
could therefore amount to a total of 12 independent commands.
The corresponding transmission times are found in the Technical Data
in Section 12 “Annex”.
3.5.4. Analog operating modes

The NSD570 can be programmed for the following operating modes.
3.5.4.1. 1 single tone command A

Single tone test and guard signal
1 single tone command “A” (for blocking application only!)
Programmable for bandwidth:
120, 240, 360, 480, 960, 1200, 2400, 2800 Hz
Available
Amplitude Bandwidth
F1 F2 F3 Frequency
Fig. 3-25 1 single tone command A
Command assignment to frequencies:

Injected F1 F2 F3 Transmitted
Guard X Guard
A X A
Test X Test

Calculation of frequencies:
Bandwidth FShift
B B Calculation
120 Hz 33.90 Hz Fc = Rx or Tx center frequency
240 Hz 65.57 Hz configured by HMI570
F1 = Fc – FShift
360 Hz 95.24 Hz
B
F2 = Fc
480 Hz 125.00 Hz
F3 = Fc + FShiftB B
960 Hz 235.29 Hz
1200 Hz 285.71 Hz
2400 Hz 500.00 Hz
2800 Hz 666.67 Hz
3.5.4.2. 2 independent single tone commands A, B

Single tone test and guard signal
2 independent single tone commands “A”, “B”
240, 360, 480, 960, 1200, 2400, 2800 Hz
Available
Amplitude Bandwidth
F1 F2 F3 F4 F5 Frequency
Fig. 3-26 2 independent single tone commands A, B

Injected F1 F2 F3 F4 F5 Transmitted
Guard X Guard
A X A
B X B
A&B X A&B
Test X Test

Bandwidth FShift
B B Calculation
120 Hz n.a. Fc = Rx or Tx center frequency
F1 = Fc – 2*FShift
360 Hz 52.63 Hz
B
F2 = Fc – FShift
480 Hz 71.42 Hz
B
F3 = Fc
960 Hz 142.86 Hz
F4 = Fc + FShiftB
1200 Hz 181.82 Hz
F5 = Fc + 2*FShift B B
2400 Hz 285.71 Hz
2800 Hz 400.00 Hz
3.5.4.3. 2 independent dual tone commands A, B

Dual tone test, single tone guard signal
2 independent dual tone commands “A”, “B”
240, 360, 480, 960, 1200, 2400, 2800 Hz
Available
Amplitude Bandwidth
F1 F2 F3 F4 F5 Frequency
Fig. 3-27 2 independent dual tone commands A, B

Injected F1 F2 F3 F4 F5 Transmitted
Guard X Guard
A X X A
B X X B
A&B X X A&B
Test X X Test

Bandwidth FShift
B B Calculation
F1 = Fc – 2*FShift
360 Hz 46.51 Hz
B
F2 = Fc – FShift
480 Hz 62.50 Hz
B
F3 = Fc
960 Hz 111.11 Hz
F4 = Fc + FShift B
1200 Hz 133.33 Hz
F5 = Fc + 2*FShift B
2400 Hz 250.00 Hz
2800 Hz 285.71 Hz
3.5.4.4. 3 independent dual tone commands A, B, C

3 independent dual tone commands “A”, “B”, “C”
360, 480, 960, 1200, 2400, 2800 Hz
Available
Amplitude Bandwidth
F1 F2 F3 F4 F5 F6 Frequency
Fig. 3-28 3 independent dual tone commands A, B, C

Injected F1 F2 F3 F4 F5 F6 Transmitted
Guard X Guard
A X X A
B X X B
C X X C
A&B X X A&B
B&C X X B&C
A&C X X A&C
A&B&C X X A&B&C
Test X X Test

Bandwidth FShift
B B Calculation
240 Hz n.a. configured by HMI570
F1 = Fc – 2.5*FShift
360 Hz 44.44 Hz
B
480 Hz 58.82 Hz
B
B
960 Hz 105.26 Hz
F4 = Fc + 0.5*FShift B
1200 Hz 125.00 Hz
F5 = Fc + 1.5*FShift B
2400 Hz 250.00 Hz
F6 = Fc + 2.5*FShift B B
2800 Hz 285.71 Hz
3.5.4.5. 4 independent dual tone commands A, B, C, D

4 independent dual tone commands “A”, “B”, “C”, “D”
480, 960, 1200, 2400, 2800 Hz
Available
Amplitude Bandwidth
F1 F2 F3 F4 F5 F6 F7 F8 Frequency
Fig. 3-29 4 independent dual tone commands A, B, C, D


Injected F1 F2 F3 F4 F5 F6 F7 F8 Transmitted
Guard X Guard
A X X A
B X X B
C X X C
D X X D
A&B X X A&B
B&C X X B&C
C&D X X C&D
A&C X X A&C
B&D X X B&D
A&D X X A&D
A&B&C X X A&B&C
A&B&D X X A&B&D
A&C&D X X A&C&D
B&C&D X X B&C&D
A&B&C&D X X A&B&C&D
Test X X Test
Bandwidth FShift
B B Calculation
240 Hz n.a. configured by HMI570
F1 = Fc – 3.5*FShift F5 = Fc + 0.5*FShift
360 Hz n.a.
B B B
F2 = Fc – 2.5*FShift F6 = Fc + 1.5*FShift
480 Hz 42.55 Hz
B B B
F3 = Fc – 1.5*FShiftB B F7 = Fc + 2.5*FShift
B
960 Hz 83.33 Hz
F4 = Fc – 0.5*FShiftB B F8 = Fc + 3.5*FShift
B
1200 Hz 111.11 Hz
2400 Hz 222.22 Hz
2800 Hz 250.00 Hz

3.5.5. Processing of unused commands

In order to improve security against unwanted operation, the NSD570
receiver ignores all received frequency pairs which would activate one
or more commands not configured to any output of any relay interface
of the equipment.
Example:
Of the 4 available commands A, B, C and D, command D is not
configured to any G3LR/G3LS output of the equipment.
The NSD570 receiver of the equipment then considers only
- the frequency pair belonging to the command A and
- the frequency pair belonging to the command B and
- the frequency pair belonging to the command C and
- the frequency pairs belonging to the command combinations A&B,
A&C, B&C, A&B&C and
- the frequency pair belonging to the test command,
and ignores all other frequency pairs, i.e.
- the frequency pair belonging to the command D and
- the frequency pairs belonging to command combinations
containing D: A&D, B&D, C&D, A&B&D, A&C&D, B&C&D,
A&B&C&D.
3.5.6. Digital operating principle

The NSD570 Digital uses a cyclic block code to transmit guard, test
and command messages in the digital communication channel.
During normal operation the NSD570 transmits a guard message. This
signal is generated by the digital signal processor (DSP) on the Digital
Interface G3LD and passed on to the configured data interface which
converts it to the corresponding line signal before sending it to the
multiplexer.
At the receiver, the line signal coming from the multiplexer is entered
via the data interface into the signal processor and is continuously
evaluated. Alarm is given should the bit error rate exceed a pre-set
level.
Upon being instructed to send one or more commands, the NSD570
interrupts the guard message and transmits the command message.
Command messages recognized by the receiver as being genuine
appear as command(s) at the appropriate output(s) after a code
evaluation time which is depending on the application setting of the
individual commands.

3.5.6.1. Digital code structure

The block code used for guard, test and command messages is
BCH (31,21,5) - the well-known and proven Bose-Chaudhuri-
Hocquenghem code. The hamming distance of the code is 5, i.e. at
least 5 bits are different between the individual guard/test/command
code words). 21 bits are utilized for guard, commands, test, EOC and
digital address (5 bits in each frame, 10-bit address combined after
two frames). The remaining 10 bits are used for detection and
correction of bit errors.
3.5.6.2. Digital frame structure

The 31 bits of the BCH (31,21,5) code are extended with 17 synchro-
nization bits, which leads to a frame length of 6 x 8 bits = 48 bits in
64 kbps mode of the G.703 and RS-530 interface.
For the 56 kbps mode of the RS-530 interface the code is extended
with 18 synchronization bits which leads to a frame length of 7 x 7 bits
= 49 bits.
At least 2 frames and up to 6 frames are evaluated. A dynamic
adaptive frame evaluation - depending on prevailing channel condition
- is implemented in the receiver of the digital NSD570.
The following numbers of consecutive frames are evaluated for a
specific command (all of them having no bit errors or max. 1 bit error
respectively):
- blocking 2 or 3 frames
- permissive tripping 3 or 5 frames
- direct tripping 4 or 6 frames
3.5.6.3. Programming of the digital system

A special user interface program, the HMI570 is provided for setting
the unit, i.e. choice of the data interface in use, commands and their
application (blocking, permissive or direct tripping), the alarm threshold
and the response of the unit in case of a link alarm.
Being able to program the unit eliminates tuned frequency dependent
components, which simplifies the stocking of spare parts and makes
the units more readily interchangeable.
existing data interface of the multiplexer and the operation to be
adapted to the different requirements of the various protection
schemes.
The levels of security and dependability are given after the application
for the specific command is chosen.

The basic version of the NSD570 Digital is designed to transmit two

commands. By inserting up to three additional Relay Interfaces G3LR
or just one GOOSE LAN Interface G3LS, it can be expanded to handle
up to eight commands. An NSD570 with six commands is ideal, for
example, for phase segregated protection of a dual-circuit line.
3.5.7. Digital operating modes

There are no special operating modes for the digital NSD570 as they
are known for the analog version - except for the fact that several
digital (and optical) standard interfaces are available and various bit
transfer rates are supported. The operating modes of the different
interfaces are described in Section 5.7 “Configuration notes for
NSD570 Digital”.
3.5.8. Ethernet operating principle

The NSD570 Ethernet uses a proprietary protocol (patent pending)
which defines the payload of a UDP/IP packet. The UDP port that is
used for the transmission can be set by means of the User Interface
Program HMI570, for details refer to Section 4.10.5.3 “Edit
Configuration”.
Beside the actual Teleprotection commands the payload content
comprises several data fields which allow for measurement of various
parameters. The following channel conditions can be evaluated:
• Transmission time
• Packet loss
• Channel loss
Alarms are being generated in case that one or more of these
parameters exceed user configurable values.
The entire payload is protected by an SHA-256 keyed hash code, a
sequence number and a unique node address which cover several
security issues. Possible attacks as Man-in-the-middle, Replay or
Message fake can be recognized and repelled.
3.5.8.1. Channel supervision

Various effects lead to the fact that the transmission time on a packet
switched network varies. Therefore, special means of channel
supervision have to be applied in order to judge channel availability
and quality.
For this purpose, the NSD570 Ethernet sends continuous guard
packets. The Guard Packet Sending Interval – referred to as TG in Fig.
3-30 - can be set by means of the User Interface Program HMI570, for

details refer to Section 4.10.5.3 “Edit Configuration”. In order to

supervise the channel availability, the reception of packets in regular
intervals is measured. If two subsequent packets from one NSD570
Ethernet are not received by the remote one within a certain interval,
the link is regarded as broken and an alarm is raised.
In order to supervise the channel quality, the NSD570 Ethernet
measures the Packet Loss Rate (i.e. the ratio of sent to received
packets) and the transmission time in a certain interval (user
adjustable). The measurement of the transmission time TT in Fig. 3-30
is eminently important as it depends on it whether or not a time-critical
protection command can be received within a delay which is adequate
for the application. An alarm is raised if the measured delay exceeds a
given threshold.
The Transmission Time Test Interval – referred to as TTT in Fig. 3-30 –
can be set by means of the User Interface Program HMI570, for details
refer to Section 4.10.5.3 “Edit Configuration”.
Station A Station B
Guard packets
TG - configurable
Trans.Time loop test packets
TTT - configurable
Trans.Time loop test packets
TT - measured
Fig. 3-30 Channel supervision
The handling of packet loss and transmission time values and

associated alarming is described in Section 3.5.15.1 “Transmission
Time and Packet Loss monitoring”.

3.5.8.2. Command handling

As soon as a command is injected, the NSD570 Ethernet starts
sending tripping packets which are being repeated in an interval of two
milliseconds referred to as TR in Fig. 3-31. This ensures fast reception
of packets even under very bad channel conditions, i.e. if some
packets get lost.
Reception of one packet at the receiving side triggers the configured
relay interface outputs according to the commands received within the
packet.
After fifteen repetitions with two milliseconds interval (i.e. 16 tripping
packets total), the NSD570 Ethernet continuous sending tripping
packets in the Guard Packet Sending Interval (described in Section
3.5.8.1. “Channel supervision”) until the command is removed from the
input and pure guard packets are transferred further on.
Station A Station B
Guard packets
Trans. Time loop test packets
Command fed in
Tripping packets
Command TR
repetition
≈ ≈
Switchback to „idle
mode“
i.e. sending of
Guard packets
Fig. 3-31 Command handling
3.5.8.3. Programming of the Ethernet system

A special User Interface program, the HMI570 is provided for setting
the unit, i.e. choice of the data interface in use, commands, alarm
thresholds and the response of the unit in case of a link alarm.

existing data interface and the operation to be adapted to the
conditions of the given transmission channel.
The basic version of the NSD570 Ethernet is designed to transmit two
commands. By inserting up to three additional Relay Interfaces G3LR
or just one GOOSE LAN Interface G3LS, it can be expanded to handle
up to eight commands. An NSD570 with six commands is ideal, for
example, for phase segregated protection of a dual-circuit line.
3.5.9. Ethernet operating modes

There are no special operating modes for the NSD570 Ethernet as
they are known for the Analog version - except for the fact that the
built-in electrical Ethernet interface or alternatively an optical SFP
module interface can be used and that different transmission data
rates can be selected. The operating modes of the different interfaces
are described in Section 5.8 “Configuration notes common for G3LE,
G3LM and G3LS”.
3.5.10. GOOSE operating principle

Generic Object Oriented Substation Events (GOOSE) according to
IEC 61850 are used as a control model mechanism in which any
format of data (status, value) is grouped into a data set. The protocol is
designed to transmit this data set with real-time requirements from one
device to some other devices.
GOOSE data is directly embedded into Ethernet data packets and
works on publish-subscribe mechanism with multicast MAC
addresses. GOOSE messaging uses VLAN and priority tagging as per
IEEE 802.1Q to have a separate virtual network within the same
physical network and sets appropriate message priority levels.
Precautions must be taken that all network switches in the LAN are
correctly configured, using dedicated VLANs and appropriate priority
for GOOSE message exchange.
To meet the timing requirements, the GOOSE protocol is implemented
using an enhanced retransmission mechanism as shown in Fig. 3-32.
Change of information = event
Tmax Tmax Tmin Tmin Tmax t
Fig. 3-32 GOOSE frame flow example

The current state of information is periodically distributed to listening

devices. In case no change of information takes place, the period
between two GOOSE messages is Tmax. These GOOSE messages
may be observed by the receiving devices as a kind of heart beat
signal.
In case of an event (i.e. a change of information), the GOOSE
message is retransmitted immediately. Events are retransmitted with
increasing intervals (e.g. after Tmin = 4 ms, 8 ms, 16 ms, etc.). Please
note that the appearance and disappearance of a command signal are
considered as individual events.
Tmin and Tmax can be configured. These parameters are part of the
G3LS IEC 61850 configuration which is extracted from the substation
configuration file generated by the system engineering tool. GOOSE is
the only network protocol supported by G3LS.
3.5.11. GOOSE operating modes

According to IEC 61850 basically every data object of a logical node
can be assigned to a GOOSE data set. Engineering tools such as
HITACHI ABBs “IET” support the substation engineer with the
configuration of G3LS. Since the data received by G3LS via GOOSE
are forwarded to a line interface which allows transferring a maximum
of eight command “bits”, only a few data objects related to trip
command transmission are processed by NSD570. Others are
ignored.
3.5.12. Common functions
3.5.12.1. Command application

Each command can be configured individually for transmitting
protection signals in blocking, permissive tripping or direct tripping
protection schemes.
Choosing the application of the command determines the individual
evaluation of the corresponding tripping signals regarding security and
dependability. The transmission time depends on the channel quality
(SNR/BER/PLR). The processing of the line signal is adaptive and
therefore always ensures the shortest possible transmission times for
the chosen application and the available channel quality.
The NSD570 Analog can transmit up to 4 commands (A - D), the
NSD570 Digital and NSD570 Ethernet can transmit up to 8 commands
(A - H) in any combination.

3.5.12.2. Unblocking
An “unblocking” command used in directional comparison or in
permissive tripping schemes with overreaching first zone can be
allocated to one or more outputs on the Relay Interface G3LR. Note
that “unblocking” commands are not transmitted from the remote end,
but automatically produced by certain types of line faults (PLC
channels).
Should the communication channel be almost completely lost, i.e.
when the NSD570 is receiving neither guard nor tripping signals and
the unblocking threshold is exceeded, the unblocking contacts close
for a predefined time. After detection of the unblocking condition the
release of this pulse can be delayed (filtered) for a certain time whilst
the channel may recover.
The internal signal evaluation time to detect the unblocking condition is
typical less than the nominal command transmission time.
For the NSD570 Analog, further to the unblocking condition “no guard
and no trip signals being received”, the total signal level in the chosen
bandwidth must be below a configurable threshold (compared to the
guard signal level) before an unblocking impulse is generated. The
unblocking threshold for the analog version can be configured in the
range of -20 … -10 dB below the nominal guard signal level.
For the NSD570 Digital, further to the unblocking condition “no guard
and no trip signals being received”, LOS (Loss Of Signal) or AIS
(Alarm Indication Signal) or invalid frames must be received before an
unblocking impulse is generated.
For the NSD570 Ethernet either two consecutive guard packets must
get lost or LOS (Loss Of Signal) must be received before an
unblocking impulse is generated. Note that the Unblocking condition
detection time is directly depending on the configurable Guard Packet
Sending Interval, e.g. for a Guard Packet Sending Interval of 5 ms the
Unblocking condition detection time is approximately 10 ms.
The unblocking extra delay is configurable by means of the HMI570 in
the range of 0 ... 100 ms in steps of 1 ms.
The unblocking pulse duration is configurable by means of the HMI570
in the range of 50 … 500 ms in steps of 1 ms.
3.5.12.3. Maximum Tx Input Monitoring

For each command maximum Tx input duration monitoring can be
programmed to OFF or a particular duration, i.e. the transmission of
persistent commands can be disabled.

The duration of each single command injected at the relay interface

inputs is individually monitored if the Tx Input Duration alarm is
enabled for this command.
Alarm is given and – if no persistent command is injected
simultaneously - the guard signal is transmitted instead of the tripping
signal should the command duration exceed the predefined value.
Also the boost criterion of the NSD570 analog is set inactive before the
guard signal is transmitted again.
The Maximum Tx Input Duration can be configured in the range of 3 …
60 seconds in steps of 1 sec by means of the HMI570.
Note: The cyclic or manual loop test of NSD570 Analog is

not available during persistent command trans-
mission!
The cyclic or manual loop test of NSD570 Digital and
NSD570 Ethernet is always available, irrespective of
persistent command transmission.
3.5.12.4. Tx Input On-Delay

Warning:
If an input on-delay is configured, it has a direct influence on the
transmission time of the equipment. It is delayed correspondingly and
thus means an artificial deterioration of the equipment performance
regarding command transfer delay. Normally the receiver at the
remote station decides whether it was a genuine command of
adequate length or only a transient spark on a command input.
Therefore, the command inputs are not delayed by default. If there is a
request for some special applications (e.g. direct tripping when using
digital communication systems) a “pick up time” for the command
inputs can be configured. A command is transmitted only after the
corresponding command input was activated for the preset delay time.
The command sending duration is then prolonged by the same time.
Tx Input On-Delay
Command at G3LR input
Trip signal to remote
3-Tx_Input_On-Delay.vsd
Fig. 3-33 Tx Input On-Delay

The preset input command delay can be configured for each command
separately.
The Tx Input On-Delay is configurable by means of the HMI570 and
can be set in the range of 0 … 10 ms in steps of 1 ms.
3.5.12.5. Transparent Tx Input and Rx Output Duration

An enabled Transparent Tx Input or Rx Output Duration assures that a
tripping signal or a command output is active as long as the command
is injected at the command input or the tripping signal is received.
A command injected or received passes transparently, without any
alteration.
Transparent Tx input and Rx output duration can be programmed for
each command and each direction (Tx or Rx) separately.
When transparent command duration is selected, limited, fixed and
prolonged command duration is not applicable.
3.5.12.6. Prolonged Tx Input and Rx Output Duration

A Tx input or Rx output prolongation ensures a steady tripping signal
transmission or command output release even in the event of
discontinuations of the signal being received.
The NSD570 receiver compensates the time needed for evaluating the
tripping signals, i.e. the command duration at the output has almost
the same pulse width as the transmitted command at the remote
station (if no prolongation time is configured).
Prolonged Tx Input Duration
3-Prolonged_Tx_Input_Duration.vsd
Fig. 3-34 Prolonged Tx Input Duration
Warning:
With a Prolonged Tx Input Duration of 0 ms, the receiver at the remote
station decides whether a received command of adequate length was
genuine or only a transient spark on a command input. However, with
a Prolonged Tx Input Duration > 0 ms, even a short command e.g.
produced by such a spark is extended in length such that the receiver
may interpret it as a genuine command.

A Tx input and Rx output prolongation can be programmed for each

command and each direction (Tx or Rx) separately.
The Prolonged Tx Input and Rx Output Duration is configurable in the
range of 0 … 3000 ms in steps of 1 ms by means of the HMI570.
Default setting of the Prolonged Tx Input Duration is 0 ms.
Default settings of the Prolonged Rx Output Duration for the command
application are:
• Blocking 0 ms
• Permissive Tripping 10 ms
• Direct Tripping 100 ms
When prolonged command duration is selected, transparent, limited
and fixed command duration is not applicable.
3.5.12.7. Limited Tx Input and Rx Output Duration

An enabled Limited Tx Input or Rx Output Duration assures that a
tripping signal or a command output is active for the preset time at the
most.
A command injected or received shorter than the configured Limited
Tx Input or Rx Output Duration passes transparently, without any
alteration.
When a command is injected longer, the tripping signal is transmitted
to the remote equipment with the configured Limited Tx Input Duration
only. When a tripping signal is received longer, the command output is
released with the configured Limited Rx Output Duration only.
If a command is shortly interrupted within the configured Limited Tx
Input or Rx Output Duration, more than one command can be sent to
the remote station or released at the command output.
Limited Tx Input Duration
3-Limited_Tx_Input_Duration.vsd
Fig. 3-35 Limited Tx Input Duration
A Tx input and Rx output duration limitation can be programmed for

each command and each direction (Tx or Rx) separately.

The Limited Tx Input and Rx Output Duration is configurable in the

The default setting is 100 ms.
When limited command duration is selected, transparent, fixed and
3.5.12.8. Fixed Tx Input and Rx Output Duration

An enabled Fixed Tx Input or Rx Output Duration assures that a
tripping signal or a command output is active for a preset and constant
duration, independent of the injected command’s length or received
tripping signal’s length.
A command injected or tripping signal received shorter than the
configured time is prolonged to the Fixed Tx Input or Rx Output
duration, whereas a longer command or tripping signal is stopped after
the elapsed time.
If a command is shortly interrupted at the input while the tripping signal
is sent for the fixed duration, it is regarded as one command only.
Accordingly, a shortly interrupted tripping signal during release of a
command output is regarded as one command only.
Fixed Tx Input Duration
3-Fixed_Tx_Input_Duration.vsd
Fig. 3-36 Fixed Tx Input Duration
A Fixed Tx Input and Rx Output Duration can be programmed for each

command and each direction (Tx or Rx) separately.
The Fixed Tx Input and Rx Output Duration is configurable in the
The default setting is 100 ms.
When fixed command duration is selected, transparent, limited and

3.5.12.9. Command acknowledge

A Tx command acknowledge is programmable for each command.
The Tx command injected is then looped back from the line interface
(G3LA, G3LD or G3LE) to one of the various outputs on the relay
interface type G3LR, to acknowledge that the corresponding command
was sent. This is, however, no confirmation that the command has
been received by the opposite station.
A “Tx command summary acknowledge” can be signaled on one of the
outputs of the relay interfaces for acknowledging when any command
has been sent.
A “Rx command summary acknowledge” can be signaled on one of
the outputs of the relay interfaces for acknowledging when any
command is received.
A “Tx or RX command summary acknowledge” can be signaled on one
of the outputs of the relay interfaces for acknowledging when any
command has been sent or received.
The operating time of the acknowledge outputs is as long as the
commands are sent or received, i.e. the Tx input command delay and
the Rx command prolongation are also considered.
3.5.12.10. Rx Guard
The state of the NSD570 guard receiver can be signaled by the line
interface to one of the various outputs on the relay interface type
G3LR. Reception of the NSD570 guard with adequate signal quality
means that the corresponding solid-state output is closed or the coil of
the selected relay contact is energized.
The configured output reflects the guard receiver state without any
additional pick-up or hold delays.

3.5.13. Functions of the analog system
3.5.13.1. Transmit level setting / Transmit level monitoring

The transmit (Tx) signal level can be set in the wide range of -24 dBm
to +2 dBm in steps of 1 dBm by means of the HMI570. This setting is
valid for the single tone guard signal. Including power boosting (refer
to Section 3.5.8.3 “Programming of the Ethernet system”) the
maximum output level for a single tone command signal is therefore
+11 dBm and +8 dBm (RMS) for a dual tone command signal.
The transmit (Tx) alarm threshold can be configured from -10 dB to
-3 dB in steps of 1 dB by means of the HMI570. From this follows that
the Tx level must drop off from nominal by the configured value before
alarm is given.
3.5.13.2. Receive level setting / Receive level monitoring

The receive (Rx) signal level can be set in the wide range of -30 dBm
to +2 dBm in steps of 1 dBm by means of the HMI570. This setting is
valid for the single tone guard signal. Including power boosting the
maximum input level for a single tone command signal is therefore
+11 dBm and +8 dBm (RMS) for a dual tone command signal.
Since the dynamic range of the receiver is 15 dB from nominal, the
overall input level range is in fact from -45 dBm to +17 dBm!
The receive (Rx) alarm threshold can be configured for a lower / upper
limit from ±3 dB to ±12 dB in steps of 1 dB by means of the HMI570.
This means that the Rx level must drop off or rise from nominal by the
configured value before alarm is given.
3.5.13.3. Boosting / Boost Output

In the case of NSD570 Analog, the tripping signal can be boosted and
be transmitted at a higher power in relation to the guard signal. The
ratio between the boosted tripping signal and the guard signal is
referred to as boost ratio and is expressed in dB.
The power boosting is selectable via HMI570 in the range of 0 dB to
9 dB and in steps of 1 dB.
When transmitting a test signal, the boost signal will not be set active
and the test signal will not be boosted.
As long as any command is transmitted, the boost output on the
Analog Interface G3LA is operated (refer to Section 3.4.2.7 “How to
use the Display Panel G1LC”).

3.5.13.4. Embedded Operation Channel (EOC)

By means of the EOC the configuration and monitoring of the remote
equipment in a link is possible from the local terminal.
The EOC needs no additional bandwidth, as it is operated in the guard
channel and therefore switched off during command transmission.
Note: The EOC of NSD570 Analog is not available during

persistent command transmission!
The EOC is shortly interrupted by the manual or cyclic
loop test!
There is a limited functionality of the EOC when the equipment is in

T-operation mode (refer to Section 3.6.7.1 “NSD570
Analog/Digital/Ethernet in “normal” T-operation” and 3.6.7.2 “NSD570
Analog/Digital/Ethernet in “inverse” T-operation”, i.e. only end-to-end
operation for configurations with T-offs).
All HMI570 functions are supported also for the remote equipment,
connected via the EOC, except for the following features:
• activating the local and remote test mode in the remote station
• switch back to previous configuration
• change the micro-controller’s UART baud rate
In principle, the “Firmware download” via the EOC is working as well,
but due to the low transmission rate it would take a couple of hours to
download a new version via the EOC. It is therefore strongly
recommended to switch off the cyclic loop test during a firmware
download via EOC!
The following transmission rates will arise:
• channel bandwidth 120 / 240 / 360 Hz 20 bps
• channel bandwidth 480 6 / 960 Hz T T 50 bps
• channel bandwidth 1200 / 2400 / 2800 Hz 100 bps
On the other hand, the immunity of the EOC against interference and
noise is very high. It operates down to a SNR of 6 dB.
Note: The Signal to Noise Ratio (SNR) and the Tx/Rx level
measurement displayed by the HMI570 do only have
an adequate accuracy if the EOC is switched off!
6
T T In 480 Hz channel bandwidth and with operating mode “4 independent
dual tone commands A, B, C, D” -> 20 bps only.
All other modes -> 50 bps.

3.5.14. Functions of the digital system
3.5.14.1. Bit error rate monitoring

The BER is determined in 200 seconds (short term average) and in
262 minutes (long term average). The actual values can be seen by
uploading the status of NSD570 Digital by means of the HMI570.
If the bit error rate (BER) reaches a pre-defined threshold, alarm is
given, and dependent actions are taken (e.g. the command outputs will
go to the quiescent state if configured).
3.5.14.2. Addressing
Provision is made by means of HMI570 for individually addressing
NSD570 teleprotection devices. The data transmitted from station A
can only generate a tripping command in station B, if station B's
address is contained in the incoming signal. The address and the local
alarm signals are transmitted to the remote station where they are
continuously evaluated. This coded information is contained in both
trip and guard messages. The time taken to recognize an address lies
within the time taken to detect a tripping message. This can prevent
false tripping, if for example channels of the data circuit-terminating
equipment are switched during the transmission of a continuous
command and the command signal is relayed to another station.
The command outputs are switched to their programmed alarm states
should a wrong address be detected (after the configured link alarm
pick-up time, refer to Section 5.5.2 “Status of the command outputs
during a link failure”). This can also occur should addresses be
corrupted by bit errors. The following programming is therefore
recommended for the alarm states of the command outputs:
- in applications with continuous commands, the outputs should be
programmed to retain the states they had prior to the alarm
(“frozen”) to avoid unwanted interruptions of commands.
- for short time tripping commands, the outputs should be
programmed to adopt their quiescent states (guard state = blocked).
The equipment ignores any incoming signal (Guard / Trip) if an
address error is detected. The LEDs on the front plate indicate the
corresponding state (alarm LEDs Receive/Local light up). The event
recorder and the internal trip counters can only record a command
during address error, if the programming of the command output states
for the event of an alarm permits the command to be transferred to the
relay interfaces. In any case an address error alarm is added to the
event recorder list.

The usable range of the digital address is from 0 … 1023 (not to be

mixed up with the device address needed to connect the device by
means of the HMI570!).
The addressing facility is configurable via HMI570 to be switched ON
or OFF.

equipment in a link is possible from the local terminal.
The EOC needs no additional bandwidth, as it is operated within the
used data stream. Since there are specific bits reserved for the EOC in
the digital frame structure, it is not switched off during command
transmission.
Note: Contrary to NSD570 Analog and in accordance with

NSD570 Ethernet, the EOC of NSD570 Digital is
available during persistent command transmission!
There is a limited functionality of the EOC when the equipment is in

T-operation mode (refer to Section 3.6.7.1 “NSD570
Analog/Digital/Ethernet in “normal” T-operation” and 3.6.7.2 “NSD570
Analog/Digital/Ethernet in “inverse” T-operation”, i.e. only end-to-end
operation for configurations with T-off).
All HMI functions are supported also for the remote equipment,
connected via the EOC, except the following features:
• change the micro-controller’s UART baud rate
The “Firmware download” via the EOC is working as well, due to the
relatively high transmission rate it would take approx. one hour to
download a new version via the EOC.
The following transmission rate will arise:
• channel data rate 56 kbps 1000 bps
• channel data rate 64 kbps 1333 bps
On the other hand, the immunity of the EOC against bit errors is not
too high. It operates up to a BER of 1E-05 without increased response
time for HMI requests.

3.5.15. Functions of the Ethernet system
3.5.15.1. Transmission Time and Packet Loss monitoring

As described in Section 3.5.8.1 “Channel supervision” the NSD570
Ethernet continuously monitors the channel and measures
Transmission Time and Packet Loss Rate.
If these values exceed user adjustable limits, the NSD570 Ethernet
generates corresponding alarms in order to indicate poor channel
quality. The Transmission Time - TT in Fig. 3-30 - is continuously
measured. Alarm is generated if several TT test packets are not
received within a given time limit. The number of considered TT test
packets depends on the configured Warning/Alarm Sensitivity
threshold. Please note that before the alarm, a warning might be
raised in order to signal a degradation of the channel quality. If the
channel quality becomes even worse, the Transmission Time alarm is
raised.
Transmission Time Warning/Alarm Sensitivity can be set to Low,
Medium and High. Basis for warning and alarm is the supervision of m
packets within a sliding window where n out of m packets must not be
received within the expected time. The reception of the reflected signal
must take place before 6 x T0 (T0 = nominal transmission time) after
sending it, i.e. 3 x T0 for one direction.
Additional propagation delay of the communication channel (e.g.
switches, routers) can be taken into account with the parameter
“Propagation Time” by means of corresponding HMI570 setting (refer
to Section 4.10.5.3 “Edit Configuration”). Twice the configured
propagation time will then be added to the threshold.
In order to set the correct Propagation Time, the delay of the link must
be found out, e.g. by pinging the remote equipment and determining
the minimum delay for an unloaded network.
The following table shows the values for n and m for Warning and
Alarm depending on the chosen Sensitivity Level:
Transmission Time Warning / Low Medium High

Alarm Sensitivity
n=3 n=2 n=1
Warning
m = 10 m=5 m=3
n=5 n=3 n=2
Alarm
m = 10 m=5 m=3
Please note that the sensitivity levels – low, medium, high – are valid
for both, Alarm and Warning, i.e. there is no independent setting of
Alarm and Warning Sensitivity possible.

The Packet Loss Rate is continuously monitored if the equipment

receives packets in the Guard Packet Sending Interval (guard or
tripping packets). When the measured Packet Loss Rate exceeds the
user adjustable threshold, an alarm is raised. This value can be set by
means of the User Interface Program HMI570, for details refer to
Section 4.10.5.3 “Edit Configuration”.
3.5.15.2. Security functions

Several measures are taken to ensure that received commands are
coming from an authenticated source i.e. another NSD570 Ethernet
and thus the attack potentiality from external sources is nonsignificant.
The IP address of a source must comply with the remote address that
can be set by means of the User Interface Program HMI570 (for
details refer to Section 4.10.5.3 “Edit Configuration”). Only correct IP
address pairs will establish a successful connection between two
G3LE.
In order to ensure packet reception from a secure source, the NSD570
Ethernet protocol contains a node address which is unique. Only
packets from this source are being accepted from the receiver.
For measuring purposes and to avoid replay attacks, the protocol
contains a sequence number which must be in very narrow limits to be
accepted as valid by the receiving NSD570 Ethernet.
The entire protocol payload (APDU) is protected by an SHA-256 keyed
hash code which is being re-calculated at the receiving NSD570
Ethernet and compared to the one contained in the payload of the
received packet. The key necessary to calculate the hash is
downloaded to the NSD570 Ethernet by means of the HMI570 while
commissioning, where it must be typed in by the user (for details refer
to Section 4.10.8.7 “Set WAN Password (NSD570 Ethernet WAN
Interface only)”). It must always be the same one at both sides i.e.
local and remote NSD570 Ethernet must contain the same key.
The User Interface Program HMI570 forces some key complexity i.e.
the key must have a certain minimum length and must at least contain
alpha-numerical, numerical and special characters. At delivery, the
NSD570 Ethernet is equipped with a default key, to make the interface
operational immediately. However, there is a warning indicating the
default key is being used. In this context it is recommended to
• change the default key to a user defined key immediately
• change the key in certain intervals e.g. annually or more frequently


equipment in a link is possible from the local terminal. The EOC is
operated via a second UDP transmission channel which can be
configured by means of the User Interface Program HMI570 (for
details refer to Section 4.10.5.3 “Edit Configuration”).
Thus, the EOC data exchange in NSD570 Ethernet is very fast, even
transfers of some megabyte are done within seconds.
Note: Contrary to NSD570 Analog and in accordance with

NSD570 Digital, the EOC of NSD570 Ethernet is
All HMI functions are supported also for the remote equipment
connected via the EOC except the following features:
• change the UART baud rate
3.5.16. Event Recorder
3.5.16.1. General
The event recorder registers special events of the NSD570 system,
provides them with an accurate time stamp and stores the information
sequentially into a non-volatile memory. The resolution of the events
which can be discriminated between is 1 ms.
There are three different types of NSD570 events: the command
events, the alarm events and the manipulation events.
The maximum number of events that can be stored is 7500. If more
than 7500 events occur, the eldest events are deleted and the newest
events are preserved.
The timing information for the event recorder is provided by the real
time clock (RTC) on the line interfaces type G3LA, G3LD and G3LE.
The date and time are set via the User Interface HMI570 (refer to
Section 4).
If the accuracy of the RTC is not sufficient, an external clock can be
used (see Section 3.5.16.5 “RTC synchronization from an external
clock”).
The events are displayed by means of the HMI570 in a text-based
view.

Refer to Section 4 “User interface program” for instructions to upload,

view and save events.
3.5.16.2. Command events

The event recorder acquires the timing information of all commands
which are sent and received via the inputs and outputs of the Relay
Interfaces type G3LR and the GOOSE LAN Interface G3LS.
The following events are recorded as NSD570 command events:
• Start time and end time of all commands as they were injected at
the Relay Interface inputs (excluding Tx input on-delay and
Prolonged, Limited or Fixed input duration, if configured; i.e.
the duration of the sent tripping signal may differ from the duration
of the injected command).
• Start time and end time of all commands as they were released at
the Relay Interface outputs (including Prolonged, Limited or
Fixed output duration, if configured; i.e. the duration of the
received tripping signal may differ from the duration of the released
command).
• Start and end time of an unblocking pulse.
3.5.16.3. Alarm events

The event recorder acquires the alarms as they appear on the system,
i.e. pick up and hold times of the alarm relays are not included.
The following events are recorded as alarm events:
• Start time and end time of all NSD570 low level alarms (refer to
Section 9 “Troubleshooting” for details).
3.5.16.4. Manipulation events

The following events are recorded as manipulation events:
• Time when a loop test was sent
• Time when a loop test was reflected (not applicable for G3LE)
• Time when a loop test was received (only applicable for G3LE)
• Time when a loop test failed
• Time when a manual loop test was initiated (by means of the loop
test button on the front plate)
• Time when the configuration was downloaded
• Time when switched back to the previous configuration
• Time when a firmware version was downloaded
• Time when a new date and time was set

• Time when the equipment started up

• Time when a command counter was set to zero
• Time when the event recorder was erased
• Time when a manual reset was conducted
• Time when an automatic reset was conducted
• Time when a 1+1 switching criteria was detected and the respective
line interface was set to active or inactive
3.5.16.5. RTC synchronization from an external clock

An external clock source can be supplied to increase the accuracy of
the NSD570 system time. The clock signal has to be provided in the
IRIG-B format at TTL compliant level and it has to be connected to
the supply backplane type G1LB (refer to Section 6 “Installation and
wiring”).
The IRIG-B format only informs about the time and the number of days
having passed in the current year, but not about the number of the
year. Therefore, the date and time have to be set once manually in the
NSD570 to supply the system with information about the current year.
See Section 4 “User interface program” for the procedure about how to
set the date and time.
Alternatively, the RTC can be synchronized using an external sync
pulse only (every second – 1 PPS).
3.5.17. Counters
All transmitted and received NSD570 commands, all transmitted and
received loop tests and the number of unblocking pulses are counted
individually by separate counters. The counters will overflow after >216 P P
= 65536 events. They are stored in non-volatile memory.

Each single counter can be selectively set to zero or all counters at
once by means of the HMI570.
Refer to Section 4 for instructions to upload and reset command, loop
test and unblocking counters.
Two specific counters can be viewed after uploading the status from
an NSD570 device (link Device Information in the Edit
Configuration menu of the HMI570):
• Firmware Download Counter
• Configuration Download Counter
These counters cannot be set to zero.

3.5.18. Test facilities for the Line Interfaces
3.5.18.1. Testing during normal operation

An automatic loop testing routine cyclically checks the teleprotection
link. The test signal, which is transmitted in the same way as a
genuine command signal (except for boosting in case of the NSD570
Analog version), is recognized by the receiver and “reflected” back to
the transmit station. The test routine is terminated, provided that the
test signal arrives back at the transmitter within a certain time,
otherwise it is repeated and the NSD570 gives alarm should it fail
repeatedly.
The loop test can also be initiated manually at any of the stations by
pressing a button on the front plate of the equipment or via the
HMI570. The result of the test is indicated by the LEDs on the front
plate or on the display panel G1LC, if mounted.
There are also internal test routines that continuously monitor the
availability of the NSD570.
The testing facilities impair in no way the ability of the equipment to
respond to a protection command, i.e. a genuine tripping command is
always given priority over all tests.
An NSD570 unit can also interrogate the status of the remote unit and
give alarm if necessary. Information regarding the nature of the
problem is contained in the signal received (via EOC).
A serial interface is provided on the front of the unit for service and
diagnostic purposes. With the aid of a PC/notebook and the HMI570
the following is available: details of equipment settings, firmware
version, operating parameters and alarm signals generated by the
local and remote units.
3.5.18.2. Cyclic Loop Test
Note: The following description of the cyclic loop test is valid

for NSD570 Analog and NSD570 Digital only.
NSD570 Ethernet is monitoring the transmission time
more frequently by means of a loop test signal (every
second per default, also refer to Section 3.5.15.1
“Transmission Time and Packet Loss monitoring”).
But the results of these measurements are only
registered in the event recorder at the time interval of
x hour as configured for the cyclic loop test (see
below).

A cyclic loop test sequentially checks the integrity of the teleprotection

link. The test signal simulates the transmission of a genuine tripping
signal and is recognized as such at the receiving end, from where it is
echoed back to the transmitter. The test is deemed successfully,
providing the transmitter receives the echo. If it does not, the test is
repeated and alarm is given should the results of three subsequent
trials be negative.
The first cyclic loop test is sent 10 minutes after power-on the
equipment.
If the cyclic loop test is not turned off by the HMI570, a test signal with
its own test frequency or test code is transmitted to the remote station
and reflected back once every 1/3/6/12/24 hours, depending on the
programming (default setting: 6 hour interval).
The test signal is processed in the same way as a normal tripping
signal (interruption of the guard signal and transmission of a test
frequency or test message for 3 x T0 (T0 = nominal transmission time;
refer to Section 5.13.2.1 “Nominal transmission time”); the reception of
the reflected signal must take place before 6 x T0 after sending it),
which ensures that all the functions required for transmitting a tripping
signal are fully tested.
Additional propagation delay of the communication channel (e.g. radio
link, multiplexer) can be taken into account with the parameter
“Propagation Time” by means of corresponding HMI570 setting (defer
to Section 5.5.3 “Link Propagation Time”).
If an automatically initiated test is not received correctly it is being
repeated at intervals of about 5 minutes until the remote station
answers. A loop test alarm is given after the third unsuccessful
attempt. The alarm is immediately removed and the interval is set back
to the programmed value (e.g. 6 hours) after the loop test signal is
received again from the remote station.
The testing facilities impair in no way the ability of the equipment to
respond to a protection command, i.e. a genuine tripping command is
always given priority over all tests.
Note: The cyclic loop test of NSD570 Analog is not

The cyclic loop test of NSD570 Digital is always
available, irrespective of persistent command
transmission.
The loop test signal is always transmitted and evaluated in the same
way as the command configured for the highest security requirements.

Note: The NSD570 Analog loop test is performed at the

nominal command signal level and is not boosted.
The loop test is thus performed under more exact
conditions than those of boosted transfer tripping
signals.
3.5.18.3. Manual Loop Test
Note: The following description of the manual loop test is

valid for NSD570 Analog and NSD570 Digital only.
NSD570 Ethernet is monitoring the transmission time
more frequently by means of a loop test signal (every
second per default, also refer to Section 3.5.15.1
“Transmission Time and Packet Loss monitoring”).
When the loop test is initiated manually, the result of
the last measurement is displayed in the HMI570
window or on the display Panel G1LC.
The loop test can also be initiated manually from any station via the
HMI570 or via the button on the local front plate. The result of the test
can be viewed in the HMI570 window or on the Display Panel G1LC, if
mounted. The actual measured transmission time (Tac) is displayed
(half the value of both directions there and back). A delay of 1 ms is
added to the displayed value, representing one input and one output
circuit of a relay interface type G3LR (which can not be included in this
test; the same applies for the input/output circuits and the processing
time of GOOSE messages if G3LS is used).
Note: The measured actual transmission time by means of

the loop test does not include a configured input pick-
up delay for the commands.
The loop test signal is always transmitted and evaluated in the same
way as the command configured for the highest security requirements.
If the reflection of a manually transmitted test signal is not received
correctly, this is displayed in the loop test window.
A manually initiated loop test is transmitted in the same way as the
cyclic loop test.
Note: The manual loop test of NSD570 Analog is not

The manual loop test of NSD570 Digital is always
available, irrespective of persistent command
transmission.

3.5.18.4. Local Test Mode

The NSD570 can be set via HMI570 to a local test mode for checking
the relay interfaces, e.g. for measuring the command prolongation.
In this operating mode, which is indicated by a flashing “Ok / Fail” LED
and via the HMI570 by the alarm message “LOCAL TEST MODE
ACTIVE”, the command input signal is looped via the line interface
back to the corresponding command output of the local Relay Interface
type G3LR or G3LS.
Note: The trip counters will count the local commands as

well.
During the test mode the guard signal is continuously transmitted to
the opposite station.
Caution Genuine commands cannot be transmitted between

the stations when the equipment is in the local test
mode.
3.5.18.5. Remote Test Mode

The NSD570 can be set via HMI570 to a remote operating mode for
checking the transmission channel, e.g. transmission time
measurements without external looping of the commands in the
remote station.
Before starting the test, the local system must be isolated from the
protection circuits. The remote system's command outputs are
blocked; all commands are sent back as long as they are received.
in the remote station and via the HMI570 by the alarm message
“REMOTE TEST MODE ACTIVE” (the local station indicates a
“Remote Alarm”), the command input signal is looped via the remote
line interface back to the corresponding command output of the local
relay interface type G3LR or G3LS.
Note: The local and remote trip counters will count the
sent/received commands as well.
Caution Genuine commands cannot be transmitted between

the stations when the equipment is in the remote
test mode.

Caution The remote test mode must only be used for

commissioning point-to-point teleprotection links (not
applicable for T-operation; i.e. the two NSD570 links
in a T-off arrangement have to be commissioned by
means of the remote test mode as normal link first).
3.5.19. Test facilities for the GOOSE LAN Interface
3.5.19.1. Overview
The module G3LS supports the transmission of test commands
according to IEC 61850-7. This feature must be enabled separately,
on both sides of a teleprotection link. Test commands issued by a
protection relay are then transmitted transparently and evaluated from
the protection relay on the other side. Test commands do not activate
circuit breakers.
Substation A Substation B
Communication
VLAN RTB RTB VLAN
channel
GOOSE GOOSE
Protection Interface Line Interface Line Interface Interface Protection
Relay G3LS G3LA/D/E G3LA/D/E G3LS Relay
(Sender) (Receiver)
Fig. 3-37 Example G3LS commissioning
If the protection relay in substation A sends a trip with quality attribute

“test” flag enabled, G3LS considers the quality to be “invalid” in normal
operation mode and refuses to transmit this trip. The reason is that
G3LS command attribute depth is limited to one bit, being either
“good” or “invalid”.
Activating the G3LS commissioning function “test command
acceptance” configures the G3LS device to interpret the test flag of the
quality parameter as “true”.
G3LS in substation B with activated commissioning function “test
command transmission” forwards a command received from the line
interface with the test flag of the quality parameter set to the protection
relay in substation B.
3.5.19.2. Test command acceptance

G3LS can be set via HMI570 to “test command acceptance” for
supporting the attached protection relays with test command
transmission.


and via the HMI570 by the alarm message “TEST COMMAND
ACCEPTANCE ACTIVE”, the commands received from the protection
relay are forwarded to the line interface although the quality contains
an enabled test flag.
Caution A G3LS running in “Test command acceptance”

mode forwards test commands as real commands,
capable of activating circuit breakers. Therefore,
never activate “Test command acceptance” without
activating “Test command transmission” on the other
side of the link.
3.5.19.3. Test command transmission

G3LS can run in “test command transmission” mode if enabled in the
HMI570.
and via the HMI570 by the alarm message “TEST COMMAND
TRANSMISSION ACTIVE”, commands received from the line interface
are forwarded with an enabled test flag in the quality parameter to the
protection relay.
Caution A G3LS configured to run in “Test command

transmission” mode forwards commands with quality
marked as “test”. This means every command will
be discarded by the protection relay.
3.6. NSD570 Applications

Power system faults taking place at specific points in the power
system are isolated by operation of the associated protection and
circuit-breakers. About 85 percent of all faults at the higher voltage
levels occur on overhead lines and are single phase to earth faults of a
temporary nature, e.g. caused by lightning. Provided that fast fault
clearance is achieved, they do not spread to other conductors and
usually do not result in permanent damage; the fault path is rapidly de-
ionized after isolation and the circuit can then be successfully re-
closed.
Faults due to deterioration of solid or liquid or gas insulation are
generally permanent and, because of the energy containment, there is
a risk of explosion and fire; reclosure is usually not possible, and there
is again a requirement for fast fault clearance.
Fast selective protection applied to cables and overhead lines requires
communication between the circuit ends. The NSD570 teleprotection

equipment is suitable for transmission of permissive tripping, direct

tripping and blocking commands via analog (audio-frequency) and
digital and fiber optic links; it is designed for duplex communication,
and some typical applications are described below.
3.6.1. Permissive tripping schemes

Permissive transfer tripping is used typically for the protection of
transmission lines. The transfer-tripping link between the protection
equipment at the ends of the line ensures that all faults can be cleared
in the time of the first zone along 100 % of the line.
In a permissive scheme, the transfer tripping signal from the NSD570
is connected in series with a local criterion (protection starting,
directional decision or phase selection) and tripping can only take
place at the receiving end, if a transfer tripping signal is being received
and the local Protection Relay detects a fault in the direction of the
protected line.
The reception of a spurious tripping signal caused by interference on
the communications channel cannot therefore give rise on its own to
unwanted tripping, but it may cause unwanted tripping under external
fault conditions when the protection is active and the fault is within the
reach of its starting elements (permissive underreaching) or within the
reach of the distance relay (permissive overreaching).
On the other hand, a delayed transfer-tripping signal may mean that a
fault on the line is tripped in zone 2 time instead of undelayed in
zone 1.
High dependability and a short transmission time therefore take priority
over high security in a permissive scheme.
Typical requirements are transmission times of less than 20 ms and
false command rates under worst-case interference conditions of less
than 1E-04 (overreaching schemes) respectively 1E-05 (under-
reaching schemes).
The following typical settings result:
Command application: permissive
Bandwidth analog: ≥ 480 Hz for single tone commands
≥ 960 Hz for dual tone commands
Relay interface output: solid state
Command prolongation: 20 ms, must sometimes be reduced to
10 ms or less in permissive
overreaching applications

3.6.1.1. Permissive underreaching transfer tripping (PUTT)

Stepped distance/time protection is used, with its high-speed zone 1
reach set to typically 85 percent of the protected circuit length. The
zone 1 relay is directional and does not operate for faults behind the
relay position; it initiates tripping of the local circuit-breaker, and
command transmission indicates that an internal fault within zone 1
reach is seen at the transmit end. The zone 1 reach must
accommodate practical measurement errors without risking unwanted
high-speed tripping for faults external to the protected circuit, while the
reaches of zone 2 and 3, with their necessary time lags, extend
beyond the protected circuit; their operation is associated with backup
protection of adjacent busbars and line sections.
For a fault on the protected circuit, one end, or the other, or both ends
will experience zone 1 relay operation, and the communication link
used is used to “accelerate” the protection in order to avoid delayed
zone 2 tripping for internal fault positions close to the circuit ends. The
command transmission time is much shorter than the zone 2 time
delay, and the tripping action of the received command is made
dependent on fault detecting devices, e.g. underimpedance,
undervoltage or overcurrent starting relays, to achieve single-phase or
three-phase tripping. Alternatively, the received command may be
used to extend the zone 1 relay reach to typically 130 percent of the
protected circuit length, or to bypass the time-lag of an independently
operating zone 2 relay.
Reception of a spurious tripping command, caused for instance by
switchgear noise influencing the communication channel, cannot on its
own result in unwanted tripping, and the use of local fault detecting
devices to control tripping action thus limits the risk of unwanted
tripping to conditions for which these devices operate in case of
external faults, e.g. to faults within the reach of an underimpedance
starting relay.
Failure of the communication link does not prevent correct operation of
the protection; selectivity is retained, but tripping is delayed at one
circuit end for certain fault positions. For this reason, the
communication link is sometimes described as a supplementary
feature in such applications.
Typical requirements in a PUTT scheme are:
• nominal transmission time less than one power-frequency cycle,
and typical permissible delay about one and a half cycle
• high dependability, because inadequate dependability may cause
delayed tripping on internal faults
• good security, because inadequate security may cause unwanted
tripping on external faults

3.6.1.2. Permissive overreaching transfer tripping (POTT)

This method also uses transmission of tripping commands under
internal fault conditions to obtain high-speed tripping with distance
protection. The directional zone 1 reach is set beyond the end of the
circuit, typically to 130 percent of the protected circuit length. The zone
1 relays then cannot be permitted to trip directly, and tripping at each
end is made dependent upon both operation of the local zone 1 relay
and reception of a tripping command from the far end. In other words,
tripping at each end depends on zone 1 relay operation at both ends,
and correct operation of both relays and correct functioning of the
communication link in both directions are necessary for complete
isolation of a faulted circuit. The communication link is thus an
essential feature in such applications, and both a high dependability
and a short command transmission time are required.
POTT is sometimes used as second protection in duplicated main
protection schemes, for distance protection of short lines where
accurate zone 1 reach setting is difficult due to arc voltage and ground
resistance, and for distance protection of longer overhead lines with
series capacitors. A POTT scheme is applicable only where there is
adequate feed of fault current at both ends of the protected circuit; if
the circuit-breaker at one end is open, a received command at this end
must be looped back to the other end to accomplish tripping on
internal faults. Reversal of fault current following partial clearance of
external faults, e.g. on parallel circuits, require consideration of
operating and resetting times of relays and teleprotection equipment.
The risk of unwanted tripping due to flashover or switchgear noise
influencing the communication link is limited to external fault positions
just beyond the ends of the protected circuit ends. Communication link
failure will cause delayed zone 2 tripping at one end of the circuit, or at
both ends.
Typical requirements in a POTT scheme are:
• nominal transmission time less than one power-frequency cycle,
and typical permissible delay about one and a half cycle
• high dependability, because inadequate dependability causes
delayed tripping on all internal faults
• good security, because inadequate security may cause unwanted
tripping on external faults
3.6.2. Blocking schemes

These types of protection differ fundamentally from tripping schemes
where “inward” fault current flow initiates a command to trip. The
operating principle of blocking schemes is detection of “outward” fault
current flow at one end of a protected circuit when the fault is external

to it. Such detection initiates transmission of a blocking command

which inhibits the tripping action at the other end where the fault
current flow is “inward”. In case of external faults, either end may thus
block the other, while no commands are transmitted in case of internal
faults.
Directional current relays or high-speed distance relays with zone 1
reach set beyond the far circuit end may be used as “inward” fault
current detectors, and the devices detecting “outward” fault current are
usually directional impedance or directional current relays.
Alternatively, command transmission may be initiated by a non-
directional starting relay and interrupted by the zone 1 relay; one end
or the other will then transmit a blocking command on external faults,
and the blocking commands are only interrupted at both ends in case
of internal faults.
Blocking schemes work correctly for all fault positions on the protected
circuit, even in case of a weak or missing in-feed or an open circuit-
breaker at one circuit end. Zone 1 extension may also be used in a
similar way as in a PUTT scheme; the zone 1 relay reach is then set to
cover about 85 percent of the circuit length and is switched to typically
130 percent after a short waiting time, unless a blocking command is
received. These zone 1 settings allow fast tripping at both circuit ends
for any fault position where their characteristics overlap.
In blocking schemes, communication link failure generally does not
affect the ability of the protection to trip correctly on internal faults;
command transmission is, however, essential for avoiding unwanted
tripping on external faults. Because of the importance of the
communication link, the teleprotection supervision facilities may be
arranged to switch the zone 1 relay settings from overreaching to
underreaching in the event of a communication link failure.
To obtain correct blocking action on external faults, the tripping action
of the Protection Relay at the end feeding “inward” fault current must
be delayed sufficiently to ensure that the “do not trip” command sent
from the end feeding “outward” fault current has arrived. This delay
must be kept to a minimum to ensure fast clearance of internal faults,
and a short command transmission time is therefore required.
The use of the communication link to convey blocking commands
avoids the risk of unwanted tripping due to interference and noise, e.g.
caused by circuit-breaker operation, unless this can prevent command
reception. Even a short interruption of genuine blocking commands
may cause spurious tripping, and a high dependability is therefore
required.
Impulsive interference and noise during internal faults, e.g. caused by
circuit-breaker operation, may delay tripping by simulating a blocking

signal; the duration of such delays is unlikely to exceed half a power

frequency cycle, so that only a moderate security is required.
Typical requirements in blocking schemes are:
• nominal transmission time about half a power-frequency cycle and
maximum permissible delay one cycle
• high dependability, because inadequate dependability may cause
unwanted tripping on external faults
• moderate security, because inadequate security may cause
delayed tripping on internal faults; delays shorter than half a power
frequency cycle are usually considered acceptable
Transmission times of less than 10 ms for a 50 Hz power system or

less than 8 ms for a 60 Hz power system are therefore required for
blocking. False command rates under worst-case interference
conditions should be less than 1E-03 or even less than 1E-04.
The following configuration and settings are recommended for a
blocking line protection scheme:
Command application: blocking
Relay interface output: solid state
Command prolongation: 0 ms
3.6.3. Unblocking
In the early days of power line carrier communication, blocking
schemes were often used for overhead line protection in conjunction
with single-purpose on/off (amplitude-shift type) carriers with common
transmit/receive (simplex) channels. No carrier signals were
transmitted under healthy line and “inward” fault current flow
conditions, and the Protection Relays initiated carrier transmission only
if “outward” fault current flow was detected. The carrier “off” condition
thus meant “permission to trip”, while a received carrier signal meant
“block” = “do not trip”.
Since blocking commands are transmitted under external fault
conditions only, i.e. over healthy line sections, cost-saving phase-to-
ground couplings were used, and since carrier transmission is not
required in case of internal faults, the actual line attenuation under
fault conditions is of no importance. Link testing under normal healthy
line conditions required the use of manual “carrier send” facilities, and
automatic link monitoring required “clock test” devices transmitting

carrier signals of short duration at regular time intervals, e.g. every 30

minutes.
PUTT or POTT schemes were also used together with single-purpose
on/off duplex carriers having separate transmit and receive channels.
Continuous carrier signals were transmitted during healthy line
conditions, and the Protection Relays interrupted the carrier
transmission only if “inward” fault current flow was detected. These
schemes avoided the use of “outward” fault current detecting devices,
and a received carrier signal again meant “block”, while a carrier “off”
condition meant “unblock” = “permission to trip”. Certain types of faults
would prevent carrier signal reception by bridging the circuit, thus
causing the carrier receivers to “automatically” output an “unblocking”
command without the aid of the protection at the remote line end.
The “unblock” output signal duration was limited to about 8 power-
frequency cycles to avoid unwanted tripping in the event of permanent
channel failure, cost-saving phase-to-ground couplings were again
used, and the normal continuous carrier transmission simplified link
monitoring.
Most modern power line carriers are multi-purpose duplex equipment
for speech plus data transmission and teleprotection, the latter usually
being of the frequency-shift type allowing channel monitoring by a
continuously transmitted guard signal, which is replaced by one or
more command signals during fault conditions. The standard
modulation method is single sideband suppressed carrier, and the
preferred coupling arrangement is phase-to-phase, which in normal
operation causes less interference with other circuits and provides
lower line attenuation than phase-to-ground coupling, and exhibits only
moderate additional attenuation under all phase-to-earth fault and
most phase-to-phase fault conditions.
Phase-to-phase faults and three-phase faults represent a severe
shock to a power system, in particular when they occur close to a
busbar, and fast fault clearance is then mandatory. Three-phase faults
and phase-to-phase faults involving the coupled phases close to one
line end cause high additional line attenuation, and teleprotection
receivers on power line carrier links may then be unable to decide if
the remote line end was transmitting a guard or a command signal.
However, a decision must be made from a protection point of view,
and analog NSD570 receivers therefore include a device which
outputs an “unblocking” signal of about 200 milliseconds duration if
neither a clean guard nor a valid command signal is received for a
specific pre-set time, typically one power-frequency cycle.
It is noted that “unblocking commands” are not transmitted at
Protection Relay request; they are “automatically” produced by certain

fault types. The received “unblocking” signal permits tripping and

should arrive at about the same time as the local Protection Relay
picks up; this ensures minimum fault clearing time, because relay pick
up time at the remote line end and command transmission time are not
involved.
NSD570 “unblocking” signals may be used to switch underreaching
zone 1 distance relays to overreaching in PUTT schemes, or to bypass
the time delay of independently operating zone 2 relays, but they are
used more often as fleeting “trip enable” signals in POTT schemes, to
assist the essential communication links under difficult internal line
fault conditions. The main problem with fast “unblocking” devices is to
avoid unwanted tripping on external faults.
“Unblocking” is not a protection scheme, but a standard “emergency”
feature included in all analog NSD570 receivers, whether they are
intended for power line carrier applications or not. It is also included in
all digital NSD570 receivers, where it indicates a complete loss of
signal or a poor signal quality, i.e. a bit error rate insufficient for reliable
command transmission.
Typical requirements in “unblocking” applications are:
• nominal “loss of receive signal” detection time about one power-
frequency cycle, and typical permissible detection delay about two
cycles
• high dependability, because inadequate immunity to fault arcing
noise may result in guard signal simulation and suppression of
“unblocking” output signal and thus cause delayed tripping on
internal faults
• good security, because inadequate immunity to circuit-breaker
noise may result in guard signal suppression and simulation of
“unblocking” output signal and thus cause unwanted tripping on
external faults
3.6.4. Earth fault protection

Earth faults have less effect on the power system stability than phase
faults, in particular if the fault current is limited, and it may be difficult
or even impossible to achieve correct distance relay operation under
earth fault conditions on overhead lines, due to a high resistance value
in the fault current path, e.g. in cases of mid-span faults, use of
wooden poles, high ground resistivity, or bush fire.
Such problems do not occur under phase-to-phase fault conditions,
and a power direction comparison system is often used for earth fault
protection together with a conventional stepped distance-time
protection for phase-to-phase faults. The directional power relays (zero
sequence and/or negative sequence) then detect all earth faults

outside the pick up range of the distance relays, which detect all
phase-to-phase and three-phase faults and all earth faults within their
pick up range. The overall protection scheme involves the use of a
communication link, and a common channel may be used in either a
permissive tripping or a blocking scheme to achieve fast fault
clearance both under earth fault and phase fault conditions.
However, since the earth fault protection cannot provide phase
information, it is sometimes preferred to use two separate command
channels to achieve fast fault clearance, either single-phase or three-
phase, under low-impedance fault conditions and delayed three-phase
tripping and re-closure lock out under high-impedance earth fault
conditions, e.g. caused by bush fire. The delayed tripping action of the
earth fault protection, about 10 power frequency cycles, avoids
interference with the fast tripping action of the distance protection.
3.6.5. Duplicated main protection

Two independently operating main protection systems are often used
on important circuits; the purpose is to improve the reliability of tripping
on internal faults. The overlapping characteristics of the two systems
duplicate the tripping function, and this permits failure of one protection
equipment or one communication link (and maintenance or repair work
on one system) without loss of tripping on internal faults.
One protection system may fail to trip under difficult or marginal fault
conditions, and the different capabilities of the systems are then used
to advantage. The types of protection and communication links and
their independent use influence both the improved overall
dependability (reliability of tripping on internal faults) and the reduced
security (increased risk of unwanted tripping on external faults).
The use of two main protection systems on important circuits is
justified in relation to the attainable availability and tripping reliability of
a single system. It is generally more economical to achieve the
improved reliability of tripping on internal faults by two systems than
designing one system to the higher reliability.
Some associated equipment (e.g. current and voltage transformers,
trip coils and power supplies) may also be duplicated, and triple
systems consisting of two protections using telecommunication
facilities and one stepped distance-time protection without
communication are sometimes used.
The NSD570 teleprotection equipment is particularly suited to
duplicated protection applications, because each unit can convey two
or more independent commands at the same time. The units are
preferably allocated to different transmission media, line protection
commands may be criss-crossed between NSD570s, and important

(direct transfer tripping) commands may be conveyed in parallel over

both communication links.
For economical reasons it is possible to operate two equal or also two
different line interfaces in one NSD570 rack sharing up to four relay
interfaces, whereas one line interface (preferably the one with the
shortest transmission time) is the main line interface and the other one
is the stand-by line interface. The selection between main and stand-
by channel is determined according to the current hardware and link
alarms of both line interfaces, thus supporting device and channel
redundancy.
R R
MP1 A A MP1
MP2 B B MP2
Route 1 (e.g. Cable,
BFP C PLC, Radio, PCM) C BFP
GSD/LS D NSD570 NSD570 D GSD/LS
A A
B Route 2 (e.g. Cable, B
PLC, Radio, PCM) C
C
D NSD570 D
NSD570
MP1: 1st main protection GSD: generator shut down BFP: breaker failure protection
MP2: 2nd main protection LS: load shedding + overvoltage protection
R: protection relay + shunt reactor protection
3-Single-line2.vsd
Fig. 3-38 Duplicated line protection and breaker-failure

protection of an important single circuit

R2 R1 R1 R2
MP1 Line 1 A A MP1 Line 1

MP2 Line 2 B B MP2 Line 2
Route 1 (e.g. Cable,
BFP Line 1 C PLC, Radio, PCM) C BFP Line 1
BFP Line 2 D NSD570 NSD570 D BFP Line 2
MP1 Line 2 A A MP1 Line 2

MP2 Line 1 B Route 2 (e.g. Cable, B MP2 Line 1
PLC, Radio, PCM) C
C
D NSD570 NSD570 D
MP1: 1st main protection R1/R2: protection relay BFP: breaker failure protection
MP2: 2nd main protection + overvoltage protection
+ shunt reactor protection
3-Dual-line2.vsd
Fig. 3-39 Duplicated line protection of a twin line, with breaker-failure

protection on each circuit
3.6.6. Direct transfer tripping

Most protective systems are intended to respond to faults within a
precise zone, generally bounded by circuit-breakers. Their basis
function is to decide whether a fault is external or internal and, in the
latter case, to trip the circuit-breakers and isolate the protected zone.
Provided that fault conditions are as expected and provided that the
equipment functions correctly, such protection systems are very
effective.
The selective protection of circuits or components of a power system is
concerned only with what happens in its protected zone and thus
excludes consideration of the behavior of the power system as a
whole. Protection systems should therefore also be able to respond to
faults over a considerable area of the power system, in particular to
provide for conditions of a failure to clear a fault by neighboring
selective protections, which may be due to a failure to trip by these
protections or by their associated circuit-breakers.
Protection of this type is usually called “back-up” protection, and at the
lower voltage levels the desired function may be obtained by time

delays. The times involved are typically 0.5 to 2 seconds, and the
possibility of experiencing such fault duration and subsequent tripping
of a number of circuit-breakers is out of the question at the higher
voltage levels in large heavily loaded power systems. It is therefore
necessary to employ telecommunication techniques to reduce the
operating time of back-up protections to a few power frequency cycles.
3.6.6.1. Line protection

Direct transfer tripping may be used in conjunction with underreaching
distance protection to initiate tripping at the remote line end when the
local Protection Relay picks up. This ensures a high degree of tripping
reliability for the protected line, because fast or delayed tripping is
achieved at both line ends, even if one relay picks up after a time-lag
or not at all, e.g. due to weak in-feed, saturation of current
transformers, high earth-fault impedance, or relay failure.
Direct transfer tripping is, however, rarely used for line protection,
because reception of a spurious command always results in unwanted
tripping. A longer command transmission time must then be allowed to
achieve a considerably better security than required in permissive
tripping applications, and direct transfer tripping is also hardly suitable
in conjunction with single-phase automatic re-closure, unless a phase-
segregated transmission (one command per phase) is used, because
phase selection is needed at the receive end.
3.6.6.2. Re-closure lock out

Automatic re-closure is widely used in various forms to avoid
permanent isolation of a circuit in case of temporary faults, which
represent a high proportion of faults on overhead lines. Faults must be
isolated for a short time, about 0.3 seconds, to de-ionize the fault path
before the circuit is re-energized; the overall time must be kept to a
minimum, and this requires fast coordinated tripping of the circuit-
breakers at the line ends.
High-speed tripping and fast automatic re-closure thus limit the
dissipation of energy at the fault, minimize the disturbance to the
power system and reduce interruption of supply to important loads.
A re-closure lock-out command must sometimes be transferred to a
remote line end after that a fault has been cleared. Since reception of
a spurious command does not result in unwanted tripping, the
dependability and security requirements pertaining to permissive
tripping then apply.

3.6.6.3. Breaker back-up protection

The purpose of breaker back-up protection, often called breaker failure
protection, is to initiate fast tripping of the circuit-breaker(s) adjacent to
a damaged circuit-breaker which, due to jamming or loss of air
pressure, has failed to clear a fault.
In case of a fault on a busbar and a jammed line circuit-breaker
connected to it, the busbar protection first tries to clear the fault by
three-phase tripping and re-closure lock out of all local circuit-breakers
feeding fault current to the busbar. Since the local line circuit-breaker
is stuck, fault current is still flowing, and the breaker back-up protection
must now isolate the fault by sending a direct tripping command to the
remote line end, requesting three-phase tripping and re-closure lock
out.
In case of a line fault and a jammed circuit-breaker at one line end, the
line protection first tries to clear the fault by single phase or three-
phase tripping at both line ends. Due to the jammed circuit-breaker,
fault current is still flowing, and the breaker back-up protection must
now isolate the fault by three-phase tripping and re-closure lock out of
all local circuit-breakers feeding fault current to the line. After thus
having cleared the fault, it sends a direct tripping command to the
remote line end, requesting re-closure lock out and three-phase
tripping (to also disconnect the two healthy phases, if the line fault was
single phase).
3.6.6.4. Shunt reactor protection

The current flow in a line’s shunt capacitance causes a voltage drop in
its series inductance and series resistance, which in turn leads to a
considerable voltage change at the receiving end from the no-load to
full-load current. This reduces the line’s current carrying capacity,
causes increased power losses and may result in stability problems;
the large inductance of the lines and transformers is in fact the main
cause of stability problems for longer lines.
The most common remedy is to provide shunt reactors at the
substations. The shunt reactors reduce the problems associated with
the line’s shunt capacitance by partly canceling out the power-
frequency shunt capacitive current, and for cost reasons they are
sometimes connected to the line without circuit-breakers. The line and
the reactors must then be protected together, and since it may not be
possible to provide adequate protection of the reactors by the relays at
the line ends, some problems arise from this requirement.
In case of a reactor fault, the fault current may be of limited or
negligible value, and it is usually necessary to distinguish between
reactor faults and line faults, because automatic re-closure is only

desirable for line faults. The use of a communication link overcomes

the problems when the reactor protection initiates three-phase tripping
and re-closure lock out of the local line circuit-breaker and at the same
time sends a direct tripping command to the remote line end,
requesting three-phase tripping and re-closure lock out.
Shunt reactor protection and breaker back-up protection may share a
common direct transfer tripping channel, because tripping commands
originate at the same location and terminate on the same remote
circuit-breaker.
3.6.6.5. Transformer protection

Transformers are sometimes connected to a line with circuit-breakers
only on the secondary lower voltage side. Transformer faults including
core insulation and interturn faults cannot be detected by the line
protection and require current differential protection in conjunction with
gas and oil actuated Buchholz relays.
When picking up, the transformer protection initiates tripping of the
secondary-side circuit-breaker and transmission of a direct tripping
command to the circuit-breaker(s) at the remote line end(s). High
dependability, fast transmission (less than 0.1 second) and high
security are required to avoid damage and unwanted tripping due to
interference and noise influencing the communication link.
In cases where the line is an important interconnection, automatic re-
closure may be required to follow tripping and disconnection of the
faulty transformer by a motor-operated isolator; this may require the
use of further communication facilities.
3.6.6.6. Power system instability

The complex interconnection of a number of generating centers by a
power transmission system constitutes a network which, even when
heavily loaded, is normally stable. When disturbed by some stimulus
such as a fault, the system may become unstable and, depending on
the type, location and duration of the fault, begin to oscillate; the
generating centers then swing beyond the stability limit and drop out of
step.
Power swing conditions cause interchange of three-phase currents,
amplitude-modulated at a frequency of typically 1 to 2 Hz, and present
serious problems to the continued operation of the power system.
When the generating centers are in anti-phase with each other, the
currents and voltages correspond to those which would occur with a
three-phase fault at the power system’s electrical center, and

protections based on directional relays or distance relays may operate

at some point of the system and cause uncontrolled tripping.
Such uncontrolled (and usually unwanted) tripping can be prevented
by providing out-of-step blocking features; this can be done without the
use of communication links and is therefore not dealt with here. It may,
however, be desirable to initiate controlled tripping at certain points to
sectionalize the power system and minimize the disturbance, and
facilitate the restoration of normal conditions.
These points do not necessarily coincide with those at which distance
protections would operate, and the use of special devices and
communication channels for transmission of direct transfer tripping
commands may be required.
3.6.6.7. Generator shutdown and load shedding

Two power systems, each basically self-contained, may be
interconnected by a number of synchronous tie lines, e.g. for the
purpose of interchanging surplus power. The loss of one tie line, e.g.
caused by clearing of a permanent fault and subsequent re-closure
lock out, may not produce tripping conditions on other ties; they may
then become overloaded and, if this occurs at a time of heavy system
load, the subsequent tripping of an overloaded tie line may produce
successive overloading and tripping of other interconnections and thus
result in a widespread disruption of the system.
Since the effects of overload are thermal, they can be considered in a
considerably longer time scale than faults, e.g. up to one minute
compared to a fraction of a second; they may, however, affect a
considerable portion of the power system.
It may therefore be necessary to employ teleprotection links to transmit
generator shutdown commands and load shedding commands from
interconnection points over larger distances and through a number of
intermediate stations to generator sites and to load locations. The
dependability, security and transmission time requirements are similar
to those which apply to breaker back-up protection, but the overall
operating time must be considered, due to the tandem connection of
communication links through a number of intermediate stations.
It is noted that telecommunication facilities for generator shutdown and
load shedding permit interconnections to be operated closer to their
overload limits than without their use; they thus improve network
utilization and commercial efficiency of the electricity supply. Without
such facilities, larger safety margins are needed to avoid overload and
stability problems in case of a tie line loss.

3.6.6.8. Typical requirements in direct tripping applications

• nominal transmission time less than one and a half power-
frequency cycle, and maximum permissible delay about two and a
half cycles
• very high dependability, because inadequate dependability causes
delayed tripping; delays shorter than about one power frequency
cycle are usually acceptable
• very high security, because inadequate security always causes
unwanted tripping; the false trip probability must be kept extremely
small in normal operation and in particular during fault and
abnormal operating conditions
Communication facilities for direct transfer tripping applications are

often duplicated at the upper voltage levels, to improve the reliability of
wanted operation.
Very high security and dependability, achieved at the expense of
transmission time, are therefore required in direct transfer tripping
applications.
Transmission times of 25 ms to 40 ms are generally sufficient for direct
transfer tripping. False command rates under worst-case interference
conditions should be less than 1E-07 or even less than 1E-08.
The following typical settings result:
Command application: direct
Relay interface output: solid state or relay contacts
Command prolongation: 10 ms up to 100 ms (it is
recommended not to configure a
prolongation below 10 ms)
Command outputs set to the quiescent state in case of an
alarm

3.6.7. Teed lines and tapped lines

In power systems undergoing development and extensions, multi-
ended circuits are sometimes used for economic reasons instead of a
number of two-ended circuits. Multi-ended circuits may be either
• teed circuits provided with circuit-breakers at each end at the same
voltage level, where the ends are of equal or comparable
importance, or
• tapped circuits where the two-ended main circuit is equipped with
circuit-breakers at each end and the taps are transformers
connected to the main circuit with circuit-breakers only on the
secondary lower voltage sides. The taps supply loads are generally
less important than the main circuit.
A teed circuit usually presents a difficult protection problem. When
distance relays are used for line protection, their reaches are affected
by the length of the line sections and the in-feed or out-feed of fault
current at the line ends; the latter may increase or decrease the
apparent line impedance seen under fault conditions and thus cause
the protection to underreach or overreach.
The distance relays can sometimes (under “favorable” conditions) be
set to a suitable zone 1 reach at all ends, i.e. to underreach and avoid
overreaching the nearest end. Operation of any zone 1 relay is then
arranged to transmit permissive underreaching commands to all other
ends, so that an internal fault detected at one end will initiate tripping
at all ends.
The choice of a suitable zone 1 reach is, however, often difficult or
insufficient when the setting should avoid overreaching the nearest
end, so that a considerable portion of the line would be protected by
the delayed zone 2. The zone 1 relays are then be set to overreach
beyond the line ends, and a blocking or a permissive overreaching
protection must be used.
Detection of “outward” fault current flow at any end may be arranged to
transmit blocking commands to all other ends, so that an external fault
detected at one end will prevent tripping at all ends.
Alternatively, detection of “inward” fault current flow at any end may be
arranged to transmit permissive overreaching commands to all other
ends; an internal fault must then be detected at all ends to initiate
tripping at any end.
Individual analysis is always required to ensure correct function of the
protective system, and attention must be paid to the risk of loss of
tripping on internal faults when two ends of a teed circuit are also
interconnected by a direct line. This may result in “outward” fault

current flow at one end during some internal fault conditions, and the
direction of power flow in the direct line must be considered.
Protection of a multi-ended circuit generally requires communication
between all ends, and the classical solution for protection of a multi-
ended circuit with n terminals is to provide two transmitters and two
receivers at each end and communication links between all ends, i.e.
n x (n-1):2 communication links (2 out of n) and n x (n-1) transmitters
and receivers. Command inputs must be parallel connected at all
ends, while the command outputs are either parallel connected (wired
OR) or series connected (wired AND), depending on the chosen
protection scheme.
Type NSD570 teleprotection offers solutions saving both information
links and terminal equipment, and the diagram below shows the
arrangement for a three-ended circuit: The operating principle is,
however, also applicable to circuits with four or more ends and thus
considerably reduces the required number of NSD570s and
communication links, because only (n-1) communication links (from A
to first T, from first T to second T, etc., and from last T to B) are
required, together with 2 x (n-1) NSD570s (one at A and B and two at
each T).
A B
TX TX
TX TX
RX RX
RX RX
TPE 1 TPE 2
TX RX RX TX
TX RX 3-T-operation.vsd
Fig. 3-40 T-operation principle

3.6.7.1. NSD570 Analog/Digital/Ethernet in “normal” T-operation

One NSD570 is installed in A and one in B, and two NSD570 in a
common rack are required in T. Under normal fault-free conditions with
the NSD570 Analog, the guard signals transmitted from A and B are
through-connected in T towards B and A. At the same time they are
evaluated in T, while the guard signals originating at T are suppressed.
In case of the NSD570 Digital and NSD570 Ethernet, the guard signals
are also generated at T, i.e. there is no through-connection of the
guard from A to B or from B to A.
Under fault conditions, blocking or permissive underreach tripping
commands originating at A and/or B are through-connected at T and
simultaneously lead to the NSD570 outputs (“dropping” of commands),
which are parallel-connected to the Protection Relay input (wired OR).
When a command originating at T is applied to the parallel-connected
NSD570 transmitter inputs of an NSD570 Analog, the A-T-B and B-T-A
through-connections are interrupted, and the T command is sent to A
and B instead of the guard signals received from B and A.
T-commands originating at an NSD570 Digital and NSD570 Ethernet
are sent to A and B instead of the guard signals generated in T.
When a command from A or B is received in T and a local transmit
command is active at the same time, a combined command signal is
generated and conveyed to B or A (“inserting” of commands).
The operating principle of the “normal” NSD570 T-operation is thus to
perform all required OR combinations of blocking commands or
permissive underreach tripping commands in the intermediate T
stations. The command delays due to the signal through-connections
at T are small and may be ignored in practical operation, while
conventional tandem connections at the transmit and receive
interfaces in T would result in addition of the A to T, T to T and T to B
command transmission times.
For NSD570 Analog and NSD570 Digital, loop tests may only be
initiated at the outer stations A and B; test signals are relayed through
all stations and thus test the complete teleprotection system. The
cyclic loop test must be switched off in the T-station. For NSD570
Ethernet, loop tests are always performed between A and T
respectively B and T.
Transmitter and receivers of the analog version must use the same
bandwidth in “normal” T-operation, while end-to-end operation allows a
different transmit and receive channel bandwidth.
Only two analog, two digital or two Ethernet line interfaces are allowed
in the NSD570 rack of the T station. But the digital interfaces of the
two links in a digital T-operation scheme may be different, i.e. one link

may use the G.703 interface of G3LD while the other uses the RS-530
interface.
In the “normal” T-operation the EOC is only operating between the
outer stations A and B and - in case of the analog version - only if the
guard signal is transmitted. For NSD570 Analog, NSD570 Digital and
NSD570 Ethernet, the EOC must be switched off in the T-station.
If the NSD570 Analog is used, the guard signal is restored in the
T station if one link fails, i.e. the “healthy” link remains active (as a
simple point-to-point connection). If the guard signal reappears from
the “lost” outer station, the guard signal originated in the T station will
be removed and the original T-operation scheme is re-established.
Because there is no through-connection of the guard signals in the
NSD570 Digital and NSD570 Ethernet, no restoring is needed in case
one link fails. The “healthy” link automatically remains active.
Note: NSD570 with GOOSE LAN Interface G3LS does not

support normal T-operation mode.
3.6.7.2. NSD570 Analog/Digital/Ethernet in “inverse” T-operation

One NSD570 is installed in A and one in B, and two NSD570 in a
common rack are required in T. Under normal fault-free conditions, the
guard signals originating at T are transmitted towards A and B. The
guard signals received from A and B are evaluated at T but not
through-connected towards B and A, just as in normal end-to-end
operations.
Under fault conditions, commands received from A and/or B are lead
to the NSD570 outputs at T, which are series-connected to the
Protection Relay input (wired AND), but received command signals are
only through-connected when at least one command originates at T. In
contrast to the NSD570 Digital and NSD570 Ethernet, the received
guard signals of the NSD570 Analog are through-connected as well
when a command is originating at T. Consequentially the “boosting”
facility is disabled in the NSD570 Analog devices configured for
“Inverse T-Operation”, but the boosting output on the Analog Interface
G3LA is still operated when a command is injected at T.
Commands originating at T are therefore not transmitted towards A
and B; they just through-connect received guard (NSD570 Analog
only) and command signals. No provisions are made for individual
through-connection of specific command signals. Any command signal
received from A is sent to B, and vice versa, when some command
originates at T.

All ends must thus transmit command signals to generate a receive

command state at any end, and the operating principle of the “inverse”
NSD570 T-operation is to perform all required AND combinations of
permissive overreach tripping commands in the intermediate T
stations. The command delays due the signal through-connections at
T are small and may be ignored in practical operation, but the
application is generally confined to one command per end, because
command signals cannot be selectively through-connected at T.
For NSD570 Analog and NSD570 Digital, loop tests may be initiated at
all stations; test signals from the outer stations are either reflected
from the T station or from the remote outer station (when a command
is injected at the T station) and thus test the complete teleprotection
system. For NSD570 Ethernet, loop tests are always performed
between A - T and T - B.
Transmitter and receivers of the analog version must use the same
bandwidth and center frequencies in “inverse” T-operation, while end-
to-end operation allows a different transmit and receive channel
bandwidth.
Only two analog, two digital or two Ethernet line interfaces are allowed
in the NSD570 rack of the T station. But the digital interfaces of the
two links in a digital T-operation scheme may be different, i.e. one link
may use the G.703 interface of G3LD while the other uses the RS-530
interface.
In the “inverse” T-operation the EOC is operating between the outer
stations A and T respectively B and T (when no command is injected
at the T station) or - in case of the NSD570 Analog and only if the
guard signal is transmitted - between the outer stations A and B (when
a command is injected at the T station). For the NSD570 Digital and
NSD570 Ethernet, the EOC always operates between A and T
respectively B and T, independent of the command state in T.
Note: NSD570 with GOOSE LAN Interface G3LS does not

support inverse T-operation mode.
3.6.7.3. Addressing of NSD570 Digital in T-operation

For point-to-point links, the local address must be the same as the
remote address at the opposite end of the line. The remote address is
included in the outgoing signal and compared with the local address by
the receiver. The address of the station for which the signal is intended
thus forms part of the signal transmitted.
The programming is somewhat special in teed stations. In normal T-
operation (Section 3.6.7.1 “NSD570 Analog/Digital/Ethernet in
“normal” T-operation”), the incoming signal is relayed through the teed

station as long as no local command is being activated, i.e. the

address in the incoming signal is also relayed unchanged. Should the
protection in the teed station trip, the tripping signal is generated
locally and has to be transmitted to the other stations with the same
address information than previously.
Thus, in the teed station both the local and remote addresses applied
to the Digital Interface G3LD are identical with the address in the
incoming signal. Refer to the configuration example in Section 5.12.3
“TPE1 and TPE 2 in T-station”.
A B
Local address: 15 Local address: 23
Remote address: 23 Remote address: 15
TX TX
TX TX
RX RX
RX RX

Remote address: 15 TPE 1 TPE 2 Remote address: 23
TX RX RX TX
wired OR
wired OR
TX RX 3-Normal-T-operation-with-digital-addresses.vsd
Fig. 3-41 Addressing example for normal T-operation
In inverse T-operation (Section 3.6.7.2 “NSD570

Analog/Digital/Ethernet in “inverse” T-operation”), the outgoing signal
in the teed station is generated locally in the quiescent state and in
case a local command is being activated the incoming signal is relayed
to the other stations. Since there are two independent links A-T and B-
T in the quiescent state, the digital addresses have to be configured
correspondingly.

A B
T
TX
X
TX TX
R RX
X RX RX
TPE 1 TPE 2
TX RX RX TX
wired AND
wired OR
TX RX 3-Inverse-T-operation-with-digital-addresses.vsd
Fig. 3-42 Addressing example for inverse T-operation
3.6.7.4. Tapped lines

(See also Section 3.6.6 “Direct transfer tripping”, Section 3.6.6.5
“Transformer protection”.)
Stepped distance/time Protection Relays are well suited for multi-
ended circuit applications involving transformer tapping points; the
setting of their zone 1 coverage is eased, because it may reach into
part of the transformer impedance, and a permissive underreaching
transfer tripping scheme may be chosen for line protection.
The transformers are often connected to the main circuit with circuit-
breakers only on the secondary lower voltage sides; they usually
supply loads and are less important than the main circuit, but power
feedback to the main circuit may occur during fault conditions. The line
protection must then be arranged to trip the breakers at the main
circuit ends and some or all secondary-side circuit-breakers at the
tapping points.
Transformer faults cannot be detected by the main circuit protection,
and a transformer protection must initiate tripping of its secondary-side
circuit-breaker and transmission of direct tripping commands to the
circuit-breakers at the main circuit ends and to some or all other
circuit-breakers at the tapping points. Fast transmission, high

dependability and high security are required as in all direct transfer

tripping applications.
Received direct tripping commands are usually arranged to cause
three-phase tripping and re-closure lock out. Command transmission
of limited duration is sufficient to achieve wanted operation, and
subsequent restoration to normal operation is then accomplished by
SCADA commands after that the faulty transformer has been
disconnected from the main circuit.
NSD570 in “normal” T-operation (refer to Section 3.6.7.1 “NSD570
Analog/Digital/Ethernet in “normal” T-operation”) are suitable for such
applications, when direct tripping is arranged to take priority over
blocking or permissive underreach tripping.
In cases of important main circuits and tapping points, automatic re-
closure may be required to follow tripping and disconnection of the
faulty transformer by a motor-operated isolator. Command
transmission must then be arranged to continue until the faulty
transformer has been isolated from the main circuit; it must first be
ensured that the circuit-breakers at all ends have tripped, and the use
of further communication facilities is thus required.

3.6.8. Phase-Segregated Command Transmission
3.6.8.1. Twin Line - Two Systems on Common Towers
E E
T1 T2 T1 R2
S1 S2 S1 S2
R1 R2 R1 T2
a b
3-Twin-line.vsd
Fig. 3-43 Twin Line - Two Systems on Common Towers
The conductor arrangement in Fig. 3-43b is often preferred, because it

provides a better balance of the line capacitances to earth than the
arrangement shown in Fig. 3-43a.
Suppose now that a lightning stroke close to the line induces a voltage
adding to all phase voltages, and suppose that this causes insulation
breakdown on the phase T conductor of the circuit 1 and flash-over
across a T1 insulator shown on Fig. 3-43b, somewhere in the center
portion of the line. Suppose further that insulation breakdown occurs a
moment later on the phase R conductor of the circuit 2 (subsequent
flash-over across a neighboring R2 insulator). In a POTT scheme, the
circuit 1 and 2 Protection Relays are then in this situation:
Underimpedance/undervoltage/overcurrent start relays detect
phase-to-ground fault on phases R and T; the distance relays on
both circuits transmit permissive tripping commands; permissive

tripping commands (without phase names) are received at all line

ends; the received commands in combination with the local phase
information result in three-phase tripping * at all line ends, because
the line protections believe that they are faced with either a phase-
to-phase fault on both circuits, or with an intercircuit fault. A PUTT
scheme would behave similarly, at least at one line end.
* The usual strategy is to use three-pole tripping in case of two-phase or three-

phase faults. Single-pole fault clearance may be used in case of phase-to-
ground faults, if the protection and the power system arrangement permits;
however, some power utilities are afraid of negative sequence and never use
single-pole tripping.
That was an unnecessary and unwanted action, because the phase

conductors R1 and T2 and both phase conductors S1 and S2 were
healthy; it would have been sufficient to trip the phase T circuit
breakers on circuit 1 and the phase R circuit breakers at the circuit 2
ends.
Correct single-pole fault clearance can be achieved on both circuits
when phase names are attached to the permissive tripping commands,
e.g. if phase-segregated command transmission is used in a POTT
scheme. This requires the use of three line protection commands (R,
S, T) instead of only one permissive tripping command on each circuit,
and the tripping action of a received R, S or T command must be
made dependent of the local R, S or T fault detecting devices (logical
AND combination, or series wiring).
3.6.8.2. Long Single EHV Overhead Line

About 85 percent of all faults at the higher voltage levels occur on
overhead lines and are single phase to ground faults of a temporary
nature, e.g. caused by lightning. Provided that fast fault clearance is
achieved, they do not spread to other conductors and usually do not
result in permanent damage; the fault must be isolated for about 0.3
seconds to de-ionize the fault path, and the circuit can usually be
successfully re-energized after about 0.5 seconds.
Consider a single-circuit overhead line and suppose now that a
lightning stroke has induced a voltage adding to all phase voltages,
and that this causes insulation breakdown and flash-over across a
phase R insulator somewhere on the line. Both line ends then detect a
phase R to ground fault, and the circuit breakers are tripped at both
line ends, either single-phase or three-phase, as appropriate and pre-
programmed.
Longer EHV overhead lines sometimes exhibit a somewhat peculiar
transient response upon re-closure, and the generating centers at the
line ends may be slightly out of phase when the circuit breakers re-

close, which may cause the line Protection Relays to pick up

sporadically. This may result in unwanted re-tripping and re-closure
lock-out, at least at one line end.
It is noted that the re-closures at the line ends are not synchronized.
When the last circuit breaker re-closes, the line protections at both
ends may pick up sporadically and indicate a transient fault on phase
R at one end and on phase T at the other end. Re-tripping and re-
closure lock-out can be avoided under such conditions when phase
names are attached to the permissive tripping commands, e.g. if
phase-segregated command transmission is used in a POTT scheme;
the tripping action of a received R, S or T command must then be
made dependent of the local R, S or T fault detecting devices (logical
AND combination).
If a blocking scheme is used for line protection, the line end feeding
“outward” fault current transmits a blocking command to the remote
end in case of an external fault to prevent possible tripping due to in-
feed of “inward” fault current. Some users let this blocking command
stand on the line for about 0.75 seconds, i.e. for a time sufficiently long
to prevent unwanted tripping if the protection at the line end feeding
“inward” fault current should pick up sporadically when the circuit
breakers on the adjacent line section re-close.
It is further noted that a distance relay set to underreach in a PUTT
scheme may be switched to overreach while a re-closure pulse is
applied to the line circuit breaker; this allows fast a fault clearance
independent of communication facilities *, e.g. if a metallic connection
T
exists across the insulation. Such rare faults are usually due to failure
to remove grounding connections before replacing a circuit into
service; they are normally three-phase and may cause considerable
disturbance to the power system, in particular when they are close to a
busbar. They are therefore usually considered to be permanent faults,
requiring three-phase tripping and re-closure lock-out.
 A power line carrier link is obviously unable to work, when maintenance work is
done on the overhead line and maintenance grounds are placed at the working
location, and the line is three-phase grounded at both ends.

4. User interface program
4.1. Introduction
The HMI570 software is the interface between the user and the
NSD570 system. Therefore, it is an integral component of the NSD570
equipment family. It allows the user to commission, configure and
monitor a NSD570 device.
The HMI570 has a client / server architecture. This means that the
application runs on a server and the user interacts with the application
through a web browser (client).
There are two different kinds of HMI570 applications available:
• The “HMI570 PC” can be installed from CD onto a PC/Notebook
and allows connecting an NSD570 device locally and remote over
EOC. This kind is also required for remote access of NSD570
equipment over LAN/WAN using the Management LAN Interface
G3LM.
• The “HMI570 LAN” runs on a NSD570 LAN Interface G3LL in the
NSD570 rack. It allows connecting an NSD570 device remotely
over LAN/WAN using a web browser only.
The HMI570 supports:

• Configuration of NSD570 systems
• Commissioning of NSD570 links
• Monitoring of NSD570 devices
To establish a connection to the NSD570 system, the HMI570 has to

communicate with the NSD570 device, see Section 4.5
“Communication between the HMI570 PC and the NSD570”.
Some functions of the HMI570 can also be used without a device
connected. Configuration data entered into the HMI570 in this mode
can be saved to file for later use or data fetched previously from a
device and saved to file can be analyzed and visualized later with the
HMI570.
From HMI570 PC version 1.40 onwards it is possible to install HMI570
with additional IEC 61850 related functionality, which is needed for the
engineering of the GOOSE LAN Interface G3LS. The description
provided in this section reflects the feature set of the standard HMI570
without support of IEC 61850 engineering. The menu items provided
by HMI570 without IEC 61850 support allow the configuration of the
non IEC 61850 specific parameters and the handling of a completed
User interface program August 2021 4-1

IEC 61850 configuration (e.g. downloading to G3LS). However, the

creation of an IEC 61850 configuration for G3LS is not supported.
If G3LS is needed and HMI570 is installed with IEC 61850 support,
please refer to the document “Engineering of GOOSE LAN Interface
G3LS” in Section 12 “Annex”. It contains a description of the additional
menu entries of the extended HMI570 version including IEC 61850
related functionality.
4.2. Safety instruction

The teleprotection link gets disturbed while using
Caution certain functions offered by the HMI570 for commis-
test mode).

Note: It is recommended to disconnect the PC/notebook

from the LAN while running the HMI570 and
connecting a device via the RS-232 interface.
4.3. System requirements and technical data for HMI570

Please refer to 1KHW000894 “Software Installation Description
HMI570”.
4.4. Installation of HMI570

Please refer to 1KHW000894 “Software Installation Description
HMI570”.
4.5. Communication between the HMI570 PC and the NSD570

To connect the HMI570 PC running on a PC to a NSD570 via the
RS-232 interface on the front plate, a 9-pole 1:1 modem cable (female
to male) is required. Also, the handshake signals (RTS and CTS) must
be 1:1 connected. In case the COM port of the PC has a 25-pole
RS-232 connector, an adapter (25-pole female to 9-pole male) is
needed.
4-2 August 2021 User interface program

The default baud rate (57’600) requires a cable length below 3 meters.
Parameter Setting
Baud rate 57’600

Data bits 8
Parity None
Stop bits 1
Flow control RTS, CTS handshake
Table 4-1 RS-232 default interface settings
4.5.1. Local connection

Substation A
Station bus
NSD570
TPE 1 TPE 2 LAN IF TPE 1 TPE 2
100 101 102 120 121
NSD570 A1 NSD570 A2
RS232
Device
address
HMI570
4-Local-connection.vsd
Fig. 4-1 Example for local connection
A connection between the PC/notebook allows to connect all NSD570

that are within a substation and wired by the station bus. In the
example above, the devices with address 100, 101, 102, 120 and 121
can be connected via a local connection.
In contrast to the LAN Interface G3LL the Management LAN Interface
G3LM is not only accessible over LAN but also over the local serial
port. However, serial connection to G3LM is only possible if the LAN
port is down (unplug the LAN cable).
Note: Every NSD570 line interface within a substation must

have a unique device address.
Serial connection to the Management LAN Interface
G3LM is only possible if the LAN cable is unplugged.

4.5.2. Remote connection over (EOC)

Embedded operation channel (EOC)
Station bus
NSD570
TPE 1 TPE 2 TPE 1 TPE 2 TPE 1 TPE 2
100 101 120 121 220 221
NSD570 A1 NSD570 A2 NSD570 B1

RS232
Device
address
HMI570
4-Remote-connection.vsd
Fig. 4-2 Remote connection over EOC
Note: This remote connection is only possible if both

devices (the local and the remote) have the EOC
switched on.
A connection over EOC allows connecting the remote peer device of a

link. In the example above, a remote connection with device address
100 effectively connects device 220.
4.6. Remote connection over LAN / WAN / Internet
4.6.1. Use of LAN Interfaces G3LL / G3LM

Substation A Substation F
Station bus
TPE1 TPE2 LAN

TPE1 TPE2 LAN TPE1 TPE2 100 120 Interface
100 101 Interface 120 121
NSD570 F1
NSD570 A1 NSD570 A2
Device
address
LAN / WAN
Internet
HMI570
4-Remote-connection.vsd
Fig. 4-3 Remote connection over LAN / WAN / Internet
In the example above, the devices with address 100, 101, 120 and 121
in Substation A can be connected from the local PC via the LAN
Interface G3LL/G3LM in the NSD570 A1 rack. The devices with
address 100, 120 in Substation B can be connected via LAN Interface
G3LL/G3LM in the NSD570 F1 rack. The LAN Interfaces and the

subsequent NSD570 devices can be distinguished by their IP address.

However, it is recommended to use unique NSD570 Device Addresses
in a network (not as in the example above).

(e.g. Internet).
Additionally, remote connection over Internet re-
quires appropriate security measures (see Section
4.6.2 “Security considerations for connections over
Internet”).
Never connect a NSD570 LAN Interface G3LL or
G3LM directly to the Internet!
Note: This connection over LAN / WAN / Internet needs a

LAN Interface G3LL/G3LM plugged in the NSD570
module rack and connected to the corresponding
communication media.
In case of the Management LAN Interface G3LM, not
only a web browser but also the “HMI570 PC”
software (version 1.30 or higher) has to be installed
on the local PC to get access to NSD570 equipment
over LAN / WAN.
4.6.2. Security considerations for connections over Internet

Recommended security measures:
• Never connect a NSD570 LAN Interface directly to the Internet,
there must be at least a firewall in between.
• Only use encrypted SSL connections to access the HMI570 LAN
running on the NSD570 LAN Interface G3LL.
• On the Management LAN Interface G3LM, SSL is always enabled
(and cannot be disabled by the user). Make sure the default
certificate is replaced before accessing G3LM over LAN. The
certificate should periodically be replaced by an administrator.
• If access from the Internet is required, make sure that the SSL port
of G3LL/G3LM is open in the firewall. SSL port number: G3LL:
443; G3LM: 5000 (see also Annex: Technical Data NSD570).
• SNMP v1/v2 is not a secure protocol. Therefore, it is strongly
recommended not to use it over Internet.

4.7. Multiple connection

Substation A
Station bus
TPE1 TPE2 LAN TPE1 TPE2

100 101 Interface 120 121
NSD570 A1 NSD570 A2
Device
address RS232
LAN / WAN
Internet
HMI570
HMI570
4-Multiple-connection.vsd
Fig. 4-4 Multiple connection from local and remote
Note: Do not connect a device simultaneously from local

and from remote site.
Substation A
Station bus
NSD570
TPE 1 TPE 2 TPE 1 TPE 2
100 101 120 121
NSD570 A1 NSD570 A2
RS232 RS232
HMI570 HMI570
4-Multiple-connection.vsd
Fig. 4-5 Multiple connection via the station bus
Note: Do not plug more than one PC/notebook

simultaneously to NSD570 racks that are
interconnected by a station bus.

4.8. Browser front end

The HMI570 uses a web browser as front end (client part). This means
that all interactions between the user and the HMI570 take place in a
web browser window.
• Microsoft® Edge web browser is recommended to use with
HMI570.
4.8.1. Browser settings

In order to run the HMI570 properly, the following settings of the web
browser must be configured:
• Cookies must be enabled
• META refresh tag must be enabled
• File download must be enabled
• Bypass proxy server for the localhost address
• JavaScript must be enabled
All the settings above are enabled by default in Microsoft® Edge web
browser.
4.8.1.1. Additional browser settings for the HMI570 LAN
There are additional browser settings to observe when using the

HMI570 LAN (G3LL):
• Bypass proxy server for the IP addresses that are used for G3LL
• Add IP addresses of G3LL to trusted sites
4.9. Starting the program
4.9.1. HMI570 PC
As it was mentioned in the Section 4.1 “Introduction”, the HMI570 has
a client / server architecture. In the PC version of HMI570, the server
and the client are running on the same PC.
4.9.1.1. Start HMI570 PC Server and Client Simultaneously

This is a common way how to start HMI570. To start the HMI570
Server and the Client (browser with HMI570) simultaneously, select on
the taskbar Start → Programs → HMI570 Shortcut Folder → Start
HMI570. The HMI570 Server will be started and when the server is
ready, the HMI570 Client will start automatically.

4.9.1.2. Start HMI570 PC Server
Note: This section and all sections below until the Section
4.9.2 “HMI570 LAN” refer to the HMI570 “PC” Version
1.14 and higher. In older versions of HMI570 it is not
possible to start HMI570 Server separately from the
HMI570 Client.
In HMI570 Version 1.14 or higher it is possible to start HMI570 PC
Server separately from the HMI570 Client. This could be useful when
HMI570 is used quite often, as it takes more time and requires more
PC processor power to start the HMI570 Server compared to the
HMI570 Client. In this case HMI570 Server can be started only once
and the HMI570 Client can be started and stopped whenever needed.
To start HMI570 Server separately without a Client, select on the
taskbar Start → Programs → HMI570 Shortcut Folder → HMI570
Server → Start HMI570 Server.
Note: See Section 4.9.1.5 “Change HMI570 PC Server

Settings” on how to adjust HMI570 Server settings to
get more benefits from a separate start of the HMI570
Server and the Client.
4.9.1.3. Stop HMI570 PC Server

All HMI570 Clients (browsers with open HMI570) are required to be
closed before stopping HMI570 Server (see Section 4.10.10 “Exit
HMI570” on how to exit from HMI570 in the correct way). If the setting
“Shut Down Server Automatically” is set and all Clients were closed
appropriately, the HMI570 Server will stop automatically. Otherwise, to
stop HMI570 Server right-click on the HMI570 Server Icon in the
System Tray (it looks like ) and select “Shut Down (Stop Server)”
from the pop-up menu.
An alternative way to stop HMI570 Server is to select on the taskbar
Start → Programs → HMI570 Shortcut Folder → HMI570 Server →
Stop HMI570 Server. The browser will be opened and the HMI570
Server will be stopped. After HMI570 Server is stopped, the browser
displays an error page with a message like: “The page cannot be
displayed”. This is the normal behavior of the browser.
4.9.1.4. Start HMI570 PC Client

When HMI570 Server is already running there are several ways to
start a new HMI570 Client.

Double-click with the left mouse button on the HMI570 Server Icon in
the System Tray (it looks like ) starts a new browser (or browser tab)
with the HMI570 Client.
Right-click on the HMI570 Server Icon in the System Tray opens a
pop-up menu, from which select “Open HMI570” to start a new
browser (or browser tab) with the HMI570 Client.
On the taskbar Start → Programs → HMI570 Shortcut Folder →
HMI570 Server → “Open a browser with HMI570” starts a new browser
(or browser tab) with the HMI570 Client.
Note: It is not allowed to start a new browser separately and

just type the HMI570 URL-address into the address
bar.
The correct way to start a new browser with HMI570
is to use bin\startBrowser.bat and
bin\startBrowserInit.bat in the HMI570 program folder.
Note: Up to version V1.48, HMI570 forced the Internet

Explorer from Microsoft to be opened. However, it
was possible to use an alternative web browser, as
for example Mozilla Firefox, by manually adapting the
files bin\startBrowser.bat and bin\startBrowserInit.bat
in the HMI570 program folder.
Beginning with version 1.49, the default browser
installed on the computer is opened by HMI570, or a
new tab is opened if the browser is already running.
4.9.1.5. Change HMI570 PC Server Settings

To change the HMI570 PC Server Settings right-click on the HMI570
Server Icon in the System Tray (it looks like ). From a pop-up menu
select “Settings” and then one of the following settings:
Setting Explanation
Start Server with If this setting is selected, the HMI570
Windows Server will be started automatically
during Windows start-up. The HMI570
Client can be started manually later at
any time.
Shut Down Server If this setting is selected, the HMI570
Automatically Server stops automatically when the last
HMI570 Client has been closed.

Note: “Shut Down Server Automatically” is enabled by

default after HMI570 installation, whereas “Start
Server with Windows” is disabled by default.
4.9.2. HMI570 LAN

In the HMI570 LAN version, HMI570 Server is running on G3LL LAN
Interface and the HMI570 Client is running on a PC/Notebook. To start
the HMI570 Client for the HMI570 LAN, open a web browser and type
the following URL:
http://<IP_LAN_Interface>/hmi570/index.jsp
To access the LAN Interface over an encrypted SSL connection, use
the subsequent URL (auto redirect to this address since HMI570 LAN
Version 1.13):
https://<IP_LAN_Interface>/hmi570/index.jsp
where <IP_LAN_Interface> is the IP address of the LAN Interface that
shall be connected (e.g. https://172.20.162.54/hmi570/index.jsp).
Note: The usage of an SSL connection requires a NSD570

LAN interface that is SSL enabled (standard since
HMI570 LAN Version 1.13).
Encrypted SSL connections are strongly
recommended for communication channels that are
not secure (e.g. Internet).
4.10. Operation
4.10.1. Introduction
This section outlines the operation of the HMI570. It describes the
different menus and functions, how they can be executed and
particularities to be regarded when using the HMI570.
It is recommended to read this section thoroughly before beginning to
work with the HMI570.
4.10.2. Basic operation principles

Due to the nature of the HMI570 as client / server software, there are
some operation principles that may be different to other software tools:

• Do not use the buttons from the toolbars of the browser (in parti-
cular do not use “Back”, “Forward”, “Stop”, “Refresh” or “Reload”).
• A few functions need somewhat longer to execute. This execution
time depends on the speed of the PC/notebook. The progress bar
at the bottom right side of the browser shows the status of the
executed function. Do not use the “Stop” button from the browser
toolbar because this will not stop the execution. Do not start
another function by clicking a menu item before the previous
function has finished.
• Do not edit manually the URL (web address).
• Do not close the browser window manually to exit the HMI570.
Instead click on “Exit HMI570” on the left side of the window.
4.10.3. Design
The HMI570 window is divided into three parts. At the top there is a
header with the logos and the green Status Box. At the left side there
are the menu items.
The display sector on the right-hand side of the menu shows the
information and input fields of the currently executed function, e.g.
status, alarm, configuration info.
Status Box
The green box in the top right corner is the Status Box. It shows the
name of the user that is logged in, the permissions the user has, the
name of the configuration that is loaded, the name and address of the
device that is connected and what kind of interface is in use (Analog,
Digital, Ethernet, GOOSE, Management).
4.10.4. Log-in / Log-off

Before starting to work with the HMI570, logging in with username and
password is required.
Click on “Log In” in the menu bar and type in username and
password. If you are connected to the NSD570 equipment by a serial
cable, select “local” and confirm by clicking on the “Log In” button or by
pressing “Enter”.
In case of remote access over the Management LAN Interface G3LM
select “LAN”, type in the correct IP address and confirm by clicking on
the “Log In” button or by pressing “Enter”.
If the certificate sent by G3LM is unknown to HMI570, the certificate
status is displayed. The user has three options:
1. “accept temporarily”: The certificate is accepted for one HMI570
session only. The next time logging in on the same G3LM the

message is displayed again. This option shall be used only in

trusted networks and if the certificate is known by the user.
2. “do not accept”: The certificate is not accepted and hence the
connection refused. This option shall be used if the certificate is
unknown or if connected through an untrustworthy network.
3. “accept permanently”: The certificate is accepted and stored on the
HMI570 PC. In subsequent sessions, the connection to this G3LM
is established without user interaction. This option shall be used
only in trusted networks and if the certificate is known by the user.
Note: Username and password are case sensitive.
There are three predefined user roles (permissions) supported by

HMI570:
• Admin – This role allows to create new users and to change
passwords and user rights of any existing other user. There
must be at least one user with the admin permissions defined
in the system.
• Modify – This role allows to modify the configuration on the
equipment and execute restart of the equipment.
• View – This role allows to view configurations and the event
recorder only.
For the detailed description of each permission, please refer to the
Section 4.14.1 “User Administration and Permissions”.
It is recommended to create at least three different users for all three
permission types. For example:
User: Permissions: Default Password:
Administrator admin, modify, view welcome
Service view, modify none
Operator view none
After the installation of HMI570 on the PC/notebook, there is a single
default user “Administrator” present in the system (with default
password “welcome”).
Note: For security reasons, the Administrator password

must be changed immediately after the installation of
the HMI570. There is a warning message displayed at
the top of the HMI570 window until the default
password has been changed.

The password complexity is checked by HMI570.

Note:
From HMI570 version 1.30 onwards, it shall consist of
at least six characters and of at least eight characters
from version 1.48 onwards, as a combination of
letters, numbers and “special” characters.
Note: If the Management LAN Interface G3LM shall be

accessed over an untrustworthy network, it is highly
recommended to upload the certificate locally over the
serial port of the NSD570 equipment and distribute it
to the PCs for remote access. The Certificate
Management of HMI570 supports certificate
import/export for such cases.
If a default certificate or invalid certificate (expired
date) is received, the option “accept permanently” is
disabled.
In both cases it is highly recommended to generate a
new certificate on G3LM which enables accepting and
storing the certificate permanently on the HMI PC
(see Section 4.13.4 “Certificate Management for
details).
After logging in, the username and the permissions are indicated in the
green Status Box on the top.
It is possible to add and delete users and to change the passwords
and permissions. This is described in Section “HMI570 Settings”
4.14.1 “User Administration and Permissions”.
To log off, just click on “Log Off” in the menu bar. It is recommended
to disconnect the device first, before logging off.
4.10.4.1. Connect / Disconnect Device

For details about different connections see Section 4.5
“Communication between the HMI570 PC and the NSD570”.
Local Connection:
The HMI570 PC/notebook is physically and logically connected to the
local NSD570.
Remote Connection over Embedded Operation Channel (EOC):

The HMI570 PC/notebook is physically connected to the line interface
of the local NSD570. The logical connection is made to the remote
peer device of the link.

Note: This remote connection is only possible if both line

interfaces of the local and the remote device have the
EOC switched on.
Note: A remote connection over EOC has the drawback of a

slow communication between the HMI570 and the
remote device. The response time of the HMI570 may
increase drastically (especially with an analog link).
Please be patient and do not press any button from
the toolbars of the browser.
Note: A remote connection over EOC is not possible to the

GOOSE LAN interface(s) G3LS and the Management
LAN interface G3LM in the remote NSD570 rack.
4.10.4.2. Connect Device

To connect a device, click on Connect Device and then type in the
device address. For the line interfaces G3LA/G3LD/G3LE choose
between „local” or „remote over EOC”.
Please note: to connect remotely, type the address of the local line
interface and check the „remote over EOC” box.
If the device address of the line interface is unknown, use 241 for the
device plugged in TPE 1 respectively 246 for TPE 2. These addresses
are the default addresses of the rack and cannot be used as device
addresses.
If the device address of the GOOSE LAN Interface is unknown, use
242 for the G3LS plugged in TPE 1 respectively 247 for TPE 2. These
addresses are the default addresses of the rack and cannot be used
as G3LS addresses.
If the device address of the Management LAN Interface is unknown,
use 250 for the G3LM plugged in the rack. This address is the default
address of the rack and cannot be used as G3LM address.
To connect a device with the default address, the two buttons for
G3LA/D/E and the two buttons for G3LS under “TPE 1” and “TPE 2”
below “Connect with Local Default Address” can be used. In addition,
a button G3LM is available to connect the Management LAN Interface
with the default address.
Note: If a device shall be connected with the default

address, the station bus of this rack must be
disconnected (because the devices TPE 1 or TPE 2
of all other racks share the same default addresses).

The device address range is configurable from 1 to 240.

If the connection is successful, information of the device will be
displayed, an example is shown next:
Device connected
Analog line interface
Device address 101 local
DSP firmware version 1.14
Controller firmware version 1.04
The green Status Box displays the name and address of the
connected device and what kind of interface is in use (Analog, Digital,
Ethernet, GOOSE, Management).
A boot failure of the line interface is indicated by the red “Fail” LED on
the front plate whereas all other LEDs are off. In this case it is possible
to connect the device with address 255. It is recommended to
disconnect the station bus and plug off the other line interface in the
rack first, before connecting with 255 to the line interface concerned.
After a successful connection to the device with address 255, execute
a firmware download, see Section 4.10.8.8 “Firmware Download”.
4.10.4.3. Error messages and troubleshooting

Error! The device is already connected by another user/
application
Only one connection to a device can be established at the same time.
If there already is a connection to the device it must be disrupted
before a new connection can be established. If a session is aborted
(the browser window was closed for example) with a device connected
to, this device cannot be reconnected before the aborted session is
timed out (this will take a maximum of 60 minutes). The only possible
faster solution is to stop and restart the HMI570.
Note: Stop and restart of the “HMI570 LAN” on G3LL is not

possible (remote connection over LAN / WAN /
Internet).
See Section 4.14.4 “LAN Interface” what to do in this
case (“Reset communication”).
Error! Device communication timeout
The device could not be reached. Several reasons are possible:
1. The HMI570 PC/notebook is not or not correctly connected to the
NSD570
→ check the cabling, try a shorter cable according to Section 4.5
“Communication between the HMI570 PC and the NSD570”

2. The device address is wrong (e.g. two TPE with the same address)
→ verify the device address or try it with the default device address
3. The NSD570 is not running
→ verify that the desired device is running
4. The parameters for the Device Communication of the HMI570 and
the NSD570 do not correspond
→ try to connect the NSD570 with another baud rate
5. The station bus is not correctly wired
→ check the cabling of the station bus
Error! Device communication is busy! Please try it later again.

Another user is connected to a device and occupies the
communication channel.
Note: If it is not possible to connect the device after some

retries, stop and restart the “HMI570 PC”.
Stop and restart of the “HMI570 LAN” on G3LL is not
possible (remote connection over LAN / WAN /
Internet).
See Section 4.14.4 “LAN Interface” what to do in this
case (“Reset communication”).
COM port is not available or owned by another application

The COM (RS-232) port cannot be used by the HMI570. Two reasons
are possible.
1. The HMI570 PC/notebook does not support the desired COM port
(RS-232)
→ check the COM ports of the PC/notebook and the HMI570
settings
2. Another application uses the COM (RS-232) port
→ stop the application that uses the COM port
Error! This configuration version is not supported.

Or
Error! This configuration file is based on a newer NSD570 file
format.
Or
Error! The NSD570 is using a newer configuration file format.
The firmware version of the device is not compatible with the HMI570.
→ update the HMI570 to the latest version.

The menu item “Connect Device” cannot be selected.

First make sure that you are logged in (see 4.10.4 “Log-in / Log-off“). If
you are logged in and “Connect Device” is still not selectable, it is
possible that another user has started the Alarm Polling (see Section
4.11 “Alarm Polling”). This can happen only when using the “HMI570
LAN”.
The browser shows the error

“Connection Timed Out”, response (504)
This can happen when the user tries to connect a device remotely over
the EOC with the HMI570 LAN.
In case of the NSD570 Analog it may take a long time due to the low
transmission rate of the EOC.
When the connection between the NSD570 LAN Interface (where the
“HMI570 LAN” runs) and the browser goes over a proxy server, this
timeout error comes from the proxy. To avoid the error, the browser
must be configured to bypass the proxy for the NSD570 LAN Interface,
see 4.8.1.1 Additional browser settings for the HMI570 LAN.
4.10.4.4. Disconnect Device

To disconnect the device, click on Disconnect Device in the menu
bar.
Note: It is strongly recommended to disconnect a device as

soon as there are no more intentions to interact with it
any longer.
4.10.5. Configuration
4.10.5.1. Load From Disk

If Load From Disk is not accessible, the current configuration has to
be discarded first, see Section 4.10.5.5. “Discard Configuration”.
Load Default Configuration

Loading a default configuration is a good start for the configuration of a
NSD570 device. There are six default configurations for line interfaces
and one for the management interface. Additionally, two HW default
configurations for the GOOSE LAN interface G3LS are provided:
Default_TPE1_Analog.xml Analog Line Interface TPE 1

plugged at the left side of the rack (slot N28)
Default_TPE2_Analog.xml Analog Line Interface TPE 2
plugged at the right side of the rack (slot N58)

Default_TPE1_Digital.xml Digital Line Interface TPE 1

Default_TPE2_Digital.xml Digital Line Interface TPE 2
Default_TPE1_Ethernet.xml Ethernet Line Interface TPE 1
Default_TPE2_Ethernet.xml Ethernet Line Interface TPE 2
Default_Management.xml Management LAN Interface G3LM
plugged at the rightmost position of the rack
(slot N84)
Default_TPE1_GOOSE.xml GOOSE LAN interface G3LS
Default_TPE2_GOOSE.xml GOOSE LAN interface G3LS
plugged at the right side of the rack (slot 64)
Click on the corresponding „load” button to load a default

configuration.
Load Configuration from local disk
An earlier saved configuration can be loaded from the local disk.
Click on Load Configuration and then the „Browse…” button to select
the file on your local disk, press the „load” button afterwards.
4.10.5.2. View Configuration

Choose this menu item to view the entire configuration of the NSD570
on one browser page. This gives an overview of all the settings and is
especially intended for printing out the configuration.
Note: “View Configuration” does not work with the HMI570

“LAN” version. For printing out the configuration, save
it to disk and load it into the HMI570 “PC” version.
4.10.5.3. Edit Configuration
4.10.5.3.1. Line Interface Configuration

If a configuration is loaded (either from disk or uploaded from a device)
Edit Configuration allows viewing and editing the settings.
The Edit Configuration submenus are further described below. The
first three submenus (Device Information, Hardware Versions and
Firmware Versions) are not editable.

To edit a configuration parameter, choose the submenu, click on the

edit button and type in the desired values or choose them from a
dropdown list. If the changes are to be skipped, click on the cancel
button. Click on the update button to confirm.
Note: Clicking the update button confirms only a change of

the parameters stored inside the HMI570, it has no
influence on the configuration of a connected device.
Device Information
Contains the type of the interface (analog, digital, Ethernet,
management), the position where it is plugged in, the serial number
and the counter of the firmware and configuration downloads.
Hardware Versions
Displays the hardware versions of the plugged modules and SFP
identifications. The power supply units have no version coding.
Firmware Versions
Displays the firmware version of the Micro Controller and the Digital
Signal Processor (DSP) in case of an analog or a digital line interface.
Displays the firmware version of the processor in case of an Ethernet
line interface (also applies for GOOSE LAN Interface and
Management LAN interface).
Device Identification
Contains the configuration type (analog, digital, Ethernet, GOOSE,
management), the name of the station, the HE number and the device
address.
Common Settings
In this menu item the general device operation mode can be
configured, settings for the Extra Delay and Pulse Duration for
Unblocking and for the Pickup Time and Hold Time for Link Failure can
be edited, the Embedded Operation Channel (EOC) for remote
connection can be enabled and the settings for External Real-Time
Sync (IRIG-B) can be configured. Furthermore, the Propagation Time
i.e. the delay on the transmission channel can be set here.
Analog Interface (only shown for analog configuration types)

Defines the Line Type, the Rx and Tx Bandwidth, the Center
Frequencies and the Analog Operating Mode. Power Boost,
Unblocking Threshold, Rx and Tx Level and Alarm Threshold can also
be changed.

Digital Interface (only shown for digital configuration types)

There are seven different types of digital and optical interfaces:
1. G.703 64 kbps co-directional
2. RS-530
3. E1 2048 kbps
4. T1 1544 kbps
5. Optical Direct Fiber
6. Optical OTERM/OPTIF
7. Optical IEEE C37.94
Every interface type allows the configuration of the following
parameters:
Digital Address Check (on/off),
Local Digital Address,
Remote Digital Address,
Bit Error Rate (BER) Alarm Threshold.
Additional parameters per interface may be changed (type specific).
Ethernet Interface (only shown for Ethernet configuration types)
Allows the configuration of the following parameters:
Auto negotiation (auto/manual),
Local IP Address,
Subnet Mask,
Default Gateway,
Remote IP Address,
IP Priority (TOS/DSCP and ECN),
VLAN Tagging (disabled/enabled),
UDP Port Teleprotection Packets,
UDP Port EOC Packets,
Guard Packets Sending Interval,
Transmission Time Test Interval,
Transmission Time Warning / Alarm Sensitivity (Low/Medium/High),
Packet Loss Rate Alarm Threshold,
Automatic Laser Shutdown (on/off).
In case of Auto negotiation set to manual the following sub menus
appear:
Data Rate [Mbps] (10/100),
Duplex Mode (Full Duplex/Half Duplex).
In case of VLAN ID set to enabled, the following sub menus appear:
VLAN ID,
Priority.

Command Settings
Contains the settings for every command. If the application is set to
off, the corresponding command cannot be used.
Max. Tx Input Monitoring can be given in seconds or disabled.
It can be chosen between Transparent, Prolonged, Limited or Fixed Tx
Input and Rx Output Duration.
Tx Input On-Delay, Tx Input Duration value and Rx Output Duration
value are given in milliseconds.
Relay Interface
Displays the settings for the relay interfaces. If the interfaces are used,
commands, alarms, acknowledges and some status information can
individually be mapped to the inputs and outputs of the relay
interfaces. In case G3LS is selected, only commands can be mapped
to the inputs and outputs.
Alarm Settings
The Pickup Time and Hold Time can be set.
The behavior in case of a failing redundant power supply can be set:
• if set to “HW Warning”, then “Warning: Undervoltage redundant
supply 1/2” is raised.
• if set to “HW Alarm”, then “Undervoltage alarm supply 1/2” is raised.
The alarm output for User Alarms 1 … 3 can individually be set to
“delayed” or “undelayed”. If set to “delayed”, then the user alarm
output is operated with respect to the configured Pickup and Hold
Times. If set to “undelayed”, then the user alarm output follows the
alarm state without any additional delay.
User Alarms 1 ... 3 can be configured to combine some different
alarms into a user alarm (by logical OR-gating of selected high-level
alarms).
Jumper Settings
Displays the jumper settings for the Analog Interface, the E1/T1
Interface and the Relay Interfaces.
Note: These parameters have no influence on the device

and must be set manually for documentation purpose.
Rack Assembly
Displays the type of the plugged components and boards.

Note: These parameters have no influence on the device

and must be set manually for documentation purpose.
Rack Assembly is not available for the Management
LAN Interface G3LM and the GOOSE LAN Interface
G3LS.
4.10.5.3.2. GOOSE Interface Configuration

This menu provides access to parameters of the GOOSE LAN
interface which are not in relation to IEC 61850.
Device Information
Contains the type of the interface (GOOSE Interface), the position
where it is plugged in and a counter for firmware and HW/IED
configuration downloads.
SFP Identification
If an SFP transceiver is plugged the following information about it can
be found in this menu: Vendor, Part Number and Transceiver Code.
Firmware Version
Display the firmware version of the G3LS software running on the
embedded processor.
The identification of a GOOSE LAN interface contains several
parameters which allow the identification of a G3LS device.
Station Name:
It's recommended to assign a unique, human readable identifier to
each G3LS device. This helps for example to identify a G3LS device in
case of remote connection or if the device is unplugged from the
NSD570 rack.
HE number is thought to be a unique identifier which is typically
assigned by HITACHI ABB's engineering group during the device
configuration.
Device Address: See Section 4.5 “Communication between the
HMI570 PC and the NSD570” for details.
GOOSE LAN Interface

Automatic Laser Shutdown (ALS):
Can be configured to on or off (default). Applicable for the laser of the
SFP transceiver used as optical network interface, which is optionally
plugged into the SFP cage (if configured to “on”, the laser is shut down
when no optical signal is received).

Number of Protection Commands:

The parameter “Number of protection commands” defines how many
commands are exchanged between the line interface and G3LS. In
other words, the parameter defines how many physical slots are
(virtually) occupied by G3LS and how many slots can be used by
G3LR interfaces. The parameter is valid for both directions.
External Real-Time Sync (IRIG-B):
G3LS supports to synchronize its real time clock using the IRIG-B
signal as a clock reference. If External Real-Time Sync (IRIG-B) is
configured to “off” the quality attribute of the time stamp which are
published as part of the PhyHealth and EEHealth data objects are set
to invalid. The “clock failure” and the “clock not sync” bits are set.
4.10.5.3.3. IEC 61850 Configuration

HMI570 without IEC 61850 support does not integrate the features
needed to create an IEC 61850 configuration for G3LS. These
features are available from HMI570 1.40 onwards and if HMI570 has
been installed with IEC 61850 support enabled.
Since IEC 61850 related functions of HMI570 are very specific to
G3LS, all of them are described in detail in the annex document
“Engineering of GOOSE LAN Interface G3LS”.
4.10.5.3.4. Management Interface Configuration

This menu item allows the configuration of the Management LAN
Interface G3LM. The following parameters can be set:
• IP Address
• Subnet Mask
• Default Gateway
• 802.1Q VLAN Tagging (enabled/disabled)
• VLAN ID
• VLAN Priority
• Auto Negotiation (manual/auto)
• Data Rate [Mbps] (10/100)
• Duplex Mode (Full Duplex/Half Duplex)
• Automatic Laser Shutdown (on/off)
• External Real-Time Sync (IRIG-B) (on/off)

SNMP Event Polling

This menu item allows the configuration of the SNMP event polling
running on G3LM:
• Alarm Polling (on/off)
• Command and Manipulation Event Polling (on/off)
• Trip Counter Polling (on/off)
Devices to be polled can be added by specifying the device address

and clicking on add new device. If the check box “Remote over EOC”
is selected, the remote device is also polled.
To remove a device, simply check “Select” and click on remove all
selected.
Additionally, the length of the polling cycle can be set (ranges from
5 seconds to 24 hours).
Only if Alarm Polling is set to “on”, Command and Manipulation Event
Polling, as well as Trip Counter Polling can be enabled individually. In
case of Command and Manipulation Event Polling and/or Trip Counter
Polling enabled, it is possible to poll local devices only, the check box
“Remote over EOC” will be disabled.
The alarms collected from the configured devices can be accessed by
network alarm polling or SNMP requests (if SNMP is enabled).
SNMP Parameters
If SNMP is enabled, traps are sent to the configured network
management stations (NMS). In addition to the IP address, the port of
the NMS and the SNMP version can be configured.
With HMI570 version 1.46 and higher, also the “Community String”,
“System Name” and “System Contact” can be configured.
Since HMI570 version 1.49, the SNMPv3 support is added. Selection
can be made between “1 and 2”, “1”, “2”, “3”.
When the SNMP version of a SNMP Trap Subscriber is set to 3, a
SNMPv3 user specified in the SNMPv3 User Management table can
be selected under “SNMPv3 User Name”.
The SNMPv3 traps will then be sent using the authentication and
privacy settings of the specified SNMPv3 user.
When using SNMP version 3 for SNMP traps, the SNMP version in the
general SNMP settings must be configured to version 3 as well.

SNTP Time Parameters

If SNTP is enabled, the primary and the secondary NTP/SNTP server
can be configured. Additionally, the SNTP interval can be configured.
With HMI570 version 1.49 and higher, the time zone offset from UTC
time (Universal Time Coordinated), as well as the daylight saving time
(DST) can be configured and stored on the Management LAN
interface (G3LM).
The UTC time received from the specified SNTP server over LAN is
adjusted according to these settings and distributed over the IRIG-B
output to the interfaces in connected NSD570 racks. The adjusted
(local) time is also used for time stamping of user activity log entries,
events in the MIB table and traps sent to the NMS.
In case the daylight saving time (also called summer time in Europe) is
set to "on", the time offset is increased by +1 hour. This change has to
be done manually according to the local situation (i.e. when the time
shift takes place).
4.10.5.4. Save To Disk

The configuration can be saved to disk.
Choose Save To Disk in the menu. Click with the left mouse button on
the link and choose “Save this file to disk…” and select the destination
folder.
It is recommended to save configurations with the extension *.xml.
4.10.5.5. Discard Configuration

Discards the current configuration of the HMI570. Has neither
influence on the connected device nor on a saved configuration.
After discarding a configuration, it is possible to upload a configuration
from the device or load one from the local disk.
4.10.5.6. Download To Device

Downloads the configuration to the device. It is recommended to save
a configuration to disk (see Section 4.10.5.4 “Save To Disk”) before
downloading to the device.
To activate the downloaded configuration, reset the device after the
download. The link gets disturbed during reset! A wrongly configured
device can cause a malfunction of the teleprotection link!


4.10.5.7. Upload From Device

Uploads a configuration from the device.
If Upload From Device is not accessible, maybe there is no device
connected (see Section 4.10.4.2. “Connect Device”) or the previously
used configuration has not been discarded inside the HMI570 (see
Section 4.10.5.5. “Discard Configuration”).
4.10.6. Event Recorder

The event recorder is a feature of the NSD570 device. It logs
command, alarm and manipulation events in the non-volatile memory
of the NSD570. Every event is logged with a time stamp.
To ensure the correctness of the time stamps, check time and time of
the device, see Section 4.10.8.5. “Get Time and Date”.
The event recorder can store approximately 7500 event entries. If this
is exceeded, the oldest events will be overwritten.

Loads events from the local disk. Click on the „Browse…” button to
choose the file and press the „load” button.
4.10.6.2. View Events

Shows the events available at the HMI570 (previously loaded from
disk or uploaded from a device). It is also intended for printing the
events.

Saves events available at the HMI570 to the local disk.
Choose Save To Disk in the menu bar. Click with the left mouse
button on the link and choose “Save this file to disk…” and select the
destination folder.
It is recommended to save events with the ending *.xml.

4.10.6.4. Upload Events

If Upload Events is not accessible, maybe no device is connected
(Section 4.10.4.2 “Connect Device”).
It is possible to upload and view the latest (last saved) 50, 100, 200,
500, 1000, 2000, 5000 or all entries of the Event Recorder.
4.10.6.5. Clear Event Recorder

Clears the Event Recorder in the connected NSD570. After clicking
Clear Event Recorder, pressing the „clear” button confirms the
erasure of the Event Recorder. When the Event Recorder is cleared,
only one entry is shown in the list: Event Recorder cleared.
Note: Clear Event Recorder deletes all events recorded in

an NSD570 device. It is not possible to restore them
afterwards.
4.10.6.6. Import events into a spreadsheet or word processing tool

There are two ways to import events into a third party tool (e.g.
Microsoft® Excel):
1. The third party tool supports an XML file import
Start the tool and import the saved NSD570 event file (*.xml).
2. Copy and paste
Choose the menu Event Recorder, View Events and select the
entire list of events or a part of it. Right click the selected events
and choose “Copy”. Change to the third party tool and insert the
copied events.
4.10.7. Status / Alarm

If Status / Alarm menu is not accessible, possibly no device is
connected (see Section 4.10.4.2 “Connect Device”).
4.10.7.1. Upload Status

Uploads the status information from the connected device. If the
Status Upload was successful, the following information is displayed:
4.10.7.1.1. General status of line interfaces

Loop Test
If a loop test has passed, then the transmission time of the loop test is
also indicated. Else „Loop test did not pass!” is shown without

transmission time. In some device operation modes, e.g. “Teed”, the

Loop Test is not available and „Loop test is not supported in this
mode” is shown.
Line interface in 1+1 operation mode (1+1 Device Mode only)
Either ‘is active’ or ‘is inactive’ is displayed.
4.10.7.1.2. Status of Analog Interface G3LA

Cyclic Redundancy Check (CRC)
The results of the CRC memory checks are shown.
Signal to Noise Ratio (SNR) (NSD570 Analog Interface only)
The Signal to Noise Ratio (SNR) in 4 kHz noise bandwidth is
displayed.
Note: The Signal to Noise Ratio (SNR) is only displayed in

HMI570 when the NSD570 Analog is in guard state
(i.e. the SNR is not displayed when the device is
receiving command signals).
Rx Level (NSD570 Analog Interface only)

Receive level in dBm.
Tx Level (NSD570 Analog Interface only)
Transmit Level in dBm.
measurement do only have an adequate accuracy if
the EOC is switched off!
4.10.7.1.3. Status of Digital Interface G3LD

The results of the CRC memory checks are shown.
Bit Error Rate (BER) (NSD570 Digital Interface only)
The Bit Error Rate (BER) is displayed as 200 sec. average and
262 minutes average.
4.10.7.1.4. Status of Ethernet WAN Interface G3LE

Transmission Time [ms]
The Transmission Time is displayed as 60 sec. average and 4 hours
average.

Packet Loss Rate [%]

The Packet Loss Rate is displayed as 60 sec. average and 4 hours
average.
Transmission Time, standard deviation and min/max
The Transmission Time standard deviation is displayed as 60 sec.
average and 4 hours average. The minimum and maximum
Transmission Times of the last 60 sec. are displayed.
Received packets, Lost packets, Duplicated packets, Old packets,
Unauthenticated packets
The packets statistics of the last 60 sec. and 4 hours are displayed.
Number of disconnections
The number of disconnections in the last 60 sec. and 4 hours are
displayed.
MAC address
MAC address of the Ethernet interface (with HMI570 version 1.47 and
higher).
4.10.7.1.5. Status of Management LAN Interface G3LM

The status information of the Management LAN Interface G3LM is
completely different to the line interfaces. The following information is
displayed after uploading the status.
Synchronized to (primary or secondary) SNTP server
Current SNTP server from where the UTC time is received.
Number of user activity log entries
Current number of user activities recorded in the log file.
SNMP trap sequence number
The trap sequence number indicates the number of SNMP traps which
have been sent since system startup.
Logged in user
User name of the currently logged in user.
SNMP Event Polling state
State of the SNMP event polling. The following states are possible:
• enabled and active: enabled in configuration and running
• enabled but suspended: enabled in configuration but stopped
by user
• disabled: disabled in configuration

Duration of last event polling cycle

Time in seconds used to poll all devices during the last polling cycle.
This time can vary significantly depending on the accessibility of the
devices. If all devices are accessible the time is minimal. It increases
with the number of inaccessible devices.
Time since last event polling cycle
Indicates the elapsed time since the last event polling cycle was
started.
Total number of event polling cycles
Number of event polling cycles performed since system startup.
Number of event polling cycle overruns
Indicates the number of event polling cycles which took longer than the
configured event polling cycle time since system startup.
MAC address
MAC address of the Ethernet interface.
SNMPv3 Engine Id
The SNMPv3 Engine Id is required when configuring the SNMPv3 trap
receiver.
4.10.7.1.6. Status of GOOSE LAN Interface G3LS

The result of the CRC memory check is shown. See Section 3.4.6.4
“Processor environment G3LS” for further information about the
RAM supervision feature.
MAC address
MAC address of the Ethernet interface.
4.10.7.2. Upload Alarm

Alarms are indicated by the red LED on the front plate of the NSD570.
To view the alarms, upload them from the device by clicking on
Upload Alarm.
If no alarms occurred, the message „no pending alarms” is displayed.
Note: Alarms of the Management LAN Interface G3LM

cannot be displayed by LEDs except the Ethernet link
status and Ok/Fail alarm.

4.10.7.3. Trip Counter

The trip counters display the number of sent and received commands
and loop tests of the connected device. The number of unblocking
pulses is also shown. Each device has its own trip counter.
Upload Trip Counter

To upload and view the trip counters, click Upload Trip Counter.
Reset Trip Counter

Mark the checkbox of the command, loop test, unblocking counter(s)
you want to delete and press the “Reset Trip Counter” button. Check
“All” to delete all counters.
4.10.8. Maintenance
If Maintenance is not accessible, maybe no device is connected (see
Section 4.10.4.2 “Connect Device”).
The user must have “modify” permission to execute the maintenance
menu. Users having just “view” permission can only start a loop test.
All other menu entries are prohibited.
4.10.8.1. Manual Loop Test

Starts a loop test.
If the loop test passes, the transmission time is displayed. If the loop
test fails, an error message will appear and no transmission time is
shown. The loop test state and the transmission time can be viewed in
the status (see Section 4.10.7.1. “Upload Status”). A loop test can also
be started by pushing the “Loop Test” button on the front plate of the
NSD570.
4.10.8.2. Reset Device

Resets the connected device. After downloading a firmware or a
configuration, you always have to reset the device. The link gets
disturbed when a reset is executed!

the “Reset Device” in the Maintenance menu of the
HMI570 should not be activated, as this causes the
NSD570 to be re-initialized and thus be blocked for
approx. 10 seconds.

4.10.8.3. Previous Configuration

When downloading a configuration, the device stores the previous
configuration to fall back on in case the downloaded configuration
does not work as expected.
Execute Previous Configuration to switch to this fall back configuration
and reset the device.
4.10.8.4. Set Time and Date

Adjusting the Real Time Clock (RTC) of the device with the
“HMI570 PC”, date and time are taken from the PC/Notebook
connected to the device.
Note: The time and date of the PC/notebook must be

correct to execute this function.
Adjusting the Real Time Clock (RTC) of the device with the
“HMI570 LAN”, date and time are taken from the NSD570 LAN
Interface.
Note: The time and date of LAN Interface must be correct to

execute this function, see 4.14.4 “LAN Interface”.
“Set Time and Date” executed with a connection to a remote device

over EOC will mirror the time of the local device to the remote device.
Therefore, check first the time and date of the local device.
4.10.8.5. Get Time and Date

Shows the current time and date of the connected device. To adjust
time and date, see Section 4.10.8.4. “Set Time and Date”.
4.10.8.6. Device Communication

The baud rate of the RS-232 connection to the connected NSD570 is
changeable. There are three possible values: 57’600, 19’200 and
9’600.
To keep the connection to the device working it is necessary to set the
baud rate of the HMI570 accordingly.
Choose HMI570 Options and then Device Communication. Set the
“RS-232 baud rate” to the same value as in Maintenance / Device
Communication. Click on update to accept or cancel to skip.

Note: 57’600 baud is the default baud rate. To connect a

NSD570 with changed baud rate it is necessary to set
the baud rate of the HMI570 accordingly.
4.10.8.7. Set WAN Password (NSD570 Ethernet WAN Interface only)

To set the WAN password used for the key to protect the Ethernet
packets click on Set WAN Password. Enter and confirm the new
password.
It is strongly recommended to change the default
Note:
password when commissioning a new Ethernet line
interface the first time. Furthermore, it is strongly
recommended to comply with the following password
handling notes:
• The password should consist of a minimum of
eight characters.
• The password should contain letters, numbers
and “special” characters.
• The password should be changed at least
annually (or more frequently - depending on the
risk).
4.10.8.8. Firmware Download

To download a new firmware, click on Firmware Download. The link
gets disturbed while using this function!
After a successful firmware download, reset the device. This will
activate the new firmware. This step is obsolete for HMI570 version
1.13 or higher. The reset of the device will be done automatically. The
firmware version can be viewed by clicking on Firmware Versions in
the Configuration menu after uploading the configuration from the
device.

Note Please read 1KHW000896 “NSD570 Firmware

Download Description” before executing a Firmware
Download.

4.10.9. Commissioning
4.10.9.1. Line Interfaces

In the Commissioning menu you can put the device into test modes.
Depending on the connection type (remote, local) you can start a
Remote Test Mode respectively a Local Test Mode when your
connection is local. The user must have “modify” permission to start /
stop test modes.
To start a test mode, press the Start Local / Start Remote Test Mode
button.
A yellow warning message appears in the header of the HMI570. This
indicates that the device is in a test mode.
To stop the test mode, press the Stop Local / Stop Remote Test
Mode button. The warning will disappear when the Test Mode is
stopped. The link gets disturbed while using this function!
For details refer to Sections 3.5.18.4 “Local Test Mode” and 3.5.18.5
“Remote Test Mode”.

test mode).
Click on “Info” underneath Commissioning at the bottom of the menu

line to read out MAC address of the Ethernet line interface.
4.10.9.2. GOOSE LAN Interface

This menu provides the start and the stop buttons of the
commissioning functions provided by G3LS. In this special test mode,
the G3LS device supports transmitting commands with quality test flag
set to “true” according to IEC 61850-7-3. For details refer to Section
3.5.19 “Test facilities for the GOOSE LAN Interface”.
Caution When a user is logged in with only “view”

permission, it is not possible to disable the device.

4.10.10. Exit HMI570

Click on the “Exit” button to end and exit the application.
The HMI570 PC shuts down the server and closes the browser
window. If the browser shows a dialog “Do you want to close this
window?” click the “Yes” button. If the browser shows a message
“can't reach this page” (or similar) after clicking on the “Exit” button, the
window can be closed manually.
The HMI570 LAN shows the message “Please close the browser”.
Then you can manually close the browser window.
Note: Do not close the browser window manually before

clicking the Exit button.
4.11. Alarm Polling
Note Before HMI570 Version 1.14 the Local Alarm Polling

functionality was only provided with the LAN
Interface G3LL, plugged into the NSD570 rack and
connected over LAN / WAN / Intranet / Internet.
Formerly, this feature was simply named Alarm
Polling.
Starting from HMI570 Version 1.14 the old Alarm
Polling functionality is renamed into “Local Alarm
Polling” and is available for both versions of HMI570
LAN and PC.
The Local Alarm Polling functionality of the HMI570 (further in the

document it is referred to as Alarm Polling) polls NSD570 devices in
the same substation interconnected by the station bus for their alarms.
The devices to be polled must be configured in the Device list (see
Section 4.11.4 “Configure Alarm Polling”).
To work with the Alarm Polling the user has to be logged in.
Note It is not possible to connect any devices for any user

while Alarm Polling is running.
The Alarm Polling can only be started when no device is connected.
Caution Only one Alarm Polling can be started for all users
at a time (see Section 4.11.13 “Multiple users”).

Substation A
Station bus
TPE1 TPE2
120 121
NSD570 A3
TPE1 TPE2
110 111
NSD570 A2
TPE1 TPE2 LAN LAN / WAN

100 101 Interface
NSD570 A1
Device
address
HMI570
LAN
4-Alarm Polling.vsd
Fig. 4-6 Alarm Polling over LAN Interface in an NSD570 network
Substation A
Station bus
TPE1 TPE2
120 121
NSD570 A3
TPE1 TPE2
110 111
NSD570 A2
TPE1 TPE2
100 101
NSD570 A1
RS 232 Device
address
HMI570
PC
4-Alarm Polling_PC.vsd
Fig. 4-7 Alarm Polling over RS-232 Interface in an NSD570 network

In the above examples, the LAN Interface G3LL in the rack NSD570
A1 as well as the HMI570 connected to the NSD570 A1 over the RS-
232 port can poll all NSD570 devices that are interconnected by the
station bus (these are the devices with address 100, 101, 110, 111,
120 and 121).
If the LAN Management Interface G3LM (instead of G3LL) is part of
the system above, the local alarm polling of the “HMI570 PC” has to be
used.
The result of every Alarm Polling cycle is displayed in the
“HMI570 LAN” or “HMI570 PC” by the browser running on the
PC/Notebook.
4.11.1. Impact when the Alarm Polling is started
Log in, Log out It is possible to log in and out while the Alarm
Polling is running. But only logged in users can
work with the Alarm Polling.
User Administration Always possible.
Connect device Only possible when Alarm Polling is stopped.
Configuration It is possible to load from disk and save to disk
when Alarm Polling is started.
Event Recorder It is possible to load from disk and save to disk
when Alarm Polling is started.
Alarm Polling Returns to the graphical view or to the entry
screen, depending whether the Alarm Polling is
started or not.
HMI570 Options Do not change Device Communication
parameters during Alarm Polling!
Exit HMI570 Alarm Polling will be stopped automatically
before exiting.
The table below shows all the functions of the Alarm Polling and when
they are executable:
Started Stopped
Start Alarm Polling X

Stop Alarm Polling X
Configure Alarm Polling X
Graphical View X

Started Stopped
View entire logfile X X

View latest 50 entries X X
Clear entire logfile X
Refresh page X
Stop refreshing X
Start Auto Pop-up X
Stop Auto Pop-up X
4.11.2. Start Alarm Polling

Starts the Alarm Polling for all users and shows the graphical view of
the devices (see Section 4.11.5 “Graphical View”). Please be patient,
as this can take a long time (especially when an analog device gives
no response) and all the devices in the list are polled once before the
view appears.
4.11.3. Stop Alarm Polling

The Alarm Polling stops for all users.
4.11.4. Configure Alarm Polling

Different settings of the Alarm Polling functionality can be configured
here.
The “Device List” shows the configurable parameters and the device
list.
Entering devices in the Device List:
Type in the address of the device and mark the checkbox if you want
to poll its remote peer as well. Click the “Add new device” button.
Note: The device address must be in the range of

1 … 240.
The remote polling is only effective when the connection over EOC is
enabled in the configuration.
Changing devices in the Device List:
Click on the “Edit device” button next to the device and make your
changes. Click on the “Change” button.

Deleting devices from the Device List:

Click on the “Edit device” button next to the device. Click on the
“Delete Device” button. There is no other way to restore an
accidentally deleted device than to add it anew.
Changing Polling Parameters:
Polling Cycle: Select the desired polling cycle time (ranges from
5 seconds to 24 hours).
The polling waits at the end of each cycle until the specified time is
over (counted from the start of the cycle).
Note: If the polling of all devices takes longer than the

selected Polling Cycle, the polling continues
immediately with the first device.
Auto Pop-up:
If the checkbox is selected, the graphical view pops up every time an
error/alarm occurs. This setting is the general setting for all users.
Each user can stop it individually, when this feature is switched on
(see Section 4.11.12 “Stop Auto Pop-Up”).
Logfile:
Select the logfile checkbox to log each polling cycle into a log file. It is
only possible to create a log file in the HMI570 LAN version when the
polling cycle is set to 1 hour or higher and in contrast 1 minute or
higher in the HMI570 PC version.
To save the changes click on the update button.
4.11.5. Graphical View

Shows the alarm LED picture of the devices. When an alarm occurs, a
click on the picture shows the individual alarm message view.
No Alarm:
Alarms:
No Response:
Note: The red Receive LED means, that the connection

between the device and its peer is disturbed.

Note: The picture “No Response” is shown for any device

when it is not possible to upload the alarms.
4.11.6. View Entire Logfile

Shows the entire logfile on screen. When the Alarm Polling is started,
the page refreshes itself every 5 seconds. To stop the Refreshing,
click on “Stop Refreshing”. The page is not updated, although the
logfile is still being written. To refresh the page, choose “Refresh
Page”. When the Alarm Polling is stopped the whole logfile is shown
and cannot be refreshed.
4.11.7. View Latest 50 Entries

The 50 newest entries of the logfile are shown. The page refreshing
works like with the whole logfile. The difference is the amount of
entries and that the oldest of the 50 entries are not shown anymore
when newer entries are in the file.
4.11.8. Clear Entire Logfile

The whole logfile is cleared by clicking on the clear button. The entry
“Logfile cleared by user: (name of the logged in user)” is entered.
Caution It is not possible to “undo” the clearing. All data will

be lost after clearing.
4.11.9. Refresh Page

Refreshes the logfile views.
4.11.10. Stop Refreshing

The logfile stops updating its views. The logfile is still being written.
4.11.11. Start Auto Pop-Up

When the Auto Pop–Up is switched on for all users, the clicking on
“Start Auto Pop-Up” causes the graphical view to pop up as active
window whenever it refreshes itself and any device has an alarm.

4.11.12. Stop Auto Pop-Up

To stop the graphical view from popping up, choose “Stop Auto Pop-
up”. To switch this feature off for all the users, uncheck the
corresponding checkbox in the Alarm Polling Configuration.
4.11.13. Multiple users (in case of HMI570 LAN version)

Because the status of the Alarm Polling affects all users, the
executable features depend also on what the other users are doing.
• Starting and stopping the Alarm Polling does this for all users.
• Only one user at the time is allowed in the configuration.
• No user can enter the configuration while the Alarm Polling is
started.
• No user can connect any device while the Alarm Polling is started.
• No user can start the Alarm Polling while a user is connected to a
device.
• No user can start the Alarm Polling while another user is in the
configuration. Only this user can start the Alarm Polling.
Messages are displayed when other users affect the status of the
Alarm Polling for all users.
4.12. Network Alarm Polling
Caution The Network Alarm Polling function is only available

for the HMI570 PC version 1.14 or higher. This
function is not available on LAN versions of HMI570.
If the Management LAN Interface G3LM is used,
HMI PC version 1.30 or higher is required.
The Network Alarm Polling functionality of the HMI570 (further in the

document it is referred to as network polling) polls simultaneously
several NSD570 LAN Interfaces G3LL with the Local Alarm Polling
running on it, and Management LAN Interfaces G3LM with SNMP
Event Polling running on it. It aggregates information from all NSD570
LAN Interfaces G3LL/G3LM into one single page, thus allowing to see
all alarm information from different substations, interconnected only via
LAN (office LAN / VLAN / secure Internet connection) on one page.
The LAN-Interfaces to be polled must be configured first before
starting network polling (see Section 4.11.4 “Configure Alarm Polling”).
To work with the network polling the user has to be logged in.

Note It is not possible to connect any devices for any user

while network polling is running.
The network polling can only be started when no device is connected

over the RS-232 port.
Substation A Substation B Substation X
Station bus Station bus Station bus
TPE1 TPE2 TPE1 TPE2 TPE1 TPE2

120 121 150 151 190 191
NSD570 A3 NSD570 B3 NSD570 X3
TPE1 TPE2 TPE1 TPE2 TPE1 TPE2

110 111 140 141 180 181
NSD570 A2 NSD570 B2 NSD570 X2
TPE1 TPE2 LAN TPE1 TPE2 LAN TPE1 TPE2 LAN

100 101 Interface 130 131 Interface 170 171 Interface
NSD570 A1 NSD570 B1 ….. NSD570 X1
LAN / WAN / SSL

Secure Internet Connection (HTTPS)
HMI570
PC
4-Network Polling.vsd
Fig. 4-8 Network Alarm Polling
In the above examples, the LAN Interface in the rack NSD570 A1 polls
all NSD570 devices that are interconnected by the station bus within
Substation A (these are the devices with address 100, 101, 110, 111,
120 and 121). In the same way the LAN Interface in the rack NSD570
B1 polls all NSD570 devices within Substation B (130, 131, 140, 141,
150 and 151) and LAN Interface in the rack NSD570 X1 polls all
NSD570 devices within substation X (170, 171, 180, 181, 190 and
191).
The result of each polling cycle from all devices (100, 101, 110, 111,
120, 121, 130, 131, 140, 141, 150, 151, 170, 171, 180, 181, 190 and
191) is displayed in the HMI570 Client running on the PC/Notebook.
4.12.1. Start Network Alarm Polling

To start the Network Alarm Polling, choose Network Alarm Polling in
the main menu bar and then Start Alarm Polling from the submenu.
Press the “Start” button to start the Network Alarm Polling. Please be
patient, as starting of network polling can take some time (especially
when the network is overloaded, or the network connection is slow).
After Network Alarm Polling has been started HMI570 redirects to the

graphical view of the current polling situation of a network (see Section

4.11.5 “Graphical View”).
If the Start Alarm Polling sub-menu is not active, the Network Alarm
Polling has already been started before.
During the Network Alarm Polling start-up, HMI570 PC connects to
each configured LAN Interface. It automatically logs in to HMI570 LAN
version on each LAN Interface using the current user name and
password and then automatically starts Local Alarm Polling on the
LAN Interface (if it was not started before by another user).
If the connection to LAN Interface cannot be established (for example
due to network problems or wrong IP address) the message “Error!
Cannot connect to the target” is displayed.
If the current HMI570 PC user does not have rights to login to HMI570
LAN on the LAN Interface G3LL, the message “Error! Wrong user
name or password” is displayed.
4.12.2. Stop Network Alarm Polling

To stop the Network Alarm Polling, choose Network Alarm Polling in
the main menu bar and then Stop Alarm Polling from the submenu.
Press the “Stop” button to stop the Network Alarm Polling.
If the Stop Alarm Polling sub-menu is not active, the Network Alarm
Polling has already been stopped before.
If the Local Alarm Polling on LAN Interface was started by the network
polling, it will be stopped automatically together with the Network
Alarm Polling. If the Local Alarm Polling on LAN Interface was started
before and network polling just “joined” it, the Local Alarm Polling on
the LAN Interface will not be stopped by the network polling.
4.12.3. Configure Network Alarm Polling
Note: Before configuring Network Alarm Polling, the Local

Alarm Polling on each LAN Interface G3LL has to be
configured first. See Section 4.11.4 “Configure Alarm
Polling” on how to do it.
On the Management LAN Interface G3LM the SNMP
Event Polling has to be configured first. See Section
4.10.5.3 “Edit Configuration” (Management Interface)
for details.

Note: Each LAN Interface G3LL which shall be polled by the

Network Alarm Polling has to have at least one user
with the same username and password as HMI570
PC on which this network polling is running.
The above is not required in case of Management
LAN Interface G3LM.
Note: The certificates of all Management LAN Interfaces

G3LM being polled, have to be stored on the HMI570
PC.
To configure network polling choose Network Alarm Polling in the

main menu bar and then Configure Alarm Polling from the submenu.
It is not possible to configure the Network Alarm Polling while polling is
running. If the Configure Alarm Polling submenu is not active, stop the
Network Alarm Polling first.
To change the Network Alarm Polling configuration, press the “edit”
button.
4.12.3.1. Configure LAN-Interfaces List

The “LAN-Interfaces List” shows the list of LAN Interfaces
G3LL/G3LM which have to be polled by the network polling. You can
edit the following settings for each LAN Interface in the list:
“Position” is an additional parameter which helps to arrange LAN
Interfaces in the desired order in the graphical view page. The polling
information from the LAN Interface with a lower position number will be
at the top of the graphical view page, the LAN Interface with a higher
position number will be at the bottom of the graphical view page.
“Name” is an additional textual name which helps to indentify the
current LAN Interface in the graphical view page.
“IP Address” is an important identifier of a LAN Interface. Each LAN
Interface in the list must have its own IP-Address which is used during
network polling to access this LAN Interface.
IP Address cannot be empty or repeated within the list.
“Connection” is the type of connection which is used to connect to the
LAN Interface. All LAN Interfaces G3LL with HMI570 Version 1.13 or
higher use secure HTTPS connection and all LAN Interfaces with
HMI570 Version 1.12 or lower use the HTTP connection type. The
connection type has to be selected according to the version of the LAN

Interface which is polled. In case of the Management LAN Interface

G3LM the connection type SSL has to be used.
Caution It is strongly prohibited to use HTTP connections

over communication channels that are not secure
(e.g. Internet). In case unsecure communication
channels are used, all LAN Interfaces have to be
updated to the latest version of HMI570 which
supports HTTPS connections.
Button “add new line” adds a new empty line to the list of LAN
Interfaces.
Button “remove all selected” deletes all LAN Interfaces which are
selected by the “select” checkbox on the right side of the list.
4.12.3.2. Configure General Network Alarm Polling Settings

“Page auto-refresh time [s]” is the time in seconds for a browser to
auto-refresh the graphical view of the current polling situation on the
network.
“Information update time [s]” is the time in seconds between each
request from the HMI570 PC Server to a LAN Interface over the
network.
LAN
Reads alarms from LAN IF 1
Reads alarms from LAN IF n

Thread 1
Thread 2
Thread 3
Thread n
…..
HMI 570 PC Server
HMI570
PC
Refresh information from the Server
HMI 570 PC Client (IE browser)
4-Network Polling Inside.vsd
Fig. 4-9 Inside Network Alarm Polling

In Fig. 4-9 the “Information update time” is a timeout in seconds for

each thread during its communication with a LAN Interface. The “Page
auto-refresh time” is the parameter controlling how often a browser
refreshes the information from the HMI570 Server.
A lower “Information update time” means that HMI570 sends more
often information over the network and obviously generates higher
network traffic. However, in this case the delay between an alarm
appearance and its display in the graphic view page is smaller.
A lower “Page auto-refresh time” means that the graphical view page
reloads more often and there is a higher processor load on the
PC/notebook. However, the delay between the alarm appearance and
its display in the graphic view page is smaller.
To not overload the network or PC/notebook with the network polling
running on it, the minimal “Page auto-refresh time” should be at least
5 seconds and the minimal “Information update time” should be at
least 5 seconds as well. Optimal values for these parameters are
10 seconds and 60 seconds respectively.
Note: The maximum delay (the worst case) between the

time an alarm occurs and it is displayed in the
graphical view page equals to:
the time of Local Alarm Polling cycle in a LAN
Interface plus the time of page auto-refresh plus the
information update time.
Press “cancel” button to discard all your recent changes in both

sections (LAN Interfaces list and general settings).
Press “update” button to save all your changes.
4.12.4. Graphical View

Graphical view shows the current status of the Network Alarm Polling.
When the Network Alarm Polling is stopped, the message “Network
alarm polling is stopped” is displayed.
When the Network Alarm Polling is running, the following information is
displayed in the graphical view page:
4.12.4.1. Summary information

Summary information which aggregates all information from all LAN
Interfaces into one table is always shown on the top of the graphical
view page.

Total number of polled G3LL/G3LM
Number of polled G3LL/G3LM which are unreachable
Total number of polled devices
Number of devices with No Response
Number of devices with Alarms
If the line “Number of polled G3LL/G3LM which are unreachable” is

highlighted with a yellow color during network polling start-up, it means
that the connection with some LAN Interfaces (G3LL/G3LM) is not yet
established. After the connection is established with a LAN Interface, it
is removed from the unreachable list.
During running of the networking polling, the yellow color of the line
“Number of polled G3LL/G3LM which are unreachable” means
connection problems with at least one LAN Interface. In this case scroll
down the graphical view page to see which LAN Interface has
connection problems.
If the line “Number of devices with No Response” is highlighted with a
yellow color, it means that at least one of all polled devices has
problems with alarm uploading. In this case scroll down the graphical
view page to see which device has problems.
If the line “Number of devices with Alarms” is highlighted with a red
color, it means that at least one of all polled devices has at least one
alarm. In this case scroll down the graphical view page to see which
device has the alarm.
4.12.4.2. Detailed polling information

Below summary information, the detailed polling information for each
LAN Interface is shown. Information from each LAN Interface is
separated from another by a horizontal line.
The IP address of a LAN Interface is shown in the first line in the
“Device Address” column. Clicking on this IP address opens a new
browser which will automatically be connected to the corresponding
LAN Interface.
Next to the IP address the configured LAN Interface name is shown in
the “Device Name” column.
Next to the LAN Interface name, the current status of the Local Alarm
Polling function, which is running on the LAN Interface, is shown. If the

Local Alarm Polling is running properly without any errors, the time of
the last polling cycle is shown there.
Note: The time of the last polling cycle is gathered from the
LAN Interface and could be different from the time of
the PC/notebook where network polling is running.
Please refer to the “Commissioning Instructions LAN
Interface G3LL” (1KHW001289) on how to set time
and date of the LAN Interface G3LL.
Below the information about the LAN Interface detailed information

about alarms of each device is shown. The graphical representation of
device’s alarms is the same as in the Local Alarm Polling. See Section
4.11.5 “Graphical View” for more details.
A click on the device’s picture opens a new browser which will
automatically be connected to the LAN Interface G3LL from where you
can access this device. This is not possible in case of Management
LAN Interface G3LM (because no HMI570 server and no HMI570
client is running on G3LM). To access a device via G3LM, the Network
Alarm Polling has to be stopped. Then start a new browser with the
HMI570 Client (as described in Section 4.9.1.4 “Start HMI570 PC
Client”) and connect to the required device.
If an alarm has occurred, the description of the alarm is shown below
the device’s picture.
4.12.4.3. Pause Alarm Polling
Note: This function is only available when Network Alarm

Polling is running.
The browser refreshes the graphic view page regularly according to

the “Page auto-refresh time” setting in the Network Alarm Polling
configuration. Select “Pause Alarm Polling” from the menu in the right
side to stop auto-refresh.
The message “The Network Alarm Polling is paused. Information has
not been updated since … local time.” will be displayed at the top of
the page.
After Network Alarm Polling has been paused information can be
refreshed from time to time manually using “Refresh” button of the
browser.
Select “Resume Alarm Polling” from the menu in the right side to
continue the Network Alarm Polling.

4.12.5. Starting and Stopping Local Alarm Polling on LAN Interface

during Network Alarm Polling
It is possible to stop Local Alarm Polling on the LAN Interface while
Network Alarm Polling is still running.
Connect to the LAN Interface using a new browser or just click on the
LAN Interface’s IP Address or one of the device’s picture.
To connect a device through the LAN Interface, the Local Alarm
Polling has to be stopped first.
Note: Do not forget to log in first, in order to be able to stop

Local Alarm Polling and to connect a device.
See Section 4.11.3 “Stop Alarm Polling” on how to stop Local Alarm
Polling on the LAN Interface. It is allowed to stop Local Alarm Polling
while the Network Alarm Polling is still running and displaying the
alarm summary from this LAN Interface.
After the Local Alarm Polling has been stopped on the LAN Interface,
the message “Local Alarm Polling function was stopped on the target”
is displayed in the Network Alarm Polling.
After some time, it is possible to restart Local Alarm Polling on the LAN
Interface where it was stopped before. After Local Alarm Polling has
started, the Network alarm polling again shows the alarm situation on
the LAN Interface.
4.13. Management
This section contains specific items for the Management LAN Interface
G3LM. Some of these are only available if the user is logged in and
connected to G3LM. The corresponding links can be found in the
menu “Management Interface Configuration”.
4.13.1. User Activity Logging

The user activity logging service running on the Management LAN
Interface G3LM logs the most important user activities performed on
G3LM as well as on the line interfaces connected to the station bus.
Every activity is recorded with date, time, device address and device
location (local/remote).
The following user activities are logged:
• Log-in successful (user logged in)
• Log-in failed – Unknown user

• Log-in failed – Wrong password

• Log-out (user logged out)
• Log-out by user inactivity (timeout)
• Configuration download successful
• Configuration upload successful
• Recovery of previous configuration successful
• Firmware download successful
• Configuration download failed
• Configuration upload failed
• Recovery of previous configuration failed
• Firmware download failed
• User account created
• User account deleted
• User password changed successfully
• User password changed unsuccessfully
• Manual reset
• Reset trips
• Date and time set
• System startup G3LM
• New certificate generated
• Log file created/deleted

Loads user activities from the local disk. Click on the „Browse…”
button to choose the file and press the „load” button.

Saves user activities available at the HMI570 to the local disk.
Choose Save To Disk in the menu bar. Click with the left mouse
button on the link and choose “Save” and select the destination folder.
It is recommended to save user activities with the ending *.xml.
4.13.1.3. View
Shows the user activities available at the HMI570 (previously loaded
from disk or uploaded from a device). It is also intended for printing the
user activities.

4.13.1.4. Upload Entries

If Upload Entries is not accessible, maybe no device is connected
(Section 4.10.4.2 “Connect Device”).
It is possible to upload and view the latest (last saved) 50, 100, 200,
500, 1000 or all entries of the user activity logfile.
4.13.1.5. Clear Logfile

Clears the user activity logfile on the connected Management LAN
Interface. After clicking Clear Logfile, pressing the „clear” button
confirms the erasure of the user activity logfile. When the logfile is
cleared, only one entry is shown in the list: Logfile deleted.
4.13.2. User Administration

For security reasons the user accounts for remote access over the
Management LAN Interface G3LM are located on G3LM and have to
be administrated separately from the HMI570 internal ones.
The menu item User Administration provides the functions to add,
remove as well as to modify user accounts on the Management LAN
Interface G3LM. User without “admin” permission can only change the
password.
The available permissions (view, modify, admin) allow the same
manipulation as defined in Section “HMI570 Settings” 4.14.1 “User
Administration and Permissions”.
Remove
User accounts can be removed by checking the select box in the most
right column and clicking on remove all selected.
Add
In order to add a new user account, fill in user name and password,
select one of the three permissions and click add.
Change Access
The user permission can be changed by typing in the user name,
selecting the new permission and clicking change access.
Change Password
To change the password, key in the new password, repeat it and click
on change password.
All users (incl. administrators) can only change their own password.
If a user has lost the password, his account has to be deleted and
created again with a new password by an administrator.

4.13.3. SNMPv3 User Management

In order to use SNMP version 3 protocol, the SNMP users need to be
defined on the G3LM Management Interface.
In the SNMPv3 User Management table, new SNMPv3 users can be
added and existing users can be modified and deleted.
All enabled users defined in this table will have read access to the
SNMP version 3 interface of G3LM.
Add new SNMP user

The SNMPv3 user name must be between 6 and 30 characters long
and must be unique.
SNMPv3 users can either be enabled or disabled. Only SNMPv3 users
which are enabled will have SNMPv3 GET access to G3LM. Disabled
users may still be used to send SNMPv3 traps to the Management
Station.
The SNMPv3 authentication protocol can either be MD5, SHA or
None. In case of None, the authentication is disabled. If the SNMPv3
authentication is enabled, an authentication password needs to be
specified.
The SNMPv3 privacy protocol can either be DES, AES or None. In
case of None, the encryption is disabled. If the SNMPv3 encryption is
enabled, a privacy password needs to be specified.
When SNMPv3 privacy/encryption is enabled, also SNMPv3
authentication needs to be enabled.
Click on “save” to confirm the new user, or on “cancel” to skip.
4.13.4. Certificate Management

The Management LAN Interface G3LM makes use of SSL (Secure
Sockets Layer) for secure communication over IP networks. SSL
provides server authentication by public key certificates. The G3LM
acts as server and sends its certificate during the login process to the
HMI570. If the certificate is already stored on the HMI570 PC, the
connection to G3LM is established without further user interaction.
Otherwise, the user has to manually accept or refuse the certificate.
Details of the login process can be found in Section 4.10.4 “Log-in /
Log-off”.
The menu item Certificate Management provides the functions to
manage certificates on G3LM and HMI570.

Generate on G3LM
This service is only available for users with “admin” permission. In
order to generate a new self-signed certificate, click on generate on
G3LM. This process takes a few seconds, during which certificate
upload should not be performed.
Note: For security reasons the certificate on the G3LM

module should be regenerated periodically.
Upload from G3LM

The certificate stored on the G3LM module can be uploaded by
clicking on upload from G3LM.
Add to HMI store

Once the certificate has been uploaded from G3LM, it can be saved on
the HMI570 PC by clicking on add to HMI store.
Import Certificate
G3LM certificates which have been uploaded on other PCs can be
imported and added to the local HMI certificate store by clicking on
import certificate.
Export Certificate
In order to distribute locally stored certificates to other HMI570 PCs,
they can be exported by selecting the check box in the most right
column and clicking on export certificate.
Delete
Certificates can be removed from the local HMI certificate store by
selecting the check box in the most right column and clicking on
remove all selected.
4.13.5. Start SNMP Event Polling

The SNMP event polling can be started by clicking on this link. It is
only active if the alarm polling is currently suspended.
4.13.6. Stop SNMP Event Polling

The SNMP event polling can be stopped by clicking on this link. It is
only active if the alarm polling is currently running.

4.14. HMI570 Settings
4.14.1. User Administration and Permissions

In this menu item, users can be added or deleted; permissions and
passwords can be changed.
Log in as a user with “admin” permission, e.g. Administrator.
Click on User Administration.
Add new User

Type the name of a new user into the text field User name, set the
User Permissions, enter a Password and Confirm Password, click
on the “Add new user” button to add the new user to the list.
Edit and Delete User

Click on “Edit user” button to change user permissions or to delete the
user.
Select the new User Permissions and click on the “Change user
permissions” button.
Click on “Delete user” to remove the user or click on “Back” to skip.
To change a password, click on the “Change password” button for
the wanted user, type in the new password under Set New Password
and Confirm Password. Click on “update” to save the new password,
or on “cancel” to skip.
User Permissions
View: a user with view permission can monitor an NSD570 but he/she
can neither disturb a link nor clear any data stored on the NSD570. For
details see the table below.
Modify: a user with modify permission can monitor the NSD570 and
can make changes to the configuration of a device. Some functions
that could disturb or disable a running NSD570 can also be executed.
For details see the table below:
Action View Modify

Permission Permission
Load/save configuration from/to disk X X
Load/save event recorder from/to disk X X
Connect and disconnect device X X
Upload status, alarm and trip counter from X X
device
Upload configuration and event recorder X X

Action View Modify

Permission Permission
from device
Discard configuration in HMI X X
Execute manual loop test X X
Reset device X
Reset trip counter X
Set time and date X
Firmware download X
Change baud rate for device X
communication
Clear event recorder of device X
Download configuration to device X
Execute commissioning functions X
Export/import HMI570 settings X
Table 4-2 Permissions “View” and “Modify”
Admin: admin permission allows the user to access the User

Administration menu and make changes to the user settings, as
described above.
On the Management LAN Interface G3LM, admin permission
additionally allows the user to generate new certificates and clear the
user activity log.
The permissions are also displayed in the green Status Box when a
user is logged in.
4.14.2. Change password

A user without admin permission can only change his/her own pass-
word.
Log in as a user without “admin” permission, e.g. Operator.
Click on Change Password in the menu HMI570 Settings.
The logged in user is prompted to type in a new password under Set
New Password and Confirm Password. Click on “update” to save
the new password, or on “cancel” to skip.

4.14.3. Device Communication

These settings refer to the RS-232 connection.
Set the COM port number for your serial connection to the NSD570,
choose the baud rate and turn on/off the handshake protocols. If you
have enabled “RTS/CTS In”, you also have to enable “RTS/CTS Out”
and vice versa.
Click on “update” to accept or “cancel” to skip.
Note: The HMI570 settings are stored and become effective

in all HMI570 sessions.
4.14.4. LAN Interface
Note: This menu is only available with the HMI570 LAN and
contains LAN Interface G3LL specific options.
The date and time of the LAN Interface G3LL is displayed here. This
time must be correct to set the date and time of a connected NSD570
Device (see 4.10.8.4 “Set Time and Date“).
Please refer to the “Commissioning Instructions LAN Interface G3LL”
(1KHW001289) on how to set time and date of the LAN Interface.
The button “Reset communication” disconnects all devices, even the
devices that are connected by other users are disconnected.
Note: This function can cause unexpected malfunctions to

other users. Use this function just in case of a
communication error.
4.14.5. Export Settings
Note: Export/import of HMI570 settings is only available for

the HMI570 version 1.14 or higher.
Only users with “admin” permissions can export and
import HMI570 settings.
This function exports all current HMI570 settings such as device

communication settings, Local Alarm Polling and Network Alarm
Polling settings, into a single zip file which can be stored on the disk
and imported again.

Choose Export Settings in the menu bar. Click with the left mouse
button on the link, choose “Save this file to disk…” and select the
destination folder where to store the zipped settings.
4.14.6. Import Settings

This function imports all HMI570 settings from a zip file which was
created before by “Export Settings” function.
Choose Import Settings in the menu bar. Click on the “Choose File”
button to select an appropriate zip file from the local disk and click on
the “load” button.
Note: It is only possible to import settings from the same

type of HMI570 (LAN-version from LAN-version and
PC-version from PC-version).
4.14.7. About
This menu shows information about the version of the HMI570 and of
software used in this product. A link allows visiting the HITACHI ABB
Communication Networks website.

5. Configuration and Settings
5.1. Introduction
The NSD570 system is configured by means of the user interface
program “NSD570 Human Machine Interface” (also called HMI570)
supplied with it. The user interface program runs on a PC connected to
the RS-232 interface of the NSD570 rack or connected via Ethernet to
the optional LAN interface G3LL/G3LM.
The configuration of the NSD570 has to be done according to
document “Programming and Testing Instructions NSD570”
(1KHW000898-EN).
The two major steps of the procedure are:
1. Programming and
2. Testing
Each of these steps consists of a number of substeps with associated
instructions listed in the document. Each substep is documented in a
report to be filled in during the procedure. Templates for these reports
– one for programming and one for testing - are included in the
document. These reports should be kept for reference as long as the
equipment is in use.
Programming is done with the equipment not powered. Few hardware
programming is made by inserting or removing jumpers. Software
settings are entered via the HMI570 menu “Configuration”. Usually
these settings are saved to a file, which is downloaded into the
equipment later during testing of the system.
Note: The configuration download operation will only be

successful when the system components (including
the HMI570 program) are compatible. To verify this,
refer to document “Compatibility requirements for
NSD570” (1KHW000902-EN). In case of uncertainty,
use the newest available HMI570 version.
Testing is done with the equipment powered. Some of the test

procedures are supported by the HMI570, menu “Maintenance”,
“Status / Alarm” and “Event Recorder”.
Configuration and Settings August 2021 5-1

5.2. Configuration
From a communications point of view the main parameters of
consequence are:
• Analog channels → bandwidth, center frequencies Tx/Rx, Line
Interface levels
• Digital channels → type, data rate and operating mode of the data
interface
• Ethernet channels→ type, data rate and operating mode of the
Ethernet interface
• security and dependability
For the protection the main parameters of consequence are:

• transmission time
• command prolongation (= trip extension)
• status of the command outputs in case of a link failure
• arranging the command inputs to suit the battery voltage
• If a GOOSE interface type G3LS is plugged into NSD570, the
IEC 61850 related configuration parameters have to be configured.
The corresponding programming instructions can be found in the
document “Programming and Testing Instructions NSD570”
(1KHW000898-EN) which is available in Section 12 “Annex”.
The configuration is complete if all links in the “Configuration” menu
are worked off from “Device Identification” down to “Rack Assembly”
and the editable items are set to the desired values.
5.3. Use of HMI570 files

Data entered into HMI570 as described in Section 5.4 can be saved to
file. The extension of such files is xml. The data can be loaded back
anytime into HMI570 from these files for modifications or for
downloading to an NSD570 terminal connected to HMI570.
To save the data to file, click on “Configuration” in the main menu,
then on “Save To Disk”.
To reload data from a previously stored file, click on “Configuration”
in the main menu, then on “Load From Disk” and finally on the
“Browse” button to choose the corresponding file from your file
directory.
Maybe you have to click on “Discard Configuration” first before a
new configuration can be loaded from file.
To view or print the information recorded in a file after having opened
it, use the “View Configuration” link (full screen display of all settings)
or the various items in the “Edit Configuration” menu.
5-2 August 2021 Configuration and Settings

5.4. Configuration with HMI570

In this section it is explained, how to create a configuration with the
HMI570 for an NSD570 equipment. It is recommended to work through
the next sections in this document and the section A of the document
“Programming and Testing Instructions NSD570” (1KHW000898-EN)
step by step. After that, a configuration is created which should be
stored in a file. This is described in Section 5.3 “Use of HMI570 files”.
5.4.1. Configure device type

Not more than two NSD570 devices have to be configured in the same
rack (TPE 1 and TPE 2). They may be either NSD570 Analog,
NSD570 Digital or NSD570 Ethernet version. “Analog”, “Digital” and
“Ethernet” represent the type of the line interface in use (Analog
Interface G3LA, Digital Interface G3LD or Ethernet Interface G3LE).
There are six default configuration files available for each of these
possible device types (TPE 1 Analog, TPE 1 Digital, TPE1 Ethernet,
TPE 2 Analog, TPE 2 Digital, TPE 2 Ethernet). Choose the one that
fits the desired application by clicking on the “Load From Disk” link in
the “Configuration” menu and click on the corresponding “load”
button on the right side of the Default… .xml file list.
In addition to the line interfaces, the Management LAN Interface G3LM
can also be configured by HMI570. The file “Default_Management.xml”
is a good starting point for its configuration.
If a GOOSE interface G3LS is plugged into TPE 1 or TPE 2 of the
NSD570 rack, it can be configured by HMI570 too. Two default
configuration files for the G3LS hardware are available to start with
(“Default_TPE1_GOOSE.xml” and “Default_TPE2_GOOSE.xml”).
Furthermore, the GOOSE network stack (IEC 61850) needs to be
configured using HMI570 (for details please refer to annex document
“Engineering of GOOSE LAN Interface G3LS”).
5.4.2. Configure device parameters

After a default configuration or a previously created xml file has been
loaded, the device parameters can be altered in order to adapt them to
the protection scheme where the teleprotection equipment is used in.
The possible settings and/or the setting ranges of the parameters that
can be modified are listed in the document “Programming and Testing
Instructions NSD570” (1KHW000898-EN). Some additional informa-
tion, which may be helpful for deciding the appropriate setting, is given
in the following sections.

5.5. General configuration notes
5.5.1. 1+1 Device Operation Mode

When selecting this operation mode, two redundant communication
channels can be set up with two line interfaces in one NSD570 rack,
sharing up to four common Relay Interfaces plugged in TPE 1. There
is no need for duplicated Relay Interfaces plugged in TPE 2. The 1+1
path protection mode is also supported with GOOSE LAN Interface
G3LS (in combination with Relay Interface G3LR, if required).
The line interface in TPE 1 (slot N28) always provides the main
communication channel, whereas the line interface in TPE 2 (slot N58)
provides the stand-by channel. As the main line interface is controlling
the relay interfaces under normal condition, it is recommended to plug
the line interface with the shorter transmission time into TPE 1.
Digital line interfaces of each type (G.703, RS-530, E1/T1, optical) can
be mixed with each other and also mixed with the Analog line interface
or the Ethernet line interface to perform 1+1 operation. A typical
application is a Digital line interface plugged in TPE 1 and an Analog
line interface or an Ethernet line interface in TPE 2. But also two line
interfaces of the same type in TPE 1/2 are possible.
Both line interfaces detect the following four high level alarms and
separately evaluate the same switching criterion according to these
alarms:
• Main Line Interface hardware alarm
• Main Line Interface link alarm
• Stand-by Line Interface hardware alarm
• Stand-by Line Interface link alarm.
The hardware alarm is supplemented with a toggle bit detection. Each
line interface listens to a toggle bit from the other one. If it stops
toggling, a hardware alarm is assumed.
A Main and a Stand-by Channel Failure high level alarm can be
mapped to the G3LR Relay Interface outputs, in order to indicate the
actual state of a particular communication channel regarding quality
and availability.
The control of the relay interfaces G3LR/G3LS is only switched from
the Main to the Stand-by line interface in the following cases:
• Main hardware alarm but no stand-by hardware alarm
• No main hardware alarm, no stand-by hardware alarm and no
stand-by link alarm but main link alarm.
In any other case the Main line interface controls the relay interfaces.

Every time the line interfaces switch the relay interface control from
one to another, an Event Recorder entry in both line interfaces is
generated, indicating whether this particular line interface is active or
inactive.
If a line interface is active or inactive can also be extracted from the
Status, displayed in the HMI570.
Note: When setting up a 1+1 link, it shall be assured that

always the Main Line Interface in TPE 1 is first
configured for 1+1 operation mode while the Stand-by
Line Interface remains in normal operation mode and
with all Relay Interfaces disabled. After successful
start-up of the Main Line Interface, also the Stand-by
Line Interface in TPE 2 can be configured for 1+1
operation mode. Neglecting this compulsory
configuration sequence may lead to erroneous
behavior at the command outputs and the Line
Interfaces.
Note: When setting up a 1+1 link, it shall be assured that

both Line Interfaces are configured totally equal
regarding unblocking, command and alarm settings.
Otherwise unwanted behavior might occur at the
command outputs.
5.5.2. Status of the command outputs during a link failure

For detecting a link failure, each type of Line Interface uses specific
low level alarms:
• Analog Line Interface
- SNR alarm
- Rx level alarm
• Digital Line Interface (G.703, E1/T1, Optical)
- BER alarm
- AIS / LOS / LOF / LFA
- Wrong remote digital address detected
• Digital Line Interface (RS-530)
- BER alarm
- pattern synchronization error
- Wrong remote digital address detected
• Ethernet Line Interface
- LOS
- 2 consecutive guard packets lost

The response of the command outputs to a link failure alarm can be

set by means of the HMI570. The following settings are possible:
a) are unaffected (state according to trip signal evaluation)
The command outputs continue to correspond to the current status
of tripping signal processing, i.e. they do not respond at all to the
alarm.
b) are set to guard state (blocked)
The command outputs are set to their quiescent states (= no
tripping signal).
c) retain in state prior to link failure (frozen)
The command outputs retain the statuses they had immediately
prior to the alarm detection.
d) direct to guard state, others to command state
The command outputs configured for direct tripping are set to
guard state and the command outputs configured for permissive
tripping or blocking are set to their tripped states.
These settings apply to all signals in the case of units equipped for
several commands.
Alternative a) is the default setting when the units are supplied from
the works. With this setting the NSD570 responds normally to changes
in the status of the input signals. This is permissible in spite of the
alarm condition, due to the high security of tripping signal evaluation.
Sometimes setting b) is preferred to setting a), for example, when
redundant sets of communications equipment are installed.
Setting c) is used when the status of the command outputs - that they
had in the last alarm free condition - shall be “frozen”.
Setting d) is only used in seldom cases with overreaching or blocking
protection schemes having special logic and in certain instances for
blocking auto-reclosure relays.
The responses of the command outputs according to b) and d)
become effective after an internal alarm processing time (e.g. less
than 1 second for low Rx-level alarm) from the instant the alarm
condition arises and remain so throughout the alarm condition and for
a further processing time of the same quantity after it disappears. The
pick-up time and the hold time can be further delayed by 0 …15
seconds. This might be necessary if, for example, clamping of the
command outputs should be avoided in case of recurrent noise bursts
on the power line, produced by switching operations involving slow
speed isolators. The interference so generated is characterized by
high amplitude and relatively long duration of up to 8 seconds.

Note: Since the command outputs only respond after the

above mentioned pick-up time, “freezing” of the
outputs - setting c) - even in case of a continuous
command requires this delay to be set to zero.
The command prolongation times have to be set to a
value higher than the alarm detection time (i.e.
> 0.7 sec for NSD570 Analog and > 0.1 sec for
NSD570 Digital) to ensure a steady output signal.
In case of the NSD570 Ethernet the command
prolongation times have to be set to a value higher
than the configured Guard Packets Sending Interval.
5.5.3. Link Propagation Time

A valid cyclic or manual loop test must be received within a definite
time slot (refer to Section 3.5.18.2 “Cyclic Loop Test”). Additional
propagation delay of the communication channel (e.g. radio link,
multiplexer) can be taken into account with the parameter
“Propagation Time” by means of corresponding HMI570 setting. This
parameter must be set to the one way propagation time of the
Propagation Time Configurable 0 … 200 ms in steps of 1 ms
(default = 0 ms)

5.6. Configuration notes for NSD570 Analog
5.6.1. Analog Channel selection

In case of the NSD570 Analog, channel selection means the choice of
transmission bandwidth and channel center frequency. Being able to
select the transmission bandwidth and to set the channel center
frequency in steps of 60 Hz permits the best use to be made of any
“frequency gaps” there may be.
The choice of bandwidth is mainly influenced by two factors:
• desired command transmission time
• free bands available when a communications channel is used for
several purposes
The bandwidth is usually based on the first criterion and can be
chosen with the aid of the table in Section 2 of the Technical Data
NSD570 (1KHW000892-EN); see Section 12 “Annex”). The
bandwidths given are overall values, which apply equally to NSD570
Analog version with one or with several commands.
A good compromise between bandwidth, transmission time, security
and dependability is provided by channels 480 Hz and 960 Hz wide,
which are suitable for most applications. Where shorter transmission
times are desired, wider channels may be selected without
encountering any difficulties and without diminishing the security
against false tripping signals.
60 Hz steps for selecting the channel center frequency enable the
ideal frequency to be chosen for the particular case.
In case of a band limited carrier channel of a multiplex equipment for
example, the NSD570 Analog center frequency should be close to the
center of the carrier channel, because the group delay is lowest there.
In the frequency multiplexing mode, i.e. when several NSD570 Analog
share a common communications channel, the center frequencies
must be chosen such that there is no overlapping of the frequencies of
neighboring NSD570 channels.
A gap between channel frequencies is not necessary, provided that
adjacent NSD570 channels have the same bandwidth and the overall
bandwidth does not exceed 3700 Hz (usable bandwidth is from 300 Hz
to 4000 Hz; examples of channel allocation can be seen in Fig. 3-24 in
Section 3.5.3.3 “Programming of the analog system”). If the
NSD570 channels have different bandwidths, some restrictions have
to be taken into account. Please refer to Table 5-1 in Section 5.6.2
“Parallel operation of analog NSD570s”.

The instructions in Section 5.6.3 “2-wire and 4-wire operation of

NSD570 Analog” must be observed for 2-wire operation.
5.6.2. Parallel operation of analog NSD570s

Several NSD570s may be operated in parallel in a frequency-division
multiplex mode on a four-wire connection. AF channels can thus be
used simultaneously in different systems for different purposes. Since
this reduces the bandwidth available to each NSD570, the
transmission times increase correspondingly.
Parallel operation does not require gaps between frequency bands if
they use the same bandwidth, i.e. the various channels can be placed
adjacent to each other.
Where NSD570 with different bandwidths are operated in parallel, the
following gaps between frequency bands have to be kept, i.e. the
various channels can not be placed adjacent to each other:
Bandwidth Device 1 *1
120 Hz 240 Hz 360 Hz 480 Hz 960 Hz 1200 Hz
120 Hz 0 Hz
240 Hz 60 Hz 0 Hz
Bandwidth Device 2
360 Hz 60 Hz 60 Hz 0 Hz
480 Hz 120 Hz 60 Hz 60 Hz 0 Hz
960 Hz 180 Hz 180 Hz 120 Hz 120 Hz 0 Hz
1200 Hz 240 Hz 240 Hz 180 Hz 180 Hz 60 Hz 0 Hz
2400 Hz 480 Hz 420 Hz 420 Hz 360 Hz 300 Hz *2 240 Hz
2800 Hz 600 Hz 600 Hz 540 Hz *2 540 Hz
*1 The NSD570 channels with 2400 Hz and 2800 Hz bandwidth are not mentioned here because they can not
be combined with other 2400 Hz or 2800 Hz channels.
*2 Since the usable band for the NSD570 is from 300 to 4000 Hz, the resulting overall bandwidth of 3700 Hz
is exceeded with the required gap taken into account!
Table 5-1 Minimum frequency gaps between channels

Where several NSD570s with different bandwidths are operated in

parallel, it is advisable to select the transmit levels (signal powers)
proportional to the bandwidth; this results in identical signal-to-noise
ratios in the remote receivers. The relationship (rounded to 3 dB steps)
between the levels is given in the Table 5-2.
Bandwidth Signal power at a point of zero relative level

2800 Hz 0 dBm0
2400 Hz 0 dBm0
1200 Hz - 3 dBm0
960 Hz - 6 dBm0
480 Hz - 9 dBm0
360 Hz - 9 dBm0
240 Hz - 12 dBm0
120 Hz - 15 dBm0
Table 5-2 Relative levels for different bandwidths
Attention must be paid to correct line terminations when operating

NSD570s in parallel (a maximum of three parallel devices is
recommended). Only one unit may be set to 600 Ohms impedance,
while the others must be set to high impedance. Alternatively, the lines
may be terminated with 600 Ohm resistors at the barrier transformers
and all NDS570s set to high impedance. This is the recommended
setting since the devices can be taken out of operation without
influencing the other devices.
The input impedance is programmed on the Analog Interface G3LA,
see “Programming and Testing Instructions” in Section 12 “Annex”.
The summed voltage of the transmitters operating in parallel must not
exceed 3.5 Vpeak, corresponding to +10 dBm peak envelope power, to
avoid that the transmitters overload each other.
The summed voltage at the receivers operating in parallel has also to
be taken into account. Please refer to Section 5.6.5 “Receive level for
NSD570 Analog”.
Caution When two NSD570 - operated in parallel - are using

single tone commands, then the power boost ratio
must not exceed 6 dB. To allow a higher boost ratio
of up to 9 dB, a gap of 60 Hz has to be introduced
between the two adjacent frequency bands.

5.6.3. 2-wire and 4-wire operation of NSD570 Analog
4-wire operation is recommended.
Caution T-operation requires a 4-wire communication link.
For one unit per pair of cores, 2-wire operation is possible without a
hybrid and frequency gaps; however, the following must be observed:
• Transmitter and receiver must use separate frequency bands, a
frequency gap between them is only necessary if the bandwidth is
different (please refer to Table 5-1 in Section 5.6.2 “Parallel
operation of analog NSD570s”.) or if the power boost ratio exceeds
6 dB when single tone commands are used (to allow a higher
boost ratio of up to 9 dB, a gap of 60 Hz has to be introduced
between the two adjacent frequency bands).
• The NSD570 receiver’s alarm pick-up level must be set to ± 12 dB.
• The Tx/Rx-level must be set 6 dB above the measured receive
guard signal level, i.e. 6 dB higher than for 4-wire operation; the
resulting level margin before alarm release is then 6 dB.
Example: measured receive guard level is –12 dBm, the setting in
HMI570 must then be “Rx Level [dBm]” = “–6”
• The communication link attenuation must be less than 12 dB.
In case of higher link attenuation in 2-wire operation, the transmit and
receive directions must be separated by a hybrid. The permissible link
attenuation then increases in proportion to the transhybrid loss by
some 15 dB. In spite of the use of a hybrid, the transmitter and
receiver are not allowed to use the same frequency band.
Note: Use Rx-AF Signal Output on G3LA (X100/3, X100/4)

for 2-wire operation.
5.6.4. Transmit level and power boosting for NSD570 Analog

The transmitting level can be set in a wide range using the HMI570
(refer to the “Programming and Testing Instructions” in Section 12
“Annex”).
When the communications channel is a leased line, any national
regulations with respect to the transmitting levels of the guard signal
and the tripping signal must be observed.
In case of the NSD570 Analog, the power of the command signal can
be boosted in relation to the guard signal. This is generally what is
meant by power boosting. The ratio between the boosted command
signal and the guard signal is referred to as boost ratio BR and

usually expressed in decibels (dB). Programming is done by means of

the HMI570 and enables the power boost to be set from 0 to 9 dB in
steps of 1 dB. The maximum output level with power boosting,
however, must not exceed +11 dBm!
Boosting the power of the tripping signal is used primarily in two cases:
• When using leased lines for which regulations permit only a low-
power guard signal, but a higher tripping signal level of short
duration.
• In a multi-purpose system, where the teleprotection equipment is
sharing an AF channel in parallel with speech or data transmission
in a frequency multiplexing mode. This is typical with PLC (power
line carrier). In this case, any speech and any modem signal
superimposed on it are switched off whilst tripping signals are being
transmitted so that the total PLC transmitter power is available to
the NSD570. This ensures the best possible signal-to-noise ratio at
the NSD570 receiver. The maximum boost ratio which can be
achieved depends on which other PLC signals can be switched off
during the transmission of a tripping signal.
The suppression of these other signals is initiated by the power boost

criterion output (“BOOST”) on the NSD570, which is a potential-free
and polarity-free solid state output on the module G3LA, non-
conducting in the quiescent state and conducting during a tripping
signal.
Caution If the transmit level is measured by means of the

HMI570 in guard state, the level will vary approx.
2.5 dB because the guard signal is modulated to
transmit data via the EOC. The SNR-value
displayed by the HMI570 will vary as well,
depending on the packets transmitted via the EOC.
The Signal to Noise Ratio (SNR) and the Tx/Rx level

5.6.5. Receive level for NSD570 Analog

In case of 4-wire operation and NSD570 in parallel or in case of
NSD570 in 2-wire operation the maximum Rx line level depends on
the Rx Level settings made by means of the HMI570.
Table 5-3 shows the maximum Rx line level (peak voltage) against the
Rx Level setting. The peak line level is equal to the sum of the peak
voltages of the guard signals of all parallel NSD570 at the Rx input,
multiplied by the boost ratio. If the line level exceeds 3.32 Vp, an
attenuator must be placed in front of the Rx input, reducing the level
below 3.32 Vp. However, for 2-wire operation, the attenuator will
reduce also the Tx-signals. This can be avoided by separating the Tx-
and Rx- signals with a hybrid.
Rx Level [dBm] Line Level [Vp] Rx Level [dBm] Line Level [Vp]
0 3.32
-1 2.96 -16 0.53
-2 2.64 -17 0.47
-3 2.35 -18 0.42
-4 2.09 -19 0.37
-5 1.87 -20 0.33
-6 1.66 -21 0.30
-7 1.48 -22 0.26
-8 1.32 -23 0.23
-9 1.18 -24 0.21
-10 1.05 -25 0.19
-11 0.94 -26 0.17
-12 0.83 -27 0.15
-13 0.74 -28 0.13
-14 0.66 -29 0.12
-15 0.59 -30 0.10
Table 5-3 Rx level setting and maximum line level
Note: The NSD570 Analog does not support the measuring

of the internal Rx level, the table above therefore
represents the levels calculated for the line side.
5.6.6. NSD570 Analog over PLC equipment ETL500 or ETL600

The standard connection of the NSD570 to the PLC is via 4-wire port
AF4 on the AF interface board type O4LE of ETL500 or ETL600. The
level at the port has to be set to –10 dBm. This port allows boosting of
the ETL whenever an NSD570 command is transmitted.

The NSD570 boost control output must be connected to the external

boost input of the ETL on the O4LE board. The voltage supply for the
signal is provided by ETL/O4LE.
Note: When using the NSD570 via PLC equipment type

ETL, boosting should be disabled on the NSD570, but
enabled on the PLC equipment (since the power
boost ratio depends on which facilities are using the
PLC channel).
The single channel ETL allows boosting of at most one external

teleprotection equipment. The ETL sets the boost ratio for the NSD570
signal as high as possible, but not higher than 8 dB.
The dual channel ETL allows independent boosting of up to two
external teleprotection equipment, one in channel 1 and the other in
channel 2. Boosting of the NSD570 in channel 1 has priority over
boosting of the NSD570 in channel 2.
The triple channel ETL allows independent boosting of up to three
external teleprotection equipment, one in channel 1, one in channel 2
and the one in channel 3. Boosting of the NSD570 in channel 1 has
priority over boosting of the NSD570 in channel 2, which in turn has
priority over boosting of the NSD570 in channel 3.
If the ETL is operated with the internal teleprotection equipment
NSD550/NSD600, boosting of NSD550/NSD600 has priority over
boosting of NSD570.
If two or more NSD570 need to be operated over one channel of ETL,
the NSD570 4-wire ports have to be connected in parallel to port AF4
on the O4LE board of ETL. To maintain the impedance of 600 Ohm at
the port, one of the NSD570 must be set to 600 Ohm impedance, the
others to high impedance. Alternatively, the lines may be terminated
with 600 Ohm resistors at the barrier transformers and all NDS570s
set to high impedance. This is the recommended setting since the
devices can be taken out of operation without influencing the other
devices. Similarly, the boost control outputs of all NSD570 also have to
be connected in parallel to the external boost input of the O4LE board.
Care has to be taken that the input and output levels at the O4LE port
AF4 are correctly set. With each of the NSD570 set to an output level
of –10 dBm, the input level to the ETL at O4LE port AF4 must be set
to:
- 10 dBm (PEP) in case of a single NSD570 (default),
- 4 dBm (PEP) in case of two NSD570 connected in parallel,
- 0.5 dBm (PEP) in case of three NSD570 connected in parallel.

The system level must be set to:

- 6 dBm0 in case of a single NSD570 (default),
0 dBm0 * in case of two NSD570 connected in parallel,
+ 3.5 dBm0 * in case of three NSD570 connected in parallel.
* Setting is only possible when selecting “Other signals” as reference
signal
The O4LE output port AF4 of ETL will usually carry more signals than
just the NSD570 signals due to other services such as speech and
data transmitted by the ETL. To prevent the NSD570 inputs connected
to the AF4 port to be overdriven by these additional signals, the output
filter of the AF4 port on the O4LE board of ETL should be enabled.
The bandwidth of the filter must be set such that the frequency bands
occupied by the NSD570 signals are within the passband of the filter.
Refer to Figure 3-10 of the ETL Instruction Manual 1KHL015946-EN
for correct settings of NSD570 center frequency and bandwidth.
Note: The NSD570 may be placed above speech. The

maximum programmable bandwidth for the NSD570
Analog is then 1200 Hz (for that purpose speech must
be limited to 2400 Hz, to 2200 Hz or to 2000 Hz if an
NSD550/NSD600 with ETL-pilot as guard signal is
used, or to 2000 Hz if an NSD550/NSD600 with its
own guard signal is used).
All NSD570 operating modes may be selected when using the

NSD570 with the PLC equipment. If only two commands for
permissive tripping are required, single tone commands are
recommended (since they are virtually independent from the gain
distortion of the communications channel and because they have a
higher dependability, as the signal-to-noise ratio with a single tone
command is better than with a dual tone command).
With dual tone commands selected for the use with the PLC
equipment, the gain distortion of the communications channel must not
vary more than 3 dB within the NSD570 bandwidth. This can be
ensured by proper equalization of the PLC channel, using the ETL built
in equalizer. The additional delay caused by the equalization filter has
to be taken into account.

5.7. Configuration notes for NSD570 Digital
5.7.1. Digital channel selection

In the case of the NSD570 Digital, channel selection means the choice
of the Line Interface on the Digital Interface type G3LD. It may be
either one of the two on-board interfaces (G.703 co-directional or
RS530 / RS-422/V.11) or one of the possible piggyback module
interfaces (E1/T1 or optical). For each interface type a subset of
settings is available (to configure the operating mode or data rate for
example).
The main application of the digital interfaces is either a point-to-point
connection of two distant NSD570 equipment or the interfacing of
NSD570 to a PDH multiplexer or a data circuit-terminating equipment
(DCE).
5.7.2. G.703 interface application notes

A co-directional interface only requires two pairs of conductors
(instead of the four needed by a contra-directional scheme). Each pair
is used to transfer a combined data and clock signal between the two
sets of terminal equipment. The combined signal comprises a 64 kbps
information signal, a 64 kHz bit clock and the 8 kHz octet clock. The
symbol rate of the combined clock/data signal is 256 kBaud.
Transmitter
comb. data / clock signal Tx
Receiver
comb. data / clock signal Rx
G.703 Interface on G3LD PCM Multiplexer
5-G703-Appl-notes.vsd
Fig. 5-1 G.703 interface application
The signals are coupled into and out of the equipment by isolating
transformers such that only the voltage difference between the cores is
processed. Thus, the influence of common mode interference on
signal evaluation depends on the degree of longitudinal balance.
It may be configured whether the transmitted clock/data signal is
synchronized on the internal 64 kHz timing signal only or if the timing
information which is reproduced from the received clock/data signal
shall be used to synchronize the transmitted clock/data signal. When
interfacing NSD570 with a PCM multiplexer, the recommended setting
for the G.703 Tx Clock synchronization is “Rx”, considering the
multiplexer as clock master.

Note: If two NSD570 with G.703 interfaces are directly

connected and operated in a point-to-point
configuration,
• one NSD570 must be configured for synchronizing
as Master (internal clock source), i.e. G.703 Tx
Clock Sync must be configured to none.
• one NSD570 must be configured for synchronizing
as Slave (external clock source), i.e. G.703 Tx Clock
Sync must be configured to Rx.
With these settings a clock loop can be avoided.
Note: Normally the data circuit-terminating equipment (DCE)

with a G.703 co-directional interface provides the octet
timing as described in the ITU-T standard. However,
some modems and converters may not follow these
rules and introduce a bit-shift between octet
boundaries.
The NSD570 Digital will only work in this case if
firmware version 1.23 or higher is used. Please contact
your local representative in order to get a free upgrade
version of the “NSD570 Software & Documentation CD”
including the actual NSD570 Digital firmware version.
5.7.3. RS-530 (RS-422/V.11) interface application notes

The electrical characteristics of this interface conform to the standard
TIA/EIA-422 (RS-422), which is electrically identical to the standards
V.11 (ITU-T), X.27 (ITU-T) and Part 3 of DIN 66259. The data transfer
rate is either 64 kbps or 56 kbps.
The RS-530 (RS-422/V.11) interface on G3LD can be programmed for
the modes of operation described below. The signal designations (SD,
RD, ST, RT, TT) were taken from the TIA/EIA-449 recommendation.
5.7.3.1. Transmit and receive timing provided by the DCE

In this case, the outgoing data signal (SD) is synchronized to the
transmit timing signal (ST) and the incoming data signal (RD) is
sampled at the rate of the receive timing signal (RT).

Transmitter
SD (Send Data)
ST (Send Timing)
Receiver
RD (Receive Data)
RT (Receive Timing)
Data Circuit-Terminating
Equipment (DCE)
RS-530 Interface G3LD
5-RS530-Appl-notes.vsd
Fig. 5-2 RS-530 interface application with Tx and Rx timing by DCE
The basic configuration for the above application is:

RS530 Rx Clock set to “ext. RT”
RS530 Tx Clock set to “ext. ST”
RS530 Rx Clock Sync set to “none”
RS530 Tx Clock Sync TT set to “none”
RS530 Terminal Timing TT set to “off”
When only the ST signal is available from the DCE and shall be
connected externally in parallel to the RT input as shown in Fig. 5-3,
the sampling of the incoming data signal (RD) is synchronized to the
transmit timing signal (ST). The DCE must be configured accordingly,
whereas the same configuration as above applies for the NSD570.
Transmitter
A
B SD (Send Data)
B ST (Send Timing)
Receiver
A
B RD (Receive Data)
B RT (Receive Timing) Data Circuit-

Terminating Equipment
RS-530 Interface G3LD (DCE)
5-RS530-Appl-notes.vsd
Fig. 5-3 RS-530 interface application with Tx and Rx timing by DCE
5.7.3.2. Transmit timing provided by the DCE

The interface only requires the transmit timing signal (ST) from the
DCE. The outgoing data (SD) is synchronized to this clock. The
internal clock used to sample the incoming signal is synchronized by
the data signal (RD).

Transmitter
SD (Send Data)
ST (Send Timing)
Receiver
RD (Receive Data)
RS-530 Interface on G3LD Equipment (DCE)
5-RS530-Appl_notes.vsd
Fig. 5-4 RS-530 interface application with Tx timing by DCE

RS530 Rx Clock set to “internal”
RS530 Tx Clock set to “ext. ST”
RS530 Rx Clock Sync set to “RD”
RS530 Tx Clock Sync TT set to “none”
5.7.3.3. Transmit timing for the DCE provided by G3LD

In this operating mode, G3LD generates its own transmit timing signal
(TT) and transmits it together with the data signal (SD) to the DCE.
The transmit timing signal (TT) can be either synchronized to the
incoming data signal (RD) (clock loop) or derived from the internal
quartz oscillator.
Transmitter
SD (Send Data)
TT (Terminal Timing)
Receiver
RD (Receive Data)
Fig. 5-5 RS-530 interface application with TT for DCE by G3LD

RS530 Tx Clock set to “internal”
RS530 Tx Clock Sync TT set to “RD” or “none”
RS530 Terminal Timing TT set to “on”

5.7.3.4. Transmit and receive timing generated internally (G3LD)

Data is transferred between the G3LD and the DCE without
transmitting a timing information. The receive timing signal is
generated internally in the G3LD and synchronized to the incoming
data (RD). The outgoing data signal (SD) can be transmitted in
synchronism with the incoming data or with the internal clock
frequency of G3LD.
Transmitter
SD (Send Data)
Receiver
RD (Receive Data)
Fig. 5-6 RS-530 interface application with Tx/Rx timing internally

RS530 Tx Clock set to “internal”
RS530 Tx Clock Sync TT set to “RD” or “none”
Note: If two NSD570 with RS-530 interfaces are operated in a

point-to-point configuration, one of them has to be
configured as “Master” (the send data SD are
synchronized on the internal clock only, i.e. Rx Clock
Sync and Tx Clock Sync TT are both “none”) and the
other as “Slave” (the send data are synchronized on the
timing information which is reproduced from the received
data signal, i.e. Rx Clock Sync and Tx Clock Sync TT
are both set to “RD”). With these settings, a clock loop
can be avoided.
For the “Master” station, alternatively the terminal timing
(TT) signal provided by the remote station can be used
as an external clock reference (wired on the ST inputs).

5.7.4. E1/T1 Interface application notes

The E1/T1 interface allows interconnecting NSD570 with a PDH
multiplexer or even with an SDH/SONET add/drop multiplexer
featuring E1/T1 interfaces. Framing, signaling and line coding can be
configured according to prevalent standards.
For data transmission the NSD570 does not utilize the full payload of
the 2.048 Mbps frame (PCM30/31 for SDH access) or 1.544 Mbps
frame (PCM24 for SONET access).
Data are transmitted in the first timeslot (TS1) after the synchronization
pulse. Therefore, in a NSD570 link over a PDH system, only TS1 has
to be connected through the system. For both E1/T1, when using AMI
line coding, additionally TS3 has to be connected through the system.
With this coding, TS3 is used for loss of signal detection.
5.7.4.1. E1 Interface
Depending on the distance (cable length) between the E1 interface
and the communication equipment (e.g. a SDH multiplexer), the
receiver sensitivity can be programmed to short haul for a maximum
cable attenuation of 10 dB or to long haul for a maximum cable
attenuation of 43 dB. Maximum cable length: see “Technical Data” in
Section 12 “Annex”.
The E1 interface is configured to recover the clock for transmission
from the received signal, assuming the connected PDH multiplexer or
SDH add/drop multiplexer is the clock master.
An internal elastic buffer size can be configured individually for the
input and the output circuits. This buffer may help to compensate clock
deviations or clock wander between the internal and the external
timing. Compensation of jitter and detection of slips is also possible by
means of a higher buffer size thus introducing a higher delay. A
compromise has to be found in actual tests with the used
communication equipment regarding high jitter capability versus low
additional delay.
The E1 coding (HDB3 or AMI) and frame format (double frame or
CRC4 multiframe) can be configured to comply with different
communication system interfaces.
Hardware version 2 of the E1/T1 interface has three jumpers for
setting the correct impedance: 120 Ohm for E1 and 100 Ohm for T1.
For E1 operation, all 3 jumpers must be set to position “E1”.

5.7.4.2. T1 Interface
Depending on the distance (cable length) between the T1 interface
and the communication equipment (e.g. a SONET multiplexer), the
receiver sensitivity can be programmed to short haul for a maximum
cable attenuation of 10 dB or to long haul for a maximum cable
attenuation of 36 dB. Maximum cable length: see “Technical Data” in
Section 12 “Annex”.
The T1 interface is configured to recover the clock for transmission
from the received signal, assuming the connected PDH multiplexer or
SONET add/drop multiplexer is the clock master.
An internal elastic buffer size can be configured individually for the
input and the output circuits. This buffer may help to compensate clock
deviations or clock wander between the internal and the external
timing. Compensation of jitter and detection of slips is also possible by
means of a higher buffer size thus introducing a higher delay. A
compromise has to be found in actual tests with the used
communication equipment regarding high jitter capability versus low
additional delay.
The T1 coding (B8ZS or AMI) and frame format (4 frames or extended
superframe) can be configured to comply with different communication
system interfaces.
Hardware version 2 of the E1/T1 interface has three jumpers for
setting the correct impedance: 120 Ohm for E1 and 100 Ohm for T1.
For T1 operation, all 3 jumpers must be set to position “T1”.
5.7.5. Optical interface application notes

fiber optic cables at a data rate of 2.048 Mbps. The optical interface
can be programmed to operate with a direct fiber connection,
FOX515/512 compatible interfaces such as an OTERM or an OPTIF,
FOX615/612 compatible interfaces such as an OPIC2, as well as with
a 3rd party multiplexer equipment that complies with the IEEE C37.94
standard and provides a 1 x 64 kbps teleprotection interface
(IEEE C37.94 only supported by G1LOa).
The correct framing, signaling and line coding is automatically set after
choosing the interface type out of the HMI570 pull down menu.
5.7.5.1. Optical Direct Fiber and Optical OTERM/OPTIF Interface

The G1LO allows interconnecting an NSD570 with a FOX515/512
multiplexer, using one of the optical 2 Mbps access cards, OTERM or

OPTIF. The G1LOa can also be connected to a FOX615/612 interface

such as an OPIC2.
Further, a point-to-point link with a distance of up to 60 km with G1LO,
or up to 240 km with G1LOa and the appropriate SFP transceiver
module, can be realized by connecting two optical interfaces directly.
For data transmission, the NSD570 utilizes a bit orientated proprietary
frame with MCMI coding whereof only channel 1 is used. Other
channels are at free disposal.
In a point-to-point application a byte orientated E1 (PCM31) frame is
used.
Depending on the distance (cable length) between the optical interface
and the communication equipment and its input saturation power, the
laser output power can be programmed for long haul (< -1 dBm) or
short haul (< -17 dBm, default) application, when using G1LO. G1LOa
requires no settings regarding the laser output power since this is done
by choosing the appropriate SFP transceiver module.
The optical interface recovers the clock for transmission from the
received signal, assuming the connected FOX515/512 or FOX615/612
multiplexer is the clock master.
In Optical Direct Fiber transmission only, one G1LOa must be
programmed as clock master, while the G1LOa at the opposite side
must be programmed as clock slave. This setting does not apply to
G1LO.
A communication link over a FOX515/512 or FOX615/612 multiplexer
enables the operation between the optical interface on one side and all
other electrical interfaces of the NSD570, connected to the
corresponding data I/O-board of FOX515/512 or FOX615/612 on the
other side.
Additionally, for the G1LOa, both interface types can be programmed
to enable the Automatic Laser Shutdown feature. This helps to prevent
eye injuries during maintenance work. The laser is shut down when no
optical signal is received.
5.7.5.2. Optical IEEE C37.94 Interface

This optical interface is available with G1LOa and allows inter-
connecting an NSD570 with a dedicated multiplexer interface
according to IEEE C37.94.
For data transmission, the NSD570 utilizes the IEEE C37.94 frame
with 16 bit header, 48 bit overhead and 8 bit data as described in the
corresponding standard. The coding scheme is NRZ.

The optical interface recovers the clock for transmission from the
received signal, assuming the connected multiplexer is clock master.
There is no manual configuration needed (except for ALS, if required).
5.8. Configuration notes common for G3LE, G3LM and G3LS
5.8.1. General
The NSD570 Ethernet interfaces G3LE, G3LM and G3LS are based
on the same hardware module. Therefore, some of the configuration
parameters are similar. This section describes the common part of the
configuration.
5.8.2. Ethernet interface selection

Two possibilities of connecting to G3LE, G3LM and G3LS interface are
available: one RJ45 socket to connect to a 10/100 Mbps electrical
Ethernet and a SFP cage for insertion of various optical SFP modules.
While the RJ45 interface can be used as is, i.e. only an Ethernet cable
must be inserted, the SFP interfacing capability does only consist of
the cage. An accordant SFP transceiver module must be inserted
before the interface is operational.
To select one of the connectors, the sliding switch must be moved
towards the required interface (see Fig. 5-7).

Interface selection switch in Interface selection switch in

position RJ45 connector position SFP module
Fig. 5-7 Optical or electrical interface selection
Please note that only one interface can be active at a time.

Independently from the activated interface, the two LEDs of the RJ45
connector always show the actual interface status:
• Green LED: indicates the presence of a link
• Yellow LED: interface is operating at 100 Mbps connection speed
5.8.3. RJ45 interface configuration

The 10/100 Mbps Fast Ethernet interface can be configured to auto
negotiation or manual mode. In auto negotiation mode the interface
automatically sets the interface speed depending on the data rate of
the connected device.
In manual mode the data rate of the interface can be set to 10 Mbps or
100 Mbps. The operating mode can be configured to half duplex
restricting the transmission of data in one direction at a time (sending
or receiving) or full duplex allowing for simultaneous data sending and
receiving.
These parameters can be set by means of the HMI570 User Interface
Program. For details refer to Section 4.10.5.3 “Edit Configuration”.

Note: Some routing devices may cause problems when

running in auto negotiation mode. In certain intervals
they are repeating the auto negotiation procedure
resulting in link loss during this time. If link losses
occur or the router statistics show connection errors, it
may help to set the Ethernet interface to manual
mode.
5.8.4. SFP module configuration

As SFP modules are operating mostly independent and its parameters
cannot be influenced, there are no special configuration parameters for
the SFP, meaning that neither the data rate nor the operating mode of
the SFP can be set.
The only parameter to be configured is the Automatic Laser Shutdown
(ALS) for optical SFP transceivers. This feature can be enabled or
disabled. ALS shall only be enabled if it is supported by the connected
equipment as well.
The ALS can be configured to off (default) or on by means of the
HMI570 User Interface Program. For details refer to Section 4.10.5.3
“Edit Configuration”.
5.8.5. GPS synchronization

If an external GPS clock is connected to the IRIG-B input of the
NSD570 equipment, the on board real time clock (RTC) can be
synchronized to this clock source.
To enable external GPS synchronization, set the parameter “External
Real-Time Sync (IRIG-B)” to “on”. The default setting is “off”.
This parameter can be configured by means of the HMI570 User
Interface Program. For details refer to Section 4.10.5.3 “Edit
Configuration”.

5.9. Configuration notes for Ethernet WAN Interface G3LE
5.9.1. General
parameters are similar. This section describes the Ethernet WAN
Interface (G3LE) specific configuration. For the description of common
functionality on G3LE, G3LM and G3LS please refer to Section 5.8
“Configuration notes common for G3LE, G3LM and G3LS”.
5.9.2. Ethernet WAN interface configuration

In order to establish a connection, the Ethernet interface parameters
must be set correctly. The local IP address specifies the address of the
local Ethernet interface. This IP address must correspond with the
remote IP address on the remote station whereas the remote IP
address of the remote station must correspond with the local IP
address of the local Ethernet interface as shown in Fig. 5-8.
NSD570 Ethernet local NSD570 Ethernet remote

Local IP address Local IP address
e.g. 192.168.0.2 e.g. 192.168.0.3
Remote IP address Remote IP address
e.g. 192.168.0.3 e.g. 192.168.0.2
Fig. 5-8 IP address configuration
The subnet mask specifies the network class the interfaces are
operating in. The following table gives an overview of IP addresses
and the appropriate subnet masks:
Class IP address range Subnet mask

Class A 0.0.0.0 – 127.255.255.255 255.0.0.0
Class B 128.0.0.0 – 191.255.255.255 255.255.0.0
Class C 192.0.0.0 – 223.255.255.255 255.255.255.0
The default gateway is the address of the node the NSD570 Ethernet
uses as access point to the IP network, i.e. a router. Typically the
default gateway IP address is xxx.xxx.xxx.1 e.g. 192.168.0.1, but this
may vary.

The NSD570 Ethernet uses a UDP/IP based protocol. The UDP port
number to be used must be configured, there are separate UDP ports
for the Teleprotection transmission and the Embedded Operation
Channel (EOC). The following table shows port ranges according to
Internet Assigned Numbers Authority (IANA):
Port range Naming

0 – 1023 Well known ports
1024 – 49151 Registered ports
49152 - 65535 Private ports
The ports on local and remote site must correspond, otherwise the
communication will fail. In order to avoid conflicts with registered ports
it is recommended to use port numbers in the private port range. The
default port numbers are 49152 for Teleprotection transmission and
49153 for EOC transmission.
These parameters can be configured by means of the HMI570 User
Configuration”.
5.9.3. Priority settings on transport layer (IPv4 Routing)

Teleprotection commands are time critical data that should be
transmitted as fast as possible through the network. In addition to the
link layer prioritization, IP offers possibilities to set priorities and handle
high priority traffic faster if the network is administrated accordingly.
The NSD570 Ethernet supports IP priority settings.
The “Differentiated Services” field (DS field) in the IP header is used
for packet classification purposes: “Differentiated Services Code Point”
(DSCP), a value with 6 bits. Explicit Congestion Notification (ECN)
occupies the least-significant 2 bits of the IPv4 Type of Service field
(TOS). The DS field and ECN field replace the outdated IPv4 TOS field
(8 bits).
The parameter range for DSCP is 0 – 63, for ECN 0 - 3.
This DS field in the IP protocol header makes prioritization of IP
packets possible. According to RFC 2474 and RFC 3168 the DSCP
can be set with this value, allowing for the Differentiated Services
(DiffServ) traffic classification, which places each packet into a limited
number of traffic classes. Please note that the DiffServ model does not
handle prioritization of certain traffic classes – this must be handled by
the network operator. However, DiffServ provides a framework to allow
classification and differentiated treatment.

There are different classes covered by the DSCP setting whereas two
of them are relevant to be set for the Ethernet WAN interface G3LE:
0 – Best Effort (BE) forwarding characteristics, i.e. no priority.
46 – Expedited Forwarding (EF) covering the characteristics of
low delay, low loss and low jitter suitable for real-time
applications (default setting).
Interface Program. For details refer to Section 4.10.5.3.
5.9.4. VLAN ID
In order to run the transmission on a separate virtual network, the
NSD570 Ethernet interfaces offer the setting of a VLAN ID according
to IEEE 802.1q. The parameter range is 0 - 4094, the default setting is
1 and the VLAN ID tagging option is disabled per default.
Configuration”.
5.9.5. Link layer priority settings

Ethernet offers possibilities to set priorities and handle high priority
traffic faster if the network is administrated accordingly. The NSD570
supports the Ethernet priority.
Priority tagging of the Ethernet frame according to IEEE 802.1p is
supported. The parameter range is between 0 - 7 (highest priority), the
default value is 5. As this field is part of IEEE 802.1q (VLAN tagging)
VLAN tagging must be enabled in the HMI570 User Interface program
first.
5.9.6. Supervision and alarm settings

The transmission channel is supervised by guard packets which are
sent in user programmable intervals. For details refer to Section
3.5.8.1 “Channel supervision”.
The Guard Packet Sending Interval can be set by means of the
HMI570 User Interface Program from 5 ms - 100 ms, the default value
is 5 ms.
If two subsequent guard packets fail to arrive at the remote station, an
alarm is being raised indicating a malfunction of the transmission
channel. Furthermore, the Unblocking signal is being generated which
can be sent to an output of the Relay Interfaces G3LR.

Note: The Guard Packet Sending Interval must be configured

with the same value on the local and remote equipment.
Otherwise the connection will fail and an according alarm
will be raised.
The Transmission Time from the local to the remote station is

measured by means of the Transmission Time Test Interval. Its
parameter range is 100 ms - 10’000 ms, the default value is 1000 ms.
If the transmission time exceeds a certain limit, a warning or an alarm
is being raised. The Transmission Time Warning/Alarm Sensitivity can
be set to Low/Medium/High, the default value is Normal. For details
refer to Section 3.5.15.1 “Transmission Time and Packet Loss
monitoring”.
The Packet Loss Rate is calculated permanently as ratio of received to
actually sent packets. It can be set by means of the HMI570 User
Interface Program in a range of 0.1 % - 10 %, the default value is 1 %.
For details on packet loss monitoring refer to Section 3.5.15.1
“Transmission Time and Packet Loss monitoring”.
5.9.7. Network configuration hints

The Ethernet Line interface alarming and warning features allow for
supervision of the transmission channel and inform the user about bad
channel conditions. Nevertheless, to ensure the required end-to-end
delay, proper engineering of the network is essential. Some proposals
on how to achieve this:
• To ensure low latency, the available bandwidth should be higher
than the total peak traffic generated by all services in the network.
• Bandwidth reservation for Teleprotection traffic per direction shall
be twice the maximum data rate as stated in the Technical Data
(1KHW000892-EN).
• If the network structure contains different routes from the local to
the remote station it is recommended to lead the Teleprotection
traffic over static routes in order to avoid differences in
transmission time, packet re-ordering etc. caused by varying delay
of different routes.
• Use RSTP instead of STP or other routing protocols that provide
fast switchover times.
• Make use of the prioritization mechanisms offered by Ethernet
(Layer 2) and IP (Layer 3) protocols which are supported by the
Ethernet line interface.

5.10. Configuration notes for NSD570 Management
5.10.1. General
parameters are similar. This section describes the Management LAN
Interface (G3LM) specific configuration. For the description of common
functionality on G3LE, G3LM and G3LS please refer to Section 5.8.
The Management LAN Interface G3LM can be accessed either over
the local serial port or over LAN for configuration. Serial connection to
G3LM is only possible if the LAN port is down (unplug the LAN cable).
Before the management LAN Interface G3LM can be accessed over
LAN, the basic IP parameters have to be set. Please refer to the
document “Commissioning Instructions Management LAN Interface
G3LM” (1KHW002232) for the initial set up of G3LM.
5.10.2. Ethernet LAN interface configuration

In order to establish a connection to the Management LAN Interface
G3LM, the IP parameters have to be set correctly. The IP address
specifies the address of the Management Interface.
The subnet mask specifies the network class the Management
Interface is operating in. The following table gives an overview of IP
addresses and the appropriate subnet masks:
Class IP address range Subnet mask

Class A 0.0.0.0 – 127.255.255.255 255.0.0.0
Class B 128.0.0.0 – 191.255.255.255 255.255.0.0
Class C 192.0.0.0 – 223.255.255.255 255.255.255.0
The default gateway is the address of the node the Management

Interface uses as access point to the IP network, i.e. a router.
Typically, the default gateway IP address is xxx.xxx.xxx.1 e.g.
192.168.0.1, but this may vary.
These parameters can be configured by means of the HMI570 User
Configuration”.

5.10.3. VLAN ID
In order to run the transmission on a separate virtual network, the
NSD570 Ethernet interfaces offer the setting of a VLAN ID according
to IEEE 802.1q. The parameter range is 0 - 4094, the default setting is
1 and the VLAN ID tagging option is disabled per default.
Configuration”.
5.10.4. Link layer priority settings

Ethernet offers possibilities to set priorities and handle high priority
traffic faster if the network is administrated accordingly. The NSD570
supports the Ethernet priority.
Priority tagging of the Ethernet frame according to IEEE 802.1p is
supported. The parameter range is between 0 - 7 (highest priority), the
default value is 0. As this field is part of IEEE 802.1q (VLAN tagging)
VLAN tagging must be enabled in the HMI570 User Interface program
first.
5.10.5. SNMP
5.10.5.1. Overview
The Simple Network Management Protocol (SNMP) is a component of
the Internet Protocol Suite and is used in network management
systems to monitor network-attached devices. On the Management
LAN Interface G3LM, SNMP allows management stations to retrieve
alarm and basic device information of NSD570 devices connected to
the RS-485 station bus. With G3LM firmware version 1.19 and higher,
also command and manipulation events as well as trip counter
information can be retrieved.
The Management LAN Interface G3LM supports the SNMPv2-SMI
standard MIB and the Hitachi ABB proprietary NSD570R3-G3LM MIB,
to be found in the HMI570 installation folder (two versions: one
supporting SNMPv1, the other supporting SNMPv2c and SNMPv3).
In order to update the management information base (MIB) on G3LM,
SNMP event polling has to be enabled. The MIB stores basic device
information including device accessibility, as well as all current device
alarms. The MIB tree is shown in the figure below.

enterprises (1.6.6.1)
abb (17268)
utility communication products (2818)
tpe (4)
nsd570 (1)
trapSequenceNumber
device (1) alarm (2) event (3) tripCounter (4) alarmTriggeredTrap/ deviceIsAccessibleAgainTrap /
alarmClearedTrap deviceIsNoMoreAccessibleTrap
deviceTable (1) alarmTable (1) eventTable (1) tripCounterTable (1)
deviceEntry (1) alarmEntry (1) eventEntry (1) tripCounterEntry (1)
<alarmFields> <deviceFields>
<deviceFields> <alarmFields> <eventFields> <tripCounterFields> + trapSequenceNumber + trapSequenceNumber
deviceFields alarmFields eventFields tripCounterFields

deviceAddress (1) alarmDeviceAddress (1) eventDeviceAddress (1) tripCounterDeviceAddress (1)
deviceLocation (2) alarmDeviceLocation (2) eventDeviceLocation (2) tripCounterDeviceLocation (2)
deviceName (3) alarmDeviceName (2) eventIndex (2) tripCounterId (2)
deviceLineInterfaceType (4) alarmDeviceLineInterfaceType (3) eventTimeStampString (3) tripCounterName (3)
deviceIsAccessible (5) alarmId (4) eventTimeStamp (4) tripCounterTxValue (4)
deviceTimeStamp (6) alarmText (5) eventTimeSubMilliseconds (5) tripCounterRxValue (5)
deviceConfigDownloadCount (7) alarmSeverity (6) eventString (6)
alarmTimeStamp (7) eventType (7)
eventData (8)
Fig. 5-9 G3LM MIB Tree
Note:
Italic values in the MIB tree shown above are available with G3LM
firmware version 1.19 and higher.
In case of alarms and command or manipulation events polled from
the NSD570 Line Interfaces, the SNMP agent on G3LM actively sends
traps to up to four network management stations.
5.10.5.2. Device information

The MIB stores the following information of all devices being polled by
the SNMP event polling:
• Device address
• Device location: local (1), remote (2)
• Device name: station name of the Line Interface
• Device Line Interface type: analog (1), digital (2), Ethernet (3)
• Device is accessible: indicates if device is accessible for alarm
polling, not accessible (1), accessible (2)
• Device time stamp: time of last device fields update
• Device configuration download counter (available with G3LM
firmware version 1.19 and higher)

The management station can use the SNMP requests GET and
GETNEXT to retrieve information stored in the MIB.
The device information is initialized after system start up during the
first polling cycle. Information updates are performed whenever a
device becomes accessible again after being inaccessible during
SNMP event polling or when the SNMP event polling is restarted after
being stopped for a while (starting and stopping SNMP event polling is
described in Sections 4.13.5 “Start SNMP Event Polling” and 4.13.6
“Stop SNMP Event Polling”).
5.10.5.3. Alarm information

All current device alarms are stored in the MIB and can be accessed
by the management station using the SNMP requests GET and
GETNEXT.
The table for SNMP alarm events has a capacity for the maximum
number of polled local and remote devices (1 or 2 line interfaces in
max. 32 racks, and their remote line interfaces over EOC, i.e. alarms
of max. 128 devices). However, only the last successfully polled alarm
status of each device is stored in the table for SNMP alarm events (i.e.
all alarms which were active at that time).
An alarm table entry in the MIB contains the following information:
• Alarm device address
• Alarm device location: local (1), remote (2)
• Alarm device name: station name of the Line Interface
• Alarm device Line Interface type: analog (1), digital (2), Ethernet (3)
• Alarm ID: unique identifier of the alarm
• Alarm text: human readable text describing the alarm (as in
HMI570)
• Alarm severity: warning (1) or alarm (2)
• Alarm time stamp: time of alarm detection by the alarm polling
The alarm information in the MIB is updated every polling cycle.
5.10.5.4. Command and Manipulation Event information

With G3LM firmware version 1.19 and higher, also command and
manipulation events are stored in the MIB and can be accessed by the
management station using the SNMP requests GET and GETNEXT.
If enabled, all new command and manipulation events of each
configured local line interface are uploaded in each polling cycle.
When a new event is discovered, a trap is sent to the configured
SNMP management stations.

This feature is only working for polled local devices, because

uploading the data from remote devices over the EOC would take too
long. Remote devices cannot be configured in HMI570 when
command and manipulation event polling is enabled.
The very first time a device is discovered, no trap is sent (usually
during the initial polling cycle). If a device becomes inaccessible, the
events are kept stored internally and will be updated once the device
becomes accessible again. In this case, given that new events
occurred meanwhile, a trap is sent to the NMS station for each newly
discovered command or manipulation event.
The table for SNMP command and manipulation events has a
maximum capacity of 1280 entries. This number divided by the
number of polled local devices gives the maximum number of events
which can be stored per device (maximum 128 events for 10 local
devices, for example). When this number of events in the table is
reached, the oldest events will be dropped from the table for SNMP
command and manipulation events.
A command and manipulation event table entry in the MIB contains the
following information:
• Event device address
• Event device location: local (1)
• Event index
• Event time stamp string (human readable)
• Event time stamp: seconds since the Epoch (Unix time); time of
event in the corresponding line interface event recorder
• Event time stamp: sub-milliseconds
• Event string: human readable text describing the event (as in
HMI570)
• Event type: unique number identifying the event type, matching
each possible event string (useful for non-English environments)
• Event data: off (0), on (1) or occurred (2)
Table 5-4 provides a list of the command and manipulation events that
are polled by G3LM (other manipulation events are not polled, e.g.
loop test sent/reflected/failed).

Event type Event string

0 Rx Command A
1 Rx Command B
2 Rx Command C
3 Rx Command D
4 Rx Command E
5 Rx Command F
6 Rx Command G
7 Rx Command H
10 Tx Command A
11 Tx Command B
12 Tx Command C
13 Tx Command D
14 Tx Command E
15 Tx Command F
16 Tx Command G
17 Tx Command H
19 Unblocking
21 System Startup
22 Set time and date
23 Firmware download
24 Configuration download
25 Loop test button active
29 User reset
30 Event recorder cleared
31 Trip counter reset
33 Previous configuration
54 Automatic reset
Table 5-4 List of polled command and manipulation events
5.10.5.5. Trip Counter information

With G3LM firmware version 1.19 and higher, also trip counters are
stored in the MIB and can be accessed by the management station
using the SNMP requests GET and GETNEXT.
If enabled, all trip counters of each configured local line interface are
uploaded in each polling cycle. The counters are stored to the SNMP
trip counter table. No traps are sent to the configured SNMP
management stations when the trip counter status changes.
uploading the data from remote devices over the EOC would take too
long. Remote devices cannot be configured in HMI570 when trip
counter polling is enabled.

The table for trip counters has a capacity for the maximum number of
polled local devices (1 or 2 line interfaces in max. 32 racks, i.e. trip
counters of max. 64 devices). However, only the last successfully
polled trip counter status of each device is stored in the table for
SNMP trip counters (i.e. all actual counts at that time).
A trip counter table entry in the MIB contains the following information:
• Trip counter device address
• Trip counter device location: local (1)
• Trip counter ID: command A (0), command B (1), …, loop test (10),
unblocking (11)
• Trip counter name: human-readable name of the trip counter (as in
HMI570)
• Trip counter Tx value: current Tx trip counter value
• Trip counter Rx value: current Rx trip counter value
5.10.5.6. Configuration download counter information

With G3LM firmware version 1.19 and higher, the Device Table in the
MIB was extended with the Configuration Download Counter. It can be
accessed by the management station using the SNMP requests GET
and GETNEXT.
In each polling cycle, the first part of the configuration of all configured
line interfaces is requested. The configuration download counter is
extracted and the SNMP Device Table is updated accordingly.
If the counter has changed, a trap is sent to the configured SNMP
management stations.
uploading the configuration data from remote devices over the EOC
would take too long. Remote devices are therefore ignored.
The very first time a device is discovered, no trap is sent (usually
during the initial polling cycle). If a device becomes inaccessible, the
counter is kept stored internally and will be updated once the device
becomes accessible again. In this case, given that the counter has
changed meanwhile, a trap is sent to the NMS stations.

5.10.5.7. Traps
Traps are messages sent by the SNMP agent without being requested
by the management station.
The following traps can be generated by the G3LM agent:
• Cold start trap: sent after system startup
• Device accessible trap: sent whenever a device gets accessible e.g.
after system startup
• Device not accessible trap: sent if a device did not respond during
an alarm polling cycle
• Alarm triggered trap: sent whenever a new alarm has been detected
by the alarm polling
• Alarm cleared trap: sent after an alarm has been cleared
• Event occurred trap: sent after a command or manipulation event
has been detected (with G3LM firmware version 1.19 and higher)
• Device configuration download counter changed trap: sent after a
configuration download counter change has been detected (with
G3LM firmware version 1.19 and higher)
All traps are sent to the configured management stations.
5.10.5.8. SNMP configuration

In order to monitor NSD570 equipment by SNMP, all Line Interfaces of
interest have to be polled by the management LAN interface G3LM
and SNMP has to be enabled.
NSD570 supports SNMPv1, SNMPv2c and SNMPv3. Using the
HMI570 link SNMP Parameters, the SNMP version is configured:
• 1 and 2 (auto): G3LM accepts SNMPv1 and SNMPv2c requests
• 1: G3LM accepts SNMPv1 requests only
• 2: G3LM accepts SNMPv2c requests only
• 3: G3LM accepts SNMPv3 requests only
Follow the step-by-step instruction below to activate all SNMP services
in the SNMP Event Polling configuration (see also Section 4.10.5.3
“Edit Configuration):
1. In case of SNMPv3, connect to the management LAN interface and
add new SNMP users in the menu “SNMPv3 User Management”.
2. In the menu “Edit Configuration” under “SNMP Event Polling”,
enable the “Alarm Polling”. In addition, the “Command and
Manipulation Event Polling” and/or “Trip Counter Polling” can be
activated.
3. Add the device addresses of all devices to be polled.
4. Choose a suitable alarm polling cycle.
5. Enable SNMP in the menu “SNMP Parameters”.

6. Set the IP address, port and SNMP version for up to four

management stations to receive traps. In case of SNMPv3, select
the SNMPv3 User Name from the drop-down list.
7. Download the configuration and reset the management LAN
interface.
After system startup, the configured management stations receive the
cold start trap followed by device accessible traps of devices which
have been polled successfully. Traps are sent only if events are
available.
5.10.5.9. SNMPv2-SMI standard MIB configuration

The four SNMPv2-SMI standard MIB attributes sysName, sysLocation,
SysContact and Community are configurable by the HMI570:
SNMP attribute HMI570 name HMI570 menu

sysLocation Station name Device Identification
sysName SNMP System Name SNMP Parameters
sysContact SNMP System Contact SNMP Parameters
community SNMP Community String SNMP Parameters
In the SNMPv2-SMI standard MIB tree, the attributes can be found in

SNMPv2-MIB/internet/mgmt/mib-2/system.
5.10.6. SNTP Client
5.10.6.1. Overview
The Simple Network Time Protocol (SNTP) is used to transfer
accurate time information from the dedicated servers to clients.
On the Management LAN Interface G3LMa, the SNTP client, when
enabled, polls NTP/SNTP servers for the UTC time information.
The SNTP client is enabled via HMI570 by setting the configuration
parameter “SNTP Enable” to “on”.
Other configurable values are the IP addresses of the primary and
secondary server and the SNTP polling interval.
With G3LM firmware version 1.19 and higher, the Time Zone Offset
from UTC (Universal Time Coordinated) can be configured and the
Daylight Saving Time (also called summer time in Europe) can be set
to “on” or “off”, to meet the local time situation.

5.10.6.2. SNTP primary and secondary servers

IP addresses of the NTP/SNTP primary and secondary servers are
configurable via HMI570.
SNTP client is able to poll redundant NTP/SNTP servers for UTC time
in case one of them is not reachable. This brings additional reliability to
SNTP based time synchronization.
In case both servers are available, timing information from the primary
server is evaluated.
IP address 0.0.0.0 means do not poll this server.
5.10.6.3. SNTP polling interval

This configurable value defines how often the SNTP client asks for
updated timing information from the NTP/SNTP servers. The value
ranges from 1 sec to 1024 sec. Default value is 10 sec.
5.10.6.4. Time zone offset from UTC

With G3LM firmware version 1.19 and higher, the Time Zone Offset
from UTC (Universal Time Coordinated) can be configured.
A selection from a list with 38 official UTC offsets can be made (in the
range from UTC -12:00 to UTC +14:00).
The UTC time received from the specified SNTP server over LAN is
adjusted according to these settings and distributed over the IRIG-B
output of G3LMa to the interfaces in connected NSD570 racks. The
adjusted (local) time is also used for time stamping of user activity log
entries, events in the MIB table and traps sent to the NMS.
5.10.6.5. Daylight Saving Time

With G3LM firmware version 1.19 and higher, the Daylight Saving
Time (also called summer time in Europe) can be set to “off” or “on”.
If Daylight Saving Time is set to "on", the time offset is increased by
+1 hour. This change has to be done manually according to the local
situation (i.e. when the time shift takes place).

5.11. Configuration notes for NSD570 GOOSE LAN interface
5.11.1. General
parameters are similar. This section describes the GOOSE LAN
Interface (G3LS) specific configuration. For the description of common
functionality on G3LE, G3LM and G3LS please refer to Section 5.8
“Configuration notes common for G3LE, G3LM and G3LS”.
The G3LS configuration is split into two categories, GOOSE interface
general parameters and IEC 61850 specific parameters. The general
parameter configuration is described in the next section. The
IEC 61850 specific concepts and configuration possibilities provided
by HMI570 are described in the document “Engineering of GOOSE
LAN Interface G3LS” in Section 12 “Annex”.
5.11.2. GOOSE Interface Configuration
5.11.2.1. Number of protection commands

The parameter specifies how many commands are exchanged
between the line interface and G3LS. It defines how many physical
slots of the NSD570 rack are virtually occupied by G3LS and how
many slots remain available for G3LR interfaces. The following table
shows the dependencies if a line interface with 8 commands is
available.
G3LS: Configured number of commands 1 2 3 4 5 6 7 8
G3LS: Number of virtually occupied slots 1 2 3 4
Remaining slots available for G3LR 3 2 1 0
First slot available for G3LR in TPE 1 N40 N46 N52
First slot available for G3LR in TPE 2 N70 N76 N84
Depending on the configuration, G3LR interfaces have to be plugged

into the right slots. For example, if a G3LS interface handles three
protection commands, two G3LR interfaces can be plugged into slots
N46 and N52.
The parameter “Number of Protection Commands” is valid for transmit
and receive path, although they can differ in the IEC 61850
configuration. The number of commands transmitted by the line
interface should match with the total number of commands handled by

G3LS and G3LR interfaces. To ensure this parameter is engineered in

a consistent manner, a consistency check tool is integrated in HMI570
with IEC 61850 support.
5.11.2.2. Network configuration hints

A trip is the most time critical event which is exchanged between
devices in a substation. Trips are encapsulated in GOOSE messages
and GOOSE data is directly embedded into Ethernet data packets.
Ethernet frames containing GOOSE data are addressed with multicast
MAC addresses. Therefore, no configuration of IP addresses is
needed.
Normally the Ethernet priority will be set to highest for GOOSE frames.
To get a deterministic behavior of the network, a proper network
engineering is mandatory. Please refer to Section 5.13.2.3
“Transmission time with G3LS” for further information about timing
calculation and network planning.
5.11.2.3. GPS synchronization

G3LS has an internal real time clock (RTC). The time stamps
published with GOOSE frames are derived from this RTC. By default,
the RTC is synchronized to the line interface in TPE 1. Optionally the
RTC clock can be synchronized to an external IRIG-B clock signal.
However, it is not possible to make time zone settings.
To enable external GPS synchronization, set the parameter “External
Real-Time Sync (IRIG-B)” to “on”. The default setting is “off”.
Note: Make sure the RTC or the external IRIG-B clock source
provides the required time of day.
If for example “Universal Time Coordinated” (UTC) is
required in the whole substation, the clock source (e.g. a
GPS receiver) has to be configured such that the IRIG-B
signal is provided without a “local time offset”.
5.11.3. IEC 61850 Configuration

Please refer to the annex document “Engineering of GOOSE LAN
Interface G3LS” for information about the engineering concepts and
related menu entries of HMI570.

5.12. Configuration examples
5.12.1. Example of NSD570 Analog configuration

(File name: Default_TPE1_Analog.xml)
Device information
Line Interface Type analog

Line Interface Position 1
Serial Number
Firmware Download Counter 0
Configuration Download Counter 0
Hardware versions
Interface Slot Module Piggyback

Power Supply Unit 1 (N01) Version 0
Common Interface (N22) Version 0
Line Interface TPE 1 (N28) Version 0 Version 0
Relay Interface 1 TPE 1 (N34) G3LR, Version 0 Version 0
Relay Interface 4 TPE 2 (N84)
G3LR, Version 0 Version 0
LAN Interface
Bus Plane Version 0
Firmware versions
Microcontroller 0.00
Digital Signal Processor 0.00
Device identification
Configuration Type analog

Station Name default config TPE 1

HE Number HE xxxxxx
Device Address 100
Common settings
Device Mode Normal

Unblocking Extra Delay [ms] 10
Unblocking Pulse Duration [ms] 200
are unaffected (state according
Command Outputs During Link Failure
to trip signal evaluation)
Link Failure Pickup Time [s] 10
Link Failure Hold Time [s] 0
External Real-Time Sync (IRIG-B) off
Embedded Operation Channel ( EOC ) on
Cyclic Loop Test Interval [h] 6
Propagation Time [ms] 0
Analog interface
Line Type four wire

Rx Bandwidth [Hz] 480
Rx Center Frequency [Hz] 2400
Tx Bandwidth [Hz] 480
Tx Center Frequency [Hz] 2400
Analog Operating Mode 2 single tone commands
Power Boost [dB] 0
Unblocking Threshold [dBm0] -14
Tx Level [dBm] -6
Rx Level [dBm] -6
Tx Alarm Threshold [dB] -6
Rx Alarm Threshold [+/- dB] 6

Command settings
Com- Appli- Tx Input Tx Input Tx Input Max Tx Rx Output Rx Output
mand cation On-Delay Duration Duration Input Duration Duration
[ms] Value Monitoring Value [ms]
[ms] [s]
A permissive 0 transparent 0 off prolonged 10
B permissive 0 transparent 0 off prolonged 10
C off 0 transparent 0 off transparent 0
D off 0 transparent 0 off transparent 0
Relay interfaces
Interface 1 Interface 2 Interface 3 Interface 4

TPE 1
(N34) (N40) (N46) (N52)
Relay Interface G3LR not used not used not used
Input 1 Command A Command C Command E Command G
Input 2 Command B Command D Command F Command H
Output 1 Command A Command C Command E Command G
Output 2 Command B Command D Command F Command H
Relay Output 1 not used not used not used not used

TPE 2
(N64) (N70) (N76) (N84)
Relay Interface not used not used not used not used

Alarm Settings
Pickup Time [s] 15

Hold Time [s] 15
Redundant Power
HW Warning
Supply Failure
User Alarm 1 User Alarm 2 User Alarm 3

Alarm Output delayed delayed delayed
OR-gating of Alarms User Alarm 1 User Alarm 2 User Alarm 3

HW Alarm Local off off off
HW Warning Local off off off
Link Alarm Local off off off
Tx Alarm Local off off off
Rx Alarm Local off off off
Tx Signal Local off off off
Rx Signal Local off off off
SNR / BER Local off off off
HW Alarm Remote off off off

Link Alarm Remote off off off
Tx Alarm Remote off off off
Rx Alarm Remote off off off
Tx Signal Remote off off off
Rx Signal Remote off off off
SNR / BER Remote off off off

Jumper settings
Analog interface
Jumper settings impedance
Rx Impedance 600 Ohm

Tx Impedance 600 Ohm
Relay interfaces
Jumper settings nominal battery voltage
TPE 1 Input 1 Input 2

Relay Interface 1 (N34) 125 .. 250 VDC 125 .. 250V DC
Relay Interface 2 (N40) not assembled not assembled

Rack assembly

Power Supply Unit 1 (N01) G3LI
Power Supply Unit 2 (N09) not assembled
Line Interface TPE 1 (N28) G3LA not assembled
Relay Interface 1 TPE 1 (N34) G3LR not assembled
Relay Interface 2 TPE 1 (N40) not assembled not assembled
Line Interface TPE 2 (N58) not assembled not assembled
Relay Interfaces 3 TPE 2 (N76) not assembled not assembled
not assembled not assembled
LAN Interface

5.12.2. Example of NSD570 Digital configuration

(File name: Default_TPE1_Digital.xml)
Device information
Line Interface Type digital

Serial Number
Hardware versions

LAN Interface
Bus Plane Version 0
Firmware versions
Microcontroller 0.00
Digital Signal Processor 0.00

Configuration Type digital

HE Number HE xxxxxx
Device Address 200
Common settings
Device Mode Normal

Cyclic Loop Test Interval 6
Digital interface
Interface Type G.703 64 kbps codirectional

BER Alarm Threshold ( 1E... ) -3
Digital Address Check off
Local Digital Address 341
Remote Digital Address 682
G.703 Tx Clock Sync Rx

Command settings
[ms] [s]
C off 0 transparent 0 off transparent 0
D off 0 transparent 0 off transparent 0
E off 0 transparent 0 off transparent 0
F off 0 transparent 0 off transparent 0
G off 0 transparent 0 off transparent 0
H off 0 transparent 0 off transparent 0
Relay Interfaces

TPE 1
(N34) (N40) (N46) (N52)

TPE 2
(N64) (N70) (N76) (N84)

Alarm settings
Pickup Time [s] 15

Hold Time [s] 15
Redundant Power
HW Warning
Supply Failure




Jumper settings
Relay interfaces

Relay Interface 1 (N34) 125 .. 250 VDC 125 .. 250V DC

Rack assembly

Line Interface TPE 1 (N28) G3LD not assembled
LAN Interface

5.12.3. Example of NSD570 Digital configuration for T-operation
5.12.3.1. TPE1 and TPE 2 in T-station
Device information TPE1

Serial Number

Serial Number
Device identification TPE1

Station Name default config TPE 1 in T
HE Number HE xxxxxx
Device Address 201

Station Name default config TPE 2 in T
HE Number HE xxxxxx
Device Address 202

Common settings TPE1 and TPE2
Device Mode Teed

Embedded Operation Channel ( EOC ) off
Cyclic Loop Test Interval off
Digital interface TPE1
Interface Type G.703 64.kbps codirectional

Digital Address Check on
G.703 Tx Clock Sync none

G.703 Tx Clock Sync none

Command settings TPE1 and TPE2

[ms] [s]
C permissive 0 transparent 0 off prolonged 10
D permissive 0 transparent 0 off prolonged 10
Relay Interfaces TPE1 and TPE2

TPE1, TPE 2
(N64) (N70) (N76) (N84)
Relay Interface G3LR G3LR not used not used
Input 1 Command A Command C not used not used
Input 2 Command B Command D not used not used
Output 1 Command A Command C not used not used
Output 2 Command B Command D not used not used
Relay interfaces TPE1 and TPE2

TPE1, TPE 2 Input 1 Input 2

Relay Interface 1 (N34) 125 .. 250 VDC 125 .. 250 VDC

Rack assembly

LAN Interface
5.12.3.2. TPE1 in station A (connected to TPE1 in T-station)

Serial Number

HE Number HE xxxxxx
Device Address 200

Common settings TPE1
Device Mode Normal

Cyclic Loop Test Interval 6h

Command settings TPE1

[ms] [s]

Relay Interfaces TPE1

TPE1
(N64) (N70) (N76) (N84)


Rack assembly

LAN Interface

5.12.3.3. TPE1 in station B (connected to TPE2 in T-station)

Serial Number

HE Number HE xxxxxx
Device Address 203
Common settings TPE1
Device Mode Normal

Cyclic Loop Test Interval 6h


Command settings TPE1

[ms] [s]
Relay Interfaces TPE1

TPE1
(N64) (N70) (N76) (N84)



Rack assembly

LAN Interface

5.12.4. Example of NSD570 Ethernet configuration

(File name: Default_TPE1_Ethernet.xml)
Device information
Line Interface Type Ethernet

Hardware versions

LAN Interface
Bus Plane Version 0
SFP identifications
Interface Vendor Part number Transceiver code

Line Interface TPE 1 no information no information no information
Line Interface TPE 2 not accessible not accessible not accessible
Firmware versions
Processor 0.00

Configuration Type Ethernet

HE Number HE xxxxxx
Device Address 200
Common settings
Device Mode Normal

Cyclic Loop Test Interval 6
Ethernet interface
Auto Negotiation manual

Data Rate [Mbps] 100
Duplex Mode Full Duplex
Local IP Address 192.168.0.2
Subnet Mask 255.255.255.0
Default Gateway 192.168.0.1
Remote IP Address 192.168.0.3
IP Priority (TOS/DSCP and ECN) 46 and 0
VLAN Tagging (802.1Q) disabled
UDP Port Teleprotection Packets 49152
UDP Port EOC Packets 49153
Guard Packets Sending Interval [ms] 5
Transmission Time Test Interval [ms] 1000
Transmission Time Warning / Alarm Sensitivity Medium
Packet Loss Rate Alarm Threshold [%] 1.0
Automatic Laser Shutdown (ALS) off

Command settings
[ms] [s]
C off 0 transparent 0 off prolonged 10
D off 0 transparent 0 off prolonged 10
Relay Interfaces

TPE 1
(N34) (N40) (N46) (N52)

TPE 2
(N64) (N70) (N76) (N84)

Alarm settings
Pickup Time [s] 15

Hold Time [s] 15
Redundant Power
HW Warning
Supply Failure




Jumper settings
Relay interfaces


Rack assembly

Line Interface TPE 1 (N28) G3LE not assembled
LAN Interface

5.12.5. Example of NSD570 GOOSE LAN configuration

(File name: Default_TPE1_GOOSE.xml)
Device Information
Relay Interface Type goose lan

Relay Interface Position 2
HW Configuration Download Counter 0
IED Configuration Download Counter 0
SFP Identification
Vendor Part Number Transceiver Code

GOOSE LAN no information no information no information
Interface G3LS
Firmware Version
Processor 1.00
Configuration Type goose lan

Station Name default config GOOSE
HE Number HE xxxxxx
Device Address 110
GOOSE LAN Interface

Number of Protection Commands 4

5.12.6. Example of NSD570 Management configuration

(File name: Default_Management.xml)
Device Information
Interface Type management

Interface Position 10
SFP Identifications
Interface Vendor Part number Transceiver code

Management no information no information no information
Interface G3LM
Firmware Versions
Processor 0.00
Configuration Type management

Station Name default config LAN
HE Number HE xxxxxx
Device Address 202
Management Interface
IP Address 192.168.0.4
Subnet Mask 255.255.255.0
Default Gateway 192.168.0.1
VLAN Tagging (802.1Q) disabled
Auto Negotiation auto

SNMP Event Polling
Alarm Polling off

Command and Manipulation Event Polling off
Trip Counter Polling off
Length of Polling Cycle 5 sec
Device List
Device Address Remote over EOC

100 0
SNMP Parameters
SNMP Enable off

SNMP Version 1 and 2
SNMP Community String default NSD community string
SNMP System Name G3LM
SNMP System Contact Hitachi ABB Power Grids
NMS IP Address NMS Port SNMP Version SNMPv3 User Name

0.0.0.0 162 1
0.0.0.0 162 1
0.0.0.0 162 1
0.0.0.0 162 1
SNTP Time Parameters
SNTP Enable off

SNTP Primary Server 192.168.0.2
SNTP Secondary Server 0.0.0.0
SNTP Interval [s] 10
Time Zone Offset UTC 00:00
Daylight Saving Time off

5.13. Performance criteria
5.13.1. General
A fundamental requirement in all the applications that teleprotection
equipment is used in is, that command signals are communicated
reliably at the highest possible speed (transmission time). In the event
of a fault on the protected unit, the command signals must be received
at the remote end in the shortest possible time even if the channel is
disturbed by the fault (dependability).
On the other hand, interference on the communications channel must
never cause unwanted operation of the protection by simulating a
tripping signal when there is no fault on the power system (security).
The most important features of a teleprotection equipment are
therefore transmission time, dependability and security. From the
communications engineering point of view, the bandwidth or data rate
a teleprotection equipment uses must also be taken into account.
By security is understood that the receiver does not generate spurious
tripping signals in the presence of interference on the communications
channel. Dependability characterizes the receiver's ability to recognize
a genuine tripping signal within a given time in spite of interference on
the communications channel. It is obvious that to demand maximum
security at the same time as maximum dependability is contradictory
and one can only be increased at the expense of the other.
When using the NSD570 Analog with single tone command signals,
interference with the guard signal by an alien single tone, which
matches exactly one of the trip frequencies, could generate a false
command if the level of the interference signal is significantly higher
than the guard signal level.
The security against single tone interference depends on how the
command outputs are programmed to respond in case of a link alarm.
Should alien single tone interference appear, select the transmission
of dual tone command signals. This setting prevents an unintended
tripping by a discrete sine tone.
Note: Maloperation can mean both fail to trip (sometimes

called underfunction) and false trip (sometimes called
overfunction).

5.13.2. Transmission time

Traditional teleprotection equipment have a set of fixed signal
evaluation times for which the equipment delivers the requested
performance (transmission time, dependability and security).
For example there could be found three different evaluation times: One
for blocking (T1, fast), one for permissive tripping (T2, medium) and
one for direct tripping (T3, slow), each selection being compliant with
the requested security and dependability for the given application.
Once the equipment is programmed for direct tripping (T3, slow) for
example, it will not trip very fast even if the actual prevailing channel
conditions would permit to do so.
For the NSD570 Analog, this disadvantage is avoided by using
patented dynamic adaptation. This can be seen as two receivers
connected in parallel: a fast one (T1), and a slower one (T2). Both
comply with the requested security for a given application (user
programmable) such as blocking, permissive tripping or direct tripping.
If now the actual channel condition during command transmission is
good, the NSD570 will decide to trip with its fast receiver (T1) and not
wait for the slower one (T2). If the actual channel condition is worse, it
will not trip with receiver T1 but wait for receiver T2 to trip.
With this in mind, shorter transmission times can therefore be
expected on average, compared with traditional solutions.
Moreover, the decision threshold for accepting a trip is permanently
and smoothly adapted to the actual prevailing received noise power:
from “low” for good channels to “high” for noisy channels. This
prevents noise from producing unwanted trips.
For the NSD570 Digital, the patented dynamic adaptation works as
follows:
The messages (guard or trip or test) are transmitted in consecutive
frames. Depending on the actual digital channel condition the receiver
trips after the reception of
- N error free-frames (→ good channel)
- M erroneous frames with max. 1 error corrected (→ channel with
bit errors); with M > N
N and M depend on the application setting (blocking, permissive
tripping or direct tripping).
The adaptation is the dynamic selection between tripping after N
frames (fast, in case of no errors) or M frames (slower, in case of
errors). The error correcting facility has a beneficial impact on
dependability.

Due to the specific characteristics of a packet switched network the

NSD570 Ethernet does not require dynamic adaptation. From the
security point of view the probability of an unwanted command is
negligible due to the security already provided by the 32 bit CRC
Ethernet trailer and further measures which are taken to secure the
transmission of the packets through the other layers (e.g. hash code,
unique node address, etc.).
Independently from the tripping scheme that is being selected the
NSD570 Ethernet sends the first tripping packet plus 15 repetitions
every 2 ms in case of a command injected at the relay interfaces (e.g.
16 tripping packets total). This guarantees on one hand the fastest
possible reception time in case of an undisturbed channel and the
possibility to receive later packets only within a short delay in case that
former packets got lost.
5.13.2.1. Nominal transmission time

The nominal transmission time T0 is the time elapsed from the
initiating of the command input of the teleprotection transmitter until
the teleprotection receiver has given an output, measured under noise
or bit error free conditions, i.e. there is no interference on the channel.
The measurement is carried out with the transmitter and receiver
connected back-to-back via the Line Interface terminals.
The nominal transmission time T0 is composed of three terms:
T0 = TI/O + Tg + Tev
TI/O Switching times of the relay interfaces at the transmitting and
receiving end, TI/O approx. 1 ms if G3LR with a solid state
output is used, or approx. 8 ms if a relay contact is used for
the command.
Tg NSD570 channel delay (analog: group delay of the filters
which depends on the channel bandwidth and whether the
EOC is switched on or not; digital/Ethernet: due to conversion
from digital to the format of the data interface in use).
Tev Signal evaluation time in the NSD570 receiver. It depends on
the settings of the command application. Since there is no
channel interference, the dynamic adaptation is not in
operation and the fastest receiver will always become
effective when measuring T0.

5.13.2.2. Maximum actual transmission time

In order to estimate the actual transmission time Tac in practical
applications, the delay introduced by the communications channel
(cable, microwave, PLC, multiplexer, cable, microwave, IP network)
must be added to the nominal transmission time. Severe disturbances
(noise, bit errors, lost packets) on the transmission path may
occasionally introduce an additional delay of a few milliseconds.
Commands which are not received within Tac are considered as lost or
missed commands (refer also to Section 5.13.5 “Dependability”).
The actual transmission time of the NSD570 is measured, for example,
by means of the manual or cyclic loop tests, see Section 3.5.18 “Test
facilities for the Line Interfaces”.
5.13.2.3. Transmission time with G3LS

Calculation of the (worst case) transmission time including protection
relays is more complex if a G3LS device is used in the setup.
NSD570 NSD570
Protection Substation Line Line Substation Protection

G3LS G3LS
Relay LAN Interface Interface LAN Relay
TRA TNA TSA TL TSB TNB TRB
Fig. 5-10 G3LS transmission time
The transmission time T is composed:

TOV = TRA + TNA + TSA + TL + TSB + TNB + TRB
TR Processing time needed by the Protection IED network stack.
This parameter is described in the PIXIT definitions of the
Protection IED. A Protection IED is normally qualified with a
performance class according to IEC 61850. If both relays are
certified for performance class 3 7, it means that TRA + TRB
< 3 ms.
TN Time needed by the network to forward a frame from the

Protection IED interface to the G3LS interface. According to
the IEC 61850-5 a network simulation must be performed to
get this value. See appendix “PICOM method” for further
information.
7 Performance classes in this context are only valid for identical protection
relays since the standard does not define receive and transmit time
separately.

TS Time needed by G3LS to forward a frame to the line interface.
TL Transmission time of the line interfaces. This time depends on

the type of line interface and its configuration. Please note
that in practical applications the delay introduced by the
communications channel has to be taken into account (refer to
Section 5.13.2.2 “Maximum actual transmission time”).
In a chain as shown in Fig. 5-10 the setup of the Substation LAN can
have a big impact on the worst case transmission time. If a GOOSE
packet is lost by the network, it will be retransmitted after a certain
amount of milliseconds Tmin (see Section 3.5.10. “GOOSE operating
principle”). A safety margin needs to be added to TOV. A rule of thumb
is to add a margin of 20% of TOV for the substation internal LANs share
to the overall transmission time.
To get a low probability for packet loss in the substation LAN it’s
important to have the network switches properly configured. The
following points should be considered:
• A dedicated VLAN ID shall be assigned to each logical
connection transferring real time traffic.
• GOOSE frames shall be transmitted at the highest priority.
• A network simulation shall be performed. The maximal load for
each receiving port in the network shall be calculated. The load
must be in the range which can be handled by the receiving
device without discarding GOOSE messages.
5.13.3. Security
The NSD570 with its dynamic adaptation of the receiver provides the
best security / dependability trade-off for the chosen command appli-
cation at lowest possible transmission time.
Security is expressed as the “worst case” false signal rate (probability
of unwanted commands Puc) for blocks of noise or bit errors of 200 ms
duration. “Worst case” is defined as the level of interference at which
the guard signal is completely suppressed in analog channels and
corresponds to a bit error rate of 0.1 to 0.5 in digital channels.
Levels of security are virtually independent of the chosen NSD570
Analog bandwidth or NSD570 Digital interface type or data rate. For
NSD570 Ethernet the probability of an unwanted command is
negligible due to the security already provided by the 32 bit CRC
Ethernet trailer and further measures which are taken to secure the
transmission of the packets through the other layers (e.g. hash code,
unique node address, etc.).
The security level Puc is fixed for each of the possible command
applications.

5.13.4. Security measurements

All security measurements were performed according to the
procedures prescribed in IEC 60834-1:
noise/bit error burst 200 ms
duration of pause 200 ms
noise bandwidth 4 kHz
SNR -10 dB… -30 dB
BER 0.1 … 0.5
Security is determined by coupling bursts of white noise of high
amplitude into the communication channel of the analog or digital
NSD570. For measuring the security of the digital NSD570, a bit error
generator that introduces random bit errors of a certain quantity can be
used alternatively. The number of bursts injected and the number of
false commands they cause at the receiving end are counted.
The probability of unwanted commands is then calculated according to
the following relationship:
Puc = Nuc / NB
Puc = probability of an unwanted command

Nuc = number of unwanted commands received
NB = number of noise bursts injected
5.13.5. Dependability
For analog channels dependability is expressed as the signal-to-noise
ratio (SNR) for a noise bandwidth of 4 kHz, which must be maintained
during the transmission of a tripping signal to enable that it can be
received within 1.3, 1.5 or 2.0 times the nominal transmission time T0
(probability of missing a command Pmc < 1%). Dependability varies
with the bandwidth, so the signal-to-noise ratio will differ in accordance
with the chosen bandwidth.
For digital channels dependability is expressed as the bit error rate
BER, which must be maintained during the transmission of a tripping
signal to enable that it can be received within 1.3 times the nominal
transmission time T0 (probability of missing a command Pmc < 1%).
For Ethernet/IP based channels dependability is expressed as the
Packet Loss Rate PLR, which must be maintained during the
transmission of a tripping signal to enable that it can be received within
a certain maximum actual transmission time Tac required by the
protection application (probability of missing a command Pmc < 1E-02
for blocking, Pmc < 1E-03 for permissive tripping and Pmc < 1E-04 for
direct tripping).

5.13.6. Dependability measurements

All dependability measurements were performed according to the
procedures prescribed in IEC 60834-1:
command duration 50 ms or 3 x T0
duration of pause 2 x command duration
noise bandwidth 4 kHz
SNR -6 dB … +20 dB
BER 1E-01 … 1E-06
PLR 90 % … 0.1 %
continuous noise/bit errors/packet losses

Dependability is determined by sending a large number of commands
to the remote station. The number of commands transmitted and the
number of commands received within a specified time (normally 1.3 x
T0, 1.5 x T0, 2 x T0 and 3 x T0) are recorded. The lower the signal-to-
noise ratio (SNR), the higher the bit error rate (BER) and the higher
the Packet Loss Rate (PLR) at the input of the receiving NSD570, the
fewer the commands which will be received in the prescribed time.
The following applies for a sufficiently high number of transmitted
commands:
Pmc = (NT - NR) / NT
Pmc = probability of missing a command

NT = number of commands transmitted
NR = number of commands received

6. Installation and wiring
6.1. Introduction
Installation of the equipment can only be made smoothly if it is
properly planned beforehand. The system should be engineered not
only to take account of immediate needs, but also allow for long-term
network development.
6.2. Safety instructions

Mechanical installation

DANGER


Insertion and removal of plug-in modules


cable.
Back cover

be disconnected.
Installation and wiring August 2021 6-1

This is a Class  equipment specified in

DANGER IEC 60950-1. The equipment and the cabinet must
be earthed.
The equipment must be supplied over circuit
breaker.


The isolating terminals from the external cables

DANGER must be kept open during installation, maintenance
and before storage, decommissioning and disposal.
The Faston supply connectors at the rear of the rack

DANGER must be covered with an isolation sleeve.
The power supply is dangerous (hazardous voltage

DANGER and/or hazardous energy level).
Do not install the equipment with a live supply.

Caution Connecting a load between terminals NO (normally

open) and NC (normally closed) is not allowed.
Use only one contact set NO or NC.
Power supply for alarm
Caution The alarm power supply must be short current and

over current protected.
6-2 August 2021 Installation and wiring


Laser / LED
Caution Class  Laser/LED Product.

Laser / LED
ESD protection

6.2.1. General
The aim is not just to install the equipment properly, but also to ensure
its long-term operational reliability. Strictly observe all safety
instructions during installation so that if damage does occur, warranty
and service rights do not become void.
6.3. Unpacking
6.3.1. Inspection upon receipt

Check that the consignment is complete immediately upon receipt.
Notify the nearest Hitachi ABB Power Grids company or agent without
delay should departures from the delivery note, the shipping papers or
the order be found.
6.3.2. What to do if there is transport damage

Visually inspect all the material when unpacking it. Where there is
evidence of transport damage, lodge a claim immediately in writing
with the last carrier, notify the nearest Hitachi ABB Power Grids

company or agent and also ABB Power Grids Switzerland Ltd,

Communication Networks, CH-5400 Baden, Switzerland.
6.3.3. Precautions to avoid transport damage

Insert the modules carefully but firmly into the racks so that they
cannot fall out. Modules and other loose parts that are packed
separately must be packed and secured such as to preclude damage.
6.4. Installation
6.4.1. Place of installation and ambient conditions

The room where the equipment is installed should be free of dust, the
floor covered if possible with a semi-conducting plastic flooring
material and cement floors and walls should be suitably painted.
The room must be well ventilated so that the temperature is in the
range +10° to +45°C and the relative humidity between 30 and 70 %.
Lead/acid batteries must not be in the same room.
6.4.2. Cabinet
The standard equipment is supplied in an Hitachi ABB Power Grids
cabinet Type E40A. These cabinets are equipped with a hinged frame
and are suitable for installation:
• standing against a wall,
• back-to-back,
• side-by-side,
• standing alone.
A gap of 2 to 3 cm should be left between cabinets standing side-by-
side to permit single cabinets to be removed without difficulty. Leave
sufficient space in front to avoid damage when the hinged frame is
opened. There must generally be enough room for carrying out
maintenance and for using the associated instruments.
Do not install equipment cabinets in corners, which would hinder
opening the hinged frame and working on the cabinet.
Free access is especially important in the case of cabinets not
equipped with a hinged frame. Cabinets are normally erected on a
pedestal or as a suite of cabinets on a platform to facilitate cleaning
the floor and routing of cables.

6.4.3. Installing racks in cabinets

Pay attention when determining the cabinet layout that air can circulate
freely around the equipment and overheating cannot take place. To
this end, a space of at least 4 cm must be left between the racks.
6.5. Wiring
6.5.1. Introduction
While being installed, the equipment must be switched off and no
external connections may be made to it.
6.5.2. Grounding system

The grounding system must go out radially from the station ground rail.
On no account may there be any loops that would permit circulating
ground currents.
Every cabinet must have its own ground conductor (gauge > 25 mm2)
connected by adequately rated cable lugs to the station ground rail.
The ground connection to the cabinet shall be clearly visible and made
to the designated ground terminal.
For safety reasons, looping ground conductors to or from neighboring
cabinets or other equipment is not permissible.
To ensure proper RF-grounding and EMC protection, the hinged frame
or mounting rack inside the cabinet must be connected to the ground
rail of the cabinet using a short copper band (length < 20 cm). In
addition, the hinged frame or mounting rack must be blank (non-
painted) in order to ensure a low impedance RF-grounding of the
NSD570 rack bolted to it. If not, then one has to connect the NSD570
rack via a short copper band (length < 20 cm) to an unpainted spot of
the hinged frame.
6.5.3. External connections

Connections are made via cables to be plugged into the connectors at
the rear of the equipment. Some of these connectors (those of type
Phoenix) also allow direct plugging of screwless spring-cage type
terminal blocks. The external connections are then made by clamping
wires into these terminal blocks.
When clamping wires into the terminals plugging of screwless spring
clamp type terminal blocks, do not clamp more than one wire per
terminal.

Note: Do not clamp more than one wire per terminal when
using screwless spring-cage type terminal blocks.
The length of the optional available connecting cables is 2500 mm.

All external cables have to be secured to the cable rail in the rear of
the equipment with the help of plastic cable ties as shown. In case of
screened cables, the upper cable binder has to be replaced with the
metallic spring clamp supplied with the cable, in order to ensure a low
impedance electrical connection of the cable screen to the equipment
chassis also at high frequencies, see Fig. 6-1. and Fig. 6-2.
RS-422 - G.703 E1/T1

RS-449/RS-530/X.21
Plastic cable tie Metallic spring clamp
Fig. 6-1 Mounting of external cables with cable screen

Ethernet on LAN Interface G3LL Ethernet on LAN Interface G3LMa
Plastic cable tie Metallic spring Plastic cable tie Metallic spring
clamp clamp
Fig. 6-2 Mounting of external cables with cable screen (G3LL and
G3LMa)

In case of optical cables only the upper cable tie is used in order to
minimize the stress of the optical fiber. Do not over tighten ties used
for dressing as damage may result. To maximize the bending radius,
the fiber has to be routed in a circle as shown in Fig. 6-3.
Optical Interface G1LOa
Plastic cable tie
Fig. 6-3 Mounting of external optical cables (G1LOa)

6.5.3.1. Power Supply

The NSD570 must always be connected via circuit breakers to the
supply voltage(s). In case of redundant supply (two power supplies),
circuit breakers have to be inserted in both supply lines.
Recommended circuit breakers:
B9AS Label E: CI-BREAK  60 VDC / 250 VAC
Ident. number: 2CDS282001R0377
Type: S202P-K6
Max. voltage:  60 VDC or  250 VAC
B9AV Label E: CI-BREAK > 60 VDC … 250 VDC

Ident. number: GHS2820164R0377
Type: S282UC-K06A
Max. voltage:  250 VDC
The supply connectors (Faston, 6.3 mm x 0.8 mm) are at the rear of
the module rack. For exact locations refer to Fig. 6-4.
View from rear:

Power Supply 2:
{ DC +
AC L
Positive battery pole DC supply
or AC Line supply
{ DC -
AC N
Negative battery pole DC supply
or AC Neutral supply
Power Supply 1:
{ DC +
AC L
Positive battery pole DC supply
or AC Line supply
{ DC -
AC N
Negative battery pole DC supply
or AC Neutral supply
PE
Protective earth connectors
Plastic cable ties
Fig. 6-4 Supply connections

6.5.3.2. Station bus and Real Time Clock synchronization
6.5.3.2.1. Connection to terminal block at rear of equipment

The screwless (spring-cage) type terminal block can be plugged onto
connector X103 of the supply backplane G1LB.
Recommended wire size: ≥ 0.25 mm2 (unshielded twisted pairs).
Wire size range: Solid and stranded 0.14 to 1.5 mm2.
Stripping length: 9 mm
X103
G1LB
BACKPLANE
SUPPLY
G3LC
INTERFACE
COMMON
A
1
RS-485
1
B
2
GND
3
7
GPS-SYNC (IRIG-B)
4
+
5
-
EXT-SYNC (1 PPS)
6
+
7
-
6-G1LB_Connector.vsd
Fig. 6-5 Connector for station bus and Real Time Clock
synchronization

6.5.3.2.2. Connection via G1LB cable and G3LMa cable for RTC
sync/station bus
These cables are equipped with screwless (spring-cage) type
terminals.
Wire size range: Solid 0.2 to 4.0 mm2, stranded 0.2 to 2.5 mm2.
COMMON RS-485 GPS-SYNC (IRIG-B) EXT-SYNC (1 PPS)

INTERFACE
G3LC A B GND
SUPPLY
BACKPLANE
G1LB + - + -
X103 1 2 3 4 5 6 7
G1LB/G3LMa CABLE FOR
RTC SYNC/STATION BUS
WH BN GN GY PK BU RD YE
Terminals
1 2 3 4 5 6 7 8
6-G1LB_G3LMa_Cable.vsd
Fig. 6-6 Station bus and Real Time Clock synchronization
6.5.3.3. System alarm relays

connector X102 of the common interface G3LC.
Recommended wire size: ≥ 0.75 mm2.

X102
G3LC
INTERFACE
COMMON
1
NO
ALARM RELAY 1
2
C
CONTACT RATING: 150W, 8A MAKE,

ALARM CONTACTS ARE SHOWN IN ALARM POS.
NOTE :
1
3
NC
4
8
5A CARRY, 0.6A BREAK

5
6
NO
ALARM RELAY 2
7
C
8
NC
6-G3LC_Connector.vsd
Fig. 6-7 Connector for system alarm relays
6.5.3.3.2. Connection via G3LC cable for alarm relays

The cable is equipped with screwless (spring-cage) type terminals.
COMMON ALARM RELAY 1 ALARM RELAY 2
INTERFACE
G3LC NOTE :
ALARM CONTACTS ARE SHOWN IN ALARM POS.
CONTACT RATING: 150W, 8A MAKE,
5A CARRY, 0.6A BREAK
NO C NC NO C NC
X102 1 2 3 6 7 8
G3LC CABLE FOR

ALARM RELAYS
BK BK BK BK BK BK GNYE
Terminals 1 2 3 4 5 6 PE
6-GL3C_Cable.vsd
Fig. 6-8 G3LC cable for alarm relays

6.5.3.4. Relay Interface G3LR

connector X101 of the relay interface G3LR.
X101
G3LR
INTERFACE
RELAY
JUMPER
1A+1D
1A+1C
1A+1B
G1LR
G3LR CABLE FOR
RELAY INTERFACE
125VDC...250VDC
External dry contact
60VDC...110VDC
24VDC...48VDC
U BAT nom.
G1LR
(option)
1A
1
1B
TX1
1C
1D
(VOLT. RANGE: 24...250VDC)

JUMPER
2A+2C
2A+2D
2A+2B
G1LR
1
INPUT
125VDC...250VDC
60VDC...110VDC
24VDC...48VDC
External dry
U BAT nom.
contact
2A
3
2B
TX2
2C
2D
4
(SOLID STATE / 5...250VDC/2A) (HEAVY DUTY / 5...250VDC/5A CARRY)

5
-
RX1
OUTPUT
6
+
7
-
RX2
8
+
9
NO
RX/REL1
10
C
11
NC
OUTPUT
14
12
NO
RX/REL2
13
C
14
NC
6-G3LR_Connector.vsd
Fig. 6-9 Connector for relay interface

6.5.3.4.2. Connection via G3LR cable for relay interface

RELAY INPUT OUTPUT OUTPUT

INTERFACE (VOLT. RANGE: 24...250VDC) (SOLID STATE / 5...250VDC/2A) (HEAVY DUTY / 5...250VDC/5A CARRY)
G3LR
TX1 TX2 RX1 RX2 RX/REL 1 RX/REL2
JUMPER U BAT nom. JUMPER U BAT nom.
1A+1B 24VDC...48VDC 2A+2B 24VDC...48VDC
1A+1C 60VDC...110VDC 2A+2C 60VDC...110VDC
1A+1D 125VDC...250VDC 2A+2D 125VDC...250VDC
External dry
G1LR External dry contact G1LR
contact
G1LR
1D
1C
2C
2D
1A
1B
2A
2B
(option)
- + - + NO C NC NO C NC
X101 1 2 3 4 5 6 7 8 9 10 11 12 13 14
G3LR CABLE FOR
RELAY INTERFACE
BK BK BK BK BK BK BK BK BK BK BK BK BK BK GNYE
Terminals
1 2 3 4 5 6 7 8 9 10 11 12 13 14 PE
6-G3LR_Cable.vsd
Fig. 6-10 G3LR cable for relay interface
Note: G3LRa provides two more jumpers (1E and 2E) to program the
fourth range of the nominal station battery voltage for the inputs.
Fig. 6-11 Piggyback G1LR Input Tripping Voltage

6.5.3.5. Analog Interface G3LA

connector X100 of the Analog Interface G3LA.
X100
INTERFACE
ANALOG
G3LA
JUMPER OUTPUT
TB
TA
IMPEDANCE
X302
X301
>1.5kOhm
600Ohm
TA
TB
X303
TX-
AF
1
2
JUMPER
RB
RA
IMPEDANCE
X203 RB
X202
RA
>1.5kOhm
600Ohm
INPUT
X204
6 RX-AF
3
4
5
BOOST
6
6-G3LA_Connector.vsd
Fig. 6-12 Connector for analog interface

6.5.3.5.2. Connection via G3LA cable for analog interface

ANALOG RX-AF
IMPEDANCE TX-AF IMPEDANCE BOOST
INTERFACE
G3LA
X301 X202
TA RA
X302 X203
RB
X204
X303
TB
JUMPER OUTPUT JUMPER INPUT

TA 600Ohm RA 600Ohm
TB >1.5kOhm RB >1.5kOhm
X100 1 2 3 4 5 6
G3LA CABLE FOR
ANALOG INTERFACE
WH BN GN YE GY PK
Terminals 1 2 3 4 5 6
6-G3LA_Cable.vsd
Fig. 6-13 G3LA cable for analog interface

6.5.3.6. Digital Interface G3LD
6.5.3.6.1. RS-422 – RS-449/RS-530/X.21interface

a) Connector at rear of equipment (male D-sub 25 poles)
The connecting cable must be a shielded twisted pair cable (SF/UTP).
G3LD
INTERFACE
DIGITAL
X101
PE
1
1
14 SD-A
DATA
SEND
2
SD-B
14
RECEIVE RECEIVE TERMINAL SEND

RD-A
DATA
RS-422 INTERFACE
3
RD-B
25
16
13 RT-A
TIMING TIMING TIMING

17
RT-B
9
24 TT-A
TT-B
11
ST-A
15
ST-B
12
SG
7
6-G3LD_Cable.vsd
Fig. 6-14 Connector for digital interface (male D-sub 25 poles)

b) Connection via G3LD cable with isolating terminals (10 poles)

Recommended wire size: ≥ 0.25 mm2 (shielded twisted pairs).
DIGITAL RS-422 INTERFACE
INTERFACE
G3LD SEND RECEIVE RECEIVE TERMINAL SEND
DATA DATA TIMING TIMING TIMING
RD-A
RD-B
SD-A
SD-B
RT-A
RT-B
PE
ST-A
ST-B
TT-A
TT-B
CHASSIS
GND
X101 1 2 14 3 16 17 9 24 11 15 12
G3LD*CABLE WITH
ISOLATING TERMINALS
WH BN GN YE GY PK BU RD BK VT
Terminals 5 6 1 2 3 4 9 10 7 8 PE
6-G3LD_Cable.vsd
Fig. 6-15 G3LD cable with isolating terminals (10 poles)
c) Connection via G3LD cable with RS-449 interface (37 poles)

INTERFACE
RD-A
RD-B
SD-A
SD-B
RT-A
RT-B
PE
ST-A
ST-B
TT-A
TT-B
CHASSIS
GND
X101 1 2 14 3 16 17 9 24 11 15 12
G3LD*CABLE WITH
RS-449 INTERFACE
(37-P) WH BN GN YE GY PK BU RD BK VT
1 4 22 6 24 8 26 17 35 5 23
6-G3LD_Cable.vsd
Fig. 6-16 G3LD cable with RS-449 interface (male D-sub connector
37 poles)

d) Connection via G3LD cable with RS-530 interface (25 poles)

INTERFACE
PE
RD-A
RD-B
SD-A
SD-B
CHASSIS
RT-A
RT-B
ST-A
ST-B
TT-A
TT-B
GND
X101 1 2 14 3 16 17 9 24 11 15 12
G3LD*CABLE WITH
RS-530 INTERFACE (25-P)
WH BN GN YE GY PK BU RD BK VT
1 2 14 3 16 17 9 24 11 15 12
6-G3LD_Cable.vsd
Fig. 6-17 G3LD cable with RS-530 interface (male D-sub connector
25 poles)
e) Connection via G3LD cable with X.21 interface (15 poles)

INTERFACE
PE
RD-A
RD-B
SD-A
SD-B
RT-A
RT-B
ST-A
ST-B
TT-A
TT-B
CHASSIS
GND
X101 1 2 14 3 16 17 9 24 11 15 12
G3LD*CABLE WITH
X.21 INTERFACE (15-P)
WH BN GN YE GY PK BU RD
1 2 9 4 11 7 14 6 13
6-G3LD_Cable.vsd
Fig. 6-18 G3LD cable with X.21 interface (male D-sub connector 15
poles)

6.5.3.6.2. G.703 co-directional interface

a) Connector at rear of equipment (RJ45, 8 poles)
The connecting RJ45 cable must be a shielded twisted pair cable
(SF/UTP).
G3LD
INTERFACE
DIGITAL
G.703 CODIRECTIONAL INTERFACE
X201
DATA
6
+
RX
3
-
DATA
4
+
TX
5
-
2
1
7
8
8
1
6-G3LD_Cable.vsd
Fig. 6-19 Connector for G.703 codirectional interface

(RJ45, 8 poles)
b) Connection via cable for all interfaces with RJ45 connector,

patch panel V9OZ and patch cord V9OH
The 1:1 patch cord cable V9OH has RJ45 connectors at both ends.
In addition, a patch panel V9OZ (see Section 6.5.4 “Connection via
Cable for all Interfaces with RJ45 Connector”) can be delivered that
allows connection of wires to “LSA Plus Quick Connect” type of
terminals (manufactured by KRONE). With this system the
connections to the patch panel can be made quickly without soldering.
A push-on tool (referred to as a KRONE tool), may be used for that
purpose.
Wire size range: 0.4 mm (AWG 26) … 0.65 mm (AWG 22).
The connection cable must be shielded twisted pairs (SF/UTP) with a
nominal impedance of 120 Ohm.

DIGITAL G.703 CODIRECTIONAL INTERFACE

INTERFACE RJ45 Patch panel
G3LD RX TX
DATA DATA
1 1
2 2
3 = Rx - 3 = Rx -
CHASSIS
+ - + - GND 4 = Tx + 6 = Rx +
X201 6 3 4 5 2 7 8 1
5 = Tx - 4 = Tx +
CABLE V9OH
6 = Rx + 5 = Tx -
7 8
PANEL V9OZ
6 3 4 5 2 7 8 1 8 7
6-G3LD_Cable.vsd View of pins: top-down,
as real terminal strip
Fig. 6-20 G.703 co-directional interface with cable for all interfaces
with RJ45 connector
For more information about the patch panel V9OZ see Section 6.5.4
“Connection via Cable for all Interfaces with RJ45 Connector”.
6.5.3.6.3. E1/T1 Interface G1LE

The connector is located on the optional piggyback module G1LE,
mounted face down on top of the Digital Interface G3LD.
The connecting RJ45 cable must be a shielded twisted pair cable
(SF/UTP) with a nominal impedance of 120 Ohm.
G3LD
INTERFACE
DIGITAL
(OPTION)
G1LE
X101
RL2
DATA
E1/T1 INTERFACE
RX
1
RL1
2
XL2
DATA
4
TX
XL1
53
7
8
8
1
6
6-G3LD_Cable.vsd
Fig. 6-21 Connector for E1/T1 interface (RJ45, 8 poles)


In addition, a patch panel V9OZ (see Section 6.5.4 “Connection via
Cable for all Interfaces with RJ45 Connector”) can be delivered that
allows connection of wires to “LSA Plus Quick Connect” type of
purpose.
DIGITAL
INTERFACE
G1LE
(OPTION) E1/T1 INTERFACE RJ45 Patch panel
G3LD
RX
DATA
TX
DATA
1 = RL2 1 = RL2
2 = RL1 2 = RL1
3 3
4 = XL2 6
RL2
RL1
XL2
XL1
CHASSIS
3 7 8 6
GND
5 = XL1 4 = XL2
X101 1 2 4 5
6 5 = XL1
CABLE V9OH
7 8
PANEL V9OZ
8 7
1 2 4 5 3 7 8 6
6-G3LD_Cable.vsd
View of pins: top-down,
Fig. 6-22 E1/T1 interface with cable for all interfaces with RJ45
connector
6.5.3.6.4. Optical Interfaces G1LO and G1LOa

When handling optical fibers please remember:
Fiber optic Installation



may result.
When connecting other external cables or mounting
the rear cover, ensure that the optical fibers are not
bruised or crimped.
a) Connector at rear of equipment

The connectors are located on the optional piggyback module G1LO
or G1LOa. These modules are mounted face down on top of the digital
interface G3LD.
G1LO provides E2000 connectors, G1LOa provides SFP modules
with LC connectors.
G1LO G1LOa
G3LD
INTERFACE
DIGITAL
(OPTION)
G1LO(a)
(E2000 or LC)
X701 ORX
OPTICAL INTERFACE
OTX
6-G3LD_Cable.vsd
Fig. 6-23 Connectors for optical fibers

b) Connection of G1LO via optical cable (E2000 or FC/PC)

The available optical cables have E2000 connectors at both ends or
E2000 and FC/PC connectors.
DIGITAL G1LO
INTERFACE (OPTION) OPTICAL INTERFACE
G3LD
X701 (OPT. CONN. RX TX

E2000) RD BU
1) 1)
6-G3LD_Cable.vsd
1) Optical cable type Connector

V9WP, V9WR E2000 – FC/PC
V9WQ, V9WS E2000 – E2000
Fig. 6-24 Optical Interface G1LO with optical cable
For the fiber optic connections, the NSD570 provides E-2000 Duplex
Compact 0.1 dB - SM APC mating adapters with 0.1 dB insertion loss.
This kind of adapter features a spring loaded metal shutter that avoids
laser radiation exposure when it is mated on one end only.
Fig. 6-25 E-2000 duplex compact mating adapters

These adapters match with E-2000™ 0.1 dB Duplex Compact and

Simplex SM APC fiber optic connectors that are suitable for
termination of fiber cable types according to ITU-T G.652, G.653,
G.654 and G.655. This kind of connector features integrated black
protective caps that avoid laser radiation exposure when they are
unmated.
Fig. 6-26 E-2000 duplex compact fiber optic connector
Fig. 6-27 E-2000 simplex fiber optic connector

c) Optical SFP modules for G1LOa

All supported SFP modules are designed in conformance with the SFP
Multi-Source Agreement (SFF document INF-8074i) and are hot
pluggable, i.e. they can be installed and removed from the operational
NSD570 equipment.
The supported SFP modules can provide the following interfaces:
• 2 Mbps, 850 nm, multi-mode, nominal distance 1 km, maximum
distance 2 km, intended for IEEE C37.94 applications.
• S-1.1 / 2 Mbps, 1310 nm, single-mode, nominal distance
30 km, maximum distance 50 km, intended for IEEE C37.94
applications, for connections to FOX515/512 or FOX615/612
multiplexer equipment or direct fiber connections.
• L-1.1 / 2 Mbps, 1310 nm, single-mode, nominal distance
60 km, maximum distance 80 km, intended for direct fiber
connections.
• X-1.2 / 2 Mbps, 1550 nm, single-mode, nominal distance
120 km, maximum distance 150 km, utilizable for long haul
direct fiber connections only.
• U-1.2 / 2 Mbps, CWDM 1550 nm, single-mode, nominal
distance 180 km, maximum distance 240 km, utilizable for
extra long haul direct fiber connections only.
Please refer to Hitachi ABB Power Grids for the latest list of supported
SFP modules. Only SFP modules recommended by Hitachi ABB
Power Grids can guarantee the specified functionality of the G1LOa
piggyback.
A plugged SFP module is secured in the SFP cage by a locking
mechanism. To remove the SFP module from the SFP cage this
locking mechanism must be released.
No tool or equipment is required to install or remove a SFP module.
To install SFP modules, the bail latch should be in the locked position.
The module is oriented so that the bail is on the left side of the SFP.
The module is pushed into the SFP cage carefully until a clicking
sound indicates that the module is locked (see also Fig. 6-28).
After disconnection of the optical cable, SFP modules can be removed
from the SFP cage by using the metal bail latch located on the left side
of the SFP module. Pull on the bail to unlock and remove the SFP
module (see also Fig. 6-28).

SFP module SFP module

Bail in locked position Bail in open position
install remove
Rx Rx
Tx Tx
Fig. 6-28 Optical SFP module installation
To protect optics, dust covers should always be installed when cables

are not connected.
Unplugged SFP modules should be stored in an ESD safe
environment.
d) Optical attenuators
Since some earlier used 850 nm SFP modules provide higher optical
output power than IEEE defines for its C37.94 standard, optical
attenuators may need to be inserted on the SFP transmitter,
depending on the multiplexer’s receiver robustness.
The following optical attenuator is intended for combination with the
850 nm SFP module:
• 10 dB LC/PC, 850 nm, multi-mode
For SFP transceivers with 1310 nm (L-1.1) or 1550 nm, the maximum
output power is higher than the receiver saturation. Optical attenuators
are therefore required when NSD570 equipment are directly
interconnected via short length optical fibers with low attenuation (e.g.
for test purposes).
The following optical attenuator is intended for combination with these
1310 nm (L-1.1) or 1550 nm SFP modules:
• 10 dB LC/PC, 1310/1550 nm, single-mode

e) Connection of G1LOa via optical cable (LC, FC/PC or ST)

The optical cables for G1LOa require standard duplex LC connectors
and can be terminated with duplex LC, ST, or FC/PC connectors on
the other end, depending on the required termination.
Duplex ST connector Duplex LC connector
Fig. 6-29 Duplex LC to ST adapter cable
Cable reference Connector Cable type

V9YE LC – ST Outside cabinet, multi-mode
This cable is intended for the direct connection of G1LOa with

FOX615/612 multiplexer equipment or 3rd party multiplexer equipment
complying with IEEE C37.94 standard connectors, placed outside the
communication cabinet.
To meet the optical output level requirements of the standard, optical
attenuators may be required to be plugged between the transmit
connector of G1LOa and the cable.
Dual FC/PC connector Duplex LC connector
Fig. 6-30 Duplex LC to FC/PC adapter cable

V9KW FC/PC - LC Inside cabinet, single-mode
V9KZ FC/PC - LC Outside cabinet, single-mode
These cables are intended for the direct connection of G1LOa with the
teleprotection interface of a multiplexer, providing FC/PC connectors
on single-mode fibers, placed inside or outside the communication
cabinet (e.g. FOX515 OTERM).
To meet the optical output level requirements of the corresponding
interface, optical attenuators may be required to be plugged between
the receive connector of the multiplexer and the cable.

Duplex LC connector Duplex LC connector
Fig. 6-31 Duplex LC to LC adapter cable

V9YG LC – LC Inside cabinet, multi-mode
V9YF LC – LC Outside cabinet, multi-mode
V9KU LC – LC Inside cabinet, single-mode
V9KX LC – LC Outside cabinet, single-mode
These cables are intended for the direct connection of G1LOa with the
teleprotection interface of a multiplexer, providing LC connectors,
placed inside or outside the communication cabinet (e.g. FOX515
OPTIF or FOX615 OPIC2).
To meet the optical output level requirements of the corresponding
interface, optical attenuators may be required to be plugged between
the receive connector of the multiplexer and the cable.

6.5.3.7. LAN Interface G3LL
6.5.3.7.1. Ethernet 10/100BaseT LAN interface

X201 RJ45
G3LL
LAN Interface
Ethernet Interface
TX+
DATA
TX
1
TX-
2
RX+
1
DATA
3
RX
RX-
6
8
4
5
7
8
75 75
PE
6-G3LL_Connector.vsd
Fig. 6-32 Connector for Ethernet interface (RJ45, 8 poles)

In addition, a patch panel V9OZ (see Section 6.5.4) can be delivered
that allows connection of wires to “LSA Plus Quick Connect” type of


purpose.
LAN Interface
G3LL RJ45 Patch panel
Ethernet Interface
1 = TX+ 1 = TX+
TX RX
2 = TX- 2 = TX-
75
DATA DATA
3 = RX+ 3 = RX+
PE
4 6 = RX-
75
5 4
RX+
CHASSIS
TX+
RX-
TX-
GND 6 = RX- 5
X201 RJ45 1 2 3 6 4 5 7 8
7 8
CABLE V9OH 8 7
PANEL V9OZ 1 2 3 6 4 5 7 8
6-G3LL_Cable.vsd
connector
6.5.3.7.2. Station bus

c) Connection to terminal block at rear of equipment
connector X500 of the LAN Interface G3LL.

X500
G3LL
LAN Interface
A
1
RS-485
B
2
GND
3
4
5
6
1
7
6-G3LL_Connector.vsd
Fig. 6-34 Connector for station bus interface (7 poles)
d) Station bus wiring

For a proper operation of the NSD570 LAN Interface it is necessary to
wire the station bus of the supply backplane G1LB (Pin 1, 2 and 3 of
the connector X103) to the station bus of the NSD570 LAN Interface
G3LL (Pin 1, 2 and 3 of the connector X500).
This can be done with the optional connecting cable “G3LL*CABLE
FOR STATION BUS/RTC SYNC”. The optional connecting cable
G1LB*CABLE FOR STATION BUS/RTC SYNC will then be
unnecessary.

6.5.3.8. Ethernet Interfaces G3LE, G3LM, G3LS

Since the Ethernet line interface G3LE, the Ethernet Management
interface G3LM and the Ethernet GOOSE LAN relay interface are
sharing their hardware platform, the physical wiring is similar.
6.5.3.8.1. General
a) Connectors at rear of equipment
IRIG-B connector (1)
G3LMa
Management LAN Interface
IRIG-B+
IRIG-B OUT
2
IRIG-B-
1 X2311 IRIG-B OUT

1
2 6-G3LM_Connector.vsd
SFP cage (2)
Interface selection switch (3)
Ethernet connector (4)

X102 RJ45
G3LM
Ethernet Interface
TX+
DATA
TX
1
8 TX-
2
RX+
DATA
3
RX
RX-
1
5
86
4
7
75 75
PE
6-G3LM_Connector.vsd
Fig. 6-35 Connectors of the Ethernet interface

There is an 8 pole RJ45 Ethernet connector for connection to a

10/100 Mbps Fast Ethernet network. The connecting cable must be a
Cat5e Ethernet cable SF/UTP according to ISO/IEC 11801 (electrical).
The green LED of the Ethernet connector indicates the existence of a
link while the yellow LED lights up when the interface is operating at
100 Mbps connection speed (see also (4) in Fig. 6-35).
In addition to the Ethernet connector the G3LE/M/S provides an SFP
cage for insertion of SFP modules (see also (2) in Fig. 6-35). To
activate the SFP module please move the interface selection switch to
the position towards the SFP module (see also (3) in Fig. 6-35).
Please note that the RJ45 connector is deactivated while the SFP
module is activated and vice-versa. The position of the switch
determines the active interface. Independently from the activated
interface the two LEDs of the RJ45 connector do always show the
actual interface status.
IRIG-B output connector (see also (1) in Fig. 6-35) is available on the
G3LE/M/S boards starting with hardware rubric number R0002.
b) Optical SFP modules

All recommended SFP modules are designed in conformance with the
SFP Multi-Source Agreement (SFF document INF-8074i) and are hot
pluggable, i.e. they can be installed and removed from the operational
NSD570 equipment.
The supported SFP modules provide the following interfaces:
• Fast Ethernet, 850 nm, multi-mode, nominal distance 0.5 km,
maximum distance 1 km
• Fast Ethernet, 1310 nm, multi-mode, nominal distance 0.5 km,
• Fast Ethernet, 1310 nm, single-mode, nominal distance 30 km,
Please refer to Hitachi ABB Power Grids for the latest list of
recommended SFP modules. Only SFP modules recommended by
Hitachi ABB Power Grids can guarantee the specified functionality of
these Ethernet Interfaces.
A plugged SFP module is secured in the SFP cage by a locking
mechanism. To remove the SFP module from the SFP cage this
locking must be released.
No tool or equipment is required to install or remove a SFP module.
To install SFP modules, the bail latch should be in the locked position.
The module is oriented so that the bail is on the left side of the SFP.
The module is pushed into the SFP cage carefully until a clicking
sound indicates that the module is locked (see also Fig. 6-36).

After disconnection of the optical cable, SFP modules can be removed

from the SFP cage by using the metal bail latch located on the left side
of the SFP module. Pull on the bail to unlock and remove the SFP
module (see also Fig. 6-36).
SFP module SFP module
Bail in locked position Bail in open position
install remove
Rx Rx
Tx Tx
Fig. 6-36 Optical SFP module installation
To protect optics, dust covers should always be installed when cables

are not connected.
Unplugged SFP modules should be stored in an ESD safe
environment.
When handling with optical fibers please remember:
Fiberoptic Installation


may result.
When connecting other external cables and also the
rear cover, ensure that the optical fibers are not
bruised or crimped.

c) Connection via cable for all interfaces with RJ45 connector,

In addition, a patch panel V9OZ (see section 6.5.4) can be delivered
that allows connection of wires to “LSA Plus Quick Connect” type of
purpose.
G3LM RJ45 Patch panel
Ethernet Interface
1 = TX+ 1 = TX+
TX RX 2 = TX- 2 = TX-
DATA DATA 75
3 = RX+ 3 = RX+
PE
75
4 6 = RX-
5 4
RX+
CHASSIS
TX+
RX-
TX-
GND 6 = RX- 5
X102 RJ45 1 2 3 6 4 5 7 8
7 8
CABLE V9OH 8 7
PANEL V9OZ 1 2 3 6 4 5 7 8
6-G3LM_Cable.vsd
connector
For more information about the patch panel V9OZ see section 6.5.4.
d) Connection via G3LMa cable

This cable is equipped with screwless (spring-cage) type terminals.


G3LMa
IRIG-B OUT
IRIG-B+
IRIG-B-
2 1 X2311 IRIG-B OUT
G3LMa CABLE FOR

RTC SYNC/STATION BUS
BN WH
Terminals
4 5
6-G3LMa_Cable.vsd
Fig. 6-38 Ethernet interface with cable for RTC synchronisation
6.5.4. Connection via Cable for all Interfaces with RJ45 Connector
The 1:1 patch cord cable V9OH and the patch panel V9OZ can be
used for all interfaces with RJ45 connector:
• G3LD: G.703 Interface
• G1LE: E1/T1 Interface
• G3LE: Ethernet Interface
• G3LL: Ethernet Interface
• G3LM: Ethernet Interface
• G3LS: Ethernet Interface
One type of the patch panel V9OZ is available:

• 1 x RJ45 connector plus 1 x LSA Plus Quick connector
LSA Plus Quick Connect is manufactured by KRONE. With this system

the connections to the patch panel can be made quickly without
soldering. An insertion tool (referred to as a KRONE tool), which is
supplied as an accessory, permits insulation displacement, connection
and cutting of the wire at the same time. For best results, a solid wire
of 0.5 mm diameter with a PVC insulation of 0.2 mm thickness should
be used.

6.5.4.1. Patch panel V9OZ with 1 x RJ45
Fig. 6-39 Patch panel V9OZ with 1 x RJ45
6.5.5. Internal connections

All internal connections within the Module Rack G7BI are provided by
Supply Backplane G1LB, Common Interface G3LC and Bus Plane with
Front Cover G1LA except for the optional Display Panel G1LC.

6.5.6. Display Panel G1LC

The optional Display Panel G1LC is assembled to the module rack
G7BI, replacing the blanking cover plate that is mounted in front of the
power supply units. An enclosed ribbon cable connects the Display
Panel to the adjacent Common Interface G3LC as follows:
Fig. 6-40 Mounting of the Display Panel G1LC
Caution:
The ribbon cable has to be

mounted as shown in the
picture (i.e. cable leaving
the socket/plug on G1LC
downwards).
Fig. 6-41 Correct connection of the ribbon cable

6.6. Photographs
Fig. 6-42 Front view of the NSD570 module rack, equipped with two
line interfaces - each of them operating four Relay
Interfaces G3LR - and the optional Display Panel G1LC.
Fig. 6-43 Rear view of the NSD570 module rack, equipped with an
Analog Interface G3LA and a Digital Interface G3LD - each
of them operating four Relay Interfaces G3LR, with
connecting cables (rear cover removed).

7. Commissioning


DANGER


Warning labels

observed.
Inserting and removing of plug-in modules

Commissioning August 2021 7-1


cable.
Back cover

be disconnected.
ESD protection

Laser / LED

Laser / LED
Using HMI570

test mode).
7-2 August 2021 Commissioning




LAN Interface G3LL
The LAN Interface G3LL contains a lithium battery.

DANGER
Danger of explosion exists if the lithium battery is
incorrectly replaced. Replace only with the same or
equivalent type recommended by the manufacturer.
For replacing and inserting the battery always use a
potentially-free soldering iron.
Check the polarity before inserting the battery.


7.2. Testing the communication channel

It is essential that the behavior and the characteristics of the
communication link between the sets of teleprotection equipment are
checked prior to final commissioning. This is necessary to confirm the
design criteria used for engineering the system or, if the criteria were
inaccurate, to take the appropriate corrective action.
When an analog communication link is installed, it is of interest
whether the frequency response is appropriate and whether there are
noise or spurious/interference signals present in the bandwidth used of
the NSD570.
When a digital communication link is installed, it is of interest whether
there are bit errors present in the channel used of the NSD570.
When an Ethernet communication link is installed, it is of interest
whether the guard/trip packets are handled with highest priority by the
network nodes, especially during high network traffic when packets
may be lost in the channel used of the NSD570.
In case the NSD570s are in a point-to-point connection, it is necessary
to know whether the permissible line attenuation (analog) or the
permissible line length (digital, Ethernet) is not exceeded.
It is assumed that the communication link is commissioned properly
before the teleprotection equipment is set into operation.
In any case it is advisable to measure the transmission delay that is
introduced by the communication link. Refer to Section 5.13.2 for
remarks about “Transmission Time”. This delay can be taken into
account for the reception threshold of the cyclic and the manual loop
test by appropriate HMI570 configuration (see Section 5.5.3).
7.3. Commissioning the equipment

Once the prevailing conditions of the communication channel have
been established, it is permissible to proceed with commissioning the
equipment itself. Before switching on the power supply, perform the
checks below. Correct any deviations or shortcomings immediately.
7.3.1. Preliminary inspection and checks

a) Check that the cabinet is grounded in accordance with regulations.
b) Check that the polarity of the power supply is correct.
c) Check that the external connections to the cabinet terminals are
correct in relation to user’s diagrams of the cabinet.
d) Check that all the internal connections have been made and that
they are correct.
7-4 August 2021 Commissioning

e) Check that all the modules are properly inserted in their intended
slots.
f) Check the configuration and settings in relation to the settings given
by the customer.
7.3.2. Checks according to commissioning instructions

Since the equipment is tested according to the Programming and
Testing Instructions 1KHW000898-EN prior to delivery, only those
settings have to be made that are necessary to adapt the equipment to
the operating conditions prevailing in the customer’s plant.
The Commissioning Instructions are given in document 1KHW000900-
EN, which is available in Section 12 “Annex”.
Caution Do not close/establish the connections to the

protection devices until the NSD570 is properly
commissioned.
7.3.3. HMI570 functions to support commissioning

The following functions of the HMI570 can be used to simplify the
measurements and to reduce travel during commissioning:
a) Manual loop test

b) Local test mode
c) Remote test mode
Refer to Section 3.5.18 “Test facilities for the Line Interfaces” for a
detailed description of the above mentioned test facilities.

8. Operation and maintenance

Warning labels

observed.

DANGER



Operation and maintenance August 2021 8-1


cable.
Back cover

be disconnected.
ESD protection


Laser / LED

Laser / LED
8-2 August 2021 Operation and maintenance

Using HMI570

test mode).



Caution The following safety instructions must be strictly

observed to prevent injury to persons and damage
to plant.

• It is important that these Operating Instructions are read and fully

comprehended by all people involved including personnel that has
already undergone training and is otherwise qualified before
changing the configuration or carrying out maintenance etc.
• Take note of the instructions in Section 6.3 “Unpacking” to avoid
damage to the equipment while being transported.
• Cabinets that have not been secured to the floor can tip forwards
when the hinged equipment frame is opened.
• Safety devices such as cover plates must not be removed or
bypassed.
• Pay attention to high-voltage warnings.
• Before switching on the power supply, check that the circuit is
protected by a miniature circuit breaker and the equipment/cabinet
is properly grounded and check the polarity and value of the power
supply.
• It is not permitted to insert or withdraw modules during operation;
the power supply must be switched off first.
• The modules contain CMOS integrated circuits that can be
damaged by electrostatic discharge. It is important to take certain
precautions to prevent electrostatic discharge before removing the
packing or withdrawing them from the racks. Indispensable
precautions to avoid ESD damage are earthing of people working
on the modules and a working surface that protected against
electrostatic discharge. Only transport modules in their original
packing or installed in racks.
• It is not permitted to modify the equipment in any way.
8.2. Operation
8.2.1. Normal operation

The LEDs on the front of the equipment indicate its status. Only the
green LEDs should be lit in normal operation. The red LEDs indicate
an alarm status and should not light during normal operation.
Refer to Section 3.3.4 “Front plate Signals and Controls” where a
detailed explanation of the various LEDs is given.
8.2.2. Equipment failure

Refer to Section 9 “Troubleshooting” for a list of possible failures.
A faulty operation will be indicated by red LEDs on the front plate of
the module rack. In case there is some fault with the system or the
link, red LEDs in the “SYSTEM ALARMS” field of the line interface on
the front plate will light up. If there is a hardware failure on a specific
module, its “Ok / Fail” LED will turn red.

Refer to Section 3.3.4. “Front plate Signals and Controls” where a

detailed explanation of the various LEDs is given.
If any of the red alarm LEDs of the system light up, the corresponding
alarm contact on the common interface G3LC will also operate after
the configured alarm pick up delay.
The “Upload Alarm” function or the event recorder functions of the
HMI570 can be used to see the details of the alarms, see Sections
4.10.6.2 “View Events” and 4.10.7.2 “Upload Alarm”.
Refer to Section 9.3.11 “List of low level alarms and corrective actions”
for details about causes of alarms.
8.3. Maintenance
All NSD570 modules are subject to a thorough final test following
manufacturing and the complete equipment is calibrated and tested
before shipment.
The most important functions are performed digitally by the software
and are therefore not subject to ageing. Because of the digital
techniques involved, the settings made by means of the user interface
program HMI570 and the stability of the equipment as a whole are
guaranteed over a long period of time.
The various processors on the modules include a number of self-
monitoring functions, which together with the loop test performed at
periodic intervals continuously check the operation of the modules and
the availability of the communications channel as a whole.
Nevertheless, testing at periodic intervals is recommended. The
frequency of testing depends very much on the operating conditions in
the particular installation, but should not be less than once every two
years. The following periodic measurements are recommended.
8.3.1. Periodic functional checks

It is important that the reasons for readings, which diverge widely from
values recorded during commissioning, be found, even if this means
checking the entire equipment.
Checking and testing must be carried out by qualified and authorized
personnel only, using suitable instruments. Incorrect settings can
impair the proper operation of the equipment.
8.3.1.1. Check input power supply voltage

Verify that the external power supply voltage is within tolerance.
For power supply module G3LH:

48 V DC … 250 V DC ±20% or 100 V AC … 240 V AC -15% +10%

For power supply module G3LI (replacement for G3LH):
24 V DC … 60 V DC ±20%
For power supply module G3LK (replacement for G3LH):
110 V DC … 250 V DC ±20% or 110 V AC … 230 V AC -15% +10%).
8.3.1.2. Checks during operation

The ability of the equipment to function correctly can be checked by
manually initiating the loop test: simply press the button “Loop Test” on
the front plate of the module rack. Provided that the signal transmitted
by the test is received back again within the allotted time, the LED
“Trip” lights up and the “Guard” LED is deactivated for about 3 s to
confirm that the test was successful. If not, the “Ok / Fail” LED flashes
for about 5 s.
Should the equipment fail the loop test in two consecutive attempts, it
must be removed from service and checked according to the following
sections.
In case of the NSD570 Analog, the transmitting and receiving levels
shall be checked by means of the HMI570 (see Section 8.3.1.6 “Check
AF line levels”) after completing the loop test. Readjustment is
unnecessary, provided that the receiver level does not vary by more
than ±3 dB from its nominal value. If the discrepancy is greater, the
transmitter level at the remote station and the attenuation of the
communications channel should be checked before readjusting the
receiver.
In case of the NSD570 Digital, the quality of the communications
channel shall be checked by means of the HMI570 (see Section
8.3.1.7 “Check bit error rates”) after completing the loop test. This may
be verified – for example – by using a bit error rate test equipment,
which provides the required data interface and transmission rate. It
shall be connected to the communications channel instead of the
NSD570 Digital. Corrective actions are unnecessary, provided that the
measured bit error rate is less than 1E-07. The peak voltage of the
output signal at the remote station and the attenuation of the
communications channel (i.e. the peak voltage of the signal at the
receiver) should be checked before continuing with fault diagnostics.
In case of the NSD570 Ethernet, the quality of the communications
channel shall be checked by means of the HMI570 (see Section
8.3.1.8 “Check bit error rates”) after completing the loop test. This may
be verified – for example – by using a LAN/network test equipment.
Corrective actions are unnecessary, provided that the measured

Packet Loss Rate is less than 0.1% and the measured transmission
time is less than 10 ms (assuming a network delay of 6 ms).

8.3.1.3. Check status data

The status data of both the local and remote equipment can be
uploaded in the HMI570, using the function Upload Status in the
Status / Alarm menu. A printout of the status data can be taken for
documentation purpose and compared with the previous status data.
8.3.1.4. Check alarm events

The alarms stored by the built in event recorder of the NSD570
terminals can be inspected. Upload the stored events by activating
Upload Latest … Events in the Event Recorder menu.
8.3.1.5. Alarm polling for several NSD570 in a substation
Note: This function is available only in association with the

LAN Interface G3LL, the Management LAN Interface
G3LM or when using HMI570 “PC” version 1.14 or
higher.
To check the alarm status of a number of NSD570 terminals
connected by the station bus, the function “Alarm polling” can be used
(see also Section 9.3.13 “Alarm polling”). The alarm status of the
addressed terminals is polled in selectable intervals and in case of any
alarm, the alarm text is recorded in a file and displayed on the screen.
8.3.1.6. Check AF line levels

The HMI570 can be used to check the levels of the AF signals
transferred over the analog NSD570 link. The function is accessible by
clicking on the Upload Status link in the Status / Alarm menu. A
printout of the status data can be taken for documentation purpose
and compared with the previous status data.

8.3.1.7. Check bit error rates

The HMI570 can be used to check the prevailing bit error rate (BER) of
the digital NSD570 link. The function is accessible by clicking on the
Upload Status link in the Status / Alarm menu. A printout of the
status data can be taken for documentation purpose and compared
with the previous status data.
Note: The Bit Error Rate (BER) short term measurement

does only have an adequate accuracy if the prevailing
BER is higher than 1E-05!
The measurement of the short term average BER
takes 200 seconds, the long term average BER is
only displayed after the equipment is continuously
powered for at least 4.5 hours (262 minutes).
8.3.1.8. Check Packet Loss Rates and Transmission Times

The HMI570 can be used to check the prevailing Packet Loss Rate
(PLR) and transmission time measurements of the Ethernet NSD570
link. The function is accessible by clicking on the Upload Status link in
the Status / Alarm menu. A printout of the status data can be taken
for documentation purpose and compared with the previous status
data.
8.3.1.9. Removing the equipment from service for testing

1. Switch off the equipment and open all isolating terminals to the
protection equipment afterwards.
2. Switch on the equipment again by closing the circuit breakers.
3. Set the equipment to the Local Test Mode by clicking on the
designated button in the Commissioning menu of the HMI570.
4. Check that the unit is indeed in the local test mode (corresponding
warning message appears on screen and the “Ok / Fail” LED of the
line interface flashes).
5. Inject commands at the local terminal blocks and check the local
command outputs for correct operation.
(Note: The trip counters will count the local commands as well!).

6. Deactivate the Local Test Mode by clicking on the designated

button in the Commissioning menu of the HMI570.
7. Carry out the manual loop test according to Section 8.3.1.2
“Checks during operation”.
8. The isolating terminals to the protection equipment may be closed
again, provided that there is no alarm.
9. If required, synchronize the trip counters in the local and in the
remote station by resetting them (menu Status / Alarm -> link Trip
Counter -> link Reset Trip Counter: mark check box “All” and
click on the button Reset Trip Counter).
8.3.1.10. Checking the entire link

Following any changes made to the NSD570 equipment or other
components of the communications channel, it is recommended to
repeat the commissioning procedure described in the document
“Commissioning Instructions” 1KHW000900-EN in Section 12 “Annex”
for the units at both ends of the line.
Replace any modules found to be faulty. It is not recommended to
carry out any repairs on site.

9. Troubleshooting
Should the communication between two NSD570 units fail, either the
communications channel or one of the NSD570 modules can be
defective.
Following a systematic procedure is the quickest way to localize and
eliminate a fault.


DANGER



Troubleshooting August 2021 9-1


cable.
Safety and monitoring facilities
Mechanical safety facilities such as cover plates

DANGER must not be removed or by-passed.
Back cover

be disconnected.
ESD protection

Using HMI570

test mode).
9-2 August 2021 Troubleshooting



Laser / LED

Laser / LED
Caution Read the following safety instructions carefully

before attempting to locate faults.
• Fault-finding may only be conducted by properly trained personnel

that have been authorized to do so.
• It is not permitted to insert or withdraw modules during operation;
the power supply must be switched off first.
• The modules contain CMOS integrated circuits that can be
damaged by electrostatic discharge. It is important to take certain
precautions to prevent electrostatic discharge before removing the
packing or withdrawing them from the racks. Indispensable
precautions to avoid ESD damage are earthing of people working
on the modules and a working surface that is protected against
electrostatic discharge. Only transport modules in their original
packing or installed in racks.
• The modules are manufactured according to the latest SMD
technology. Repair at the component level is therefore neither
intended nor recommended. As a rule, corrective action is confined
to locating and replacing defective modules.
• Dangerous voltages can occur on the connections to the modules
Common Interface G3LC and Relay Interface G3LR. Take care not
to touch these connections under any circumstances.
• It is not permitted to modify the equipment in any way.

9.2. Fuses
Used fuses in the equipment (per power supply unit):
G3LH: 2.5 AT / 250 V (5 x 20 mm)
G3LI: 6.3 AT / 250 V (5 x 20 mm)
G3LK: 2.5 AT / 250 V (5 x 20 mm)
9.3. Alarms
9.3.1. Alarm concept

The alarm concept of the NSD570 system is designed to
• detect and locate the sources responsible for abnormal operation of
the system, and
• provide information about the kind of problems detected.
The NSD570 alarms are hierarchically organized, with high level

alarms on top and a variety of low level alarms at the bottom of the
hierarchy. Low level alarms are grouped into 4 categories:
• Common alarms and relay interface alarms
• Analog interface alarms
• Digital interface alarms
• Ethernet interface alarms
Begin and end of all low level alarms are recorded with date/time
stamps by the event recorder integral to the NSD570.
The high level alarms can be signaled - with a configurable delay/hold
time - on the various outputs of the Relay Interfaces G3LR.
A number of alarms are generated by the HMI570. These HMI-alarms
are not mapped into high level alarms and cannot be routed to relay
outputs.
Three user alarms can be mapped on the outputs on G3LR. The alarm
sources to generate these user alarms can be configured individually
by logical OR-gating of any from the high level alarms “HW Alarm”,
“HW Warning”, “Link Alarm”, “Transmit Alarm” and “Receive Alarm”
with some special alarms (Tx/Rx Signal, SNR/BER/PLR alarm). This is
valid for the local alarms as well as for the remote alarms (except for
“HW Warning”).
If the alarm output of the user alarm is set to “delayed”, then the
programmed pick up delay for the outputs will be activated by the first
configured alarm of the list that appears, and the hold time will be
counted down to zero when the last configured alarm in the list has
disappeared.
If the alarm output of the user alarm is set to “undelayed”, then the

outputs will be activated instantaneously without any additional pick up

delay by the first configured alarm of the list that appears, and will be
de-activated without any additional hold time when the last configured
alarm in the list has disappeared.
For each NSD570 in the rack there is an alarm relay with switch over
contacts available on the Common Interface G3LC. It is activated if
any of the local alarms of the corresponding device appears.
The programmed alarm pick-up and hold delay is valid for these
outputs too.
Note: In case of detected low level alarms which do not

allow reliable operation anymore, the command
outputs are blocked.
Note: The remote alarms are not signaled on the alarm

outputs of the local G3LC. But they are included in the
“System Alarm” which may be mapped on any
available output of the Relay Interfaces G3LR.
9.3.2. Problem localization

If for both equipment in a link the state of hardware alarms and link
alarms are known, the source of the problem can be localized to one
or several of the four major fault areas of a link marked in Fig. 9-1.
Table 9-1 shows how the affected areas can be found from the alarm
information.
Note that an equipment’s link alarm is only considered to be valid
when no hardware alarm is present.
Equipment A Equipment B
Channel A to B
Commands NSD570 NSD570 Commands

Channel B to A
9-Fault-location.vsd
Fig. 9-1 The four major fault location areas of an NSD570 link

Equipment A Equipment B
Hardware Link Hardware Link Problem localized in
Alarm Alarm Alarm Alarm
No No No No -
No No No Yes Channel A > B
No Yes No No Channel B > A
No Yes No Yes Channels B > A and A > B
Yes X No X Equipment A
No X Yes X Equipment B
Yes X Yes X Equipment A and B
Table 9-1 Alarm localization with link and hardware alarms
9.3.3. Alarm pick up and hold delay

The alarm pick-up time and the alarm hold time can be set in the range
from 1 … 15 seconds. They are valid for all alarms in common, i.e. for
the high level alarms and the user alarms (if their alarm output is set to
“delayed”), which are mapped on the outputs of G3LR, and for the
alarm relays on G3LC that reflect the local alarm of the two devices in
a rack.
9.3.4. High level and user alarms
The following table lists the high level and the user alarms, their
meaning and output devices (red LEDs on equipment front; switch
over contacts on G3LR which are programmable by means of the
HMI570; user defined alarms):
High level or Re- Meaning Displayed Output Source

user alarm mark by LED via for
G3LR user
contact alarm
HW Warning The equipment is operational, X X X
but one of the redundant “Unit 1”,
power supply units (PSU) “Unit 2”
failed.
HW Alarm Signals that a hardware X X X
problem in the equipment “OK / Fail”
generating the alarm has been (on the
detected. modules
concerned)


G3LR user
contact alarm
Link Alarm Indicates that the quality of the X X
received signal is insufficient.
Possible reasons are
excessive noise, low input
level, interference, faulty
transmitter at the remote side,
interrupted connections, …
Transmit Signals a problem detected in X X X
Alarm the equipment's transmit part. “Transmit”
Receive Signals a problem detected in X X X
Alarm the equipment's receive part. “Receive”
Transmit Indicates that the quality of the X
Signal output signal is insufficient.
Possible reason is low output
level.
Receive Indicates that the quality of the X
Signal received signal is insufficient.
Possible reasons are
excessive noise, low input
level, interference, faulty
transmitter at the remote side,
interrupted connections, …
Low level alarms resulting from
communication errors between
multiplexer equipment are
ignored.
SNR / BER / Indicates that either the signal X
PLR to noise ratio of the analog
input signal is too low or the bit
error rate of the digital input
signal is too high or the ratio of
received to sent packets of the
Ethernet interface is too high.
Local Alarm 1) OR function of all alarms of the X X
local equipment “Local”
(except HW-Warning).
Remote 2) OR function of all alarms of the X X
Alarm remote equipment “Remote”
(except HW-Warning).
System Local Alarm OR Remote Alarm X
Alarm


G3LR user
contact alarm
Main 3) Main Line Interface in 1+1 X
Channel operation mode has HW
Failure and/or link alarms. The main
as well as the stand-by Line
Interface is able to detect Main
Channel Failure.
Stand-by 3) Stand-by Line Interface in 1+1 X
Channel operation mode has HW
Failure and/or link alarms. The main
as well as the stand-by Line
Interface is able to detect
Stand-by Channel Failure.
Table 9-2 High level alarms
Remarks:
1) For each line interface, a switch over contact is available on G3LC
2) The alarm is sent via EOC over the link to the remote equipment, so
that the following equation holds: Remote Alarm on Local
Equipment = Local Alarm on Remote Equipment.
3) Only available with analog and digital line interface configured for
1+1 device operation mode.
9.3.5. Low level common alarms and relay interface alarms

Self-testing routines continuously monitor the operational status of the
NSD570. Alarm is given in the following cases:
• The system detects incompatibilities with the hardware used
(during startup)
• The short circuit supervision for the two solid state outputs on the
relay interfaces has picked up (Imax > 2.5 A approx.)
• Tx single component failure in one of the two input circuits on the
relay interfaces
• HW Warning: undervoltage alarm of one of the two redundant
power supply modules
• Alarm: cyclic loop test failure (after 3 unsuccessful attempts)
• Rx single component failure (guard and command signals being
either received simultaneously or completely lost)
• Tx command duration (if monitoring is enabled, the guard signal is
sent again after the configured maximum Tx command duration
time has elapsed)

• Checksum error (internal and external program and data memory)

• Internal system clock error / external synchronization error
• External power supply and internal supply voltage failure
• Real Time Bus communication error
• Hardware and/or software configuration error
• EOC checksum error
• Alarm signal from the remote station
• Local or remote test mode activated

The following table lists the low level common alarms and the relay
interface alarms, and shows their influence on the high level alarms.
High Level Alarm
Main & Stby.

Ch. Failure
Interface)
Transmit
OK / Fail
Warning
Receive
Remote
Remark
System
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Local
Code
(Line
Link
HW
HW
Low Level Alarm
HW Version Common Interface and Bus 0.20 X X X X OK
Plane do not match
Overcurrent in MOSFET output 2 4) 0.19 X X X X OK
Overcurrent in MOSFET output 1 4) 0.18 X X X X OK
Single component failure input 2 4) 0.17 X X X X X OK
Single component failure input 1 4) 0.16 X X X X X OK
Error Relay Interface 4 TPE 2 (N84) 5) 0.14 OK
Micro controller FLASH verify error 0.5 X X X X X Fail
5 V supply voltage failure 0.4 X X X X X OK
Warning: Undervoltage redundant supply 2 10) 0.3 X OK
Warning: Undervoltage redundant supply 1 10) 0.2 X OK
Undervoltage alarm supply 2 6) 10) 0.1 X X X X OK
Undervoltage alarm supply 1 7) 10) 0.0 X X X X OK
Program memory internal CRC check failed 1.31 X X X X X Fail
Program memory SDRAM CRC check failed 1.30 X X X X X Fail
Data memory lookup table CRC check failed 1.29 X X X X X Fail
Program memory internal CRC add. 1.28 X X X X X Fail
segment failed
DSP in safe operation mode 9) 1.27 Fail
SDRAM data memory check failed 1.26 X X X X X Fail
Internal data memory check failed 1.25 X X X X X Fail
Program Memory micro controller CRC 1.24 X X X X X Fail
check failed
Remote test mode active 1.21 X X X Flashing
Local test mode active 1.20 X X X Flashing
Wrong time from RTC 1.18 X X X OK
No signal (IRIG-B) on RTC 1.16 X X X OK
More Relay Interfaces configured than 5) 1.12 X X X OK
plugged
Wrong slot for Line Interface 1.10 X X X X X Fail
Configuration error 1.7 X X X X X Fail
Link failure: command outputs set to a pre- 1.6 X X X X OK
defined state
Loop test error 1.5 X X X OK

High Level Alarm
Main & Stby.

Ch. Failure
Interface)
Transmit
OK / Fail
Warning
Receive
Remote
Remark
System
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Local
Code
(Line
Link
HW
HW
Low Level Alarm
Unblocking pulse 8) 1.4 OK
Remote alarm 1.3 X OK
CRC failure EOC 1.2 X X X X OK
Simultaneous trip and guard received 1.1 X X X X X OK
No trip and no guard 1.0 X X X X X X OK
G3LS Interface Alarm 4.31 X X X OK
Tx continuous command H 5) 4.19 X X X X OK
Tx continuous command G 5) 4.18 X X X X OK
Tx continuous command F 5) 4.17 X X X X OK
Tx continuous command E 5) 4.16 X X X X OK
Tx continuous command D 5) 4.15 X X X X OK
Tx continuous command C 5) 4.14 X X X X OK
Tx continuous command B 5) 4.13 X X X X OK
Tx continuous command A 5) 4.12 X X X X OK
Comm. error Relay Interface 4 TPE 2 (N84) 5) 4.11 X X X OK
Continuous command alarm 5) 4.0 X X X X OK
Table 9-3 Low level common alarms and relay interface alarms
Remarks:
4) Only in combination with other relay interface alarms; the
corresponding “Ok / Fail” LED of the affected relay interface lights
up red
5) Only in combination with other relay interface alarms
6) LED “Supply Unit 2” lights red
7) LED “Supply Unit 1” lights red
8) Generates an entry in the event recorder only and activates an
output contact, if configured
9) No high level alarm is generated. Only the “Ok / Fail” LED lights
up red and the corresponding G3LC system alarm relay contact is
closed.
10) If an “Undervoltage of redundant supply 1/2” condition is detected,
the behavior depends on the Redundant Power Supply Failure
setting found in the Alarm Settings dialogue of the line interface:

• if Redundant Power Supply Failure is set to HW Warning, then

Warning: Undervoltage redundant supply 1/2 and the high level
alarm HW Warning is raised.
• if Redundant Power Supply Failure is set to HW Alarm, then
Undervoltage alarm supply 1/2 and the high level alarm HW
Alarm is raised.
In the following sections, the low level alarms for the Analog interface,
the Digital interface and the Ethernet interface can be found. However,
the influence on the high level alarms “Transmit Signal” and “Receive
Signal” is not shown in the corresponding tables. They are associated
with low level alarms as follows:
Interface Transmit Signal Receive Signal

Transmit level
Analog SNR alarm or Receive level alarm
alarm
BER alarm or Loss of Signal G.703 or
Digital no assignment LOF Loss of Frame or LFA Loss of Frame
Alignment
Transmission time alarm or LOS Loss of
Ethernet no assignment
Signal
Table 9-4 Transmit and receive signal alarm
9.3.6. Analog interface alarms

The following criteria are continuously monitored and produce alarms:
• Tx signal level drop off below configured limit (- dB from nominal)
• Rx signal level out of configured limits (± dB from nominal)
• Internal supply voltage failure
• The SNR in 4 kHz noise bandwidth is lower than the threshold
according to Table 9-5:
Bandwidth [Hz] SNR alarm threshold [dB]
120 6
240 6
360 6
480 6
960 9
1200 10
2400 13
2800 14
Table 9-5 SNR alarm threshold

The following table lists the low level analog interface alarms, and
shows their influence on the high level alarms.
High Level Alarm
Main & Stby.

Ch. Failure
Interface)
Transmit
OK / Fail
Warning
Receive
Remote
Remark
System
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Local
Code
(Line
Link
HW
HW
Low Level Alarm
SNR Alarm 2.6 X X X X X X OK

Receive level alarm 2.5 X X X X X X OK
Transmit level alarm 2.4 X X X X OK
+/- 12 V supply voltage failure 2.0 X X X X X Fail
Table 9-6 Low level analog interface alarms
9.3.7. Digital interface alarms

• FPGA initialization failure
• Address error
• Synchronization error
• Bit error rate above the configured level
• LOS Loss Of incoming Signal (G.703/E1/T1/Optical)
• AIS Alarm Indication Signal (G.703/E1/T1/Optical)
• LFA Loss of Frame Alignment (E1/T1/Optical OTERM/OPTIF)
• LOF Loss of Frame (Optical)
• RRA Receive Remote Alarm (E1/T1/Optical)
• Laser failure (Optical)
• ALS Automatic Laser Shutdown is active (Optical)
The following criteria are monitored during start-up and produce

alarms:
• Missing piggyback (if configured) or not supported by the firmware
loaded on G3LD or the piggyback does not match the configuration
• Missing SFP transceiver
• FPGA CRC/loading failure on G3LD
• Specific E1/T1 framer errors on G1LE and G1LO

The following table lists the low level digital interface alarms, and
shows their influence on the high level alarms. Some alarms are only
generated with the corresponding piggyback plugged.
Specific High Level Alarm

Piggy-
backs
Alarms
Main & Stby.

Ch. Failure
Interface)
Transmit
OK / Fail
Warning
Receive
Remote
System
G1LOa
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
G1LO
G1LE
Local
Code
(Line
Link
HW
HW
Low Level Alarm
ALS Automatic Laser Shutdown is 3.30 X X X X X OK
active
SFP transceiver not plugged 3.29 X X X X X X X Fail
Laser Failure 3.28 X X X X X X X Fail
Remote equipment has wrong 3.25 X X X X X OK
address
BER Bit Error Rate alarm 3.24 X X X X X X OK
Alarm Indication Signal G.703 3.21 X X X X X X OK
Loss of Signal G.703 3.20 X X X X X X OK
Pattern synchronization error 3.17 X X X X OK
Piggyback does not match 3.14 X X X X X Fail
configuration
Read error from E1/T1 framer 3.13 X X X X X X X Fail
Write error to E1/T1 framer 3.12 X X X X X X X Fail
LOF Loss of Frame 3.9 X X X X X X X OK
Piggyback missing 3.8 X X X X X Fail
LOS Loss of Signal 3.7 X X X X X X X X X OK
AIS Alarm Indication Signal 3.6 X X X X X X X X OK
LFA Loss of Frame Alignment 3.5 X X X X X X X X OK
RRA Receive Remote Alarm 3.4 X X X X X OK
FW version does not support 3.3 X X X X X Fail
piggyback
Initialization failure in FPGA 3.2 X X X X X Fail
CRC failure while loading FPGA 3.1 X X X X X Fail
FPGA not loaded 3.0 X X X X X Fail
Table 9-7 Low level digital interface alarms

9.3.8. Ethernet interface alarms

• Remote Equipment has different guard packets sending interval
• Remote Equipment has different WAN protocol version
• LOS Loss Of incoming Signal
• Packet Loss Rate alarm
• Transmission Time alarm
• Transmission Time warning
• Duplicate IP address in subnet
• Laser failure (Optical)
• ALS Automatic Laser Shutdown is active (Optical)
The following criteria are monitored during start-up and produce

alarms:
• Default WAN protocol password
• Missing SFP transceiver
• FPGA loading failure
The following table lists the low level Ethernet interface alarms, and
shows their influence on the high level alarms.
High Level Alarm
Interface)
Transmit
OK / Fail
Warning
Receive
Remote
System
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Local
Code
(Line
Link
HW
HW
Low Level Alarm

ALS Automatic Laser Shutdown is active 3.30 X X X X OK
SFP transceiver not plugged 3.29 X X X X X Fail
Laser Failure 3.28 X X X X X Fail
Remote Equipment has different guard 3.27 X X X X OK
packets sending interval
Remote Equipment has different WAN 3.26 X X X X OK
protocol version
Duplicate IP address in subnet 3.23 X X X X X OK
Packet Loss alarm 3.22 X X X X X OK
Transmission Time alarm 3.19 X X X X X OK
Transmission Time warning 3.18 OK
Default WAN protocol password 3.11 X X X OK
LOS Loss of Signal 3.7 X X X X X OK
FPGA not loaded 3.0 X X X X Fail
Table 9-8 Low level Ethernet interface alarms

9.3.9. Management interface alarms

The alarms and warnings of the Management LAN Interface G3LM are
not part of the alarm concept described in the previous sections since
G3LM is no line interface and has a completely different functionality.
G3LM alarms and warnings are not captured during alarm polling and
are not available in the SNMP alarm table. They can only be accessed
by connecting to G3LM with HMI570 and uploading them. If the
Ethernet link is down, G3LM has to be connected over the serial port
of the NSD570 equipment.
A few alarm cases are indicated by the LAN LEDs (Ok/Fail, Link) on
the front plate:
Ok/Fail Link Description

Ok On Everything is ok.
Ok Off There is no link (electrical or optical).
Fail On There is one or more alarms on the G3LM that do not
influence the Ethernet link.
Fail Off There is one or more alarms on the G3LM that do
interrupt the Ethernet link.
Ok Blinking 2 seconds period: Automatic Laser Shutdown (ALS)
is active – laser is off. During ALS restart, the link
LED blinks fast for 2 seconds indicating that the laser
is on. Only possible if SFP/Ethernet switch is set to
SFP and ALS is configured.
Ok n/a New firmware is being written to flash memory.
blinking
after FW
download
Table 9-9 LAN LEDs

The following table lists all available alarms and warnings on G3LM:
Warning
Ok / Fail
Alarm
Link
LED
LED
Description
FPGA not loaded x Fail Off
Ethernet link down x Ok Off
Wrong time from RTC x Ok On
No signal (IRIG-B) on RTC x Ok On
SFP/Ethernet switch error x Fail Off
SFP transceiver not plugged x Fail Off
SFP transceiver signal loss x Ok Off
SFP transceiver laser failure x Fail Off
User file not loaded (parse error) x Fail On
Duplicate IP address in subnet x Fail Off
SNTP client out of sync x Ok Off
HW version insufficient for SNTP x Ok Off
Default configuration loaded x Ok On
Default users loaded x Ok On
Default SSL keys loaded x Ok On
User activity logfile full x Ok On
ALS Automatic Laser Shutdown is active x Ok On
Alarm polling cycle is too short x Ok On
SNMP alarm table is full - too many alarms x Ok On
Table 9-10 G3LM alarms and warnings
9.3.10. GOOSE LAN interface alarms

The alarms of the GOOSE LAN Interface G3LS are not part of the
alarm concept described in the previous sections since G3LS is not a
line interface and has a completely different functionality. G3LS alarms
are not captured during alarm polling and are not available in the
SNMP alarm table. They can only be accessed by connecting to G3LS
with HMI570 and uploading them. G3LS has to be connected over the
serial port of the NSD570 equipment.
Some G3LS alarms are reported to the OK/Fail LED of the Relay
Interface 1.
All alarms except for “Wrong slot for G3LS” activate the “G3LS
Interface Alarm” (see Table 9-3) of the corresponding line interface.

INTERFACE 1
Ok / Fail LED
RELAY
Description
ALS Automatic Laser Shutdown is active Ok
SFP transceiver not plugged Fail
SFP transceiver laser failure Fail
RTB CRC error Fail
RTB misalignment Fail

RTB disturbance Fail
Program memory CRC check failed Fail

Processor in safe operation mode Fail
Wrong time from RTC Ok

No signal (IRIG-B) on RTC Ok
G3LS HW configuration error Fail

IED configuration error Fail
Major ISS error Fail
LOS Loss of Signal Fail
FPGA not loaded Fail
Wrong slot for G3LS Fail
GOOSE Communication Failed Fail

Ethernet Link Down Fail
Table 9-11 G3LS alarms
9.3.11. List of low level alarms and corrective actions

Once the problem has been localized, corrective actions are required
to eliminate the source of the problem. The following table lists all low
level alarms with explanations and proposed corrective actions (in
italic).
The alarms with entry “HMI” in column “Alarm Code” at the end of the
following table are generated by the user interface program HMI570.
Low Level Alarm Alarm Explanation
Code Corrective Action
HW Version Common Interface and Bus 0.20 Change the bus plane or the common interface board
Plane do not match (whichever does have a non-compatible hardware version).
Refer to document 1KHW000902 “Compatibility Requirements
NSD570”
Overcurrent in MOSFET output 2 0.19 This error appears always in conjunction with at least one
“Error Relay Interface …” (Alarm Code 0.7 to 0.14) that
indicates the plug-in position of the affected relay board(s).
1. Disconnect the external cable from the affected relay


Overcurrent in MOSFET output 1 0.18 interface and check whether the alarm disappears.
2. If after step 1 the alarm does not disappear, check for short
circuits between the wires connected to output 1 or 2 of the
affected boards. Decrease the externally applied voltage or
increase the load impedance at output 1 or 2 of the affected
relay interface.
Single component failure input 2 0.17 A hardware error on input 1 or 2 of one or more of the relay
interfaces has been detected. This error appears always in
conjunction with at least one “Error Relay Interface …” (Alarm
Single component failure input 1 0.16 Code 0.7 to 0.14) that indicates the plug-in position of the
affected relay board(s).
Replace the affected relay interface(s).
Error Relay Interface 4 TPE 2 (N84) 0.14 Indicates the plug-in position of the relay interface(s)
Error Relay Interface 3 TPE 2 (N76) 0.13 generating at least one of the following low level alarms:
Error Relay Interface 2 TPE 2 (N70) 0.12 - Overcurrent in MOSFET output 2 (Alarm Code 0.19),
- Overcurrent in MOSFET output 1 (Alarm Code 0.18),
Error Relay Interface 1 TPE 2 (N64) 0.11
- Single component failure input 2 (Alarm Code 0.17),
- Single component failure input 1 (Alarm Code 0.16).
Follow the instructions given for these low level alarms.
Micro-controller FLASH verify error 0.5 Error during startup of the DSP / micro controller on the line
interface, indicating a hardware defect of the micro controller
or FLASH memory.
Replace the line interface
5 V supply voltage failure 0.4 Supply on Common Interface faulty or contact problems at the
connector.
Check connectors to bus plane, replace module rack.
Warning: Undervoltage redundant supply 2 0.3 Replace defective power supply module 2
Warning: Undervoltage redundant supply 1 0.2 Replace defective power supply module 1
Undervoltage alarm supply 2 0.1 Burden for supply module 2 too high (secondary short circuit),
supply monitoring on common interface defective, supply
module defective or no primary voltage.
Watch the Supply LEDs while troubleshooting:
pull out each individual module, otherwise replace power
supply unit 2, otherwise replace module rack.
Undervoltage alarm supply 1 0.0 Burden for supply module 1 too high (secondary short circuit),
supply monitoring on common interface defective, supply
module defective or no primary voltage.
Watch the Supply LEDs while troubleshooting:
pull out each individual module, otherwise replace power
supply unit 1, otherwise replace module rack.
Program memory internal CRC check failed 1.31 Indicating a hardware defect of the DSP / SDRAM on the line
interface.
If persistent: replace the line interface.


Program memory SDRAM CRC check failed 1.30 Indicating a hardware defect of the DSP / SDRAM on the line
interface.

Data memory lookup table CRC check failed 1.29 Indicating a hardware defect of the DSP / SDRAM on the line
interface.
Program memory internal CRC add. 1.28 Indicating a hardware defect of the DSP / SDRAM on the line
segment failed interface.
DSP in safe operation mode 1.27 Indicating a persistent program or data memory error in DSP /
SDRAM. The DSP is halted and command tripping is
suppressed.
Replace the line interface.
SDRAM data memory check failed 1.26 Indicating a hardware defect of the DSP / SDRAM on the line
interface.
Internal data memory check failed 1.25 Indicating a hardware defect of the DSP / SDRAM on the line
interface.
Program Memory micro-controller CRC 1.24 Indicating a hardware defect of the micro-controller FLASH
check failed memory on the line interface.
Remote test mode active 1.21 The remote test mode is still active.
Deactivate the remote test mode and conclude testing /
commissioning activities before leaving the equipment.
Local test mode active 1.20 The local test mode is still active.
Deactivate the local test mode and conclude testing /
commissioning activities before leaving the equipment.
Wrong time from RTC 1.18 If no external sync time (GPS Sync = IRIG-B) is available or
card never operated before or not powered up for several
days -> internal time not valid.
Set time
If external sync time (GPS Sync = IRIG-B)
Check timing source and connections
No signal (IRIG-B) on RTC 1.16 If the external sync time (GPS Sync = IRIG-B) is missing for
more than 140 sec (valid from NSD570 Rel. 3.7 onwards).
Check timing source and connections
More Relay Interfaces configured than 1.12 This error appears always in conjunction with at least one
plugged “Comm. error Relay Interface …” (Alarm Code 4.4 to 4.11)
that indicates the plug-in position of the affected relay
board(s).
Plug missing relay interfaces or replace defective ones. Refer
to same time appearing alarms “Comm. error Relay Interface
…” for finding faulty or missing boards.
Reset the equipment using HMI570.
Wrong slot for Line Interface 1.10 Use correct slot


Initialization alarm during startup 1.9 Error during startup of the line interface, indicating a hardware
defect of the DSP.
If persistent, replace the line interface.
Configuration error 1.7 Invalid configuration or board was not configured
Download valid configuration. If persistent, replace line
interface.
Under certain circumstances, this error occurs after a firmware
download.
Upload configuration from device and afterwards download
configuration to device without any changes.
Configuration version mismatch.
Error displayed after an attempt to download a configuration
generated with an HMI570 version not compatible with the
NSD570 firmware.
Link failure: command outputs set to a pre- 1.6 Check link
defined state
Loop test error 1.5 Check link, check settings, check hardware.
Unblocking pulse 1.4 Unblocking condition occurred (visible in event recorder only)
Remote alarm 1.3 Error in the remote device.
CRC failure EOC 1.2 Communication error in the EOC.
If persistent, check link.
Simultaneous trip and guard received 1.1 Check link.
No trip and no guard 1.0 Check link, check connections.
SNR Alarm 2.6 Check link.

Receive level alarm 2.5 Check link, check connections.
Transmit level alarm 2.4 Check connections for possible short circuits / overload,
disconnect cable; if still alarm, replace line interface
+/- 12 V supply voltage failure 2.0 Indicating a hardware defect of the internal 12 V supply on the
analog line interface
Replace the analog line interface if the error persists.
ALS Automatic Laser Shutdown is active 3.30 The laser is shut down because no optical input signal is
detected. This is done for eye safety reasons when the
interface is configured to ALS = on.
Re-establish the optical input signal and wait for a maximum
of 100 seconds or configure the interface to ALS = off.
SFP transceiver not plugged 3.29 Optical piggyback G1Loa is mounted but no SFP transceiver
module is assembled.
The SFP/Ethernet switch of G3LE is in position SFP but no
module is assembled
Plug the corresponding SFP transceiver module according to
the desired application.
Laser Failure 3.28 The laser does not run properly due to a hardware problem.
Replace the optical interface G1LO or the SFP transceiver
module on G1Loa or on G3LE.


Remote Equipment has different guard 3.27 The Guard Packet Sending Interval is different on local and
packets sending interval remote equipment.
Set the Guard Packet Sending Interval to the same value on
remote and local equipment.
Remote Equipment has different WAN 3.26 Incompatible protocol versions are used because one of the
protocol version NSD570 Ethernet G3LE is older than the other one.
NSD570 Ethernet with equal firmware versions are necessary
on both equipment. Alternatively a firmware update on at least
one equipment will solve the problem.
Remote equipment has wrong address 3.25 The local digital address in the configuration file of the local
equipment does not match with the remote digital address of
the remote equipment or vice versa.
Correct the digital address in the configuration file of the local
equipment or of the remote equipment, so that they match.
BER Bit Error Rate alarm 3.24 The communication channel is distorted.
Find the reason for the distortion in the channel or increase
the “BER Alarm Threshold” in the configuration file.
Duplicate IP address in subnet 3.23 IP address collision has been detected by G3LE.
Resolve the IP address conflict by changing the IP address on
the affected devices.
Packet Loss alarm 3.22 Too many Ethernet packets get lost on the transmission
channel
Check the transmission channel on defective elements,
changes of the routing path or congestion.
Maybe the Packet Loss Rate Alarm Threshold is just set lower
than required by the application. Check the Packet Loss Rate
Alarm Threshold setting.
Alarm Indication Signal G.703 3.21 The Alarm Indication Signal (all 1’s bit pattern) according to
G.703 is received, generated by some multiplexer on the
Check the communication channel and correct the problem.
Loss Of Signal G.703 3.20 There is a problem with the communication channel: The
received signal level is insufficient or the channel is
interrupted.
Check the wiring of the communication channel and check the
signal at the receiver input. Correct the communication
problem.
Transmission Time alarm 3.19 The transmission time of the Ethernet packets is higher than
required for the specific application. A reception of Ethernet
packets in the required time is highly jeopardized or
impossible.
Maybe the transmission time alarm threshold is just set more
sensitive than required by the application. Check the
Transmission Time Alarm Sensitivity and the Propagation
Time settings.


Transmission Time warning 3.18 The transmission time of the Ethernet packets has risen. A
reception of Ethernet packets in the required time is
jeopardized. Pre-stage of the Transmission Time alarm.
Maybe the transmission time warning threshold is just set
more sensitive than required by the application. Check the
Transmission Time Warning Sensitivity and the Propagation
Time settings.
Pattern synchronization error 3.17 There is a synchronization problem or the communication
channel is distorted.
Check the synchronization settings of the local and the remote
device. Find the reason for the distortion in the channel and
correct the problem.
Piggyback does not match configuration 3.14 The mounted piggyback does not support the configured
interface type.
Reconfigure the interface type to match the piggyback or
replace the piggyback to match the configured interface type.
Read error from E1/T1 framer 3.13 The E1/T1 framer cannot be read due to a hardware problem.
Replace the digital line interface G3LD, otherwise replace the
E1/T1 interface G1LE or the optical interface G1LO.
Write error to E1/T1 framer 3.12 The E1/T1 framer cannot be written due to a hardware
problem.
Replace the digital line interface G3LD, otherwise replace the
E1/T1 interface G1LE or the optical interface G1LO.
Default WAN password 3.11 No WAN password has been set for G3LE, the device is still
using the default password. There is no impairment of
functionality but this is a security issue.
Set another WAN password on the remote and local
equipment.
LOF Loss of Frame 3.9 No frame can be detected in the received optical signal.
Verify the device on the other side of the link is configured for
the same optical interface type as the local device (e.g.
Optical IEEE C37.94).
Piggyback missing 3.8 An interface requiring a piggyback module has been
configured, but the piggyback module is not plugged.
Reconfigure the device or plug the piggyback module.
LOS Loss Of Signal 3.7 There is a problem with the communication channel: The
received signal level is insufficient or the channel is
interrupted.
Check the wiring of the communication channel and check the
signal at the receiver input. Correct the communication
problem.
AIS Alarm Indication Signal 3.6 The Alarm Indication Signal (all 1’s bit pattern) is present in
the received E1/T1 or optical data, generated by some
multiplexer on the communication channel.
Check the communication channel and correct the problem.


LFA Loss of Frame Alignment 3.5 There is a synchronization problem or the communication
channel is distorted.
Check the synchronization settings of the local and the remote
device. Find the reason for the distortion in the channel and
correct the problem.
RRA Receive Remote Alarm 3.4 The remote equipment reports a communication error in the
E1/T1 or Optical interface.
Check the communication channel between the local
equipment output and the remote equipment input and correct
the problem.
FW version does not support piggyback 3.3 Update the firmware of the digital line interface to a version
that supports the piggyback. Refer to documents
1KHW000902 “Compatibility Requirements NSD570” and
1KHW000896 “Firmware Download Description NSD570”.
Initialization failure in FPGA 3.2 Some hardware in the digital line interface could not be
initialized.
Reset the equipment using HMI570. If the error persists,
replace the digital line interface.
CRC failure while loading FPGA 3.1 Some hardware in the digital line interface could not be
initialized.
Reset the equipment using HMI570. If the error persists,
replace the digital line interface.
FPGA not loaded 3.0 A hardware fault on the digital line interface or the Ethernet
line interface has been detected.
If the alarm persists after system restart, replace the line
interface.
G3LS Interface Alarm 4.31 The G3LS reports at least one of the G3LS alarm shown in
Table 9-11 (except for Wrong slot for G3LS).
Upload the alarms from the module G3LS using HMI570 and
execute the corresponding corrective actions.
Tx continuous command H 4.19 The continuous command monitoring for the corresponding
Tx continuous command G 4.18 command (A … H) is enabled and the maximum duration as
configured by HMI570 has been exceeded. This error appears
Tx continuous command F 4.17
always in conjunction with the “Continuous command alarm”
Tx continuous command E 4.16 (Alarm Code 4.0).
Tx continuous command D 4.15 Verify that the continuous command monitoring / maximum
Tx continuous command C 4.14 duration of the corresponding command (A … H) as
configured by HMI570 is correct or change the settings of the
Tx continuous command B 4.13
equipment generating the command so that it is not longer
Tx continuous command A 4.12
than allowed.


Comm. error Relay Interface 4 TPE 2 (N84) 4.11 Either the corresponding relay interface is not plugged, the
Comm. error Relay Interface 3 TPE 2 (N76) 4.10 relay interface is faulty or there is a problem with the
connector of the relay interface to the bus plane.
Comm. error Relay Interface 2 TPE 2 (N70) 4.9
Plug the relay interface or – if already plugged – check its
connector to the bus plane.
Power off the equipment for at least 5 seconds.
If the error persists, replace the relay interface. If this does not
Comm. error Relay Interface 2 TPE 1 (N40) 4.5 help, replace the module rack.
Continuous command alarm 4.0 The maximum command duration as configured by HMI570
has been exceeded for one or several of the configured
commands. This error appears always in conjunction with at
least one “Tx continuous command …” (Alarm Code 4.12 to
4.19).
Verify that the maximum command duration as configured by
HMI570 is correct or change the settings of the equipment
generating the commands so that they are not longer than
allowed.
FPGA not loaded G3LM A hardware fault on the management or the GOOSE LAN
G3LS interface has been detected.
If the alarm persists after system restart replace the
management interface.
Ethernet link down G3LM Ethernet link is down. No communication over LAN
G3LS possible.
Check if the Ethernet port is properly connected to the LAN.
Wrong time from RTC G3LM If no external sync time (GPS Sync = IRIG-B) is available or
G3LS card never operated before or not powered up for several
days -> internal time not valid.
Set time.
If external sync time (GPS Sync = IRIG-B):
Check timing source and connections.
No signal (IRIG-B) on RTC G3LM If the external sync time (GPS Sync = IRIG-B) is missing for
G3LS more than 140 sec (valid from NSD570 Rel. 3.7 onwards).
Check timing source and connections.
SFP/Ethernet switch error G3LM The SFP/Ethernet switch is in ambiguous position.
G3LS Check the SFP/Ethernet switch and set it to the required
position.
SFP transceiver not plugged G3LM The SFP/Ethernet switch is in position SFP but no module is
G3LS assembled.
Plug a SFP transceiver module.
SFP transceiver signal loss G3LM There is a problem with the communication channel: The
G3LS received signal level on the SFP module is insufficient or the
channel is interrupted.
Check the wiring of the communication channel and check
the signal at the receiver input. Correct the communication
problem.


SFP transceiver laser failure G3LM The laser on the SFP module does not work properly due to
G3LS a hardware problem.
Replace the SFP transceiver module.
User file not loaded (parse error) G3LM The user file is corrupt.
Set up the user accounts again and restart the system
(connection only over serial port possible). If the alarm
persists replace the management interface.
Duplicate IP address in subnet G3LM IP address collision has been detected.
Resolve the IP address conflict by changing the IP address
on the affected devices.
Default configuration loaded G3LM The default configuration has been loaded since no user
configuration has been downloaded yet or the current
configuration is corrupt.
Download a new configuration and reset the equipment.
Default users loaded G3LM Only the default user accounts are available for login.
For security reasons all default accounts should be deleted.
Use specific user accounts.
Default SSL keys loaded G3LM Default certificate has been generated and loaded.
For security reasons the default certificate should be
replaced by generating a new one.
User activity logfile full G3LM The user activity logfile is full. New user activity entries
overwrite the oldest ones.
Upload the user activity logfile and store it on your backup
drive. Delete the user activity logfile on G3LM to clear the
warning.
SNTP client out of sync G3LM The SNTP client is active but neither the primary nor the
secondary SNTP server is responding.
Check if the SNTP servers are operational and properly
connected to the LAN. Check if the configured IP addresses
are correct.
HW version insufficient for SNTP G3LM The SNTP client is configured on a G3LM (without index a).
Substitute the G3LM by a G3LMa or disable the SNTP
client.
ALS Automatic Laser Shutdown is active G3LM The laser on the SFP module is shut down because no
G3LS optical input signal is detected. This is done for eye safety
reasons when the interface is configured to ALS = on.
Re-establish the optical input signal and wait for a maximum
of 100 seconds or configure the interface to ALS = off.
Alarm polling cycle is too short G3LM The polling of all devices during the last cycle took longer
than the configured polling cycle time.
If the warning persists, check if devices are accessible (the
polling of devices which are not accessible takes much
more time).
If all devices are accessible increase the polling cycle time.
SNMP alarm table is full - too many alarms G3LM The SNMP alarm table is full. New alarms cannot be stored.
If the warning persists reduce the number of devices being
polled.


RTB CRC error G3LS The Real Time Bus on the NSD570 backplane is not correctly
driven by the line interface.
Replace the line interface.
RTB misalignment G3LS An error occurred on the Real Time Bus of the NSD570
backplane.
Verify all modules are plugged into the correct rack slot
position. Restart the whole NSD570 rack. If the alarm persists
replace the line interface.
RTB disturbance G3LS The Real Time Bus on the NSD570 backplane is not correctly
driven by the line interface or other modules interfere.
Verify all modules are plugged into the correct rack slot
position and the number of configured commands for G3LS
match the remaining number of commands for G3LR and the
number of G3LR modules within the rack. If the alarm persists
replace the line interface or possibly plugged G3LR modules
one by one.
Program memory CRC check failed G3LS Program memory CRC check failed during start-up or during
runtime.
If the error persists replace the G3LS module.
Processor in safe operation mode G3LS Indicating a persistent program memory error in the SDRAM.
The processor is halted and command tripping as well as
GOOSE transmission is suppressed.
Replace the G3LS module.
G3LS HW configuration error G3LS G3LS HW XML configuration has wrong CRC, length or
version.
Download a valid hardware configuration with HMI570.
IED configuration error G3LS ICZ File cannot be uncompressed or not be processed with
the IEC 61850 Stack.
Generate a valid ICZ file with HMI570 and download it to the
target.
Major ISS error G3LS Task supervision in the IEC 61850 Stack detected an error.
Restart G3LS. If the alarm persists generate a valid ICZ file
with HMI570 and download it to the target.
Wrong slot for G3LS G3LS G3LS must be plugged in slot 34 or 64.
Plug G3LS in either one of the two allowed rack slots
positions.
GOOSE Communication Failed G3LS Check network connection and IED configurations.


Error! Alarm upload failed HMI HMI570 could not upload the alarms from the device.
Check the communication channel to the NSD570 device.
Check the wiring and the connectors.
Error! Can not connect to device HMI Refer to Section 4.10.4.2 “Connect Device”
Error! Communication incorrectly initialized HMI Refer to Section 4.10.4.3 “Error messages and
troubleshooting”
Error! Configuration download failed HMI HMI570 could not download the configuration to the device.
Error! Configuration file is invalid HMI The selected file is not a valid configuration file.
Try to load a valid configuration file.
Error! Configuration is invalid HMI The configuration is not valid.
Correct the settings to remove the detected conflicts given in
the warning text.
Error! Configuration load failed HMI HMI570 could not load the selected configuration from disk.
Check permissions for reading from the specified directory of
the disk. Check the disk.
Error! Configuration save failed HMI HMI570 could not save the configuration to disk.
Check permissions for writing to the specified directory of the
disk. Check the disk.
Error! Configuration upload failed HMI HMI570 could not upload the configuration from the device.
Error! Could not save HMI570 Options HMI HMI570 could not save the changed RS-232 port parameter.
You will have the default settings the next time you start the
HMI570.
Check permissions for writing to the HMI570 directory of the
Error! Device communication failed HMI The communication between the HMI570 and the device
failed.
Error! Device communication is busy! Please HMI Refer to Section 4.10.4.3 “Error messages and
try it later again troubleshooting”
Error! Device communication timeout HMI Refer to Section 4.10.4.3 “Error messages and
troubleshooting”
Error! Device communication, device reports HMI A communication error or a compatibility problem has
wrong checksum probably occurred.
Error! Device communication, device reports HMI Retry the operation.
wrong end byte If the error persists, make sure that HMI570 and the line
Error! Device communication, device trans- HMI interface generating the alarm are compatible, using
mission restart document 1KHW000902 “Compatibility Requirements
NSD570”.
Error! Device could not execute this function HMI
Error! Device does not allow this function HMI
Error! Device reports unknown function HMI


Error! Disconnection failed HMI HMI570 could not disconnect from the device.
Error! DSP boot failure HMI On the DSP interface, the DSP could not boot correctly due to
a hardware problem.
Replace the DSP interface.
Error! Event recorder contains invalid data HMI The event recorder contains invalid data and cannot be
uploaded by the HMI570.
Try to upload a smaller number of events.
If that does not work, try to configure a lower baud rate of the
RS-232 connection from your PC to the connected NSD570
(refer to Section 4.10.8.6 “Device Communication”).
If that does also not work, you have to clear the event
recorder.
Error! Event recorder file is invalid HMI The selected file is not a valid event recorder file.
Try to load a valid event recorder file.
Error! Event recorder load failed HMI HMI570 could not load the selected event recorder from disk.
Check permissions for reading from the specified directory of
the disk. Check the disk.
Error! Event recorder save failed HMI HMI570 could not save the event recorder to disk.
Check permissions for writing to the specified directory of the
Error! Event recorder upload failed HMI HMI570 could not upload the event recorder from the device.
Error! File can not be saved or loaded HMI HMI570 cannot save or load a file.
Save error: Check permissions for reading from and writing to
the specified directory of the disk. Check the disk.
Error! Firmware download failed HMI HMI570 could not download the selected firmware to the
device.
Error! No configuration loaded HMI A configuration must be loaded.
Load a configuration from disk or upload a configuration from
device.
Error! No device connected HMI A device must be connected.
Connect to the device, if this fails:
Error! Send task failed HMI HMI570 could not send a task to the device.
Error! Status upload failed HMI HMI570 could not upload the Status from the device.
Error! The device is already connected by HMI Refer to Section 4.10.4.3 “Error messages and
another user/application troubleshooting”.


Error! This configuration version is not HMI The installed HMI570 version does not support the version of
supported the configuration running on the device.
Update the HMI570 to the newest version.
Error! Time and date upload failed HMI HMI570 could not upload the time and date from the device.
Error! Trip counter upload failed HMI HMI570 could not upload the trip counter from the device.
Error! Upload failed (wrong length) HMI HMI570 could not upload the configuration from the device.
Error! Wrong configuration checksum HMI Retry the operation.
Error! Wrong configuration length HMI If the error persists, make sure that HMI570 and the line
interface generating the alarm are compatible, using
document 1KHW000902 “Compatibility Requirements
NSD570”.
Error! You don't have the permission to HMI A user without modify permission is not allowed to execute
execute this function ! some functions, refer to Section 4.14 “HMI570 Settings”.
The default password is used. Please HMI Valid for HMI570 from version 1.49 onwards.
change it immediately. For security reasons, the Administrator password must be
changed immediately after the installation of the HMI570.
Invalid password HMI Password during user login is not correct.
Type in the correct password or ask a user with admin
permission to change it.
Password must be at least 4 characters long. HMI Valid for HMI570 up to version 1.21.
Use a password that is at least 4 characters long.
Password must be at least 6 characters long. HMI Valid for HMI570 from version 1.30 to 1.47.
Password must be at least 8 characters long. HMI Valid for HMI570 from version 1.48 onwards.
Password must consist of a combination of HMI Compose the password accordingly.
letters, numbers and at least one “special”
character (!”#$%&'()*+,-./:;<=>?@[]^_`|~).
You are not registered HMI The HMI570 does not know the user name.
Check that you typed the user name correct. If you are not
registered, ask a user with admin permission to add you as a
new user, refer to Section 4.14 “HMI570 Settings”.
Channel Exception No SSL Handshake HMI Communication over LAN not possible.
Exception Check cable connection to LAN.
Could not log in. Check the cable connection HMI Login failed or more than one HMI570 attempts to connect to
and IP address. Management LAN Interface G3LM.
Check cable connection to LAN and IP address.
Could not log in. Check the user name and HMI Login failed.
password.
Check the user name and password.
Certificate import failed. Wrong file format. HMI Use the correct certificate file format: X.509
Access rights (view, modify or admin) have HMI Specify one of the three available permissions: view, modify or
to be specified. admin.


Passwords do not match! HMI The confirmation of the password failed.
Enter the password correctly.
Device address already exists. HMI Check the device addresses in the SNMP alarm/event polling
device list.
Table 9-12 Low level alarms with explanation and corrective actions
9.3.12. Alarm event recorder

The event recorder is described in detail in Section 3.5.16 “Event
Recorder”.
All alarm events available in the system are recorded continuously in
the nonvolatile memory of G3LA, or G3LD or G3LE with date and time
stamps supplied by the internal real time clock (RTC) of the
equipment.
The following events are recorded:
• changes of the alarm status of the system,
• commands or loop tests sent/received,
• external manipulations to the equipment, e.g. when the internal
clock is set or a new configuration is downloaded.
The RTC has an autonomy of about 12 hours. If the power supply to
the equipment is switched off for more than 12 hours, the time-stamp
supplied by the RTC will no longer be correct. Note that the RTC can
be synchronized to an external clock source via two special inputs
available on the Supply Backplane G1LB (refer to Section 3.5.16.5
“RTC synchronization from an external clock” and Section 6.5.3.2
“Station bus and Real Time Clock synchronization”).
Up to 7500 alarm events are recorded. If this number is exceeded, the
oldest events are discarded.
9.3.13. Alarm polling
Note: This function is available only in association with the

LAN Interface G3LL, the Management LAN Interface
G3LM or when using HMI570 “PC” version 1.14 or
higher.
The alarm polling facility allows monitoring the alarm status of a

number of NSD570 terminals connected to the station bus. The alarm
status of the addressed terminals is polled in selectable intervals and
in case of any alarm, the alarm text is recorded to a log file and
displayed on the screen.

Once a list of NSD570 terminals to be polled has been configured, the

alarm polling can be switched on and off. With alarm polling enabled,
all devices in the list are polled at specified intervals (daily, hourly,
every xx minutes) and the alarms coming back – if any – are written to
the log file with date and time stamps.
If a device cannot be reached, a communication error will be recorded
for that device.
If a specific device in the network has to be connected via the HMI570,
the alarm polling function has to be switched off first.
All low level alarms are reported via alarm polling and can be viewed
on screen or in the log file.
A detailed description and the configuration of the HMI570 “LAN” and
“PC” version for setting up the Alarm Polling can be found in Section
4.11 “Alarm Polling”.
9.4. Warnings
Warnings are used to signal that an equipment is not in normal
operation state, but otherwise working properly.
A warning is given from the NSD570 system when one of the two
power supply modules in the redundant configuration fails (under-
voltage detector on Common Interface G3LC activated).
9.5. Some basic checks

It is advisable to do the following basic checks before energizing a
teleprotection link. This minimizes the chance of a fault in the first
place and also reduces the time for troubleshooting in case there is
any.
• Check of the communication line (as described in Section 7.2
“Testing the communication channel”), especially if the NSD570
Analog is used in the frequency band of a PLC link.
• Ensure that the wires are properly connected to the equipment.
Check that Tx and Rx lines are cross-connected to the
communication devices or to the remote equipment in a point-to-
point configuration.
• Check whether the supply voltage to be applied to the equipment is
correct.
• Ensure that all the modules are properly inserted in their intended
slots.
• Check that the external connections are correct as per plant
drawings.

9.6. Frequently asked questions
9.6.1. General
Question:
The “Connect” operation is not successful. What can I do to correct
this problem?
Answer:
Check all hardware and its settings forming the communication path,
starting at the PC/notebook and ending at the equipment. The section
“Communication between the HMI570 and the NSD570” in Section 4.5
“Communication between the HMI570 PC and the NSD570” gives the
relevant information. If the communication path is made up of several
sections as in case of connection via modem, intranet/internet,
dedicated data channel and/or via EOC, proceed in steps, checking
the path sections in sequence starting at the side of the PC/notebook.
Note that only one HMI570 at a time is able to connect to a
Management LAN Interface G3LM via LAN. If a second HMI570
attempts to connect, HMI570 displays:
Communication error
Error ! Cannot establish communication
Error ! Cannot connect to device
Could not log in. Check the cable connection and IP
address.
Question:
The “Connect” operation is still not successful. What else can I do to
correct this problem?
Answer:
Maybe the device address used is incorrect. Try the default device
addresses: use 241 for the line interface plugged in TPE 1 respectively
246 for TPE 2, use 242 for the GOOSE interface plugged in TPE 1
respectively 247 for TPE 2, or use 250 for the Management interface
plugged in the rack. Note that the station bus of the rack must be
disconnected. This is because all devices plugged in TPE 1
respectively TPE 2 share the same default addresses. If the “Connect
Device” was successful, the programmed device address is shown
and automatically used for the next interactions (e.g. Configuration
Upload From Device).
Question:
The “Connect” operation is again not successful. What else can I do to

Answer:
For some reasons (e.g. a boot failure of the device indicated by the red
Fail LED and all others off) it is only possible to connect the line
interfaces with address 255. It is required to disconnect the station bus
and plug off one line interface in the rack first, before connecting with
255 to the other line interface. After successfully connecting the device
with address 255, a firmware download has to be executed, see
Section 4.10.8.8 “Firmware Download”. If the problem still exists,
replace the corresponding line interface module.
Question:
The “Connect” operation is again not successful. What else can I do to
Answer:
Use the “Reset Communication” button under HMI570 Settings.
Question:
The teleprotection link does not work. What can I do to correct this
problem?
Answer:
Check the alarms: If there is a hardware alarm at either side of the link,
the reason of it must be found and the problem corrected. Upload the
equipment status/alarm and study the alarm messages given by the
HMI570. One single problem can produce a number of such
messages.
If for both equipment of the link no hardware alarms are reported
(anymore), the problem has to be sought in the link. Upload the
equipment status/alarm and study the alarm messages given by the
HMI570. It may be possible to restrict the problem to one of the
following 3 cases:
1. excessive signal attenuation (voltage level at the analog or digital
receiver too low)
2. excessive line noise, bit errors or packet losses
3. excessive distortion or jitter
Find and correct the source(s) of the problems by measuring at
different points along the communication line with data testers (for
NSD570 Digital), with LAN/network test equipment (for NSD570
Ethernet) or level generators/selective level meters (for NSD570
Analog).
Question:
What shall I do if some alarms are present, signaled by alarm relay
contacts and/or alarm LEDs?
Answer:
Upload status/alarm data to see the details about the causes of the

alarms. If both hardware and link alarms are present, first remove the
cause of the hardware alarm. After this has been done, upload system
status once again and – if a link alarm should still be present – find the
cause of the link alarm. Check whether the alarm threshold levels are
appropriate.
Question:
Why do the AF levels and the SNR level displayed by the status of the
HMI570 fluctuate?
Answer:
The level will vary approx. 2.5 dB because the guard signal is
modulated to transmit data via the EOC. The SNR value displayed by
the HMI570 will vary as well, depending on the packets transmitted via
the EOC. The Signal to Noise Ratio (SNR) and the Tx/Rx level
measurement do only have an adequate accuracy if the EOC is
switched off!
Question:
How can I calculate the guard and trip frequencies of the NSD570
Analog for the various operating modes and channel center
frequencies?
Answer:
See Section 3.5.4. “Analog operating modes”.
Question:
How are the outputs on the Relay Interface G3LR operated, if they are
configured as alarm outputs? And what about the LEDs of the outputs
on the front plate?
Answer:
The relay contacts on G3LR are operated in the same way than the
alarm relays on the Common Interface G3LC, i.e. the “alarm” condition
is the same as the “power off” state of the equipment (relay coil not
energized). On both modules the user can still choose – by using the
corresponding output contacts - whether the alarm contact shall be
“normally open” or “normally closed”.
The solid-state outputs are operated differently. An alarm condition is
signaled with a conducting (energized) FET. Therefore the “alarm”
condition is not the same as the “power off” state of the equipment.
Both type of output contacts are activated only after the programmed
alarm delay time has elapsed. The same applies for the alarm hold
time.
The LEDs of the outputs on G3LR correspond with the state of the
contacts, i.e. they also light up only if the alarm delay time has elapsed
and they will light on for the duration of the alarm hold time.

Question:
My new notebook PC does not provide an RS-232 interface with a 9-
pole D-sub connector, but an USB interface instead. What can I do?
Answer:
You have to use an external RS-232 to USB converter. It is
recommended to use the following converter, which was tested and
works fine with HMI570 and other user interface programs provided by
Hitachi ABB (see also Section 11.1):
V9OP*USB-TO-SERIAL CONVERTER
9.6.2. Where can I get the latest version of this FAQ?

Send e-mail to:
communication.networks@hitachi-powergrids.com
9.7. Replacing faulty modules

Modules may only be replaced by properly trained personnel
authorized to do so. Strictly observe the safety instructions at the
beginning of this section.
Except for the power supply module G3HL, G3LI and G3LK, modules
may not be withdrawn or inserted while the equipment is in operation.
Switch off the power supply and disconnect external cables first.
As stated earlier, replacement of faulty items can be done only at
module level and not component level since surface mount technology
is used for components of most of the modules. While replacing a
faulty module with a new module, ensure that the fault is not due to
some incorrect external wiring or mode of operation. Else even the
new module will go faulty. Remember to program correct jumper
settings (if any) on the new module before replacement.
9.8. Returning modules for repair

A module identified and confirmed to be faulty should be sent for
repairs to Hitachi ABB. It should be packed preferably in the original
packing or in anti-static bags with additional mechanical protection to
avoid damage during transport. It should be accompanied by a short
description of the observed fault.
Hitachi ABB is not responsible for a module received which was
damaged during transport. The financial implications of the repairs
depend upon the agreement with the client.
Refer to document “1KHM010296 - Repair and Return Procedure” in
Section 12 “Appendix”.

9.9. Support
Refer to document “1KHW029009 - Customer Connect Portal User
Instruction” in Section 12 “Appendix”.

10. Storage, decommissioning and disposal



DANGER

ESD protection



Storage, decommissioning and disposal August 2021 10-1


10.2. Storage
The equipment must be stored at a temperature between -40 °C and
+70 °C and a relative humidity < 95 %, non-condensing.
The cabinet should be stored in its original wooden frame and plastic
cover. Make sure that the plastic cover is undamaged. Where the
equipment has to be stored for a long period, precautions to prevent
corrosion must be taken. This is especially important in humid
climates.
Modules should be stored preferably in their original packing with an
outer packing to protect against mechanical damage.
10.3. Decommissioning
The procedure for decommissioning the equipment is as follows:
• First of all, the application in which the equipment is used, must be
disabled. This is of special importance when protection signaling is
concerned.
• Switch off the circuit breaker controlling the power supply to the
equipment (OFF). Disconnect the power supply cable from the
equipment. Repeat for redundant power supply, if applicable.
• Open the isolating terminals from the external cables.
• Disconnect the external wiring according to the respective wiring
lists and diagrams to avoid any risk of disconnecting other
equipment by mistake.
• If the complete cabinet has to be removed, support it in a way that
it cannot fall over when its anchoring is undone and remove the
bolts holding the base frame. The cabinet can then be lifted out
and dismantled. Should no suitable support for the cabinet be
available, it should be laid down horizontally.
• If the NSD570 rack has to be removed from the cabinet,
disconnect the internal wiring between the NSD570 rack and the
terminal blocks in the cabinet. Then remove the screws holding
the rack at the front and withdraw the rack.
• If it is intended to use an NSD570 rack somewhere else, carefully
pack it while observing the ESD rules.
10-2 August 2021 Storage, decommissioning and disposal

10.4. Disposal
When disposing of the equipment, do so in strict accordance with
regional and national regulations for the disposal of electrical and
electronic components.
The modular construction of the equipment enables the printed circuit
boards and housings to be easily separated for recycling.
LAN Interface G3LL

Storage, decommissioning and disposal August 2021 10-3

11. Appendices
11.1. Order numbers

Type Description Order number
Basic Equipment 8
NSD570 Standard Equipment 1 x analog, 24-48 VDC 1KHW001179R1011
Consists of 1 x G7BI, 1 x G3LI, 1 x G3LA, 1 x G3LR
NSD570 Standard Equipment 1 x analog, 110-250 V 1KHW001179R1021
Consists of 1 x G7BI, 1 x G3LK, 1 x G3LA, 1 x G3LR
NSD570 Standard Equipment 2 x analog, 24-48 VDC 1KHW001179R1012
Consists of 1 x G7BI, 1 x G3LI, 2 x G3LA, 2 x G3LR
NSD570 Standard Equipment 2 x analog, 110-250 V 1KHW001179R1022
Consists of 1 x G7BI, 1 x G3LK, 2 x G3LA, 2 x G3LR
NSD570 Standard Equipment 1 x digital, 24-48 VDC 1KHW001179R2011
Consists of 1 x G7BI, 1 x G3LI, 1 x G3LD, 1 x G3LR
NSD570 Standard Equipment 1 x digital, 110-250 V 1KHW001179R2021
Consists of 1 x G7BI, 1 x G3LK, 1 x G3LD, 1 x G3LR
NSD570 Standard Equipment 2 x digital, 24-48 VDC 1KHW001179R2012
Consists of 1 x G7BI, 1 x G3LI, 2 x G3LD, 2 x G3LR
NSD570 Standard Equipment 2 x digital, 110-250 V 1KHW001179R2022
Consists of 1 x G7BI, 1 x G3LK, 2 x G3LD, 2 x G3LR
NSD570 Standard Equipment 1 x Ethernet, 24-48 VDC 1KHW001179R4011
Consists of 1 x G7BI, 1 x G3LI, 1 x G3LE, 1 x G3LR
NSD570 Standard Equipment 1 x Ethernet, 110-250 V 1KHW001179R4021
Consists of 1 x G7BI, 1 x G3LK, 1 x G3LE, 1 x G3LR
NSD570 Standard Equipment 2 x Ethernet, 24-48 VDC 1KHW001179R4012
Consists of 1 x G7BI, 1 x G3LI, 2 x G3LE, 2 x G3LR
NSD570 Standard Equipment 2 x Ethernet, 110-250 V 1KHW001179R4022
Consists of 1 x G7BI, 1 x G3LK, 2 x G3LE, 2 x G3LR
Module Rack
G7BI G7BI*MODULE RACK NSD570 1KHW000911R0001
Power Supply
G3LH 9 G3LH*POWER SUPPLY NSD570 1KHW000909R0001
G3LI G3LI*POWER SUPPLY 24-48 VDC NSD570 1KHW002145R0001
G3LK G3LK*POWER SUPPLY 110-250 VDC/VAC NSD570 1KHW002144R0001

Appendices August 2021 11-1

Interface Cards
G3LA G3LA*ANALOG INTERFACE NSD570 1KHW000884R0101
G3LD G3LD*DIGITAL INTERFACE NSD570 1KHW000886R0102
G1LE G1LE*E1/T1 INTERFACE NSD570 1KHW000888R0002
G1LO 10 G1LO*OPTICAL INTERFACE OTERM/P2P 1KHW000965R0001

NSD570
G1LOa G1LOa*OPTICAL INTERFACE NSD570 1KHW001869R0001
G3LE G3LE*ETHERNET INTERFACE NSD570 1KHW001924R0002
G3LR 11 G3LR*RELAY INTERFACE NSD570 1KHW000880R0101
G3LRa G3LRa*RELAY INTERFACE NSD570 1KHW000628R0102
G1LR G1LR*INPUT TRIPPING VOLTAGE NSD570 1KHW000882R0001
G3LS G3LS*GOOSE LAN INTERFACE NSD570 1KHW002630R0002
Electrical Connecting Cables
G3LA*CABLE FOR ANALOG INTERFACE New 1KHW027436R0025
Old 1KHW000664R0001
G1LB*CABLE FOR STATION BUS/RTC SYNC New 1KHW027433R0025
Old 1KHW000668R0001
G3LC*CABLE FOR ALARM RELAYS New 1KHW027439R0025
Old 1KHW000658R0001
G3LD*CABLE WITH X.21 INTERFACE (15-P) New 1KHW027444R0025
Old 1KHW000670R0001
G3LD*CABLE WITH RS-530 INTERFACE (25-P) New 1KHW027443R0025
Old 1KHW000669R0001
G3LD*CABLE WITH RS-449 INTERFACE (37-P) New 1KHW027445R0025
Old 1KHW000671R0001
G3LD*CABLE WITH ISOLATING TERMINALS New 1KHW027442R0025
Old 1KHW000662R0001
G3LR*CABLE FOR RELAY INTERFACE New 1KHW027449R0025
Old 1KHW000659R0001

11-2 August 2021 Appendices

Optical Connecting Cables
V9WP*FO-CB SM 2F INT. FC/PC-E2000/APC New 1KHW027516R0020 12
Old 1KHW000580R0002 13
V9WQ*FO-CB SM 2F INT.E2000/APC-E2000/APC New 1KHW027517R0020 12
Old 1KHW000581R0002 13
V9WR*FO-CB SM 2F EXT. FC/PC-E2000/APC New 1KHW027518R0100 12
Old 1KHW000582R0010 13
V9WS*FO-CB SM 2F EXT.E2000/APC-E2000/APC New 1KHW027519R0100 12
Old 1KHW000583R0010 13
V9YE*FO-CB MM 2F EXT. LC/PC-ST/PC New 1KHW027541R0100 12
Old 1KHW001862R0010 13
V9YF*FO-CB MM 2F EXT. LC/PC-LC/PC New 1KHW027542R0100 12
Old 1KHW001873R0010 13
V9YG*FO-CB MM 2F INT. LC/PC-LC/PC New 1KHW027543R0040 12
Old 1KHW001874R0004 13
V9KU*FO-CB SM 2F INT. LC/PC-LC/PC New 1KHW027494R0020 12
Old 1KHW001321R0002 13
V9KV*FO-CB SM 2F INT. LC/PC-E2000/APC New 1KHW027495R0040 12
Old 1KHW001322R0004 13
V9KW*FO-CB SM 2F INT. FC/PC-LC/PC New 1KHW027496R0020 12
Old 1KHW001323R0002 13
V9KX*FO-CB SM 2F EXT. LC/PC-LC/PC New 1KHW027497R0100 12
Old 1KHW001324R0010 13
V9KZ*FO-CB SM 2F EXT. FC/PC-LC/PC New 1KHW027499R0100 12
Old 1KHW001326R0010 13
12 Other length available on request:

order number above plus R0xxx where xxx = length in decimeter.
13 Other length available on request:
order number above plus R00xx where xx = length in meters.

Optical SFP transceiver modules
SFP*FE/2MBPS 850NM MM 13DB 0.5KM/1KM 1KHW001871R0005
SFP*FE 1310NM MM 11DB 0.5KM/1KM (only for G3LE/M/S) 1KHW028291P0001
SFP*S1.1/FE/2MBPS 1310NM SM 19DB 30KM 1KHW001872R0001
SFP*L1.1/FE/2MBPS 1310NM SM 29DB 60KM 1KHW001998R0001
SFP*X1.2/FE/2MBPS 1550NM SM 35DB 120KM 1KHW001661R0001
SFP*STM1/FE/2MBPS CWDM 1550NM 50DB 180KM 1KHW002211R0001
Optical attenuator
OPT.ATT.*10DB LC/PC 850NM MM 1KHW001878R0010
OPT.ATT.*10DB LC/PC 1310/1550NM SM 1KHW001997R0010
Display Panel
G1LC G1LC*DISPLAY PANEL NSD570 1KHW001018R0001
G3LM 14 G3LM*MANAGEMENT LAN INTERFACE NSD570 1KHW001923R0001
G3LMa G3LMa*MANAGEMENT LAN INTERFACE NSD570 1KHW001923R0002
G3LMa*CABLE STATION BUS/SYNC 1KHW028384R0025
LAN Interface
G3LL 15 G3LL*LAN INTERFACE NSD570 1KHW001016R0001
G3LL*CABLE FOR STATION BUS/RTC SYNC New 1KHW027447R0025
Old 1KHW001213R0001
Patch panels and cables for RJ45 connectors on G3LD, G1LE, G3LE, G3LS,
G3LL and G3LM
V9OZ PATCHPANEL 1x RJ45 WITH LSA CONNEC. 1KHW001755R0002
V9OH V9OH*PATCHCORD RJ45 1:1 S-FTP New 1KHW027503R0030
Old 1KHW001756R0003


Software and Documentation
NSD570*SOFTWARE & DOCUMENTATION CD 1KHW000925R0100
BRO Brochure NSD570 1KHA000746-SEN
BAL Operating Instructions NSD570 1KHW000890
DS Technical Data NSD570 1KHW000892
Software Installation Description HMI570 1KHW000894
Firmware Download Description NSD570 1KHW000896
PTI Programming and Testing Instructions NSD570 1KHW000898
CI Commissioning Instructions NSD570 1KHW000900
Compatibility Requirements NSD570 1KHW000902
Anomaly List NSD570 1KHW000904
Commissioning Instructions LAN Interface G3LL 1KHW001289
Commissioning Instructions Management LAN 1KHW002232

Interface G3LM
Copy Instructions Compact Flash Card G3LL 1KHW001291
Engineering of GOOSE LAN Interface G3LS 1KHW002649
Repair and Return Procedure 1KHM010296
Support Document 1KHM010297
Safety Instructions Leaflet 1KHW002933
Declaration of Conformity (CE marking) 1KHM007042
DGL Cyber Security Product Deployment Guideline 1KHW002600
NERC-CIP Statement 1KHW028472
G3LS IEC 61850 MICS - 1KHW002634

Model Implementation Conformance Statement
G3LS IEC 61850 PICS - 1KHW002635

Protocol Implementation Conformance Statement
G3LS IEC 61850 TICS - 1KHW002636

Tissues Implementation Conformance Statement
G3LS IEC 61850 PIXIT - Protocol Implementation eXtra 1KHW002637

Information for Testing
G3LS IEC 61850 SICS - 1KHW002638

SCL Implementation Conformance Statement
G3LS IEC 61850 Conformance Certificate Level B 1KHL050091
Table 11-1 Order numbers

Optional items
For G7BI NSD570*STANDARD ACCESSORIES 1KHW001039R0001

(one set is delivered with each module rack)
For G7BI Cover Plate with marking strip (1U, RAL 7035) 1KHW002234R0011
(one plate is delivered with each module rack)
For G7BI ESD EARTHING SET 4.5MM 1KHW000330R0001

(conductive bonded wrist strap for connection to
the ESD bonding point EBP at the rear of the rack)
For Special screwdriver from PHOENIX CONTACT SZS 0,6 x 3,5

modules (for releasing the tension spring of the connectors) Order No. 12 05 05 3
For cables Special screwdriver from PHOENIX CONTACT SZF 1 - 0,6 x 3,5
(for releasing the tension spring of the terminals) Order No. 12 04 51 7
For cables KRONE*ACCESSORIES SET 1KHW001566R0004
For cables LSA PLUS*INSERTION TOOL HENF469509P0001
For PC D-SUB*CABEL STRAIGHT 9P M/F New 1KHW027463R0030
Old 1KHL015456P0001
For PC V9OP*USB-TO-SERIAL CONVERTER 1KHW001529R0002
Transport NSD570*TRANSPORT PACKAGE SET 1KHW001187R0001
Table 11-2 Order numbers accessories

11.2. Photographs
11.2.1. Front view of NSD570

The front view of NSD570 (see below) shows a fully equipped rack
with two redundant power supply modules (not in sight) and two
teleprotection equipment devices each with four relay interfaces.
Fig. 11-1 Front view of NSD570
11.2.2. Rear view of NSD570

The rear view of NSD570 (see below) shows the same equipment as
mentioned above with optionally available cables.
Fig. 11-2 Rear view of NSD570

11.3. Dimension Drawing Module Rack G7BI

All dimensions are in [mm].
Fig. 11-3 Front view
Fig. 11-4 Top view

Fig. 11-5 Side view

12. Annex
Technical Data NSD570 1KHW000892
Software Installation Description HMI570 1KHW000894
Firmware Download Description NSD570 1KHW000896
Programming and
Testing Instructions NSD570 1KHW000898
Test Report NSD570 1KHD608525
Commissioning Instructions NSD570 1KHW000900
Commissioning Report NSD570 1KHD608528
Compatibility Requirements NSD570 1KHW000902
Anomaly List NSD570 1KHW000904
Commissioning Instructions LAN Interface G3LL 1KHW001289
Copy Instructions Compact Flash Card G3LL 1KHW001291
Commissioning Instructions LAN Interface G3LM 1KHW002232
Engineering of GOOSE LAN Interface G3LS 1KHW002649
Repair and Return Procedure

(with Fault Report Form) 1KHM010296
Support Document 1KHM010297
Notification Form for Errors in this Document
Annex July 2020 12-1

ABB Power Grids Switzerland Ltd
TECHNICAL DATA NSD570

Document ID: 1KHW000892-EN Revision: Q Date: 2021-08-04
The teleprotection equipment NSD570 complies with EMC Directive 2014/30/EU and the Low-Voltage Directive
2014/35/EU.
NSD570 complies with or exceeds the requirements according to IEC publication 60834-1 "Teleprotection
Equipment of Power Systems - Performance and Testing – Part 1: Command Systems”.
Contents:
1. System Overview........................................................................................................................................... 3
2. Analog System Data ...................................................................................................................................... 3
3. Digital System Data ....................................................................................................................................... 5
4. Ethernet System Data ................................................................................................................................... 6
5. Common System Data .................................................................................................................................. 7
6. Special Operating Modes .............................................................................................................................. 8
7. Analog Line Interface (G3LA) ........................................................................................................................ 9
8. Digital Line Interfaces (G3LD) ..................................................................................................................... 10

8.1. G.703 Codirectional Interface ........................................................................................................... 10
8.2. RS-422 Interface ............................................................................................................................... 11
8.3. E1/T1 Interface (G1LE) ..................................................................................................................... 12
8.4. Optical Interface (G1LO) ................................................................................................................... 14
8.5. Optical Interface (G1LOa) ................................................................................................................. 15
9. Ethernet Line Interfaces (G3LE).................................................................................................................. 16
10. Relay Interface (G3LR) ............................................................................................................................... 17
11. GOOSE LAN Interface (G3LS).................................................................................................................... 19
12. Power Supply .............................................................................................................................................. 20

12.1. G3LH ................................................................................................................................................. 20
12.2. G3LI................................................................................................................................................... 20
12.3. G3LK ................................................................................................................................................. 21
12.4. Power Consumption .......................................................................................................................... 21
13. Common Interface (G3LC) .......................................................................................................................... 22
14. Bus Plane With Front Cover (G1LA) ........................................................................................................... 23
15. Supply Backplane (G1LB) ........................................................................................................................... 23
16. Internal Tripping Voltage (G1LR) ................................................................................................................ 23
17. LCD Display Panel (G1LC) ......................................................................................................................... 23
18. LAN Interface (G3LL) .................................................................................................................................. 24
19. Management LAN Interface (G3LM) ........................................................................................................... 24
Copyright 2002-2021 Hitachi Power Grids. All rights reserved. 1 / 33

Technical Data NSD570 1KHW000892-EN / Rev. Q ABB Power Grids Switzerland Ltd
20. HMI570 User Interface ................................................................................................................................ 26

20.1. HMI570 „PC“ ..................................................................................................................................... 26
20.2. HMI570 „LAN“ ................................................................................................................................... 27
21. Alarms.......................................................................................................................................................... 28
22. Event Recorder and Counters ..................................................................................................................... 29
23. Electromagnetic Compatibility (EMC).......................................................................................................... 30

23.1. Electrical Safety................................................................................................................................. 30
23.2. Emission ............................................................................................................................................ 30
23.3. Immunity ............................................................................................................................................ 30
23.4. Insulation ........................................................................................................................................... 31
24. Mechanical Data, Dimensions and Weights ................................................................................................ 31
25. Ambient Conditions ..................................................................................................................................... 33

25.1. Operation ........................................................................................................................................... 33
25.2. Transport ........................................................................................................................................... 33
25.3. Storage .............................................................................................................................................. 33

1. SYSTEM OVERVIEW
Application Transmission of protection commands for:

Line protection
- permissive tripping
- direct tripping
- blocking
Transformer protection (direct tripping)
Breaker failure protection (direct tripping)
Reactor and generator protection (direct tripping)
Operating mode Full duplex, bi-directional

- Point-to-point
- Point-to-point with redundant 1+1 path protection
- Point-to-multipoint for the protection of lines with T-offs
Communication medium analog and digital channels, fiber optic channels, Ethernet/IP channels
- pilot wires
- leased lines
- voice frequency channels of analog or digital communication systems
- PLC links
- data channels of digital multiplexers
- E1 or T1 circuits (SDH or SONET multiplexers)
- microwave radio links
- IP based telecommunication networks
Number of NSD570 in one rack 1 or 2
Mix of Analog, Digital and Ethernet systems in the same rack in any combination
Mechanical design 19 inch rack, 4 height units (4U) including 1U for cable tray
2 slots for single or redundant power supply
2 x 5 slots for one line interface and up to 4 relay interfaces
Optional LCD front display panel
Optional Ethernet/LAN/WEB interface for remote management
2. ANALOG SYSTEM DATA
Number of commands 1, 2, 3 or 4 independent, simultaneous, in any combination

commands individually configurable blocking, permissive or direct tripping
free command allocation to one or more output contacts
Bandwidth programmable 120, 240, 360, 480, 960, 1200, 2400, 2800 Hz
Channel center frequencies programmable from 360 Hz to 3900 Hz in steps of 60 Hz
Frequency stability  ±1 Hz
Line interface analog, type G3LA 4-wire or 2-wire circuit, full duplex operation
impedance 600 Ohm or high impedance
Command power boosting
Boost criterion free contact closes simultaneously with command transmission
Power boosting ratio selectable via HMI570 0 to 9 dB in steps of 1 dB
Operating modes 1 or 2 single-tone command(s) Command signal: single tone
Guard signal: single tone
Test signal: single tone
1 to 4 dual tone commands Command signal: 2 simultaneous tones
Guard signal: single tone
Test signal: 2 simultaneous tones
Admissible gain distortion for dual tone commands 3 dB (between the two tones)
Embedded Operation Channel (EOC)

- Configuration and monitoring of the opposite station from the local terminal
- Needs no additional bandwidth
- Operates in the guard channel
- Disabled during command transmission
- End-to-end operation for configurations with T-offs (“normal” T-operation)
Transmission rate NSD570 channel bandwidth data rate
120 / 240 / 360 Hz 20 bps
480 *) / 960 Hz 50 bps
1200 / 2400 / 2800 Hz 100 bps
*) 4 dual-tone commands in 480 Hz 20 bps
Required SNR > 6 dB

Nominal transmission time T0 including operating times of the relay interface G3LR (solid state outputs), EOC configured to ON,
command application set to direct tripping (except for 1 single-tone command).
Notes:
- Figures are given for back-to-back operation (according to IEC 60834-1).
- Transmission times are about 10% lower with Embedded Operation Channel (EOC) disabled.
1 single-tone
Channel 1 or 2 single-tone 1 or 2 dual-tone 1 to 3 dual-tone 1 to 4 dual-tone
command
Bandwidth commands commands commands commands
(blocking only)
120 Hz 50 ms N.A. N.A. N.A. N.A.
240 Hz 27 ms 38 ms 43 ms N.A. N.A.
360 Hz 19 ms 26 ms 30 ms 31 ms N.A.
480 Hz 15 ms 20 ms 23 ms 24 ms 28 ms
960 Hz 8.5 ms 11 ms 13 ms 14 ms 15 ms
1200 Hz 7.0 ms 9.5 ms 11 ms 11 ms 12 ms
2400 Hz 4.5 ms 6.0 ms 7.0 ms 7.0 ms 7.0 ms
2800 Hz 4.5 ms 5.5 ms 6.0 ms 6.0 ms 6.5 ms
Security Puc measured according to IEC 60834-1 with 200 ms noise bursts / 200 ms pause
Puc for worst case SNR Single-tone commands Dual-tone commands
- blocking Puc < 1E-03 Puc < 1E-04
- permissive Puc < 1E-05 Puc < 1E-06
- direct Puc < 1E-08 Puc < 1E-09
Dependability Pmc measured according to IEC 60834-1 noise bandwidth 4 kHz

Notes:
- Command application: B = Blocking; P = Permissive tripping; D = Direct tripping.
- Figures are given with Embedded Operation Channel (EOC) configured to ON.
- Due to the available test equipment for dependability measurements, fractional numbers for T0 in
the table above had to be increased by 0.5 ms to the next higher integer number.
- Due to white noise level measuring tolerance, the SNR values below may deviate by 1 dB.
- Performance guidance figures as per IEC 60834-1 (Fig. 21) are met for bandwidth > 960 Hz.
Required SNR (dB) for Pmc < 1% in 1.3 T0

Channel 1 single-tone 1 or 2 single-tone 1 or 2 dual-tone 1 to 3 dual-tone 1 to 4 dual-tone
Bandwidth command commands commands commands commands
B B P D B P D B P D B P D
120 Hz +10 N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A.
240 Hz +8 -1 +3 +9 +1 +5 +11 N.A. N.A. N.A. N.A. N.A. N.A.
360 Hz +8 +1 +5 +10 +3 +6 +12 +2 +6 +11 N.A. N.A. N.A.
480 Hz +4 +2 +6 +12 +4 +8 +15 +4 +7 +13 -1 +2 +5
960 Hz +5 +5 +9 +16 +6 +9 +14 +5 +8 +13 +3 +5 +8
1200 Hz +16 +4 +8 +16 +6 +10 +14 +6 +8 +13 +6 +8 +11
2400 Hz +7 +7 +10 +15 +8 +11 +16 +8 +11 +16 +8 +10 +14
2800 Hz +8 +5 +7 +9 +9 +12 +16 +10 +12 +16 +7 +10 +14

120 Hz -5 N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A.
240 Hz -1 -4 0 +8 0 +4 +10 N.A. N.A. N.A. N.A. N.A. N.A.
360 Hz +1 -1 +3 +9 0 +5 +11 0 4 +10 N.A. N.A. N.A.
480 Hz +1 -1 +4 +11 +1 +6 +12 +1 +6 +12 -1 +1 +5
960 Hz +4 0 +3 +8 +4 +8 +13 +2 +6 +12 +2 +4 +8
1200 Hz +5 0 +2 +5 +4 +8 +13 +5 +8 +12 +5 +7 +10
2400 Hz +7 +3 +5 +11 +3 +4 +6 +4 +5 +7 +7 +9 +13
2800 Hz +8 +4 +6 +8 +5 +7 +13 +5 +9 +14 +3 +5 +6

120 Hz -6 N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A.
240 Hz -2 -8 -6 -2 -7 -5 -2 N.A. N.A. N.A. N.A. N.A. N.A.
360 Hz 0 -6 -3 0 -5 -4 -1 -5 -3 -1 N.A. N.A. N.A.
480 Hz 0 -5 -1 +1 -4 -1 0 -4 -2 0 -5 -4 -3
960 Hz +3 -3 +1 +4 -1 0 +2 -1 0 +2 -2 -1 0
1200 Hz +4 -1 +2 +4 -1 +1 +4 0 +1 +3 0 +2 +3
2400 Hz +6 +1 +3 +6 +2 +3 +6 +3 +4 +6 +2 +3 +5
2800 Hz +7 +3 +5 +8 +3 +4 +6 +3 +5 +7 +2 +4 +5

3. DIGITAL SYSTEM DATA
Number of commands 1, 2, 3, 4, 5, 6, 7 or 8 independent, simultaneous, in any combination

commands individually configurable blocking, permissive or direct tripping
Line interface digital, type G3LD G.703.1, codirectional (RJ45 connector, 8 pole)
56 or 64 kbps RS-422/V.11 interface (Sub-D
connector, 25 pole = RS-530)
optional piggyback, type G1LE E1 interface: 2.048 Mbps (PDH/SDH),

ITU-T G.703.6
T1 interface: 1.544 Mbps (SONET)
(RJ45 connector, 8 pole)
optional piggyback, type G1LO Optical interface: 2.048 Mbps

(E2000 connector, duplex)
optional piggyback, type G1LOa Optical interface: 2.048 Mbps

(LC connector, duplex)
optional connecting cables for RS-422/V.11 X.21/X.24 (Sub-D, 15 pole),

EIA RS-530 (Sub-D, 25 pole),
EIA RS-449 (Sub-D, 37 pole),
or terminal blocks with isolating blades
optional connecting cable for G.703/E1/T1 RJ45 (8 pole, 1:1 direct wire connection)
optional connecting cables for G1LO E2000 (Single-mode, duplex)

FC/PC (Single-mode, duplex)
optional connecting cables for G1LOa ST (multi-mode, duplex)

FC/PC (single-mode, duplex)
LC (multi-mode and single-mode, duplex)
Frequency stability  ± 6.4 Hz (± 100 ppm)
Operating principle guard state guard message

command state command message
test state test message
Message coding Cyclic block code

- Bose-Chaudhuri-Hocquenghem BCH (31,21,5)
- Hamming Distance 5
- Code structure 21 bits for guard, commands, test, address
10 bits for error detection and correction
Frame length 6 x 8 bit = 48 bit in 64 kbps mode 31 bit BCH(31,21,5) plus 17 synchronization bits
7 x 7 bit = 49 bit in 56 kbps mode 31 bit BCH(31,21,5) plus 18 synchronization bits
Signal processing dynamic adaptive frame evaluation 2 to 6 frames / correction of max. 1 bit error
depending on prevailing channel condition
- blocking 2 or 3 frames (with max. 1 bit error per frame)
- permissive tripping 3 or 5 frames (with max. 1 bit error per frame)
- direct tripping 4 or 6 frames (with max. 1 bit error per frame)
Nominal transmission time T0 for back-to-back operation (according to IEC 60834-1),

including operating time of the relay interface G3LR (solid state outputs)
- blocking T0  4 ms
- permissive tripping T0  5 ms
- direct tripping T0  6 ms
Security Puc according to IEC 60834-1 with 200 ms BER bursts / 200 ms pause
@ BER = 0.5: @ BER = 0.15 (worst case):
- blocking Puc < 1E-10 blocking Puc < 1E-05
- permissive Puc < 1E-17 permissive Puc < 1E-09
- direct Puc < 1E-24 direct Puc < 1E-12
Dependability Pmc measured according to IEC 60834-1 for T0 as stated above

required BER for Pmc < 1% in 1.3 T0
- blocking BER < 1E-03
- permissive BER < 8 x 1E-04
- direct BER < 5 x 1E-04
Performance guidance figures as per IEC 60834-1 (Fig. 21) are met for all configurations.

Addressing facility range of digital terminal addresses 0 to 1023
- Configuration and monitoring of the opposite equipment from the local terminal
- Needs no additional channel
- Available during guard and command state
Transmission rate channel data rate 56 kbps 1000 bps

channel data rate 64 kbps 1333 bps
4. ETHERNET SYSTEM DATA
Number of commands 1, 2, 3, 4, 5, 6, 7 or 8 independent, simultaneous, in any combination

Line interface Ethernet, type G3LE 10/100 Mbps Fast Ethernet (RJ45 connector,
8 pole), auto/manual negotiation, full/half duplex
optional SFP (Small Form-factor Pluggable) Optical (100 Mbps):
850 nm multi-mode (connector type LC)
1310 nm single-mode (connector type LC)
connecting cables for RJ45 Cat5e Ethernet cable SF/UTP according to
ISO/IEC 11801 (electrical)
Operating principle guard state guard packets

command state command packets
test state test packets
Message coding UDP/IP based default UDP port 49152 for Teleprotection traffic,
(User Datagram Protocol) default UDP port 49153 for EOC traffic
APDU protected addressing by using MAC addresses,
(Application Protocol Data Unit) frame numbering by using sequence numbers,
(SHA = Secure Hash Algorithm) authentication by APDU protection using SHA-256
Ethernet frame 110 byte Ethernet frame w/o VLAN tagging excluding Ethernet preamble (9 byte)
114 byte Ethernet frame with VLAN tagging excluding Ethernet preamble (9 byte)
Required bandwidth max. data rate without VLAN tagging 476 kbps at command transfer
average data rate without VLAN tagging 191 kbps at 5 ms guard packet interval (adjustable)
max. data rate with VLAN tagging 492 kbps at command transfer
average data rate with VLAN tagging 197 kbps at 5 ms guard packet interval (adjustable)
(all values unidirectional and including Ethernet
preamble)
VLAN / priority VLAN tagging selectable via HMI570 disabled (default) / enabled
(Layer 2, optional) IEEE 802.1q VLAN-ID 0 to 4094, if enabled: default 1
IEEE 802.1p Ethernet priority 0 to 7 (highest priority), if enabled: default 5
IP priority Differentiated services / Type of Service DiffServ (6 bit DSCP + 2 bit ECN) / TOS (8 bit)
(Layer 3) selectable via HMI570:
Differentiated Services Code Point (DSCP) 0 to 63 (6 bit, default 46 = Expedited Forwarding)
Explicit Congestion Notification (ECN) 0 to 3 (2 bit, default 0)
Nominal transmission time T0 for back-to-back operation (according to IEC 60834-1),

including operating time of the relay interface G3LR (solid state outputs)
- blocking, permissive & direct tripping T0  4 ms
Security Puc according to IEC 60834-1 with 200 ms BER bursts / 200 ms pause
- by 32-bit CRC Ethernet trailer & SHA-256 < 1E-18
Dependability Pmc measured according to IEC 60834-1 for T0 as stated above
Performance criteria Abbrev. blocking / permissive tripping / direct tripping

Dependability - probability of missing a command Pmc < 1E-02 1E-03 1E-02 1E-04 1E-03 1E-02 1E-04 1E-03
channel condition - required packet loss rate PLR < 0.1% 0.1% 1% 0.1% 3% 10% 4% 9%
equal bit error rate (119 byte packets every 2 ms) BER < 1.1E-06 1.1E-06 1.2E-05 1.1E-06 3.5E-05 1.2E-04 4.7E-05 1.1E-04
max. actual transmission time Tac  4 ms 5 ms 5 ms 6 ms 6 ms 6 ms 8 ms 8 ms
Performance criteria Abbrev. blocking / permissive tripping / direct tripping

Dependability - probability of missing a command Pmc < 1E-02 1E-04 1E-02 1E-04 1E-03 1E-04 1E-04 1E-04
channel condition - required packet loss rate PLR < 20% 10% 30% 10% 20% 20% 30% 50%
equal bit error rate (119 byte packets every 2 ms) BER < 2.6E-04 1.2E-04 4.1E-04 1.2E-04 2.6E-04 2.6E-04 4.1E-04 7.9E-04
max. actual transmission time Tac  8 ms 10 ms 10 ms 12 ms 12 ms 15 ms 20 ms 30 ms

- Configuration and monitoring of the opposite equipment from the local terminal
- Needs no additional channel
- Available during guard and command state
Transmission rate according to data rate of serial HMI570 connection at 9’600 / 19’200 / 57’600 bps
Cyber/IT security integrity - unauthorized modification combination of node addressing, sequence

numbering and keyed message digest
authentication – spoofing/forgery by keyed message digest and sequence numbering
(e.g. man-in-the-middle attacks)
authorization – unauthorized use combination of sequenced number and message
(e.g. message tampering/faking) digest
auditability - hiding of attacks combination of sequenced number and message
(e.g. replay) digest
Availability - Denial of Service (DoS) by socket checking and limited receive FIFO queue,
packet size 100 byte, processing of 1 packet per ms
WAN password complexity At least 8 characters (must be a combination of
letters, numbers and “special” characters)
5. COMMON SYSTEM DATA
Device address range for connecting to PC via HMI570 1 to 240
Sent command pick up time programmable for each command 0 to 20 ms, steps of 1 ms
(Tx Input On-Delay) compensation of sent commands duration equal to the pick-up time
Sent command prolongation 1 programmable for each command 0 to 3 s, steps of 1 ms

(Prolonged Tx Input Duration) default value 0 ms
Sent command limitation 1 programmable for each command 20 ms to 3 s, steps of 1 ms

(Limited Tx Input Duration) default value 100 ms
Sent command fixed duration 1 programmable for each command 20 ms to 3 s, steps of 1 ms

(Fixed Tx Input Duration) default value 100 ms
Received command prolongation programmable for each command 0 to 3 s, steps of 1 ms

(Prolonged Rx Output Duration) default value for blocking 0 ms
default value for permissive tripping 10 ms
default value for direct tripping 100 ms
Received command limitation 1 programmable for each command 20 ms to 3 s, steps of 1 ms

(Limited Rx Output Duration) default value 100 ms
Received command fixed duration 1 programmable for each command 20 ms to 3 s, steps of 1 ms

(Fixed Rx Output Duration) default value 100 ms
Unblocking output unblocking condition Analog no guard and no trip received

unblocking threshold programmable -20 to -10 dB from nominal level (1 dB steps)
default unblocking threshold -14 dB from nominal level
detection delay less than nominal command transmission time
unblocking condition Digital LOS or AIS received, or invalid frames
detection delay less than nominal command transmission time
unblocking condition Ethernet LOS or two consecutive guard packets lost
detection delay according to configured guard packets interval
extra output pick-up delay 0 ms to 100 ms, programmable in steps of 1 ms
(default 10 ms)
unblocking pulse duration 50 ms to 500 ms, programmable in steps of 1 ms
(default 200 ms)
unblocking output freely configurable onto free contacts of any relay interface G3LR
Command output status

during channel alarm programmable:
- outputs assume states in accordance with current input tripping signal processing, i.e. they are
not influenced by the alarm (default)
- all outputs are forced into guard state (blocked)
- direct tripping O/Ps are forced to guard state and permissive or blocking O/Ps to command state
- the command outputs retain the status they had immediately prior to the alarm (“freezing”)
1
Available only for NSD570 Rel.3.2 or later.

pick-up time 0 to 15 s, programmable in steps of 1 s

(default 10 s, except for “freezing” -> 0 s)
hold time 0 to 15 s, programmable in steps of 1 s
(default 0 s)
Command acknowledge free allocation of a command acknowledge O/P to one of the outputs of the relay interface G3LR
- for sent commands individual or collective
- for received commands collective
Received guard state signaling free allocation to one of the outputs of the relay interface G3LR
Built-in test facilities:
Cyclic loop test - The loop test signal is transmitted in the same way as a tripping signal
(in case of the NSD570 Analog version, the tripping signal is not boosted)
- It is recognized by the receiver and echoed back to the transmitter
- A genuine tripping command is always given priority over any tests
configurable test interval 1 / 3 / 6 (default) / 12 / 24, hours, or disabled
first loop test sent 10 minutes after power-on
loop test alarm (NSD570 Analog/Digital) after 3 unsuccessful trials
if a loop test fails, the test interval is lowered to 5 minutes
event recording sent / replied / failed loop test
Manual loop test - Activated via HMI570, or by pressing the loop test button on the equipment front panel
HMI570 window displays actual transmission time (Tac) as ½ round trip time
- Activated by pressing the loop test button on the equipment front panel
Display Panel shows actual transmission time (Tac) as ½ round trip time
test success indication green Trip LED lights up for 3 seconds

test failure indication red Fail LED flashes for 3 seconds
Local test mode - All sent commands are looped back by the local line interface
- The guard signal is transmitted to the opposite station
- Commands are not transferred to the remote end
activated via HMI570
test mode indication red Fail LED flashes (on local equipment)
Remote test mode - Remote command outputs are blocked

- All transmitted commands are sent back by the remote line interface to the local terminal
activated via HMI570 and EOC
test mode indication red Fail LED flashes (on remote equipment)
6. SPECIAL OPERATING MODES
T-operation
- For the protection of cables and power lines with T-offs (multi-terminal lines)
- A command sent by any station is received by all other stations
- Transit through-connection of signals in T-stations between two NSD570 in the same rack, with minimum delay
- Restoring of guard signal in T-Station if one link fails
- For NSD570 Analog and Digital, EOC communication is only available between outer stations (“normal” T-operation)
- For NSD570 Ethernet, EOC communication is only available between the outer stations and the T-station (“normal” T-operation)
Transit delay NSD570 Analog for all bandwidths < 3 ms
Transit delay NSD570 Digital for all interface types / data rates < 3 ms
Transit delay NSD570 Ethernet for all interface types / data rates < 3 ms
1+1 protection
- For path and equipment redundancy

- From NSD570 Rel.3.2 onwards, two Line Interfaces in the same rack serving two different communication channels and sharing
common Relay Interfaces plugged in the slots of TPE 1 (for Ethernet Line Interface available from NSD570 Rel.3.4 or later)
- Main and Stand-by redundancy scheme increases the system availability considerably while not compromising the security

7. ANALOG LINE INTERFACE (G3LA)
CE standards compliance Common Technical Regulation CTR017,

Technical Basis for Regulation TBR017
Hardware release monitoring via HMI570
Line interface 4-wire or 2-wire 600 Ohm terminated or high impedance

(jumper setting)
Boost output Electrically isolated via opto-coupler
Max. number of NSD570 connected in parallel to the same circuit ≤ 3 (recommended)
Transmitter:
AF output Isolated from ground balanced

Impedance terminated 600 Ohm
high-impedance > 1.5 kOhm
300 Hz … 500 Hz > 12.0 dB
Return loss (Rnom = 600 Ohm)
500 Hz … 4 kHz > 15.0 dB
Longitudinal conversion loss 300 Hz … 600 Hz > 40 dB
(compliant with TBR017) 600 Hz … 3.4 kHz > 46 dB
Balance-to-ground 300 Hz … 4 kHz > 40 dB
Spurious emissions < 8 kHz < - 38 dBm
> 8 kHz < - 56 dBm
guard signal - 24 dBm to + 2 dBm
Signal level single tones adjustable in steps of 1.0 dB
command signal (incl. power boosting) - 24 dBm to + 11 dBm
Signal level dual tones (RMS) command signal (incl. power boosting) - 27 dBm to + 8 dBm
- 3 dB to -10 dB
Transmitter monitor level drop off
adjustable in steps of 1.0 dB
Attenuation distortion 300 Hz … 4 kHz ± 1.0 dB
Admissible transverse application of 50/60 Hz with min. receiving signal level 10 Vp
Boost control output Electrically isolated contact Opto-coupler

Contact ratings voltage max. 60 VDC
current max. 50 mA (limited)
polarity independent
Operating time pick-up delay < 250 us
Overvoltage protection voltage < 80 VDC
Power boosting ratio 0 to 9 dB,
adjustable in steps of 1 dB
Receiver:
AF input Isolated from ground balanced

Impedance terminated 600 Ohm
high-impedance > 1.5 kOhm
Return loss (Rnom = 600 Ohm) 300 Hz … 500 Hz > 12.0 dB
500 Hz … 4 kHz > 16.0 dB
Longitudinal conversion loss 300 Hz … 600 Hz > 40 dB
(according to TBR017) 600 Hz … 3.4 kHz > 46 dB
Balance-to-ground 300 Hz … 4 kHz > 40 dB
Received signal level - 30 dBm to + 2 dBm
nominal
Level monitor ± 3 dB to ± 12 dB
Lower and upper limit programmable
Receiver dynamic range from nominal  15 dB
Attenuation distortion 300 Hz … 4 kHz ± 1.0 dB
Admissible transverse application of 50/60 Hz with min. receiving signal level 10 Vp

8. DIGITAL LINE INTERFACES (G3LD)
8.1. G.703 Codirectional Interface

Coding and electrical characteristics according to ITU-T G.703, jitter specification according to G.823.
Data and Clock output:
Bit rate 64 kbps

Symbol rate 256 kBaud
Clock tolerance  100 ppm
Longitudinal conversion loss 128 kHz > 50 dB
Output jitter amplitude Band B1 (20 Hz…20 kHz) < 0.25 UI
Band B2 (3 kHz…20 kHz) < 0.05 UI
Test load impedance 120 Ohm
Peak voltage of a pulse (Mark) 1.0 V
Peak voltage without a pulse (Space) 0  0.1 V
Synchronization of Tx clock frequency programmable ON/OFF on receive clock
UI = Unit Interval (1 / Symbol Rate)
Data and clock input:
Bit rate 64 kbps

Symbol rate 256 kBaud
Clock tolerance  100 ppm
Longitudinal conversion loss 128 kHz > 50 dB
Input jitter acceptance up to 4.33 Hz > 1.15 UI
20 Hz…600 Hz > 0.25 UI
3 kHz…20 kHz > 0.05 UI
Return loss 4 kHz … 13 kHz > 12 dB
13 kHz … 256 kHz > 18 dB
256 kHz … 384 kHz > 14 dB
Input impedance 120 Ohm
Voltage of a pulse 1.0 V
Admissible transverse application of 50/60 Hz cable attenuation 3 dB 300 mVpp transversal
Various:
Shielding, cable screen to be earthed with metallic clamp on → cable tray at rear side of rack
Maximum cable length 22 AWG 500 m
(using STP = Shielded Twisted Pair) (diameter 0.6438 mm = 0.3255 mm2)
Alarms: incoming signal level too low Loss Of Signal (LOS)
4 x 8 = 32 following bits logical "1" Alarm Indication Signal (AIS)
Onboard Connector RJ45

8.2. RS-422 Interface

The electrical characteristics comply with TIA/EIA-422-B (RS-422) and ITU-T V.11, the pinout complies with TIA/EIA-530-A (RS-530).
Signal output (SD):
Bit rate 64 kbps or 56 kbps

Output voltage with 100 Ohm load   2 V differential
Synchronization of Tx clock frequency (configurable via HMI570) off (none), ST, RD
Clock Output to DCE (TT):
Frequency 64 kHz or 56 kHz

Tolerance  100 ppm
Output voltage with 100 Ohm load   2 V differential
Synchronization of TT clock frequency (configurable via HMI570) off (none), RD
Signal input (RD):

Input voltage   6 V differential
  7 V to signal ground
Sensitivity   0.2 V
Input impedance > 100 … < 120 Ohm
Synchronization of Rx clock frequency (configurable via HMI570) off (none), RT, RD
Clock tolerance when Rx clock is extracted from RD  100 ppm
Clock input transmitter (ST) and receiver (RT):

Input voltage   6 V differential
  7 V to signal ground
Sensitivity   0.2 V
Input impedance > 100 … < 120 Ohm
Clock tolerance of external ST  100 ppm
Clock tolerance of external RT  100 ppm
Various:
Maximum cable length Internal clock 1000 m
(using STP = Shielded Twisted Pair, 22 AWG) External clock 500 m
Onboard Connector Sub-D, 25 pol, male, TIA/EIA-530-A
(RS-530)

8.3. E1/T1 Interface (G1LE)
Optional piggyback to be mounted on Digital Interface G3LD (configurable for E1 and T1 operation; E1 = default configuration).
Connector on piggyback RJ45
E1 interface (2.048 Mbps)
Coding and electrical characteristics comply with ITU-T recommendation G.703. Framing according to G.704, signaling according to G.775
and Q.703. Jitter performance according to G.823.
Data is transmitted in timeslot 1 of the E1 frame (timeslot 0 serves for frame synchronization and signaling).
Signal output:
Bit rate 2048 kbps

Tolerance of bit clock  50 ppm
Output jitter amplitude Band B1 (20 Hz… 100 kHz) < 1.5 UI
Band B2 (18 kHz… 100 kHz) < 0.2 UI
Output impedance Jumper setting 120 Ohm
Signal input:
Bit rate 2048 kbps

Return Loss 51 kHz … 102 kHz > 12 dB
102 kHz … 2048 kHz > 18 dB
2048 kHz … 3072 kHz > 14 dB
Input jitter acceptance up to 1.67 Hz > 18 UI
20 Hz…2.4 kHz > 1.5 UI
18 kHz…100 kHz > 0.2 UI
Input impedance Jumper setting 120 Ohm
Various:
Data stream encoding/decoding configurable for AMI or HDB3 (default)

detection of code violations AMI -> all violations are recognized
HDB3 -> double violations and 4 subsequent
zeroes
Receiver sensitivity configurable for max. cable attenuation 10 dB (short haul; default)
43 dB (long haul)
Clock synchronization slave mode on receive data

- if no data is received (LOS) switches automatically to free running mode
Internal elastic buffer size configurable individual for input/output 0 or 96 Bits, 1 or 2 frames (default)
-> compensates clock deviations and wander between internal/external timing
-> compensates jitter, detects slips with some additional delay
compromise to be made on high jitter tolerance versus low additional delay
Framing formats double-frame (default) Sync. pattern in timeslot 0 (E1)

- maximum synchronization delay 375 s
CRC4-multiframe transmission of CRC4 bits
- maximum synchronization delay 2.125 ms
Alarms: incoming signal too low,

too few transitions Loss Of Signal (LOS)
all one condition Alarm Indication Signal (AIS)
alarm in remote station Remote Receive Alarm (RRA)
frame detection failed Loss of Frame Alignment (LFA)

T1 Interface (1.544 Mbps)

Coding and signal comply with ITU-T recommendation G.703 and ANSI T1.102. Framing according to G.704, signaling according to G.775
and Q.703. Jitter performance according to G.823.
Data is transmitted in channel 1 of the T1 frame (the first bit serves for frame synchronization and signaling).
Signal output:
Bit rate 1544 kbps

Output jitter amplitude Band B1 (10 Hz… 40 kHz) < 5 UI
Band B2 (8 kHz… 40 kHz) < 0.1 UI
Output impedance Jumper setting 100 Ohm
Tolerance of output impedance 5%
Peak voltage of a pulse 3.6 V
Minimum voltage of a pulse 2.4 V
Signal input:
Bit rate 1544 kbps

Input impedance Jumper setting 100 Ohm
Tolerance of input impedance 5%
Peak voltage of a pulse 3.6 V
Minimum voltage of a pulse 2.4 V
Various:
Data stream encoding/decoding configurable for AMI or B8ZS (default)

if AMI line coding is configured, 0xFF is transmitted
in timeslot 3 to allow loss of signal detection
Receiver sensitivity configurable for max. cable attenuation 10 dB (short haul; default)
36 dB (long haul)
Clock synchronization slave mode on receiving data

Internal buffer size configurable individually for input/output 0 or 96 Bits, 1 or 2 frames (default)
-> compensates clock deviations/wander (between internal/external timing)
-> compensates jitter, detects slips (with some additional delay)
compromise to be made on high jitter capability versus low additional delay
Framing formats 4-multiframe (default) synchronization data in bit 1 (T1)

extended superframe (24 frames) additional transmission of CRC6 data
(in order to detect transmission bit errors;
remote alarm reception even with high BER)
Alarms: incoming signal level too low,

too few transitions Loss Of Signal (LOS)
all one condition Alarm Indication Signal (AIS)
alarm in remote station Remote Receive Alarm (RRA)
frame detection failed Loss of Frame Alignment (LFA)

8.4. Optical Interface (G1LO)
Optional piggyback to be mounted on Digital Interface G3LD (configurable for Optical Direct Fiber and Optical OTERM/OPTIF operation).
Connector on piggyback E2000/APC (others via adaptor)
Framing complies with ITU-T recommendation G.704 for Optical Direct Fiber and with FOX-6Plus for Optical OTERM/OPTIF operation. The
jitter performance is according to G.823.
Data is transmitted in timeslot 1 of the PCM31 frame for Optical Direct Fiber and in channel 1 of the FOX-6Plus frame if Optical
OTERM/OPTIF is selected.
Signal output:
Wavelength 1310 nm
Bit rate 2048 kbps
Bit clock accuracy  50 ppm
Output jitter amplitude Band B1 (20 Hz… 100 kHz) < 1.5 UI
Band B2 (18 kHz… 100 kHz) < 0.2 UI
Optical output power Short haul -22 … -17 dBm
Long haul -5 … -1 dBm
Signal input:
Wavelength range Sensitivity < -32 dBm 850 … 1550 nm

Bit rate 2048 kbps
Input jitter tolerance up to 1.67 Hz > 18 UI
20 … 2400 Hz > 1.5 UI
18 ... 100 kHz > 0.2 UI
Receiver input sensitivity < -36 dBm
Receiver saturation power > - 1 dBm
Various:
Maximum cable length 9 m single-mode fiber (acc. G.652) 50 km

50 m multi-mode fiber (acc. G.651) 25 km
Data stream encoding/decoding CMI (Code Mark Inversion)
Optical transmission rate 4096 kBd
Clock synchronization slave mode on receive data

Internal elastic buffer size fixed setting 2 frames

-> compensates clock deviations and wander between internal/external timing
-> compensates jitter, detects slips with some additional delay
Framing format Optical Direct Fiber double-frame sync. pattern in timeslot 0 (PCM31)
- maximum synchronization delay 375 s
Framing format Optical FOX/OTERM according to FOX-6Plus 32 bits with 5 sync. bits every 15.625 s
- can also be connected with OTERM on FOX515
Alarm too few transitions Loss Of Signal (LOS)
Optical budget including aging 25 dB
Notes:
G1LO was phased out by end of 2008 (replaced by G1LOa).

8.5. Optical Interface (G1LOa)
Optional piggyback to be mounted on Digital Interface G3LD (configurable for Optical Direct Fiber, Optical OTERM/OPTIF and Optical IEEE
C37.94 operation).
Selection of wavelength and distance through insertion of a particular SFP transceiver module, according to the required application
Connector on piggyback: LC/PC (others via adaptor)
Signal output:
Interface type → Optical IEEE C37.94 Optical OTERM/OPTIF Optical Direct Fiber
Framing complies to IEEE C37.94 ABB FOX-6Plus ITU-T G.704
Data transmission in Channel 1 of 12 (64 kbps) Channel 1 of 6 (64 kbps) Time slot 1 of 32 (64 kbps)
Transmission rate 2048 kbaud 4096 kbaud 4096 kbaud
Bit rate 2048 kbps 2048 kbps 2048 kbps
Line coding NRZ MCMI MCMI
Bit clock accuracy  30 ppm  30 ppm  30 ppm
Output jitter amplitude < 0.1 UI < 0.15 UI < 0.15 UI
Signal input:
Interface type → Optical IEEE C37.94 Optical OTERM/OPTIF Optical Direct Fiber
Bit clock tolerance  100 ppm  100 ppm  100 ppm
Input jitter tolerance > 0.2 > 0.2 > 0.2
Clock Mode Slave or free running if LOS is Slave or free running if LOS is Master or Slave (Configurable)
detected detected
Synchronization to Header (first 16 bits of frame) 8 synchronization bits, Double frame in time slot 0
distributed in one frame
Detected alarms - SFP transceiver not plugged - SFP transceiver not plugged - SFP transceiver not plugged
- Laser failure - Laser failure - Laser failure
- LOS Loss Of Signal - LOS Loss Of Signal - LOS Loss Of Signal
- LOF Loss Of Frame - LOF Loss Of Frame - LOF Loss Of Frame
- AIS Alarm Indication Signal - LFA Loss of Frame Alignment - AIS Alarm Indication Signal
- RRA Receive Remote Alarm - AIS Alarm Indication Signal - RRA Receive Remote Alarm
- RRA Receive Remote Alarm
The optical parameters are subject to the selected SFP transceiver module. The following table shows the characteristics of the SFP
transceiver modules approved for G1LOa and available by default (others on request):
IEEE C37.94 IEEE C37.94,

Interface type → OTERM/OPTIF,
Direct Fiber Direct Fiber only
SFP application 2 Mbps S-1.1 L-1.1 X-1.2 U-1.2
Wavelength 850 nm 1310 nm 1310 nm 1550 nm CWDM 1550 nm
Media Multi-mode fiber Single-mode fiber Single-mode fiber Single-mode fiber Single-mode fiber
Nominal distance 1 km 30 km 60 km 120 km 180 km
Maximum distance 2 2 km 50 km 80 km 150 km 240 km
Output power -19 … -11 dBm 3 -15 … -8 dBm -5 … 0 dBm 0 … 5 dBm 5 … 8 dBm
Input sensitivity -32 dBm -34 dBm -34 dBm -35 dBm -45 dBm
Input saturation -3 dBm 0 dBm -3 dBm 0 dBm -10 dBm
Optical budget 13 dB 19 dB 29 dB 35 dB 50 dB
2
The maximum distance is dependent on the attenuation per kilometer of the used optical fiber and the number of required splices.
3
Level range according to IEEE C37.94 for "mean optical power" into 62.5/125 μm fiber. For "mean optical power" into 50/125 μm fiber the
level range is -23 dBm … -11 dBm.
Please note that previous 850 nm SFP transceivers, used for NSD570 until mid of 2013, provide higher optical output power than defined
in the IEEE C37.94 standard, thus optical attenuators may be required for connection of NSD570 to other vendor’s multiplexer equipment
via these phased out SFP transceivers (depending on the attenuation of the used optical fiber and its connectors, and on the saturation
level of the multiplexer’s optical receiver).

9. ETHERNET LINE INTERFACES (G3LE)
Connectors RJ45 for 100BASE-TX interface, cage for SFP module insertion
Selection of interface by setting lever of switch towards 100BASE-TX (RJ45) or SFP interface
Selection of SFP interface through insertion of a particular SFP transceiver module, according to the required application
Connector on SFP: LC/PC (others via adaptor)
100BASE-TX Interface (RJ45):
Data rate 10/100 Mbps

Modes Auto negotiation or Manual
Data rate (available in Manual mode only) 10 Mbps or 100 Mbps
Duplex modes (available in Manual mode only) Full Duplex or Half Duplex
Onboard connector RJ45
Electrically compliant with IEEE 802.3 10BASE-T
IEEE 802.3 100BASE-TX
Specified cable Cat5e Ethernet cable SF/UTP according to
SFP interface:
Data rate optical 100 Mbps

Optional SFP (Small Form-factor Pluggable) 850 nm multi-mode (connector type LC)
Laser settings ALS (Automatic Laser shutdown)
transceiver modules approved for G3LE and available by default (others on request):
Wavelength 850 nm 1310 nm 1310 nm

Media Multi-mode fiber Multi-mode fiber Single-mode fiber
Nominal distance 0.5 km 0.5 km 30 km
Maximum distance 4 1.0 km 1.0 km 50 km
Output power -19 … -11 dBm (62.5 μm) -20 … -14 dBm (62.5 μm) -15 … -8 dBm
-23 … -11 dBm (50 μm) -23.5 … -14 dBm (50 μm)
Input sensitivity -32 dBm -31 dBm -34 dBm
Input saturation -3 dBm -8 dBm 0 dBm
Optical budget 13 dB 11 dB 19 dB
Various:
Ethernet frame size 110 byte without VLAN tagging,

114 byte with VLAN tagging,
excluding Ethernet preamble (9 byte)
Max. data rates 476 kbps at command transfer without
(in one direction, including Ethernet preamble) VLAN tagging
191 kbps at 5 ms guard packets interval
average data rate without VLAN tagging
492 kbps at command transfer with VLAN
tagging
197 kbps at 5 ms guard interval average
data rate with VLAN tagging
Notes:
For used UDP ports refer to Section 4. Ethernet System Data.
4

10. RELAY INTERFACE (G3LR)
Signal inputs (opto couplers)
Number of command send inputs 2, electrically isolated by opto couplers commands can be freely allocated to I/Ps
Method of tripping - external contact and station battery voltage polarity independent
- external dry contact with optional internal aux. tripping voltage G1LR
Nominal battery voltage (24, 48, 60, 110, 125, 220, 250) VDC tolerance ± 20 %
G3LR: Input voltage ranges 5 3, programmable with jumpers:

Jumpers Nominal battery voltage
.A + .B 24 VDC to 48 VDC
.A + .C 60 VDC to 110 VDC
.A + .D 125 VDC to 250 VDC
G3LRa: Input voltage ranges 4, programmable with jumpers:
Jumpers Nominal battery voltage
.A + .B 24 VDC
.A + .C 48 VDC to 60 VDC
.A + .D 110 VDC to 125 VDC
.A + .E 220 VDC to 250 VDC
G3LR: Operating thresholds input operates at:
Jumpers Voltage
.A + .B 10 … 15 VDC
.A + .C 25 … 30 VDC
.A + .D 70 … 80 VDC
G3LRa: Operating thresholds input operates at:
Jumpers Voltage
.A + .B 10 … 15 VDC
.A + .C 25 … 30 VDC
.A + .D 70 … 80 VDC
.A + .E 146 … 165 VDC
G3LR: Contact burden input current ION

for nominal battery voltage ≥ 48 VDC 10 … 20 mA
for nominal battery voltage 24 VDC 5 … 10 mA
I/mA
ION
tON t/ms
G3LRa: Contact burden steady state input current IC 3 … 5 mA

inrush current IP > 20 mA 6
tA 7 – tON > 10 ms
electric charge Q > 200 µC
I/mA
IP
Q
IC
tON tA t/ms
Operating time < 750 s, 450 s typical
Overvoltage protection 400 VDC
5
Nominal battery voltage 220 VDC and 250 VDC are not suitable for persistent command application!
6
Wetting current for electrical and thermal destruction of oxidation/corrosion buildup on the external relay contacts.
7
tA is the instant of time when the input current is equal to 10 mA.
Signal outputs (solid state)
Number of outputs 2 electrically isolated commands, alarms and special functions freely
assignable
Normally Open contact solid-state relay bounce-free, shock and vibration safe
DC voltage 5 … 250 VDC (+ 20 % max.)
Tripping current ON/OFF ratio  1/3 up to 1 min./3 min.  2 A;
Continuous 1A
Current limitation typ. 2.6 A
Short circuit cut off after approx. 6 ms for 1 s
Leakage current  200 A; at 312 V / 70C
Operating time  250 s (typ. 60 s)
Reverse polarity protection 400 VDC
Signal outputs (Relay)
Number of outputs 2 (electrically isolated)

"Heavy Duty" commands, alarms and special
functions freely assignable
Normally Open contact mono stable,
or Normally Closed contact electromechanical relay
Max. switching power see diagram
Tripping command 5 ... 250 VDC
250 VAC max.
Rated current  5 A carry (up to 45°C)
≤ 10 A carry (for 1 sec.)
≤ 16 A make (for 200 ms)
Break current (DC inductive load) up to 1 A @ 250 VDC
(depending on L and R, an external
"arc suppression" may be required)
Operating time < 8 ms (typ. 4 ms)
Bounce < 1 ms (typ. 0.2 ms)
Reset time < 4 ms (typ. 3.6 ms)
Notes:
G3LR is phased out by end of 2016 (replaced by G3LRa).

11. GOOSE LAN INTERFACE (G3LS)
Data rate 100 Mbps

Duplex mode Full Duplex
SFP interface:

transceiver modules approved for G3LS and available by default (others on request):

-23 … -11 dBm (50 μm) -23.5 … -14 dBm (50 μm)
GOOSE message processing time at the sending side < 3 ms 9

at the receiving side < 3 ms 9
Supports IEC 61850 Edition 1 and Edition 2.
IEC 61850 related data:

Can be found in the following documents:
• Model Implementation Conformance Statement for the IEC 61850 interface in NSD570 with G3LS extension.
1KHW002634_NSD570_G3LS_IEC_61850_MICS.pdf
• Protocol Implementation Conformance Statement for the IEC 61850 interface in NSD570 with G3LS extension.
1KHW002635_NSD570_G3LS_IEC_61850_PICS.pdf
• Tissues Implementation Conformance Statement for the IEC 61850 interface in NSD570 with G3LS extension.
1KHW002636_NSD570_G3LS_IEC_61850_TICS.pdf
• Protocol Implementation eXtra Information for Testing for the IEC 61850 interface in NSD570 with G3LS extension.
1KHW002637_NSD570_G3LS_IEC_61850_PIXIT.pdf
• SCL Implementation Conformance Statement for the IEC 61850 interface in NSD570 with G3LS extension.
1KHW002638_NSD570_G3LS_IEC_61850_SICS.pdf
8
9
The nominal transmission times as specified for the Analog/Digital/Ethernet systems have to be increased by min. 1 ms / max. 3 ms per
end of the NSD570 link when a GOOSE LAN Interface G3LS instead of Relay Interface G3LR is used for command forwarding.

12. POWER SUPPLY
12.1. G3LH
- Electrically isolated
- Hot pluggable
- Output power 60 W sufficient to supply all possible rack assemblies
- Single or redundant configuration (passive load sharing, decoupled by means of diodes)
Nominal input voltage from 48 VDC to 250 VDC (± 20 %)

from 100 VAC to 240 VAC (-15%, +10%)
Plug-in Monitoring plugged / not plugged
Output voltage 12.3 VDC
Output voltage monitoring independent for both power supply modules
Efficiency DC > 80 %
AC > 75 %
Reverse polarity protection not applicable (bipolar connection possible)

Overvoltage protection on primary side
Short circuit proof on secondary side approx. 6 A
Immunity against power interruptions on primary side 20 ms
Fuse 5 x 20 mm 2.5 AT
Onboard Connector: H 15 (DIN 41612)
Notes:
G3LH was phased out by end of 2010 (replaced by G3LI or G3LK, depending on input voltage).
12.2. G3LI
- Hot pluggable
Reverse polarity protection yes

Short circuit proof on secondary side approx. 7.5 A

12.3. G3LK
- Hot pluggable

from 110 VAC to 230 VAC (-15%, +10%)
AC > 70 %
Reverse polarity protection not applicable (bipolar connection possible)

Short circuit proof on secondary side approx. 7.5 A
12.4. Power Consumption
Maximum power consumption of all kind of modules, valid for all power supplies:
basic version (rack, one supply module, one line interface, one relay interface):
basic version Analog (2 commands) 10 W max

basic version Digital (2 commands) 10 W max.
basic version Ethernet (2 commands) 12 W max.
per additional supply module G3LH 3 W max.

per additional supply module G3LI 3 W max.
per additional supply module G3LK 3 W max.
per additional analog interface G3LA 3 W max.
per additional digital interface G3LD 3 W max.
per additional Ethernet interface G3LE 5 W max.
per additional relay interface G3LR/G3LRa 1 W max.
per additional Ethernet interface G3LS 5 W max.
optional LAN interface G3LL 10 W max.
optional LAN management interface G3LM/G3LMa 5 W max.
optional E1/T1 interface G1LE 0.5 W max.
optional optical interface G1LO/G1LOa 1.5 W max.
optional display panel G1LC 1.5 W max.
optional input tripping voltage G1LR 1 W max.

13. COMMON INTERFACE (G3LC)
LED indication on front panel Supervision of power supply output voltage green = ok, red = failed, dark = not plugged
Main functions on board DC/DC converter for internal +5 V supply voltage

clock source (8.192 MHz) for Real Time Bus (RTB) on busplane
local alarm of the two NSD570 in the rack Two heavy duty relay with free change-over
contacts
RS-232 interface (COM 1):
Service interface TIA/EIA-232-F (RS-232), DCE Electrically isolated

(front access, 9-pole Sub-D socket, female)
Transmission rate programmable 9’600 bps / 19’200 bps / 57’600 bps
Direct connection to COM port of a PC/notebook = DTE
Connecting cable serial 1:1 cable, 9 pin Sub-D connector PC/notebook -> female, NSD570 -> male
Hardware flow control if requested from external devices RTS/CTS
If connected via a modem (= DCE) “Null-Modem” cable necessary (male-male) cross connection of 103  104, 105  106
Protocol 8N1, no flow control
G3LC alarm outputs
Number of outputs 2 (electrically isolated)
"Heavy Duty" one relay for each NSD570 in the

rack (to signal a local alarm)
Normally Open contact mono stable,

or Normally Closed contact electromechanical relay
Max. switching power see diagram
Alarm voltage 5 ... 250 VDC

250 VAC max.
Rated current  5 A carry (up to 45°C)

≤ 10 A carry (for 1 sec.)
≤ 16 A make (for 200 ms)
Break current (DC inductive load) up to 1 A @ 250 VDC

(depending on L and R, an external
"arc suppression" may be required)
Operating time < 8 ms (typ. 4 ms)
Bounce < 1 ms (typ. 0.2 ms)
Reset time < 4 ms (typ. 3.6 ms)
NSD570 intra-station network
Serial two wire station bus interface type RS-485

electrically compliant with TIA/EIA-485-A
cable twisted pair (incl. screen according RS-485
recommendation -> internal isolated ground)
max. cable length 500 m
max. number of interconnected racks 32, i.e. max. 64 NSD570 in local station network
Synchronization of Real Time Clock

(RTC; on line interface)
one input for IRIG-B synchronization signal
one input for PPS external second impulses (GPS) – TTL

IRIG-B input:
Synchronization signal format IRIG-B unmodulated

Supported formats: B000, B001, B002 or B003
Voltage levels Input “LOW” -15V ... + 0.8 V
Input “HIGH” + 2V ... + 15 V
Input resistance  750 Ohm
Over voltage protection ± 26 VDC
Precision of synchronization  0.5 ms
GPS Sync input
Synchronization signal format Pulses Every second (PPS)

Voltage levels Input “LOW” -0.5 V ... + 0.8 V
(TTL) Input “HIGH” +2V…+7V
Input resistance  1 kOhm
Over voltage protection ± 5 VDC
Reverse polarity protection Yes
Precision of synchronization  0.5 ms
14. BUS PLANE WITH FRONT COVER (G1LA)
15. SUPPLY BACKPLANE (G1LB)
Power supply connectors Fast-On 6.3 mm AC: L / N / PE, DC: + / - / PE
16. INTERNAL TRIPPING VOLTAGE (G1LR)
Optional piggyback module to be plugged onto G3LR or G3LRa.

If mounted, both command inputs of the module G3LR are operated by means of a dry external contact.
Internal auxiliary voltage 24 VDC ± 4 V
Power dissipation < 0.5 W per input
Insulation same as command inputs (see section on EMC)
17. LCD DISPLAY PANEL (G1LC)
Optional front panel (instead of Blanking Cover Plate for power supply modules), for displaying status, counters, alarm messages and
firmware versions of the local and remote NSD570.
For local access only, selected configuration data are also available (e.g. line interface settings, command application or relay interface
input/output assignment).
Measured transmission time is displayed when manual loop test button of TPE 1 or TPE 2 is pressed on the front plate.
Display lights up if any command of TPE 1 or TPE 2 is sent or received.
Readout device dot matrix LCD display two lines, 16 characters

Lightness adjustable background LED in 4 steps or switched OFF
Contrast adjustable in 16 steps
Standby time after last interaction adjustable 1 … 60 minutes
Handling menu-driven enabled by four front panel buttons
Internal connection via ribbon cable to Common Interface G3LC supply voltage 12 V / 2-wire data link

18. LAN INTERFACE (G3LL)
Ethernet interface that allows connecting an NSD570 system to TCP/IP-networks for configuration and monitoring.
The “HMI570 LAN” application (server version of the HMI570) runs on the NSD570 LAN Interface.
Serial two wire station bus interface type RS-485

electrically compliant with TIA/EIA-485-A
cable twisted pair (incl. screen according RS-485
recommendation -> internal isolated ground)
Ethernet LAN interface type Ethernet 10BASE-T/100BASE-TX

electrically compliant with IEEE 802.3 10BASE-T
cable S/UTP (Screened / Unshielded Twisted Pair) or
S/STP (Screened / Shielded Twisted Pair)
Ethernet cable, category 5 or higher
Secure sockets layer (SSL) port number 443/TCP
On-board server architecture PC/AT compatible computer PC/104

ROM type 128 MB Compact Flash Card
for HMI570 LAN Version 1.11 and 1.12
256 MB Compact Flash Card
for HMI570 LAN Version 1.10, 1.13 and higher
RTC buffer Lithium battery
battery type MAXELL ER10/28, 3.6V, 410 mAh
battery lifetime 1.0 year @ +85°C
4.5 year @ +25°C
Notes:
G3LL was phased out by end of 2012 (replaced by G3LM).
19. MANAGEMENT LAN INTERFACE (G3LM)
Ethernet interface that allows connecting an NSD570 system to TCP/IP-networks for configuration and monitoring.
In contrast to the LAN interface G3LL, no “HMI570 LAN” application is running on G3LM. Instead, Ethernet to serial port conversion (and
vice versa) and other functions (like SNMP) are performed on this module.
HMI570 version 1.30 or higher has to be used to login on G3LM and connect to any line interface in the same rack or connected to the
station bus.

Data rate 10/100 Mbps

Modes Auto negotiation or Manual
Data rate (available in Manual mode only) 10 Mbps or 100 Mbps
Duplex modes (available in Manual mode only) Full Duplex or Half Duplex
SFP interface:


transceiver modules approved for G3LM and available by default (others on request):

-23 … -11 dBm (50 μm) -23.5 … -14 dBm (50 μm)
VLAN / Priority VLAN tagging selectable via HMI570 disabled (default) / enabled
(Layer 2, optional) IEEE 802.1q VLAN ID 0 to 4094, if enabled: default 1
IEEE 802.1p Ethernet priority 0 to 7 (highest priority), if enabled: default 0
Secure sockets layer (SSL) version TLS 1.2 (for Rel.3.6 or later)
TLS 1.0 (for Rel.3.1 to 3.5)
cipher algorithms RSA 1024, AES128-SHA256 (for Rel.3.6 or later)
RSA 1024, AES128-SHA (for Rel.3.1 to 3.5)
certificate format X.509
port number 5000/TCP
SNMP versions SNMPv1, SNMPv2c, SNMPv3 (for Rel.3.7 or later)

services getRequest, getNextRequest, response, trap;
traps are sent on alarm state or device availability
changes;
with Rel.3.7 or later, traps are also sent for
commands and manipulation events, as well as for
configuration download counter changes.
port number 161/UDP (SNMP Agent)
162/UDP (default port for SNMP traps, configurable
by HMI570)
Management Information Base (MIB) ASN.1 definition of the MIB is supplied
(one MIB-file for SNMPv1, one for SNMPv2c-v3)
network management up to 4 management stations can be served with
traps
application access to device information and alarms of all
NSD570 racks connected to the station bus;
with Rel.3.7 or later, also trip counters are
accessible using SNMP requests.
support of up to 64 terminals via one G3LM
SNMPv3 user administration for Rel.3.7 or later:
max. 10 simultaneous users supported,
enabled users have read access to G3LM,
SNMPv3 authentication protocol configurable for
each user (MD5, SHA or None), password required.
SNMPv3 privacy protocol configurable for each
user (DES, AES or None), password required.
SNTP client (requires G3LMa) version SNTP v1

compatibility NTP/SNTP servers v1, v2, v3 and v4
redundancy up to 2 different servers
application polling the UTC time information from a primary or
secondary server (upon availability), polling interval
configurable by HMI570
UTC time zone offset for Rel.3.7 or later:
38 official offsets configurable by HMI570,
range: from UTC -12:00 to UTC +14:00
Daylight Saving Time (“summer time”) for Rel.3.7 or later:
configurable by HMI570 to “off” and “on” (time offset
+1 hour)
accuracy < 250 us (in case of a back-to-back connection to
the server)
port number 123/UDP
10

User administration max. number of users 200

3 password levels admin/modify/view
password complexity At least 8 characters (must be a combination of
User activity logging max. number of entries 2000 (overwriting circular buffer)
log entries log-in successful or failed (unknown user and/or
wrong password
log-out (by user or by timeout)
configuration download successful or failed
configuration upload successful or failed
recovery of previous configuration successful or
failed
firmware download successful or failed
user account created or deleted
user password changed successfully
user password changed unsuccessfully
user permission changed
manual reset, reset trips (trip counters)
system startup G3LM
logfile created or deleted, date and time set
new certificate generated
IRIG-B output (G3LMa only) 1 electrical, galvanically isolated

Supported serial time code formats: IRIG-B006 (100 pps, pulse with code, no carrier,
BCDTOY, BCDYEAR)
Nominal output voltage: 5 VDC
Output resistance 150 Ohm
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)"
Notes:
G3LM is phased out by end of 2016 (replaced by G3LMa).
20. HMI570 USER INTERFACE
20.1. HMI570 „PC“
Browser front end Microsoft® Edge (recommended) standards: HTTP/1.1, HTML 4
Hardware requirements (minimal) PC/notebook, x86 compatible CPU ≥ AMD Athlon / Duron or Intel Pentium
CPU clock ≥ 1 GHz
RAM ≥ 512 Mbyte
free harddisk space ≥ 200 MB or at least 1 GB in case of the IEC 61850
enabled HMI570
SVGA, resolution ≥ 1024 x 768, 256 colors
operating system Windows 7 / 8 / 10
Access to the system local and remote

Requirements for local access installation on PC/notebook browser plus HMI570 Software on CD-ROM
with install-package
connection PC-to-NSD570 via serial RS-232 interface cable, or
via USB/RS-232 converter
Security 3 password levels admin/modify/view

password complexity At least 8 characters (must be a combination of
HMI570 PC main functions: configuration on-line

configuration off-line with file for downloading
testing and commissioning
status and alarm monitoring
local and remote access to configuration data, hardware inventory,
firmware- and software versions

local alarm polling when connected via serial cable to the RS-232
(of all NSD570s accessible via station bus) interface of one rack or via Ethernet cable to the
LAN interface G3LM of one rack
network alarm polling when connected via Ethernet/IP network to several
LAN Interfaces G3LL and/or G3LM (running local
alarm polling or SNMP alarm polling)
Local and remote access facilities - serial cable at 9’600 bps, 19’200 bps, 57’600 bps
- embedded operation channel (EOC) at 100 bps max (NSD570 Analog) or
at 1’333 bps max. (NSD570 Digital) or
at 9’600/19’200/57’600 bps (NSD570 Ethernet)
- intranet/internet using IP, via LAN Interface type G3LM
Event recorder upload of all events recorded in an equipment

text display of events
events can be saved to file
Firmware download locally or from a remote site via any communication channel,
via EOC of NSD570 Analog -> not recommended
Configuration download in case of failure reverting to the previous operating condition
Manual jumper settings on relay interfaces G3LR input command tripping voltage (4 jumpers)
(also stored in configuration file) on analog interface G3LA line impedance (2 jumpers)
on E1/T1 interface G1LE line impedance (3 jumpers)
20.2. HMI570 „LAN“
The “HMI570 LAN” requires a NSD570 LAN Interface (G3LL)
Browser front end Internet Explorer standards: HTTP/1.1, HTML 4
Access to the system remote (local, if PC is directly connected to G3LL)
Requirements for remote access installation on PC/notebook HTTP 1.1 browser and IP connection to the LAN
Interface G3LL
connection to the NSD570s in a network via Corporate Network (Intranet) or Internet
Security 3 password levels admin/modify/view

Secure socket layer (SSL) connection (for remote connection only)
HMI570 LAN main functions: configuration on-line

configuration off-line with file for downloading
testing and commissioning
status and alarm monitoring
local and remote access to configuration data , hardware inventory,
firmware- and software versions
local alarm polling of all NSD570s accessible via station bus
Remote access facilities intranet/internet using IP, with embedded web server on LAN
Interface G3LL, 10BASE-T/100BASE-TX (option)
Event recorder upload of all events recorded in an equipment

text display of events
events can be saved to file
Firmware download from a remote site via any communication channel,

via EOC of NSD570 Analog -> not recommended
Configuration download in case of failure reverting to the previous operating condition
Manual jumper settings on relay interfaces G3LR input command tripping voltage (4 jumpers)
(also stored in configuration file) on analog interface G3LA line impedance (2 jumpers)
on E1/T1 interface G1LE line impedance (3 jumpers)
Notes:
HMI570 LAN was phased out by end of 2012, together with LAN Interface G3LL (replaced by G3LM).

21. ALARMS
Alarm sources readable via the HMI570
Tx signal level drop from nominal level - 3 dB to - 10 dB (programmable, 1 dB steps)

detection time <1s
Rx guard signal level deviation from nominal level > ± 3 dB … ± 12 dB (programmable, 1 dB steps)
detection time <1s
SNR alarm threshold depending on Bandwidth [Hz] SNR alarm threshold [dB]
channel bandwidth: 120 / 240 / 360 / 480 6
960 9
1200 10
2400 13
2800 14
detection time <1s
Bit Error Rate (BER) alarm threshold setting via HMI570 1E-01 / 1E-02 / 1E-03 (default)
(Digital) 1E-04 / 1E-05 / 1E-06
detection time < 200 s (worst case)
Packet Loss Rate (PLR) alarm threshold setting via HMI570 0.1% to 10%
(Ethernet) default 1%
detection time < 60 s (worst case)
Transmission Time Alarm (Ethernet) Warning/Alarm sensitivity setting low/medium/high
Wrong digital address detection time 2 frames
ALS Automatic Laser Shutdown assert time 500 … 800 ms

negate time 90 ± 10 s
Tx single component failure from relay interface instantaneous alarm

Rx single component failure 2 criteria supervision guard and command signal state violation,
Instantaneous alarm
Max. Tx input monitoring configurable for each command monitoring ENABLED or DISABLED
if monitoring is enabled sending guard signal after programmable delay:
3 to 60 s (default 5 s)
Rx output overload of solid-state command outputs instantaneous
Checksum error external SDRAM / internal SRAM failure instantaneous
Loop test error NSD570 Analog/Digital > 3 attempts
System clock error CPU, Real Time Bus instantaneous
General system error watchdog >5s
Module hardware alarm instantaneous
Power supply voltage too low instantaneous
Internal aux. supply voltage supervision of DC/DC converter 12 VDC / 3.3 VDC (on each board)
Alarm types
The following alarms are freely configurable via the HMI570 onto any free output of a relay interface G3LR:
System alarm / general alarm collective for all alarm sources (local and remote)
Hardware warning indicates that one of the two power supply modules in redundant configuration failed (if “Redundant
Power Supply Failure” is configured to “HW Warning”, else it will raise a HW alarm)
Hardware alarm general hardware failure alarms
Link alarm indicates a link failure (SNR/BER/PLR, level/sync or loop test failure)
Transmit alarm indicates that the failure is in the local sending circuits or the Tx signal is incorrect
Receive alarm indicates that the failure is in the local receiving circuits or the Rx signal is incorrect
Local alarm indicates that the alarm originates from local equipment, also available on G3LC for each NSD570
in the rack
Remote alarm indicates that the alarm originates from remote equipment
Main channel alarm indicates that the Main Line Interface in 1+1 redundant path protection mode has detected a
hardware or link alarm
Standby channel alarm indicates that the Standby Line Interface in 1+1 redundant path protection mode has detected a
hardware or link alarm
User-defined alarm groups 1, 2, 3 freely configurable groups, as a combination of several alarms from the local or from the
remote equipment

General alarm output 1 free changeover contact on G3LC for each NSD570 in the rack
Alarm settings Alarm relay pick-up delay 0 to 15 s (default 15 s)
Alarm relay drop-off time 0 to 15 s (default 15 s)
User alarms 1 – 3 configurable: “delayed” (as above) or “undelayed”
Status and alarm LEDs on the front panel (per NSD570) light up immediately after alarm source is detected
One hardware status LED per line, relay, GOOSE and LAN interface green = Ok / red = Fail
One status LED for each input/output and relay contact green = activated, dark = not activated
Two status LEDs for Guard and Trip reception green = signal reception, dark = no signal
Four alarm LEDs per system Transmit, Receive, Local, Remote Alarm red = alarm
One hardware status LED per power supply module green = Ok / red = Fail; dark = no module plugged
One status LED for the LAN interface green = Ethernet link established, dark = no signal
22. EVENT RECORDER AND COUNTERS
Event recorder:
Start time and end time of transmitted commands

received commands
unblocking pulses
alarms
loop tests sent / replied / failed
manipulations start up / user-reset / configuration download
firmware download / set of date and time / start
manual loop test / reset counter / erase of event
recorder / previous configuration
1+1 path protection switching criteria detected line interface is now active, or
line interface is not active anymore
Storage medium non-volatile memory
No. of recordable events before overwriting of the oldest event 7500 (sequentially stored)
Time resolution 1 ms
Accuracy of time stamp internal Real Time Clock free running -5.3 s… +3.6 s per day (+25°C)
-9.6 s… +3.6 s per day (-5 to +45°C)
aging is ±5 ppm per year
synchronized - on external GPS receiver (IRIG-B)

- on external Pulses Per Second (PPS)
RTC buffer in case of power supply failure for > 12 hours
Recording rate continuous 100 events per second

bursts < 1 min. 200 events per second
Trip counters non-volatile storage for each command

- commands transmitted up to 65536
- commands received up to 65536
- loop tests transmitted up to 65536
- loop tests received up to 65536
- unblocking condition up to 65536
resetting via HMI570 each single counter selectively or

all counters at once
Storage medium non-volatile memory

23. ELECTROMAGNETIC COMPATIBILITY (EMC)
23.1. Electrical Safety

Meets the safety requirements according to EN / IEC 60950-1: 2006 / AC: 2011 and EN / IEC 62368-1: 2014 / A11: 2017
23.2. Emission
The equipment meets the EMC requirements for emission EN 61000-6-4: 2019
Conducted emission 150 kHz to 30 MHz
EN 55022 / EN 55032 Class A
LF disturbance emission (48 VDC) 0 kHz to 4 kHz
CCITT P.53 < 3 mV (psophometrically weighted)
Radiated emission 30 MHz to 1000 MHz
EN 55022 / EN 55032 Class A
23.3. Immunity
The equipment meets the EMC requirements for immunity EN 61000-6-2: 2005 and EN 61000-6-5: 2015
Radiated electromagnetic field 80 MHz to 1000 MHz, 80% AM, 1 kHz repetition rate
IEC 61000-4-3 10 V/m
IEEE 1613 / IEEE C37.90.2 20 V/m
Radiated electromagnetic field 1.0 GHz to 3.0 GHz, 80% AM, 1 kHz repetition rate
IEC 61000-4-3 10 V/m
Power frequency magnetic field 50 Hz
IEC 61000-4-8 30 A/m (continuous), 300 A/m (3 seconds)
Electrostatic discharge (ESD) contact air discharge
IEC 61000-4-2 8 kV 15 kV
IEEE 1613 / IEEE C37.90.3 8 kV 15 kV
Fast transient Surge immunity Conducted RF Damped Conducted CM
burst 1) test interference 2) oscillatory waves 3) disturbance 4)
IEC 61000-4-4 IEC 61000-4-5 IEC 61000-4-6 IEC 61000-4-18 IEC 61000-4-16
Power Supply
DC supply input ≤ 60 VDC ± 4 kV ± 2 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
± 1 kV DM ± 1.25 kV DM
DC supply input > 60 VDC ± 4 kV ± 4 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
± 2 kV DM ± 1.25 kV DM
AC supply input ± 4 kV ± 4 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
± 2 kV DM ± 1.25 kV DM
Analog Line Interface
2/4-wire ± 2 kV ± 1 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
Boost output ± 2 kV ± 2 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
± 1 kV DM ± 1.25 kV DM
Digital Line Interface
RS-422/RS-530 ± 2 kV ± 1.0 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
1.5 kV CM 5)
G.703.1 ± 2 kV ± 1.0 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
1.5 kV CM 5)
E1/T1 ± 2 kV ± 1.0 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
1.5 kV CM 5)
Ethernet Line Interface and
GOOSE LAN Interface
Ethernet ± 2 kV ± 1.0 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
1.5 kV CM 5
Relay Interface
Command Input ± 4 kV ± 4 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
± 2 kV DM ± 1.25 kV DM
Solid-state Output ± 4 kV ± 4 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
± 2 kV DM ± 1.25 kV DM
Relay Output ± 4 kV ± 4 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
± 2 kV DM ± 1.25 kV DM
Common Interface
Alarm Relay Output ± 4 kV ± 4 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
± 2 kV DM ± 1.25 kV DM
RS-485 Station Bus ± 2 kV ± 1.0 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
1.5 kV CM 5)
IRIG-B Input ± 2 kV ± 1 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
GPS Sync. Input ± 2 kV ± 1 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
RS-232 Serial Interface ± 2 kV ± 1 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V


1.5 kV CM 5
LAN Interface (G3LL)
1.5 kV CM 5
RS-485 Station Bus ± 2 kV ± 1.0 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V
1.5 kV CM 5)
1) 4)
5/50 ns, 5 kHz repetition rate Continuous mode, frequency 50 Hz
2)
150 kHz to 80 MHz, AM 1 kHz / 80% 5)
Waveform 10/700 s
3)
1 MHz, 400 Hz repetition rate, 2 s burst duration
23.4. Insulation
Power Impulse Insulation
frequency Voltage resistance
withstand test (@ 500 VDC)
IEC 60255-5 / IEC 60255-5 / IEC 60255-5 /
IEC 60255-27 IEC 60255-27 IEC 60255-27
Power Supply
DC supply input ≤ 60VDC 1.0 kV ± 5 kV  100 M
DC supply input > 60VDC 2.5 kV ± 5 kV  100 M
AC supply input 2.5 kV ± 5 kV  100 M
Analog Line Interface
2/4-wire 1.0 kV ± 1 kV  100 M
Boost output 1.0 kV ± 1 kV  100 M
Digital Line Interface
RS-422/RS-530 1.0 kV ± 1 kV  100 M
G.703.1 1.0 kV ± 1 kV  100 M
E1/T1 1.0 kV ± 1 kV  100 M
Ethernet Line Interface and
GOOSE LAN Interface
Ethernet 1.0 kV ± 1 kV  100 M
Relay Interface
Command Input 2.5 kV ± 5 kV  100 M
Solid-state Output 2.5 kV ± 5 kV  100 M
Relay Output 2.5 kV ± 5 kV  100 M
Common Interface
Alarm Relay Output 2.5 kV ± 5 kV  100 M
RS-485 Station Bus 1.0 kV ± 1 kV  100 M
IRIG-B Input 500 V ± 1 kV  100 M
GPS Sync. Input 500 V ± 1 kV  100 M
RS-232 Serial Interface 500 V ± 1 kV  100 M
LAN Interface (G3LL)
RS-485 Station Bus 1.0 kV ± 1 kV  100 M
24. MECHANICAL DATA, DIMENSIONS AND WEIGHTS
Height 3 units high = 133.35 mm (1 unit = 44.45 mm)

4 units high = 177.8 mm (including cable tray at the back side and cover
plate with labeling strip at the front side)
Overall depth 300 mm
Installation width 482.6 mm (19'')
Material side panels, cover plates hot-dip galvanized sheet

horizontal rails extruded aluminum section
Color RAL 7035 / Pantone 420 (light grey)
IP protection degree of protection IP20 (according to EN 60529 / IEC 60529)
Equipment rack 19" wide conforming to standard DIN 41494
Dimension of modules (H x W x D) power supply unit 3U / 8HP / 220 mm

line and relay interfaces 3U / 6HP / 220 mm
LAN & GOOSE interfaces 3U / 6HP / 220 mm

No. of slots power supply unit 2

line interfaces 2
relay & GOOSE interfaces 8
Weight basic version (rack, one supply module, one line interface, one relay interface):
basic version Analog (2 commands) 5.66 kg

basic version Digital (2 commands) 5.58 kg
basic version Ethernet (2 commands) 5.61 kg
per additional supply module G3LH 0.60 kg

per additional supply module G3LI 0.54 kg
per additional supply module G3LK 0.52 kg
per additional analog interface G3LA 0.26 kg
per additional digital interface G3LD 0.18 kg
per additional Ethernet interface G3LE 0.21 kg
per additional relay interface G3LR/G3LRa 0.22 kg
per additional GOOSE LAN interface G3LS 0.21 kg
optional LAN interface G3LL 0.32 kg
optional LAN management interface G3LM/G3LMa 0.21 kg
optional E1/T1 interface G1LE 0.04 kg
optional optical interface G1LO 0.10 kg
optional optical interface G1LOa (incl. SFP) 0.08 kg
optional display panel G1LC 0.15 kg
optional input tripping voltage G1LR 0.02 kg
optional SFP transceiver for G3LE/G3LM/G3LS 0.02 kg
Traceability all modules labeled with barcode module type and serial number
Installation cabinet with hinged frame (typical) conforming to standard IEC 60297-3
or in an open frame
installation in a cubicle without hinged frame installation set available upon request
Removal of boards power supply module(s) from the front side

line and relay interfaces from the back side
EMC shielding front integrated in front panel (Ground layers)

back screening and protection cover
External connections by means of wires connected directly to spring-clamp terminals at the back of the equipment, or
by means of connecting cables with special terminations (terminal blocks with isolating blades),
cable length of optional connecting cables: 2500 mm
Wiring type of connecting terminals/sockets spring cage / RJ45 / Sub-D

directly to the modules G3LA, G3LC, G3LR 0.2 - 2.5 mm2 for solid and stranded wire
(AWG 24 - 12)
directly to the module G1LB 0.14 - 1.5 mm2 for solid and stranded wire
(AWG 28 - 16)
directly to module G3LD via RJ45/Sub-D refer to paragraph 8
directly to module G3LE via RJ45 refer to paragraph 9
directly to module G3LL via RJ45 refer to paragraph 18
directly to module G3LM via RJ45 refer to paragraph 19
directly to module G3LS via RJ45 refer to paragraph 11
to the power supply units via Faston connector 6.3 x 0.8 mm (DIN 46244)
to optional cables with isolating terminals 0.2 - 2.5 mm2 for stranded wire (AWG 24 - 12)
0.2 - 4.0 mm2 for solid wire (AWG 24 - 11)
to optional cables with Sub-D sockets refer to paragraph 8
to optional cables with RJ45 press-fit terminals 0.5 - 0.65 mm diameter (AWG 24 - 22) solid wire
shield earthing at the rear cable tray below the equipment
ESD earthing (for service & maintenance) snap fastener 4.5 mm at the rear cable tray,
(EBP - Earth Bonding Point) for connecting an ESD wrist bracelet

25. AMBIENT CONDITIONS
The ambient conditions stated under „operation“ are valid for an altitude of up to 2000 meters above sea level (according to
EN/IEC 60950-1). If NSD570 shall be operated above this level, certain restrictions apply to the maximum voltage for the command
inputs/outputs and the maximum voltage for the alarm relays (please contact Hitachi ABB in this case).
25.1. Operation
Climatic conditions Complies with IEC 60721-3-3 Class 3K5
Within specification Temperature range -5 to + 55 °C
Relative humidity (non condensing)  95%, < 28 g/m3
Operational -20 to + 55 °C
Mechanical conditions Complies with IEC 60721-3-3 Class 3M1
Vibration sinusoidal Complies with IEC 60068-2-6
Shock Complies with IEC 60068-2-27
25.2. Transport
Temperature range -40 to +70 °C
Mechanical conditions Complies with IEC 60721-3-2 Class 2M1
Vibration sinusoidal Complies with IEC 60068-2-6
Shock Complies with IEC 60068-2-27
Free fall Complies with IEC 60068-2-32

(0.25 m/equipment packed)
25.3. Storage
Temperature range -40 to + 70 °C
Mechanical conditions Complies with IEC 60721-3-1, Class 1M1
All technical data are subject to change without notice.
Grid Automation
Bruggerstrasse 72
CH-5400 Baden, Switzerland
Phone: Please refer to https://www.hitachi-powergrids.com/contact-us/Customer-Connect-Center

(Customer Connect Center)
E-Mail: communication.networks@hitachi-powergrids.com
Internet: www.hitachi-powergrids.com/communication-networks


ABB Power Grids Switzerland Ltd 1KHW000894
Archive No.: Rev. Date:
Software Installation Description: < HMI570 > - J 2021-08-04
Responsible Department: Prepared: Approved: Distribution: Lang.: Page:
PGGA-PT1 07-08-28 sig. Wettstein 2021-08-04 sig. Strittmatter - EN 1/4
Valid for: Derived from: Replaces: Classification-No.: File:
- - - - 1KHW000894JE Software
Installation HMI570.doc
Teleprotection Equipment: NSD570
Software Installation Description: < HMI570 >
Contents:
1 Purpose of document 1
2 HMI570 Installation on Microsoft® Windows 1
2.1 System requirements 1
2.2 Installation of the HMI570 2
2.3 Installation notes for HMI570 version 1.49 and higher 2
2.4 Installation notes for HMI570 version 1.40 and higher 2
2.5 Installation notes for older HMI570 versions 3
2.6 Uninstall 4
2.7 Updates 4
List of equipment:
PC with Windows 7 or 8 or 10
HMI570 Installation CD
 Note: Please refer 1KHW000902 for compatibility between software HMI570,

firmware and hardware of NSD570.
1 Purpose of document
This document describes the software installation process for the HMI570.
2 HMI570 Installation on Microsoft® Windows
2.1 System requirements
The minimum requirements for installing and running the HMI570 are as follows:
1. x86 compatible Processor (AMD Athlon / Duron or Intel Pentium), 1 GHz or higher
2. 512 MB of RAM
3. SVGA Controller with min. 1024 x 768 resolution and 256 colors
4. 200 MB of free disk space or at least 1 GB in case of the IEC 61850 enabled HMI570
5. CD ROM drive
6. Microsoft® Windows Vista, 7 or 8 or 10
7. Web-browser supporting HTTP/1.1 and HTML 4 (Microsoft® Edge is recommended)
8. 1 free serial port (RS-232 or USB with external RS-232-to-USB converter)
ABB is a registered trademark of ABB Asea Brown Boveri Ltd. Manufactured by/for a Hitachi Power Grids company.
Revision: Language: Page:
J EN 2/4 1KHW000894
2.2 Installation of the HMI570

An Installation Package is provided for Microsoft® Windows 7, 8 and 10.
1. Make sure you have administrator rights on the PC/notebook.

2. Make sure that your Windows user account, as well as the folder where HMI570 is
installed to, does not contain any special characters like &, !, *, #, $, etc.
3. Insert the HMI570 CD into the CD-ROM drive.
4. Double-click on the “HMI570-install.exe” to start the installation.
5. Follow the wizard
 Note: Microsoft® no longer provides support for Windows XP (since April 2014).
However, if HMI570 version 1.40 or higher shall be operated under Windows
XP (not recommended), service pack 3 is required for full IEC 61850 support.
2.3 Installation notes for HMI570 version 1.49 and higher

Up to version 1.48, HMI570 forced the Internet Explorer from Microsoft® to be opened. However, it
was possible to use an alternative web browser, as for example Mozilla Firefox, by manually
adapting the files bin\startBrowser.bat and bin\startBrowserInit.bat in the HMI570 program folder.
Beginning with version 1.49, the default browser installed on the computer is opened by HMI570, or
a new tab is opened if the browser is already running.
HMI570 version 1.49 was optimized for the display of the different user interface pages under
modern web browsers like Microsoft® Edge and Google Chrome. Previous versions were
correspondingly optimized for the browser Internet Explorer from Microsoft®. If the default browser
on the computer is Internet Explorer, HMI570 version 1.49 will also make use of this type.
The HMI570 Server version 1.49 will no longer shutdown by default when the last browser tab is
closed. However, the previous behavior can still be enabled:
Right-click on the HMI570 Server Icon in the System Tray. Select “Settings” from the pop-up menu
and then click on "Shut Down Server Automatically".
2.4 Installation notes for HMI570 version 1.40 and higher

HMI570 versions from 1.40 onwards support two installation modes.
Installation with support for SCL file handling

This version provides support for IEC 61850 configuration file management as used in connection
with the G3LS GOOSE LAN interface. If G3LS is not expected to become a part of the substation
setup, this installation mode of HMI570 is not needed.
Installation without support for SCL file handling

This version of HMI570 is smaller and does not depend on the .NET framework. It supports only
the download of completely engineered ICZ files to a G3LS device and the upload of ICZ files from
a G3LS device. The generation of an IEC 61850 configuration for G3LS is not supported.
J EN 3/4 1KHW000894
2.5 Installation notes for older HMI570 versions
Applicable only for HMI570 V1.21, V1.30 and V1.31 (Microsoft® Windows XP, Vista, 7, 8 and 10):
If the HMI570 is operated by several users on the same PC/notebook, the user accounts have
to share the same "%temp%" folder. This can be achieved by granting the full access to the
administrator’s "%temp%" folder:
1. Log in under the same user account under which HMI570 was installed.
2. Navigate to the user’s temp folder: %TEMP%
3. Open the folder’s Properties dialog and navigate to the “Security” tab.
 Note: If the tab “Security” is not shown in the folder’s Properties, the setting “Use
simple file sharing” must be removed (unchecked) in the “Folder Options…”
menu of the Windows Explorer (File Explorer):
Tools -> Folder Options… -> “View”
4. Add the users which will use HMI570 using “Add…” button.
5. Assign full control to the folder for each user added in the previous step.
Applicable only for HMI570 V1.14 and lower (Microsoft® Windows XP):
Full access to the HMI570 program folder must be granted for each user in case he has no
administrator rights on the PC. This can be achieved by executing the following steps:
1. Navigate to the folder where HMI570 was installed. By default it is installed into
%PROGRAMFILES%\ABB\HMI570 1.14
2. Open the folder’s Properties dialog and navigate to the “Security” tab.
 Note: If the tab “Security” is not shown in the folder’s Properties, the setting “Use
simple file sharing” must be removed (unchecked) in the “Folder Options…”
menu of the Windows Explorer (File Explorer):
Tools -> Folder Options… -> “View”
3. Add the users which will use HMI570 using “Add…” button.
4. Assign full control to the folder for each user added in the previous step.
J EN 4/4 1KHW000894
2.6 Uninstall
Start → Settings → Control Panel → Add/Remove Software
Choose HMI570 and click on „Add/Remove“
All the files and folders, that were installed, are removed from your system.
2.7 Updates
1. If the current version of HMI570 is 1.14 or higher, export the current HMI570 settings to your
local disk
Start HMI570 → Log In → enter username & password → HMI570 Settings → Export Settings
 Note: It is not possible to export the HMI570 settings of the HMI570 version 1.13 or
lower. In this case the new HMI570 has to be configured again in the same
way after the reinstallation.
2. Uninstall the old version of the HMI570

Start → Settings → Control Panel → Add/Remove Software
Choose HMI570 and click on „Add/Remove“
3. Install the new version of the HMI570
4. Import the previously saved HMI570 settings from step 1
Start HMI570 → Log In → enter username & password → HMI570 Settings → Import Settings
 Note: It is possible to install different versions of the HMI570 on the same PC /

notebook. Every version must be installed in a separate directory and must be
given a different shortcut name.
 Note: It is not possible to run different versions of the HMI570 on the same PC /
notebook simultaneously.
ABB Power Grids Switzerland Ltd 1KHW000896-EN
Firmware Download Description: < NSD570 > - I 2021-08-04
PGGA-PT1 2002-10-02 sig. Schnyder 2021-08-04 sig. Strittmatter - EN 1/4
- - - - 1KHW000896IE Firmware
Download for NSD570.doc
Firmware Download Description: < NSD570 >
Contents:
2 General 2
2.1 Necessity for a firmware download 2
2.2 Risks of a firmware download 2
2.3 Firmware download files 3
3 Firmware download 3
4 Troubleshooting 4
List of equipment:
HMI570 (Version 1.49 or higher)
Firmware download files
PC  NSD570 (1:1 serial RS-232) cable
 Note: Please refer 1KHW000902 for compatibility between software HMI570,

firmware and hardware of NSD570.
I EN 2/4 1KHW000896-EN
This document describes the firmware download process for the teleprotection equipment NSD570,
supported by the user interface program HMI570.
2 General
The HMI570 user interface program supports firmware download for the modules G3LA, G3LD,
G3LE, G3LM and G3LS.
The firmware download gives the opportunity to update the equipment to the latest release or to
modify a module ordered from stock to the actual release in the existing equipment.
2.1 Necessity for a firmware download
The firmware download has to be used in the following cases:

1. Update already configured equipment with the newest available firmware versions.
Typically, this might become necessary when firmware versions are available with new
functionality.
2. Modify equipment if the configuration download (with HMI570) detects an incompatibility.
Possible situations are if a configuration is downloaded to virgin equipment or the HMI570 has
extended functionality, which is not available on the firmware in the equipment.
2.2 Risks of a firmware download
The firmware download procedure should be performed exclusively by instructed service

personnel. The operator is not allowed to perform this operation.
Caution ACTIVATING A FIRMWARE DOWNLOAD WILL CAUSE MALFUNCTION

OF THE TELEPROTECTION-LINK.
If the protective system is already in use, open the connections to it in the
local and in the remote station. Install the firmware in both stations and re-
commission the link according the document “Commissioning Instructions
NSD570” before the connections to the protection devices are closed again.
Caution NEVER SWITCH OFF THE POWER TO THE EQUIPMENT WHILE A

FIRMWARE DOWNLOAD IS IN PROGRESS.
Violation of this rule will produce a system with incomplete firmware, so that it
will not work anymore. If this should happen, a new firmware download has to
be executed.
Caution Should the communication to the equipment be interrupted during the

download process, correct the communication problem WITHOUT switching
off the power to the equipment and restart the firmware download.
Caution Keep your hands away from keyboard and mouse while a firmware download
is in progress.
I EN 3/4 1KHW000896-EN
2.3 Firmware download files

To perform a firmware download of the system, the firmware files (*.ldr) are needed. These files are
either supplied together with the HMI570 software or separately in case of updates. If supplied with
the “NSD570 Software and Documentation CD”, the files are stored in the release directory.
Release directories can be found in the directory 'Firmware'. Make sure that the latest version of
the firmware is used to update the equipment.
Hardware module Firmware file Example

G3LA NSD570_Analog_Vx_yz.ldr NSD570_Analog_V1_18.ldr
G3LD NSD570_Digital_Vx_yz.ldr NSD570_Digital_V1_50.ldr
G3LE NSD570_Ethernet_Vx_yz.ldr NSD570_Ethernet_V3_43.ldr
G3LM NSD570_Management_Vx_yz.ldr NSD570_Management_V1_19.ldr
G3LS NSD570_GOOSE_Vx_yz.ldr NSD570_GOOSE_V1_08.ldr
Caution Never edit a firmware download file (*.ldr)
Caution Never download a firmware file to a module that is not destined for,
e.g. never download the file NSD570_Digital_V1_50.ldr to a G3LA module.
3 Firmware download
 Note: It is recommended to use the newest version of the HMI570, but in any case
the HMI570 must belong to the same release as the firmware to be down-
loaded (please refer to document „Compatibility Requirements NSD570”).
Caution If a device that shall be a target for the firmware download is already
configured, it is necessary to upload the configuration from the device and
store it to the hard disk of the PC before firmware download.
1. Start the HMI570

2. Log in as User with modify permission
3. Connect the device that shall be the target for the firmware download
4. If the configuration of the device shall remain the same after the firmware download, upload it
and store it on the PC. This allows the HMI570 to convert the old configuration version to the
new version, matching the new firmware.
5. Click Maintenance --> Firmware Download
6. Click the Browse button and a file selector window appears.
7. Select the firmware file and click the Open button.
8. Click the Download button.
9. The firmware download will now take some minutes to complete.
Keep your hands away from keyboard and mouse while the download is in progress.
10. The following message informs about the success of the firmware download.
11. To activate the new firmware, the device must be reset
Click Maintenance --> Reset Device
This step is obsolete for HMI570 version 1.13 or higher. The reset of the device and its
disconnection will be done automatically.
I EN 4/4 1KHW000896-EN
12. If the device shows the alarm “Begin Configuration error” after re-booting, connect again to the
same device and download the previously saved configuration from step 4 to the device
without any changes. With this procedure HMI570 converts the old configuration version
to the new version which is compatible to the newly installed firmware.
4 Troubleshooting
If a firmware download was not successful, e.g. caused by a power off situation during the down-
load, it is - in most cases - possible to “revitalize” the module by another firmware download.
A few basic principles have to be taken into account for the module concerned:
• It can be accessed neither with its configured device address nor with the default addresses
(241 or 246 for the line interfaces G3LA/D/E, 242 or 247 for the GOOSE interfaces G3LS, 250
for Management interface G3LM). For the line interfaces G3LA/D/E, use the device address
255 instead (at first, the other line interface, the GOOSE interface(s) and the Management
interface G3LM in the same rack have to be unplugged and the connection to the RS-485
station bus has to be removed).
• After power up the equipment rack again it can take up to 25 minutes until a connection to the
device by means of HMI570 is possible.
• Should the communication to the equipment be interrupted during the download process (e.g.
a crashed PC, an unplugged RS-232 cable or everything else except a power off situation),
correct the communication problem WITHOUT switching off the power supply and WITHOUT
executing a reset of the device, simply restart the firmware download. If the power supply is
switched off or the device is reset, it will be necessary to wait up to 15 minutes and to use the
address 255 for connecting the line interface.
Programming and Testing Instructions: < NSD570 > - M 2021-08-04
PGGA-PT1 2002-09-04 sig. Strittmatter 2021-08-04 sig. M. Buhl - EN 1/41
- - - - 1KHW000898ME Programming
and Testing of NSD570.doc
Teleprotection Equipment: Series NSD570
Programming and Testing Instructions: < NSD570 >
This document describes programming and testing of the teleprotection equipment NSD570 Analog, NSD570
Digital (including the optical interface for the NSD570 Digital) and NSD570 Ethernet.
Contents:
A Programming Instructions for the NSD570 Equipment ................................ 3

A.1 General......................................................................................................... 3
A.2 Create a configuration for the equipment using the HMI570 ....................... 3
A.3 Check interfaces in the rack G7BI ............................................................... 3
A.4 Common settings for all types of equipment NSD570
Analog/Digital/Ethernet ................................................................................ 4
A.5 Settings for the analog line interface............................................................ 6
A.6 Settings for the digital line interface ............................................................. 8
A.7 Settings for the Ethernet line interface ....................................................... 11
A.8 Settings for the individual commands ........................................................ 12
A.9 Settings for the relay interface(s) G3LR..................................................... 14
A.10 Settings for the GOOSE LAN interface G3LS............................................ 16
A.11 Alarm settings ............................................................................................ 17
A.12 Display Panel ............................................................................................. 18
A.13 Management LAN Interface ....................................................................... 18
B Testing Instructions for the NSD570 Equipment. ....................................... 19
B.1 General....................................................................................................... 19
B.2 Check power supply ................................................................................... 19
B.3 Preparing the equipment ............................................................................ 20
B.4 Change configuration ................................................................................. 21
B.5 Remarks for T-operation ............................................................................ 22
B.6 Configure Real Time Clock (RTC) ............................................................. 22
B.7 Analog line interface................................................................................... 23
B.8 Digital line interface .................................................................................... 24
B.9 Ethernet line interface ................................................................................ 25
B.10 1+1 Device operation mode ....................................................................... 26
B.11 GOOSE LAN interface G3LS ..................................................................... 26
B.12 Relay interfaces G3LR ............................................................................... 27
B.13 System alarm indication ............................................................................. 28
B.14 System functions ........................................................................................ 28
B.15 Display Panel ............................................................................................. 29
B.16 LAN Interface ............................................................................................. 29
B.17 Concluding works ....................................................................................... 30
NSD570 System Settings................................................................... A1 - A9
NSD570 System Test Report ..................... Refer to document 1KHD608525
M EN 2/41 1KHW000898-EN
Basic test equipment

Software HMI570 (user interface program)
PC  COM 1 cable (1:1 serial RS-232) One male, one female plug Sub-D, 9 pin
Digital multimeter ABB Metrawatt M2012 or equivalent
Level meter General purpose (True RMS or selective)
Power supply unit 0...100 VDC General purpose
Oscilloscope bandwidth  1 MHz Tektronix 2235 or equivalent
Optional test equipment

Level transmitter PS-33 (Acterna) or equivalent
Selective level meter SPM-32 (Acterna) or equivalent
Storage oscilloscope Fs  1 Ms/s Tektronix 2430A or equivalent
Test box for teleprotection equipment MK11 or equivalent
Optical power meter 850 / 1310 / 1550 nm WWG OLP-16C or equivalent
Optical attenuator ANDO AQ3150 or equivalent
Notes:

• This document is part of the Operating Instructions NSD570 (1KHW000890).
• Please refer to document "Compatibility Requirements for NSD570" (1KHW000902) for
compatibility between software HMI570, firmware "Analog", firmware "Digital", firmware
“Ethernet”, firmware “GOOSE”, firmware “Management” and hardware of NSD570.
Designations and abbreviations used:
Designation Meaning
( ..… ) Measured value

[ ..… ] Programmed value
[ ]D Preferred setting (default)
[X ] Test passed or jumper is set
[ ] Not tested or jumper is not set
G3LR Module type
RTC Real Time Clock
LED Light Emitting Diode found on the front panel
HMI570 User Interface for NSD570 running on a PC/notebook
N1, …, N84 Position in rack. Slot number N1, …, N84
Rx Receiver
Tx Transmitter
PC Personal Computer or Notebook Computer
X100, …, X701 Onboard connector of the plug in modules
X1, …, X99 Connector designation of the optional connecting cables
PLC Power Line Carrier equipment (e.g. ETL600 series)
M EN 3/41 1KHW000898-EN
A Programming Instructions for the NSD570 Equipment
A.1 General
Most settings for the line interfaces, the relay interfaces and the command application of the
teleprotection equipment NSD570 are performed with the configuration program HMI570. Typically,
these data are configured off-line and stored as a file on a disk. All these settings are loaded from a
file and downloaded to the equipment. A few settings have to be done by means of jumper plugs,
e.g. the impedance of the analog line interface. These settings can be entered in the configuration
data file as well and downloaded to the equipment by the HMI570 (for information purpose only,
e.g. for remote read out).
One or two NSD570 systems can be accommodated in the rack. They can be of the same type or
even a mix of analog, digital or Ethernet system in the same rack is possible. Access to both
systems is possible via the serial COM 1 interface on the front panel of the rack G7BI (using the
HMI570 and the device address number for connection to the equipment). The programming
instructions as well as the testing instructions cover all possible rack configurations.
Follow systematically, step-by-step this instruction and the equipment will work properly!
A.2 Create a configuration for the equipment using the HMI570

To configure a system from scratch, the HMI570 software has to be installed on the PC/notebook
first (see document "HMI570 Software Installation Description" 1KHW000894). After starting the
HMI570, a default configuration file for the analog, for the digital or for the Ethernet version can be
loaded for easy adaptation to the application needs of the system. This can be done "off-line" (i.e.
without connection to the system) and even without performing a "login" to the HMI570. The
modified configuration file can be saved afterwards to the local disk or be downloaded to the
equipment (after performing a "login" and a "connect" to the designated system).
It is also possible to load and modify a pre-configured file, which is saved in your local file system.
If the equipment was already configured earlier, the configuration can also be uploaded, modified,
saved to disk or downloaded again (after changing the desired settings).
For more detailed information about the configuration procedure with the help of HMI570 please
refer to the Operating Instructions NSD570, 1KHW000890, section 5, "Configuration and settings".
A.3 Check interfaces in the rack G7BI

Most of the modules (including hardware releases) of the rack assembly are auto-detected by the
NSD570 system and can be viewed after connecting to the equipment and uploading the configu-
ration.
For information purposes, the complete rack assembly may also be entered and stored in the
configuration data (e.g. for remote read out).
A.3.1 Check position of interfaces

If the configuration was done "off-line", check if all required interfaces are present and inserted at
the correct position in the module rack (as given in the HMI570 configuration pages), before down-
loading the new configuration to the system.
If desired, complete the rack assembly in the configuration data, save it to disk and download it to
the equipment. The rack assembly data can be entered in the device configuration by clicking on
the Rack Assembly link in the configuration menu and choosing the module and piggyback type
from a pull down menu for each slot in the rack.
A.3.2 Check presence of cover plates

The front of the rack must be covered completely. Check that a blanking cover plate or the optional
Display Panel type G1LC is present on the left hand side (width x height = 94 x 128 mm).
Check, if the screening cover at the rear of the rack is present (width x height = 430 x 130 mm;
covering all the modules and the external connections to the modules).
M EN 4/41 1KHW000898-EN
A.4 Common settings for all types of equipment NSD570 Analog/Digital/Ethernet
A.4.1 Power supply

If the equipment is mounted in a cabinet, check that the following circuit breakers (or equivalent)
are installed:
48 / 60 VDC, 100 - 240 VAC Circuit breaker B9AS (1KHL015141R0001, type S202P-K 6A)
72 - 250 VDC Circuit breaker B9AV (1KHL015999R0001, type S282UC-K 6A)
Caution Before powering the module rack for the first time, check the wiring of
protective earth and power supply polarity. Also check the voltage source for
the power supply.
A.4.2 Device identification

The following information can be entered and saved into the configuration data (to identify the
equipment in the rack):
Station Name: A name consisting of 20 characters can be entered (e.g. to designate the
substation)
HE Number: The module rack type G7BI is usually marked with a unique HE number ex
works. This 6-digit number (or any other text with 20 characters max.) can be
entered.
Device Address: The address of the device may be chosen out of the range 1 … 240. After the
initial configuration, a connection to the NSD570 is later on established using
this device address. If two NSD570 are equipped in the same rack, different
addresses have to be selected. The same applies if several NSD570 module
racks are locally interconnected via the RS-485 station bus. In this network
different addresses have to be used for each NSD570.
A.4.3 Operating mode of the equipment

The NSD570 Analog/Digital/Ethernet can be configured for the following operating modes:
"Normal" Standard type for point-to-point connection via any transmission media (default)
"1+1" Line interface redundancy to protect against equipment and communication path
failures
"T-Operation"
(Teed) Protection of power lines with teed feeders (having single or multiple tee-offs).
This mode is not supported by the G3LS GOOSE LAN interface.
"Inverse
T-Operation" For power lines with one or several teed terminals protected by a permissive
(Inv Teed) overreach transfer tripping scheme.
This mode is not supported by the G3LS GOOSE LAN interface.
Caution For setting up an 1+1 link it has to be adhered to the following configuration
sequence in order to avoid erroneous behavior of the equipment:
- Connect to the Stand-by Line Interface in TPE 2, configure it for normal operation mode and
disable all Relay Interfaces at first
- Connect to the Main Line Interface in TPE 1, configure it for 1+1 operation mode and enable the
required Relay Interfaces in TPE 1, according to the application
- Connect again to the Stand-by Line Interface in TPE2, configure it for 1+1 operation mode and
enable the required Relay Interfaces in TPE 1, according to the application
A.4.4 Unblocking
An „unblocking“ command used in directional comparison or in permissive tripping schemes with
overreaching first zone can be allocated to one or more outputs on the relay interface module. Note
M EN 5/41 1KHW000898-EN
that „unblocking“ commands are not transmitted from the remote end, but automatically produced
by certain types of line faults (PLC channels).
Should the communication channel be almost completely lost, i.e. when the NSD570 is receiving
neither guard nor tripping signals and the unblocking threshold is exceeded, the unblocking
contacts close for a predefined time. After detection of the unblocking condition the release of this
pulse can be delayed (filtered) for a certain time whilst the channel may recover.
Unblocking Extra Delay configurable from 0 ... 100 ms in steps of 1 ms;
default NSD570 Analog/Digital: 10 ms
Unblocking Pulse Duration configurable from 50 … 500 ms in steps of 1 ms;
default: 200 ms
A.4.5 Command outputs during link failure

It can be programmed how the command outputs respond to a channel failure, for example to SNR
alarm or Rx level alarm in case of NSD570 Analog, to BER alarm or AIS/LOS received in case of
NSD570 Digital and to LOS received or two consecutive guard packets lost in case of NSD570
Ethernet:
- are unaffected (state according to trip signal evaluation)
The command outputs continue to correspond to the current status of tripping signal processing,
i.e. they do not respond at all to the alarm. (default)
- are set to guard state (blocked)
The command outputs are set to their quiescent states (= no tripping signal).
- retain in state prior to link failure (frozen)
The command outputs retain the statuses they had immediately prior to the alarm detection.
- direct to guard state, others to command state
The command outputs configured for direct tripping are set to guard state and the command
outputs configured for permissive tripping or blocking are set to their tripped states.
The response of the command outputs becomes effective after an internal alarm processing time
from the instant the alarm condition arises and remains so throughout the alarm condition and for a
further processing time of the same quantity after it disappears. The alarm-condition pick-up time
and the hold time for the command outputs can be further delayed:
Link failure pick up time configurable from 0 … 15 sec in steps of 1 sec
default: 10 sec (except for “frozen” -> 0 sec)
Link failure hold time configurable from 0 … 15 sec in steps of 1 sec
default: 0 sec
A.4.6 Synchronization of internal Real Time Clock (RTC)

The timing information for the system and especially for the event recorder is provided by the built-
in real time clock (RTC). The date and time of this RTC is set via the HMI570. If the accuracy of
this time setting procedure is not sufficient and an external time source is available (e.g. a GPS
receiver or an NTP/SNTP master), the RTC can be synchronized using an external sync pulse
(every second) which is automatically detected by the line interfaces, and/or using an external
IRIG-B synchronization signal (e.g. derived from the SNTP client operated on G3LMa, by
connecting the IRIG-B output of G3LMa with a dedicated cable to the IRIG-B input of NSD570).
External Synchronization Signal (IRIG-B) configurable to off (default) or on
A.4.7 Embedded Operation Channel (EOC)

For certain equipment operating modes, an EOC may be encoded into the channel used for
transmitting guard, command and test signals (without needing additional bandwidth).
Embedded Operation Channel (EOC) Configurable to off or on (default)
A.4.8 Cyclic Loop Test Interval

An cyclic loop test sequentially checks the integrity of the teleprotection channel. The test signal
simulates the transmission of a genuine tripping signal and is recognized as such at the receiving
end, from whence it is echoed back to the transmitter.
Cyclic Loop Test Interval Configurable to off / 1 h / 3 h / 6 h (default) / 12 h / 24 h
M EN 6/41 1KHW000898-EN
A.4.9 Propagation Time

A valid manual or cyclic loop test must be received within a definite time slot. Additional
propagation delay of the communication channel (e.g. radio link, multiplexer) can be taken into
account with the parameter “Propagation Time” by means of corresponding HMI570 setting. This
parameter must be set to the one way propagation time of the communication channel.
Propagation Time Configurable 0 … 200 ms in steps of 1 ms (default = 0 ms)
A.5 Settings for the analog line interface
A.5.1 Barrier transformers

If the equipment is connected to cables, pilot wires or leased circuits, check that the following
barrier transformers are installed:
This apparatus must only be used in conjunction with barrier transformers
Caution withstanding a test voltage of 15 kVrms or 20 kVrms at 50 Hz / 60 Hz for
1 minute, according to national regulations or to electric utilities' practice.
A.5.2 Connection to the AF communication circuits

Operation of the NSD570 Analog is possible over 2-wire and 4-wire voice frequency communi-
cation circuits. 4-wire operation is recommended. For 2-wire operation the transmitter and receiver
must have separate frequency bands (not overlapping) and the Tx impedance has to be
programmed to "high impedance" (refer to A.5.9). Further constraints for 2-wire operation e.g. level
settings and admissible line attenuation are described in the Operating Instructions NSD570.
A.5.3 Analog channel bandwidth

The Tx and the Rx bandwidth can be set individually.
The usable frequency range is from 300…3960 Hz.
Tx bandwidth configurable to 120 / 240 / 360 / 480 (default) / 960 / 1200 / 2400 / 2800 Hz
Rx bandwidth configurable to 120 / 240 / 360 / 480 (default) / 960 / 1200 / 2400 / 2800 Hz
A.5.4 Analog channel center frequency

The Tx and the Rx center frequencies can be set individually.
The Tx and Rx center frequencies can be configured from 360 Hz to 3900 Hz in 60 Hz steps.
Default Tx center frequency: 2400 Hz / default Rx center frequency: 2400 Hz
360 Hz 960 Hz 1560 Hz 2160 Hz 2760 Hz 3360 Hz
420 Hz 1020 Hz 1620 Hz 2220 Hz 2820 Hz 3420 Hz
480 Hz 1080 Hz 1680 Hz 2280 Hz 2880 Hz 3480 Hz
540 Hz 1140 Hz 1740 Hz 2340 Hz 2940 Hz 3540 Hz
600 Hz 1200 Hz 1800 Hz 2400 Hz 3000 Hz 3600 Hz
660 Hz 1260 Hz 1860 Hz 2460 Hz 3060 Hz 3660 Hz
720 Hz 1320 Hz 1920 Hz 2520 Hz 3120 Hz 3720 Hz
780 Hz 1380 Hz 1980 Hz 2580 Hz 3180 Hz 3840 Hz
840 Hz 1440 Hz 2040 Hz 2640 Hz 3240 Hz 3900 Hz
900 Hz 1500 Hz 2100 Hz 2700 Hz 3300 Hz
Note: Center frequency ± (0.5 x bandwidth) must be in the range 300…3960 Hz
A.5.5 Analog operating mode

In the guard state, i.e. when there is no command actuated at the inputs, the NSD570 transmits a
single tone guard signal.
In the command state, the NSD570 interrupts the guard signal to transmit the tripping signal, which
can be a single tone signal or a dual tone signal (simultaneously transmitted - each having half the
amplitude of a single tone command), depending on the operating mode.
M EN 7/41 1KHW000898-EN
There are two operating modes with single tone commands and 3 operating modes with dual tone
commands available. All commands and command combinations can be transmitted simulta-
neously and are fully independent from each other.
If a maximum of two commands is required when using the NSD570 over PLC channels, the
operating modes with single tone commands are recommended.
It is further recommended, only to select the number of commands that is really needed (in order to
let the equipment make best possible use of the available bandwidth).
Selectable operating modes:
- 1 single tone command A (configurable for all bandwidths)
- 2 single tone commands A, B, A&B (default; not configurable for 120 Hz bandwidth)
- 2 dual tone commands A, B, A&B (not configurable for 120 Hz bandwidth)
- 3 dual tone commands A, B, C and all combinations of the commands, e.g. B&C
(not configurable for 120 Hz and 240 Hz bandwidth)
- 4 dual tone commands A, B, C, D and all combinations of the commands, e.g. A&C&D
(not configurable for 120 Hz, 240 Hz and 360 Hz bandwidth)
A.5.6 Power boosting

The power of the tripping signal can be boosted and be transmitted at a higher power in relation to
the guard signal. The ratio between the boosted tripping signal and the guard signal is referred to
as boost ratio and expressed in dB. This is recommended for transmission over cables, leased
lines or pilot wires.
When the NSD570 is connected to a PLC equipment, the boost ratio should not be set on the
NSD570, but on the PLC according to how its channels are used and which other signal may be
suppressed during command transmission (in order to release the necessary output power for
boosting the tripping signal). The suppression of these other signals is initiated by the power boost
criterion output on the Analog Interface type G3LA. For further details refer to the Operating
Instructions NSD570.
Power boosting configurable for 0 … 9 dB in steps of 1 dB (default: 0 dB)
A.5.7 Unblocking threshold

Further to the unblocking condition "no guard and no trip signals being received", the total signal
level in the chosen bandwidth must be below a configurable threshold (compared to the guard
signal level) before an unblocking impulse is generated (which can be signaled on one or more
outputs of the relay interfaces).
Unblocking threshold configurable for -20 … -10 dBm0 in steps of 1 dBm0
(default: -14 dBm0)
A.5.8 Signal and alarm levels

Tx signal level:
- single tone guard signal configurable from - 24 dBm … + 2 dBm in steps of 1 dBm
(default: -6 dBm)
This leads to the following levels:
-> single tone command signal - 24 dBm … + 11 dBm (incl. power boosting)
-> dual tone command signals - 27 dBm … + 8 dBm (RMS; incl. power boosting)
Rx signal level (nominal) configurable from - 30 dBm … + 2 dBm in steps of 1 dBm

(default: -6 dBm)
Tx alarm (level drop off) configurable from - 10 dB … -3 dB in steps of 1 dB

(default: -6 dB)
Rx alarm (lower / upper limit) configurable from ± 3 dB … ± 12 dB in steps of 1 dB

(default: ± 6 dB)
M EN 8/41 1KHW000898-EN
A.5.9 Manual jumper settings on G3LA

Tx Impedance matched to line 600 Ohm Jumper TA (default)
high-impedance > 1.5 kOhm Jumper TB
Rx Impedance matched to line 600 Ohm Jumper RA (default)
high-impedance > 1.5 kOhm Jumper RB
Maximum number of devices running parallel over the same circuit: 3 (recommended, for details
refer to the Operating Instructions).
The jumper settings can be entered in the device configuration by clicking on the Jumper Settings
link in the Edit Configuration menu and choosing the appropriate value from a pull down menu.
A.6 Settings for the digital line interface

After clicking on the link Digital Interface in the Edit Configuration menu, a choice has to be
made which interface type shall be used. Click on the edit button and a pull down menu will appear
for selecting the desired digital interface type (G.703 64 kbps codirectional, RS-530, E1 2048 kbps,
T1 1544 kbps, Optical Direct Fiber, Optical OTERM/OPTIF, Optical IEEE C37.94).
After you have chosen the interface type, click on the update button and the entire interface
specific settings will appear on screen. They can be changed by clicking on the edit button again.
Default setting for the interface type is G.703 64 kbps codirectional.
A.6.1 Interface independent settings

BER Alarm Threshold:
If the bit error rate (BER) reaches the pre-defined threshold, alarm is given and dependent actions
are taken (e.g. the command outputs will go to the quiescent state if configured). The BER is
determined in 200 seconds (short term average) and in 262 minutes (long term average).
BER Alarm Threshold (1E…) configurable for 1E-06, 1E-05, 1E-04, 1E-03 (default),
1E-02 and 1E-01
Digital Address:
If the addressing facility is enabled, a digital address is added into the data stream used for
transmitting guard, test and trip messages. The receiver continuously monitors whether the
incoming data stream includes the address of the remote station. If not, the command outputs are
blocked and alarm is given.
This feature is used to protect against channel crossovers in switched or routed networks.
Digital Address Check configurable to off (default) or on
Local Digital Address configurable from 0 … 1023 (default 341)
Remote Digital Address configurable from 0 … 1023 (default 682)
A.6.2 G.703 codirectional interface on G3LD

It may be configured whether the transmitted clock/data signal is synchronized on the internal
64 kHz timing signal only or if the timing information which is reproduced from the received
clock/data signal shall be used to synchronize the transmitted clock/data signal.
G.703 Tx Clock Sync configurable to none or to Rx (default)
A.6.3 RS-530 interface on G3LD

The RS-530 interface data rate can be set to 64 kbps (default) or 56 kbps.
The clock source for both the send data (SD) and the receive data (RD) may be selected. If an
external timing signal is available, the interface can be programmed to synchronize the incoming
and outgoing data on to these signals (ST = Send Timing; RT = Receive Timing). If no external
clock source is available, the internal timing signal can be chosen.
RS-530 Rx Clock configurable to internal (default) or ext. RT
RS-530 Tx Clock configurable to internal (default) or ext. ST
M EN 9/41 1KHW000898-EN
If no external clock source (RT) for the receive data is available, it may be configured whether the
receive data is synchronized on the internal timing signal only or if the timing information which is
reproduced from the received data signal shall be used to synchronize the internal clock of the
receiver.
RS-530 Rx Clock Sync configurable to RD (default) or to none
If no external clock source (ST) for the send data is available, it may be configured whether the
send data is synchronized on the internal timing signal only or if the timing information that is
reproduced from the received data signal shall be used to synchronize the internal clock of the
transmitter. This setting is also valid for the terminal timing (TT) signal, which sometimes has to be
provided from the interface to the communication equipment (e.g. a multiplexer).
RS-530 Tx Clock Sync TT configurable to RD (default) or to none
If no external clock signal is available at all (ST, RT) both, Rx Clock Sync and Tx Clock Sync TT
have to be programmed to either RD or none.
The RS-530 terminal timing (TT) signal can be set to off (default) or to on (if requested from the
application and/or multiplexer).
If two NSD570 with RS-530 interfaces are operated in a point-to-point configuration, one of them
has to be configured as "Master" (the send data SD are synchronized on the internal clock only, i.e.
Rx Clock Sync and Tx Clock Synch TT are both off) and the other as "Slave" (the send data are
synchronized on the timing information which is reproduced from the received data signal, i.e. Rx
Clock Sync and Tx Clock Synch TT are both set to RD). With these settings a clock loop can be
avoided. For the "Master" station, alternatively the terminal timing (TT) signal provided by the
remote station can be used as an external clock reference (wired on the ST inputs).
A.6.4 E1 interface on G1LE

Depending on the distance (cable length) between the E1 interface and the communication
equipment (e.g. a multiplexer), the receiver sensitivity can be programmed for short haul (max.
cable attenuation 10 dB) or long haul (max. cable attenuation 43 dB) application.
Long Haul configurable to off (default = short haul) or on
An internal elastic buffer size can be configured individually for the input and the output circuits.
This buffer may help to compensate clock deviations or clock wander between the internal and the
external timing. Compensation of jitter and detection of slips is also possible by means of a higher
buffer size thus introducing a higher delay. A compromise has to be found in actual tests with the
used communication equipment regarding high jitter capability versus low additional delay.
Rx Buffer configurable to 1 frame, 2 frames (default), 96 bit, bypass
Tx Buffer configurable to 1 frame, 2 frames (default), 96 bit, bypass
The following combinations are not possible:
Rx Buffer = bypass and Tx Buffer = bypass
Rx Buffer = bypass and Tx Buffer = 96 bit
Rx Buffer = 96 bit and Tx Buffer = bypass
Rx Buffer = 96 bit and Tx Buffer = 96 bit
The E1 coding format can be adjusted to the one that is used by the communication equipment.
E1 Coding configurable to HDB3 (default) or AMI
The E1 frame format can be adjusted to the one that is used by the communication equipment.
E1 Frame Format configurable to double frame (default) or CRC4 multiframe
Hardware version 2 of the E1/T1 interface has three jumpers for setting the correct impedance:
120 Ohm for E1 and 100 Ohm for T1. For E1 operation, all 3 jumpers must be set to position E1.
HMI570 versions 1.13 or higher allow entering the position of these jumpers for documentation
purposes.
A.6.5 T1 interface on G1LE

Depending on the distance (cable length) between the T1 interface and the communication
equipment (e.g. a multiplexer), the receiver sensitivity can be programmed for short haul (max.
cable attenuation 10 dB) or long haul (max. cable attenuation 36 dB) application.
M EN 10/41 1KHW000898-EN
An internal elastic buffer size can be configured individually for the input and the output circuits.
This buffer may help to compensate clock deviations or clock wander between the internal and the
external timing. Compensation of jitter and detection of slips is also possible by means of a higher
buffer size thus introducing a higher delay. A compromise has to be found in actual tests with the
used communication equipment regarding high jitter capability versus low additional delay.
Rx Buffer configurable to 1 frame, 2 frames (default), 96 bit, bypass
Tx Buffer configurable to 1 frame, 2 frames (default), 96 bit, bypass
The following combinations are not possible:
Rx Buffer = bypass and Tx Buffer = bypass
Rx Buffer = bypass and Tx Buffer = 96 bit
Rx Buffer = 96 bit and Tx Buffer = bypass
Rx Buffer = 96 bit and Tx Buffer = 96 bit
Rx Buffer = bypass and Tx Buffer = 1 frame
Rx Buffer = bypass and Tx Buffer = 2 frames
Rx Buffer = 1 frame and Tx Buffer = bypass
Rx Buffer = 2 frames and Tx Buffer = bypass
The T1 coding format can be adjusted to the one that is used by the communication equipment.
T1 Coding configurable to B8ZS (default) or AMI
The T1 frame format can be adjusted to the one that is used by the communication equipment.
T1 Frame Format configurable to 4 frames (default) or extended superframe
Hardware version 2 of the E1/T1 interface has three jumpers for setting the correct impedance: 120
Ohm for E1 and 100 Ohm for T1. For T1 operation, all 3 jumpers must be set to position T1.
HMI570 versions 1.13 or higher allow entering the position of these jumpers for documentation
purposes.
For details refer to the Operating Instructions NSD570.
A.6.6 Optical interface G1LO

Depending on the distance (cable length) between the optical interface and the communication
equipment and its optical input saturation power, the laser output power can be programmed for
short haul (< -17 dBm) or long haul (< -1 dBm) application.
G1LO does not support interface type Optical IEEE C37.94. Therefore, this setting shall be
avoided.
A.6.7 Optical interface G1LOa

The Automatic Laser Shutdown (ALS) feature can be enabled or disabled. ALS shall only be
enabled if it is supported by the connected multiplexer equipment as well.
Automatic Laser Shutdown configurable to off (default) or on
If Optical Direct Fiber is selected, it may be configured whether the transmitted optical signal is
synchronized on the internal timing only or if the timing information which is reproduced from the
received optical signal shall be used to synchronize the transmitted optical signal.
Clock Mode configurable to Master (default) or to Slave
If two NSD570 with optical interfaces are operated in a point-to-point configuration, one of them
has to be configured as Master and the other one as Slave. With these settings a clock loop can be
avoided.
A.6.8 Grounding the shield of optional connecting cables

The cable shield of the optional connecting cables for the Digital Interface G3LD, for the Ethernet
WAN Interface G3LE, for the GOOSE LAN Interface G3LS and for the LAN Interface G3LM must
be grounded at the cable tray below the module slots in the back of the rack.
If the connections are made directly to the interfaces, shielded twisted pair cables have to be used
and the customer must properly ground them at the cable tray.
For details refer to the Operating Instructions NSD570.
M EN 11/41 1KHW000898-EN
A.7 Settings for the Ethernet line interface

After clicking on the link Ethernet Interface in the Edit Configuration menu, the interface
configuration appears. For details refer to Section 5 of the Operating Instructions NSD570.
A.7.1 Interface selection

In order to select one of the interfaces, electrical Ethernet X102 or optical SFP X103, the selection
switch between the two interfaces has to be moved towards the required interface. Default = X102.
A.7.2 Interface settings (RJ45 interface only)

Auto negotiation:
The interface is automatically negotiating the transmission speed with the connected equipment
(auto) or can be configured manually (manual = default setting).
Auto negotiation is configurable for manual or auto. If manual is selected the additional menu
items Data Rate [Mbps] and Duplex Mode appear. The data rate can be configured to 10 Mbps
or 100 Mbps (default), the Duplex Mode to Half Duplex or Full Duplex (default).
A.7.3 Ethernet / IP / UDP settings

Ethernet interface settings:
The Ethernet frame can be extended by the IEEE 802.1q VLAN ID and IEEE 802.1p priority
settings. VLAN ID setting makes assigning of a VLAN ID number possible (range: 0 to 4094,
default: 1), whereas the priority setting can mark packets from 0 to 7 (highest priority; default: 5).
VLAN Tagging (802.1Q) is configurable as disabled (default) or enabled. If enabled is
selected, the additional menu items 802.1Q VLAN ID and 802.1Q Priority appear.
IP settings:
The IP configuration requires setting of the Local IP Address (e.g. 192.168.0.2), Remote IP
Address (e.g. 192.168.0.3), the Default Gateway (e.g. 192.168.0.1) and the Subnet Mask (e.g.
255.255.255.0). Please make sure that the Local IP Address matches the Remote IP Address of
the remote equipment and the Remote IP Address matches the Local IP Address on the remote
equipment.
The TOS/DSCP and ECN menu item makes settings of the corresponding field in the IP protocol
header possible, enabling priority setting on the IP layer. For a more detailed description please
refer to Section 5 of the Operating Instructions NSD570. Relevant settings of this field are:
0 and 0 Best Effort (BE) forwarding characteristics i.e. no priority
46 and 0 Expedited Forwarding (EF) covering the characteristics of low delay, low loss and low
jitter suitable for real-time applications (default)
UDP port settings:

The UDP Port Teleprotection Packets (e.g. 49152) and the UDP Port EOC Packets (e.g. 49153)
can be configured. Note that the port numbers on the local and remote equipment must match.
Please consider the remarks regarding UDP port numbering in Section 5 of the Operating
Instructions NSD570.
A.7.4 Channel supervision and alarm settings

Guard Packets Sending Interval:
The G3LE continuously sends guard packets to supervise the channel availability. The Guard
Packets Sending Interval determines the interval of these packets. It can be set in a range from
5 ms (default) to 100 ms.
Transmission Time Test Interval:

In regular intervals the G3LE measures the transmission time in order to determine the channel
quality. The Transmission Time Test Interval determines the interval of these packets. It can be set
in a range from 100 ms to 10’000 ms (0.1 s to 10 s). Default setting: 1000 ms (1 s).
M EN 12/41 1KHW000898-EN
Transmission Time Warning / Alarm Sensitivity:

Based upon the delays measured in the Transmission Time Test Interval, the G3LE raises alarms
and warnings. For this it uses an n out of m measurement which means that n measurements out
of a sliding window of m values must not exceed a certain limit. Fixed values for n and m can be
selected by setting one of the possible sensitivity levels Low, Medium (default) and High. For
details on this please refer to Section 3 of the Operating Instructions NSD570.
Packet Loss Rate Alarm Threshold:

In addition to the transmission time the G3LE does also measure the packet loss rate in order to
determine the channel quality. It raises a corresponding alarm if a certain threshold level is
exceeded. This level can be set by means of the Packet Loss Rate Alarm Threshold in a range
from 0.1 % to 10 %. Default setting = 1.0%.
A.7.5 Laser setting for optical SFP

Automatic Laser Shutdown (ALS):
This parameter can be set to on or off (default). If it is set to on, the laser is shut down when no
optical input signal is detected. This is done for eye safety reasons.
A.7.6 WAN Password

Set WAN Password:
After clicking on the link Maintenance in the Main menu select the menu item Set WAN
Password. Enter a new password here. The Ethernet line interface works with the default
password but an alarm is being raised on this.
A.8 Settings for the individual commands
A.8.1 Command Application

Each command can be configured individually for transmitting protection signals in blocking,
permissive tripping or direct tripping protection schemes.
Choosing the application of the command determines the individual evaluation of the correspon-
ding tripping signals regarding security/dependability. The transmission time depends on the
channel quality (SNR/BER/PLR). The processing of the line signal is adaptive and therefore always
ensures the shortest possible transmission times for the chosen command application.
The NSD570 Analog can transmit up to 4 commands (A – D), the NSD570 Digital and NSD570
Ethernet can transmit up to 8 commands (A – H). Each of these commands can be set for:
- Off (not used)
- Blocking
- Permissive
- Direct
Usually the commands A – D or A – H respectively are configured in ascending order regarding
security requirements of the command application (for example: A for blocking, B and C for
permissive and D for direct tripping). Nevertheless alternative configurations are possible.
A.8.2 Maximum Tx Input Monitoring

For each command maximum Tx input duration monitoring can be programmed to OFF (default) or
a particular duration, i.e. the transmission of persistent commands can be disabled.
The duration of each single command injected at the relay interface inputs is separately and
continuously monitored (if the Tx trip duration alarm is enabled for this command).
Alarm is given and – if no persistent command is injected simultaneously – the guard signal is
transmitted instead of the tripping signal should the command duration exceed the predefined
value.
Also the boost criterion is set inactive before the guard signal is transmitted again.
Max Tx Input Monitoring configurable from 3 … 60 sec in steps of 1 sec
(default: 5 sec)
M EN 13/41 1KHW000898-EN
A.8.3 Tx Input On-Delay

Warning:
If an input on-delay is configured, it has a direct influence on the transmission time of the
equipment. It is delayed correspondingly and thus means a artificial deterioration of the equipment
performance. Normally the receiver at the remote station decides whether it was a genuine
command of adequate length or only a transient spark on a command input.
Therefore the command inputs are not delayed in the default operating modes. If there is a request
for some special applications (e.g. direct tripping when using digital communication systems) a
“pick up time” for the command inputs can be configured. A command is transmitted only after the
corresponding command input was activated for the preset delay time. The command sending
duration is then prolonged by the same time.
The preset input command delay can be configured for each command separately.
Tx Input On-Delay configurable from 0 … 20 ms in steps of 1 ms (default 0 ms)
A.8.4 Transparent Tx Input and Rx Output Duration

An enabled Transparent Tx Input or Rx Output Duration assures that a tripping signal is sent or a
command output is active as long as the command is injected at the command input or the tripping
signal is received.
A command injected or a tripping signal received passes transparently, without any alteration.
Transparent Tx input and Rx output duration can be programmed for each command and each
direction (Tx or Rx) separately.
When transparent command duration is selected, limited, fixed and prolonged command duration is
not applicable.
A.8.5 Prolonged Tx Input and Rx Output Duration

A Tx input or Rx output prolongation ensures a steady tripping signal transmission or command
output release even in the event of discontinuations of the signal being received.
The NSD570 receiver compensates the time needed for evaluating the tripping signals, i.e. the
command duration at the output has almost the same pulse width as the transmitted command at
the remote station (if no prolongation time is configured).
A command prolongation can be programmed for each command and each direction (Tx or Rx)
separately.
Prolonged Tx Input Duration configurable from 0 … 3000 ms in steps of 1 ms
Default 0 ms
Prolonged Rx Output Duration configurable from 0 … 3000 ms in steps of 1 ms
Default Blocking 0 ms
Default Permissive Tripping 10 ms
Default Direct Tripping 100 ms
When prolonged command duration is selected, transparent, limited and fixed command duration is
not applicable.
A.8.6 Limited Tx Input and Rx Output Duration

An enabled Limited Tx Input or Rx Output Duration assures that a tripping signal is sent or a
command output is active for the preset time at the most.
A command injected or a tripping signal received shorter than the configured Limited Tx Input or Rx
Output Duration passes transparently, without any alteration.
When a command is injected longer, the tripping signal is transmitted to the remote equipment with
the configured Limited Tx Input Duration only. If a tripping signal is received longer, the command
output is active for the configured Limited Rx Output Duration only.
If a command or tripping signal is shortly interrupted within the configured Limited Tx Input or Rx
Output Duration, more than one command can be sent to the remote station or released at the
command output.
A Tx input and Rx output duration limitation can be programmed for each command and each
direction (Tx or Rx) separately.
M EN 14/41 1KHW000898-EN
Limited Tx Input Duration configurable from 20 … 3000 ms in steps of 1 ms (default 100 ms)
Limited Rx Output Duration configurable from 20 … 3000 ms in steps of 1 ms (default 100 ms)
When limited command duration is selected, transparent, fixed and prolonged command duration is
not applicable.
A.8.7 Fixed Tx Input and Rx Output Duration

An enabled Fixed Tx Input or Rx Output Duration assures that a tripping signal is sent or a
command output is active for a preset and constant duration, independent of the injected
command’s or received tripping signal’s length.
A command injected shorter or a tripping signal received shorter than the configured time is
prolonged to the Fixed Tx Input or Rx Output duration, whereas a longer command tripping signal
is stopped after the elapsed time.
If a command is shortly interrupted at the input while the tripping signal is sent for the fixed
duration, it is regarded as one command only. Accordingly, a shortly interrupted tripping signal
during release of a command output is regarded as one command only.
A fixed Tx input and Rx output duration can be programmed for each command and each direction
(Tx or Rx) separately.
Fixed Tx Input Duration configurable from 20 … 3000 ms in steps of 1 ms (default 100 ms)
Fixed Rx Output Duration configurable from 20 … 3000 ms in steps of 1 ms (default 100 ms)
When fixed command duration is selected, transparent, limited and prolonged command duration is
not applicable.
A.9 Settings for the relay interface(s) G3LR

The inputs / outputs on the interface module are programmable; if a command requires two output
contacts, for example, both outputs can be assigned to one interface or even to different interfaces.
More inputs / outputs are easily obtained by inserting additional relay interfaces.
Each Relay Interface type G3LR provides the following electrically isolated inputs and outputs:
- 2 opto-coupler inputs, used for command injection
- 2 solid state outputs and 2 heavy duty relays with change-over contacts, used for command
issuing and signaling of various alarms and special functions (e.g. unblocking)
A maximum of 4 relay interfaces per NSD570 in the rack can be configured.
First of all, the relay interfaces that are plugged in the module rack and which shall also be used for
the NSD570 system have to be switched to “on” or to “G3LR” in HMI570 version 1.40 onwards in
the corresponding configuration list of the HMI570.
Please refer to section A.10.1 if G3LR interfaces should be used in parallel with G3LS interfaces.
A.9.1 Configuration of the inputs

Each of the configured commands can individually be mapped to one or several inputs. The inputs
can also be configured as “not used” (if, for example, three commands have to be transmitted using
two relay interfaces).
A.9.2 Configuration of the solid state and relay outputs

The following signals can individually be mapped to one or several outputs (solid state or relay
contacts). For a detailed description of the alarms refer to the Operating Instructions NSD570.
- Each output can also be configured as “not used” (if, for example, more outputs are available
on the used relay interfaces than signals have to be mapped)
- Each of the configured commands (A – D for the analog version or A – H for the digital
version)
- Tx command acknowledge (programmable for each command: the Tx command injected is
then looped back from the line interface to the configured output to acknowledge that the
corresponding command was sent. This is, however, no confirmation that the command has
also been received by the opposite station)
- Tx command summary acknowledge (for acknowledging when any command is sent)
- Rx command summary acknowledge (for acknowledging when any command is received)
M EN 15/41 1KHW000898-EN
- Tx or Rx command summary acknowledge (for acknowledging when any command is sent or

received)
- Rx Guard State (indicating the received guard signal state)
- Unblocking
- Hardware Warning (local)
- Hardware Alarm (local) - Link Alarm (local)
- Transmit Alarm (local) - Receive Alarm (local)
- Local Alarm - Remote Alarm
- System Alarm (incl. remote) - User Alarm 1
- User Alarm 2 - User Alarm 3
- Main Channel Failure - Standby Channel Failure
(only in 1+1 mode) (only in 1+1 mode)
A.9.3 Nominal input voltage

This has to be set manually via jumpers on G3LR.
Preparation for programming:
Switch off the NSD570 supply (via external circuit breakers) and pull out the G3LR modules from
the rack G7BI. If optional connecting cables are used, they have to be removed from the module
beforehand.
The input circuits can be set to operate in one of the following ranges for the nominal station
battery voltage:
G3LR
24 VDC … 48 VDC jumper 1A and 1B for input 1
jumper 2A and 2B for input 2
60 VDC … 110 VDC jumper 1A and 1C for input 1
jumper 2A and 2C for input 2
125 VDC … 250 VDC jumper 1A and 1D for input 1
(default setting) jumper 2A and 2D for input 2
G3LRa
24 VDC jumper 1A and 1B for input 1
jumper 2A and 2B for input 2
48 VDC … 60 VDC jumper 1A and 1C for input 1
jumper 2A and 2C for input 2
110 VDC … 125 VDC jumper 1A and 1D for input 1
jumper 2A and 2D for input 2
220 VDC … 250 VDC jumper 1A and 1E for input 1
(default setting) jumper 2A and 2E for input 2
The jumper settings can be entered in the device configuration by clicking on the Jumper Settings
link in the Edit Configuration menu and choosing the voltage range from a pull down menu for
each input of the relay interfaces.
A.9.4 Tripping of the inputs on a contact basis

If no station battery is available or if it shall not be used, the command inputs can also be tripped by
an external dry contact only. For that purpose, the optional module type G1LR (internal tripping
voltage 24 VDC) has to be plugged on to the Relay Interface G3LR. The module G1LR covers both
inputs of a relay interface, it is therefore not possible to have an external tripping voltage on one
input and the internal tripping voltage on the other input of the same board. But a mix of internal
and external tripping voltage on neighboring relay interfaces is possible.
M EN 16/41 1KHW000898-EN
Preparation for mounting G1LR:

Switch off the NSD570 supply (via external circuit breakers) and pull out the G3LR modules from
the rack G7BI. If optional connecting cables are used, they have to be removed from the module
beforehand. Remove the four jumper plugs and put them to a safe place if they shall be reused
later. Mount the piggyback module into the jumper plug sockets (since the sockets are not all
mounted equidistantly, a mistaken placing of the module is not possible).
Tripping on a contact basis can be entered in the device configuration by clicking on the Jumper
Settings link in the configuration menu and choosing Internal 24 VDC from a pull down menu for
both inputs of the corresponding relay interface.
A.9.5 Relay contacts

The relay outputs can be operated as normally open (NO) or normally close (NC) contacts. Since
all three terminals of the relays (NO/NC/Common) are available on the module socket or on the
terminal block of the optional connecting cable, NO or NC contacts are obtained by wiring the
output contacts correspondingly.
Warning: do not use NO and NC simultaneously!
A.10 Settings for the GOOSE LAN interface G3LS

Optional one G3LS GOOSE LAN interface can be plugged per TPE. Valid slots are N34 and N64.
Up to eight commands can be handled by one G3LS interface. The number of commands is
configurable. It should be noted, however, that the number of commands corresponds to the
number of physical rack slots which are virtually occupied by the G3LS (example: 6 GOOSE
commands → 3 rack slots are virtually occupied).
A.10.1 GOOSE Interface Configuration

The GOOSE LAN interface needs a proper setup of the device identification related parameters.
Please refer to section A.4.2 “Device identification” for a description of these parameters.
GOOSE LAN Interface

In order to select one of the interfaces, electrical Ethernet X102 or optical SFP X103, the selection
switch between the two interfaces has to be moved towards the required interface. Default = X102.
If an optical SFP network interface is plugged, the automatic laser shutdown can be configured to
be either on or off (default).
The parameter “Number of protection commands” defines how many commands are exchanged
between the line interface and G3LS. In other words, the parameter defines how many physical
slots are occupied by G3LS and how many slots can be allocated by G3LR interfaces. Two
commands occupy one physical slot. The parameter is valid for both directions.
If G3LS is installed in parallel with G3LR interfaces in one TPE, a few things need to be
considered. It’s mandatory to place G3LS in slot N34 or N64. Additional G3LR interfaces can be
adjoined in the slots which are not virtually allocated by G3LS. The number of slots which are
virtually occupied by G3LS depends on the parameter “Number of Protection Commands” in the
GOOSE Interfaces Configuration section.
Basically, G3LS behaves equal to G3LR. For example, if three commands are handled by G3LR
interfaces two slots would be occupied by two G3LR boards. The same is true if three commands
are handled by one G3LS interface. This implies that commands E to H could be assigned to G3LR
interfaces. Of course, this is only true if a line interface supporting eight commands is configured.
A detailed description is available in the main part of the NSD570 Operating Instructions in section
5.
G3LS has an internal real time clock (RTC). The time stamps published with GOOSE frames are
derived from this RTC. By default, the RTC is synchronized to the line interface in TPE1. Optionally
the RTC clock can be synchronized to an IRIG-B clock signal.
M EN 17/41 1KHW000898-EN
A.10.2 IEC 61850 Configuration

Basically, an ICZ-file is needed to be downloaded to the G3LS device. This file provides the
configuration parameters needed by the IEC 61850 part of the G3LS firmware. The engineering
procedure is described in the appendix 1KHW002649 “Engineering of GOOSE LAN Interface
G3LS”. Please refer to this annex document for a detailed description about IEC 61850
engineering.
Verify the line interface configuration, the GOOSE Interface configuration and the IEC 61850
configuration are consistent. In case of an inconsistent configuration the behavior of NSD570 is
undefined! HMI570 provides a consistency checker tool which simplifies the verification. It is highly
recommended to run this tool before downloading any kind of configurations to the device. For
more information on configuration verification see appendix 1KHW002649 “Engineering of GOOSE
LAN Interface G3LS”.
A.11 Alarm settings
A.11.1 Alarm pick up and hold delays

A system alarm for each NSD570 in the rack is given on the common interface outputs. Several
further alarms (including system alarm) may be mapped on the relay interface outputs (refer to
A.9.2).
The signaling of an alarm on the alarm outputs may be delayed after detection of the alarm source
(pick up time). Also a prolongation of the alarm signaling after the alarm source has disappeared
can be programmed (hold time).
If several alarm sources appear or disappear in a sequence, the pick up time for combined alarms
(e.g. system alarm) will be triggered with the first appearing alarm and the hold time will start when
the last alarm has disappeared.
Alarm pick up time configurable from 0 … 15 sec in steps of 1 sec (default 15 sec)
Alarm hold time configurable from 0 … 15 sec in steps of 1 sec (default 15 sec)
A.11.2 Behavior in case of a failing redundant power supply

The behavior in case of a failing redundant power supply can be set:
• If “Redundant Power Supply Failure“ is set to “HW Warning”, then “Warning: Undervoltage
redundant supply 1/2” is raised.
• If “Redundant Power Supply Failure“ set to “HW Alarm”, then “Undervoltage alarm supply 1/2” is
raised.
A.11.3 Alarm relay contacts

The alarm relay outputs on the common interface can be operated as normally open (NO) or
normally close (NC) contacts. Since all three terminals of the relays (NO/NC/Common) are
available on the module socket or on the terminal block of the optional connecting cable, NO or NC
contacts are obtained by wiring the output contacts correspondingly.
Warning: do not use NO and NC simultaneously!
A.11.4 Configuration of user alarms

It is possible to combine some of the different alarm sources (by logical „OR“ gating) into three
different „user defined“ alarm signals. These user alarms (1 … 3) are individually configurable on
each output (solid state or relay contact) of the relay interfaces.
In addition is it possible to select for each user alarm if the output signal shall be delayed or
undelayed.
delayed the user alarm output is operated with respect to the configured alarm pick up and
hold times.
undelayed the user alarm output follows the alarm state without any additional delays.
M EN 18/41 1KHW000898-EN
The following alarm sources can be combined in user alarm 1, 2 or 3:

- HW Warning Local
- HW Alarm Local - HW Alarm Remote
- Link Alarm Local - Link Alarm Remote
- Tx Alarm Local - Tx Alarm Remote
- Rx Alarm Local - Rx Alarm Remote
- Tx Signal Local - Tx Signal Remote
- Rx Signal Local - Rx Signal Remote
- SNR/BER/PLR Local - SNR/BER/PLR Remote
A.12 Display Panel

The optional display panel G1LC provides various information such as trip counter reading or alarm
messages from the NSD570 Teleprotection Equipment – without having the need of a PC/note-
book.
As readout device a dot matrix LCD display with two lines, 16 characters each, and a yellow/green
background LED is used. The lightness of the background LED, the contrast of the LCD and the
standby time of the display are adjustable.
Four buttons that enable the menu-driven handling are accessible on the front of the display panel.
Preparation for mounting G1LC:
Switch off the NSD570 supply (via external circuit breakers) and remove the blanking cover plate
from the rack G7BI. Connect the enclosed ribbon cable from the display panel to the adjacent
Common Interface G3LC (refer to Operating Instructions, Section 6).
Fix the Display Panel G1LC on the rack by means of the four captive screws.
Switch on the NSD570 supply again, the  intro appears on the display.
The following display settings may be modified (please refer to the Operating Instructions for a
detailed description how to navigate through menu structure of the display panel):
- Increase/decrease the contrast setting of the LCD-module (16 steps); default: step 10
- Increase/decrease the backlight setting of the LCD-module (4 steps and OFF); default: step 3
- Change the standby time of the display panel (1 – 60 minutes); default: 10 minutes
A.13 Management LAN Interface

The optional Management LAN Interface is an Ethernet 10/100BaseT interface. It can be used to
connect one or more NSD570 systems to TCP/IP-networks for configuration, monitoring and
maintenance.
The Management LAN Interface is plugged into the most left slot (N84) of the Module Rack G7BI.
Therefore, the TPE 2 in this rack can only utilize a maximum number of three Relay Interfaces
G3LR.
Other NSD570 devices may be connected via the local station bus (RS-485) to the Management
LAN Interface.
There is a special document available that describes the programming, testing and commissioning
of the Management LAN Interface (please refer to 1KHW002232 “Commissioning Instructions LAN
Interface G3LM” in the annex of the Operating Instructions NSD570).
M EN 19/41 1KHW000898-EN
B Testing Instructions for the NSD570 Equipment.
B.1 General
Some of the tests for the NSD570 system can be done with assistance of the HMI570 user
interface program. For example: the transmission time of one direction can be verified with a
manually initiated loop test, the result is immediately displayed on screen.
The guard signal of the NSD570 Analog version is QPSK modulated to accommodate also an
Embedded Operation Channel (EOC). As a result the level of the guard signal changes
continuously. Its exact level can therefore only be measured, if the EOC is switched off by means
of the HMI570.
B.1.1 Test conditions

Temperature range: 20 C to 35 C.
The connections for the tests can be made either directly at the rear of equipment (spring-clamp
terminals, Sub-D and RJ45 sockets) or at the terminals and sockets of the optional connecting
cables.
B.1.2 Visual checks before powering the equipment
Check the wiring of protective earth to the equipment.

DANGER If the NSD570 module rack is mounted in a cabinet, check that the rack
is properly earthed at the cabinet.
Check if a protective earth wire of at least 25 mm2 has been connected
visibly to the earth bolt of the cabinet.
Caution Check the voltage source and the polarity for the power supply.
In case of battery supply and if the NSD570 module rack is mounted in a
cabinet: check if the positive pole (+) of the battery is grounded. If it is, place
an earth jumper to the positive pole of the cabinet supply.
48 VDC and higher battery voltages are hazardous.

Do not make any installation under energized condition.
 Note: Now the equipment can be powered by closing the external circuit breaker(s)
or switching on the external power supply unit.
B.2 Check power supply

Check the auxiliary supply voltage at the inputs of the power supply module G3LH, G3LI or G3LK.
Following input ranges have to be considered:
• G3LH 48 VDC to 250 VDC (± 20%) or 100 VAC to 240 VAC (-15%, +10%), 50/60 Hz
• G3LI 24 VDC to 60 VDC (± 20%)
• G3LK 110 VDC to 250 VDC (± 20%) or 110 VAC to 230 VAC (-15%, +10%), 50/60 Hz
In case of dual (redundant) power supply, the supply voltage for both modules must be checked.
Two LEDs on the front panel indicate the status of the power supply modules (green = Ok, red =
fail, dark = not assembled).
There is no easy access to the internal DC voltages generated by the power supply modules
(+12.3 V), generated by the common interface type G3LC (+12 V and +5 V) or generated by the
various plug-in modules (+3.3 V). However, in case these voltages go outside their limits, it will be
indicated by the corresponding status LED of the module on the front panel and by a hardware
alarm.
M EN 20/41 1KHW000898-EN
B.3 Preparing the equipment

Follow the steps below for connecting to the equipment, downloading the configuration and
preparing the system for testing:
B.3.1 Connecting to the equipment

1. Start the HMI570, log yourself in, load the pre-configured file and connect to the equipment as
described in the Operating Instructions NSD570, 1KHW000890, section 4, section
“Communication to the NSD570”.
2. If no configuration was downloaded to the systems in the rack before, make sure that no
connection is made to the RS-485 station bus interface at the rear of the rack while connecting
to the equipment with the default device address. After setting of all (unique!) device
addresses of the NSD570 systems that are supposed to be connected to the local station bus,
the corresponding wires can be reconnected to the RS-485 interface terminals.
3. Connect the equipment using the default device addresses:
Type “241” in the Local Device Address entry field when you want to connect to the line
interface in the left rack half (TPE 1); type “246” in the Local Device Address entry field when
you want to connect to the line interface in the right rack half (TPE 2). Use default device
addresses “242” for GOOSE Interface G3LS in TPE 1 and “247” for GOOSE Interface G3LS in
TPE 2. Use default device address “250” for Management Interface G3LM in TPE 2. This
method with the default addresses can also be used to determine the configured device
address of the systems in a rack (not having a RS-485 connection to the local station bus!).
B.3.2 Download the configuration

4. In the Configuration menu, click on Download Configuration. Compatibility checks are now
performed to verify if downloaded functionality and settings can be handled by the equipment.
Three grades of compatibility are possible:
• Full compatibility: The download operation is possible without restrictions. Go on with
step 5
• Restricted compatibility: The download operation is possible with some alterations of the
settings to be downloaded. An on-screen message will report each of these alterations. It is
recommended in this case to change the settings responsible for the reported alterations or
to update the firmware of the system as described in document “Firmware Download
Description NSD570”, 1KHW000896.
• No compatibility: the download operation is not possible due to incompatibility between
HMI570 and hardware/firmware. Solve the problem by getting compatible versions for
HMI570, hardware and firmware as given by document “Compatibility Requirements for
NSD570”, 1KHW000902. Perhaps it is only necessary to update the firmware of the system
as described in document “Firmware Download Description NSD570”, 1KHW000896.
Afterwards restart the programming and testing procedure.
• No compatibility: the download operation is not possible due to missing functions in the
hardware/firmware. Changing the settings responsible for the reported incompatibility may
solve this problem. Otherwise update the firmware as described in document “Firmware
Download Description NSD570”, 1KHW000896.
5. If the download operation is possible, a message will appear, which informs you that the
configuration download was successful.
6. Reset the device using the Reset Device link in the Maintenance Menu, a message will
appear when the task was sent successfully.
7. Disconnect Device – ignore the error messages that might appear on screen (because
the device address has changed) and reconnect to the system with the new device
address.
M EN 21/41 1KHW000898-EN
Note: If two NSD570 are equipped in the same rack and by mistake the same device
address was configured, a connection to any of the two devices is no longer possible.
In this case proceed as follows:
Switch off the NSD570 supply (via external circuit breakers) and pull out one of the
two line interfaces (G3LA/G3LD/G3LE). Switch on the supply again, connect to the
remaining device and reconfigure the device address. Switch off the NSD570 supply
(via external circuit breakers) and plug in the other line interfaces. Switch on the
supply again.
This procedure also applies if by mistake the same device address was configured for
GOOSE interface(s) G3LS and Management interface G3LM.
8. If you like to see whether your new configuration has become effective, wait until the green
“Ok” LED lights up again, click then on the Discard Configuration link in the Configuration
menu and on the Upload Configuration link afterwards. With View Configuration you can
see the uploaded configuration including Device Info, Hardware Versions and Firmware
Versions (which are not configurable but readable from the device).
B.3.3 Preparing the system for testing

9. Synchronize the internal time and date of the NSD570 system on your local PC/notebook time
information: click on the link Set Time and Date in the Maintenance menu (see B.6). A
message will appear when the task was sent successfully.
Note: this has initially to be done so that no alarms from the RTC will appear later on.
If an external time information signal is connected to the synchronization inputs of the
equipment rack, the internal clock has not to be set but to be checked using the Get Time and
Date link in the Maintenance menu.
10. Check whether the Jumper Settings in the Configuration menu correspond to the actual
requirements. If not, update the entries for the Analog Interface (if plugged), for the E1/T1
Interface (if plugged) and for the Relay Interfaces, save the configuration to disk, download it
and reset the equipment.
11. The same as described in the previous step applies also for the Configuration menu item
Rack Assembly – edit the rack assembly list if it does not represent the current state.
12. Switch off the NSD570 supply, connect the two units under test: analog, digital, optical or
Ethernet terminals back-to-back (cross-connected) or via the communication channel (e. g.
PLC equipment ETL, or digital multiplexer equipment FOX, or Ethernet/IP network).
13. Switch on the NSD570 supply again, the green “Guard” LED of the NSD570 systems TPE 1
and TPE 2 (if available) should light up.
B.4 Change configuration

If it is necessary to change configuration parameters, refer to section 5 of the Operating
Instructions NSD570, section “Configuration and Settings” or in section “A” of this document.
It may be necessary to change parameters temporarily only (e.g. switching off the EOC in the
NSD570 Analog for measuring the exact guard level). They have to be set to the original entries
again after the tests have been concluded.
If the system does not work properly after downloading the modified configuration and after the
manual reset has been performed, use the link Previous Configuration in the Maintenance menu
to switch back to the last configuration, which will properly work out as before, after resetting the
equipment again.
M EN 22/41 1KHW000898-EN
B.5 Remarks for T-operation

NSD570 Analog in T-operation:
When a link with NSD570 Analog in T-operation has to be tested, the preparation has to be done
as follows:
- Adjust transmitter level at both outer stations of the T-ed line
- Adjust receiver level at both devices in the T-station
- Adjust transmitter level at both devices in the T-station
- Adjust receiver level at both outer stations of the T-ed line
Normal T-operation mode:
Measure the transmission time (and command prolongation time):
- The T-ed-configuration can be regarded as two individual links (outer station A <-> T-station
and outer station B <-> T-station). The transmission time (and the command prolongation
time) can now be measured as in case of a standard link.
Pay attention to the fact, that in the T-station the command inputs and outputs have to be
connected in parallel directly at the relay interfaces or at the isolating terminals.
- Measure the transmission time from outer station A to outer station B and vice-versa
according B.14.2 of this Testing Instructions. An additional delay of 3 ms has to be expected
compared to the point-to-point operating time of a standard link.
Inverse T-operation mode:
Measure the transmission time (and command prolongation time):
- The T-ed-configuration cannot be regarded as two individual links (outer station A <-> T-
station and outer station B <-> T-station). The transmission time (and the command
prolongation time) can only be measured from A to T and from B to T.
Pay attention to the fact, that in the T-station the command inputs have to be connected in
parallel and the outputs have to be connected in series directly at the relay interfaces or at
the isolating terminals.
- Measure the transmission time from outer station A to outer station B and vice-versa
according B.14.2 of this Testing Instructions For this measurement a continuous command
has to be injected in the T-station while commands are injected in A or B. An additional delay
of 3 ms has to be expected compared to the point-to-point operating time of a standard link.
B.6 Configure Real Time Clock (RTC)

The internal real time clock (RTC; mounted on the line interfaces) has to be set to the actual date
and time for proper operation of the event recorder.
If a GOOSE LAN interface G3LS and/or a Management LAN interface G3LM is available in the
rack, also set the RTC correctly on these modules for accurate timestamping of the corresponding
services (e.g. published GOOSE frames, user activity logging).
B.6.1 Setting real time clock

1. Check if the time and date of your PC is exact.
2. Setting the date and time using the HMI570: click on the link Set Time and Date in the
Maintenance menu, the RTC will be adjusted to your PC time and date.
3. Click Get Time and Date in the Maintenance menu, the date and time displayed on screen
should be the same as that of your PC.
B.6.2 Testing external real time clock synchronization (if available)

The external synchronization – either a signal with a pulse each second or a signal having IRIG-B
format or both – has to be connected to the corresponding G3LC inputs (connector X103 on supply
backplane type G1LB or terminals of the external connecting cable for G1LB, if used).
a) If only an external sync pulse (each second) is available:
Set the RTC according B.6.1
M EN 23/41 1KHW000898-EN
b) If an external GPS signal having IRIG-B format is available:

Set the time on the PC running HMI570 a few hours back/forward.
Click on the link Set Time and Date in the Maintenance menu, the RTC would normally be
adjusted to your PC time and date.
Click Get Time and Date in the Maintenance menu, the date and time displayed on screen
should not be the same as that of your PC but is the exact time as provided by the GPS
receiver.
Set the time on the PC back to the exact time.
B.7 Analog line interface

The frequency of the guard and trip tones in the used channel cannot be easily determined and
also not be viewed by the HMI570. They depend on the channel bandwidth, the center frequency
and the analog operating mode. It is therefore recommended to measure signal levels with a
broadband level meter (to a reference of 600 Ohm), assuring that no other signals are existent on
the line outside the NSD570 channel. Alternatively, a selective level meter with peak level search
can be used.
For calculation of guard and trip frequencies please refer to the Operating Instructions NSD570.
B.7.1 Transmitter
Measure the guard level level that is fed into the 600 Ohm line (for this measurement the EOC in
the local station has to be switched off):
- Switch off the EOC (if it is enabled)
- Measured guard level = [ Tx level according setting ± 2 ] dBm
- Switch on the EOC again, if requested
Measure the command level that is fed into the 600 Ohm line (for this measurement, a command
signal has to be injected at the command inputs, the boost ratio has to be set to 0 dB):
- Set the boost ratio to 0 dB
- Measure Single Tone command level = [ Tx level according setting ± 2 ] dBm
- Measure Dual Tone command level = [ Tx level according setting – 3 dB ± 2 ] dBm
- Remove the command signal from the command inputs
- Set the boost ratio back to the initial value
B.7.2 Power boosting / Boost output

Measure the boosted command level that is fed into the 600 Ohm line (for this measurement, a
command signal has to be injected at the command inputs; boost ratio = BR according setting):
- Measure Single Tone command level = [ Tx level according setting + BR ± 2 ] dBm
- Measure Dual Tone command level = [ Tx level according setting – 3 dB + BR ± 2 ] dBm
If the NSD570 is connected to a PLC equipment, it may be possible that the boosted command
level – due to its tolerance range of ± 2 dB – overmodulates the PLC amplifier. Therefore, the
signal level has to be reduced to the maximum level that is allowed at the protection input of the
PLC equipment.
Check that the boost output contact is activated as long as a command is injected (this measure-
ment is only necessary if the contact is really needed, e.g. if connected to a PLC equipment):
- The boost output is closed as long as a command is transmitted on the line
B.7.3 Receiver
Measure the guard level that is received at the 600 Ohm line input (for this measurement the EOC
in the remote station has to be switched off):
- Measured guard level = [ Rx level according setting ± 2 ] dBm
M EN 24/41 1KHW000898-EN
B.8 Digital line interface
B.8.1 Transmitter / Receiver

There are no special measurements foreseen for the digital line interface. Nevertheless, the
settings made for the chosen interface type (G.703, RS-530, E1, T1, Optical) should be verified
with the actual used communication equipment (whether timing, synchronization, buffering, coding
and formats match the best possible way). This can be checked and optimized for example by
monitoring the BER and the manual loop test time for different settings (click on the link Status /
Alarm in the main menu and Upload Status afterwards).
B.8.2 Optical output power / optical receiver sensitivity

G1LO
The optical power meter must be sensitive to a wavelength of 1310 nm for the Optical Direct Fiber
and the Optical OTERM/OPTIF interface. A single mode adapter cable has to be used for
connecting the power meter to G1LO.
The optical output power can be measured for both, the short haul and long haul setting:
- Switch to short haul (if not already set)
- Measured output power = [ -22 … -17 ] dBm
- Switch to long haul
- Measured output power = [ -5 … -1 ] dBm
- Switch to short haul again, if requested
To determine the optical receiver sensitivity the output signal of the optical interface has to be
attenuated and looped back to the input. The guard LED of the NSD570 must always be on while
increasing the optical attenuation.
The optical receiver sensitivity for the Optical Direct Fiber and the Optical OTERM/OPTIF interface
can be measured as follows:
- Switch to long haul (if not already set)
- Measured maximum attenuation > 25 dB
- Switch to short haul again, if requested
G1LOa
Depending on the selected SFP module, the optical power meter must be sensitive to a wavelength
of either 850 nm, 1310 nm or 1550 nm and a single or a multi mode adapter cable has to be used
for connecting the power meter to G1LOa.
The following output power levels shall be measured:
- Measured output power with 850 nm, MM 50/125 µm, 1 km SFP = [ -23 … -11 ] dBm
- Measured output power with 850 nm, MM 62.5/125 µm, 1 km SFP = [ -19 … -11 ] dBm
- Measured output power with 1310 nm, SM, 30 km SFP = [ -15 … -8 ] dBm
- Measured output power with 1310 nm, SM, 60 km SFP = [ -5 … 0 ] dBm
- Measured output power with 1550 nm, SM, 120 km SFP = [ 0 … 5 ] dBm
- Measured output power with CWDM (1550 nm), SM, 180 km SFP = [ 5 … 8 ] dBm
To determine the optical receiver sensitivity the output signal of the SFP has to be attenuated and
looped back to the input. The guard LED of the NSD570 must always be on while increasing the
optical attenuation.
The following optical receiver sensitivities shall be measured:
- Measured minimum received power with 850 nm, MM, 1 km SFP < -32 dBm
- Measured minimum received power with 1310 nm, SM, 30 km SFP < -34 dBm
- Measured minimum received power with CWDM (1550 nm), SM, 180 km SFP < -45 dBm
M EN 25/41 1KHW000898-EN
B.8.3 Address check

This test is only necessary for high performance measurements or for a customer approval of the
equipment.
For this test, the remote digital address has to be changed in the local device. After resetting the
local device, it must immediately raise an alarm.
Note that the Digital Address Check has to be enabled for this test by means of the HMI570 (refer
to A.6.1 Interface independent settings).
B.9 Ethernet line interface

There are no special measurements foreseen for the Ethernet line interface. The local and remote
device must be connected and after a few seconds all LEDs on the front of the NSD must change
to green and the alarms must disappear. If this is not the case the settings on local and remote side
should be verified. The remote IP address of the local interface must match the local IP address of
the remote interface and vice-versa. The UPD port numbers must match as well as the settings for
the Guard Packets Sending Interval and the Transmission Time Test Interval. Furthermore the
WAN Password must match on both sides.
If VLAN Tagging is enabled, the VLAN ID must be the same as well.
In order to set the correct Propagation time, it is necessary to connect with a computer to the
remote Ethernet line interface and send a ping to it. This has to be done when the used IP network
is not loaded (i.e. no or only low traffic). The measured time divided by 2 must be set as
propagation time.
The connection is established properly after both devices are connected to the network, all LED are
green and no alarm is risen by means of the HMI570
B.9.2 Optical output power / optical receiver sensitivity (only if optical SFP is used)
for connecting the power meter to G3LE.
- Measured output power with 850 nm, MM 50/125 µm, 0.5 km SFP = [ -23 … -11 ] dBm
- Measured output power with 850 nm, MM 62.5/125 µm, 0.5 km SFP = [ -19 … -11 ] dBm
- Measured output power with 1310 nm, MM 50/125 µm, 0.5 km SFP = [ -23.5 … -14 ] dBm
- Measured minimum received power with 850 nm, MM, 0.5 km SFP < -32 dBm
M EN 26/41 1KHW000898-EN
B.10 1+1 Device operation mode

A 1+1 link can be tested for proper switchover in fault state when performing the following steps:
- Run a redundant 1+1 link without any alarms and make sure both line interfaces in one
NSD570 rack receive Guard
- Upload status of TPE 1 and verify “Line interface in 1+1 operation mode is active”
- Upload status of TPE 2 and verify “Line interface in 1+1 operation mode is inactive”
- Unplug the cable of the line interface in TPE 1 so that it raises receive and local alarm
- Reconnect the cable of the line interface in TPE 2 so that Guard is received and the alarms
disappear
disappear
B.11 GOOSE LAN interface G3LS

There are no special measurements foreseen for the GOOSE LAN interface. GOOSE message
transfer can only be tested by means of external IEDs or dedicated test equipment. Testing of
G3LS is supported by commissioning features which are described in the NSD570 operating
instructions, section 3.5.19. “Test facilities for the GOOSE LAN Interface”.
If G3LS is configured correctly and external equipment provides the expected GOOSE
communication there should not be any alarm on the module. In case of missing external
equipment there should not be more than one alarm pending, namely “GOOSE Communication
Failed”. Otherwise the configuration of G3LS needs to be verified.
The optical power meter must be sensitive to the wavelength of the installed SFP. Since G3LS is
designed for local applications within a substation the use of multi-mode fibers and SFP is
adequate.
The following output power level shall be measured:
M EN 27/41 1KHW000898-EN
B.12 Relay interfaces G3LR
Designation Meaning
(T.22/..1) Connector 1 of terminal block connected to rack position N22
B.12.1 Inputs
How to activate a command input depends on the jumper settings on G3LR
• If no optional module type G1LR (internal tripping voltage 24 VDC) is mounted on G3LR:
By means of an external contact, inject a tripping voltage at the command inputs with the
voltage level U1 according to the jumper settings on G3LR, i.e. 24 VDC (G3LRa only), 48 VDC,
110 VDC, 220 VDC)
• If the optional module type G1LR (internal tripping voltage 24 VDC) is mounted on G3LR:
Short circuit the command input by means of an external contact only.
Activate the command inputs and check if the corresponding Input LED lights up on the front panel.
B.12.2 Outputs
Depending upon the programmed criteria, activate the required action using the following table.
Check the contact closure of the programmed outputs on G3LR by means of an auxiliary tripping
voltage (of the same level as used for the command inputs) and an external current limitation.
Check if the corresponding Output LED lights up on the front panel.
Set the link back to an alarm free condition after this test.
Output on G3LR Action to enforce the output

Rx Command A-H Inject a Tx command at the corresponding input of the remote station
Ack Tx Command A-H Inject a Tx command at the corresponding input of the local station
Ack Tx Summary Inject any Tx command at the inputs of the local station
Ack Rx Summary Inject any Tx command at inputs of the remote station
Ack Tx/Rx Summary Inject any Tx command at the inputs of the local station and any Tx
command at the inputs of the remote station
Rx Guard State Disconnect the line interface input signal
Unblocking Disconnect the line interface input signal
HW Warning Only applicable if two (redundant) power supply modules are plugged:
remove the input supply voltage from one of the two power supply
modules
Hardware alarm Not applicable (this alarm cannot easily be generated since it would
require short-circuiting of signals or even a destruction of components)
Link alarm Disconnect the line interface input signal
Transmit alarm Inject a continuous Tx command > 10 sec
Receive alarm Disconnect the line interface input signal
Local Alarm Disconnect the line interface input signal
Remote alarm Disconnect the line interface input signal at the remote station
System alarm Disconnect the line interface input signal
User alarm 1-3 Not applicable (this alarm depends on the alarm settings, i.e. the logical
OR gating of several internal alarm sources; some of them can be
generated – see above – others would require short-circuiting of signals
or even a destruction of components)
Main and Standby Only applicable in 1+1 device operation mode. Disconnect the line
Channel Failure interface input signal of TPE 1 (Main) and TPE 2 (Stand-by).
M EN 28/41 1KHW000898-EN
 Note: This test is only necessary for the Rx commands. Other signals on the
outputs must only be monitored for high performance measurements or
for a customer approval of the equipment.
Precise measurement of the programmed alarm delay times is not
necessary – only operating of the contact shall be monitored.
B.13 System alarm indication

The system alarm may be triggered by interrupting the connection to the line interface
(disconnecting of at least the input = receiver circuit). After the programmed delay time the
corresponding system alarm relay on G3LC operates.
Check that the relay output is changing its state (precise measurement of the programmed alarm
delay time is not necessary).
Now restore the connection to the line interface. The alarm LEDs will immediately go off and the
relay output will change its state after the programmed delay time.
B.14 System functions
B.14.1 NSD570 loop test

The NSD570 is tested by issuing a loop test via HMI570 or by pressing the “Loop Test” button on
the front panel of the module rack.
In the Maintenance menu click on the link Manual Loop Test.
If the loop test is successful, the “Trip” LED on the front panel will light up for three seconds and a
message will appear on the PC screen indicating the measured loop test time for one direction
(TLink).
The transmission time of the loop test depends on the chosen bandwidth for the NSD570 Analog,
the used interface type of the NSD570 Digital, as well as – for both types of devices – on the
settings for the command application (the loop test is always transmitted as the command
configured for the highest requirements regarding security) and on the delay introduced by the
communication link (e.g. PLC or Ethernet/IP network).
B.14.2 Command transmission time

Check the transmission time of the NSD570 commands over the link.
Transmit at few commands with a command / pause duration of about 100 ms / 1000 ms and
measure the actual transmission time for the command from the local station to the remote station.
 Note: The nominal transmission time as given in the Operating Instructions NSD570
shall serve as a guideline for the mean value of several commands. This is
valid only, if the two NSD570 are connected back-to-back.
If there is a communication link connected in between, the delay of this
link (propagation time) has to be added to the nominal transmission
time.
If a “Tx Input On-Delay” is configured for the specific command, this
time has to be added to the nominal transmission time.
B.14.3 Command prolongation time

This test is only necessary for high performance measurements or for a customer approval of the
equipment. It is only applicable if “Transparent Tx Input Duration” and “Prolonged Rx Output
Duration” is configured for the command.
If available, a well-suited test instrument for this purpose (e.g. the MK11) would simplify this
measurement.
Measure the difference between the received command signal pulse length and the transmitted
command signal pulse length.
M EN 29/41 1KHW000898-EN
B.15 Display Panel

With the following minimized test procedure the four buttons on the front of the display panel (which
enable the menu-driven handling) as well as the communication of the display panel with the line
interface(s) present in the module rack shall be tested:
1. Press the button with the arrow towards “down” -> SELECT DEVICE / TPE1 will appear
2. Press the “Enter” button -> MAIN MENU / Trip Counter will appear
3. Press the “Enter” button -> Cmd A Tx: ….. / Cmd A Rx: ….. will appear (press the “up” button
repeatedly to see all counter readings)
4. Press the “Loop Test” button of the TPE 1 device in the rack -> after some seconds LOOP
TEST TIME / TPE 1 ….. ms will appear
5. If the rack is equipped with only one teleprotection device TPE 1, proceed with step 10; else
press the “Back” button -> SELECT DEVICE / TPE1 will appear
6. Press the button with the arrow towards “up” -> SELECT DEVICE / TPE2 will appear
8. Press the “Enter” button -> Cmd A Tx: ….. / Cmd A Rx: ….. will appear (press the “up” button
repeatedly to see all counter readings)
10. Continuously press the “Back” button for more than 6 seconds -> the display panel will reset,
the backlight will go off and the  intro will restart
B.16 LAN Interface

There are no special measurements foreseen for the management LAN interface G3LM.
Nevertheless, the operation of the HMI570 management LAN functionality and the connection to
the device with the serial cable should be tested.
B.16.1 Connecting to the device with serial cable

Before using an NSD570 Management LAN Interface G3LM for the first time, there is a serial
RS-232 connection to the NSD570 equipment necessary. Connect a serial cable to the test PC and
to the NSD570 front panel (labelled “COM 1”). In order to be able to communicate with G3LM,
make sure that there is no Ethernet cable plugged into it, neither electrical nor optical SFP 1.
Start the HMI570 software on the test PC. If you have already configured an administrative
account, then please log in with that one. If not, log in with the following default account:
User name: Administrator
Password: welcome
Choose “Connect via: local” and leave the IP Address field blank. Then press “Log In”.
Instructions NSD570, section “Configuration and Settings” or in section “A” of this document.
Create a printout of the active configuration data that need to be uploaded and saved to disk (see
B.17.4).
1
There is an automatic internal switch between Ethernet and Serial port. If an Ethernet link is present, the
serial port is switched off, i.e. switched to master mode so that alarm polling can work.
M EN 30/41 1KHW000898-EN
of either 850 nm, 1310 nm or 1550 nm and a single or a multi-mode adapter cable has to be used
for connecting the power meter to G3LM.
B.16.3 Test HMI570 Management LAN functionality

Test the access and the basic functionality of the HMI570.
1. Power up the NSD570 with Management LAN Interface G3LM and await the startup delay
(approx. 2 minutes). When Ok/Fail LED turns to green, G3LM has started successfully.
2. Start HMI570 PC that is connected to LAN and has therefore access to the NSD570
Management LAN Interface G3LM (connect both to the same LAN, or connect the PC directly
to G3LM and use same subnet).
3. “Log In” with a configured user name and password. Enter the G3LM IP address and mark
“Connect Via: LAN”. Your login data will be checked on G3LM (not in HMI570).
4. In menu “Connect Device” enter the configured device address (not the default one!) and click
“Connect” -> “Device connected” must appear.
5. Click “Configuration”, “Upload From Device” -> “Configuration upload successful” must
appear.
B.17 Concluding works
B.17.1 Reset counters

After all NSD570 tests have passed successfully, reset the counters by using the HMI570.
In the Status / Alarm menu click on Trip Counter, then on Reset Trip Counter, activate the
checkbox “All” and click on the Reset button.
B.17.2 Clear event recorder

In the menu Event Recorder click on the link Clear Event Recorder.
B.17.3 Manual reset

In the Maintenance menu click on the link Reset Device.
M EN 31/41 1KHW000898-EN
B.17.4 Save the initial configuration data ex works

In the Configuration menu click on the link Upload Configuration and then on Save
Configuration.
Save the “XML” configuration file on a disk with the Serial No. of the NSD570 rack and the No. of
the device (TPE 1 or TPE2) coded in the file name, e.g. HE501249_1_B0.XML.
Click on the link and choose Save this file to disk. This action saves the active configuration to
disk under the chosen name. All settings you have made and downloaded to the equipment will be
saved, including the manual entries (Jumper Settings, Rack Assembly) and also the information
that can only be read from the device (Device Information, Hardware and Firmware Versions).
B.17.5 Documentation
Create a printout of the active configuration data that was uploaded and saved to disk before (see
B.17.4).
Click on the link View Configuration in the Configuration menu and use the Print icon of your
browser to generate a handout of all settings and all available device information.
B.17.6 MAC Address

Each NSD570 module with an Ethernet interface is programmed with a MAC address. Verify that
the first three bytes of the MAC address are equal to 00:D0:93:xx:xx:xx.
For the modules G3LM/G3LMa and G3LS click on Status Upload to read the MAC address and
for the module G3LE click on Commissioning Info. With HMI570 “PC” version 1.47 or higher, the
MAC address display for G3LE is also available in the menu Status Upload.
B.17.7 Collect back tracing data

All components of the NSD570 system are marked with a barcode label including the type
designation and the manufacturer’s series number.
By collecting this data with a barcode reader and saving it into a project database (with the serial
“HE” No. of the rack as a reference), a back tracing of the system with all its modules can be
ensured. The barcode reader must be able to read the barcode 128 format.
Read the following barcodes from the back side of the rack:
- On the right side plate: G7BI, G1LA, G3LC, G1LB (module rack with basic components)
- From the right to the left: G3LA, G3LD, G3LE, G3LS, G3LR/G3LRa, G3LM/G3LMa
(interfaces plugged in the intended slots);
if the Digital Interface G3LD is equipped with an optional piggyback module (either E1/T1
interface G1LE or Optical Interface G1LO/G1LOa), read its barcode label that is located on
the soldering side of the module.
Read the following barcodes from the front side of the rack:
- Behind the blanking cover plate: G3LH, G3LI, G3LK (one or two modules)
- Optional Display Panel G1LC (if it is mounted instead of the blanking cover plate)
B.17.8 Mount covers

After collecting the barcode data, the Blanking Cover Plate or the optional Display Panel G1LC
must be screwed again on the front side of the rack (covering the power supply modules) and the
screening cover must be snapped on the back side of the rack.
NSD570 System Settings EN A1/A9 HE
Item to be Selected
No. Function Rack or programmed or alternative Remarks
module fitted or setting
A.1 General
A.2 Create a configuration for the [ ]

equipment using the HMI570
A.3 Check interfaces in the rack G7BI
TPE1 TPE2
A.3.1 Check position of interfaces [ ] [ ]
front back
A.3.2 Check presence of cover plates [ ] [ ]
A.4 Common settings for all types of

equipment NSD570
Analog/Digital/Ethernet
Unit 1 Unit 2
A.4.1 Power supply G3LH [ ] [ ]
G3LI [ ] [ ]
G3LK [ ] [ ]
Circuit breaker B9AS [ ] [ ] All voltages
except
Circuit breaker B9AV [ ] [ ] 72 – 250 VDC
A.4.2 Device identification

TPE1 TPE2
Station Name G3LA/D/E ____________ [ ] [ ]
HE Number G3LA/D/E ____________ [ ] [ ]
Device address G3LA/D/E ID= ____/____ [ ] [ ]
A.4.3 Operating mode of the equipment

TPE1 TPE2
Normal G3LA/D/E [ ] [ ] Default
1+1 G3LA/D/E [ ]
T-operation G3LA/D/E [ ]
Inverse T-operation G3LA/D/E [ ]
A.4.4 Unblocking
TPE1 TPE2
Unblocking Extra Delay G3LA/D/E ____/____ [ms] [ ] [ ]
Unblocking Pulse Duration G3LA/D/E ____/____ [ms] [ ] [ ]
A.4.5 Command outputs during link

failure TPE1 TPE2
Responding to channel failure

Command outputs are unaffected G3LA/D/E [ ] [ ] Default
Cmd. Outputs set to guard state G3LA/D/E [ ] [ ]
Cmd. Outputs retain in state G3LA/D/E [ ] [ ]
Direct = guard, others = command G3LA/D/E [ ] [ ]
Channel failure pick up time G3LA/D/E ____/____ [s] [ ] [ ]
Channel failure hold up time G3LA/D/E ____/____ [s] [ ] [ ]
Copyright 2002-2021 Hitachi Power Grids. All rights reserved. Form 1KHW000898M-EN
Item to be Selected
A.4.6 Synchronization of internal Real

Time Clock (RTC)
External Sync Pulse (per second) G3LC available [ ] Connector on G1LB
Ext. Synchronization Signal (GPS) G3LC type IRIG-B [ ] Connector on G1LB
TPE1 TPE2
A.4.7 Embedded Operation Channel G3LA/D/E enabled
(EOC) [ ] [ ]
TPE1 TPE2
A.4.8 Cyclic Loop Test Interval G3LA/D/E enabled
____/____ [h] [ ] [ ]
A.4.9 Propagation Time G3LA/D/E ____/____ [ms] [ ] [ ] Default = 0 ms
A.5 Settings for the analog line

interface
TPE1 TPE2 If connected to
A.5.1 Barrier transformers G3LA installed [ ] [ ] cables, pilot wires or
leased circuits
TPE1 TPE2
A.5.2 Connection to the AF G3LA [ ] [ ]
2-wire
communication circuits
4-wire [ ] [ ] Default
TPE1 TPE2
A.5.3 Analog channel bandwidth G3LA
Tx: _____ [Hz] [ ]
Rx: _____ [Hz] [ ]
Tx: _____ [Hz] [ ]
Rx: _____ [Hz] [ ]
TPE1 TPE2
A.5.4 Analog channel center frequency G3LA
Tx: _____ [Hz] [ ]
Rx: _____ [Hz] [ ]
Tx: _____ [Hz] [ ]
Rx: _____ [Hz] [ ]
No of cmds TPE1 TPE2

A.5.5 Analog operating mode G3LA
1 single tone [ ] [ ]
2 single tone [ ] [ ] Default
2 dual tone [ ] [ ]
3 dual tone [ ] [ ]
4 dual tone [ ] [ ]
TPE1 TPE2
A.5.6 Power boosting G3LA
____/____ [dB] [ ] [ ]
TPE1 TPE2
A.5.7 Unblocking threshold G3LA
___/___ [dBm0] [ ] [ ]
Item to be Selected
Signal levels: TPE1 TPE2

A.5.8 Signal and alarm levels G3LA
Tx: ____ [dBm] [ ]
Rx: ____ [dBm] [ ]
Tx: ____ [dBm] [ ]
Rx: ____ [dBm] [ ]
Alarm levels: TPE1 TPE2

G3LA
Tx: - ____ [dB] [ ]
Rx: ± ____ [dB] [ ]
Tx: - ____ [dB] [ ]
Rx: ± ____ [dB] [ ]
Impedance TPE1 TPE2

A.5.9 Manual jumper settings G3LA
Tx: 600 Ohm [ ] [ ] Default
Tx: > 1.5 kOhm [ ] [ ]
Rx: 600 Ohm [ ] [ ] Default
Rx: > 1.5 kOhm [ ] [ ]
A.6 Settings for the digital line

interface
A.6.1 Interface independent settings TPE1 TPE2
BER alarm threshold G3LD 1E-0_ / 1E-0_ [ ] [ ]

Digital Address Check G3LD enabled [ ] [ ]
Local address G3LD _____ / _____ [ ] [ ]
Remote address G3LD _____ / _____ [ ] [ ]
A.6.2 G.703 codirectional interface TPE1 TPE2
G.703 Tx Clock Sync G3LD None [ ] [ ]

on Rx Signal [ ] [ ] Default
A.6.3 RS-530 interface TPE1 TPE2
Interface data rate G3LD 56 kbps [ ] [ ]

64 kbps [ ] [ ] Default
Clock source for send data (SD) G3LD internal [ ] [ ] Default
external ST [ ] [ ]
Clock source for receive data (RD) G3LD internal [ ] [ ] Default
external RT [ ] [ ]
If no external ST is available: G3LD on RD [ ] [ ] Default
Rx Clock synchronization none [ ] [ ]
If no external RT is available: G3LD on RD [ ] [ ] Default
Tx Clock & TT synchronization none [ ] [ ]
Terminal Timing (TT) signal G3LD off [ ] [ ] Default
on [ ] [ ]
If two NSD570 in a link are operated G3LD Master [ ] [ ]
point-to-point (without MUX) Slave [ ] [ ]
Item to be Selected
A.6.4 E1 interface TPE1 TPE2
Receiver sensitivity G3LD/ Short haul [ ] [ ] Default

G1LE Long haul [ ] [ ]
Internal elastic Rx buffer size G3LD/ 1 Frame [ ] [ ]
G1LE 2 Frames [ ] [ ] Default
96 Bit [ ] [ ]
Bypass [ ] [ ]
Internal elastic Tx buffer size G3LD/ 1 Frame [ ] [ ]
96 Bit [ ] [ ]
Bypass [ ] [ ]
E1 Coding G3LD/ HDB3 [ ] [ ] Default
G1LE AMI [ ] [ ]
E1 Frame Format G3LD/ Double Frame [ ] [ ] Default
G1LE CRC4 Multi Fr. [ ] [ ]
E1 impedance G1LE 3 jumpers E1 [ ] [ ] Default
A.6.5 T1 interface TPE1 TPE2
Receiver sensitivity G3LD/ Short haul [ ] [ ] Default

G1LE Long haul [ ] [ ]
Internal elastic Rx buffer size G3LD/ 1 Frame [ ] [ ]
96 Bit [ ] [ ]
Bypass [ ] [ ]
Internal elastic Tx buffer size G3LD/ 1 Frame [ ] [ ]
96 Bit [ ] [ ]
Bypass [ ] [ ]
T1 Coding G3LD/ B8ZS [ ] [ ] Default
G1LE AMI [ ] [ ]
T1 Frame Format G3LD/ 4 Frames [ ] [ ] Default
G1LE Ext. Super Fr. [ ] [ ]
T1 impedance G1LE 3 jumpers T1 [ ] [ ]
A.6.6 Optical interface G1LO TPE1 TPE2
Laser output power (Optical Direct G3LD/ Short haul [ ] [ ] Default

Fiber or Optical FOX/OTERM only) G1LO Long haul [ ] [ ]
A.6.7 Optical interface G1LOa TPE1 TPE2
Automatic Laser Shutdown (ALS) G3LD/ off [ ] [ ] Default

G1LOa on [ ] [ ]
Clock Mode (Optical Direct Fiber G3LD/ Master [ ] [ ] Default
only) G1LOa Slave [ ] [ ]
A.6.8 Grounding the shield of optional TPE1 TPE2

connecting cables
Proper grounding at the cable tray G3LD/E Earth clip [ ] [ ]
G3LS/M
Item to be Selected
A.7 Settings for the Ethernet line

interface
A.7.1 Interface selection TPE1 TPE2
Selection switch in position G3LE X102 (RJ45) [ ] [ ] Default

X103 (SFP) [ ] [ ]
A.7.2 Interface settings (RJ45 interface TPE1 TPE2
only)
Auto negotiation G3LE manual [ ] [ ] Default
auto [ ] [ ]
Data Rate G3LE 100 Mbps [ ] [ ] Default
(for setting “manual” only) 10 Mbps [ ] [ ]
Duplex Mode G3LE Full Duplex [ ] [ ] Default
(for setting “manual” only) Half Duplex [ ] [ ]
A.7.3 Ethernet / IP / UDP settings TPE1 TPE2
Local IP address G3LE ___.___.___.___ [ ]

___.___.___.___ [ ]
Subnet Mask G3LE ___.___.___.___ [ ]
___.___.___.___ [ ]
Default Gateway G3LE ___.___.___.___ [ ]
___.___.___.___ [ ]
Remote IP address G3LE ___.___.___.___ [ ]
___.___.___.___ [ ]
TOS/DSCP and ECN G3LE __ & __ / __ & __ [ ] [ ]
VLAN Tagging G3LE disabled [ ] [ ] Default
enabled [ ] [ ]
802.1P VLAN ID (if enabled) G3LE ______ / ______ [ ] [ ]
802.1Q Priority (if enabled) G3LE ______ / ______ [ ] [ ]
UDP Port Teleprotection Packets G3LE ______ / ______ [ ] [ ]
UDP Port EOC Packets G3LE ______ / ______ [ ] [ ]
A.7.4 Channel supervision and alarm TPE1 TPE2
settings
Guard Packets Sending Interval G3LE [ms] ______ / ______ [ ] [ ]
Transmission Time Test Interval G3LE [ms] ______ / ______ [ ] [ ]
Transmission Time Warning / Alarm G3LE Low [ ] [ ]
Sensitivity Medium [ ] [ ] Default
High [ ] [ ]
Packet Loss Rate Alarm Threshold G3LE [%] ______ / ______ [ ] [ ]
A.7.5 Laser setting for optical SFP TPE1 TPE2
Automatic Laser Shutdown (ALS) G3LE off [ ] [ ] Default

on [ ] [ ]
A.7.6 WAN Password TPE1 TPE2
Status WAN Password G3LE Default [ ] [ ] Equipment alarm

New password [ ] [ ]
Item to be
No. Function Rack or programmed Selected alternative or setting Remarks
module or fitted
A.8 Settings for the individual

commands
A.8.1 Command Application Command A B C D E F G H

Not used G3LA/D/E TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Blocking G3LA/D/E TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Permissive Tripping G3LA/D/E TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Direct Tripping G3LA/D/E TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Not used G3LA/D/E TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Blocking G3LA/D/E TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Permissive Tripping G3LA/D/E TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Direct Tripping G3LA/D/E TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
A.8.2 Maximum Tx Input Command A B C D E F G H

Monitoring
Monitoring enabled G3LA/D/E TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Maximum trip duration [s] G3LA/D/E TPE 1 __ __ __ __ __ __ __ __
Monitoring enabled G3LA/D/E TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Maximum trip duration [s] G3LA/D/E TPE 2 __ __ __ __ __ __ __ __
A.8.3 Tx Input On-Delay Command A B C D E F G H

Delay before sending [ms] G3LA/D/E TPE 1 __ __ __ __ __ __ __ __
Delay before sending [ms] G3LA/D/E TPE 2 __ __ __ __ __ __ __ __
A.8.4 Transparent Tx Input and Rx Command A B C D E F G H

Output Duration
Tx Input enabled G3LA/D/E TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Tx Input enabled G3LA/D/E TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Rx Output enabled G3LA/D/E TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Rx Output enabled G3LA/D/E TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
A.8.5 Prolonged Tx Input and Rx Command A B C D E F G H

Output Duration
Tx Prolongation [ms] G3LA/D/E TPE 1 __ __ __ __ __ __ __ __
Tx Prolongation [ms] G3LA/D/E TPE 2 __ __ __ __ __ __ __ __
Rx Prolongation [ms] G3LA/D/E TPE 1 __ __ __ __ __ __ __ __
Rx Prolongation [ms] G3LA/D/E TPE 2 __ __ __ __ __ __ __ __
A.8.6 Limited Tx Input and Rx Command A B C D E F G H

Output Duration
Tx Limitation [ms] G3LA/D/E TPE 1 __ __ __ __ __ __ __ __
Tx Limitation [ms] G3LA/D/E TPE 2 __ __ __ __ __ __ __ __
Rx Limitation [ms] G3LA/D/E TPE 1 __ __ __ __ __ __ __ __
Rx Limitation [ms] G3LA/D/E TPE 2 __ __ __ __ __ __ __ __
Item to be
module or fitted
A.8.7 Fixed Tx Input and Rx Command A B C D E F G H

Output Duration
Tx Fixed Duration [ms] G3LA/D/E TPE 1 __ __ __ __ __ __ __ __
Tx Fixed Duration [ms] G3LA/D/E TPE 2 __ __ __ __ __ __ __ __
Rx Fixed Duration [ms] G3LA/D/E TPE 1 __ __ __ __ __ __ __ __
Rx Fixed Duration [ms] G3LA/D/E TPE 2 __ __ __ __ __ __ __ __
A.9 Settings for the relay

interface(s)
A.9.1 Configuration of the inputs Command A B C D E F G H

Mapping according setting G3LR TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Mapping according setting G3LS TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Mapping according setting G3LR TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Mapping according setting G3LS TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
A.9.2 Configuration of the solid Command A B C D E F G H

state and relay outputs
Cmd mapping acc. setting G3LR TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Cmd mapping acc. setting G3LS TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Cmd mapping acc. setting G3LR TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Cmd mapping acc. setting G3LS TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Slot N34 N40 N46 N52 N64 N70 N76 N84
Other signals acc. setting G3LR TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Other signals acc. setting G3LR TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
A.9.3 Nominal input voltage

G3LR
Input 1 G3LR Jumper plugs N34 N40 N46 N52 N64 N70 N76 N84
24 VDC … 48 VDC 1A, 1B [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
60 VDC … 110 VDC 1A, 1C [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
125 VDC … 250 VDC 1A, 1D [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] Default
Input 2 G3LR Jumper plugs N34 N40 N46 N52 N64 N70 N76 N84
24 VDC … 48 VDC 2A, 2B [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
60 VDC … 110 VDC 2A, 2C [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
125 VDC … 250 VDC 2A, 2D [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] Default
Item to be
module or fitted
G3LRa
Input 1 G3LRa Jumper plugs N34 N40 N46 N52 N64 N70 N76 N84
24 VDC 1A, 1B [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
48 VDC … 60 VDC 1A, 1C [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
120 VDC … 125 VDC 1A, 1D [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
220 VDC … 250 VDC 1A, 1E [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] Default
Input 2 G3LRa Jumper plugs N34 N40 N46 N52 N64 N70 N76 N84
24 VDC 2A, 2B [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
48 VDC … 60 VDC 2A, 2C [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
120 VDC … 125 VDC 2A, 2D [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
220 VDC … 250 VDC 2A, 2E [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] Default
A.9.4 Tripping of the inputs on a

contact basis N34 N40 N46 N52 N64 N70 N76 N84
Input 1 and Input 2 G3LR G1LR [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
mounted
A.9.5 Relay contacts

Relay 1 contacts G3LR ext. N34 N40 N46 N52 N64 N70 N76 N84
connecting
Normally open NO [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Normally closed NC [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Relay 2 contacts G3LR ext. N34 N40 N46 N52 N64 N70 N76 N84
connecting
Normally open NO [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
Normally closed NC [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
A.10 Settings for the GOOSE LAN

interface G3LS
TPE1 TPE2
A.10.1 GOOSE Interface
Configuration
Device identification G3LS N34 [ ] N64 [ ]
Station name G3LS ___________ ___________
HE Number G3LS ___________ ___________
Device address G3LS ____ ____
GOOSE LAN Interface G3LS
Automatic Laser Shutdown G3LS off [ ] [ ] Default
on [ ] [ ]
Number of Protection
Commands G3LS ____ ____
Ext. Sync. Signal (GPS) G3LS type IRIG-B [ ] [ ]
Item to be
module or fitted
TPE1 TPE2
A.10.2 IEC 61850 Configuration
SCL configuration file names G3LS
CID file name G3LS ___________ ___________
ICZ file name G3LS ___________ ___________
Local SCD-file name G3LS ___________ ___________
Remote SCD-file name G3LS ___________ ___________
Item to be Selected
A.11 Alarm settings

TPE1 TPE2
A.11.1 Alarm pick up and hold delays
Alarm pick up time G3LA/D/E ____/____ [s] [ ] [ ]
Alarm hold up time G3LA/D/E ____/____ [s] [ ] [ ]
A.11.2 Behavior in case of a failing

TPE1 TPE2
redundant power supply
Redundant Power Supply Failure G3LA/D/E HW Warning [ ] [ ]
HW Alarm [ ] [ ]
TPE1 TPE2
A.11.3 Alarm relay contacts G3LC ext. connecting
Normally open NO [ ] [ ]
Normally closed NC [ ] [ ]
TPE1 TPE2
A.11.4 Configuration of user alarms
User Alarm 1 G3LR acc. setting [ ] [ ]
A.12 Display Panel

Contrast setting of the LCD-module G1LC 16 steps step [ …. ] default: step 10
Backlight setting of the LCD-module G1LC 4 steps or OFF step [ …. ] default: step 3
Standby time of the display panel G1LC 1 … 60 minutes min. [ .… ] default: 10 min.
A.13 Management LAN Interface

IP address G3LM ___.___.___.___ [ ]
Subnet mask G3LM ___.___.___.___ [ ]
ABB Power Grids Switzerland Ltd HE
Archive No.: Doc. Rev.: Date:
Factory Settings and Routine Tests - M 2021-08-05
PGGA-CE4 2003-01-31 / A. Bemsel 2021-08-05 / M. Buhl - EN 1/2
Valid for: Derived from: Replaces: Classification-No.: Document No. / File:
- - - 1KHD608525ME Test Report
NSD570.doc
NSD570
Factory Settings and Routine Tests

According to Programming and Testing Instructions NSD570 1KHW000898ME
Project …………………………………………………
ABB Order No. …………………………………………………
Station …………………………………………………
Direction …………………………………………………
Contents:
NSD570 Printout Equipment Settings Pages 1 to ......
NSD570 System Test Report Pages B1 to B8
NSD570 List of used Test Instruments Page 1
……….. ……………………………………………………… Pages ...... to ......
Test conditions: Temperature range: 20 C to 35 C.
Basic test equipment:

PCCOM 1 cable (1:1 serial RS-232) One male, one female plug Sub-D, 9 pin
Oscilloscope BW  1 MHz Tektronix 2235 or similar
Optional test equipment:

Storage oscilloscope Fs  1 Ms/s Tektronix 2430A or similar
Test box for teleprotection equipment MK11 (ABB)
Optical attenuator ANDO AQ3150 or equivalent
Doc. Rev.: Language: Page:
NSD570 System Test Report M EN 2/2 HE
Notes:
 • Please refer to document "Compatibility Requirements for NSD570" (1KHW000902) for compatibility
between software HMI570, firmware "Analog", firmware "Digital", firmware “Ethernet” and hardware of
NSD570
Designation Meaning
( ..….) Measured value
G3LR Module type
RTC Real time clock
Rx Receiver
Tx Transmitter
Safety Instructions
Please have a look in the Programming and Testing Instructions <NSD570> 1KHW000898.
Copyright 2002-2021 Hitachi Power Grids. All rights reserved. Form 1KHD608525M-EN
Rev.: Doc. Rev.: Language: Page:
NSD570 System Test Report M EN B1/B8 HE
Test Permissible Test

No. Test procedure Test point value Units result
B.1 General
B.1.1 Test conditions Temperature range 20 … 35 C [ ]
B.1.2 Visual checks before powering

the equipment Unit 1 Unit 2
Correct wiring of power supply Unit 1 and Unit 2 polarity ok [ ] [ ]
Correct wiring of protective earth G7BI PE wired [ ]
Equipment connected to adequate Via circuit breaker [ ]
voltage source B9AS or B9AV
B.2 Check power supply

Unit 1 Unit 2
DC battery voltage G3LH (+ to -) 38.4 … 300 V DC [ ] [ ]
G3LI (+ to -) 19.2 … 72 [ ] [ ]
G3LK (+ to -) 88.0 … 300 [ ] [ ]
AC mains voltage G3LH (L to N) 85.0 … 264 V AC [ ] [ ]
G3LK (L to N) 93.0 … 253 [ ] [ ]
LED indication LED Unit 1 and Unit 2 Green LED [ ] [ ]
on the front panel
B.3 Preparing the equipment TPE1 TPE2

B.3.1 Connecting to the equipment Check communication TPE1 / TPE2 [ ] [ ]
between PC & NSD570
B.3.2 Download the configuration Download successful HExxxxxxAy.XML [ ] [ ]
B.3.3 Preparing the system for testing Set time and date no RTC alarm [ ] [ ]
Update jumper settings HMI570 [ ] [ ]
Update rack assembly HMI570 [ ] [ ]
Establish link Guard LED [ ] [ ]
TPE1 TPE2
B.4 Change configuration If necessary
[ ] [ ]
B.5 Remarks for T-operation Adjusting level Analog T [ ]

Measuring T0 Normal T [ ]
Measuring T0 Inverse T [ ]
B.6 Configure Real Time Clock (RTC) TPE1 TPE2
B.6.1 Setting real time clock Check PC time / date Actual / exact [ ]
Set time and date [ ] [ ]
Get time and date Actual / exact [ ] [ ]
B.6.2 Testing external real time clock

synchronization (if available) TPE1 TPE2
External sync pulse only Set time and date [ ] [ ]
External GPS signal (IRIG-B) Adjust PC time / date Wrong time [ ] [ ]
Adjust PC time / date Actual / exact [ ] [ ]

B.7 Analog line interface

B.7.1 Transmitter TPE1 TPE2
Guard level G3LA; X100/1-2 [ setting ± 2 ] dBm [ ] [ ]
Command level G3LA; X100/1-2 [ setting ± 2 ] dBm [ ] [ ]
If connected to PLC PLC protection input Max. level dBm ____ ____
-> reduce level setting if necessary G3LA; X100/1-2 measure level dBm (…....) (…....)
B.7.2 Power boosting / Boost output
Boost output activation G3LA; X100/5-6 with cmd. [ ] [ ]
B.7.3 Receiver
B.8 Digital line interface
B.8.1 Transmitter / Receiver TPE1 TPE2

Communication established G3LD/G1LE/G1LO/ acc. interface [ ] [ ]
G1LOa
B.8.2 Optical output power / optical
receiver sensitivity
G1LO TPE1 TPE2
Output power (Optical Direct Fiber G3LD/G1LO; X701/Tx [ -22 … -17 ] dBm (…....) (…....)
or Optical OTERM/OPTIF only) (short haul)
G3LD/G1LO; X701/Tx [ -5 … -1 ] dBm (…....) (…....)
(long haul)
Max. attenuation (Optical Direct G3LD/G1LO; X701/Rx > 25 dB (…....) (…....)
Fiber or Optical OTERM/OPTIF (long haul)
only)
G1LOa
Output power TPE1 TPE2
• 2 Mbps, 850 nm, MM, 1 km G3LD/G1LOa; X701/Tx
with 50/125 µm fiber [ -23 … -11 ] dBm (…....) (…....)
with 62.5/125 µm fiber [ -19 … -11 ] dBm (…....) (…....)
• 2 Mbps, 1310 nm, SM, 30 km G3LD/G1LOa; X701/Tx [ -15 … -8 ] dBm (…....) (…....)
• 2 Mbps, 1310 nm, SM, 60 km G3LD/G1LOa; X701/Tx [ -5 … 0 ] dBm (…....) (…....)
• 2 Mbps, 1550 nm, SM, 120 km G3LD/G1LOa; X701/Tx [ 0 … 5 ] dBm (…....) (…....)
• 2 Mbps, CWDM, SM, 180 km G3LD/G1LOa; X701/Tx [ 5 … 8 ] dBm (…....) (…....)
[ ] (1550 nm) [ ] ( ……... nm)
Receiver sensitivity TPE1 TPE2
• 2 Mbps, 850 nm, MM, 1 km G3LD/G1LOa; X701/Rx -32 dBm (…....) (…....)
• 2 Mbps, 1310 nm, SM, 30 km G3LD/G1LOa; X701/Rx -34 dBm (…....) (…....)
• 2 Mbps, 1310 nm, SM, 60 km G3LD/G1LOa; X701/Rx -34 dBm (…....) (..…..)
• 2 Mbps, 1550 nm, SM, 120 km G3LD/G1LOa; X701/Rx -35 dBm (…....) (…....)
• 2 Mbps, CWDM, SM, 180 km G3LD/G1LOa; X701/Rx -45 dBm (…....) (…....)
[ ] (1550 nm) [ ] ( ……... nm)

B.8.3 Address check TPE1 TPE2
Change device address G3LD/G1LE/G1LO/ Local alarm [ ] [ ]

G1LOa
B.9 Ethernet line interface

Communication established G3LE acc. interface [ ] [ ]
B.9.2 Optical output power / optical (if optical SFP is used)
• 100 Mbps, 850 nm, MM, 0.5 km G3LE; X103/Tx (50 µm) [ -23 … -11 ] dBm (…...) (…...)
• 100 Mbps, 1310 nm, MM, 0.5 km G3LE; X103/Tx (50 µm) [ -23.5 ... -14 ] dBm (…...) (…...)
• 100 Mbps, 1310 nm, SM, 30 km G3LE; X103/Tx [ -15 … -8 ] dBm (…...) (…...)
• 100 Mbps, 850 nm, MM, 0.5 km G3LE; X103/Rx -32 dBm (…...) (…...)
• 100 Mbps, 1310 nm, MM, 0.5 km G3LE; X103/Rx -31 dBm (…...) (…...)
• 100 Mbps, 1310 nm, SM, 30 km G3LE; X103/Rx -34 dBm (…...) (…...)
B.10 1+1 Operation mode (if used) TPE1 TPE2

No failure Status upload TPE 1 active [ ] [ ]
Main line interface link alarm Status upload TPE 2 active [ ] [ ]
Main & stand-by line interface link Status upload TPE 1 active [ ] [ ]
alarm
Main line interface hardware alarm Status upload TPE 2 active [ ]
Stand-by line interface hardware Status upload TPE 1 active [ ]
alarm
B.11 GOOSE LAN interface

Upload alarms G3LS Depending on [ ] [ ]
ext. equipment
B.11.2 Optical output power / optical (if optical SFP is used)

• 100 Mbps, 850 nm, MM, 0.5 km G3LS; X103/Tx (50 µm) [ -23 … -11 ] dBm (…...) (…...)
• 100 Mbps, 1310 nm, MM, 0.5 km G3LS; X103/Tx (50 µm) [ -23.5 ... -14 ] dBm (…...) (…...)
• 100 Mbps, 1310 nm, SM, 30 km G3LS; X103/Tx [ -15 … -8 ] dBm (…...) (…...)
• 100 Mbps, 850 nm, MM, 0.5 km G3LS; X103/Rx -32 dBm (…...) (…...)
• 100 Mbps, 1310 nm, MM, 0.5 km G3LS; X103/Rx -31 dBm (…...) (…...)
• 100 Mbps, 1310 nm, SM, 30 km G3LS; X103/Rx -34 dBm (…...) (…...)

B.12 Relay interfaces G3LR
B.12.1 Inputs
Input 1 G3LR U1, see N34 N40 N46 N52
Activate Input 1 (T…/1) – (T.../2) System settings V DC [ ] [ ] [ ] [ ]
Check LED Input 1 LED Input 1 ON N64 N70 N76 N84
[ ] [ ] [ ] [ ]
Input 2 G3LR U1, see N34 N40 N46 N52

Activate Input 2 (T…/3) – (T.../4) System settings V DC [ ] [ ] [ ] [ ]
Check LED Input 2 LED Input 1 ON N64 N70 N76 N84
[ ] [ ] [ ] [ ]
B.12.2 Outputs
Enforce action for G3LR U1, see N34 N40 N46 N52
Output 1 (T…/5) – (T.../6) System settings V DC [ ] [ ] [ ] [ ]
Check Output 1 closed N64 N70 N76 N84
Check LED Output 1 LED Output 1 ON [ ] [ ] [ ] [ ]
Output 2 (T…/7) – (T.../8) System settings V DC [ ] [ ] [ ] [ ]
Check Output 2 closed N64 N70 N76 N84
Check LED Output 2 LED Output 2 ON [ ] [ ] [ ] [ ]
Relay 1 (T…/9) – (T.../10) System settings V DC [ ] [ ] [ ] [ ]
Check Relay 1 closed N64 N70 N76 N84
Check LED Relay 1 LED Relay 1 ON [ ] [ ] [ ] [ ]
Relay 2 (T…/12) – (T.../13) System settings V DC [ ] [ ] [ ] [ ]
Check Relay 2 closed
N64 N70 N76 N84
Check LED Relay 2 LED Relay 2 ON [ ] [ ] [ ] [ ]

B.13 System alarm indication To be measured only if

requested TPE1 TPE2
Activate alarm by interrupting LEDs "Local", "Receive" LED to be ON [ ] [ ]

receive line connection
State of alarm relay after G3LC; X102/1-2 (TPE1) changed [ ] [ ]
programmed delay and X102/6-7 (TPE2)
Deactivate alarm by restoring the LEDs "Local", "Receive" LED to be [ ] [ ]
link OFF

B.14 System functions
B.14.1 NSD570 loop test TPE1 TPE2
Check actual TLink HMI570 / Loop Test Button

transmission time < 1.3*T0 ms (…...) (…...)
B.14.2 Command
transmission time TPE1 TPE2 TPE1 TPE2
Command A Terminal,
Tx command A [ ] (T34/1)–(T34/2) (T64/1)–(T64/2) Refer to manual
[ ] (T…/..)–(T…/..) (T…/..)–(T…/..) for rated value ms ____ ____
Rx command A [ ] (T34/5)–(T34/6) (T64/5)–(T64/6)
[ ] (T…/..)–(T…/..) (T…/..)–(T…/..) Mean value  T0 ms (…...) (…...)
Command B Terminal,
Tx command B [ ] (T34/3)–(T34/4) (T64/3)–(T64/4) Refer to manual
Rx command B [ ] (T34/7)–(T34/8) (T64/7)–(T64/8)
Command C Terminal,
Tx command C [ ] (T40/1)–(T40/2) (T70/1)–(T70/2) Refer to manual
Rx command C [ ] (T40/5)–(T40/6) (T70/5)–(T70/6)
Command D Terminal,
Tx command D [ ] (T40/3)–(T40/4) (T70/3)–(T70/4) Refer to manual
Rx command D [ ] (T40/7)–(T40/8) (T70/7)–(T70/8)
Command E Terminal,
Tx command E [ ] (T46/1)–(T46/2) (T76/1)–(T76/2) Refer to manual
Rx command E [ ] (T46/5)–(T46/6) (T76/5)–(T76/6)
Command F Terminal,
Tx command F [ ] (T46/3)–(T46/4) (T76/3)–(T76/4) Refer to manual
Rx command F [ ] (T46/7)–(T46/8) (T76/7)–(T76/8)
Command G Terminal,
Tx command G [ ] (T52/1)–(T52/2) (T84/1)–(T84/2) Refer to manual
Rx command G [ ] (T52/5)–(T52/6) (T84/5)–(T84/6)
Command H Terminal,
Tx command H [ ] (T52/3)–(T52/4) (T84/3)–(T84/4) Refer to manual
Rx command H [ ] (T52/7)–(T52/8) (T84/7)–(T84/8)

B.14.3 Prolonged Rx Output To be measured TPE1 TPE2

Duration only if requested
Rx Command A See above Setting ± 0.25 x T0 ms (………..) (………..)
Rx Command B See above Setting ± 0.25 x T0 ms (………..) (………..)
Rx Command C See above Setting ± 0.25 x T0 ms (………..) (………..)
Rx Command D See above Setting ± 0.25 x T0 ms (………..) (………..)
Rx Command E See above Setting ± 0.25 x T0 ms (………..) (………..)
Rx Command F See above Setting ± 0.25 x T0 ms (………..) (………..)
Rx Command G See above Setting ± 0.25 x T0 ms (………..) (………..)
Rx Command H See above Setting ± 0.25 x T0 ms (………..) (………..)
B.15 Display Panel TPE1 TPE2
Connecting to the G1LC <-> TPE 1/2 Counter readings [ ] [ ]

device
Return information TPE 1/2 -> G1LC Loop Test time [ ] [ ]
Reset the display panel G1LC “Back” ABB intro [ ]
B.16 LAN Interface TPE1 TPE2
B.16.1 Connecting to the HMI570 -> G3LM Configuration [ ]

device with serial upload for
cable documentation
B.16.2 Optical output power / (if opt. SFP is used)
optical receiver
sensitivity
100 Mbps, ______ nm, [ ]
____ Mode, _____ km
Output power G3LM; X103/Tx [ ____ … ____ ] dBm [ ]
Receiver sensitivity G3LM; X103/Rx [ ____ … ____ ] dBm [ ]
B.16.3 Test HMI570 G3LM <-> TPE 1/2 TPE configuration [ ] [ ]

Management LAN upload successful
functionality
B.17 Concluding works TPE1 TPE2
B.17.1 Reset counters

Reset all counters HMI570 All counters = 0 [ ] [ ]
B.17.2 Clear event recorder
Clear event recorder HMI570 1 event only [ ] [ ]
B.17.3 Manual reset
Reset device HMI570 Reset / start up [ ] [ ]
B.17.4 Save the initial
configuration data ex
works
Upload/save config. HMI570 HExxxxxxBy.XML [ ] [ ]
B.17.5 Documentation
View/print configuration HMI570 # printout pages (………..) (………..)

B.17.6 MAC Address TPE1 TPE2

Verify MAC Address HMI570 00:D0:93:xx: xx: xx [ ] [ ]
G3LE /Commissioning Info
or /Status Upload
Verify MAC Address HMI570 00:D0:93: xx: xx: xx [ ] [ ]
G3LS /Status Upload
Verify MAC Address HMI570 00:D0:93: xx: xx: xx [ ] [ ]
G3LM/G3LMa /Status Upload
B.17.7 Collect back tracing Barcode reader G7BI, G1LA, G3LC, [ ] [ ]
G1LB, G3LA, G3LD,
data G3LE, G3LS,
G3LR/G3LRa,
G3LM/G3LMa G1LC,
G1LE, G1LO/G1LOa,
G3LH, G3LI, G3LK
B.17.8 Mount covers Rack G7BI Front and back [ ] [ ]
CUSTOMER ACCEPTANCE
The acceptance form is completed by Hitachi ABB and the customer representative once all tests detailed in
this document have been performed successfully. Customer acceptance form is part of the test protocol.
Testfield ABB Power Grids Switzerland Ltd

Department PGGA-CE4
Date: __________________________________
Test Engineer: __________________________________
Supervisor: __________________________________
FAT Witnessed
FAT Date: __________________________________
Date Company Name Signature
Commissioning Instructions: < NSD570 > - J 2021-08-05
PGGA-PT1 2012-09-04 H.J. Maag 2021-08-05 M. Buhl - EN 1/12
- - - - 1KHW000900JE Commissioning
of NSD570.doc
Commissioning Instructions: < NSD570 >
This document describes commissioning of the teleprotection equipment NSD570 Analog, NSD570 Digital
(including the optical interface for the NSD570 Digital) and NSD570 Ethernet.
Contents:
C Commissioning Instructions for the NSD570 Equipment. ............................ 3

C.1 General......................................................................................................... 3
C.2 Check power supply ..................................................................................... 4
C.3 Preparing the equipment .............................................................................. 4
C.4 Change configuration ................................................................................... 5
C.5 Remarks for T-operation .............................................................................. 5
C.6 Configure Real Time Clock (RTC) ............................................................... 6
C.7 Analog line interface..................................................................................... 6
C.8 Digital line interface ...................................................................................... 7
C.9 Ethernet line interface .................................................................................. 8
C.10 1+1 Device operation mode ......................................................................... 9
C.11 GOOSE LAN interface ................................................................................. 9
C.12 System alarm indication ............................................................................. 10
C.13 System functions ........................................................................................ 10
C.14 Display Panel ............................................................................................. 11
C.15 Management LAN Interface ....................................................................... 11
C.16 Concluding works ....................................................................................... 11
NSD570 Commissioning Report ................ Refer to document 1KHD608528
J EN 2/12 1KHW000900-EN

PC  COM 1 cable (1:1 serial RS-232) One male, one female plug Sub-D, 9 pin
Oscilloscope bandwidth  1 MHz Tektronix 2235 or similar
Optional test equipment

Test box for teleprotection equipment MK11 or equivalent
Modem tester DT-24 (Acterna) or equivalent
RS-232 interface tester DV-24 (Acterna) or equivalent
Notes:

“Ethernet”, firmware “GOOSE”, firmware “Management” and hardware of NSD570.
Designation Meaning

G3LR Module type
RTC Real Time Clock
Rx Receiver
Tx Transmitter
J EN 3/12 1KHW000900-EN
C Commissioning Instructions for the NSD570 Equipment.
C.1 General
Some of the tests for the NSD570 system can be done with assistance of the HMI570 user
interface program. For example: the transmission time of one direction can be verified with a
manually initiated loop test, the result is immediately displayed on screen.
The guard signal of the NSD570 Analog version is modulated to also accommodate an Embedded
Operation Channel (EOC). As a result, the level of the guard signal changes slightly but
continuously. Its exact level can therefore only be measured, if the EOC is switched off by means
of the HMI570.
C.1.1 Test conditions

Temperature range: -5 C to 45 C.
terminals, Sub-D and RJ45 sockets) or at the terminals and sockets of the optional connecting
cables.
C.1.2 Visual checks before powering the equipment


Caution If the protective system is already in use, open the connections to it

while commissioning the NSD570.
Open the isolating terminals of the optional external connecting cables in the
local and in the remote station or interrupt the direct wire connection to the
equipment if no connecting cables are used.
J EN 4/12 1KHW000900-EN
C.2 Check power supply

Check the auxiliary supply voltage at the inputs of the power supply module G3LH, G3LI or G3LK.
Following input ranges have to be considered:
• G3LH 48 VDC to 250 VDC (± 20%) or 100 VAC to 240 VAC (-15%, +10%), 50/60 Hz
• G3LI 24 VDC to 60 VDC (± 20%)
• G3LK 110 VDC to 250 VDC (± 20%) or 110 VAC to 230 VAC (-15%, +10%), 50/60 Hz
In case of dual (redundant) power supply, the supply voltage for both modules must be checked.
Two LEDs on the front panel indicate the status of the power supply modules (green = Ok, red =
fail, dark = not assembled).
C.3 Preparing the equipment

Follow the steps below for connecting to the equipment, uploading the configuration and preparing
the system for commissioning.
C.3.1 Connecting to the equipment

1. Start the HMI570, log in and connect to the equipment as described in the Operating
Instructions, 1KHW000890, section 4, section "Communication to the NSD570".
2. If no configuration was downloaded to the systems in the rack before, make sure that no
connection is made to the RS-485 station bus interface at the rear of the rack while connecting
the equipment with the default device address.
3. Connect the equipment using the default device addresses:
Type “241” in the Local Device Address entry field when you want to connect to the line
interface in the left rack half (TPE 1); type “246” in the Local Device Address entry field when
you want to connect to the line interface in the right rack half (TPE 2). Use default device
addresses “242” for GOOSE Interface G3LS in TPE 1 and “247” for GOOSE Interface G3LS in
TPE 2. Use default device address “250” for Management Interface G3LM in TPE 2. This
method with the default addresses can also be used to determine the configured device
address of the systems in a rack (not having a RS-485 connection to the local station bus!).
4. After setting of all (unique!) device addresses of the NSD570 systems that are supposed to be
connected to the local station bus, the corresponding wires can be reconnected to the RS-485
interface terminals.
C.3.2 Upload the configuration

5. In the Configuration menu, click on Upload Configuration. With View Configuration you
can see the uploaded configuration including Device Information, Hardware Versions and
Firmware Versions (which are not configurable but readable from the device).
In case of configuration parameters have to be changed, refer to the Operating Instructions
NSD570, section "Configuration and Settings" and to the document "Programming and
Testing Instructions" in the annex of the manual.
If the firmware has to be updated, refer of the Operating Instructions NSD570, section "User
Interface Program" and to the document "Firmware Download Description" in the annex of the
manual. Make sure that both devices in a link have the same firmware version!
C.3.3 Preparing the system for testing

6. Synchronize the internal time and date of the NSD570 system to your local PC/notebook time
information: click on the link Set Time and Date in the Maintenance menu (see C.6). A
message will appear when the task was sent successfully.
Note: this has initially to be done so that no alarms from the RTC will appear later on.
If an external time information signal is connected to the synchronization inputs of the
equipment rack, the internal clock has not to be set but to be checked using the Get Time and
Date link in the Maintenance menu.
J EN 5/12 1KHW000900-EN
7. Check whether the Jumper Settings in the Configuration menu correspond to the actual
requirements. If not, update the entries for the Analog Interface (if plugged), for the E1/T1
Interface (if plugged) and for the Relay Interfaces, save the configuration to disk, download it
and reset the equipment.
8. The same as described in the previous step applies also for the Configuration menu item
Rack Assembly - edit the rack assembly list if it does not represent the current state.
C.4 Change configuration

Instructions NSD570, section "Configuration and Settings" or to the document "Programming and
Testing Instructions".
It may be necessary to change parameters temporarily only (e.g. switching off the EOC in the
NSD570 Analog for measuring the exact guard level). They have to be set to the original entries
again after the tests have been concluded.
If the system does not work properly after downloading the modified configuration and after the
manual reset has been performed, use the link Previous Configuration in the Maintenance menu
to switch back to the last configuration, which will properly work as before, after resetting the
equipment again.
C.5 Remarks for T-operation

NSD570 Analog in T-operation:
When a link with NSD570 Analog in T-operation has to be commissioned, the preparation has to be
done as follows:
- Adjust transmitter level at both outer stations of the T-ed line
- Adjust receiver level at both devices in the T-station
- Adjust transmitter level at both devices in the T-station
- Adjust receiver level at both outer stations of the T-ed line
Normal T-operation mode:
Measure the transmission time:
- The T-ed-configuration can be regarded as two individual links (outer station A <-> T-station
and outer station B <-> T-station). The transmission time can now be measured as in case of
a standard link (i.e. the commands have to be looped on a contact basis at the remote site if
the transmission time is measured from the local station).
Pay attention to the fact that in the T-station the command inputs and outputs have to be
connected in parallel directly at the relay interfaces or at the isolating terminals.
- Measure the transmission time from outer station A to B and vice-versa according C.13.3 of
this Commissioning Instructions.
Inverse T-operation mode:
Measure the transmission time:
- The T-ed-configuration cannot be regarded as two individual links (outer station A <-> T-
station and outer station B <-> T-station). The transmission time can only be measured from
A to T and from B to T. Pay attention to the fact that in the T-station the command inputs
have to be connected in parallel and the outputs have to be connected in series directly at
the relay interfaces or at the isolating terminals.
- Measure the transmission time from outer station A to T, respectively from outer station B to
T according C.13.3 of this Commissioning Instructions.
J EN 6/12 1KHW000900-EN
C.6 Configure Real Time Clock (RTC)

The internal real time clock (RTC; mounted on the line interfaces) has to be set to the actual date
and time for proper operation of the event recorder.
If a GOOSE LAN interface G3LS and/or a Management LAN interface G3LM is available in the
rack, also set the RTC correctly on these modules for accurate timestamping of the corresponding
services (e.g. published GOOSE frames, user activity logging).
C.6.1 Setting real time clock

1. Check if the time and date of your PC is exact.
2. Setting the date and time using the HMI570: click on the link Set Time and Date in the
Maintenance menu, the RTC will be adjusted to your PC time and date.
3. Click Get Time and Date in the Maintenance menu, the date and time displayed on screen
should be the same as that of your PC.
C.6.2 Testing external real time clock synchronization (if available)

The external synchronization - either a signal with a pulse each second or a signal having IRIG-B
format or both - has to be connected to the corresponding G3LC inputs (connector X103 on supply
backplane type G1LB or terminals of the external connecting cable for G1LB, if used).
a) If only an external sync pulse (each second) is available:
Set the RTC according C.6.1
b) If an external GPS signal having IRIG-B format is available:
Set the time on the PC running HMI570 a few hours back/forward.
Click on the link Set Time and Date in the Maintenance menu, the RTC would normally be
adjusted to your PC time and date.
Click Get Time and Date in the Maintenance menu, the date and time displayed on screen
should not be the same as that of your PC but is the exact time as provided by the GPS
receiver.
Set the time on the PC back to the exact time.
C.7 Analog line interface

The frequency of the guard and trip tones in the used channel cannot be easily determined and
also not be viewed by the HMI570. They depend on the channel bandwidth, the center frequency
and the analog operating mode. It is therefore recommended to measure signal levels with a
broadband level meter (to a reference of 600 Ohm), assuring that no other signals are existent on
the line outside the NSD570 channel. Alternatively, a selective level meter with peak level search
can be used.
For calculation of guard and trip frequencies please refer to the Operating Instructions NSD570.
C.7.1 Transmitter
Measure the guard level that is fed into the 600 Ohm line (for this measurement the EOC in the
local station has to be switched off):
- Measured guard level = [ Tx level according setting ± 2 ] dBm
Measure the command level that is fed into the 600 Ohm line (for this measurement, a command
signal has to be injected at the command inputs, the boost ratio has to be set to 0 dB):
- Set the boost ratio to 0 dB
- Measure Single Tone command level = [ Tx level according setting ± 2 ] dBm
- Measure Dual Tone command level = [ Tx level according setting - 3 dB ± 2 ] dBm
- Set the boost ratio back to the initial value
J EN 7/12 1KHW000900-EN
C.7.2 Power boosting / Boost output

Measure the boosted command level that is fed into the 600 Ohm line (for this measurement, a
command signal has to be injected at the command inputs; boost ratio = BR according setting):
- Measure Single Tone command level = [ Tx level according setting + BR ± 2 ] dBm
- Measure Dual Tone command level = [ Tx level according setting - 3 dB + BR ± 2 ] dBm
If the NSD570 is connected to a PLC equipment, it may be possible that the boosted command
level - due to its tolerance range of ± 2 dB - overmodulates the PLC amplifier. Therefore the signal
level has to be reduced to the maximum level that is allowed at the protection input of the PLC
equipment.
Check that the boost output contact is activated as long as a command is injected (this measure-
ment is only necessary if the contact is really needed, e.g. if connected to a PLC equipment):
- The boost output is closed as long as a command is transmitted on the line
C.7.3 Receiver
Measure the guard level that is received at the 600 Ohm line input (for this measurement the EOC
in the remote station has to be switched off):
- Measured guard level = [ Rx level according setting ± 2 ] dBm
C.8 Digital line interface
C.8.1 Transmitter / Receiver

There are no special measurements foreseen for the digital line interface. Nevertheless, the
settings made for the chosen interface type (G.703, RS-530, E1, T1, Optical) should be verified
with the actual used communication equipment (whether timing, synchronization, buffering, coding
and formats match the best possible way). This can be checked and optimized for example by
monitoring the BER and the manual loop test time for different settings (click on the link Status /
Alarm in the main menu and Upload Status afterwards).
C.8.2 Optical output power / optical received power
G1LO
The optical power meter must be sensitive to a wavelength of 1310 nm for the Optical Direct Fiber
and the Optical OTERM/OPTIF interface. A single mode adapter cable has to be used for
connecting the power meter to G1LO.
The optical output power is measured for the actual setting, short haul or long haul:
- Measured output power short haul = [ -22 … -17 ] dBm
- Measured output power long haul = [ -5 … -1 ] dBm
The following optical received power shall be measured:
- Measured received power = [ -36 … -1 ] dBm
J EN 8/12 1KHW000900-EN
G1LOa
for connecting the power meter to G1LOa.
- Measured output power with 850 nm, MM 50/125 µm, 1 km SFP = [ -23 … -11 ] dBm
- Measured output power with 850 nm, MM 62.5/125 µm, 1 km SFP = [ -19 … -11 ] dBm
- Measured output power with 1310 nm, SM, 60 km SFP = [ -5 … 0 ] dBm
- Measured output power with 1550 nm, SM, 120 km SFP = [ 0 … 5 ] dBm
- Measured output power with CWDM (1550 nm), SM, 180 km SFP = [ 5 … 8 ] dBm
- Measured received power with 850 nm, MM, 1 km SFP = [ -32 … -3 ] dBm
- Measured received power with 1310 nm, SM, 30 km SFP = [ -34 … 0 ] dBm
- Measured received power with 1310 nm, SM, 60 km SFP = [ -34 … -3 ] dBm
- Measured received power with CWDM (1550 nm), SM, 180 km SFP = [ -45 … -10 ] dBm
C.9 Ethernet line interface

There are no special measurements foreseen for the Ethernet line interface. Nevertheless, the
settings on local and remote side should be verified. The remote IP address of the local interface
must match the local IP address of the remote interface and vice-versa. The UPD port numbers
must match as well as the settings for the Guard Packets Sending Interval and the Transmission
Time Test Interval. Furthermore, the WAN Password must match on both sides.
If VLAN Tagging is enabled, the VLAN ID must be the same as well.
In order to set the correct Propagation time, it is necessary to connect with a computer to the
remote Ethernet Line interface and send a ping to it. This has to be done when the used IP network
is not loaded (i.e. no or only low traffic). The measured time divided by 2 must be set as
propagation time.
The connection is established properly after both devices are connected to the network, all LED are
green and no alarm is risen by means of the HMI570.
C.9.2 Optical output power / optical receiver sensitivity (only if optical SFP is used)
for connecting the power meter to G3LE.
- Measured received power with 850 nm, MM, 0.5 km SFP = [ -32 … -3 ] dBm
J EN 9/12 1KHW000900-EN
C.10 1+1 Device operation mode

A 1+1 link can be tested for proper switchover in fault state when performing the following steps:
- Run a redundant 1+1 link without any alarms and make sure both line interfaces in one
NSD570 rack receive Guard
disappear
disappear
C.11 GOOSE LAN interface

There are no special measurements foreseen for the GOOSE LAN interface. GOOSE message
transfer can only be tested by means of external IEDs or dedicated test equipment. Testing of
G3LS is supported by commissioning features which are described in the NSD570 operating
instructions, section 3.5.19. “Test facilities for the GOOSE LAN Interface”.
If G3LS is configured correctly and external equipment provides the expected GOOSE
communication there should not be any alarm on the module. In case of missing external
equipment there should not be more than one alarm pending, namely “GOOSE Communication
Failed”. Otherwise the configuration of G3LS needs to be verified.
C.11.2 Optical output power / optical receiver sensitivity (only if optical SFP is used)
The optical power meter must be sensitive to the wavelength of the installed SFP. Since G3LS is
designed for local applications within a substation the use of multi-mode fibers and SFP is
adequate.
J EN 10/12 1KHW000900-EN
C.12 System alarm indication

The system alarm may be triggered by interrupting the connection to the line interface
(disconnecting of at least the input = receiver circuit). After the programmed delay time the
corresponding system alarm relay on G3LC operates.
Check that the relay output is changing its state (precise measurement of the programmed alarm
delay time is not necessary).
Now restore the connection to the line interface. The alarm LEDs will immediately go off and the
relay output will change its state after the programmed delay time.
C.13 System functions
C.13.1 Transmission Channel

Check the transmission channel quality: measure the actual SNR/BER/PLR by clicking on the
Upload Status link in the Status / Alarm menu.
C.13.2 NSD570 loop test

The NSD570 is tested by issuing a loop test via HMI570 or by pressing the "Loop Test" button on
the front panel of the module rack.
In the Maintenance menu click on the link Manual Loop Test.
If the loop test is successful, the "Trip" LED on the front panel will light up for three seconds and a
message will appear on the PC screen indicating the measured loop test time for one direction
(TLink).
The transmission time of the loop test depends on the chosen bandwidth for the NSD570 Analog,
the used interface type of the NSD570 Digital, as well as - for both types of devices - on the
settings for the command application (the loop test is always transmitted as the command
configured for the highest requirements regarding security) and on the delay introduced by the
communication link (e.g. PLC or Ethernet/IP network).
C.13.3 Command transmission time

Check the transmission time of the NSD570 commands over the link.
Activate the command inputs by injecting an appropriate tripping voltage or by using an external
contact only, if the module G1LR (internal tripping voltage 24 VDC) is mounted on the Relay
Interface G3LR. Check the command outputs by means of an auxiliary tripping voltage (of the
same level as used for the command inputs) and an external current limitation.
1. Connect to the remote equipment and start the remote test mode (Commissioning menu ->
Start Remote Test Mode).
2. Transmit at few commands with a command / pause duration of about 100 ms / 1000 ms and
measure the actual transmission time of the looped command.
3. After measuring the transmission time the remote test mode has to be disabled
(Commissioning menu -> Stop Remote Test Mode).
 Notes: •
•
The remote test mode can only be enabled if the EOC is activated.
The times measured are the loop times there and back. The transmission
time for one direction is thus half the measured time.
• Two times the nominal transmission time T0 as measured in the
system test report may serve as a reference for the upper limit. If there is
an additional communication link connected in between (compared
to the measurements conducted in the systems test field), the delay
of this link has to be added to the nominal transmission time.
J EN 11/12 1KHW000900-EN
C.14 Display Panel

With the following minimized test procedure the four buttons on the front of the display panel (which
enable the menu-driven handling) as well as the communication of the display panel with the line
interface(s) present in the module rack shall be tested:
1. Press the button with the arrow towards “down” -> SELECT DEVICE / TPE1 will appear
3. Press the “Enter” button -> Cmd A Tx: ….. / Cmd A Rx: ….. will appear (press the “up”
button repeatedly to see all counter readings)
5. If the rack is equipped with only one teleprotection device TPE 1, proceed with step 10;
else press the “Back” button -> SELECT DEVICE / TPE1 will appear
6. Press the button with the arrow towards “up” -> SELECT DEVICE / TPE2 will appear
8. Press the “Enter” button -> Cmd A Tx: ….. / Cmd A Rx: ….. will appear (press the “up”
button repeatedly to see all counter readings)
10. Continuously press the “Back” button for more than 6 seconds -> the display panel will
reset, the backlight will go off and the  intro will restart
C.15 Management LAN Interface

A description of the commissioning procedure for the Management LAN interface G3LM can be
found in the following document which is part of the annex of the Operating Instructions NSD570:
1KHW002232 “Commissioning of LAN Interface G3LM”
C.16 Concluding works
C.16.1 Reset counters

After all NSD570 tests have passed successfully, reset the counters by using the HMI570.
In the Status / Alarm menu click on Trip Counter, then on Reset Trip Counter, activate the
checkbox "All" and click on the Reset button.
C.16.2 Clear event recorder

In the menu Event Recorder click on the link Clear Event Recorder.
C.16.3 Manual reset

In the Maintenance menu click on the link Reset Device.
C.16.4 Save the configuration data

In the Configuration menu click on the link Upload Configuration and then on Save
Configuration.
Save the "XML" configuration file on a disk with the Serial No. of the NSD570 rack and the No. of
the device (TPE 1 or TPE2) coded in the file name, e.g. HE501249_1_C0.XML.
Click on the link and choose Save this file to disk. This action saves the active configuration to
disk under the chosen name. All settings you have made and downloaded to the equipment will be
saved, including the manual entries (Jumper Settings, Rack Assembly) and also the information
that only can be read from the device (Device Information, Hardware and Firmware Versions).
J EN 12/12 1KHW000900-EN
C.16.5 Documentation
Create a printout of the active configuration data that was uploaded and saved to disk before (see
C.16.4).
Click on the link View Configuration in the Configuration menu and use the Print icon of your
browser to generate a handout of all settings and all available device information.
C.16.6 Mount covers

Make sure that the Blanking Cover Plate or the optional Display Panel G1LC is screwed on the
front side of the rack (covering the power supply modules) and the screening cover is snapped on
the back side of the rack.
C.16.7 Reconnect protection devices

After commissioning the NSD570, close the connections to the protection devices:
Close the isolating terminals of the optional external connecting cables in the local and in the
remote station or reconnect the direct wire connection to the equipment if no connecting cables are
used.
ABB Power Grids Switzerland Ltd HE
Commissioning Report - K 2021-08-05
PGGA-CE4 2003-01-31 / A. Bemsel 2021-08-05 / M. Buhl - EN 1/2
Valid for: Derived from: Replaces: Classification-No.: Document No. / File:
- - - 1KHD608528KE Commissioning
Report NSD570.doc
NSD570
Commissioning Report
According to Commissioning Instructions NSD570 1KHW000900IE
Project …………………………………………………
ABB Order No.: …………………………………………………
Station …………………………………………………
Direction …………………………………………………
Contents:
NSD570 Printout Equipment Settings Pages 1 to ….
NSD570 Commissioning Report Pages C1 to C6
……….. ……………………………………………………… Pages ...... to ......
Test conditions: Temperature range: 10 °C to 45 °C.
Basic test equipment:

PCCOM 1 cable (1:1 serial RS-232) One male, one female plug Sub-D, 9 pin
Oscilloscope BW  1 MHz Tektronix 2235 or similar
Optional test equipment:

RS-232 interface tester DV-24 (Acterna) or equivalent
NSD570 Commissioning Report K EN 2/2 HE
Notes:
 • Please refer to document "Compatibility Requirements for NSD570" (1KHW000902) for compatibility
between software HMI570, firmware "Analog", firmware "Digital", firmware “Ethernet”, firmware
“GOOSE”, firmware “Management” and hardware of NSD570.
Designation Meaning
( ..….) Measured value
G3LR Module type
RTC Real Time Clock
Rx Receiver
Tx Transmitter
Ping DOS program on command line interface to measure transmission times
Safety Instructions
Please have a look in the Commissioning Instructions <NSD570> 1KHW000900.
Copyright 2002-2021 Hitachi Power Grids. All rights reserved. Form 1KHD608528K-EN
NSD570 Commissioning Report EN C1/C6 HE

C.1 General
C.1.1 Test conditions Temperature range -5 … 45 C [ ]
C.1.2 Visual checks before powering

the equipment
Equipment connected to adequate Via circuit breaker [ ]
voltage source B9AS or B9AV
Connection to protection devices Open or interrupted local / remote [ ]

Unit 1 Unit 2
DC battery voltage G3LH (+ to -) 38.4 … 300 V DC [ ] [ ]
G3LI (+ to -) 19.2 … 72 [ ] [ ]
G3LK (+ to -) 88.0 … 300 [ ] [ ]
AC mains voltage G3LH (L to N) 85.0 … 264 V AC [ ] [ ]
G3LK (L to N) 93.0 … 253 [ ] [ ]
LED indication LED Unit 1 and Unit 2 Green LED [ ] [ ]
on the front panel
C.3 Preparing the equipment TPE1 TPE2

C.3.1 Connecting to the equipment Check communication TPE1 / TPE2 [ ] [ ]
between PC & NSD570
C.3.2 Upload the configuration Upload of valid configu- HExxxxxxBy.XML [ ] [ ]
ration successful
C.3.3 Preparing the system for testing Set time and date no RTC alarm [ ] [ ]
Update jumper settings HMI570 [ ] [ ]
Update rack assembly HMI570 [ ] [ ]
Establish link Guard LED [ ] [ ]
TPE1 TPE2
C.4 Change configuration If necessary
[ ] [ ]
C.5 Remarks for T-operation Adjusting level Analog T [ ]

Measuring T0 Normal T [ ]
Measuring T0 Inverse T [ ]
C.6 Configure Real Time Clock (RTC) TPE1 TPE2

C.6.1 Setting real time clock Check PC time / date Actual / exact [ ]
C.6.2 Testing external real time clock
synchronization (if available) TPE1 TPE2
External sync pulse only Set time and date [ ] [ ]
External GPS signal (IRIG-B) Adjust PC time / date Wrong time [ ] [ ]
Adjust PC time / date Actual / exact [ ] [ ]

C.7 Analog line interface

C.7.1 Transmitter TPE1 TPE2
If connected to PLC PLC protection input Max. level dBm ____ ____
-> reduce level setting if necessary G3LA; X100/1-2 measure level dBm (…..) (…..)
C.7.2 Power boosting / Boost output
Boost output activation G3LA; X100/5-6 with cmd. [ ] [ ]
C.7.3 Receiver
C.8 Digital line interface

C.8.1 Transmitter / Receiver TPE1 TPE2
Communication established G3LD/G1LE/G1LO/ acc. interface [ ] [ ]
G1LOa
C.8.2 Optical output power / optical
received power
G1LO TPE1 TPE2
Output power (Optical Direct Fiber G3LD/G1LO; X701/Tx [ -22 … -17 ] dBm (…..) (…..)
or Optical OTERM/OPTIF only) (short haul)
G3LD/G1LO; X701/Tx [ -5 … -1 ] dBm (…..) (…..)
(long haul)
Received power (Optical Direct Receiving fiber [ -36 … -1 ] dBm (…..) (…..)
Fiber or Optical OTERM/OPTIF
only)
G1LOa
• 2 Mbps, 850 nm, MM, 1 km G3LD/G1LOa; X701/Tx
with 50/125 µm fiber [ -23 … -11 ] dBm (…..) (…..)
with 62.5/125 µm fiber [ -19 … -11 ] dBm (…..) (…..)
• 2 Mbps, 1310 nm, SM, 30 km G3LD/G1LOa; X701/Tx [ -15 … -8 ] dBm (…..) (…..)
• 2 Mbps, 1310 nm, SM, 60 km G3LD/G1LOa; X701/Tx [ -5 … 0 ] dBm (…..) (…..)
• 2 Mbps, 1550 nm, SM, 120 km G3LD/G1LOa; X701/Tx [ 0 … 5 ] dBm (…..) (…..)
• 2 Mbps, CWDM, SM, 180 km G3LD/G1LOa; X701/Tx [ 5 … 8 ] dBm (…..) (…..)
[ ] (1550 nm) [ ] ( ……... nm)
Received power TPE1 TPE2
• 2 Mbps, 850 nm, MM, 1 km Receiving fiber [ -32 … -3 ] dBm (…..) (…..)
• 2 Mbps, 1310 nm, SM, 30 km Receiving fiber [ -34 … 0 ] dBm (…..) (…..)
• 2 Mbps, 1310 nm, SM, 60 km Receiving fiber [ -34 … -3 ] dBm (…..) (…..)
• 2 Mbps, CWDM, SM, 180 km Receiving fiber [ -45 … -10 ] dBm (…..) (…..)
[ ] (1550 nm) [ ] ( ……... nm)

C.9 Ethernet line interface

Ping communication channel PC Depending on
ms (…..) (…..)
application
Communication established G3LE acc. interface [ ] [ ]
C.9.2 Optical output power / optical (if optical SFP is used)

received power
• 100 Mbps, 850 nm, MM, 0.5 km G3LE; X103/Tx (50 µm) [ -23 … -11 ] dBm (…..) (…..)
• 100 Mbps, 1310 nm, MM, 0.5 km G3LE; X103/Tx (50 µm) [ -23.5 ... -14 ] dBm (…..) (…..)
• 100 Mbps, 1310 nm, SM, 30 km G3LE; X103/Tx [ -15 … -8 ] dBm (…..) (…..)
• 100 Mbps, 850 nm, MM, 0.5 km Receiving fiber [ -32 … -3 ] dBm (…..) (…..)
C.10 1+1 Operation mode (if used) TPE1 TPE2

Main line interface link alarm Status upload TPE 2 active [ ] [ ]
Main & stand-by line interface link Status upload TPE 1 active [ ] [ ]
alarm
Main line interface hardware alarm Status upload TPE 2 active [ ]
Stand-by line interface hardware Status upload TPE 1 active [ ]
alarm
C.11 GOOSE LAN interface

Upload alarms G3LS No alarm [ ] [ ]
C.11.2 Optical output power (if optical SFP is used)
• 100 Mbps, 850 nm, MM, 0.5 km G3LS; X103/Tx (50 µm) [ -23 … -11 ] dBm (…..) (…..)
• 100 Mbps, 1310 nm, MM, 0.5 km G3LS; X103/Tx (50 µm) [ -23.5 ... -14 ] dBm (…..) (…..)
• 100 Mbps, 1310 nm, SM, 30 km G3LS; X103/Tx [ -15 … -8 ] dBm (…..) (…..)

C.12 System alarm indication To be measured only

if requested TPE1 TPE2
Activate alarm by interrupting LEDs "Local", LED to be ON [ ] [ ]

receive line connection "Receive"
Deactivate alarm by restoring the LEDs "Local", LED to be [ ] [ ]
link "Receive" OFF

C.13 System functions
C.13.1 Transmission TPE1 TPE2

Channel
Check actual trans- HMI570 / Upload Status BER (200 sec.) 1E-0x (......) (......)
mission channel SNR x dB (......) (…...)
quality PLR x% (......) (......)
C.13.2 NSD570 loop test TPE1 TPE2
Check actual TLink HMI570 / Loop Test Button

transmission time < 2 * T0 ms (…...) (…...)
C.13.3 Command
transmission time TPE1 TPE2 TPE1 TPE2
Command A Terminal,
Tx command A [ ](T34/1)–(T34/2) (T64/1)–(T64/2) Refer to manual
[ ](T…/..)–(T…/..) (T…/..)–(T…/..) for 2* rated value ms ____ ____
Rx command A [ ](T34/5)–(T34/6) (T64/5)–(T64/6) Mean value
[ ](T…/..)–(T…/..) (T…/..)–(T…/..)  2 * T0 ms (…...) (…...)
Command B Terminal,
Tx command B [ ](T34/3)–(T34/4) (T64/3)–(T64/4) Refer to manual
Rx command B [ ](T34/7)–(T34/8) (T64/7)–(T64/8) Mean value
[ ](T…/..)–(T…/..) (T…/..)–(T…/..)  2 * T0 ms (…...) (…...)
Command C Terminal,
Tx command C [ ](T40/1)–(T40/2) (T70/1)–(T70/2) Refer to manual
Rx command C [ ](T40/5)–(T40/6) (T70/5)–(T70/6) Mean value
[ ](T…/..)–(T…/..) (T…/..)–(T…/..)  2 * T0 ms (…...) (…...)
Command D Terminal,
Tx command D [ ](T40/3)–(T40/4) (T70/3)–(T70/4) Refer to manual
Rx command D [ ](T40/7)–(T40/8) (T70/7)–(T70/8) Mean value
[ ](T…/..)–(T…/..) (T…/..)–(T…/..)  2 * T0 ms (…...) (…...)

Command E Terminal,
Tx command E [ ](T46/1)–(T46/2) (T76/1)–(T76/2) Refer to manual
Rx command E [ ](T46/5)–(T46/6) (T76/5)–(T76/6) Mean value
[ ](T…/..)–(T…/..) (T…/..)–(T…/..)  2 * T0 ms (…...) (…...)
Command F Terminal,
Tx command F [ ](T46/3)–(T46/4) (T76/3)–(T76/4) Refer to manual
Rx command F [ ](T46/7)–(T46/8) (T76/7)–(T76/8) Mean value
[ ](T…/..)–(T…/..) (T…/..)–(T…/..)  2 * T0 ms (…...) (…...)
Command G Terminal,
Tx command G [ ](T52/1)–(T52/2) (T84/1)–(T84/2) Refer to manual
Rx command G [ ](T52/5)–(T52/6) (T84/5)–(T84/6) Mean value
[ ](T…/..)–(T…/..) (T…/..)–(T…/..)  2 * T0 ms (…...) (…...)
Command H Terminal,
Tx command H [ ](T52/3)–(T52/4) (T84/3)–(T84/4) Refer to manual
Rx command H [ ](T52/7)–(T52/8) (T84/7)–(T84/8) Mean value
[ ](T…/..)–(T…/..) (T…/..)–(T…/..)  2 * T0 ms (…...) (…...)

C.14 Display Panel TPE1 TPE2
Connecting to the G1LC <-> TPE 1/2 Counter readings [ ] [ ]

device
Return information TPE 1/2 -> G1LC Loop Test time [ ] [ ]
Reset the display panel G1LC “Back” ABB intro [ ]
C.15 LAN Interface

Separate document for G3LM <-> TPE 1/2 1KHW002232 [ ]
G3LM

C.16 Concluding works TPE1 TPE2
C.16.1 Reset counters

Reset all counters HMI570 All counters = 0 [ ] [ ]
C.16.2 Clear event recorder

Clear event recorder HMI570 1 event only [ ] [ ]
C.16.3 Manual reset

Reset device HMI570 Reset / start up [ ] [ ]
C.16.4 Save the

configuration data
Upload/save config. HMI570 HExxxxxxCy.XML [ ] [ ]
C.16.5 Documentation
View/print configuration HMI570 # printout pages (………..) (………..)
C.16.6 Mount covers Rack G7BI Front and back [ ] [ ]
C.16.7 Reconnect protection Connection to Closed or local / [ ] [ ]

devices protection devices reconnected remote
Company: _________________________________
Department: _________________________________
Date: _________________________________
Signed: _________________________________
Visa: _________________________________
Inspector: _________________________________
_________________________________
Compatibility Requirements: < NSD570 > - S 2021-08-04
PGGA-PT1 2002-11-01 M. Buhl 2021-08-04 M. Strittmatter - EN 1/29
- - - - 1KHW000902SE Compatibility
Requirements NSD570.doc
Compatibility Requirements: < NSD570 >
Contents:
1 Purpose of Document 2
2 General 2
3 Release and Version Management 2
4 Compatibility Rules 2
5 Compatibility Matrix 3
6 NSD570 Basic Equipment Analog/Digital/Ethernet 4
6.1 Hardware Versions 4
6.2 Firmware Versions NSD570 Analog 6
6.3 Firmware Versions NSD570 Digital 8
6.4 Firmware Versions NSD570 Ethernet 12
6.5 Firmware Versions Not Upgradeable by the User 15
6.6 Software Versions HMI570 16
6.6.1 HMI570 “PC” 16
6.6.2 HMI570 “LAN” 19
7 NSD570 Options 22
7.1 Hardware Versions 22
7.2 Firmware Versions NSD570 Management 23
7.3 Firmware Versions GOOSE LAN Interface 27
7.4 Firmware Versions Not Upgradeable by the User 28
S EN 2/29 1KHW000902-EN
1 Purpose of Document
Description of the compatibility requirements for the NSD570 system.
2 General
The NSD570 system comprises:
1. Hardware, consisting of a number of modules.
2. Firmware, residing on some of the modules and making the processors on these modules
execute various functions such as modulation, digital filtering, etc.
3. Web browser based software, implementing the user interface for configuration, testing
and monitoring of the equipment.
3 Release and Version Management

ABB continuously enhances the NSD570 system by upgrading hardware, firmware and software.
An NSD570 system release, identified by a release number, is a product of defined functionality
comprising hardware modules, firmware and software.
Firmware and software are identified with version numbers of the form NN.nn., e.g. 5.08 (leading
zeros may be omitted).
Releases are identified by release numbers of the form RR.r, e.g. 3.1 (leading zeros may be
omitted).
Hardware modules are identified with type codes consisting of 4 characters like G3LA, G3LC,
G3LD or G3LR. Sometimes, a fifth character - the revision index - is appended to identify an
upgraded version of a module. Example: G3LDa would be an upgraded version of G3LD; G3LDb
would be an upgraded version of G3LDa and so on.
Hardware modules may have different versions within the same type code (when there are only
minor differences between the versions). Hardware versions do only consist of a one-digit number,
e.g. 1.
 Note: The information content of type codes in case of modules containing firmware
depends on the possibility to download firmware from HMI570 to the module:
• If for a module firmware download is not possible, the type code of that
module identifies the hardware including the firmware version.
Examples: G3LR, G1LC
• If for a module firmware download is possible, the type code of that module
identifies the hardware excluding the firmware version. The download files
for the firmware of such modules are included on the “Software &
Documentation CD”.
Examples: G3LA, G3LD
4 Compatibility Rules
• Rule Nr. 1:
The modules of an NSD570 terminal and the firmware on these modules must belong to the
same release as given in the next Paragraph(s).
If system contains modules of different releases, it will generally not work correctly.
• Rule Nr. 2:
The two NSD570 terminals of a link must belong to the same release. Moreover, the firmware
loaded on the line interfaces (G3LA, G3LD, G3LE) and the GOOSE LAN Interface (G3LS) must
have the identical version (valid only for firmware that can be downloaded, i.e. not applicable
for the micro controller firmware on G3LA and G3LD).
S EN 3/29 1KHW000902-EN
Caution There is no reliable operation guaranteed when violating rule Nr. 2!
• Rule Nr. 3:
The HMI570 software must have full or restricted compatibility to the NSD570 terminals being
connected to.
The term "restricted compatibility" is used when the functionality has been changed between
releases as long as the HMI570 program can handle these changes in a reasonable way.
5 Compatibility Matrix
The following table indicates the minimum required HMI570 “PC” and “LAN” versions when
deploying a particular NSD570 Analog, Digital, Ethernet, Management or GOOSE firmware
version.
Further, the minimum required NSD570 Digital firmware version is shown when assembling a
particular optional piggyback on the digital line interface G3LD.
Main Release HMI570 HMI570 NSD570 NSD570 Optional NSD570 NSD570 NSD570
Release Date “PC” “LAN” Analog Digital Piggyback Ethernet Mgmt. GOOSE
Version Version Version Version for G3LD Version Version Version
1.0 02.2003 1.03 1.10 1.05 1.14
2.0 06.2003 1.04 1.10 1.20 G1LO V1
2.0 09.2003 1.04 1.10 1.22 G1LO V3
2.0 07.2004 1.11 1.11 1.11 1.31
2.0 11.2005 1.12 1.12 1.33
2.0 08.2006 1.12 1.12 1.34 G1LE V2
2.1 10.2007 1.13 1.13 1.13 1.35
2.2 08.2008 1.14 1.14 1.40 G1LOa V1
3.0 12.2009 1.21 1.21 3.25
3.1 02.2010 1.30 3.27 1.03
3.2 05.2010 1.31 1.31 1.14 1.42 3.28 1.04
3.2.1 02.2011 1.32 1.32 3.30 1.07
3.2.2 12.2011 1.32 1.32 3.31 1.08
3.3 10.2012 1.40 1.40 1.15 1.43 1.00
3.4 06.2013 1.41 1.41 1.44 3.33 1.09 1.01
3.5 07.2014 1.42 discont. 1.45 3.35 1.11 1.03
3.6 10.2016 1.46 1.16 1.48 3.40 1.14 1.06
3.6.1 09.2017 1.46 1.16
3.6.2 06.2018 1.47 1.17 1.07
3.6.3 11.2019 1.48 1.17 1.49 3.42 1.18
3.7 08.2021 1.49 1.18 1.50 3.43 1.19 1.08
Firmware versions mentioned in the following sections of this document but not in the above table
require the same HMI570 version as the precedent firmware version shown in the list.
Example: NSD570 Digital Version 1.36 requires at least HMI570 version 1.13.
S EN 4/29 1KHW000902-EN
6 NSD570 Basic Equipment Analog/Digital/Ethernet

The NSD570 basic equipment consists of the following hardware, firmware and software versions.
6.1 Hardware Versions

Hardware Versions Description and update/upgrade information
G7BI Vers. 0 Initial version of NSD570 Module Rack.
G7BI Vers. 1 An ESD bonding point (EBP) was added on the left side of the earthing
rail.
The back cover of Module Rack version “1” was modified to improve
cable routing. The new back cover would not fit on version “0” Module
Rack G7BI.
Since module rack and back cover are always delivered as a set -> no
specific action required.
G7BI Vers. 2 Actual version (identifiable by holes instead of cutouts in the flanges used
for fixing the rack in a hinge frame, for example)
For this version the handling of the back cover was optimized. The new
back cover would not fit on version “1” Module Rack G7BI.
Since module rack and back cover are always delivered as a set -> no
specific action required.
G3LH Vers. 1 Initial version of NSD570 Universal Power Supply.
(Power Supply G3LH version „0“ was not released and distributed)
G3LH was phased out by end of 2010 (replacement: G3LI or G3LK).
G3LI Vers. 0 Initial version of NSD570 Power Supply 24-48 VDC.
Replacement for G3LH (nominal voltages 24 VDC, 48 VDC, 60 VDC)
G3LK Vers. 0 Initial version of NSD570 Power Supply 110-250 VDC/VAC.
Replacement for G3LH (nominal voltages 110 VDC, 220 VDC, 250 VDC
and 120 VAC, 230 VAC).
G1LA Vers. 0 Initial version of NSD570 Busplane with Front Cover.
If both, the Busplane G1LA and the Common Interface G3LC have
version „0“ -> no specific action required.
If the Busplane G1LA has version “0” and the Common Interface G3LC
has version “1” -> an upgrade of the busplane is recommended (ask your
local representative about the procedure).
However, since the module rack including G1LA and G3LC is always
delivered as a set, typically no specific action is required.
G1LA Vers. 1 If Management LAN Interface G3LM is equipped in the rack:
For station bus communication the G1LA HW version “2” is required.
G1LA Vers. 2 Actual version
G1LB Vers. 0 Initial version of NSD570 Supply Backplane.
Minor layout redesign of the module for Supply Backplane G1LB version
“1”, which has no consequences for the external connections or for the
compatibility (version “1” is identifiable by the additional capacitors on the
left side of the terminal block X103) -> no specific action required.
G1LB Vers. 1 Actual version (also identified by new rubric of the board -> R0002)
S EN 5/29 1KHW000902-EN

G3LC Vers. 0 Initial version of NSD570 Common Interface.
If both, the Busplane G1LA and the Common Interface G3LC have
version „0“ -> no specific action required.
If the Common Interface G3LC has version “0” and Busplane G1LA has
version “1” -> an upgrade of the busplane is required (ask your local
representative about the procedure).
However, since the module rack including G1LA and G3LC is always
delivered as a set, typically no specific action is required.
G3LC Vers. 1 If LAN Interface G3LL is equipped in the rack:
For station bus communication the optional connecting cable
“G3LL*CABLE FOR STATION BUS/RTC SYNC” (1KHW001213R0001) or
a two wire connection from G3LL to G1LB is required.
If LAN Management Interface G3LM is equipped in the rack:
For station bus communication the G3LC HW version “2” is required.
G3LC Vers. 2 Actual version
G3LA Vers. 0 Initial version of NSD570 Analog Interface.
There is an improved amplitude response (gain distortion) of the Tx/Rx
filters in Analog Interface G3LA version “1” -> no specific action
required.
If the NSD570 Analog system is used in a T-operation mode, G3LA
version “1” modules are recommended (but not required) at least in the
T-station.
By ignoring the “Compatibility Rules” (see Section 4) in this only case, it
would also be possible to use a G3LA version “0” and a G3LA version “1”
in a link.
G3LA Vers. 1 Actual version
G3LD Vers. 0 Initial version of NSD570 Digital Interface.
Under normal operating conditions and if the cable length to the data
circuit-terminating equipment (DCE) is not significantly above 100 meter
-> no specific action required.
G3LD Vers. 1 Minor layout redesign to improve the performance of the serial on-board
interfaces RS-530 and G.703 of G3LD (also identified by new rubric of the
board -> R0102).
G3LD Vers. 2 Actual version
Minor layout redesign due to component obsolescence.
G3LE Vers. 0 Initial version of NSD570 Ethernet WAN Interface.
G3LE Vers. 1 Actual version (also identified by new rubric of the board -> R0002)
No change in the G3LE related hardware - the HW version number
increases due to common hardware platform with G3LMa.
G3LR Vers. 0 Initial version of NSD570 Relay Interface
If the firmware version 1.00 is stored in the FLASH – see label – it is
recommended (but not required) to update it at the factory; ask your local
representative about the procedure).
G3LR Vers. 1 A FLASH memory device has been replaced by a PROM device.
G3LR is phased out by end of 2016 (replacement: G3LRa).
G3LRa Vers. 2 Actual version (also identified by new rubric of the board -> R0102)
4 programmable input voltage ranges (instead of 3), with an additional
tripping threshold operating at 146 … 165 VDC; command inputs with
inrush current >10 mA for >10 ms.
S EN 6/29 1KHW000902-EN
 Note: All hardware versions can be viewed by means of the HMI570, except for:
Module Rack G7BI, Supply Backplane G1LB, Power Supply G3LH, G3LI and
G3LK.
6.2 Firmware Versions NSD570 Analog

Firmware Versions Description and update/upgrade information
NSD570 Analog If the current version is less than 1.04 -> an update to the latest version
Vers. 1.05 is recommended at the earliest convenience (see remarks in “actual
version”).
If the current version is 1.04 -> an update to the latest version is not
immediately necessary but recommended e.g. during the next regular
maintenance check (see remarks in “actual version”).
NSD570 Analog A “T-operation” with different center frequencies of send and receive
Vers. 1.11 channel is now possible with this version (whereas the same bandwidth of
Tx and Rx channel in the T-operation mode is still required).
The loop test reception “window” was adapted so that an equipment
connected back-to-back with its own receiver will not raise an alarm.
If the features and modes mentioned above shall not be applied and the
current version is 1.05 -> no specific action required (the firmware may
be updated during the next regular maintenance check, if desired; see
remarks in “actual version”).
NSD570 Analog A minor bug in the “retain in state” mode for the command outputs during
Vers. 1.12 link failure was fixed.
If the current version is 1.11 or lower and the “retain in state” function is
configured -> an update to the latest version is not immediately
necessary but recommended, e.g. during the next regular maintenance
check (see remarks in “actual version”).
NSD570 Analog In this version, a new parameter “link propagation time” is configurable, in
Vers. 1.13 order to take the delay of the telecommunication link into account (used to
calculate the admissible loop test overall delay before alarm is given).
After the cyclic loop test alarm is detected, the test interval was increased
to its original configuration (1/3/6/12/24 hours) when using earlier firm-
ware versions. With this version the test interval during loop test alarm
state is 5 min. until the link has re-established.
The SNR alarm threshold levels were aligned within the same channel
bandwidth and are no longer dependent on the application setting and the
chosen operating mode.
In order to improve security against unwanted operation, the NSD570
Analog receiver using this firmware version will ignore all received tripping
signals which would activate one or more commands not configured to
any G3LR Relay Interface output of the equipment.
If the features mentioned above shall not be applied and the current
version is 1.12 -> no specific action required (the firmware may be
updated during the next regular maintenance check, if desired; see
Please note that the user interface HMI570 version 1.13 or higher is
required for updating the equipment with this firmware version.
S EN 7/29 1KHW000902-EN

NSD570 Analog Newly introduced features are:
Vers. 1.14 • Two redundant communication channels (1+1) with two Line
Interfaces in one NSD570 rack, sharing up to four Relay Interfaces
plugged in TPE 1 (no Relay Interfaces in TPE 2 required anymore).
• Improved Real Time Clock accuracy
• New command input and output duration parameters
• Safe DSP operation mode where command tripping is suppressed in
case of a persistent program or data memory error in the DSP or
SDRAM
If the features mentioned above shall not be applied and the current
NSD570 Analog This version supports the new GOOSE LAN Interface G3LS.
Vers. 1.15 If the G3LS module is not used and the current version is 1.14
-> no specific action required (the firmware may be updated during the
next regular maintenance check, if desired; see remarks in “actual
version”).
NSD570 Analog This version supports the new features:
Vers. 1.16 • Configurable redundant power supply failure behavior (HW Warning or
HW Alarm in case of a faulty redundant power supply module)
• G3LS interface common alarm
If the new features are not used and the current version is 1.15
version”).
NSD570 Analog This version supports the new feature:
Vers. 1.17 • Undelayed/delayed configurable alarm outputs for user alarms 1 ... 3
If the new feature is not used and the current version is 1.16
version”).
S EN 8/29 1KHW000902-EN

NSD570 Analog Actual version
Vers. 1.18 Improvements and bugfixes:
• Delay of alarm "No signal (IRIG-B) on RTC" increased to 140 sec, to
avoid equipment alarm in case of short IRIG-B input signal failures
(e.g. caused by a G3LMa module reset).
• Date processing in case of missing IRIG-B signal adapted.
If no IRIG-B signal is used to synchronize the RTC on G3LA, and the
be updated during the next regular maintenance check, if desired.
Ask your local representative for a free upgrade version of the “NSD570
Software & Documentation CD” including the actual NSD570 Analog
firmware version.
Take the NSD570 link out of service, update the firmware according the
“Firmware Download Description NSD570” (1KHW000896) and re-
commission the equipment according the “Commissioning Instructions
NSD570” (1KHW000900).
 Note: The firmware NSD570 Analog can be downloaded to the Analog Interface G3LA.
The programmed firmware version can be viewed by means of the HMI570.
The newest firmware version can always be used for updating an analog
NSD570 link.
6.3 Firmware Versions NSD570 Digital

NSD570 Digital If the current version is less than 1.14 -> an update to the latest version
version”).
NSD570 Digital For this version the signal pulse shape of the T1 interface was slightly
Vers. 1.15 adjusted (only applicable if the G1LE option is used on G3LD) -> an
update to the latest version is not immediately necessary but
recommended e.g. during the next regular maintenance check (see
NSD570 Digital For this version the G.703 jitter performance was improved and the start
Vers. 1.16 up time of the RS-422 interface after power off/on or reset was reduced
-> an update to the latest version is not immediately necessary but
NSD570 Digital With this version also the optical interfaces of the optional module G1LO
Vers. 1.20 are supported -> an update to the latest version is not immediately
necessary but recommended e.g. during the next regular maintenance
check (see remarks in “actual version”).
S EN 9/29 1KHW000902-EN

NSD570 Digital For this version the “inverse T-operation” function was improved and the
Vers. 1.22 “mixed-mode” operation via a FOX515 link was enabled (e.g. local
connection to OTERM and remote connection to GECOD) -> an update
to the latest version is not immediately necessary but recommended
e.g. during the next regular maintenance check (see remarks in “actual
version”).
NSD570 Digital This version also operates via “low-end” converters and communication
Vers. 1.23 devices – equipped with G.703 codirectional interfaces – that ignore
octet-boundaries (which is usually not the case for sophisticated PCM
multiplex or time slot access equipment) -> an update to the latest
version is not immediately necessary but recommended e.g. during
the next regular maintenance check (see remarks in “actual version”).
NSD570 Digital For this version the “normal T-operation” function was improved (reduced
Vers. 1.31 delay in T-station, remote configuration- and firmware-download in both
directions to outer stations enabled, alarm management harmonized).
The loop test reception “window” was adapted so that an equipment
connected back-to-back with its own receiver will not raise an alarm.
current version is 1.23 -> an update to the latest version is not
NSD570 Digital With this version the loop test can also be performed while commands are
Vers. 1.32 transmitted. The start-up performance was improved (after powering up
the equipment). A minor bug in the “retain in state” mode of the command
outputs was fixed.
-> An update to the latest version is not immediately necessary but
NSD570 Digital With this version the accuracy of the bit error rate (BER) measurement at
Vers. 1.33 low bit error rates was improved (see also Anomaly List, Section 2.3.1).
If the optional piggyback G1LO (the optical interface for the NSD570
Digital) is plugged onto the Digital Interface G3LD, it is allowed with this
version to configure and use the interfaces on the G3LD “main” board as
well (see Anomaly List, Section 2.3.4).
The NSD570 using this firmware version has a reduced responsiveness
to short-term alarm sources in respect of event recorder entries, as long
as no deterioration of the system performance must be expected.
S EN 10/29 1KHW000902-EN

NSD570 Digital After the cyclic loop test alarm is detected, the test interval was increased
Vers. 1.34 to its original configuration (1/3/6/12/24 hours) when using earlier firm-
ware versions. With this version the test interval during loop test alarm
state is 5 min. until the link has re-established.
When using the optional piggyback G1LO hardware version 2 or 3 and
the embedded operation channel (EOC) is configured to “off”, no remote
alarm is generated anymore (as with previous versions).
With this version no continuing reset of the Digital Interface G3LD will
occur if the module is configured as TPE 1, but plugged into slot 6 (N58)
of TPE 2 (see Anomaly List, Section 2.3.2).
The configurable behavior patterns for “Command Outputs During Link
Failure” will all operate as described in the Manual Section 5.5 (see
Anomaly List, Section 2.3.3).
This firmware supports the hardware version 2 of the optional piggyback
G1LE (E1/T1 Interface) for the Digital Interface G3LD.
NSD570 Digital In this version, a new parameter “link propagation time” is configurable, in
If this feature mentioned above shall not be applied and the current
NSD570 Digital For some multiplexer equipment with a T1 interface, it was necessary to
Vers. 1.36 allocate the first four time slots for reliable operation of the teleprotection
when using earlier firmware versions of NSD570 Digital.
With this or a higher firmware version, only one time slot is required for
proper NSD570 communication over multiplexer equipment with a T1
interface (channel 1 with 64 kbps out of the T1 frame with 1.544 Mbps).
If this feature mentioned above shall not be applied and the current
NSD570 Digital This firmware version supports the new optical interface G1LOa.
Vers. 1.40 If this feature mentioned above shall not be applied and the current
version is 1.35 or 1.36 -> no specific action required (the firmware may
S EN 11/29 1KHW000902-EN

NSD570 Digital Newly introduced features are:
Vers. 1.42 • Two redundant communication channels (1+1) with two Line
Interfaces in one NSD570 rack, sharing up to four Relay Interfaces
plugged in TPE 1 (no Relay Interfaces in TPE 2 required anymore).
• Improved Real Time Clock accuracy
• New command input and output duration parameters
• Safe DSP operation mode where command tripping is suppressed in
case of a persistent program or data memory error in the DSP or
SDRAM
• Enhanced compatibility with non-ABB multiplexer or converter
equipment, transmitting according to optical IEEE C37.94 standard
If those features mentioned above shall not be applied and the current
version is 1.40 -> no specific action is required (the firmware may be
NSD570 Digital This version supports the new GOOSE LAN Interface G3LS.
Vers. 1.43 If the G3LS module is not used and the current version is 1.42
-> no specific action is required (the firmware may be updated during
the next regular maintenance check, if desired; see remarks in “actual
version”).
NSD570 Digital The G.703 interface synchronization performance was improved.
Vers. 1.44 If the current version is 1.43 -> no specific action required (the firmware
may be updated during the next regular maintenance check, if desired;
see remarks in “actual version”).
NSD570 Digital The G.703 interface jitter acceptance was improved.
Vers. 1.45 -> An update to the latest version is not immediately necessary but
recommended e.g. during the next regular maintenance check; see
remarks in “actual version”.
NSD570 Digital This version supports the new features:
version”).
S EN 12/29 1KHW000902-EN

NSD570 Digital This version supports the new feature:
version”).
NSD570 Digital Actual version
• Date processing in case of missing IRIG-B signal adapted.
If no IRIG-B signal is used to synchronize the RTC on G3LD, and the
Software & Documentation CD” including the actual NSD570 Digital
firmware version.
NSD570” (1KHW000900).
 Note: The firmware NSD570 Digital can be downloaded to the Digital Interface G3LD.
The newest firmware version can always be used for updating a digital NSD570
link, regardless which interface is operated (G.703, RS-530, E1, T1, optical).
6.4 Firmware Versions NSD570 Ethernet

NSD570 Ethernet Initial version
Vers. 3.25 Please note that the user interface HMI570 version 1.21 or higher is
NSD570 Ethernet Minor bugs fixed.
recommended (see remarks in “actual version”).
NSD570 Ethernet Minor bugs fixed.
NSD570 Ethernet New command input and output duration parameters introduced.
S EN 13/29 1KHW000902-EN

NSD570 Ethernet Problem with firmware download to Ethernet Line Interface G3LE via
Vers. 3.30 Management LAN Interface G3LM solved. Minor bugs fixed.
NSD570 Ethernet With firmware version 3.30 and lower, the alarm relays are inversely
Vers. 3.31 operated, i.e. the “alarm” condition does not correspond to the “power off”
state of the equipment (relay coil not energized).
With firmware version 3.31, the alarm relays on the Common Interface
G3LC and the relay contacts on the Relay Interface G3LR (if configured
as alarm outputs) are correctly operated.
Please note that the wiring to the alarm relay contacts has to be
interchanged after a firmware update to version 3.31.
NSD570 Ethernet This firmware version provides 1+1 path protection mode support as
Vers. 3.33 already available for NSD570 Analog/Digital with Rel.3.2.
In addition, a RAM supervision was implemented. In case of a defective
RAM in the CPU, an alarm is raised and command tripping is suppressed.
NSD570 Ethernet Issue fixed: Link failure after reset of G3LE line interfaces which are
Vers. 3.35 connected back-to-back with an Ethernet crossover cable.
NSD570 Ethernet This version supports the new features:
• Enabling faster firmware download for future FW versions
version”).
NSD570 Ethernet When the Ethernet Line Interface G3LE is used in 1+1 path protection
Vers. 3.40 mode and is programmed with firmware version 3.39 or lower, the alarm
relays on the Common Interface G3LC do not work as expected.
If G3LE is not used in 1+1 path protection mode and the current version is
3.39 -> no specific action required (the firmware may be updated during
the next regular maintenance check, if desired; see remarks in “actual
version”).
S EN 14/29 1KHW000902-EN

NSD570 Ethernet This version supports the new feature
version”).
NSD570 Ethernet VxWorks IPnet patch CDR-R186785.1-1 was applied to fix the following
Vers. 3.42 vulnerabilities:
• CVE-2019-12256, CVE-2019-12260, CVE-2019-12261,
CVE-2019-12263, CVE-2019-12258, CVE-2019-12262
If there is a risk that attackers can directly access the device from remote
and exploit the vulnerabilities (when no firewall with appropriate rules is
implemented, for example), an immediate update from a previous
version is highly recommended (see remarks in “actual version”).
NSD570 Ethernet Actual version
• Signal timing on real-time bus improved for 1+1 operation mode.
• Minor bug in switching criteria of 1+1 path protection mode fixed.
• WAN communication protocol improved, to avoid rare module restarts.
• A manual loop test clears a pending loop test error when successful.
• The configuration download counter is increased after the reset of the
device only, and not already after the configuration download.
If the 1+1 operation mode is used, or if seldom self-restarts are observed,
or if the IRIG-B signal is used to synchronize the RTC on G3LE, an
immediate update from a previous version is highly recommended.
If the current firmware version on the Ethernet Line Interface G3LE is 3.28
or lower, this firmware version cannot be downloaded directly to the
module by means of user interface HMI570, because a boot loader
update and a firmware update to version 3.30 on G3LE is required first.
Please refer to the update description available on the latest
“NSD570 Software & Documentation CD” (including the required
files/tools to update the boot loader and the firmware) or contact your
local representative and ask for the update procedure.
NSD570” (1KHW000900).
 Note: The firmware NSD570 Ethernet can be downloaded to the Ethernet Line
Interface G3LE.
The newest firmware version can always be used for updating an Ethernet
NSD570 link, but the latest user interface HMI570 must be utilized.
S EN 15/29 1KHW000902-EN
6.5 Firmware Versions Not Upgradeable by the User

G3LA/G3LD If the current version is higher than 1.00 -> no specific action required.
C Vers. 1.03 If the current version is 1.00 -> it is recommended (but not required) to
update the module at the factory (ask your local representative about the
procedure).
G3LA/G3LD This version is only needed if the additional features of the Display Panel
C Vers. 1.04 G1LC (with C firmware version 1.01) shall be utilized.
In all other cases -> no specific action required (see C version 1.03)
G3LA/G3LD Micro controller memory check optimized.
C Vers. 1.05 If the current version is 1.04 -> no specific action required.
G3LA/G3LD Actual version
C Vers. 1.06 Compatible with new flash memory type used in G3LD Vers. 2.
If the current version is 1.04 or 1.05 -> no specific action required.
G3LR Actual version
FPGA Vers. 1.01 If the firmware version 1.00 is stored in the FLASH on the module – see
label – it is recommended (but not required) to update the module at the
factory (ask your local representative about the procedure).
 Note: The micro controller firmware (C) is the same for both line interfaces, G3LA and
G3LD. It may not be upgraded by the customer/user (the module has to be
returned to the factory). The programmed firmware version can be viewed by
means of the HMI570.
The firmware version of G3LR is visible on the module only. There is an
adhesive label on PROM A203, indicating the firmware version.
Beginning with version 1.01 the firmware is stored in a PROM. It is therefore not
possible (and not necessary) to update it.
S EN 16/29 1KHW000902-EN
6.6 Software Versions HMI570
6.6.1 HMI570 “PC”
Software Versions Description and update/upgrade information

HMI570 “PC” If the current version is less than 1.03 -> an update to the latest version
version”).
immediately necessary but recommended (see remarks in “actual
version”).
HMI570 “PC” With this version also the optical interfaces of the optional module G1LO
Vers. 1.04 are supported. Some “comfort” features have been added -> an update
to the latest version is not immediately necessary but recommended
(see remarks in “actual version”).
HMI570 “PC” The common functions and views of this version were synchronized to the
Vers. 1.11 HMI570 “LAN” version 1.11 -> an update to the latest version is not
immediately necessary but recommended (see remarks in “actual
version”).
HMI570 “PC” This version limits the selectable values of the “BER Alarm Threshold” for
Vers. 1.12 the NSD570 Digital to the feasible range of 1E-01 to 1E-06. The new
default setting for the BER alarm threshold is 1E-03.
The default value of the configuration setting “Unblocking Extra Delay
[ms]“ for the NSD570 Digital was increased from 5 ms to 10 ms.
The list box items for the configuration setting “Command Outputs During
Link Failure” are described in more detail now (self-explanatory).
The selectable value range of the configuration setting “Max Tx Trip
Duration [s]” was expanded from 1…15 s to 1…30 s.
The station name was added to the Event Recorder list.
The display of the status information was adapted to the improved BER
measurement method introduced with version 1.33 of NSD570 Digital.
HMI570 “PC” In this version, a new parameter “link propagation time” is configurable, in
This software supports the hardware version 2 of the optional piggyback
Updated versions of Java Runtime Environment (JRE) 1.5.0_12 and
Tomcat web server 4.1.36 are used.
Please note that HMI570 version 1.13 or higher is required for
updating the equipment with the firmware version 1.13 or higher of
NSD570 Analog and version 1.35 or higher of NSD570 Digital.
S EN 17/29 1KHW000902-EN

HMI570 “PC” The Local Alarm Polling and the Network Alarm Polling functions were
Vers. 1.14 introduced in this version.
Starting from this software version, it is possible to export/import the
HMI570 settings and to start HMI570 client separately from HMI570
server.
This software supports the optional piggyback G1LOa (Optical Interface)
for the Digital Interface G3LD.
NSD570 Digital.
HMI570 “PC” This version supports the NSD570 Ethernet Line Interface G3LE.
Vers. 1.21 Additionally, the two new power supply modules type G3LI and G3LK can
be chosen from a pull-down menu in the rack assembly list.
-> An update to the latest version is required if the Ethernet WAN
Interface G3LE is used. Otherwise it is not immediately necessary
but recommended (see remarks in “actual version”).
HMI570 “PC” This version supports the Management LAN Interfaces G3LM.
Vers. 1.30 Password complexity enhanced from 4 to 6 characters (which must be a
combination of letters, numbers and “special” characters).
-> An update to the latest version is required if the Management LAN
Interface G3LM is used. Otherwise it is not immediately necessary
HMI570 “PC” This software supports new command input and output duration
Vers. 1.31 parameters and the new redundant (1+1) operation mode which releases
from the need of extra Relay Interfaces in TPE 2.
NSD570 Digital and version 1.14 or higher of NSD570 Analog.
HMI570 “PC” Some functions (e.g. event recorder upload) did not work properly with
Vers. 1.32 earlier versions under certain Windows operating systems, if the HMI570
is operated by several users on the same PC/notebook and the different
user accounts do not share the “%temp%” folder.
Device Address in default configuration type “management” (G3LM)
changed. Downloading wrong firmware intercepted. Minor bugs fixed.
HMI570 “PC” This software supports the GOOSE LAN Interface G3LS. It is now
Vers. 1.40 possible to install HMI570 PC in two different versions:
• The extended HMI570 version provides IEC 61850 SCL file handling
capabilities to create and maintain G3LS configurations.
• There is also a reduced variant where only the download of prepared
G3LS configurations is supported.
If G3LS is not part of your substation, there is no need for the extended
version of HMI570. Please install HMI570 with the default settings in the
installer wizard. If support for G3LS is required, please enable the
corresponding checkbox during the installation procedure.
S EN 18/29 1KHW000902-EN

HMI570 “PC” This version provides improved support of IEC 61850 engineering.
Vers. 1.41 The menu structure of IEC 61850 was completely re-designed.
New IEC 61850 functionality was added.
The overall HMI570 performance could be improved significantly.
HMI570 “PC” This version provides support of IEC 61850 Edition 1 engineering in
Vers. 1.42 addition to the Edition 2 engineering supported previously.
Default encoding of HMI570 is changed to UTF-8. If non-English charac-
ters were saved on the device with previous HMI570 versions, they will
not be displayed correctly after uploading the configuration with this
HMI570 version and have to be corrected manually.
HMI570 page layout was redesigned to be compatible with Internet
Explorer 10, 11 and future versions. Internet Explorer versions 6 and 7
are no longer supported.
Java runtime, Tomcat application server as well as other components of
HMI570 are updated to their latest versions.
HMI570 “PC” This version supports the new features:
Vers. 1.46 • Configuration of NTP/SNTP client on G3LMa
• Configuration of SNMP attributes sysName, sysContact and
community on G3LM/G3LMa
• Configurable redundant power supply failure behavior (HW Warning or
• Maximum configurable Tx Input On-Delay increased from 10 ms to
20 ms
• Display of G3LM/G3LMa hardware version
• Java runtime, Tomcat application server as well as other components
of HMI570 are updated to their latest versions.
HMI570 “PC” This version configures line interfaces to send the “Link Alarm” instead of
Vers. 1.47 the “Local Alarm” to G3LS GOOSE interface (to avoid that the quality
attribute of the commands is affected by alarms originated from G3LS).
The MAC address display for G3LE is now also available in the menu
“Status Upload” (as for G3LM/G3LS).
Some guidelines for the SNTP configuration were implemented.
Additionally, certain naming was aligned and minor bugs were fixed.
An update to the latest version is required if the GOOSE LAN
Interface G3LS programmed with firmware version 1.06 or higher is
used. Otherwise it is not immediately necessary but recommended
(see remarks in “actual version”).
S EN 19/29 1KHW000902-EN

HMI570 “PC” This version supports the new features:
• Password complexity enhanced from 6 to 8 characters (which must be
a combination of letters, numbers and “special” characters) for both,
local HMI570 and G3LM user management, as well as for setting the
WAN password of G3LE
of HMI570 are updated to newer versions
HMI570 “PC” Actual version
Vers. 1.49 This version does not force the Internet Explorer from Microsoft to be
opened. Instead the default browser installed on the computer is used.
The following new features on G3LM are supported:
• SNMPv3 including user management.
• SNMP polling of commands and manipulation events.
• SNMP polling of trip counters.
• UTC time zone offset and DST settings.
Cyber security improvements:
• After installation, only one default account is available in HMI570. A
warning message is displayed until the password has been changed.
• After a new user login, all previously loaded files in HMI570
(configuration, events, logs) are removed from the session.
of HMI570 are updated to newer versions.
• Issues fixed, which were found during the periodic security testing,
executed by our Cybersecurity Assurance Center (CsAC).
An update to the latest version is required if the new features of the
Management LAN Interface G3LM shall be used. Otherwise it is not
immediately necessary but recommended.
Software & Documentation CD” including the actual HMI570 “PC” version.
Uninstall the previous version of the HMI570 on your PC/notebook.
Install the new version on your PC/notebook according to the “Software
Installation Description HMI570” (1KHW000894).
6.6.2 HMI570 “LAN”

HMI570 “LAN” Initial version
Vers. 1.10 For the image file of this software to be stored, a 256 MB compact flash
card is required.
An update to the latest version is not immediately necessary but
S EN 20/29 1KHW000902-EN

HMI570 “LAN” For the image file of this software to be stored, a 128 or 256 MB compact
Vers. 1.11 flash card is required.
The “size” of the software could be reduced so that the image file now fits
on a 128 MB compact flash card. Nevertheless this version can also be
copied onto a 256 MB compact flash card.
An update to the latest version is not immediately necessary but
HMI570 “LAN” For the image file of this software to be stored, a 128 or 256 MB compact
Vers. 1.12 flash card is required.
This version limits the selectable values of the “BER Alarm Threshold” for
the NSD570 Digital to the feasible range of 1E-01 to 1E-06. The new
default setting for the BER alarm threshold is 1E-03.
The default value of the configuration setting “Unblocking Extra Delay
[ms]“ for the NSD570 Digital was increased from 5 ms to 10 ms.
The list box items for the configuration setting “Command Outputs During
Link Failure” are described in more detail now (self-explanatory).
The selectable value range of the configuration setting “Max Tx Trip
Duration [s]” was expanded from 1…15 s to 1…30 s.
The station name was added to the Event Recorder list.
The display of the status information was adapted to the improved BER
measurement method introduced with version 1.33 of NSD570 Digital.
HMI570 “LAN” For the image file of this software to be stored, a 256 MB compact flash
Vers. 1.13 card is required.
In this version, a new parameter “link propagation time” is configurable, in
order to take the delay of the telecommunication link into account (used to
This software supports the hardware version 2 of the optional piggyback
Updated versions of Java Runtime Environment (JRE) 1.5.0_12 and
Tomcat web server 4.1.36 are used.
NSD570 Analog and version 1.35 or higher of NSD570 Digital.
HMI570 “LAN” For the image file of this software to be stored, a 256 MB compact flash
Vers. 1.14 card is required.
This software supports the optional piggyback G1LOa (Optical Interface)
for the Digital Interface G3LD.
Some non-critical bugs in the Local Alarm Polling function were fixed.
NSD570 Digital.
S EN 21/29 1KHW000902-EN

HMI570 “LAN” This version supports the NSD570 Ethernet Line Interface G3LE.
Vers. 1.21 Additionally, the two new power supply modules type G3LI and G3LK can
be chosen from a pull-down menu in the rack assembly list.
-> An update to the latest version is required if the Ethernet WAN
Interface G3LE is used. Otherwise it is not immediately necessary
HMI570 “LAN” Contrary to HMI570 “PC” Vers. 1.30, this version was not officially
Vers. 1.30 released (see remarks in “actual version”).
HMI570 “LAN” This version supports the Management LAN Interface G3LM.
Vers. 1.31 Password complexity enhanced from 4 to 6 characters (which must be a
combination of letters, numbers and “special” characters)
This software supports new command input and output duration
parameters and the new redundant (1+1) operation mode which releases
from the need of extra Relay Interfaces in TPE 2.
NSD570 Digital and version 1.14 or higher of NSD570 Analog.
HMI570 “LAN” Device Address in default configuration type “management” (G3LM)
Vers. 1.32 changed. Downloading wrong firmware intercepted. Minor bugs fixed.
HMI570 “LAN” This software supports the GOOSE LAN Interface G3LS. It provides the
Vers. 1.40 same feature set as the reduced variant of HMI570 “PC” Vers. 1.40,
without full SCL handling capabilities. The download of prepared G3LS
configurations is supported.
HMI570 “LAN” Actual version
Vers. 1.41 This version provides improved support of IEC 61850 engineering.
The menu structure of IEC 61850 was completely re-designed.
New IEC 61850 functionality was added.
The overall HMI570 performance could be improved significantly.
recommended.
Software & Documentation CD” including the actual image file of the
HMI570 “LAN” version.
Copy the new image file of the HMI570 “LAN” version onto your compact
flash card and re-commission the LAN Interface G3LL according to the
“Commissioning Instructions NSD570 LAN Interface” (1KHW001289).
If the existing LAN Interface G3LL is equipped with a 128 MB compact
flash card only, please contact your local representative and ask for the
258 MB version of the “G3LL Compact Flash Card NSD570” (order
number: 1KHW001204R0100).
Please note that HMI570”LAN” Vers. 1.41 is the last official release,
as the NSD570 LAN Interface G3LL was phased out by end of 2012.
 Note: The software version of the HMI570 can be viewed by clicking on the “About
HMI570” link in the “HMI570 Options” menu.
S EN 22/29 1KHW000902-EN
7 NSD570 Options
The NSD570 options consist of following hardware and firmware versions.
7.1 Hardware Versions

G1LE Vers. 0 Initial version of NSD570 E1/T1 Interface.
G1LE Vers. 1 The signal pulse shape and the input resistance of the E1/T1 Interface
G1LE version “1” was marginally modified in order to fully meet the E1
standard -> no specific action required.
G1LE Vers. 2 Actual version
(G1LE version “2” is the redesign of version “1” and a full functional
equivalent to version “1”).
The input/output impedance is selectable between 100 Ohm for T1
interface type and 120 Ohm for E1 interface type by means of 3 jumpers.
G1LE version 2 requires firmware NSD570 Digital Version 1.34 or
higher and software HMI570 Version 1.13 or higher.
G1LR Vers. 1 Initial version of NSD570 Internal Tripping Voltage 24 VDC.
(Internal Tripping Voltage G1LR version „0“ was not officially released)
G1LO Vers. 1 Initial version of NSD570 Optical Interface.
(Optical interface G1LO version „0“ was not officially released)
If the current version is “1” -> an update to version “2” or “3” is
recommended at the earliest convenience (see remarks in “G1LO
version 2”).
G1LO Vers. 2 A creeping deterioration of the receiver sensitivity was reported (which
leads to an NSD570 Rx alarm) when G1LO with hardware version “1” is
operated in links with high optical attenuation.
In order to avoid this early deterioration, G1LO modules version „1“ can
be updated to version „2“ at the factory; ask your local representative
about the procedure.
Although this became only a problem in long optical links (several km), it
is recommended to update also the G1LO modules operated in short links
as a preventive measure, e.g. during the next regular maintenance check.
G1LO Vers. 3 Actual version
(G1LO version “3” is the redesign of version “1” and a full functional
equivalent to version “2”).
G1LO was phased out by end of 2008 (replacement: G1LOa).
G1LO requires firmware NSD570 Digital Version 1.22 or higher and
software HMI570 Version 1.04 or higher.
G1LOa Vers. 1 Initial version of NSD570 Universal Optical Interface.
(Optical interface G1LOa version „0“ was not officially released)
G1LOa is the successor of G1LO and its full functional equivalent.
G1LOa requires firmware NSD570 Digital Version 1.40 or higher and
software HMI570 Version 1.14 or higher.
G1LC Vers. 0 Initial version of NSD570 Display Panel.
G3LL Vers. 0 Initial version of NSD570 LAN Interface.
G3LL was phased out by end of 2012 (replacement: G3LM).
G3LM Vers. 0 Initial version of NSD570 LAN Management Interface.
S EN 23/29 1KHW000902-EN

G3LMa Vers. 1 Actual version (also identified by new rubric of the board -> R0002)
G3LMa is required to enable the NTP/SNTP client function.
The G3LMa comes with an IRIG-B output to distribute the UTC time
received from an optional NTP/SNTP server.
G3LS Vers. 0 Initial version of NSD570 GOOSE LAN Interface.
G3LS Vers. 1 Actual version (also identified by new rubric of the board -> R0002)
No change in the G3LS related hardware – the HW version number
increases due to common hardware platform with G3LMa.
 Note: All hardware versions can be viewed by means of the HMI570, except for:
Internal Tripping Voltage G1LR (not viewable), Display Panel G1LC (viewable on
the display itself).
7.2 Firmware Versions NSD570 Management

NSD570 Mgmt. Initial version
NSD570 Mgmt. Minor bugs fixed.
NSD570 Mgmt. Some bugs fixed in user administration and access security improved.
NSD570 Mgmt. Problem with firmware download to Ethernet Line Interface G3LE via
Vers. 1.07 Management LAN Interface G3LM solved. Minor bugs fixed.
NSD570 Mgmt. With firmware version 1.07 or lower, the SNMP trap which clears the
Vers. 1.08 alarm contains the same time stamp as the SNMP trap that previously
reported the alarm. As a result, the duration of the alarm - as indicated by
the NSD570 equipment - cannot be correctly determined by the network
management system.
With firmware version 1.08, the SNMP trap which clears the alarm is sent
with the correct alarm “off” time stamp.
S EN 24/29 1KHW000902-EN

NSD570 Mgmt. This version fully supports the new GOOSE LAN Interface G3LS.
Vers. 1.09 Bug fixes:
• Broadcast address removed from SNMP IP-MIB.
• Value of ifStackLastChange in SNMP IF-MIB constantly set to 0.
• Other minor bugs fixed.
NSD570 Mgmt. Support of new flash chip added (the flash chip on the Ethernet board of
Vers. 1.10 G3LM had to be changed, because the previous version was
discontinued by the manufacturer; G3LM modules equipped with the new
flash chip are programmed with this firmware version ex-works).
Please note that G3LM interfaces programmed with firmware version
1.10 or higher cannot be downgraded with versions 1.09 or lower.
NSD570 Mgmt. MAC address reading problem on new flash chip was fixed.
Vers. 1.11 -> An update to the latest version is only required if the G3LM
module is programmed with firmware version 1.10 (see remarks in
“actual version”).
NSD570 Mgmt. This version supports the new features:
Vers. 1.14 • Enabling the NTP/SNTP client on G3LMa
• Configuration of SNMP attributes sysName, sysContact and
community on G3LM/G3LMa
• Display of G3LM/G3LMa hardware version
• Updated to the latest cyber security requirements & OpenSSL V1.0.1
• HMI570 always enforces TLS 1.0 / 1.2 and refuses SSL 3.0. The TLS
client’s ability to fall back to the SSL 3.0 protocol was also disabled on
G3LM (thus eliminating the “POODLE” vulnerability CVE-2014-3566)
• “TCP Predictability” vulnerability eliminated (CVE-2015-3963)
NSD570 Mgmt. This version has the following bugs and Cyber Security vulnerability fixed:
Vers. 1.16 • G3LM resets when own device address is polled via SNMP
• G3LM optical Ethernet port down when power cycled with the
selection switch in SFP position
• OpenSSL CVE-2016-6304: OCSP Status Request extension
unbounded memory growth
highly recommended, especially if the SFP interface is used (see
S EN 25/29 1KHW000902-EN

NSD570 Mgmt. This version has the following bug fixed:
Vers. 1.17 • When operating SNMP alarm polling, it may happen that unnecessary
SNMP traps are sent by G3LM: “Device is no more accessible” and
“Device is accessible again” just some seconds later.
If G3LM does not send such traps occasionally, and if the current version
is 1.16 -> no specific action is required (the firmware may be updated
during the next regular maintenance check, if desired).
NSD570 Mgmt. VxWorks IPnet patch CDR-R186785.1-1 was applied to fix the following
Vers. 1.18 vulnerabilities:
• CVE-2019-12256, CVE-2019-12260, CVE-2019-12261,
CVE-2019-12263, CVE-2019-12258, CVE-2019-12262
If there is a risk that attackers can directly access the device from remote
and exploit the vulnerabilities (when no firewall with appropriate rules is
implemented, for example), an immediate update from a previous
version is highly recommended (see remarks in “actual version”).
S EN 26/29 1KHW000902-EN

NSD570 Mgmt. Actual version.
Vers. 1.19 This version supports the new features:
• SNMPv3 including access to MIB, traps, and user management.
• SNMP polling of commands and manipulation events.
• SNMP polling of trip counters.
• SNMP polling of configuration download counter.
• UTC time zone offset and DST settings.
Improvements and bugfixes:
• RTC synchronization via IRIG-B output modified (time signal derived
from SNTP), to avoid alarm “Wrong time from RTC” on line interfaces
due to a date conflict (their RTC is free running, i.e. no adjustments
by SNTP/IRIG-B, one minute before and one minute after midnight).
avoid alarm in case of short IRIG-B failures.
• Signal timing on real-time bus improved.
• Bug fixed where long SNTP polling intervals could lead to a module
reset when SNTP servers are not reachable.
An update to the latest version is required if the new features of the
Management LAN Interface G3LM or the IRIG-B output shall be used.
Otherwise it is not immediately necessary but recommended.
If the current firmware version on the Management LAN Interface G3LM
is 1.05 or lower, this firmware version cannot be downloaded directly to
the module by means of user interface HMI570, because a boot loader
update and a firmware update to version 1.07 on G3LM is required first.
Please refer to the update description available on the latest
“NSD570 Software & Documentation CD” (including the required
files/tools to update the boot loader and the firmware) or contact your
local representative and ask for the update procedure.
Update the firmware according the “Firmware Download Description
NSD570” (1KHW000896) and re-commission the Management LAN
Interface G3LM according to the “Commissioning Instructions NSD570
Management LAN Interface G3LM” (1KHW002232).
 Note: The firmware NSD570 Management can be downloaded to the Management

LAN Interface G3LM.
The newest firmware version can always be used for updating an NSD570
Management LAN Interface G3LM, but the latest user interface HMI570 must be
utilized.
S EN 27/29 1KHW000902-EN
7.3 Firmware Versions GOOSE LAN Interface

G3LS Initial version
Vers. 1.00 -> An update to the latest version is recommended (see remarks in
G3LS Bug fixed: Under certain circumstances it could happen that one
Vers. 1.01 command out of thousand transferred commands was delayed by max.
4-5 milliseconds compared to the average end-to-end delay.
-> An update to the latest version is recommended (see remarks in
G3LS Bugs fixed:
Vers. 1.03 • G3LS sent GOOSE frames with invalid stNum at startup.
• In case the RTC was synchronized with external GPS/IRIG-B sources,
the respective RTC alarms were not considered for PhyHealth and
EEHealth.
G3LS This version supports the new features:
Vers. 1.06 • Notification of a G3LS interface common alarm to the line interfaces
G3LA/G3LD/G3LE
G3LS In this version, the range of the Application Identification (APPID) is
Vers. 1.07 extended. With previous firmware versions, a mismatch with the
subscribed IEDs could occur, leading to a GOOSE communication failed
(GCF) alarm reported by G3LS.
If G3LS does not report GCF and the current version is 1.06
version”).
S EN 28/29 1KHW000902-EN

G3LS Actual version
• Signal timing on real-time bus improved.
If no IRIG-B signal is used to synchronize the RTC on G3LS, and the
Software & Documentation CD” including the actual NSD570 G3LS
firmware version.
Update the firmware according the “Firmware Download Description
NSD570” (1KHW000896) and re-commission the equipment according
the “Commissioning Instructions NSD570” (1KHW000900).
 Note: The firmware NSD570 GOOSE can be downloaded to the GOOSE LAN
Interface G3LS.
The newest firmware version can always be used for updating an NSD570
GOOSE LAN Interface G3LS, but the latest user interface HMI570 must be
utilized.
7.4 Firmware Versions Not Upgradeable by the User

G1LC Initial version
C Vers. 1.00
G1LC With this version a counter reset on the two line interfaces G3LA/D in the
C Vers. 1.01 module rack by means of the Display Panel G1LC is possible (if required,
this feature can be disabled mechanically).
A sent or received command on G3LA/D will automatically activate the
Display Panel and display a corresponding message.
The configured baud rate for the RS-232 communication of the connected
line interface can be viewed with the Display Panel.
All the mentioned features above are only available if the micro controller
firmware version of the line interfaces G3LA or G3LD is greater or equal
to version 1.04.
G1LC The display of the status information was adapted to the improved BER
C Vers. 1.02 measurement method introduced with version 1.33 of NSD570 Digital.
G1LC This version supports the new alarms of the optional piggyback G1LOa
C Vers. 1.03 (Optical Interface) for the Digital Interface G3LD.
G1LC This version supports the new alarms and configuration settings of the
C Vers. 1.04 Ethernet Line Interface G3LE.
S EN 29/29 1KHW000902-EN

G1LC Actual version
C Vers. 1.05 Support for G3LS related functions has been added.
This version supports the new path protection (1+1) operation mode, with
two Line Interfaces in one NSD570 rack, sharing up to four Relay
Interfaces plugged in TPE 1 (no Relay Interfaces in TPE 2 required
anymore).
 Note: The micro controller firmware (C) for G1LC may not be upgraded by the
customer/user (the module has to be returned to the factory). The programmed
firmware version can be viewed by means of the Display Panel G1LC itself.
Anomaly List: < NSD570 > - S 2021-08-11
PGGA-PT1 2003-02-25 M. Buhl 2021-08-11 M. Strittmatter - EN 1/10
- - - - 1KHW000904SE Anomaly List
NSD570.doc
Anomaly List: < NSD570 >
Contents
2 Anomalies 2
2.1 Common Functions 2
2.1.1 Manual Loop Test (remote activation) 2
2.1.2 No incoming GPS synchronization signal (IRIG-B) 2
2.1.3 Configuration of individual relay interfaces per line interface 3
2.2 NSD570 Analog 3
2.2.1 Accuracy of signal to noise and level measurement 3
2.2.2 Loop test 4
2.2.3 1+1 path protection with G3LA as line interface 4
2.3 NSD570 Digital 5
2.3.1 Accuracy of bit error rate measurement 5
2.3.2 Interchanging the two digital line interfaces in the same rack 5
2.3.3 Command outputs during link failure 5
2.3.4 Using G.703 interface while Optical Interface G1LO is plugged onto G3LD 6
2.3.5 Start up problems of G.703 interface in self-loop configuration 6
2.3.6 Optical Interface G1LO with broken or disconnected optical fibers 6
2.3.7 Using G.703 or RS-530 interfaces while E1/T1 Interface G1LE is plugged onto G3LD 7
2.3.8 Loop test 7
2.3.9 1+1 path protection with G3LD as line interface 8
2.4 NSD570 Ethernet 8
2.4.1 Configuration upload may fail via G3LM when used in a specific rack assembly 8
2.5 NSD570 Management 9
2.5.1 G3LM may crash if its own device address is in the list for SNMP alarm polling 9
2.5.2 RTC of G3LM does not obtain the time provided by the on-board NTP/SNTP client 9
2.6 HMI570 “LAN” 9
2.6.1 Communication between LAN interface and line interfaces 9
2.6.2 Menu item “View Configuration” 10
S EN 2/10 1KHW000904-EN
This document describes the currently known anomalies in the behavior of the NSD570
teleprotection system. Such anomalies express themselves in unexpected system behavior not
described in the Operating Instructions NSD570 (1KHW000890-EN), 13th Edition.
This document is updated immediately after a new anomaly has been discovered and verified. For
that reason, the approval date instead of a revision index is normally used to identify consecutive
versions of this document (if no regular revision of the Operating Instructions including the annex is
at issue). The actual version can therefore be derived from the newer date in either the “Rev.” box
or in the “Approved” box in the header of this page.
2 Anomalies
For each anomaly, the following information is given:
- the types of the hardware modules and/or the versions of firmware or software taken to be
responsible for the observed anomaly,
- a description of the anomaly,
- a workaround (if any).
Please note that no intermediate firmware and software versions are stated in the following
sections if the anomaly is not yet eliminated (just the first affected version and the latest released
version; for released intermediate versions, please refer to the document “Compatibility
Requirements” in the annex of the NSD570 Instruction Manual).
2.1 Common Functions
2.1.1 Manual Loop Test (remote activation)

2.1.1.1 Hardware, software and/or firmware versions
G3LA, NSD570 Analog FW Vers. 1.05 - 1.18
G3LD, NSD570 Digital FW Vers. 1.14 - 1.50
G3LE, NSD570 Ethernet FW Vers. 3.25 - 3.43
HMI570 „PC“ SW Vers. 1.03 - 1.49
HMI570 „LAN“ SW Vers. 1.10 - 1.41
2.1.1.2 Description
If a remote manual loop test is activated by means of the HMI570 (connected with remote device ->
Manual Loop Test), the displayed status information is outdated.
2.1.1.3 Workaround
For G3LA / NSD570 Analog -> wait a few minutes (depending on the programmed bandwidth) and
perform a remote status upload to get the actual loop test time.
For G3LD / NSD570 Digital and G3LE / NSD570 Ethernet -> wait a few seconds and perform a
remote status upload to get the actual loop test time.
2.1.2 No incoming GPS synchronization signal (IRIG-B)

HMI570 „PC“ SW Vers. 1.03 - 1.48
HMI570 „LAN“ SW Vers. 1.10 - 1.41
S EN 3/10 1KHW000904-EN
2.1.2.2 Description
If the GPS synchronization for the internal RTC is configured to “ON” but there is no incoming
IRIG-B signal, an alarm “Begin no signal (IRIG-B) on RTC” will be generated correctly by the
device. However, in addition the alarm “Wrong time from RTC” will appear and disappear approx.
every minute and will therefore fill the event recorder with dispensable alarm messages.
2.1.2.3 Workaround
Remove the external source for the alarm condition. Check the wiring and source of the IRIG-B
signal and also check connector X103 on G1LB.
The anomaly is eliminated in NSD570 Analog FW Vers. 1.18 or higher, and in NSD570 Digital
FW Vers. 1.50 or higher. Use the newest available firmware version for updating your analog or
digital NSD570 link.
2.1.3 Configuration of individual relay interfaces per line interface

HMI570 „PC“ SW Vers. 1.03 - 1.49
HMI570 „LAN“ SW Vers. 1.10 - 1.41
2.1.3.2 Description
If more than four relay interfaces are configured per line interface, equipment faults may occur.
Two line interfaces in the module rack may accidentally be configured for using the same relay
interface. This cannot be detected and therefore not be avoided by the HMI570, because each line
interface is configured separately.
In both above cases, inadmissible operating conditions may arise and even malfunctions
have to be expected!
2.1.3.3 Workaround
If only one line interface is plugged in the module rack, make sure that a maximum of four relay
interfaces are configured (if required, they may be plugged in any assigned slot of the rack).
If two line interfaces are plugged in the rack, make sure that only a maximum of four relay
interfaces in the corresponding rack half are configured (i.e. line interface TPE 1 uses relay
interfaces in the left rack half only and TPE 2 uses relay interfaces in the right rack half only).
2.2 NSD570 Analog
2.2.1 Accuracy of signal to noise and level measurement

2.2.1.2 Description
The guard signal of the NSD570 Analog version is modulated to accommodate also the Embedded
Operation Channel (EOC). As a result, the measured level of the received guard signal, which can
be viewed by means of the HMI570 status display, changes continuously (approx. 2.5 dB).
Also the SNR value will vary (since it is also determined in the guard channel), depending on the
packets that are currently transmitted via the EOC.
In case the EOC is enabled in one NSD570 Analog of a link and accidentally disabled in the other,
the NSD570 with the EOC configured to “off” may sporadically report an SNR alarm.
The measured Tx level (which can also be viewed in the HMI570 status display) is only accurate if
the line impedance matches approx. 600 Ohm.
S EN 4/10 1KHW000904-EN
2.2.1.3 Workaround
For exact Rx level and SNR measurements of the received signal, switch off the EOC by means of
the HMI570.
Make sure that the EOC is either enabled or disabled in both NSD570 Analog of a link.
For exact Tx level measurement, make sure that the line impedance matches approx. 600 Ohm. To
verify this, a comparison measurement can be done by opening the terminals to the line and
terminate the output circuit with a 600 Ohm resistor.
2.2.2 Loop test

2.2.2.2 Description
Whenever an automatically initiated loop test is not correctly received, the next automatically
initiated loop test will be performed 5 minutes later. As long as the automatically initiated loop tests
fail, the interval between them will stay at 5 minutes. If in this situation a manual loop test is
performed, the next automatically performed loop test will take place after the configured loop test
interval irrespective on whether the manual loop test was successful or not.
2.2.2.3 Workaround
None.
2.2.3 1+1 path protection with G3LA as line interface

2.2.3.2 Description
For the configuration “1+1 Device Operation Mode”, with two G3LA as line interfaces or with G3LA
as standby line interface in TPE 2, the transmission time may increase by up to 6 milliseconds, if
the switchover from main to standby channel or vice versa just takes place during command
reception.
Furthermore, a persistent command may be shortly interrupted at the output during switchover from
main to standby channel or vice versa (depending on the type of channel deterioration and the time
required to detect this alarm/switchover condition).
2.2.3.3 Workaround
None (the anomalies could be avoided when using duplicated relay interfaces G3LR in TPE 2).
Use the G3LA as standby line interface (TPE 2) in “1+1 Device Operation Mode” if the second
line interface is a G3LD or G3LE (this is the default configuration anyway).
Utilize a maximum number of three G3LR relay interfaces if G3LA shall be operated in 1+1
path protection mode (either way only four commands are available with G3LA, requiring two
G3LR, which can thus be protected in the “1+1 Device Operation Mode”).
S EN 5/10 1KHW000904-EN
2.3 NSD570 Digital
2.3.1 Accuracy of bit error rate measurement

G3LD, NSD570 Digital FW Vers. 1.14, 1.15, 1.16, 1.20, 1.22, 1.23, 1.31, 1.32
HMI570 „PC“ SW Vers. 1.03, 1.04, 1.11
HMI570 „LAN“ SW Vers. 1.10, 1.11
2.3.1.2 Description
The short term bit error rate (BER) measurement, which can be viewed by means of the HMI570
status display, is only estimation for low bit error rates and may differ from the prevailing channel
BER by up to factor 3.
The BER alarm threshold is not affected by this anomaly but the BER alarm may “flicker” (event
recorder entries) when a threshold of 1E-05 or lower is configured.
2.3.1.3 Workaround
No specific action required (a BER alarm threshold of 1E-04 or 1E-03 may be configured if too
many event recorder entries shall be avoided).
The anomaly is eliminated in NSD570 Digital FW Vers. 1.33 and higher. Use the newest
available firmware version for updating your digital NSD570 link.
2.3.2 Interchanging the two digital line interfaces in the same rack
G3LD, NSD570 Digital FW Vers. 1.20, 1.22, 1.23, 1.31, 1.32, 1.33
HMI570 „PC“ SW Vers. 1.03, 1.04, 1.11, 1.12
HMI570 „LAN“ SW Vers. 1.10 - 1.12
2.3.2.2 Description
Misconfiguration of relay interfaces can result in a continuing system reset and a connection to the
equipment by means of the HMI570 may become impossible in the following case:
Assuming that a Digital Interface G3LD is configured as TPE 1 with one or more Relay Interfaces
G3LR assigned. If this card is removed and plugged into slot 6 (N58) of TPE 2, the Digital Interface
G3LD will not recognize the configured relay interfaces (actually for TPE 1) and will perform a
continuing system reset.
Note that the anomaly described above is not true for digital line interfaces ex-works, which have
not been configured before. They can be plugged in both available slots of the rack and will start up
correctly (unless they are not damaged).
2.3.2.3 Workaround
Plug the Digital Interface G3LD into slot 1 (N28), configure the relay interfaces of TPE 1 to “off” and
the required relay interfaces of TPE 2 to “on”. Download the modified configuration to the device
and activate “Reset Device”. Now the G3LD module can be plugged into slot 6 (N58). A connection
by means of the HMI570 should be possible (if not, the line interface is damaged and must be
replaced). Continue with configuration of the line interface for TPE 2.
2.3.3 Command outputs during link failure

G3LD, NSD570 Digital FW Vers. 1.14, 1.15, 1.16, 1.20, 1.22, 1.23, 1.31, 1.32, 1.33
HMI570 „PC“ SW Vers. 1.03, 1.04, 1.11, 1.12
HMI570 „LAN“ SW Vers. 1.10 - 1.12
S EN 6/10 1KHW000904-EN
2.3.3.2 Description
The response of the command outputs to a link failure can be set by means of the HMI570 for one
out of four different behavior patterns.
For the setting "do not change" the command outputs of the NSD570 Digital may not release as
expected (see Section 5.5.2 in the manual) at very high bit error rates (≥1E-02) or when the
incoming signal is lost.
2.3.3.3 Workaround
If none of the other three settings fits your requirements, the wrong behavior can be delayed by
setting the “Link Failure Pickup Time” to a higher value (e.g. the maximum of 15 seconds; during
this time the link may have reestablished and no incorrect action will take place).
2.3.4 Using G.703 interface while Optical Interface G1LO is plugged onto G3LD
G3LD, NSD570 Digital FW Vers. 1.20, 1.22, 1.23, 1.31, 1.32
HMI570 „PC“ SW Vers. 1.03, 1.04, 1.11
HMI570 „LAN“ SW Vers. 1.10, 1.11
2.3.4.2 Description
If the optional piggyback G1LO (the optical interface for the NSD570 Digital) is plugged onto the
Digital Interface G3LD, it is no longer allowed to configure and use the interfaces on the G3LD
“main” board. No reliable operation is possible in this case!
In case of the G.703 interface, this will lead to a permanent AIS alarm for example.
2.3.4.3 Workaround
If the interfaces on the G3LD “main” board shall be configured and used again, take the NSD570
link out of service, remove the Optical Interface G1LO from G3LD and re-commission the NSD570
link for the standard interface on G3LD that is required.
2.3.5 Start up problems of G.703 interface in self-loop configuration

HMI570 „PC“ SW Vers. 1.03 - 1.49
HMI570 „LAN“ SW Vers. 1.10 - 1.41
2.3.5.2 Description
If the G.703 interface of the NSD570 Digital is looped with itself via the RJ45 terminals (e.g. for test
purposes when no remote device is available), it can happen in seldom cases after power up the
equipment that the receiver may not synchronize to its own sending signal.
2.3.5.3 Workaround
Plug in the wires for the local loop only after the equipment was powered up and the startup
process of the line interface G3LD has finished (i.e. after all LEDs have light up once).
2.3.6 Optical Interface G1LO with broken or disconnected optical fibers

G3LD, NSD570 Digital FW Vers. 1.20, 1.22, 1.23, 1.31, 1.32
HMI570 „PC“ SW Vers. 1.03, 1.04, 1.11
HMI570 „LAN“ SW Vers. 1.10, 1.11
S EN 7/10 1KHW000904-EN
2.3.6.2 Description
If the external optical fibers to the G1LO optical interface of the NSD570 Digital are interrupted, the
following behavior may be observed:
- If both fibers (Tx/Rx) are interrupted, multiple (redundant) “Begin & End Loss of Signal” entries
are logged instead of one.
Therefore, the event recorder is filled with dispensable alarm messages.
- If only one optical fiber is interrupted, the device that still receives signals from the remote
station detects bit errors (which are “produced” by the remote device because the synchroni-
zation endeavors on the “lost” Rx signal affect the Tx signal as well).
2.3.6.3 Workaround
Remove the source of the alarms, event recorder entries and bit errors by restoring the optical fiber
connection between the two devices (reconnect the optical plugs in the appropriate sockets or fix
the broken fibers.
2.3.7 Using G.703 or RS-530 interfaces while E1/T1 Interface G1LE is plugged onto G3LD
G1LE HW Vers. 2
HMI570 „PC“ SW Vers. 1.12 - 1.49
HMI570 „LAN“ SW Vers. 1.12 - 1.41
2.3.7.2 Description
If the optional piggyback G1LE (the E1/T1 interface for the NSD570 Digital) is plugged onto the
Digital Interface G3LD, it is no longer allowed to configure and use the interfaces on the G3LD
“main” board. No reliable operation is possible in this case!
2.3.7.3 Workaround
If the interfaces on the G3LD “main” board shall be configured and used again, take the NSD570
link out of service, remove the E1/T1 Interface G1LE from G3LD and re-commission the NSD570
link for the standard interface on G3LD that is required.
For NSD570 Digital FW Vers. 1.48 and higher, the G3LD reports the alarm “Piggyback does not
match configuration” in case the E1/T1 Interface G1LE Vers. 2 is plugged but not configured
correctly.
2.3.8 Loop test

2.3.8.2 Description
Whenever an automatically initiated loop test is not correctly received, the next automatically
initiated loop test will be performed 5 minutes later. As long as the automatically initiated loop tests
fail, the interval between them will stay at 5 minutes. If in this situation a manual loop test is
performed, the next automatically performed loop test will take place after the configured loop test
interval irrespective on whether the manual loop test was successful or not.
2.3.8.3 Workaround
None.
S EN 8/10 1KHW000904-EN
2.3.9 1+1 path protection with G3LD as line interface

2.3.9.2 Description
For the configuration “1+1 Device Operation Mode”, with two G3LD as line interfaces or with G3LD
as main line interface in TPE 1, the transmission time may increase by up to 4 milliseconds, if the
switchover from main to standby channel or vice versa just takes place during command reception.
Furthermore, a persistent command may be shortly interrupted at the output during switchover from
main to standby channel or vice versa (depending on the type of channel deterioration and the time
required to detect this alarm/switchover condition).
During switchover from main to standby channel (or vice versa), some few bit errors might be
caused. If the BER Alarm Threshold is configured too sensitive (i.e. 1E-05 or 1E-06), the active line
interface may thus raise a BER alarm. As a consequence, the line interfaces might be switching
there and back every 200 seconds in worst case (200 seconds is the BER alarm detection time).
2.3.9.3 Workaround
None (the anomalies could be avoided when using duplicated relay interfaces G3LR in TPE 2).
Use the G3LD as main line interface (TPE 1) in “1+1 Device Operation Mode” if the second line
interface is a G3LA or G3LE (this is the default configuration anyway).
Use a BER Alarm Threshold in the range from 1E-04 to 1E-01 (it is recommended to use the
default setting 1E-03).
2.4 NSD570 Ethernet
2.4.1 Configuration upload may fail via G3LM when used in a specific rack assembly
G3LM, NSD570 Management FW Vers. 1.03 – 1.19
HMI570 „PC“ SW Vers. 1.21 - 1.49
HMI570 „LAN“ SW Vers. 1.21 - 1.41
G3LC HW Vers. 0, 1
G1LC HW Vers. 0
G1LC µC Vers. 1.00 - 1.06
2.4.1.2 Description
If the Ethernet Line Interface G3LE is used in a Module Rack G7BI, which is also equipped with a
Management LAN Interface G3LM and a Display Panel G1LC, and the Common Interface G3LC
(contained in Module Rack G7BI) has hardware version 0 or 1, the configuration upload from G3LE
via G3LM may fail.
2.4.1.3 Workaround
Since 2009, Module Racks G7BI are delivered ex works with built-in G3LC hardware version 2, for
which the described anomaly does not apply. It only takes place if Module Racks G7BI delivered
earlier are to be retrofit with Ethernet Line Interface G3LE and with LAN Interface G3LM (to allow
remote management).
If the above is the case, exchange the equipment rack type G7BI with a newer one that contains
G3LC hardware version 2. This might be required anyway, as G7BI racks delivered before 2009 do
not allow RS-485 station bus operation for G3LM (only TPE 1 and TPE 2 in the same rack as
G3LM are accessible from remote; please refer to the document “Compatibility Requirements” in
the annex of the NSD570 Instruction Manual). Thus, only one rack in the substation has usually to
be replaced, in order to reach all existing racks with one G3LM via station bus (max. 64 NSD570).
S EN 9/10 1KHW000904-EN
2.5 NSD570 Management
2.5.1 G3LM may crash if its own device address is in the list for SNMP alarm polling
2.5.1.2 Description
If the SNMP alarm polling function of the Management Interface G3LM is enabled and the G3LM
device address is accidentally added to the device list for the line interfaces to be polled, then the
module G3LM may crash and stop working.
As the Management Interface G3LM does not belong to the type of interfaces where alarm polling
can be applied (only line interfaces G3LA, G3LD and G3LE), it is in fact an invalid configuration to
add the G3LM device address to the device list for SNMP alarm polling.
2.5.1.3 Workaround
Do not include the G3LM device address into the device list for the SNMP alarm polling function.
For NSD570 Management FW Vers. 1.16 and higher, the G3LM ignores alarm polling requests to
its own device address and is thus not affected anymore by such misconfigurations.
2.5.2 RTC of G3LM does not obtain the time provided by the on-board NTP/SNTP client
2.5.2.2 Description
Even if the NTP/SNTP time server is running and the on-board NTP/SNTP client of G3LM is
enabled and configured properly (HMI570 menu item “SNTP Time Parameters”), the internal RTC
(real time clock) of the G3LM module will not obtain this synchronized real time signal
automatically.
2.5.2.3 Workaround
To synchronize the internal RTC of G3LM to the time information provided by the on-board
NTP/SNTP client, it is necessary to configure the menu item “GPS sync” to on (to be found in
HMI570 under “Management Interface Configuration” – “Management Interface”).
Furthermore, the IRIG-B output on G3LMa has to be interconnected with the IRIG-B input of the
same NSD570 rack (e.g. by using the special G3LMa*CABLE STATION BUS/SYNC).
2.6 HMI570 “LAN”
2.6.1 Communication between LAN interface and line interfaces

G3LL, HMI570 “LAN” SW Vers. 1.10 - 1.41
2.6.1.2 Description
The LAN Interface G3LL communicates with the line interfaces G3LA or G3LD in the same rack via
the station bus interface. Caused by massive interferences on the station bus this communication
may be blocked eventually.
2.6.1.3 Workaround
Use the following menu item of the user interface HMI570 “LAN” to reset the communication:
Menu: “HMI570 Options” - “LAN Interface” - “Reset communication”
If this happens every once a while, the wiring of the station bus should also be checked.
S EN 10/10 1KHW000904-EN
2.6.2 Menu item “View Configuration”

G3LL, HMI570 “LAN” SW Vers. 1.10 - 1.41
2.6.2.2 Description
If the menu item “View Configuration” is activated by clicking on the corresponding link, the
following message will appear on the screen:
View Configuration is not supported in this version of the HMI570 LAN.
Please use Edit Configuration instead.
The reason is that the “off-the-shelf” PC/104 board on the LAN interface G3LL does not provide the
necessary amount of RAM to build up this memory-consuming page.
2.6.2.3 Workaround
If you like to view the entire configuration of the NSD570 (connected from remote via the LAN
Interface) on one browser page or if you like to print out a breakdown configuration, proceed as
follows:
Upload the configuration from device by means of the HMI570 “LAN”
Save the configuration to disk
Start the HMI570 “PC” (which must be installed on your local PC/notebook)
Load the configuration from disk
View and print the configuration
Commissioning Instructions: < NSD570 LAN Interface > - C 2010-01-04
PSND 2004-04-06 H. Schnyder 2010-01-04 M. Strittmatter - EN 1/18
- - - - 1KHW001289CE Commissioning
of LAN Interface G3LL.doc
Commissioning Instructions: < NSD570 LAN Interface >
This document describes commissioning of the NSD570 LAN Interface type G3LL, an optional module for the
NSD570 Teleprotection System.
Contents:
C Commissioning Instructions for the NSD570 LAN Interface ........................ 3

C.1 General......................................................................................................... 3
C.4 Physical connection to the LAN Interface G3LL .......................................... 4
C.5 SSH Connection ........................................................................................... 6
C.6 Configure the networking parameters .......................................................... 8
C.7 File transfer to/from NSD570 LAN Interface .............................................. 12
C.8 Put the newest Instruction Manual on the NSD570 LAN Interface G3LL .. 14
C.9 Backup and restore of the network configuration parameters ................... 14
C.10 Change root password ............................................................................... 14
C.11 Determine Ethernet MAC address ............................................................. 15
C.12 Test HMI570 LAN functionality................................................................... 15
Sheet NSD570 Commissioning Report ....................................................... C1 – C2
C EN 2/18 1KHW001289-EN

PC with Windows 7, XP or Vista Commissioning PC
Ethernet cross connect cable
SSH client Software PuTTY 0.60 (http://www.putty.nl/)
(putty-0.60-installer.exe)
Notes:

“Ethernet” and hardware of NSD570
During commissioning of the NSD570 LAN Interface, the networking

Caution parameters will be changed and stored in the Compact Flash card.
A misconfiguration of these parameters can inhibit any access to the LAN
Interface after reboot.
There will be no way to change or redo the misconfigured parameters except
to replace the Compact Flash card or to reprogram it with the image file. The
reprogramming can only be done according to “Copy Instructions Compact
Flash Card G3LL” (1KHW001291).
For commissioning of the NSD570 LAN Interface it is therefore highly
recommended to have the equipment available which is mentioned in
“Copy Instructions Compact Flash Card G3LL” (1KHW001291) and the
image file or at least a programmed CompactFlash card as spare part.
Designation Meaning

[X] Test passed or jumper is set
G3LL Module type
RTC Real Time Clock
Rx Receiver
Tx Transmitter
C EN 3/18 1KHW001289-EN
C Commissioning Instructions for the NSD570 LAN Interface
C.1 General
This document is part of the Operating Instructions NSD570 (1KHW000890) and describes the
programming, testing and commissioning of the NSD570 LAN Interface type G3LL.
Please note that NSD570 devices in the rack (Analog/Digital/Ethernet) should be programmed and
tested or commissioned properly before the LAN Interface is put into service (the checks in Section
C.1.2 may then be skipped because they are already done; please refer to documents
1KHW000898 “Programming and Testing Instructions NSD570” and 1KHW000900
“Commissioning Instructions NSD570” in the annex of the Operating Instructions).
After the NSD570 devices are tested or commissioned, switch of the power supply of the module
rack, insert the LAN Interface in slot N84, connect the optional connecting cables and follow the
steps below for setting up the LAN connection.

terminals and RJ45 socket) or at the terminals and sockets of the optional connecting cables.




Check the status of the plugged power supply modules which is indicated by the LEDs on the front
panel (green = Ok, red = fail, dark = not assembled).
C EN 4/18 1KHW001289-EN
C.3.1 Install the SSH client software

Before you can access the LAN Interface G3LL over a SSH connection it is necessary to install a
SSH client on the PC. This has to be done only the first time. It is recommended to use the
freeware tool PuTTY found on the “NSD570 Software & Documentation CD”
(1KHW000925R0100).
Execute the file “putty-0.60-installer.exe” to install this SSH client on your PC.
C.4 Physical connection to the LAN Interface G3LL

To commission an NSD570 LAN Interface, there is an Ethernet connection to the G3LL card
necessary. The LAN Interface can be connected directly to the commissioning PC over an Ethernet
cross connect cable or over a switch or hub.
C.4.1 Connection over an Ethernet switch or hub

The RJ45 connector (X203) of the LAN Interface G3LL must be connected with an Ethernet switch
or hub. The connecting cable must be a straight Ethernet cable (not a cross connect cable). Now
it is possible to connect the LAN Interface G3LL from every PC that is connected to the Ethernet
LAN.
 Note: The factory default IP address of the LAN Interface (172.20.162.54) must not
be used by another device in the Ethernet LAN.
C.4.2 Direct connection over an Ethernet cross connect cable

The RJ45 connector (X203) of the LAN Interface G3LL must be connected with the Ethernet port of
the commissioning PC. The connecting cable must be an Ethernet cross connect cable.
C.4.3 Network configuration

The subnet mask of the commissioning PC must be configured to 255.255.255.0 and the IP
address has to be in the same subnet (example 172.20.162.23).
C EN 5/18 1KHW001289-EN
The command „ipconfig“ in the DOS box shows the settings (see below).
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : #####

IP Address. . . . . . . . . . . . . . . . . . : 172.20.162.23
Subnet Mask . . . . . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . . . . . : #####

Note: If the IP address and subnet mask of your PC is already set as shown above
you can continue with the next point (C.4.4 ).
If you have to change IP address and subnet mask, please set them back to
the original values after finishing the G3LL commissioning.
Change the network settings of the commissioning PC

The following steps show, how the subnet mask can be configured (Windows® XP).
Start → Settings → Network Connections → Local Area Connection → Properties
The window “Local Area Connection Properties” (the left one below) should appear. Mark “Internet
Protocol (TCP/IP)“ and press “Properties”. The window “Internet Protocol (TCP/IP) Properties”
appears (the right one below) and there the network settings can be configured.
C EN 6/18 1KHW001289-EN
C.4.4 Ethernet connection test (ping)

The „ping“ command in the DOS box can be used to test the IP connection to the LAN Interface.
C:\Documents and Settings\userxy>ping 172.20.162.54
Pinging 172.20.162.54 with 32 bytes of data:
Reply from 172.20.162.54: bytes=32 time<10ms TTL=62

Ping statistics for 172.20.162.54:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C.5 SSH Connection
C.5.1 Establish a SSH connection

There must be a SSH connection between the commissioning PC and the NSD570 LAN Interface
G3LL in order to set the following parameters:
• Network parameters (IP Address etc.)
using the ctool
• Time and date
• Root password
1. Start the application „putty.exe“

2. The “PuTTY Configuration” window appears. Type in the currently configured IP address of the
NSD570 LAN Interfaces G3LL (default is 172.20.162.54) in the field “Host Name”.
Press the “Open” Button (you can save the IP address with the Save button).
C EN 7/18 1KHW001289-EN
3. The first time you connect an NSD570 LAN Interface G3LL, the “Host Identification” dialog box
will be shown. Press “Yes” to store the public key locally on your PC / Notebook and the dialog
box will not be shown anymore the next time.
4. Enter username and password. The factory default user is “root” and the default password for
root is “TfATEwimt5ya” (first character of every word in the sentence “The first ABB
Teleprotection Equipment was installed more than 50 years ago”).
5. The SSH connection to the NSD570 LAN Interface is now established.

It is now possible to execute commands on the LAN interface.
Caution Through this SSH connection you are able to execute a number of Linux
console commands. But it is recommended to work with the commands
available in the main menu of the “ctool” instead of using Linux commands.
Do not execute any unknown commands because this could cause
malfunction of the NSD570 LAN Interface.
C.5.2 Connection termination

An established connection can be terminated with the “exit” command.
C EN 8/18 1KHW001289-EN
C.6 Configure the networking parameters
C.6.1 Start the ctool

The ctool can be started with the following commands in the SSH console:
• cd /ctool
• . /ctool.sh
The Main Menu appears:
C.6.2 Networking Parameter

Note: The NSD570 LAN Interface G3LL must be rebooted after changing the
network settings. The modified network settings will be active after the reboot.
It is very important to remember the values of the modified settings.
It will not be possible to access the NSD570 LAN Interface without
knowing the current IP Address !!
If the value of a modified IP address is forgotten, the CompactFlash card of
the NSD570 LAN Interface must be rewritten with the image file, see “Copy
Instructions Compact Flash Card G3LL” (1KHW001291).
Afterwards the default IP address can be used to access the LAN Interface.
C.6.2.1 DHCP or Static IP-Address
Selection: Press „1“ and Enter in the “Main Menu”

Function: The submenu allows changing between DHCP (Dynamic Host Configuration Protocol) and static IP
address.
Default: „Static IP Address“
Caution DHCP (Dynamic Host Configuration Protocol) is not recommended with the
NSD570 LAN Interface G3LL. The NSD570 LAN Interface in DHCP mode
will not start without the presence of a DHCP server.
C EN 9/18 1KHW001289-EN
C.6.2.2 IP Address

Function: The currently configured IP address is displayed. Enter the new IP address. Only valid IP
addresses will be accepted.
Remarks: The IP address can only be configured if „Static IP Address“ is set (see “DHCP or static IP-
Address”).
Default: 172.20.162.54
C.6.2.3 Subnet Mask

Function: The currently configured subnet mask is displayed. Enter the new subnet mask. Only valid subnet
masks will be accepted.
Remarks: The Subnet mask can only be configured if „Static IP Address“ is set (see “DHCP or static IP-
Address”).
Default: 255.255.255.0
C.6.2.4 Default Gateway

Function: The currently configured Default Gateway is displayed. Enter the new Default Gateway. Only valid
Default Gateways will be accepted.
Remarks: The Default Gateway can only be configured if „Static IP Address“ is set (see “DHCP or static IP-
Address”)
Default: 172.20.162.1
C.6.2.5 Computer Name

Function: Displays the currently configured Computer Name. Enter the new Computer Name.
Remarks: The Computer Name appears as console prompt.
Default: NSD570LAN
C.6.2.6 Domain Name

Function: Displays the currently configured Domain Name. Enter the new Domain Name
Default: noname.com
C EN 10/18 1KHW001289-EN
C.6.2.7 Domain Nameserver (DNS)

Function: Displays the currently configured Domain Nameservers.
Enter first the number of Domain Nameservers to configure. Afterwards enter the IP Addresses of
the Domain Nameservers. Only valid IP addresses will be accepted.
Remarks: A maximal number of 3 Domain Nameservers can be configured.
C.6.2.8 FTP Server ON/OFF

Function: Toggles the FTP Server of the G3LL on/off.
Default: FTP Server disabled.

Note: For security reasons, the FTP server should be disabled if it is not
momentarily needed for transfer of large file structures (e.g. replacing the
whole HMI570).
For a small number of files (e.g. backup configuration files, as described in
Section C.7) the use of the “SSH Secure File Transfer” is recommended
instead.
C.6.2.9 System Logging Options
Selection: Press „9“ and Enter in the “Main Menu” - a submenu appears:

Note: “System logging” in this section always means the logging of the Linux system
itself. Note that the web server and the HMI570 both keep their own separate
logging mechanisms, which are always enabled.
The system logging should only be turned on temporarily for debugging
purposes!
C.6.2.9.1 Logging ON/OFF NOW
Selection: Press „1“ and Enter in the “Logging Options Menu”

Function: Immediately starts or shuts down the Linux system logging on the running system.
C.6.2.9.2 Logging OFF for All Coming Bootups

Function: There will be no system logging from the next restart on.
Remark: This setting is the default for logging.
C EN 11/18 1KHW001289-EN
C.6.2.9.3 Logging ON only on Next Bootup

Function: The system logging will be active upon the next restart until the system is shut down again.
Afterwards the system logging will be turned off again if the settings are not changed manually.
C.6.2.9.4 Logging ON for All Coming Bootups

Function: From the next restart on, the system logging will always be active (even after further restarts) until it
is turned off in the ctool again.
C.6.2.9.5 Save Log Files from tmpfs to CompactFlash

Function: You will be prompted for a directory name. Enter a name (e.g. “bak_logfiles”) and copies of all log
files will be placed in a corresponding subdirectory of /tmp (e.g. “/tmp/bak_logfiles”).

Note: The log files are kept in RAM (tmpfs). They are deleted when the system is
being shut down or reset. To keep the logfiles for later debugging purposes,
save them to the CompactFlash.
C.6.2.9.6 Show Logging Status

Function: Displays if the logging is active at the moment and the logging settings after coming bootups.
C.6.2.9.7 Back to Main Menu

Function: Exits the Logging Submenu and displays the Main Menu again.
C.6.2.10 Local Backup

Function: All files containing network configuration parameters will be copied into the backup directory
(”/ctool/backup”).
C.6.2.11 Local Restore

Function: All files containing network configuration parameters will be copied from the backup directory
(”/ctool/backup”) to their appropriate location in file system of the NSD570 LAN Interface G3LL.
C.6.2.12 Set Time and Date

Function: Adjusts time and date.
Enter new time and data in the following format. Values in [ ] are optional.
C EN 12/18 1KHW001289-EN
Format to use: MM/DD[/YYYY] hh:mm[:ss]

MM - month (2 digits)
DD - day within month (2 digits)
hh - hour (2 digits)
mm - minute (2 digits)
YY - year (4 digits, optional)
ss - second (2 digits, optional)
C.6.2.13 Show all Network Parameters

Function: Lists all network parameters that can be set within ctool.
(Logging parameters are listed separately in the “System Logging Options” submenu under “Show
Logging Status”)

Note: Please note that if you have changed the settings, they will not be in effect
until the system has been restarted, but already be shown.
C.6.2.14 Reset LAN Interface

Function: Resets the LAN Interface
C.6.2.15 Exit ctool

Function: Exits the ctool

Note: Please note, you must reboot the NSD570 LAN Interface after changing the
network settings.
C.7 File transfer to/from NSD570 LAN Interface

There are a lot of tools which support file transfer over SSH but it is recommended to use the
“pscp” tool which is included in PuTTY.

Note: File transfer could be done using FTP. But this is not secure and therefore not
recommended. For using FTP the FTP server must be running, it can be
activated in the ctool and will need a restart of the LAN Interface.
C.7.1 Get file(s) from the NSD570 LAN Interface G3LL

1. Start the local command line
Start – Run… – “cmd”
2. Change to the PuTTY directory (Default C:\Program Files\PuTTY\)
3. Type following command to copy files into “C:\<localPath>\”
“pscp -v root@<IP Address>:/<remotePath>/<filename> C:\<localPath>\”
4. Insert the password (Default “TfATEwimt5ya”)
C EN 13/18 1KHW001289-EN

Note: To get all files from a folder the * character can be used instead of the
filename.
C.7.2 Put file(s) on the NSD570 LAN Interface G3LL

1. Start the local command line
Start – Run… – “cmd”
2. Change to the PuTTY directory (Default C:\Program Files\PuTTY\)
3. Type following command to put <fileName> into the LAN Interface folder “/<remotePath>/”
“pscp -v C:\<localPath>\<fileName> root@<IP Address>:/<remotePath>/”
4. Insert the password (Default “TfATEwimt5ya”)

Note: To put all files from a folder onto the NSD570 LAN Interface the * character
can be used instead of the filename.
C EN 14/18 1KHW001289-EN
C.8 Put the newest Instruction Manual on the NSD570 LAN Interface G3LL
1. Copy the newest instruction manual on the NSD570 LAN Interface with pscp (see C.7.2)
“pscp -v C:\<localPath>\1KHW000890-EN-NSD570.pdf root@<IP
Address>:/g3ll/tomcat/webapps/hmi570/InstructionManual/”

Note: The name of the Instruction Manual “1KHW000890-EN-NSD570.pdf” must not
change!
C.9 Backup and restore of the network configuration parameters

The files containing the NSD570 LAN Interface G3LL network configuration parameters can be
backed up to the commissioning PC and restored from there back to the NSD570 LAN Interface.
It is recommended to use the “pscp” tool for that purpose. It is included in PuTTY.
C.9.1 Create Backup

Execute the following steps to create a backup of the NSD570 LAN Interface network configuration
parameters and download them to the commissioning PC.
2. Establish a SSH connection to the LAN interface (see C.5.1)
3. Start ctool and execute “Local Backup” (see C.6.2.10)
4. Get the files from the NSD570 LAN Interface G3LL using “pscp” (see C.7.1) with the
command:
“pscp -v root@172.20.162.54:/ctool/backup/* C:\<localBackupFolder>\”
C.9.2 Restore Backup

Execute the following steps to restore a backup of the NSD570 LAN Interface network
configuration parameters. The files are uploaded from the commissioning PC.
1. Put the files from the PC to the NSD570 LAN Interface using “pscp” (see C.7.2)
“pscp -v C:\<localBackupFolder>\* root@172.20.162.54:/ctool/backup”
2. Establish a SSH connection to the LAN interface (see C.5.1)
3. Start ctool and execute “Local Restore” (see C.6.2.11)
4. The NSD570 LAN Interface must be rebooted after changing the network settings.
C.10 Change root password

The linux root password is necessary to access the LAN Interface over a SSH connection. The
factory default for root password is “TfATEwimt5ya” (first character of every word in the sentence
“The first ABB Teleprotection Equipment was installed more than 50 years ago”).
Type “passwd” in the SSH console to change the linux root password. You must type in the new
password twice.
C EN 15/18 1KHW001289-EN

Note: The linux root password must be changed after commissioning or by the
customer itself. The default password must not be used anymore for security
reasons.
The customer must keep the altered password safely. It is not possible to
connect the LAN Interface over SSH without knowing the root password.
C.11 Determine Ethernet MAC address

Note: This step is not mandatory to commission the NSD570 LAN interface G3LL.
However, the Ethernet MAC address is useful for troubleshooting and shall
therefore be documented in the test report.
Type “ifconfig” in the SSH console to view the Ethernet MAC address (HWaddr in the textbox
below).
eth0 Link encap:Ethernet HWaddr 00:30:59:01:9F:87

inet addr:172.20.162.47 Bcast:172.20.255.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:336982 errors:0 dropped:0 overruns:0 frame:0
TX packets:27081 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:41835948 (39.8 MiB) TX bytes:21863857 (20.8 MiB)
Interrupt:15
lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
C.12 collisions:0
Test HMI570 LANtxqueuelen:0
functionality
RX bytes:656 (656.0 iB) TX bytes:656 (656.0 iB)
At the end of the commissioning of the NSD570 LAN Interface, test the access and the basic
functionality of the HMI570 LAN.
1. Power up the NSD570 with LAN Interface G3LL and await the startup delay (approx. 3
minutes)
2. Start a web browser on a PC that is connected to LAN and has therefore access to the
NSD570 LAN Interface G3LL
3. Enter the URL http://<IP_LAN_Interface>/hmi570/index.jsp
where IP_LAN_Interface is the IP address of the LAN Interface that shall be connected
(e.g. http://172.20.162.54/hmi570/index.jsp).
4. To access the LAN Interface over an encrypted SSL connection, use the subsequent URL
(auto redirect to this address since HMI570 LAN version 1.13):
https://<IP_LAN_Interface>/hmi570/index.jsp
where <IP_LAN_Interface> is the IP address of the LAN Interface that shall be connected
(e.g. https://172.20.162.54/hmi570/index.jsp).
5. Click „HMI570 ( Human Machine Interface )“
6. “Log In” with User name “Service” and Password “welcome”
7. Click “Connect Device” and the button “TPE 1”
8. “Device connected” must appear
9. Click “Configuration”, “Upload From Device”
10. “Configuration upload successful” must appear
11. Click “Exit HMI570”, press button „Exit“ and close the browser
C EN 16/18 1KHW001289-EN

Note: If you access the LAN Interface G3LL over an encrypted SSL connection, the
browser informs you that there is a problem with the site’s security certificate
(examples for Internet Explorer messages see below).
Because self-signed certificates are used for the connection to the LAN
Interface G3LL, you can proceed with Yes (IE6) or click on the link “Continue
to this website” (IE7).
Internet Explorer version 6 (IE6):
Internet Explorer version 7 (IE7):
G3LL Commissioning Report EN C1/C2 HE

C.1 General

the equipment
Unit 1 Unit 2
Equipment connected to Via circuit breaker [ ]
adequate voltage source B9AS or B9AV
C.2 Check power supply Unit 1 Unit 2
LED indication on the front panel Unit 1 and Unit 2 Green LED [ ] [ ]

C.3.1 Install the SSH client software [ ]
C.4 Physical connection to the LAN
Interface
C.4.1 Connection over an Ethernet [ ]
switch or hub or
C.4.2 Direct connection over an [ ]
C.4.3 Network configuration IP address and subnet 172.20.162.23 [ ]
mask of the 255.255.255.0
commissioning PC
C.4.4 Ethernet connection test (ping) Ping test successful [ ]
C.6 Configure the networking

parameters
C.6.2.1 DHCP or Static IP-Address Static IP Address [ ]
DHCP [ ]
C.6.2.2 IP Address
(………..………..………..………..)
C.6.2.3 Subnet Mask
(………..………..………..………..)
C.6.2.4 Default Gateway(s)
(………..………..………..………..)
C.6.2.5 Computer Name
(………..………..………..………..)
C.6.2.6 Domain Name
(………..………..………..………..)
ABB is a registered trademark of ABB Asea Brown Boveri Ltd. Manufactured by/for a Hitachi Power Grids company. Form 1KHW001289C-EN
Copyright 2002-2021 Hitachi Power Grids. All rights reserved. Rev. 2010-01-04
G3LL Commissioning Report EN C2/C2 HE

C.6.2.7 Domain Nameserver (DNS)

(………..………..………..………..)
(………..………..………..………..)
(………..………..………..………..)
C.6.2.8 FTP Server ON/OFF FTP Server setting DISABLED [ ]
C.6.2.9 System Logging Options Logging for all coming OFF [ ]
bootups
C.6.2.12 Set Time and Date Time and date correct? Ok [ ]
C.10 Change root password Root password changed? Ok [ ]
C.11 Determine Ethernet MAC MAC address (………..………..………..………..)

address
C.12 Test HMI570 LAN functionality HMI570 LAN running? Ok [ ]
Company: _________________________________
Department: _________________________________
Date: _________________________________
Signed: _________________________________
Visa: _________________________________
ABB is a registered trademark of ABB Asea Brown Boveri Ltd. Manufactured by/for a Hitachi Power Grids company. Form 1KHW001289C-EN
Copyright 2002-2021 Hitachi Power Grids. All rights reserved. Rev. 2010-01-04
Copy Instructions: < NSD570 Compact Flash Card G3LL > - A 07-10-16
PSND 04-04-06 sig. Braun 07-10-16 sig. Strittmatter - EN 1/5
- - - -
Copy Instructions: < NSD570 Compact Flash Card G3LL >
Contents:
2 Installation of Software “All Image” Application on Microsoft® Windows 2
2.1 System Requirements 2
2.2 License Information 2
2.3 Installation 2
2.4 Online Manual 2
3 Utilization of the All Image Software 2
3.1 Connecting the device 2
3.2 Starting the application 3
3.3 Copy the image to the CompactFlash Card 3
List of equipment:
PC with Windows 7 / XP / Vista
Software “All Image” included on the “NSD570 Software &
Documentation CD” (1KHW000925R0100)
Standard CompactFlash card reader
A EN 2/5 1KHW001291-EN
This document describes how to update the CompactFlash (CF) card of the NSD570 LAN interface
G3LL using a standard CompactFlash card reader.
The program “All Image” (AI-setup.exe) found on the CD-ROM is required to copy the image file of
the HMI570 “LAN” version to the CompactFlash card reader.
2 Installation of Software “All Image” Application on Microsoft®

Windows
2.1 System Requirements

IBM PC or 100% compatible computer:
• Windows 7, XP or Vista
• 2 MB available hard disk space (plus additional for CF image files)
• Standard CompactFlash card reader
2.2 License Information

The trial software is valid for 14 days. To get a fully functional product after expiration, please
purchase a license as explained in the help menu.
2.3 Installation
1. Run AI-Setup.exe found on the CD
2. Click “Next” and accept the license agreement
3. Choose the destination location for the file and click “Next”
4. Select the start menu folder and additional tasks
5. Then click “Install”
2.4 Online Manual

The online reference manual is in the menu “Help” → “Documentation”.
3 Utilization of the All Image Software
3.1 Connecting the device

If you don’t have an integrated CompactFlash card reader on your PC, connect an USB
CompactFlash card reader to the PC and insert the CompactFlash card.
No additional drivers are needed.
A EN 3/5 1KHW001291-EN
3.2 Starting the application

Start “All-Image” found in the Windows Start menu.
3.3 Copy the image to the CompactFlash Card

1. Select “Write Disk”.
2. Choose your CompactFlash card on the Disk Drive combo box.
 Note: If your CompactFlash drive is not displayed in the list, check your CompactFlash card.
Make sure the CompactFlash card is inserted into your CompactFlash reader before you
start the application.
A EN 4/5 1KHW001291-EN
If you are not sure which drive is the correct one, click the information icon next to the combo box.
Typically, the following information is displayed for a 256 MB CompactFlash card:
3. Pick an image file by clicking “Browse…” and click “Open”.
4. Click the button “Write Disk”.
5. An information window about drive type discrepancy appears. Click “Yes” to continue.
A EN 5/5 1KHW001291-EN
6. Click “Yes” to overwrite the content on the CompactFlash card.
7. Now the image is being written onto the CompactFlash card.
8. After completion close the application and remove the CompactFlash card from the card reader.
Commissioning Instructions: < NSD570 Management LAN - C 2021-08-11
Interface G3LM >
PGGA-PT1 2009-07-16 M. Burri 2021-08-11 H.-J. Maag - EN 1/15
- - - - 1KHW002232CE Commissioning
of LAN Interface G3LM.doc
Commissioning Instructions: < NSD570 Management LAN Interface G3LM >
This document describes commissioning of the NSD570 Management LAN Interface G3LM, an optional module
for the NSD570 Teleprotection System.

PC with HMI570 software installed Commissioning PC
Serial RS-232 cable with 9-pin connectors
Notes:

“Ethernet”, firmware “Management” and hardware of NSD570
C EN 2/15 1KHW002232-EN
Contents:
C Commissioning Instructions for the NSD570 Management LAN Interface

G3LM ............................................................................................................ 3
C.1 General ......................................................................................................... 3
C.4 Serially connect to the Management LAN Interface G3LM .......................... 4
C.5 Enter Configuration....................................................................................... 4
C.6 Download the configuration .......................................................................... 5
C.7 Reset the device ........................................................................................... 5
C.8 Re-connect to the Management LAN Interface G3LM ................................. 5
C.9 Set time and date ......................................................................................... 6
C.10 Set up the Management LAN Interface User Accounts ............................... 6
C.11 Set up the SNMPv3 User Accounts ............................................................. 6
C.12 Generate a new SSL certificate .................................................................... 6
C.13 Upload and store the generated certificate .................................................. 6
C.14 Determine MAC address .............................................................................. 6
C.15 Set up and test the Ethernet/IP connection .................................................. 6
C.16 Test HMI570 Management LAN functionality ............................................... 9
C.17 Test SNTP client functionality....................................................................... 9
C.18 Delete the user activity log file ...................................................................... 9
C.19 Exit HMI570 .................................................................................................. 9
Sheet G3LM Commissioning Report ...........................................................C1 – C5
Designation Meaning

[X] Test passed or jumper is set
G3LM Module type of the Management LAN Interface
RTC Real Time Clock
Rx Receiver
Tx Transmitter
C EN 3/15 1KHW002232-EN
C Commissioning Instructions for the NSD570 Management LAN

Interface G3LM
C.1 General
This document is part of the Operating Instructions NSD570 (1KHW000890) and describes the
programming, testing and commissioning of the NSD570 Management LAN Interface type G3LM.
Please note that NSD570 devices in the rack (Analog, Digital, Ethernet) should be programmed
and tested or commissioned properly before the LAN Interface is put into service (the checks in
Section C.1.2 may then be skipped because they are already done; please refer to documents
1KHW000898 “Programming and Testing Instructions NSD570” and 1KHW000900
“Commissioning Instructions NSD570” in the annex of the Operating Instructions).
After the NSD570 devices are tested or commissioned, switch off the power supply of the module
rack, insert the LAN Interface in slot N84, connect the optional connecting cables and follow the
steps below for setting up the LAN connection.

terminals and RJ45 socket) or at the terminals and sockets of the optional connecting cables.




Check the status of the plugged power supply modules which is indicated by the LEDs on the front
panel (green = Ok, red = fail, dark = not assembled).
C EN 4/15 1KHW002232-EN
C.3.1 Interface selection

In order to select one of the interfaces, electrical Ethernet X102 (RJ45) or optical SFP X103, the
selection switch between the two interfaces has to be moved towards the required interface.
SFP RJ45
C.3.2 Install the HMI570 Software

Before you can access the Management LAN Interface G3LM, it is necessary to install the latest
HMI570 software (version 1.30 or higher) on your PC/notebook. This has to be done only the first
time. If you already have the latest release installed, you may proceed to the next point.
C.4 Serially connect to the Management LAN Interface G3LM

To commission an NSD570 Management LAN Interface for the first time, there is a serial RS-232
connection to the NSD570 equipment necessary. Connect a serial cable to the commissioning PC
and to the NSD570 front panel (labelled “COM 1”). In order to be able to communicate with the
Management LAN Interface G3LM, make sure that there is no Ethernet cable plugged into it,
neither electrical nor optical SFP 1.
Start the HMI570 software on the commissioning PC. If you have already configured an
administrative account, then please log in with that one. If not, log in with the following default
account:
User name: Administrator
Password: welcome
Choose “Connect via: local” and leave the IP Address field blank. Then press “Log In”.
For security reasons, the Administrator password must be changed immediately

after the installation of the HMI570. There is a warning message displayed at
the top of the HMI570 window until the default password has been changed.
C.5 Enter Configuration
C.5.1 Configure HMI570 serial port settings

Go to the menu “HMI570 Settings | Device Communication”. Configure the serial port parameters
according to your needs. Default is COM1, 57600, None, None. Then press “update”. You may
export the HMI570 settings for later reuse, but this is not required.
1
There is an automatic internal switch between Ethernet and Serial port. If an Ethernet link is present, the
serial port is switched off, i.e. switched to master mode, so that alarm polling can work.
C EN 5/15 1KHW002232-EN
C.5.2 Create the Management LAN Interface Configuration

Go to the menu “Management Interface Configuration | Load From Disk” and load the file
“Default_Management.xml” by pressing the “load” button in right of the displayed file name. The
menu “Device Identification” will show up.
If you already have a valid configuration file, e.g. from the engineering department, then load that
one instead of the default one. Then fill in the requested values in the commissioning report
Sections C.5.2.1 to C.5.2.5 and proceed with C.6.
C.5.2.1 Device Identification

Press “edit”. Enter a unique station name, the HE number and the device address. Write the
entered values down in the commissioning report. Then, press “update”. The station name must be
unique since it will show up in new SSL certificates and in the SNMP management data.
C.5.2.2 Management Interface

Go to the menu “Management Interface” and press “edit”. Fill in all values as desired. Also write
down all values in the commissioning report. When finished, press “update”.
C.5.2.3 SNMP Event Polling

SNMP Event Polling is off by default. With NSD570 Rel. 3.7 and higher, you can individually enable
“Alarm Polling”, “Command and Manipulation Event Polling” and “Trip Counter Polling”. However,
“Alarm Polling” must be set to “on” if the two other polling types shall be enabled. Change the
“Length of a Polling Cycle” as desired and add the device information in the list of polled devices.
When finished, press “update”. Also write down all the configuration values in the commissioning
report.
C.5.2.4 SNMP Parameters

SNMP is off by default. If you have to enable it, then switch to the menu “SNMP Parameters” and
change the configuration as desired. When finished, press “update”. Also write down all the
configuration values in the commissioning report.
C.5.2.5 SNTP Time Parameters

SNTP is off by default. If you have to enable it, then switch to the menu “SNTP Time Parameters”
and change the configuration as desired. When finished, press “update”. Also write down all the
configuration values in the commissioning report.
C.5.3 Save the Management LAN Interface configuration to file

Go to the menu “Management Interface Configuration | Save To Disk”. Click onto the displayed link
and choose a storage position in the file system. This step is important!
C.6 Download the configuration

Go to menu “Connect Device” and press “G3LM” in the bottom right corner. The message “device
connected” must show up.
After connecting, go to “Management Interface Configuration | Load From Disk” to load the
previously stored configuration (press “Browse”, then “load”). Then, go to “Management Interface
Configuration | Download To Device” to download the configuration to the Management LAN
Interface G3LM.
C.7 Reset the device

To activate the new configuration, you need to reset the device. This is done in the menu
“Maintenance | Reset Device”.
C.8 Re-connect to the Management LAN Interface G3LM

Go to HMI570 menu “Connect Device”. Press the button “G3LM” or enter the default address 250.
Then press the connect button.
C EN 6/15 1KHW002232-EN
C.9 Set time and date

If everything worked fine, go to the menu “Maintenance | Set Time And Date”. Set the time and
date on the G3LM. “Send task successful” must show up.
C.10 Set up the Management LAN Interface User Accounts

Go to the menu “Management Interface Configuration | User Administration”. There you can delete
the default users and add your own ones. For security reasons it is highly recommended to remove
the default user accounts.
C.11 Set up the SNMPv3 User Accounts

NSD570 Release 3.7 or higher is also supporting SNMPv3 (in addition to SNMPv1 and SNMPv2c).
If SNMPv3 shall be used, the SNMP users have to be added in the menu “Management Interface
Configuration | SNMPv3 User Management”. There you can add and enable SNMP users, select
their authentication and privacy protocol and define the related passwords.
C.12 Generate a new SSL certificate

Now go to the menu “Management Interface Configuration | Certificate Management”. There, enter
a number for “Valid Days”, e.g. 365, then press the button “generate on G3LM” to generate a new,
non-default public key certificate and private key on the target device.
C.13 Upload and store the generated certificate

After ca. 10 seconds, press the “upload from G3LM” button. Then “store” to add the new certificate
to the local trusted certificate store. Then export the new certificate to file for distribution to other
HMI570 PCs.
C.14 Determine MAC address

Note: This step is not mandatory to commission the NSD570 LAN interface G3LM.
However, the Ethernet MAC address is useful for troubleshooting and shall
therefore be documented in the test report.
Go to the menu “Status Upload” to view the Ethernet MAC address.
C.15 Set up and test the Ethernet/IP connection

Depending on the port selection (RJ45 or SFP) and your network equipment, either use an
electrical or optical cable to connect G3LM to a switch or commissioning PC.
To set up and test the Ethernet connection, one of the test cases C.15.2 or C.15.3 shall be
performed.
If everything is connected fine and the Ethernet link layer was able to establish physical
connection, the link LED on the NSD570 front panel will be on.
C.15.1 Optical output power / optical received power (only if optical SFP is used)
of either 850 nm or 1310 nm and a single or a multi mode adapter cable has to be used for
connecting the power meter to G3LM.
C EN 7/15 1KHW002232-EN

C.15.2 Connection over an Ethernet switch or hub

The RJ45 connector (X102) of the Management LAN Interface G3LM must be connected with an
Ethernet switch or hub. The connecting cable must be a straight Ethernet cable (not a cross
connect cable). Now it is possible to connect the G3LM from every PC that is connected to the
Ethernet LAN.
Ethernet Switch / Hub
(straight)
Ethernet
cable Ethernet
Commissioning PC
A Connect G3LM
 Note: The configured Management LAN Interface IP address must not be used by
another device in the Ethernet LAN.
C.15.3 Direct connection over an Ethernet cross connect cable

The RJ45 connector (X102) of the LAN Interface G3LM must be connected with the Ethernet port
of the commissioning PC. The connecting cable must be an Ethernet cross connect cable.
Commissioning PC
Ethernet
cross connect cable
A Connect G3LM
C EN 8/15 1KHW002232-EN
C.15.4 Change the network settings of the commissioning PC

The following steps describe how the subnet mask can be configured in Windows® 10.
Start → Settings → Network & Internet → Ethernet → Change adapter options
Select the Ethernet device and click on “Change settings of this connection”. The window “Ethernet
Properties” (the left one below) should appear. Mark “Internet Protocol Version 4 (TCP/IPv4)“ and
click on “Properties”. The window “Internet Protocol Version 4 (TCP/IPv4) Properties” appears (the
right one below) and there the network settings can be configured.
C.15.5 Ethernet connection test (ping)

The „ping“ command in the DOS box (Command Prompt app) can be used to test the IP
connection to the LAN Interface.
C:\Users\userxy>ping 192.168.0.4
Pinging 192.168.0.4 with 32 bytes of data:

Ping statistics for 192.168.0.4:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C EN 9/15 1KHW002232-EN
C.16 Test HMI570 Management LAN functionality

At the end of the commissioning of the NSD570 Management LAN Interface, test the access and
the basic functionality of the HMI570.
1. Power up the NSD570 with Management LAN Interface G3LM and await the startup delay
(approx. 2 minutes). When Ok/Fail LED turns to green, G3LM has started successfully.
2. Start HMI570 PC that is connected to LAN and has therefore access to the NSD570
Management LAN Interface G3LM
3. “Log In” with a configured user name and password. Enter the G3LM IP address and mark
“Connect Via: LAN”. Your login data will be checked on the Management LAN Interface G3LM
(not in HMI570).
4. In menu “Connect Device” enter the configured device address (not the default one!) and click
“Connect”
5. “Device connected” must appear
6. Click “Configuration”, “Upload From Device”
7. “Configuration upload successful” must appear
C.17 Test SNTP client functionality

At the end of the commissioning of the NSD570 Management LAN Interface and HMI570
Management LAN functionality, test the SNTP client functionality.
1. In the menu “Management Interface Configuration”, click “SNTP Time Parameters”

2. Activate SNTP client by setting “SNTP Enable” to “on”
3. Configure “SNTP Primary Server” address with the IP address of the primary SNTP server on
the LAN
4. Keep the default configuration value “10 s” for “SNTP Interval”
5. Wait for 15 seconds
6. Go to menu “Status/Alarm” and click “Upload Status”
7. “Status upload successful” must appear
8. “Synchronized to primary SNTP server” must appear
C.18 Delete the user activity log file

At the end of all your actions, delete the user activity log file (menu “Management | User Activity
Logging | Clear Logfile”).
C.19 Exit HMI570

Click “Exit HMI570”, press button „Exit“ and close the browser.
G3LM Commissioning Report EN C1/C5 HE

C.1 General

the equipment
Unit 1 Unit 2
Equipment connected to Via circuit breaker [ ]
adequate voltage source B9AS or B9AV
C.2 Check power supply Unit 1 Unit 2
LED indication on the front panel Unit 1 and Unit 2 Green LED [ ] [ ]

C.3.1 Interface selection G3LM interface RJ45 [ ]D
selection switch SFP [ ]
C.3.2 Install the HMI570 Software OK [ ]
C.4 Serially connect to the OK [ ]

C.5 Enter Configuration

C.5.1 Configure HMI570 serial port
settings
Serial baud rate 9600 or bps [ ]
19200 or bps [ ]
57600 bps [ ]D
RS-232 handshake in None [ ]D
RTS/CTS In [ ]
RS-232 handshake out None [ ]D
RTS/CTS Out [ ]
C.5.2 Create the Management LAN
Interface Configuration
C.5.2.1 Device Identification
Station Name […………………………………………]
HE Number “HE XXXXX…” [HE ….…………………………………]
Device Address 1 … 240 […………………………………………]
Copyright 2002-2021 Hitachi Power Grids. All rights reserved. Form 1KHW002232C-EN

C.5.2.2 Management Interface
IP Address X.X.X.X […………………………………………]
Subnet Mask X.X.X.X […………………………………………]
Default Gateway X.X.X.X […………………………………………]

VLAN Tagging disabled [ ]D
enabled [ ]
VLAN ID (if enabled) 0 … 4094 […………]
Priority (if enabled) 0…7 […………]
Auto Negotiation manual [ ]
auto [ ]D
Data Rate (if manual) 100 Mbps [ ]D
10 Mbps [ ]
Duplex Mode (if manual) Full Duplex [ ]D
Half Duplex [ ]
Automatic Laser Shutdown (ALS) off [ ]D
on [ ]
External Real-Time Sync (IRIG-B) off [ ]D
on [ ]
C.5.2.3 SNMP Event Polling
Alarm Polling off [ ]D
on [ ]
Command and Manipulation (with NSD570 Rel. 3.7 and off [ ]D
higher only)
Event Polling
on [ ]
Trip Counter Polling (with NSD570 Rel. 3.7 and off [ ]D
higher only)
on [ ]
Length of a Polling Cycle 5 sec 10 sec [ ]D [ ]
30 sec 1 min [ ] [ ]
2 min 10 min [ ] [ ]
30 min 1h [ ] [ ]
2h 10h 24h [ ] [ ] [ ]
Device List Up to 239 devices
Device Address 1 … 239 […………]
Remote Over EOC [ ]D
[ ]

C.5.2.4 SNMP Parameters

SNMP Enable off [ ]D
on [ ]
SNMP Version (SNMPv3 with NSD570 Rel. 1 and 2 (auto) [ ]D
3.7 and higher only)
1 [ ]
2 [ ]
3 [ ]
SNMP Community String […………………………………………]
SNMP System Name […………………………………………]
SNMP System Contact […………………………………………]
SNMP Trap Subscribers Up to 4 subscribers

NMS IP Address X.X.X.X […………………………………………]
Port 0 … 65535 […………]
Version 1/2/3 [ ]D [ ] [ ]
SNMPv3 User Name (from NSD570 Rel. 3.7 on) […………………………………………]

Port 0 … 65535 […………]
Version 1/2/3 [ ]D [ ] [ ]

Port 0 … 65535 […………]
Version 1/2/3 [ ]D [ ] [ ]

Port 0 … 65535 […………]
Version 1/2/3 [ ]D [ ] [ ]
C.5.2.5 SNTP Time Parameters

SNTP Enable off [ ]D
on [ ]
SNTP Primary Server X.X.X.X […………………………………………]
SNTP Secondary Server X.X.X.X […………………………………………]
SNTP Interval 1 … 1024 sec […………]
Time Zone Offset UTC time -12:00 … hours […………]
(from NSD570 Rel. 3.7 on) +14:00
Daylight Saving Time Europe: summer time off [ ]D
(from NSD570 Rel. 3.7 on)
on [ ]

C.5.3 Save the Management LAN OK [ ]

Interface configuration to file
C.6 Download the configuration OK [ ]
C.7 Reset the device OK [ ]
C.8 Re-connect to the Management OK [ ]

LAN Interface G3LM
C.9 Set time and date OK [ ]
C.10 Set up the Management LAN OK [ ]

Interface User Accounts
C.11 Set up the SNMPv3 User (with NSD570 Rel. 3.7 and OK [ ]
higher only)
Accounts
C.12 Generate a new SSL certificate OK [ ]
C.13 Upload and store the generated OK [ ]

certificate
C.14 Determine MAC address [ 00 : D0 : 93 :_____:_____:_____ ]
C.15 Set up and test the Ethernet/IP

connection
C.15.1 Optical output power / optical (if optical SFP is used)
received power
Output power TPE 2
100 Mbps, 850 nm, MM, 0.5 km G3LM; X103/Tx [ -23 … -11 ] dBm (…………)
(50 µm)
100 Mbps, 1310 nm, MM, 0.5 km G3LM; X103/Tx [ -23.5 … -14 ] dBm (…………)
(50 µm)
100 Mbps, 1310 nm, SM, 30 km G3LM; X103/Tx [ -15 … -8 ] dBm (…………)
Received power TPE 2
100 Mbps, 850 nm, MM, 0.5 km Receiving fiber [ -32 … -3 ] dBm (…………)
100 Mbps, 1310 nm, MM, 0.5 km Receiving fiber [ -31 … 8 ] dBm (…………)
100 Mbps, 1310 nm, SM, 30 km Receiving fiber [ -34 … 0 ] dBm (…………)
C.15.2 Connection over an Ethernet OK [ ]

switch or hub
C.15.3 Direct connection over an OK [ ]

C.15.4 Change the network settings of OK [ ]

the commissioning PC
C.15.5 Ethernet connection test (ping) OK [ ]
C.16 Test HMI570 Management LAN HMI570 OK [ ]

functionality
C.17 Test SNTP client functionality OK [ ]
C.18 Delete the user activity log file OK [ ]
Company: _________________________________
Department: _________________________________
Date: _________________________________
Signed: _________________________________
Visa: _________________________________
Engineering of GOOSE LAN Interface G3LS - D 2018-05-17
PGGA-PT1 2013-03-26 A. Freihofer 2018-05-17 H.-J. Maag - EN 1/25
- - - - 1KHW002649DE Engineering of
GOOSE LAN Interface G3LS.doc
Engineering guideline: < GOOSE LAN Interface G3LS >
This document describes the engineering approaches and the related functionality of HMI570 for the
engineering and configuration of G3LS, an optional module for the NSD570 Teleprotection System.
D EN 2/25 1KHW002649-EN
Contents:
1. Overview ....................................................................................................... 4
2. G3LS as a Proxy or a GGIO Gateway for NSD570 ..................................... 4
2.1 G3LS Data Model .....................................................................................................5
2.1.1 Proxy Gateway Data Model ......................................................................................5
2.1.2 GGIO Gateway Data Model ......................................................................................6
2.1.3 G3LS published DataSet ..........................................................................................7
2.1.4 G3LS subscribed DataSet ........................................................................................8
2.2 Quality mapping ........................................................................................................8
2.2.1 Unmapped quality .....................................................................................................8
2.2.2 Mapped quality .........................................................................................................9
2.2.3 Support of IEC 61850 Edition 2003 and 2007...........................................................9
3. HMI570 with IEC 61850 and G3LS support ............................................... 10
3.1 GOOSE Interface Configuration .............................................................................10
3.2 IEC 61850 Configuration.........................................................................................10
3.2.1 ICD Generator ........................................................................................................10
3.2.2 IEC 61850 substation configuration ........................................................................11
3.2.3 IEC 61850 IED configuration ..................................................................................11
3.2.4 Verify Configuration Consistency ............................................................................13
3.2.5 CID Editor ...............................................................................................................13
4. IEC 61850 Engineering Concepts .............................................................. 14
4.1 Advanced Engineering Approach ...........................................................................14
4.1.1 Overview .................................................................................................................14
4.1.2 Configuration process .............................................................................................14
4.1.3 Summary related to HMI570 ...................................................................................17
4.2 Simple Engineering Approach ................................................................................18
4.2.1 Overview .................................................................................................................18
4.3 Manual Engineering Approach ................................................................................21
4.3.1 Overview .................................................................................................................21
4.4 Engineering Approach Comparison ........................................................................23
5. Status information provided by G3LS ......................................................... 24
D EN 3/25 1KHW002649-EN
Designation Meaning
CCF Communication Configuration File (ABB proprietary)

DA Data Attribute
DO Data Object
FCDA Functionally Constrained Data Attribute
GOOSE Generic Object Oriented Substation Events
GPS Global Positioning System
HMI570 NSD570 User Interface Program
IEC International Engineering Consortium
IED Intelligent Electronic Device
IP Internet Protocol
LN Logical Node
PC Personal Computer
RTC Real Time Clock
SA Substation Automation
SCL Substation Configuration Language
SET System Engineering Tool
TPE Teleprotection Equipment
VLAN Virtual Local Area Network
VLAN ID Virtual Local Area Network Identifier
XML Extensible Mark-up Language
D EN 4/25 1KHW002649-EN
1. Overview
This document is part of the Operating Instructions NSD570 (1KHW000890). It describes the
engineering of the GOOSE LAN interface G3LS.
From HMI570 version 1.40 onwards, the installer provides IEC 61850 support as an option. IEC
61850 support is needed for the engineering of the GOOSE LAN interface G3LS.
If HMI570 is installed without the IEC 61850 option, only a minimal set of G3LS related features is
provided. This minimal set of features enables the user to handle pre-engineered IEC 61850
configuration files. It is possible to do a download to the device, upload a configuration from a
device and store it on a PC. It is not possible to edit or generate any kind of SCL files in case
HMI570 was installed without the IEC 61850 option.
The present document describes the capabilities of G3LS together with the enhanced HMI570 PC
enabled for IEC 61850 support. G3LS requires two configuration files. One file is used for the
GOOSE interface configuration. The second configuration file is needed by the IEC 61850 stack
which is part of the G3LS firmware.
2. G3LS as a Proxy or a GGIO Gateway for NSD570

IEC 61850 is a standard for the definition of electrical substation automation (SA) systems. The
abstract data models defined in IEC 61850-8-1 can be mapped to a number of network protocols.
G3LS supports GOOSE only. A total of eight protection commands per direction as well as some
link and device status information are handled by G3LS. Figure 1 shows the common setup with
G3LS as a gateway.
GOOSE Substation A Substation B GOOSE

Protection NSD570 A NSD570 B Protection
IED A IED B
PhyHealth
DataSet
DataSet
Inputs
EEHealth Inputs
Commands [1-8]
Commands [1-8]
G3LS A Line Line G3LS B

IED interface interface IED
PhyHealth
DataSet
DataSet
Inputs
Inputs
EEHealth
Commands [1-8]
Commands [1-8]
Figure 1 Example setup with G3LS

Depending on the configuration G3LS either acts as a Proxy Gateway or as a GGIO gateway
according to IEC 61850-90-1. The following sections describe different approaches to setup a
teleprotection link including G3LS.
The whole system engineering is about exchanging and converting SCL configuration files. The
following configuration files types are necessary in order to support the NSD570 engineering
processes.

For IEC 61850 compatible IED a capability description is provided. For G3LS either a
customized file can be generated by HMI570 or a generic file can be downloaded from
HMI570. Which file is used depends on the applied engineering approach.
D EN 5/25 1KHW002649-EN

Specification of the whole substation with all IED and communication configuration.
An IID file defines the configuration of one IED for a project. In G3LS engineering
processes IID files are used to keep the SET up to date at any phase of the process.
Specification of one completely engineered IED with relevant information of the IED
connected to it and the corresponding communication in between.
ICZ This is the native configuration format used by G3LS devices. Basically the ICZ file is
very similar compared to a CID file. HMI570 PC with IEC 61850 add-on supports to
convert CID files to ICZ files and vice versa without loss of information. HMI570
without IEC 61850 support cannot handle CID files. However the download of ICZ files
is supported. HMI570 PC Version is installed without IEC 61850 engineering support
by default. Also HMI570 LAN which runs on G3LL management interface supports
only the download of ICZ files.
ICZ is the recommended format for G3LS configuration backup because HMI570 does
not need to convert the configuration before it can be downloaded to G3LS. A CID file
is converted to an ICZ file during the download procedure. This happens transparently.
Table 1: IEC 61850 specific file types used for G3LS configuration
ICD and IID files can be imported into IEC 61850 system engineering tools such as ABB’s
Integrated Engineering Tool IET600. SCD files are exported by the system engineering tool.
HMI570 supports the import of SCD, CID and ICZ files. IID, CID and ICZ files can be generated by
HMI570.
2.1 G3LS Data Model

Depending on the configuration G3LS represents either a GGIO Gateway or a Proxy Gateway
according to IEC 61850-90-1.
2.1.1 Proxy Gateway Data Model

If G3LS is configured as a Proxy Gateway it works with a Data Model as showed in Figure 2.
NSD570 SA1Y1 NSD570 SB1Y1
LD0 LD0
Prot. IED LNs: LNs: Prot. IED

SA1F1 - LPHD1 - LPHD1 SB1F1
- ITPC1 line - ITPC1
LNs:
LNs:
- XRBRF1 SB1F1LD0 SA1F1LD0
- ZGGIO1
- YPSCH1
LNs: LNs:
- ZGGIO1 - XRBRF1
- YPSCH1
Figure 2 Example: IEC 61850 Proxy GW Data Model of G3LS
The following properties of a proxy gateway should be noted:

• A proxy representing a protection IED in the remote substation is modeled as a Logical
Device of G3LS. The Logical Device contains a copy of the relevant parts of the Data
Model of the represented Protection IED.
For example: The proxy of SA1F1 in Figure 2 is SB1Y1/SA1F1LD0
• The Data Model of the proxy is derived from the Data Model of the represented Protection
IED. Generating a proxy Data Model is completely automated by HMI570.
D EN 6/25 1KHW002649-EN
• The proxy gateway approach provides a maximum of semantic validation across

substation boarders.
An example how the Proxy Gateway SB1Y1 of Figure 2 could look like in SCL (many lines and
details have been deleted):
<LDevice inst="LD0">
<LN0 lnClass="LLN0" inst="" lnType="ABBNSD570_LLN0">
<DataSet name="Teleprotection">
<FCDA ldInst="LD0" lnClass="LPHD" lnInst="1" doName="PhyHealth" fc="ST" />
<FCDA ldInst="LD0" lnClass="ITPC" lnInst="1" doName="EEHealth" fc="ST" />
<FCDA ldInst="SA1F1LD0" prefix="X" lnClass="RBRF" lnInst="1" doName="OpEx" daName="general" fc="ST" />
<FCDA ldInst="SA1F1LD0" prefix="X" lnClass="RBRF" lnInst="1" doName="OpEx" daName="q" fc="ST" />
<FCDA ldInst="SA1F1LD0" prefix="Y" lnClass="PSCH" lnInst="1" doName="Op" daName="general" fc="ST" />
<FCDA ldInst="SA1F1LD0" prefix="Y" lnClass="PSCH" lnInst="1" doName="Op" daName="q" fc="ST" />
</DataSet>
<Inputs>
<ExtRef iedName="SB1F1" ldInst="LD0" prefix="Z" lnClass="GGIO" lnInst="1" doName="Ind1" daName="stVal" intAddr="A"/>
<ExtRef iedName="SB1F1" ldInst="LD0" prefix="Z" lnClass="GGIO" lnInst="1" doName="Ind1" daName="q"/>
...
</Inputs>
...
</LN0>
<LN lnClass="LPHD" inst="1" lnType="ABBNSD570_LPHD" />
<DOI name="Proxy"> <DAI name="stVal"> <Val>false</Val> </DAI> </DOI>
</LN>
<LN lnClass="ITPC" inst="1" lnType="ABBNSD570_ITPC">
<DOI name="NumTxCmd"> <DAI name="setVal"> <Val>2</Val> </DAI> </DOI>
<DOI name="NumRxCmd"> <DAI name="setVal"> <Val>1</Val> </DAI> </DOI>
<DOI name="TpcTxMod1"> <DAI name="setVal"> <Val>Blocking</Val> </DAI> </DOI>
...
</LN>
</LDevice>
<LDevice inst="SA1F1LD0">
<LN0 lnClass="LLN0" inst="" lnType="ABBIED600_LLN0_#LIB2">
...
</LN0>
<LN lnClass="LPHD" inst="1" lnType="ABBIED600_REV1_LPHD_#LIB2">
<DOI name="Proxy"> <DAI name="stVal"> <Val>true</Val> </DAI> </DOI>
</LN>
<LN prefix="X" lnClass="RBRF" inst="1" lnType="ABBIED600_REV1_SP16RBRF_#LIB1">
...
</LN>
<LN prefix="Y" lnClass="PSCH" inst="1" lnType="ABBIED600_ZSPSCH_#LIB1">
...
</LN>
</LDevice>
2.1.2 GGIO Gateway Data Model

IEC 61850-90-1 describes a GGIO as follows:
“A number of arbitrary I/O points are exchanged between the stations. In IEC 61850, this would be
implemented by using GGIOs. A separate cross-reference list is necessary to interpret the actual
meaning of the anonymous data points of the GGIOs. This approach provides no semantics and
delivers very little value within the scope of IEC 61850 conformant engineering.”
Especially for compatibility reasons with binary contact based environments, G3LS supports the
GGIO Gateway approach. Since both substations can be engineered independent from each other
it is also possible to create a IEC 61850 configuration for only one end of the teleprotection link.
The NSD570 installed in the remote substation does not necessarily have a G3LS interface
plugged. It can be equipped with G3LR interfaces instead. It is also possible to create mixed setups
where G3LS and G3LR interfaces are installed in one NSD570 TPE.
NSD570 SA1Y1 NSD570 SB1Y1
Prot. IED
LD0 LD0 Prot. IED
SA1F1
SB1F1
LNs: line LNs:
LNs:
- LPHD1 - LPHD1 LNs:
- XRBRF1
- ITPC1 - ITPC1 - ZGGIO1
- YPSCH1
- GGIO1 - RBRF1
- PSCH1
Figure 3 Example: IEC 61850 GGIO GW Data Model of G3LS

G3LS implements an improved variant of a GGIO Gateway. In addition to LN type GGIO G3LS
supports LN type PSCH and RBRF as well. In comparison to the proxy gateway Data Model the
GGIO gateway Data Model of G3LS does not provide full semantic validation. The commands of
the Protection IED are represented in the dataset of G3LS by either one of the following LN, DO,
DA combination in the remote substation.
D EN 7/25 1KHW002649-EN
• GGIO.Ind.stVal, GGIO.Ind.q
• PSCH.TxBlk.general, PSCH.TxBlk.q (blocking)
• PSCH.TxPrm.general, PSCH.TxPrm.q (permissive)
• PSCH.TxTr.general, PSCH.TxTr.q (direct)
• RBRF.OpEx.general, RBRF.OpEx.q
The LN, DO, DA combinations above are based on definitions of IEC 61850 Edition 2007A (Ed.2).
To support substations engineered according to IEC 61850 Edition 2003 (Ed.1), on Input side
additionally PSCH.ProTx is supported to be subscribed.
In most cases the Data Model of the G3LS in the remote substation will not exactly match with the
Data Model of the corresponding Protection IED. But at least it is possible to assign a Data Type
which is accurate to different types of applications.An additional disadvantage compared to the
proxy gateway approach is that the semantic information is not automatically exchanged across
substation borders by engineering tools. A consistent command mapping between both substation
can be guaranteed only with manual verification.
An example how the GGIO Gateway SB1Y1 of Figure 3 could look like in SCL (some lines and
details have been deleted):
<LDevice inst="LD0">
<LN0 lnClass="LLN0" inst="" lnType="ABBNSD570_LLN0">
<FCDA ldInst="LD0" lnClass="RBRF" lnInst="1" doName="OpEx" daName="general" fc="ST" />
<FCDA ldInst="LD0" lnClass="RBRF" lnInst="1" doName="OpEx" daName="q" fc="ST" />
<FCDA ldInst="LD0" lnClass="PSCH" lnInst="1" doName="TxPrm" daName="general" fc="ST" />
<FCDA ldInst="LD0" lnClass="PSCH" lnInst="1" doName="TxPrm" daName="q" fc="ST" />
...
</DataSet>
<Inputs>
<ExtRef iedName="SB1F1" ldInst="LD0" prefix="Z" lnClass="GGIO" lnInst="1" doName="Ind1" daName="stVal" intAddr="A"/>
<ExtRef iedName="SB1F1" ldInst="LD0" prefix="Z" lnClass="GGIO" lnInst="1" doName="Ind1" daName="q"/>
...
</Inputs>
...
</LN0>
<LN lnClass="LPHD" inst="1" lnType="ABBNSD570_LPHD" />
<DOI name="Proxy"> <DAI name="stVal"> <Val>false</Val> </DAI> </DOI>
</LN>
<LN lnClass="ITPC" inst="1" lnType="ABBNSD570_ITPC">
<DOI name="NumTxCmd"> <DAI name="setVal"> <Val>2</Val> </DAI> </DOI>
<DOI name="NumRxCmd"> <DAI name="setVal"> <Val>1</Val> </DAI> </DOI>
<DOI name="TpcTxMod1"> <DAI name="setVal"> <Val>Blocking</Val> </DAI> </DOI>
...
</LN>
<LN lnClass="PSCH" inst="1" lnType="ABBNSD570_PSCH">
<DOI name="TxBlk">
<DAI name="q" sAddr="unmapped" />
</DOI>
</LN>
<LN lnClass="PSCH" inst="2" lnType="ABBNSD570_PSCH">
<DOI name="TxPrm">
<DAI name="q" sAddr="unmapped" />
</DOI>
</LN>
...
</LDevice>
2.1.3 G3LS published DataSet

The layout of a DataSet published by G3LS is directly derived from the command assignment on
the teleprotection link. The DataSet has a fixed structure according to the following rules:
• LPHD.PhyHealth is the first object of the DataSet published by G3LS
• ITPC.EEHealth is the second object of the DataSet published by G3LS
• Behind LPHD.PhyHealth and ITPC.EEHealth up to eight DataAttributes representing the
teleprotection commands can be appended.
Each teleprotection command received from the Line Interface is published as one status
DataAttribute and the corresponding quality DataAttribute. The first pair of command FCDA entries
represents teleprotection command A. The second represents command B and so on. The content
of the quality information depends on the configuration. Details about quality mapping are covered
in section 2.2.
The SET is not allowed to change the DataSet of G3LS. Therefore “modify” attribute of the DataSet
defined in the ICD file of NSD570 is set to “false”.
Below is an example of a maximum size DataSet of G3LS in SCL syntax.
D EN 8/25 1KHW002649-EN
<FCDA ldInst="LD0" lnClass="PSCH" lnInst="1" doName="TxBlk" daName="general" fc="ST" />
<FCDA ldInst="LD0" lnClass="PSCH" lnInst="1" doName="TxBlk" daName="q" fc="ST" />
<FCDA ldInst="LD0" lnClass="PSCH" lnInst="2" doName="TxPrm" daName="general" fc="ST" />
<FCDA ldInst="LD0" lnClass="PSCH" lnInst="2" doName="TxPrm" daName="q" fc="ST" />
<FCDA ldInst="LD0" lnClass="GGIO" lnInst="1" doName="Ind1" daName="stVal" fc="ST" />
<FCDA ldInst="LD0" lnClass="GGIO" lnInst="1" doName="Ind1" daName="q" fc="ST" />
<FCDA ldInst="LD0" lnClass="RBRF" lnInst="1" doName="OpEx" daName="general" fc="ST" />
<FCDA ldInst="LD0" lnClass="RBRF" lnInst="1" doName="OpEx" daName="q" fc="ST" />
<FCDA ldInst="LD0" lnClass="PSCH" lnInst="3" doName="TxBlk" daName="general" fc="ST" />
<FCDA ldInst="LD0" lnClass="PSCH" lnInst="3" doName="TxBlk" daName="q" fc="ST" />
</DataSet>
2.1.4 G3LS subscribed DataSet

As a GOOSE subscriber G3LS is flexible. It is able to subscribe to DataSets of up to eight
Protection IEDs. HMI570 provides a command mapping editor which enables the communication
engineer to define the mapping between transmitted teleprotection commands and DataAttributes
received from subscribed DataSets.
DataAttributes which can be mapped to teleprotection commands have to fulfill the following
constraints:
• LN type is either “GGIO”, “PSCH” or “RBRF”
• functional constraint is “ST”
• bType is “BOOLEAN”
• The corresponding quality DataAttribute is in the DataSet as well.
If DataAttributes which do not fulfill this rules are part of a subscribed DataSet HMI570 will not
allow the user to map these commands to teleprotection commands of the Line Interface. G3LS will
simply ignore them.
2.2 Quality mapping

G3LS does not handle DataAttributes received from Protection IED without quality information.
Only commands which are published together with the corresponding quality information can be
transmitted over the teleprotection line.
Internally G3LS considers the quality attribute as either “Good” or “Invalid”. How this simplified
binary quality information is processed and finally forwarded to the Line Interface depends on the
configuration of G3LS. NSD570 with G3LS supports two different command mapping approaches.
Either a status attribute is transmitted as one teleprotection command or it is transmitted together
with the corresponding binary quality information. The second approach allocates two
teleprotection commands per protection command. Details of both approaches are described in the
following two sections.
2.2.1 Unmapped quality

If a status value is mapped to a teleprotection command and the corresponding quality attribute is
not mapped to a teleprotection command, NSD570 works as showed in Figure 4.
Protection NSD570 A NSD570 B Protection
IED A IED B
G3LS Line Interface Line Interface G3LS
status
status
&
q
q q
Link Alarm
no alarm → good
invalid → no trip
alarm → invalid
Figure 4 One teleprotection command per IEC 61850 command

On the GOOSE subscriber side G3LS strips down the quality attribute received from the Protection
IED to one bit which is considered as either “Good” or “Invalid”. This bit is merged with the status
D EN 9/25 1KHW002649-EN
attribute before it is forwarded to the Line Interface. If the command is not received at all or
received with invalid quality the command is not forwarded to the Line Interface.
On the GOOSE publishing side, G3LS generates the quality information based on the status of the
Line Interface. If the Line Interface detects a “Link Alarm”, the quality of commands go to “Invalid”.
Please refer to section “High level and user alarms” in section “Troubleshooting” of the Operating
Instructions for a description of the conditions when a “Link Alarm” is raised by the Line Interface.
In case of Logical Node GGIO the system engineer has to verify that the
Caution provided mechanism of stripping down the quality attribute is permitted by the
application. One could think of applications where invalid quality shall not
lead to command suppression.
2.2.2 Mapped quality

If a quality attribute is assigned to a teleprotection command of the Line Interface G3LS behaves
as showed in Figure 5.
Protection NSD570 A NSD 570 B Protection

IED A IED B
G 3LS Line Interface Line Interface G3LS
status status
q q
q
& q
good → no trip q
invalid → trip Link Alarm
no alarm → good
alarm → invalid
Figure 5 Two teleprotection commands per IEC 61850 command

The quality attribute is transparently sent to remote substation. No link alarms are considered by
G3LS to generate the quality information. If the quality is invalid a trip is sent to the remote
substation and the input LED is switched on.
 Note: In case of a GOOSE communication failure the status and quality information
is not available on the local G3LS. In order to inform the remote substation
invalid quality is sent and the input LED is activated.
It is mandatory to map the quality attribute immediately following on the corresponding protection
command. For example if PSCH.TxBlk.general is mapped to command A the corresponding quality
attribute PSCH.TxBlk.q has to be transmitted on command B.
 Note: For mapped quality it is recommended to configure the line interface

parameter "Command Outputs During Link Failure" which is located in the
"Common Settings" section to "retain in state prior to link failure (frozen)".
Otherwise NSD570 will not behave as expected in case of a teleprotection link
interruption. The status value is forced to false even if it was true before the
line interruption.
2.2.3 Support of IEC 61850 Edition 2003 and 2007

G3LS supports both editions (2003 and 2007) of IEC 61850 called Edition 1 and Edition 2. Most
data type definitions used by G3LS ICD files are equal in both editions. However, the definition of
LN PSCH has changed and LN ITPC did not even exist in Edition 1. Therefore two ICD files are
offered by HMI570. One ICD file supports engineering in substations according to Edition 1 and the
other supports substations according to Edition 2. The G3LS data model remains the same in both
ICD files. The data model defined in the ICD file of G3LS according to Edition 1 borrows the
definition of LN ITPC and LN PSCH from Edition 2 standard.
D EN 10/25 1KHW002649-EN
3. HMI570 with IEC 61850 and G3LS support

A complete set of configuration files for a NSD570 rack including a Line Interface and a G3LS
interface consists of three types of configuration files:
• Line Interface configuration (not covered by this document)
• GOOSE Interface configuration (not covered by this document)
• IEC 61850 configuration
The following sections provide an introduction to the IEC 61850 configuration specific functionality
of HMI570. How to generate additional configuration files for NSD570 is covered by the main part
of the NSD570 operating instruction manual.
3.1 GOOSE Interface Configuration

The entries in menu “GOOSE Interface Configuration” provide access to some parameters of G3LS
which are not related to IEC 61850 configuration. These parameters are basically independent
from the IEC 61850 configuration. There is only one parameter which has to be consistent with the
IEC 61850 configuration. This is the parameter “Number of Protection Commands” found in the
“GOOSE LAN Interface” section.
Since these parameters are accessible with HMI570 without IEC 61850 support as well they are
covered in the main part of the NSD570 operating instructions. Please refer to section 5, section
“Number of Protection Commands“ to find detailed information about GOOSE interface
configuration parameters.
3.2 IEC 61850 Configuration

The menu entries mentioned in the following sections provide access to the configuration settings
related to the IEC 61850 network stack running on the G3LS device. This section covers the IEC
61850 specific menu entries and features found in HMI570 with IEC 61850 support. An introduction
to different engineering approaches will be provided in section 4.
3.2.1 ICD Generator

The capability description for NSD570 IED can be downloaded from HMI570. There are two
different types of ICD files provided.
• A generic ICD file is provided for import into a SET. This ICD file is generic with respect to
the teleprotection link configuration. This ICD file serves as a starting point for the
Advanced Engineering approach as described in section 4.1.
• A pair of customized ICD files can be generated. The user defines the teleprotection link
configuration in a bidirectional manner. HMI570 generates a ICD file for both G3LS
interfaces of the teleprotection link. These files serve as a starting point for the Simple
Engineering approach as described in section 4.2.
Before downloading the ICD file the edition of the IEC 61850 standard needs to be defined.
Currently Edition 1 and Edition 2 are supported. Please refer to section 2.2.3 for details.
For customized ICD files the following parameters can be configured per teleprotection command.
LN Class
Depending on the protection application the semantic of different LN classes can be assigned to a
teleprotection command.
Transmit quality
Quality mapping in general is described in section 2.2. If the “Transmit quality” flag of a command
is set to “Yes” the following teleprotection command is considered as the corresponding quality bit.
D EN 11/25 1KHW002649-EN
Application
The application type is stored into LN ITPC. LN ITPC allows to provide this information in a
standardized way. Make sure parameters entered into ICD Generator are consistent with the
parameters configured in the Line Interface.
3.2.2 IEC 61850 substation configuration

This section groups the functions of HMI570 which are related to substation configuration import.
The imported SCD file should at least contain a Protection IED and a NSD570 IED. The DataSet of
the Protection IED needs to be subscribed by the NSD570 IED.
Load Substation Configuration From Disk

This menu entry provides a file open dialog where the user is prompted to select the SCD file. After
processing the SCD file the user is automatically prompted to select one NSD570 instance out of a
list containing all NSD570 IED out of the SCD file.
Select IED
A drop down menu shows all IED instances of a previously loaded SCD file which are of IED type
NSD570. One instance needs to be selected to enable further configuration steps. After one
NSD570 is selected, the user is guided to the “Command Mapping Editor”.
Command Mapping Editor

If a SCD file gets initially imported into HMI570 the mapping between DataAttributes received from
the substation LAN and transmitted teleprotection commands is not defined. To define this
mapping an editor is integrated into HMI570. The editor enables the user to assign DataAttributes
out of subscribed DataSets to teleprotection commands.
Only DataAttributes fulfilling the criteria described in section 2.1.4 are listed in the Command
Mapping Editor and can be assigned to teleprotection commands. If a DataAttribute is not assigned
to a teleprotection command, it is ignored by G3LS.
Additionally to status attributes, quality attributes may be assigned to teleprotection commands.
Quality attributes have to be assigned immediately following on the corresponding status attribute.
If a quality attribute is assigned to a teleprotection command G3LS will process this command in
Mapped mode (see section 2.2.2). If the quality attribute is not assigned to a teleprotection
command G3LS works in unmapped mode (see section 2.2.1).
On SCL level HMI570 expects NSD570 IED instances with proper Inputs sections generated by the
SET. If the user assigns a command to a DataAttribute an intAddr tag is inserted into the
corresponding ExtRef line of the Inputs section.
If the command mapping is changed it is highly recommended to export the new NSD570
configuration as IID file. The IID file can be reimported into the SET. This step allows to store all
relevant information back to the SCD file. If the SCD file is exported again it will provide the
Command Mapping already. HMI570 will not prompt the user to define the mapping again. Of
course it is possible to rearrange commands if needed.
Verify Configuration Consistency

The consistency checker tool is described in detail in section 3.2.4. It can be called if a NSD570
IED configuration with mapped commands is available.
Discard Substation Configuration

The currently loaded substation configuration is discarded by HMI570.
3.2.3 IEC 61850 IED configuration

This HMI570 menu section groups the G3LS IED configuration functions. Most of these menu
entries are only available if HMI570 has loaded an IED configuration. There are three ways to get
an IED configuration loaded.
• The configuration can be imported from a SCD file as described in the previous section.
The IED configuration is available after “Generate From Substation Configuration” has
been executed.
• The IED configuration can be loaded from a CID or an ICZ file.
• The third possibility is to upload the configuration from a G3LS device.
D EN 12/25 1KHW002649-EN
Generate From Substation Configuration

An IED configuration for G3LS can be generated based on a SCD file. This menu entry initiates a
switch from substation mode to IED mode. In IED mode HMI570 operates on the data model of one
IED. All other IED which may are in the SCD file are out of scope until the IED configuration gets
discarded.
Load From Disk

An already existing IED configuration (CID file or ICZ file) is loaded from disk. HMI570
distinguishes between two different types of IED configuration files:
• IED configurations which are under control of a SET and have been imported from a SCD
file into HMI570.
• IED configurations which have been generated by HMI570’s CID editor. The CID editor will
be described in section 3.2.5.
Depending on the type of IED configuration HMI570 offers different functions to deal with the
configuration. Please refer to Table 1 to get an overview about file types.
Merge Proxy Capabilities From Remote Substation

This menu entry is only relevant with respect to Advanced Engineering as described in section 4.1.
The starting point is an IED configuration where the Inputs section is completely engineered but the
DataSet is not defined yet. The “Merge Proxy Capabilities From Remote Substation” function of
HMI570 prompts the user to import an ICD file. If the ICD file contains a NSD570 with DataSet the
existing Inputs section and the DataSet from the ICD file will be merged to a complete Proxy
Gateway configuration.
View Configuration
The view of the configuration is mainly provided for printing purpose. This link is only active if the
CID file is not marked as maintained by the SET. IED configurations maintained by a SET are not
visible in HMI570. This menu entry is only relevant with respect to manual engineering as
described in section 4.3.
Edit Configuration
Changing the IEC 61850 configuration parameters is only possible if the CID file is not marked as
maintained by the SET. The reason is that configurations generated by a SET shall not be altered
by HMI570, in order to keep consistency. This menu entry is only relevant with respect to manual
engineering as described in section 4.3.
Verify Configuration Consistency

The consistency checker tool will be described in detail in section 3.2.4.
Export as Instantiated IED Description (IID)

The current IED configuration can be exported to an IID file. The IID file serves as an update to be
imported into the SET. Since for manually engineered IED configurations no relation to a system
configuration exists, this functionality is not available for manually engineered IED configurations.
Save To Disk
Save a CID file or an ICZ file to disk. Please refer to Table 1 to get an overview about file types.
Download To Device
Download the IED configuration to the device.
Discard IED Configuration

This menu entry discards the currently active IED configuration. If the IED configuration has been
derived from an SCD file HMI570 will switch back to substation mode.
Upload From Device

Get the IED configuration back from the device.
D EN 13/25 1KHW002649-EN
3.2.4 Verify Configuration Consistency

A teleprotection link configuration including G3LS devices requires up to six configuration files.
Some parameters have to be consistent with each other. Since this is not always easy, HMI570
integrates a consistency verification tool.
The first step is to load a completely engineered IED configuration into the verification tool. Up to
five additional configuration files specifying the link configuration may be imported. The consistency
verification tool verifies the imported configuration files against the IED configuration of the local
NSD570.
The verification process consists of comparing the number of commands and the application
(Blocking, Permissive, Direct) types against each other. Inconsistent parameters are highlighted.
Parameters listed with “-“ are considered as “don’t care”.
3.2.5 CID Editor

The CID Editor is only relevant with respect to manual engineering approach as described in
section 4.3.
Based on a template CID file, a configuration for G3LS can be created manually. To start the CID
Editor click “Load From Disk” in the “IEC 61850 IED Configuration” and choose the Default CID file.
These are the parameters which are configurable for a G3LS IED. Most values have to match with
the corresponding parameters of the Protection IED.
Parameter Name Description
Common Parameter
Number of Protection Commands It is mandatory that the number of protection commands
matches to the value entered in the HW configuration of
G3LS. Please refer to section 3.1 for details.
G3LS Output (GCB to be published)
VLAN Priority Priority flag acc. IEEE 802.1p
VLAN ID Virtual LAN ID acc. IEEE 802.1Q
Data Set Name Name of the DataSet published by NSD570
Configuration Revision ConfRef has to match with the ConfRef expected by Prot.
IED
G3LS IED Application ID Numeric application ID (matches with ID of Protection IED)
G3LS IED Name IED name of NSD570
G3LS IED MAC Address Multicast MAC address used for GOOSE frames
GOOSE Control Block Name GCB name of NSD570
GOOSE Application ID Unique ID in string format.
normally according the following convention:
[NSD570 IED Name]LD0/LLN0.[NSD570 IED GCB Name]
G3LS Input (GCB to be subscribed)
Data Set Name Name of the DataSet published by the Protection IED
Logical Device Instance Name of Logical Device Instance e.g. LD0
Configuration Revision ConfRef has to match with the ConfRef sent by Prot. IED
Connected IED Application ID Numeric application ID (matches with ID of NSD570 IED)
Connected IED Name Protection IED name
Connected IED MAC Address Multicast MAC address used for GOOSE frames
GOOSE Control Block Name GCB name of Protection IED
GOOSE Application ID Unique ID in string format.
normally according the following convention:
[Prot. IED Name]LD0/LLN0.[Prot. IED GCB Name]
Table 2 Parameters manually entered
D EN 14/25 1KHW002649-EN
 Note: Files generated by substation engineering tools must not be altered by

HMI570. Therefore “View Configuration” and “Edit configuration” is only
supported with IED configurations created from scratch with HMI570.
4. IEC 61850 Engineering Concepts

HMI570 supports a total of three different engineering approaches to create an IEC 61850
configuration for G3LS. They are described in the following sections.
The Advanced Engineering Approach is the recommended procedure to generate an IEC 61850
configuration for G3LS. The resulting Proxy Gateway configuration provides as much semantics as
possible. Consistency between configurations of both substations is guaranteed by the involved
engineering tools.
The Simple Engineering Approach generates a GGIO Gateway configuration for G3LS. Compared
to the Advanced Engineering Approach it is more straight forward but it is also more error-prone.
There is less semantics available and consistency between the two configurations can be
guaranteed partially only with manual verification. With respect to configurations where only one
substation will be equipped with G3LS interfaces the Simple Engineering Approach might be the
preferred approach.
HMI570 provides also a limited set of features to edit a standard CID file of G3LS. This allows to
setup G3LS without using a SET. Manual configuration may be reasonable for laboratory
environments. However, it is not recommended for productive use.
4.1 Advanced Engineering Approach
4.1.1 Overview
As a starting point the local Protection IED is instantiated in the SET. A DataSet containing the
DataAttributes which will be transmitted over the teleprotection link is assigned. Based on the
DataModel and the DataSet of the local Protection IED a proxy configuration for the remote
NSD570 can be generated by HMI570. This system engineering process is complex but for the
most parts automated.
Features:
• Proxy Gateway Data Model is applied to G3LS. Different LN types (GGIO, PSCH, RBRF)
are supported. The commands are transmitted with semantics.
• The provision of required G3LS configuration parameters is automated. SCL files are
exchanged across substation borders.
• The teleprotection link configuration is derived from Protection IED configuration.
Restrictions:
• Forwarding commands from G3LR to G3LS and vice versa is currently not supported with
this engineering approach.
• A SET which supports IID file import is mandatory.
4.1.2 Configuration process

Figure 6 shows two separate and independent HMI570 instances, one in each substation. This
reflects the situation when a distributed configuration process takes place, e.g. during
commissioning of a substation. However, the described configuration steps can also be done in
only one HMI570 instance during overall project engineering and away from the substation.
D EN 15/25 1KHW002649-EN
Prot_A.icd NSD570_generic.icd
(1) HMI570 (3)
DB Substation_A.scd
(2) NSD570_A_proxy.icd Prot_B.icd
NSD570_A.iid
System DB
System HMI570 Engineering
Engineering Tool
Substation_B.scd
Tool
NSD570_B_proxy.icd (4)
NSD570_A.iid (5) NSD570_B.iid
Substation_A.scd
(6)
NSD570_A.icz NSD570_B.icz
Protection
Protection (7) (7) IED
IED Engineering
Engineering Tool
Tool
IED Configuration
IED Configuration
Legend:
Mandatory step Protection Protection
NSD570 A NSD570 B
Optional step IED A IED B
Figure 6 Advanced Engineering Approach

Figure 7 provides the relation between different phases of the engineering process and the
interfaces which are configured in each phase of the proxy engineering process. The numbers in
brackets refer to the phases of the process described below.
(2)
Substation
A B
(1)
Protection NSD570 NSD570 Protection
IED A A B (3) IED B
(6)
(4+5)
Figure 7 Interface definition and connection per process phase

The following description covers the configuration of a link consisting of one Protection IED and
one NSD570 per substation. In general there are no restrictions with respect to the number of
subscribed DataSets and publishing Protection IED. E.g. a setup with up to eight Protection IED
exchanging teleprotection commands over one NSD570 link is supported.
Phase 1, SET Substation A:

The Protection IED and the NSD570 IED are instantiated based on the corresponding ICD files.
HMI570 provides a generic capability description for G3LS. The following steps are done in the
SET for this first phase:
• The Protection IED is instantiated
• The DataSet of the Protection IED containing DataAttributes which will be transmitted over
the teleprotection link is defined.
• The corresponding GOOSE control block is created.
• The NSD570 IED is instantiated.
• The DataSet published by the Protection IED is subscribed by NSD570.
The above steps result in a configuration which defines the connection between the Protection IED
and the NSD570 IED in one direction. This intermediate status is exported to a SCD file.
D EN 16/25 1KHW002649-EN
Phase 2, HMI570 Substation A:

The intermediate substation configuration is imported into HMI570. HMI570 provides a list
containing all NSD570 devices found in the SCD file. The user is prompted to select one NSD570.
The next step is to define the mapping between DataAttributes subscribed by NSD570 and
teleprotection commands transmitted over the link. Each DataAttribute fulfilling the rules described
in section 2.1.4 can be assigned to a teleprotection command. Optionally the corresponding quality
value can be assigned to a dedicated teleprotection command. Please refer to section 2.2 for
details about quality mapping.
If this mapping is defined HMI570 is ready to generate a customized ICD file for the remote
NSD570 IED. This ICD file will be used to instantiate the NSD570 IED in the SET of substation B.
In comparison to the previously used generic ICD file the generated file provides a proxy gateway
description. The proxy data model provides semantic information according to the data model of
the represented Protection IED. Details about the proxy model are described in section 2.1.
The DataSet of the proxy gateway in Substation B is a merger of the fixed and always available
health status data from Logical Nodes LPHD and ITPC and the variable specified teleprotection
commands.
It is recommended to export the current configuration as an IID file. In addition to the configuration
imported from SCD file the IID file contains information about command mapping. The IID file can
be used to merge the command mapping information back to the SET. If such an updated SCD file
is imported into HMI570 later on, HMI570 will take over the command mapping from the SCD file.
Phase 3, SET Substation B:

The ICD file generated by HMI570 of Substation A in phase 2 is imported to the SET in Substation
B. The following steps are done in the SET to get a completely engineered NSD570 IED in
substation B:
• The Protection IED is instantiated.
• The DataSet of the Protection IED containing DataAttributes which will be transmitted from
substation B to substation A is defined.
• The corresponding GOOSE control block is created.
• The NSD570 IED is instantiated based on the generated ICD file.
• The GOOSE control block of the NSD570 IED is created. The DataSet which is defined in
the ICD file is assigned to the new GOOSE control block.
• The DataSet published by the Protection IED is subscribed by NSD570 IED.
• The DataSet published by NSD570 IED is subscribed by the Protection IED.
Now the NSD570 IED and the Protection IED of substation B are bidirectional connected. The
configuration is exported to a SCD file.
Phase 4, HMI570 of Substation B:

The SCD file of substation B is imported into HMI570 of substation B. The steps needed to be done
in HMI570 are similar to the steps done in Phase 2:
• Select the NSD570 IED
• Define the command mapping
• Generate the proxy for the remote substation. This is the proxy gateway which will be
instantiated in substation A. Therefore it is exported as ICD file by HMI570.
• Export the configuration of NSD570 to an IID file. Use the IID file to update the SET of
substation B.
Substation B is now completely engineered. Only the programming of the IED is not done yet.
D EN 17/25 1KHW002649-EN
Phase 5, HMI570 of Substation A:

As a starting point for the fifth phase there is an intermediate substation configuration for substation
A available. The intermediate substation configuration provides all parameters needed to send
commands from Protection IED A to NSD570 IED A. Additionally, a proxy gateway definition has
been generated by HMI570 of substation B. This ICD file provides a proxy gateway configuration
which supports to send commands from NSD570 IED A to Protection IED A. The remaining step to
get a bidirectional configuration for substation A is to merge the current substation configuration
with the proxy definition.
HMI570 supports this merging procedure automatically. As a starting point for this merging
procedure the IED configuration of NSD570 IED A needs to be present in HMI570. If the
configuration has not been discarded since Phase 2 this is still the case. Otherwise the SCD file
containing the current configuration of substation A needs to be imported into HMI570. After
selecting the corresponding NSD570 instance, an IED configuration can be generated by HMI570.
The proxy ICD file can be merged into the IED configuration. The merged configuration can be
exported to an IID file.
Phase 6, SET substation A:

The NSD570 IED instance needs to be updated using the IID file generated in phase 5. The
updated NSD570 has now a DataSet. The GOOSE control block of NSD570 is not defined yet. It
needs to be defined manually in the SET. Finally, Protection IED A is subscribed to the DataSet
published by NSD570 IED A. An updated SCD file can be generated and imported into HMI570.
Phase 7, HMI570 of Substation A and Substation B

Before the configuration is downloaded to the NSD570 IED a consistency check should be
performed. Please refer to section 3.2.4 for details about the configuration verification tool of
HMI570.
The recommended process to get the NSD570 devices programmed is to export the final
substation configuration from SET to an SCD file. If the NSD570 IED is configured based on the
SCD file it is guaranteed that the SCD file contains a complete set of configuration parameters. The
SCD file is imported into HMI570, the NSD570 IED is selected and an IED configuration can be
generated. The generated IED configuration can be downloaded to the NSD570 device. The IED
configuration can be stored to disk as well.
4.1.3 Summary related to HMI570

Previous sections provid an overview on a conceptual level. This section provides the relation to
HMI570 menu entries for each step of the Advanced Engineering Approach. One instance of
HMI570 runs in the context of Substation A, a second instance runs in the context of Substation B.
Links referred in the following list can be found in the “IEC 61850 Configuration” menu of HMI570.
HMI570 provides the generic ICD file of NSD570 for download. The download link can be found in
the “ICD Generator” view.
HMI570 running in substation A (Phase 2):

• Use “Load Substation Configuration From Disk” to import the SCD file containing the
intermediate substation configuration of substation A. Follow the screens of HMI570 to get
an IED configuration where the subscribed DataAttributes are mapped to teleprotection
commands.
• To generate the proxy ICD file for substation B a click on “Generate Proxy File For Remote
Substation” is enough.
• A click on ”Generate From Substation Configuration” triggers the transaction from
substation configuration mode to IED configuration mode. In IED configuration mode the
current configuration can be exported to an IID file. A click on “Export as Instantiated IED
Description (IID)” will generate the IID file which serves as an update for the SET.
HMI570 running in substation B (Phase 4):

The procedure for substation B is exactly the same as the procedure described for
substation A in Phase 2.
D EN 18/25 1KHW002649-EN
HMI570 running in substation A (Phase 5):

• If HMI570 does not still have the state from Phase 2 loaded, the SCD file is imported again.
If needed the link “Load Substation Configuration From Disk” is used to import the SCD file
again. If the SET has been updated with the IID file in Phase 2 the command mapping
information is included in the SCD file. After importing the SCD file HMI570 will directly
offer to switch to IED configuration mode. Please do so with a click on ”Generate From
Substation Configuration”.
• The next step is to merge the proxy ICD into the current configuration. The mentioned ICD
file has been generated in Phase 4. The link “Merge Proxy Capabilities From Remote
Substation” is provided for that purpose.
• The resulting configuration can be exported as IID file using the link “Export as Instantiated
IED Description (IID)”. This IID file will be imported into the SET.
HMI570 in both substations (Phase 7):

• This is now the right time to start the configuration consistency verification tool for both
substations. A click on the link “Verify Configuration Consistency” starts this tool. Please
refer to section 3.2.4 for details.
• Finally the IEC 61850 configuration is downloaded to the G3LS IED. If a device is
connected and HMI570 has loaded an IED configuration HMI570 offers the link “Download
To Device”.
• A click on “Save To Disk” offers to store the IED configuration as ICZ file or as CID file.
Please refer Table 1 to find a description about CID and ICZ file format.
4.2 Simple Engineering Approach
4.2.1 Overview
Simple engineering provides a straight forward approach to create a GGIO gateway configuration
for G3LS. Both substations can be engineered independently from each other since no exchange
of SCL files across substation boarders is needed during the configuration flow. As a drawback no
semantic validation across substation borders is provided.
First of all two customized ICD files are generated by a central instance of HMI570. Each ICD file
defines the capabilities of a NSD570 IED with customized DataSet. Since teleprotection commands
are forwarded straight to attributes in the DataSet of G3LS, the teleprotection link setup is implicitly
defined if the DataSets of both NSD570 IED are defined. Finally the NSD570 IED and the
Protection IED in each substation need to be connected with each other to get the teleprotection
link engineered.
Features:
• G3LS configuration without exchange of SCL files across substation boarders.
• Commands can be exchanged between G3LS and G3LR interfaces.
• Flexible and straight forward approach
Restrictions:
• Command mapping consistency across substation boarders can be guaranteed only with
manual verification.
• Semantic information is only available on LN type level. There is no real proxy generated.
D EN 19/25 1KHW002649-EN

The Simple Engineering Approach is shown in Figure 8 and Figure 9.
HMI570
(2) (2)
(1)
NSD570_A.icd NSD570_B.icd
ICD Editor:
definition of Phase 1
System teleprotection System
Prot_A.icd Prot_B.icd
DB Engineering link Engineering DB
Tool Tool
HMI570 HMI570
NSD570_A.iid NSD570_B.iid
Command Command
Substation_A.scd Substation_B.scd
(3)
(3)
Mapping Mapping
Editor Editor
CID, ICZ CID, ICZ

generator generator
NSD570_A.icz NSD570_B.icz
Protection (4) (4)
Protection
IED IED
Engineering Engineering
Tool Tool
IED Configuration
IED Configuration
Legend: Protection Protection

NSD570 A NSD570 B
IED A IED B
Optional step
Figure 8 Simple Engineering Approach
Substation
(2+3) A B
(1)
Protection NSD570 NSD570 Protection
IED A A B IED B
(1) (2+3)
Figure 9 Interface definition and connection per process phase

The engineering process is divided into different phases which are referenced by the numbers in
brackets in Figure 8 and Figure 9. Phase 1 is executed centrally for both substations. The
subsequent phases have to be executed for both substations. They are independent from each
other.
Following the configuration of a link consisting of one Protection IED and one NSD570 per
substation is described. In general there are no restrictions with respect to the number of
subscribed DataSets and publishing Protection IED. E.g. a setup with up to eight Protection IED
exchanging teleprotection commands over one NSD570 link is supported.
Phase 1, central instance of HMI570:

As a first step the teleprotection link requirements are defined. Based on the central link
configuration an ICD file for each substation is generated. The fact that a central instance of
HMI570 generates two ICD files ensures a consistent engineering across substation boarders.
The generated ICD files define two GGIO gateways where all parameters with respect to GOOSE
publishing are preconfigured. In detail these are the DataSet, LN instances for each teleprotection
command and the parameters related to GOOSE publishing of LN ITPC. The GOOSE subscriber
side (Inputs section) needs to be defined later on.
It is recommended to archive the configuration e.g. by printing the ICD Generator view. This will
simplify the configuration process in phase 3.
Phase 2, SET in each substation:

The following steps have to be executed in the SET to get the teleprotection link configured:
D EN 20/25 1KHW002649-EN
• The corresponding GOOSE control block is created and the corresponding DataSet is
attached.
• The NSD570 IED is instantiated. Therefore one of the previously generated ICD files is
imported into the SET of each substation.
• The GOOSE control block needed to publish the predefined DataSet of the NSD570 IED is
created.
• The DataSet published by the Protection IED is subscribed by the NSD570 IED.
• The DataSet published by NSD570 IED is subscribed by the Protection IED.
and the NSD570 IED in a bidirectional manner. This configuration is exported to a SCD file.
Phase 3, HMI570 in each substation:

The substation configuration is imported into HMI570. HMI570 provides a list containing all
NSD570 devices found in the SCD file. The user is prompted to select one NSD570. The next step
is to define the mapping between DataAttributes subscribed by NSD570 and teleprotection
commands transmitted over the link. Each DataAttribute fulfilling the rules described in section
2.1.4 can be assigned to a teleprotection command. Optionally the corresponding quality value can
be assigned to a dedicated teleprotection command. Please refer to section 2.2 for details about
quality mapping.
The commands have to be assigned in a consistent manner with the DataSet

Caution of the NSD570 IED in the remote substation.
It is recommended to assign the commands based on the ICD Generator
view which has been printed in phase 1.
It is recommended to export the NSD570 IED configuration to an IID file which will be used to
update the NSD570 IED in the SET. If this optional step is done the SET merges all configuration
parameters into the SCD file. If such a complete SCD file is imported into HMI570 the user will not
be prompted to do any kind of manual configuration again. HMI570 will directly allow to generate
and to download the device configuration.
Phase 4, HMI570 in each substation:

Before the configuration is downloaded to the NSD570 IED a consistency check should be
performed. Please refer to section 3.2.4 for details about the configuration verification tool of
HMI570.
The recommended process to get the NSD570 devices programmed is to export the final
substation configuration from SET to an SCD file. If the NSD570 IED is configured based on the
SCD file it is verified that the SCD file contains a complete set of configuration parameters as used
by NSD570. The SCD file is imported into HMI570, the NSD570 IED is selected and an IED
configuration can be generated. The generated IED configuration can be downloaded to the
NSD570 device.

Previous sections provided an overview on a conceptual level. This section provides the relation to
HMI570 menu entries for each step of the simple engineering process. Phase 1 is executed once.
Subsequent phases are executed per substation. Links referred in the following list can be found in
the “IEC 61850 Configuration” menu of HMI570.
Central instance of HMI570 (Phase 1):

• Use the link “ICD Generator” to start with the simple engineering process. Please refer to
section 3.2.1 for details about the ICD Generator.
• Enter the project specific link configuration.
• Archive the generated ICD files for both substations.
D EN 21/25 1KHW002649-EN
HMI570 running in each substation (Phase 3):

• Use “Load Substation Configuration From Disk” to import the SCD file containing the
substation configuration. Fallow the screens of HMI570 to get an IED configuration where
the subscribed DataAttributes are mapped to teleprotection commands.
• A click on ”Generate From Substation Configuration” triggers the transaction from
substation configuration mode to IED configuration mode.
• A click on “Export as Instantiated IED Description (IID)” will generate the IID file which
serves as an update for the SET.
HMI570 running in each substation (Phase 4):

• Recommended procedure:
o After the SET has been updated using the generated IID file a new SCD file can be
imported into HMI570. Triggered by a click on “Load Substation Configuration
From Disk” HMI570 will prompt the used to select one NSD570 IED. Finally it will
import the NSD570 IED configuration from SCD file including the command
mapping information. There are no additional parameters to be configured
manually.
o A click on ”Generate From Substation Configuration” triggers the transaction from
substation configuration mode to IED configuration mode.
• Shortcut variant:
o The loop over the SET is not mandatory. After phase 3 HMI570 can immediately
generate and download the configuration to the device. The disadvantage is that
the status of the substation configuration will never be verified.
• This is now the right time to start the configuration consistency verification tool for both
• Finally the IEC 61850 configuration is downloaded to the G3LS IED. If a device is
connected and HMI570 has loaded an IED configuration HMI570 offers the link “Download
To Device”.
• A click on “Save To Disk” offers to store the IED configuration as ICZ file or as CID file.
Please refer Table 1 to find a description about CID and ICZ file format.
4.3 Manual Engineering Approach
4.3.1 Overview
HMI570 integrates a simple CID Editor to create a IEC 61850 configuration for NSD570. This
engineering approach is simple though not flexible at all. Several configuration parameters have to
be configured manually, others are not configurable. The approach is feasible for testing purpose in
laboratory environments. It is not recommended to use it in productive environments.
Features:
• G3LS IEC 61850 configuration is generated without SCD files.
Restrictions:
• Only a small selection out of a large matrix of possible teleprotection link configurations is
supported.
• The connection between Protection IED and NSD570 is based on manual parameter entry.
There are many parameters which have to be consistent for both IED. This is not easy to
maintain without support of engineering tools. Maintaining the configuration manually is
error-prone.
• Commands are engineered without semantic (GGIO gateway approach).
• Engineering across substations is not automated.
D EN 22/25 1KHW002649-EN

The Manual Engineering approach is shown in Figure 10.
Prot_A.icd Prot_B.icd
SET SET
DB NSD570.icd NSD570.icd DB
Protection HMI570 HMI570 Protection

IED IED
Engineering Engineering
Tool Tool
IED Configuration NSD570_A.ICZ NSD570_B.ICZ IED Configuration
Protection Protection
NSD570 A NSD570 B
IED A IED B
Figure 10 Manual Engineering Approach

As visible in Figure 10 there is no SET needed to create a IEC 61850 configuration for NSD570.
The configuration for NSD570 is created using HMI570 only. Please refer to section 3.2.5 for
details about the CID Editor.
A SET is probably needed to configure the Protection IED. To get NSD570 instantiated into the
SET some static ICD files are provided. The files differ only in the number of supported
teleprotection commands. The following templates are provided:
• NSD570_GGIO_1CMD.ICD: One command
• NSD570_GGIO_2CMD.ICD: Two commands
• NSD570_GGIO_3CMD.ICD: Three commands
• NSD570_GGIO_4CMD.ICD: Four commands
• NSD570_GGIO_8CMD.ICD: Eight commands
As G3LS only provides GGIO Logical Nodes with this engineering approach, it will happen that the
connected Protection IED, having other Logical Nodes (e.g. PSCH, RBRF, etc.), must be
interconnected over the common functional constraint (fc) of type ‘ST’ (status). This implies that the
semantics of a teleprotection command is lost during transmission over the teleprotection gateway.
The system engineer has to manually verify if the Protection device output on one side matches the
Protection device input on the other side of the link.
The following process description is based on the assumption that a SCD file is mandatory to get
the Protection IED configured.
HMI570 in each substation:

To get an IEC 61850 configuration for NSD570 the CID Editor offers to create a customized CID
file for NSD570. Details about parameters which can be accessed with the CID Editor are covered
in section 3.2.5.
If the configuration is created it should be verified. Finally it can be stored to disk and downloaded
to the NSD570 IED.
SET in each substation:

The following steps need to be executed in a SET to get a minimum configuration for one
substation:
• The GOOSE control block of the Protection IED is created and the previously defined
DataSet is attached.
• A dummy instance of NSD570 is instantiated based on one of the previously mentioned
static ICD files.
• The DataSet published by the Protection IED is subscribed by the NSD570 IED.
• The DataSet published by NSD570 is subscribed by the Protection IED.
D EN 23/25 1KHW002649-EN
• Verify the DataSet of the Protection IED respectively the Inputs sections which will be
generated for the NSD570 IED fits to the Inputs section which is defined in the generated
CID file of the NSD570 IED.
and the NSD570 IED in a bidirectional manner. This configuration serves to finalize the Protection
IED configuration using the IED engineering tool.

The HMI570 related engineering process involves the steps mentioned below. The links can be
found in the Section “IEC 61850 IED Configuration” of HMI570.
• A default IED configuration is loaded using the link “Load From Disk” followed by a click on
the “load” button next to the file name “Default_G3LS_IED.cid”.
• The IED configuration can be adapted according to the teleprotection link requirements.
Please refer to section 3.2.5 to find a description about the parameters which are offered to
be changed by the CID editor.
• It is recommended to start the configuration consistency verification tool for both
• If the IED configuration is ready it can be exported to a CID or a ICZ file using the link
“Save To Disk”. For details about the offered file formats please refer to Table 1.
• Finally the IED configuration can be downloaded to the G3LS device. Therefore the link
“Download To Device” is provided.
4.4 Engineering Approach Comparison

Each of the engineering approaches presented above have advantages and disadvantages. Below
a feature comparison is provided:
Feature / Restriction Eng. approach
Advanced
Manual
Consistency across substation boarders is guaranteed by tools Yes Simple
No No
SCL files need to be exchanged across substation boarders Yes No No
Engineering across substations is automated Yes No No
Commands are transmitted with semantic (Proxy Gateway DataModel) Yes No No
Configuration consistency within a substation is guaranteed by tools Yes Yes No
Multiple Protection IEDs can be connected to one NSD570 Yes Yes No
Commands can be transmitted with dedicated Quality information Yes Yes No
G3LR interfaces can be used symmetrically in both substations Yes Yes Yes
One command can be exchanged between a G3LR and a G3LS interface No Yes Yes
Configuration can be verified by HMI570 Yes Yes Yes
G3LS configuration is possible without SCD file No No Yes
IED update using IID files needs to be supported by SET Yes No No
Table 3 G3LS IEC 61850 engineering approach comparison
D EN 24/25 1KHW002649-EN
5. Status information provided by G3LS

G3LS provides several types of alarm notifications representing the status of the teleprotection
equipment. In general the status of G3LS may be monitored on the following different notification
channels:
• G3LS provides alarm notifications via HMI570 and LED directly to the user.
• General G3LS alarm indication to the line interfaces of type G3LA, G3LD or G3LE.
• The Protection IED observes the status of G3LS based on information provided in the
DataSet which is published by G3LS.
In detail the notification channels of G3LS are provided as mentioned in the list below. Table 4
provides an overview about the mapping of internal alarms to external notification channels. Alarms
are logically OR-combined per notification channel.
• HMI570
All types of alarms are directly visible in HMI570 after an alarm upload has been
processed.
• LED of the Relay Interface 1
Some of the alarms generated by G3LS are mapped to the OK/Fail LED of the Relay
Interface 1.
• Indication to the line interfaces
All alarms except for “Wrong slot for G3LS” activate the “G3LS Interface Alarm” on the
corresponding line interface of type G3LA, G3LD or G3LE.
• LPHD.PhyHealth
Alarms related to the state of the physical communication device take influence on the data
object PhyHealth in the Logical Node LPHD. PhyHealth is set to either OK or Alarm by
G3LS. LPHD is always part of a G3LS DataSet.
• ITPC.EEHealth
Alarms related to the state of the communication channel take influence on the data object
EEHealth in the Logical Node ITPC. EEHealth is set to either OK or Alarm by G3LS. ITPC
is always part of a G3LS DataSet.
• Command quality
Some alarms are mapped to the Quality data attributes of the Logical Nodes representing
the teleprotection commands. Each teleprotection command is published with
corresponding quality attribute. Please refer to section 2.1.3 “G3LS published DataSet” for
details.
D EN 25/25 1KHW002649-EN
set on LINE INTERFACE
LPHD.PhyHealth.stVal 2
G3LS Interface Alarm 1
RELAY INTERFACE 1
ITPC.EEHealth.stVal
Command Quality
ITPC.EEHealth.q
Ok / Fail LED
Alarm from G3LS
ALS Automatic Laser Shutdown is active Ok Yes Alarm Ok Good Good
SFP transceiver not plugged Fail Yes Alarm Ok Good Good
SFP transceiver laser failure Fail Yes Alarm Ok Good Good
RTB CRC error Fail Yes Alarm Ok Invalid Good
RTB misalignment Fail Yes Alarm Ok Invalid Good
RTB disturbance Fail Yes Alarm Ok Invalid Good
Program memory CRC check failed Fail Yes Alarm Ok Invalid Good
Processor in safe operation mode Fail Yes Alarm Ok Good Good
Wrong time from RTC Ok Yes Alarm Ok Good Good
No signal (IRIG-B) on RTC Ok Yes Alarm Ok Good Good
G3LS HW configuration error Fail Yes Alarm Ok Invalid Good
IED configuration error Fail Yes Alarm Ok Invalid Good
Major ISS error Fail Yes Alarm Ok Good Good
LOS Loss of Signal Fail Yes Alarm Ok Good Good
FPGA not loaded Fail Yes Alarm Ok Invalid Good
Wrong slot for G3LS Fail No Alarm Ok Good Good
GOOSE Communication Failed Fail Yes Ok Ok Good Good
Ethernet Link Down Fail Yes Ok Ok Good Good
Alarm from Line Interface
HW Warning Ok - Ok Warning Good Good
Link Alarm Ok - Ok Alarm Good Invalid
Table 4 G3LS alarm mapping
1
The G3LS Interface Alarm activates the Local Alarm and the System Alarm on the corresponding line
interface.
2
Please note that LPHD.PhyHealth.q always indicates “Good“.
—
PGGA-PS | Grid Automation Products
Fault Report
To: PGGA-PS
Hitachi ABB Power Grids Switzerland Ltd E-Mail: CH-communication.networks.repairs@hitachi-powergrids.com
Power Grids Telephone +41 58 585 77 37
PGGA-PS Repair Center
Please always include a FAULT REPORT and the RMA number
Bruggerstrasse 72
when sending any item(s) to ABB for Repair & Return.
Please fill out a separate FAULT REPORT for each item and send the RMA request to PGGA-PS via email to
CH-communication.networks.repairs@hitachi-powergrids.com
Please do not ship the material without RMA number!
SECTION 1: General Information
Equipment Type (required): </For instance FOX615, FOX515, NSD, ETL, ...>
Module Type (required): </For instance CESM1, COBUX, G3LD, O4LE, ...>
Serial No. (required): </Please include your or End-Customer Project No./Reference>
PGGA-PS Order No. / Delivery date: </Inlcude material type/family>
Your Original PO No.: </Include the material model/module name>
SECTION 2: Fault Description
Problem Occurred: during installation in service

during commissioning other:
Observed Faults: Over-function Outside tolerance

Under-function Sporadic error
Abnormal temperature Repair Report required
Fault Description:
</Please provide a detailed Fault Description, this will enable us to process faster the Warranty/Repair case>
SECTION 3: Repair & Delivery Type
Warranty repair Advance replacement

Express repair / delivery
Service Contract Number :
SECTION 4: Customer’s Address

Delivery Address for repaired Item(s) Billing Address (if different from Delivery Address)
Company:
Address:
Post Code:
City:
Country:
Attn. To:
Mobile:
Telephone:
E-Mail:
Fax:
SECTION 5: Fault Report issued by
Name: Company:
E-Mail: City / Country:
Telephone: Date:
1 of 3 2021-08-12
—
Warranty Repair & Return Procedure
To: PGGA-PS
Power Grids Telepho +41 58 585 77 37
Bruggerstrasse 72
A. GENERAL
All of ABB’s equipment and parts are warranted against defects in material and workmanship for a period as agreed in the ORDER or in the SERVICE
CONTRACT.
Please always include a FAULT REPORT and the RMA number when sending any item(s) to ABB for Repair & Return.
Benefits of the Repair & Return Procedure:

- Quality of response
- Single Point-of- Entry to ensure the process efficiency and reliability
- Expedite service for all Service Contracts
B. REPAIR & RETURN PROCEDURE
2 of 3 2021-08-12
—
Guide & Help
To: PGGA-PS
Power Grids Telepho +41 58 585 77 37
Bruggerstrasse 72
Please fill out a separate FAULT REPORT for each item and send the RMA request to PGGA-PS via email to
CH-communication.networks.repairs@hitachi-powergrids.com
Please do not ship the material without RMA number!
C. Guide to complete the FAULT REPORT
▶ Completely fill out all 5 sections of a separate FAULT REPORT for each item.
▶ Include FAULT REPORT with Item(s) and refer to RMA no. when returned to PGGA-PS.
▶ E-Mail copy of FAULT REPORT to PGGA-PS including shipment tracking details.
▶ Include name and contact details of a technical person who can be contacted by the PGGA-PS repair engineers to discuss technical issues related
to the fault. This information shall be stated at Section 4 of the FAULT REPORT.
▶ Note down the equipment type to which the Item belongs to (e.g. FOX615, ETL600, NSD570) on the FAULT REPORT, Section 1.
▶ Note down serial number and release number (if any) of the faulty Item on the FAULT REPORT, Section 1.
▶ In case of SERVICE CONTRACT in force, the number of the SERVICE CONTRACT shall be indicated on the FAULT REPORT, Section 3.
▶ Advance Replacement:
If you need an Advance Replacement, tick the respective field on the FAULT REPORT.
A purchase order is required before shipment of the Advance Replacement. The customer will be invoiced for the full price of the Advance
Replacement unit.
Please note that PGGA-PS does not guarantee that Replacement Iitems will be available, except for Replacement Items defined in a SERVICE
CONTRACT.
▶ Testing fee:
This service will be charged with CHF 500.00 for each unit.
D. Purchase Order for Out of Warranty Repair
After receiving modules with FAULT REPORT the Item(s) will be repaired if
▶ under warranty or
▶ under Service Contract
otherwise a quotation for the repair cost will be sent to the customer.
NO REPAIR will be started by PGGA-PS until a Purchase Order for the amount quoted for repair is received by PGGA-PS. Items received by PGGA-PS
without a RMA no., FAULT REPORT and Purchase Order will be placed in isolation and no repair actions will be started until all the above documentation
is completed.
E. Packing & Transportation costs
When packing the Item(s) anti-static bags shall be used to wrap-in item(s) carefully. Please ensure that the packing is sufficient to avoid damages during
shipment. Ideally, item(s) shall be returned in the same packaging as it was supplied.
Any Item(s) received in damaged conditions, appearing to be caused from inadequate packing, will not be repaired until a purchase order covering repair
cost of the additional damage is received by PGGA-PS.
The transport to Baden has to be borne by the buyer.
3 of 3 2021-08-12
INSTRUCTION
Hitachi ABB Power Grids Extranet

Customer Connect Portal (CCP) User
Information - Benutzerinformation
Document ID 1KHW029009
Document edition Revision: E

Date: 2021-05-26
Copyright and confidentiality Copyright in this document vests in Hitachi Power Grids.
Manuals and software are protected by copyright. All rights reserved. The copying,
reproduction, translation, conversion into any electronic medium or machine scanna-
ble 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 agree-
ment of Hitachi Power Grids.
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 autho-
rized by contract or otherwise in writing by Hitachi Power Grids.
Disclaimer ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Hitachi ABB Power Grids Switzerland Ltd (hereinafter referred to as Hitachi ABB
Power Grids) has taken reasonable care in compiling this document, however Hitachi
ABB Power Grids 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 ABB Power Grids 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 ABB Power Grids reserves the right to amend this document at any time with-
out 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 ABB Power Grids 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 ABB Power Grids 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 sys-
tem functionality in your environment is as expected.
Copyright 2021 Hitachi Power Grids. All rights reserved. 2

Hitachi ABB | EXTRANET CONTENTS
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Steps to be taken by users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Einführung . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Erforderliche Benutzeraktionen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Hitachi ABB | EXTRANET INTRODUCTION
Für den deutschsprachigen Wortlaut siehe Abschnitt 3 Einführung (auf Seite 5).
English text follows below:
1 Introduction
The Wired Communication Networks product documentation and software, and the service tools
are provided via the specific “Wired Communication Networks Extranet” dashboard of the Cus-
tomer Connect Portal.
Registration is required, and registration requests need approval by Hitachi ABB Power Grids
before you can access the portal. The steps to be taken are explained below.
2 Steps to be taken by users

Steps required for logging in to the Wired Communication Networks Extranet
Proceed as follows:
1. Send an e-mail to the Hitachi ABB Power Grids Extranet Webmaster by clicking HERE.
Make sure that your sender e-mail address is identical with the e-mail address you will use
when signing up on the Customer Connect Portal. Do not modify the predefined subject and
text. Add your first name, last name, e-mail address, company address, and country in the e-
mail text. In case you want to register several users for your company, please add their first
name, last name, e-mail address, and phone number for each of the users by copying the
predefined e-mail body text.
2. After receiving your e-mail an administrator will verify your data and assign your account or
the requested accounts, respectively, to the “Wired Communication Networks Extranet”
dashboard of the Customer Connect Portal. This can take typically up to 2 business days.
3. Every registered user will get a confirmation e-mail when their “Wired Communication Net-
works Extranet” dashboard (on ccp.abb.com/wired-communication) is set up. Check your e-
mail inbox and activate your account by clicking on the link you have received from Hitachi
ABB Power Grids. You will have to accept the CCP terms and conditions prior to your first
login.
4. You will see this dashboard when you log in to the Customer Connect Portal.
End of instruction
For opening a trouble ticket related to your Hitachi ABB Power Grids products click on the 9-dot
icon in the title bar, then click on “Customer Support Portal”. You will be signed on automati-
cally.
If you have any question related to the “Wired Communication Networks Extranet” dashboard,
contact ch-mcs_extranet_webmaster@hitachi-powergrids.com via e-mail.

Hitachi ABB | EXTRANET EINFÜHRUNG
For the English text see section 1 Introduction (on page 4).
Nachfolgend der deutschsprachige Text:
3 Einführung
Die Dokumentation und Software für Wired Communication Networks Produkte sowie die Ser-
vice Tools sind auf einem spezifischen “Wired Communication Networks Extranet” Dashboard
des Customer Connect Portals verfügbar.
Eine Registrierung ist erforderlich; die Registrierung muss von Hitachi ABB Power Grids über-
prüft und bewilligt werden, bevor Sie Zugang erhalten. Die Details dazu sind im Folgenden
erklärt.
4 Erforderliche Benutzeraktionen
Erforderliche Schritte zum Einloggen im Wired Communication Networks Extranet
Gehen Sie wie folgt vor:
1. Senden Sie eine Email an den Hitachi ABB Power Grids Extranet Webmaster: klicken Sie
dazu HIER. Stellen Sie sicher, dass Ihre Absenderadresse mit der Email-Adresse identisch
ist, welche Sie beim Login auf dem Customer Connect Portal verwenden werden. Ändern
Sie bitte den vorgegebenen Betreff und Text nicht. Addieren Sie Vorname, Name, Email-
Adresse, Telefonnummer, Firmenanschrift und Land im Email-Text. Falls Sie mehrere Benut-
zer für Ihre Firma registrieren wollen, addieren Sie Vorname, Name, Email-Adresse und
Telefonnummer für jeden der Benutzer, indem Sie den vordefinierten Email-Text kopieren
und darunter einfügen.
2. Nach Empfang Ihrer Email wird ein Administrator Ihre Angaben überprüfen und Ihr Benutzer-
konto, bzw. die Benutzerkonten dem “Wired Communication Networks Extranet” Dashboard
des Customer Connect Portals zuordnen. Dies kann üblicherweise bis zu 2 Arbeitstage in
Anspruch nehmen.
3. Jeder registrierte Benutzer erhält eine Bestätigung per Email, wenn das “Wired Communica-
tion Networks Extranet” Dashboard (auf ccp.abb.com/wired-communication) aufgesetzt ist.
Überprüfen Sie Ihren Email-Posteingang und aktivieren Sie Ihr Benutzerkonto durch Klicken
des Links, den Sie in einer Email von Hitachi ABB Power Grids empfangen haben. Bei der
ersten Anmeldung müssen Sie die geltenden Geschäftsbedingungen akzeptieren.
4. Danach steht Ihnen dieses nach dem Login ins Customer Connect Portal zu Verfügung.
Ende der Anleitung
Für das Eröffnen eines Problem-Reports zu Ihren Hitachi ABB Power Grids-Produkten klicken
Sie bitte auf das 9-Punkte-Symbol in der Titelleiste des Portals und dann auf “Customer Support
Portal”. Sie werden dort automatisch angemeldet.
Bei Fragen zum “Wired Communication Networks Extranet” Dashboard kontaktieren Sie bitte
ch-mcs_extranet_webmaster@hitachi-powergrids.com via Email.

—
Hitachi ABB Power Grids Switzerland Ltd
Bruggerstrasse 72
5400 Baden - Switzerland
Phone: please refer to https://www.hitachi-powergrids.com/contact-us/Customer-Connect-Center

(Customer Contact Center)
www.hitachi-powergrids.com/communication-networks
Document ID: 1KHW029009
Copyright 2021 Hitachi Power Grids. All rights reserved.

Specifications subject to change without notice.
Notification Form for Errors in this Document
Dear User
We constantly endeavour to improve the quality of our technical publications and
would like to hear your suggestions and comments. Would you therefore please fill in
this questionnaire and return it to the address given below.

Grid Automation, PGGA
Bruggerstrasse 72
CH-5400 Baden
e-mail communication.networks@hitachi-powergrids.com
---------------------------------------------------------------------------------------------------------------
Concerns publication(s): ____________________________________________
Have you discovered any mistakes in this publication? If so, please note here the
pages, sections etc.
Do you find the publication readily understandable and logically structured? Can you
make any suggestions to improve it?
Is the information sufficient for the purpose of the publication? If not, what is missing
and where should it be included?
Name Date
Company
Postal code Town Country

IMPORTANT NOTICE!
The NSD570 equipment may only be installed, operated and

maintained by trained personnel.
Experience has shown that reliable operation of our products is

assured, providing the information and recommendations con-
tained in these Operating Instructions are adhered to.
It is scarcely possible for the instructions to cover every eventu-

ality that can occur when using technical devices and systems.
We would therefore request the user to notify us directly or our
agent of any unusual observations or instances, in which these
instructions provide no or insufficient information.
In addition to these instructions, any applicable local regulations

and safety procedures must always be strictly observed both
when connecting up and commissioning this equipment.
Any work such as insertion or removal of soldered jumpers or

setting resistors, which may be necessary, may only be per-
formed by appropriately qualified personnel.
We expressly accept no responsibility for any direct damage,

which may result from incorrect operation of this equipment,
even if no reference is made to the particular situation in the
Operating Instructions.
Third Party Code:

Additional copyright notices and license terms applicable to
portions of the software are set forth in the
THIRDPARTYLICENSEREADME file. In addition to any terms
and conditions of any third party opensource/freeware license
identified in the THIRDPARTYLICENSEREADME file, the
disclaimer of warranty and limitation of liability provisions in the
contract shall apply to all software in this product.

Contact us:

Bruggerstrasse 72
CH-5400 Baden
Phone: please refer to https://www.hitachi-powergrids.com/contact-us/Customer-Connect-Center

(Customer Connect Center)
www.hitachi-powergrids.com/communication-networks

Document ID:1KHW000890

Specifications subject to change without notice.

1KHW000890-En NSD570 Operating Instructions (13th Ed. Aug. 2021)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1KHW000890-En NSD570 Operating Instructions (13th Ed. Aug. 2021)

Uploaded by

Copyright:

Available Formats

OPERATING INSTRUCTION S

HITACHI ABB POWER GRIDS

Document revision: 1st Edition 2002-12-20 7th Edition 2009-12-24

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

Copyright 2002-2021 Hitachi Power Grids. All rights reserved.

4. User interface program

5. Configuration and settings

6. Installation and wiring

8. Operation and maintenance

10. Storage, decommissioning and disposal

1. Introduction ............................................................. 1-1

2. Safety Instructions .................................................. 2-1

3. System Description ................................................. 3-1

Contents August 2021 1-I

3.4.3. Digital Line Interface G3LD .................................................... 3-25

1-II August 2021 Contents

3.5. Functional description ............................................................ 3-51

Contents August 2021 1-III

3.5.15. Functions of the Ethernet system .......................................... 3-78

1-IV August 2021 Contents

4. User interface program ........................................... 4-1

Contents August 2021 1-V

4.10.6.5. Clear Event Recorder ............................................................ 4-27

1-VI August 2021 Contents

4.13.1. User Activity Logging ............................................................. 4-49

5. Configuration and Settings .................................... 5-1

Contents August 2021 1-VII

1-VIII August 2021 Contents

5.11.2.2. Network configuration hints.................................................... 5-42

6. Installation and wiring ............................................ 6-1

Contents August 2021 1-IX

6.5.3.6. Digital Interface G3LD............................................................ 6-17

7. Commissioning ....................................................... 7-1

8. Operation and maintenance ................................... 8-1

9. Troubleshooting ...................................................... 9-1

1-X August 2021 Contents

9.3.4. High level and user alarms ...................................................... 9-6

10. Storage, decommissioning and disposal ........... 10-1

11. Appendices ............................................................ 11-1

Contents August 2021 1-XI

1-XII August 2021 Contents

Fig. 3-37 Example G3LS commissioning ........................................................ 3-87

Contents August 2021 1-XIII

Fig. 6-10 G3LR cable for relay interface ......................................................... 6-14

1-XIV August 2021 Contents

Contents August 2021 1-XV

1-XVI August 2021 Contents

Contents August 2021 1-XVII

IED Intelligent Electronic Device

1-XVIII August 2021 Contents

RTC Real Time Clock

Contents August 2021 1-XIX

Fig. 1-1 Front view of NSD570

Introduction August 2021 1-1

1.1. Using these Operating Instructions

1.2. Personnel qualifications

1.2.1. Operating personnel

1-2 August 2021 Introduction

1.2.2. Service personnel

1.3. Warranty restriction

Introduction August 2021 1-3

2.1. Presentation of safety information

In this manual the safety instructions are marked as follows:

Information or dos and don’ts to prevent serious