Citect Interface

Advanced Interface Features

1. 
   Configure the interface for disconnected startup. Refer to the UniInt Interface User Manual for more details on UniInt disconnected startup.
   

5. Interface Installation

After the interface has been installed and tested, Buffering should be enabled on the interface node. Buffering refers to either PI API Buffer Server (Bufserv) or the PI Buffer Subsystem (PIBufss). For more information about Buffering see the Buffering chapter of this manual.

In most cases, interfaces on interface nodes should be installed as automatic services. Services keep running after the user logs off. Automatic services automatically restart when the computer is restarted, which is useful in the event of a power failure.

The guidelines are different if an interface is installed on the PI Server node. In this case, the typical procedure is to install the PI Server as an automatic service and install the interface as an automatic service that depends on the PI Update Manager and PI Network Manager services. This typical scenario assumes that Buffering is not enabled on the PI Server node. Bufserv can be enabled on the PI Server node so that interfaces on the PI Server node do not need to be started and stopped in conjunction with the PI Server, but it is not standard practice to enable buffering on the PI Server node. The PI Buffer Subsystem can also be installed on the PI Server. See the UniInt Interface User Manual for special procedural information.

Naming Conventions and Requirements

In the installation procedure below, it is assumed that the name of the interface executable is PI_Citect.exe and that the startup command file is called PI_Citect.bat.

When Configuring the Interface Manually

It is customary for the user to rename the executable and the startup command file when multiple copies of the interface are run. For example, PI_Citect1.exe and PI_Citect1.bat would typically be used for instance 1, PI_Citect2.exe and PI_Citect2.bat for instance 2, and so on. When an interface is run as a service, the executable and the command file must have the same root name because the service looks for its command-line parameters in a file that has the same root name.

Interface Directories

PIHOME Directory Tree

32-bit Interfaces

The [PIHOME] directory tree is defined by the PIHOME entry in the pipc.ini configuration file. This pipc.ini file is an ASCII text file, which is located in the %windir% directory.

For 32-bit operating systems, a typical pipc.ini file contains the following lines:

[PIPC]

PIHOME=C:\Program Files\PIPC

For 64-bit operating systems, a typical pipc.ini file contains the following lines:

[PIPC]

PIHOME=C:\Program Files (X86)\PIPC

The above lines define the root of the PIHOME directory on the C: drive. The PIHOME directory does not need to be on the C: drive. OSIsoft recommends using the paths shown above as the root PIHOME directory name.

Interface Installation Directory

The interface install kit will automatically install the interface to:

PIHOME\Interfaces\Citect\

PIHOME is defined in the pipc.ini file.

Interface Installation Procedure

The PI Citect interface setup program uses the services of the Microsoft Windows Installer. Windows Installer is a standard part of Windows 2000 and later operating systems. To install, run the appropriate installation kit.

Citect_#.#.#.#_.exe

Installing the Citect API DLL files

For the interface to run, it must be able to locate the Citect API DLL.

If the interface is running directly on the Citect node then the interface will be able to find the DLL files if the Citect Bin directory is on the PATH, or the DLL files are copied to either the Windows\System32 directory or to the interface installation directory. The recommended method is to having the Citect Bin directory added to the PATH. This means that there are no duplicate copies of files that can cause problems if the Citect software is updated.

If the interface is running on a separate PI interface node and connecting to a remote Citect machine then the DLLs must be copied from the Citect machines Bin directory into the interface installation directory.

The DLL files required by the interface are the following:

CtApi.dll

Ct_ipc.dll

CtEng32.dll

CtRes32.DLL

CtUtil32.dll

CiDebugHelp.dll (only on Citect 5.41 or later)

Note : If the Citect software is updated then any copies of the DLLs must also be updated. If the interface is collecting data from version 6.0 of Citect, you may have to download the latest version of citect on a test machine and grab these files.

Directory: interfaces
interfaces -> Pi interface for Siemens Spectrum Power tg (Linux)
interfaces -> Interface to the pi system Version 37 and Greater
interfaces -> Interface to the pi system
interfaces -> How to Contact Us
interfaces -> How to Contact Us
interfaces -> Emerson Deltav batch Interface

Download 0.67 Mb.

Share with your friends: