DOCSLIB.ORG

Data Acquisition Using Arrowhead Framework for Condition Based Maintenance of Industrial Equipment

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Data Acquisition Using Arrowhead Framework for Condition Based Maintenance of Industrial Equipment Data Acquisition using Arrowhead Framework for Condition Based Maintenance of Industrial Equipment Johan Jansson Högberg Computer Science and Engineering, master's level 2019 Luleå University of Technology Department of Computer Science, Electrical and Space Engineering ABSTRACT As Industry 4.0 and Internet of Things are established across factories and enterprises, the interest for learning more about these concepts and the possibilities they provide for condition based maintenance is expressed by a factory in Sweden. By addressing the aspects of Internet of Things and Industry 4.0, a system for performing data acquisition from sensors in an industrial environment is developed using Arrowhead Framework. This framework is evaluated around its suitability for this kind of application, and re- garding what the framework may provide to the factory compared to other solutions and systems. A solution featuring a system based on Arrowhead Framework is developed, implemented, and briefly tested. The system is successful in performing data acquisition, and Arrowhead Framework is considered a viable option that may be used to provide a system tailored for different purposes, presumed that the factory is prepared to allocate resources on developing a solution around it. iii PREFACE This thesis work has been a challenging, but yet greatly rewarding experience for me. I am grateful to have had the possibility to perform my thesis work within this industry, and being able to work with all the people involved here. I have been taught many things and experiences, which I am glad to be able to bring with me to future workplaces. I would like to thank my supervisor Ulf Bodin at Lule˚aUniversity of Technology and company supervisor Isak Grimholm for providing me with the guidance needed to realise this thesis work. I would like to thank Jens Aslin˚ for the great cooperation we have had, as well as the guys at IFM and the employees of the IT department at the factory who have supported me by providing tips, help and material needed for this work. Last but not least, I would like to thank PhD student Cristina Paniagua at Lule˚aUniversity of Technology for helping me solve problems I have encountered while working with Arrowhead Framework. Johan Jansson H¨ogberg v CONTENTS Chapter 1 { Introduction 3 1.1 Background . 3 1.2 Motivation . 4 1.3 Problem Definition . 4 1.3.1 System Requirements . 4 1.3.2 Topic Related Questions . 5 1.4 Delimitations . 5 1.5 Related Work . 6 1.5.1 Components and services of Industry 4.0 and IoT . 6 1.5.2 Usage of Arrowhead Framework in similar applications. 6 1.5.3 Similar project previously held at the factory . 6 Chapter 2 { Method 9 2.1 Method . 9 2.1.1 Research Methodology . 9 2.1.2 Evaluation . 10 Chapter 3 { Theory 13 3.1 Industry 4.0 . 13 3.2 Internet of Things . 13 3.3 Cloud- and fog computing . 14 3.4 Industrial automation systems . 14 3.4.1 ISA-95 . 14 3.4.2 RAMI 4.0 . 16 3.5 OPC and OPC-UA . 16 3.6 Service-oriented architectures . 18 3.7 Arrowhead Framework . 18 3.7.1 Concept . 19 3.7.2 Core systems . 19 3.7.3 Compliance and maturity levels . 22 Chapter 4 { Plant System 25 4.1 Transportation Buffer . 25 4.1.1 Transportation Cart . 25 4.1.2 Network structure . 27 4.2 Alternative Proof of Concept . 27 Chapter 5 { Solution 29 5.1 Solution overview . 29 5.2 Sensors . 30 5.2.1 IO-Link sensors . 31 5.2.2 Vibration sensors and IFM VSE100 Diagnostic electronic . 32 5.3 Arrowhead Framework components . 32 5.4 Connectivity towards networks and internet . 33 5.5 Microsoft Azure . 34 5.6 ThingWorx . 34 Chapter 6 { Results, Evaluation and Future work 37 6.1 Resulting implementation . 37 6.2 Evaluation and discussion . 41 6.3 Future work . 43 6.3.1 Sensors and framework components . 44 6.3.2 Cloud services and analysis . 44 Appendix A{ Tables and Graphs 45 viii Abbreviations & Acronyms AHF . Arrowhead Framework API . Application Programming Interface BU3 . The sequential buffer at the factory CBM . Condition-Based Monitoring ERP . Enterprise Resource Planning IIoT . Industrial Internet of Things IoT . Internet of Things IR . Infrared MES . Manufacturing Execution System OPC . Open Platform Communications OPC-UA . Open Platform Communications Unified Architecture PLC . Programmable Logic Controller PoC . Proof of Concept RAMI4.0 . Reference Architecture Model Industrie 4.0 SCADA . Supervisory Control and Data Acquisition SOA . Service Oriented Architecture 1 CHAPTER 1 Introduction 1.1 Background Industry 4.0 and Internet of Things are two popular topics regarding the development of and evolution within industries today. The industrial digitization that is occurring enables manufacturers to more easily observe and interact with machines and manufac- turing equipment, in favour for optimizing and increasing production. One area that has benefited from this is the utilization of condition-based maintenance (CBM), where equipment is maintained with regard to its condition, rather than being maintained on a interval-basis regardless of condition. This thesis focuses on a factory that is looking to modernize and take part of the benefits from condition-based maintenance. At this factory, equipment in a certain pro- duction line is maintained on a pre-planned interval-based maintenance routine. During each maintenance occasion, the equipment is inspected manually and treated upon judge- ments from visual inspection. As the inspections are carried out by hand, humans need to physically enter the area of the equipment. Due to safety regulations, any affected production equipment may not be in operation when inspections occur. Consequently, inspections are often scheduled to occur mainly during nights and weekends, outside pro- duction hours. This in turn may lead to high operational costs in terms of expensive maintenance efforts, unforeseen repairs if malfunctions arise between maintenance occa- sions, and in case production is halted during active hours; overtime production in order to cover for lost production time. Another effect that follows from this is a larger amount of staffing as a result of installing a higher capacity to cover the maintenance and repair needs. There is also a risk of a poorer quality outcome as a result of equipment malfunc- tioning, causing direct or indirect quality impacts on the product in case equipment is not maintained properly. Apart from production impacts, malfunctions also increase the risk of injuries to persons. To be able to continue the production in an effective and competitive way in the future, the factory wishes to modernize and increase the efficiency of the maintenance, as well 3 4 Introduction as taking steps towards Industry 4.0. 1.2 Motivation The factory wishes to advance from the interval-based maintenance that is used today and establish a condition-based maintenance routine for the equipment, as well as explore the area of Industry 4.0 and the possibilities it provides. To enable condition-based maintenance, the idea is to with the use of sensors measure parameters of the equipment which are likely to provide information that can be correlated to wear of the parts in the equipment. By storing the sensed data for the different parameters a model may be created from it. This model may be used for determining the condition of the equipment using real-time data, and finally establish a condition-based maintenance routine. 1.3 Problem Definition The goal of this master thesis is to provide and implement a solution using Arrowhead Framework, a service-oriented software architecture developed for industrial automation. The solution shall enable data collection from sensors on legacy equipment, and store the data in a location it can be reached for processing, visualization, and analysis. A visualization platform will visualize stored and real-time sensor data. The solution shall utilize Industry 4.0 concepts as a way to demonstrate its possibilities for future interest. The targeted equipment the solution is developed for is a transportation cart in a large sequential buffer, which transports, stores, and sorts the manufactured goods between assembly lines. Furthermore, the factory has engaged a project to rebuild this sequential buffer, making it a suitable target as it more easily may be adapted to be able to utilize the solution produced from this thesis, if desired. The reason behind choosing Arrowhead Framework for this purpose is purely out of interest as it is a newly developed framework and the product of a large EU project involving many partners, including Lule˚aUni- versity of Technology. More of this in section 3.7. By performing this implementation, Arrowhead Framework is investigated and demonstrated regarding its usefulness for the factory and suitability for this type of application. 1.3.1 System Requirements Besides the general goals, there are some specifications and requests regarding the system that the factory wishes to meet. The system shall: • Be a generic IoT-platform. • Be scalable and flexible in such way that additional hardware may be added to the system to expand its physical size and area of operation, and able to have hardware replaced or upgraded with other hardware. 1.4. Delimitations 5 • Be compliant with any sensors and adjoining systems. • Refine and identify the data connecting it to events in the real system. • Be compliant with legacy-equipment. These requests are established as the factory do not want the system to be restricted for usage with only specific systems and suppliers. This strengthens the motivation for using Arrowhead Framework, as it allegedly is
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, [email protected], 2Penza State University, Penza, Russia, [email protected], [email protected], 3National Technical University "Kharkiv Polytechnic Institute", Kharkiv, Ukraina, [email protected] 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: [email protected] 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]
  • 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’.
    [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]