DNP3 Server and Introduction to the Tag Processor Exercise

Transcription

1 Hands-On RTAC Session DNP3 Server and Introduction to the Tag Processor Exercise Figure 1 Connection Diagram DNP3 Servers on the RTAC The SEL-3530 Real-Time Automation Controller (RTAC) can support 32 DNP3 server sessions simultaneously. In this exercise, you will configure a DNP3 Ethernet server connection on the RTAC. This DNP3 server connection will simulate mapping all the substation data to a remote supervisory control and data acquisition (SCADA) client over a network. Exercise Step 1. Insert a new Other DNP Ethernet Server Device in your project. Name the device Control_Center. Figure 2 Insert DNP3 Ethernet Server DNP3 Server and Introduction to the Tag Processor Exercise Page 1 of

2 Step 2. Under the Settings tab, adjust the Server DNP Address and Client DNP Address, as shown in Figure 3. When the Allow Anonymous DNP IP Clients setting is True, it will allow any Internet Protocol (IP) address to connect. When it is set to False, you must enter the IP address, or up to ten IP addresses, of the DNP3 clients that will be allowed to connect. Only one connection is supported on the server at a time. Note that there are no tabs for tags for a DNP3 server connection. Instead, there is a place to declare a map, as indicated in Figure 3. Leave this set to None until you create the DNP3 map. Step 3. Figure 3 DNP3 Client Settings Under Tag Lists, insert a new DNP3 Shared Server Map called Control_Center. Figure 4 DNP Server Shared Map DNP3 Server and Introduction to the Tag Processor Exercise Page 2 of

3 Step 4. In the Control_Center_DNP map, under the Binary Inputs tab, click on the + icon and add 100 binary inputs, starting at 0. By default, Event Class for binary inputs should be 1. Step 5. Figure 5 Add Binary Inputs Add 50 analog inputs to the DNP3 server starting at 0, as shown in Figure 6. By default, the Event Class should be set to 2 for analog inputs. Assign the Deadband to 1 for each point. Figure 6 DNP3 Server Analog Inputs Step 6. Add 10 binary outputs to the DNP3 server, as shown in Figure 7. Figure 7 Add Binary Outputs DNP3 Server and Introduction to the Tag Processor Exercise Page 3 of

4 Step 7. Now that the DNP3 server shared map has been configured, you can assign the map to the Control_Center_DNP server device under its Settings tab, as shown in Figure 8. Figure 8 Assign Shared Map to Server DNP3 Server and Introduction to the Tag Processor Exercise Page 4 of

5 Step 8. Once the DNP3 server is configured and points are assigned, you can use the Tag Processor to move the information from the client connections into the server tags. In the Tag Processor, simply enter the Control Center tags in the Destination Tag Name column and the desired source tags in the Source Expression column. Type some tags in by hand to learn the automatic completion functions, and enter others by pressing <Ctrl+C> to copy and <Ctrl+V> to paste into the Tag Processor. Figure 9 Tag Processor DNP3 Server and Introduction to the Tag Processor Exercise Page 5 of

6 Step 9. Analog inputs are mapped using the same procedure. Step 10. Figure 10 Analogs in Tag Processor Binary outputs or controls are mapped in the reverse direction as compared with the inputs. Logically, the control signal is coming from a remote DNP3 client device into the DNP3 server in the RTAC. This requires the Control_Center_DNP server tags be placed in the Source Expression side of the Tag Processor. There are many attributes of Control tags, and each can be mapped independently to accomplish any task required. Map the controls shown in Figure 11 into your Tag Processor as an example. Step 11. Figure 11 Controls in the Tag Processor The Tag Processor can be built completely outside of the programming software and pasted in after completion. A spreadsheet with a sample Tag Processor that can be pasted into your project to demonstrate this is available. DNP3 Server and Introduction to the Tag Processor Exercise Page 6 of

7 Step 12. Save and send your project to the RTAC. Then go online, and view the Control_Center_DNP tags. Ensure they have good quality and are the same magnitude as the source data from the Feeder_1_SEL and Main_BKR_DNP client connections. Step 13. Figure 12 Online Control Center View Confirm that the controls sent from the Control_Center_DNP connection are processed through the Tag Processor and are executed at the relay. Figure 13 Force Controls From the Control Center DNP3 Server and Introduction to the Tag Processor Exercise Page 7 of