-
Feature
|
Support
|
Interface Part Number
|
PI-IN-CI-CITEC-NTI
|
Auto Creates PI Points
|
No
|
Point Builder Utility
|
Yes
|
ICU Control
|
Yes
|
PI Point Types
|
real / digital / integer / string
|
Sub-second Timestamps
|
Yes
|
Sub-second Scan Classes
|
Yes
|
Automatically Incorporates PI Point Attribute Changes
|
Yes
|
Exception Reporting
|
Yes
|
Outputs from PI
|
Yes
|
Inputs to PI:
|
Scan-based/Event Tags
|
Supports Questionable Bit
|
No
|
Supports Multi-character PointSource
|
Yes
|
Maximum Point Count
|
Unlimited
|
* Uses PI SDK
|
No
|
PINet String Support
|
N/A
|
* Source of Timestamps
|
PI Interface
|
History Recovery
|
No
|
* UniInt-based
* Disconnected Startup
* SetDeviceStatus
|
Yes
Yes
Yes
|
* Failover
|
UniInt Failover (Phase 2); Cold, Warm and Hot
|
* Vendor Software Required on Interface Node / PINet Node
|
Yes
|
Vendor Software Required on Foreign Device
|
Yes
|
Vendor Hardware Required
|
No
|
Additional PI Software Included with interface
|
Yes
|
Device Point Types
|
|
Serial-Based interface
|
No
|
* See paragraphs below for further explanation.
Source of Timestamps
Timestamps are generated within the interface. If the scan class is sub-second, then sub-second timestamps will be used.
UniInt-based
UniInt stands for Universal Interface. UniInt is not a separate product or file; it is an OSIsoftdeveloped template used by developers and is integrated into many interfaces, including this interface. The purpose of UniInt is to keep a consistent feature set and behavior across as many of OSIsoft’s interfaces as possible. It also allows for the very rapid development of new interfaces. In any UniInt-based interface, the interface uses some of the UniIntsupplied configuration parameters and some interface-specific parameters. UniInt is constantly being upgraded with new options and features.
The UniInt Interface User Manual is a supplement to this manual.
Disconnected Start-Up
The PI Citect interface is built with a version of UniInt that supports disconnected start-up. Disconnected start-up is the ability to start the interface without a connection to the PI Server. This functionality is enabled by adding /cachemode to the list of start-up parameters or by enabling disconnected startup using the ICU. Refer to the UniInt Interface User Manual for more details on UniInt disconnected startup.
SetDeviceStatus
The PI Citect Interface is built with UniInt 4.5.4.0 New functionality has been added to support health tags. The Health tag with the point attribute Exdesc = [UI_DEVSTAT], is used to represent the status of the connection to the Citect system. The following events can be written into the tag:
"1 | Starting" - the interface is starting
"2 | Connected/No Data" - the interface is part of a failover pair and is not currently active.
"3 | 1 device(s) in error | Not connected to Citect" - the interface is unable to connect to the Citect system.
"Good" - the interface is scanning the Citect system for data.
“4 | Intf Shutdown” – interface has shutdown.
Refer to the UniInt Interface User Manual.doc file for more information about how to configure health points.
Failover
UniInt Failover Support
UniInt Phase 2 Failover provides support for cold, warm or hot failover configurations. The Phase 2 hot failover results in a no data loss solution for bi-directional data transfer between the PI Server and the Data Source given a single point of failure in the system architecture similar to Phase 1. However, in warm and cold failover configurations, you can expect a small period of data loss during a single point of failure transition. This failover solution requires that two copies of the interface be installed on different interface nodes collecting data simultaneously from a single data source. Phase 2 Failover requires each interface have access to a shared data file. Failover operation is automatic and operates with no user interaction. Each interface participating in failover has the ability to monitor and determine liveliness and failover status. To assist in administering system operations, the ability to manually trigger failover to a desired interface is also supported by the failover scheme.
The failover scheme is described in detail in the UniInt Interface User Manual, which is a supplement to this manual. Details for configuring this interface to use failover are described in the UniInt Failover Configuration section of this manual.
The interface requires that the PI API and Citect API be installed on the PI Interface node. The PI API version must be at least 1.6.x.x. The version of Citect API client depends on the version of Citect. Version 3.x of the interface has been built for Version 6 or later of Citect.
The Citect API consists of a set of DLL files, which should be copied from the Citect machine onto the PI Interface node.
These files are (and must be copied into the folder where the PI_Citect.exe is located):
-
CtApi.dll
-
CtEng32.dll
-
CiDebugHelp.dll
-
CtRes32.dll
-
CtUtil32.dll
-
Ct_ipc.dll
Vendor Software Required on Foreign Device
The interface requires that Citect API licenses are available on the Citect system. If the Citect system does not have an API license available, the connection request from the interface will be rejected by the Citect node.
Additional PI Software
A test utility called “PI_CitectTest.exe” is included with the interface. This can be used to ensure that the machine running the interface can connect successfully to the Citect node and read values from the Citect real-time database.
Share with your friends: |