Professional Documents
Culture Documents
Teleprotection System
p
Operating Instructions
2002 ABB Switzerland Ltd
Baden
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
7. Commissioning
9. Troubleshooting
11. Appendices
12. Annex
NSD570 1KHW000890-EN ABB Switzerland Ltd
September 2003
1. Introduction
1. Introduction
September 2003
2. Safety Instructions
2. Safety Instructions
Personnel qualification
An authorized and properly trained personnel only is
DANGER admitted to carry out installing, programming,
commissioning, maintenance, troubleshooting and
work of the equipment.
Instruction Manual
The Operating Instructions should be read and
DANGER clearly understood before working on the equipment.
Alteration
Alteration of the equipment is not allowed.
DANGER
Warning labels
Precautions and indications to hazardous voltages
DANGER and hazardous energy level must be strictly
observed.
Technical specifications
The equipment must be operated within the
DANGER technical specifications. Failure to do so may result
in personal injuries or equipment damage.
Alteration
Alteration of the equipment is not allowed.
DANGER
ESD protection
Mechanical Installation
The equipment must be mounted in a cabinet.
DANGER
Shipping
Electrical Installation
This is a Class Ι equipment specified in IEC 60950.
DANGER The equipment and the cabinet must be earthed.
The equipment must be supplied over circuit
breaker.
Back cover
Hazardous voltages and/or hazardous energy level
DANGER behind the back cover. Before removing the back
cover, the isolating terminals of the external cables
must be opened or the cables to the terminals must
be disconnected.
EMC
Laser / LED
Using HMI570
Commissioning
September 2003
3. System Description
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).
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.
al
op
an
an l
an al
l
op tal
a lo
a lo
di g
di al
ta
a lo
t ic
gi
tic
al
al
al
gi
gi
i
an
an
dig
an
o
t
o
og
ta
di
g
Protection Protection
commands commands
analog g
analo
Com.-Channels.vsd
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
OUTPUT
BOOST
Alarm 1
Alarm 2
(analog)
RELAY
INPUT
LINE
Laptop
Display Panel
G1LC Line Interface
Common
(analog, digital
Interface
or optical)
SYNC Relay Interface
GPS G3LA or G3LD G3LR
G3LC (or G3LD/G1LE or G3LD/G1LO) (or G3LR/G1LR)
Station
Supply
Bus Backplane
DC /
MAINS 1 Busplane (with Front Cover)
DC /
G1LB G1LA
MAINS 2
G3LH
G3LH
Power Supply 1
Power Supply 2
Line Interface
LAN Interface /
(analog, digital
Web Server
or optical)
Relay Interface
G3LA or G3LD G3LR
G3LL (or G3LD/G1LE or G3LD/G1LO) (or G3LR/G1LR)
G7BI
LAN
INPUT
LINE
OUTPUT
RELAY
BOOST
(analog)
G3LA, G3LD
G3LR, G3LL
Common Interface G3LC
Power Supply G3LH
Power Supply G3LH
G3LR
G3LR
G3LR
G3LR
G3LR
G3LR
G3LR
300 mm
PS2 PS1
POWER SUPPLY 1
POWER SUPPLY 2
X101
X100
X103
X102
X105 X104
PE PE
84 76 70 64 58 52 46 40 34 28 22 09 01
3-Rear View_Analog.vsd
PS2 PS1
X101
POWER SUPPLY 2
POWER SUPPLY 1
X101
X103
X201
X102
X105 X104
PE PE
84 76 70 64 58 52 46 40 34 28 22 09 01
EQUIPMENT 2 EQUIPMENT 1
3-Rear View_Digital.vsd
G3LR G3LR G3LR G3LR G3LD G3LR G3LR G3LA G3LC G3LH G1LB
PS2 PS1
X101
POWER SUPPLY 2
POWER SUPPLY 1
X101
X101
X101
X101
X101
X101
X100
X103
X201
X102
X105 X104
PE PE
84 76 70 64 58 52 46 40 34 28 22 09 01
EQUIPMENT 2 EQUIPMENT 1
3-Rear View_Mixed.vsd
PS2 PS1
X101
POWER SUPPLY 2
POWER SUPPLY 1
X101
X101
X101
X101
X101
X101
X101
X101
X100
X103
X201
X102
X101 X105 X104
PE PE
84 76 70 64 58 52 46 40 34 28 22 09 01
EQUIPMENT 2 EQUIPMENT 1
3-Rear View_Fully.vsd
Fig. 3.8 Fully equipped rack with redundant power supply units
RX_DATA2
2-wire communication bus for G1LC LCD-Display
TX_DATA2 12 V X101
extern 2
IRIG-B
IRIG-B
extern 2
GPS_SYNC
GPS_SYNC
TxD_RTB
RTB clock RxD_RTB
RTB & RTB
LOOP_DIS 8.192 MHz
frame sync
FS_RTB
3-Block-diagram-G3LC.vsd
SDRAM
Rx_Gain
X100/6
32
X100/3
x1 u1
RTC
Z
Slot-Coding
X100/1 Digital signal Data bus HW Version G3LC
24
processor In
u1 x1
HW Version G1LA
Z
Tx-Level
u1 x1
Buffer
8
+3.3 V DO
12 V 12 V DI
FS SPORT1 Reset
CLK
WD
3.3 V uC RS-232
SPORT0 Flag RS-485
Reset
+12 V
12 V 12 V
Supply 33 MHz
+12 V monitoring Serial-
Watchdog
-12 V FLASH
-12 V
Loop Test
Clk
RTB
Block-diagram-G3LA.vsd
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.
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.
SDRAM
DO
DI 32
FS
Signaling
from FPGA
CLK
In
5
buffer 24
RTC Sync_Bus
Line interface
Rx Data -
Codirectional
T+
T- 8
Signaling to
G.703
G.703
Tx Data + Slot-Coding
FPGA
RD-B ST
RS-422
RTB
Loop Test
Block-diagram-G3LD.vsd
12 V 3.3 V 1B
PROM 1C X101 / 2
12 V 1D Tx Input 1
1A
3.3 V 2.5 V
5V X101 / 1
Connector X100 to front plane bus
2B
2C X101 / 4
GND 2D Tx Input 2
3.3 V
2A
Supervision
X101 / 3
X101 / 6
Rx Output 1
Hardware release coding FPGA
3 (Xilinx Spartan II) X101 / 5
Slot coding
X101 / 8
Rx Output 2
4
SPORT0 X101 / 7
12 V
4
Loop disable
X101 / 9
Relay 1
LED X101 / 11
12 V
8 X101 / 10
X101 / 12
Relay 2
X101 / 14
X101 / 13
Block-diagram-G3LR.vsd
“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.
Up
Back Enter
Down
3.4.5.2.4. Reset
A Display Panel reset will occur if the Back button is permanently
pressed for more than 6 seconds.
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
| |
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
Available
Bandwidth Frequency
Amplitude
Guard Signal
Trip Signal
Available
Amplitude Bandwidth Frequency
Guard Signal
Trip Signal
F1 F2 F3 F4 F5 Frequency Time
Analog-operating-principle.vsd
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:
1200 Hz
3) 1500 Hz 3480 Hz
2400 Hz 960 Hz
0 0.3 0.5 1.0 1.5 2.0 2.5 3.0 3.4 3.96 kHz
Example_channel_allocation.vsd
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.
F1 F2 F3 Frequency
Calculation of frequencies:
F1 F2 F3 F4 F5 Frequency
Calculation of frequencies:
Available
Amplitude Bandwidth
F1 F2 F3 F4 F5 Frequency
Calculation of frequencies:
Available
Amplitude Bandwidth
F1 F2 F3 F4 F5 F6 Frequency
Calculation of frequencies:
Available
Amplitude Bandwidth
F1 F2 F3 F4 F5 F6 F7 F8 Frequency
Calculation of frequencies:
- blocking 2 or 3 frames
- permissive tripping 3 or 5 frames
- direct tripping 4 or 6 frames
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.
Tac
Local: Prolongation
G3LR Input
Remote:
G3LR Output
Command-prolongation.vsd
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.
Note: The Signal to Noise Ratio (SNR) and the Tx/Rx level
measurement displayed by the HMI570 do only have
an adequate accuracy if the EOC is switched off!
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
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.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.
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.
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.
Note: The local and remote trip counters will count the
sent/received commands as well.
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.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
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.
R R
MP1 A A MP1
MP2 B B MP2
Route 1 (e.g. Cable,
BFP C PLC, Radio, PCM) C BFP
GSD/LS D NSD570 NSD570 D GSD/LS
A A
B Route 2 (e.g. Cable, B
PLC, Radio, PCM) C
C
D NSD570 D
NSD570
MP1: 1st main protection GSD: generator shut down BFP: breaker failure protection
MP2: 2nd main protection LS: load shedding + overvoltage protection
R: protection relay + shunt reactor protection
3-Single-line2.vsd
R2 R1 R1 R2
MP1: 1st main protection R1/R2: protection relay BFP: breaker failure protection
MP2: 2nd main protection + overvoltage protection
+ shunt reactor protection
3-Dual-line2.vsd
A B
TX TX
TX TX
RX RX
RX RX
TPE 1 TPE 2
TX RX RX TX
TX RX 3-T-operation.vsd
A B
Local address: 15 Local address: 23
Remote address: 23 Remote address: 15
TX TX
TX TX
RX RX
RX RX
TPE 1 TPE 2
Local address: 15 Local address: 23
Remote address: 15 Remote address: 23
TX RX RX TX
TX RX Normal-T-operation-with-digital-addresses.vsd
A B
Local address: 15 Local address: 23
Remote address: 23 Remote address: 15
TX TX
TX TX
RX RX
RX RX
TPE 1 TPE 2
Local address: 23 Local address: 15
Remote address: 15 Remote address: 23
TX RX RX TX
TX RX Inverse-T-operation-with-digital-addresses.vsd
E E
T1 T2 T1 R2
S1 S2 S1 S2
R1 R2 R1 T2
Fig. 1 Fig. 2
3-Twin-line.vsd
September 2003
4.3. System requirements and technical data for the HMI570 ........ 4-4
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).
The HMI570 supports:
• Configuration of NSD570 systems
• Commissioning of NSD570 links
• Monitoring of NSD570 devices.
Parameter Setting
NSD570
TPE 1 TPE 2 TPE 1 TPE 2
100 101 120 121
NSD570 A1 NSD570 A2
RS232
Device
address
HMI570
4-Local-connection.vsd
Substation A Substation B
Station bus
NSD570
TPE 1 TPE 2 TPE 1 TPE 2 TPE 1 TPE 2
100 101 120 121 220 221
HMI570
4-Remote-connection.vsd
Device
address
LAN / WAN
Internet
HMI570
4-Remote-connection.vsd
Detailed instructions will follow how you can set this for the most
common browsers.
4.8. Operation
4.8.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.8.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).
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.8.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.
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:
Firmware download X
Change baud rate for device X
communication
Clear event recorder of device X
Download configuration to device X
Execute commissioning functions X
Local Connection:
The HMI570 PC/notebook is physically and logically connected to the
local NSD570.
4.8.8. Configuration
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.
Rack Assembly
Displays the type of the plugged components and boards.
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.
Note: The Signal to Noise Ratio (SNR) and the Tx/Rx level
measurement do only have an adequate accuracy if
the EOC is switched off!
4.8.11. Maintenance
If Maintenance is not accessible, maybe no device is connected (see
Section 4.8.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.8.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!
4.8.13.2. 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 or visit our website.
September 2003
5.7. Configuration notes for the digital NSD570 Digital ................. 5-14
5.7.1. Digital Channel selection ....................................................... 5-14
5.7.2. G.703 interface application notes .......................................... 5-14
5.7.3. RS-530 (RS-422/V.11) interface application notes ................ 5-16
5.7.3.1. Transmit and receive timing provided by the DCE................. 5-16
5.7.3.2. Transmit timing provided by the DCE .................................... 5-16
5.7.3.3. Transmit timing for the DCE provided by the G3LD ............... 5-17
5.7.3.4. Transmit and receive timing generated internally (G3LD)...... 5-18
5.7.4. E1/T1 interface application notes........................................... 5-19
5.7.4.1. E1 Interface ........................................................................... 5-19
5.7.4.2. T1 Interface............................................................................ 5-20
5.7.5. Optical interface application notes ......................................... 5-20
5.7.5.1. Optical Direct Fiber and Optical FOX/OTERM Interface ........ 5-20
5.7.5.2. Optical IEEE C37.94 Interface ............................................... 5-21
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.
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.
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.
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.
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.
Bandwidth Device 1 *1
120 Hz 240 Hz 360 Hz 480 Hz 960 Hz 1200 Hz
120 Hz 0 Hz
240 Hz 60 Hz 0 Hz
Bandwidth Device 2
360 Hz 60 Hz 60 Hz 0 Hz
480 Hz 120 Hz 60 Hz 60 Hz 0 Hz
960 Hz 180 Hz 180 Hz 120 Hz 120 Hz 0 Hz
1200 Hz 240 Hz 240 Hz 180 Hz 180 Hz 60 Hz 0 Hz
2400 Hz 480 Hz 420 Hz 420 Hz 360 Hz 300 Hz *2 240 Hz
2800 Hz 600 Hz 600 Hz 540 Hz *2 540 Hz
*1 The NSD570 channels with 2400 Hz and 2800 Hz bandwidth are not mentioned here because they can not
be combined with other 2400 Hz or 2800 Hz channels.
*2 Since the usable band for the NSD570 is from 300 to 4000 Hz, the resulting overall bandwidth of 3700 Hz
is exceeded with the required gap taken into account!
Table 5.1
Table 5.2
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.)
• the NSD570 receiver’s alarm pick-up level must be set to ± 12 dB
• the receive guard signal level must be set 6 dB lower than for 4-
wire operation; the resulting level margin before alarm release is
then 6 dB
• 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.
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 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.
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).
Transmitter
Receiver
5-G703-Appl-notes.vsd
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.
Transmitter
SD (Send Data)
ST (Send Timing)
Receiver
RD (Receive Data)
RT (Receive Timing)
Data Circuit-Terminating
Equipment (DCE)
RS-530 Interface G3LD
5-RS530-Appl-notes.vsd
Transmitter
SD (Send Data)
ST (Send Timing)
Receiver
RD (Receive Data)
Data Circuit-Terminating
RS-530 Interface on G3LD Equipment (DCE)
5-RS530-Appl_notes.vsd
Transmitter
SD (Send Data)
TT (Terminal Timing)
Receiver
RD (Receive Data)
Data Circuit-Terminating
RS-530 Interface on G3LD Equipment (DCE)
5-RS530-Appl_notes.vsd
Transmitter
SD (Send Data)
Receiver
RD (Receive Data)
Data Circuit-Terminating
RS-530 Interface on G3LD Equipment (DCE)
5-RS530-Appl_notes.vsd
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.
An internal elastic buffer size can be configured individually for the
input and the output circuits. This buffer may help to compensate clock
deviations or clock wander between the internal and the external
timing. Compensation of jitter and detection of slips is also possible by
means of a higher buffer size thus introducing a higher delay. A
compromise has to be found in actual tests with the used
communication equipment regarding high jitter capability versus low
additional delay.
The T1 coding (B8ZS or AMI) and frame format (4 frames or extended
superframe) can be configured to comply with different communication
system interfaces.
Device Information
Hardware Versions
Firmware Versions
Microcontroller 0.00
Digital Signal Processor 0.00
Device Identification
Common Settings
Analog Interface
Command Settings
Relay Interfaces
Alarm Settings
Jumper Settings
Analog Interface
Jumper Settings Impedance
Relay Interfaces
Jumper Settings Nominal Battery Voltage
Rack Assembly
Device Information
Hardware Versions
Firmware Versions
Microcontroller 0.00
Digital Signal Processor 0.00
Device Identification
Common Settings
Digital Interface
Command Settings
Relay Interfaces
Alarm Settings
Jumper Settings
Relay Interfaces
Jumper Settings Nominal Battery Voltage
Rack Assembly
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.
T0 = TI/O + Tg + Tev
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.
Puc = Nuc / NB
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%).
September 2003
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.
Mechanical installation
Back cover
Electrical Installation
Laser / LED
ESD protection
6.2.1. General
The aim is not just to install the equipment properly, but also to ensure
its long-term operational reliability. Strictly observe all safety
instructions during installation so that if damage does occur, warranty
and service rights do not become void.
6.3. Unpacking
6.4. Installation
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.5. Wiring
6.5.1. Introduction
While being installed, the equipment must be switched off and no
external connections may be made to it.
Note: Do not clamp more than one wire per terminal when
using screwless spring clamp type terminal blocks.
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.
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.2.
Power Supply 1:
DC+
AC L Positive battery pole DC supply
or AC Line supply
DC-
AC N Negative battery pole DC supply
or AC Neutral supply
PE
X103
G1LB
BACKPLANE
SUPPLY
G3LC
INTERFACE
COMMON
A
1
RS-485
1
B
2
GND
3
7
IRIG-B
4
+
5
-
GPS-SYNC
6
+
7
-
6-G1LB_Connector.vsd
Fig. 6.3 Connector for station bus and Real Time Clock
synchronization
SUPPLY
BACKPLANE
G1LB + - + -
X103 1 2 3 4 5 6 7
G1LB CABLE FOR
RTC SYNC/STATION BUS
Terminals
1 2 3 4 5 6 7 8
6-G1LB_Cable.vsd
X102
G3LC
INTERFACE
COMMON
1
NO
ALARM RELAY 1
2
C
1
ALARM RELAY 2
7
C
8
NC
6-G3LC_Connector.vsd
NO C NC NO C NC
X102 1 2 3 6 7 8
6-GL3C_Cable.vsd
X101
G3LR
RELAY
INTERFACE
JUMPER
1A+1D
1A+1C
1A+1B
G1LR
RELAY INTERFACE
G3LR CABLE FOR
125VDC...250VDC
60VDC...110VDC
External dry contact
24VDC...48VDC
U BAT nom.
(option)
G1LR
1A
1
-
1B
TX1
1C
1D
2
+
2A+2B
G1LR
1
INPUT
External dry contact
125VDC...250VDC
60VDC...110VDC
24VDC...48VDC
U BAT nom.
2A
3
-
2B
TX2
2C
2D
4
+
RX1
OUTPUT
6
+
7
-
RX2
8
+
9
NO
RX/REL1
10
C
11
NC
OUTPUT
14
12
NO
RX/REL2
13
C
14
NC
6-G3LR_Connector.vsd
G1LR
1D
1C
2C
2D
1A
1B
2A
2B
(option)
- + - + - + - + NO C NC NO C NC
X101 1 2 3 4 5 6 7 8 9 10 11 12 13 14
G3LR CABLE FOR
RELAY INTERFACE
BK BK BK BK BK BK BK BK BK BK BK BK BK BK GNYE
Terminals
1 2 3 4 5 6 7 8 9 10 11 12 13 14 PE
6-G3LR_Cable.vsd
X100
INTERFACE
ANALOG
G3LA
JUMPER OUTPUT
TB
TA
IMPEDANCE
X302
X301
>1.5kOhm
600Ohm
TA
TB
X303
TX-
AF
1 2
JUMPER
RB
RA
IMPEDANCE
X203 RB
X202
RA
>1.5kOhm
600Ohm
INPUT
X204
6
RX-AF
3
4
5
BOOST
6
6-G3LA_Connector.vsd
ANALOG RX-AF
IMPEDANCE TX-AF IMPEDANCE BOOST
INTERFACE
G3LA
X301 X202
TA RA
X302 X203
TB RB
X204
X303
JUMPER OUTPUT JUMPER INPUT
TA 600Ohm RA 600Ohm
TB >1.5kOhm RB >1.5kOhm
X100 1 2 3 4 5 6
G3LA CABLE FOR
ANALOG INTERFACE
WH BN GN YE GY PK
Terminals 1 2 3 4 5 6
6-G3LA_Cable.vsd
G3LD
INTERFACE
DIGITAL
X101
PE
1
1 SD-A
14
DATA
SEND
2
SD-B
14
DATA
RS-422 INTERFACE
3
RD-B
16
25 13 RT-A
9
TT-A
24
11 TT-B
ST-A
15
ST-B
12
SG
7
6-G3LD_Cable.vsd
PE
RD-A
RD-B
SD-A
SD-B
RT-A
RT-B
ST-A
ST-B
TT-A
TT-B
CHASSIS
GND
X101 1 2 14 3 16 17 9 24 11 15 12
G3LD*CABLE WITH
ISOLATING TERMINALS
WH BN GN YE GY PK BU RD BK VT
Terminals 5 6 1 2 3 4 9 10 7 8 PE
6-G3LD_Cable.vsd
PE
RD-A
RD-B
SD-A
SD-B
RT-A
RT-B
ST-A
ST-B
TT-A
TT-B
CHASSIS
GND
X101 1 2 14 3 16 17 9 24 11 15 12
G3LD*CABLE WITH
RS-449 INTERFACE
(37-P) WH BN GN YE GY PK BU RD BK VT
1 4 22 6 24 8 26 17 35 5 23
6-G3LD_Cable.vsd
PE
CHASSIS
RD-A
RD-B
SD-A
SD-B
RT-A
RT-B
ST-A
ST-B
TT-A
TT-B
GND
X101 1 2 14 3 16 17 9 24 11 15 12
G3LD*CABLE WITH
RS-530 INTERFACE (25-P)
WH BN GN YE GY PK BU RD BK VT
1 2 14 3 16 17 9 24 11 15 12
6-G3LD_Cable.vsd
PE
RD-A
RD-B
SD-A
SD-B
RT-A
RT-B
ST-A
ST-B
TT-A
CHASSIS
TT-B
GND
X101 1 2 14 3 16 17 9 24 11 15 12
G3LD*CABLE WITH
X.21 INTERFACE (15-P)
WH BN GN YE GY PK BU RD
1 2 9 4 11 7 14 6 13
6-G3LD_Cable.vsd
Fig. 6.15 G3LD cable with X.21 interface (male Sub-D connector
15 poles)
G3LD
INTERFACE
DIGITAL
G.703 CODIRECTIONAL INTERFACE
X201
DATA
6
+
RX
3
-
DATA
4
+
TX
5
-
2
1
7
8
8
6-G3LD_Cable.vsd
G3LD
INTERFACE
DIGITAL
(OPTION)
G1LE
X101
RL2
DATA
E1/T1 INTERFACE
RX
1
RL1
2
XL2
DATA
4
TX
XL1
5
3
7
8
8
1
6
6-G3LD_Cable.vsd
DIGITAL
INTERFACE
G1LE
(OPTION) E1/T1 INTERFACE
RJ45 Press-Fit
G3LD
RX TX 1 = RL2 1 = RL2
DATA DATA
2 = RL1 2 = RL1
3 3
4 = XL2 6
RL2
CHASSIS
5 = XL1 5 = XL1
RL1
XL2
XL1
GND
X101 1 2 4 5 3 7 8 6
6 4 = XL2
G3LD*CABLE FOR
G.703/E1/T1INTERFACE
(RJ45 connector 8 poles)
7 7
8 8
Press-fit
terminals 1 2 4 5 3 7 8 6
View of pins: top-down,
6-G3LD_Cable.vsd as real terminal strip
G3LD
INTERFACE
DIGITAL
E2000)
X701 (OPT. CONN.
(OPTION)
G1LO
RX
OPTICAL INTERFACE
TX
6-G3LD_Cable.vsd
DIGITAL G1LO
INTERFACE (OPTION) OPTICAL INTERFACE
G3LD
1) 1)
6-G3LD_Cable.vsd
1)
Optical cable type Connector
V9WP, V9WR E2000 – E2000
V9WQ, V9WS E2000 – FC/PC
Fig. 6.21 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.
Caution:
6.6. Photographs
Fig. 6.27 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.28 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).
September 2003
7. Commissioning
7. Commissioning
Personnel qualification
An authorized and properly trained personnel only is
DANGER admitted to carry out installing, programming,
commissioning, maintenance, troubleshooting and
work of the equipment.
Mechanical Installation
The equipment must be mounted in a cabinet.
DANGER
Warning labels
Precautions and indications to hazardous voltages
DANGER and hazardous energy level must be strictly
observed.
Back cover
Hazardous voltages and/or hazardous energy level
DANGER behind the back cover. Before removing the back
cover, the isolating terminals of the external cables
must be opened or the cables to the terminals must
be disconnected.
ESD protection
Laser / LED
Using HMI570
September 2003
Personnel qualification
Warning labels
Mechanical Installation
Back cover
ESD protection
Electrical Installation
Laser / LED
Using HMI570
8.2. Operation
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.
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.
Note: The Signal to Noise Ratio (SNR) and the Tx/Rx level
measurement do only have an adequate accuracy if
the EOC is switched off!
September 2003
9. Troubleshooting
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.
Personnel qualification
An authorized and properly trained personnel only is
DANGER admitted to carry out installing, programming,
commissioning, maintenance, troubleshooting and
work of the equipment.
Mechanical Installation
The equipment must be mounted in a cabinet.
DANGER
Back cover
Hazardous voltages and/or hazardous energy level
DANGER behind the back cover. Before removing the back
cover, the isolating terminals of the external cables
must be opened or the cables to the terminals must
be disconnected.
ESD protection
Using HMI570
Laser / LED
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
Remarks:
The following table lists the low level common alarms and the relay
interface alarms, and shows their influence on the high level alarms.
Interface)
Transmit
OK / Fail
Warning
Receive
Remark
Remote
System
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Local
Code
(Line
Link
HW
HW
Low Level Alarm
HW Release Common Interface and Bus Plane 0.20 X X X X OK
do not match
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
Error Relay Interface 3 TPE 2 (N76) 4) 0.13 OK
Error Relay Interface 2 TPE 2 (N70) 4) 0.12 OK
Error Relay Interface 1 TPE 2 (N64) 4) 0.11 OK
Error Relay Interface 4 TPE 1 (N52) 4) 0.10 OK
Error Relay Interface 3 TPE 1 (N46) 4) 0.9 OK
Error Relay Interface 2 TPE 1 (N40) 4) 0.8 OK
Error Relay Interface 1 TPE 1 (N34) 4) 0.7 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 1.28 X X X X Fail
failed
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 1.24 X X X X Fail
failed
Remote test mode active 1.21 X X X Flashing
Local test mode active 1.20 X X X Flashing
Wrong time from RTC 1.18 X X X OK
No signal (IRIG-B) on RTC 1.16 X X X OK
More Relay Interfaces configured than 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- 1.6 X X X X OK
defined state
Loop test error 1.5 X X X OK
Unblocking pulse 7) 1.4 OK
Interface)
Transmit
OK / Fail
Warning
Receive
Remark
Remote
System
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Local
Code
(Line
Link
HW
HW
Low Level Alarm
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
Comm. error Relay Interface 3 TPE 2 (N76) 4) 4.10 X X X OK
Comm. error Relay Interface 2 TPE 2 (N70) 4) 4.9 X X X OK
Comm. error Relay Interface 1 TPE 2 (N64) 4) 4.8 X X X OK
Comm. error Relay Interface 4 TPE 1 (N52) 4) 4.7 X X X OK
Comm. error Relay Interface 3 TPE 1 (N46) 4) 4.6 X X X OK
Comm. error Relay Interface 2 TPE 1 (N40) 4) 4.5 X X X OK
Comm. error Relay Interface 1 TPE 1 (N34) 4) 4.4 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
The following table lists the low level analog interface alarms, and
shows their influence on the high level alarms.
Interface)
Transmit
OK / Fail
Warning
Receive
Remark
Remote
System
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Local
Code
(Line
Link
HW
HW
The following table lists the low level digital interface alarms, and
shows their influence on the high level alarms.
Interface)
Transmit
OK / Fail
Warning
Receive
Remark
Remote
System
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Alarm
Local
Code
(Line
Link
HW
HW
Low Level Alarm
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
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).
Equipment A Equipment B
Channel A to B
9-Fault-location.vsd
Fig. 9.1 The four major fault location areas of an NSD570 link
Equipment A Equipment B
Error Relay Interface 2 TPE 2 (N70) 0.12 - Overcurrent in MOSFET output 2 (Alarm Code 0.19),
- Overcurrent in MOSFET output 1 (Alarm Code 0.18),
Error Relay Interface 1 TPE 2 (N64) 0.11
- Single component failure input 2 (Alarm Code 0.17),
Error Relay Interface 4 TPE 1 (N52) 0.10
- Single component failure input 1 (Alarm Code 0.16).
Error Relay Interface 3 TPE 1 (N46) 0.9
Follow the instructions given for these low level alarms.
Error Relay Interface 2 TPE 1 (N40) 0.8
Error Relay Interface 1 TPE 1 (N34) 0.7
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
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.
If persistent: replace the line interface.
Program memory internal CRC add. 1.28 Indicating a hardware defect of the DSP / SDRAM on the line
segment failed interface.
If persistent: replace the line interface.
SDRAM data memory check failed 1.26 Indicating a hardware defect of the DSP / SDRAM on the line
interface.
If persistent: replace the line interface.
Internal data memory check failed 1.25 Indicating a hardware defect of the DSP / SDRAM on the line
interface.
If persistent: replace the line interface.
Program Memory micro-controller CRC 1.24 Indicating a hardware defect of the micro-controller FLASH
check failed memory on the line interface.
If persistent: replace 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
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.
Tx continuous command H 4.19 The continuous command monitoring for the corresponding
Tx continuous command G 4.18 command (A … H) is enabled and the maximum duration as
configured by HMI570 has been exceeded. This error appears
Tx continuous command F 4.17
always in conjunction with the “Continuous command alarm”
Tx continuous command E 4.16 (Alarm Code 4.0).
Tx continuous command D 4.15 Verify that the continuous command monitoring / maximum
Tx continuous command C 4.14 duration of the corresponding command (A … H) as configured
Tx continuous command B 4.13 by HMI570 is correct or change the settings of the equipment
generating the command so that it is not longer than allowed.
Tx continuous command A 4.12
Comm. error Relay Interface 4 TPE 2 (N84) 4.11 Either the corresponding relay interface is not plugged, the
Comm. error Relay Interface 3 TPE 2 (N76) 4.10 relay interface is faulty or there is a problem with the connector
of the relay interface to the bus plane.
Comm. error Relay Interface 2 TPE 2 (N70) 4.9
Plug the relay interface or – if already plugged – check its
Comm. error Relay Interface 1 TPE 2 (N64) 4.8
connector to the bus plane. If the error persists, replace the
Comm. error Relay Interface 4 TPE 1 (N52) 4.7 relay interface. If this does not help, replace the module rack.
Comm. error Relay Interface 3 TPE 1 (N46) 4.6
Comm. error Relay Interface 2 TPE 1 (N40) 4.5
Comm. error Relay Interface 1 TPE 1 (N34) 4.4
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.
Table 9.6 Low level alarms with explanation and corrective actions
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.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: 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.
9.9. Support
Refer to document “1KHM010297 - Need Support for your Communi-
cation System?” in the Appendix.
September 2003
Personnel qualification
An authorized and properly trained personnel only is
DANGER admitted to carry out installing, programming,
commissioning, maintenance, troubleshooting and
work of the equipment.
Mechanical Installation
The equipment must be mounted in a cabinet.
DANGER
ESD protection
Electrical Installation
The circuit breaker for the power supply of the
DANGER equipment must be switched OFF.
The circuit breakers for optional equipment in the
cabinet must be switched OFF.
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.
September 2003
11. Appendices
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 / uC Micro Controller
HMI570 NSD570 User Interface Program
Basic Equipment
Module Rack
Display Panel
Power Supply
Interface Cards
Optional items
For cables Special screwdriver from PHOENIX CONTACT SZF 1 - 0,6 x 3,5
(for releasing the tension spring of the terminals) Order No. 12 04 51 7
11.3. Photographs
September 2003
12. Annex
Programming and
Testing Instructions NSD570 1KHW000898
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
- Configuration and monitoring of the opposite station from the local terminal
- Needs no additional bandwidth
- Operates in the guard channel
- Disabled during command transmission
- End-to-end operation for configurations with T-offs (“normal” T-operation)
Transmission rate NSD570 channel bandwidth data rate
120 / 240 / 360 Hz 20 bps
)
480 * / 960 Hz 50 bps
1200 / 2400 / 2800 Hz 100 bps
)
* 4 dual-tone commands in 480 Hz 20 bps
Required SNR > 6 dB
Nominal transmission time T0 including operating times of the relay interface (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.
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
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 connecting cables for G.703/E1/T1 RJ45 (8 pole, direct wire connection)
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
- Configuration and monitoring of the opposite equipment from the local terminal
- Needs no additional channel
- Available during guard and command state
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
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
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 ½ 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)
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 Digital for all interface types / data rates < 3 ms
1+1 protection
Transmitter:
Receiver:
Various:
Shielding, cable screen to be earthed with metallic clamp on cable tray at rear side of rack
Maximum cable length 22 AWG 500 m
2
(using STP = Shielded Twisted Pair) (diameter 0.6438 mm = 0.3255 mm )
Alarms: incoming signal level too low Loss Of Signal (LOS)
4 x 8 = 32 following bits logical "1" Alarm Indication Signal (AIS)
Onboard Connector RJ45
Various:
Shielding, cable screen to be earthed with metallic clamp on cable tray at rear side of rack
Maximum cable length Internal clock 1000 m
(using STP = Shielded Twisted Pair) External clock 500 m
Onboard Connector Sub-D, 25 pol, male, TIA/EIA-530-A
(RS-530)
Optional piggyback to be mounted on Digital Interface G3LD (configurable for E1 and T1 operation; E1 = default configuration).
Hardware release monitoring via HMI570
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:
Signal input:
Various:
Shielding, cable screen to be earthed with metallic clamp on cable tray at rear side of rack
Maximum cable length 22 AWG 1500 m
2
(using STP = Shielded Twisted Pair) (diameter 0.6438 mm = 0.3255 mm )
Receiver sensitivity configurable for max. cable attenuation 10 dB (short haul; default)
43 dB (long haul)
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
Signal output:
Signal input:
Various:
Shielding, cable screen to be earthed with metallic clamp on cable tray at rear side of rack
Maximum cable length 22 AWG 2000 m
2
(using STP = Shielded Twisted Pair) (diameter 0.6438 mm = 0.3255 mm )
Receiver sensitivity configurable for max. cable attenuation 10 dB (short haul; default)
36 dB (long haul)
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
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).
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) < 1.5 UI
Band B2 (18 kHz… 100 kHz) < 0.2 UI
Optical output power Short haul -22… -17 dBm
Long haul -5… -1 dBm
Signal input:
Various:
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
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:
Various:
Framing format According to IEEE C37.94 256 bits with 16 bit header, 48 bit overhead and 192
bit payload.
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
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
Tripping current ON/OFF ratio ≤ 1/3 up to 5 min./15 min. ≤ 2 A;
Continuous ≤1A
Current limitation typ. 2.6 A
Short circuit cut off after approx. 6 ms for 1 s
Leakage current ≤ 200 µA; at 312 V / 70°C
Operating time ≤ 250 µs (typ. 60 µs)
Reverse polarity protection 400 VDC
Efficiency DC > 80 %
AC > 75 %
basic version (rack, one supply module, one line interface, one relay interface):
LED indication on front panel Supervision of power supply output voltage green = ok, red = failed, dark = not plugged
Connecting cable serial 1:1 cable, 9 pin Sub-D connector PC/notebook -> female, NSD570 -> male
If connected via a modem (= DCE) “Null-Modem” cable necessary (male-male) cross connection of 103 ↔ 104, 105 ↔ 106
IRIG-B input:
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).
Ethernet 10/100BaseT interface with embedded web server for connecting the NSD570 to TCP/IP-networks.
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
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
Local and remote access facilities - serial cable at 9600 bps, 19200 bps, 57600 bps
Firmware download locally or from a remote site via any communication channel,
via EOC of NSD570 Analog -> not recommended
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)
17. ALARMS
Rx guard signal level deviation from nominal level > ± 3 dB … ± 12 dB (programmable, 1 dB steps)
detection time <1s
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)
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
Event recorder:
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
19.1. Emission
The equipment meets the EMC requirements for emission EN 50081-2: 1993 (EN 55022 class A)
19.2. 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
19.3. Insulation
Power Impulse Insulation
frequency Voltage resistance
withstand test (@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Ω
Weight basic version (rack, one supply module, one line interface, one relay interface):
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
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)
to the power supply units via Faston connector 6.3 x 0.8 mm (DIN 4624)
2
to optional cables with isolating terminals 0.2 - 2.5 mm for stranded wire, (AWG 24 - 12)
2
0.2 - 4.0 mm for solid wire (AWG 24 - 11)
to optional cables with RJ45 press-fit terminals 0.5 - 0.65 mm diameter (AWG 24 - 22) solid wire
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
21.1. Operation
Climatic conditions Complies with IEC 60721-3-3 Class 3K5
Operational - 20 to + 55 °C
21.2. Transport
21.3. Storage
Climatic conditions Complies with IEC 60721-3-1 Class 1K5
Temperature range - 40 to + 70 °C
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)
1 Purpose of document
This document describes the software installation process for the HMI570.
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)
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
Revision: Language: Page:
A EN 2/4 1KHW000894
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.
Revision: Language: Page:
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.
Revision: Language: Page:
A EN 4/4 1KHW000894
2.4 Deinstallation
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
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 > - A 03-09-01
Responsible Department: Prepared: Approved: Distribution: Lang.: Page:
PTUKT2 02-10-02 sig. Schnyder 02-12-20 sig. Strittmatter - EN 1/3
Valid for: Derived from: Replaces: Classification-No.: File:
- - - -
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
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
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
Revision: Language: Page:
A 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.
Caution Keep your hands away from keyboard and mouse while a firmware download
is in progress.
Revision: Language: Page:
A EN 3/3 1KHW000896
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.
Caution Never download a firmware file to a module that is not destined for,
e.g. never download the file NSD570_Digital_V1_22.ldr to a G3LA module.
3 Firmware download
This document describes programming and testing of the teleprotection equipment NSD570 Analog and
NSD570 Digital, including the optical interface for the NSD570 Digital.
Contents:
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
Revision: Language: Page:
A EN 2/37 1KHW000898-EN
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
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)
Revision: Language: Page:
A EN 3/37 1KHW000898-EN
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!
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.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
Revision: Language: Page:
A EN 5/37 1KHW000898-EN
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.
Revision: Language: Page:
A EN 8/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
An internal elastic buffer size can be configured individually for the input and the output circuits.
This buffer may help to compensate clock deviations or clock wander between the internal and the
external timing. Compensation of jitter and detection of slips is also possible by means of a higher
buffer size thus introducing a higher delay. A compromise has to be found in actual tests with the
used communication equipment regarding high jitter capability versus low additional delay.
Rx Buffer configurable to 1 frame 2 frames (default), 96 bit, bypass
Tx Buffer configurable to 1 frame 2 frames (default), 96 bit, bypass
The following combinations are not possible:
Rx Buffer = bypass and Tx Buffer = bypass
Rx Buffer = bypass and Tx Buffer = 96 bit
Rx Buffer = 96 bit and Tx Buffer = bypass
Rx Buffer = 96 bit and Tx Buffer = 96 bit
The E1 coding format can be adjusted to the one that is used by the communication equipment.
E1 Coding configurable to HDB3 (default) or AMI
The E1 frame format can be adjusted to the one that is used by the communication equipment.
E1 Frame Format configurable to double frame (default) or CRC4 multiframe
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.
Long Haul configurable to off (default = short haul) or on
An internal elastic buffer size can be configured individually for the input and the output circuits.
This buffer may help to compensate clock deviations or clock wander between the internal and the
external timing. Compensation of jitter and detection of slips is also possible by means of a higher
buffer size thus introducing a higher delay. A compromise has to be found in actual tests with the
used communication equipment regarding high jitter capability versus low additional delay.
Rx Buffer configurable to 1 frame 2 frames (default), 96 bit, bypass
Tx Buffer configurable to 1 frame 2 frames (default), 96 bit, bypass
The following combinations are not possible:
Rx Buffer = bypass and Tx Buffer = bypass
Rx Buffer = bypass and Tx Buffer = 96 bit
Rx Buffer = 96 bit and Tx Buffer = bypass
Rx Buffer = 96 bit and Tx Buffer = 96 bit
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
Revision: Language: Page:
A 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.
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.
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.
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.
) Note: Now the equipment can be powered by closing the external circuit breaker(s)
or switching on the external power supply unit.
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).
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.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.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
Revision: Language: Page:
A EN 20/37 1KHW000898-EN
Designation Meaning
(T.22/..1) Connector 1 of terminal block connected to rack position N22
Revision: Language: Page:
A 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.
) 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.
) 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.13.5 Documentation
Create a printout of the active configuration data that was uploaded and saved to disk before (see
B.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.
Item to be Selected
No. Function Rack or programmed or alternative Remarks
module fitted or setting
A.1 General
A.4.4 Unblocking
left * right *
Unblocking Extra Delay G3LA/D ____/____ [ms] [ ] [ ]
Unblocking Pulse Duration G3LA/D ____/____ [ms] [ ] [ ]
∗
"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. 2003-09-01
Revision: Language: Page:
NSD570 System Settings A EN A2/A7 HE
Item to be Selected
No. Function Rack or programmed or alternative Remarks
module fitted or setting
left * right *
A.4.7 Embedded Operation Channel G3LA/D enabled
(EOC) [ ] [ ]
left * right *
A.4.8 Cyclic Loop Test G3LA/D enabled
Interval ____/____ [h] [ ] [ ]
left * right *
A.5.2 Connection to the AF G3LA [ ] [ ]
2-wire
communication circuits
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] [ ]
Item to be Selected
No. Function Rack or programmed or alternative Remarks
module fitted or setting
Item to be Selected
No. Function Rack or programmed or alternative Remarks
module fitted or setting
Item to be
programmed or
fitted
Item to be
programmed or
fitted
Item to be Selected
No. Function Rack or programmed or alternative Remarks
module fitted or setting
Normally open NO [ ] [ ]
Normally closed NC [ ] [ ]
Item to be Selected
No. Function Rack or programmed or alternative Remarks
module fitted or setting
B.1 General
B.6.1 Setting real time clock Check PC time / date Actual / exact [ ]
Set time and date [ ] [ ]
Get time and date Actual / exact [ ] [ ]
∗
"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. 2003-09-01
Revision: Language: Page:
NSD570 System Test Report A EN B2/B5 HE
If connected to PLC PLC protection input Max. level dBm ____ ____
-> reduce level setting if necessary G3LA; X100/1-2 measure level dBm (…..) (…..)
B.7.3 Receiver
Guard level G3LA; X100/3-4 [ setting ± 2 ] dBm [ ] [ ]
Output power (Optical Direct Fiber G3LD/G1LO; X701/Tx [ -22 … -17 ] dBm (…..) (…..)
or Optical FOX/OTERM only) (short haul)
G3LD/G1LO; X701/Tx [ -5 … -1 ] dBm (…..) (…..)
(long haul)
Optical output power (Optical IEEE G3LD/G1LO; X701/Tx [ -16 … -11 ] dBm (…..) (…..)
C37.94 only)
Max. attenuation (Optical Direct G3LD/G1LO; X701/Rx > 25 dB (…..) (…..)
Fiber or Optical FOX/OTERM only) (long haul)
Max. attenuation (Optical IEEE G3LD/G1LO; X701/Rx > 10 dB (…..) (…..)
C37.94 only)
B.9.1 Inputs
Input 1 G3LR U1, see N34 N40 N46 N52
Activate Input 1 (T…/1) – (T.../2) System settings V DC [ ] [ ] [ ] [ ]
Check LED Input 1 LED Input 1 ON N64 N70 N76 N84
[ ] [ ] [ ] [ ]
B.9.2 Outputs
Enforce action for G3LR U1, see N34 N40 N46 N52
Output 1 (T…/5) – (T.../6) System settings V DC [ ] [ ] [ ] [ ]
Check Output 1 closed N64 N70 N76 N84
Check LED Output 1 LED Output 1 ON [ ] [ ] [ ] [ ]
Enforce action for G3LR U1, see N34 N40 N46 N52
Output 2 (T…/7) – (T.../8) System settings V DC [ ] [ ] [ ] [ ]
Check Output 2 closed N64 N70 N76 N84
Check LED Output 2 LED Output 2 ON [ ] [ ] [ ] [ ]
Enforce action for G3LR U1, see N34 N40 N46 N52
Relay 1 (T…/9) – (T.../10) System settings V DC [ ] [ ] [ ] [ ]
Check Relay 1 closed N64 N70 N76 N84
Check LED Relay 1 LED Relay 1 ON [ ] [ ] [ ] [ ]
Enforce action for G3LR U1, see N34 N40 N46 N52
Relay 2 (T…/12) – (T.../13) System settings V DC [ ] [ ] [ ] [ ]
Check Relay 2 closed
N64 N70 N76 N84
Check LED Relay 2 LED Relay 2 ON [ ] [ ] [ ] [ ]
B.11.2 Command
transmission time left * right *
B.13.5 Documentation
View/print configuration HMI570 # printout pages (………..) (………..)
Company: _________________________________
Department: _________________________________
Date: _________________________________
Signed: _________________________________
Visa: _________________________________
This document describes commissioning of the teleprotection equipment NSD570 Analog and NSD570 Digital,
including the optical interface for the NSD570 Digital.
Contents:
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
Revision: Language: Page:
A EN 2/14 1KHW000900-EN
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
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)
Revision: Language: Page:
A EN 3/14 1KHW000900-EN
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.
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.
) Note: Now the equipment can be powered by closing the external circuit breaker(s)
or switching on the external power supply unit.
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.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
Revision: Language: Page:
A EN 7/14 1KHW000900-EN
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.12.5 Documentation
Create a printout of the active configuration data that was uploaded and saved to disk before (see
C.12.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.1 General
C.6.1 Setting real time clock Check PC time / date Actual / exact [ ]
Set time and date [ ] [ ]
Get time and date Actual / exact [ ] [ ]
∗
"left" and "right" stands for NSD570 in the left half / right half of the rack (front view)
© ABB Switzerland Ltd, Utility Automation Systems Form 1KHW000900-EN
Rev. 2003-09-01
Revision: Language: Page:
NSD570 Commissioning Report A EN C2/C4 HE
If connected to PLC PLC protection input Max. level dBm ____ ____
-> reduce level setting if necessary G3LA; X100/1-2 measure level dBm (…..) (…..)
C.7.3 Receiver
Guard level G3LA; X100/3-4 [ setting ± 2 ] dBm [ ] [ ]
Output power (Optical Direct Fiber G3LD/G1LO; X701/Tx [ -22 … -17 ] dBm (…..) (…..)
or Optical FOX/OTERM only) (short haul)
G3LD/G1LO; X701/Tx [ -5 … -1 ] dBm (…..) (…..)
(long haul)
Optical output power (Optical IEEE G3LD/G1LO; X701/Tx [ -16 … -11 ] dBm (…..) (…..)
C37.94 only)
Optical input power G3LD/G1LO; X701/Rx [ -36 … -1 ] dBm (…..) (…..)
C.10.3 Command
transmission time left * right *
C.12.5 Documentation
View/print configuration HMI570 # printout pages (………..) (………..)
Company: _________________________________
Department: _________________________________
Date: _________________________________
Signed: _________________________________
Visa: _________________________________
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 6
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.
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
Revision: Language: Page:
A EN 2/6 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.
• 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.
) Note: All hardware versions can be viewed by means of the HMI570, except for:
Module Rack G7BI, Supply Backplane G1LB, Power Supply G3LH.
Revision: Language: Page:
A EN 4/6 1KHW000902-EN
) 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).
Revision: Language: Page:
A EN 5/6 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.
) Note: The software version of the HMI570 can be viewed by clicking on the “About
HMI570” link in the “HMI570 Options” menu.
Revision: Language: Page:
A EN 6/6 1KHW000902-EN
6 NSD570 Options
The NSD570 options consist of following hardware and firmware versions:
) 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).
) 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 > - A 03-09-01
Responsible Department: Prepared: Approved: Distribution: Lang.: Page:
PTUKT2 03-02-25 sig. M. Buhl 03-02-28 sig. M. Strittmatter - EN 1/4
Valid for: Derived from: Replaces: Classification-No.: File:
- - - -
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 Connecting different interface types over a multiplexer 4
2.3.3 Connecting an E1 or T1 Interface over a multiplexer 4
2.3.4 Interchanging the two digital line interfaces in the same rack 4
1 Purpose of document
This document describes the currently known anomalies in the behaviour of the NSD570
teleprotection system. Such anomalies express themselves in unexpected system behaviour not
described in the Operating Instructions NSD570 (1KHW000890-EN), 3rd Edition (2003-09-01).
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).
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
Revision: Language: Page:
A EN 2/4 1KHW000904-EN
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.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.2 Description
If more than four relay interfaces are configured per line interface, equipment faults may occur.
Two line interfaces in the module rack may accidentally be configured for using the same relay
interface. This cannot be detected and therefore not be avoided by the HMI570, because each line
interface is configured separately.
In both above cases, inadmissible operating conditions may arise and even malfunctions
have to be expected!
2.1.3.3 Workaround
If only one line interface is plugged in the module rack, make sure that a maximum of four relay
interfaces are configured (if required, they may be plugged in any assigned slot of the rack).
If two line interfaces are plugged in the rack, make sure that only a maximum of four relay
interfaces in the corresponding rack half are configured (i.e. line interface TPE 1 uses relay
interfaces in the left rack half only and TPE 2 uses relay interfaces in the right rack half only).
Revision: Language: Page:
A EN 3/4 1KHW000904-EN
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.1.2 Description
The short term and long 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).
Revision: Language: Page:
A EN 4/4 1KHW000904-EN
2.3.2.2 Description
If two NSD570 are linked together over a multiplexer using different interfaces, depending on the
interface type, communication is not possible. The only “mixed-mode” operation that works via a
FOX515 link can be realized with the optical interface on one side and the G.703 codirectional
interface on the other. All other conceivable combinations of interfaces as for example G.703
codirectional with RS-530 will not work.
2.3.2.3 Workaround
There is no workaround at this time. Use the same interfaces on both sides of the multiplexer
instead.
2.3.3.2 Description
The E1 and T1 Interfaces need a constant ‘0’ on timeslot 2. Otherwise a BER of 0.25 arises.
2.3.3.3 Workaround
If a direct point-to-point connection is realized, no specific action is required.
If a link over a multiplexer is needed, make sure timeslot 1 and 2 are through connected.
2.3.4 Interchanging the two digital line interfaces in the same rack
2.3.4.1 Hardware, software and/or firmware versions
G3LD, NSD570 Digital FW Vers. 1.20, 1.22,
HMI570 SW Vers. 1.03, 1.04
2.3.4.2 Description
Missconfiguration 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
(unless they are not damaged).
2.3.4.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.
ABB
ABB Switzerland Ltd e-mail: utilitycommunication@ch.abb.com
Utility Automation Systems LN : utilitycommunication@ABB_CH01
PTUKS Customer Service Fax: ++ 41 58 585 16 85
CH-5400 Baden / Switzerland Tel : ++ 41 58 589 37 35
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
Customer
Modules
Customer Support Center
for Repair ABB Switzerland Ltd
Dept. PTUKS
5. Repair of Modules
• Always ensure that a separate Fault Report form accompanies your material when it is returned to PTUKS.
• Always fax copy of Fault Report to PTUKS to check the arrival of your delivery.
• Always include the name and contact details of an engineer who can be contacted by the PTUKS 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 PTUKS does not guarantee that it will have replacement items available at all times,
except for replacement on SERVICE CONTRACT.
This service will be charged with US$ 350.00 for each unit.
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 PTUKS until a purchase order for the amount quoted for repair is received by
PTUKS.
All items received by PTUKS 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 PTUKS.
Fault Report
A separate “Fault Report” must be completed for each individual faulty item you intend to return to PTUKS.
___________________________________________________________________________________________________
________________________________________ _________________________________________
Company: ______________________________
Questions,
Technical
Support
1. Support
request
2. Formal acceptance of
price and delivery terms
ABB
3. Service delivery
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
www.abb.com/utilitycommunications