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: