GE Sensor Series H201TI 220VAC Control Application Transformer System

Description

For meaningful readings and good response time, the most important factors are proper location and installation of the H201Ti. For a typical transformer, the four most common locations to install the H201Ti are shown in Figure 2.

1. Radiator’s return pipe: The recommended location to mount the H201Ti is on the straight section of the radiator’s return pipe, which is joining the bottom of the radiator to the transformer’s main tank (on the discharge side of the pump to avoid negative pressure). This location presents the H201Ti with the best combination of oil flow, temperature and ease of access.
2. Filling valve (top of tank): In terms of performance (excellent convective oil flow), this location is a very good alternative location to install the H201Ti. However, the higher operating temperatures somewhat reduce the Hydran 201 sensor lifetime. Access to the H201Ti is also more difficult.
3. Inlet of radiator: See the comments on location2.
4. Drain valve (bottom of tank): At this location, the H201Ti performances are good, rather than excellent. The low oil flow may affect the gas level readings; however, the lower operating temperatures and ease of access make this location a valid alternative choice.

Do not separate the Hydran 201Ti Intelligent Transmitters from their respective Hydran 201 sensor. The H201Ti is set at the factory for a specific H201 sensor. To verify whether the two components are paired correctly, consult the serial numbers indicated on the shipping box and/or the Test Certificate and Data Sheet. The sensor’s serial number is located below the connector (see Figure 4 below); while the H201Ti’s serial number is located at the back of the heating plate (see Figure 5).

With the development of power plant applications, DCS has evolved from a relatively independent control island to a control system closely connected to external systems. Due to communication failures in the DCS network, local DCS crashes can occur, affecting the safe and stable operation of the unit. In severe cases, it can cause communication paralysis in the entire DCS network, unit tripping, and even affect the safety of the power grid. Therefore, network communication faults and their prevention in DCS systems have become important issues that need to be considered and solved at present.

Analysis of the causes of communication faults in DCS network There are several different nodes connected to the communication network of DCS, which are usually divided into two categories. One type is a node directly connected to the production process through an I/O board, called a controller. Another type of node is the other types of nodes that are connected to the human-machine interface, known as operator stations, engineer stations, historical stations, and dynamic data servers. The manifestation of local DCS crashes is: frequent operator station crashes; Initialization, crash, and disconnection of the Distributed Processing Unit (DPU); Redundant controller (server) switch unsuccessful; Data communication interruption, etc. In addition to being related to the maturity and reliability of application software design, it is also related to the severity of communication network congestion, mainly due to the following factors:

(1) Due to the inherent problems of the Microsoft WINDOWSNT operating system and the potential conflicts between DCS application software and the NT operating system during operation, using the NT operating system is more prone to operator station and engineer station crashes than using the UNIX operating system, especially when several special keys are pressed during keyboard operation, resulting in crashes. Under extreme operating conditions, external triggering factors can exploit security vulnerabilities in the NT operating system, triggering a large number of sporadic alarm messages, leading to network anomalies.

(2) When a node is connected to the communication network of DCS, a network interface is usually required. The controller sends data to the interface, and the human-machine interface reads data from the network interface. Reading data should comply with the network communication protocol. The commonly used communication protocol is broadcast, where nodes on the network send data to the network and continuously broadcast data, while nodes that need data receive it. In addition to this method, there is also an inquiry method where a node queries other nodes on the network for data, but if the other nodes do not have this data, it repeatedly queries until it reads the data. So if there is no such data on the network, it will cause network congestion.

(3) In the case of DCS operating for a relatively long time, the maintenance personnel of the power plant are constantly changing, and the configuration of the controller is also constantly changing. However, the application software configuration is only added and not reduced, and some configurations are actually no longer connected to the real I/O point. When the DPU reads data, all data points on the DPU are read in, and a large portion of the data is invalid, resulting in high DPU load rate and network congestion.

(4) After the software upgrade, the DCS network communication was blocked due to mismatched hardware drivers.

(5) Due to the need for MIS (or SIS) systems to read real-time production data from DCS, network congestion becomes very frequent when dynamic data servers are connected to the network, resulting in various human-machine interface nodes experiencing crashes.

(6) High external environmental temperature during DCS operation (such as faults in the control room air conditioning, power fan, and cabinet fan), large fluctuations in power supply, and long switching time are also important reasons for DCS shutdown.

Model recommendation:
S70601-SE
ALC12DE-010-1312
A6824
TG-13
MVI56E-MNET
VF1406M, C9
05704-A-0145
A6410
873EC-JIPFGZ-5
3CP260.60-1
AKM54K-ANC2AA00
VM600 IOC4T
PR9268/601-000
PDP403
UNITROL 1010
WR-D4007
CS513 (3BSE000435R)
PR6426/010-140+CON021
S60300-PB
SM100-40-050-P1-45-S1-B0
PP835A
6186M-17PT
MC-4/11/10/400
MKD071B-061-KP0-KN
T126-0001 REV.P3
IC754VSI12CTD
8440-2165 SPM-D2-11
PR9268/201-000
5AP920-1505.01
PR6423/003-030-CN
DKC11.1-040-7-FW
PR6423/003-030
10302/1/1
SCL055/30010/A/00/AA/AA/01/001
MDB-8E
1756-L72
6SM77K-3.000
MKD071B-061-KG1-KN
IC754CGL12CTD-FH
ISH070/60017/0/0/00/0/00/00/00/00
SE352
3500/42M
MVI56E-MNETC
2098-DSD-020X
SPNIS21
AN-X2-AB-DHRIO
IC693CPU374
LSH-050-2-45-320/T1.1R
ISH070/60017/0/0/00/0/00/10/00
5X00241G02
8MSA4X.R0-67
1326AS-B440G-21-A
CC-PDIS01
VT-MACAS-500-10/V0/I