RTU 560 with IEC 61850 Vaasa Engineering Oy Joakim Ainasoja Bachelor’s thesis Electrical Engineering Vaasa 2010
BACHELOR’S THESIS Author: Degree programme: Specialization: Supervisor: Joakim Ainasoja Electrical Engineering Power Engineering Erik Englund Title: RTU 560 with IEC 61850 ____________________________________________________________ Date: 1.12.2010 Number of pages: 44 Appendices: 2 ____________________________________________________________ Abstract This thesis work was made in cooperation with Vaasa Engineering Oy.
EXAMENSARBETE Författare: Utbildningsprogram och ort: Inriktningsalternativ/Fördjupning: Handledare: Joakim Ainasoja Elektroteknik Vasa Elkraftsteknik Erik Englund Titel: RTU 560 med IEC 61850 ____________________________________________________________ Datum: 1.12.2010 Sidantal: 44 Bilagor: 2 ____________________________________________________________ Abstrakt Detta examensarbete har gjorts i samarbete med Vaasa Engineering Oy.
OPINNÄYTETYÖ Tekijä: Koulutusohjelma ja paikkakunta: Suuntautumisvaihtoehto/Syventävät opinnot: Ohjaaja: Joakim Ainasoja Sähkötekniikka Vaasa Voimatekniikka Erik Englund Nimike: RTU 560 IEC 61850-protokollalla ____________________________________________________________ Päivämäärä: 1.12.2010 Sivumäärä: 44 Liitteet: 2 ____________________________________________________________ Tiivistelmä Tämä opinnäytetyö tehtiin yhteistyössä Vaasa Engineering Oy:n kanssa.
Table of contents Abstract Abstrakt Tiivistelmä Abbreviations 1 2 3 1.1 1.2 1.3 3.1 3.2 3.3 3.4 Introduction ................................................................................................................................... 1 Background ................................................................................................................................. 2 Goal ..............................................................................................................
5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 6 7 5.11 5.2.1 Problems occurring with CET .................................................................................. 21 Vampset .................................................................................................................................... 22 5.3.1 Problems with VAMP .................................................................................................. 22 RTUtil ............................................................
Abbreviations ASCII BRCB CAP 505 CCT CET DCS DHCP DNP 3.0 EPRI GOOSE GSE GSSE I/O IEC IED IEEE IET ISO ISP L/R LAN MAC address MMS NO/NC OSI PC PCM 600 PLC RCB RTU SCADA SNTP TCP/IP UCA URCB VEO VMD WAN WLAN American Standard Code for Information Interchange Buffered Report Control Block Computer Aided Programming 505 Communication Configuration Tool Communication Engineering Tool Distributed Control System Dynamic Host Configuration Protocol Distributed Network Protocol 3.
1 Introduction 1 What if there were no standards published yet to this day. People would roam around while producing unique ideas which would lead to a very wide array of individual products that could not merge with each other in any way since they are all unique. Imagine owning an elegant phone with a lot of features. Without standards this phone would be rendered useless since no other phone would use the same features.
1.1 Background 2 This thesis work was assigned to me by Vaasa Engineering Oy. My work began in the beginning of February 2010. The popularity of the IEC 61850 protocol is growing in the Finnish electrical substation market but the implementation of the protocol is not yet perfect, meaning that errors and flaws may occur when establishing communication between devices from various vendors. 1.
3 Fuse Transformer Breaker Transmission Breaker Transforme r Breaker Generator 2 The electrical power system and its control G Figure 1. Basic generation and distribution of electricity. Components inside the red rectangle are in need of intelligent protection devices. The basic idea of electrical distribution is to find a power source such as light, wind, water or diesel engines. These powers are then harnessed so that they turn the axle of a generator which in return generates electricity.
4 Before computer aid in process control was developed and affordable, many control rooms consisted of a control table hardwired to all the adjustable devices in the process and a large screen from were alarms and conditions were readable and mostly all different commands had to be sent through its own wire making cabling very expensive. In recent years, process control has taken a big step forward thanks to computer aid.
3 Communication in substation automation 5 3.1 Basics of data communication People have learnt how to regulate voltage quickly and efficiently, which is a crucial knowledge within data communication. George Boole is the person credited for coming up with the idea of having two different states defining yes or no / on or off / TRUE or FALSE (hence the name BOOLEAN value). Later on it was realized that Boole’s idea could be implemented into computer logic.
3.2 LAN and WAN networks 6 LAN networks can be found today at homes, offices, industry etc. A LAN network is built within a small area that does not need an Internet connection for transmitting data between devices that are interconnected. Ethernet cable or wireless (WLAN) connection from the device to the router is needed to create a LAN. WAN is the complementary connection between multiple LANs or other networks, so that information can be obtained between users over longer distances.
7 3.3 The OSI model Many protocols are built upon the seven layer OSI (Open Systems Interconnection) model which is a reference on how to build up the messages to be sent. The model works so that the information/data needed to be sent is first processed through the seven layers before being sent, with each layer adding or modifying the data within the message as for example receiver address or encryption.
8 3.4 Common protocols for data communication Below some of the types of protocols used today are described briefly. All countless protocols available are not mentioned, only the ones that are commonly used and that are not manufacturer-specific. It is also hard to compare the protocols side by side, therefore only some of their individual features are brought up. The information given here is only scratching the surface by brief explanations for these standards.
3.4.2 Modbus 9 Modbus was developed by Modicon ® in 1979 to be used for communications with PLC devices. It is an open protocol which means that developers can design products that make use of the Modbus standard, without limitations. It grew rapidly in popularity and is now one of the most widely used methods for connecting industrial electronic devices. In a standard Modbus system there is one master unit and there may be up to 247 slave units.
3.4.4 SPA-bus 10 The SPA-bus uses an asynchronous serial communications protocol (1 start bit, 7 data bits + even parity, 1 stop bit) with a common data transfer rate of 9600 b/s. Messages on the bus consist of ASCII characters, which are easier for a human to interpret than hex-code which is normally used by many other protocols. The bus can support one master and several slaves. (1) 3.4.
Some of the features included in IEC 61850 are: 11 1. Data Modeling - Primary process objects as well as protection and control functionality in the substation are modeled into different standard logical nodes, which can be grouped under different logical devices. There are logical nodes for data/functions related to the logical device (LLN0) and physical device (LPHD). 2.
12 MMS is an international standard (ISO 9506) dealing with messaging system for transferring real time process data and supervisory control information between networked devices and/or computer applications. MMS defines the following: 1. A set of standard objects that must exist in every device and on which operations like read, write, event signaling etc can be executed. VMD is the main object and all other objects like variables, domains, journals, files etc come under VMD. 2.
4 Hardware 13 4.1 Remote Terminal Units RTU is a physical device designed to send and receive data from the physical protection and control units and then deliver data to a control room computer. An RTU may have I/Os for measuring and sending analogue and digital signals, such as power measurement at 4 20 mA or voltage measurement of 0 - 10 V, which today are common ranges of analogue signals. This analogue data is interpreted and encoded into digital data that is then sent to the monitoring equipment.
14 RTU 560s are often big rack mounted units with many I/O connections depending on their applications. A new smaller unit, the DIN-rail mounted RTU 560G, will be analyzed and tested further on in this thesis. Figure 7. ABB RTU560G remote terminal unit. (2) 4.1.3 Netcon 500 The Netcon 500 has been designed to act as a data concentrator and a protocol converter in station automation systems.
4.1.4 Siemens AK 1703 ACP 15 Siemens AK 1703 ACP from the SICAM products offers automation, telecontrol and communication functions for combined flexibly and in full compliance with IEC 61850. Especially noteworthy is the possibility of offering client and server functionality on only one Ethernet interface.
4.2 Protective relays 16 Not all protective units from all different vendors will be mentioned below, just the ones commonly used by VEO. A protective relay (also in this context referred to as IED) is the unit for supervising electric circuits ranging from low voltage to high voltage installations. Its main objectives are fault detection and reading measurements supplied from connected devices, such as current transformers, voltage transformers, position indicators etc.
17 4.2.4 GE GE (General Electric) Multilin 3 series providing protection, control, monitoring and metering, and both local and remote user interfaces in one assembly. They give various protocol support through front USB, rear serial, Ethernet and fiber ports. 4.3 Control center software 4.3.1 ABB MicroSCADA MicroSCADA is a SCADA system made by ABB for managing and supervising an entire distribution network in utility and industry environments.
5 Configuration process 18 The following configuration steps describe the procedures used when trying to accomplish the goals of this thesis work. The configuration process means going through one software after another in a certain order and will be explained in that same order. As none of the first attempts after a software configuration was instantly successful all these steps had to be figured out one by one. Problems and mistakes first made are explained along with their solutions.
19 Before any work was begun the station topology needed to be defined. This would help in seeing the big picture on how the test station should function and it was also easier to keep track on what solutions are possible and all the needed hardware. The station built is illustrated below in figure 10. Figure 10. Thesis project system overview A so called I/O list was also made which defines which signals to use and their addresses for the IEC 60870-5-101 communication.
5.1 REF 541 and CAP 505 20 The CET tool, which is used to configure the SPA-ZC 400 needed to have the REF 541 configuration file (file format .ar) imported. REF 541 can natively communicate over LON, SPA and DNP 3.0 protocols and since the SPA-ZC 400 module was attached to the REF 541 it was possible to simply set the SPA-ZC 400s IP address and receive the .ar file through Ethernet TCP-IP connection using CAP 505. Figure 11. CAP 505 relay download tool. 5.2 CET and SPA-ZC configuration When the .
5.2.1 Problems occurring with CET 21 The first SPA-ZC unit used had an older firmware than the firmware set in CET, thus the Ethernet address given in CET would not apply to the SPA-ZC unit but instead it would assume the address given as its primary SNTP server, which is the address of the RTU 560. For the communication to work the units could not have the same addresses. This problem was resolved by getting a newer SPA-ZC unit with firmware version 2.
5.3 Vampset 22 The VAMP 257 has native support for IEC 61850 and an Ethernet port on its backside, so no extra equipment was needed to configure the protection and communication settings. Only a few of the protection capabilities were enabled, since most of them function in the same way from a communication viewpoint. VAMP 257 supports the use of three datasets to which the user can address any signal or object he wants.
23 The same problem was encountered with the REF 541 unit and it was resolved in the same manner using the RTU 560 PLC for inverting the local/remote signal state from REF 541. 5.4 RTUtil The RTUtil tool has been developed by ABB specifically for use with the RTU 560 models and it is the main software during the configuration process. In RTUtil there are three main views, Network Tree, Hardware Tree and Signal Tree.
24 At the beginning the hardware and protocols to be used were defined in RTUtil by adding the items to the network tree and the hardware tree. In the network tree, the RTU and all the outgoing lines were defined and also the IEDs connected at the other end of those lines. In the hardware tree the type of RTU was defined and the connected lines were linked. An I/O bus had to be added to the CMU board in the RTU since it is crucial for the internal communication to work.
25 Another problem encountered was that with the RTUtil software installation a template .icd file for the RTU functions came bundled at the installation directory. That file is meant for import into the CCT tool and when doing so a faulty configuration would be generated. Instead it was important to extract a new .iid file and rename it to .icd for the configuration to be successful, i.e. the same procedures as with the CET and Vampset exports. 5.
26 Figure 16. PCM 600 5.6 CCT/IET CCT is a licensed tool created by ABB. It comes bundled with the PCM600 Engineer Pro software package and is meant for handling process objects and report control blocks throughout the station. The version used (CCT 3.2.1) for designing this project was a bit unstable and tended to crash quite often. It also did not show all IEDs on some occasions, which led to a lot of retries. Firstly a new project was created and the previously exported .
27 It was then important to check that all the units had correct IP addresses and that the devices all had the same bus connection selected. Figure 17. Selecting the bus connection for SPA-ZC in CCT. With the same bus connection selected it was necessary to select update IEC 61850 data flow from the tools menu and that will automatically apply the RTU as a client logical node to the report control blocks sent by the relays. Figure 18. RTU 560G seen as a client logical node for the SPA-ZC RCB rcbStatUrg.
5.6.1 Problems with CCT 28 One major problem encountered during the testing stage was that after a new configuration upload to the RTU, the RTU would never get past the boot stage, meaning that it would reboot over and over making it inaccessible for any troubleshooting. The only way to reset the RTU was to pull out the compact flash card and insert it to the PC for file access which enabled me to manually remove the configuration files from the flash card.
29 Figure 19. IEC 61850 object addresses in Microsoft Excel where each row is one object. By cross referencing the objects logical nodes and classes with the ones found in Vampset and CET, their origin and objective could be determined. The unique object identifier may be written in Excel or made later in RTUtil, but since Microsoft Excel has superb copy paste functions it is much faster to write them along with the IEC 60870-5-101 address attributes in Excel. The signal type, SPI, DPI, MFI etc.
5.8 Multiprog WT 30 The RTU 560G has a PROCONOS programmable logic controller and to create programs for it the software MWT is used. From RTUtil it is possible to do an MWT export so that the “foundation” for the PLC program is built automatically. It is also possible to launch the MWT application from RTUtil. Firstly the configuration files built with RTUtil needed to be re-imported to MWT so that variables with their I/O configuration could be accessed and applied to function block I/Os.
31 Figure 21. PLC program for duplicate commands and signal bit states. Apparently the REF 541 relay demanded a signal from PLC objects to be active for at least 100ms, so by creating a 150ms delay from select to execute command the relay functioned as intended. Function blocks DCO_IN_1 and DCO_IN_3 have the same input DCO made under PLC in RTUtil.
32 Figure 22. PLC program section for inverted L/R and RTU time written to variable VAR_TIMESTAMP. When the program had been completed the PLC program files were built. By copying the program file directly to the flash drive using a PC the RTU was able to boot with the PLC program. The file to be copied was found under the PC catalogue address //c//r/plc/bootfile.pro and was copied to /plc.
33 one containing event lists and the two others containing measurement diagrams for the two bays. Buttons for switching between the pages were also created from pictures drawn in Adobe Photoshop, since drawings in jpeg format could be imported and assigned to tasks. See figure 23 for the final HMI view. Figure 23. RTU 560G HMI Custom symbols were made for the indication of breaker position and L/R (local/remote). This was done in the component view editor within HMI Editor. Figure 24.
34 The RTU web interface can be accessed by setting the computer in the same IP range as the RTU, in this case 192.168.0.X where the X can be any number ranging from 5 to 254. IP numbers ending with 1 to 4 are already in use by the station devices. As the RTU got the IP of 192.168.0.2 the web interface could be accessed by typing http://192.168.0.2 in the web browser. Figure 25. Web interface showing the configuration upload view of the RTU 560.
5.10 MicroSCADA 35 Lastly the control station was made in MicroSCADA. The communication from the RTU to MicroSCADA was made by using the IEC 60870-5-101 protocol over a RS 232 interface. For the communication to work a custom cable had to be made. The wire connections can be seen in figure 26. Figure 26.
36 Figure 28. Link properties made in RTUtil. Once the communication was established it was time to add the process objects, which was done by utilizing Install standard functions in Object Navigator. This navigator gives the user the ability to easily add and edit process objects relating to the same station device simultaneously. It will also greatly ease the insertion of process object symbols later in the display builder. Figure 29. Install Standard Function interface.
37 Figure 30. Setting of attributes to the switching object. The VAMP 257 switching command was made without the select before operate function. It was set in the REF 541 since only the REF 541 had been configured to use the function. When the attributes were made the objects could be created and addresses defined. Figure 31. Creation of objects and editing of addresses and basic properties.
38 When the objects had been set the display builder could be launched and the process display was built by the drag-and-drop method from the object browser into the display. Figure 32. Dragging objects into the process display A custom button was made for the PLC multiple open/close command by inserting a “virtual switch” seen in the upper right corner of figure 32.
39 Figure 33. Command procedure for time synchronization. The command procedure then had to be linked to a time channel that would execute the code over and over after a time interval. This time interval needs to be shorter than the timeout setting in RTUtil. Figure 34. Time channel with 5 minute time interval for command execution.
The final station process display is seen below in figure 35. 40 Figure 35. Process display made in MicroSCADA showing na overcurrent trip on bay A2. 5.10.1 Problems with MicroSCADA MicroSCADA won’t allow the user to control the bay if the station or the bay shows local in the process. Due to the lack of external I/O ports on the RTU it was necessary to create a “simulated” L/R setting for the station, and that was done with the RTU PLC by copying the REF 541 relays L/R signal.
5.11 Results 41 The final result was a functioning station with devices made by two vendors in both local and remote control. Even if the remote simulation was done on the same PC as the local control, it was still over a different communication link as if it had been done from a separate distant control station. The PLC program with both breakers opening simultaneously did not function quite as well as initially planned, as it somehow made the VAMP execute two times per command.
6 Discussion and conclusion 42 At first when this thesis work was assigned to me I did not know what to expect or how to start, as most engineering concerning station automation and data communication was new to me. After digging through the Internet and a few books, the functionality required at substations became clearer and after that the smaller details also started to fall into place. After acquiring basic information and procedures for substation engineering the practical work could begin.
43 I have not had the opportunity to read the specific demands of the IEC 61850 standard, but the interoperability can still be improved between products from different vendors by ensuring a better compliance with the IEC 61850 standard. The standard could also be extended to cover all the basic electrical IED functions, so that a third party software manufacturer could compete and concentrate on making the configuration process as easy and reliable as possible.
7 List of sources 44 1. ABB Substation Automation Oy. ABB. [Online] July 31, 2001. [Cited: March 1, 2010.] http://library.abb.com/global/scot/scot229.nsf/veritydisplay/811733b652456305c 2256db40046851e/$File/SPAcommprot_EN_C.pdf. 2. ABB Substation Automation. ABB Substaion Automation. [Online] [Cited: October 9, 2010.] http://www05.abb.com/global/scot/scot258.nsf/veritydisplay/c52cd496dbc40747c 1257705005cd6d8/$File/Xf536DEABB%201596%2010%20en%20RTU560%20for %20DIN%20rail%20Flyer.pdf. 3.
RTU 560 with IEC 61850 configuration guide Guide Revision 1 Made by: Joakim Ainasoja 1.12.
Guide Joakim Ainasoja 1.12.2010 2 (33) Contents RTU 560 with IEC 61850 configuration guide ..................................................................... 2 1 General steps of the RTU 560 configuration for IEC 61850........................................ 3 2 Introduction ................................................................................................................... 4 3 VAMP IEC 61850 settings .................................................................................
3 (33) 1 General steps of the RTU 560 configuration for IEC 61850
4 (33) 2 Introduction This guide has been made in co-development with a thesis project made in 2010 at Vaasa Engineering Oy concerning the RTU 560 as a station RTU and gateway between IEC 61850 and IEC 60870-5-101. It covers all the configuration steps used to complete the thesis.
5 (33) Figure 3. Selecting objects into datasets. Set the dataset(s) to be used into report control block(s) and set the report control block name. The report ID can be left at default as it is unique by default. It is recommended to use the BRCB (Buffered Report Control Block) for communication with RTU stations. Figure 4. Report control block settings. And that concludes the necessary VAMP settings.
6 (33) 4 SPA-ZC 400 IEC 61850 settings As with VAMP it is necessary to set name and IP addresses for the device, as well as set the IP address for the time synchronization server. Figure 5. SPA-ZC name and IP addresses. Make sure that the RCB attributes correspond to the desired functions. Data set should be set to true. Figure 6. RCB attributes in CET tool.
7 (33) Figure 7. Inverted local/remote setting. 5 Software needed for RTU 560 configuration (latest versions preferred): a) RTUtil b) Web browser with Java plugin (e.g. Internet Explorer) c) Multiprog wt (for PLC functions) 1 d) HMI editor (for integrated HMI functions) 5.1 Additional software for IEC 61850 engineering: e) PCM600 with necessary connectivity packages f) 5.2 IET/CCT (comes bundled with PCM600)1 Additional useful software and accessories: g) Windows Notepad (for accessing .ICD and .
8 (33) 6 Configuration of RTU 560 in RTUtil. Firstly it is necessary to build the project environment data. Initialize the signal tree: Set number of levels by giving them names, if three levels are desired, leave level four empty. If the plan is to give level one the name Runsor which is six characters, level two the name 22kV and three AA3 it is then recommended that level one has 7 bytes reserved for characters (name + space), level 2 should have 5 bytes reserved and level 3 should have 4 bytes.
9 (33) Figure 10. Adding items to the network tree. Then the final network tree might look something like figure 11. Figure 11. Network tree Afterwards the Station RTU and IEDs need to be linked to the hardware tree. Figure 12. Linking items into the hardware tree.
10 (33) Notice that all items that are linked to another tree get a small red circle at the item icon indicating that it has been linked. This will also happen to the icon in the tree that the item is linked from. Items to be linked between the trees are signal objects, IEDs, Hardware objects and communication lines. Build up the hardware tree by selecting items that are meant to be used in the station like type of RTU, I/O boards, PLC, HMI, archive etc.
11 (33) When all required settings are made it is time to do a consistency check. The consistency check will reveal any direct error or if some items have the same name, address etc. It is recommended to do a consistency check regularly as the project is being built so that mistakes can be detected early. Figure 14. Consistency check menu. If no errors appear it is time to export the Excel pattern files.
12 (33) Then select the exported PD Excel file by browsing it. When the Excel file has been selected it should open in the Excel software (if installed) for the user to view the default names. Then select the correct unique column identifiers for all the process data fields (on line 5 unless the Excel file has been modified). Figure 16. Selecting the Excel file sheets for the corresponding hardware. Figure 17. Excel view of the IEC 61850 address columns with unique column identifier names on row 5.
13 (33) Figure 18. Selection of columns for the corresponding parameters. A secondary faster method of selecting these columns is to use the “set the first __ characters of the default name to: ____” by checking first how many letters are equal in the columns. Then the amount of equal letters is set to the first “box” and then writing the string of letters in the other “box”.
14 (33) Export a .iid file from RTUtil and rename it to .icd. This file is then needed in the CCT tool. At IEC 61850 sub line, IED name and access point name should be set before the .iid export. Figure 20. Example of IED name and access point name for the RTU on a IEC 61850 line.
15 (33) 7 PCM 600 configuration Not many steps are needed with the PCM 600 tool for IEC 61850 engineering with RTU 560. Basically it can be used just for setting up a substation structure with generic IEC 61850 IEDs. One extra IED may be added under a bay to act as the RTU later in CCT. IP addresses may be added and technical keys need to be set for all the IEDs. The technical key of the RTU should be the same as set in RTUtil.
16 (33) 8 CCT configuration Build a new project and import the .scd file generated from PCM 600 so that a substation structure will be built. The IEDs appear empty, therefore the IEDs .icd files should be imported by right-clicking them and selecting import. Figure 22. Menu for importing the .scd file. During the thesis project it was noticed that regularly generated .icd files would not import properly into the used version of CCT. However by generating .
17 (33) When the bus connection has been selected it is important to select Update DataFlow from the Tools menu as illustrated in figure 24. Figure 24. Selecting update dataflow in CCT. Now the RTU should appear as a client to the RCBs from the relays. Figure 25. RTU 560 as client to a VAMP RCB.
18 (33) Figure 26. Removal of unnecessary RCBs in CCT. Now when the settings are made a new .scd file should be exported. 9 Importing IEC 61850 process objects into RTUtil The new .scd file from CCT should then be synchronized with the previously exported Excel file. Make sure that a backup copy has been made of the Excel file (in case any changes need to be made or errors occur) as the Excel file will be overwritten containing new data. The synchronization is done by selecting SCD import in RTUtil.
19 (33) Select the .scd file fol import and then select the Excel file containing the process data (usually named ExcelExportPD_.xls ) Figure 28. Step 3 of SCD import in RTUtil. When the import is done the IEC 61850 process object appear in the Excel file as one signal per row. Figure 29. Example of imported process objects in an Excel file.
20 (33) Excel has great functions for sorting data and that can be used to sort the process objects and make them easier to find within the Excel file. To do so simply select all the rows containing IEC 61850 objects and select Sort..from the Data menu. Figure 30. Sorting of rows by columns in Excel. The object unique identifiers can then be written into Excel as the objects can be identified by cross referencing them with the objects in the relay configuration tool.
21 (33) Then the Excel file should be imported to RTUtil (note that a new RTUtil project will be made and get the same name as the Excel file once the import is done). Note that the third column (RTUtil560 import) in Excel must be set to Y (=yes) for all the objects to be imported. An error that occurred in the thesis project was when the access point name were different in RTUtil compared to the name inside the .scd file.
22 (33) When the Excel file has been imported the process objects should appear in the signal tree and if the IEDs have already been defined they should automatically be linked. Otherwise they should be linked manually to the corresponding IED. Figure 36. Process objects in RTUtil. Now objects meant to be used in the PLC function can be assigned to the desired PLC task. See figure 38 for an example. Archive function can be set for all objects to show up in the RTU event list, both in Web interface and HMI.
23 (33) Figure 37. Selected data points for PLC task Q0x2. Now that all objects are inserted and the attributes are set, the RTU configuration files can be built. Four files will be built (.iod, .gcd, .ptx and .oad file formats) and all these files can later be uploaded to the RTU. A Multiprog WT export should be made so that the PLC program can be made with MWT (Multiprog WT).
24 (33) 10 Multiprog WT configuration for PLC functions Multiprog WT can be launched from RTUtil along with an exported RTU560 template project. Firstly it is important to do an import of process data addresses, see figure 38. Figure 38. Import of RTU objects in MWT. Figure 39. Select RTUtil NT Import.
25 (33) Then build the POU by right clicking the folder named Logical POUs and the Insert. A new window will appear where you can select the program name etc., see figure 40 for an example of a new program. Figure 40. Example of a new program in MWT. When the worksheets for the program appear, simply right-click the worksheet with a “function-block-looking” icon and select Open Worksheet. Figure 41. How to open worksheets in MWT.
26 (33) Creation or selection of RTU variables can be done by just right-clicking any input or output on the function blocks and select Variable. Create variable: At Scope, Global should be selected. If Global Variables Worksheets is selected at Global_Variables it is possible to type a name in the variable list -> select Properties -> select variable type and set the initial value for a new static variable. Figure 42. Creation of a new variable.
27 (33) Figure 43. Example program worksheet in MWT. Remember to compile the worksheets and build cross references when you are done. The program should then be assigned to the desired task. Figure 44. Insert program to task.
28 (33) Figure 45. Selection of program to task. Now the PLC program can be built from the Build menu. One way to get the program into the RTU is to manually copy the file into the compact flash card. For the bootfile to be generated during the build process, right-click the PLC:PROCONOS folder and choose settings, then mark the checkbox Generate boot project during compile. Figure 46. Selection for generating a boot file during compile.
29 (33) It is also possible to directly connect with the RTU unit for uploading and debugging of the PLC program in real-time. That was not tested during the thesis project so no stepby-step guide for that method can be given here. At least for a TCP/IP connection a certain .dll file is needed. The connection settings should most likely be made in the PROCONOS settings window shown in figure 46. 11 HMI editor The HMI editor is a Java code based software which is very easy to use.
30 (33) Figure 48. Example on how the breaker position indicator and command are set. If more than the main page is made, remember to make buttons for navigating between the pages. When the process display is made, simply save the project and upload the project file (.jar file format) to the RTU.
31 (33) 12 Web interface and upload of configuration files To connect to the RTU web interface you can simply connect through a web browser such as Internet Explorer or Mozilla Firefox by entering the IP address of the RTU; http://. If the IP is unknown the RTU 560 CMU board has a jumper that can be moved so that it will get the default IP address of 192.168.0.1. Figure 49. RTU 560 web interface welcome screen.
32 (33) Figure 50. Configuration file manager in RTU 560 web interface When logged in as Admin the user has the rights to change passwords and “roles” (user rights) for the other users. The Admin user can also enable the test mode on the RTU web controls. Figure 51.
33 (33) The HMI application can be launched from the web interface, but a quicker method is to right click the HMI launch link, copy the link address and create a shortcut icon on the desktop for easier access to HMI. A problem noticed in the thesis work was that even if the web browser Firefox had Internet access and a connection with the RTU, the HMI application would not launch if Internet Explorer was set to offline mode.
A1 A1 A1 A1 A1 A1 A1 SS1 SS1 SS1 SS1 SS1 SS1 SS1 A1 A1 SS1 SS1 A1 SS1 A1 A1 SS1 SS1 A1 SS1 A1 A1 SS1 SS1 A1 SS1 A1 A1 SS1 SS1 A1 SS1 A1 A1 SS1 A1 A1 SS1 SS1 A1 SS1 SS1 A1 A1 SS1 A1 A1 SS1 SS1 Subnet Station SS1 Subnet Station Bay Object description, max 30 characters Trip Counter Q01A1 Q0 Q01A1 Q0 Q01A1 Q0 Q01A1 Q0 Q01A1 Q0 Wear Fault Wear Breaker Location Status Station Local/Remote Q01A1 A01 Q01A1 Q0 U> trip U> alarm U> directio
A2 A2 A2 A2 A2 A2 A2 A2 A2 A2 SS1 SS1 SS1 SS1 SS1 SS1 SS1 SS1 SS1 SS1 A1 A2 SS1 SS1 A2 SS1 A1 A2 SS1 SS1 A2 SS1 A2 A2 SS1 SS1 A2 SS1 A2 A2 SS1 SS1 A2 SS1 A2 A2 SS1 A2 A2 SS1 SS1 A2 SS1 SS1 Voltage A2 Station Station Voltage SS1 Bay Bay Object description, max 30 characters Q01A1 Q0 Q01A1 Q0 Q02A1 Q0 Q02A1 Q0 Q02A1 Q0 Q02A1 Q0 Q02A1 A01 Q02A1 A01 Q02A1 A01 Q02A1 A01 Q02A1 A01 Q02A1 A01 Q02A1 A01 Q02A1 A01 Q02A1 A01 Q02A1 A01 Q02A1
