Intertrip Equipment NSD570

p

1KHW000890-ENEdition April 2004

CommunicateIT NSD570 Teleprotection System Operating Instructions

© 2002 ABB Switzerland Ltd Baden

Released Editions Release Date1st Edition 2002-12-20 2nd Edition 2003-01-31 3rd Edition 2003-09-01 4th Edition 2004-04-16

This Operating Instructions applies to the NSD570 Teleprotection System. All rights with respect to this document, including applications for patent and registration of other industrial property rights, are reserved. Unauthorized use, in particular reproduction or making available to third parties, is prohibited. This document has been carefully prepared and reviewed. Should in spite of this the reader find an error, she/he is requested to inform us at her/his earliest convenience. The data contained herein purport solely to describe the product and are not a warranty of performance or characteristic. It is with the best interest of our customers in mind that we constantly strive to improve our products and keep them abreast of advances in technology. This may, however, lead to discrepancies between a product and its “Technical Description” or “Operating Instructions”.

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 Switzerland Ltd

April 2004

1. Introduction

1.1. Using these Operating Instructions .......................................... 1-3

1.2. Personnel qualifications ........................................................... 1-3 1.2.1. Operating personnel ................................................................ 1-3 1.2.2. Service personnel .................................................................... 1-4

1.3. Warranty restriction.................................................................. 1-4

Introduction April 2004 1-1

ABB Switzerland Ltd 1KHW000890-EN NSD570

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 or digital communication links. Analog links include pilot wires, speech channels of power line carrier equipment and voice channels of analog or digital communication systems, whereas digital channels include G.703 co-directional, RS-422/V.11 - RS-449/RS-530/ X.21 (56 kbps, 64 kbps), E1, T1 interfaces and optical fibers.

The conversion from an analog to a digital system is possible by exchanging of only one module (the line interface of the NSD570).

The NSD570 comprises printed circuit boards with a height of three standard units (3U) mounted in a 19" 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.

Fig. 1.1 Front view of NSD570

1-2 April 2004 Introduction


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 the annex of the manual.

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

Introduction April 2004 1-3


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.

1-4 April 2004 Introduction


April 2004

2. Safety Instructions

2.1. Presentation of safety information ........................................... 2-2

2.2. Basic principles........................................................................ 2-3

2.3. General instructions................................................................. 2-3

2.4. Product-specific instructions .................................................... 2-4

Safety Instructions April 2004 2-1


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:

DANGER Information or do’s and don’ts to prevent serious personal injury or extensive equipment damage.

Caution Specific information or do’s 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:

DANGER Hazardous voltage and hazardous energy level. Beware of electric shock.

Caution Specific information to prevent minor damage and operating problems.

Caution ESD

Specific information to prevent equipment damage by electrostatic discharge.

2-2 April 2004 Safety Instructions


2.2. Basic principles

The NSD570 is a state-of-the-art equipment that fulfils 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

DANGER An authorized and properly trained personnel only is admitted to carry out installing, programming, commissioning, maintenance, troubleshooting and work of the equipment.

Instruction Manual

DANGER The Operating Instructions should be read and clearly understood before working on the equipment.

Safety and monitoring facilities

DANGER Mechanical safety facilities such as cover plates must not be removed or by-passed.

Alteration

DANGER Alteration of the equipment is not allowed.

Warning labels

DANGER Precautions and indications to hazardous voltages and hazardous energy level must be strictly observed.



2.4. Product-specific instructions

Technical specifications

DANGER The equipment must be operated within the technical specifications. Failure to do so may result in personal injuries or equipment damage.

Alteration

DANGER Alteration of the equipment is not allowed.

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.

ESD protection

Caution ESD

The modules in this equipment contain devices, 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

DANGER The equipment must be mounted in a cabinet.

DANGER Cabinets, which are not secured to the floor, tip 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

DANGER This is a Class Ι equipment specified in IEC 60950. The equipment and the cabinet must be earthed. The equipment must be supplied over circuit breaker.

DANGER The circuit breaker for the power supply of the equipment must be switched OFF. The circuit breakers for optional equipment in the cabinet must be switched OFF.

DANGER Do not connect or disconnect energized cables to or from the equipment.

DANGER The isolating terminals of the external cables must be kept open during installation, maintenance and before storage, decommissioning and disposal.

DANGER The Faston supply connectors at the rear of the rack must be covered with an isolation sleeve.

DANGER The power supply is dangerous (hazardous voltage 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 and also the rear cover, ensure that the optical fibers are not bruised or crimped.

Back cover

DANGER Hazardous voltages and/or hazardous energy level 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

DANGER Do not work on the system or connect or disconnect cables during periods of lightning.

Electrical strength test

DANGER Do not repeat any electrical strength tests. Improper 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.

Common Interface G3LC

DANGER Hazardous voltages and/or hazardous energy level on the module and the cable. Do not touch the module and the cable leads.

Relay Interface G3LR


LAN Interface G3LL

DANGER The LAN Interface G3LL contains a lithium battery.

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.

Laser / LED

Caution Laser / LED

Class Ι Laser/LED Product.

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.



April 2004

3. System Description

3.1. Introduction .............................................................................. 3-5 3.1.1. General NSD570 Features ...................................................... 3-6 3.1.2. Features of the NSD570 Analog .............................................. 3-8 3.1.3. Features of the NSD570 Digital ............................................... 3-8

3.2. Communication Channels........................................................ 3-9

3.3. System Architecture............................................................... 3-10 3.3.1. System Block Diagram........................................................... 3-10 3.3.2. Mechanical Design ................................................................ 3-11 3.3.3. External connections.............................................................. 3-12 3.3.4. Frontplate Signals and Controls............................................. 3-13 3.3.5. Service interface (COM 1) ..................................................... 3-13 3.3.6. Power supply G3LH............................................................... 3-14 3.3.7. Examples of rack assemblies ................................................ 3-14

3.4. Modules descriptions ............................................................. 3-17 3.4.1. Common Interface G3LC....................................................... 3-17 3.4.1.1. Block diagram G3LC.............................................................. 3-17 3.4.1.2. Short description G3LC.......................................................... 3-18 3.4.2. Analog Line Interface G3LA................................................... 3-19 3.4.2.1. Block diagram G3LA.............................................................. 3-19 3.4.2.2. Short Description G3LA ......................................................... 3-19 3.4.2.3. External Interfaces G3LA....................................................... 3-20 3.4.2.4. Processor Environment G3LA ............................................... 3-20 3.4.2.5. Transmitter G3LA .................................................................. 3-21 3.4.2.6. Receiver G3LA ......................................................................3-21 3.4.2.7. Boosting Output G3LA........................................................... 3-22 3.4.3. Digital Line Interface G3LD.................................................... 3-22 3.4.3.1. Block diagram G3LD.............................................................. 3-22 3.4.3.2. Short Description G3LD......................................................... 3-22 3.4.3.3. External Interfaces G3LD....................................................... 3-23 3.4.3.4. Processor Environment G3LD ............................................... 3-23 3.4.3.5. External Cable and Connector G3LD..................................... 3-24 3.4.3.6. E1/T1 Interface G1LE ............................................................ 3-24 3.4.3.7. Optical Interface G1LO .......................................................... 3-25 3.4.4. Relay Interface G3LR ............................................................ 3-26 3.4.4.1. Block diagram G3LR.............................................................. 3-26 3.4.4.2. Short Description G3LR......................................................... 3-26 3.4.4.3. Inputs G3LR........................................................................... 3-27

System Description April 2004 3-1


3.4.4.4. Solid State Outputs G3LR...................................................... 3-27 3.4.4.5. Relay Contacts G3LR ............................................................ 3-28 3.4.4.6. Input Tripping Voltage G1LR ................................................. 3-28 3.4.4.7. External Cable and Connector G3LR..................................... 3-28 3.4.5. Display Panel G1LC............................................................... 3-29 3.4.5.1. Short Description G1LC......................................................... 3-29 3.4.5.2. How to use the Display Panel G1LC...................................... 3-30 3.4.5.2.1. Display Panel activation and standby .................................... 3-30 3.4.5.2.2. Buttons on G1LC ...................................................................3-30 3.4.5.2.3. Menu navigation hints ............................................................ 3-31 3.4.5.2.4. Reset ..................................................................................... 3-31 3.4.5.2.5. Display Panel settings............................................................ 3-31 3.4.5.3. Menu Structure Display Panel G1LC ..................................... 3-32 3.4.5.3.1. Top level menu ......................................................................3-32 3.4.5.3.2. Menu tree if connected to a local device................................ 3-32 3.4.5.3.3. Menu tree if connected to a remote device ............................ 3-34 3.4.5.4. Additional Features of Display Panel G1LC........................... 3-35 3.4.5.4.1. Requirements ........................................................................ 3-35 3.4.5.4.2. Display device communication baud rate............................... 3-35 3.4.5.4.3. Reset counters via display panel ........................................... 3-35 3.4.5.4.4. Disabling reset counters via display panel ............................. 3-35 3.4.5.4.5. Automatic display of Tx or Rx commands.............................. 3-36 3.4.6. LAN Interface G3LL ............................................................... 3-37 3.4.6.1. Short Description G3LL.......................................................... 3-37 3.4.6.2. Block diagram G3LL .............................................................. 3-38

3.5. Functional description ............................................................ 3-39 3.5.1. General Operating Principle................................................... 3-39 3.5.2. Signal processing .................................................................. 3-39 3.5.3. Analog Operating Principle .................................................... 3-40 3.5.3.1. Single-tone principle .............................................................. 3-40 3.5.3.2. Dual-tone principle ................................................................. 3-41 3.5.3.3. Programming of the analog system ....................................... 3-41 3.5.4. Analog Operating Modes ....................................................... 3-43 3.5.4.1. 1 single tone command A ...................................................... 3-43 3.5.4.2. 2 independent single tone commands A, B............................ 3-44 3.5.4.3. 2 independent dual tone commands A, B .............................. 3-44 3.5.4.4. 3 independent dual tone commands A, B, C.......................... 3-45 3.5.4.5. 4 independent dual tone commands A, B, C, D ..................... 3-46 3.5.5. Digital Operating Principle ..................................................... 3-48 3.5.5.1. Digital code structure ............................................................. 3-48 3.5.5.2. Digital frame structure............................................................ 3-48 3.5.5.3. Programming of the digital system......................................... 3-49 3.5.6. Digital Operating Modes ........................................................ 3-49 3.5.7. Common Functions................................................................ 3-50 3.5.7.1. Command Application............................................................ 3-50

3-2 April 2004 System Description


3.5.7.2. Unblocking ............................................................................. 3-50 3.5.7.3. Tx Trip Duration Monitoring ................................................... 3-51 3.5.7.4. Tx input command delay........................................................ 3-51 3.5.7.5. Command Prolongation ......................................................... 3-52 3.5.7.6. Command Acknowledge ........................................................ 3-52 3.5.7.7. Rx Guard ............................................................................... 3-53 3.5.8. Functions of the analog system ............................................. 3-53 3.5.8.1. Transmit level setting / Transmit level monitoring .................. 3-53 3.5.8.2. Receive level setting / Receive level monitoring .................... 3-53 3.5.8.3. Boosting / Boost Output ......................................................... 3-54 3.5.8.4. Embedded Operation Channel (EOC) ................................... 3-54 3.5.9. Functions of the digital system............................................... 3-55 3.5.9.1. Bit error rate monitoring ......................................................... 3-55 3.5.9.2. Addressing............................................................................. 3-55 3.5.9.3. Embedded Operation Channel (EOC) ................................... 3-56 3.5.10. Event Recorder......................................................................3-57 3.5.10.1. General .................................................................................. 3-57 3.5.10.2. Command Events .................................................................. 3-57 3.5.10.3. Alarm Events ......................................................................... 3-58 3.5.10.4. Manipulation Events............................................................... 3-58 3.5.10.5. RTC Synchronization From an External Clock....................... 3-58 3.5.11. Counters ................................................................................ 3-59 3.5.12. Test facilities .......................................................................... 3-59 3.5.12.1. Testing during normal operation ............................................ 3-59 3.5.12.2. Cyclic Loop Test .................................................................... 3-60 3.5.12.3. Manual Loop Test .................................................................. 3-61 3.5.12.4. Local Test Mode ....................................................................3-61 3.5.12.5. Remote Test Mode ................................................................ 3-62

3.6. NSD570 Applications ............................................................. 3-63 3.6.1. Permissive tripping schemes ................................................. 3-63 3.6.1.1. Permissive underreaching transfer tripping (PUTT)............... 3-64 3.6.1.2. Permissive overreaching transfer tripping (POTT)................. 3-65 3.6.2. Blocking schemes.................................................................. 3-66 3.6.3. Unblocking ............................................................................. 3-68 3.6.4. Earth fault protection.............................................................. 3-70 3.6.5. Duplicated main protection .................................................... 3-71 3.6.6. Direct transfer tripping............................................................ 3-73 3.6.6.1. Line protection .......................................................................3-73 3.6.6.2. Re-closure lock out ................................................................ 3-74 3.6.6.3. Breaker back-up protection.................................................... 3-74 3.6.6.4. Shunt reactor protection......................................................... 3-75 3.6.6.5. Transformer protection........................................................... 3-76 3.6.6.6. Power system instability......................................................... 3-76 3.6.6.7. Generator shutdown and load shedding ................................ 3-77 3.6.6.8. Typical requirements in direct tripping applications ............... 3-78



3.6.7. Teed lines and tapped lines ................................................... 3-79 3.6.7.1. NSD570 Analog/Digital in “normal” T-operation..................... 3-81 3.6.7.2. NSD570 Analog/Digital in “inverse” T-operation .................... 3-82 3.6.7.3. Addressing of NSD570 Digital in T-operation ........................ 3-83 3.6.7.4. Tapped lines .......................................................................... 3-85 3.6.8. Phase-Segregated Command Transmission ......................... 3-86 3.6.8.1. Twin Line - Two Systems on Common Towers...................... 3-86 3.6.8.2. Long Single EHV Overhead Line ........................................... 3-87



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, and for digital communication facilities, provided by digital multiplexers, and for optical fiber.

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 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 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).



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, or via optical fibers.

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 commands via digital lines; 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 or digital 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 per device). 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 d.c. 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 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.

Remote access An optional LAN interface is 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.

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 protection, 1 + 1 configuration Two independent NSD570 units in a common rack, for improved reliability in duplicated protection schemes. A mix of digital and analog units in the same rack is possible.

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.

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 on 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 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 centre 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 Short transmission times (as low as 4 ms transmitting one command, or 6 ms transmitting two to four commands) 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.

Programmable command configuration Any command programmable for blocking, permissive tripping or direct transfer tripping.

Up to 8 independent commands per unit 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 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.

3.2. Communication Channels

Protectioncommands

analoganalog

analog

Protectioncommands

3-Com.-Channels.vsd

analo

g

analo

gdi

gita

lan

alog

digi

tal

optic

al analog

analog

digital

digital

optical

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



3.3. System Architecture

3.3.1. System Block Diagram

StationBus

SYNCGPS

DC /MAINS 1

DC /MAINS 2

CommonInterface

Busplane (with Front Cover)

LAN Interface /Web Server

Laptop

Relay Interface

Line Interface(analog, digital

or optical)

Ala

rm 1

Ala

rm 2

LIN

E

INP

UT

OU

TPU

T

RE

LAY

INP

UT

OU

TPU

T

RE

LAY

LIN

E

BO

OS

T(a

nalo

g)B

OO

ST

(ana

log)

LAN

Pow

er S

uppl

y 1

Display Panel

SupplyBackplane

Pow

er S

uppl

y 2

Relay Interface

Line Interface(analog, digital

or optical)

G7BI

G1LC

G1LB

G3LCG3LR

(or G3LR/G1LR)

G1LA

G3LA or G3LD(or G3LD/G1LE or G3LD/G1LO)

G3LL

G3L

H

G3L

H

G3LA or G3LD(or G3LD/G1LE or G3LD/G1LO)

G3LR(or G3LR/G1LR)

3-System block diagram.vsd

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 analog NSD570 system consists of:

1 Module Rack, type G7BI 1 Analog Interface, type G3LA 1-4 Relay Interface(s), type G3LR



The digital NSD570 system consists of:

1 Module Rack, type G7BI 1 Digital Interface, type G3LD 1-4 Relay Interface(s), type G3LR

Available options for both NSD570 systems are:

1 Display Panel per Module Rack G7BI, type G1LC 1 LAN Interface per Module Rack G7BI, type G3LL 1 piggyback per Relay Interface G3LR for tripping the two command

inputs by an internal d.c. voltage and an external dry contact only, type G1LR

Options available for the digital NSD570 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

3.3.2. Mechanical Design

Supply Backplane G1LB

Pow

er S

uppl

y G

3LH

300

mm

Pow

er S

uppl

y G

3LH

Com

mon

Inte

rfac

e G

3LC

G3L

R, G

3LL

G3L

A, G

3LD

G3L

R

G3L

R

G3L

R

G3L

R

G3L

A, G

3LD

G3L

R

G3L

R

G3L

R

Analog Interface G3LADigital Interface G3LDRelay Interface G3LRLAN Interface G3LL

Optional:Display PanelG1LC

BlankingCover Plate

Bus Plane with front cover G1LA

Top view3-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 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 raster units (8R) for single or redundant power supply - 1 slot with 6R 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

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 Sub-D connectors, RJ45 connectors or spring-clamp terminal connectors (2.5 mm2).

By using the optionally available connecting cables, the signals can then be routed to isolating terminals (4 mm2), to Sub-D 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. The length of the connecting cables is 2.5 meters (refer to Section 6 of this manual 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 optical connectors used are E2000.




3.3.4. Frontplate Signals and Controls

Fig. 3.4 Frontplate signals and controls

Status and alarm LEDs on the front panel: - 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 (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 frontplate 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 Sub-D 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) Sub-D connector.

Via the serial RS-232 interface a 57600 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 of this manual).

3.3.6. Power supply G3LH

The rack can be equipped with one single power supply unit type G3LH or may have a redundant supply with two units. The input voltage range of the power supply unit covers all the standard battery voltages between 48 VDC and 250 VDC and a mains supply of 115 VAC to 230 VAC. The power supply cable is connected to FASTON terminals located on the side of the unit (refer to Section 6 of this manual). The power supply modules are hot pluggable.

3.3.7. Examples of rack assemblies

Find below a few examples how a 19" rack NSD570 can be equipped.

• Basic Equipment Analog:

Minimal 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; capable of transmitting up to two commands.

G7BIREAR VIEW(COVER REMOVED)

X10

3

X10

1

X10

0

X102 PO

WE

R S

UPP

LY 1

84 4076 70 64 58 52 46 34 28 22 09 01

X105 X104PE PE

PS2 PS1

G3LR G3LA G3LC G1LBG3LH

3-Rear View_Analog.vsd

POW

ER S

UP

PLY

2

Fig. 3.5 Basic equipment analog



• Basic Equipment Digital:

Minimal rack assembly, comprising of one Module Rack type G7BI, one Digital Interface type G3LD, one Relay Interface type G3LR and a single Power Supply type G3LH; capable of transmitting up to two commands.


X10

3

X101

X101

X201

X102 PO

WER

SU

PPL

Y 1

PO

WER

SU

PPL

Y 2

84 4076 70 64 58 52 46 34 28 22 09 01

X105 X104PE PE

PS2 PS1

EQUIPMENT 1EQUIPMENT 2

G3LR G3LD G3LC G1LBG3LH

3-Rear View_Digital.vsd

Fig. 3.6 Basic equipment digital

• Two independent NSD570 in the same rack:

Rack assembly for transmitting the maximum number of commands with an analog system (4 commands) and a digital system (8 commands) in the same module rack.


X10

1

X103

X10

1

X10

1

X10

1

X101

X10

1

X10

1

X10

0

X20

1

X10

2

POW

ER

SU

PPLY

1

POW

ER

SU

PPLY

2

84 4076 70 64 58 52 46 34 28 22 09 01

X105 X104PE PE

PS2 PS1


G3LR G3LDG3LRG3LRG3LR G3LRG3LR G3LA G3LC G1LBG3LH

3-Rear View_Mixed.vsd

Fig. 3.7 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.


X10

1

X103

X10

1

X10

1

X10

1

X101

X10

1

X10

1

X10

1

X10

1

X10

0

X20

1X1

01

X10

2

POW

ER

SU

PPLY

1

POW

ER

SU

PPLY

2

84 4076 70 64 58 52 46 34 28 22 09 01

X105 X104PE PE

PS2 PS1


G1LRG3LR

G1LEG3LD

G1LRG3LR

G1LRG3LR

G1LRG3LR

G1LRG3LR

G1LRG3LR

G1LRG3LR

G1LRG3LR G3LA G3LC G3LH G1LBG3LH

3-Rear View_Fully.vsd

Fig. 3.8 Fully equipped rack with redundant power supply units



3.4. Modules descriptions

3.4.1. Common Interface G3LC

3.4.1.1. Block diagram G3LC

RS-232

RS-485

SYS_AL_1

externIRIG-B

externGPS_SYNC

RX_DATA1TX_DATA2

SYS_AL_2

X901

RTB

SUP1

SUP2

GND GND

12.3 V Supply 1

12.3 V Supply 2

Supply supervision&

plug In check

12 V

2-wire communication busRS-232 transceiver

&isolated supply

RS-485 transceiver&

isolated supply

DC/DC5 V Supplymax. 1 A

+12 V

+5 V

RTB clock&

frame sync FS_RTB8.192 MHz

Relay 1, X102

Relay 2, X102

IRIG-B

GPS_SYNC

Check1Check2

SUP_AL_1SUP_AL_2

TxD_RTB

LOOP_DISRxD_RTB

LCD-DisplayX101

LED_0..34

Supply1_LEDALARM1_LEDSupply2_LEDALARM2_LED

2-wire communication bus for G1LCRX_DATA2TX_DATA2 12 V

COM1

2

2

RTB

3-Block-diagram-G3LC.vsd

Fig. 3.9 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, busplane 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 busplane 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 busplane 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 Sub-D, 9 pin female connector X901 on the front panel.

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) 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 connection of the synchronization inputs (GPS-synchronization, 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

Digital signalprocessor

SPORT1

SDRAM

RTC

uC

Serial-FLASH

SPORT0

RTB

RS-232

Reset

DODI

CLKFS

Outbuffer

8

Data bus

Buffer8

32

Inbuffer

Watchdog33 MHz

RS-485Reset

WD

Loop Test

Flag

32

8

24

24u1 x1

u1x1

Codec

50Hz / 60Hz 4 kHz

Smoothingfilter

Outputamplifier

Z

u1 x1

12 V

3.3 V

12 V

+12 V-12 V

+3.3 V

+12 V

-12 V

12 V

12 V

Boost

Clk

Outbuffer

RARB

TATB

Rx-AF

Tx-AF

Tx-Level

Supplymonitoring

Z

4 W

/ 2

W

Rx_

Gai

n

Tx_G

ain

X100/1

X100/2

X100/3

X100/4

X100/5

X100/6

Slot-Coding

Sync_Bus

LED'sLocal Alarm

HW Version G3LCHW Version G1LA# of G3LHAlarm on G3LHHW Version G3LA

3-Block-diagram-G3LA.vsd

Amplifierlimiter

Amplifier

Fig. 3.10 Block diagram G3LA

3.4.2.2. Short Description G3LA

The Analog Interface G3LA converts the incoming protection commands of the Relay Interfaces G3LR 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 relay interfaces. Communication between the G3LA and



the G3LR 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 NSD570’s 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. ETL500). The external signals are provided on the X100 connector (1 - 6; spring clamp 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.

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

Digital signalprocessor

SPORT1

RS

-422

Line

inte

rface

SDRAM

RTC

uC

Serial-FLASH

SPORT0

RTB

RS-232

Slot-Coding

Reset

Sync_Bus

FPG

A

16.384 MHz

DODI

CLKFS

G.7

03Li

ne in

terfa

ceRx Data -

Rx Data +

Tx Data -

Tx Data +

T+T-

S+S-

GLOS

SD

TT

RD

RTST

SD-A

SD-B

RD-A

RD-B

TT-BRT-A

RT-B

ST-A

ST-B

TT-A

G.7

03C

odire

ctio

nal

RS-

422

/ V.1

1

Con

nect

or to

pigg

y-ba

ck

Outbuffer

LED'sLocal Alarm

Outbuffer

5

Signaling toFPGA

HW Version G3LC

HW Version G1LA

# of G3LH

Alarm on G3LH

HW Version G3LD

Inbuffer

5

Signalingfrom FPGA

8

DODI

CLKFS

Data bus

Buffer8

32

Inbuffer

Watchdog33 MHz

RS-485Reset

WD

Loop Test

Flag

24

24

32

8

24

24

3-Block-diagram-G3LD.vsd

Fig. 3.11 Block diagram G3LD

3.4.3.2. Short Description G3LD

The Digital Interface G3LD converts the incoming protection commands of the Relay Interfaces G3LR 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 relay interfaces. Communication between the G3LD and the G3LR 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 NSD570’s 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) • Optical Interface G1LO (refer to Section 3.4.3.7)

3.4.3.3. External Interfaces G3LD

The G3LD comprises two interfaces:

• The TIA/EIA-422 / V.11 interface can be operated at 64 or 56 kbps. It is equipped with a male Sub-D 25-pin connector. This connector X101 is located at the rear of the G3LD and conforms to TIA/EIA-530.

• The G.703 codirectional 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)

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.

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 Sub-D connectors that comply with the standards X.21, RS-449 or again with RS-530.

The connector block for the G.703 interface is equipped with insulation displacement connectors that are terminated with a special punch-down tool.


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 one of the available interfaces (RS-530, G.703, E1, T1) can be selected and operated at the same time.

The E1/T1 interfaces can use the same external connecting cable as the G.703 interface on the G3LD.

3.4.3.7. Optical Interface G1LO

The Optical Interface G1LO 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 or with an optical 850 nm interface, depending the module version.

The optical interface permits the transmission of protection signals via fiber optical cables at a data rate of 2.048 Mbps. The G1LO can be programmed to operate with a direct fiber connection and additionally with FOX-6+, FOX-20 and the OTERM interface of the FOX515 with a wavelength of 1310 nm. The 850 nm interface can be utilized with a MUX that conforms to IEEE C37.94. The correct framing, signaling and line coding is automatically set after choosing the interface type out of the HMI570 pull down menu.

When the G1LO is plugged onto the main board, only one of the available interfaces (RS-530, G.703, Optical Direct Fiber, Optical FOX/OTERM, Optical IEEE C37.94) can be selected and operated at the same time.

The optical interfaces are equipped with modern E2000 type connectors that provide twin connections, one for the Tx and one for the Rx fiber.

When multimode fibers at 850 nm are employed, distances of up to 3 km can be achieved. When the 1310 nm wavelength is used, 25 km can be achieved with multimode fibers and 50 km with single mode fibers. With this interface the NSD570 can be utilized in a point to point application.



3.4.4. Relay Interface G3LR

3.4.4.1. Block diagram G3LR

Slot coding

4

Loop disable

SPORT0

4

LED

8

Hardware release coding

3

PROM

FPGA(Xilinx Spartan II)

X101 / 6

X101 / 5

X101 / 8

X101 / 712 V

X101 / 9

X101 / 11

X101 / 1012 V

X101 / 12

X101 / 14

X101 / 13

1B

1D

1C X101 / 2

X101 / 1

1A

2B

2D

2C X101 / 4

X101 / 3

2A

12 V

5 V

GND

Connector X100 to front plane bus

3.3 V 2.5 V

3.3 VSupervision

12 V 3.3 V

Tx Input 1

Tx Input 2

Rx Output 1

Relay 1

Relay 2

3-Block-diagram-G3LR.vsd

Rx Output 2

Fig. 3.12 Block diagram G3LR

3.4.4.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 or G3LD) and the external protection and logic circuits. Communication with the line interface takes place through the serial Real Time Bus (RT-Bus) on the busplane 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 busplane from the rear of the rack G7BI assembly. At the front of the G3LR module, the internal signals are connected to the busplane via a PCI connector. The external signals are accessible by the customer via a Phoenix connector block with spring-clamp terminals (see 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 panel and are driven by the G3LR module via the PCI connector. Green LED’s are provided for each input, output and relay contact (an “OK/Fail” LED will indicate



“Green” for “OK” condition 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.4.3. Inputs G3LR

The G3LR has two isolated command input circuits.

The input circuits can be programmed by jumpers to one of three voltage ranges for the nominal station battery voltage. Each programming group covers the lower and upper nominal battery voltage as follows:

24 VDC and 48 VDC 60 VDC and 110 VDC125 VDC and 250 VDC

The switching threshold is approximately 60% 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 VDC). 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.4.6.

3.4.4.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.4.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.4.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 VDC, 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.4.7. External Cable and Connector G3LR

Each G3LR module is furnished with a 14-pin spring clamp terminal block for external connections. The user can choose to either connect directly to this 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



consist of a 14 pin knife-disconnect terminal block plus a ground terminal, a 15 core cable with wires of 0.75 mm2 cross sectional area.

The Phoenix connectors fulfill the necessary requirements for high voltages (air and creeping distances according to IEC 60950) that can be applied to the terminals (250 VDC ± 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 VDC). The terminals accept stranded wires with a cross sectional area of up to 2.5 mm2 or solid wire with a cross sectional area of up to of 4 mm2.


3.4.5. Display Panel G1LC

3.4.5.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.

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.5.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.13 Display Panel G1LC

3.4.5.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.5.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.5.2.3. Menu navigation hints

A flashing b sign will appear to indicate that the Up or Down button may be used to scroll in this menu level. Note that the flashing b 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.5.2.4. Reset

A Display Panel reset will occur if the Back button is permanently pressed for more than 6 seconds.

3.4.5.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.5.3. Menu Structure Display Panel G1LC

3.4.5.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 | |---CONTRAST | |---Lighting | |---Standby time | |---FW/HW Version

3.4.5.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 Digital Line Interface only | |---CMD F TX/RX Digital Line Interface only | |---CMD G TX/RX Digital Line Interface only | |---CMD H TX/RX Digital Line Interface only | |---LOOP TX/RX | |---UNBLOCKING | |---ALARMS Alarm messages according device state | |---STATUS | |---INTERFACE TYPE | |---LOOP TEST STATE | |---LOOP TEST TIME | |---RX LEVEL Analog Line Interface only | |---TX LEVEL Analog Line Interface only | |---SNR Analog Line Interface only | |---BER 16 s AVERAGE Digital Line Interface only | |---BER 262 min AVG. Digital Line Interface only | |---FIRMWARE | |---DSP | |---CONTROLLER | |---CONFIGURATION | |---CONFIGURATION | |---Device Info | | |---LINE IF TYPE | | |---LINE IF POSITION | | |---SERIAL NUMBER | | |---FW DOWNLOAD COUNTER | | |---CONFIG DOWNLOAD COUNTER | |



| |---HW Version | | |---COMMON IF G3LC | | |---LINE IF G3LA Analog Line Interface only | | |---LINE IF G3LD Digital Line Interface only | | |---PIGGYBACK @ G3LD Digital Line Interface only | | |---REL. IF G3LR N34 If connected to TPE 1 the HW | | |---REL. IF G3LR N40 Information of all 8 Relay | | |---REL. IF G3LR N46 Interfaces are visible | | |---REL. IF G3LR N52 | | |---REL. IF G3LR N64 If connected to TPE 2 | | |---REL. IF G3LR N70 If connected to TPE 2 | | |---REL. IF G3LR N76 If connected to TPE 2 | | |---REL. IF G3LR N84 If connected to TPE 2 | | |---BUSPLANE G1LA | | | |---Device ID | | |---STATION NAME | | |---HE NUMBER | | |---DEVICE ADDRESS | | | |---Common Settings | | |---DEVICE MODE | | |---CMD OUT LNK FAIL | | |---EOC | | |---CYCL. LOOP TEST | | | |---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, Optical | | | Direct Fiber and Optical FOX/OTERM | | | 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 | | | |---Command Settings | | |---COMMAND A | | |---COMMAND B | | |---COMMAND C | | |---COMMAND D | | |---COMMAND E Digital Line Interface only | | |---COMMAND F Digital Line Interface only | | |---COMMAND G Digital Line Interface only | | |---COMMAND H 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 = 0n | | | |---INPUT 2 If Relay Interface 1 = 0n | | | |---OUTPUT 1 If Relay Interface 1 = 0n | | | |---OUTPUT 2 If Relay Interface 1 = 0n | | | |---RELAY OUTPUT 1 If Relay Interface 1 = 0n | | | |---RELAY OUTPUT 2 If Relay Interface 1 = 0n | | |---TPE1 INTERFACE 2 (N40) TPE2 INTERFACE 2 (N70) | | | |---INPUT 1 If Relay Interface 2 = 0n | | | |---INPUT 2 If Relay Interface 2 = 0n | | | |---OUTPUT 1 If Relay Interface 2 = 0n | | | |---OUTPUT 2 If Relay Interface 2 = 0n | | | |---RELAY OUTPUT 1 If Relay Interface 2 = 0n | | | |---RELAY OUTPUT 2 If Relay Interface 2 = 0n | | |---TPE1 INTERFACE 3 (N46) TPE2 INTERFACE 3 (N76) | | | |---INPUT 1 If Relay Interface 3 = 0n | | | |---INPUT 2 If Relay Interface 3 = 0n | | | |---OUTPUT 1 If Relay Interface 3 = 0n | | | |---OUTPUT 2 If Relay Interface 3 = 0n | | | |---RELAY OUTPUT 1 If Relay Interface 3 = 0n | | | |---RELAY OUTPUT 2 If Relay Interface 3 = 0n | | |---TPE1 INTERFACE 4 (N52) TPE2 INTERFACE 4 (N84) | | | |---INPUT 1 If Relay Interface 4 = 0n | | | |---INPUT 2 If Relay Interface 4 = 0n | | | |---OUTPUT 1 If Relay Interface 4 = 0n | | | |---OUTPUT 2 If Relay Interface 4 = 0n | | | |---RELAY OUTPUT 1 If Relay Interface 4 = 0n | | | |---RELAY OUTPUT 2 If Relay Interface 4 = 0n | |---MAINTENANCE | |---Get Time & Date | | |---TIME | | |---DATE | |---Reset TPE x x = 1 or 2 | |---RESET TPE x ? x = 1 or 2 | |---DEVICE ADDRESS

3.4.5.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 | |---CMD E TX/RX Digital Line Interface only | |---CMD F TX/RX Digital Line Interface only | |---CMD G TX/RX Digital Line Interface only | |---CMD H TX/RX Digital Line Interface only | |---LOOP TX/RX | |---UNBLOCKING | |---ALARMS Alarm messages according device state | |---STATUS | |---INTERFACE TYPE | |---LOOP TEST STATE | |---LOOP TEST TIME | |---RX LEVEL Analog Line Interface only | |---TX LEVEL Analog Line Interface only | |---SNR Analog Line Interface only | |---BER 16 s AVERAGE Digital Line Interface only | |---BER 262 min AVG. Digital Line Interface only | |---FIRMWARE | |---DSP | |---CONTROLLER | |---CONFIGURATION



3.4.5.4. Additional Features of Display Panel G1LC

3.4.5.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 Vers. 1.04 and if the firmware version of the Display Panel G1LC is greater or equal to Vers. 1.01.

For details refer to the document "Compatibility requirements NSD570" (1KHW000902-EN) in the annex of this Operating Instructions.

3.4.5.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.5.4.3. Reset counters via display panel

If the conditions described in the Section 3.4.5.4.1 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 | |---CMD E TX/RX Digital Line Interface only | |---CMD F TX/RX Digital Line Interface only | |---CMD G TX/RX Digital Line Interface only | |---CMD H TX/RX Digital Line Interface only | |---LOOP TX/RX | |---UNBLOCKING | |---CLEAR COUNTER? | | |---CLEAR ALL CTR. | | |---CLEAR CMD CTR. | | |---CLEAR LOOP CTR. | | |---CLEAR UNBL. CTR.

3.4.5.4.4. Disabling reset counters via display panel

If it shall not be allowed to reset the trip counters via the display panel, this feature can be disabled, if required.



Two PCB pads have to be interconnected by a solder bridge for that purpose (see Fig. 3.14).

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.14 Disabling reset counters

3.4.5.4.5. Automatic display of Tx or Rx commands

If a line interface G3LA or G3LD 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.6. LAN Interface G3LL

3.4.6.1. Short Description G3LL

The NSD570 LAN Interface (G3LL) 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 only (e.g. Internet Explorer, Mozilla, Netscape) is needed on the PC/notebook for using the HMI570 LAN on G3LL.

Station bus

LAN InterfaceG3LL

1 .. 3G3LR

G3LAor

G3LD

HMI570LAN

NSD570 Rack

Internet /Intranet

Ethernet10/100BaseT

Webbrowser

Substation A

G3LAor

G3LD

1 .. 4G3LR

1 .. 4G3LR

G3LAor

G3LD

NSD570 Rack

G3LAor

G3LD

1 .. 4G3LR

3-LANIFSubstation

Fig. 3.15 Connection to the NSD570 devices via G3LL



3.4.6.2. Block diagram G3LL

NSD570

Bus Plane

LAN (RJ45)X201

DC/DCPC/104

Isolationbus driver

Ok/Fail LAN

Link LAN

DC/DCRS485

5V_L

5V_485

IsolationRS485 driver

Stationbus (RS485)X500

SwitchLogic

Isolationbus driver

COM1

External connectionsat rear of equipment

10/100 BaseT

PC/104

HW_COMI

3 BlockDiagramG3LL

12V

12V

Fig. 3.16 Block diagram G3LL



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 or optical).

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.

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 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.

Frequency

Time

Guard Signal

Trip Signal

3-Analog-operating-principle.vsd

Amplitude

FrequencyTripsignal

AvailableBandwidth

Testsignal

Groupsignal

Fig. 3.17 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.

F5

Amplitude

FrequencyF1 F2 F3 F4

AvailableBandwidth Frequency

Time

Guard Signal

Trip Signal

3-Analog-operating-principle.vsd

Fig. 3.18 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 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, 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:

0 0.3 0.5 1.0 1.5 2.0 2.5 3.0 3.4

2760

960 1920 2880

960

1500 3480

1200

2400 960

960 960

2)

3)

3.96 kHz

SPEECH 2000 Hz1)

3-Example_channel_allocation.vsd

Fig. 3.19 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 the annex of this manual.

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

Amplitude

FrequencyF1 F2 F3

AvailableBandwidth

Fig. 3.20 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 Calculation 120 Hz 33.90 Hz240 Hz 65.57 Hz360 Hz 95.24 Hz480 Hz 125.00 Hz960 Hz 235.29 Hz

1200 Hz 285.71 Hz2400 Hz 500.00 Hz2800 Hz 666.67 Hz

Fc = Rx or Tx center frequency configured by HMI570

F1 = Fc – FShift

F2 = Fc F3 = Fc + FShift



3.5.4.2. 2 independent single tone commands A, B

Single tone test and guard signal

2 independent single tone commands "A", "B"

Programmable for bandwidth: 240, 360, 480, 960, 1200, 2400, 2800 Hz

Amplitude

FrequencyF1 F2 F3 F4 F5

AvailableBandwidth

Fig. 3.21 2 independent single tone commands A, B

Command assignment to frequencies: 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 Calculation 120 Hz n.a. 240 Hz 36.36 Hz360 Hz 52.63 Hz480 Hz 71.42 Hz960 Hz 142.86 Hz


F1 = Fc – 2*FShift

F2 = Fc – FShift

F3 = Fc

1200 Hz 181.82 HzF4 = Fc + FShift

2400 Hz 285.71 Hz2800 Hz 400.00 Hz

F5 = Fc + 2*FShift

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"

Programmable for bandwidth: 240, 360, 480, 960, 1200, 2400, 2800 Hz



F5

Amplitude

FrequencyF1 F2 F3 F4

AvailableBandwidth

Fig. 3.22 2 independent dual tone commands A, B

Command assignment to frequencies: 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 Calculation 120 Hz n.a. 240 Hz 31.25 Hz360 Hz 46.51 Hz480 Hz 62.50 Hz960 Hz 111.11 Hz

1200 Hz 133.33 Hz2400 Hz 250.00 Hz2800 Hz 285.71 Hz


F1 = Fc – 2*FShift

F2 = Fc – FShift

F3 = Fc F4 = Fc + FShift

F5 = Fc + 2*FShift

3.5.4.4. 3 independent dual tone commands A, B, C


3 independent dual tone commands "A", "B", "C"

Programmable for bandwidth: 360, 480, 960, 1200, 2400, 2800 Hz

F6

Amplitude

FrequencyF1 F2 F3 F4 F5

AvailableBandwidth

Fig. 3.23 3 independent dual tone commands A, B, C




Command assignment to frequencies: 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 F BShiftB Calculation 120 Hz n.a. 240 Hz n.a. 360 Hz 44.44 Hz480 Hz 58.82 Hz960 Hz 105.26 Hz

1200 Hz 125.00 Hz2400 Hz 250.00 Hz2800 Hz 285.71 Hz


F1 = Fc – 2.5*FBShift



F4 = Fc + 0.5*FBShift

F5 = Fc + 1.5*FBShift

F6 = Fc + 2.5*FBShiftB

3.5.4.5. 4 independent dual tone commands A, B, C, D


4 independent dual tone commands "A", "B", "C", "D"

Programmable for bandwidth: 480, 960, 1200, 2400, 2800 Hz

Amplitude

FrequencyF1 F2 F3 F4 F5 F6 F7 F8

AvailableBandwidth

Fig. 3.24 4 independent dual tone commands A, B, C, D



Command assignment to frequencies: 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 F BShiftB Calculation 120 Hz n.a. 240 Hz n.a. 360 Hz n.a. 480 Hz 42.55 Hz960 Hz 83.33 Hz

1200 Hz 111.11 Hz2400 Hz 222.22 Hz2800 Hz 250.00 Hz


F1 = Fc – 3.5*F BShiftB F5 = Fc + 0.5*FBShift

F2 = Fc – 2.5*F BShift BF6 = Fc + 1.5*FBShift





3.5.5. 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.5.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 bit 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.5.2. Digital frame structure

The 31 bits of the BCH (31,21,5) code are extended with 17 synchronization bits which leads to a frame length of 6 x 8 bit = 48 bit 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 bit = 49 bit.

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 number 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.5.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.

The ability to program the unit enables the best use to be made of the 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, 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.6. 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 of this manual.



3.5.7. Common Functions

3.5.7.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). 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 can transmit up to 8 commands (A - H) in any combination.

3.5.7.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.



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.7.3. Tx Trip Duration Monitoring

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

The duration of each single command injected at the relay interface (G3LR) inputs is individually 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 of the NSD570 analog is set inactive before the guard signal is transmitted again.

The maximum Tx Trip Duration can be configured in the range of 1 … 15 seconds in steps of 1 sec by means of the HMI570.

3.5.7.4. Tx input command delay

Warning: If an input command 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.

The preset input command delay can be configured for each command separately.

The Tx input command 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.7.5. Command Prolongation

A command prolongation ensures a steady output command 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).

ProlongationLocal:G3LR Input

Remote:G3LR Output

Tac

3-Command-prolongation.vsd

Fig. 3.25 Command Prolongation Time

A command prolongation can be programmed for each command separately.

The Rx command prolongation is configurable in the range of 0 … 3000 ms in steps of 1 ms by means of the HMI570.

Default settings of the prolongation for the command application are:

• Blocking 0 ms • Permissive Tripping 10 ms • Direct Tripping 100 ms

3.5.7.6. Command Acknowledge

A Tx command acknowledge is programmable for each command. The Tx command injected is then looped back from the line interface (G3LA or G3LD) 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.7.7. 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.8. Functions of the analog system

3.5.8.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) 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.8.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.8.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 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).

3.5.8.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 the NSD570 Analog is not available

during continuous command transmission! The EOC is shortly interrupted by the manual or cyclicloop test!

There is a limited functionality of the EOC when the equipment is in T-operation mode (refer to Section 3.6.7.1 and 3.6.7.2; 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 also the "Firmware download" via the EOC is working, 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 1 / 960 Hz 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 havean adequate accuracy if the EOC is switched off!

3.5.9. Functions of the digital system

3.5.9.1. Bit error rate monitoring

The BER is determined in 16 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.9.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.1 of this manual). This can also occur should addresses be corrupted by bit errors. The following

1 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.



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 to avoid unwanted interruptions of commands.

- for short time tripping commands, the outputs should be programmed to adopt their quiescent states.

The equipment ignores any incoming signal (Guard / Trip) if an address error is detected. The LEDs on the frontplate 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.

3.5.9.3. 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 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: The EOC of the NSD570 Digital is available during

continuous 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 and 3.6.7.2; 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: • activating the local and remote test mode in the remote station • switch back to previous configuration • change the micro-controller’s UART baud rate



Also the "Firmware download" via the EOC is working, 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.10. Event Recorder

3.5.10.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 and G3LD. The date and time is 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.10.5).

The events are displayed by means of the HMI570 in a text based view.

Refer to Section 4 of this manual for instructions to upload, view and save events.

3.5.10.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.



The following events are recorded as NSD570 command events:

• Start time and end time of all commands sent excluding Tx input command delay (i.e. the command was injected earlier at the input by the amount of the configured delay)

• Start time and end time of all commands received including command prolongation (i.e. the command was longer released to the output by the amount of the configured prolongation)

• Start and end time of an unblocking pulse

3.5.10.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 of this manual for details).

3.5.10.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

• Time when a loop test failed

• Time when a manual loop test was initiated (by means of the loop test button on the front panel)

• 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

3.5.10.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 of this Manual).



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. So the date and time has to be set once manually in the NSD570 to supply the system with information about the current year. See Section 4 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).

3.5.11. 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 = 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.12. Test facilities

3.5.12.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 frontpanel of the equipment or via the HMI570. The result of the test is indicated by the LEDs on the frontplate.



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 release, operating parameters and alarm signals generated by the local and remote units.

3.5.12.2. Cyclic Loop Test

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 loop test signal of the analog NSD570 is transmitted without boosting, i.e. with the nominal command tone level.

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.9.2.1); the reception of the reflected signal must take place between 1.5 x T0 and 6 x T0 after sending it), which ensures that all the functions required for transmitting a tripping signal are fully tested.

If an automatically initiated test is not received correctly it is being repeated at intervals of about 5 minutes until either the remote station answers or a continuous alarm is given after the third attempt.



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.

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 exactingconditions than those of boosted transfer trippingsignals.

3.5.12.3. Manual Loop Test

The loop test can also be initiated manually from any station via the HMI570 or via the button on the local front panel. The result of the test can be viewed in the HMI570 window. The actual measured transmission time (Tac) is displayed (half the value of both directions there and back, a delay of 1 ms is added for one input and one output circuit of a relay interface type G3LR (which can not be included in this test).

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.

3.5.12.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.

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.12.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 this operating mode, which is indicated by a flashing "Ok / Fail" LED 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.

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.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 optical 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 commu-nication 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.



AB

C

D NSD570

AB

C

D NSD570

MP1

MP2

GSD/LSBFP

MP1

MP2

GSD/LSBFP

A

B

C

DNSD570

A

B

C

DNSD570

R

Route 1 (e.g. Cable,PLC, Radio, PCM)

R


BFP: breaker failure protection + overvoltage protection + shunt reactor protection

MP1: 1st main protectionMP2: 2nd main protection LS: load shedding

R: protection relay

3-Single-line2.vsd

GSD: generator shut down

Fig. 3.26 Duplicated line protection and breaker-failure

protection of an important single circuit

R1/R2: protection relay

AB

C

D NSD570

AB

C

D NSD570

MP1 Line 1

MP2 Line 2

BFP Line 2BFP Line 1

A

B

C

DNSD570

A

B

C

DNSD570

MP1 Line 2 MP2 Line 1

MP1 Line 1MP2 Line 2

BFP Line 1BFP Line 2

MP1 Line 2 MP2 Line 1

R1 R2R1R2



BFP: breaker failure protection + overvoltage protection + shunt reactor protection

MP1: 1st main protectionMP2: 2nd main protection

3-Dual-line2.vsd

Fig. 3.27 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 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).

TX

RX

TX

RX

TX RX TXRX

TX

RX

TX RX

TX

RX

A

T

B

TPE 1 TPE 2

3-T-operation.vsd

Fig. 3.28 T-operation principle



3.6.7.1. NSD570 Analog/Digital 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, 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 a 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 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.

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.

Transmitter and receivers of the analog version must use the same bandwidth and center frequencies in "normal" T-operation, while end-to-end operation allows a different transmit and receive channel bandwidth.

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.

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, no restoring is needed in case of one link fails. The "healthy" link automatically remains active.

Please refer to Section 5 "Configuration and settings" of this manual for details about configuring command application and T-operation mode.

3.6.7.2. NSD570 Analog/Digital 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 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.

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.

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.

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 analog version and only if the guard signal is transmitted - between the outer stations A and B (when a command is injected at the T station). In a digital scheme the EOC always operates between A and T respectively B and T, independent of the command state in T.

Please refer to Section 5 "Configuration and settings" of this manual for details about configuring command application and "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), 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.




TX

RX

TX

RX

TX RX TXRX

TX

RX

TX RX

TX

RX

A

T

B

TPE 1 TPE 2

Local address: 15Remote address: 23




3-Normal-T-operation-with-digital-addresses.vsd

Fig. 3.29 Addressing example for normal T-operation

In inverse T-operation (Section 3.6.7.2), 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.

TX

RX

TX

RX

TX RX TXRX

TX

RX

TX

RX

TX RX

A

T

B

TPE 1 TPE 2





3-Inverse-T-operation-with-digital-addresses.vsd

Fig. 3.30 Addressing example for inverse T-operation


3.6.7.4. Tapped lines

(See also Direct Transfer Tripping, Section 3.6.6; Transformer Protection, Section 3.6.6.5)

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) 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.

Please refer to Section 5 "Configuration and settings" of this manual for details about configuring command application and "normal" T-operation mode.



3.6.8. Phase-Segregated Command Transmission

3.6.8.1. Twin Line - Two Systems on Common Towers

3-Twin-line.vsd

E

T1 T2

S1 S2

R1 R2

Fig. 1

E

T1 R2

S1 S2

R1 T2

Fig. 2

Fig. 3.31 Twin Line - Two Systems on Common Towers

The conductor arrangement in Fig. 2 is often preferred, because it provides a better balance of the line capacitances to earth than the arrangement shown in Fig1.

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. 2, 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 informations 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 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.



April 2004


4.1. Introduction .............................................................................. 4-3

4.2. Safety instruction ..................................................................... 4-4

4.3. System requirements and technical data for the HMI570 ........ 4-4

4.4. Installation of the HMI570 ........................................................ 4-4

4.5. Communication between the HMI570 PC and the NSD570..... 4-5 4.5.1. Local connection...................................................................... 4-5 4.5.2. Remote connection over (EOC)............................................... 4-6

4.6. Communication between the HMI570 LAN and the NSD570...4-6 4.6.1. Remote connection over LAN / WAN / Internet........................ 4-6 4.6.2. Security considerations for connections over Internet.............. 4-7

4.7. Multiple connection .................................................................. 4-8

4.8. Browser front end .................................................................... 4-9 4.8.1. Browser Settings...................................................................... 4-9 4.8.1.1. Internet Explorer 5.x............................................................... 4-10 4.8.1.2. Internet Explorer 6 ................................................................. 4-10 4.8.1.3. Mozilla 1.x, Netscape 6.x / 7.x ............................................... 4-11 4.8.1.4. Additional browser settings for the HMI570 LAN ................... 4-12

4.9. Starting the program .............................................................. 4-13 4.9.1. HMI570 PC ............................................................................ 4-13 4.9.2. HMI570 LAN .......................................................................... 4-13

4.10. Operation ............................................................................... 4-14 4.10.1. Introduction ............................................................................ 4-14 4.10.2. Basic operation principles ...................................................... 4-14 4.10.3. Design.................................................................................... 4-14 4.10.4. Login / Logoff ......................................................................... 4-15 4.10.5. User Administration and Permissions .................................... 4-15 4.10.6. Change password.................................................................. 4-17 4.10.7. Connect / Disconnect Device................................................. 4-17 4.10.7.1. Connect Device ..................................................................... 4-18 4.10.7.2. Error messages and troubleshooting ..................................... 4-19 4.10.7.3. Disconnect Device ................................................................. 4-20 4.10.8. Configuration ......................................................................... 4-21 4.10.8.1. Load From Disk ..................................................................... 4-21 4.10.8.2. View Configuration................................................................. 4-21 4.10.8.3. Edit Configuration .................................................................. 4-21 4.10.8.4. Save To Disk ......................................................................... 4-24

User interface program April 2004 4-1


4.10.8.5. Discard Configuration ............................................................ 4-24 4.10.8.6. Download To Device.............................................................. 4-24 4.10.8.7. Upload From Device .............................................................. 4-24 4.10.9. Event Recorder......................................................................4-25 4.10.9.1. Load From Disk ..................................................................... 4-25 4.10.9.2. View Events ........................................................................... 4-25 4.10.9.3. Save To Disk ......................................................................... 4-25 4.10.9.4. Upload Events ....................................................................... 4-25 4.10.9.5. Clear Event Recorder ............................................................ 4-25 4.10.9.6. Import events into a spreadsheet or word processing tool..... 4-26 4.10.10. Status / Alarm ........................................................................ 4-26 4.10.10.1. Upload Status ........................................................................ 4-26 4.10.10.2. Upload Alarm ......................................................................... 4-27 4.10.10.3. Trip Counter........................................................................... 4-27 4.10.11. Maintenance .......................................................................... 4-27 4.10.11.1. Manual Loop Test .................................................................. 4-27 4.10.11.2. Reset Device ......................................................................... 4-28 4.10.11.3. Previous Configuration........................................................... 4-28 4.10.11.4. Set Time and Date................................................................. 4-28 4.10.11.5. Get Time and Date................................................................. 4-28 4.10.11.6. Device Communication .......................................................... 4-29 4.10.11.7. Firmware Download...............................................................4-29 4.10.12. Commissioning ...................................................................... 4-30 4.10.13. Alarm Polling.......................................................................... 4-30 4.10.13.1. Impact when the Alarm Polling is started ............................... 4-32 4.10.13.2. Start Alarm Polling ................................................................. 4-33 4.10.13.3. Stop Alarm Polling ................................................................. 4-33 4.10.13.4. Configure Alarm Polling ......................................................... 4-33 4.10.13.5. Graphical View....................................................................... 4-34 4.10.13.6. View Entire Logfile ................................................................. 4-35 4.10.13.7. View Latest 50 Entries ........................................................... 4-35 4.10.13.8. Clear Entire Logfile ................................................................ 4-35 4.10.13.9. Refresh Page.........................................................................4-35 4.10.13.10. Stop Refreshing .....................................................................4-35 4.10.13.11. Start Auto Pop-Up.................................................................. 4-35 4.10.13.12. Stop Auto Pop-Up.................................................................. 4-35 4.10.13.13. Multiple users......................................................................... 4-36 4.10.14. HMI570 Options.....................................................................4-36 4.10.14.1. Device Communication .......................................................... 4-36 4.10.14.2. LAN Interface......................................................................... 4-36 4.10.14.3. About .....................................................................................4-37 4.10.14.4. Exit HMI570 ...........................................................................4-37

4-2 April 2004 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 allows no connection over LAN/WAN but no LAN interface G3LL is needed.

• The “HMI570 LAN” needs a NSD570 LAN Interface (G3LL) in the NSD570 rack. It allows connecting an NSD570 device remotely over LAN/WAN.

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.



4.2. Safety instruction



Note: It is recommended to disconnect the PC / notebook

from the LAN while running the HMI570 andconnecting a device via the RS-232 interface.

4.3. System requirements and technical data for the HMI570

Please refer to 1KHW000894 Software Installation Description HMI570.

4.4. Installation of the 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 panel, 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.

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

4-Local-connection.vsd

RS232

TPE 1100

TPE 2101

NSD570 A1

HMI570

Substation A

TPE 1120

TPE 2121

NSD570

Station bus

NSD570 A2

Deviceaddress

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, 120 and 121 can be connected via a local connection.

Note: Every NSD570 line interface within a substation must

have a unique device address.



4.5.2. Remote connection over (EOC)

RS232

HMI570

TPE 1220

TPE 2221

Substation B

NSD570 B1

Embedded operation channel (EOC)

TPE 1100

TPE 2101

NSD570 A1

Substation A

TPE 1120

TPE 2121

NSD570

Station bus

NSD570 A2

Deviceaddress

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. Communication between the HMI570 LAN and the NSD570

4.6.1. Remote connection over LAN / WAN / Internet

LAN / WANInternet

TPE1100

TPE2101

NSD570 A1

Substation AStation bus

Deviceaddress

LANInterface

TPE1120

TPE2121

NSD570 A2

HMI570

TPE1100

TPE2120

NSD570 F1

Substation F

LANInterface

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 HMI570 LAN via the LAN Interface in the NSD570 A1 rack. The devices with address 100, 120 in Substation B can be connected from the HMI570 LAN via the LAN



Interface 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).

Caution Encrypted SSL connections are strongly recommended for communication channels that are not secure (e.g. Internet).

Additionally, remote connection over Internet requires appropriate security measures (see Section 4.6.2).

Never connect a NSD570 LAN Interface directly to the Internet!

Note: This connection over LAN / WAN / Internet needs a

LAN Interface G3LL plugged in the NSD570 module rack and connected to the corresponding communi-cation media.

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.



4.7. Multiple connection

LAN / WANInternet

TPE1100

TPE2101

NSD570 A1


Deviceaddress

LANInterface

TPE1120

TPE2121

NSD570 A2

4-Multiple-connection.vsd

RS232

HMI570

HMI570

Fig. 4.4 Multiple connection from local and remote

Note: Do not connect a device simultaneously from local

and from remote site.

RS232

HMI570

TPE 1100

TPE 2101

NSD570 A1

Substation A

TPE 1120

TPE 2121

NSD570

Station bus

NSD570 A2RS232

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 areinterconnected 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. Several web browsers supporting HTTP/1.1 and HTML 4 can be used as HMI570 front end. Subsequently listed are the web browsers that are recommended to use:

• Microsoft® Internet Explorer 5.x

• Microsoft® Internet Explorer 6.0

• Mozilla 1.2 or higher (http://www.mozilla.org)

• Netscape 7.0 or higher (http://www.netscape.org)

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

• File download must be enabled

• The HMI570 pages must not be cached

• Bypass proxy server for local address and for the IP addresses that are used for the HMI570 LAN Interface

• JavaScript must be enabled

Detailed instructions will follow how you can set this for the most common browsers.


http://www.mozilla.org/

http://www.netscape.org/


4.8.1.1. Internet Explorer 5.x

• Enable Cookies

Menu bar at the top Tools Internet Options Security choose local intranet press button Custom Level… Cookies: Enable all cookies settings

• Enable File Download

Menu bar at the top Tools Internet Options Security press button Custom Level… Downloads File Download: Enable

• Avoid caching of HMI570 Pages

Menu bar at the top Tools Internet Options General press button Settings… (under Temporary Internet Files) Check for newer versions of stored pages: Select: Automatically

• Bypass proxy server for local address

Menu bar at the top Tools Internet Options Connection press button LAN Settings… If the checkbox Use a proxy server is activated, also activate the checkbox Bypass proxy server for local address

• Enable JavaScript

Menu bar at the top Tools Internet Options Security choose local intranet press button Custom Level… Active Scripting: enable

4.8.1.2. Internet Explorer 6

• Enable Cookies

Menu bar at the top Tools Internet Option Privacy Move the Slider to the bottom (Accept all cookies)

The META refresh tag must also be enabled:

Menu bar at the top Tools Internet Option Security Enable Allow META REFRESH

• Enable File Download

Menu bar at the top Tools Internet Options Security press button Custom Level… Downloads File Download: Enable




Menu bar at the top Tools Internet Option General press button Settings… (under Temporary Internet Files) Check for newer versions of stored pages: Select: Automatically


Menu bar at the top Tools Internet Option Connection press button LAN Settings… If the checkbox Use a proxy server for your LAN is activated, also activate the checkbox Bypass proxy server for local address


Menu bar at the top Tools Internet Options Security choose local intranet press button Custom Level… Active Scripting: enable

4.8.1.3. Mozilla 1.x, Netscape 6.x / 7.x

• Enable Cookies

Menu bar at the top Edit Preferences Privacy & Security Cookies Select: Enable all cookies


Menu bar at the top Edit Preferences Advanced Cache Select: Every time I view the page or when the page is out of

date


Menu bar at the top Edit Preferences Advanced Proxies If the checkbox Manual proxy configuration is activated, type localhost in the field No Proxy for


Menu bar at the top Edit Preferences Advanced Scripts & Windows Enable Script for Navigator



4.8.1.4. Additional browser settings for the HMI570 LAN

There are additional browser settings to observe when using the HMI570 LAN

• Bypass proxy server for the IP addresses that are used for HMI570 LAN Interfaces

Internet Explorer 5.x and 6

• Bypass proxy server for the IP addresses that are used for HMI570 LAN Interfaces Menu bar at the top Tools Internet Option Connection press button LAN Settings… If the checkbox “Use a proxy server for your LAN” is activated, press the button “Advanced…”. The window “Proxy Settings” opens. Enter the proxy IP address and port in the upper part of the window (inside the frame “Servers”). In lower part (inside the frame “Exceptions”) enter the IP addresses that are used for HMI570 LAN Interfaces.

Mozilla 1.x, Netscape 6.x / 7.x

• Bypass proxy server for the IP addresses that are used for HMI570 LAN Interfaces

Menu bar at the top Edit Preferences Advanced Proxies If the checkbox Manual proxy configuration is activated, enter the IP addresses that are used for HMI570 LAN Interfaces in the field “No Proxy for”.



4.9. Starting the program

4.9.1. HMI570 PC

On the taskbar Start Programs HMI570-Shortcut Folder start HMI570 starts the HMI570. The server will be started and also a browser (Internet Explorer).

If you would like to use another browser than Internet Explorer or the Internet Explorer does not start properly, restart the browser and type in the URL:

http://localhost:10570/hmi570/index.jsp

Note: It is not possible to run more than one HMI570

application parallel on the same PC / notebook.

Nevertheless it would be possible to open anotherbrowser window, type in the above URL and connecta different NSD570 (for the time being this is applicable and verified for Internet Explorer only).

4.9.2. HMI570 LAN

Start a web browser (Internet Explorer, Mozilla, Netscape) and type in the following URL:

http://<IP_LAN_Interface>/hmi570/index.jsp

To access the LAN Interface over an encrypted SSL connection, use the subsequent URL:

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. http://172.20.162.54/hmi570/index.jsp).

Note: The usage of an SSL connection requires a NSD570

LAN interface that is SSL enabled.

Encrypted SSL connections are stronglyrecommended for communication channels that arenot 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 chapter 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 progress 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 used (analog or digital).



4.10.4. Login / Logoff

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. To confirm, click on the "Log In" button or press "Enter".

Note: Username and password are case sensitive.

There are three predefined users:

User: Password: Permissions:

Administrator welcome admin, modify, view

Service welcome view, modify

Operator welcome view

Note: For security reasons the passwords should be

changed immediately after the installation of the HMI570.

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 4.10.5. 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.5. 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 and click on the "Add new user" button. Set the permissions of the new user and press the "Change" button to confirm. To add a password, choose "Edit user" for the wanted user, type in the new password and confirm with "Set".



Delete User

Click on "Edit user" button of the user to be deleted. Press "Delete User" to delete the user or "Cancel" to skip.

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 Permission

Modify 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 device

X X

Upload configuration and event recorder from device

X X

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 communication

X

Clear event recorder of device X

Download configuration to device X

Execute commissioning functions 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.

The permissions are also displayed in the green Status Box, when a user is logged in.

4.10.6. 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 User Administration.

The logged in user is prompted to type in a new password. The "update" button sets the new password.

4.10.7. 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 local NSD570. The logical connection is made to the remote peer device of the link.

Note: This remote connection is only possible if both

devices (the local and the remote) have the EOCswitched on.

Note: A remote connection over EOC has the drawback of a

slow communication between the HMI570 and theremote device. The respond time of the HMI570 may increase drastically (especially with an analog link). Please be patient and do not press any button fromthe toolbars of the browser.



4.10.7.1. Connect Device

To connect a device, click on Connect Device and then type in the device address. Choose between „local“ or „remote over EOC“.

Please note: to connect remotely, type the address of the local device and check the „remote over EOC“ box.

If the device address 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.

To connect a device with the default address, the two buttons “TPE 1” and “TPE 2” below “Connect with Local Default Address” can be used.

Note: If a device shall be connected with the default

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

The device address range is 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.05 Controller firmware version 1.03 Configuration version 1.00

The green Status Box displays the name and address of the connected device and what kind of interface is in use (digital, analog).

A boot failure of the device is indicated by the red “Fail” LED on the frontplate 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 one line interface in the rack first, before connecting with 255 to the other line interface. After a successful connection to the device with address 255, execute a firmware download, see Section 4.10.11.7. Firmware Download.



4.10.7.2. 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” is not possible

(remote connection over LAN / WAN / Internet). See Section 4.10.14.2 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

2. The device address is wrong 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” is not possible (remote connection over LAN / WAN / Internet). See Section 4.10.14.2 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

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 Login / Logoff). 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.10.13 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.4 Additional browser settings for the HMI570 LAN.

4.10.7.3. 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.8. Configuration

4.10.8.1. Load From Disk

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

Load Default Configuration

Loading a default configuration is a good start for the configuration of a NSD570 device. There are four default configurations:

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 plugged at the left side of the rack (slot N28)

Default_TPE2_Digital.xml Digital Line Interface TPE 2 plugged at the right side of the rack (slot N58)

Click on the according „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.8.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.

4.10.8.3. Edit 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 to a connected device.

Device Information Contains the type of the interface (analog, digital), 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. The power supply units have no version coding.

Firmware Versions Displays the firmware version of the Micro Controller and the Digital Signal Processor (DSP).

Device Identification Contains the version of the configuration, the configuration type (analog, digital), the name of the station, the HE number and the device address.

Common Settings In this menu item the 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 GPS Synchronization can be configured.

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, Un-blocking 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. G703 64kbps codirectional 2. RS-530 3. E1 2048kbps 4. T1 1544kbps 5. Optical Direct Fiber 6. Optical FOX/OTERM 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).

Command Settings

Contains the settings for every command. If the application is set to off, the corresponding command cannot be used. If Tx Trip Duration Monitoring is enabled, the Max. Tx Trip Duration can be given in seconds. Tx Input Delay and Rx Prolongation is given in milliseconds.

Relay Interface

Displays the settings for the relay interfaces. If the interfaces are used, commands can individually be mapped to the inputs and outputs of the relay interfaces.

Alarm Settings

The Pickup Time and Hold Time can be set. User Alarms 1...3 can be configured to combine some different alarms into a user alarm.

Jumper Settings

Displays the jumper settings for the Relay Interfaces and the Analog Interface.

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.



4.10.8.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.8.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 or load one from the local disk.

4.10.8.6. Download To Device

Downloads the configuration to the device. It is recommended to save a configuration to disk (see Section 4.10.8.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.8.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.7.1. Connect Device) or the previously used configuration has not been discarded inside the HMI570 (see Section 4.10.8.5. Discard Configuration).



4.10.9. 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.11.5. Get Time and Date.

The event recorder can store approximately 7500 event entries. If this is exceeded, the oldest events will be overwritten.

4.10.9.1. Load From Disk

Loads events from the local disk. Click on the „Browse…“ button to choose the file and press the „load“ button.

4.10.9.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.

4.10.9.3. Save To Disk

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.9.4. Upload Events

If Upload Events is not accessible, maybe no device is connected (Section 4.10.7.1 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.9.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 themafterwards.



4.10.9.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.10. Status / Alarm

If Status / Alarm menu is not accessible, maybe no device is connected (see Section 4.10.7.1 Connect Device).

4.10.10.1. Upload Status

Uploads the status information from the connected device. If the Status Upload was successful, the following information is displayed:

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.

Cyclic Redundancy Check (CRC)

The results of the CRC memory checks are shown.

The information about the Loop Test and CRC are shown on both analog and digital interface.

Signal to Noise Ratio (SNR) (NSD570 Analog Interface only)

The Signal to Noise Ratio (SNR) in 4 kHz noise bandwidth is displayed for an NSD570 Analog device.

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!



Bit Error Rate (BER) (NSD570 Digital Interface only)

The Bit Error Rate (BER) is displayed as 16 sec. average and 262 minutes average.

4.10.10.2. Upload Alarm

Alarms are indicated by the red LED on the front panel 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.

4.10.10.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.11. Maintenance

If Maintenance is not accessible, maybe no device is connected (see Section 4.10.7.1 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.11.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.10.1. Upload Status). A loop test can also be started by pushing the "Loop Test" button on the frontside of the NSD570.



4.10.11.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!

Caution During routine tests with the NSD570 in operation 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. During this time no commands can be transmitted.

4.10.11.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.11.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.10.14.2 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.11.5. Get Time and Date

Shows the current time and date of the connected device. To adjust time and date, see Section 4.10.11.4. Set Time and Date.



4.10.11.6. Device Communication

The baud rate of the RS-232 connection to the connected NSD570 is changeable. There are three possible values: 57600, 19200 and 9600.

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 Device Communication. Click on update to accept or cancel to skip.

Note: 57600 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.11.7. 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. 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.12. Commissioning

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.12.4. and 3.5.12.5.


4.10.13. Alarm Polling

Caution The Alarm Polling functionality is only possible with a LAN Interface G3LL plugged into the NSD570 module rack and a connection to G3LL over LAN / WAN / Internet.

The Alarm Polling functionality of the HMI570 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.10.13.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.10.13.13 Multiple users).

LAN / WANTPE1100

TPE2101

NSD570 A1


Deviceaddress

LANInterface

HMI570LAN

4-Alarm Polling.vsd

TPE1110

TPE2111

TPE1120

TPE2121

NSD570 A3

NSD570 A2

Fig. 4.6 Alarm polling in an NSD570 network

In the above example, the LAN Interface in the rack NSD570 A1 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).

The result of every Alarm Polling cycle is displayed in the “HMI570 LAN” by the browser running on the PC/Notebook.



4.10.13.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 Only possible when Alarm Polling is stopped.

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

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.10.13.2. Start Alarm Polling

Starts the Alarm Polling for all users and shows the graphical view of the devices (see Section 4.10.13.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.10.13.3. Stop Alarm Polling

The Alarm Polling stops for all users.

4.10.13.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 Device Button.

Note: The device address must be in the range of

1 … 239.

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 button next to the device and make your changes. Click on the Change button.

Deleting devices from the Device List: Click on the Edit button next to the device. Click on the Delete 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.

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 marked, the graphical view pops up every time an error 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.10.13.12 Stop Auto Pop-Up).

Logfile: The size is the maximum size of the logfile. If the logfile exceeds this size, the oldest entry is deleted. When the new size is smaller than the old one, the file is shortened.

To save the changes made to the parameters click on the update button.

Exit configuration: Exits the configuration and shows the entry screen of the Alarm Polling.

4.10.13.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 the remote

device when it is not possible to upload its alarms.



4.10.13.6. View Entire Logfile

Shows the entire logfile on screen. When the Alarm Polling is started, the page refreshes itself every 60 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.10.13.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.10.13.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.10.13.9. Refresh Page

Refreshes the logfile views.

4.10.13.10. Stop Refreshing

The logfiles stop updating its views. The logfile is still being written.

4.10.13.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.

Note: The Auto Pop-Up functionality does only work with

Microsoft® Internet Explorer

4.10.13.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.10.13.13. Multiple users

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.10.14. HMI570 Options

4.10.14.1. Device Communication

These settings refer to the RS-232 connection.

Set the COM Port number for your serial connection to the NSD570, the baud rate or 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.10.14.2. LAN Interface

Note: This menu is only available with the HMI570 LAN and

contains LAN Interface specific options.

The date and time of the LAN Interface is displayed here. This time must be correct to set the date and time of a connected NSD570 Device (see 4.10.11.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 acommunication error.

4.10.14.3. About

This menu shows information about the version of the HMI570. There are also address, phone number, fax number and the email address for contact displayed. A link allows visiting the ABB Utility Communications website.

4.10.14.4. Exit HMI570

Click on the Exit button to end and exit the application.

The HMI570 PC will shutdown the server and closes the browser window. If the browser shows a dialog “Do you want to close this window?” click the “Yes” button.

The HMI570 LAN shows the dialog “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.



April 2004


5.1. Introduction .............................................................................. 5-3

5.2. Configuration ........................................................................... 5-4

5.3. Use of HMI570 files.................................................................. 5-4

5.4. Configuration with HMI570....................................................... 5-5 5.4.1. Configure device type .............................................................. 5-5 5.4.2. Configure device parameters................................................... 5-5

5.5. General configuration notes..................................................... 5-6 5.5.1. Status of the command outputs during a link failure ................ 5-6

5.6. Configuration notes for the 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-12 5.6.5. Receive level for NSD570 Analog.......................................... 5-13 5.6.6. NSD570 Analog over PLC equipment ETL500 ...................... 5-14

5.7. Configuration notes for the digital 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-18 5.7.3.1. Transmit and receive timing provided by the DCE................. 5-18 5.7.3.2. Transmit timing provided by the DCE .................................... 5-18 5.7.3.3. Transmit timing for the DCE provided by the G3LD............... 5-19 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 FOX/OTERM Interface........ 5-22 5.7.5.2. Optical IEEE C37.94 Interface ............................................... 5-23

5.8. Configuration examples ......................................................... 5-24 5.8.1. Example of NSD570 Analog configuration............................. 5-24 5.8.2. Example of NSD570 Digital configuration .............................. 5-29

Configuration and settings April 2004 5-1


5.9. Performance Criteria.............................................................. 5-34 5.9.1. General .................................................................................. 5-34 5.9.2. Transmission time.................................................................. 5-35 5.9.2.1. Nominal transmission time..................................................... 5-36 5.9.2.2. Maximum Actual Transmission Time ..................................... 5-36 5.9.3. Security.................................................................................. 5-37 5.9.4. Security Measurements ......................................................... 5-37 5.9.5. Dependability ......................................................................... 5-38 5.9.6. Dependability Measurements ................................................ 5-38

5-2 April 2004 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.

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 (includingthe 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".



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

• security and dependability

For the protection the main parameters of consequence are:

• transmission time • command prolongation (= trip extension) • status of the command outputs in the event of an alarm • arranging the command inputs to suit the battery voltage

The corresponding programming instructions can be found in the document "Programming and Testing Instructions NSD570" (1KHW000898-EN) which is available in the annex of this manual.

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.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.

5.4.1. Configure device type

A maximum of two devices have to be configured in the same rack (TPE 1 and TPE 2). They may be either NSD570 Analog or NSD570 Digital version. "Analog" and "Digital" represent the type of the line interface in use (Analog Interface G3LA or Digital Interface G3LD).

There are four default configuration files available for each of these possible device types (TPE 1 Analog, TPE 1 Digital, TPE 2 Analog, TPE 2 Digital). 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.

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. Status of the command outputs during a link failure

The response of the command outputs to a level or signal-to-noise ratio alarm in the analog version or to a loss of Rx synchronization, the detection of LOS/AIS, an excessive bit error rate or an address error in the digital version can be set by means of the HMI570. The following settings are possible:

a) do not change 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) guard state The command outputs are set to their quiescent states (= no tripping signal).

c) retain in state The command outputs retain the statuses they had immediately prior to the alarm detection.

d) set permissive and blocking 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 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. > 1second) to ensure a steady output signal.



5.6. Configuration notes for the 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 • the 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 annex of this manual). 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.19 in Section 3.5.3.3). 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.

The instructions in Section 5.6.3 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

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 Ban

dwid

th D

evic

e 2

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

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

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 the 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

A 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.) 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 Rx-level must be set 6dB 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 the annex of this manual).

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 measurement do only have an adequate accuracy if the EOC is switched off!

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.

The following table shows the maximum Rx line level against the Rx Level setting:

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

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

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

The NSD570 boost control output must be connected to the external boost input of the ETL500 on the O4LE board. The voltage supply for the signal is provided by ETL500/O4LE.

Note: When using the NSD570 via PLC equipment type

ETL500, boosting should be disabled on the NSD570, but enabled on the PLC equipment (since the powerboost ratio depends on which facilities are using the PLC channel).

The single channel ETL500 allows boosting of at most one external teleprotection equipment. The ETL500 sets the boost ratio for the NSD570 signal as high as possible, but not higher than 8 dB.

The dual channel ETL500 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.

If the ETL500 is operated with the internal teleprotection equipment NSD550, boosting of NSD550 has priority over boosting of NSD570.

If two or more NSD570 need to be operated over one channel of ETL500, the NSD570 4-wire ports have to be connected in parallel to port AF4 on the O4LE board of ETL500. 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 ETL500 at O4LE port AF4 must be set to:

- 10 dBm in case of a single NSD570, - 4 dBm in case of two NSD570 connected in parallel,

- 0.5 dBm in case of three NSD570 connected in parallel.



The O4LE output port AF4 of ETL500 will usually carry more signals than just the NSD570 signals due to other services such as speech and data transmitted by the ETL500. 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 ETL500 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 ETL500 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 NSD570Analog is then 1200 Hz (for that purpose speech must be limited to 2400 Hz, to 2200 Hz or to 2000 Hz if an NSD550 with ETL-pilot as guard signal is used, or to 2000 Hz if an NSD550 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 ETL500 built in equalizer. The additional delay caused by the equalization filter has to be taken into account.



5.7. Configuration notes for the digital 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 codirectional 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 codirectional 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.

5-G703-Appl-notes.vsd

G.703 Interface on G3LD

Receiver

Transmitter

comb. data / clock signal Tx

comb. data / clock signal Rx

PCM Multiplexer

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 operated in apoint-to-point configuration, only one of them must be configured for synchronizing the transmitter clock onthe received clock/data signal. With this setting a clock loop can be avoided.

Note: Normally the data circuit-terminating equipment

(DCE) with a G.703 codirectional 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 not work inthis case. Please contact your local representative in order to get some workaround information.



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).

SD (Send Data)

RD (Receive Data)

ST (Send Timing)

RT (Receive Timing)Data Circuit-TerminatingEquipment (DCE)RS-530 Interface G3LD

Transmitter

Receiver

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"

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). Provision is also made for synchronizing the sampling of the incoming data to the transmit timing signal (ST). This requires that the ST signal is connected externally in parallel also to the RT input and the interface must be configured accordingly.



SD (Send Data)

RD (Receive Data)

ST (Send Timing)

Data Circuit-TerminatingEquipment (DCE)RS-530 Interface on G3LD

Transmitter

Receiver

5-RS530-Appl_notes.vsd

Fig. 5.3 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" RS530 Terminal Timing TT set to "off"

5.7.3.3. Transmit timing for the DCE provided by the G3LD In this operating mode, the 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.


SD (Send Data)

RD (Receive Data)

TT (Terminal Timing)


Transmitter

Receiver

Fig. 5.4 RS-530 interface application with TT for DCE by G3LD


RS530 Rx Clock set to "internal" RS530 Tx Clock set to "internal" RS530 Rx Clock Sync set to "RD" 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.


RD (Receive Data)

SD (Send Data)


Transmitter

Receiver

Fig. 5.5 RS-530 interface application with Tx/Rx timing internally


RS530 Rx Clock set to "internal" RS530 Tx Clock set to "internal" RS530 Rx Clock Sync set to "RD" RS530 Tx Clock Sync TT set to "RD" or "none" RS530 Terminal Timing TT set to "off"

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 ClockSync and Tx Clock Sync TT are both "none") and theother as "Slave" (the send data are synchronized on thetiming 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 loopcan be avoided. For the "Master" station, alternatively the terminal timing(TT) signal provided by the remote station can be usedas an external clock reference (wired on the ST inputs).



5.7.4. E1/T1 Interface application notes

The E1/T1 interface allows to interconnect 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.

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.



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.

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.


The T1 coding (B8ZS or AMI) and frame format (4 frames or extended superframe) can be configured to comply with different communication system interfaces.

5.7.5. Optical interface application notes

The optical interface permits the transmission of protection signals via fiber optical cables at a data rate of 2.048 Mbps. The optical interface OTERM/P2P can be programmed to operate with a direct fiber connection and additionally with FOX-6+, FOX-20 and the OTERM interface of the FOX515. The optical interface IEEE C37.94 can be utilized with a multiplexer that complies with this standard for optical fiber interfaces between teleprotection and multiplexer equipment.

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 FOX/OTERM Interface

This optical interface allows interconnecting NSD570 with a FOX515 multiplexer, using the optical 2 Mbps access card OTERM.

Further a point-to-point link with a distance of up to 50 km can be realized connecting two optical interfaces directly.

For data transmission NSD570 utilizes a bit orientated FOX-6Plus frame with MCMI coding where 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.

The optical interface recovers the clock for transmission from the received signal, assuming the connected FOX515 multiplexer is the clock master.

A communication link over a FOX515 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 on the other side.

There is no other manual configuration needed.

5.7.5.2. Optical IEEE C37.94 Interface

This optical interface allows interconnecting NSD570 with a dedicated multiplexer interface according to IEEE C37.94.

For data transmission 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 output power is < -11 dBm and not selectable.

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.



5.8. Configuration examples

5.8.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) Version 0 Version 0








Relay Interface 4 TPE 2 LAN Interface

(N84) Version 0 Version 0

Bus Plane Version 0

Firmware Versions

Microcontroller 0.00

Digital Signal Processor 0.00



Device Identification

Configuration Version 1.00

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

Command Outputs During Link Failure do not change

Link Failure Pickup Time [s] 10

Link Failure Hold Time [s] 0

GPS Sync off

Embedded Operation Channel ( EOC ) on

Cyclic Loop Test Interval 6 h

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

Command Application Tx Trip Duration Monitoring

Max Tx Trip Duration [s]

Tx Input Delay [ms]

Rx Prolon-gation [ms]

A permissive off 5 0 10

B permissive off 5 0 10

C off off 5 0 0

D off off 5 0 0

Relay Interfaces

TPE 1 Interface 1 (N34)

Interface 2 (N40)

Interface 3 (N46)

Interface 4 (N52)

Used on off off off

Input 1 Command A Command C Command A Command A

Input 2 Command B Command D Command B Command B

Output 1 Command A Command C Command A Command A

Output 2 Command B Command D Command B Command B

Relay Output 1 not used not used not used not used



Interface 2 (N70)

Interface 3 (N76)

Interface 4 (N84)

Used off off off off

Input 1 Command A Command A Command A Command A

Input 2 Command B Command B Command B Command B

Output 1 Command A Command A Command A Command A

Output 2 Command B Command B Command B Command B





Alarm Settings

Pickup Time [s] 15

Hold Time [s] 15

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 .. 250VDC 125 .. 250V DC

Relay Interface 2 (N40) not assembled not assembled








Rack Assembly

Slot Module Piggyback

Power Supply Unit 1 (N01) G3LH

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


(N84) not assembled not assembled



5.8.2. Example of NSD570 Digital configuration

(File name: Default_TPE1_Digital.xml)

Device Information

Line Interface Type digital

Line Interface Position 1

Serial Number

Firmware Download Counter 0

Configuration Download Counter 0

Hardware Versions

Interface Slot Module Piggyback



Common Interface (N22) Version 0











(N84) Version 0 Version 0

Bus Plane Version 0

Firmware Versions

Microcontroller 0.00

Digital Signal Processor 0.00



Device Identification

Configuration Version 1.00

Configuration Type digital

Station Name default config TPE 1

HE Number HE xxxxxx

Device Address 200

Common Settings

Device Mode Normal

Unblocking Extra Delay [ms] 5

Unblocking Pulse Duration [ms] 200

Command Outputs During Link Failure do not change

Link Failure Pickup Time [s] 10

Link Failure Hold Time [s] 0

GPS Sync off

Embedded Operation Channel ( EOC ) on

Cyclic Loop Test Interval 6 h

Digital Interface

Interface Type G703 64kbps codirectional

BER Alarm Threshold ( 1E... ) -6

Digital Address Check off

Local Digital Address 341

Remote Digital Address 682

G.703 Tx Clock Sync Rx



Command Settings

Command Application Tx Trip Duration Monitoring

Max Tx Trip Duration [s]

Tx Input Delay [ms]

Rx Prolon-gation [ms]

A permissive off 5 0 10

B permissive off 5 0 10

C off off 5 0 0

D off off 5 0 0

E off off 5 0 0

F off off 5 0 0

G off off 5 0 0

H off off 5 0 0

Relay Interfaces


Interface 2 (N40)

Interface 3 (N46)

Interface 4 (N52)

Used on off off off

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




Interface 2 (N70)

Interface 3 (N76)

Interface 4 (N84)

Used off off off off

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





Alarm Settings

Pickup Time [s] 15

Hold Time [s] 15

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

Relay Interfaces Jumper Settings Nominal Battery Voltage


Relay Interface 1 (N34) 125 .. 250VDC 125 .. 250V DC









Rack Assembly

Slot Module Piggyback

Power Supply Unit 1 (N01) G3LH

Power Supply Unit 2 (N09) not assembled

Line Interface TPE 1 (N28) G3LD not assembled

Relay Interface 1 TPE 1 (N34) G3LR not assembled




Line Interface TPE 2 (N58) not assembled not assembled



Relay Interfaces 3 TPE 2 (N76) not assembled not assembled


(N84) not assembled not assembled



5.9. Performance Criteria

5.9.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.9.2. Transmission time

Traditional teleprotection have a set of fixed signal evaluation times for which the equipment delivers the requested performance (trans-mission 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 can be avoided by using patented dynamic adaptation. For the NSD570 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 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.



5.9.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 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: 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.9.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) must be added to the nominal transmission time. Severe disturbances (noise or bit errors) 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.9.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.12.



5.9.3. Security

The NSD570 with its dynamic adaptation of the receiver provides the best security / dependability trade-off for the chosen command applic-ation 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.

The security level Puc is fixed for each of the possible command applications.

5.9.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.9.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 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%).

5.9.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 continuous noise/bit errors

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 and 2 x T0) are recorded. The lower the signal-to-noise ratio (SNR) and the higher the bit error rate (BER) 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



April 2004


6.1. Introduction .............................................................................. 6-3

6.2. Safety instructions ................................................................... 6-3 6.2.1. General .................................................................................... 6-5

6.3. Unpacking................................................................................ 6-5 6.3.1. Inspection upon receipt............................................................ 6-5 6.3.2. What to do if there is transport damage................................... 6-5 6.3.3. Precautions to avoid transport damage ................................... 6-5

6.4. Installation................................................................................ 6-6 6.4.1. Place of installation and ambient conditions ............................ 6-6 6.4.2. Cabinet .................................................................................... 6-6 6.4.3. Installing racks in cabinets ....................................................... 6-6

6.5. Wiring....................................................................................... 6-6 6.5.1. Introduction .............................................................................. 6-6 6.5.2. Grounding system.................................................................... 6-7 6.5.3. External connections................................................................ 6-7 6.5.3.1. Power Supply......................................................................... 6-10 6.5.3.2. Station bus and Real Time Clock synchronization................. 6-11 6.5.3.2.1. Connection to terminal block at rear of equipment................. 6-11 6.5.3.2.2. Connection via G1LB cable for RTC sync/station bus ........... 6-12 6.5.3.3. System alarm relays .............................................................. 6-12 6.5.3.3.1. Connection to terminal block at rear of equipment................. 6-12 6.5.3.3.2. Connection via G3LC cable for alarm relays.......................... 6-13 6.5.3.4. Relay Interface G3LR ............................................................ 6-14 6.5.3.4.1. Connection to terminal block at rear of equipment................. 6-14 6.5.3.4.2. Connection via G3LR cable for relay interface....................... 6-15 6.5.3.5. Analog Interface G3LA........................................................... 6-16 6.5.3.5.1. Connection to terminal block at rear of equipment................. 6-16 6.5.3.5.2. Connection via G3LA cable for analog interface.................... 6-17 6.5.3.6. Digital Interface G3LD............................................................ 6-18 6.5.3.6.1. RS-422 – RS-449/RS-530/X.21interface ............................... 6-18 6.5.3.6.2. G.703 codirectional interface ................................................. 6-21 6.5.3.6.3. E1/T1 Interface G1LE ............................................................ 6-22 6.5.3.6.4. Optical Interface G1LO .......................................................... 6-24 6.5.3.7. LAN Interface G3LL ............................................................... 6-27 6.5.3.7.1. Ethernet 10/100BaseT LAN interface .................................... 6-27 6.5.3.7.2. Station bus............................................................................. 6-28

Installation and wiring April 2004 6-1


6.5.4. Internal connections............................................................... 6-29 6.5.4.1. Display Panel G1LC............................................................... 6-29

6.6. Photographs .......................................................................... 6-30

6-2 April 2004 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





Insertion and removal of plug-in modules


Back cover





DANGER This is a Class Ι equipment specified in IEC 60950. The equipment and the cabinet must be earthed. The equipment must be supplied over circuit breaker.



DANGER The isolating terminals from the external cables must be kept open during installation, maintenance and before storage, decommissioning and disposal.

DANGER The Faston supply connectors at the rear of the rack must be covered with an isolation sleeve.

DANGER The power supply is dangerous (hazardous voltage 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.



Laser / LED

Caution Laser / LED


ESD protection

Caution ESD


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 ABB 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 ABB company or agent and also ABB Switzerland Ltd, Utility Communication Systems, 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 ABB 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 clamp 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 clamp 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 binders 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.

RS-422 - RS-449/RS-530/X.21

G.703 E1/T1

Plastic cable binder

Metallic spring clamp

Fig. 6.1 Mounting of external cables with cable screen



Ethernet on LAN Interface G3LL

Plastic cable binder

Metallic spring clamp

Fig. 6.2 Mounting of external cables with cable screen (G3LL)



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: 1KHL015141R0001 Type: S282 K6A Max. voltage: ≤ 60 VDC or ≤ 250 VAC

B9AV Label E: CI-BREAK > 60 VDC … 250 VDC Ident. number: 1KHL015999R0001 Type: S282 UC-K 6A 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.3.

View from rear:

DC+AC L

DC- AC N

DC+AC L

DC- AC N

PE

Power Supply 2:

Positive battery pole DC supply or AC Line supply

Negative battery pole DC supply or AC Neutral supply

Power Supply 1:

Positive battery pole DC supply or AC Line supply

Negative battery pole DC supplyor AC Neutral supply

Protective earth connectors

Plastic cable binders

Fig. 6.3 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-clamp) type terminal block can be plugged onto connector X103 of the supply backplane G1LB. Recommended wire size: 0.8 mm2 (unshielded twisted pairs). Wire size range: Solid and stranded 0.14 to 1.5 mm2.

X103

RS

-

1

INTE

RFA

CE

G3LC

CO

MM

ON

AB

SU

PP

LYB

AC

KP

LAN

EG

1LB

Fig. 6.4

Installation

485

23

GN

D

1

6-G1LB_Connector.vsd

EX

T-SY

NC

(1 PP

S)

GP

S-S

YN

C (IR

IG-B

)

67

+5

4-

+-

7

Connector for station bus and Real Time Clock synchronization

and wiring April 2004 6-11


6.5.3.2.2. Connection via G1LB cable for RTC sync/station bus

The cable is equipped with screwless (spring-clamp) type terminals. Recommended wire size: 1.5 mm2 (unshielded twisted pairs). Wire size range: Solid 0.2 to 4.0 mm2, stranded 0.2 to 2.5 mm2.

6-G1LB_Cable.vsd

X103

6 71 2 4 5

G1LB CABLE FORRTC SYNC/STATION BUS

RTC SYNC/STATION BUS

EXT-SYNC (1 PPS)RS-485 GPS-SYNC (IRIG-B)

6 71 2+

5

INTERFACEG3LC

COMMON

WH BN GY PK BU RD

3

3

GN

A B GND

SUPPLYBACKPLANEG1LB

8

YE

4- + -

Terminals

Fig. 6.5 Station bus and Real Time Clock synchronization

6.5.3.3. System alarm relays


The screwless (spring-clamp) type terminal block can be plugged onto connector X102 of the common interface G3LC. Recommended wire size: 1.2 mm2. Wire size range: Solid and stranded 0.2 to 2.5 mm2.



AL NO

X1021 N

O2 C

ALAR

M R

ELA

Y CO

CO

MM

ON

INTER

FACE

G3LC

6.5.3.3.2

G3LC CABALARM R

X102

Term

COMMONINTERFACEG3LC

ARM

CO

NTA

CTS

AR

TE :

3 NC

1 NTA

CT R

ATING

: 155A

4

1

6-G3LC_Connector.vsd

ALARM

RELAY

2

6 NO

E SHO

WN

IN A

LARM

POS

.

NC

8C7

0W, 8A

MAK

E, C

ARR

Y, 0.6A BR

EAK

58

Fig. 6.6 Connector for system alarm relays

. Connection via G3LC cable for alarm relays

The cable is equipped with screwless (spring-clamp) type terminals. Recommended wire size: 1.5 mm2. Wire size range: Solid 0.2 to 4.0 mm2, stranded 0.2 to 2.5 mm2.

ALARM RELAY 2

6NO

ALARM CONTACTS ARE SHOWN IN ALARM POS.NOTE :

BK

LE FORELAYS

NC8

GNYE

4 5 6

BK

C7

1 2

1

BK

NO2

BK

C

3

3

BK

NC

PE

BK

ALARM RELAY 1

CONTACT RATING: 150W, 8A MAKE,5A CARRY, 0.6A BREAK

inals

6-GL3C_Cable.vsd

Fig. 6.7 G3LC cable for alarm relays



6.5.3.4. Relay Interface G3LR


The screwless (spring-clamp) type terminal block can be plugged onto connector X101 of the relay interface G3LR. Recommended wire size: 1.2 mm2. Wire size range: Solid and stranded 0.2 to 2.5 mm2.

G3LR

CABLE FO

RR

ELAY INTE

RFAC

E

TX1

12

1B1C1D

1A

X101-

+ (VOLT. R

AN

JUM

PE

R

2A+2C

2A+2D

2A+2B

INTE

RFAC

EG

3LR

RELAY

G1LR

(option)

G1LR

24VD

C...48V

DC

60VD

C...110V

DC

125VD

C...250V

DC

JUM

PE

R

1A+1C

1A+1D

1A+1B

UB

AT nom

.

G1LR

External dry contact

1

Fig. 6

6-14

6-G3LR_Connector.vsd

9 NO

10 C11 N

C

RX/R

EL1

1213

NO

C14 N

C3

4

TX2R

X1

65

78

RX2

-+

-+

RX/R

EL2

GE: 24...250V

DC

)IN

PUT

(SOLID

STATE / 5...250VDC

/2A)O

UTPU

TO

UTPU

T(H

EAVY DU

TY / 5...250VDC

/5A CAR

RY)

24VD

C...48V

DC

60VD

C...110V

DC

125VD

C...250V

DC

UBAT nom

.

2B

2C2D

2A-+

External dry contact

1

4

.8 Connector for relay interface

April 2004 Installation and wiring


6.5.3.4.2. Connection via G3LR cable for relay interface

The cable is equipped with screwless (spring clamp) type terminals. Recommended wire size: 1.5 mm2. Wire size range: Solid 0.2 to 4.0 mm2, stranded 0.2 to 2.5 mm2.

6-G3LR_Cable.vsd

G3LR CABLE FORRELAY INTERFACE

1 9 10

9NO

10C

11

11NC

RX/REL 1

12 13 14

12 13NO C

14NC

TX1

1 2

1B 1C 1D1A

3 4

TX2

X101

RX1

65 7 8

RX2

2 3 4 5 6 7 8

BK BK BK BK BK BK BK BK BK BK BK BK BK

PE

GNYEBK

- + - + - +

RX/REL2

(VOLT. RANGE: 24...250VDC)INPUT

(SOLID STATE / 5...250VDC/2A)OUTPUT OUTPUT

(HEAVY DUTY / 5...250VDC/5A CARRY)

24VDC...48VDC60VDC...110VDC125VDC...250VDC

JUMPER

2A+2C2A+2D

2A+2BU BAT nom.

INTERFACEG3LR

RELAY

G1LR

2B 2C 2D2A

- +

(option)

G1LR External dry contact

24VDC...48VDC60VDC...110VDC

125VDC...250VDC

JUMPER

1A+1C1A+1D

1A+1BU BAT nom.

G1LR External dry contact

Terminals

Fig. 6.9 G3LR cable for relay interface



6.5.3.5. Analog Interface G3LA

6.5.3.5.1. Connection to terminal block at rear of equipment The screwless (spring clamp) type terminal block can be plugged onto connector X100 of the Analog Interface G3LA. Recommended wire size: 1.2 mm2 (unshielded twisted pairs). Wire size range: Solid and stranded 0.2 to 2.5 mm2.

X100

TX-AF

12

IMP

EDAN

CE

X301

X303

X302TB

TA

TB>1.5kO

hm600O

hmTA

JUM

PERO

UTPU

T

INTE

RFAC

EG

3LA

ANA

LOG

6

1

Fig. 6

6-16

X202

X203R

A

X204

RB

>1.5kOhm

600Ohm

INPU

T

RB

RA

JUM

PER IM

PEDAN

CE

6-G3LA_Connector.vsd

BOO

ST

RX-AF

56

34

.10 Connector for analog interface



6.5.3.5.2. Connection via G3LA cable for analog interface

The cable is equipped with screwless (spring clamp) type terminals. Recommended wire size: 1.5 mm2 (unshielded twisted pairs). Wire size range: Solid 0.2 to 4.0 mm2, stranded 0.2 to 2.5 mm2.

X100

5 61 2 3 4

G3LA CABLE FORANALOG INTERFACE

BOOSTTX-AF RX-AF

5 61 2 3 4

WH BN GN YE GY PK

IMPEDANCE

X301

X303

X302TB

TAX202

X203RA

X204RB

TB >1.5kOhm600OhmTA

JUMPER OUTPUT

>1.5kOhm600Ohm

INPUT

RBRA

JUMPER

INTERFACEG3LA

ANALOGIMPEDANCE

Terminals

6-G3LA_Cable.vsd

Fig. 6.11 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 Sub-D 25 poles)

X1011

PE

INTE

RFA

CE

G3LD

DIG

ITAL

1

125

14

Fig. 6.12

6-18

RS

-422 IN

2 SD-A

163

14

RT-A

RD-A

SD-B

RD-B

SEN

DD

ATA

RE

CE

IVED

ATA

TR

E

6-G3LD_Cable.vsd

TER

FAC

E

249

17

RT-B

TT-ATT-A

TT-B

1511

12

ST-B

ST-A

TER

MIN

ALIM

ING

CE

IVE

TIMIN

GS

EN

DTIM

ING

7

SG

3

Connector for digital interface (male Sub-D 25 poles)



b) Connection via G3LD cable with isolating terminals (10 poles)

The cable is equipped with screwless (spring-clamp) type terminals. Recommended wire size: 1.5 mm2 (shielded twisted pairs). Wire size range: Solid 0.2 to 4.0 mm2, stranded 0.2 to 2.5 mm2.

6-G3LD_Cable.vsd

RS-422 INTERFACE

X101 1

CHASSISGND

PE

WH

2

5

SD-A

2491716314

6 1 2

BN GN YE

9

BU

RT-

A

RD

-A

SD-B

RD

-B

RT-

B

TT-A

TT-A

TT-B

1511 12

10 7 8

RD BK VT

ST-B

ST-A

SENDDATA

TERMINALRECEIVEDATA TIMING

RECEIVETIMING

SENDTIMING

GY PK

3 4 PE

INTERFACEG3LD

DIGITAL

G3LD*CABLE WITHISOLATING TERMINALS

Terminals

Fig. 6.13 G3LD cable with isolating terminals (10 poles)

c) Connection via G3LD cable with RS-449 interface (37 poles)

6-G3LD_Cable.vsd

RS-422 INTERFACE

1

PE

2

SD

-A

2491716314

RT-

A

RD

-A

SD

-B

RD

-B

RT-

B

TT-A

TT-A

TT-B

1511 12

ST-

B

ST-

A

SENDDATA


RECEIVETIMING

SENDTIMING

INTERFACEG3LD

DIGITAL

G3LD*CABLE WITHRS-449 INTERFACE(37-P)

1

WH

4 22 6 24

BN GN YE

17

BU

35 5 23

RD BK VT

8 26

GY PK

X101

CHASSISGND

Fig. 6.14 G3LD cable with RS-449 interface (male Sub-D connector 37 poles)



d) Connection via G3LD cable with RS-530 interface (25 poles)

6-G3LD_Cable.vsd

RS-422 INTERFACE

X101 1

1

PE

WH

2

2

SD

-A

2491716314

14 3 16

BN GN YE

24

BU

RT-

A

RD

-A

SD

-B

RD

-B

RT-

B

TT-A

TT-A

TT-B

1511 12

11 15 12

RD BK VT

ST-

B

ST-

A

SENDDATA


RECEIVETIMING

SENDTIMING

17 9

GY PK

G3LD*CABLE WITHRS-530 INTERFACE (25-P)

INTERFACEG3LD

DIGITAL

CHASSISGND

Fig. 6.15 G3LD cable with RS-530 interface (male Sub-D connector 25 poles)

e) Connection via G3LD cable with X.21 interface (15 poles)

RS-422 INTERFACE

X101 1

1

PE

WH

2

2

SD

-A

2491716314

9 4 11

BN GN YE

7

GY

RT-

A

RD

-A

SD

-B

RD

-B

RT-

B

TT-A

TT-A

TT-B

1511 12

14 6 13

PK BU RD

ST-

B

ST-

A

SENDDATA


RECEIVETIMING

SENDTIMING

6-G3LD_Cable.vsd

INTERFACEG3LD

DIGITAL

G3LD*CABLE WITHX.21 INTERFACE (15-P)

CHASSISGND

Fig. 6.16 G3LD cable with X.21 interface (male Sub-D connector 15 poles)



6.5.3.6.2. G.703 codirectional interface

a) Connector at rear of equipment (RJ45, 8 poles)

63

45

G.703 C

OD

IRE

CTIO

NA

L INTE

RFA

CE

27

RX

DA

TAD

ATA

TX

+-

+-

X201

36

25

47

INTE

RFA

CE

G3LD

DIG

ITAL

1

8

Fig. 6.17

b) Conn(RJ45

The cabequippedwires oftwisted p

INTERFACEG3LD

DIGITAL

G3LD*CABLE FOG.703/E1/T1INTE(RJ45 connector

Prte

Fig. 6.18

Installatio

88

6-G3LD_Cable.vsd

11

Connector for G.703 codirectional interface (RJ45, 8 poles)

ection via G3LD cable for G.703/E1/T1 interface , 8 poles)

le has RJ45 connectors at both ends and in addition is with a connection module that allows toolless connection of

size 0.5 mm (AWG 24) … 0.65 mm (AWG 22), shielded airs.

RJ45 Press-Fit1 1 2 2 3 = Rx - 3 = Rx -4 = Tx + 6 = Rx +5 = Tx - 5 = Tx - 6 = Rx + 4 = Tx +7 7 8 8

6-G3LD_Cable.vsd

6 3 4 5

G.703 CODIRECTIONAL INTERFACE

2 7 8 1

RXDATA DATA

TX

+ - + -X201 36 254 187

RRFACE

8 poles)

36 254 187ess-fitrminals

CHASSISGND

View of pins: top-down, as real terminal strip

G.703 codirectional interface with G3LD cable for G.703/E1/T1 interface (RJ45, 8 poles)

n and wiring April 2004 6-21


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.

G1LE

E1/T1 INTE

RFA

CE

12

45

RL1

RL2

XL2

XL1

(OPTIO

N)

X101

INTER

FAC

EG

3LD

DIG

ITAL

37

86

RX

DA

TAD

ATATX

6-G3LD_Cable.vsd

1

8

Fig. 6.19 Connector for E1/T1 interface (RJ45, 8 poles)



b) Connection via G3LD cable for G.703/E1/T1 Interface (RJ45, 8 poles)

The cable has RJ45 connectors at both ends and in addition is equipped with a connection module that allows toolless connection of wires of size 0.5 mm (AWG 24) … 0.65 mm (AWG 22), shielded twisted pairs.

RJ45 Press-Fit1 = RL2 1 = RL22 = RL1 2 = RL13 3 4 = XL2 6 5 = XL1 5 = XL16 4 = XL27 7 8 8

6-G3LD_Cable.vsd

Press-fitterminals

G1LEE1/T1 INTERFACE

1 2 4 5R

L1

RL2

XL2

XL1

(OPTION)

X101

INTERFACEG3LD

DIGITAL

3 7 8 6

G3LD*CABLE FORG.703/E1/T1INTERFACE(RJ45 connector 8 poles)

1 2 4 5 3 7 8 6

CHASSISGND

RXDATA DATA

TX

View of pins: top-down, as real terminal strip

Fig. 6.20 E1/T1 interface with G3LD cable for G.703/E1/T1 interface (RJ45 8 poles)



6.5.3.6.4. Optical Interface G1LO

When handling with optical fibers please remember: Fiberoptic 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 and also the rear cover, ensure that the optical fibers are not bruised or crimped.

a) Connector at rear of equipment (E2000™) The connector is located on the optional piggyback module G1LO, mounted face down on top of the digital interface G3LD.

6-G3LD_Cable.vsd

G1LO

OPTIC

AL INTE

RFAC

E

TX

(OPTIO

N)

X701 (OP

T. CO

NN

.E2000)

INTE

RFAC

EG

3LD

DIG

ITAL

RX

Fig. 6.21 Connector E2000™ for optical fiber



b) Connection via optical cable (E2000™ or FC/PC)

The available optical cables have E2000™ connectors at both ends or E2000™ and FC/PC connectors.

6-G3LD_Cable.vsd

G1LOOPTICAL INTERFACE(OPTION)

X701 (OPT. CONN.E2000)

INTERFACEG3LD

DIGITAL

1) 1)

TXBURD

RX

1) Optical cable type Connector

V9WP, V9WR E2000™ – E2000™ V9WQ, V9WS E2000™ – FC/PC

Fig. 6.22 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 spring loaded metal shutter that avoid laser radiation exposure when they are mated on one end only.

Fig. 6.23 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 connectors features integrated black protective caps that avoid laser radiation exposure when they are unmated.

Fig. 6.24 E-2000™ duplex compact fiber optic connector

Fig. 6.25 E-2000™ simplex fiber optic connector



6.5.3.7. LAN Interface G3LL

6.5.3.7.1. Ethernet 10/100BaseT LAN interface


X201 R

J4

G3LL

LAN

Fig. 6.2

Installati

Ethernet In

12 TX-

TX+

5

TXD

ATA

Interface

1

terface

36

RX+

RX-

DA

TAR

X

45

78

75 75

PE

6-G3LL_Connector.vsd

8

6 Connector for Ethernet interface (RJ45, 8 poles)

on and wiring April 2004 6-27


6.5.3.7.2. Station bus

b) Connection to terminal block at rear of equipment

The screwless (spring clamp) type terminal block can be plugged onto connector X500 of the LAN Interface G3LL. Recommended wire size: 1.2 mm2 (unshielded twisted pairs). Wire size range: Solid and stranded 0.2 to 2.5 mm2.

X500

RS

-485

12

G3LL

LAN

Interface

3

AB

GN

D

1

7

Fig. 6

b) St

For awire tthe cG3LL

This FOR conne(1KH

6-28

45

67

6-G3LL_Connector.vsd

.27 Connector for station bus interface (7 poles)

ation bus wiring

proper operation of the NSD570 LAN Interface it is necessary to he station bus of the supply backplane G1LB (Pin 1, 2 and 3 of onnector X103) to the station bus of the NSD570 LAN Interface (Pin 1, 2 and 3 of the connector X500).

can be done with the optional connecting cable “G3LL*CABLE STATION BUS/RTC SYNC” (1KHW001213R0001). The optional cting cable G1LB*CABLE FOR STATION BUS/RTC SYNC

W000668R0001) will then be dispensable.



6.5.4. 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.4.1. 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.28 Mounting of the Display Panel G1LC

Caution:

The ribbon cable has to be mounted abducing down-wards.

Fig. 6.29 Correct connection of the ribbon cable



6.6. Photographs

Fig. 6.30 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.31 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).



April 2004

7. Commissioning

7.1. Safety instructions ................................................................... 7-2

7.2. Testing the communication channel ........................................ 7-4

7.3. Commissioning the equipment................................................. 7-5 7.3.1. Preliminary inspection and checks........................................... 7-5 7.3.2. Checks according to commissioning instructions..................... 7-6 7.3.3. HMI570 functions to support commissioning ........................... 7-6

Commissioning April 2004 7-1


7. Commissioning









Warning labels


Inserting and removing of plug-in modules


7-2 April 2004 Commissioning


Back cover


ESD protection

Caution ESD


Laser / LED

Caution Laser / LED


Using HMI570








LAN Interface G3LL

DANGER The LAN Interface G3LL contains a lithium battery.

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.

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) 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.9.2. of this manual for remarks about "Transmission Time".

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. 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 the annex of this manual.

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.12. of this manual for a detailed description of the above mentioned test facilities.



April 2004



8.2. Operation ................................................................................. 8-5 8.2.1. Normal operation ..................................................................... 8-5 8.2.2. Equipment failure..................................................................... 8-5

8.3. Maintenance ............................................................................ 8-6 8.3.1. Periodic Functional Checks ..................................................... 8-6 8.3.1.1. Check input power supply voltage ........................................... 8-6 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-8 8.3.1.6. Check AF line levels ................................................................ 8-8 8.3.1.7. Check bit error rates ................................................................ 8-8 8.3.1.8. Removing the equipment from service for testing.................... 8-9 8.3.1.9. Checking the entire link............................................................ 8-9

Operation and maintenance April 2004 8-1






Warning labels









Back cover


8-2 April 2004 Operation and maintenance


ESD protection

Caution ESD




Laser / LED

Caution Laser / LED


Using HMI570








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 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 and alarm status and should not light during normal operation.

Refer to Section 3.3.4. of this manual 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. of this manual 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 Section 4.8.9.2. and 4.8.10.2.

See Section 9.3.4. “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 (48 V DC … 250 V DC ±20% or 100 V AC … 240 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) 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) 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.


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!

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.6 of this Manual). 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.


measurement do only have an adequate accuracy ifthe EOC is switched off!

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 prevailingBER is higher than 1E-05!

The measurement of the short term average BERtakes 16 seconds, the long term average BER is onlydisplayed after the equipment is continuously powered for at least 4.5 hours (262 minutes).



8.3.1.8. 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.

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.9. 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 the annex of this manual 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.



April 2004

9. Troubleshooting


9.2. Fuses ....................................................................................... 9-4

9.3. Alarms...................................................................................... 9-5 9.3.1. Alarm concept.......................................................................... 9-5 9.3.2. Alarm pick up and hold delay................................................... 9-6 9.3.2.1. High level alarms ..................................................................... 9-6 9.3.2.2. Low level common alarms and relay interface alarms ............. 9-7 9.3.2.3. Analog interface alarms ......................................................... 9-10 9.3.2.4. Digital interface alarms .......................................................... 9-10 9.3.3. Problem localization............................................................... 9-12 9.3.4. List of low level alarms and corrective actions ....................... 9-13 9.3.5. Alarm event recorder ............................................................. 9-20 9.3.6. Alarm polling .......................................................................... 9-21

9.4. Warnings................................................................................ 9-21

9.5. Some basic checks................................................................ 9-22

9.6. Frequently asked questions ................................................... 9-23 9.6.1. General .................................................................................. 9-23 9.6.2. Where can I get the latest version of this FAQ?..................... 9-25

9.7. Replacing faulty modules....................................................... 9-26

9.8. Returning modules for repair ................................................. 9-26

9.9. Support .................................................................................. 9-26

Troubleshooting April 2004 9-1


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.











Safety and monitoring facilities

DANGER Mechanical safety facilities such as cover plates must not be removed or by-passed.

9-2 April 2004 Troubleshooting


Back cover


ESD protection

Caution ESD


Using HMI570






Laser / LED

Caution 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)



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 3 categories:

- common alarms and relay interface alarms - analog interface alarms - digital 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 alarm). This is valid for the local alarms as well as for the remote alarms (except for "HW Warning"). 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.

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 appear. The programmed alarm pick-up and hold delay is valid for these outputs too.

Note: The remote alarms are not signaled on the alarm

outputs of the local G3LC. But they are included inthe “System Alarm” which may be mapped on anyavailable output of the Relay Interfaces G3LR.



9.3.2. 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, 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.2.1. High level alarms

The following table lists the high level alarms, their meaning and output devices (red LEDs on equipment front; switch over contacts on G3LR which are programmable by means of the HMI570):

High level alarm

Re-mark

Meaning Displayed by LED

Output via G3LR contact

HW Warning The equipment is operational, but one of the redundant power supply units (PSU) failed

X ”Unit 1”, “Unit 2”

X

HW Alarm Signals that a hardware problem in the equipment generating the alarm has been detected

X ”OK / Fail” (on the modules concerned)

X

Link Alarm Indicates that the quality of the received signal is insufficient. Possible reasons are excessive noise, low input level, interfe-rence, faulty transmitter at the remote side, …

X

Transmit Alarm Signals a problem detected in the equipment's transmit part

X ”Transmit”

X

Receive Alarm Signals a problem detected in the equipment's receive part

X ”Receive”

X

Local Alarm 1) OR function of all alarms of the local equipment (except HW-Warning)

X ”Local”

X

Remote Alarm 2) OR function of all alarms of the remote equipment (except HW-Warning)

X ”Remote”

X

System Alarm Local Alarm OR Remote Alarm X

Table 9.1 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.



9.3.2.2. 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 Low Level Alarm

Rem

ark

Ala

rm

Cod

e H

W

War

ning

H

W

Ala

rm

Link

A

larm

Tr

ansm

it

Ala

rm

Rec

eive

A

larm

Lo

cal

Ala

rm

Rem

ote

Ala

rm

Syst

em

Ala

rm

OK

/ Fa

il

(Lin

e

Inte

rfac

e)

HW Release Common Interface and Bus Plane do not match

0.20 X X X X OK

Overcurrent in MOSFET output 2 3) 0.19 X X X X OK

Overcurrent in MOSFET output 1 3) 0.18 X X X X OK

Single component failure input 2 3) 0.17 X X X X X OK

Single component failure input 1 3) 0.16 X X X X X OK

Error Relay Interface 4 TPE 2 (N84) 4) 0.14 OK








Micro controller FLASH verify error 0.5 X X X X Fail

5 V supply voltage failure 0.4 X X X X OK

Warning: Undervoltage redundant supply 2 0.3 X OK

Warning: Undervoltage redundant supply 1 0.2 X OK

Undervoltage alarm supply 2 5) 0.1 X X X X OK

Undervoltage alarm supply 1 6) 0.0 X X X X OK

Program memory internal CRC check failed 1.31 X X X X Fail

Program memory SDRAM CRC check failed 1.30 X X X X Fail

Data memory lookup table CRC check failed 1.29 X X X X Fail

Program memory internal CRC add. segment failed

1.28 X X X X Fail

SDRAM data memory check failed 1.26 X X X X Fail

Internal data memory check failed 1.25 X X X X Fail

Program Memory micro controller CRC check failed

1.24 X X X X Fail

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 plugged 4) 1.12 X X X OK

Wrong slot for Line Interface 1.10 X X X X Fail

Configuration error 1.7 X X X X Fail

Link failure: command outputs set to a pre-defined state

1.6 X X X X OK

Loop test error 1.5 X X X OK

Unblocking pulse 7) 1.4 OK




Rem

ark

Ala

rm

Cod

e H

W

War

ning

H

W

Ala

rm

Link

A

larm

Tr

ansm

it

Ala

rm

Rec

eive

A

larm

Lo

cal

Ala

rm

Rem

ote

Ala

rm

Syst

em

Ala

rm

OK

/ Fa

il

(Lin

e

Inte

rfac

e)

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 OK

No trip and no guard 1.0 X X X X X OK

Tx continuous command H 4) 4.19 X X X X OK

Tx continuous command G 4) 4.18 X X X X OK

Tx continuous command F 4) 4.17 X X X X OK

Tx continuous command E 4) 4.16 X X X X OK

Tx continuous command D 4) 4.15 X X X X OK

Tx continuous command C 4) 4.14 X X X X OK

Tx continuous command B 4) 4.13 X X X X OK

Tx continuous command A 4) 4.12 X X X X OK

Comm. error Relay Interface 4 TPE 2 (N84) 4) 4.11 X X X OK








Continuous command alarm 4) 4.0 X X X X OK

Table 9.2 Low level common alarms and relay interface alarms

Remarks:

3) Only in combination with other relay interface alarms; the corresponding “Ok / Fail” LED of the affected relay interface lights up red

4) Only in combination with other relay interface alarms 5) LED “Supply Unit 2” lights red 6) LED “Supply Unit 1” lights red 7) Generates an entry in the event recorder only and activates an output contact, if configured



9.3.2.3. 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)

• Signal-to-noise ratio too low (the threshold for the SNR alarm depends on the setting of the bandwidth and the operating mode; in general it is 3 dB above the specified value for Pmc < 1%)

• Internal supply voltage failure

The following table lists the low level analog interface alarms, and shows their influence on the high level alarms.


Rem

ark

Ala

rm

Cod

e H

W

War

ning

H

W

Ala

rm

Link

A

larm

Tr

ansm

it

Ala

rm

Rec

eive

A

larm

Lo

cal

Ala

rm

Rem

ote

Ala

rm

Syst

em

Ala

rm

OK

/ Fa

il

(Lin

e

Inte

rfac

e)

SNR Alarm 2.6 X X X X X OK

Receive level alarm 2.5 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 Fail

Table 9.3 Low level analog interface alarms

9.3.2.4. Digital interface alarms

The following criteria are continuously monitored and produce 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)

• LFA Loss of Frame Alignment (E1/T1)

• RRA Receive Remote Alarm (E1/T1/Optical Direct Fiber)

• Laser failure (G1LO)



The following criteria are monitored during start-up and produce alarms:

• Missing piggyback (if configured) or not supported by the firmware loaded on G3LD

• FPGA CRC/loading failure on G3LD

• Specific E1/T1 framer errors on G1LE and G1LO (see list below)

The following table lists the low level digital interface alarms, and shows their influence on the high level alarms.


Rem

ark

Ala

rm

Cod

e H

W

War

ning

H

W

Ala

rm

Link

A

larm

Tr

ansm

it

Ala

rm

Rec

eive

A

larm

Lo

cal

Ala

rm

Rem

ote

Ala

rm

Syst

em

Ala

rm

OK

/ Fa

il

(Lin

e

Inte

rfac

e)

Laser Failure 3.28 X X X X X Fail

Remote equipment has wrong address 3.25 X X X X OK

BER Bit Error Rate alarm 3.24 X X X X X OK

Alarm Indication Signal G.703 3.21 X X X X X OK

Loss of Signal G.703 3.20 X X X X X OK

Pattern synchronization error 3.17 X X X X OK

Read error from E1/T1 framer 8) 3.13 X X X X Fail

Write error to E1/T1 framer 8) 3.12 X X X X Fail

Piggyback missing 3.8 X X X X Fail

LOS Loss of Signal 8) 3.7 X X X X X OK

AIS Alarm Indication Signal 3.6 X X X X X OK

LFA Loss of Frame Alignment 3.5 X X X X X OK

RRA Receive Remote Alarm 9) 3.4 X X OK

FW version does not support piggyback 3.3 X X X X Fail

Initialization failure in FPGA 3.2 X X X X Fail

CRC failure while loading FPGA 3.1 X X X X Fail

FPGA not loaded 3.0 X X X X Fail

Table 9.4 Low level digital interface alarms

Remarks:

8) Also applicable for Optical Interface G1LO (Optical Direct Fiber, Optical FOX/OTERM, Optical IEEE C37.94).

9) Also applicable for Optical Interface G1LO (Optical Direct Fiber).



9.3.3. 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.5 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.

Channel A to BEquipment A Equipment B

NSD570 NSD570Channel B to A

Commands Commands

9-Fault-location.vsd

Fig. 9.1 The four major fault location areas of an NSD570 link

Equipment A Equipment B

Hardware Alarm

Link Alarm

Hardware Alarm

Link Alarm

Problem localized in

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.5 Alarm localization with link and hardware alarms



9.3.4. 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

Code Explanation Corrective Action

HW Release Common Interface and Bus Plane do not match

0.20 Change the bus plane or the common interface board (whichever does have a non-compatible hardware version). Refer to document 1KHW000902 “Compatibility Requirements NSD570”

Overcurrent in MOSFET output 2 0.19

Overcurrent in MOSFET output 1 0.18

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 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

Single component failure input 1 0.16

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 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) generating at least one of the following low level alarms:

- Overcurrent in MOSFET output 2 (Alarm Code 0.19),

- Overcurrent in MOSFET output 1 (Alarm Code 0.18),

- 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 busplane, 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



Low Level Alarm Alarm Code

Explanation Corrective Action

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. If persistent: replace 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. segment failed

1.28 Indicating a hardware defect of the DSP / SDRAM on 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 check failed

1.24 Indicating a hardware defect of the micro-controller FLASH 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 externally 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 externally sync time (GPS Sync = IRIG-B)

Check timing source and connections

No signal (IRIG-B) on RTC 1.16 Check timing source and connections





More Relay Interfaces configured than plugged

1.12 This error appears always in conjunction with at least one “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.

Link failure: command outputs set to a pre-defined state

1.6 Check link

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.

Laser Failure 3.28 The laser does not run properly due to a hardware problem.

Replace the optical interface G1LO.

Remote equipment has wrong address 3.25 The device address in the configuration file does not match with the device address of the remote equipment.

Correct the device address in the configuration file or in 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.

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 communication channel.

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.

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.

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.

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 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 an error in the E1/T1 or Optical Direct Fiber interface.

Check the E1/T1/Optical Direct Fiber settings of both the remote or local device or replace the remote or local digital line interface or replace the remote or local E1/T1 interface or the optical interface.

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 in the digital line interface has been detected.

Replace the digital line interface.

Tx continuous command H 4.19

Tx continuous command G 4.18

Tx continuous command F 4.17

Tx continuous command E 4.16

Tx continuous command D 4.15

Tx continuous command C 4.14

Tx continuous command B 4.13

Tx continuous command A 4.12

The continuous command monitoring for the corresponding command (A … H) is enabled and the maximum duration as configured by HMI570 has been exceeded. This error appears always in conjunction with the “Continuous command alarm”(Alarm Code 4.0).

Verify that the continuous command monitoring / maximum duration of the corresponding command (A … H) as configured by HMI570 is correct or change the settings of the equipment generating the command so that it is not longer than allowed.

Comm. error Relay Interface 4 TPE 2 (N84) 4.11








Either the corresponding relay interface is not plugged, the relay interface is faulty or there is a problem with the connector of the relay interface to the bus plane.

Plug the relay interface or – if already plugged – check its connector to the bus plane. If the error persists, replace the relay interface. If this does not 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.





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.7.1

Error! Communication incorrectly initialized HMI Refer to Section 4.10.7.2

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 disk. Check the disk.

Error! Device communication failed HMI The communication between the HMI570 and the device failed.


Error! Device communication is busy! Please try it later again

HMI Refer to Section 4.10.7.2

Error! Device communication timeout HMI Refer to Section 4.10.7.2

Error! Device communication, device reports wrong checksum

HMI

Error! Device communication, device reports wrong end byte

HMI

Error! Device communication, device trans-mission restart

HMI

Error! Device could not execute this function HMI

Error! Device does not allow this function HMI

Error! Device reports unknown function HMI

A communication error or a compatibility problem has probably occurred.

Retry the operation.

If the error persists, make sure that HMI570 and the line interface generating the alarm are compatible, using document 1KHW000902 “Compatibility Requirements NSD570”.

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, 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 disk. Check the disk.

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 another user/application

HMI Refer to Section 4.10.7.2

Error! This configuration version is not supported

HMI The installed HMI570 version does not support the version of 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

Error! Wrong configuration checksum HMI

Error! Wrong configuration length HMI

HMI570 could not upload the configuration from the device.

Retry the operation.

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 execute this function !

HMI A user without modify permission is not allowed to execute some functions.

Refer to Section 4.10.5

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 Use a password that is at least 4 characters long

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.10.5.

Table 9.6 Low level alarms with explanation and corrective actions

9.3.5. Alarm event recorder

The event recorder is described in detail in Section 3.5.10.

All alarm events available in the system are recorded continuously in the nonvolatile memory of G3LA or G3LD 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.10.5 and Section 6.5.3.2).

Up to 7500 alarm events are recorded. If this number is exceeded, the oldest events are discarded.



9.3.6. Alarm polling

Note: This function is available only in association with the

LAN Interface G3LL!

The alarm polling facility allows to monitor 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” for setting up the Alarm Polling can be found in Section 4.10.13 of these Operating Instructions.

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), 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 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.

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 device plugged in TPE 1 respectively 246 for TPE 2. 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 address. 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 correct this problem?

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 device 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.8.11.7 Firmware Download. If the problem still exists, replace the corresponding line interface module.



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 or bit errors, 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) or level generators/selective level meters (for NSD570 Analog).

Question: 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 panel?

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.

9.6.2. Where can I get the latest version of this FAQ?

Send e-mail to:

[email protected]


mailto:[email protected]


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 G3HL, 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 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.

ABB is not responsible for a module received which was damaged during transport. The financial implications of the repairs depends upon the agreement with the client.

Refer to document “1KHM010296 - Repair and Return Procedure” in the Appendix.

9.9. Support

Refer to document “1KHM010297 - Need Support for your Communi-cation System?” in the Appendix.



April 2004


10.1. Safety instructions ................................................................. 10-2

10.2. Storage .................................................................................. 10-3

10.3. Decommissioning .................................................................. 10-3

10.4. Disposal ................................................................................. 10-3

Storage, decommissioning and disposal April 2004 10-1









ESD protection

Caution ESD






10-2 April 2004 Storage, decommissioning and disposal


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.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.

Storage, decommissioning and disposal April 2004 10-3


LAN Interface G3LL


10-4 April 2004 Storage, decommissioning and disposal


April 2004

11. Appendices

11.1. Abbreviations ......................................................................... 11-2

11.2. Order numbers....................................................................... 11-4

11.3. Photographs .......................................................................... 11-7 11.3.1. Front view of NSD570............................................................ 11-7 11.3.2. Rear view of NSD570 ............................................................ 11-7

11.4. Dimension Drawing Module Rack G7BI................................. 11-8

Appendices April 2004 11-1


11. Appendices

11.1. Abbreviations

AC Alternating Current

AIS Alarm Indication Signal

AF Audio Frequency

AWG American Wire Gauge

BER Bit Error Rate

C Common (terminal of switchover relays)

DC Direct Current

DCE Data Circuit-terminating Equipment

DSP Digital Signal Processor

DTE Data Terminal Equipment

EMC Electromagnetic Compatibility

EOC Embedded Operation Channel

ESD Electrostatic Discharge

FPGA Field Programmable Gate Array

FSK Frequency Shift Keying

HF High Frequency

HMI Human Machine Interface

HTML Hyper Text Markup Language

HTTP Hyper Text Transfer Protocol

IEC International Engineering Consortium

IP Internet Protocol

ITU-T International Telecommunication Union – Telecommunication Standardization Sector of ITU

LAN Local Area Network

LED Light Emitting Diode

LOS Loss Of Signal

MC /µC Micro Controller

HMI570 NSD570 User Interface Program

11-2 April 2004 Appendices


N.A. / n.a. Not Applicable or Not Available

NC Normally Closed (terminal of switchover relays)

NO Normally Open (terminal of switchover relays)

PC Personal Computer

PDH Plesiochronous Digital Hierarchy

PE Protective Earth

PLC Power Line Carrier (communication via the high-voltage line)

RD Receive Data

RF Radio Frequency

RMS Root Mean Square

RT Receive Timing

RT-Bus Real Time Bus

RTC Real Time Clock

Rx Receive(r)

SD Send Data

SDH Synchronous Digital Hierarchy

SONET Synchronous Optical Network

SMD Surface Mounted Device

SNR Signal to noise ratio

ST Send Timing

STP Shielded Twisted Pairs

TCP Transmission Control Protocol

TPE Teleprotection Equipment

TT Terminal Timing

Tx Transmit(ter)

UTP Unshielded Twisted Pairs

WAN Wide Area Network



11.2. Order numbers

Type Description Order number

Basic Equipment

NSD570 Analog

NSD570*BASIC EQUIPMENT ANALOG Consists of G7BI, G3LH, G3LA, G3LR (one each)

1KHW000913R0001

NSD570 Digital

NSD570*BASIC EQUIPMENT DIGITAL Consists of G7BI, G3LH, G3LD, G3LR (one each)

1KHW000914R0001

Module Rack

G7BI G7BI*MODULE RACK NSD570 1KHW000911R0001

Display Panel

G1LC G1LC*DISPLAY PANEL NSD570 1KHW001018R0001

Power Supply

G3LH G3LH*POWER SUPPLY NSD570 1KHW000909R0001

Interface Cards

G3LA G3LA*ANALOG INTERFACE NSD570 1KHW000884R0101

G3LD G3LD*DIGITAL INTERFACE NSD570 1KHW000886R0102

G1LE G1LE*E1/T1 INTERFACE NSD570 1KHW000888R0001

G1LO G1LO*OPTICAL INTERFACE OTERM/P2P NSD570

1KHW000965R0001

G1LO G1LO*OPTICAL INTERFACE IEEE C37.94 NSD570

1KHW000965R0010

G3LR G3LR*RELAY INTERFACE NSD570 1KHW000880R0101

G1LR G1LR*INPUT TRIPPING VOLTAGE NSD570 1KHW000882R0001

Electrical Connecting Cables

G3LA*CABLE FOR ANALOG INTERFACE 1KHW000664R0001

G1LB*CABLE FOR STATION BUS/RTC SYNC 1KHW000668R0001

G3LC*CABLE FOR ALARM RELAYS 1KHW000658R0001

G3LD*CABLE WITH X.21 INTERFACE (15-P) 1KHW000670R0001

G3LD*CABLE WITH RS-530 INTERFACE (25-P) 1KHW000669R0001

G3LD*CABLE WITH RS-449 INTERFACE (37-P) 1KHW000671R0001

G3LD*CABLE WITH ISOLATING TERMINALS 1KHW000662R0001

G3LD*CABLE FOR G.703/E1/T1 INTERFACE 1KHW001003R0001

G3LR*CABLE FOR RELAY INTERFACE 1KHW000659R0001



Type Description Order number Optical Connecting Cables

V9WP*FOC-CB SM 2F INTERN E2000-FC/PC 2M (2m) 1KHW000580R0002 1

V9WQ*FOC-CB SM 2F INTERN E2000-E2000 2M (2m) 1KHW000581R0002 1

V9WR*FOC-CB SM 2F EXTERN E2000-FC/PC 10M (10m) 1KHW000582R0010 1

V9WS*FOC-CB SM 2F EXTERN E2000-E2000 10M (10m) 1KHW000583R0010 1

LAN Interface

G3LL G3LL*LAN INTERFACE NSD570 1KHW001016R0001

G3LL*CABLE FOR STATION BUS/RTC SYNC 1KHW001213R0001

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

Copy Instructions Compact Flash Card G3LL 1KHW001291

Repair and Return Procedure 1KHM010296

Support Document 1KHM010297

Table 11.1 Order numbers

1 Other length available on request: order number above plus R00xx where xx = length in meters.



Type Description Order number

Optional items

For G7BI ESD EARTHING SET 4.5MM (conductive bonded wrist strap for connection to the ESD bonding point EBP at the rear of the rack)

1KHW000330R0001

For G7BI NSD570*STANDARD ACCESSORIES (one set is delivered with each module rack)

1KHW001039R0001

For modules

Special screwdriver from PHOENIX CONTACT (for releasing the tension spring of the connectors)

SZS 0,6 x 3,5 Order No. 12 05 05 3

For cables Special screwdriver from PHOENIX CONTACT (for releasing the tension spring of the terminals)

SZF 1 - 0,6 x 3,5 Order No. 12 04 51 7

Table 11.2 Order numbers accessories



11.3. Photographs

11.3.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 each with four relay interfaces.

Fig. 11.1 Front view of NSD570

11.3.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.4. 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



April 2004

12. Annex

Technical Data NSD570 1KHW000892

Software Installation Description HMI570 1KHW000894

Firmware Download Description NSD570 1KHW000896

Programming and Testing Instructions NSD570 1KHW000898

Commissioning Instructions NSD570 1KHW000900

Compatibility Requirements NSD570 1KHW000902

Anomaly List NSD570 1KHW000904

Commissioning Instructions LAN Interface G3LL 1KHW001289

Copy Instructions Compact Flash Card G3LL 1KHW001291

Repair and Return procedure 1KHM010296

Support Document 1KHM010297

Annex April 2004 12-1

ABB Switzerland Ltd

TECHNICAL DATA NSD570 The teleprotection equipment NSD570 complies with EMC Directive 89/336/EEC and the Low-Voltage Directive 73/23/EEC. 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...........................................................................................................................................2 2. Analog System Data......................................................................................................................................2 3. Digital System Data.......................................................................................................................................4 4. Common System Data ..................................................................................................................................5 5. Special Operating Modes ..............................................................................................................................6 6. Analog Interface (G3LA)................................................................................................................................7 7. Digital Line Interfaces (G3LD) .......................................................................................................................8

7.1. G.703 Codirectional Interface .............................................................................................................8 7.2. RS-422 Interface .................................................................................................................................9 7.3. E1/T1 Interface (G1LE) .....................................................................................................................10 7.4. Optical Interface (G1LO)...................................................................................................................12

8. Relay Interface (G3LR) ...............................................................................................................................14 9. Power Supply (G3LH) .................................................................................................................................15 10. Common Interface (G3LC) ..........................................................................................................................16 11. Bus Plane With Front Cover (G1LA) ...........................................................................................................17 12. Supply Backplane (G1LB) ...........................................................................................................................17 13. Internal Tripping Voltage (G1LR) ................................................................................................................17 14. LCD Display Panel (G1LC) .........................................................................................................................17 15. LAN Interface Data (G3LL)..........................................................................................................................18 16. HMI570 User Interface ................................................................................................................................18

16.1. HMI570 „LAN“ ...................................................................................................................................18 16.2. HMI570 „PC“ .....................................................................................................................................19

17. Alarms .........................................................................................................................................................20 18. Event Recorder and Counters.....................................................................................................................21 19. Electromagnetic Compatibility (EMC) .........................................................................................................21

19.1. Electrical Safety ................................................................................................................................21 19.2. Emission............................................................................................................................................21 19.3. Immunity............................................................................................................................................21 19.4. Insulation...........................................................................................................................................22

20. Mechanical Data, Dimensions and Weights................................................................................................23 21. Ambient Conditions .....................................................................................................................................24

21.1. Operation...........................................................................................................................................24 21.2. Transport ...........................................................................................................................................24 21.3. Storage..............................................................................................................................................24

1KHW000892-EN Edition 2004-08-02 1 / 24

Technical Data NSD570 ABB Switzerland Ltd

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-multipoint for the protection of lines with T-offs

Communication medium analog and digital channels, fiberoptic 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

Number of NSD570 in one rack 1 or 2 Mix of analogue and digital 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

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 analogue, 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

1KHW000892-EN Edition 2004-08-02 2 / 24


Nominal transmission time T0 including operating times of the relay interface (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.

Channel

Bandwidth 1 single-tone

command (blocking only)

1 or 2 single-tone commands

1 or 2 dual-tone commands

1 to 3 dual-tone commands


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.

Required SNR (dB) for Pmc < 1% in 1.3 T0

Channel Bandwidth

1 single-tone command





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


Channel Bandwidth






B B P D B P D B P D B P D 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


Channel Bandwidth






B B P D B P D B P D B P D 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

1KHW000892-EN Edition 2004-08-02 3 / 24


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 free command allocation to one or more output contacts 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 (SDH), G.703.6 T1 interface: 1.544 Mbps (SONET) (RJ45 connector, 8 pole) 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 cables for G.703/E1/T1 RJ45 (8 pole, direct wire connection) 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 - permissive tripping 3 or 5 frames - direct tripping 4 or 6 frames Nominal transmission time T0 including operating time of the relay interface (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 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 Addressing facility range of digital terminal addresses 0 to 1023 Embedded Operation Channel (EOC) - 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

1KHW000892-EN Edition 2004-08-02 4 / 24


4. COMMON SYSTEM DATA

Device address range for connecting to PC via HMI 1 to 240 Send command pick up time programmable for each command 0 to 10 ms, step 1 ms (Tx Input Delay) compensation of sent commands duration equal to the pick-up time Received command prolongation programmable for each command 0 to 3 s, in steps of 1 ms (Rx Prolongation) default value for blocking 0 ms default value for permissive tripping 10 ms default value for direct tripping 100 ms Unblocking output Unblocking condition analogue 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 Extra output pick-up delay 0 ms to 100 ms, programmable in steps of 1 ms (default 5 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 are not influenced by the alarm (default)

- All outputs are forced into guard state - 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

Pick-up time 0 to 15 s, programmable in steps of 1 s (default 10 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 an unboosted tripping signal - 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 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

test success indication green Trip LED lights up for 3 seconds test failure indication red Fail LED flashes for 3 seconds HMI window displays actual transmission time (Tac) as 1⁄2 round trip time

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)

1KHW000892-EN Edition 2004-08-02 5 / 24


5. 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 - EOC communication only available between outer stations (“normal” T-operation) Transit delay NSD570 Analog for all bandwidths < 3 ms Transit delay NSD570 Digital for all interface types / data rates < 3 ms 1+1 protection - For path and equipment redundancy - Two NSD570 in the same rack serving two different communication channels - The command inputs/outputs of the two systems are connected in parallel ("first come, first served")

1KHW000892-EN Edition 2004-08-02 6 / 24


6. ANALOG 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

high-impedance 600 Ohm > 1.5 kOhm

Return loss (Rnom = 600 Ohm) 300 Hz … 500 Hz 500 Hz … 4 kHz

> 12.0 dB > 15.0 dB

Longitudinal conversion loss (compliant with TBR017)

300 Hz … 600 Hz 600 Hz … 3.4 kHz

> 40 dB > 46 dB

Balance-to-ground 300 Hz … 4 kHz > 40 dB Spurious emissions

< 8 kHz > 8 kHz

< - 38 dBm < - 56 dBm

Signal level single tones guard signal command signal (incl. power boosting)

- 24 dBm to + 2 dBm adjustable in steps of 1.0 dB - 24 dBm to + 11 dBm

Signal level dual tones (RMS) command signal (incl. power boosting) - 27 dBm to + 8 dBm Transmitter monitor level drop off - 3 dB to -10 dB

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

current polarity

max. 60 VDC max. 50 mA (limited) 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

high-impedance 600 Ohm > 1.5 kOhm

Return loss (Rnom = 600 Ohm) 300 Hz … 500 Hz 500 Hz … 4 kHz

> 12.0 dB > 16.0 dB

Longitudinal conversion loss (according to TBR017)

300 Hz … 600 Hz 600 Hz … 3.4 kHz

> 40 dB > 46 dB

Balance-to-ground 300 Hz … 4 kHz > 40 dB Received signal level nominal - 30 dBm to + 2 dBm

adjustable in steps of 1.0 dB Level monitor Lower and upper limit programmable ± 3 dB to ± 12 dB

adjustable in steps of 1.0 dB 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

1KHW000892-EN Edition 2004-08-02 7 / 24


7. DIGITAL LINE INTERFACES (G3LD)

Hardware release monitoring via HMI570

7.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)

Band B2 (3 kHz…20 kHz) < 0.25 UI < 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

20 Hz…600 Hz 3 kHz…20 kHz

> 1.15 UI > 0.25 UI > 0.05 UI

Return loss 4 kHz … 13 kHz 13 kHz … 256 kHz 256 kHz … 384 kHz

> 12 dB > 18 dB > 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 (using STP = Shielded Twisted Pair)

22 AWG (diameter 0.6438 mm = 0.3255 mm2)

500 m

Alarms: incoming signal level too low 4 x 8 = 32 following bits logical "1"

Loss Of Signal (LOS) Alarm Indication Signal (AIS)

Onboard Connector RJ45

1KHW000892-EN Edition 2004-08-02 8 / 24


7.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 HMI) 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 HMI) off (none), RD

Signal input (RD):

Bit rate 64 kbps or 56 kbps 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 HMI) off (none), RT, RD Clock tolerance when Rx clock is extracted from RD ± 100 ppm

Clock input transmitter (ST) and receiver (RT):

Bit rate 64 kbps or 56 kbps 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:

Shielding, cable screen to be earthed with metallic clamp on cable tray at rear side of rack Maximum cable length (using STP = Shielded Twisted Pair, 22 AWG)

Internal clock External clock

1000 m 500 m

Onboard Connector Sub-D, 25 pol, male, TIA/EIA-530-A (RS-530)

1KHW000892-EN Edition 2004-08-02 9 / 24


7.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 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. Signal output:

Bit rate 2048 kbps Tolerance of bit clock ± 50 ppm Output jitter amplitude Band B1 (20 Hz… 100 kHz)

Band B2 (18 kHz… 100 kHz) < 1.5 UI < 0.2 UI

Output impedance 120 Ohm Peak voltage of a pulse (Mark) 3.0 V Peak voltage without a pulse (Space) 0 ± 0.3 V

Signal input:

Bit rate 2048 kbps Tolerance of bit clock ± 50 ppm Return Loss 51 kHz … 102 kHz

102 kHz … 2048 kHz 2048 kHz … 3072 kHz

> 12 dB > 18 dB > 14 dB

Input jitter acceptance up to 1.67 Hz 20 Hz…2.4 kHz 18 kHz…100 kHz

> 18 UI > 1.5 UI > 0.2 UI

Input impedance 120 Ohm Peak voltage of a pulse (Mark) 3.0 V Peak voltage without a pulse (Space) 0 ± 0.3 V

Various:



1500 m

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) Status messages counted events per second code violations Invalid framing bits CRC failure

1KHW000892-EN Edition 2004-08-02 10 / 24


T1 Interface (1.5 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 timeslot 1 of the T1 frame. Signal output:

Bit rate 1544 kbps Tolerance of bit clock ± 32 ppm Output jitter amplitude Band B1 (10 Hz… 40 kHz)

Band B2 (8 kHz… 40 kHz) < 5 UI < 0.1 UI

Output impedance 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 Tolerance of bit clock ± 130 ppm Input impedance 100 Ohm Tolerance of input impedance ± 5 % Peak voltage of a pulse 3.6 V Minimum voltage of a pulse 2.4 V

Various:



2000 m

Data stream encoding/decoding configurable for AMI or B8ZS (default) Receiver sensitivity configurable for max. cable attenuation 10 dB (short haul; default) 36 dB (long haul) Clock synchronisation Slave mode on receiving data - if no data is received (LOS) switches automatically to free running mode 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) - maximum synchronization delay 1.5 ms extended superframe (24 frames) additional transmission of CRC6 data (in order to detect transmission bit errors; remote alarm reception even with high BER) - maximum synchronization delay 6.125 ms 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) Status messages counted events per second code violations invalid framing bits CRC failures

1KHW000892-EN Edition 2004-08-02 11 / 24


7.4. Optical Interface (G1LO) Optional piggyback to be mounted on Digital Interface G3LD (configurable for Optical Direct Fiber and Optical FOX/OTERM operation; a special version of the module - configurable for IEEE C37.94 - is available on request). Hardware release monitoring via HMI570 Connector on piggyback: E2000/APC (others via adaptor)

Optical Direct Fiber and Optical FOX/OTERM Interface

Framing complies with ITU-T recommendation G.704 for Optical Direct Fiber and with FOX-6Plus for Optical FOX/OTERM 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 FOX/OTERM is selected. Signal output:

Wavelength 1310 nm Bit rate 2048 kBps Tolerance of bit clock ± 50 ppm Output jitter amplitude Band B1 (20 Hz… 100 kHz)

Band B2 (18 kHz… 100 kHz) < 1.5 UI < 0.2 UI

Optical output power Short haul Long haul

-22… -17 dBm -5… -1 dBm

Signal input:

Wavelength range Sensitivity < -32 dBm 850… 1550 nm Bit rate 2048 kbps Tolerance of bit clock ± 50 ppm Input jitter tolerance up to 1.67 Hz

20 … 2400 Hz 18 ... 100 kHz

> 18 UI > 1.5 UI > 0.2 UI

Receiver input sensitivity < -36 dBm Receiver saturation power > - 1 dBm

Various:

Maximum cable length 9 µm singlemode fiber (acc. G.652) 50 µm multimode fiber (acc. G.651)

50 km 25 km

Data stream encoding/decoding CMI Clock synchronization Slave mode On receive data - if no data is received (LOS) switches automatically to free running mode 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

1KHW000892-EN Edition 2004-08-02 12 / 24


Optical IEEE C37.94 Interface

Framing, jitter performance and alarm handling comply with IEEE C37.94. Data is transmitted in the first 8 data bits of the IEEE C37.94 frame. Signal output:

Wavelength 850 nm Bit rate 2048 kbps Tolerance of bit clock ± 100 ppm Output jitter amplitude < 0.2 UI Optical output power -16… -11 dBm

Signal input:

Wavelength range Sensitivity < -32 dBm 850… 1550 nm Bit rate 2048 kbps Tolerance of bit clock ± 100 ppm Input jitter tolerance > 0.1 UI Receiver input sensitivity < -32 dBm Receiver saturation power > - 1 dBm

Various:

Maximum cable length 50 µm multimode fiber (acc. G.651) 3.5 km Data stream encoding/decoding NRZ Clock synchronization Slave mode On receive data - if no data is received (LOS) switches automatically to free running mode 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 According to IEEE C37.94 256 bits with 16 bit header, 48 bit overhead and 192 bit payload. Alarms Too few transitions Loss Of Signal (LOS) All one condition Alarm Indication Signal (AIS) Optical budget including aging 10 dB

1KHW000892-EN Edition 2004-08-02 13 / 24


8. RELAY INTERFACE (G3LR)

Hardware release monitoring via HMI570 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 % Input voltage ranges 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

Operating thresholds input operates at:

Jumpers Voltage .A + .B 10 … 15 VDC .A + .C 25 … 30 VDC .A + .D 70 … 80 VDC

Contact burden input current 10 … 20 mA for nominal battery voltage 24 VDC 5 … 10 mA Operating time < 750 µs, 450 µs typical Overvoltage protection 400 VDC

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 5 min./15 min. ≤ 2 A; Continuous ≤ 1 A

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)

1KHW000892-EN Edition 2004-08-02 14 / 24


Operating time < 8 ms (typ. 5 ms)

Bounce < 1 ms (typ. 0.2 ms)

Reset time < 4 ms (typ. 3.6 ms)

Overvoltage protection 400 VDC

9. POWER SUPPLY (G3LH)

- Only one type for all specified voltages - 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

Inrush current limitation on primary side approx. 4.7 A

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 Power consumption for 48 VDC nominal battery voltage: 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. per additional supply module G3LH 3 W max. per additional analog interface G3LA 3 W max. per additional digital interface G3LD 3 W max. per additional relay interface G3LR 1 W max. optional LAN Interface G3LL 10 W max. optional E1/T1 interface G1LE 0.5 W max. optional optical interface G1LO 1.5 W max. optional display panel G1LC 1.5 W max. optional input tripping voltage G1LR 1 W max. Onboard Connector: H 15 (DIN 41612)

1KHW000892-EN Edition 2004-08-02 15 / 24


10. COMMON INTERFACE (G3LC)

Hardware release monitoring via HMI570 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 Protocoll 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. 5 ms) Bounce < 1 ms (typ. 0.2 ms) Reset time < 4 ms (typ. 3.6 ms) Overvoltage protection 400 VDC 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. no. of NSD570 in local station network 32 Synchronization of Real Time Clock (RTC; on line interface) One input for IRIG-B synchronization signal One input for external second impulses (GPS) – TTL

1KHW000892-EN Edition 2004-08-02 16 / 24


IRIG-B input:

Synchronization signal format IRIG-B unmodulated 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.5V ... + 0.8 V (TTL) Input “HIGH” + 2V … + 7 V Input resistance ≥ 1 kOhm Over voltage protection ± 5 VDC Reverse polarity protection Yes Precision of synchronization ± 0.5 ms

11. BUS PLANE WITH FRONT COVER (G1LA)


12. SUPPLY BACKPLANE (G1LB)

Power supply connectors Fast-On 6.3 mm AC: L / N / PE, DC: + / - / PE

13. INTERNAL TRIPPING VOLTAGE (G1LR)

Optional piggyback module to be plugged onto G3LR. 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 chapter on EMC)

14. LCD DISPLAY PANEL (G1LC)

Optional front panel (instead of Blanking Cover Plate), 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). 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

1KHW000892-EN Edition 2004-08-02 17 / 24


15. LAN INTERFACE DATA (G3LL)

Ethernet 10/100BaseT interface that allows to connect 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) max. cable length 500 m Ethernet LAN interface type Ethernet 10/100 BaseT electrically compliant with IEEE 802.3 10BASE-T IEEE 802.3 100BASE-TX cable S/UTP (Screened / Unshielded Twisted Pair) or S/STP (Screened / Shielded Twisted Pair) Ethernet cable, category 5 or higher max. cable length 100 m On-board server architecture PC/AT compatible computer PC/104 ROM type 128 MB Compact Flash Card 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 16. HMI570 USER INTERFACE

16.1. HMI570 „LAN“

The “HMI570 LAN” requires a NSD570 LAN Interface (G3LL) Browser front end Internet Explorer, Netscape, Mozilla standards: HTTP/1.1, HTML 4 Access to the system remote

Requirements for remote access installation on PC/notebook HTTP 1.1 browser and IP connection to the LAN interface type G3LL of NSD570 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 access 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 Remote access facilities - intranet/internet using IP with embedded web server on LAN interface type G3LL, 10/100BaseT (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 analogue interface G3LA line impedance (2 jumpers)

1KHW000892-EN Edition 2004-08-02 18 / 24


16.2. HMI570 „PC“ Browser front end Internet Explorer, Netscape, Mozilla standards: HTTP/1.1, HTML 4 Hardware requirements (minimal) PC/notebook, x86 compatible CPU ≥ Pentium III CPU clock ≥ 400 MHz RAM ≥ 128 Mbyte free harddisk space ≥ 50 Mbyte SVGA, resolution ≥ 1024 x 768, 256 colors operating system Windows NT/2000/XP Access to the system local and remote

Requirements for local access installation on PC/notebook Browser plus 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 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 and remote access facilities - serial cable at 9600 bps, 19200 bps, 57600 bps - embedded operation channel (EOC) at 100 bps max (NSD570 analog) or at 1000 bps (NSD570 digital) 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 analogue interface G3LA line impedance (2 jumpers)

1KHW000892-EN Edition 2004-08-02 19 / 24


17. ALARMS

Alarm sources readable via the HMI Tx signal level drop from nominal level - 3 dB to - 10 dB (programmable, 1 dB steps) detection time < 1 s Rx guard signal level deviation from nominal level > ± 3 dB … ± 12 dB (programmable, 1 dB steps) detection time < 1 s SNR alarm threshold depending on command application setting (security): approx. Pmc < 1 % value detection time < 1 s BER alarm threshold setting via HMI570 1E-01 / 1E-02 / 1E-03 / 1E-04 / 1E-05 / 1E-06 (default) / 1E-07 / 1E-08 / 1E-09 detection time < 16 s (worst case) Wrong digital address detection time 2 frames Tx single component failure from relay interface instantaneous alarm Rx single component failure 2 criteria supervision guard and command signal state violation, Instantaneous alarm Tx command duration configurable for each command monitoring ENABLED or DISABLED if monitoring is enabled sending guard signal after programmable delay: 1 to 15 s (default 5 s) Rx output overload of solid-state command outputs instantaneous Checksum error external SDRAM / internal SRAM failure instantaneous Loop test error > 3 attempts System clock error CPU, Real Time Bus instantaneous General system error watchdog > 5 s 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 HMI 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 Hardware alarm general hardware failure alarms Link alarm indicates a link failure (SNR/BER, 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 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 relay pick-up delay 0 to 15 s (default 15 s) Alarm relay drop-off time 0 to 15 s (default 15 s) 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 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

1KHW000892-EN Edition 2004-08-02 20 / 24


18. 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 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 max. + 20 seconds per day

synchronized - on external GPS receiver (IRIG-B) - on external Pulses Per Second 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

19. ELECTROMAGNETIC COMPATIBILITY (EMC)

19.1. Electrical Safety Meets the safety requirements according to IEC 60950 / EN 60950

19.2. Emission The equipment meets the EMC requirements for emission EN 50081-2: 1993 (EN 55022 class A) Conducted emission 150 kHz to 30 MHz EN 55022 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 Class A

19.3. Immunity The equipment meets the EMC requirements for immunity EN 61000-6-2: 1999 Radiated electromagnetic field 26 to 1000 MHz, 80% AM, 1 kHz repetition rate IEC 61000-4-3 10 V/m Radiated electromagnetic field 1 … 2.5 GHz, 80% AM, 1 kHz repetition rate IEC 61000-4-3 10 V/m Electrostatic discharge (ESD) contact air discharge IEC 61000-4-2 8 kV 15 kV

1KHW000892-EN Edition 2004-08-02 21 / 24


Fast transient burst 1)

Surge immunity test

Conducted RF interference 2)

Damped oscillatory waves 3)

Conducted CM disturbance 4)

IEC 61000-4-4 IEC 61000-4-5 IEC 61000-4-6 IEC 61000-4-12 IEC 61000-4-16 Power Supply DC supply input ± 4 kV ± 4 kV CM

± 2 kV DM 10 V (e.m.f.) ± 2.5 kV CM

± 1.25 kV DM 30 V

AC supply input ± 4 kV ± 4 kV CM ± 2 kV DM

10 V (e.m.f.) ± 2.5 kV CM ± 1.25 kV DM

30 V

Analog Line Interface 2/4-wire ± 2 kV ± 2 kV CM 10 V (e.m.f.) ± 2.5 kV CM 30 V Boost output ± 2 kV ± 2 kV CM

± 1 kV DM 10 V (e.m.f.) ± 2.5 kV CM

± 1.25 kV DM 30 V

Digital Line Interface RS-422/RS-530 ± 2 kV ± 1.0 kV CM

± 1.5 kV CM 5)10 V (e.m.f.) ± 2.5 kV CM 30 V

G.703.1 ± 2 kV ± 1.0 kV CM ± 1.5 kV CM 5)

10 V (e.m.f.) ± 2.5 kV CM 30 V

E1/T1 ± 2 kV ± 1.0 kV CM ± 1.5 kV CM 5)

10 V (e.m.f.) ± 2.5 kV CM 30 V

Relay Interface Command Input ± 4 kV ± 4 kV CM

± 2 kV DM 10 V (e.m.f.) ± 2.5 kV CM

± 1.25 kV DM 30 V

Solid-state Output ± 4 kV ± 4 kV CM ± 2 kV DM

10 V (e.m.f.) ± 2.5 kV CM ± 1.25 kV DM

30 V

Relay Output ± 4 kV ± 4 kV CM ± 2 kV DM

10 V (e.m.f.) ± 2.5 kV CM ± 1.25 kV DM

30 V

Common Interface Alarm Relay Output ± 4 kV ± 4 kV CM

± 2 kV DM 10 V (e.m.f.) ± 2.5 kV CM

± 1.25 kV DM 30 V

RS-485 Station Bus ± 2 kV ± 1.0 kV CM ± 1.5 kV CM 5)

10 V (e.m.f.) ± 2.5 kV CM 30 V

NMEA/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 LAN Interface Ethernet ± 2 kV ± 1.0 kV CM

± 1.0 kV DM 10 V (e.m.f.) ± 2.5 kV CM

30 V

RS-485 Station Bus ± 2 kV ± 1.0 kV CM ± 1.5 kV CM 5)

10 V (e.m.f.) ± 2.5 kV CM 30 V

1) 5/50 ns, 5 kHz repetition rate 2) 0.15 to 80 MHz, AM 1kHz/80% 3) 1 MHz, 400 Hz repetition rate, 2 s burst duration 4) Continuous mode, frequency 50 Hz 5) Waveform 10/700 µs

19.4. Insulation Power frequency withstand test

Impulse Voltage

Insulation resistance (@500 VDC)

IEC 60255-5 IEC 60255-5 IEC 60255-5 Power Supply DC supply input 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 ± 2 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Ω 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Ω NMEA/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 Ethernet 1.0 kV ± 1 kV ≥ 100 MΩ RS-485 Station Bus 1.0 kV ± 1 kV ≥ 100 MΩ

1KHW000892-EN Edition 2004-08-02 22 / 24


20. MECHANICAL DATA, DIMENSIONS AND WEIGHTS

Weight basic version (rack, one supply module, one line interface, one relay interface): basic version analog (2 commands) 5.64 kg basic version digital (2 commands) 5.60 kg per additional supply module G3LH 0.60 kg per additional analog interface G3LA 0.26 kg per additional digital interface G3LD 0.18 kg per additional relay interface G3LR 0.22 kg optional LAN interface G3LL 0.32 kg optional E1/T1 interface G1LE 0.04 kg optional optical interface G1LO 0.10 kg optional display panel G1LC 0.15 kg optional input tripping voltage G1LR 0.02 kg Height 3 units high = 133.35 mm (1 unit = 44.45 mm) 4 units high = 177.8 mm (including labelling strip and cable tray) Overall depth 300 mm Installation width 482.6 mm (19'') Material side panels, cover plates hot-dip galvanized sheet horizontal rails extruded aluminium section Color RAL 7035 / Pantone 420 (light grey) IP protection degree of protection IP20 (according EN 60529 / IEC 60529) Equipment rack 19" wide conforming to standard DIN 41494 Dimension of modules (H x B x T) power supply unit 3U / 8R / 220 mm line and relay interfaces 3U / 6R / 220 mm LAN Interface 3U / 8R / 220 mm No. of slots power supply unit 2 line interfaces 2 relay interfaces 8 Backtracing all modules labelled with barcode module type and serial number Installation cabinet with hinged frame (typical) conforming to standard IEC 60297-3 or in a 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 7 to the power supply units via Faston connector 6.3 x 0.8 mm (DIN 4624) 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 7 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

1KHW000892-EN Edition 2004-08-02 23 / 24


21. AMBIENT CONDITIONS

21.1. Operation Climatic conditions Complies with IEC 60721-3-3 Class 3K5 Within specification Temperature range -5 to + 45 °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

21.2. Transport Climatic conditions Complies with IEC 60721-3-2 Class 2K4 Temperature range - 40 to +70 °C Relative humidity (non condensing) ≤ 95%, < 28 g/m3 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 (0.25 m/equipment packed) Complies with IEC 60068-2-32

21.3. Storage Climatic conditions Complies with IEC 60721-3-1 Class 1K5 Temperature range - 40 to + 70 °C Relative humidity (non condensing) ≤ 95%, < 28 g/m3 Mechanical conditions Complies with IEC 60721-3-1, Class 1M1 All technical data are subject to change without notice. ABB Switzerland Ltd Utility Communications CH-5400 Baden/Switzerland Call Center: +41 844 845 845 E-mail: [email protected] Internet: http://www.abb.com/utilitycommunications

1KHW000892-EN Edition 2004-08-02 24 / 24

ABB Switzerland Ltd 1KHW000894 Archive No.: Rev. Date: Software Installation Description: < HMI570 > - A 03-09-01

Responsible Department: Prepared: Approved: Distribution: Lang.: Page:

PTUKT2 02-10-01 sig. Schnyder 02-12-20 sig. Strittmatter - EN 1/4 Valid for: Derived from: Replaces: Classification-No.: File:

- - - -

We reserve all rights in this document and in the information contained therein. Reproduction, use or disclosure to

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 Technical data 2 2.3 Installation of the HMI570 2 2.4 Deinstallation 4 2.5 Updates 4

List of equipment:

PC with Windows NT / 2000 / XP HMI570 (Version 1.04 or higher)

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), 400 MHz 2. 128 MB of RAM 3. SVGA Controller with min. 1024 x 768 resolution and 256 colors 4. 50 MB of free disk space 5. CD ROM drive 6. Microsoft® Windows NT4, 2000 or XP 7. Web-browser supporting HTTP/1.1 and HTML 4 (Internet Explorer 5 and higher, Netscape 6

and higher, Mozilla 1.x) 8. 1 free serial port (RS-232)

third parties without express authority is strictly forbidden. © ABB Switzerland Ltd, Utility Automation Systems

Revision: Language: Page:

A EN 2/4 1KHW000894

2.2 Technical data

Java Virtual Machine (JVM) Version 1.3.1

2.3 Installation of the HMI570

An Installation Package is provided for Microsoft® Windows NT 4.0, 2000 and XP.

1. Insert the HMI570 CD into the CD-ROM drive.

2. Double-click on the “HMI570-install.exe” to start the installation.

3. A welcome window will appear. If you are running other programs at the moment, choose “Cancel” and close all other programs first, before starting the installation again. If no other applications are running, choose “Next” to continue the installation.

4. Choose the folder where the HMI570 should be installed in. To install to a different folder, either type in a new path or click on “Change” to browse for existing folder. Click on „Next“ to continue.


A EN 3/4 1KHW000894

5. Choose the shortcut folder. To install to a different folder, type in the path or select an

existing folder from the list. The shortcut will be used to start the HMI570. Continue with “Next”.

6. The installation program will now search for a Java Virtual Machine (JVM) on your system. This could take a few moments. The JVM has to be version 1.3.1_09. If one or several suitable JVMs were found, a list will be shown, where you can choose the JVM for the HMI570. Go on with “Next”.

If no JVM Version 1.3.1_09 could be found, the installer can install it automatically. Click on “Next” to install it. Already installed JVM of other versions - even newer ones - will not be affected.

Important: If you decide to install the JVM 1.3.1_9 of the installation package, do not change the installation path of the JVM. After the successful installation of JVM do not reboot the system, if a prompt window appears. Click on “No” and then the installation of the HMI570 will continue.

7. The current window shows a summary, which installation and shortcut folder you have chosen and where the JVM is or will be installed, depending on if a JVM was found or not. Click on “Next” to continue. The files will now be copied into the folders.

8. Click on “Finish” to complete the installation.


A EN 4/4 1KHW000894

2.4 Deinstallation

Start Settings Control Panel Add/Remove Software Choose HMI570 and click on „Add/Remove“

All the files and folders, that were installed, are being removed from your system. Only the files installed to the JVM folder and the JVM remain on the system.

2.5 Updates 1. Uninstall the old version of the HMI570

Start Settings Control Panel Add/Remove Software Choose HMI570 and click on „Add/Remove“

2. Install the new version of the HMI570 It is possible to install different version 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.

ABB Switzerland Ltd 1KHW000896 Archive No.: Rev. Date: Firmware Download Description: < NSD570 > - B 04-04-16



- - - -



Firmware Download Description: < NSD570 >

Contents:

1 Purpose of document 2 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 3

List of equipment:

PC with Windows NT / 2000 / XP HMI570 (Version 1.04 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.



B EN 2/3 1KHW000896

1 Purpose of document 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 and G3LD. 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.


B EN 3/3 1KHW000896

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_05.ldr

G3LD NSD570_Digital_Vx_yz.ldr NSD570_Digital_V1_23.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_23.ldr to a G3LA module.

3 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. Click Maintenance --> Firmware Download 5. Click the Browse button and a file selector window appears 6. Select the firmware file and click the Open button 7. Click the Download button 8. The firmware download will now take some minutes to complete.

Keep your hands away from keyboard and mouse while the download is in progress. 9. The following message informs about the success of the firmware download. 10. To activate the new firmware, the device must be reset

Click Maintenance --> Reset Device

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). Use the device address 255 instead. • After power up the equipment rack again it can take up to 15 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 device.

ABB Switzerland Ltd 1KHW000898-EN Archive No.: Rev. Date: Programming and Testing Instructions: < NSD570 > - B 04-04-16


PTUKT2 02-09-04 sig. Strittmatter 03-01-31 sig. Strittmatter - EN 1/37 Valid for: Derived from: Replaces: Classification-No.: File:

- - - -

Teleprotection Equipment: Series NSD570

Programming and Testing Instructions: < NSD570 >

This document describes programming and testing of the teleprotection equipment NSD570 Analog and NSD570 Digital, including the optical interface for the NSD570 Digital.

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 both types of equipment NSD570 Analog/Digital ...... 4 A.5 Settings for the analog line interface............................................................ 6 A.6 Settings for the digital line interface ............................................................. 8 A.7 Settings for the individual commands ........................................................ 10 A.8 Settings for the relay interface(s) ............................................................... 11 A.9 Alarm settings ............................................................................................ 13 A.10 Display Panel ............................................................................................. 14 A.11 LAN Interface ............................................................................................. 14 B Testing Instructions for the NSD570 Equipment........................................ 15 B.1 General....................................................................................................... 15 B.2 Check power supply................................................................................... 15 B.3 Preparing the equipment............................................................................ 16 B.4 Change configuration ................................................................................. 17 B.5 Remarks for T-operation ............................................................................ 18 B.6 Configure Real Time Clock (RTC) ............................................................. 18 B.7 Analog line interface................................................................................... 19 B.8 Digital line interface.................................................................................... 20 B.9 Relay interfaces ......................................................................................... 20 B.10 System alarm indication ............................................................................. 22 B.11 System functions........................................................................................ 22 B.12 Display Panel ............................................................................................. 23 B.13 LAN Interface ............................................................................................. 23 B.14 Concluding works....................................................................................... 24 Sheet NSD570 System Settings................................................................... A1 - A7 Sheet NSD570 System Test Report............................................................. B1 - B5

We reserve all rights in this document and in the information contained therein. Reproduction, use or disclosure to third parties without express authority is strictly forbidden. © ABB Switzerland Ltd, Utility Automation Systems


B EN 2/37 1KHW000898-EN

Basic test equipment

PC with Windows NT, 2000 or XP

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 Modem tester DT-24 (Acterna) or equivalent RS-232 interface tester DV-24 (Acterna) or equivalent Optical power meter 850 nm / 1310 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" 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. ETL500 series)


B EN 3/37 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 this 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 and digital system in the same rack is possible. Access to both systems is possible via the serial COM 1 interface on the frontpanel 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 or for the digital 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).


B EN 4/37 1KHW000898-EN

A.4 Common settings for both types of equipment NSD570 Analog/Digital

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 S282 K 6A) 72 - 250 VDC Circuit breaker B9AV (1KHL015999R0001, type S282 UC-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 and the NSD570 Digital 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) "Inverse T-Operation" For power lines with one or several teed terminals protected by a permissive (Inv Teed) overreach transfer tripping scheme

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 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: 10 ms, default NSD570 Digital: 5 ms Unblocking Pulse Duration configurable from 50 … 500 ms in steps of 1 ms;

default: 200 ms


B EN 5/37 1KHW000898-EN

A.4.5 Command outputs during link failure It can be programmed how the command outputs respond to a channel failure, i. e. to SNR/BER alarm or Rx level/Sync lost alarm and in case the AIS/LOS is received by the digital NSD570: - do not change: alarm does not influence the command outputs (default) - guard state: alarm sets command outputs to guard state - retain in state: the command outputs retain the status they had immediately prior to the alarm - set permissive and blocking to command state: alarm sets command outputs for direct

tripping to guard state and command outputs for permissive tripping or blocking to command state

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 seconds in steps of 1 sec

default: 10 sec Link failure hold time configurable from 0 …15 seconds 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), 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.

External Synchronization Signal (GPS Sync) 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 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


B EN 6/37 1KHW000898-EN

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:

Caution If connected to cables, pilot wires or leased circuits: This apparatus must only be used in conjunction with barrier transformers 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. 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).


B EN 7/37 1KHW000898-EN

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 to 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 to -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 to + 2 dBm in steps of 1 dBm (default: -6 dBm)

This leads to the following levels: -> single tone command signal - 24 dBm to + 11 dBm (incl. power boosting) -> dual tone command signals - 27 dBm to + 8 dBm (RMS; incl. power boosting)

Rx signal level (nominal) configurable from - 30 dBm to + 2 dBm in steps of 1 dBm (default: -6 dBm) Tx alarm (level drop off) configurable from - 10 dB to -3 dB in steps of 1 dB (default: -6 dB) Rx alarm (lower / upper limit) configurable from ± 3 dB to ± 12 dB in steps of 1 dB (default: ± 6 dB)

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.


B EN 8/37 1KHW000898-EN

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 FOX/OTERM, 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 16 seconds (short term average) and in 262 minutes (long term average).

BER Alarm Threshold (1E…) configurable for 1E-09, 1E-08, 1E-07, 1E-06 (default) 1E-05, 1E-04, 1E-03, 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 to 1023 (default 341) Remote Digital Address configurable from 0 to 1023 (default 682)

A.6.2 G.703 codirectional interface 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 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"

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), the Rx Clock Sync and the Tx Clock Sync TT have both be programmed either to "RD" or both be programmed to "none".


B EN 9/37 1KHW000898-EN

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 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


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

For details refer to the Operating Instructions NSD570.

A.6.5 T1 interface 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.



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


B EN 10/37 1KHW000898-EN

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

For details refer to the Operating Instructions NSD570.

A.6.6 Optical interfaces 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. This is only applicable for the Optical Direct Fiber and the Optical FOX/OTERM interface, as the laser output power of the Optical IEEE C37.94 interface cannot be varied.


A.6.7 Grounding the shield of optional connecting cables The cable shield of the optional connecting cables for the Digital Interface type G3LD 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.

A.7 Settings for the individual commands

A.7.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). 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 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.7.2 Tx Trip Duration Monitoring For each command a Tx trip duration monitoring can be programmed to OFF (default) or ON, 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 Trip Duration configurable from 1 … 15 seconds in steps of 1 sec (default: 5 seconds)


B EN 11/37 1KHW000898-EN

A.7.3 Tx input command delay Warning: If an input command 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 command delay configurable from 0 …10 ms in steps of 1 ms (default 0 ms)

A.7.4 Rx command prolongation A command prolongation ensures a steady output command 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 separately.

Rx command prolongation configurable from 0 … 3000 ms in steps of 1 ms Default Blocking 0 ms Default Permissive Tripping 10 ms Default Direct Tripping 100 ms

A.8 Settings for the relay interface(s) 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 signalling 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" in the corresponding configuration list of the HMI570.

A.8.1 Configuration of the inputs Each of the configured commands can individually be mapped on one or several inputs. The inputs can also be configured as "not used" (if, for example, three commands has to be transmitted using two relay interfaces).


B EN 12/37 1KHW000898-EN

A.8.2 Configuration of the solid state and relay outputs The following signals can individually be mapped on 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 has 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) - 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

A.8.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:

• 24 VDC … 48 VDC

• 60 VDC … 110 VDC

• 125 VDC … 250 VDC (default setting)

jumper plugs 1A and 1B for input 1 jumper plugs 2A and 2B for input 2 jumper plugs 1A and 1C for input 1 jumper plugs 2A and 2C for input 2 jumper plugs 1A and 1D for input 1 jumper plugs 2A and 2D 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.8.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.


B EN 13/37 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.8.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.9 Alarm settings

A.9.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.8.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 seconds in steps of 1 sec. (default 15 sec) Alarm hold time configurable from 0 … 15 seconds in steps of 1 sec. (default 15 sec)

A.9.2 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.9.3 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. 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 Local - SNR / BER Remote


B EN 14/37 1KHW000898-EN

A.10 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 ABB 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.11 LAN Interface The optional LAN Interface G3LL 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 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 LAN Interface G3LL. There is a special document available that describes the programming, testing and commissioning of the LAN Interface G3LL (please refer to 1KHW001289 “Commissioning Instructions LAN Interface G3LL” in the annex of the Operating Instructions NSD570).


B EN 15/37 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

DANGER Check the wiring of protective earth to the equipment. 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.

DANGER 48 VDC and higher battery voltages are hazardous. Beware of electric shock. 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 G3LH. It must be in the range from 48 VDC to 250 VDC (± 20 %) for nominal battery voltage and from 100 VAC to 240 VAC (-15%, +10%) for nominal mains voltage 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.


B EN 16/37 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, chapter 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 NSD570 in the left rack half (TPE 1); type "246" in the Local Device Address entry field when you want to connect to the NSD570 in the right rack half (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. 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). 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.


B EN 17/37 1KHW000898-EN

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) 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 or optical terminals back-to-back (cross-connected) or via the communication channel (e. g. PLC equipment ETL or digital multiplexer equipment FOX).

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, chapter "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.


B EN 18/37 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.11.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.11.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.

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 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.


B EN 19/37 1KHW000898-EN

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 - Remove the command signal from the command inputs

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):

- Switch off the EOC (if it is enabled) - Measured guard level = [ Rx level according setting ± 2 ] dBm - Switch on the EOC again, if requested


B EN 20/37 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) 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 The optical power meter must be sensitive to a wavelength of 1310 nm for the Optical Direct Fiber and the Optical FOX/OTERM 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

The optical power meter must be sensitive to a wavelength of 850 nm for the Optical IEEE C37.94 interface. A multi mode adapter cable has to be used for connecting the power meter to G1LO. The optical output power is measured as follows:

- Measured output power = [ -16 … -11 ] dBm

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 FOX/OTERM 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

The optical receiver sensitivity for the Optical IEEE C37.94 interface can be measured as follows: - Measured maximum attenuation > 10 dB

B.8.3 Address check This test is only necessary for high performance measurements or a custom 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 Relay interfaces


Designation Meaning (T.22/..1) Connector 1 of terminal block connected to rack position N22


B EN 21/37 1KHW000898-EN

B.9.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 (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.9.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 can not 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)

Note: This test is only necessary for the Rx commands. Other signals on the outputs must only be monitored for high performance measurements or a custom approval of the equipment.

Precise measurement of the programmed alarm delay times is not necessary - only operating of the contact shall be monitored.


B EN 22/37 1KHW000898-EN

B.10 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.11 System functions

B.11.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).

B.11.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 has to be added to the nominal transmission time.

B.11.3 Command prolongation time This test is only necessary for high performance measurements or a custom approval of the equipment. 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.


B EN 23/37 1KHW000898-EN

B.12 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 7. Press the “Enter” button -> MAIN MENU / Trip Counter 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) 9. Press the “Loop Test” button of the TPE 2 device in the rack -> after some seconds LOOP

TEST TIME / TPE 2 ….. ms will appear 10. Continuously press the “Back” button for more than 6 seconds -> the display panel will reset,

the backlight will go off and the ABB intro will restart

B.13 LAN Interface A description of the test procedure can be found in 1KHW001289 “Commissioning Instructions LAN Interface G3LL” in the annex of the Operating Instructions NSD570.


B EN 24/37 1KHW000898-EN

B.14 Concluding works

B.14.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.14.2 Clear event recorder In the menu Event Recorder click on the link Clear Event Recorder.

B.14.3 Manual reset In the Maintenance menu click on the link Reset Device.

B.14.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.14.5 Documentation Create a printout of the active configuration data that was uploaded and saved to disk before (see B.14.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.14.6 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, G3LR (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), 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 (one or two modules) - Optional Display Panel G1LC (if it is mounted instead of the blanking cover plate)

B.14.7 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.

Revision: Language: Page: NSD570 System Settings B EN A1/A7 HE

No.

Function

Rack or module

Item to be programmed or

fitted

Selected alternative or setting

Remarks

A.1 General

A.2 Create a configuration for the equipment using the HMI570

[ ]

A.3 Check interfaces in the rack G7BI

left ∗ right *

A.3.1 Check position of interfaces [ ] [ ] front back A.3.2 Check presence of cover plates [ ] [ ]

A.4 Common settings for both types of equipment NSD570 Analog/Digital

Unit 1 Unit 2 A.4.1 Power supply G3LH [ ] [ ] Circuit breaker B9AS [ ] [ ] All voltages except Circuit breaker B9AV [ ] [ ] 72 - 250 VDC

A.4.2 Device identification

left * right *

Station Name G3LA/D ____________ [ ] [ ] HE Number G3LA/D ____________ [ ] [ ] Device address G3LA/D ID= ____/____ [ ] [ ]

A.4.3 Operating mode of the equipment

left * right *

Normal G3LA/D [ ] [ ] Default 1+1 G3LA/D [ ] T-operation G3LA/D [ ] Inverse T-operation G3LA/D [ ]

A.4.4 Unblocking

left * right *

Unblocking Extra Delay G3LA/D ____/____ [ms] [ ] [ ] Unblocking Pulse Duration G3LA/D ____/____ [ms] [ ] [ ]

left * right * A.4.5 Command outputs during link G3LA/D [ ] [ ]

Responding to channel failure G3LA/D

Command outputs not influenced G3LR [ ] [ ] Default Cmd. outputs set to guard state G3LR [ ] [ ]

Cmd. outputs retain in state G3LR [ ] [ ]

Direct = guard, others = command G3LR [ ] [ ]

Channel failure pick up time G3LA/D ____/____ [s] [ ] [ ] Channel failure hold up time G3LA/D ____/____ [s] [ ] [ ]

∗ "left" and "right" stands for NSD570 in the left half / right half of the rack (front view)

© ABB Switzerland Ltd, Utility Automation Systems Form 1KHW000898-EN Rev. 2004-04-16


No.

Function

Rack or module


fitted


Remarks

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

left * right * A.4.7 Embedded Operation Channel

(EOC) G3LA/D enabled

[ ] [ ]

left * right * A.4.8 Cyclic Loop Test G3LA/D

Interval enabled ____/____ [h] [ ] [ ]

A.5 Settings for the analog line interface

left * right * A.5.1 Barrier transformers G3LA installed [ ] [ ]

If connected to cables, pilot wires or leased circuits

left * right * [ ] [ ] A.5.2 Connection to the AF

communication circuits G3LA 2-wire

4-wire [ ] [ ] Default left * right *

[ ] [ ]

[ ]

A.5.3 Analog channel bandwidth G3LA Tx: _____ [Hz] Rx: _____ [Hz]

Tx: _____ [Hz] Rx: _____ [Hz] [ ]

left * right *

[ ] [ ]

[ ]

A.5.4 Analog channel center frequency G3LA Tx: _____ [Hz] Rx: _____ [Hz]

Tx: _____ [Hz] Rx: _____ [Hz] [ ]

No of cmds left * right *

1 single tone [ ] [ ] 2 single tone [ ] [ ] 2 dual tone [ ] [ ] 3 dual tone [ ] [ ]

A.5.5 Analog operating mode G3LA

4 dual tone [ ] [ ]

Default

left * right * A.5.6 Power boosting G3LA ____/____ [dB] [ ] [ ]

left * right * A.5.7 Unblocking threshold G3LA ___/___ [dBm0] [ ] [ ]



No.

Function

Rack or module


fitted


Remarks

left * right *

[ ] [ ]

[ ]

A.5.8 Signal and alarm levels G3LA Signal levels: Tx: ____ [dBm] Rx: ____ [dBm]

Tx: ____ [dBm] Rx: ____ [dBm] [ ]

left * right *

[ ] [ ]

[ ]

G3LA Alarm levels: Tx: - ____ [dB] Rx: ± ____ [dB]

Tx: - ____ [dB] Rx: ± ____ [dB] [ ]

Impedance left * right *

Tx: 600 Ohm [ ] [ ]

Tx: > 1.5 kOhm [ ] [ ]

Rx: 600 Ohm [ ] [ ]

A.5.9 Manual jumper settings G3LA

Rx: > 1.5 kOhm [ ] [ ]

Default Default

A.6 Settings for the digital line interface

A.6.1 Interface independent settings left * right *

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 left * right *

G.703 Tx Clock Sync G3LD None on Rx Signal

[ ] [ ]

[ ] [ ]

Default

A.6.3 RS-530 interface left * right *

Interface data rate G3LD 56 kbps 64 kbps

[ ] [ ]

[ ] [ ]

Default

Clock source for send data (SD) G3LD internal external ST

[ ] [ ]

[ ] [ ]

Default

Clock source for receive data (RD) G3LD internal external RT

[ ] [ ]

[ ] [ ]

Default

If no external ST is available: Rx Clock synchronization

G3LD on RD none

[ ] [ ]

[ ] [ ]

Default

If no external RT is available: Tx Clock & TT synchronization

G3LD on RD none

[ ] [ ]

[ ] [ ]

Default

Terminal Timing (TT) signal G3LD off on

[ ] [ ]

[ ] [ ]

Default

If two NSD570 in a link are operated point-to-point (without MUX)

G3LD Master Slave

[ ] [ ]

[ ] [ ]



No.

Function

Rack or module


fitted


Remarks

A.6.4 E1 interface left * right *

Receiver sensitivity G3LD/ G1LE

Short haul Long haul

[ ][ ]

[ ] [ ]

Default

Internal elastic Rx buffer size G3LD/ G1LE

1 Frame 2 Frames 96 Bit Bypass

[ ][ ][ ][ ]

[ ] [ ] [ ] [ ]

Default

Internal elastic Tx buffer size G3LD/ G1LE


[ ][ ][ ][ ]

[ ] [ ] [ ] [ ]

Default

E1 Coding G3LD/ G1LE

HDB3 AMI

[ ][ ]

[ ] [ ]

Default

E1 Frame Format G3LD/ G1LE

Double Frame CRC4 Multi Fr.

[ ][ ]

[ ] [ ]

Default

A.6.5 T1 interface left * right *

Receiver sensitivity G3LD/ G1LE


[ ][ ]

[ ] [ ]

Default

Internal elastic Rx buffer size G3LD/ G1LE


[ ][ ][ ][ ]

[ ] [ ] [ ] [ ]

Default

Internal elastic Tx buffer size G3LD/ G1LE


[ ][ ][ ][ ]

[ ] [ ] [ ] [ ]

Default

T1 Coding G3LD/ G1LE

B8ZS AMI

[ ][ ]

[ ] [ ]

Default

T1 Frame Format G3LD/ G1LE

4 Frames Ext. Super Fr.

[ ][ ]

[ ] [ ]

Default

A.6.6 Optical interface left * right *

Receiver sensitivity (Optical Direct Fiber or Optical FOX/OTERM only)

G3LD/ G1LO


[ ][ ]

[ ] [ ]

Default

A.6.7 Grounding the shield of optional connecting cables

left * right *

Proper grounding at the cable tray G3LD Earth clip [ ] [ ]




fitted

A.7 Settings for the individual commands

A.7.1 Command Application Command A B C D E F G H

Not used G3LA/D TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Blocking G3LA/D TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Permissive Tripping G3LA/D TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Direct Tripping G3LA/D TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Not used G3LA/D TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Blocking G3LA/D TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Permissive Tripping G3LA/D TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Direct Tripping G3LA/D TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

A.7.2 Tx Trip Duration Monitoring Command A B C D E F G H

Monitoring enabled G3LA/D TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Maximum trip duration [s] G3LA/D TPE 1 __ __ __ __ __ __ __ __

Monitoring enabled G3LA/D TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Maximum trip duration [s] G3LA/D TPE 2 __ __ __ __ __ __ __ __

A.7.3 Tx input command delay Command A B C D E F G H

Delay before sending [ms] G3LA/D TPE 1 __ __ __ __ __ __ __ __

Delay before sending [ms] G3LA/D TPE 2 __ __ __ __ __ __ __ __

A.7.4 Rx command prolongation Command A B C D E F G H

Rx Prolongation [ms] G3LA/D TPE 1 __ __ __ __ __ __ __ __

Rx Prolongation [ms] G3LA/D TPE 2 __ __ __ __ __ __ __ __

A.8 Settings for the relay interface(s)

A.8.1 Configuration of the inputs Command A B C D E F G H

Mapping according setting G3LR TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Mapping according setting G3LR TPE 2 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

A.8.2 Configuration of the solid state and relay outputs

Command A B C D E F G H

Cmd mapping acc. setting G3LR TPE 1 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Cmd mapping acc. setting G3LR 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 [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]




fitted

A.8.3 Nominal input voltage 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

A.8.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.8.5 Relay contacts Relay 1 contacts G3LR ext. connecting N34 N40 N46 N52 N64 N70 N76 N84 Normally open NO [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] Normally closed NC [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

Relay 2 contacts G3LR ext. connecting N34 N40 N46 N52 N64 N70 N76 N84

Normally open NO [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] Normally closed NC [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]

No.

Function

Rack or module


fitted


Remarks

A.9 Alarm settings

A.9.1 Alarm pick up and hold delays left * right *

Alarm pick up time G3LA/D ____/____ [s] [ ] [ ] Alarm hold up time G3LA/D ____/____ [s] [ ] [ ]

A.9.2 Alarm relay contacts G3LC ext. connecting left * right *

Normally open NO [ ] [ ] Normally closed NC [ ] [ ]

A.9.3 Configuration of user alarms left * right *

User Alarm 1 G3LR acc. setting [ ] [ ] User Alarm 2 G3LR acc. setting [ ] [ ] User Alarm 3 G3LR acc. setting [ ] [ ]



No.

Function

Rack or module


fitted


Remarks

A.10 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.11 LAN Interface Settings acc. separate document G3LL 1KHW001289 [ ]


Revision: Language: Page: NSD570 System Test Report B EN B1/B5 HE

Test No.

Test procedure

Test point

Permissible value

Units

Test result

B.1 General

B.1.1 Test conditions Temperature range 20 … 35 ° C [ ]

B.1.2 Visual checks before powering the equipment

Correct wiring of protective earth G7BI PE wired [ ] Correct wiring of power supply G3LH (unit 1 / unit 2) polarity ok [ ] Equipment connected to adequate

voltage source Via circuit breaker B9AS or B9AV

[ ]

B.2 Check power supply Unit 1 Unit 2

DC battery voltage G3LH (+ to -) 38.4 … 300 V DC [ ] [ ] AC mains voltage G3LH (L to N) 85.0 … 264 V AC [ ] [ ] LED indication on the front panel G3LH (unit 1 / unit 2) green [ ] [ ]

B.3 Preparing the equipment left ∗ right *

B.3.1 Connecting to the equipment Check communication between PC & NSD570

TPE 1 /TPE 2 [ ] [ ]

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 [ ] [ ]

left * right * 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) left * right *

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)

left * right *

External sync pulse only Set time and date [ ] [ ] External GPS signal Adjust PC time / date Wrong time [ ] [ ] Set time and date [ ] [ ] Get time and date Actual / exact [ ] [ ] Adjust PC time / date Actual / exact [ ] [ ]




Test No.

Test procedure

Test point

Permissible value

Units

Test result

B.7 Analog line interface B.7.1 Transmitter left * right *

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 Command level G3LA; X100/1-2 [ setting ± 2 ] dBm [ ] [ ] Boost output activation G3LA; X100/5-6 with cmd. [ ] [ ]

B.7.3 Receiver Guard level G3LA; X100/3-4 [ setting ± 2 ] dBm [ ] [ ]

B.8 Digital line interface

B.8.1 Transmitter / Receiver left * right *

Communication established G3LD/G1LE/G1LO acc. interface [ ] [ ]

B.8.2 Optical output power / optical receiver sensitivity

left * right *

Output power (Optical Direct Fiber or Optical FOX/OTERM only)

G3LD/G1LO; X701/Tx [ -22 … -17 ] (short haul)

dBm (…..) (…..)

G3LD/G1LO; X701/Tx [ -5 … -1 ] (long haul)

dBm (…..) (…..)

Optical output power (Optical IEEE C37.94 only)

G3LD/G1LO; X701/Tx [ -16 … -11 ] dBm (…..) (…..)

Max. attenuation (Optical Direct Fiber or Optical FOX/OTERM only)

G3LD/G1LO; X701/Rx > 25 (long haul)

dB (…..) (…..)

Max. attenuation (Optical IEEE C37.94 only)

G3LD/G1LO; X701/Rx > 10 dB (…..) (…..)

B.8.3 Address check left * right *

Change device address G3LD/G1LE/G1LO Local alarm [ ] [ ]



Test No.

Test procedure

Test point

Permissible value

Units

Test result

B.9 Relay interfaces

B.9.1 Inputs

N34 N40 N46 N52 [ ] [ ] [ ] [ ] N64 N70 N76 N84

Input 1 Activate Input 1 Check LED Input 1

G3LR (T…/1) – (T.../2) LED Input 1

U1, see System settings ON

V DC

[ ] [ ] [ ] [ ]

N34 N40 N46 N52 [ ] [ ] [ ] [ ] N64 N70 N76 N84

Input 2 Activate Input 2 Check LED Input 2

G3LR (T…/3) – (T.../4) LED Input 1

U1, see System settings ON

V DC

[ ] [ ] [ ] [ ]

B.9.2 Outputs

N34 N40 N46 N52 [ ] [ ] [ ] [ ] N64 N70 N76 N84

Enforce action for Output 1 Check Output 1 Check LED Output 1

G3LR (T…/5) – (T.../6) LED Output 1

U1, see System settings closed ON

V DC

[ ] [ ] [ ] [ ]

N34 N40 N46 N52 [ ] [ ] [ ] [ ] N64 N70 N76 N84

Enforce action for Output 2 Check Output 2 Check LED Output 2

G3LR (T…/7) – (T.../8) LED Output 2


V DC

[ ] [ ] [ ] [ ]

N34 N40 N46 N52 [ ] [ ] [ ] [ ] N64 N70 N76 N84

Enforce action for Relay 1 Check Relay 1 Check LED Relay 1

G3LR (T…/9) – (T.../10) LED Relay 1


V DC

[ ] [ ] [ ] [ ]

N34 N40 N46 N52

[ ] [ ] [ ] [ ]

N64 N70 N76 N84

Enforce action for Relay 2 Check Relay 2 Check LED Relay 2

G3LR (T…/12) – (T.../13) LED Relay 2


V DC

[ ] [ ] [ ] [ ]

Test No.

Test procedure

Test point

Permissible value

Units

Test result

B.10 System alarm indication To be measured only if requested

left * right *

Activate alarm by interrupting receive line connection

LEDs "Local", "Receive"

LED to be ON [ ] [ ]

State of alarm relay after programmed delay

G3LC; X102/1-2 (left) and X102/6-7 (right)

changed [ ] [ ]

Deactivate alarm by restoring the link


LED to be OFF

[ ] [ ]



changed [ ] [ ]



Test No.

Test procedure

Test point

Permissible value

Units

Test result

B.11 System functions

B.11.1 NSD570 loop test left * right *

Check actual transmission time TLink

HMI570 / Loop Test Button

< 1.3*T0

ms

(………..)

(………..)

B.11.2 Command transmission time

left * right *

Command A Tx command A Rx command A

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)

Refer to manual for rated value Mean value ≤ T0

ms ms

_______ (………..)

_______ (………..)

Command B Tx command B Rx command B

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command C Tx command C Rx command C

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command D Tx command D Rx command D

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command E Tx command E Rx command E

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command F Tx command F Rx command F

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command G Tx command G Rx command G

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command H Tx command H Rx command H

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

B.11.3 Command prolongation time

To be measured only if requested

left * right *

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 (………..) (………..)



Test No.

Test procedure

Test point

Permissible value

Units

Test result

B.12 Display Panel left * right *

Connecting to the device G1LC <-> TPE 1/2 Counter readings [ ] [ ] Return information TPE1/2 -> G1LC Loop Test time [ ] [ ] Reset the display panel G1LC “Back” ABB intro [ ]

B.13 LAN Interface

Separate document G3LL<-> TPE 1/2 1KHW001289 [ ]

B.14 Concluding works left * right *

B.14.1 Reset counters Reset all counters HMI570 All counters = 0 [ ] [ ]

B.14.2 Clear event recorder Clear event recorder HMI570 1 event only [ ] [ ]

B.14.3 Manual reset Reset device HMI570 Reset / start up [ ] [ ]

B.14.4 Save the initial configuration data ex works

Upload/save config. HMI570 HExxxxxxBy.XML [ ] [ ]

B.14.5 Documentation View/print configuration HMI570 # printout pages (………..) (………..)

B.14.6 Collect back tracing data

Barcode reader G7BI, G1LA, G3LC, G1LB, G3LA, G3LD, G3LR, G3LL G1LE, G1LO, G3LH, G1LC

[ ] [ ]

B.14.7 Mount covers Rack G7BI Front and back [ ] [ ]

Company: _________________________________

Department: _________________________________

Date: _________________________________

Signed: _________________________________

Visa: _________________________________


ABB Switzerland Ltd 1KHW000900-EN Archive No.: Rev. Date: Commissioning Instructions: < NSD570 > - B 04-04-16


PTUKT2 02-09-04 sig. Maag 03-01-31 sig. Strittmatter - EN 1/14 Valid for: Derived from: Replaces: Classification-No.: File:

- - - -


Commissioning Instructions: < NSD570 >

This document describes commissioning of the teleprotection equipment NSD570 Analog and NSD570 Digital, including the optical interface for the NSD570 Digital.

Contents:

C Commissioning Instructions for the NSD570 Equipment............................. 3 C.1 General......................................................................................................... 3 C.2 Check power supply..................................................................................... 3 C.3 Preparing the equipment.............................................................................. 4 C.4 Change configuration ................................................................................... 4 C.5 Remarks for T-operation .............................................................................. 5 C.6 Configure Real Time Clock (RTC) ............................................................... 5 C.7 Analog line interface..................................................................................... 6 C.8 Digital line interface...................................................................................... 7 C.9 System alarm indication ............................................................................... 7 C.10 System functions.......................................................................................... 7 C.11 Display Panel ............................................................................................... 8 C.12 LAN Interface ............................................................................................... 8 C.13 Concluding works......................................................................................... 9 Sheet NSD570 Commissioning Report .......................................................C1 – C4



B EN 2/14 1KHW000900-EN


PC with Windows NT, 2000 or XP

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 similar

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 Modem tester DT-24 (Acterna) or equivalent RS-232 interface tester DV-24 (Acterna) or equivalent Optical power meter 850 nm / 1310 nm WWG OLP-16C or equivalent

Notes:






B EN 3/14 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 accommodate also 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. 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.

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.


C.2 Check power supply Check the auxiliary supply voltage at the inputs of G3LH. It must be in the range from 48 VDC to 250 VDC (± 20 %) for nominal battery voltage and from 100 VAC to 240 VAC (-15%, +10%) for nominal mains voltage 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).


B EN 4/14 1KHW000900-EN

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, chapter 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 NSD570 in the left rack half (TPE 1); type "246" in the Local Device Address entry field when you want to connect to the NSD570 in the right rack half (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, chapter "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, chapter "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.

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) 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 If it is necessary to change configuration parameters, refer to section 5 of the Operating Instructions NSD570, chapter "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.


B EN 5/14 1KHW000900-EN

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.10.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.10.3 of this Commissioning Instructions.

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.

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.


B EN 6/14 1KHW000900-EN

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):

- 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

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 - Remove the command signal from the command inputs

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):

- Switch off the EOC (if it is enabled) - Measured guard level = [ Rx level according setting ± 2 ] dBm - Switch on the EOC again, if requested


B EN 7/14 1KHW000900-EN

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) 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 input power The optical power meter must be sensitive to a wavelength of 1310 nm for the Optical Direct Fiber and the Optical FOX/OTERM 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 optical power meter must be sensitive to a wavelength of 850 nm for the Optical IEEE C37.94 interface. A multi mode adapter cable has to be used for connecting the power meter to G1LO. The optical output power is measured as follows:

- Measured output power = [ -16 … -11 ] dBm

The optical input power for all optical interfaces is measured as follows: - Measured input power = [ -36 … -1 ] dBm

C.9 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.10 System functions

C.10.1 Transmission Channel Check the transmission channel quality: measure the actual SNR/BER by clicking on the Upload Status link in the Status / Alarm menu.

C.10.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).


B EN 8/14 1KHW000900-EN

C.10.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.

C.11 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 7. Press the “Enter” button -> MAIN MENU / Trip Counter 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) 9. Press the “Loop Test” button of the TPE 2 device in the rack -> after some seconds LOOP

TEST TIME / TPE 2 ….. ms will appear 10. Continuously press the “Back” button for more than 6 seconds -> the display panel will

reset, the backlight will go off and the ABB intro will restart

C.12 LAN Interface A description of the commissioning procedure can be found in 1KHW001289 “Commissioning Instructions LAN Interface G3LL” in the annex of the Operating Instructions NSD570.


B EN 9/14 1KHW000900-EN

C.13 Concluding works

C.13.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.13.2 Clear event recorder In the menu Event Recorder click on the link Clear Event Recorder.

C.13.3 Manual reset In the Maintenance menu click on the link Reset Device.

C.13.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).

C.13.5 Documentation Create a printout of the active configuration data that was uploaded and saved to disk before (see C.13.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.13.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.13.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.

Revision: Language: Page: NSD570 Commissioning Report B EN C1/C4 HE

Test No.

Test procedure

Test point

Permissible value

Units

Test result

C.1 General

C.1.1 Test conditions Temperature range -5 … 45 ° C [ ]


Correct wiring of protective earth G7BI PE wired [ ] Correct wiring of power supply G3LH (unit 1 / unit 2) polarity ok [ ] Equipment connected to adequate

voltage source Via circuit breaker B9AS or B9AV

[ ]

Connection to protection devices Open or interrupted local / remote [ ]

C.2 Check power supply

Unit 1 Unit 2 DC battery voltage G3LH (+ to -) 38.4 … 300 V DC [ ] [ ] AC mains voltage G3LH (L to N) 85.0 … 264 V AC [ ] [ ] LED indication on the front panel G3LH (unit 1 / unit 2) green [ ] [ ]

C.3 Preparing the equipment left ∗ right *

C.3.1 Connecting to the equipment Check communication between PC & NSD570

TPE 1 /TPE 2 [ ] [ ]

C.3.2 Upload the configuration Upload of valid configu-ration successful

HExxxxxxBy.XML [ ] [ ]

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 [ ] [ ]

left * right * 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) left * right *

C.6.1 Setting real time clock Check PC time / date Actual / exact [ ] Set time and date [ ] [ ] Get time and date Actual / exact [ ] [ ]

C.6.2 Testing external real time clock synchronization (if available)

left * right *

External sync pulse only Set time and date [ ] [ ] External GPS signal Adjust PC time / date Wrong time [ ] [ ] Set time and date [ ] [ ] Get time and date Actual / exact [ ] [ ] Adjust PC time / date Actual / exact [ ] [ ]




Test No.

Test procedure

Test point

Permissible value

Units

Test result

C.7 Analog line interface C.7.1 Transmitter left * right *

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 (…..) (…..)

C.7.2 Power boosting / Boost output Command level G3LA; X100/1-2 [ setting ± 2 ] dBm [ ] [ ] Boost output activation G3LA; X100/5-6 with cmd. [ ] [ ]

C.7.3 Receiver Guard level G3LA; X100/3-4 [ setting ± 2 ] dBm [ ] [ ]

C.8 Digital line interface

C.8.1 Transmitter / Receiver left * right *

Communication established G3LD/G1LE/G1LO acc. interface [ ] [ ]

C.8.2 Optical output power / optical input power

left * right *

Output power (Optical Direct Fiber or Optical FOX/OTERM only)

G3LD/G1LO; X701/Tx [ -22 … -17 ] (short haul)

dBm (…..) (…..)

G3LD/G1LO; X701/Tx [ -5 … -1 ] (long haul)

dBm (…..) (…..)

Optical output power (Optical IEEE C37.94 only)

G3LD/G1LO; X701/Tx [ -16 … -11 ] dBm (…..) (…..)

Optical input power (Optical Direct Fiber or Optical FOX/OTERM only)

G3LD/G1LO; X701/Rx [ -36 … -1 ] dBm (…..) (…..)

Optical input power (Optical IEEE C37.94 only)

G3LD/G1LO; X701/Rx [ -32 … -1 ] dBm (…..) (…..)

Test No.

Test procedure

Test point

Permissible value

Units

Test result

C.9 System alarm indication To be measured only if requested

left * right *

Activate alarm by interrupting receive line connection


LED to be ON [ ] [ ]



changed [ ] [ ]

Deactivate alarm by restoring the link


LED to be OFF

[ ] [ ]



changed [ ] [ ]



Test No.

Test procedure

Test point

Permissible value

Units

Test result

C.10 System functions

C.10.1 Transmission Channel left * right *

Check actual trans-mission channel quality

HMI570 / Upload Status

BER (16 sec.) SNR

1E-0x x dB

(………..)

(………..)

C.10.2 NSD570 loop test left * right *

Check actual transmission time TLink

HMI570 / Loop Test Button

< 2*T0

ms

(………..)

(………..)

C.10.3 Command transmission time

left * right *

Command A Tx command A Rx command A

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)

Refer to manual for 2*rated value Mean value ≤ 2*T0

ms ms

_______ (………..)

_______ (………..)

Command B Tx command B Rx command B

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command C Tx command C Rx command C

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command D Tx command D Rx command D

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command E Tx command E Rx command E

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command F Tx command F Rx command F

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command G Tx command G Rx command G

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

Command H Tx command H Rx command H

Terminal, (T…/...) – (T.../…) (T…/...) – (T.../…)


ms ms

_______ (………..)

_______ (………..)

C.11 Display Panel left * right *

Connecting to the device G1LC <-> TPE 1/2 Counter readings [ ] [ ] Return information TPE1/2 -> G1LC Loop Test time [ ] [ ] Reset the display panel G1LC “Back” ABB intro [ ]

C.12 LAN Interface Separate document G3LL<-> TPE 1/2 1KHW001289 [ ]




Test No.

Test procedure

Test point

Permissible value

Units

Test result

C.13 Concluding works left * right *

C.13.1 Reset counters Reset all counters HMI570 All counters = 0 [ ] [ ]

C.13.2 Clear event recorder Clear event recorder HMI570 1 event only [ ] [ ]

C.13.3 Manual reset Reset device HMI570 Reset / start up [ ] [ ]

C.13.4 Save the configuration data

Upload/save config. HMI570 HExxxxxxCy.XML [ ] [ ]

C.13.5 Documentation View/print configuration HMI570 # printout pages (………..) (………..)

C.13.6 Mount covers Rack G7BI Front and back [ ] [ ]

C.13.7 Reconnect protection devices

Connection to protection devices

Closed or reconnected

local / remote

[ ] [ ]

Company: _________________________________

Department: _________________________________

Date: _________________________________

Signed: _________________________________

Visa: _________________________________

ABB Switzerland Ltd 1KHW000902-EN Archive No.: Rev. Date: Compatibility Requirements: < NSD570 > - E 04-12-20


PTUKT2 02-11-01 sig. M. Buhl 03-02-28 sig. M. Strittmatter - EN 1/8 Valid for: Derived from: Replaces: Classification-No.: File:

- - - -


Compatibility Requirements: < NSD570 > Contents:

1 Purpose of Document 1 2 General 1 3 Release and Version Management 1 4 Compatibility Rules 2 5 NSD570 Basic Equipment Analog/Digital 2 6 NSD570 Options 7

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.



E EN 2/8 1KHW000902-EN

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. Example: G3LR

• 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”. Example: 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) must have the identical version (valid only for firmware that can be downloaded, i.e. not applicable for the micro controller firmware!).

Caution There is no reliable operation possible when violating this rule!

• 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 NSD570 Basic Equipment Analog/Digital The NSD570 basic equipment consists of the following hardware, firmware and software versions:

Hardware Versions Description and update/upgrade information

G7BI Vers. 0 Initial version The back cover of Module Rack version “1” 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. 1 Actual version (identifiable by the additional ESD bonding point (EBP) on the left side of the earthing rail)

G3LH Vers. 1 Initial version (Power Supply G3LH version „0“ was not released and distributed)

G1LA Vers. 0 Initial version 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 Actual version


E EN 3/8 1KHW000902-EN


G1LB Vers. 0 Initial version 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)

G3LC Vers. 0 Initial version 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 Actual version

G3LA Vers. 0 Initial version 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 Minor layout redesign of the module for Digital Interface G3LD version “1”; the performance of the serial on-board interfaces RS-530 and G.703 was improved. 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 Actual version (also identified by new rubric of the board -> R0102)

G3LR Vers. 0 Initial version A FLASH memory has been replaced by a PROM in Relay Interface G3LR version “1” -> no specific action required. 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 Actual version

Note: All hardware versions can be viewed by means of the HMI570, except for: Module Rack G7BI, Supply Backplane G1LB, Power Supply G3LH.


E EN 4/8 1KHW000902-EN

Firmware Versions Description and update/upgrade information

NSD570 Digital Vers. 1.14

If the current version is less than 1.14 -> an update to the latest version is recommended at the earliest convenience (see remarks in “actual version”). If the current version is 1.14 -> 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”).


For this version the signal pulse shape of the T1 interface was slightly 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 remarks in “actual version”).


For this version the G.703 jitter performance was improved and the start 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 recommended e.g. during the next regular maintenance check (see remarks in “actual version”).


With this version also the optical interfaces of the optional module G1LO 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”).


For this version the “inverse T-operation” function was improved and the “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”).


This version also operates via “low-end” converters and communication 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”).


For this version the “normal T-operation” function was improved (reduced 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. If the features and modes mentioned above shall not be applied and the current version is 1.23 -> 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”).


Actual version With this version the loop test can also be performed while commands are 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 recommended e.g. during the next regular maintenance check. Ask your local representative for a free upgrade version of the “NSD570 Software & Documentation CD” including the actual NSD570 Digital 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).


E EN 5/8 1KHW000902-EN


NSD570 Analog Vers. 1.05

If the current version is less than 1.04 -> an update to the latest version 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”).


A “T-operation” with different center frequencies of send and receive 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”).


Actual version 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 recommended if the “retain in state” function is used. 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 firmware NSD570 Digital to the Digital Interface G3LD. The firmware versions can be viewed by means of the HMI570. The newest firmware version can always be used for updating an analog NSD570 link. The same applies for updating a digital NSD570 link, regardless which interface is operated (G.703, RS-530, E1, T1, optical).


G3LA/G3LD µC Vers. 1.03

If the current version is higher than 1.00 -> no specific action required. 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 µC Vers. 1.04

Actual version This version is only needed if the additional features of the Display Panel G1LC (with µC firmware Vers. 1.01) shall be utilized. In all other cases -> no specific action required (see µC Vers. 1.03)

G3LR FPGA Vers. 1.01

Actual version 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).


E EN 6/8 1KHW000902-EN

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 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.

Software Versions Description and update/upgrade information

HMI570 “PC” Vers. 1.03

If the current version is less than 1.03 -> an update to the latest version is recommended at the earliest convenience (see remarks in “actual version”). If the current version is 1.03 -> an update to the latest version is not immediately necessary but recommended (see remarks in “actual version”).


With this version also the optical interfaces of the optional module G1LO 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”).


Actual version The common functions and views of this version were synchronized to the HMI570 “LAN” version 1.11. Ask your local representative for a free upgrade version of the “NSD570 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 the “Software Installation Description HMI570” (1KHW000894).

Software Versions Description and update/upgrade information

HMI570 “LAN” Vers. 1.10

Initial version (runs on the optional LAN Interface type G3LL) The image file of this software is stored on a 256 MB compact flash card -> 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”).

HMI570 “LAN” Vers. 1.11

Actual version (runs on the optional LAN Interface type G3LL) 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. Ask your local representative for a free upgrade version of the “NSD570 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 according the “Copy Instructions NSD570 Compact Flash Card G3LL” (1KHW001291) and re-commission the LAN Interface G3LL according the “Commissioning Instructions NSD570 LAN Interface” (1KHW001289).

Note: The software version of the HMI570 can be viewed by clicking on the “About HMI570” link in the “HMI570 Options” menu.


E EN 7/8 1KHW000902-EN

6 NSD570 Options The NSD570 options consist of following hardware and firmware versions:


G1LE Vers. 0 Initial version 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. 1 Actual version

G1LR Vers. 1 Initial version (Internal Tripping Voltage G1LR version „0“ was not officially released)

G1LO Vers. 1 Initial version (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 requires Firmware NSD570 Digital Version 1.22 or higher and Software HMI570 Version 1.04 or higher.

G1LC Vers. 0 Initial version of the Display Panel type G1LC

G3LL Vers. 0 Initial version of the LAN Interface type G3LL

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).


E EN 8/8 1KHW000902-EN


G1LC µC Vers. 1.00

Initial version

G1LC µC Vers. 1.01

Actual version With this version a counter reset on the two line interfaces G3LA/D in the 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.

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 firmware version can be viewed by means of the Display Panel G1LC itself.

ABB Switzerland Ltd 1KHW000904-EN Archive No.: Rev. Date: Anomaly List: < NSD570 > - E 04-12-20


PTUKT2 03-02-25 sig. M. Buhl 03-02-28 sig. M. Strittmatter - EN 1/6 Valid for: Derived from: Replaces: Classification-No.: File:

- - - -



Anomaly List: < NSD570 >

Contents

1 Purpose of document 1 2 Anomalies 1

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 2

2.2 NSD570 Analog 3 2.2.1 Accuracy of signal to noise and level measurement 3

2.3 NSD570 Digital 3 2.3.1 Accuracy of bit error rate measurement 3 2.3.2 Interchanging the two digital line interfaces in the same rack 4 2.3.3 Command outputs during link failure 4 2.3.4 Using G.703 interface while Optical Interface G1LO is plugged onto G3LD 5 2.3.5 Start up problems of G.703 interface in self-loop configuration 5 2.3.6 Optical Interface G1LO with broken or disconnected optical fibers 5

2.4 HMI570 “LAN” 6 2.4.1 Communication between LAN interface and line interfaces 6 2.4.2 Menu item “View Configuration” 6

1 Purpose of document 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), 4th Edition (April 2004). 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).



E EN 2/6 1KHW000904-EN

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.11, 1.12, 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.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 -> 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)


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.

2.1.3 Configuration of individual relay interfaces per line interface


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).


E EN 3/6 1KHW000904-EN

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.1 Hardware, software and/or firmware versions G3LA, NSD570 Analog FW Vers. 1.05, 1.11, 1.12, HMI570 „PC“ SW Vers. 1.03, 1.04, 1.11 HMI570 „LAN“ SW Vers. 1.10, 1.11

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. 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.

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. 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.3 NSD570 Digital

2.3.1 Accuracy of bit error rate measurement

2.3.1.1 Hardware, software and/or firmware versions 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).


E EN 4/6 1KHW000904-EN

2.3.2 Interchanging the two digital line interfaces in the same rack

2.3.2.1 Hardware, software and/or firmware versions 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.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

2.3.3.1 Hardware, software and/or firmware versions 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.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 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).


E EN 5/6 1KHW000904-EN

2.3.4 Using G.703 interface while Optical Interface G1LO is plugged onto G3LD


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

2.3.5.1 Hardware, software and/or firmware versions G3LD, NSD570 Digital FW Vers. 1.32, HMI570 „PC“ SW Vers. 1.03, 1.04, 1.11, HMI570 „LAN“ SW Vers. 1.10, 1.11

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 start up 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


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 a “Remote Alarm” is received before the fibers are disconnected, the alarm will be kept (although no EOC signal is received).

- 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.


E EN 6/6 1KHW000904-EN

2.4 HMI570 “LAN”

2.4.1 Communication between LAN interface and line interfaces

2.4.1.1 Hardware, software and/or firmware versions G3LA, NSD570 Analog FW Vers. 1.05, 1.11, 1.12, G3LD, NSD570 Digital FW Vers. 1.14, 1.15, 1.16, 1.20, 1.22, 1.23, 1.31, 1.32, G3LL, HMI570 “LAN” SW Vers. 1.10, 1.11

2.4.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.4.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.

2.4.2 Menu item “View Configuration”

2.4.2.1 Hardware, software and/or firmware versions G3LA, NSD570 Analog FW Vers. 1.05, 1.11, 1.12, G3LD, NSD570 Digital FW Vers. 1.14, 1.15, 1.16, 1.20, 1.22, 1.23, 1.31, 1.32, G3LL, HMI570 “LAN” SW Vers. 1.10, 1.11

2.4.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.4.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

ABB Switzerland Ltd 1KHW001289-EN Archive No.: Rev. Date: Commissioning Instructions: < NSD570 LAN Interface > - _ 04-04-16



- - - -


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.2 Check power supply..................................................................................... 3 C.3 Preparing the equipment.............................................................................. 4 C.4 Physical connection to the LAN Interface .................................................... 4 C.5 Configure the networking parameters.......................................................... 6

Sheet NSD570 Commissioning Report .......................................................C1 – C2



_ EN 2/16 1KHW001289-EN


PC with Windows NT, 2000 or XP Commissioning PC

Ethernet cross connect cable SSH client Software SSH ® Secure Shell for Windows 3.0.0

(SSHWin-3.0.0)

Notes:



Caution During commissioning of the NSD570 LAN Interface, the networking parameters will be changed and stored in the Compact Flash card. A misconfiguration of this 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 with the Flash Card Copy Station, see “Copy Instructions Compact Flash Card G3LL” (1KHW001291). For commissioning of the NSD570 LAN Interface it is therefore highly recommended to take along the Flash Card Copy Station and the image file or at least a programmed Compact Flash card as spare part.




_ EN 3/16 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) 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.

C.1.1 Test conditions Temperature range: -5° C to 45° C. The connections for the tests can be made either directly at the rear of equipment (spring-clamp terminals and RJ45 socket) or at the terminals and sockets of the optional connecting cables.





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.


C.2 Check power supply Check the auxiliary supply voltage at the inputs of G3LH. It must be in the range from 48 VDC to 250 VDC (± 20 %) for nominal battery voltage and from 100 VAC to 240 VAC (-15%, +10%) for nominal mains voltage 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).


_ EN 4/16 1KHW001289-EN

C.3 Preparing the equipment

C.3.1 Install the SSH client software Before you can access a LAN Interface over an SSH connection it is necessary to install an SSH client on the PC. This has to be done only the first time. It is recommended to use the SSH ® Secure Shell application. Execute the file “SSHWinClient-3.0.0-build203.exe” to install this software on your PC. To be able to use the backspace key, it is necessary to change the following setting of the SSH Secure Shell application. Choose Edit – Settings – Keyboard and mark „Backspace sends Delete“.

C.4 Physical connection to the LAN Interface 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 an Ethernet patch cable (not a cross connect cable). Now it is possible to connect the LAN Interface from every PC that is connected to the Ethernet LAN.

EthernetEthernet

patch cable

Ethernet Switch / Hub

CommissioningPC

A Connect G3LL

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.


_ EN 5/16 1KHW001289-EN

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 (a normal patch cable will not work).

Ethernetcross connect cable

CommissioningPC

A Connect G3LL

C.4.3 Subnet Mask The Subnet Mask of the Commissioning PC must be configured to 255.255.255.0. The command „ipconfig“ in the DOS Box shows the settings (see below).

Change the Subnet Mask of the Commissioning PC The following steps show, how the Subnet Mask can be configured (Windows® 2000). Start Settings Network and Dial up Connections Local Area Connection Properties The window “Local Are 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 Subnet Mask can be configured.

Windows 2000 IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ##### IP Address. . . . . . . . . . . . : ##### Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : #####


_ EN 6/16 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 Reply from 172.20.162.54: bytes=32 time<10ms TTL=62 Reply from 172.20.162.54: bytes=32 time<10ms TTL=62 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 Configure the networking parameters

C.5.1 Establish an SSH connection There must be a SSH connection between the Commissioning PC and the NSD570 LAN Interface in order to set the following parameters: • Network parameters (IP Address etc.)

using the ctool • Time and date • Root password 1. Start the application „SSH Secure Shell Client“ 2. Press „Quick Connect“ in the menu bar

3. The Dialog Box “Connect to Remote Host” appears. Type in the currently configured IP Address

of the NSD570 LAN Interfaces (default is 172.20.162.54) in the field “Host Name” and “root” as “User Name”. Press the “Connect” Button.


_ EN 7/16 1KHW001289-EN

4. The first time you connect an NSD570 LAN Interface, 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.

5. Enter the password for the root user. The factory default for root password is “TfATEwimt5ya”

(first character of every word of the sentence “The first ABB Teleprotection Equipment was installed more than 50 years ago”).

6. 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 connections you are able to execute a number of Linux console commands. Do not execute any unknown commands because this could cause malfunction of the NSD570 LAN Interface.


_ EN 8/16 1KHW001289-EN

C.5.2 Connection termination An established connection can be terminated with „Disconnect” in the Menu “File”.

C.5.3 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.5.4 Networking Parameter

Note: The NSD570 LAN Interface 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 Compact Flash 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.


_ EN 9/16 1KHW001289-EN

C.5.4.1 DHCP or Static IP-Address

Selection: Press „1“ and Enter in the “Main Menu”

Function: The submenu allows to change 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. The NSD570 LAN Interface in DHCP mode will not start without the presence of a DHCP server.

C.5.4.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.5.4.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.5.4.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


_ EN 10/16 1KHW001289-EN

C.5.4.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.5.4.6 Domain Name


Function: Displays the currently configured Domain Name. Enter the new Domain Name

Default: noname.com

C.5.4.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.5.4.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. backupped configuration files, as described in Section 0) the use of the “SSH Secure File Transfer” is recommended instead.

C.5.4.9 System Logging Options

Selection: Press „9“ and Enter in the “Main Menu” - a submenu appears:


_ EN 11/16 1KHW001289-EN

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.5.4.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.5.4.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.5.4.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.5.4.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.5.4.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.5.4.9.6 Show Logging Status


Function: Displays if the logging is active at the moment and the logging settings after coming bootups.

C.5.4.9.7 Back to Main Menu


Function: Exits the Logging Submenu and displays the Main Menu again.

C.5.4.10 Local Backup

Selection: Press „10“ and Enter in the “Main Menu” Function: All files containing network configuration parameters will be copied into the backup directory

(”/ctool/backup”).


_ EN 12/16 1KHW001289-EN

C.5.4.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.

C.5.4.12 Set Time and Date


Function: Adjusts time and date. Enter new time and data in the following format. Values in [ ] are optional.

Format to use: MMDDhhmm[YYYY][.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.5.4.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.5.4.14 Reset LAN Interface


Function: Resets the LAN Interface

C.5.4.15 Exit ctool


Function: Exits the ctool

Note: Please note, you must reboot the NSD570 LAN Interface after changing the network settings.

C.5.5 Backup and restore of the network configuration parameters The files containing the NSD570 LAN Interface network configuration parameters can be backed up to the Commissioning PC and restored from there back to the NSD570 LAN Interface.


_ EN 13/16 1KHW001289-EN

C.5.5.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. 1. Establish a SSH connection to the LAN interface (see C.5.1) 2. Start ctool and execute “Local Backup” (see C.5.3) 3. Open an “SSH Secure File Transfer” Window

Window New File Transfer 4. Change to directory /ctool/backup and select all files, press right mouse button and Download to

the Commissioning PC

C.5.5.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. Establish a SSH connection to the LAN interface (see C.5.1) 2. Open an “SSH Secure File Transfer” Window

Window New File Transfer 3. Change to directory /ctool/backup, select all files and delete them 4. Press right mouse button and choose “Upload”. The “Upload – Select Files” window appears.

Select the files that shall be restored from the Commissioning PC to the NSD570 LAN Interface.


_ EN 14/16 1KHW001289-EN

5. Start ctool and execute “Local Restore” (see C.5.3) 6. The NSD570 LAN Interface must be rebooted after changing the network settings.

C.5.6 Change root password The linux root password is necessary to access the LAN Interface over an SSH connection. The factory default for root password is “TfATEwimt5ya” (first character of every word of 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.

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.5.7 Test HMI570 LAN functionality 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 LAN Interface G3LL and wait 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

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 (eg. http://172.20.162.54/hmi570/index.jsp).

4. Click „HMI570 ( Human Machine Interface )“

5. “Log In” with User name “Service” and Password “welcome”

6. Click “Connect Device” and the button “TPE 1”

7. “Device connected” must appear

8. Click “Configuration”, “Upload From Device”

9. “Configuration upload successful” must appear

10. Click “Exit HMI570”, press button „Exit“ and close the browser

Revision: Language: Page: G3LL Commissioning Report _ EN C1/C2 HE

Test No.

Test procedure

Test point

Permissible value

Units

Test result

C.1 General

C.1.1 Test conditions Temperature range -5 … 45 ° C [ ]


Correct wiring of protective earth G7BI PE wired [ ] Correct wiring of power supply G3LH (unit 1 / unit 2) polarity ok [ ] Equipment connected to

adequate voltage source Via circuit breaker B9AS or B9AV

[ ]

Connection to protection devices Open or interrupted local / remote [ ]

C.2 Check power supply

Unit 1 Unit 2 DC battery voltage G3LH (+ to -) 38.4 … 300 V DC [ ] [ ] AC mains voltage G3LH (L to N) 85.0 … 264 V AC [ ] [ ] LED indication on the front panel G3LH (unit 1 / unit 2) green [ ] [ ] LED indication on the front panel G3LH (unit 1 / unit 2) green [ ] [ ]

C.3 Preparing the equipment 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 Ethernet cross connect cable

[ ]

C.4.3 Subnet Mask Subnet Mask of the Commissioning PC

255.255.255.0.

[ ]

C.4.4 Ethernet connection test (ping) Ping test successful [ ]

C.5 Configure the networking parameters

C.5.4.1 DHCP or Static IP-Address Static IP Address DHCP

[ ] [ ]

C.5.4.2 IP Address (………..………..………..………..)

C.5.4.3 Subnet Mask (………..………..………..………..)

C.5.4.4 Default Gateway(s) (………..………..………..………..)

C.5.4.5 Computer Name (………..………..………..………..)

C.5.4.6 Domain Name (………..………..………..………..)


Revision: Language: Page: G3LL Commissioning Report _ EN C2/C2 HE

Test No.

Test procedure

Test point

Permissible value

Units

Test result

C.5.4.7 Domain Nameserver (DNS) (………..………..………..………..)

(………..………..………..………..)

(………..………..………..………..)

C.5.4.8 FTP Server ON/OFF FTP Server setting DISABLED [ ] C.5.4.9 System Logging Options Logging for all coming

bootups OFF [ ]

C.5.4.12 Set Time and Date Time and date correct? Ok [ ]

C.5.6 Change root password Root password changed? Ok [ ]

C.5.7 Test HMI570 LAN functionality HMI570 LAN running? Ok [ ]

Company: _________________________________

Department: _________________________________

Date: _________________________________

Signed: _________________________________

Visa: _________________________________


ABB Switzerland Ltd 1KHW001291-EN Archive No.: Rev. Date: Copy Instructions: < NSD570 Compact Flash Card G3LL > - _ 04-04-16


PTUKT2 04-04-06 sig. Braun 04-04-16 sig. Strittmatter - EN 1/14 Valid for: Derived from: Replaces: Classification-No.: File:

- - - -



Copy Instructions: < NSD570 Compact Flash Card G3LL >

Contents:

1 Purpose of document 2 2 FC CopyStation Driver and Application Installation on Microsoft® Windows 2

2.1 Manufacturer Information 2 2.2 Online Manual 2 2.3 System Requirements 2 2.4 Installation of FC CopyStation Driver and Software under Windows 2000 2 2.5 Installation of FC CopyStation Driver and Software under Windows XP 6

3 Utilization of the Altec “FlashCard CopyStation Mobile” 10 3.1 Connecting the Device 10 3.2 Starting the application program 10 3.3 Copying the CompactFlash contents into an image on the PC 10 3.4 Copying an image on the PC onto the CompactFlash 12 3.5 Verifying the contents of a CompactFlash towards an image file 13

List of equipment:

PC with Windows 2000 / XP Altec FlashCard CopyStation Mobile with included driver CD



_ EN 2/14 1KHW001291-EN

1 Purpose of document This document describes the driver and software installation of the “Altec FlashCard CopyStation Mobile” device (hereafter called FC CopyStation) and its usage to read and write images of CompactFlash cards.

2 FC CopyStation Driver and Application Installation on Microsoft® Windows

2.1 Manufacturer Information The FlashCard CopyStation Mobile is manufactured by altec ComputerSysteme GmbH. In case of problems with the installation and usage, their support may be of some help: altec ComputerSysteme GmbH Bayernstraße 10 30855 Langenhagen Germany www.altec-computersysteme.com Their technical support hotline is reachable under phone no. +49 (0)511-98381-70 on Monday through Friday from 11am to 3pm (CET) or over the email address [email protected]

2.2 Online Manual There is some online reference to the Flash Card Copy Station software, however much of the information there applies to the non-mobile version of the Flash Card Copy Station. You’ll find it in the Menu “Help” “Help topics” of the mobile Flash Card Copy Station application.

2.3 System Requirements IBM PC or 100% compatible computer, • Windows NT 4.0 SP 5 or later, Windows 2000 Professional, or Windows XP Professional • 64 MB RAM memory • 3 MB available hard disk space (plus additional for CF image files) • One unused PCMCIA slot

2.4 Installation of FC CopyStation Driver and Software under Windows 2000

The Installation Package works with Microsoft® Windows 2000 and XP. Some steps however differ, so the installation under the two operating systems is described separately from each other. 1. Insert the CD-ROM labelled “FlashCard CopyStation Mobile – Software & Driver” into the CD-

ROM drive.

2. Open the folder “english” on that CD-ROM and double-click on the file “setup.cmd”. A command window will pop up for a short time and display some status information about the installation (on your PC system this may be too quick to really see anything).

http://www.altec-computersysteme.com


_ EN 3/14 1KHW001291-EN

There is a shortcut to the FlashCardCopyStation program placed on the Windows desktop by the setup script.

There are installation instructions contained in this folder on the CD, however in most cases, what’s described there will not be enough to get the device running. Instead, there are some further steps necessary.

3. The name of the installed application should be cfcopy.exe, however it is cfcopy.exe.exe instead. Due to this it may be necessary to adjust the target of the shortcut on the desktop to the correct location (right-click on the shortcut, choose “Properties” and adjust the filename to cfcopy.exe.exe under “Target”, leave the path before as it is, so there should be an entry like “ “C:\Program Files\altec\FlashCardCopy\cfcopy.exe.exe” ”, note that the whole path has to stand in quotes “”).

4. Attach the cable with the PCMCIA-Adapter to the FC

CopyStation and plug it into the PCMCIA slot of your PC. Microsoft® Windows will discover the newly added hardware and install a “PCMCIA IDE/ATAPI” device driver for it. This, however, is not the correct driver for our device. We will deal with that issue as described in the following steps.

5. Right-click on “My Computer” and choose “Properties”. In the window, which opens up, switch over to the “Hardware” tab, there press the “Device Manager” button.


_ EN 4/14 1KHW001291-EN

6. As the window of the device manager opens up, find the “PCMCIA IDE/ATAPI Controller” in the “IDE ATA/ATAPI” section and choose “Properties” from the context menu (right-click on “PCMCIA IDE/ATAPI Controller”).

7. In that window switch over to the “Driver” tab, where you now press the “Update Driver...” button.

8. In the wizard that opens up, first click “Next >”. After that, you are given the choice of having the system search for a suitable driver or getting a list displayed to choose a driver from. Choose the second option (“Display a list of the known drivers for this device so that I can choose a specific driver”).


_ EN 5/14 1KHW001291-EN

9. After clicking “Next >”, in the following window a list of drivers will be displayed. Pick “mobile Flash Card Copy Station” from that list and click on “Next >” twice again.

10. The wizard will complain about not finding a digital signature for that driver. This is the normal behaviour and not to worry about (no signed driver exists for the device we are installing). Just click “Yes” to continue the installation.

11. After this a message will tell you to enter the CD labelled “FlashCardCopyStation Install Disk” into your CD-ROM drive. Do so and click the “OK” button.

12. Now the location of the file “cfcopy2k” is needed,

enter “<driveletter>:\english” (where “<driveletter>” is the letter of your CD-ROM drive) into the field “Copy files from” and click the “OK” button.

13. Now the new drivers are being installed. When done, you can click the “Finish” button to close the wizard.

Now the driver should be fully functional. A double click on the FlashCardCopyStation icon on the desktop should not generate any error messages.


_ EN 6/14 1KHW001291-EN

2.5 Installation of FC CopyStation Driver and Software under Windows XP

The Installation Package works with Microsoft® Windows 2000 and XP. Some steps however differ, so the installation under the two operating systems is described separately from each other. 1. Insert the CD-ROM labelled “FlashCard CopyStation Mobile – Software & Driver” into the CD-

ROM drive.

2. Open the folder “english” on that CD-ROM and double-click on the file “setup.cmd”. A command window will pop up for a short time and display some status information about the installation (on your system this may be too quick to really see anything).

There’s a shortcut to the FlashCardCopyStation program placed on the Windows desktop by the setup script.

There are installation instructions contained in this folder on the CD, however in most cases, what’s described there will not be enough to get the device running. Instead, there are some further steps necessary.

3. The name of the installed application should be cfcopy.exe, however it is cfcopy.exe.exe instead. Due to this it may be necessary to adjust the target of the shortcut on the desktop to the correct location (right-click on the shortcut, choose “Properties” and adjust the filename to cfcopy.exe.exe under “Target”, leave the path before as it is, so there should be an entry like “ “C:\Program Files\altec\FlashCardCopy\cfcopy.exe.exe” ”, note that the whole path has to stand in quotes “”).

4. Attach the cable with the PCMCIA-Adapter to the FC

CopyStation and plug it into the PCMCIA slot of your PC. Microsoft® Windows will discover the newly added hardware and install a “PCMCIA IDE/ATAPI” device driver for it. This, however, is not the correct driver for our device. We will deal with that issue as described in the following steps.


_ EN 7/14 1KHW001291-EN

5. Right-click on “My Computer” and choose “Properties”. In the window that opens up, on the “Hardware” tab, click the button “Device Manager”.

6. As the window of the device manager opens up, find the “PCMCIA IDE/ATAPI Controller” in the “IDE ATA/ATAPI” section and choose “Properties” from the context menu (right-click on “PCMCIA IDE/ATAPI Controller”).

7. Switch to the tab Driver and click on the button “Update Driver...”


_ EN 8/14 1KHW001291-EN

8. A wizard opens up. First click on “Next >”. Then you have to choose how to install the software. Here you should select the “Install from a list or specific location (Advanced)” option and click on “Next >”.

9. The following screen asks about search and installation options. Do not let Windows search for the “best driver” by itself, instead choose “Don’t search. I will choose the driver to install.” This is necessary because the driver provided on the Altec CD is not signed for Windows compatibility, so Windows will not choose that one by itself.

10. On the following screen, you get to pick the Driver you want to use. “mobile Flash Card Copy Station” is the choice to take. Then click “Next >”.


_ EN 9/14 1KHW001291-EN

11. Now Windows will complain that the chosen driver has not passed the Windows Logo testing to verify compatibility with Windows XP. This is normal and nothing to worry about. So click on the “Continue Anyway” button.

12. Next the program will ask you to enter the CD “FlashCardCopyStation Install Disk” into the CD-ROM drive. Do so and click “OK”. Hereafter you will be prompted for the location of the file “cfcopy2k.sys” on the CD-ROM. Enter <driveletter>:\english (where <driveletter> is the letter of your CD-ROM drive) into the field “Copy files from” and click the “OK” button.

13. Now the new drivers are being installed. When done, you can click the “Finish” button to close

the wizard.

Now the driver should be fully functional. A double click on the FlashCardCopyStation icon on the desktop should not generate any error messages.


_ EN 10/14 1KHW001291-EN

3 Utilization of the Altec “FlashCard CopyStation Mobile”

3.1 Connecting the Device The Altec “FlashCard CopyStation Mobile” consists of a box with two PCMCIA slots in the front, a cable with a PCMCIA adapter on one side, and two PCMCIA adapters for compact flash cards.

To connect the device, plug the cable into the socket in the back of the box and insert the PCMCIA adapter on the other side of the cable into the PCMCIA slot of your (notebook) PC.

3.2 Starting the application program The application program can be started by double-clicking onto the FlashCardCopyStation icon created on the desktop by the installation program. If there is any problem detecting the device (maybe it’s not plugged into the PCMCIA slot), an error message “Flash Card Copy Station Service not running !” will appear on startup. The same message also appears if the wrong driver is installed. So if everything seems connected correctly, but that message still appears on program startup, you might want to try again steps 5 through 13 of the installation instructions. If everything works correctly, the program window “mobile Flash Card Copy Station” will appear.

3.3 Copying the CompactFlash contents into an image on the PC 1. In the application window, there are two

buttons representing the two PCMCIA slots. After inserting the PCMCIA adapter with the CompactFlash into the upper slot of the CF CopyStation, the writing on the upper button should change from “No Card” to some information about what CompactFlash card was entered (e.g. SanDisk SDCFB).

Note: To copy data from a CompactFlash down to an image file, the source CompactFlash must be inserted into the upper slot! Otherwise it will not work. (The error “No Card Inserted !” will be displayed in a message dialog.) If there are two CompactFlash cards inserted, it will always read from the one in the upper slot.


_ EN 11/14 1KHW001291-EN

2. A click onto that button reveals some further information

about the CompactFlash card, as seen in the following picture.

3. To create an image file, you first

have to choose a filename. Click on the “Select” button right next to the field “Image File”. An “Open” window pops up where a file name can be entered or an existing image file can be chosen.

4. After the file name is entered, click on the “Open” button. If the

filename does not exit yet, you will be asked whether or not to create a file of that name. Choose “Yes”.

5. In the application window, the name of

the image file now is entered in the respective field. Now be sure to choose “Read Master” under “Action” and click on the “Start” button to get the copying process going.

6. After the “Progress” bar has filled up, a message box “Operation

successful!” appears on the screen indicating that the image file has been successfully written.


_ EN 12/14 1KHW001291-EN

3.4 Copying an image on the PC onto the CompactFlash The FlashCard CopyStation Mobile has two slots for PCMCIA cards with an inserted CompactFlash. They can both be used to copy an image onto a card – one or the other or both simultaneously. The image always is written to all the entered cards. 1. In the application window, there are

two buttons representing the two PCMCIA slots. After inserting the PCMCIA adapter with the CompactFlash into one of the slots of the CF CopyStation, the writing on the respective button should change from “No Card” to some information about what CompactFlash card was entered (e.g. SanDisk SDCFB).



3. First you have to select an image

file to read from. Click on the “Select” button right next to the field “Image File”. An “Open” window pops up where a file can be chosen.

4. After the file is chosen, click on the

“Open” button. In the application window, the name of the image file now is entered in the respective field. Now choose “Write all cards” under “Action” and click on the “Start” button to get the copying process going.


_ EN 13/14 1KHW001291-EN

Note: It is possible, to write the image of a CompactFlash of some size onto a CompactFlash of some larger size! For example, the image of a 64 MB CompactFlash card can be copied onto a card of 128 MB size. However, the question “One or more cards do not have correct capacity! Continue?” will be displayed and should be answered with “Yes”.

5. After the “Progress” bar has filled up, a message box “Operation

successful!” appears on the screen indicating that the contents of the image file have been successfully written onto the CompactFlash card(s).

6. In case the CompactFlash is worn out or damaged in some other way, the data written onto the

CompactFlash might not have been saved the right way. So it’s wise to verify at this point that the image data on the CompactFlash matches the contents of the image file. The following section covers how to do that.

3.5 Verifying the contents of a CompactFlash towards an image file Verifying ensures that the CompactFlash contains the exact data as found in the image file it’s compared to. This is especially helpful to check whether the image that has been written onto CompactFlash has been stored there correctly. The FlashCard CopyStation Mobile has two slots for PCMCIA cards with an inserted CompactFlash. They can both be used to verify an image with a card – one or the other or both simultaneously. The image always is compared to all the inserted cards. 1. In the application window, there are

two buttons representing the two PCMCIA slots. After inserting the PCMCIA adapter with the CompactFlash into one of the slots of the CF CopyStation, the writing on the respective button should change from “No Card” to some information about what CompactFlash card was entered (e.g. SanDisk SDCFB).




_ EN 14/14 1KHW001291-EN

3. First you have to select an image file to compare to. Click on the “Select” button right next to the field “Image File”. An “Open” window pops up where a file can be chosen.

4. After the file is chosen, click on the

“Open” button. In the application window, the name of the image file now is entered in the respective field. Now choose “Verify all cards” under “Action” and click on the “Start” button to get the copying process going.

5. The image file is compared to all entered CompactFlash cards. If they all match, a message box “Operation successful!” is shown on the screen. If at least one of the card contents does not match the image file, the message “Operation not Successful!” is displayed when done.

In case of two inserted CompactFlash cards the question remains, which card the error message applies to. The answer is given by the output on the buttons which represent the two PCMCIA slots. If the image and the CompactFlash contents do not match, the button will show the label “Comp Error”. If they match, the label will still contain the information about the type of flash card which is entered. For example, in the picture shown, the contents of the card in the upper slot did not match the image while the comparison for the lower slot resulted in a match.

Note: After the button label has changed to “Comp Error”, it will remain that way until a new CompactFlash is entered into the slot! So in case a verification process results in a mismatch and the image is afterwards written and compared once more, the label may still be “Comp Error” even though the image and the card contents now match. So in that case, before verifying again, remove and reinsert the CompactFlash, so the button label is set back to the card information.

ABB ABB Switzerland Ltd e-mail: [email protected] Utility Automation Systems LN : utilitycommunication@ABB_CH01 PTUAB Repair Center Fax: ++ 41 58 585 65 65 CH-5400 Baden / Switzerland Tel : ++ 41 58 589 37 35

Repair & Return Procedure

1) General All our equipment and parts are warranted against defects in material and workmanship for a period as agreed in the order or in the SERVICE CONTRACT. All faulty parts returned to us should have a FAULT REPORT. The Repair & Return Procedure have following benefit for you: N Quality of response N Single Point-of- Entry to ensure the process efficiency and reliability N Expedite service for all Service Contracts 2) Repair & Return Process AABBBB SSwwiittzzeerrllaanndd LLttdd CCuussttoommeerr UUttiilliittyy AAuuttoommaattiioonn SSyysstteemmss DDeepptt.. PPTTUUAABB // RReeppaaiirr CCeenntteerr 55440000 BBaaddeenn // SSwwiittzzeerrllaanndd

MMoodduulleess ffoorr RReeppaaiirr

1 . Send Modules with Fault Report (Please send a fax copy of the Fault Report to PTUKS to follow-up your delivery)

2 . Check the Modules and Repair Type (If Warranty Repair or Service Contract send

the modules to repair and fax an acknowledgement of receipt to customer. If Out of Warranty Repair send an offer to customer)

3 . Send an Offer to Customer (Within 5 working days after receiving faulty modules with fault report for Out of Warranty Repair)

4 . Send Formal Purchase Order

5. Repair of Modules

6. Delivery with Repair Report

(Invoicing in case of Out of Warranty Repair)

09.01.2004 Page 1 of 3 1KHM010296 RevE


Repair & Return Procedure (continued)

3) Guide to Complete Fault Report • Always ensure that a separate Fault Report form accompanies your material when it is returned to PTUAB. • Always fax copy of Fault Report to PTUAB to check the arrival of your delivery. • Always complete Section 2 - Fault Symptoms. • Always include the name and contact details of an engineer who can be contacted by the PTUAB repair

technicians to discuss technical issues relating to the fault. This information should be recorded at the bottom of the Fault Report form.

• Always record the serial number and the release number (if any) of your faulty module on the Fault Report. • Always record the contract number of SERVICE CONTRACT on the Fault Report • Advance Replacements

If you require an Advance Replacement please record this on the Fault Report form. A purchase order is required before the shipment of any Advance Replacement. The customer will be invoiced the full price for the advance replacement unit. Please also note that PTUAB does not guarantee that it will have replacement items available at all times, except for replacement on SERVICE CONTRACT.

• Unit for Checking This service will be charged with US$ 350.00 for each unit. 4) Purchase Order for Out of Warranty Repair After receiving modules with fault report we will repair the modules if it is under warranty or under Service Contract, otherwise we will send a quotation for the repair cost. No repairs will be commenced by PTUAB until a purchase order for the amount quoted for repair is received by PTUAB. All items received by PTUAB without a Fault Report Form and Purchase Order will be placed in Isolation and no repair actions will be commenced until all the above documentation is completed. 5) Packaging When packaging the item please use anti-static bags especially when using foam chips as packing material. Please ensure that the packaging is sufficient to protect the equipment from damage during shipment. Ideally, equipment should be returned in the same packaging it was supplied in. Any items that are received in a damaged condition, that appears to have arisen from inadequate packing, will be placed in Isolation until a new quote has been provided to you to cover repair of the additional damage and a purchase order is received by PTUAB.

09.01.2004 Page 2 of 3 1KHM010296 RevE


Fault Report

A separate “Fault Report” must be completed for each individual faulty item you intend to return to PTUAB.

Section 1: General Information Equipment Type: _____________________________________________ Module Type: _____________________________________________ Serial Number / Release Number_ _____________________________________________ PTUK Order No / Delivery date: _____________________________________________ Your Original PO No: _____________________________________________ Section 2: Fault Symptoms Problem Occurred: During Installation During Commissioning In Service Other:_____________________ Observed Faults: Overfunction Underfunction Outside tolerance

Abnormal temperature Sporadic error Unit for checking

Fault Description ; ____________________________________________________________________________________ ___________________________________________________________________________________________________ Section 3: Repair & Delivery Type

Out of Warranty Repair Expedited Repair Advanced Replacement

In-Warranty Repair Express Delivery Service Contract

Service Contract No. -----------------------

Section 4: Customer Address Customer’s delivery address for repaired items Customer Billing Address Company: ________________________________ Company: ________________________________

________________________________________ _________________________________________

Attn.: ___________________________________ ATTN: ___________________________________

Contact Tel No: __________________________ Contact Tel No: ___________________________

Contact Fax No: __________________________ Contact Fax No: ___________________________

Contact e-mail: __________________________ Contact e-mail: ___________________________ Section 5: Fault Report issued by: Company: ______________________________ Engineer's Name: _________________________ Contact Details:__________________ Date:_____________ (Phone /e-mail)

09.01.2004 Page 3 of 3 1KHM010296 RevE

NNEEEEDD SSUUPPPPOORRTT FFOORR YYOOUURR CCOOMMMMUUNNIICCAATTIIOONN SSYYSSTTEEMM??

ABB Switzerland Ltd 02-01-17

QQuueessttiioonnss,, TTeecchhnniiccaall SSuuppppoorrtt

11.. SSuuppppoorrtt rreeqquueesstt

CCuussttoommeerr SSuuppppoorrtt CCeenntteerr

uuttiilliittyyccoommmmuunniiccaattiioonn@@cchh..aabbbb..ccoomm oorr ++4411 884444 884455 884455

22.. FFoorrmmaall aacccceeppttaannccee ooff pprriiccee aanndd ddeelliivveerryy tteerrmmss

33.. SSeerrvviiccee ddeelliivveerryy

GGooaallss ooff tthhee pprroocceessss:: Quality of response Short response time to customers Clear pricing of services Single Point-of-Entry to ensure proce

1KHM010297Rev.A

ss efficiency and reliability

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. ABB Switzerland Ltd Utility Automation Systems Betreuung Dokumentation, PTU-BD1 Bruggerstrasse 72 CH-5401 Baden Telefax +41 58 585 35 82 ---------------------------------------------------------------------------------------------------------------

Concerns publication: 1KHW000890-EN (NSD570)

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! 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.

ABB Switzerland Ltd Utility Automation Systems Bruggerstrasse 72 CH-5400 Baden / Switzerland Phone +41 58 589 37 35 Fax +41 58 585 16 85 E-mail [email protected] www.abb.com/utilitycommunications

The IndustrialIT wordmark and all mentioned product names in the form XXXXXXIT are registered or pending trademarks of ABB.

Printed in Switzerland (0412-0000-0)

http://www.abb.com/utilitycommunications

[email protected]