Citect Interface
Download 0.67 Mb.
|
- Navigate this page:
- Scan-based
- Event-based
- Output Points
- UniInt Failover
- Data Collection Steps
Input PointsInput tags are serviced by the interface to collect data from Citect and send it to PI. They can either be scan-based or event-based. Scan-based tags are serviced regularly at a pre-defined time interval. Event-based tags are serviced when a change occurs in a separate PI tag. Scan-basedIt is possible to configure an input tag to be updated at a regular time interval specified by any one of a set of user-defined scan classes. The interval of each scan class is based from and controlled by the interface. When a scan class’s time interval expires, the data for the tags that are configured for that scan class is requested. By default for this interface, only the tags whose values have changed since the last read will be collected from Citect and hence the PI point will not be updated. The points will be scanned every scan period but if there is no change for a point, the interface won’t make any request to collect the data. This is very helpful in reducing the number of requests being made to the Citect IO server. For information about defining scan-based input tags, see the description of /f in the Command-line Parameters section. If you define the /V2 Startup Command line parameter then the interface will scan and collect new data for every tag even if there is no change in tag value in Citect. For more information see the description of /V2 in the Command-line Parameters section. Event-basedAn input tag can be configured to send data to PI on an event, based on the exception of the data from a separate PI point. When the value of this separate PI point changes the data for the actual tag is requested from Citect. For information about setting up an exception tag, see the ExDesc section. Output PointsOutput tags are serviced by the interface to collect data from PI and send it to Citect based on the exception of a separate PI tag (referred to as a “source” tag). When the value of the source tag changes, it is sent both to Citect and to the output tag. This keeps a record of data that were sent to Citect. For more information about setting up an output tag, see the Output Points section in the PI Point Configuration chapter. If a tag is defined to be an output tag, its settings override any settings that apply to input tags. UniInt FailoverThis interface supports UniInt failover. Refer to the UniInt Failover Configuration chapter of this document for configuring the interface for failover.
If you are familiar with running PI data collection interface programs, this checklist helps you get the interface running. If you are not familiar with PI interfaces, return to this section after reading the rest of the manual in detail. This checklist summarizes the steps for installing this interface. You need not perform a given task if you have already done so as part of the installation of another interface. For example, you only have to configure one instance of Buffering for every interface node regardless of how many interfaces run on that node. The Data Collection Steps below are required. Interface Diagnostics and Advanced Interface Features are optional.
2.If you are running the interface on an interface node, edit the PI Server’s Trust Table to allow the interface to write data. 3.Run the installation kit for the PI Interface Configuration Utility (ICU) on the interface node if the ICU will be used to configure the interface. This kit runs the PI SDK installation kit, which installs both the PI API and the PI SDK. 4.Run the installation kit for this interface. This kit also runs the PI SDK installation kit which installs both the PI API and the PI SDK if necessary. 5.Ensure that the Citect API DLL files are installed on the interface node where PI_Citect.exe is located. Read Installing the Citect API DLL Files for more information.
6.If the interface is collecting data from version 6.0 of Citect, you may have to download the latest version of Citect (7.x or above) on a test machine and grab these .dll files and copy it in the interface folder. This is a known backward compatibility issues and this is the suggested way of fixing it. 7.If the interface is making connection to Citect Client process remotely (/Cihost parameter), make sure the citect.ini file in the ProgramData directory has this [CtAPI] Remote=1 entry. You can find this file in the directory at %ALLUSERSPROFILE% \Citect\CitectSCADA 7.20\Config. The environment variable ALLUSERSPROFILE is set as C:\ProgramData in Windows 7 by default and as C:\Documents and Settings\All Users in Windows XP by default. You can add this text to the top of the file: [CtAPI] Remote=1 8.Ensure that there are sufficient Citect API licenses available on the Citect node. 9.If you are running the interface on an interface node, check the computer’s time zone properties. An improper time zone configuration can cause the PI Server to reject the data that this interface writes. 10.Test the connection between the interface node and the Citect node using the PI_CitectTest.exe connection tester. 11.Run the ICU and configure a new instance of this interface. Essential startup parameters for this interface are: Point Source (/PS=x) Interface ID (/ID=#) PI Server (/Host=host:port) Scan Class (/F=##:##:##,offset) Citect Node Name (/cihost=name) Citect User Name for remote connection (/ciuser=x) Citect User Password (/cipass=password) 12. Define digital states. Cit_Bad_Conn - an indicator of communication problems with the Citect node. 13.Build input tags and, if desired, output tags for this interface using the point builder utility PICitect_PointBuilder.exe. Important point attributes and their purposes are: Location1 specifies the interface instance ID. Location2 is the input / output parameter (0=input, 1=output). Location3 not used. Location4 specifies the scan class. Location5 not used. ExDesc is optional and used for event driven point scans (EVENT=). InstrumentTag is the Citect point name. 14.Start the interface interactively and confirm its successful connection to the PI Server without buffering. 15.Confirm that the interface collects data successfully. 16.Stop the interface and configure a buffering application (either Bufserv or PIBufss). When configuring buffering use the ICU menu item Tools Buffering… Buffering Settings to make a change to the default value (32678) for the Primary and Secondary Memory Buffer Size (Bytes) to 2000000. This will optimize the throughput for buffering and is recommended by OSIsoft. 17.Start the buffering application and the interface. Confirm that the interface works together with the buffering application by either physically removing the connection between the interface node and the PI Server Node or by stopping the PI Server. 18.Configure the interface to run as a Service. Confirm that the interface runs properly as a Service. 19.Restart the interface node and confirm that the interface and the buffering application restart.
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:
|