using breaker and remote bits to implement controls

Date Code 20180720 SEL Application Guide 2018-21

Using Breaker and Remote Bits to Implement Controls Through DNP3 From an RTAC HMI

Aarti Gurav

INTRODUCTION

SEL Real-Time Automation Controllers (RTACs) are powerful components of a SCADA system for data concentration, IEC 61131 logic processing, remote control operations, and HMI visualization. This application guide focuses on two important features of the RTAC, which are issuing controls and the HMI. The RTAC family of products supports an optional web-based HMI to visualize data and create custom diagrams to monitor and control the system. ACSELERATOR Diagram Builder™ SEL-5035 Software enables you to create and manage HMI projects for visualization. This application guide is useful for engineers to program controls from an RTAC to IEDs. Operators can then use the capability programmed in the RTAC to control the system in case of an emergency. In most SEL relays, including the SEL-351S Protection System, breaker bits are generally used to control circuit breakers and remote bits are used to control other parameters in a relay.

NOTE: This application guide uses the SEL-351S and the SEL-3555 RTAC as examples to implement breaker and remote controls via HMI; it does not specifically recommend any protection logic settings.

Scope

The scope of this application guide is as follows:

➤ Illustrate configuring Ethernet communications settings between an RTAC and a relay to establish communication.

➤ Configure relay settings by using ACSELERATOR QuickSet® SEL-5030 Software with reference to the SEL-351S Instruction Manual [1] for implementing binary controls.

➤ Configure relay settings by using QuickSet for DNP3 communications with the RTAC.

➤ Configure the SEL-3555 by using ACSELERATOR RTAC® SEL-5033 Software to establish communication to the relay.

➤ Build an HMI by using Diagram Builder to implement controls.

Equipment

The following devices are used in this setup:

➤ An SEL-3555 RTAC [2] (note that other RTAC models can also be used, except the SEL-3505 and SEL-3505-3 because they do not have an HMI option)

➤ An SEL-351S Protection System

➤ An SEL-2730M Managed 24-Port Ethernet Switch

➤ A computer

Application Guide Volume VII AG2018-21

2

SEL Application Guide 2018-21 Date Code 20180720

Software

The following software is used in this setup:

➤ ACSELERATOR QuickSet SEL-5030 Software

➤ ACSELERATOR RTAC SEL-5033 Software [3]

➤ ACSELERATOR Diagram Builder SEL-5035 Software

CONFIGURATION

The SEL-3555 and the SEL-351S are connected through the SEL-2730M, as shown in Figure 1. Note that, although this application guide uses a managed Ethernet switch, an unmanaged switch would achieve the same results. You can use a laptop for configuration (if it is connected to the same switch) to communicate with the relay and RTAC. Note that the RTAC, relay, and laptop should be on the same subnet to establish communication. The process of configuring the Ethernet ports of the relay and the RTAC is described in the following steps. The SEL-3555 is used for this application because it can provide a web-based HMI.

NOTE: The IP addresses in Figure 1 are for illustrating the example and are not recommendations of any particular IP address setting.

Step 1. Configure the relay Ethernet port IP address.

a. Use an SEL-C662 Cable (serial-to-USB) to connect the serial DB9 port on the front of the relay to the laptop USB port.

b. Launch QuickSet and establish serial communication with the relay through the Communications Parameters window. The communications parameters set on PORT F of the relay and configured on QuickSet must match to establish communication to the relay.

c. After communication has been established, read the relay settings.

d. Go to Port 5 > Ethernet Port to open the Ethernet Port Settings. Enter the Device IP Address, Subnet Mask, and Default Router for the relay, as shown in Figure 2. In this example, an IP address of 10.37.17.59 is used. The goal of configuring the IP address is to bring the relay IP address onto the same subnet as the RTAC IP address in order to establish communication.

e. Set the NETPORT Primary Net Port setting to A. The SEL-351S used in this example has two Ethernet ports: Port 5A and Port 5B.

f. Send the settings to the relay by clicking File > Send.

Figure 1 Connection Diagram

Managed Ethernet Switch

SEL-2730M

SEL-351S

Protection SystemIP Address: 10.37.17.59

SEL-3555

Real-Time AutomationController (RTAC)IP Address: 10.37.17.63

Laptop IP Address: 10.37.17.105

3


Step 2. Configure the RTAC Ethernet port IP address.

a. Connect Ethernet Port 1 of the RTAC to the laptop.

b. If Eth_1 on the RTAC is configured with a default IP address, set the IP address of the laptop to 192.168.1.5. This ensures the laptop is on the same subnet as the RTAC default IP on Eth_1, which is 192.168.1.2.

c. If the RTAC has been in service and the IP address is different from the default, put the laptop on the same subnet as the RTAC IP address. The IP address of the laptop can be set using the network settings. Open the web browser and type https://192.168.1.2 and access the RTAC web interface. If this is the first time connecting to the RTAC, configure the username and password.

d. Once logged into the web interface, under Network, click Interface and set the IP address on Eth_2 to 10.37.17.63, which is on the same subnet as the relay.

e. Ensure you plug the RTAC Eth_2 port into the SEL-2730M.

Figure 2 SEL-351S Ethernet Port Settings

4


Step 3. Plug the laptop into the switch and change the IP address of the laptop to 10.37.17.105, which is on the same subnet as the relay and the RTAC.

PART 1: USING BREAKER BITS TO IMPLEMENT CONTROLS Section 1: Configuring Relay Settings

QuickSet is used to configure the relay settings. In most SEL relays, the OPEN command (OC) and CLOSE command (CC) are used as breaker bits. The OC breaker bit asserts when the OPEN command is issued to the breaker, and the CC breaker bit asserts when the CLOSE command is issued. When the OC bit asserts, it causes the TRIP logic in the relay to be satisfied when the OC bit is programmed in TRIP logic. This TRIP logic can be tied to an output contact that will trip the breaker. When the CC bit asserts, it causes the CLOSE logic in the relay to be satisfied when the CC bit is programmed in CLOSE logic. This CLOSE logic can be tied to an output contact that will close the breaker.

The SEL-351S Instruction Manual [1] provides details on DNP3 binary control settings for the SEL-351S. In the binary controls section of the manual where DNP3 is used, there are two important settings: BOOPTCC and BOOPPUL. BOOPTCC controls how binary outputs respond to CLOSE and TRIP operations. BOOPPUL controls how binary outputs respond to PULSE operation. For instance, if BOOPTCC and BOOPPUL were set to PULSE, Table 1 shows how the remote bits and breaker bits would respond to the control command being sent. For this application guide, the OC and CC bits will be pulsed, which would cause the TRIP and CLOSE operation.

Figure 3 Setting the RTAC IP Address

5


If BOOPTCC were set to SET and BOOPPUL were set to PULSE, using a PULSE command to control the OC bit to trip the breaker would do nothing (see Table 2).

Step 1. In QuickSet, under Global, click the DNP Settings list item. Set BOOPTCC and BOOPPUL to PULSE, as shown in Figure 4.

Table 1 BOOPTCC = PULSE, BOOPPUL = PULSE

Label Close (0x4X) Trip (0x8X) Latch On (3) Latch Off (4) Pulse On (1) Pulse Off (2)

RBx Pulse Pulse Set Clear Pulse Clear

OC and CC Pulse Pulse Pulse Do nothing Pulse Do nothing

Resetsa

a DRST_DEM, DRST_ENE, DRST_BK, DRST_MML, DRST_HIS, DRST_PDM, DRST_TAR, DRST_HAL, and DRSTDNPE.

Pulse Pulse Pulse Do nothing Pulse Do nothing

NXTEVE Read oldest Read oldest Read oldest Read newest Read oldest Read newest

SINGEVE Pulse Pulse Pulse Do nothing Pulse Do nothing

RBx:RBy Pulse RBy Pulse RBx Pulse RBy Pulse RBx Pulse RBy Pulse RBx

OC:CC Pulse CC Pulse OC Pulse CC Pulse OC Pulse CC Pulse OC

Table 2 BOOPTCC = SET, BOOPPUL = PULSE

Label Close (0x4X) Trip (0x8X) Latch On (3) Latch Off (4) Pulse On (1) Pulse Off (2)

RBx Set Clear Set Clear Pulse Clear

OC and CC Pulse Do nothing Pulse Do nothing Pulse Do nothing

Resetsa

a DRST_DEM, DRST_ENE, DRST_BK, DRST_MML, DRST_HIS, DRST_PDM, DRST_TAR, DRST_HAL, and DRSTDNPE.

Pulse Do nothing Pulse Do nothing Pulse Do nothing

NXTEVE Read oldest Read newest Read oldest Read newest Read oldest Read newest

SINGEVE Pulse Do nothing Pulse Do nothing Pulse Do nothing

RBx:RBy Pulse RBy Pulse RBx Pulse RBy Pulse RBx Pulse RBy Pulse RBx

OC:CC Pulse CC Pulse OC Pulse CC Pulse OC Pulse CC Pulse OC

Figure 4 Setting BOOPTCC and BOOPPUL

6


Step 2. Ensure that the TRIP and CLOSE logic for the relay has the OC and CC bits, respectively, as one of the trip and close conditions, which when asserted will cause the breaker to trip or open, as shown in Figure 5 and Figure 6.

Step 3. Map the status of breaker (52A) to the latch bit (LT8), as shown in Figure 7 and Figure 8, which will set or reset with the breaker bits status. This will reflect the actual status of the breaker. The set and reset bits are the inputs to the latch bit. The latch bit logic is shown in Part 2: Using Remote Bits to Implement Controls on page 22. This setting is not required for a DNP3 client to control the breaker or monitor the breaker status 52A. It is used here to latch the status of the breaker until the next control command is sent so that it is easy to monitor the change.

Figure 5 Trip Conditions

Figure 6 Close Conditions

7


Step 4. Because we are using DNP3 communication over Ethernet, we must enable the Ethernet DNP settings in the relay, as shown in Figure 9.

a. Set Enable DNP Session in the relay to 1.

b. Set TCP port to 20000, which is the default DNP port.

c. Set DNPADR to 1, which is the SEL-351S server DNP address.

Figure 7 Breaker Status

Figure 8 Latch Bits Status

Figure 9 Ethernet DNP Settings

8


Step 5. Configure the DNP Master 1 setting by clicking the Ethernet DNP Master 1 list item in the relay.

a. Set the DNPIP1 IP Address of the client (i.e., the RTAC). We use 10.37.17.63 in this example.

b. Set the DNPTR1 Transport Protocol setting to TCP.

c. Set the REPADR1 DNP Address to Report to setting to 1024, which is for the client DNP address. In this application, the RTAC is used as a DNP3 client that receives data from the relay, and the relay is configured as a DNP3 server that sends data to the client (i.e., the RTAC).

Step 6. The DNP binary output map in the relay has to be set to include the OC and CC bits.

a. Click the Binary Output Map list item and include the CC and OC bits, as shown in Figure 11. Note the binary output index number for the CC and OC bits.

b. On the Binary Input Map, set the breaker status to the binary input point, as shown in Figure 12.

Figure 10 Ethernet DNP Master 1 Settings

Figure 11 Binary Output Map Settings

9


Step 7. This completes the relay settings. Send the relay settings to the relay by clicking File > Send, as shown in Figure 13.

Section 2: Using ACSELERATOR RTAC to Configure the RTAC

We use ACSELERATOR RTAC to configure the SEL-351S client in the RTAC; the RTAC will send control commands to the client.

Step 1. Create a new project.

a. Launch ACSELERATOR RTAC and log in using the default username and password only if the default username and password were not changed.

b. Create a new SEL RTAC project by clicking the New SEL RTAC Project tab.

c. Select the appropriate RTAC Type (i.e., SEL-3555/3560 in this example, as shown in Figure 14).

d. Select the RTAC Firmware Version. You can find the RTAC firmware version on the web interface Dashboard under Firmware Version. See Figure 15.

e. Type a Project Name as appropriate, as shown in Figure 14.

f. Click Create.

Figure 12 Binary Input Map Settings

Figure 13 Send the Relay Settings

10


Figure 14 Create a New Project

Figure 15 RTAC Web Interface Firmware Version

11


Step 2. Launch the project and add an SEL device by right clicking the device folder and navigating to Add SEL Device > 300 Series > 351S > DNP Protocol, as shown in Figure 16. This creates an SEL-351S DNP3 client device with respect to the RTAC.

Step 3. In the Connection Type drop-down menu, select Client - Ethernet, as shown in Figure 17.

Figure 16 Adding the SEL-351S

Figure 17 SEL-351S Connection Type

12


Step 4. Set the SEL-351S settings by clicking the Settings tab. See Figure 18.

a. Set the Client IP Port setting to 20000.

b. Set the Server IP Address to the IP address of the SEL-351S.

c. Set the Client DNP Address to 1024, which is the same as the REPADR1 setting configured in Step 5 on page 8.

d. Set the Server DNP Address to 1, which is the same as the DNPADR setting configured in Step 4 on page 7.

Step 5. Click the Binary Outputs tab, and add three binary output points where BO_00000 has breaker open and BO_00001 has breaker close controls corresponding to the DNP map in the relay configured in Step 6 on page 8 for OC and CC bits. BO_00002 will be used in a later section to map to a remote bit.

Step 6. Click the Binary Inputs tab, as shown in Figure 20, and add two binary inputs where BI_00000 corresponds to the binary input DNP map in the relay configured in Step 6 on page 8 for 52A status. BI_00001 will be used in a later section.

Figure 18 SEL-351S Settings

Figure 19 Adding Binary Outputs

13


Step 7. Save all the settings by typing <Ctrl+S> and click Go Online.

Step 8. When the project is online, click the Controller tab. Verify that the Offline status is FALSE and that the Message_Sent_Count and Message_Received_Count are incrementing, as shown in Figure 22. This indicates successful communication between the RTAC and the relay.

NOTE: When going online, the RTAC may need additional time to go through the autoconfiguration process with the connected IEDs, and the Offline status may not instantly change from TRUE to FALSE.

Figure 20 Adding Binary Inputs

Figure 21 Going Online

Figure 22 Verifying Communication Between the SEL-351S and the RTAC

14


Section 3: Using ACSELERATOR Diagram Builder to Configure the RTAC HMI

You can use Diagram Builder to create HMIs and load HMI diagrams into the RTAC. You can use this to monitor analog and digital values or to send controls.

Step 1. Launch Diagram Builder. Create a new project by clicking File > New > Project and name the project.

Step 2. Import the tags from the RTAC by clicking File > Import Tags.

Figure 23 Creating a New Project

Figure 24 Importing Tags From the RTAC

15


Step 3. Enter the IP Address, User Name, and Password for the RTAC, and click Load Tags, as shown in Figure 25.

NOTE: The IP address, username, and password are the same as configured in Step 2 on page 3 in Configuration.

Step 4. Click the Controls tab and add a breaker, as shown in Figure 26.

Figure 25 Loading Tags

Figure 26 Adding a Breaker

16


Step 5. Map the binary input for breaker status to the breaker, as shown under Tag Name in Figure 27, and set the color when the tag value is True or False.

Step 6. Add two DNP Binary Output Control blocks for breaker open and close operation, as shown in Figure 28.

Figure 27 Breaker Settings

Figure 28 Binary Output Control Block

17


Step 7. In the Appearance list, set Text to Breaker Open and Breaker Close, respectively, for the two binary output control blocks, as shown in Figure 29 and Figure 30.

Step 8. Under Authentication, set Always Authenticate to True; under Command, set Command Type to Pulse. Under Source, set the Tag Name that corresponds to the breaker open and close binary output index numbers. See Figure 29 and Figure 30.

Figure 29 Settings for Binary Controls: Breaker Open

Figure 30 Settings for Binary Controls: Breaker Close

18


Step 9. The index numbers were previously configured in the DNP map settings of the relay, as shown in Figure 31. The Always Authenticate setting will prompt you for the credentials of the RTAC with control permissions whenever a control is attempted. When this setting has been enabled, it will display a lock symbol on the HMI controls. This requires users to log in when attempting to operate the breaker.

Step 10. Save the project and click Send Current Project, which loads the project into the RTAC, as shown in Figure 32.

Section 4: Issuing Control Commands Through the RTAC HMI

The BREAKER OPEN and BREAKER CLOSE commands can be issued through the RTAC HMI when the controls have been mapped. Note that only certain authorized users are allowed to issue controls from the RTAC. This is managed by the user account access privileges set on the web interface of the RTAC. Refer to the SEL-5033 Instruction Manual [3] for details on user account access permissions.

Figure 31 Binary Output Index for Breaker Open and Close

Figure 32 Sending the Project to the RTAC

19


Step 1. Log in to the web interface of the RTAC using the RTAC credentials for user name and password, and navigate to the HMI CONTROL section, as shown in Figure 33.

The HMI diagram that was built using Diagram Builder loads into the RTAC HMI webpage, as shown in Figure 34.

Figure 33 RTAC HMI

Figure 34 HMI Diagram

20


Step 2. Issue a control command for BREAKER OPEN and you will be prompted with an Authentication Required dialog box, as shown in Figure 35. This ensures additional security. Enter an appropriate username and password with RTAC control permissions and click Authenticate.

Step 3. When prompted to confirm that you want to send the command, click OK, as shown in Figure 36.

Step 4. When the control command is successfully issued, a success message displays, as shown in Figure 37. Note that the status of the 52A bit changes as it is mapped to the breaker, and the color of the breaker changes according to the setting in Diagram Builder, as shown in Figure 38.

Figure 35 Sending a BREAKER OPEN Command

Figure 36 Command Confirmation Prompt

Figure 37 Control Action Success Message

21


Step 5. When the breaker is open, issue a BREAKER CLOSE command; when prompted, enter the authentication requirements, which are the credentials with RTAC control privileges, as shown in Figure 39.

Step 6. Verify receipt of a success message, as shown in Figure 40, and that the breaker changes color based on its status, as shown in Figure 41.

Figure 38 Breaker Status Change

Figure 39 Issuing a BREAKER CLOSE Command

Figure 40 BREAKER CLOSE Sent Successfully

22


PART 2: USING REMOTE BITS TO IMPLEMENT CONTROLS

In the previous section, we implemented breaker controls through breaker bits (OC and CC). In this section, we implement controls through remote bits. An important consideration about remote bits is that they are not stored in nonvolatile memory, and they are reset to a deasserted state after the relay loses power. We can avoid this by latching the status of the remote bit by using a latch bit. We can write additional logic for this.

Figure 42 provides sample logic in which the Ground Enabled LED on the SEL-351S can be controlled using remote bits. Note that this example shows control of a single LED; other controls such as Reclose Enabled and Remote Enabled can also be programmed in a similar way. The Ground Enabled LED is used to enable/disable time-delayed ground-overcurrent element tripping.

Section 1: Configuring Relay Settings

QuickSet is used to configure the relay settings. This section describes the logic we use.

The status of the Ground Enabled LED is held by the latch bit LT1. The latch bit can be set or reset by using the SET and RESET equations in the relay. In the logic example shown in Figure 42, as an initial condition, the status of LT1 is 0 because the Ground Enabled LED is not set. When we pulse RB1 and it asserts to 1, the SET equation equals logical 1 because it is a function of logical AND of rising edge of RB1 and NOT of LT1. When SET1 is TRUE, the status of LT1 is set to 1 from its previous value of 0. LT1 is programmed in LED1, which is for the Ground Enabled condition on the SEL-351S. The Ground Enabled LED should illuminate on the SEL-351S, which can be verified on the HMI or relay front panel. To disable the Ground Enabled condition, we must pulse RB1 again. When we pulse RB1 this time, the RST equation is TRUE because it is a function of logical AND of rising edge of RB1 and LT1. Because LT1 was asserted from the previous condition, the LT1 bit is 1, which results in the RST condition being TRUE and the SET condition being FALSE. This results in LT1 resetting to zero, and it eventually results in disabling the Ground Enabled condition.

Figure 41 Breaker Status Change

23


Logic for the Ground Enabled LED

SET1 = /RB1*!LT1

RST1 = /RB1*LT1

LED1 = LT1

Logic for Latch Bit LT1

Every latch bit has two inputs: SET and RESET. The 16 latch control switches in the SEL-351S provide latching relay type functions. Figure 42 shows typical latch bit logic.

Logic in Action

Step 1. After creating logic for remote bits, program the logic in the relay by using QuickSet. Navigate to Group 1 > Logic 1 and click Latch Bits Set/Reset and set the logic as shown in Figure 43.

Figure 42 Latch Bit Logic in the SEL-351S

LT1SET1

RST1(Set)

(Reset)

RelayWordBits

SELOGICSetting

LED1a

a Initial.

RB1 SET RST LT1 LED1b

b After command.

Initial Condition (Ground Enabled LED Not Lit) 0 0 0 1 0

Pulse RB1 (Ground Enabled LED Illuminates) 0 1 1 0 1 1

Pulse RB1 (Ground Enabled LED Extinguishes) 1 1 0 1 0 0

Figure 43 Latch Bits Set/Reset Equations

24


Step 2. Click Target and Operator Control LEDs and set the LED1 (Ground Enabled) equation, which is for the Ground Enabled condition, to LT1, as shown in Figure 44.

Step 3. Navigate to DNP Map 1 > Binary Output Map and map the Remote Bit RB1 in the DNP binary output map of the SEL-351S, as shown in Figure 45.

Step 4. Navigate to DNP Map 1 > Binary Input Map and map the status of Operator Control 1 - LED state on one of the binary input tags, as shown in Figure 46.

Figure 44 Target and Operator Control LEDs

Figure 45 SEL-351S Binary Output Map

Figure 46 SEL-351S Binary Input Map

25


Step 5. Save and send the settings to the relay, as shown in Figure 47.

Section 2: Configuring RTAC Settings

The RTAC settings are the same as in Section 2: Using ACSELERATOR RTAC to Configure the RTAC on page 9. Follow Step 1 through Step 8.

Section 3: Using Diagram Builder Templates to Configure the RTAC HMIStep 1. For the HMI, we use the existing SEL-351S template, which is available on the SEL

website (selinc.com/products/5035), as shown in Figure 48. You can download this with an SEL account.

NOTE: This is just a sample template; the following example illustrates programming of a single control and status indication. Additional programming will be required on the RTAC and Diagram Builder for other controls and indications.

Figure 47 Sending the Relay Settings

Figure 48 HMI Template

https://selinc.com/products/5035/

26


Step 2. When you have downloaded the SEL-351S template, open Diagram Builder, click File > New > Project, and name the project (see Figure 49).

Step 3. Click File > Open > Diagram and select the downloaded template (see Figure 50).

Step 4. After launching the template, click File > Import Tags. For the Connection Type, select Direct To RTAC, as shown in Figure 51. Enter the fields for IP Address, User Name, and Password for the RTAC and click Load Tags. See Figure 51.

Step 5. Click the Ground Enabled LED. Set the following in Properties (see Figure 52):

a. Under Authentication, set Always Authenticate to True if you want the RTAC to authenticate before issuing a control.

b. Under Command, set Command Type to Pulse.

c. Under Source, set Tag Name to be a binary output SEL_351S_1_DNP.BO_00002.

Figure 49 Creating a New Project

Figure 50 Opening the SEL-351S Template

Figure 51 Loading Tags

27


Step 6. After issuing a GROUND ENABLE command to reset the ground LED status, we must map the binary input that contains the LED status. This is mapped to BI_001 in the Binary Inputs map of the SEL-351S. See Figure 53.

Step 7. Enter the LED tag assignment and alarm setting. See Figure 54.

a. Assign the tag SEL_351S_1_DNP.BI_00001 to Input LED.

b. Set the Alarm Severity to Informational.

c. Set the Alarm Value to True.

d. Set Flash On to Alarm.

e. Set Visible On to Alarm and Normal.

f. Additionally, you can set the color of the alarm states in the Alarm Colors tab, as shown in Figure 55.

Figure 52 Settings for the GROUND ENABLE Command

Figure 53 Binary Input Map for Ground Enabled LED Status

28


Step 8. Save and send the new HMI diagram to the RTAC, as shown in Figure 56.

Figure 54 Entering the LED Tag Assignment and Alarm Setting

Figure 55 Setting Alarm Colors

Figure 56 Sending the New HMI Diagram to the RTAC

29


Section 4: Issuing a Control Command Through the RTAC HMI

The GROUND ENABLE and GROUND DISABLE commands can be issued through the RTAC HMI after the controls have been mapped.

Step 1. Log in to the web interface of the RTAC using the RTAC credentials for username and password, and navigate to the HMI Dashboard, as shown in Figure 57.

Figure 57 RTAC HMI

30


Step 2. Verify that the RTAC HMI has the diagram that Diagram Builder sent, as shown in Figure 58.

Figure 58 HMI Diagram on RTAC Web Interface

31


Step 3. Check the initial status of LT1 using the terminal program in QuickSet by giving the TAR LT1 command. The TAR command is used to check the status of Relay Word bits. Verify that LT1 is initially 0, which indicates that the Ground Enabled LED is not active, as shown in Figure 59.

Step 4. Issue a GROUND ENABLE command through the HMI by clicking the Ground Enabled box, which pulses the Remote Bit RB1. Enter the credentials for the RTAC, as shown in Figure 60.

Figure 59 Initial Status of LT1

Figure 60 Issuing a Control Command From the HMI

32


5. Verify that the control command is sent successfully, as shown in Figure 61.

Step 6. Verify that the Ground Enabled LED is flashing on the HMI, as shown in Figure 62.

Figure 61 Control Action Success Message

Figure 62 Ground Enabled Activated

33


7. Issue a TAR LT1 command on the relay terminal and verify that the status of LT1 is 1, as shown in Figure 63.

Figure 63 Status of LT1 After Control Command

34


Step 8. Pulse the Remote Bit RB1 again by clicking the Ground Enabled box on the HMI. Verify that the status of the LED has returned to a normal state, as shown in Figure 64.

Figure 64 Ground Enabled Inactivated

35


Step 9. Issue a TAR LT1 command and verify that the status of LT1 is now 0, which means that the Ground Enabled condition is no longer active and the LED has extinguished, as shown in Figure 65.

Note that you can check the actual status of the LEDs from the relay front panel after you issue control commands, but if the relay is in a remote location, the HMI simulates the actual front-panel status of the LEDs. You can map other controls in the same way and check their status.

CONCLUSION

This application guide illustrates two methods of issuing controls: breaker controls can be issued through breaker bits and other controls can be issued through remote bits. In this application guide, we use the built-in HMI of the SEL-3555, but this application can be extended to any third-party HMI software. This is a useful application for SCADA operators to control and monitor breakers and other conditions in a system.

REFERENCES

[1] SEL-351S Instruction Manual. Available at selinc.com/products/351S/.

[2] SEL-3555 Instruction Manual. Available at selinc.com/products/3555/.

[3] SEL-5033 Instruction Manual. Available at selinc.com/products/5033/.

Figure 65 Status of LT1 After the Control Command

https://selinc.com/products/351S/



36


© 2018 by Schweitzer Engineering Laboratories, Inc. All rights reserved.

All brand or product names appearing in this document are the trademark or registeredtrademark of their respective holders. No SEL trademarks may be used without writtenpermission.

SEL products appearing in this document may be covered by U.S. and Foreign patents.

2350 NE Hopkins Court • Pullman, WA 99163-5603 U.S.A.Tel: +1.509.332.1890 • Fax: +1.509.332.7990selinc.com • [email protected]

TECHNICAL SUPPORT

We appreciate your interest in SEL products and services. If you have questions or comments, please contact us at:

Schweitzer Engineering Laboratories, Inc.2350 NE Hopkins CourtPullman, WA 99163-5603 U.S.A.Tel: +1.509.338.3838Fax: +1.509.332.7990Internet: selinc.com/supportEmail: [email protected]

mailto:[email protected]

https://selinc.com/support

using breaker and remote bits to implement controls

Documents