The PI Citect Interface provides communication between PI and Citect. It is based on a version of the OSIsoft standard Universal Interface (UniInt), adapted for the Citect environment.
Data is transferred between Citect and PI via the Citect application programming interface (CTAPI) and the PI API. The interface runs on Microsoft Windows XP operating systems, or greater.
The interface supports input tags (from Citect to PI) and output tags (from PI to Citect). Data from Citect is received at cyclic frequencies or by exception in the data. The frequency of the cycles is configured by the user and controlled by the interface. The number of tags that the interface is capable of servicing is limited only by external limitations, for example, the amount of available memory in the computer and the load on the Citect IO server.
Changes that are made to the PI point database are reflected in the interface. This includes the adding, editing and deleting of tags.
All error information and some summary information are output to a log file. If the interface is run interactively from an MS-DOS prompt, then the output is displayed on the screen. The amount of summary information that is output is configurable by the user and is minimal by default. For information about configuring information messages, see /df in the Command-line Parameters section.
For the interface to be able to connect to the Citect database, the Citect node must have sufficient API licenses available. The number of Citect licenses available is shown in the “General” window of the “Citect Kernel” utility. Note that with earlier versions of Citect (before 5.40), Citect included 2 API licenses by default. As of version 5.40, the Citect API licenses (also known as Connection licenses) must be explicitly included.
Citect Clusters
Starting with Citect version 7.0 all servers need to be assigned to a Citect cluster. When referencing Citect points (see the InstrumentTag attribute), the Citect point name can be prefixed with the cluster name, i.e. “.
”. If only one Citect cluster is defined on site, the use of the Cluster prefix is optional. If multiple clusters are defined in an environment, the cluster prefix must be specified.
Each instance of the PI Citect interface can connect to only one Citect Server regardless of whether the server is a clustered server or not. To connect to a pair of Citect servers in a Reliable Clustering configuration, two interface instances configured in failover mode are required. Both servers must be located in the same Operational or Ad-Hoc Cluster.
Note: Throughout this manual there are references to where messages are written by the interface which is the PIPC.log. This interface has been built against a UniInt version (4.5.0.59 and later) which now writes all its messages to the local PI Message log.
Please note that any place in this manual where it references PIPC.log should now refer to the local PI message log. Please see the document UniInt Interface Message Logging.docx in the %PIHOME%\Interfaces\UniInt directory for more details on how to access these messages.
Reference Manuals OSIsoft
PI Server manuals
PI API Installation Instructions manual
UniInt Interface User Manual
Vendor
Citect Users Guide Version 5 or later
Citect Getting Started
Supported Operating Systems -
Platforms
|
32-bit application
|
64-bit application
|
Windows XP
|
32-bit OS
|
Yes
|
No
|
64-bit OS
|
Yes (Emulation Mode)
|
No
|
Windows 2003 Server
|
32-bit OS
|
Yes
|
No
|
64-bit OS
|
Yes (Emulation Mode)
|
No
|
Windows Vista
|
32-bit OS
|
Yes
|
No
|
64-bit OS
|
Yes (Emulation Mode)
|
No
|
Windows 2008
|
32-bit OS
|
Yes
|
No
|
Windows 2008 R2
|
64-bit OS
|
Yes (Emulation Mode)
|
No
|
Windows 7
|
32-bit OS
|
Yes
|
No
|
64-bit OS
|
Yes (Emulation Mode)
|
No
|
The interface is designed to run on the above mentioned Microsoft Windows operating systems and their associated service packs.
The interface is designed to run on the above-mentioned Microsoft Windows operating systems. Because it is dependent on vendor software, newer platforms may not yet be supported.
Please contact OSIsoft Technical Support for more information.
Share with your friends: |