China Network IsolatorOSIsoft.doc
《China Network IsolatorOSIsoft.doc》由会员分享,可在线阅读,更多相关《China Network IsolatorOSIsoft.doc(91页珍藏版)》请在三一办公上搜索。
1、China Network IsolatorVersion 2.1.2.xRevision BOSIsoft, LLC 777 Davis St., Suite 250San Leandro, CA 94577 USATel: (01) 510-297-5800Fax: (01) 510-357-8136Web: OSIsoft Australia Perth, AustraliaOSIsoft Europe GmbH Frankfurt, GermanyOSIsoft Asia Pte Ltd. Singapore OSIsoft Canada ULC Montreal & Calgary,
2、 CanadaOSIsoft, LLC Representative Office Shanghai, Peoples Republic of ChinaOSIsoft Japan KK Tokyo, JapanOSIsoft Mexico S. De R.L. De C.V. Mexico City, MexicoOSIsoft do Brasil Sistemas Ltda. Sao Paulo, BrazilChina Network IsolatorCopyright: 2007-2023 OSIsoft, LLC. All rights reserved. No part of th
3、is 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, Proc
4、essPoint, PI Asset Framework(PI-AF), IT Monitor, MCN Health Monitor, PI System, PI ActiveView, PI ACE, PI AlarmView, PI BatchView, PI Data Services, PI Manual Logger, PI ProfileView, PI WebParts, ProTRAQ, RLINK, RtAnalytics, RtBaseline, RtPortal, RtPM, RtReports and RtWebParts are all trademarks of
5、OSIsoft, LLC. All other trademarks or trade names used herein are the property of their respective owners.U.S. GOVERNMENT RIGHTSUse, 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 25
6、2.227-7013, FAR 12.212, FAR 52.227, as applicable. OSIsoft, LLC.Published: 01/0001Table of ContentsTerminologyviiChapter 1.Introduction1Limitations2PI System Administrator Tasks2Reference Manuals3Pre-Requisites3Supported Features4Diagram of Hardware Connection7Chapter 2.Principles of Operation9Netwo
7、rk Isolator9Client/Server Communications Model10System Initialization Requirements10PI Point Synchronization10Tag Sync File11Tag Map Table11Shutdown Attribute13Time-series Data Transfer13History Recovery13Real-time Data Collection14Source PI Server14Target PI Server14Update Frequency15PI Server Depe
8、ndencies15Chapter 3.Installation Checklist17Network Isolator17One-time Initialization of Target PI Server17Target PI Server18Source PI Server18Verification of Data Transfer by the Interface19Re-Initialization of Target PI Server19Chapter 4.Interface Installation21Interface Directories21PIHOME Direct
9、ory Tree21Interface Installation Kit21Installing Interface as a Windows Service22Installing Interface Service with PI Interface Configuration Utility22Service Configuration23Installing Interface Service Manually26Chapter 5.Connection Tool27Chapter 6.Digital States29Chapter 7.PointSource31Chapter 8.P
10、I Point Configuration33Chapter 9.Performance Point Configuration35Chapter 10.I/O Rate Point Configuration37Chapter 11.Startup Command File39ICU Configuration on the source PI Server39ICU Configuration on the target PI Server41Command-line Parameters42Sample PIChinaNetIso.bat Files45Chapter 12.Interf
11、ace Node Clock47Chapter 13.Security49Chapter 14.Starting / Stopping the Interface51Starting Interface as a Service51Stopping Interface Running as a Service51Chapter 15.Buffering53Appendix A.Error and Informational Messages55Message Logs55System Errors and PI Errors55Appendix B.Point Synchronization
12、Failures57Messages on the Source PI Server57Messages on the Target PI Server58Corrupt Tag Sync File58Corrupt Tag Map File58Appendix C.Cluster Configuration61Sample Installation61Appendix D.Technical Support and Resources77Before You Call or Write for Help77Help Desk and Telephone Support77Search Sup
13、port78Email-based Technical Support78Online Technical Support78Remote Access79On-site Service79Knowledge Center79Upgrades79OSIsoft Virtual Campus (vCampus)79Appendix E.Revision History81 TerminologyTo understand this interface manual, you should be familiar with the terminology used in this document
14、.BufferingBuffering refers to an Interface Nodes ability to store temporarily the data that interfaces collect and to forward these data to the appropriate PI Servers.N-Way BufferingIf you have PI Servers that are part of a PI Collective, PIBufss supports n-way buffering. Nway buffering refers to th
15、e ability of a buffering application to send the same data to each of the PI Servers in a PI Collective. (Bufserv also supports n-way buffering to multiple PI Servers however it does not guarantee identical archive records since point compressions attributes could be different between PI Servers. Wi
16、th this in mind, OSIsoft recommends that you run PIBufss instead.)ICUICU refers to the PI Interface Configuration Utility. The ICU is the primary application that you use to configure PI interface programs. You must install the ICU on the same computer on which an interface runs. A single copy of th
17、e ICU manages all of the interfaces on a particular computer.You can configure an interface by editing a startup command file. However, OSIsoft discourages this approach. Instead, OSIsoft strongly recommends that you use the ICU for interface management tasks.ICU ControlAn ICU Control is a plug-in t
18、o the ICU. Whereas the ICU handles functionality common to all interfaces, an ICU Control implements interface-specific behavior. Most PI interfaces have an associated ICU Control.Interface NodeAn Interface Node is a computer on which the PI API and/or PI SDK are installed, and PI Server programs ar
19、e not installed.PI APIThe PI API is a library of functions that allow applications to communicate and exchange data with the PI Server. All PI interfaces use the PI API.PI CollectiveA PI Collective is two or more replicated PI Servers that collect data concurrently. Collectives are part of the High
20、Availability environment. When the primary PI Server in a collective becomes unavailable, a secondary collective member node seamlessly continues to collect and provide data access to your PI clients.PIHOMEPIHOME refers to the directory that is the common location for PI 32-bit client applications.
21、A typical PIHOME on a 32-bit operating system is C:Program FilesPIPC. A typical PIHOME on a 64-bit operating system is C:Program Files (x86)PIPC.PI 32-bit interfaces reside in a subdirectory of the Interfaces directory under PIHOME. For example, files for the 32-bit Modbus Ethernet Interface are in
22、PIHOMEPIPCInterfacesModbusE.This document uses PIHOME as an abbreviation for the complete PIHOME or PIHOME64 directory path. For example, ICU files in PIHOMEICU.PIHOME64PIHOME64 is found only on a 64-bit operating system and refers to the directory that is the common location for PI 64-bit client ap
23、plications. A typical PIHOME64 is C:Program FilesPIPC. PI 64-bit interfaces reside in a subdirectory of the Interfaces directory under PIHOME64. For example, files for a 64-bit Modbus Ethernet Interface would be found in C:ProgramFilesPIPCInterfacesModbusE.This document uses PIHOME as an abbreviatio
24、n for the complete PIHOME or PIHOME64 directory path. For example, ICU files in PIHOMEICU.PI Message LogThe PI message Log is the file to which OSIsoft interfaces based on UniInt 4.5.0.x and later writes informational, debug and error message. When a PI interface runs, it writes to the local PI mess
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- China Network Isolator OSIsoft
链接地址:https://www.31ppt.com/p-2400196.html