The text selector returns a message code number to PI. User can define the PI tag as digital point and put the corresponding message text in the digital state table or define the PI tag as integer point.
Harmony Analog Input (Bailey Point Type 70)
This point type is supported only through Bailey semAPI version 2.0 and greater, which necessitates PI semAPI interface version 1.3 or greater. The conversion is the same as the other analog point types. The status of the analog value can be accessed through the following extended attributes:
Code
Field length
Description
1
1
Quality (uc_q)
2
1
high Alarm (uc_h_alrm)
3
1
low Alarm (uc_l_alrm)
4
1
Status errors are inhibited (uc_sei)
5
1
Simulated (uc_sim)
6
1
Overridden value (uc_oe)
7
1
Value is suspect (uc_susp)
8
1
Propagated quality (uc_pq)
9
1
Extended range (uc_er)
10
1
Configuration error exists (uc_cerr)
11
2
Channel condition (uc_range)
12
1
Readback status (uc_rbst)
13
1
Reference status (uc_ref)
14
1
Calibration status (uc_cal)
Harmony Analog Output (Bailey Point Type 71)
This point type is supported only through Bailey semAPI version 2.0 and greater, which necessitates PI semAPI interface version 1.3 or greater. The conversion is the same as the other analog point types. The status of the analog value can be accessed through the following extended attributes:
Code
Field length
Description
1
1
Quality (uc_q)
2
1
high Alarm (uc_h_alrm)
3
1
low Alarm (uc_l_alrm)
4
1
Status errors are inhibited (uc_sei)
5
1
Simulated (uc_sim)
6
1
Overridden value (uc_oe)
7
1
Value is suspect (uc_susp)
8
1
Propagated quality (uc_pq)
9
1
Extended range (uc_er)
10
1
Configuration error exists (uc_cerr)
11
2
Channel condition (uc_range)
12
1
Readback status (uc_rbst)
13
1
Reference status (uc_ref)
14
1
Calibration status (uc_cal)
Harmony Digital Input (Bailey Point Type 72)
This point type is supported only through Bailey semAPI version 2.0 and greater, which necessitates PI semAPI interface version 1.3 or greater. These points should be defined as type digital (D) or integer (I) in the PI system. If the Quality of the exception report is good, the interface extracts the value field of the report into the PI system. Otherwise, “Bad Input” is reported. Also, the rest of the status attribute can be accessed through the following extended attributes:
Code
Field length
Description
1
1
Quality (uc_q)
2
1
Alarm (uc_alm)
3
1
Status errors are inhibited (uc_sei)
4
1
Simulated (uc_sim)
5
1
Overridden value (uc_ovvl)
6
1
Value is suspect (uc_susp)
7
1
Propagated quality (uc_pq)
8
1
Configuration error exists (uc_cerr)
9
2
Channel condition (uc_range)
10
1
Readback status (uc_rbst)
11
1
Value (uc_val)
Harmony Digital Output (Bailey Point Type 73)
This point type is supported only through Bailey semAPI version 2.0 and greater, which necessitates PI semAPI interface version 1.3 or greater. These points should be defined as PI point type digital or integer. If the Quality of the exception report is good, the interface extracts the value field of the report into the PI system. Otherwise, Bad Output is reported. Also, the rest of the status attribute can be accessed through the following extended attributes:
The Bailey MCS Operator Console configuration contains much of the information needed for the PI Point database. The MCS can be configured from DBASE files on a personal computer. It is possible to create text files for PIDIFF or PIConfig from the DBASE files created for the MCS.
Start by entering DBASE and creating a new database with several of the same fields as the MCSTAG.dbf file. The following PI attributes can be extracted.
The field name in the MCS database is TagName. The MCS field is 14 characters long so some conversion may be necessary.
Descriptor
The field name in the MCS database is TagDescriptor. The MCS field is 32 characters long. The PI Descriptor is only 26 characters long.
EngUnits
The field name in the MCS database is EngineeringUnitDescriptor.
Note: The Engineering Unit strings must be configured in PI before configuring points that will use them.
Zero
The field name in the MCS database is ValueZero.
Span
The field name in the MCS database is Span.
DigStCode
The MCS database field ZeroState points to a string in the MCS state table.
PI2 Server: The ZeroState could be replaced with PI digital state code numbers.
Note: Most Infi90 digital points represent two-state devices, thus the DigNumber for these points in PI would be 1. The PI digital state table can be configured to have similar strings. These digital state strings must be configured before building PI points.
PI3 Server: PI3 requires that a digital state set be defined for each unique set of digital states. The digital state set must be defined before building PI points.
The field name in the MCS database is TagType. The MCS field has string descriptions of the type (e.g., ANALOG, RCM) rather than the number of the CIU point type. These can be converted with DBASE or a text editor.
One can configure performance points to monitor the amount of time in seconds that it takes an interface to complete a scan for a particular scan class. The closer the scan time is to 0 seconds, the better the performance. The scan time is recorded to millisecond resolution. Because this interface is not scan-based, performance points are not applicable.
I/O Rate Tag Configuration
An I/O Rate point can be configured to receive 10-minute averages of the total number of exceptions per minute that are sent to PI by the interface. An exception is a value that has passed the exception specifications for a given PI point. Since 10-minute averages are taken, the first average is not written to PI until 10 minutes after the interface has started. One I/O Rate tag can be configured for each copy of the interface that is in use.
