Pow-R-Command 1000 OPC Server

Transcription

1 Pow-R-Command 1000 OPC Server Technical Data TD E Effective October 2007 New Information Contents General Pow-R-Command 1000 System Applications for PRC1000 Systems Network Philosophy Connectivity at the Device Level Connectivity at the System Level Introduction of Object Linking and Embedding (OLE) Overview OLE for Process Control (OPC) What OPC Does How Data Exchange Works OPC and Data Exchange Benefits of OPC OPC and PRC1000 Systems Specifications for OPC Server in a Pow-R-Command 1000 System Capabilities of the OPC Server in a Pow-R-Command 1000 System OPC and Pow-R-Command 1000 Software Metering Through OPC Pow-R-Command 1000 Start-Up and OPC Server Start-Up & Support of an OPC Server Pow-R-Command Technical Resource Library

2 General Pow-R-Command 1000 System The Pow-R-Command 1000 (PRC1000) system is a complete network of devices that allows a facility s electrical use to be efficiently managed. With the Pow-R-Command 1000, individual loads can be switched through a network of individual panels which are influenced by building automation systems, wall switches, time schedules, software, or through telephone commands, etc. See Technical Document TD E for more information on the Pow-R-Command 1000 system. Applications for PRC1000 Systems The Pow-R-Command 1000 system is primarily designed for larger facilities where multiple nodes are networked together to allow control through software. However, the Pow-R-Command 1000 can be scaled down to meet the needs of some smaller facilities while offering the same functions as a large networked system. The Pow-R-Command system efficiently controls electrical loads yet maintains a compact design. It may also be integrated seamlessly into building automation systems, security systems, and fire/emergency systems. Network Philosophy The Pow-R-Command 1000 system is designed to interface with a number of devices. In most circumstances, the Pow-R-Command 1000 system uses an RS-485 protocol and communication standard to send and receive commands between control devices (see Figure 1). This RS-485 network is accessed through either RS-232 or Ethernet. For more information on RS-485 to RS-232 and Ethernet, please see Technical Document TD E. Beyond these capabilities, the Pow-R-Command 1000 system is capable of communication using: BACnet OPC SOAP/XML HVAC System Fire/Emergency System Security/Access Control System Other Mechanical Control System Building Automation System Lighting Control System Workstation with BAS, Lighting Control System and Integration Software Installed Networked Lighting Panelboards FIGURE 1. CONNECTION OF BAS AND LIGHTING CONTROL SYSTEM AT SYSTEM LEVEL 2 EATON CORPORATION Cutler-Hammer Pow-R-Command 1000 Technical Data TD E Effective: October 2007

3 Connectivity at the Device Level In many facilities there are a number of systems controlling separate functions of the building. Such systems may include the lighting control system, mechanical (HVAC) system and security/entry access system. To connect these systems, the devices must either use the same communication protocol or a translation bridge from the system to the devices to establish communication. The PRC1000 system supports both methods. Currently, the Pow-R-Command 1000 system is capable of integration with BACnet, Modbus, and LonWorks systems as well as systems using Johnson Controls Inc. N2 protocol. In the case of Modbus and N2 based systems, a native Pow-R-Command 1000 controller can be used to integrate at the device level. In the case of BACnet and LonWorks, a translation bridge, or gateway, must be used. For more information on integrating BACnet, Modbus and Lon- Works systems, please see Technical Document TD E. When devices are connected at the device level, each controller acts as part of one large system instead of multiple systems communicating at one point. Connectivity at the System Level In some circumstances, it is not possible for all devices to communicate using the same protocol and transmission standards. In such instances, the alternative is to communicate at the system level. This means that each system will still function independently, but there is a software bridge between each system to act as a translator. This method is similar to use of a gateway device; however, gateway devices may limit the amount of communication between systems. Introduction of Object Linking and Embedding (OLE) Overview Because of past problems with system integration, standards have been set. These standards are built upon a rule-based system that is created and governed by a body of members of industry. Among the first of such standards is Object Linking and Embedding (OLE) which was created by Microsoft. In basic terms, OLE created a set of rules for transferring and requesting data between programs. For example, when a spreadsheet from Microsoft Excel is transferred to Microsoft Word. The columns and rows transferred represent the object being transferred and embedded into Word. The data in the embedded table is dynamically linked to the source data in Excel. Each time Word needs data to update its file, it sends a request to the Excel file. The Excel file returns the requested data. To this extent, Microsoft created a standard for its programs to speak to each other. In addition, Microsoft has released this ability to other software developers so that they can create programs embedded in their software that can ask, give and receive data to/from other Microsoft products. The end result is a set of standards that can be integrated into any manufacturer s software. This allows each platform to pass data to all other platforms created to be compliant with Microsoft s OLE standard. Because OLE is based on standards, past problems with standardization have been reduced if not eliminated. Now any other software developers can build their applications to the OLE standard. This ensures user connectivity to all other programs using the same standard. Linked Data Screen Shot of Microsoft Word FIGURE 2. EXAMPLE OF EMBEDDING AND LINKING DATA BETWEEN PROGRAMS OLE for Process Control (OPC) A minor limitation of Microsoft s OLE standard is that it is not intended to pass the massive amount of data that is passed between control systems in a facility. To overcome this, a separate standard was created. This standard is known as OLE for Process Control or OPC. Like OLE, OPC is a standard method for requesting and communicating data. However, unlike OLE, OPC is meant to communicate data from devices such as Programmable Logic Controllers, energy management equipment and lighting control equipment. The OPC standard was created and is directed by a body that represents members of the manufacturing and control industry. What OPC Does In basic terms, OPC sets a standard of communication between systems that could not normally speak to each other. This standard applies to how data is requested, and given. By creating this standard, the necessity for a programmer to create a new integration program can be eliminated. Also, the problems associated with adding systems or expanding an existing system are greatly reduced. How Data Exchange Works Screen Shot of Microsoft Excel Embedded Object In general terms, there are three parts involved in the communication of data between a device and the application that needs the data, or between a controller and a device. These parts are described as follows: Client: A client is a machine or application that asks for data and at times will send data. When the client needs data, or even has another need such as communication of a command, it sends a request to a server. Server: A server is commonly a central point to which all clients send their requests. When a client calls on a server, the server then draws the necessary data from its sources, or in this case through control devices. When this occurs, the server goes through a driver. Incidentally, there are some circumstances where clients act like servers and vice versa. Driver: A driver is the bottom level of software that allows the server to communicate with the physical devices themselves. When a device is created to communicate through software, a driver is also created. All software that has this driver, and knows how to use it, can communicate with the device associated with the driver. EATON CORPORATION Cutler-Hammer Pow-R-Command 1000 Technical Data TD E Copyright

4 An example of this can be seen in a computer with a printer attached to it. When a document is ready to print, the application software in use acts as a client and sends a print command to a server. In this case, the server is a piece of software, most likely on the same machine. The server then takes the command and pulls up the proper driver for the printer. This driver in turn tells the server how to format and send the document, and passes the information to the device. From the data received through the driver the printer then prints the document. OPC and Data Exchange When using OPC, the data exchange is similar to the example of printing a document. However, in this case, there are hundreds of printers, hundreds of clients, dozens of drivers, and one or more servers. Because of the number of elements involved, there must be an underlying coordination of data presentation and transfer. It is here that the power of the OPC standard is realized. All aspects of data exchange including the client, server and driver have some element that meets the OPC specifications making the data flow smoothly and simply. Additionally, because each element meets the OPC standard, any other devices that meet the same standard can be added to the stream of data with little or no programming. Benefits of OPC The primary benefit of using OPC is an assurance that all devices that meet the OPC standards can communicate with each other. Additional devices that meet the OPC standard can be added with little difficulty or cost. As OPC is a standard based on expertise and influence from the industry, it continues to evolve based on the industry s needs. Because of the benefits of OPC there are a large number of tools, technical resources and experts in the field to support the use and implementation of OPC. Desktop Workstation Client Requesting Data Server Processing Client s Request and Returning Requested Data Driver Translating Server s Request to Device and Device s Answer to Server OPC and PRC1000 Systems When a Pow-R-Command 1000 system is installed in a facility, all the controllers, communication nodes, and software are designed to communicate with each other. When the necessity arises to integrate a PRC1000 system and an additional system, there are two options: Communication at the device level, which cannot be done in all circumstances. System level communication. This is the point where OPC is used. Eaton has developed the ability to connect the PRC1000 system, through PRC1000 software, to an OPC compliant server. When this is done, all native PRC1000 control and network access function as normal. In addition, all PRC1000 network access devices and software are used. Figure 4 illustrates the transfer of data. This path is as follows: Each PRC1000 controller is located on an RS-485 network and only knows how to speak to other PRC1000 devices. At the head of the network is a PRC1000 Network Access Device. Among other things, this device allows a user to access controllers through software. Connected to the PRC1000 Network Access Device is a workstation that is equipped with basic PRC1000 software, and is used to program the functions of controllers. The basic level of PRC1000 software is known as Lighting Optimization Software and is covered in Technical Document TD E. Included in this software is a communication device known as a Dynamic Data Exchange server. The Dynamic Data Exchange server is used like many other servers in that clients call on it for data or with commands and it passes them on to the devices. In the PRC1000 system, the DDE server has a number of functions including: Passing data to and from other applications such as Microsoft Excel Passing data to other Pow-R-Command 1000 software including the PRC1000 Custom Graphic Screens and Data Logging Software (see Technical Document TD E) Passing data to a third-party software that acts as a OPC server for OPC clients From the third-party OPC server, client applications that are written to the OPC standard can call upon it to send commands and retrieve data from the PRC1000 system. Specifications for OPC Server in a Pow-R-Command 1000 System As noted, a third-party software must be used to make the Pow-R- Command 1000 system available to clients based on OPC standards. This software must: Be developed to comply with the OPC standard based on DCOM or COM. Communicate through Pow-R-Command 1000 DDE Server. Support installation on Microsoft Windows 98, 2000, and XP. Driver Passing Request to Device and Returning Answer FIGURE 3. DATA EXCHANGE PROCESS 4 EATON CORPORATION Cutler-Hammer Pow-R-Command 1000 Technical Data TD E Effective: October 2007

5 Capabilities of the OPC Server in a Pow-R-Command 1000 System The OPC server, regardless of the manufacturer, has three functions it can perform when communicating in a Pow-R-Command 1000 system. Read Status: This includes the status of switching devices such as remotely operated circuit breaker and relays. Additionally, status of alarms, variables and errors can be read. Command On: OPC Clients can command individual switching devices, as well as groups of switching devices, on. Command Off: OPC clients can command individual switching devices as well as groups of switching devices off. Outside these functions, all programming (e.g., setting time schedules, holidays, using inputs/outputs, creating groups, etc.) to the PRC1000 system must be done through the Pow-R-Command 1000 Lighting Optimization Software. OPC and Pow-R-Command 1000 Software As noted, there are limits to accessing a PRC1000 system through an OPC client. Because of this, Pow-R-Command 1000 software is still required. Currently, the PRC1000 system has three levels of software that can be used with the OPC server. These levels are the Lighting Optimization software (see Technical Document TD E), Custom Graphics Screens and Data Logging (see Technical Document TD E), and Web Server Software (see Technical Document TD E). Each of these levels can be used for control of the Pow-R-Command 1000 system, and each will work when an OPC server is used. Figure 5 illustrates how the PRC1000 software and OPC server interact and draw data from the hardware. Metering Through OPC Eaton is a global leader in the manufacturing of industrial goods. Along with lighting control, Eaton offers a complete metering package. Through OPC servers, a PRC1000 system and an Eaton s Cutler-Hammer metering system can be efficiently integrated. Each system operates independently, but a common ground for communication is created through software. Like the PRC1000 system, Eaton s Cutler-Hammer metering supports the use of ICONICS software. For more information on metering equipment, please call In addition, information for Cutler-Hammer metering products, including connectivity, can be found in Installation Document IL Pow-R-Command 1000 Start-Up and OPC Server Even when using an OPC server with a PRC1000 system, full PRC1000 start-up is required. Although commands can be sent to the PRC1000 system through an OPC server, all other functions such as time schedules, groups, holiday schedules, and use of switch inputs must be set up and changed in PRC1000 Lighting Optimization Software. When a factory authorized PRC1000 technician starts up a system with an OPC server, they will do three things: Create all necessary schedules and controls to operate the PRC1000 system. This is done through PRC1000 software. Create a points list for use in the OPC server package. This points list will allow the system integrator to match the points to devices controlled from the OPC server side. Provide the integrator with a set of examples of how to match up the points on the Pow-R-Command 1000 side of the OPC server with the points on the OPC side of the OPC server. Figure 6 gives an example of this points table. Figure 6 is for illustration purposes only. Pow-R-Command 1000 Network Access Device (Ethernet Server Shown in Figure) Pow-R-Command 1000 RS-485 Network on Twisted Shielded Network Cable Software Sends Programming Instruction and Receives Status Ethernet OPC Client OPC Client Requesting Data/Sending Command To OPC Server, and OPC Server Answering Pow-R-Command 1000 Lighting DDE Server Sends Request to Devices Through Network Access OPC Server OPC Server Requesting Data From PRC1000 DDE Server and PRC1000 DDE Server Answering Pow-R-Command 1000 DDE Server Pow-R-Command 1000 Workstation with Pow-R-Command FIGURE 4. USING OPC CLIENT AND SERVER WITH A POW-R-COMMAND 1000 SYSTEM EATON CORPORATION Cutler-Hammer Pow-R-Command 1000 Technical Data TD E Copyright

6 Start-Up and Support of an OPC Server In most cases, it is the responsibility of the facility s integrator to establish and start up any OPC-based communication. When the PRC1000 system is brought on line, the start-up engineer will only establish the points on the PRC1000 system side of the OPC server. Eaton does not support or warranty the use of third-party OPC server packages. Only products manufactured by Eaton are supported. If Eaton is requested to purchase and develop the OPC server software, additional charges will be added to the cost of the job based on complexity. When a start-up is required for integration of Eaton PRC1000 and metering systems through an OPC server package, there are two options. The first option is to have an experienced integrator develop the interface. The second option is to use Eaton Electrical Services & Systems (EESS). EESS can provide field engineering and support for PRC1000 products, metering devices and OPC servers. To contact EESS representatives in your area, please call Pow-R-Command 1000 Network Access Device (Ethernet Server Shown in Figure) Pow-R-Command 1000 RS-485 Network on Twisted Shielded Network Cable Software Sends Programming Instruction and Receives Status Through Network Access Device Ethernet OPC Client OPC Client Requesting Data/Sending Command to OPC Server, and OPC Server Answering OPC Server Requesting Data From PRC1000 DDE Server and PRC1000 DDE Server Answering Pow-R-Command 1000 Lighting Optimization Software DDE Server Sends Request to Devices Through Network Access Devices and Receives Answer Third-Party OPC Server Pow-R-Command 1000 DDE Server Pow-R-Command 1000 Workstation with Pow-R-Command 1000 Software, Metering Software, and OPC Server Software Third-Party OPC Server Requesting Data From Metering OPC Server and Metering OPC Server Answering Metering OPC Server Sends Request to Metering Devices and Receives Status Metering System Metering Software with Built-in OPC Server FIGURE 5. USING OPC CLIENT AND SERVER WITH A POW-R-COMMAND 1000 SYSTEM AND CUTLER-HAMMER METERING SYSTEM 6 EATON CORPORATION Cutler-Hammer Pow-R-Command 1000 Technical Data TD E Effective: October 2007

7 Pow-R-Command Technical Resource Library For additional information on Pow-R-Command Networks and components, please refer to the appropriate Technical Document. As of the date of this document, Technical Documents for the Pow-R-Command 1000 system are as follows: FIGURE 6. EXAMPLE OF POINTS TABLE TAKEN FROM DDE FILE LOADED INTO ICONICS DDEOPC SERVER (FIGURE IS FOR ILLUSTRATION PURPOSES ONLY) Title Publication Number PRC1000 Universal System Controller Product Reference TD E PRC1000 System Overview TD E PRC1000 Telephone Override Controller Product Reference TD E PRC1000 Networking TD E PRC1000 Lighting Optimization Software TD E PRC1000 Human Machine Interfaces TD E PRC1000 Protocol Exchanges TD E PRC Vdc Dimming Electronic Ballasts Control TD E PRC1000 OPC Server TD E PRC1000 SOAP/XML Server TD E PRC1000 Custom Graphics and Data Logging..... TD E PRC1000 Web Server Software TD E PRC1000 Universal I/O Module TD E PRC1000 Network Signal Repeaters TD E For the most current list of documents on the Pow-R-Command 1000 system, and available downloads, please visit BACnet is a registered trademark of American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE). Modbus is a registered trademark of Modicon, a division of Schneider Electric Industries SA. Microsoft, Word, Excel and Windows are registered trademarks of Microsoft Corporation. Pow-R-Command is a trademark of Eaton Corporation. LonWorks is a registered trademark of Echelon Corporation. Cutler-Hammer is a federally registered trademark of Eaton Corporation. EATON CORPORATION Cutler-Hammer Pow-R-Command 1000 Technical Data TD E Copyright

8 Eaton Corporation Electrical Group 1000 Cherrington Parkway Moon Township, PA United States 877-ETN-CARE ( ) Eaton.com 2007 Eaton Corporation All Rights Reserved Printed in USA Publication No. TD E / Z5829 October 2007