DOCSLIB.ORG

A Technical Overview of the OPC Dataaccess Interfaces

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Technical Overview of the OPC Dataaccess Interfaces A Technical Overview of the OPC DataAccess Interfaces Al Chisholm Chief Technical Officer Intellution Inc 1 Edgewater Drive Norwood, MA 02062 781 769 8878 KEY WORDS OPC, COM, DCOM, Windows, NT, I/O, Standards, Data, Realtime ABSTRACT This paper presents a fairly detailed technical overview of the Data Access interfaces. It begins by describing the problem these interfaces are designed to solve, the functionality they provide and the object model they employ. Following this is a review of the specific interfaces provided, including a brief discussion of the specific methods exposed by those interfaces. A REVIEW OF THE PROBLEM This paper contains a fairly detailed technical overview of the OPC (OLE for Process Control) Data Access Interface. It assumes that the reader has some technical background in COM (Component Object Model) and object oriented programming. This paper will also talk about where OPC Data Access fits in the architecture of a control system and about the objects and methods that the OPC Interface presents to the programmer. In addition to talking about WHAT the objects look like, this paper will also talk a bit about WHY they look the way they do. Which is to say it will try to answer the question, “What were those guys thinking when they designed this stuff…”. This paper talks primarily about the Custom (C++) interface as that is what server vendors and most serious client vendors need to understand and implement. Display Trend Report Display Trend Report Application Application Application Application Application Application Software Software Software Software Software Software Software Software Driver Driver Driver Driver Driver Driver Driver Driver The left figure above illustrates ‘The I/O Driver Problem’. Clearly each software driver for a new device requires a unique, device-specific chunk of code to talk to the device or network. The need for this device specific code is not a problem OPC is trying to address. Rather, this is something Fieldbus is trying to address, and Devicenet, and Profibus, and Lonworks, and a host of others. The problem that OPC deals with is that each of these software drivers also presents a different software interface to the calling application. As a result, each application also requires a unique chunk of code for each driver, device or network it wants to connect to. This obviously makes it difficult to reuse applications with different sets of process interface equipment. OPC Solves this problem be creating a ‘software bus’ as shown in the right hand figure. Applications only need to know how to get data from OPC data sources. As a result, they are simpler, smaller and easier to use. Device Drivers (servers) only need to know how to provide data in a single format (OPC Server). As a result they are easier to write (and there is more of a market for such servers). Client Applications OPC OPC DCS System SCADA System OPC OPC OPC Software Driver Although the MAIN problem OPC solves is the ‘I/O Driver’, you can see in the figure above that OPC is flexible enough to be used not only between Devices and SCADA, SoftPLC or DCS systems, but also between the SCADA SoftPLC or DCS engines and the high level applications such as HMI, Trends, Reports, etc. which use their data. In this architecture, the SCADA system, the DCS system or the SOFTLOGIC system really just represents a ‘smarter’ device. THE TECHNOLOGY Now for some technology basics… Why, for example, does OPC use COM? COM is Microsoft's Component Object Model which is the ‘90’s’ way to do APIs (subroutines). In addition to being widely used, another advantage of COM is that Microsoft provides a lot of the useful common ‘plumbing’ required to connect the clients and servers. This includes DCOM (Distributed COM) which allows creation of network-based applications with a minimum of development effort. As noted earlier OPC is flexible enough to be used at different layers within the system architecture and is specifically designed to work well over a network. Efficiency is insured by the fact that (a) OPC can be exception based and (b) unlike DDE, OPC can pack 100s or 1000s of data items into each transaction. Performance is also guaranteed both by the support for multiple data items per transaction and by the fact that COM and thus OPC servers can be created in several models; inprocess, local and remote. For the highest possible performance, Inprocess servers incur 0 overhead. Millions of transactions per second are possible using this approach. Local servers allow 1000s of transactions per second. Even remote servers can manage 100s of transactions per second. And again, unlike DDE, each transaction can include many data items. THE LOGICAL OBJECT MODEL The OPC interfaces look the way they do largely because of the assumptions the OPC working group made about the applications. The main assumptions are listed below. • Apps are interested in a subset of the Tags available within the underlying Control system. • Apps are interested in many different subsets of Tags at different times and at different resolutions. • Apps want to be independent of the process objects It is important to stress that first point. A fundamental assumption is that there is some sort of control or monitoring engine running independently of anything OPC is doing and that OPC is just a window into this engine’s data. That last assumption is the only controversial one. This issue will be discussed again below. In any case, these assumptions lead logically to the model in the following figure. The Logical Object Model Custom and Automation OPCServer Interfaces OPCGroup(s) OPCGroup(s)OPCGroup(s) OPCItem(s) OPCItem(s) OPCItem(s) OPCItem(s)OPCItem(s) OPCItem(s) OPCItem(s) OPCItem(s) OPCItem(s) At the top of this figure is an OPC Server object . This is the COM object to which the application first connects. Below this is a collection of OPC Group Objects. These are created dynamically by the applications to hold lists of Tags and attributes (which OPC refers to as Items). An HMI might create a Group for each open picture. A report package might create a group to access data for each report. The contents of the Group and item collections may vary over time based on the needs of the applications. (Again this has no effect on the underlying control system). This is actually somewhat analogous to RowSets as used on OLEDB. There is a lot of data in the database, you want to look at a subset of it in your application., and that subset may vary based on your needs at the time. Which brings us back to the assumption about process object independence. There were two fundamental approaches which could have been taken to this; the first is the ‘rowset’ approach seen here. The second is a more purely object oriented approach in which the server would ‘proxy’ the process objects and expose their properties and methods to the applications. The OPC working group felt the pure object approach was basically much to complex. Two issues in particular were those of efficiency and getting the vendors to agree on the nature and properties of the specific objects. Do note that the OPC approach does allow a vendor to expose data from an OODB through a very flexible names space. TYPICAL SERVER DESIGN Typical Server Design OPC/COM Interfaces OPC Group & Item Management Item Data Optimization and Monitoring Device Specific Protocol Logic Hardware Connection Management The figure above shows a typical server design. The SERVER provides management of the OPC Groups and also controls, mediates and optimizes access to the physical devices by multiple clients. The Server is essentially an I/O Driver which ‘understands’ how to talk to some vendor specific data provider (hardware or software) and which Exposes the data from this data provider via the standard OPC Interfaces. The OPC sample server available at the OPC web site provides a very good implementation of the upper two layers of the diagram. Various commercial toolkits provide frameworks or implementations of one or more additional layers. THE GROUP AND THE ITEM The Logical Object Model The Item OPC Server The ‘Real’ SCADA or DCS System OPC Groups... OPC Item FIC101 TIC101 OPC Item OPC Item FIC102 TIC102 OPC Item FIC103 TIC103 OPC Item FIC104 FIC105... The GROUP provides a convenient way for an application to organize the data it needs. Different Groups can be used by different parts of the application; can have different refresh rates; can be polled or exception based. Operator Displays, Recipes, Reports might each use one or more groups. The ITEM provides a connection point to a value in the physical device. Typically this is a single variable such as a process value or setpoint. The ITEM provides information to the client; Value, Quality, TimeStamp, and Data Type. As mentioned before, the OPC item is a transient object which exists within the OPC server. It is used to create a connection between the server and the real data. The OPC interfaces always return the process data in a VARIANT. It is assumed that the server has a ‘native’ or ‘prefered’ datatype which is also known as the canonical datatype. OPC allows clients to read this canonical type (e.g. 4 byte float). It also allows them to specify that they want the data returned in some other format (e.g. ASCII). THE SERVER INTERFACES IN DETAIL • IOPCServer • IOPCBrowseServerAddressSpace (optional) We will now review the interfaces on these objects in more detail discussing first what functionality they provide and then listing the methods of each interface to show how that functionality is provided.
Load more

Recommended publications
  • Modbus TCP Master (OPC) User's Manual
    Station Automation COM600 3.4 Modbus TCP Master (OPC) User's Manual 1MRS756445 Station Automation COM600 3.4 Issued: 21.12.2007 Version: D/06.11.2009 Modbus TCP Master (OPC) User's Manual Contents: 1. About this manual .................................................................................. 7 1.1. Copyrights ...................................................................................... 7 1.2. Trademarks .................................................................................... 7 1.3. General .......................................................................................... 7 1.4. Document conventions .................................................................. 8 1.5. Use of symbols .............................................................................. 9 1.6. Terminology .................................................................................... 9 1.7. Abbreviations ............................................................................... 11 1.8. Related documents ...................................................................... 12 1.9. Document revisions ..................................................................... 12 2. Introduction ........................................................................................... 13 2.1. Functional overview ..................................................................... 13 2.2. Modbus OPC Server features ...................................................... 14 3. Configuration .......................................................................................
    [Show full text]
  • OPC DX Link Option for Kepserverex
    OPC DX Link Option for KEPServerEX Overview: OPC technology has been extremely successful at bridging the vertical communication gap between the plant floor and the control room. Using standards such as OPC Data Access (DA), hundreds of software applications have been written to gather data from a wide range of control systems using this simple Client/Server architecture. OPC DA did not, however, address the needs of integration and interoperability directly between devices. Historically there have been a number of high-level and low-level bus protocols, each one written to address the differing needs and uses of the devices they were intended to serve. Protocols such as PROFIBUS, DeviceNet, ControlNet, and many more, have been utilized in the past. Recently there has been a growing movement towards the use of Ethernet as an industrial communication backbone. Initially each of these respective bus specifications was redeveloped for use over Ethernet. The resulting PROFInet, Ethernet/IP, High-Speed Ethernet Fieldbus (HSE), and BACNET/IP provided a means for customers to move smoothly from their proprietary wiring schemes to Ethernet. However it didn't address the key issue of true Device-to-Device interoperability or more importantly Bus-to-Bus interoperability. While these new Ethernet based protocols could coexist on the same wire, there was still no way to get data from a PROFInet device directly into an Ethernet/IP device. Example using DX to route data between OPC Items in KEPServerEX Example of using DX to pull data from an OPC DA server and eXchange data (bi-directional) with an OPC DX server OPC DX: OPC Data Exchange (DX) was designed to address the needs of Device-to-Device and Bus-to-Bus interoperability by applying the same technologies currently used by desktop applications at the device level.
    [Show full text]
  • Investigate M2M-Related Communication Standards That Exist on the Global Market Today
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Agder University Research Archive Investigate M2M-related communication standards that exist on the global market today by Aleksander Albretsen Thesis in partial fulfilment of the degree of Master in Technology in Information and Communication Technology Agder University College Faculty of Engineering and Science Grimstad Norway June 2006 Abstract Most M2M applications use well-known communication technologies to interconnect the devices. Even though they use well-known communication technologies there are no widely used and well-defined M2M standards regarding the data exchange (application layer). This thesis investigates and identifies M2M related communication standards that exist on the global market today, and are applicable for M2M standardisation. This thesis is limited to the following segments within M2M: Security, Automatic Meter Reading (AMR) and Utility Control. Today, and in the future, IP will play an important role within M2M. This thesis is therefore mainly focusing on standards that implement how to transfer the application layer using the IP-stack. M2M is defined in this thesis as an application with a central server communicating with end-devices through a gateway, using remote communication from server to gateway. The following standards are investigated and found applicable in one or more of the selected segments: CIP, MODBUS, LonWorks, KNX, DLMS/COSEM, M-BUS, SIA, M2MXML, OPC and ZigBee. Each of the standards is explained within the thesis. All standards are identified and categorised, and area of applications and proposed solutions are described. This thesis discusses the applicability regarding each segment, multiple services behind one gateway, bandwidth consumption, software update and interconnection of networks.
    [Show full text]
  • Matrikonopc Server for Simulation User Manual.Pdf User’S Manual for This Server
    MatrikonOPC Server for Simulation User's Manual MatrikonOPC Server for Simulation User's Manual This manual is a product of Matrikon Inc. Matrikon Inc. Suite 1800, 10405 Jasper Avenue Edmonton, AB T5J 3N4 Canada Phone: 780.448.1010 Fax: 780.448.9191 www.matrikonopc.com Document Revision History: Document Date Description Author Version 2003-08-19 1.0 Initial document. DENG 2004-04-02 1.1 Added HDA and AE functionality descriptions. IMF 2008-05-14 2.0 Converted to new template. LB Added OPC item descriptions, updated Installed 2008-08-25 2.1 Files, updated Installation and Un-Installation RK, LB sections, updated Troubleshooting section. MatrikonOPC Server Framework v1.11.1.0/1.7.0.0 applied to server. Software version updated to 1.5.0.0. Updated Installation section. Updated Contacting Support section. Alias Configuration section updated to include Calculation scaling and 2009-07-17 3.0 LB Item Browser information. Limitations section updated. Appendix B – Aliases: added Scaling Calculation section, updated CSV File Format and Scaling Algorithms sections. Updated Appendix E – Security. MatrikonOPC Server for Simulation v1.5.0.0 User’s Manual 2 SOFTWARE VERSION Version: 1.5.0.0 DOCUMENT VERSION Version: 3.0 COPYRIGHT INFORMATION © Copyright 1997 - 2009, Matrikon Inc. All rights reserved. No part of this document may be reproduced, stored in a retrieval system, translated, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of Matrikon Inc. CONFIDENTIAL The information contained herein is confidential and proprietary to Matrikon Inc. It may not be disclosed or transferred, directly or indirectly, to any third party without the explicit written permission of Matrikon Inc.
    [Show full text]
  • Applicom® OPC Server Is the Best Choice for Connecting Industrial Devices to Your Favorite Industrial Applications
    Open, Reliable and Efficient, applicom® OPC server is the best choice for connecting industrial devices to your favorite industrial applications. With a collection of 30 major protocols, Woodhead is a key player in OPC technology for automation solutions. ® 07 Jan. 05 applicom OPC Server Multi-protocol OPC server for industrial networking Features • Included free-of-charge in all applicom® packages • Tested and Full compliant with OPC DA specifications v1.0a, 2.05 and 3.0 • Multi-protocol Server: manages simultaneously various protocols through an unique OPC connection • Powerful! Real-time data access with Automatic data exchange optimization • Integrates redundancy features OPC Technology • Smart OPC Item browsing OPC (OLE for Process Control) is the standard communication interface that enables the data • Simultaneous access in COM exchange between client applications (HMI/SCADA, RDBM, control/command) and industrial and DCOM modes devices (PLC, I/O blocks, drives, etc). OPC is built using the Microsoft’s technologies: OLE, COM and DCOM (Distributed COM) that are well-tested and proven foundation. • InProc / OutProc connection OPC specifications are designed by the open foundation – OPC Foundation – to meet the general needs of industry, finding then an issue of specific and proprietary interfaces problem. applicom® OPC Server Supported OS The applicom® OPC Server is an OPC Data Access (DA) compliant server that enables data exchange between OPC clients and a broad range of device manufacturers through networks • Windows 32-bit: XP SP1 / 2003 such as: Ethernet TCP/IP, Profibus, Serial, Modbus Plus, WorldFIP, etc. Server / 2000 SP3 / NT4) applicom® OPC Server supports multi-protocol feature: it can manage up to 30 different protocols simultaneously.
    [Show full text]
  • Knowledge Discovery in the SCADA Databases Used for the Municipal Power Supply System
    Knowledge Discovery in the SCADA Databases Used for the Municipal Power Supply System Valery Kamaev1, Alexey Finogeev2, Anton Finogeev3, Sergey Shevchenko4 1Volgograd State Technical University, Volgograd, Russia, kamaev@cad.vstu.ru, 2Penza State University, Penza, Russia, alexeyfinogeev@gmail.com, fanton3@yandex.ru, 3National Technical University "Kharkiv Polytechnic Institute", Kharkiv, Ukraina, sv_shevchenko@mail.ru Abstract. This scientific paper delves into the problems related to the develop- ment of intellectual data analysis system that could support decision making to manage municipal power supply services. The management problems of mu- nicipal power supply system have been specified taking into consideration modern tendencies shown by new technologies that allow for an increase in the energy efficiency. The analysis findings of the system problems related to the integrated computer-aided control of the power supply for the city have been given. The consideration was given to the hierarchy-level management decom- position model. The objective task targeted at an increase in the energy effi- ciency to minimize expenditures and energy losses during the generation and transportation of energy carriers to the Consumer, the optimization of power consumption at the prescribed level of the reliability of pipelines and networks and the satisfaction of Consumers has been defined. To optimize the support of the decision making a new approach to the monitoring of engineering systems and technological processes related to the energy consumption and transporta- tion using the technologies of geospatial analysis and Knowledge Discovery in databases (KDD) has been proposed. The data acquisition for analytical prob- lems is realized in the wireless heterogeneous medium, which includes soft- touch VPN segments of ZigBee technology realizing the 6LoWPAN standard over the IEEE 802.15.4 standard and also the segments of the networks of cellu- lar communications.
    [Show full text]
  • OPC Fundamentals
    OPC Overview Adam Hill Kepware Technologies/PTC Portland, ME (USA) Agenda • Before OPC • OPC Foundation • OPC Client Communications • OPC Specifications – OPC DA – OPC HDA – OPC AE – OPC UA and Tunneling with OPC UA May 14 – 16, 2019 INTERNATIONAL SCHOOL OF HYDROCARBON MEASUREMENT What You Will Learn 1.What does OPC stand for? 2.What is the purpose of the OPC Foundation? 3.OPC specifies the communication between what and what? May 14 – 16, 2019 INTERNATIONAL SCHOOL OF HYDROCARBON MEASUREMENT Before OPC Before OPC • No standard exists for communication between devices (data sources) and computer interfaces (data gatherers). • Proprietary connections and toolkits are developed by hardware vendors. – This limits users to one type of software and hardware package. • As users want to make more client connections to one device, or add different hardware, the problem gets sticky… May 14 – 16, 2019 INTERNATIONAL SCHOOL OF HYDROCARBON MEASUREMENT Before OPC (cont.) May 14 – 16, 2019 INTERNATIONAL SCHOOL OF HYDROCARBON MEASUREMENT OPC Foundation OPC Foundation • Formed in 1995 by a consortium of 5 companies: – Fisher-Rosemount, Rockwell, Opto 22, Intellution, and Intuitive Technology. • Now there are over 450 corporate members in the Foundation. THE FOUNDATION’S MISSION “The mission of the OPC Foundation is to manage a global organization in which users, vendors and consortia collaborate to create data transfer standards for multi-vendor, multi-platform, secure and reliable interoperability in industrial automation.” • To support this mission,
    [Show full text]
  • Fundamentals of OPC
    Presents Practical Fundamentals of OPC Revision 7.1 Web Site: www.idc-online.com E-mail: idc@idc-online.com Copyright All rights to this publication, associated software and workshop are reserved. No part of this publication or associated software may be copied, reproduced, transmitted or stored in any form or by any means (including electronic, mechanical, photocopying, recording or otherwise) without prior written permission of IDC Technologies. Disclaimer Whilst all reasonable care has been taken to ensure that the descriptions, opinions, programs, listings, software and diagrams are accurate and workable, IDC Technologies do not accept any legal responsibility or liability to any person, organization or other entity for any direct loss, consequential loss or damage, however caused, that may be suffered as a result of the use of this publication or the associated workshop and software. In case of any uncertainty, we recommend that you contact IDC Technologies for clarification or assistance. Trademarks All terms noted in this publication that are believed to be registered trademarks or trademarks are listed below: Acknowledgements IDC Technologies expresses its sincere thanks to all those engineers and technicians on our training workshops who freely made available their expertise in preparing this manual. Who is IDC Technologies? IDC Technologies is a specialist in the field of industrial communications, telecommunications, automation and control and has been providing high quality training for more than six years on an international basis from offices around the world. IDC consists of an enthusiastic team of professional engineers and support staff who are committed to providing the highest quality in their consulting and training services.
    [Show full text]
  • MSG : Multiprotocol SCADA Gateway
    MSG : Multiprotocol SCADA Gateway Overview The MSG is a modern SCADA communication gateway server for telemetry applications. It supports all of Inifnite's devices, offering seamless SCADA integration using a variety of means and and protocols. The MSG server is a host for multiple clients allowing seamless 24/7 unmanned device telemetry with centralised data management. Features Support for all Infinite product ranges including BSC-50, ADU-500, ADU- 700, Sigfox ADS, iLog & SCOM. Multiple SCADA protocols including, DNP3 DNP3 Secure Authentication v5 (SAv5) IEC 60870-5-101 IEC 60870-5-102 IEC 60870-5-103 IEC 60870-5-104 IEC 60870-5 Secure Authentication for -101 and -104 OPC Data Access OPC XML Data Access OPC Alarms & Events IEC 61850 incl: 7-410(Hydro), 7- 420(DER) & 61400-25 IEC 60870-6 (TASE.2/ICCP) incl. Bi- Directional Support Modbus Connectivity via RS232 serial port, USB, ethernet, modem. MS SQL server database backend for historical data storage and management. Integration with the WaT cloud server that offers a Web interface accessible using any browser & device. Device & data management The MSG server has a comprehensive set of tools for users to : Create and manage devices and Tags. Test SCADA connectivity and protocol integrity. View, edit, delete, search & export data. Assign tags to IO and configure their properties Available integrated with the WaT cloud server server SCADA & data functionality The MSG is a Windows application used by System Integrators and Utilities to collect data from OPC, IEC 60870-6 (TASE.2/ICCP), IEC 61850, IEC 60870-5, DNP3, or Modbus Server/Slave devices and then supplies this data to other control systems supporting OPC, IEC 60870-6 (TASE.2/ICCP) Client, IEC 60870-5, DNP3, and/or Modbus Client/Master communication protocols.
    [Show full text]
  • OPC Factory Server V3.60 OFS Product Introduction 35008244 11/2015
    OPC Factory Server V3.60 35008244 11/2015 OPC Factory Server V3.60 User Manual 11/2015 35008244.11 www.schneider-electric.com The information provided in this documentation contains general descriptions and/or technical characteristics of the performance of the products contained herein. This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications. It is the duty of any such user or integrator to perform the appropriate and complete risk analysis, evaluation and testing of the products with respect to the relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information contained herein. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us. No part of this document may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without express written permission of Schneider Electric. All pertinent state, regional, and local safety regulations must be observed when installing and using this product. For reasons of safety and to help ensure compliance with documented system data, only the manufacturer should perform repairs to components. When devices are used for applications with technical safety requirements, the relevant instructions must be followed. Failure to use Schneider Electric software or approved software with our hardware products may result in injury, harm, or improper operating results. Failure to observe this information can result in injury or equipment damage.
    [Show full text]
  • PI Interface for OPC DA Version 2.5.1.X User Guide
    PI Interface for OPC DA Version 2.5.1.x User Guide OSIsoft, LLC 777 Davis St., Suite 250 San Leandro, CA 94577 USA Tel: (01) 510-297-5800 Fax: (01) 510-357-8136 Web: http://www.osisoft.com PI Interface for OPC DA User Guide © 1998-2014 by OSIsoft, LLC. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, mechanical, photocopying, recording, or otherwise, without the prior written permission of OSIsoft, LLC. OSIsoft, the OSIsoft logo and logotype, PI Analytics, PI ProcessBook, PI DataLink, ProcessPoint, PI Asset Framework (PI AF), IT Monitor, MCN Health Monitor, PI System, PI ActiveView, PI ACE, PI AlarmView, PI BatchView, PI Coresight, PI Data Services, PI Event Frames, PI Manual Logger, PI ProfileView, PI WebParts, ProTRAQ, RLINK, RtAnalytics, RtBaseline, RtPortal, RtPM, RtReports and RtWebParts are all trademarks of OSIsoft, LLC. All other trademarks or trade names used herein are the property of their respective owners. U.S. GOVERNMENT RIGHTS Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the OSIsoft, LLC license agreement and as provided in DFARS 227.7202, DFARS 252.227-7013, FAR 12.212, FAR 52.227, as applicable. OSIsoft, LLC. Version: 2.5.1.x Published: March 2014 Contents Introduction to the PI OPC DA interface...................................................................... 1 Related manuals............................................................................................................................................
    [Show full text]
  • A Literature Survey on Open Platform Communications (OPC) Applied to Advanced Industrial Environments
    electronics Review A Literature Survey on Open Platform Communications (OPC) Applied to Advanced Industrial Environments Isaías González 1,* , Antonio José Calderón 1 , João Figueiredo 2,3 and João M. C. Sousa 3 1 Department of Electrical Engineering, Electronics and Automation, University of Extremadura, Avenida de Elvas, s/n, 06006 Badajoz, Spain; ajcalde@unex.es 2 Centre of Mechatronics Engineering—CEM, University of Évora, R. Romão Ramalho, 59, 7000-671 Évora, Portugal; jfig@uevora.pt 3 IDMEC, Instituto Superior Técnico, Universidade de Lisboa; 1049-001 Lisboa, Portugal; jmsousa@tecnico.ulisboa.pt * Correspondence: igonzp@unex.es; Tel.: +34-924-289-600 Received: 31 March 2019; Accepted: 4 May 2019; Published: 8 May 2019 Abstract: Extensive digitization and interconnection through networks have ushered in a number of new paradigms over the last years: Internet of Things, cyber–physical systems, Industry 4.0, etc. These challenging systems rely on an effective information communication between distributed components. Therefore, the heterogeneity of entities, both hardware and software, must be handled to achieve an operative interoperability and a proper behavior. However, there is also a heterogeneous availability of solutions; different technologies, protocols, and architectures aim to achieve a seamless interconnection. Henceforth, the standardization still requires great efforts from industrial and scientific environments. In this sense, the interface of the open platform communications (OPC) has supported connectivity for automation and supervision infrastructures for more than two decades. The OPC comprises the so-called classic OPC, the original protocol, as well as the last specification, unified architecture (UA). The widespread utilization of the classic OPC together with the powerful functionalities of OPC UA, make the latter one of the main candidates to lead the standardization and systems integration.
    [Show full text]