Point Source (PI2 only)
Select a point source that has not already been used by the PI system or by any other interfaces or PI client applications. Set the location parameter limits as follows:
-
|
Location1
|
Location2
|
Location3
|
Location4
|
Location5
|
Minimum
|
0
|
-20000000
|
-20000000
|
1
|
-20000000
|
Maximum
|
3
|
20000000
|
20000000
|
200
|
20000000
|
PI digital states are discrete values represented by strings. These strings are organised differently for different versions of PI.
PI2 Digital State Table
Digital states are organised in PI2 in a digital state table. PI2 Digital tags use this table for its digital states. Each digital tag has a DIGSTARTCODE field and a DIGNUMBER field which it uses as a starting point and length (minus 1) in the digital state table for its “block” of digital states. For more information about PI2 digital tags and editing the digital state table, see the PI2 System manual, Part I, sections 3.2.2 and 3.3.4.
Two blocks of digital states must be defined in the digital state table specifically for the Yokogawa LS, LOOP, AS, and ALARM tag data types. These must be defined exactly as they appear in the tables labelled Loop Status and Alarm Status below. PI digital tags that store data for these Yokogawa data types must have their DIGSTARTCODE and DIGNUMBER assigned for one of these “blocks” of states.
PI2 SYSTEM DIGITAL STATES
The PI2 system reserves states between 193 and 320. This section is used for all tags, regardless of type to indicate the state of a tag at a particular time. For example, if the interface receives bad data from a Yokogawa point, it writes the system digital state bad input to PI instead of a value. The system digital state set has many unused states that can be used by the interface and other PI clients.
The interface uses several states that are not defined as part of the standard PI system digital state set. They are defined in the table below labelled Interface States. These states must be entered somewhere in the digital state table where there is at least nine unused states in a row. For the interface to be able to use these states, it must be given the state number of the first state no_block using the “/ds” argument in the Interface Startup File (see page 16 for more information).
PI3 Digital State Sets
Digital states are organised in PI3 in digital state sets. Each digital state set is a user-defined list of strings, enumerated from 1 to n to represent different values of discrete data. For more information about PI digital tags and editing digital state sets, see the PI Data Archive Manual for Windows NT and Unix manual.
A Yokogawa tag that contains discrete data can be stored in PI using a digital tag. A Digital tag associates discrete data with the digital state strings contained in a digital state set, as specified by the user. In addition to any digital state sets defined for use with discrete numerical data, two sets must be defined specifically for the Yokogawa LS, LOOP, AS, and ALARM tag data types. The sets must be defined as they appear in the tables labelled Loop Status and Alarm Status below. PI digital tags that store data for these Yokogawa data types must be assigned to one of these sets using the DigitalSet field.
PI3 SYSTEM DIGITAL STATE SET
Similar to digital state sets is the system digital state set. This set is used for all tags, regardless of type to indicate the state of a tag at a particular time. For example, if the interface receives bad data from a Yokogawa point, it writes the system digital state bad input to PI instead of a value. The system digital state set has many unused states that can be used by the interface and other PI clients.
The interface uses several states that are not defined as part of the standard PI system digital state set. They are defined in the table below labelled Interface States. These states must be entered somewhere in the system digital state set where there is at least nine unused states in a row. For the interface to be able to use these states, it must be given the state number of the first state no_block using the “/ds” argument in the Interface Startup File (see page 16 for more information). An unused state is identified by a label ?# where # is the number of the unused state; for example, if state 100 is unused it will have ?100 as its label.
-
LOOP STATUS
|
CENTUM V
|
OOP
|
BUM
|
BUA
|
MAN
|
MAN+
|
MAN-
|
MANC
|
AUT
|
AUT+
|
AUT-
|
AUTC
|
CBM
|
CBM+
|
CBM-
|
CBMC
|
CBA
|
CBA+
|
CBA-
|
CBAC
|
PRD
|
PRD+
|
PRD-
|
PRDC
|
CAS
|
CAS+
|
CAS-
|
CASC
|
SPC
|
SPC+
|
SPC-
|
SPCC
|
DDC
|
DDC+
|
DDC-
|
DDCC
|
CBC
|
CBC+
|
CBC-
|
CBCC
|
CMP
|
CENTUM XL MICRO XL
|
MAN
|
AUT
|
CAS
|
PRD
|
DDC
|
SPC
|
CBM
|
CBA
|
CBC
|
BUM
|
BUA
|
OOP
|
SEMI
|
LS01
|
LS02
|
LS03
|
LS04
|
LS05
|
CLP+
|
CLP-
|
CND
|
STOP
|
RUN
|
HOLD
|
SUB1
|
SUB2
|
SUB3
|
SUB4
|
SUB5
|
LOCK
|
OFF
|
|
-
ALARM STATUS
|
CENTUM V
|
CAL
|
IOP
|
HI
|
LO
|
+DV
|
-DV
|
VEL
|
MHI
|
MLO
|
NR
|
ON
|
OFF
|
|
|
|
|
CENTUM XL
MICRO XL
|
NR
|
+DV
|
-DV
|
HI
|
LO
|
BPRE
|
BEND
|
NPLS
|
VEL
|
IOP
|
HH
|
LL
|
MHI
|
MLO
|
CAL
|
OOP
|
ANS+
|
ANS-
|
TRIP
|
PERR
|
ALM
|
HDV
|
LDV
|
ALM1
|
ALM2
|
ALM3
|
ALM4
|
ALM5
|
ALM6
|
LEAD
|
PRE
|
END
|
AOF
|
INT
|
ERR
|
ANS1
|
ANS2
|
ANS3
|
ANS4
|
ANS5
|
ANS6
|
PAUS
|
|
|
|
|
|
|
-
Interface States
|
NO_BLOCK
|
BAD_BLOCK
|
R_OVER_DIG
|
BAD_DIGSTATE
|
INT_MINUS
|
CONN_CLOSED
|
INIT_ERROR
|
NOT_OUTPUT
|
OUTPUT_ERR
|
|
|
|
I/F_Stopped State
This is a digital state that indicates that the interface was not running at a particular time. This state can be entered into the PI2 digital state table or the PI3 system digital state set as any string but must match the /stopstat argument in the interface startup file. See the /stopstat heading of the Interface Startup File section on page 20 for more information.
Share with your friends: |