英文资料(VB编程实现与OPC的通信连接以实现水泵的远程监测与控制).

1、山东科技大学毕业设计（论文）附录5：英文资料英文1What is OPC?OPC is open connectivity via open standards. They fill a need in automation like printer drivers did for Windows. See the summary of current and emerging OPC Specifications and OPC Certification. OPC is open connectivity in industrial automation and the enterpris

2、e systems that support industry. Interoperability is assured through the creation and maintenance of open standards specifications. There are currently seven standards specifications completed or in development. Based on fundamental standards and technology of the general computing market, the OPC F

3、oundation adapts and creates specifications that fill industry-specific needs. OPC will continue to create new standards as needs arise and to adapt existing standards to utilize new technology. OPC is a series of standards specifications. The first standard (originally called simply the OPC Specifi

4、cation and now called the Data Access Specification) resulted from the collaboration of a number of leading worldwide automation suppliers working in cooperation with Microsoft. Originally based on Microsoft's OLE COM (component object model) and DCOM (distributed component object model) technol

5、ogies, the specification defined a standard set of objects, interfaces and methods for use in process control and manufacturing automation applications to facilitate interoperability. The COM/DCOM technologies provided the framework for software products to be developed. There are now hundreds of OP

6、C Data Access servers and clients Everyone's favourite analogy for needing the original Data Access Specification is printer drivers in DOS and then in Windows. Under DOS the developer of each application had to also write a printer driver for every printer. So AutoCAD wrote the AutoCAD applicat

7、ion and the printer drivers. And WordPerfect wrote the WordPerfect application and the printer drivers. They had to write a separate printer driver for every printer they wanted to support: one for an Epson FX-80 and one for the H-P LaserJet, and on and on. In the industrial automation world, Intell

8、ution wrote their Human Machine Interface (HMI) software and a proprietary driver to each industrial device (including every PLC brand). Rockwell wrote their HMI and a proprietary driver to each industrial device (including every PLC brand, not just their own). Windows solved the printer driver prob

9、lem by incorporating printer support into the operating system. Now one printer driver served all the applications! And these were printer drivers that the printer manufacturer wrote (not the application developer). Windows provided the infrastructure to allow the industrial device driver's solu

10、tion as well. Adding the OPC specification to Microsoft's OLE technology in Windows allowed standardization. Now the industrial devices' manufacturers could write the OPC DA Servers and the software (like HMIs) could become OPC Clients. The resulting selfish benefit to the software suppliers

11、 was the ability to reduce their expenditures for connectivity and focus them on the core features of the software. For the users, the benefit was flexibility. They could now choose software suppliers based on features instead of "Do they have the driver to my unique device?" They don'

12、t have to create a custom interface that they must bear the full cost of creating and upgrading through operating system or device vendor changes. Users were also assured of better quality connectivity as the OPC DA Specification codified the connection mechanism and compliance testing. OPC interfac

13、e products are built once and reused many times; hence, they undergo continuous quality control and improvement. The user's project cycle is shorter using standardized software components. And their cost is lower. These benefits are real and tangible. Because the OPC standards are based in turn

14、upon computer industry standards, technical reliability is assured. The original specification standardized the acquisition of process data. It was quickly realized that communicating other types of data could benefit from standardization. Standards for Alarms & Events, Historical Data, and Batc

15、h data were launched. Current and emerging OPC Specifications include: OPC Data AccessThe originals! Used to move real-time data from PLCs, DCSs, and other control devices to HMIs and other display clients. The Data Access 3 specification is now a Release Candidate. It leverages earlier versions whi

16、le improving the browsing capabilities and incorporating XML-DA Schema. OPC Alarms & EventsProvides alarm and event notifications on demand (in contrast to the continuous data flow of Data Access). These include process alarms, operator actions, informational messages, and tracking/auditing mess

17、ages. OPC Batch This spec carries the OPC philosophy to the specialized needs of batch processes. It provides interfaces for the exchange of equipment capabilities (corresponding to the S88.01 Physical Model) and current operating conditions. OPC Data Exchange This specification takes us from client

18、/server to server-to-server with communication across Ethernet fieldbus networks. This provides multi-vendor interoperability! And, oh by the way, adds remote configuration, diagnostic and monitoring/management services. OPC Historical Data Access Where OPC Data Access provides access to real-time,

19、continually changing data, OPC Historical Data Access provides access to data already stored. From a simple serial data logging system to a complex SCADA system, historical archives can be retrieved in a uniform manner. OPC Security All the OPC servers provide information that is valuable to the ent

20、erprise and if improperly updated, could have significant consequences to plant processes. OPC Security specifies how to control client access to these servers in order to protect this sensitive information and to guard against unauthorized modification of process parameters. OPC XML-DA Provides fle

21、xible, consistent rules and formats for exposing plant floor data using XML, leveraging the work done by Microsoft and others on SOAP and Web Services. OPC Complex Data A companion specification to Data Access and XML-DA that allows servers to expose and describe more complicated data types such as

22、binary structures and XML documents. OPC CommandsA Working Group has been formed to develop a new set of interfaces that allow OPC clients and servers to identify, send and monitor control commands which execute on a device. OPC ComplianceThe vision of interoperability in multi vendor systems has be

23、come a reality, via the OPC standards. Certification is the process of ensuring that applications meet the standards. Certification can be accomplished in multiple manners, but most require extensive human intervention. The OPC foundation has produced automated tools to simplify this task, these too

24、ls are collectively known as the OPC Compliance tests. OPC Interoperability WorkshopsThe OPC Foundation arranges workshops hosted by member companies, where participants can test their latest OPC devices. Successfully tested client/server pairs are published on the OPC Foundations website.英文2OPC Aut

25、omation Interface The OPC Data Access Automation Interface defines a standard by which automation applications can access process data. This interface provides the same functionality as the custom interface, but in an "automation friendly" manner. The RSLinx OPC Automation Interface provid

26、es a simplified version of the OPC Data Access Automation Interface. This interface facilitates automation client applications communicating to numerous data sources, either devices on a plant floor or a database in a control room, by allowing a Visual Basic client to write the minimum amount of cod

27、e to read, write, or subscribe to data changes. The interface allows VB applications to exchange data with OPC Server applications. You can use the OPC Automation Interface to perform tasks such as:1：Getting data into applications such as Excel2：Building a graphic display to get data from a plant fl

28、oor3：Building a web page and get data to display on the pageOPCServerOPCGroupsOPCGroupOPCItemsOPCItemOPCBrowser The following illustrates the OPC Automation Interface object model. Click an object or collection to display the properties, methods, and events for that component.OPCServer object The OP

29、CServer object is an instance of an OPC Server. You must create an OPCServer object before you can get references to other objects. It contains the OPCGroups collection and creates OPCBrowser object. The following properties and methods are included in the OPCServer object:Properties：ServerName , OP

30、CGroups ,VendorInfo , ServerNodeMethods：Connect , Disconnect , GetErrorString , GetOPCServers , CreateBrowser OPCGroups collection The OPCGroups collection is an automation collection containing all of the OPCGroup objects this client has created within the scope of the OPCServer that the Automation

31、 Application has connected to via the OPCServer.Connect(). The following properties and methods are included in the OPCGroups collection:Properties: Count , DefaultGroupIsActive , DefaultGroupUpdateRateMethods：Item , Add , Remove , RemoveAllOPCGroup object The OPCGroup object maintains state informa

32、tion and provides the mechanism to give data acquisition services for the OPCItems collection that the OPCGroup object references. The following properties, methods, and events are included in the OPCGroup object:Properties：Name , IsActive , IsSubscribed , ClientHandle , ServerHandle , UpdateRate ,

33、OPCItemsMethods： SyncRead , SyncWrite , AsyncRead , AsyncWrite , AsyncRefreshEvents： DataChange , AsyncReadComplete , AsyncWriteCompleteOPCItems collection The OPCItems collection is an automation collection that contains all of the OPCItem objects this client has created within the scope of the OPC

34、Server, and corresponding OPCGroup object that the Automation Application has created. The following properties and methods are included in the OPCItems collection:Properties: DefaultRequestedDataType , DefaultAccessPath , CountMethods: Item , AddItems , RemoveOPCItem object The OPCItem object is an

35、 automation object that maintains the item's definition, current value, status information, and last update time. Note that the Custom Interface does not provide a separate Item Object. The following properties and methods are included in the OPCItem object:Properties：Value , Quality , ClientHan

36、dle , ServerHandle , AccessPath , ItemIDIsActive , RequestedDataType, TimeStampMethods： Read , WriteOPCBrowser object The OPCBrowser object browses item names in the server's configuration. There exists only one instance of an OPCBrowser object per instance of an OPC Server object. The following

37、 properties and methods are included in the OPCBrowser object:Properties：Organization , Filter , DataType , CurrentPosition , Count , AccessRightsMethods： Item , ShowBranches , ShowLeafs , MoveToRoot , MoveUp , MoveDown , GetItemID , GetAccessPaths英文3What is RSLinx ?Important user informationThis Ro

38、ckwell Software product is warranted in accord with the product license. System configuration, the performing application, operator control, and other related factors affect the product's performance.The product's implementation may vary among users.Rockwell Software reserves the right to ch

39、ange any information contained in this help file or the software at anytime without prior notice.The instructions in this help file do not claim to cover all the details or variations in the equipment, procedure, or process described, nor to provide directions for meeting every possible contingency

40、during installation, operation, or maintenance.Overview of RSLinxRSLinx is a complete 32-bit product family that provides communications to a wide range of applications. RSLinx supports Rockwell Software and Allen-Bradley programming, MMI, and component software products. It serves shop floor data t

41、o commercially available Dynamic Data Exchange (DDE) client applications, such as Microsoft Excel and Access. This allows real-time data from the plant floor to be brought into applications for display, logging, or trending. With RSLinx, you can set individual parameters or download recipes to suppo

42、rted devices from a supervisory computer. RSLinx also supports many popular industrial applications developed by OEMs, VARs, and independent software vendors using the INTERCHANGE Compatible RSLinx C API.RSLinx is available in five versions to meet the cost and functionality requirements of many dif

43、ferent applications. Depending on the version you are running, some functionality may not be operational. Refer to Key Features Supported section of each RSLinx type for specific version functionality. The RSLinx version you are running appears in the title bar at the top of the main window. The fol

44、lowing sections describe the main differences between the available versions of RSLinx.RSLinx LiteRSLinx OEMRSLinx ProfessionalRSLinx GatewayRSLinx SDKRSLinx Lite overviewRSLinx Lite provides the minimum functionality required to support selected software from Rockwell Software and Allen-Bradley. Th

45、is version is not commercially available, but is bundled with products that require only direct access to the RSLinx network drivers. This version does not support Dynamic Data Exchange (DDE) or the published RSLinx C Application Programming Interface (API). It does support communications for many p

46、rogrammable controller programming products from Rockwell Software and selected automation products from Allen-Bradley.If RSLinx Professional or RSLinx OEM is installed without the proper activation files, your installation reverts to RSLinx Lite. If you purchased RSLinx Professional or RSLinx OEM a

47、nd your installation appears as RSLinx Lite, ensure you have properly installed the included activation file.Features and BenefitsThe following features and benefits are available with RSLinx Lite:Ease of upgrade to new processors and networks because all of our 32-bit Allen-Bradley drivers are incl

48、uded in one package.Compatibility of products from Rockwell Software and Allen-Bradley .Concurrent operation of multiple communication devices .Connectivity to legacy networks supported by remote routing through six different bridge devices .Intuitive system investigation supported by graphical RSWh

49、o tree control function and comprehensive diagnostics .Intuitive user interface tested in the Rockwell Software Usability Lab.RSLinx OEM overviewRSLinx OEM includes the required functionality to supply communications services for all Rockwell Software programmable controller logic and MMI products.

50、It includes all the functionality in RSLinx Lite, plus AdvanceDDE limited to Rockwell Software products. It also supports applications developed for the RSLinx C Application Programming Interface (API). This product supports applications from many vendors that develop their software with the RSLinx

51、SDK (Software Development Kit).Features and BenefitsIn addition to the features and benefits included with RSLinx Lite, the following are also available with RSLinx OEM:Compatibility of products from third-party products or custom solutions using RSLinx's open C API or AdvanceDDE .Synchronous an

52、d asynchronous read and write access to processor data in PLC-2, PLC-3, PLC-5, PLC-5/250, SLC 500, MicroLogix 1000, AdvanceDDE, and ControlLogix 5550 processors via C API.Superior speed and reduced network load with block reads and writesEfficient use of system resources and minimal network traffic

53、via optimized DDE reads.Copy/paste hot link establishment to Rockwell Software DDE clients .OPC connectivity for local clients .Run-time support for applications developed for the RSLinx C API.AdvanceDDE to Rockwell Software products (DDE is not supported for DDE clients other than those from Rockwe

54、ll Software) .RSLinx Professional overviewRSLinx Professional for Rockwell Automation Networks and Devices is the full-featured product. RSLinx Professional includes all the features of RSLinx Lite and RSLinx OEM, plus Dynamic Data Exchange (DDE) to any DDE client, including Microsoft Excel and Acce

55、ss, as well as Rockwell Software's AdvanceDDE to any AdvanceDDE-aware client.RSLinx Professional communication capabilities also support OPC connectivity. OPC is based on Microsoft's OLE technology and provides an industry standard mechanism to communicate and exchange data between clients a

56、nd servers.Key Features SupportedIn addition to the features and benefits included with RSLinx Lite and RSLinx OEM, the following are also available with the full-featured version of RSLinx Professional:Ability to upgrade seamlessly from RSLinx Lite and/or RSLinx OEM to RSLinx Professional .Synchron

57、ous read and write access to processor data in PLC-2, PLC-3, PLC-5, PLC-5/250, MicroLogix 1000, and SLC 500 processors via DDE interface.Standard CF_Text based DDE to standard DDE clients, such as Visual Basic and Lotus 1-2-3.Standard Microsoft XL_Table based DDE to Microsoft Office DDE clients, suc

58、h as Microsoft Excel and Access.RSLinx Gateway overviewRSLinx Gateway for Rockwell Automation Networks and Devices extends RSLinx-based communications throughout the enterprise. RSLinx and WINtelligent LINX clients are able to connect over TCP/IP networks directly to RSLinx Gateway drivers. This all

59、ows them to seamlessly go online with Allen-Bradley PLC, SLC, and MicroLogix processors that are connected to networks accessible to RSLinx Gateway stations. This allows dynamic data from the plant floor into applications for display, logging or trending. It also allows setting individual parameters or downloading recipes to supported devices from a supervisory computer.Key Features Sup