Pi bailey Sem api interface Manual

Supported Features

Feature	Support
Part Number	PI IN-BA-SEMAP-NTI
*Platforms	Windows 2000/XP/2003 Server
APS Connector	Yes
Point Builder Utility	No
ICU Control	Yes
PI Point Types	Float32 / Float16 / Digital / Int16 / Int32 / string
Sub-second Timestamps	No
Sub-second Scan Classes	No
Automatically Incorporates PI Point Attribute Changes	Yes
* Exception Reporting	Done by Bailey System
Outputs from PI	Yes
Inputs to PI: Scan-based / Unsolicited / Event Tags	Unsolicited
Supports Questionable Bit	No
Supports Multi-character PointSource	Yes
Maximum Point Count	30,000
* Uses PI SDK	No
PINet String Support	Yes
* Source of Timestamps	PI server
History Recovery	No
* UniInt-based * Disconnected Startup * SetDeviceStatus	Yes Yes Yes
* Failover	Yes
Vendor Software Required on PI Interface Node	Yes
* Vendor Software Required on Foreign Device	Yes
* Vendor Hardware Required	Yes
Additional PI Software Included with Interface	No
* Serial-Based Interface	Yes

Platforms

Exception Reporting

The Bailey System sends data to the PI interface by exception. Hence, by default, the interface does not apply the PI tag’s exception reporting on top of the Bailey events.

Uses PI SDK

The PI SDK and the PI API are bundled together and must be installed on each PI Interface node. This Interface does not specifically make PI SDK calls.

Source of Timestamps

The interface keeps tracks of the current time of the PI server. It applies that time to the timestamp of the exception-based event sent from Bailey.

Failover

The interface supports failover to provide redundant data collection on both VMS platform and on Windows platform. The failover setup involves two instances of the interface, one in primary data collection mode and one in secondary or standby data collection mode. Each interface communicates to a separate ICI module. The secondary interface would monitor the ICI module status of the primary interface. If the primary ICI module is not in execute mode, the secondary interface will start collecting data. When the primary ICI module comes back on-line, the secondary interface would go back to standby mode.
Since the failover mechanism depends on the ICI module, do not set the ICI watch dog timer to 0 for the primary interface. Otherwise, the ICI module will continue to be in execute mode even if the primary interface stops communicating to the ICI module.
When installing the interface in failover setup, test the failover configuration by stopping the primary interface program and verifying that the secondary interface picks up data collection. If the secondary interface cannot read the module status of the primary ICI module within five minutes of the interface startup, the interface program will terminate, assuming the PCU address provided by the command file is incorrect. This safety check is designed to avoid having both instances of the interface collecting data at the same time.

UniInt-based

UniInt stands for Universal Interface. UniInt is not a separate product or file; it is an OSIsoft-developed 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 UniInt‑supplied 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 Bailey semAPI 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 Disconnect startup.

SetDeviceStatus

New functionality added to support Health tags. The Health tag with the point attribute Exdesc = [UI_DEVSTAT], is used to represent the status of the source device. The following events can be written into the tag:

1. 
   “1 | Starting” – the interface is starting.
   
2. 
   “Good” – the interface is properly communicating and reading data from the Bailey semAPI system.
   
3. 
   “2 | Connected/No data | ICI Offline” – this event represents that the Bailey semAPI system is offline.
   
4. 
   “3 | 1 device(s) in error | Not connected to semAPI” – This event represents a failure to communicate with the Bailey semAPI system.
   
5. 
   “4 | Intf Shutdown” – the interface is stopped.
   

Please refer to the UniInt Interface User Manual.doc for more information on how to configure UniInt health points.

Vendor Software Required

The interface needs the Bailey semAPI Runtime, Supervisory Control, or Development Kit to be installed on the interface node.

Vendor Hardware Required

The interface connects to ICI03 via SCSI or serial connection.

Download 2.52 Mb.

Share with your friends: