3701 Emergency Trip System (ETS)

System Manual
Bently Nevada™ Asset Condition Monitoring
3701 Emergency Trip System (ETS)
Part Number 179483-01

Rev. A (05/08)
3701 ETS System Manual
Copyright 2008. Bently Nevada LLC.

All rights reserved.
The information contained in this document is subject to change without notice.
The following are trademarks of General Electric Company in the United States and other
countries:
MPC, EGD, UDH, Proximitor
The following are trademarks of the legal entities cited:
Windows is a trademark of Microsoft.
Velostat is a trademark of 3M.
Contact Information
The following contact information is provided for those times when you cannot contact
your local representative:
Mailing Address 1631 Bently Parkway South

Minden, Nevada USA 89423
USA
Telephone 1.775.782.3611
1.800.227.5514
Fax 1.775.215.2873
Internet www.ge-energy.com/bently
ii
Additional Information
Notice:
This manual does not contain all the information required to operate and maintain
the product. Refer to the following manuals for other required information.
3701 ETS Datasheet (Part Number 178777-01)

• Electrical, Mechanical and feature specifications
• Ordering information
Product Disposal Statement

Customers and third parties, who are not member states of the European Union, who are
in control of the product at the end of its life or at the end of its use, are solely
responsible for the proper disposal of the product. No person, firm, corporation,
association or agency that is in control of product shall dispose of it in a manner that is
in violation of any applicable federal, state, local or international law. Bently Nevada LLC
is not responsible for the disposal of the product at the end of its life or at the end of its
use.
iii
Contents
1. Receiving and Handling Instructions..........................................................1

1.1 Receiving Inspection........................................................................................................................ 1
1.2 Handling and storage considerations ..................................................................................... 1
2. General Overview ...........................................................................................3
2.1 High Level Operational Overview............................................................................................... 3
3. Specifications ..................................................................................................5
3.1 3701 ETS Unit (3701/85) ................................................................................................................. 5
3.1.1 Overview........................................................................................................................................... 5
3.1.2 Specifications................................................................................................................................. 6
3.2 CPU Module (177933-01) ............................................................................................................... 7
3.2.1 Overview........................................................................................................................................... 7
3.2.2 LED Behavior .................................................................................................................................. 7
3.3 Input Card (177934-01)................................................................................................................... 9
3.3.1 Overview........................................................................................................................................... 9
3.3.2 Specifications...............................................................................................................................10
3.4 Output Card (177935-01).............................................................................................................11
3.4.1 Overview.........................................................................................................................................11
3.4.2 Relay Outputs...............................................................................................................................11
3.4.3 OK Relay .........................................................................................................................................12
3.4.4 DIP Switch......................................................................................................................................14
3.4.5 LED Behavior ................................................................................................................................16
3.5 Terminal Blocks ................................................................................................................................17
3.6 Terminal Base ...................................................................................................................................19
3.6.1 Network Connections...............................................................................................................19
3.6.2 Power Connections ...................................................................................................................20
3.7 TMR Relay Module...........................................................................................................................22
3.7.1 Wiring Diagram...........................................................................................................................23
3.7.2 DIP Switches .................................................................................................................................26
3.8 TMR Cable ...........................................................................................................................................27
3.9 Output-to-Relay Cable ..................................................................................................................28
4. Installation.....................................................................................................29
4.1 Physical Mounting...........................................................................................................................29
4.2 Software Installation......................................................................................................................31
5. Configuration ................................................................................................33
iv
5.1 Connecting to Your 3701 ETS Units.........................................................................................33
5.2 Configuring Your 3701 ETS Units..............................................................................................39
5.2.1 Supported Function Blocks....................................................................................................39
5.2.2 Creating a Configuration ........................................................................................................51
6. Maintenance ................................................................................................. 53
6.1 Software Maintenance .................................................................................................................53
6.2 Firmware Upgrade..........................................................................................................................53
7. System Verification...................................................................................... 55
7.1 Configuration Validation ..............................................................................................................55
7.1.1 Input Validation...........................................................................................................................55
7.1.2 Logic Validation...........................................................................................................................55
7.1.3 Output Validation .......................................................................................................................56
7.2 Online Proof Tests ...........................................................................................................................56
7.2.1 Testing Discrete Inputs ............................................................................................................56
7.2.2 Testing Speed Inputs ................................................................................................................57
7.2.3 Testing Outputs...........................................................................................................................58
8. Troubleshooting........................................................................................... 61
9. Ordering Information.................................................................................. 63
9.1 Ordering Options .............................................................................................................................63
9.2 Spares...................................................................................................................................................64
v
Section 1 - Receiving and Handling Instructions
1. Receiving and Handling Instructions

1.1 Receiving Inspection
Visually inspect all modules for obvious shipping damage. If shipping damage is
apparent, file a claim with the carrier and submit a copy to Bently Nevada, LLC.
1.2 Handling and storage considerations

Circuit boards contain devices that are susceptible to damage when exposed to
electrostatic charges. Damage caused by obvious mishandling of any circuit
boards will void the warranty. Under normal operation when inserted into the
backplane and locked in place, the ETS circuit boards are highly resistant to
damage. However, if you must install or replace circuit boards, you should take
care. To avoid damage, observe the following precautions in the order given:
1) Do not discharge static electricity onto the circuit board. Avoid tools or
procedures that would subject the circuit board to static damage. Some
possible causes include ungrounded soldering irons, nonconductive
plastics, and similar materials.
2) Personnel must be grounded with a suitable grounding strap (such as a
3M Velostat® No. 2060) before handling or maintaining a printed circuit
board.
3) Transport and store circuit boards in electrically conductive bags or foil.
4) Use extra caution during dry weather. Relative humidity less than 30%
tends to multiply the accumulation of static charges on any surface.
1
Section 2 - General Overview
2. General Overview
2.1 High Level Operational Overview
The 3701 ETS (Emergency Trip System) is a highly configurable, scalable trip
system for all rotating machinery. The system combines highly accurate
overspeed trip circuitry with high-density discrete inputs to make the ETS a
complete, configurable trip system. The ETS has a simple graphical interface that
allows intuitive configuration. It also provides redundant network interfaces and
communicates using the GE Unit Data Highway (UDH™) network architecture.
The ETS provides 6 independent overspeed circuits, each of which can
accommodate either proximity probes or magnetic speed pickups. Each speed
circuit is highly configurable, highly accurate, and designed to meet API612. The
ETS also accepts up to 48 discrete inputs. These inputs, along with the overspeed
signals, can then form the base of trip logic that is virtually infinitely configurable.
Each of the Triple Modular Redundant 3701 ETS units connects to a 2-out-of-3
voting relay module that provides the trip contacts.
For a steam turbine application, the trip contacts control the safety oil system,
which allows the inlet steam valve to actuate. Upon detecting a shutdown
condition, the ETS will activate the trip signals to shut the inlet valve and remove
all steam pressure from the turbine, causing a shutdown. Note that the turbine
manufacturer is responsible for supplying the mechanical shutdown mechanism
for the turbine.
3
Section 3 - Specifications
3. Specifications
The following sections identify each component of the 3701 ETS. Upon receiving your
system, use this manual to inspect and identify each component. This step is important
and will simplify installation, configuration, and troubleshooting. A complete TMR
system consists of 3 3701 ETS units, 1 TMR relay module, 1 (or 2) TMR cables, and 1
output-to-relay cable. Further, the ETS unit is comprised of 3 card types: the CPU, the
Input Card, and the Output Card. A simplex system consists of a single 3701 ETS unit.
3.1 3701 ETS Unit (3701/85)

3.1.1 Overview
Figure 3-1 shows a 3701 ETS unit. A full TMR system consists of 3 of these units.
Your ETS unit should arrive with all modules pre-installed in the 3701 ETS chassis.
Figure 3-1: 3701 ETS Unit
5
3.1.2 Specifications
Table 3-1: 3701 ETS Unit Specifications

Specification Value
Dimensions (L x W x H) 17.8 x 25.4 x 18.0 cm (7.0 x 10.0 x 7.1 in)
Weight 4.8 kg (10.6 lbm)
Network Connections 2 x 10/100/1000 Ethernet, RJ45 type
Supply Voltage Redundant 18-36Vdc, Nominal +24Vdc
Mounting Bulkhead/panel mounting via base plate mounting holes
Number of Slots 4 (1 CPU, 2 Input, 1 Output)
6
3.2 CPU Module (177933-01)

3.2.1 Overview
Figure 3-2 shows the CPU module. The CPU module performs all ETS trip logic
and provides communication to the human-machine interface (HMI) and
configuration software. This module occupies the left-most slot in the terminal
base.
Figure 3-2: CPU Module
The CPU module is a high-performance computing interface. The label on top

shows the Ethernet MAC addresses for identification on the network. The module
includes a USB connector that is reserved for future use. All other connections to
the CPU module are through the terminal base. The main user interface on this
card is the LEDs, whose behavior is described in Section 3.2.2.
3.2.2 LED Behavior

There are eight LEDs on the CPU module for status indication. Table 3-2
summarizes their operation:
7
Table 3-2: CPU Module LED Operation
Priority Bypass RUN
OK LED Condition (Description)
(Low=0) LED LED
Power OFF (default Not OK), Link LEDs will be off as
5 OFF OFF OFF
well.
4 ON ON ON Boot Mode (Initializing)
3 OFF 1 Hz 1 Hz Firmware Upgrade (Not OK)
Internal Failure (Node voltage failure, channel
2 OFF OFF ON disabled or in test mode) (set Not OK)
External Failure (Transducer failure) (set Not OK)
Unconfigured (set Not OK) or
1 Hz or
1 OFF OFF Config Failure (set Not OK)
OFF
(See note below)
0 ON OFF ON Run Mode (OK)
Note: The OK LED will be off if the CPU is not heart beating the FPGA, or if the FPGA is driving the
Not OK condition due to a logic CRC error or Input Card communications error.
Additionally, the CPU module has LEDs to indicate the network status. These LEDs
show both link connection and activity for the two 3701 Ethernet links. If the
hardware that is connected to a link is operational, its corresponding link LED
should be on. Likewise, if the module detects traffic on that link, the
corresponding activity LED should flash. For more information, see the
troubleshooting section.
Finally, the CPU module has LEDs that indicate whether or not the power
connections are within operational limits. There is one LED for each power
connection. In normal operation, these should both be on.
8
3.3 Input Card (177934-01)

3.3.1 Overview
The two center slots in the terminal base are reserved for Input Cards. Figure 3-3
shows an input card. This card provides signal conditioning and isolation for all
inputs into the system. The ETS supplies the physical input signals to the input
cards through the terminal base. The inputs to the ETS are discrete inputs and
speed sensor inputs. The speed sensors may either be proximity probes or
magnetic pickups. For proximity probes, a –24V supply is provided.
Figure 3-3: Input Card
9
3.3.2 Specifications
Table 3-3: Summary of 3701 ETS Input Card Specifications

Specification Value
Number of Discrete Inputs 24
Number of Speed Inputs 3 (plus 3 test)
Type of Speed Inputs Proximity Probe or Magnetic Pickup
Type of Discrete Inputs Dry Contact
Proximity Probe Supply Voltage –24Vdc (Nominal)
Proximity Probe Current Nominal 12mA, limited to 30mA, short-circuit protected
Speed Input Frequency
6Hz to 20KHz
Response
Isolation 1500Vdc on all inputs
Table 3-4 summarizes the OK LED behavior.
Table 3-4: Summary of 3701 Input Card LED Behavior

Priority
(Low=0)
5 OFF Power OFF (default Not OK),
Boot Mode. The Run LED will come on for one
4 Blink second, then off when booting. This shows the
card is initializing.
3 OFF Firmware Upgrade (Not OK)
2 OFF Node Voltage Failure or Transducer Error.
1 1 Hz Unconfigured
0 ON Run Mode (OK)
10
3.4 Output Card (177935-01)

3.4.1 Overview
The output card occupies the right-most slot of the terminal base and is depicted
in Figure 3-4.
Figure 3-4: Output Module
3.4.2 Relay Outputs

The output module has 8 output contacts. These can be operated at 250Vac@5A
or 28Vdc@5A. You can configure these modules as either normally open or
normally closed. For TMR operation, the TMR-to-output cable plugs directly into
the output receptacles; so additional wiring is not required. This cable is wired for
“de-energize to trip”, so if your application requires “energize to trip” wiring you
must modify the cable. Figure 3-5 shows the wiring diagram for the relays.
11
Figure 3-5: Output Card Relay Wiring
There are three terminals for each relay as shown in Table 3-5.
Table 3-5: Output Card Relay Terminal Descriptions
Terminal Description
Normally Open. When the coil is not energized, this terminal will be an open circuit
RLY N.O. with the armature. If a system is “de-energize to trip”, connect to this terminal and the
armature.
Relay Armature. The armature moves from the normally closed contact to the
RLY ARM
normally open contact when the coil is energized.
Normally Closed. When the coil is not energized, this terminal will be a short circuit
RLY N.C. with the armature. If a system is “energize to trip”, connect to this terminal and the
armature.
In a TMR system, the Output-to-Relay cable connects the first six relays to the
TMR Relay Module. This cable connects the normally open terminals. You can
modify this at your discretion. Also, the remaining two relay outputs are available
for general use.
3.4.3 OK Relay
The OK relay indicates the overall operational state of the entire 3701 ETS unit. If
any internal or external error occurs on any card, the unit will put the relay into
the “Not OK” state. When the system is in the “Not OK” state, it is no longer
reliably providing functional safety. Figure 3-6 shows the OK relay terminal
connections, and Table 3-6 details the connections.
12
Figure 3-6: OK Relay Terminal
Table 3-6: 3701 ETS OK Relay Connections

Terminal Description
Normally Open. When the coil is not energized, this terminal will be an open circuit
OK N.O.
with the armature.
Relay Armature. The armature moves from the normally closed contact to the
OK ARM
normally open contact when the coil is energized.
Normally Closed. When the coil is not energized, this terminal will be a short circuit
OK N.C.
with the armature.
Note that the OK relay is always “de-energize to trip”, meaning that the coil is
energized in the OK state, and de-energized in the Not OK state. Table 3-7 details
the reasons for a “Not OK” state, and whether or not the 3701 ETS can provide
functional safety. The OK relay is intended only for annunciation, not for
shutdown, but is left to the discretion of the operator. If the OK relay is used for
shutdown, proper care should be taken during online proof testing, as NOT OK
conditions can be intentionally created.
Table 3-7: Summary of Not OK Conditions

Fault Description Safety Status
A node voltage error on any card, Not Functional.

Node Voltage Error including Input Cards, CPU, or A node voltage error compromises
Output. the integrity of the system.
The CPU reboots or stops Functional.
CPU reboot or
communicating with the HMI or The FPGA handles all safety functions
timeout.
onboard FPGA. independently of the CPU.
The program in the FPGA becomes
FPGA CRC error. Not Functional.
corrupted.
13
Fault Description Safety Status
Compromised.
An open or short circuit occurs on Only the affected speed input will not
Speed Input Fault speed sensor wiring or the sensor work. All other functionality works
itself malfunctions. properly. Strictly speaking, however,
the system is not fully operational for
safety functions.
The configuration in an input card Compromised.
does not match the current Only the affected speed input(s) will
Configuration configuration logic. This can occur not work. All other functionality
Mismatch if an input card is replaced with a works properly. Strictly speaking,
spare and configuration is not however, the system is not fully
reloaded. operational for safety functions.
The embedded code on the ETS unit
Firmware Upgrade Not Functional.
is being updated.
Both power sources have failed,
Power Failure Not Functional.
and the ETS unit is not powered.
Compromised.
Either a discrete or speed input, or
a discrete output has been Only the affected channels will not
Channel Disabled. disabled. This state will be work. All other functionality works
encountered during online proof properly. Strictly speaking, however,
testing. the system is not fully operational for
safety functions.
Compromised.
A speed input is configured to use
the test input rather than the actual Only the affected speed input will not
Speed Input Test work. All other functionality works
sensor input. This state will be
Mode Enabled properly. Strictly speaking, however,
encountered during online proof
testing. the system is not fully operational for
safety functions.
The unit has either never been
configured or the current
Configuration Failure Not Functional.
configuration is invalid or
corrupted.
3.4.4 DIP Switch

The DIP switch on the output card allows the relays to function in either an
“energize to trip” or “de-energize to trip” fashion. That is, one setting is “normally
de-energized” and the other is “normally energized”, as shown in Table 3-8.
Table 3-8: DIP Switch Settings

Switch Position Trip Mode
ON De-energize to trip
OFF Energize to trip
14
If the switch is in the “ON” position, the relay functions as “de-energize to trip”.
This means that in normal, non-alarm operation, the coil of the relay is energized.
This mode is highly suggested for safety functions. If the switch is in the “OFF”
position, the relay functions as “energize to trip”.
Note that there are only four switches, and there are eight relays. As Table 3-9
shows, DIP Switch 1 controls relays 1 and 2, DIP Switch 2 controls Relays 3 and 4,
DIP Switch 3 controls Relays 5 and 6, and DIP Switch 4 controls Relays 7 and 8.
Table 3-9: DIP Switch Summary

DIP Switch Number Relays Controlled
1 Relays 1 and 2
2 Relays 3 and 4
3 Relays 5 and 6
4 Relays 7 and 8
15
3.4.5 LED Behavior

3.4.5.1 OK LED
Table 3-10: Summary of OK LED Behavior

Priority
(Low=0)
5 OFF Power OFF (default Not OK),
Boot Mode. The Run LED will come on for one
4 Blink second, and then turn off when booting. This
shows that the card is initializing.
3 OFF Firmware Upgrade (Not OK)
2 OFF Node Voltage Failure or Transducer Error.
1 1 Hz Unconfigured (set Not OK)
0 ON Run Mode (OK)
3.4.5.2 Channel LEDs
Table 3-11: Summary of Channel LED Behavior

Priority
CH LED Condition (Description)
(Low=0)
Power is OFF or Relay is not activated. That is, if the
relay is configured for “de-energize to trip”, then the
5 OFF
coil is energized. If the relay is configured for
“energize to trip”, then the coil is de-energized.
Relay is activated. Coil is energized if the relay is
4 ON configured for “energize to trip”, and de-energized if
the relay is configured for “de-energize to trip”.
3 1 Hz Hardware problem with associated relay.
16
3.5 Terminal Blocks

The terminal blocks, shown in Figure 3-7, are used to connect field wiring to the
system. The system supports 48 discrete inputs and 6 speed inputs. The part
numbers of the 6 unique terminal blocks in a TMR system are 177471-01,
177471-02, 177498-01, 177498-02, 177504-01, and 177504-02.
Figure 3-7: Terminal Block

Discrete input channels are numbered from 01 through 48. There are 2 terminals
to which a discrete input connects. These terminals are labeled ‘a’ and ‘b’.
Additionally, the speed channel has several connection options, depending upon
the type of sensor used. Refer to Table 3-12 for a description of the speed input
terminal blocks.
Table 3-12: Summary of Speed Input Terminal Blocks

Pin Description
Speed Supply Voltage. For proximity probes, this provides –24V (Vt). If
Sv
required, this is connected to the Vt terminal of a Proximitor® sensor.
Speed Signal Shield. If the speed sensor cable is shielded, connect the
Ss
shield to this terminal.
Speed Test Negative Input. When connecting a function generator or
ST- other test equipment for testing purposes, connect the common (or
negative) output to this terminal.
17
Pin Description
Speed Input “x” positive input, where “x” indicates speed input number 1-6.
This terminal is used for both magnetic pickup and Proximitor sensor
applications. For magnetic pickup, it doesn’t matter which terminal is
Sx+ connected to which wire, since the signal is AC, and biased around zero.
However, for a proximity-based speed measurement, the signal is a
negative voltage. This means the “com” terminal of the Proximitor sensor
is more positive, and should be connected here.
Speed Input “x” negative input, where “x” indicates speed input number 1
through 6. This terminal is used for both magnetic pickup and Proximitor
sensor applications. For magnetic pickup, it doesn’t matter which terminal
Sx- is connected to which wire, since the signal is AC, and biased around zero.
However, for a proximity-based speed measurement, the signal is a
negative voltage. This means the “out” terminal of the Proximitor sensor is
more negative, and should be connected here.
Speed Test Positive Input. When connecting a function generator or other
ST+ test equipment for testing purposes, connect the signal (or positive) output
to this terminal.
There are a total of 48 discrete inputs and 6 speed inputs in the system. Notice
that there are 8 discrete inputs and 1 speed input on each terminal block. For
proper operation, the terminal blocks must be inserted into the correct ETS units.
For systems with only a single input card (only 24 discrete inputs), one terminal
block is placed in each ETS unit. This means that unit #1 has the terminal block
for inputs 1-8, unit #2 has inputs 9-16, and unit #3 has inputs 17-24. The same is
true for a system with 48 inputs, but now additional terminal blocks are added.
See Figure 3-8 for more detail.
Figure 3-8: Terminal Block Ordering
18
3.6 Terminal Base

The terminal base (part number 177936-01) is the backplane unit into which you
insert all 3701 ETS cards and modules. Figure 3-9 illustrates the terminal base.
The network and power connections to the various modules are made in the
terminal base. The terminal block assemblies also plug into the terminal base.
Figure 3-9: Terminal Base
3.6.1 Network Connections

The ETS has two network connections for redundant UDH networks on the
terminal base. These connections are located on the top of the unit, as shown in
Figure 3-10. In this picture, network A is on the bottom, and network B is on the
top. The network ports are triple-speed, meaning that they support 10Mbps,
100Mbps, or 1000Mpbs (gigabit) Ethernet. These ports are assigned “static” IP
addresses, and can be set to any address. They ship from the factory with default
IP addresses of 192.168.0.101 for port A and 192.168.1.101 for port B. The default
netmask is 255.255.255.0. Please refer to the MPC™ software manual for
instructions on setting the IP addresses of these ports.
19
Figure 3-10: Top View - Ethernet Connections
3.6.2 Power Connections

The 3701 ETS also accepts redundant supplies on the top side of the terminal
base. These are nominally +24Vdc, although the unit will operate in a range from
+18 to +36Vdc. The supplies are labeled primary and secondary and are located
next to the RJ45 network connectors, as shown in Figure 3-11. Each supply has 3
connections: +24V, common, and chassis. Note that there is also a chassis
isolation switch. This switch can be used to supply an external chassis
connection, and there is a terminal available on this switch for such a connection.
Figure 3-11: Power Connections
20
The following table details the power connections:
Table 3-13: Summary of Power Supply Connections

Pin Description
Chassis. Connect the chassis from your power supply to this terminal
This is the power common. Connect the common on your power supply to
COM
this terminal
This indicates the primary +24V supply. Connect this to the +24V output of
PRI
your power supply.
This indicates the secondary +24V supply. Connect this to the +24V output
SEC
of your power supply.
21
3.7 TMR Relay Module

The TMR relay module (part number 178778-01) looks similar to the other 3701
ETS units, but is a little smaller and does not have separate card slots. Refer to
Figure 3-12. This unit receives the outputs from the 3701 ETS units via the output-
to-relay cable, performs 2-out-of-3 voting, and provides the contacts to drive trip
signals. The TMR relay module provides six output contacts. These contacts are
dry contacts, and the system should supply an external voltage from the
solenoids. The terminal blocks allow the solenoids to receive their power directly
through the contacts, or allow the contacts to simply complete the circuit.
Additionally, the TMR relay module provides alarm contacts to indicate if its own
+24V supply or the solenoid voltage has failed. The unit can individually operate
the contacts for each channel in a “de-energize to trip” mode or an “energize to
trip” mode, which is controlled via a DIP switch for each channel.
Figure 3-12: TMR Relay Module
22
3.7.1 Wiring Diagram

All solenoid connections are made at the terminal blocks. The pins have been laid
out in such a fashion that the solenoid voltages may be brought in to the module,
or wetted externally. Refer to Figure 3-13 for outputs 1 through 4.
Figure 3-13: Relay Terminal Block
The six outputs are labeled “OUT 1” through “OUT 6”, and each output has a “+”
and “-“ connection for the contact. The terminal blocks also provide power inputs
for the solenoid power. If your installation will provide external power for the
solenoids, simply connect the “PWR IN” so that the relay module can monitor the
voltage. If you will not provide external power for the solenoids, then after
connecting the “PWR IN”, simply jumper it to the contact “+” and “-“ pins. The two
rows of terminal connections simplify connections. For example, you can connect
the power and contacts on the bottom row, then on the top row, make the
jumper connections between “PWR IN” and “OUT N” if you will supply the solenoid
power through the contacts. Table 3-14details the pins.
Table 3-14: Summary of Relay Terminal Block Pins

Pin Description
PWR IN - High-Voltage or solenoid power common or ground.
High-Voltage or solenoid power. This is the “hot” or positive power
PWR IN +
connection.
This is one of the two sides of the output contact. It does not matter what
voltage is connected here, but if the solenoid requires a certain polarity, the
OUT X - ‘-‘ designation can be used for consistency. Furthermore, if PWR IN is
jumpered to the contact output, this can be used for consistency here as
well.
23
Pin Description
This is one of the two sides of the output contact. It does not matter what
voltage is connected here, but if the solenoid requires a certain polarity, the
OUT X + ‘+‘ designation can be used for consistency. Furthermore, if PWR IN is
jumpered to the contact output, this can be used for consistency here as
well.
24V ALRM Two terminals for 24V alarm contact. Open circuit indicates alarm
ALRM Two terminals for high-voltage alarm. Open circuit indicates alarm.
Figure 3-14 shows the power and contacts for outputs 5 and 6, as well as the
alarm contacts. You can see there are two terminals for the 24V alarm, and two
terminals for the solenoid (high) voltage alarm. These alarm contacts are always
“de-energize to trip”, and are closed during normal operation. An open indicates
an alarm.
Figure 3-14: Relay Terminal Block (continued)
24
A common configuration for trip applications is a two-out-of-three trip block, with
contacts on both sides of the solenoid. An example in Figure 3-15 illustrates one
of the three solenoids. HV indicates “high voltage”, and is the voltage required to
activate the solenoid. Two contacts are placed in series for redundancy around
the solenoid. In the wiring diagram, you can see how the high voltage supply is
connected to the PWR_IN- terminal, which is jumpered to OUT1-. OUT1+ is then
connected to one side of the solenoid. The other side of the solenoid is connected
to OUT2-. Note that OUT2+ is jumpered to the PWR_IN+ terminal. This same
wiring process would be repeated for solenoid 2 (using OUT3 and OUT4) and
solenoid 3 (using OUT5 and OUT6). You can see how the duplicate terminal blocks
(same connections on both upper and lower blocks) allow for simple jumpering,
clean wiring and added reliability because only one wire per terminal is required.
Figure 3-15: 2oo3 Wiring Example
25
3.7.2 DIP Switches

The TMR Relay module provides six DIP switches that are located next to the
terminal blocks. You use these switches to configure the function of each
channel for “energize to trip” or “de-energize to trip”. Figure 3-16 shows the DIP
switches. The switch should be in the “OFF” position for “de-energize to trip”
mode, and in the “ON” position for “energize to trip” mode.
Figure 3-16: DIP Switches
Table 3-15: TMR Relay Module DIP Switch Functions

Switch Position Channel Function
OFF De-energize to trip
ON Energize to trip
26
3.8 TMR Cable

You can identify the TMR cable (part number 179229) by its unique construction,
shown in Figure 3-17. The cable has 3 ends, each of which has a DB44 connector.
Each length of cable is redundant. The TMR cable allows the 3 ETS units to share
input signals. Each 3701 ETS unit physically lands one-third of the 48 discrete
inputs and 6 speed inputs, so that each unit lands 16 discrete inputs and 2 speed
inputs. This cable sends the inputs from each ETS unit to the other ETS units.
Each input card requires 1 cable, so that a system with all 48 discrete inputs
would require 2 cables. Each connector of the cable has screws to securely
mount the cable to the ETS unit.
Figure 3-17: TMR Cable
27
3.9 Output-to-Relay Cable

This cable (part number 178657-01), shown in Figure 3-18, connects the three
3701 ETS units to the TMR relay module. One end of this cable terminates in a
DB44 connector that plugs into the relay module. The other end of the cable
splits into three sections, each of which has flying lead wires that terminate in a
pluggable terminal block. These terminal blocks plug into 3701 ETS output
modules. For convenience, this cable is configured to connect to the “N.O.” pins of
the output cards for “de-energize to trip” operation. You can change this
configuration if your application requires “energize to trip” operation. Refer to the
output card section for wiring details.
Figure 3-18: Output-to-Relay Cable
28
Section 4 - Installation
4. Installation
4.1 Physical Mounting

Each ETS unit provides 4 mounting holes, located in the corners. These holes are
used to mount the units to a panel. You must mount the units in a vertical
orientation for proper airflow. You must also mount the units within close enough
proximity to allow connection of the TMR cable.
Figure 4-1 shows a side-by-side installation. Note that you need not mount the
units side by side, and can mount the units vertically instead. If you choose to
mount the units vertically, you must locate the units close enough to connect the
cables and oriented the units so that the cables point downward. Connect the
TMR cable as shown in Figure 4-1.
Figure 4-1: ETS Units
You must also connect the ETS units to the TMR relay module. You do this by using the
output-to-relay cable, as shown in Figure 4-2. Connect the DB44 to the TMR relay
module, and the terminal block plugs into the receptacles on the back of each 3701 ETS
unit.
29
1. Discrete inputs
2. Relay module
3. Inserts into receptacle
Figure 4-2: ETS System
30
Section 4 - Installation
4.2 Software Installation

The application that configures and monitors the ETS trip system is the MPC software. It
contains many features and subprograms. To install this software, simply insert the CD
and follow the on-screen instructions. The default directory for installation is D:\NGDCS
although you can select another drive or directory during installation. Refer to the MPC
software user manual for further installation and configuration options.
31
Section 5 - Configuration
5. Configuration
You configure most of the ETS unit via the MPC software package for which you
should refer to the MPC software user manual for detailed instructions. However,
this section includes some of the more basic functions of that software for your
convenience.
5.1 Connecting to Your 3701 ETS Units

Once the 3701 ETS units are installed, you must connect to them and give them a
unique static IP address. By default, all 3701 ETS units have the same IP address.
For this reason, you must connect to them individually and set their IP addresses
before connecting all units on the same network. The following instructions detail
this procedure.
1. Physically connect the ETS unit you wish to update to the network, as you
must set the IP addresses one-by-one. Use a CAT5 Ethernet cable to connect
the ETS unit to a switch or directly to your host computer.
2. Configure the IP address of the host computer (PC). By default, the ETS units
have IP addresses 192.168.0.101 for port A and 192.168.1.101 for port B, and a
default netmask of 255.255.255.0. You must configure your network
interfaces so that the host computer is on this same subnet. To do so:
a. Right-click on “My Network Places”.
b. Select “Properties”.
c. Select the interface you wish to edit, and select “Properties”.
d. Edit the TCP/IP properties. Figure 5-1 shows an example of setting the
local IP address to 192.168.0.56. This allows your computer to connect
to Port A of the 3701 ETS.
e. Click “OK”.
33
Figure 5-1: Setting the Local IP Address
3. Configure the MPC software. To do so:

a. Click on the Basic Information and Network Configuration item in the
tree view. You should see the window shown in Figure 5-2.
b. Edit the IP addresses so that they match the IP addresses you
configured for your local machine in Step 2.
c. Click “Save the Current Setting”. If you close the MPC software and
open it again, you should see your saved settings.
34
Figure 5-2: Editing Network Info
4. Be sure that the ETS unit is powered on and allow a couple minutes for it to
boot. Refer to the LED table for the CPU to determine if the CPU has booted.
5. Double-click the MPC icon to launch the MPC software.

6. Ensure that at least one of the network connections is green and indicates
“Good”, as shown in Figure 5-3. If the screen indicates that neither network A
or network B is “Good”, then your host computer IP address has a problem,
the network connection is bad, or the ETS unit’s IP address is no longer the
default IP address.
35
Figure 5-3: Good Network Connection
7. Click on the SystCFG icon to launch SystCFG.

8. From SystCFG, click on the New Node tool to create a new node numbered
101, as shown as shown in Figure 5-4. Be sure to select “ETS Controller” as the
type. NOTE: The node number is always the last octet of the IP address (e.g.
192.168.0.101).
Figure 5-4: Create Node 101
9. Click on the Link tool to link to the ETS unit, as shown in Figure 5-5.
36
10. Once connected, right click on the node and select ”Properties…”
Figure 5-5: Node Properties
11. Select the “Platform” tab.
37
12. Edit the IP address of the S unit (ETS101) as shown in Figure 5-6. ETS units are
TMR in fashion, meaning that there is an R, S, and T unit. Here, node 100 is the
R unit, node 101 is the S unit, and node 102 is the T unit.
Figure 5-6: Editing the IP Address
13. Click “OK”, and the unit will automatically update its IP address.
14. Click “OK” to reboot.
15. Repeat for the other 2 ETS units
Application Advisory
Once you change the IP address, the node number
for the unit will change! This means that when you
next try to connect to the unit, you will no longer use
node number 101. Rather, you will use the last octet of
the IP address to which you’ve set the unit. For
example, if you updated the IP address to
192.168.101.35, then you would link to node number
35. Note that it is common practice to give ETS units a
node number between 1 and 40.
38
5.2 Configuring Your 3701 ETS Units

After you configure the 3701 ETS units with the proper IP addresses, you can
configure them. There are several items you should consider when configuring
the 3701 ETS system. The following sections discuss these.
5.2.1 Supported Function Blocks

There are many function blocks in the SystCFG software. Table 5-1 summarizes
the complete list of supported function blocks.
Table 5-1: Summary of SystCFG Function Blocks
Function
Description Symbol
Block
Digital Input. These are physical inputs into the ETS
system. There are 48 DI’s supported. These are
numbered 1 to 48. For simplicity and to reduce
XDI
function blocks, the XDI block has an optional
inverter and debouncer built in (equivalent to adding
a NOT block and TIMER block).
Speed Input. These are physical inputs into the ETS

system. There are six SI’s supported. These are
numbered 1 to 6. These can be configured either as
proximity probes or magnetic pickups. Each block
XSI
displays the current and peak RPM, and has three
digital outputs that can be used in the trip logic. The
digital outputs are configured by setting thresholds
in the XSI block.
Network DI. This is a discrete (Boolean) input into

the system that is not physical, but comes over the
Ethernet Global Data (EGD™) link on the network.
This block should be used judiciously, as CPU
failures will result in this point not being updated.
In this failure case, this block will drive its default
value. Once configured, it behaves like any other
XNetDI digital input in the system. There is one caveat with
XNetDI blocks. They should be used just like XDI
blocks, meaning that all XNetDI blocks should have
unique names. You should not place two XNetDI
blocks and have them reference the same point.
This will not work as intended. Rather, you should
place one block, and use the connector tool to
connect it to multiple places.
39
Function
Description Symbol
Block
Page DI. This block allows trip logic to be extended
across configuration pages. For example, if several
XPgDI blocks are used to create a signal that you wish to
use elsewhere in the logic, an XPgDI can be used to
take that signal to another page.
Digital Output. These are physical outputs from the
ETS system. There are eight DO’s supported.
Typically, the first six of these are connected to the
XDO
TMR Relay Module, and the other two are general
purpose. This should be the last block in the trip
logic.
Network DO. This is a discrete (Boolean) output
from the system that is not physical, but is sent over
EGD link to the network. This allows other devices
on the unit data highway to have visibility of the
XNetDO
data. For convenience, all XDI and XDO blocks have
an XNetDO built in. Additional XNetDO blocks can
be used to make internal logic visible via the EGD
link.
Page DO. This block extends trip logic so that it can
be used on other pages. By default, and XDI or XDO
XPgDO can be used on other pages via an XPgDI. However,
if there are internal signals that you wish to extend
to other pages, and XPgDO will allow this to occur.
AND Two-input AND gate.
OR Two-input OR gate
NOT NOT gate
XOR Two-input XOR gate
40
Function
Description Symbol
Block
Multi-functional, eight-input gate.

This functions as a generic M-out-of-N block. If M =
QOR8 1, then it functions as an OR gate. If M = N, then it
functions as an AND gate. If 1 < M < N, then it
functions as a typical M-out-of-N, such as 2oo3.
Rsflp RS Flip Flop. Typically used to store a value.
Multi-function Timer. There are three modes this

block can have: pulse, TD_ON, or TD_OFF. Pulse
mode sends a programmable-width pulse when the
digital input goes HIGH. TD_ON detects the input
Timer going high, and makes sure it remains high for a
programmable time period before driving the
output high (similar to debouncing). TD_OFF does
the same, only drives low after the input has been
low for a time.
Digital Manual Block. This allows software-

D/MA controlled digital signals. With this block, you can
set, reset, toggle, or pulse the output.
5.2.1.1 Properties Common to all Blocks

All blocks have a properties tab, shown in Figure 5-7. Of particular interest are
the BNum and Order fields. The software automatically assigns these, but you
can modify them. All BNum entries MUST be unique across all function blocks, so
you typically should not modify this field. The Order field indicates the order in
which the software evaluates the blocks on the page. The software sets this field
in increments of 10 in the order in which you place the blocks, but this may not be
the correct order in which the software should evaluate the blocks. There are two
methods to ensure that the order of evaluation is correct. The first method is to
drop blocks onto the page in the order in which you want the software to
evaluate them (typically inputs first, then intermediate logic, and then outputs).
This method is not always feasible while you are designing the logic. The second
41
method is to edit the Order property of each block after you have placed all the
blocks, to ensure that the software evaluates them in the correct order.
Figure 5-7: Block Properties
On the “Point Dir” tab, options are configured for the point information. This
includes the EGD timeout, tagname, a description, and various other parameters.
Refer to Figure 5-8 and Table 5-2 for details of these parameters.
42
Figure 5-8: Point Directory Configuration
Table 5-2: Summary of XDI Parameters

Parameter Description Valid Ranges
Tout EGD Timeout Period (seconds) See drop down list
Tag EGD Point Name (text) Limited to 30 characters
Desc Description of the point (text) Limited to 96 characters
Attrib User Defined Attribute code Limited to 6 characters
AlmGrp Alarm Group Limited to 6 characters
ZeroSm Refer to MPC User Guide
OneSm Refer to MPC User Guide
Except Refer to MPC User Guide
ExcMax Refer to MPC User Guide
ExcMin Refer to MPC User Guide
Record Refer to MPC User Guide
Cmpres Refer to MPC User Guide
CmpMax Refer to MPC User Guide
CmpMin Refer to MPC User Guide
MaxY Maximum value of Y axis on trend plot 0 - 65535
MinY Minimum value of Y axis on trend plot
43
5.2.1.2 XDI
XDI is a discrete input block. This function block represents the physical discrete
inputs into the system. The ETS supports 48 discrete inputs, which are numbered
1-48 on the terminal blocks. In the software, you configure an XDI block for 1-48
to correspond to the physical input number. Before you do this, you may need to
change the page properties so that the address format is correct (see Figure 5-9).
If you do not change the address format, then you must enter the addresses for
the XDI blocks as 1-1-1 to 1-1-48 instead of 1 to 48.
Figure 5-9: Address Format
44
Double-click on the XDI block to configure its properties. Configuring an XDI
involves many steps. There are many parameters available. Refer to Figure 5-10
and Table 5-3 for more information.
Figure 5-10: XDI Parameters
Table 5-3: Summary of XDI Parameters

1-48 or
Addr Physical Input number of the XDI
1-1-1 to 1-1-48
0 – DI, No Invert
1 – DI, Invert
Cvt Type / Invert
2 – SOE, No Invert
3 – SOE, Invert
Indicates the number of seconds this XDI must be “1”
before the function block assumes the value of “1”. If the
TD_On 0 – 255
input goes to “0” before this time has elapsed, the block
will not change state.
Similar to TD_On, only the XDI must transition to “0” for the
specified time period before the block will take on the
TD_Off 0-255
value of “0”. NOTE: You can ONLY set TD_On or TD_Off.
NOT BOTH.
LID Local ID. Set by software. Do not modify
45
Share flag. Indicates if this point is shared. If it is shared,
it gets sent on the EGD link using a broadcast address. If it 0 – not shared
SH is not shared, it is sent on the EGD link using a multicast
address. Note: if the point is to be used as an XNetDI on 1 – shared
other units, it must be shared.
0 – automatically ACK
No Auto ACK. When set, the ETS will not automatically alarms
NAA ACK alarms on this point. If cleared, the ETS will
automatically ACK alarms for this point 1 – do not
automatically ACK
See drop-down menu.
T EGD Broadcast period for this point. Can also take on page
period.
Alarm. Indicates if this point should indicate an alarm,
AA See drop-down
and if so, if it should alarm when the input is 0 or 1.
P Priority of the alarm 0-255
The “Properties” tab also contains the “Order” property. This property is one of the
most important parameters associated with all blocks, not just XDI.
Figure 5-11: Function Order
As Section 5.2.1.1 discusses, the SystCFG software initially assigns the Order value
when you drop a function block onto a page. However, you can change these
values. The Order value indicates the order in which software evaluates the
function blocks. It is imperative that software evaluates the functions in the order
that you expect. Otherwise, the logic may not function properly, or may take
46
much longer than expected to converge. Typically, software should evaluate any
function block that has no inputs first, then function blocks once all of their inputs
have been evaluated, and so on.
5.2.1.3 XSI
XSI is a speed input block. This function block represents the physical speed
inputs. The XSI block has two “analog” outputs, and three digital outputs. The
“analog” outputs indicate the current speed in RPM (Y) as well as the highest
speed that has been detected (Yp). The digital outputs (D1 through D3)
correspond to alarm threshold settings that the software uses to drive the trip
logic. D1 and D2 are overspeed thresholds, and D3 is an underspeed threshold.
You configure the threshold levels in the XSI properties, which are detailed below.
The XSI also has six alarm thresholds. For H, HH, and HHH alarms, the alarm
activates when the RPM value goes above the specified threshold. For L, LL, and
LLL alarms, the alarm activates when the RPM value goes below the specified
threshold. These alarms are hierarchical. That is, if the RPM goes above the H
threshold, the software issues an H alarm. If the RPM continues above the HH
alarm threshold, then the software issues an HH alarm, and the system is no
longer in the H alarm state. If the RPM then decreases below the HH threshold,
but still above the H threshold, the system will transition back to the H alarm
state. As outlined in Table 5-4, some of these alarm thresholds also correspond to
digital output thresholds that the software uses to drive the trip logic.
Figure 5-12: XSI Speed Input Block
47
Similar to XDI blocks, XSI blocks have an address parameter that corresponds to
the physical address of the input. For example, if your speed sensor is connected
to “S1” on the terminal blocks, then the “Addr” field should contain “1”. If you did
not modify the page settings, and this field still uses the format “xx-xx-xx”, then
you should enter 1-1-1 to 1-1-6 for speed inputs. Table 5-4 describes some of the
parameters that are unique to XSI.
Table 5-4: Summary of XSI Parameters
Addr Physical Input number of the XSI 1-6
Indicates if the speed sensor is a proximity probe or a magnetic 0 = prox probe
Type
pickup 1 = mag pickup
Indicates the number of teeth on the gear used to detect speed.
Nteeth 1 – 65535
It tells the ETS how many pulses per revolution it should expect.
HHH Third upper limit alarm. 0-65535
Second upper limit alarm. This also controls the digital output
HH 0-65535
D1. If the RPM exceeds HH, then D1 will drive to a ‘1’.
First upper limit alarm. This also controls the digital output D2.
H 0-65535
If the RPM exceeds H, then D2 will drive to a ‘1’.
First lower limit alarm. This also controls the digital output D3.
L If the RPM falls below L, then D3 will drive to a ‘1’, indicating an 0-65535
underspeed condition.
LL Second Lower limit alarm. 0-65535
LLL Third Lower limit alarm 0-65535
Dead Band. This is similar to Hysteresis. This indicates how
much below the upper limit, or how much above the lower limit
the RPM value must go before it will transition out of the alarm
state. For example, if the H alarm limit is set to 3600 rpm, and
DB is set to 100, then the system will go into H alarm and D2 will
DB 0-65535
go to ‘1’ if the RPM goes equal to or above 3600. It will remain in
alarm and D2 will continue to drive until the RPM falls below
3500. Likewise, if the L alarm limit is set to 2000 RPM, and the
RPM falls equal to or below 2000, D3 will drive high until the RPM
comes back above 2100.
5.2.1.4 XNetDI
The XNetDI is a unique block. XNetDI is a discrete input that comes off the
network, rather than from a physical input. That is, it is an EGD point that the
software consumes and uses to drive the logic. To configure this block, you
simply enter the global name of the point you wish to consume. For example, if
the system has a point labeled “3500_Axial_Trip”, which may be an EGD point
produced by a Bently Nevada 3500 system, you would enter the name as shown
in Figure 5-13.
48
Figure 5-13: XNetDI Configuration
This XnetDI block would then receive the updates of the EGD point at the frame
rate and update the internal logic accordingly.
5.2.1.5 XPageDI
The XPageDI allows the user to extend digital logic from one configuration page
to another. For example, assume the software uses an XDI to drive logic on a
particular page. The software can then use the XpageDI block to use the XDI to
drive logic on a different page.
49
5.2.1.6 XDO
The XDO is the actual physical discrete output. This is the signal that is used to
trip the solenoid valves. It is similar in nature to an XDI, except that it has a “fail
safe” value that can be configured. Should any of several certain internal errors
occur in the system, and it can no longer guarantee proper operation, this value
will be driven on the outputs to ensure “fail safe” behavior. The SafeS bit should
be set to the state that will cause the machine to safely shut down. Figure 5-14
shows the configuration of this value.
Figure 5-14: Fail Safe Configuration
50
5.2.2 Creating a Configuration

A typical Emergency Trip System configuration combines all trip-related input
signals with some trip logic and ultimately drives contacts to trip the machine. As
mentioned in previous sections, inputs to the system can be discrete inputs
(which may indicate vibration, temperature, pressure, etc, trip conditions), and/or
speed inputs. You can input all of these inputs into your trip logic, which will drive
up to 6 contacts. In a 2-out-of-3 scenario, the 6 contacts would likely control 3
solenoid valves, with 2 contacts in series with each solenoid.
Figure 5-15 shows an example configuration. This example configures 3 speed
signals (1 signal from the HP, 1 signal from the LP, and 1 signal from the Gen) in a
2-out-of-3 voting fashion. The configuration ORs the result with a vibration,
pressure, and temperature alarm signal. The result will trip all 6 output contacts
(and subsequently all 6 solenoid valves). This example also includes a software-
controlled reset.
Figure 5-15: Example Trip Logic Configuration

The following steps show how to create this configuration and download it to the
ETS units.
51
1. Click Link tool to link to the ETS controller from SystCFG
2. Click the New Page tool to create a new page.
3. Select the Available Functions tool to display available function blocks.

4. Drag each block onto the page. Note: If you wish for software to execute the
logic in the order in which you connect the blocks, you must place the blocks
in that order. Otherwise you must alter the function block order property.
5. Connect the blocks together by clicking on the output of one block and
dragging to the input of another.
6. Assign input physical addresses. You should number speed inputs from 1 to 6.
You should number discrete inputs from 1 to 48, as the discrete input
numbers appear on the terminal blocks.
7. Assign physical addresses for the outputs. Discrete outputs are numbered
from 1 to 8. The first 6 outputs go to the TMR relay module. The other 2
outputs are general purpose outputs for the user.
8. If you want software to send the points via EGD link, be sure to give them a
tagname.
9. Click the Save tool to save the configuration locally.
10. Click the Download tool to download the configuration to the ETS unit.
52
Section 6 - Maintenance
6. Maintenance
6.1 Software Maintenance

Please refer to the MPC software manual for license agreements and
maintenance.
6.2 Firmware Upgrade

As new ETS features and functions become available, you may need to upgrade
the firmware on the ETS units. This procedure is extremely straightforward. It is
important to note that the upgrade procedure may require the unit to reboot, so
you should conduct the upgrade process during a planned outage. This is the
preferred method.
An alternative is to upgrade each of the three units independently (i.e., upgrade
one unit and allow it to return to service, then upgrade the next, and so on) while
the system is online, but this method compromises the safety function of the
system. In this method, only 2 units will always be functioning, and the 2-out-of-
3 voting system will essentially be a 2-out-of-2 system. Of course, this method
has inherent risk.
Finally, it may be possible to upgrade the firmware without any loss of protection.
These are special circumstances in which the FPGA does not need updated, but
the firmware does. In this case, the CPU will reboot, but the FPGA will continue to
provide protection. When the ETS product team releases a firmware revision,
they will disclose such possibilities indicating the “from” revision and the “to”
revision.
The following instructions describe how to upgrade the firmware.
1. Obtain the firmware upgrade file. You can obtain this either online or on a CD.
Contact your Bently Nevada, LLC representative if you require assistance.
2. Save the upgrade file to a known location on your local hard drive.
3. Double click the MPC icon to launch MPC.
4. Double-click the SystCFG icon to Launch SystCFG.
5. Click the Link tool to link to the ETS unit
6. Click the operation button .

7. Select “Upgrade Firmware”.
8. Click “Exec” in the Firmware Upgrade dialog shown in Figure 6-1.
53
Figure 6-1: Firmware Upgrade Dialog
9. Browse to the file called 3700UpgradePkg.tar.gz and click “OK”.
Figure 6-2: File Selection
54
Section 7 - System Verification
7. System Verification
7.1 Configuration Validation
Before commissioning the ETS system, you must verify that the configuration is
operating as desired. It is your responsibility to perform a commissioning test,
otherwise the ETS is not authorized to perform as a functional safety unit. If
you do not perform this validation test, you can make no claims of functional
safety. Furthermore, it is at your sole discretion to pronounce satisfactory
behavior and commission the ETS system into functionality. As such, these
validation procedures listed below may be insufficient to fully qualify an
installation, but are provided as a minimum guideline to start the validation
procedure.
7.1.1 Input Validation

You should validate proper operation of every input to the ETS system. This
includes both discrete inputs and speed inputs. This validation should be
performed AFTER all wiring has been completed, and should be repeated after
any changes to the wiring have been made.
For each Discrete input into the system, you should do the following:
1. In the driving equipment or device, force the contact to the closed
state.
2. Verify with SystCFG that the correct input is driving logic “1”.
3. In the driving equipment or device, force the contact to the opened
state.
4. Verify with SystCFG that the correct input is driving logic “0”.
For each Speed input into the system, you should do the following:
1. Verify the RPM reading in SystCFG matches the current machine speed.
2. Reset the peak RPM and verify that the RPM reading is consistent (no
glitches).
3. Ramp the machine speed up and down and verify the RPM follows as
expected.
7.1.2 Logic Validation

You should validate proper behavior of the trip logic. Part of this validation
includes the steps from the input validation section. Additionally, you should use
55
SystCFG to validate the logic state of each function block when a change is made
to any input.
7.1.3 Output Validation

You should validate proper operation of the outputs. For each of the 6 outputs
from the 3701 ETS to the TMR relay module, you should perform the following
tests:
1. Cause the output to go active (by forcing inputs or simulating
overspeed, etc.)
2. Verify through SystCFG the output is in the active state.
3. Verify the LED indicator on the ETS Output Card reflects the output is
driven.
4. Verify the LED indicator on the TMR Relay module reflects the output is
driven.
5. Verify the contact is either open or shorted, as designed. If solenoid
valves are connected, verify proper operation of the valve.
7.2 Online Proof Tests

Periodically, you should test the system while the machine is online to ensure that
the system can still perform its safety functions. For maximum test coverage, this
should be an end-to-end test. That is, inputs should be forced, and the ETS should
close specific valves at the output. The methodology that is employed determines
the effective coverage of the test. In general, we recommend that you investigate
and immediately fix any “Not OK” condition. Furthermore, when the ETS unit is
indicating “Not OK”, you should consider that its safety function is compromised.
The following sections provide some suggestions for online testing.
7.2.1 Testing Discrete Inputs

Since all 3 ETS units share inputs, you must construct online tests in a manner
that will not shut down the machine. This depends largely upon the trip logic. The
commissioning validation test should have proven that the equipment connected
to the ETS discrete inputs is functioning properly. However, you can still test as
follows:
You should complete the following procedure in its entirety for each input. That is,
only test one input at a time.
1. Ensure there are no alarms and no “NOT OK” conditions.
2. Ensure you have Administrator privileges.
56
3. Right-click on the input and disable the point in the two units that are
not under test. At this point 2 of the 3 ETS units will have locked the
state of this discrete input to the known good state.
Application Advisory
Since 2 of the 3 inputs are disable, should an actual
trip event occur on this specific discrete input during
the period when they are disabled, a trip will not
occur. Therefore, the safety function for this input is
not functional during this period. The period in which
inputs is disabled should be minimized, and only one
input should be tested at a time.
4. At the equipment generating the input, cause a state change to occur.

For example, if connected to a vibration monitor that opens a contact
upon excessive vibration, force the contact open in the vibration
monitor.
5. Verify that the value of the discrete input has not changed in the 2 ETS
units that have the input disabled.
6. Verify that the value of the discrete input has changed in the remaining
ETS unit that has the input enabled.
7. Verify that all trip logic downstream from the input functions as
intended.
8. At the generating equipment, return the input to its normal monitoring
state.
9. Verify that the value of the discrete input has returned to the normal
state in the ETS unit that has the input enabled.
10. Re-enable the input in the other 2 ETS units.
7.2.2 Testing Speed Inputs

Since you cannot generate an overspeed event while the machine is online, the
3701 ETS provides test speed inputs for online proof testing. We recommend the
following procedure for testing speed inputs:
It is highly recommended that you test a single speed input completely and return
it to normal operation before testing the next input.
57
1. Ensure that there are no alarms and no “Not OK” conditions.
2. Connect a test speed generator, such as a waveform generator, to the
test speed inputs on one of the speed inputs.
3. In SystCFG, double-click on the corresponding XSI block.
4. On the “Operator” tab, select “Test On”. This switches the input from
the normal speed input to the test input.
5. Verify that the RPM reported in SystCFG matches the output of the test
equipment. Keep in mind the “number of teeth” setting. The frequency
output from the test equipment will be divided by the “number of
teeth” in reporting the RPM. Here is an example:
Number of Teeth = 30
Waveform Generator Frequency = 1.8KHz
Frequency Detected Reported by ETS = 1800 / 30 = 60Hz.
Frequency is multiplied by 60 to get RPM: 60Hz x 60 = 3600 rpm.
6. Sweep the generator frequency and verify the RPM is following.

7. Bring the generator frequency above the overspeed threshold.
8. Verify the output of the XSI block in SystCFG changes state.
9. Verify all subsequent logic behaves as desired.
10. Return the generator frequency below the overspeed threshold.
11. Verify the output of the XSI block returns to normal.
12. Double-click on the XSI block
13. On the “Operator” tab, select “Test Off”. This will switch back to the real
speed input.
14. Verify the RPM indicated in SystCFG is the correct machine running
speed.
15. Optionally, on the “Operator” tab, select “Reset” to reset the peak RPM
observed by the ETS. Since your test caused an overspeed event, the
peak RPM reported will be larger than the actual experienced on the
real speed input.
7.2.3 Testing Outputs

Testing the inputs validates that the ETS unit will respond to changes in the
discrete inputs and speed. To ensure proper safety functionality, you must also
verify that the ETS outputs will truly shut down the machine when required. This
testing procedure greatly depends upon the configuration of your mechanical trip
58
system. For example, you may have a 2-out-of-3 (2oo3) or a 2-out-of-4 (2oo4)
configuration. You may have configured your system with “energize to trip”
relays and/or “de-energize to trip” relays. This section will describe a common
scenario with “de-energize to trip” relays in a 2-out-of-4 configuration as shown
in Figure 7-1.
Figure 7-1: 2-out-of-4 Solenoid Valve Configuration
This configuration indicates the valves to be: 20-1/AST, 20-2/AST, 20-3/AST, and
20-4/AST. Here they are configured in a serial/parallel configuration. In normal
operation, these valves are closed (that is, they do not allow oil to pass through).
When the ETS detects a trip event, all four valves open and the AST safety oil
pressure drops, causing the steam inlet valve to close. However, if only 1 of the
valves opens, the pressure drop is not sufficient to cause the steam inlet valve to
close. In this case, the ETS can detect a pressure change using the pressure
sensors 63-1 and 63-3 as indicated above.
Typically, the application would connect at least 1 contact from the ETS TMR relay
module to each solenoid. In this case, 4 contacts are used and allow individual
control.
For online testing, the general procedure would be as follows:
This procedure should be repeated for each discrete output.
1. Ensure there are NO alarms and NO “Not OK” conditions. This is
critical, as you don’t want to inadvertently shut the machine down.
2. Right-click on the output and disable the discrete output.
3. Force the discrete output to the shutdown state.
59
4. Verify that the TMR relay module indicates a high-voltage alarm. If
configured for “de-energize to trip”, this alarm will occur when the ETS
detects a voltage across a relay. In normal operation, all relays are
closed. When de-energized, the relays open, causing the machine to
trip. So if you force a discrete output to the shutdown state, the ETS
should detect a voltage across the relay, and the high-voltage alarm
will annunciate. Both an LED on the TMR relay module will indicate
this, as well as an alarm contact. This condition is expected and you
should verify it.
If the ETS does not detect the alarm, it suggests that the relay is stuck
in a shorted state. In this case, you should plan an outage and
replace the card. If your system is configured for “energize to trip”, the
same condition is true. The DIP switches on the TMR relay allow the
high voltage alarm to detect the condition for which there is no voltage
across the relay, because in normal operation the relay is open and
has a voltage across it. In either configuration, you should detect a
high voltage alarm.
5. Verify the change in safety oil pressure. Since 1 valve is opened, it is
dumping oil, and the pressure should change. However, since only 1
valve is open, the machine will not shut down.
6. Force the discrete output back to the normal operation state, and then
re-enable.
7. Verify that the high-voltage alarm goes away.
8. Verify that the safety oil pressure returns to normal.
60
Section 8 - Troubleshooting
8. Troubleshooting
This section contains a list of problems and potential solutions.
Table 8-1: List of Potential Problems and Solutions
Problem Try
Ensure that the supply voltage is between +18Vdc and +36Vdc.
Unit will not power
on Ensure that the power supply terminals are connected properly with chassis to
chassis, common to common and +24Vdc to either PRI, SEC or both.
Verify that the CAT5 cable is plugged into the ETS unit and the switch, hub, or host
computer. If the cables are not connected, plug them in now.
Verify that the link LED on the ETS unit is ON. and that the activity LED is blinking. If
there is no link, verify cable connections. If connections are verified, verify that
the CPU card is fully seated and latched into the unit. If there is still no link,
contact your product service representative.
Verify the IP address by “pinging” the unit. If the ETS unit does not reply, the IP
address is not set to what you think it is. In this case, open the MPC software
and run the “SelfTest” utility. This will show any units on the Unit Data
Highway. If you don’t see the unit, then its IP address is on a different subnet
from the host computer. You may not have reset the address from the factory
Cannot connect.
default, which is 192.168.0.101 for port A and 192.168.1.101 for port B. The
subnet mask on the UDH link is commonly set to 255.255.255.0. If your host
computer IP address does not match the first three octets (groups of 3 digits)
of the ETS unit, they will not see each other.
Verify UDP operation. If you have verified the IP address and you can ping the unit,
check if there is a green “good” status in the MPC software. If not, this means
your system is not receiving heartbeat messages. Check if your host computer
allows UDP broadcasts or if a firewall is blocking this type of message.
Verify TCP operation. If you have a green “good” status, and you have confirmed
the IP address of the unit you are trying to connect to, try to link. If you are still
unable to link, contact your product service representative.
Verify your configuration settings. The MPC software validates most settings, but
product revisions may have introduced certain bugs into the software.
- Verify that each point has a unique (and valid) address and tag name.
Discrete input values range from 1 to 48. Discrete output values range
from 1 to 8, and Speed input values range from 1 to 6.
- Verify that the inputs to all blocks connect to other blocks. The only
exceptions to this are as follows:
Cannot load
configuration 1. The QOR8 block does not require all inputs to be connected.
2. The Timer block does not require the RST pin to be connected.
3. The D/MA block does not require any inputs.
- Verify the execution order is unique for every block on a page.
- Verify that all Timer blocks have valid mode settings. Supported modes
are 1: Pulse, 2: TD_ON, and 3: TD_OFF.
61
Problem Try
Verify the configuration. XNetDI blocks receive their data over EGD link.
Verify that the source point name and GID in the XnetDI configuration are correct.
XNetDI block does Verify that the source point is configured for sharing. If not, it will not work.
not work. Verify that the source point is sending data using the EGDMonitor tool.
If none of the above solves the problem, contact your product service
representative.
Check the system event log in the historical alarm list. The ETS reports all Not OK
conditions here, and the detailed information will help locate the source of the
problem. If this information is not available to you, try the following:
Output Card OK Verify that the system power supply is valid (between +18Vdc and +36Vdc).
LED is off
Verify that the card is fully seated, and locked into position.
If the card still indicates Not OK, there may an internal problem, and this card may
need repair. Contact your product service representative.
problem. If this information is not available to you, try the following:
Verify that the system power supply is valid (between +18Vdc and +36Vdc)
Input Card OK LED Verify that the card is fully seated, and locked into position.
is off Verify the card is properly configured. You can do this by downloading the
configuration once more.
Verify that all field wiring is secure, with no shorts or opens.
problem. Furthermore, the CPU includes all input card and output card OK
statuses in the overall OK status. The state of the OK relay should also reflect
this status If this information is not available to you, try the following:
Verify that the Output card is OK (see above).
CPU OK LED is off Verify that the Input cards are OK (see above).
Verify that the unit has a valid configuration. You may need to download a new
configuration.
Power-cycle the unit, and check the OK status again.
62
Section 9 - Ordering Information
9. Ordering Information
9.1 Ordering Options
To order the 3701 ETS system, use the following part number and format. For
more detailed product information, refer to the 3701 ETS datasheet (part number
178777-01).
3701/85 – AXX – BXX – CXX – DXX – EXX – FXX
A: Redundancy
00 No Selection
01 Simplex (not currently available)
03 TMR
B: Input Slot 1
00 None
01 ETS Input Module
C: Input Slot 2
00 None
01 ETS Input Module
D: Wiring Termination
00 No Selection
01 Internal Euro Style Screw
02 External Euro Style (not currently available)
E: Output Slot
00 None
01 ETS Output Module
F: Approvals
00 None
01 CSA N/RTL (NA Zone 2)
02 ATEX/Zone2 [nAC]
03 Multi-Approvals
63
9.2 Spares
This section contains the information for ordering spare parts for the 3701 ETS.
Table 9-1: Spare Part Numbers and Descriptions

Part Number Description
179483-01 This document
3701/85 Top-level ETS part number
177936-01 ETS terminal base assembly. This is the base into which all cards plug.
177471-01 Terminal Block Assembly, Channels 1-8, Speed 1.
177498-02 Terminal Block Assembly, Channels 33-40 Speed 5.
177504-02 Terminal Block Assembly, Channels 41-48 Speed 6.
177933-01 ETS CPU Module
177934-01 ETS Input Module
177935-01 ETS Output Module
178778-01 ETS TMR Relay Module
179229 ETS TMR Cable
178657-01 ETS Relay Module Cable
178777-01 Datasheet
64

3701 Emergency Trip System (ETS)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3701 Emergency Trip System (ETS)

Uploaded by

Copyright:

Available Formats

System Manual

Bently Nevada™ Asset Condition Monitoring

3701 Emergency Trip System (ETS)

Part Number 179483-01

Copyright 2008. Bently Nevada LLC.

The information contained in this document is subject to change without notice.

The following are trademarks of the legal entities cited:

Windows is a trademark of Microsoft.

Velostat is a trademark of 3M.

Mailing Address 1631 Bently Parkway South

3701 ETS Datasheet (Part Number 178777-01)

Product Disposal Statement

1. Receiving and Handling Instructions..........................................................1

1. Receiving and Handling Instructions

1.2 Handling and storage considerations

3.1 3701 ETS Unit (3701/85)

Figure 3-1: 3701 ETS Unit

Table 3-1: 3701 ETS Unit Specifications

3.2 CPU Module (177933-01)

Figure 3-2: CPU Module

The CPU module is a high-performance computing interface. The label on top

3.2.2 LED Behavior

3.3 Input Card (177934-01)

Figure 3-3: Input Card

Table 3-3: Summary of 3701 ETS Input Card Specifications

Table 3-4 summarizes the OK LED behavior.

Table 3-4: Summary of 3701 Input Card LED Behavior

3.4 Output Card (177935-01)

Figure 3-4: Output Module

3.4.2 Relay Outputs

Figure 3-5: Output Card Relay Wiring

Figure 3-6: OK Relay Terminal

Table 3-6: 3701 ETS OK Relay Connections

Table 3-7: Summary of Not OK Conditions

A node voltage error on any card, Not Functional.

3.4.4 DIP Switch

Table 3-8: DIP Switch Settings

Table 3-9: DIP Switch Summary

3.4.5 LED Behavior

Table 3-10: Summary of OK LED Behavior

3.4.5.2 Channel LEDs

Table 3-11: Summary of Channel LED Behavior

3.5 Terminal Blocks

Figure 3-7: Terminal Block

Table 3-12: Summary of Speed Input Terminal Blocks

Figure 3-8: Terminal Block Ordering

3.6 Terminal Base

Figure 3-9: Terminal Base

3.6.1 Network Connections

Figure 3-10: Top View - Ethernet Connections

3.6.2 Power Connections

Figure 3-11: Power Connections

Table 3-13: Summary of Power Supply Connections

3.7 TMR Relay Module

Figure 3-12: TMR Relay Module

3.7.1 Wiring Diagram

Figure 3-13: Relay Terminal Block

Table 3-14: Summary of Relay Terminal Block Pins

Figure 3-14: Relay Terminal Block (continued)

Figure 3-15: 2oo3 Wiring Example

3.7.2 DIP Switches

Figure 3-16: DIP Switches

Table 3-15: TMR Relay Module DIP Switch Functions