Interface to the pi system


Output Point Types (PI Data to Bailey)



Download 0.56 Mb.
Page8/14
Date31.07.2017
Size0.56 Mb.
#24976
1   ...   4   5   6   7   8   9   10   11   ...   14

Output Point Types (PI Data to Bailey)


Bailey Point Type

Description

Data Type

Extended Attributes

12

Analog Report

Analog

No

13

Digital Report

Digital

No

22

4-byte Analog Report

Analog

No

After the output tags are defined in PI, the data can be read from the ICI into any Bailey Node as a Analog point or a Digital Point. Use function code 26 to read point type 12 (Analog Report). Use function code 42 to read point type 13 (Digital Report). The address used in the function code 26 or 42 can be calculated from the Location2 parameter of the PI tag as described in the Location2 point attribute section.

Detailed Description of Bailey Point Types

Process Variable (Bailey Point Type 1)


This is the process variable of a control Station block (Bailey function code 80, 21, 22 or 23). The block address should be that of the Station block. The alarm attributes for the station can be accessed through the extended attributes of the station status. See point type 6.

Setpoint Read (Bailey Point Type 2)


This is the set point of a control Station block. See point type 1.

Control Output Read (Bailey Point Type 3)


This is the control output of a control Station block. See point type 1.

Ratio Index Read (Bailey Point Type 4)


This is the ratio index of a ratio control Station block. See point type 1.

Analog Read (Bailey Point Type 5)


This gets the value from an analog block (function code 30) on the Infi90 system.

The status of the analog value can be accessed through the following extended attributes:



Code

Field length

Description

1

1

Quality (q)

2

2

Limit Alarm (la)

3

2

Deviation Alarm (da)

4

1

Red Tagged Status (rt)

5

1

Point Tracking (pt)

6

1

Calibration (ccv)

Station Status (Bailey Point Type 6)


By default, the interface extracts only the fields indicating the Station mode and combines them into an eight-state status, even though the Station status contains other information.

A PI tag for the Station Status is normally defined as a digital point in the PI system.



  • Manual (unlocked)

  • Auto (unlocked)

  • Cascade (unlocked)

  • Digital Station Failure

  • Manual (locked)

  • Control Station Bypassed

  • Auto (locked)

  • Cascade (locked)

Station status is processed one field at a time according to the following order. If any field is set, the evaluation is stopped at that field and the digital state is set.
Processing Order for Station Status

IF (QUALITY field is set) THEN

Tag Digital State is BAD INPUT

ELSE IF (BYPASS field is set) THEN



Tag Digital State is Control Station Bypassed

ELSE IF (DIGITAL STATION FAILURE field is set) THEN



Tag Digital State is Digital Station Failure

ELSE IF (CASCADE RATIO field is set) THEN

IF (MANUAL INTERLOCK field is set) THEN

Tag Digital State is Cascade (locked)

ELSE


Tag Digital State is Cascade (unlocked)

ELSE IF (AUTO MODE field is set) THEN

IF (MANUAL INTERLOCK field is set) THEN

Tag Digital State is Auto (locked)

ELSE


Tag Digital State is Auto (unlocked)

ELSE IF (MANUAL INTERLOCK field is set) THEN



Tag Digital State is Manual (locked)

ELSE


Tag Digital State is Manual (unlocked)

Also, the following attributes of the Station Status may be accessed through the use of the extended attributes:



Code

Field length

Description

1

1

Quality (q)

2

2

Limit Alarm (la)

3

2

Deviation Alarm (da)

4

1

Red Tagged Status (rt)

5

1

Point Tracking (spt)

6

1

Station Bypass (byp)

7

1

Manual Interlock (mi)

8

1

Output Tracking (ot)

9

1

Digital Station Failure (dsf)

10

1

Computer OK (cok)

11

1

Computer Control Level (lev)

12

1

Cascade/Ratio Mode (crn)

13

1

Auto Mode (am)

Digital Read (Bailey Point Type 7)


These points should be defined as point type digital in the PI system. If the Quality of the exception report is good, the interface extracts the value field of the report into PI. Otherwise, Bad Input is reported.

Analog Report (Bailey Point Type 12)


This is one of the point types for writing from the PI system to Infi90. Infi90 real points are in the range -9.2E18 to 9.2E18. The output is set to BAD QUALITY and the value 0 is sent to Infi90 when the PI value is a digital state code (such as Shutdown or Over Range) and the SourceTag PI point type is a float or an integer.

If the SourceTag is defined as a digital point type, the interface will convert the absolute digital state to an offset of the digital start code of the point and send the offset as an analog value to the Infi90.


Digital Report (Bailey Point Type 13)


This is another point type for sending data from the PI system to Infi90. A source tag for the digital output can be either a real, integer, or digital point in the PI database. BAD QUALITY status is sent to Infi90 when the PI value is a digital state for real or integer source points. For a digital source point, a digital state out of the point’s range is considered BAD QUALITY.

For conversion of PI values to Infi90 values, a status of 1 is sent if the source PI value is not equal to 0. Otherwise 0 is sent. For PI source tag with point type D, the PI value is converted to a digital offset before sending to the Infi90.


Module Status (Bailey Point Type 14)


On the PI 3 server, use a digital set with 4 states to represent the module status. The four states of the Module status are:

  • Configure

  • Failed

  • Error

  • Execute

The block number (Location4) should be 0 for this point type.

RCM Read (Bailey Point Type 15)


An RCM (function code 62) has many attributes that could be of interest to the user. By default, the interface extracts only the output field into the PI value for PI tags with Location5 set to 15. To get the other attributes, use the extended descriptor keyword /BLY=x,y,etc. followed by the attributes code as described below:

Code

Field length

Description

1

1

Quality (q)

2

1

Alarm (alm)

3

1

Block tagged (tag)

4

1

Output value (ov)

5

1

Logic set input received (si)

6

1

Set permissive input received (sp)

7

1

Logic reset input received (ri)

8

1

Override (or)

9

1

Feedback (fb)

10

1

Set command received (sc)

11

1

Reset command received (rc)

RMSC Read (Bailey Point Type 19)


The conversion is the same as the other analog point types. (RMSC is function code 68.) The status of the analog value can be accessed through the following extended attributes:

Code

Field length

Description

1

1

Quality (q)

2

2

Limit Alarm (la)

3

2

Deviation Alarm (da)

4

1

Red Tagged Status (rt)

5

1

Point Tracking (pt)

6

1

Calibration (ccv)

4-byte Analog Read (Bailey Point Type 21)


It is handled like other analog point types except that the precision is higher (about 7 significant digits) and the range is larger (-3.4E38 to 3.4E38). The status of the analog value can be accessed through the following extended attributes:

Code

Field length

Description

1

1

Quality (q)

2

2

Limit Alarm (la)

3

2

Deviation Alarm (da)

4

1

Red Tagged Status (rt)

5

1

Point Tracking (pt)

6

1

Calibration (ccv)

4-byte Analog Report (Bailey Point Type 22)


This is one of the point types for sending data from the PI system to Infi90. 4-byte analog reports are processed in the same way as the 3-byte analog report (type 12) except that the 4-byte analog points have greater range and higher precision. They are in the range of -3.4E38 to 3.4E38.

DAANG (Bailey Point Type 29)


The data acquisition analog block has many attributes that may be of interest to the user. By default, the interface extracts the analog output value of the block into the PI value for PI tags with location 5 set to 29. To get the other attributes, use the extended descriptor keyword /BLY=x,y,etc. followed by the attributes code as described below:

Code

Field Length

Description

1

1

Quality (q)

2

1

high alarm (ha)

3

1

low alarm (la)

4

2

alarm level (al)

5

1

(x)

6

1

block tagged (tag1)

7

1

auto/manual (am1)

8

1

constant value 1 (constant_1)

9

1

block tagged (tag3)

10

1

hardware fault/bad input (fq3)

11

1

out of range (or)

12

1

limited (lim)

13

1

auto/manual (am3)

14

1

calculated value (cal3)

15

1

Quality override (qo)

16

1

off scan (ss)

17

1

high deviation alarm (I)

18

1

low deviation alarm (lda)

19

1

high rate (hr)

20

1

low rate (lr)

21

1

variable alarms (va)

22

1

alarm suppression indication (asi)

23

1

in re-alarm (ra)

24

1

permit input select (pis)

25

1

constraints enabled (ce)

26

1

calculated value (cal5)

27

1

hardware fault/bad input (fq5)

28

1

multilevel alarming (ma)

29

1

auto/manual (am5)

String (Bailey Point Type 30)


For the Windows version of the interface talking to a PI 3 server, the user has the option of putting the string data to string tags or into the Event Logger. If the PI tag is of point type String, then the string data from Bailey will be put into the string tag directly, else the string data will be put into the PI Event logger. If the PI tag is configured as string type, the Bailey string is put into the PI tag without the prefix of time stamp, tag name and quality flag like the data going into the Event Logger. If the Bailey string has bad quality, the digital string “bad input” will be written to the PI string tag.

Since Bailey will transmit exception reports (on a rate) for the ASCII data even if it doesn’t change, the interface provides a rudimentary filtering function. The interface will send the data to the Event Logger or PI string tags only if the ASCII string or status of the related PI tag have changed.


MSDD (Bailey Point Type 51)


The multi-state device driver (Bailey function code 129) has many attributes that could be of interest to the user. By default, the interface extracts only the output field into the PI value for PI tags with location 5 set to 51. To get the other attributes, use the extended descriptor keyword /BLY=x,y,etc. followed by the attributes code as described below:

Code

Field Length

Description

1

1

Quality (q)

2

1

Alarm (alm)

3

1

status override value (sor)

4

1

control override value (cor)

5

1

operation mode (m)

6

1

block tagged (tag)

7

1

command output value (co)

8

1

feedback state 1 (fb1)

9

1

feedback state 2 (fb2)

10

1

feedback state 3 (fb3)

11

1

feedback state 4 (fb4)

12

2

good state table (gs)

13

2

requested state table (rs)

DD (Bailey Point Type 52)


The device driver (Bailey function code 123) has many attributes that could be of interest to the user. By default, the interface extracts only the output field into the PI value for PI tags with location 5 set to 52. To get the other attributes, use the extended descriptor keyword /BLY=x,y,etc. followed by the attributes code as described below:

Code

Field Length

Description

1

1

Quality (q)

2

1

Alarm (alm)

3

1

block tagged (tag)

4

1

output value (ov)

5

1

feedback state 1 (fb1)

6

1

feedback state 2 (fb2)

7

1

feedback status (fs)

8

1

override value (or)

9

2

operation mode (mode)

RMC (Bailey Point Type 53)


The remote motor control block has many attributes that could be of interest to the user. By default, the interface extracts only the output field into the PI value for PI tags with location 5 set to 53. To get the other attributes, use the extended descriptor keyword /BLY=x,y,etc. followed by the attributes code as described below:

Code

Field Length

Description

1

1

Quality (q)

2

1

Alarm (alm)

3

1

feedback state 1 (fb1)

4

1

feedback state 2 (fb2)

5

1

block tagged (tag)

6

1

output value (ov)

7

1

bad start (bs)

8

1

fault (f)

9

1

start permissive state 1 (sp1)

10

1

start permissive state 2 (sp2)

11

4

error code for bad start (rmc_err)

DADIG (Bailey Point Type 54)


The data acquisition digital block has many attributes that could be of interest to the user. By default, the interface extracts only the output field into the PI value for PI tags with location 5 set to 54. To get the other attributes, use the extended descriptor keyword /BLY=x,y,etc. followed by the attributes code as described below:

Code

Field Length

Description

1

1

Quality (q)

2

1

Alarm (alm)

3

1

time in alarm re-alarm (field is toggled) (realm)

4

1

alarms suppressed (sup)

5

1

output suspect (os)

6

1

point off scan (nr)

7

1

block tagged (tag)

8

1

output value (ov)

9

1

extended status transition latched (lat)

10

1

Quality override (qo)

11

1

set permissive (sp)

12

1

primary input selected (pi)

13

1

alternate input selected (ai)

Text Selector (Bailey Point Type 60)


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:

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)


Download 0.56 Mb.

Share with your friends:
1   ...   4   5   6   7   8   9   10   11   ...   14



The database is protected by copyright ©ininet.org 2024
send message
    Main page
copyright laws
following trademarks