WDPF Record Types User Guide U0 - 0131
WDPF Record Types User Guide U0 - 0131
Summary of Changes
Section 1. Introduction
1-1. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1-1. Using Point Record Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1-2. Contents of This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1-3. Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Section 2. Background
2-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2-2. Process Point Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2-3. Analog Point Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2-3.1. Limit Checking Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2-3.2. Configuring Limit Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2-3.3. AI Alarm Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2-4. Expanded Analog Point Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2-5. Device Point Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
2-6. Digital Point Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
2-7. Packed Digital Point Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
2-8. Packed Group Point Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
2-9. Packed Group Alarm Point Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
2-9.1. Alarm Activation by System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
2-9.2. Alarm Function Operator Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2-10. Alert and Information Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2-11. Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2-12. Record Type Identifiers and Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
2-13. Valid Record Fields for 8- and 16-Character Systems . . . . . . . . . . . . . . . . . . . . . . 2-25
2-14. Example of Point Database Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
2-15. Point Latching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Glossary
Index
This revision of “Record Types User Guide” (U0-0131) has been updated to include
miscellaneous clarifications and corrections.
All sections now include page references beside the record type descriptions in the
tables. This was done to ease the comparison of information between the record
type and its corresponding description found later in the section.
1-1. Overview
Each item of data used within the WDPF® system is referred to as a point. Points
include field inputs and outputs, calculated values, and internal system information.
Each point is identified by a name and a unique System ID number.
A point record stores the set of information which defines the attributes of the point.
Point records are the primary vehicles for moving data within the WDPF system.
They are used within each drop, and to communicate over the Westnet II Data
Highway to other WDPF drops. There are thirteen types of point records which are
described in Section 3 through Section 8.
Point records are constructed of record fields. Some fields can be defined by the
user, while other fields store information the system needs to process the point
value. Examples of record fields are the point name, System ID, value, and status.
This document contains the information required to select the proper WDPF record
type, based on the point's application. This includes information on the record fields
included in each record type, the size of each type of point record, and the
applications where specific record types are used. Once the proper record type is
selected, the information contained in this document can be used to define the point
record field values (for example, when filling in the point attribute table in the MAC
Edit function (MEDIT), or when writing an INIT statement in the database source
code for drops such as the SIU or PCH).
• Section 3. Analog Point Record Types contains reference pages describing the
following record types and associated record fields:
• Section 4. Digital Point Record Types contains reference pages describing the
following record types and associated record fields:
• Section 5. Device Point Record Types contains reference pages describing the
following record types and associated record fields:
• Section 6. Packed Record (Point and Alarm) Types contains reference pages
describing the following record types and associated record fields:
— K Algorithm Records
— L Algorithm Records
— M Algorithm Records
— P Algorithm Records
Document
Number Document Name Description
M0-0003 Self-Test Diagnostics Describes the self-test diagnostics incorporated in the
WDPF system. It also lists and describes the current
drop fault codes with suggested user responses.
M0-0010 Westnet II Data Highway Provides an overview of Data Highway operation and
Description describes the Data Highway Controller hardware
(multi-card and single card versions).
M0-0053 Q-Line Installation Manual Discusses the installation of Q-Line I/O, including
field wiring and card addressing.
M0-8000 Highway Installation Manual Describes the format and parameters of the
(WEStation Equipped) CONFIG.SHC file.
U0-0001 Global Index for WDPF User Lists and describes the current WDPF user guides.
Documentation
Document
Number Document Name Description
U0-0106 Standard Control Algorithm Describes the standard graphic and text algorithms that
User’s Guide are available for use with the DPU, TCU, MAC-DS,
and MAC-4500 controllers.
U0-0136 MAC Utilities User’s Guide Describes procedures to enter points into the
Distributed Processing Unit database.
U0-1100 QLC User’s Guide Provides information on the Q-Line Serial Link
Controller (QLC) card, which is used to interface to
the DPU through the DIOB.
U0-2101 Clock Interface Unit User’s Guide Describes the Clock Interface Unit (CIU) and
(Chronolog) provides information on configuration and operation.
U0-8205 System Point Directory User’s Provides information on the System Point Directory
Guide file and the associated utilities.
U0-8211 WEStation Graphics Language Provides a reference to the WEStation graphics
Reference Manual source language rules and commands.
In addition to the documents listed above, this manual may refer to “applicable
vendor documentation”, which is defined on a project basis. These documents may
include:
Man pages (standard UNIX on-line documentation) are also available for operating
system functions and certain WDPF functions.
• Analog Point Records (AC, AI, AL, AM, and AX types) (Section 2-3).
• Digital Point Records (DC, DI, DL, DM, and DX types) (Section 2-6).
• Packed Group Alarm Point Records (BG, BN, and BX types) (Section 2-9).
• Analog Point Records: AI, AL, AC, AM, AX and AB record types.
• Digital Point Records: DI, DL, DC, DM, and DX record types.
• Packed Group Alarm Point Records: BG, BN, and BX record types.
In addition to carrying the basic value information, each analog record type also
contains additional information associated with the value. AX record types (which
contain the minimum information) are the smallest at 22 bytes and AB record types
(which contain the most information) are the largest at 128 bytes. As a general
recommendation, select the record type that uses the least amount of memory but
still meets the needs of the point application. This will help conserve database
memory.
Table 2-1shows the fundamental analog record type features. In Table 2-1, if a point
record type is marked with an X, then the record type has the ability to use that
feature. The record type can use any or all of the marked features.
Use AI or AB record types to define analog points whenever an analog value must
be read from the field by a DPU. These are the only record types that can read a
value from an analog field device. Consequently, AI or AB record types are the only
types that can convert field data into engineering units.
AL Record Type
An analog field output must be an AL record type. This is the only record type that
can write information to an analog output card. If the AL record is intended to write
to an output card, fields CD, HS, HW, and LS must be set by the user. Additionally,
the XAOUT or AOUT algorithm must be called by the DPU application and used
with the AL record. AL record types also include other desirable features (see Table
2-1). AL record types can be used to set any of these features for a point whether or
not it is intended for field output.
Use AC and AM record types to send calculated, non-limit-checked values over the
Data Highway to other drops and throughout the application program. (See Table
2-1 for differences between AC and AM Records.) For example, one of these record
types may be used in a DPU application to carry the output of one loop to the
beginning of another loop. Note that this output can only be a loop output. It cannot
be written to a field device.
AX Record Type
AX points are suited for storing analog values. Local and received points are normally
assigned this record type (for example, the MAC Edit function (MEDIT)
automatically assigns the AX record type to local and received points). The AX record
type is also used for internal points needed by algorithms and special functions.
(such as the SIU, VXI, or PCH) may use less overhead for AX points.
NOTE
All record types need some overhead memory. This overhead is
used by the drop to manipulate and store point information.
2For extended-tag (16-character point name) DPUs, the overhead for AX points is 48. The total size is 52 bytes.
AX points are either local or received points in the DPU.
Terms Definitions
Current value The actual value of the analog point at the time of alarm processing. This
value is stored in the point’s AV field.
Previous value Contains the value of the Analog Current Value (AV) field from the
previous loop. This value is stored in the point’s PV field.
High Limit User initialized value which is stored in the point's HL field. When the
current value of the point becomes greater than or equal to this value a
“high limit” alarm is reported.
Low Limit User initialized value which is stored in the point's LL field. When the
current value of the point becomes less than or equal to this value a “low
limit” alarm is reported.
Deadband User initialized value which is stored in the point's DB field. Used in
conjunction with other alarm limits to prevent the point from oscillating
into and out of alarm when the current value is hovering around the value
of a limit.
Status Word Contains status of point alarm, scan, and so forth. This value stored in
the point’s AS field.
Term Definition
High-High Limit User initialized value which is stored in the AB point's ZH field. When
the current value of the point becomes greater than or equal to this
value, a “high-high limit” alarm is reported.
Low-Low Limit User initialized value which is stored in the AB point's ZL field. When
the current value of the point becomes less than or equal to this value,
a “low-low limit” alarm is reported.
High Incremental Limit User initialized value which is stored in the AB point's ZI field. User in
conjunction with the high-high limit. When the value of the AB point
exceeds the high-high limit plus the high incremental limit, a “high
worse” alarm occurs.
Low Incremental Limit User initialized value which is stored in the AB point's ZM field. User
in conjunction with the low-low limit. When the value of the AB point
falls below the low-low limit minus the low incremental limit, a “low
worse” alarm occurs.
Checking Guidelines
• If sensor checking is selected, the point will go into alarm when the I/O scan
detects an input or output card failure. When sensor checking is enabled, the
conditions described below are reported as “sensor alarms”:
— For outputs, whenever data is written to the output point, the data is latched
on the output board and then read back as an ‘echo check’. A fault in the
digital portion of any output board (excluding the D/A converter in analog
boards) will be detected as a failure of this check.
— For inputs, the input boards contain on-board hardware fault detection
capability. A fault indication is contained in the hardware status that is read
from the board along with the analog value data. As a result, each time an
analog input is read, the hardware status of the input board for that particular
point is also checked. Note that for analog inputs, “sensor alarms” may also
be caused by external faults (such as a field transmitter or current source
failure). This type of sensor alarm can be distinguished from a board failure
by noting which points are affected (that is, if the points associated with a
specific board all go into sensor alarm, a board failure is indicated).
• If limit checking is selected, the point will go into alarm when the point value
exceeds the specified high or low limit (HL and LL fields). An incremental
alarm (worse or better) will be generated when the value crosses the boundaries
defined by the incremental alarm limit (IL field). For example, if the current
value (AV field) is greater than HL + IL, a “high worse” alarm will be generated.
Once the point has entered an alarm state, the deadband (DB field) is used to
prevent multiple alarms from occurring when the point's value is near an alarm
limit. For example, after a “high worse” alarm occurs at value HL + IL, the point's
value must go below HL + IL - DB before the alarm state is reduced to “high”.
LC values can be defined to select specific analog alarm options. If the value of LC
is 1, 2, 3, 4, 128, or 129, limit checking will be performed on the point. In this case,
the options specified by bits 3, 4, 5, or 6 will come into play. The table below
indicates the bits to set to enable/disable various combinations of low, high, and
incremental checking:
Bit
Bit Value Definition
3 0 Low alarm checking enabled.
3 1 Low alarm checking is disabled.
4 0 High alarm checking enabled.
4 1 High alarm checking is disabled.
5 0 Low incremental alarm checking enabled.
5 1 Low incremental alarm checking is disabled.
6 0 High incremental alarm checking enabled.
6 1 High incremental alarm checking is disabled.
If not initialized by the user, the value of LC defaults to 0 (no limit checking).
Example
A wide variety of options can be selected by using different values for LC. In
general, the set of limit checking capabilities to be enabled is specified by one of the
base values shown in this example. An additional value can be added to restrict the
capabilities which have been enabled.
For example, a base LC value of 3 specifies that limit checking is on. An add-on
value of 40 disables low and low incremental checking. Therefore, an LC setting of
43 will enable high limit and high incremental alarms, but not low limit and low
incremental alarms.
• Desired functionality:
— Fixed limits
— Limit and sensor cut-out
— No low limit checking
— No low incremental limit checking
Procedure
• Fixed limits
210
HI WRS Alarm
190 AV = 190 (HL + IL + IL)
HI WRS Alarm HI BET Alarm
170 AV = 170 (HL + IL) AV < 180 (HL + IL + IL - DB)
Return
Normal AV < 140 (HL - DB)
Operating
Range
Return
0 AV > 10 (LL +DB)
LO WRS Alarm
-60 AV = -40 (LL - IL -IL)
HL = 150 IL = 20
LL = 0 DB = 10
• If fixed limits are selected, the high limit and low limit values (HL and LL fields)
are initialized by the user (in the drop database). If the ALRMLIMV algorithm
is used, variable limits are assigned to the high limit and low limit values (HL
and LL fields).
• If inhibit limit alarm after cut-out is selected, no alarm will be generated when
the point is returned to alarm/limit checking (using the CUT algorithms or the
Operator Station functions), even if its value is high or low.
Once the point is returned to limit checking, if the value crosses a limit-checking
boundary, the expected alarm will occur. For example, if the value (AV field) is
above the high limit when limit checking is restored, no alarm will be generated.
However, if the point then moves above the incremental limit (HL + IL), a “high
worse” alarm will occur.
Note that if the point is already past an incremental limit, no alarm will be
generated until the next incremental limit is exceeded. For example, consider a
point with HL = 10, IL = 5, and DB = 1. For this point, the first “high worse”
limit is 15. If the point is returned to limit checking with AV = 17, no alarm will
be generated if AV goes to 12 (below the first “high worse” limit) and then to 18
(above the first “high worse” limit). However, if the value goes to 20 (the second
“high worse” limit, HL + IL + IL) an alarm will occur.
For specific values of the LC field used to implement these options, refer to the
Analog Points Record Fields reference pages.
AB Alarming Options
The alarm capability of the AI point record type had been expanded with the AB
point record type. The chart below shows a comparison between the capabilities of
the two record types:
Function AI AB
High Limit X X
High-High Limit X
High Incremental Limit X
Low Limit X X
Low-Low Limit X
Low Incremental Limit X
Set Incremental Limit (Applies to X
both High/Low)
User Defined Sensor Limits X
Adjustable Limits X X
The analog scan task in the DPU performs the processing of the AB point records.
When enabled, the scan task continuously updates the point value and performs
limit checking, sensor checking and alarm checking. The point's value is obtained
by reading a bit pattern for its associated card and converting it to engineering units.
This value is stored in the current value (AV) field of the point. The current value
(AV field) is compared with the user entered limits to determine if alarm conditions
have occurred.
Limit alarms will not be reported for points which are cut-out, limit check removed
or alarm check removed. Sensor alarms will not be reported for points which are
scan removed and alarm check removed.
• Alarm First Incremental only - the system will report HIGH, HIGH-
HIGH, and one HIGH WORSE alarm (as well as LOW, LOW-LOW, and
one LOW WORSE alarm).
• Alarm No Incrementals - with the low and high incremental limit fields
(ZM and ZI) set to 0, the system will report - HIGH, and HIGH HIGH
alarms only (as well as only LOW and LOW-LOW alarms).
Note
240
HI WRS AV = 220
220
HI WRS AV = 200 HI BET AV < 210
200
HI WRS AV = 180 HI BET AV < 190
180
HIHI AV = 160 HIHI AV < 170
160
HIGH AV = 150 HIGH AV < 150
150
RETURN AV < 140
In Figure 2-2, (of a time-varying voltage AV), values for the terms indicating
increasingly severe, maximum, and improving alarm states, are computed as follows.
HIGH AV = HL = 150
HIHI AV = ZH = 160
HI WRS AV = ZH + ZI = 180
HI WRS AV = ZH + ZI + ZI = 200
HI WRS AV = ZH + ZI + ZI + ZI = 220
HI BET AV < 210 (ZH + ZI + ZI + ZI -DB)
HI BET AV < 190 (ZH + ZI + ZI -DB)
HIHI AV < 170 (ZH + ZI - DB)
HIGH AV < 150 (ZH -DB)
RETURN AV < 140 (HL -DB)
If limit checking is selected, the point will go into alarm when the point value
exceeds the specified high or low limit (HL and LL fields). An incremental alarm
(worse or better) will be generated when the value crosses the boundaries defined
by the incremental alarm limit (ZI field). For example, if the current value (AV field)
is greater than ZH + ZI, a “high worse” alarm will be generated.
Once the point has entered an alarm state, the deadband (DB field) is used to prevent
multiple alarms from occurring when the point's value is near an alarm limit. For
example, after a “high worse” alarm occurs at value ZH + ZI, the point's value must
go below ZH + ZI - DB before the alarm state is reduced to “high”.
Similarly to the high alarm example, the graphic below indicates a sample time-
varying voltage wave-form. As the voltage goes down, the alarm sequence is: LOW
to LOLO to LO WRS to LO WRS to LO WRS. As the voltage goes up from the
lowest point, the alarm sequence is: LO BET to LO BET to LOLO to LOW to
Return, indicating the transition into a normal operating range.
RETURN AV > 10
0
LOW AV = 0 LOW AV > -10
-20
LOLO AV = -20 LOLO AV > -40
-50
LO WRS AV = -50 LO BET AV > -70
-80
LO WRS AV = -80 LO BET AV > -100
-110
LO WRS AV= -120
-140
The value for the various limits are computed as in the table below:
LOW AV = LL = 0
LOLO AV = ZL = -20
LO WRS AV = ZL -ZM = -50
LO WRS AV = ZL - ZM - ZM = -80
LO WRS AV = ZL -ZM -ZM -ZM= -120
LOBET AV > -100 (ZL -ZM -ZM -ZM+DB)
LOBET AV > -70 (ZL -ZM -ZM +DB)
LOLO AV > -40 (ZL -ZM +DB)
LOW AV AV > -10 (ZL +DB)
Return AV > 10 (LL + DB)
The record types are designed to meet the needs of different applications; each
record type has certain record fields associated with it. As noted previously, some
fields are user-initialized; others are set up automatically by the program which
generates the drop database.
Digital point record types are structured like the analog record types. In addition to
the basic discrete data, the digital record types contain other information and use
different amounts of memory. DX record types are the smallest at 20 bytes, and DI
record types are the largest at 90 bytes.
Table 2-5 shows the fundamental record type features for digital points. In this table,
if a point record type is marked with an X, then the record type has the ability to use
that feature. The record type can use any or all of the marked features.
The record types are designed to meet the needs of different applications. As with
analog point records, it is recommended that the user select the minimum size
record type which meets the point application requirements.
Table 2-5. Digital Point Record Type Features and Sizes
Point Record Types
(Number of Bytes)
DI DL DC DM DX1, 2
Feature 90 84 72 26 20
Calculated discrete value (required by all types). X X X X X
Value broadcast over the Data Highway X X X X
30-character English description or label X X X
6-character description to label set state X X X
6-character description to label reset state X X X
Ability to change state in monitoring mode X X
Internal status checking X X
Internal alarming X X
Ability to write to a digital output card X
Ability to read from a digital input card X
Ability to invert value read from digital input card X
1 The number of bytes shown for the DX point record type reflects the overhead required by the DPU. Other drops
(such as the SIU, VXI, or PCH) may use less overhead for DX points.
2 Forextended-tag (16-character point name) DPUs, the overhead for DX points is 48. The total size is 52 bytes.
DX points are either local or received points in the DPU.
DI Record Type
Use DI points whenever a digital value must be read from the field. This is the only
record type that reads a value from a digital device.
DL Record Type
A digital field output must be a DL record type, but a DL record type does not have
to be a field output. This is the only record type that can write information to a
digital output card. DL record types also include other desirable features (see Table
2-5). DL record types can be used to set any of these features for a point whether or
not it is intended for field output.
DX Record Type
DX points are suited for storing discrete values. Local and received points are
normally assigned this record type (for example, the MAC Edit function (MEDIT)
automatically assigns the DX record type to local and received points). The DX record
type is also used for internal points needed by algorithms and special functions.
Digital point records can be initialized to include status checking, as well as sensor
checking (for outputs) or power checking (for inputs). These options are selected
using the AR, LC, and PC record fields.
Several options are available for status checking digital points. These alternatives
are selected using the AR record field (DI and DL points only). The following
options may be selected:
• Generate alarm whenever point value does not equal its initial value.
• Generate alarm when point value changes to a specified state (that is, transition
from 0 to 1, or transition from 1 to 0). This selection will prevent an alarm from
occurring when the point is returned to alarm checking (after alarm checking
was removed or cut-out).
In addition to the status check alarm options, the user may implement a ‘power OK
check’ for digital inputs (DI records) by allocating one point on each input board as
the power-check bit. This selection is specified using the PC field. Note that the
selected point must be field wired to remain set (on). If a power failure occurs, a
“sensor alarm” will be reported for the points read from the board.
Sensor checking is also provided for digital output points (DL records). Whenever
data is written to the output point, the data is latched on the output board and then
read back as an ‘echo check’. A fault in the digital portion of any output board
(excluding the output driver stage of digital boards) will be detected as a failure of
this check.
Note
For information on the specific record field values used to implement the options
described above, refer to the AR, LC, and PC descriptions in the Digital Point
Record Fields reference pages in Section 4.
A packed digital contains either 32 separate digital values or two 16-bit register
(analog) values. There are two record types: PX (22 bytes or less, depending on
drop overhead requirements) and PB (32 bytes).
Packed group records are frequently used within ladder diagrams. When using the
default naming feature in the MAC Edit function (MEDIT), packed group points
can be automatically added to the DPU database (that is, when an appropriate point
name is entered, MEDIT automatically creates the point, assigns the GP record
type, and sets the hardware address offset (HW) record field).
Packed group records are also used extensively within graphic loops to store status
information (mode, tracking, state, and so forth) for graphic modulating algorithms.
When packed group points are used, individual bits may be forced to a specific state
by an operator command.
The group alarm point record type provides 16 digital point values which may be
scanned from input hardware or set by control ladder algorithms. With this alarm
type, it is possible to create groupings of alarms under a single control point. One
of the key features is that if any one (or more than one) in the group is in the alarm
mode, there is a single indication. Alarm status may be checked for individual drops
within the group or the group as a whole. Invalidity bits are also provided for each
of the 16 digital points to allow the Operator's/Alarm Console to indicate that the
data displayed is of questionable value.
The following are factors that can affect the alarm status (BG and BN record fields
used are shown in parentheses):
• Forcing (B3)
• Acknowledge alarm.
• Release alarm.
• Unrelease alarm.
Some details in reading or setting this status are included in the individual point
record types in the appropriate sections of this manual. As these points are added,
they are initially set to the Alert alarm configuration. To change the default status,
use the “ALARMCNF” algorithm. The choice between alarm categories is under
user control through Significance Logic. For full details on setting this status, see
the appropriate alarm documentation.
2-11. Quality
Analog, expanded analog, digital and device points may have one of four quality
values: “Good”, “Fair”, “Poor”, or “Bad”. Quality may be set by the user or by the
system, as with a DPU drop. The drop which originates a point is responsible for
assigning the quality.
• “Good” quality is typically assigned to all points which are functioning normally.
• A quality of “Fair” may be set through the MMI, as a default from an Entered
Value operation.
• “Poor” quality may be set by certain text algorithms that require multiple input.
If some of the input has “Bad” quality, the output of the text algorithm may have
poor quality.
• “Bad” quality is typically assigned to points which develop sensor failure, are
scan removed, or are receiving an input signal which is itself bad.
• Quality values may also be obtained by using the quality latch function or
QLATCH algorithm for analog, expanded analog, device, and digital points.
These quality terms may be displayed in a process diagram. Each quality may be
given a color (using DEF_QUAL) and shown as a character (with PROCESS_PT).
Setting of these parameters is detailed in "WEStation Graphics Language
Reference Manual" (U0-8211).
Other references within this document include the key words, Quality, Second
Status Word, and Latch.
Table 2-6 provides an alphabetical list of each process point record type and the
corresponding record type number. Table 2-7 provides a numerical list of each
record type number and the corresponding alphanumeric name.
Figure 2-4 shows example screens used to enter point record information. This
example shows the MEDIT database entry screens (referred to as the ‘Attribute
Table’) for an AI point
--------------------------------------------
When the ‘Add point’ function is selected from the database menu in MEDIT, enter
a point name (PN record field), record type (RT record field), and broadcast
frequency. When the Attribute Table is displayed, these entries are displayed (next
to the labels ‘PTNAME’, ‘REC_TYPE’, and ‘FREQUENCY’).
After these fields, the next entry field (labeled ‘IV’) is used to enter an initial value.
This value is used by the drop to initialize the Current Value field (AV, DS, or A2
field, depending on the record type) at start-up.
The remaining fields on the Attribute Table screen(s) correspond to the user-defined
record fields, as described in the reference pages for each record type.
An “N” in the Attribute description indicates that the field requires a numerical
value. The value may be a byte, integer, or real number, as defined for this record
field. A “C” indicates this field contains a character string (of the length defined for
this record field).
Table 2-11 (below) shows the configurations of Initial Value point types and their
operations during DPU start-up.
Table 2-11. Initial Value Configurations and Operations
Table 2-12 shows the configurations of Latched point types and their operations
during DPU start-up.
Table 2-12. Latched Configurations and Operations
Note
For each of the record types listed above, the record type overview provides a table
showing the record fields included in each record type. These tables include the
following information:
For each record type category, the record types overview is followed by reference
pages which provide more detail on the record fields. Each record type is shown first
in tabular form. Following the table is a listing of the various record fields. For each
record field, the record field identifier, byte offset, and type of data value are shown,
followed by a detailed description of the record field's use and possible values. For
many of the fields, examples of parameter setting are included.
Record Type
Record Data Byte
AI AL AC AM AX Field Type Offset Description
ID I 0 System Identification (page 3-5)
AS I 2 Analog Status Word (page 3-5)
AV R 4 Analog Current Value (page 3-6)
RT* B 8 Record Type Number (page 3-6)
FM* B 9 Printer Format — Decimal Point
(page 3-7)
SR B 10 Drop System Identification
(page 3-8)
LU B 11 Time of Alarm — Seconds
(page 3-8)
AW I 12 Second Status Word (page 3-8)
DG* I 14 Signal Diagram Index (page 3-10)
PN* C8 16 Point Name (page 3-10)
TB* I 24 Full Scale Value of Point
(page 3-11)
BB* I 26 Minimum Scale Value of Point
(page 3-11)
ED* C30 28 English Description (page 3-11)
EU* C6 58 Engineering Units of Current
Value (page 3-11)
EV* R 64 Operator-Entered Value
(page 3-12)
CD* I 68 Card Type Index (page 3-12)
HW** I 70 Offset of Hardware Address
(Bytes) (page 3-19)
AP* B 72 Alarm Priority (page 3-22)
Record Type
Record Data Byte
AI AL AC AM AX Field Type Offset Description
AY* C 73 Destination (page 3-23)
MM B 74 Time of Alarm — Month
(page 3-23)
NN B 75 Time of Alarm — Date (Day)
(page 3-23)
AH B 76 Time of Alarm — Hours
(page 3-23)
MN B 77 Time of Alarm — Minutes
(page 3-24)
CM B 78 Command Word (page 3-24)
LC* B 79 Include Limit Checking
(page 3-26)
IP I 80 Input Bit Pattern (page 3-28)
HL* R 82 High Alarm Limit (page 3-29)
LL* R 86 Low Alarm Limit (page 3-29)
IL* R 90 Incremental Alarm Limit
(page 3-29)
DB* R 94 High/Low/Incremental Limit
Deadband (page 3-30)
PV R 98 Previous Input Value (page 3-30)
HS* R 102 Sensor High Limit (V/A)/ Top
Scale Out (page 3-31)
LS* R 106 Sensor Low Limit (V/A)/ Bottom
Scale Out (page 3-32)
SN R 110 Sensor Calibration Value
(page 3-33)
CV* B 114 Conversion Type Index
(page 3-33)
CJ* B 115 Cold Junction Compensation
Segment Index (page 3-36)
CI* I 116 Conversion Coefficient Index
(page 3-37)
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
AS Byte Offset: 2
Data Type: Integer
Definition: Analog Status Word
• Updated by the DPU at run time.
Bit Definition
5 Alarm unacknowledged.
7 Point is in alarm.
8, 9 Quality:
0 0 Good
1 0 Fair
0 1 Poor
1 1 Bad
AV Byte Offset: 4
Data Type: Real
Definition: Analog Current Value
• AV field may be set by initializing the MAC Edit function (MEDIT) IV field.
• If IV field is not set (left blank), AV resets to the last value during run time
(latched) during reset or power-up.
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the record type name
(AI, AL, and so forth) entered by the user.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen. The numbers
corresponding to the analog record type names are shown below:
AX 60
AM 70
AC 75
AL 80
AI 90
FM Byte Offset: 9
Data Type: Byte
Definition: Display Format — Decimal Point
• Initialized by the user as a non-negative integer.
• Defines the type of display (standard, exponential, or technical) and the number
of decimal places to be shown for a Standard option.
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
LU Byte Offset: 11
Data Type: Byte
Definition: Time of Alarm — Seconds
• Initialized to zero.
• Identifies the second when the point last went into alarm.
• Updated at run time by the analog scan software when the point goes into alarm.
AW Byte Offset: 12
Data Type: Integer
Definition: Second Status Word
• Updated by control algorithms and analog scan software.
Bit Definition
0 Invalid hardware address or Card Type not Initialized — Set/reset in
analog inputs by the analog input scan software or by analog I/O
algorithms (for example, XAOUT, AIN, XMA2, and XML2).
1 Invalid bit pattern — Set/reset in analog inputs by the analog input
scan software.
OR
OR
Bit Definition
2 Bad hardware status — Set/reset in analog I/O algorithms (for
example, XAOUT, AIN, XMA2 and XML2)
3 QLI configuration error — Set/reset by algorithms operating with a
QLI interface.
4 Normalization error — Set/reset in analog inputs by the analog input
scan software or by analog I/O algorithms (for example, XAOUT,
AIN, XMA2 and XML2).
5 No RTDs for a CJC point — Set/reset in cold junction compensated
analog inputs only by the analog scan software.
6 Information Alarm Configuration (1=Information, 0=Alert). This bit
is set by the ALARMCNF algorithm.
7 Point’s alarm is released.
8,9 If Bits 8 and 9 are both zero, the Sensor Calibration Value field (SN,
byte offset 110) is updated with the engineering units value.
Bit Definition
15 Used in conjunction with the ALARMDLY algorithm. When this bit
is set, it indicates that the Alarm Delay feature is active (see also the
CM record field (byte offset 78) in this section).
NOTE
Bits 0, 1, 2, 3, 4 or 5 being set results in bad quality and a point sensor
alarm.
DG Byte Offset: 14
Data Type: Integer
Definition: Signal Diagram Index
• Initialized by the user.
• Defines the number of the diagram.
• For 7-level systems or below, the signal diagram can be displayed using the
Operator Station CRT 1 DISP DIAG or CRT 2 DISP DIAG key.
• For 8-level systems, the Signal Diagrams can be displayed using the Operator
WEStation point menu.
• For 6- and 7- level systems, valid entries are as follows:
— Main screen diagram numbers 1000 through 4999.
— Subscreen diagram numbers 0001 through 0999.
— Group numbers 5000 through 6999 (to display the diagram specified in the
group's diagram link).
• For 8-level systems, valid entries are 0-65535.
• Do not use diagram numbers that must be displayed with groups.
PN Byte Offset: 16
Data Type: String of 8 ASCII Characters
Definition: Point Name
• Initialized by the user.
• In extended tag DPUs, the ED field contains the 16-character point name. The PN
field only contains the character “@” followed by seven “blanks.”
TB Byte Offset: 24
Data Type: Integer
Definition: Full Scale Value of Point
• Initialized by the user.
BB Byte Offset: 26
Data Type: Integer
Definition: Minimum Scale Value of Point
• Initialized by the user.
ED Byte Offset: 28
Data Type: String of 30 ASCII Characters
Definition: English Description
• Initialized by the user (default = 30 blanks).
• Provides an expanded description (30 characters maximum) of the point for use
in displays and listings.
• In extended tag DPUs, the ED field contains the point name — not the English
description.
EU Byte Offset: 58
Data Type: String of 6 ASCII Characters
Definition: Engineering Units of Current Value
• Initialized by the user (default = 6 blanks).
EV Byte Offset: 64
Data Type: Real
Definition: Operator-Entered Value
• May be initialized by the user, but not required.
• The Operator-Entered Value function causes the value entered at the MMI to be
stored in the EV field. The DPU copies the value in the EV field to the AV field
when the Entered Value command is executed (see CM field, byte offset 78).
• This field is used by the MAC Monitor function (M_MON) or user interface for
the ‘Enter Value’ function.
CD Byte Offset: 68
Data Type: Integer
Definition: Card Type Index
• Initialized by the user.
• Used by the analog input scan software and analog output algorithms to scale
the value read from or written to an analog I/O card.
• Please note that a value of zero for the CD field of an AI point will cause the
point to go into sensor alarm.
• For more information on the individual card types, see “Q-Line Installation
Manual” (M0-0053).
Note
Group/ Input/
Index Name Revision Output Range Units
11 QAI/QAV G01 Input - 20 to + 20 mV
21 QAI G02 Input - 50 to + 50 mV
QAV G02 Input - 50 to + 50 mV
QAV G04 Input - 50 to + 50 mV
31 QAI G03 Input - 100 to + 100 mV
QAV G03 Input - 100 to + 100 mV
QAV G05 Input - 100 to + 100 mV
4 QAI G04 Input - 500 to + 500 mV
5 QAI G05 Input - 1 to + 1 V
6 QAI G06 Input - 10 to + 10 V
7 (or 9) QAI G07 Input 0 to + 20 mA
8 QAI G08 Input - 50 to + 50 mV
9 (or 7) QAI G07 Input 0 to + 20 mA
102 Undefined
11 QRT G01 Input 0 to + 10 mV
12 QRT G02 Input 0 to + 33.3 mV
13 (or 34) QAW G01 Input 0 to + 1 V
14 (or 35) QAW G02 Input 0 to + 5 V
15 QAW G03 Input 0 to + 10 V
Group/ Input/
Index Name Revision Output Range Units
16 QAW G04, G05 Input 0 to + 20 mA
17 QAH G01 Input - 10.235 to + 10.235 V
18 QAH G02 Input - 5.117 to + 5.117 V
19 QAH G03 Input 0 to + 10.237 V
20 QAH G04 Input 0 to + 5.119 V
21 QAO G01 Output 0 to + 20 mA
22 QAO G02 Output 0 to + 10 V
23 QAO G03 Output - 10 to + 10 V
24 QAO G04, G05 Output 0 to + 5 V
25 QAO G05 Output - 5 to + 5 V
26 QAO G06 Output - 10 to + 10 V
27 QAO G07 Output 0 to + 20 mA
28 QAO G08 Output - 10 to + 10 V
29 QAO G01 Output + 4 to + 20 mA
303 QAM G01 Output 0 to 10.2375 V
(4QAM1
or
4QAM3)
31 QAM G01 Output 0 to + 10 V
(4QAM5)
G02 Output + 4 to + 20 mA
(4QAM6)
32 QAW G06 Input 0 to + 50 mA
332 Undefined
34 (or 13) QAW G01 Input 0 to + 1 V
35 (or 14) QAW G02 Input 0 to + 5 V
Group/ Input/
Index Name Revision Output Range Units
36 QPA G01 Input Pulse Input + 48 V
Control Input + 48 V
G02 Input Pulse Input + 5 V
Control Input + 48 V
G03 Input Pulse Input + 5 V
Control Input + 5 V
G04 Input Pulse Input + 48 V
372 Undefined
38 PC N/A N/A -32768 through Signed
Interface + 32767 Integer
39 NL-740-H A Input 0 to + 5 V
40 NL-740-H B Input 0 to + 10 V
41 NL-740-H C Input + 1 to + 5 V
42 NL-740-H C Input + 4 to + 20 mA
43 NL-740-H C Input + 5 to + 50 mA
44 NL-740-H D Input 0 to + 1 V
45 NL-740-H E Input 0 to + 500 mV
46 NL-740-H F Input 0 to + 100 mV
47 NL-750-H A Output 0 to + 5 V
47 NL-750-H A Output + 4 to + 20 mA
48 NL-750-H B Output 0 to + 10 V
48 NL-750-H B Output + 4 to + 20 mA
49 NL-750-H C Output 0 to + 10 V
49 NL-750-H C Output + 10 to + 50 mA
502 Undefined
Group/ Input/
Index Name Revision Output Range Units
5110 QLI/QLJ G01 Input 0 to + 10 V
Output 0 to + 10 V
Output readback4 0 to + 10 V
5210 QLI/QLJ G02 Input 0 to + 5 V
Output 0 to + 10 V
Output readback4 0 to + 10 V
5310 QLI/QLJ G03 Input 0 to + 20 mA
Output 4 to + 20 mA
Output readback4 4 to + 20 mA
545 QAV G01 Input - 20 to + 20 mV
555 QAV G02 Input - 50 to + 50 mV
565 QAV G03 Input - 100 to + 100 mV
57 NL-742-H A Input 0 to + 5 V
58 NL-742-H B Input 0 to + 10 V
59 NL-742-H C Input - 5 to + 5 V
60 NL-742-H D Input - 10 to + 10 V
61 NL-742-H E Input + 1 to + 5 V
62 or 63 NL-751-H Output 0 to + 5 V
Output 0 to + 10 V
NL-752-H Output 0 to + 20 V
Output + 4 to + 20 V
Output 0 to + 50 V
Output +10 to + 50 V
64 or 65 NL-751 Output - 5 to + 5 V
64 or 65 NL-751 Output - 10 to + 10 V
Group/ Input/
Index Name Revision Output Range Units
666 QSC G01 Input 0 to + 2085 Counts
G02 Input 0 to + 8191 Counts
G01 Input 0 to + 18000 Counts
677 QLC G01 Input User-defined User-
defined
6811 QAX G01 Input - 20 to +20 mV
6911 QAX G02 Input - 50 to + 50 mV
7011 QAX G03 Input - 100 to + 100 mV
719, 12 QAX w/ G01 Input - 20 to + 20 mV
QAXT
729, 12 QAX w/ G02 Input - 50 to + 50 mV
QAXT
739, 12 QAX w/ G03 Input - 100 to + 100 mV
QAXT
7413 QAX G04 Input 0 to +1 V
7513 QAX G05 Input 0 to +5 V
7613 QAX G06 Input 0 to +10 V
77 QPA G01 Input Pulse Input + 48 V
Group/ Input/
Index Name Revision Output Range Units
82 QSR G01, G03 Channel: 3 - Output Coil
(Cont’d) Drive
83 Channel: 4 - Output Coil
Drive
84 G01 - G04 Channel: 1 - Input Feedback +/- 10 V
85 Channel: 2 - Input Feedback
86 G01, G03 Channel: 3 - Input Feedback
87 Channel: 4 - Input Feedback
88 QFD G01 Input -118.75 to 5000.625 nano A
1Use CD 1, 2, or 3 if cold junction compensation is performed by reading a QRT card corresponding to a user-entered
cabinet segment. For QAV cards which do not utilize the on-board cold junction compensation feature, use one of these
CD values. (Also see Note 5).
2Not assigned.
3Obsolete.
5Use CD 54, 55, or 56 if input is a thermocouple. When one of these CD values is entered, the QAV card's on-board cold
junction compensation feature is enabled (cold junction compensation is performed by the analog scan, which reads the
junction temperature from a QAV card's 7th channel). (Also see Note 1.)
Note that on-board cold junction compensation is provided by QAV cards at level 6QAV or higher. Because these cards
require 8 addresses, care must be taken when replacing an older QAV (which required only 6 addresses) to ensure that
the addresses are available (not assigned to another card). For detailed information, refr to “Q-Line Installation Manual”
(M0-0053).
6To convert to Hz Engineering Units, use the following (linear) conversion coefficients:
QSC-G01: Gain = 4, Bias = 0
QSC-G02: Gain = 1, Bias = 0
QSS-G01: Gain = 0.5, Bias = 0
Note
Sensor limits should be specified in counts (not Hz).
7Card type index 67 should be used for QLC group 1 input points which do not require Engineering units conversion.
Card type index 67 enables the analog scan limit checking, but does not use the analog scan routines to read the hardware
in the normal manner. Note that card type index 67 is not required for QLC output points. Also note that this setting is
not valid if the WDPF system is running the Control Builder, WESinfo, Database Generation System (DBGS), or Back
Translator.
For a group 2 QLC card, use the appropriate CD value for a QAW, QAO, QBI, and QBO card.
For additional information on the QLC card, refer to “QLC User's Guide” (U0-1100).
Group/ Input/
Index Name Revision Output Range Units
8Output current range is user configurable. Boards are built to supply + or - 40 mA output current, but they can be
configured to supply +/- 60 mA output current.
9When card types 71, 72, and 73 are used, the QAX is limited to handling 11 analog inputs. The 12th input is reserved
for sensing the on-board thermocouple temperature. See “Q-Line Installation Manual” (M0-0053) for more information
on the QAX card.
10To read the QLI/QLJ analog input/output signals, the point’s HW field should be xxx0H (where xxx is at least 001).
HW Byte Offset: 70
Data Type: Integer
Definition: Offset of Hardware Address (Bytes)
• Initialized by the user for points read from or written to the field I/O. (Field
I/O refers to a Distributed I/O Bus (DIOB) point card or to an NL-700 I/O point
card.)
• For a point read from or written to a DIOB point card, this field indicates the
offset (in bytes) from the beginning of the DIOB where the pertinent I/O register
resides. (The location of this register on the DIOB depends on the address
jumper selection on the front of the pertinent Q-Line card.)
• If an HW value of 0 (zero) is used as an offset for an AI point, the point will
indicate a sensor error.
• The calculation sequence for a Q-Line point card is as follows:
3. Determine the MBU offset (if any) from the hardware drawing. The MSQ,
MDX, MSX, or MBU 0 has an offset of zero. MBU 1 has an offset of 200H.
— Set CD = 0 and HW = 0.
Note
AP Byte Offset: 72
Data Type: Byte
Definition: Alarm Priority
• Initialized by the user.
• Indicates the high and low alarm priority of the point. The highest of the two
values is used for points in SENSOR alarm; the lowest of the two values is used
for points returned to NORMAL.
where:
0 Low
1
2
3 High
AY Byte Offset: 73
Data Type: 1ASCII Character
Definition: Destination
• Whenever the drop database is updated against the Point Directory, AY is
initialized to be the first character of the characteristics of the point. If a
characteristics statement does not exist for a point, it is initialized to the “wild
card” (-) character.
MM Byte Offset: 74
Data Type: Byte
Definition: Time of Alarm — Month
• Initialized to zero.
• Indicates the month when the point last went into alarm.
• Updated at run time by the analog scan software when the point goes into alarm.
NN Byte Offset: 75
Data Type: Byte
Definition: Time of Alarm — Date (Day)
• Initialized to zero.
• Indicates the date (day) when the point last went into alarm.
• Updated at run time by the analog scan software when the point goes into alarm.
AH Byte Offset: 76
Data Type: Byte
Definition: Time of Alarm — Hours
• Initialized to zero.
• Indicates the hour when the point last went into alarm.
• Updated at run time by the analog scan software when the point goes into alarm.
MN Byte Offset: 77
Data Type: Byte
Definition: Time of Alarm — Minutes
• Initialized to zero.
• Indicates the minute when the point last went into alarm.
• Valid range is 0 through 59.
• Updated at run time by the analog scan software when the point goes into alarm.
CM Byte Offset: 78
Data Type: Byte
Definition: Command Word
• Initialized to zero.
• Command requests are issued through the CM field (byte offset 78). These
requests may be originated by drops on the network. The DPU acts on the
commands and sets the status bits in the Analog Status Word field (AS, byte
offset 2). (This applies only to points that are scanned.)
Command Definition
1 Set scan on.
2 Set scan off, and set Sensor Calibration Value field (SN, byte offset 110) to
engineering units.
3 Set alarm checking on.
4 Set alarm checking off.
5 Set limit checking on.
6 Set limit checking off.
7 Set Sensor Calibration Value field (SN, byte offset 110) to uncompensated,
normalized value.
8 Set Sensor Calibration Value field (SN, byte offset 110) to compensated,
normalized value.
9 Read entered value.
10-13 Not assigned.
14 Acknowledge alarm.
Command Definition
15-21 Not assigned.
22 Set and latch quality as Good.
23 Set and latch quality as Fair.
24 Set and latch quality as Poor.
25 Set and latch quality as Bad.
26 Unlatch quality.
27 Set Questionable Status Bit.
28 Clear Questionable Status Bit.
29 Set Low Alarm Checking off
30 Set Low Alarm Checking on
31 Set High Alarm Checking off
32 Set High Alarm Checking on
33 Set Low Incremental Alarm Checking off
34 Set Low Incremental Alarm Checking on
35 Set High Incremental Alarm Checking off
36 Set High Incremental Alarm Checking on
37 Configure for Alert Alarms
38 Configure for Information Alarms
39 Release point from alarm
40 Unrelease point from alarm
41 Enable Alarm Cut-Out
42 Disable Alarm Cut-Out
43 Clear tag-level bits
44 Set tag level 1
45 Set tag level 2
46 Set tag level 3
Note
Commands higher than 22 are supported only for
software above level 7.1K.
LC Byte Offset: 79
Data Type: Byte
Definition: Include Limit Checking
• Initialized by the user per Table 3-6. If not initialized by the user, the value of
LC defaults to 0 (no limit checking).
High Incremental
Low Incremental
Inhibit Limit
Alarm after
High Alarm
by Cut-out1
Low Alarm
Checking
Checking
Checking
Checking
Checking
Checking
Checking
Checking
Inhibited
Interface
Cut-out
Custom
Type of
Sensor
Limits
Value
Limit
LC
• A wide variety of options can be selected by using different values for LC. In
general, the set of limit checking capabilities to be enabled is specified by one
of the base values shown in Table 3-6. An additional value can be added to
restrict the capabilities which have been enabled.
For example, a base LC value of 3 specifies that limit checking is on. An add-
on value of 40 disables low and low incremental checking. Therefore, an LC
setting of 43 will enable high limit and high incremental alarms, but not low
limit and low incremental alarms.
Table 3-7. Limit Checking Restriction Terms
• Other LC values can be defined to select specific analog alarm options. Shown
below are bit settings to enable/disable various combinations of low, high, and
incremental checking:
Bit
Bit Value Definition
3 0 Low alarm checking enabled.
3 1 Low alarm checking is disabled.
4 0 High alarm checking enabled.
4 1 High alarm checking is disabled.
5 0 Low incremental alarm checking enabled.
5 1 Low incremental alarm checking is disabled.
6 0 High incremental alarm checking enabled.
6 1 High incremental alarm checking is disabled.
Note that the add-on values are only valid if an appropriate base is selected to
enable limit checking. For example, if LC is 0 or 5, any limit checking specified
by the bits listed above will NOT be performed.
IP Byte Offset: 80
Data Type: Integer
Definition: Input Bit Pattern
• Initialized to zero.
• Updated on-line by the analog input scan software. A copy of the bit pattern
read from the I/O hardware (Q-Card or NL-700) is stored in the IP field.
HL Byte Offset: 82
Data Type: Real
Definition: High Alarm Limit
• Initialized by the user or set by the ALRMLIMV Algorithm.
• Used by the limit checking routine associated with the analog input scan software.
• When limit checking is performed, the value in the Analog Current Value field
(AV) is compared with the value in the HL field. If the AV value is greater than
the HL value, Bit 3 in the Analog Status Word (AS) is set. If the AV value is less
than the HL value minus the deadband (DB, byte offset 94), Bit 3 in AS is cleared.
LL Byte Offset: 86
Data Type: Real
Definition: Low Alarm Limit
• Initialized by the user or set by the ALRMLIMV algorithm.
• Used by the limit checking routine associated with the analog input scan software.
• When limit checking is performed, the value in the Analog Current Value field
(AV) is compared with the value in the LL field. If the AV value is less than the
LL value, Bit 2 in the Analog Status Word (AS) is set. If the AV value is greater
than the LL value plus the deadband (DB, byte offset 94), Bit 2 in AS is cleared.
IL Byte Offset: 90
Data Type: Real
Definition: Incremental Alarm Limit
• Initialized by the user.
• Used by the limit checking routine associated with the analog input scan software.
• In conjunction with the High and Low Limits (HL, byte offset 82, and LL, byte
offset 84), this field defines a set of breakpoints used for incremental alarming.
The high incremental alarm breakpoints are: HL + IL, HL + 2IL, HL + 3IL, and
so forth. The low incremental alarm breakpoints are LL - IL, LL - 2IL, LL - 3IL,
and so forth. When the current value (AV) crosses one of the breakpoint values,
Bits 0 and 1 in the Analog Status word (AS) are set to indicate that the alarm
condition is eit33her getting worse or getting better
AS field::
DB Byte Offset: 94
Data Type: Real
Definition: High/Low/Incremental Limit Deadband
• Initialized by the user.
• Used by the limit checking routines associated with the analog input scan routines.
• If the current value of a point is oscillating near an alarm limit, this term
prevents the point from going into and out of alarm.
PV Byte Offset: 98
Data Type: Real
Definition: Previous Input Value
• Initialized to zero.
• Updated at run time by the limit checking routines associated with the analog
input scan software.
• Used to determine when the current value has crossed an incremental limit
boundary:
where:
— Units are volts (V) or amperes (A), depending on the type of field input card
used. (See the CD record field description, byte offset 68.)
Note
— 700 Series I/O cards do not have an over-range signal. Therefore, set the
sensor range within the card operating range if sensor limit checking is
desired for 700 Series cards.
— HS is used by the limit checking routine associated with the analog input
scan software to verify that the input signal is in its valid range. If the signal
is out of range, Bit 3 in the Second Status Word (AW, byte offset 12) and
Bits 2 and 3 in the Analog Status Word (AS, byte offset 2) are set.
• For analog output points:
— HS and LS (byte offset 106) are used to scale the signal before it is written
to the field output card by the AOUT algorithm.
— Units are volts (V) or amperes (A), depending on the type of field input card
used.
Note
— LS is used by the analog input scan software to verify that the input signal
is in its valid range. If the signal is out of range, Bit 3 in the Second Status
Word (AW, byte offset 12), and Bits 2 and 3 in the Analog Status Word (AS,
byte offset 2) are set.
— LS and HS (byte offset 102) are used to scale the signal before it is written
to the field output card by the AOUT algorithm.
• Selects the type of equation to be used for the conversion to engineering units.
• Valid entries, conversion types and their corresponding equations are given in
Table 3-8.
Table 3-8. Conversion Type Index (CVField) Values
MEDIT
Entry
(COEF CV
Statement) Entry Conversion Type Equation
Not 0 Linear (Default) Y=X
Applicable
LI 1 Linear Y = C1X + C2
P5 2 Fifth Order Y = C1 + C2X + C3X2 + C4X3 + C5X4 + C6X5
Polynomial
SQ 3 Square Root Y = C1 [SQRT (X + C2)] + C3
(SQRT)
EX 4 Exponential Y = C1 [EXP (C2X)] + C3 = C1 [eC2X] + C3
(EXP)
SP 5 SQRT of Fifth Y = SQRT (Fifth Order Polynomial Y, as defined for
Order Polynomial Entry 2)
FG 6 Six-Segment Coefficient x, y pairs are:
Function (C1 , C8)
Generator (C2 , C9)
↓
(C7 , C14)
If x ≤ C 1 , y = C8
If x ≥ C7 , y = C14
If C1 ≤ x ≤ C8 , y = value of the y-coordinate for the
corresponding x-coordinate.
(See the following figure for an example of a six-
segment function generator.)
Not 7 Thermocouple (See CJ record field description, byte offset 115)
Applicable Input
The variables used in the equations are defined as follows:
X = Original input value, which is converted to Y (engineering units) by the specified type of conversion.
Y = Final, converted value of the analog input.
C1 - C14 = Conversion coefficients.
Figure 3-2 contains examples of four conversions: linear, fifth order polynomial,
square root, and exponential.
Y = C1 X + C2
[AT]
Y Top – Y Bot
(FT)
C 1 = --------------------------------- LT
X Top – X Bot
C14
C13
C12
C11
C10
C9
C8
C1 C2 C3 C4 C5 C6 C7
• Typically used with the QAV. Typically not used with the QAX.
• 0 indicates that the point is not to be cold-junction compensated using the QRT
segment.
• The cold-junction scan routine normally calculates compensation values for all
cabinet segments, and for the B, E, J, K, R, S and T thermocouple types, as
defined in the Conversion Coefficient Index field description (CI, byte offset
116). The analog input scan software uses the CI and CJ fields to obtain the
pertinent compensation value from the data generated by the cold-junction scan
software. Valid entries are shown in the following table:
• If the CV entry is 1 through 6, the CI entry is the index to the CC Record array
containing the coefficients required for the specified conversion.
CI
Index Temperature Range Thermocouple Type
1 800 through 2000˚ F B 70% Platinum + 30% Rhodium or
94% Platinum + 6% Rhodium
2 0 through 1800˚ F E Chromel/Constantan
3 - 140 through 1400˚ F J Iron/Constantan
4 0 through 2000˚ F K Chromel/Alumel
5 500 through 2000˚ F R Platinum + 13% Rhodium
6 750 through 2000˚ F S Platinum + 10% Rhodium
7 - 50 through 750˚ F T Copper/Constantan
21 427 through 1093˚ C B 70% Platinum + 30% Rhodium or
94% Platinum + 6% Rhodium
22 - 18 through 982˚ C E Chromel/Constantan
23 - 96 through 760˚ C J Iron/Constantan
24 - 18 through 1093˚ C K Chromel/Alumel
25 260 through 1093˚ C R Platinum + 13% Rhodium
26 399 through 1093˚ C S Platinum + 10% Rhodium
27 46 through 399˚ C T Copper/Constantan
Note
Caution
Record
Type
Record Data Byte
AB AX Field Type Offset Description
ID I 0 System Identification (page 3-42)
AS I 2 Analog Status Word (page 3-42)
AV R 4 Analog Current Value (page 3-43)
RT* B 8 Record Type Number (page 3-44)
FM* B 9 Printer Format — Decimal Point (page 3-44)
SR B 10 Drop System Identification (page 3-45)
LU B 11 Time of Alarm — Seconds (page 3-45)
AW I 12 Second Status Word (page 3-45)
DG* I 14 Signal Diagram Index (page 3-47)
PN* C8 16 Point Name (page 3-47)
Record
Type
Record Data Byte
AB AX Field Type Offset Description
TB* I 24 Full Scale Value of Point (page 3-48)
BB* I 26 Minimum Scale Value of Point (page 3-48)
ED* C30 28 English Description (page 3-48)
EU* C6 58 Engineering Units of Current Value (page 3-48)
EV* R 64 Operator-Entered Value (page 3-49)
CD* I 68 Card Type Index (page 3-49)
HW** I 70 Offset of Hardware Address (Bytes) (page 3-57)
AP* B 72 Alarm Priority (page 3-60)
AY* C 73 Destination (page 3-61)
MM B 74 Time of Alarm — Month (page 3-61)
NN B 75 Time of Alarm — Date (Day) (page 3-61)
AH B 76 Time of Alarm — Hours (page 3-61)
MN B 77 Time of Alarm — Minutes (page 3-62)
CM B 78 Command Word (page 3-62)
LC* B 79 Include Limit Checking (page 3-64)
IP I 80 Input Bit Pattern (page 3-67)
HL* R 82 High Alarm Limit (page 3-67)
LL* R 86 Low Alarm Limit (page 3-68)
ZI* R 90 High Alarm Incremental Limit (page 3-68)
DB* R 94 High/Low/Incremental Limit Deadband (page 3-69)
PV R 98 Previous Input Value (page 3-69)
ZH* R 102 High-High Alarm Limit (page 3-70)
ZL* R 106 Low-Low Alarm Limit (page 3-70)
SN R 110 Sensor Calibration Value (page 3-71)
CV* B 114 Conversion Type Index (page 3-71)
CJ* B 115 Cold Junction Compensation Seg. Index (page 3-74)
Record
Type
Record Data Byte
AB AX Field Type Offset Description
CI* B 116 Conversion Coefficient Index (page 3-75)
ZM* R 118 Low Alarm Incremental Limit (page 3-76)
CQ* I 122 Configuration Word (page 3-77)
* = User-initialized field.
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
AS Byte Offset: 2
Data Type: Integer
Definition: Analog Status Word
• Updated by the DPU at run time.
Bit Definition
3 2 1 0
0 0 0 0 No alarms
0 0 0 1 Low Low
0 0 1 0 High High
0 1 0 0 Low
1 0 0 0 High
0 1 0 1 Low Better
0 1 1 0 Low Worse
1 0 0 1 High Better
1 0 1 0 High Worse
1 1 x x Sensor
5 Alarm unacknowledged.
7 Point is in alarm.
8, 9 Quality:
0 0 Good
0 1 Fair
1 0 Poor
1 1 Bad
15 Point is not being updated (by the Data Highway) at receiving drop.
AV Byte Offset: 4
Data Type: Real
Definition: Analog Current Value
• AV field may be set by initializing the MAC Edit function (MEDIT) IV field.
• If IV field is not set (left blank), AV resets to the last value during run time
(latched) during reset or power-up.
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the record type name
(AI, AL, and so forth) entered by the user.
• May be used by the Operator Station or MAC Program Loader for type
checking on displayed information.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen. The number
corresponding to the expanded analog record type name is shown below:
AB 99
FM Byte Offset: 9
Data Type: Byte
Definition: Display Format — Decimal Point
• Initialized by the user as a value from 0 to 255.
• Defines the type of display (standard, exponential, or technical) and the number
of decimal places to be shown for a Standard option.
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
LU Byte Offset: 11
Data Type: Byte
Definition: Time of Alarm — Seconds
• Initialized to zero.
• Identifies the second when the point last went into alarm.
• Updated at run time by the analog scan software when the point goes into alarm.
AW Byte Offset: 12
Data Type: Integer
Definition: Second Status Word
• Updated by control algorithms and analog scan software.
Bit Definition
0 Invalid hardware address or Card Type not Initialized — Set/reset in
analog inputs by the analog input scan software or by analog I/O
algorithms (for example, XAOUT, AIN, XMA2, and XML2).
1 Invalid bit pattern — Set/reset in analog inputs by the analog input
scan software.
OR
OR
Bit Definition
2 Bad hardware status — Set/reset in analog I/O algorithms (for
example, XAOUT, AIN, XMA2 and XML2)
3 QLI configuration error — Set/reset by algorithms operating with a
QLI interface.
4 Normalization error — Set/reset in analog inputs by the analog input
scan software or by analog I/O algorithms (for example, XAOUT,
AIN, XMA2 and XML2).
5 No RTDs for a CJC point — Set/reset in cold junction compensated
analog inputs only by the analog scan software.
6 Information Alarm Configuration (1=Information, 0=Alert). This bit
is set by the ALARMCNF algorithm.
7 Point’s alarm is released.
8,9 If Bits 8 and 9 are both zero, the Sensor Calibration Value field (SN,
byte offset 110) is updated with the engineering units value.
Bit Definition
15 Used in conjunction with the ALARMDLY algorithm. When this bit
is set, it indicates that the Alarm Delay feature is active (see also the
CM record field (byte offset 78) in this section).
NOTE
Bits 0, 1, 2, 3, 4 or 5 being set results in bad quality and a point sensor
alarm.
DG Byte Offset: 14
Data Type: Integer
Definition: Signal Diagram Index
• Initialized by the user.
• For 7-level (below) systems, the signal diagram can be displayed using the
Operator Station CRT 1 DISP DIAG or CRT 2 DISP DIAG key.
• For 8-level systems, the Signal Diagrams can be displayed using the Operator
WEStation point menu.
— Group numbers 5000 through 6999 (to display the diagram specified in the
group's diagram link).
PN Byte Offset: 16
Data Type: String of 8 ASCII Characters
Definition: Point Name
• Initialized by the user.
• In extended tag DPUs, the ED field contains the 16-character point name. The
PN field only contains the character “@” followed by seven “blanks.”
TB Byte Offset: 24
Data Type: Integer
Definition: Full Scale Value of Point
• Initialized by the user.
• Used at the Operator Station to scale the value for bar chart displays.
BB Byte Offset: 26
Data Type: Integer
Definition: Minimum Scale Value of Point
• Initialized by the user.
• Used at the Operator Station to scale the value for bar chart displays.
ED Byte Offset: 28
Data Type: String of 30 ASCII Characters
Definition: English Description
• Initialized by the user (default = 30 blanks).
• Provides an expanded description (30 characters maximum) of the point for use
in Operator Station displays and listings.
• In extended tag DPUs, the ED field contains the point name — not the English
description.
EU Byte Offset: 58
Data Type: String of 6 ASCII Characters
Definition: Engineering Units of Current Value
• Initialized by the user (default = 6 blanks).
EV Byte Offset: 64
Data Type: Real
Definition: Operator-Entered Value
• May be initialized by the user, but not required.
• Operator Station or MAC Program Loader in the EV field. The DPU copies the
value in the EV field to the AV field when the Entered Value command is
executed (see CM field, byte offset 78).
• This field is used by the MAC Monitor function (M_MON) or Operator Station
for the ‘Enter Value’ function.
CD Byte Offset: 68
Data Type: Integer
Definition: Card Type Index
• Initialized by the user.
• Used by the analog input scan software and analog output algorithms to scale
the value read from or written to an analog I/O card.
Note
Bit Definition
8 Cut-out disabled
9, 10 Tag Level
11 Tag Acknowledge
12 Shut down QSR Card
13-15 Undefined
• The valid card types and their indexes are shown in Table 3-11. The range values
shown reflect the card definitions. A narrower range may be obtained by setting
the high and low sensor limits to appropriate values.
• Setting the CD field to “0” and the HW field to “0” allows the AB point to be
used as a calculated analog. It will be limit checked even though it is not tied to
hardware.
.
Table 3-11. Card Type Index (CD Field) Values
Group/ Input/
Index Name Revision Output Range Units
11 QAI/QAV G01 Input - 20 to + 20 mV
21 QAI G02 Input - 50 to + 50 mV
QAV G02 Input - 50 to + 50 mV
QAV G04 Input - 50 to + 50 mV
31 QAI G03 Input - 100 to + 100 mV
QAV G03 Input - 100 to + 100 mV
QAV G05 Input - 100 to + 100 mV
4 QAI G04 Input - 500 to + 500 mV
5 QAI G05 Input - 1 to + 1 V
6 QAI G06 Input - 10 to + 10 V
Group/ Input/
Index Name Revision Output Range Units
7 (or 9) QAI G07 Input 0 to + 20 mA
8 QAI G08 Input - 50 to + 50 mV
9 (or 7) QAI G07 Input 0 to + 20 mA
102 Undefined
11 QRT G01 Input 0 to + 10 mV
12 QRT G02 Input 0 to + 33.3 mV
13 (or 34) QAW G01 Input 0 to + 1 V
14 (or 35) QAW G02 Input 0 to + 5 V
15 QAW G03 Input 0 to + 10 V
16 QAW G04, G05 Input 0 to + 20 mA
17 QAH G01 Input - 10.235 to + 10.235 V
18 QAH G02 Input - 5.117 to + 5.117 V
19 QAH G03 Input 0 to + 10.237 V
20 QAH G04 Input 0 to + 5.119 V
21 QAO G01 Output 0 to + 20 mA
22 QAO G02 Output 0 to + 10 V
23 QAO G03 Output - 10 to + 10 V
24 QAO G04, G05 Output 0 to + 5 V
25 QAO G05 Output - 5 to + 5 V
26 QAO G06 Output - 10 to + 10 V
27 QAO G07 Output 0 to + 20 mA
28 QAO G08 Output - 10 to + 10 V
29 QAO G01 Output + 4 to + 20 mA
303 QAM G01 Output 0 to 10.2375 V
(4QAM1
or
4QAM3)
Group/ Input/
Index Name Revision Output Range Units
31 QAM G01 Output 0 to + 10 V
(4QAM5)
G02 Output + 4 to + 20 mA
(4QAM6)
32 QAW G06 Input 0 to + 50 mA
332 Undefined
34 (or 13) QAW G01 Input 0 to + 1 V
35 (or 14) QAW G02 Input 0 to + 5 V
36 QPA G01 Input Pulse Input + 48 V
Control Input + 48 V
G02 Input Pulse Input + 5 V
Control Input + 48 V
G03 Input Pulse Input + 5 V
Control Input + 5 V
G04 Input Pulse Input + 48 V
372 Undefined
38 PC N/A N/A -32768 through Signed
Interface + 32767 Integer
39 NL-740-H A Input 0 to + 5 V
40 NL-740-H B Input 0 to + 10 V
41 NL-740-H C Input + 1 to + 5 V
42 NL-740-H C Input + 4 to + 20 mA
43 NL-740-H C Input + 5 to + 50 mA
44 NL-740-H D Input 0 to + 1 V
45 NL-740-H E Input 0 to + 500 mV
46 NL-740-H F Input 0 to + 100 mV
47 NL-750-H A Output 0 to + 5 V
47 NL-750-H A Output + 4 to + 20 mA
Group/ Input/
Index Name Revision Output Range Units
48 NL-750-H B Output 0 to + 10 V
48 NL-750-H B Output + 4 to + 20 mA
49 NL-750-H C Output 0 to + 10 V
49 NL-750-H C Output + 10 to + 50 mA
502 Undefined
5110 QLI/QLJ G01 Input 0 to + 10 V
Output 0 to + 10 V
Output readback4 0 to + 10 V
5210 QLI/QLJ G02 Input 0 to + 5 V
Output 0 to + 10 V
Output readback4 0 to + 10 V
5310 QLI/QLJ G03 Input 0 to + 20 mA
Output 4 to + 20 mA
Output readback4 4 to + 20 mA
545 QAV G01 Input - 20 to + 20 mV
555 QAV G02 Input - 50 to + 50 mV
565 QAV G03 Input - 100 to + 100 mV
57 NL-742-H A Input 0 to + 5 V
58 NL-742-H B Input 0 to + 10 V
59 NL-742-H C Input - 5 to + 5 V
60 NL-742-H D Input - 10 to + 10 V
61 NL-742-H E Input + 1 to + 5 V
62 or 63 NL-751-H Output 0 to + 5 V
Output 0 to + 10 V
Group/ Input/
Index Name Revision Output Range Units
62 or 63 NL-752-H Output 0 to + 20 V
(Cont’d)
Output + 4 to + 20 V
Output 0 to + 50 V
Output +10 to + 50 V
64 or 65 NL-751 Output - 5 to + 5 V
64 or 65 NL-751 Output - 10 to + 10 V
666 QSC G01 Input 0 to + 2085 Counts
G02 Input 0 to + 8191 Counts
G01 Input 0 to + 18000 Counts
677 QLC G01 Input User-defined User-
defined
6811 QAX G01 Input - 20 to +20 mV
6911 QAX G02 Input - 50 to + 50 mV
7011 QAX G03 Input - 100 to + 100 mV
719, 12 QAX w/ G01 Input - 20 to + 20 mV
QAXT
729, 12 QAX w/ G02 Input - 50 to + 50 mV
QAXT
739, 12 QAX w/ G03 Input - 100 to + 100 mV
QAXT
7413 QAX G04 Input 0 to +1 V
7513 QAX G05 Input 0 to +5 V
7613 QAX G06 Input 0 to +10 V
Group/ Input/
Index Name Revision Output Range Units
77 QPA G01 Input Pulse Input + 48 V
2Not assigned.
3Obsolete.
Group/ Input/
Index Name Revision Output Range Units
5Use CD 54, 55, or 56 if input is a thermocouple. When one of these CD values is entered, the QAV card's on-board cold
junction compensation feature is enabled (cold junction compensation is performed by the analog scan, which reads the
junction temperature from a QAV card's 7th channel). (Also see Note 1.)
Note that on-board cold junction compensation is provided by QAV cards at level 6QAV or higher. Because these cards
require 8 addresses, care must be taken when replacing an older QAV (which required only 6 addresses) to ensure that
the addresses are available (not assigned to another card). For detailed information, refer to “Q-Line Installation
Manual” (M0-0053).
6To convert to Hz Engineering Units, use the following (linear) conversion coefficients:
QSC-G01: Gain = 4, Bias = 0
QSC-G02: Gain = 1, Bias = 0
QSS-G01: Gain = 0.5, Bias = 0
Note
Sensor limits should be specified in counts (not Hz).
7Card type index 67 should be used for QLC group 1 input points which do not require Engineering units conversion.
Card type index 67 enables the analog scan limit checking, but does not use the analog scan routines to read the hardware
in the normal manner. Note that card type index 67 is not required for QLC output points. Also note that this setting is
not valid if the WDPF system is running the Control Builder, WESinfo, Database Generation System (DBGS), or Back
Translator.
For a group 2 QLC card, use the appropriate CD value for a QAW, QAO, QBI, and QBO card.
For additional information on the QLC card, refer to “QLC User's Guide” (U0-1100).
8Output current range is user configurable. Boards are built to supply + or - 40 mA output current, but they can be
9When card types 71, 72, and 73 are used, the QAX is limited to handling 11 analog inputs. The 12th input is reserved
for sensing the on-board thermocouple temperature. See “Q-Line Installation Manual” (M0-0053) for more information
on the QAX card.
10To read the QLI/QLJ analog input/output signals, the point’s HW field should be xxx0H (where xxx is at least 001).
HW Byte Offset: 70
Data Type: Integer
Definition: Offset of Hardware Address (Bytes)
• Initialized by the user for points read from or written to the field I/O. (Field I/O
refers to a Distributed I/O Bus (DIOB) point card or to an NL-700 I/O point card.)
• For a point read from or written to a DIOB point card, this field indicates the
offset (in bytes) from the beginning of the DIOB where the pertinent I/O register
resides. (The location of this register on the DIOB depends on the address
jumper selection on the front of the pertinent Q-Line card.)
3. Determine the MBU offset (if any) from the hardware drawing. The MSQ,
MDX, MSX, or MBU 0 has an offset of zero. MBU 1 has an offset of 200H.
Note
AP Byte Offset: 72
Data Type: Byte
Definition: Alarm Priority
• Initialized by the user.
• Indicates the high and low alarm priority of the point. The highest of the two
values is used for points in SENSOR alarm; the lowest of the two values is used
for points returned to NORMAL. Valid entries in hexadecimal are as follows:
where:
0 Low
1
2
3 High
AY Byte Offset: 73
Data Type: 1ASCII Character
Definition: Destination
• Whenever the drop database is updated against the Point Directory, AY is
initialized to be the first character of the characteristics of the point. If a
characteristics statement does not exist for a point, it is initialized to the “wild
card” (-) character.
MM Byte Offset: 74
Data Type: Byte
Definition: Time of Alarm — Month
• Initialized to zero.
• Indicates the month when the point last went into alarm.
• Updated at run time by the analog scan software when the point goes into alarm.
NN Byte Offset: 75
Data Type: Byte
Definition: Time of Alarm — Date (Day)
• Initialized to zero.
• Indicates the date (day) when the point last went into alarm.
• Updated at run time by the analog scan software when the point goes into alarm.
AH Byte Offset: 76
Data Type: Byte
Definition: Time of Alarm — Hours
• Initialized to zero.
• Indicates the hour when the point last went into alarm.
• Updated at run time by the analog scan software when the point goes into alarm.
MN Byte Offset: 77
Data Type: Byte
Definition: Time of Alarm — Minutes
• Initialized to zero.
• Indicates the minute when the point last went into alarm.
• Updated at run time by the analog scan software when the point goes into alarm.
CM Byte Offset: 78
Data Type: Byte
Definition: Command Word
• Initialized to zero.
• Command requests are issued through the CM field (byte offset 78). These
requests may be originated by drops on the network. The DPU acts on the
commands and sets the status bits in the Analog Status Word field (AS, byte
offset 2). (This applies only to points that are scanned.)
Command Definition
1 Set scan on.
2 Set scan off, and set Sensor Calibration Value field (SN, byte
Command Definition
14 Acknowledge alarm.
15 - 21 Not Assigned.
22 Set and latch quality as Good.
23 Set and latch quality as Fair.
24 Set and latch quality as Poor.
25 Set and latch quality as Bad.
26 Unlatch quality.
27 Set Questionable Status Bit.
28 Clear Questionable Status Bit.
29 Set Low Alarm Checking off
30 Set Low Alarm Checking on
31 Set High Alarm Checking off
32 Set High Alarm Checking on
33 Set Low Incremental Alarm Checking off
34 Set Low Incremental Alarm Checking on
35 Set High Incremental Alarm Checking off
36 Set High Incremental Alarm Checking on
37 Configure for Alert Alarms
38 Configure for Information Alarms
39 Release point from alarm
40 Unrelease point from alarm
41 Enable Cut-Out
42 Disable Cut-out
43 Clear tag level bits
44 Set tag level 1
45 Set tag level 2
46 Set tag level 3
Note
LC Byte Offset: 79
Data Type: Byte
Definition: Include Limit Checking
• The LC field contains a value that describes both the types of alarm checks that
are applied to an analog point and status bits, which are used to enable/disable
the individual limit and sensor checks that may be performed.
• If not initialized by the user, the value of LC defaults to 0 (no limit checking).
• Set to 2 or 4 on-line by the DPU if the point is specified in an ALRMLIMV
algorithm.
High Incremental
Low Incremental
Inhibit Limit
Alarm after
High Alarm
by Cut-out1
Low Alarm
Checking
Checking
Checking
Checking
Checking
Checking
Checking
Checking
LC Value
Inhibited
Interface
Cut-out
Custom
Type of
Sensor
Limits
Limit
0 On Off N/A N/A N/A Off Off Off Off Off
1 On On Fixed Limit Off Off On On On On
2 On On Variable Limit Off Off On On On On
3 On On Fixed Limit Off Off On On On On
and
Sensor
4 On On Variable Limit Off Off On On On On
and
Sensor
5 Off Off N/A N/A N/A Off Off Off Off Off
6 On On Fixed Limit On Off On On On On
• A wide variety of options can be selected by using different values for LC. In
general, the set of limit checking capabilities to be enabled is specified by one
of the base values as shown in Table 3-15. An additional value can be added to
restrict the capabilities which have been enabled.
For example, a base LC value of 3 specifies that limit checking is on. An add-
on value of 40 disables low and low incremental checking. Therefore, an LC
setting of 43 will enable high limit and high incremental alarms, but not low
limit and low incremental alarms.
Table 3-15. Limit Checking Restriction Terms
• Other LC values can be defined to select specific analog alarm options. The
table below indicates the bits to set to enable/disable various combinations of
low, high, and incremental checking:
Bit
Bit Value Definition
3 0 Low alarm checking enabled.
3 1 Low alarm checking is disabled.
4 0 High alarm checking enabled.
4 1 High alarm checking is disabled.
5 0 Low incremental alarm checking enabled.
5 1 Low incremental alarm checking is disabled.
6 0 High incremental alarm checking enabled.
6 1 High incremental alarm checking is disabled.
Note that the add-on values are only valid if an appropriate base is selected to
enable limit checking. For example, if LC is 0 or 5, any limit checking specified
by the bits listed above will NOT be performed.
IP Byte Offset: 80
Data Type: Integer
Definition: Input Bit Pattern
• Initialized to zero.
• Updated on-line by the analog input scan software. A copy of the bit pattern
read from the I/O hardware (Q-Card or NL-700) is stored in the IP field.
HL Byte Offset: 82
Data Type: Real
Definition: High Alarm Limit
• Initialized by the user or set by the ALRMLIMV Algorithm.
• Used by the limit checking routine associated with the analog input scan software.
• When limit checking is performed, the value in the Analog Current Value field
(AV) is compared with the value in the HL field. If the AV value is greater than
the HL value, Bit 3 in the Analog Status Word (AS) is set. If the AV value is less
than the HL value minus the deadband (DB, byte offset 94), Bit 3 in AS is cleared.
LL Byte Offset: 86
Data Type: Real
Definition: Low Alarm Limit
• Initialized by the user or set by the ALRMLIMV algorithm.
• Used by the limit checking routine associated with the analog input scan software.
• When limit checking is performed, the value in the Analog Current Value field
(AV) is compared with the value in the LL field. If the AV value is less than the
LL value, Bit 2 in the Analog Status Word (AS) is set. If the AV value is greater
than the LL value plus the deadband (DB, byte offset 94), Bit 2 in AS is cleared.
ZI Byte Offset: 90
Data Type: Real
Definition: High Alarm Incremental Limit
• Initialized by the user.
• Specified in engineering units, not percent.
• Used by the limit checking routine associated with the analog input scan software.
• In conjunction with the High-High limit, (ZH, byte offset 102), this field defines
a set of breakpoints used for incremental alarming. The high incremental alarm
breakpoints are: ZH + ZI, ZH+ 2ZI, ZH + 3ZI, and so forth. When the current
value (AV) crosses one of the breakpoint values, Bits 0 and 1 in the Analog Status
word (AS) are set to indicate that the alarm condition is either getting worse or
getting better:
AS field:
DB Byte Offset: 94
Data Type: Real
Definition: High/Low/Incremental Limit Deadband
• Initialized by the user.
• Used by the limit checking routines associated with the analog input scan routines.
• Prevents the point from oscillating into and out of alarm when the current value
is hovering around the value of a limit.
PV Byte Offset: 98
Data Type: Real
Definition: Previous Input Value
• Initialized to zero.
• Updated at run time by the limit checking routines associated with the analog
input scan software.
• Used to determine when the current value has crossed an incremental limit
boundary:
where:
• Used by the limit checking routine associated with the analog input scan software.
• When limit checking is performed, the value in the Analog Current Value field
(AV) is compared with the value in the ZH field. If the AV value is greater than
the ZH value, Bit1 in the Analog Status Word (AS) is set, while bits 0, 2, and 3
are all cleared. If the AV value is less than the ZH value minus the deadband
(DB, byte offset 94), Bit 1 in AS is cleared.
• If the High-High alarm limit value (ZH) is less than the High Limit (HL), the
High-High limit is ignored.
• Used by the limit checking routine associated with the analog input scan software.
• When limit checking is performed, the value in the Analog Current Value field
(AV) is compared with the value in the ZL field. If the AV value is less than the
ZL value, Bit 0in the Analog Status Word (AS) is set, while bits 1, 2, and 3 are
all cleared. If the AV value is greater than the ZL value plus the deadband (DB,
byte offset 94), Bit 0 in AS is cleared.
• If the Low-Low alarm limit value (ZL) is greater than the Low Limit (LL), the
Low-Low limit is ignored.
• The current value of the analog point is always written to the SN field,
independent of the scan status of the point. Normally, the engineering units
value of the process point is stored. The DPU can be commanded (on-line) to
store the uncompensated or compensated (for thermocouples) normalized value
to the SN field. Normalized values are represented in either volts (V) or amperes
(A), depending on the card type.
• The Second Status Word (AW, byte offset 12) indicates the type of scan being
updated in the SN field.
• Selects the type of equation to be used for the conversion to engineering units.
• Valid entries, conversion types and their corresponding equations are given in
Table 3-16.
Table 3-16. Conversion Type Index (CV Field) Values
MEDIT Entry
(COEF CV Conversion
Statement) Entry Type Equation
Not Applicable 0 Linear (Default) Y=X
LI 1 Linear Y = C1X + C2
P5 2 Fifth Order Y = C1 + C2X + C3X2 + C4X3 + C5X4 + C6X5
Polynomial
SQ 3 Square Root Y = C1 [SQRT (X + C2)] + C3
(SQRT)
EX 4 Exponential Y = C1 [EXP (C2X)] + C3 = C1 [eC2X] + C3
(EXP)
SP 5 SQRT of Fifth Y = SQRT (Fifth Order Polynomial Y, as defined
Order for Entry 2)
Polynomial
FG 6 Six-Segment Coefficient (x, y) pairs are:
Function (C1, C8)
Generator (C2, C9)
↓
(C7, C14)
If x ≤ C1, y = C8
If x ≥ C7, y = C14
If C1 ≤ x ≤ C8, y = value of the y-coordinate for
the corresponding x-coordinate.
(See the following figure for an example of a six-
segment function generator.)
Not Applicable 7 Thermocouple (See CJ record field description, byte offset 115.)
Input
The variables used in the equations are defined as follows:
X=Original input value, which is converted to Y (engineering units) by the specified type of
conversion.
Y=Final, converted value of the analog input.
C1 - C14=Conversion coefficients.
Y = C1 X + C2
[AT]
Y Top – Y Bot
(FT)
C 1 = --------------------------------- LT
X Top – X Bot
C14
C13
C12
C11
C10
C9
C8
C1 C2 C3 C4 C5 C6 C7
• Typically used with the QAV. Typically not used with the QAX.
• 0 indicates that the point is not to be cold-junction compensated using the QRT
segment.
• The cold-junction scan routine normally calculates compensation values for all
cabinet segments, and for the B, E, J, K, R, S and T thermocouple types, as defined
in the Conversion Coefficient Index field description (CI, byte offset 116). The
analog input scan software uses the CI and CJ fields to obtain the pertinent
compensation value from the data generated by the cold-junction scan software.
• If the CV entry is 1 through 6, the CI entry is the index to the CC Record array
containing the coefficients required for the specified conversion.
CI
Index Temperature Range Thermocouple Type
1 800 through 2000˚ F B 70% Platinum + 30% Rhodium or
94% Platinum + 6% Rhodium
2 0 through 1800˚ F E Chromel/Constantan
3 - 140 through 1400˚ F J Iron/Constantan
4 0 through 2000˚ F K Chromel/Alumel
5 500 through 2000˚ F R Platinum + 13% Rhodium
6 750 through 2000˚ F S Platinum + 10% Rhodium
7 - 50 through 750˚ F T Copper/Constantan
21 427 through 1093˚ C B 70% Platinum + 30% Rhodium or
94% Platinum + 6% Rhodium
22 - 18 through 982˚ C E Chromel/Constantan
23 - 96 through 760˚ C J Iron/Constantan
24 - 18 through 1093˚ C K Chromel/Alumel
25 260 through 1093˚ C R Platinum + 13% Rhodium
26 399 through 1093˚ C S Platinum + 10% Rhodium
27 46 through 399˚ C T Copper/Constantan
Note
• Used by the limit checking routine associated with the analog input scan software.
• In conjunction with the Low-Low Limit (ZL, byte offset 106), this field defines
a set of breakpoints used for incremental alarming. The low incremental alarm
breakpoints are ZL - ZM, ZL - 2(ZM), ZL - 3(ZM), and so forth. When the
current value (AV) crosses one of the breakpoint values, Bits 0 and 1 in the
Analog Status word (AS) are set to indicate that the alarm condition is either
getting worse or getting better:
AS field:
• Used to define tolerances (in percent) above or below the fixed sensor limits,
which are defined according to card type.
• Bits 0 through 3 are used to set the tolerance for low sensor limits:
• Bits 4 through 7 are used to set the high sensor limit tolerances:
Note
where:
Note
For each of the record types listed above, the record type overview provides a table
showing the record fields included in each record type. These tables include the
following information:
For each record type category, the record types overview is followed by reference
pages which provide more detail on the record fields. Each record type is shown first
in tabular form. Following the table is a listing of the various record fields.For each
record field, the record field identifier, byte offset, and type of data value are shown,
followed by a detailed description of the record field's use and possible values. For
many of the fields, examples of parameter setting are included.
Record Type
Recod Data Byte
DI DL DC DM DX Field Type Offset Description
ID I 0 System Identification (page 4-4)
DS I 2 Digital Status Word (page 4-4)
A2 I 4 Not Assigned (page 4-6)
A3 I 6 Not Assigned (page 4-6)
RT* B 8 Record Type Number (page 4-6)
J4 B 9 Processor Originating Point
(page 4-6)
SR B 10 Drop System Identification
(page 4-7)
LU B 11 Time of Alarm - Seconds
(page 4-7)
DW I 12 Second Status Word (page 4-7)
DG* I 14 Signal Diagram Index (page 4-9)
PN* C8 16 Point Name (page 4-9)
B2 I 24 Internal Information (page 4-10)
B3 I 26 Internal Information (page 4-10)
ED* C30 28 English Description (page 4-10)
ST* C6 58 Set Description (page 4-11)
RS* C6 64 Reset Description (page 4-11)
HW** I 70 Offset of Hardware Address
(bytes)(page 4-11)
AP* B 72 Alarm Priority (page 4-12)
AY C 73 Destination (page 4-13)
MM B 74 Time of Alarm - Month
(page 4-13)
Record Type
Recod Data Byte
DI DL DC DM DX Field Type Offset Description
NN B 75 Time of Alarm - Date (Day)
(page 4-13)
AH B 76 Time of Alarm - Hours
(page 4-13)
MN B 77 Time of Alarm - Minutes
(page 4-14)
CM B 78 Command Word (page 4-14)
LC* B 79 Include Status Checking
(page 4-15)
AR* B 80 Type of Status Checking
(page 4-16)
BP* B 81 Bit Position on Hardware
(page 4-17)
RL* I 82 Relay Close Delay Time
(milliseconds) (page 4-17)
PC* I 84 Mask for Power-On Checking
(page 4-17)
EQ* I 86 Digital Configuration Word
(page 4-18)
* = User-initialized field.
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
DS Byte Offset: 2
Data Type: Integer
Definition: Digital Status Word
• Updated by the DPU at run time.
Bit Definition
0 Digital current value. DS field (bit 0) may be set by the user through the
IV field in the MAC Edit function (MEDIT) point record attribute table.
If IV field is not set (left blank), DS (bit 0) resets to the last value during
run time (latched) during reset or power-up.
1 Digital value from the previous scan for change of state alarming.
2, 3 Sensor Alarm
0 0 Not Assigned
0 1 Not Assigned
1 0 Not Assigned
1 1 Sensor Alarm
Bit Definition
4 Alert/Information Alarm
Bit 4 Description
0 Alert Alarm
1 Information Alarm
5 Alarm unacknowledged.
7 Point is in alarm.
8, 9 Quality
0 0 Good
0 1 Fair
1 0 Poor
1 1 Bad
15 Point is not being updated (by the Data Highway) at the receiving drop.
A2 Byte Offset: 4
Data Type: Integer
Definition: Not Assigned
A3 Byte Offset: 6
Data Type: Integer
Definition: Not Assigned
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the record type name
(DI, DL, and so forth) entered by the user.
• May be used for type checking on displayed information Identifies the type of
record by number. The record type number is commonly used in the Point
Directory listing and Point Details screen. The numbers corresponding to the
digital record type names are shown below:
DX 110
DM 115
DC 120
DL 130
DI 140
J4 Byte Offset: 9
Data Type: Byte
Definition: Processor Originating Point
• Not used by any standard drop. For custom drops which include multiple
processors (such as the Cell Controller), this field is set by the drop
configuration software.
• For standard drops, set this field to 0 to ensure compatibility with future releases.
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
LU Byte Offset: 11
Data Type: Byte
Definition: Time of Alarm — Seconds
• Initialized to zero.
• Indicates the second when the point last went into alarm.
• Updated at run time by the digital scan software when the point goes into alarm.
DW Byte Offset: 12
Data Type: Integer
Definition: Second Status Word
• Bits are defined as follows:
Bit Definition
OR
OR
Bit Definition
5 Current value of the point. Updated even when point is off scan.
8, 9 Not assigned.
11 Set quality Latch Bit. After the DPU receives a ‘Latch Quality’
command, the quality of the point is set to the requested value. The
‘latched quality’ bit of the point is also set (see also the CM record field
in this section).
12 Set bit for alarm condition indication. Used in conjunction with the
ALARMDLY algorithm. When this bit is set, it indicates that an alarm
condition exists.
13 Used for Sequence of Events Digitals. When this bit is set, it indicates
that the point’s sequence of events processing was suppressed due to:
OR
14 Set bit for Sequence of Events Digitals. When this bit is set, it indicates
that a disabled point (whose sequence of events processing was
suppressed by taking it off scan) has been re-enabled by putting it back
on scan. The DPU sends a message to its SOE drop to indicate this
change in status and then clears bit 14.
15 Set bit for alarm delay indication. Used in conjunction with the
ALARMDLY algorithm. When this bit is set, it indicates that the alarm
delay feature is active.
Note
DG Byte Offset: 14
Data Type: Integer
Definition: Signal Diagram Index
• Initialized by the user.
• For 7-level (below) systems, the signal diagram can be displayed using the
Operator Station CRT 1 DISP DIAG or CRT 2 DISP DIAG key.
• For 8-level systems, the Signal Diagrams can be displayed using the Operator
WEStation point menu.
— Group numbers 5000 through 6999 (to display the diagram specified in the
group's diagram link).
PN Byte Offset: 16
Data Type: String of 8 ASCII Characters
Definition: Point Name
• Initialized by the user.
• In extended tag DPUs, the ED field contains the 16-character point name. The
PN field only contains the character “@” followed by seven “blanks.”
B2 Byte Offset: 24
Data Type: Integer
Definition: Internal Information
• Bits are defined as follows:
Bit Definition
0, 1 Tag level.
2 Tag acknowledge.
3 Invert value.
B3 Byte Offset: 26
Data Type: Integer
Definition: Internal Information
• Bits are defined as follows:
Bit Definition
0-5 Undefined.
6, 7 GP Bit mapping.
8-15 Undefined.
ED Byte Offset: 28
Data Type: String of 30 ASCII Characters
Definition: English Description
• Initialized by the user (default = 30 blanks).
• Provides an expanded description (30 characters maximum) of the point for use
in displays and listings.
• In extended tag DPUs, the ED field contains the point name — not the English
description.
ST Byte Offset: 58
Data Type: String of 6 ASCII Characters
Definition: Set Description
• Initialized by the user (default = 6 blanks).
RS Byte Offset: 64
Data Type: String of 6 ASCII Characters
Definition: Reset Description
• Initialized by the user (default = 6 blanks).
HW Byte Offset: 70
Data Type: Integer
Definition: Offset of Hardware Address (Bytes)
• Initialized by the user for points read from or written to the field I/O. (Field
I/O refers to Q-Line point cards or NL-700 I/O point cards).
2. Determine the MBU offset (if any) from the hardware drawing. The MSQ,
MDX, MSX, or MBU 0 has an offset of zero. MBU 1 has an offset of 200H.
HW = 2 (ADD) + MBU
where:
HW = hardware offset
ADD = card address (in hexadecimal)
MBU = MBU offset
• For a point read or written to a distributed (remotely-located) 700 Series I/O
module (via an IOP card), the calculation is as follows:
AP Byte Offset: 72
Data Type: Byte
Definition: Alarm Priority
• Initialized by the user.
0 Low
1
2
3 High
AY Byte Offset: 73
Data Type: 1ASCII Character
Definition: Destination
• Whenever the drop database is updated against the Point Directory, AY is
initialized to be the first character of the characteristics of the point. If a
characteristics statement does not exist for a point, it is initialized to the “wild
card” (-) character.
MM Byte Offset: 74
Data Type: Byte
Definition: Time of Alarm— Month
• Initialized to zero.
• Indicates the month when the point last went into alarm.
• Updated at run time by the digital scan software when the point goes into alarm.
NN Byte Offset: 75
Data Type: Byte
Definition: Time of Alarm —Day (Date)
• Initialized to zero.
• Indicates the date (day) when the point last went into alarm.
• Updated at run time by the digital scan software when the point goes into alarm.
AH Byte Offset: 76
Data Type: Byte
Definition: Time of Alarm — Hours
• Initialized to zero.
• Indicates the hour of the day when the point last went into alarm.
• Updated at run time by the digital scan software when the point goes into alarm.
MN Byte Offset: 77
Data Type: Byte
Definition: Time of Alarm — Minutes
• Initialized to zero.
• Indicates the minute when the point last went into alarm.
• Updated at run time by the digital scan software when the point goes into alarm.
CM Byte Offset: 78
Data Type: Byte
Definition: Command Word
• Initialized to zero.
• Command requests are issued through the CM field (byte offset 78). These
requests may be originated by drops on the network. The DPU acts on the
commands and sets the status bits in the Digital Status Word field (DS, byte
offset 2). (This applies only to points that are scanned.)
Command Definition
1 Set scan on.
2 Set scan off.
3 Set alarm checking on.
4 Set alarm checking off.
5-9 Not assigned
10 Set value = 1.
11 Set value = 0.
12-13 Not assigned
14 Acknowledge alarm.
15-19 Not assigned
20 Removed from scan and enter value (force) = 1.
21 Removed from scan and enter value (force) = 0.
22 Set and latch quality as Good.
Command Definition
23 Set and latch quality as Fair.
24 Set and latch quality as Poor.
25 Set and latch quality as Bad.
26 Unlatch quality.
29 Set AR = 0
30 Set AR = 1
31 Set AR = 2
32 Set AR = 3
33 Set AR = 4
37 Configure for Alert alarm.
38 Configure for Information alarm.
39 Release point from alarm.
40 Un-release point from alarm.
41 Enable Alarm Cut-out.
42 Disable Alarm Cut-out.
43 Clear Tag-Level Bits.
44 Set Tag-Level 1.
45 Set Tag-Level 2.
46 Set Tag-Level 3.
47 Suppress SOE events.
48 Restore SOE events.
LC Byte Offset: 79
Data Type: Byte
Definition: Include Status Checking
• Initialized by the user per Table 4-3. If not initialized by the user, the value of
LC defaults to 0 (no status checking).
AR Byte Offset: 80
Data Type: Byte
Definition: Type of Status Checking
• Initialized by the user (defaults to zero if not initialized).
• Used if status checking is to be performed (LC field (byte offset 79) = 1).
3 = Transition Alarming: the point will go into alarm when the current
value makes a transition from 0 to 1.
4 = Transition Alarming: the point will go into alarm when the current
value makes a transition from 1 to 0.
Note
BP Byte Offset: 81
Data Type: Byte
Definition: Bit Position on Hardware
• Initialized by the user.
• Defines which bit (0 through 15) is to be read from the 16 bits on a digital (or
contact) input card.
• If the bit position is not between 0 and 15, an “Illegal Message” error is
displayed when the point is downloaded into the drop.
RL Byte Offset: 82
Data Type: Integer
Definition: Relay Close Delay Time (milliseconds)
• Initialized by the user.
PC Byte Offset: 84
Data Type: Integer
Definition: Mask for Power-On Checking
• Initialized by the user. (If PC is not initialized by the user, no power checking
on the contact input is performed by the software.)
• Entry is the decimal location of the power-checking bit plus 100 (decimal). If
power is lost at the power-checking bit, the quality of the input with this
definition will be set to “BAD” if its quality is not latched. At the same time, the
points last valid value is preserved and bit 1 of its DW field is set.
• To use the power-on check, one of the 16 bits on the card must be hard-wired to
the set state when power is applied.
• Power-checking off = 0
For example, to use bit 15 for the power-on check, set PC to 115.
EQ Byte Offset: 86
Data Type: Integer
Definition: Digital Configuration
• Bits are defined as follows:
Note
For each of the record types listed above, the record type overview provides a table
showing the record fields included in each record type. These tables include the
following information:
For each record type category, the record types overview is followed by reference
pages which provide more detail on the record fields. Each record type is shown first
in tabular form. Following the table is a listing of the various record fields.For each
record field, the record field identifier, byte offset, and type of data value are shown,
followed by a detailed description of the record field's use and possible values. For
many of the fields, examples of parameter setting are included.
Record Type
Record Data Byte
VC VX Field Type Offset Description
ID I 0 System Identification (page 5-5)
DS I 2 Device Status Word (page 5-5)
A2 I 4 Second Status Word (page 5-8)
A3 I 6 Third Status Word (page 5-10)
RT* B 8 Record Type Number (page 5-10)
RI B 9 Not Assigned (page 5-11)
SR B 10 Drop System Identification (page 5-11)
LU B 11 Time of Alarm — Seconds (page 5-11)
CN I 12 Interface to Keys/Buttons (page 5-11)
CP I 14 Copy of Last CN Control Word (page 5-13)
PN* C8 16 Point Name (page 5-13)
B2 I 24 Supervisory Command and Drop Number (page 5-13)
B3 I 26 Supervisory Unit and Recipe Number (page 5-13)
ED* C30 28 English Description (page 5-13)
ST C6 58 Set Description (page 5-13)
RS C6 64 Reset Description (page 5-14)
DK I 70 System Diagram (page 5-14)
AP B 72 Alarm Priority (page 5-14)
AY C 73 Destination (page 5-15)
MM B 74 Time of Alarm — Month (page 5-15)
NN B 75 Time of Alarm — Date (Day) (page 5-15)
AH B 76 Time of Alarm — Hours (page 5-16)
MN B 77 Time of Alarm — Minutes (page 5-16)
Record Type
Record Data Byte
VC VX Field Type Offset Description
CM B 78 Command Word (page 5-16)
LC B 79 Type of Alarming (page 5-17)
W0 I 80 DPU Command Word (page 5-18)
W1 I 82 Output 1 (OPEN/START/TRIP) Hardware Address
(page 5-19)
W2 I 84 Output 2 (CLOSE/STOP/RESET) Hardware Address
(page 5-20)
W3 I 86 Output 3 (STOP OPERATION/STOP TRAVEL)
Hardware Address (page 5-20)
W4 I 88 Input 1 (OPEN/START/TRIP) Hardware Address
(page 5-21)
W5 I 90 Input 2 (CLOSE/STOP/RESET) Hardware Address
(page 5-21)
W6 I 92 Not Assigned (page 5-21)
W7 I 94 Local Input Hardware Address (page 5-21)
Z1 B 96 Output 1 (OPEN/START/TRIP) Bit Position
(page 5-22)
Z2 B 97 Output 2 (CLOSE/STOP/RESET) Bit Position
(page 5-22)
Z3 B 98 Output 3 (STOP OPERATION/STOP TRAVEL) Bit
Position (page 5-22)
Z4 B 99 Input 1 (OPEN/START/TRIP) Bit Position
(page 5-22)
Z5 B 100 Input 2 (CLOSE/OFF/RESET) Bit Position
(page 5-23)
Z6 B 101 Not Assigned (page 5-23)
Z7 B 102 Local Input Bit Position (page 5-24)
TU B 103 Transition Time Units (page 5-25)
S0 B 104 Set Time-out (in No. of Transition Time Units)
(page 5-25)
Record Type
Record Data Byte
VC VX Field Type Offset Description
R0 B 105 Reset Time-out (in No. of Transition Time Units)
(page 5-25)
EM B 106 Mode Information (page 5-26)
PT B 107 Number of Loops to Pulse I/O (page 5-27)
F4 I 108 Number of Capturing Unit (page 5-27)
CW B 110 Number of Capturing Drop (page 5-27)
TR B 111 Number of Loops to Respond (page 5-27)
F6 I 112 Set/Reset Time-out in Number of Loops (OPEN/
START or CLOSE/STOP) (page 5-28)
F7 I 114 Time-out Counter (page 5-28)
F8 I 116 Previous Loop Information (page 5-28)
F9 I 118 I/O Configuration and Internal Information
(page 5-28)
CZ I 120 Pointer (Offset) to Capturing Drop's DU Record
(page 5-28)
G1 I 122 Pointer (Segment) to Capturing Drop's DU Record
(page 5-28)
* = User-initialized field.
2 For extended-tag (16-character point name) DPUs (extended points), the overhead for VX points is 44. The total
Note
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
DS Byte Offset: 2
Data Type: Integer
Definition: Device Status Word
• Initialized by the DPU at run time.
Bit Definition
0 Current state. The current state of the hardware is based on the feedback
signal(s). If the feedback signals give conflicting data (for example, one
feedback signal indicates that the device is closed or set and another
signal indicates that the device is open or reset), the last known state is
reported. If this condition occurs at power-up (restart), the state will be
set to closed (reset). When the device is scan removed, the last
commanded state will be reported.
1 Alarm state. If set, this bit indicates that the current state in Bit 0 is an
alarm condition.
3 Output sensor failure (output does not reflect the value written to it).
Note
Bits 2 and 3 indicate problems with the I/O as
follows:
Bit 3 Bit 2 Definition
0 0 No sensor failure.
0 1 Input sensor failure.
1 0 0utput sensor failure.
1 1 Input and output sensor failure.
Bit Definition
10 Not assigned.
11 Scan removed. If set, this bit indicates that the device is removed from
scan. When the device is removed from scan, the following occurs:
—I/O is read and the W0 record field (byte offset 80) is updated
accordingly.
12 Alarm released.
13 Alarm checking off is set by operator intervention. If this bit is set, the
device will operate normally; however, alarms will not be reported. The
device alarm checking may be turned off by using the appropriate function.
14 Toggle. This bit is set or reset when a new alarm condition occurs.
15 Point is not being updated (by the Data Highway) at receiving drop.
A2 Byte Offset: 4
Data Type: Integer
Definition: Second Status Word
• For the VC record type only, A2 field may be set by the user through the IV field
in the MAC Edit function (MEDIT) point record attribute table.
— If IV field is not set (left blank), A2 resets to the last value during run time
(latched) during reset or power-up.
• Each bit can be set individually by selecting either 0 (inactive) or 1 (active). The
bits are defined below.
Bit Description
0 Current state. The current state of the hardware is based on the feedback
signal(s). If the feedback signals give conflicting data (for example, one
feedback signal indicates that the device is closed or set and another
signal indicates that the device is open or reset), the last known state will
be reported. If this condition occurs at power-up (restart), the state will
be set to closed (reset). When the device is scan removed, the last
command will be reported.
1 In transition. This bit indicates that the DEVICE algorithm is currently
trying to change the state of its equipment. This bit is set true when the
device starts to execute a command. It is reset when the feedback signals
indicate that the operation is complete, or when the operation has failed
(that is, both feedbacks are not at a 0 or 1 state.)
2 Operation failed. This bit is set following any unsuccessful attempt to
change the state of the equipment. It remains set until another attempt is
made to change the state of the equipment. Failed operations are not
indicated if the device is off scan.
3 Tripped. This bit is set whenever the equipment changes state on its own
(that is, while it is not being operated on by the DEVICE algorithm).
This bit remains set until one of the following occurs:
— Trip Acknowledge (TRIP ACK) is selected by the operator, using one of
the following approaches:
• Press TRIP ACK on the Operator’s keyboard (6- and 7-level Operator
Station).
Bit Description
4 Stopped. This bit is set whenever the device is commanded to stop (via
the user or the DPU). It remains set until another attempt is made by the
device to change the state of the equipment.
5 Emergency close.
6 Emergency open.
Note
8 Local mode.
9 Manual mode.
10 Auto mode.
11 Supervisory mode.
Note
Bit Description
13 Failed to respond.
14 Locked out.
15 Tagged out.
A3 Byte Offset: 6
Data Type: Integer
Definition: Third Status Word
• Bits are defined as follows:
Bit Definition
2 Not assigned.
7 0 = Cut-out is enabled
1 = Cut-out is disabled
8, 9 Tag level.
10 Tag Acknowledge.
11 Quality Latch Bit. After the DPU receives ‘Latch Quality’ command it
sets the quality of the point to the requested value and sets the point’s
‘latched quality’ bit.
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the record type name
(VC or VX) entered by the user.
• May be used by the Operator Station or MAC Program Loader for type
checking on displayed information.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen.
• The numbers corresponding to the device record type names are shown below:
VX 230
VC 233
RI Byte Offset: 9
Data Type: Byte
Definition: Not Assigned
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
LU Byte Offset: 11
Data Type: Byte
Definition: Time of Alarm — Seconds
• Initialized to zero.
• Indicates the second when the point last went into alarm.
• Updated at run time by the device point scan software when the point goes into
alarm.
CN Byte Offset: 12
Data Type: Integer
Definition: Interface to Keys/Buttons
• Interfaces the control functions (keys or buttons) at the operator interface to the
algorithms specified in the graphics control statement. See the applicable
graphic language documentation for information on the control statements
available in a specific software level.
• The Control keys and Programmable keys activate bits as indicated below. The
P-key definitions are defined in the Device Maintenance subscreen (DEV
MAINT key on the Operator Station).
CP Byte Offset: 14
Data Type: Integer
Definition: Copy of Last CN Control Word
PN Byte Offset: 16
Data Type: String of 8 ASCII Characters
Definition: Point Name
• Initialized by the user.
• In extended-tag DPUs, the ED field contains the 16-character point name. The
PN field only contains the character “@” followed by seven “blanks.”
B2 Byte Offset: 24
Data Type: Integer
Definition: Supervisory Command and Drop Number
B3 Byte Offset: 26
Data Type: Integer
Definition: Supervisory Unit and Recipe Number
ED Byte Offset: 28
Data Type: String of 30 ASCII Characters
Definition: English Description
• Initialized by the user (default = 30 blanks).
• Provides an expanded description (30 characters maximum) of the point for use
in Operator Station displays and listings.
• In extended-tag DPUs, the ED field contains the point name — not the English
description.
ST Byte Offset: 58
Data Type: String of 6 ASCII Characters
Definition: Set Description
• Initialized by the user (default = 6 blanks).
RS Byte Offset: 64
Data Type: String of 6 ASCII Characters
Definition: Reset Description
• Initialized by the user (default = 6 blanks).
DK Byte Offset: 70
Data Type: Integer
Definition: Signal Diagram Index
• Initialized by the user.
• For 7-level (below) systems, the signal diagram can be displayed using the
Operator Station CRT 1 DISP DIAG or CRT 2 DISP DIAG key.
• For 8-level systems, the Signal Diagrams can be displayed using the Operator
WEStation point menu.
— Group numbers 5000 through 6999 (displays the diagram specified in the
group's diagram link).
AP Byte Offset: 72
Data Type: Byte
Definition: Alarm Priority
• Initialized by the user.
0 Low
1
2
3 High
AY Byte Offset: 73
Data Type: 1ASCII Character
Definition: Destination
• Whenever the drop database is updated against the Point Directory, AY is
initialized to be the first character of the characteristics of the point. If a
characteristics statement does not exist for a point, it is initialized to the “wild
card” (-) character.
• Used by the Operator Station function to display sets of related points that are
in alarm.
MM Byte Offset: 74
Data Type: Byte
Definition: Time of Alarm— Month
• Initialized to zero.
• Indicates the month when the point last went into alarm.
• Updated at run time by the device point scan software when the point goes
into alarm.
NN Byte Offset: 75
Data Type: Byte
Definition: Time of Alarm —Day (Date)
• Initialized to zero.
• Indicates the date (day) when the point last went into alarm.
• Updated at run time by the device point scan software when the point goes into
alarm.
AH Byte Offset: 76
Data Type: Byte
Definition: Time of Alarm — Hours
• Initialized to zero.
• Indicates the hour of the day when the point last went into alarm.
• Updated at run time by the device point scan software when the point goes into
alarm.
MN Byte Offset: 77
Data Type: Byte
Definition: Time of Alarm — Minutes
• Initialized to zero.
• Indicates the minute when the point last went into alarm.
• Updated at run time by the device point scan software when the point goes into
alarm.
CM Byte Offset: 78
Data Type: Byte
Definition: Command Word
• Initialized to zero.
• Command requests are issued through the CM field (byte offset 78). These
requests may be originated by drops on the network. The DPU acts on the
commands and sets the status bits in the Device Status Word field (DS, byte
offset 2). (This applies only to points that are scanned.)
Command Definition
1 Set scan on.
2 Set scan off.
3 Set alarm checking on.
4 Set alarm checking off.
14 Acknowledge alarm.
22 Latch Quality Good.
23 Latch Quality Fair.
24 Latch Quality Poor.
25 Latch Quality Bad.
26 Unlatch Quality.
37 Configure for Alert Alarming.
38 Configure for Information Alarming.
39 Alarm Release.
40 Alarm Unrelease.
41 Enable Alarm Cutout.
42 Disable Alarm Cutout.
43 Clear Tag-out Level.
44 Set Tag Level 1.
45 Set Tag Level 2.
46 Set Tag Level 3.
LC Byte Offset: 79
Data Type: Byte
Definition: Type of Alarming
• Initialized by the user.
W0 Byte Offset: 80
Data Type: Integer
Definition: DPU Command Word
• Initialized by the DPU at run time.
• Commands at the current software level are defined with the following bits:
Bit Definition
0 Emergency close.
1 Emergency open.
2 Auto CLOSE/STOP/RESET
3 Auto OPEN/START/TRIP
4 Auto stop (for devices with three outputs).
5 Auto permissive. This bit (if set) indicates that the auto commands (that is, OPEN,
CLOSE, and STOP) may be executed in Auto mode.
6 Current state of Input 1.
7 Current state of Input 2.
8 Current state of Input 3.
9 Value currently being written to Output 1.
10 Value currently being written to Output 2.
11 Value currently being written to Output 3.
12 Value of the device CLOSE/STOP/RESET permissive.
13 Value of the device OPEN/START/TRIP permissive.
14 Local Reject.
15 Spare.
Notes
1. Bits 0 through 4 indicate commands to be executed by the DEVICE algorithm.
2. Bits 6 through 11 indicate the current states of the device feedbacks and outputs. The current states
may be updated by the DEVICE algorithm after it reads the I/O, by other algorithms in the DPU, or
by a combination of these two.
3. Bits 12 and 13 are true on start-up, but may be updated by the DPU software.
W1 Byte Offset: 82
Data Type: Integer
Definition: Output 1 (OPEN/START/TRIP) Hardware Address
• Initialized by the user.
• If the W1 field is 0, the device point scan routines will not run. Bits 0 and 1
of the F9 field (byte offset 118) will both be set.
• If initialized to -1, the device point scan will write the OPEN/START/TRIP
output value to Bit 9 of the W0 field (byte offset 80). Software external to the
device point scan may then access this output value from the W0 field. (This
function is provided by the Device algorithm.)
W2 Byte Offset: 84
Data Type: Integer
Definition: Output 2 (CLOSE/STOP/RESET) Hardware Address
• Initialized by the user.
• If initialized to -1, the device point scan will write the CLOSE/STOP/RESET
output value to Bit 10 of the W0 field (byte offset 80). Software external to the
device point scan may then access this output value from the W0 field. (This
function is provided by the DEVICE algorithm.)
W3 Byte Offset: 86
Data Type: Integer
Definition: Output 3 (STOP OPERATION/STOP TRAVEL)
Hardware Address
• Initialized by the user.
• If initialized to -1, the device point scan will write the STOP OPERATION/
STOP TRAVEL value to Bit 12 of the W0 field (byte offset 80). Software
external to the device point scan may then access this output value from the W0
field. (This function is provided by the DEVICE algorithm.)
W4 Byte Offset: 88
Data Type: Integer
Definition: Input 1 (OPEN/START/TRIP) Hardware Address
• Initialized by the user.
• If initialized to -1, the device point scan will assume that Bit 6 in the W0 field
(byte offset 80) is the OPEN/START/TRIP feedback. Software external to the
device point scan must write the Input 1 value to Bit 6 of W0. (This function is
provided by the DEVICE algorithm.)
W5 Byte Offset: 90
Data Type: Integer
Definition: Input 2 (CLOSE/STOP/RESET) Hardware Address
• Initialized by the user.
• If initialized to -1, the device point scan will assume that Bit 7 of the W0 field
(byte offset 80) is the CLOSE/STOP/RESET feedback. Software external to the
device point scan must write the Input 2 value to Bit 7 of W0. (This function is
provided by the DEVICE algorithm.)
W6 Byte Offset: 92
Data Type: Integer
Definition: Auto Mode Request
• If initialized to -1, the text algorithm “device” will use its IN3 Input as the “Auto
Mode Request” signal.
W7 Byte Offset: 94
Data Type: Integer
Definition: Local Input Hardware Address
• Initialized by the user.
• Defines the input hardware address of the Reject to Local signal. When this
input is true, the device is put into Local mode. When this input goes false, the
device is forced to its default mode (as configured in the EM record field, byte
offset 106).
• The bit position for this address is specified in the Z7 field (byte offset 102).
Z1 Byte Offset: 96
Data Type: Byte
Definition: Output 1 (OPEN/START/TRIP) Bit Position
• Initialized by the user.
• If W1 (byte offset 82) is initialized to -1, this bit position does not have to be
entered.
Z2 Byte Offset: 97
Data Type: Byte
Definition: Output 2 (CLOSE/STOP/RESET) Bit Position
• Initialized by the user.
• If W2 (byte offset 84) is initialized to -1, this bit position does not have to be
entered.
Z3 Byte Offset: 98
Data Type: Byte
Definition: Output 3 (STOP OPERATION/STOP TRAVEL) Bit
Position
• Initialized by the user.
• If W3 (byte offset 86) is initialized to -1, this bit position does not have to be
entered.
Z4 Byte Offset: 99
Data Type: Byte
Definition: Input 1 (OPEN/START/TRIP) Bit Position
• Initialized by the user.
• If W4 (byte offset 88) is initialized to -1, this bit position does not have to be
entered.
• If W5 (byte offset 90) is initialized to -1, this position does not have to be
entered.
To implement this feature, use the LOCAL output digital (LOC) of the DEVICE
algorithm. Configure whether this digital is used to place the VC point into Local
mode or to go TRUE when the VC point is in Local mode.
• Defines the bit position for the Reject to Local signal (address specified in field
W7, byte offset 94).
• Used for set and reset time-out values (field S0, byte offset 104, and R0, byte
offset 105).
• Defines the time units for the set and reset time-outs as follows:
0 Tenths of a second
1 Seconds
2 Minutes
Notes
• Used only when Bit 1 of the EM field (byte offset 106) is set. For this mode
selection, the PT field determines the length of time that the output is set ON.
• Specified in number of loops (not seconds). If the loop time for the control area
is modified, this field may need to be adjusted.
• Used by the Batch Processing Unit (BPU) or Total Computation Unit (TCU) drop.
• Used by the Batch Processing Unit (BPU) or Total Computation Unit (TCU) drop.
• Within the specified time, the device feedbacks should show that the device is
in transition (that is, both feedbacks = 0) or should show the new command
state. Otherwise, a “failed to respond” condition will occur and the operation
will be halted.
For each of the record types listed above, the record type overview provides a table
showing the record fields included in each record type. These tables include the
following information:
For each record type category, the record types overview is followed by reference
pages which provide more detail on the record fields. Each record type is shown first
in tabular form. Following the table is a listing of the various record fields For each
record field, the record field identifier, byte offset, and type of data value are shown,
followed by a detailed description of the record field's use and possible values. For
many of the fields, examples of parameter setting are included.
Record Type
Record Data Byte
PB PX Field Type Offset Description
ID I 0 System Identification (page 6-3)
AS I 2 Packed Digital Status Word (page 6-3)
AV L 4 Packed Digital Value (page 6-4)
RT* B 8 Record Type Number (page 6-4)
FM* B 9 Printer Format - Decimal Point (page 6-4)
SR B 10 Drop System Identification (page 6-5)
L0* B 11 Initial Value Selection (page 6-5)
AW I 12 Not Assigned (page 6-5)
DG* I 14 Signal Diagram Index (page 6-6)
PN* C8 16 Point Name (page 6-6)
TB I 24 Not Assigned (page 6-6)
BB I 26 Not Assigned (page 6-6)
* = User-initialized field.
Record Type PB PX
Record Size 28 8
Overhead 1 4 14
Total Size 32 22
1The overhead requirement shown for the PX point record type reflects the amount required by the DPU. Other
drops (such as the SIU, VXI, or PCH) may use less overhead for PX points.
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
AS Byte Offset: 2
Data Type: Integer
Definition: Packed Digital Status Word
• Bits are defined as follows:
Bit Definition
0 - 14 Undefined
15 Point is not being updated (by the Data Highway) at receiving drop.
AV Byte Offset: 4
Data Type: 32-Bit Logical Field
Definition: Packed Digital Value
• Current values for 32-bit logical field.
• AV field initial values may be set by the user through the IV field in the MAC
Edit function (MEDIT) point record attribute table.
— If L0 field (byte offset 11) is set to 1, AV resets to the IV field values during
reset or power-up.
— If L0 field is zero or is not set (left blank), AV remains at the last value
during run time (latched) before the reset or power-up.
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the record type name
(PB or PX) entered by the user.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen. The numbers
corresponding to the packed digital record type names are shown below:
PX 205
PB 210
FM Byte Offset: 9
Data Type: Byte
Definition: Display Format — Decimal Point
• Initialized by the user as a non-negative integer.
• Defines the type of display (standard, exponential, or technical) and the number
of decimal places to be shown for a Standard option.
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
• Identifies the drop in which the point originates.
L0 Byte Offset: 11
Data Type: Byte
Definition: Initial Value Selection
• Initialized by the user.
• Used to determine the value of the AV field (byte offset 4) during a reset or
power-up.
0 = AV field remains at the last value during run-time before the reset or
power-up (that is, the value is latched).
AW Byte Offset: 12
Data Type: Integer
Definition: Not Assigned
DG Byte Offset: 14
Data Type: Integer
Definition: Signal Diagram Index
• Initialized by the user.
• For 7-level (below) systems, the signal diagram can be displayed using the
Operator Station CRT 1 DISP DIAG or CRT 2 DISP DIAG key.
• For 8-level systems, the Signal Diagrams can be displayed using the Operator
WEStation point menu.
— Group numbers 5000 through 6999 (to display the diagram specified in the
group's diagram link).
PN Byte Offset: 16
Data Type: String of 8 ASCII Characters
Definition: Point Name
• Initialized by the user.
TB Byte Offset: 24
Data Type: Integer
Definition: Not Assigned
BB Byte Offset: 26
Data Type: Integer
Definition: Not Assigned
Record Type
Record Data Byte
GP GX Field Type Offset Description
ID I 0 System Identification (page 6-8)
DS I 2 Packed Group Status Word (page 6-8)
A2 I 4 16 Digital Point Values (page 6-8)
A3 I 6 16 Force Indication Bits (page 6-9)
RT* B 8 Record Type Number (page 6-9)
J4 B 9 Not Assigned (page 6-10)
SR B 10 Drop System Identification (page 6-10)
L0* B 11 Initial Value Selection (page 6-10)
DW I 12 Second Status Word (page 6-10)
DG* I 14 Signal Diagram Index (page 6-11)
PN* C8 16 Point Name (page 6-11)
ZY I 24 Command Word (page 6-11)
B3* I 26 Offset of Hardware Address (Bytes) (page 6-13)
B4* I 28 Hardware Type (page 6-15)
B5 I 30 Operator-entered Value (page 6-16)
B6* I 32 Bits to Invert (page 6-16)
* = User-initialized field
Record Type GP GX
Record Size 34 8
Overhead 1 2 12
Total Size 36 20
1The overhead requirement shown for the GX point record type reflects the amount required by the DPU. Other
drops (such as the SIU, VXI, or PCH) may use less overhead for GX points.
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
• A unique number that identifies the point in the WDPF System.
• For a detailed description of the System ID field, refer to Appendix B.
DS Byte Offset: 2
Data Type: Integer
Definition: Packed Group Status Word
• Bits are defined as follows:
Bit Definition
0 - 14 Undefined
15 Point is not being updated (by the Data Highway) at receiving drop.
A2 Byte Offset: 4
Data Type: Integer
Definition: 16 Digital Point Values
• Current values for 16 digital points.
• A2 field initial values may be set by the user through the IV field in the MAC
Edit function (MEDIT) point record attribute table.
— If L0 field (byte offset 11) is set to 1, A2 resets to the IV field value during
reset or power-up.
— If L0 field is zero or is not set (left blank), A2 remains the last run time value
(latched) before the reset or power-up.
A3 Byte Offset: 6
Data Type: Integer
Definition: 16 Force Indication Bits
• Indicates which (if any) of the 16 digital values in the A2 field (byte offset 4)
are forced.
Note
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the record type name
(GP or GX) entered by the user.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen. The numbers
corresponding to the packed group record type names are shown below:
Record Type Record Type Number
GX 220
GP 225
J4 Byte Offset: 9
Data Type: Byte
Definition: Not Assigned
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
L0 Byte Offset: 11
Data Type: Byte
Definition: Initial Value Selection
• Initialized by the user.
• Used to determine the value of the A2 field (byte offset 4) during a reset or
power-up.
0 = A2 field remains at the last value during run-time before the reset or
power-up (that is, the value is latched).
DW Byte Offset: 12
Data Type: Integer
Definition: Second Status Word
Bit Definition
0, 1 Tag Level
2 Tag Acknowledge
3-15 Undefined
DG Byte Offset: 14
Data Type: Integer
Definition: Signal Diagram Index
• Initialized by the user.
• For 7-level (below) systems, the signal diagram can be displayed using the
Operator Station CRT 1 DISP DIAG or CRT 2 DISP DIAG key.
• For 8-level systems, the Signal Diagrams can be displayed using the Operator
WEStation point menu.
— Group numbers 5000 through 6999 (to display the diagram specified in the
group's diagram link).
PN Byte Offset: 16
Data Type: String of 8 ASCII Characters
Definition: Point Name
• Initialized by the user.
ZY Byte Offset: 24
Data Type: Integer
Definition: Command Word
• Initialized to zero.
• Commands contained in the low byte (eight least-significant bits) at the current
software level include:
Command Definition
Bit Definition
0-3 Bit number to be acted upon (forced or cleared) in the packed group
value.
4 State to set the specified bit when the Force command is specified.
For example, if the ZY field is equal to 0101H, the force condition will be cleared
from bit 1 in the packed group value:
0 1 0 1
Clear Force
Always 0
Bit 1
Not Used for Clear Force
Command
Similarly, if the ZY field is equal to 1F03H, bit 15 in the packed group value will be
forced and set to 1:
1 F 0 3
Force and
change value
Always 0
Bit 15
Set to 1
B3 Byte Offset: 26
Data Type: Integer
Definition: Offset of Hardware Address (Bytes)
• Initialized by the user for points read from or written to the field I/O. (Field
I/O refers to Q-Line point cards or NL-700 I/O point cards.)
• Specified in decimal, not hexadecimal.
• Defines the hardware address of the point.
• Used only when the Hardware Type field (B4, byte offset 28) is set to 1
through 4.
• The calculation sequence for a Q-Line point card is:
2. Determine the MBU offset (if any) from the hardware drawing. The MSQ,
MDX, MSX, or MBU 0 has an offset of zero (0). MBU 1 has an offset of
200H.
B3 = 2 (ADD) + MBU
where:
B3 = hardware offset
ADD = card address (in hexadecimal)
MBU = MBU offset
Note
B4 Byte Offset: 28
Data Type: Integer
Definition: Hardware Type
• Initialized by the user for points read from or written to field I/O cards. When
using the MAC Edit function (MEDIT) default naming feature, the correct value
is automatically assigned to the field, according to the following list.
— 1 indicates that a field contact input point is associated with this record.
The values of the bits in the A2 field (byte offset 4) will be set equal to the
bit values on the input card by the GPSCAN routine.
— 2 indicates that a field contact output point card is associated with this
record. The values of the bits in the A2 field will be written to the output card
by the GPSCAN routine.
— 3 indicates that a NL-700 register input card is associated with this record.
The values of the bits in the A2 field will be set equal to the bit values on the
input card by the GPSCAN routine.
B5 Byte Offset: 30
Data Type: Integer
Definition: Operator-Entered Value
• Used to store operator-entered value for Point Data Entry function. This field is
used only with command 6 (see ZY field, byte offset 24).
B6 Byte Offset: 32
Data Type: Integer
Definition: Bit Inversion Mask
• Initialized by the user.
• B6 allows the user to select which input bits should be inverted. Any bits in B6
which are set, will cause the corresponding bit to be inverted before the value is
written to the A2 field.
• Bit inversion applies only when a GP point is initialized with its B4 field equal
to “1” or “3” (discrete or register input).
Note
Caution
A feature of the BG and BN point records is the ability to have a text description for
each of the individual points which make up a grouped point. With the
bgdesc_translate program, users can create a binary formatted file which contains
these text descriptions. The information in the binary file, nominally called
bgdesc.bin, is used by Details and the Point Information display.
NAME0001
0 "Alarm Descript 0 for NAME0001"
1 "Alarm Descript 1 for NAME0001"
2 "Alarm Descript 2 for NAME0001"
3 "Alarm Descript 3 for NAME0001"
4 "Alarm Descript 4 for NAME0001"
5 "Alarm Descript 5 for NAME0001"
6 "Alarm Descript 6 for NAME0001"
7 "Alarm Descript 7 for NAME0001"
8 "Alarm Descript 8 for NAME0001"
9 "Alarm Descript 9 for NAME0001"
A "Alarm Descript A for NAME0001"
B "Alarm Descript B for NAME0001"
C "Alarm Descript C for NAME0001"
D "Alarm Descript D for NAME0001"
NAME0002
1 "Alarm Descript 1 for NAME0002"
2 "Alarm Descript 2 for NAME0002"
3 "Alarm Descript 3 for NAME0002"
4 "Alarm Descript 4 for NAME0002"
5 "Alarm Descript 5 for NAME0002"
NAMELAST
Sorted by SID
This command stream will sort the point descriptions by SID for all points
numbered from 0 (zero) to 1,000 (one thousand).
Environment
$WDPF_HOME
$WDPF_PDIR
where:
$WDPF_HOME is the mount point for the WDPF software.
$WDPF_PDIR is the name of the point directory.
The group alarm scan software allows the values of appropriately configured
BG and BN points to be written to output cards.
The outputs’ values are determined by control logic (ladders or text algorithms).
The output values will be written to the I/O regardless of invalidity or forcing. The
output addresses may be determined on a bit-by-bit basis by using a BG point.
An output BN point’s value bits may contain control ladder values or text algorithm
values.
A BG point’s value bits may contain any combination of hardware inputs, hardware
outputs, control ladder values and text algorithm values.
The user will have to define the following point fields in order to use a BN record
as an output:
Record Data
Field Value Definition
HW Integer Offset of output card hardware address
LC Byte Bit 3 set to 1: use BN as an output point.
Bit 3 set to 0: use BN as an input point.
M0 - N5 Integer Offset of hardware addresses — Bit 0 to Bit 15
—If HW field is zero (0000H):
— If this field is zero, then the corresponding
bit of A2 is unused.
— If this field is -1 (FFFFH), then the
corresponding bit of A2 will be set by a
control ladder.
Record Data
Field Value Definition
M0 - N5 Integer — If this field is -2 (FFFEH), then the
(Cont’d) (Cont’d) corresponding bit of A2 will be set by a text
algorithm.
— If this field is (0xxx xxxx xxxx xxxxB). then
the corresponding bit of A2 is read from an
input card determined from the hardware
address(0xxx xxxx xxxx xxxxB).
— If this field is (10xx xxxx xxxx xxxxB), then
the corresponding bit of A2 is read from a
control ladder and written to an output card
determined from the hardware address
(00xx xxxx xxxx xxxxB).
— If this field is (11xx xxxx xxxx xxxxB), then
the corresponding bit of A2 is read from a
text algorithm and written to an output card
determined from the hardware address
(00xx xxxx xxxx xxxxB).
N6 Integer Hardware Bit Position — Bits 0 - 3
N6 bits 0 to 3 = A2 bit 0
N6 bits 4 to 7 = A2 bit 1
N6 bits 8 to 11 = A2 bit 2
N6 bits 12 to 15 = A2 bit 3
N7 Integer Hardware Bit Position — Bits 4 - 7
N7 bits 0 to 3 = A2 bit 4
N7 bits 4 to 7 = A2 bit 5
N7 bits 8 to 11 = A2 bit 6
N7 bits 12 to 15 = A2 bit 7
N8 Integer Hardware Bit Position — Bits 8 - 11
N8 bits 0 to 3 = A2 bit 8
N8 bits 4 to 7 = A2 bit 9
N8 bits 8 to 11 = A2 bit 10
N8 bits 12 to 15 = A2 bit 11
N9 Integer Hardware Bit Position — Bits 12 15
N9 bits 0 to 3 = A2 bit 12
N9 bits 4 to 7 = A2 bit 13
N9 bits 8 to 11 = A2 bit 14
N9 bits 12 to 15 = A2 bit 15
The BG/BN scan software will check the HW, LC, and M0 through N5 fields each
loop. If initialized as an output, the value of the corresponding bit(s) will be written
to the corresponding I/O card address and bit. The card is written to at all times. If
any bits are forced or invalid, their values are still written to the I/O card.
The scan will report one of two output write errors: read back failure or remote I/O
error.
The read back test is performed immediately after the bit value is written to the I/O
card. The card value is read back and compared to the bit value written. If they do
not match, Fault code 128, Fault ID 62 is reported. See “Self-Test Diagnostics”
(M0-0003) for more information on fault codes.
The remote I/O error can only occur in systems with remote Q-Line I/O. In this type
of system, after each I/0 operation, the MRC (Multibus Remote Controller) card
provides a status indicating the validity of the operation. If the BG output is invalid,
it will report Fault code 128, Fault ID 63. See “Self-Test Diagnostics” (M0-0003)
for more information on fault codes.
Indicates that all 16 bit values are to be read from the digital input card at
address 100H.
2. BG point with HW = -1
3. BG point with HW = -2
HW = 0
M0 = 100H
M1 = -1
M2 = -2
M3 = 8100H
M4 = C300H
M5 = 0
N5 = 0
N6 = 200FH
N7 = 0008H
N8 = 0
N9 = 0
Bit 0 will be read from bit 15 of the digital input card at address 100H.
Bit 3 will be set by a control ladder and written to bit 2 of the digital output
card at address 100H.
Bit 4 will be set by a text algorithm and written to bit 8 of the digital output
card at address 300H.
* = User-initialized field.
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
DS Byte Offset: 2
Data Type: Integer
Definition: Digital Status Word
• Initialized by the DPU at run time.
Bit Definition
2 Not assigned
3 Not assigned
5 Alarm unacknowledged
7 Point is in alarm (bits in alarm are shown in field C9, byte offset 58).
8 - 10 Not assigned
12 Alarm released
The setting of Bit 0 and Bit 1 (better or worse condition) applies only to alarm
toggles, not to initial alarms. If any single bit goes into an alarm condition during
an alarm togle, the alarm is considered “worse”, even if other bits return from their
alarm condition at the same time. If a single bit or multiple bits return from an alarm
condition and no other bits enter their alarm condition, a “better” condition is
indicated. When all bits leave their alarm condition, the points return from alarm.
Value Status
(A2 word) (DS word) Description
0000H 0000H No alarms.
0001H 00A0H New alarms; Unacknowledged
0111H 40A2H Incremental worse alarm
3000H 00A2H Incremental worse alarm
1000H 40A1H Incremental better alarm
0001H 00A2H Incremental worse alarm
Value Status
(A2 word) (DS word) Description
0000H 0020H No alarms, Return
A2 Byte Offset: 4
Data Type: Integer
Definition: 16 Digital Point Values
• Current Values for 16 digital points.
• A2 field values may be forced by the user. Forcing is described in the ZY field
(byte offset 24) description.
A3 Byte Offset: 6
Data Type: Integer
Definition: Invalidity Bits
• Validity status for each of the 16 digital points in the A2 field.
— Any “forced” bit (see B3 field, byte offset 26) will cause the invalidity bit
for that digital point to be SET.
— Any bit “Not Used” (set using fields M0 to N5, byte offsets 84 to 122) will
cause the invalidity bits for that digital point to be set.
— Any bit for which a Power Check Failure or Remote I/O error has been
detected will cause the invalidity bits for that digital point to be set.
— An algorithm can also cause the invalidity bits for that digital point to be set
using field D1 (byte offset 62).
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the record type name
(BG, BN, or BX) entered by the user.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen.
• The numbers corresponding to the packed group record type names are shown
below:
BX 146
BN 148
BG 150
J5 Byte Offset: 9
Data Type: Byte
Description: Initial Value Selection
• Initialized by the user.
• Used to determine the value of the A2 field (byte offset 4) during a reset or
power-up.
— If the bit in the J5 field is SET to 0, then the A2 field remains at the last value
during run-time before the reset or power-up (that is, the value is latched).
— If the bit in the J5 field is SET to 1, then the A2 field is reset to the MAC Edit
function (MEDIT) Initial Value (IV) field value during reset or power-up.
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
LU Byte Offset: 11
Data Type: Byte
Definition: Time of Alarm — Seconds
• Initialized to zero.
• Indicates the second when the point last went into alarm.
• Valid range is 0 through 59.
• Updated at run time by the device scan software when the point goes into alarm.
DW Byte Offset: 12
Data Type: Integer
Definition: Second Status Word
• Bits are defined as follows:
Bit Definition
0 Not assigned
8- 15 Not assigned
DG Byte Offset: 14
Data Type: Integer
Definition: Signal Diagram Index
• Initialized by the user.
• Defines the number of the diagram.
• For 7-level (below) systems, the signal diagram can be displayed using the
Operator Station CRT 1 DISP DIAG or CRT 2 DISP DIAG key.
• For 8-level systems, the Signal Diagrams can be displayed using the Operator
WEStation point menu.
• For 6- and 7- level systems, valid entries are as follows:
— Main screen diagram numbers 1000 through 4999.
— Group numbers 5000 through 6999 (to display the diagram specified in the
group's diagram link).
• For 8-level systems, valid entries are 0-65535.
• Do not use diagram numbers that must be displayed with groups.
PN Byte Offset: 16
Data Type: String of 8 ASCII Characters
Definition: Point Name
• Initialized by the user.
• In extended-tag DPUs, the ED field contains the 16-character point name. The
PN field contains only the character “@”, followed by seven “blanks”.
ZY Byte Offset: 24
Data Type: Integer
Definition: Command Word
• Initialized to zero.
• Commands defined by the low byte (eight least-significant bits) at the current
software level include:
Table 6-7. Command Word
Command Definition
1 Clear force for this bit.
2 Set force for this bit.
3 Set force and change value for this bit.
4 Clear all forces.
5 Set force for all bits.
6 Set alarm checking on.
7 Set alarm checking off.
8 Acknowledge alarm.
9 Release alarm.
10 Unrelease alarm.
11-36 Not assigned.
37 Configure for alert alarm.
38 Configure for information alarm.
41 Enable Alarm Cutout.
42 Disable Alarm Cutout.
Command Definition
43 Clear tag level.
44 Set tag level to 1.
45 Set tag level to 2.
46 Set tag level to 3.
• Commands defined by the high byte (eight most-significant bits) at the current
software level include:
Bit Definition
4 State to set the above bit when an Enter Value command is set.
B3 Byte Offset: 26
Data Type: Integer
Definition: 16 Force Indication Bits
• Indicates which (if any) of the 16 digital values in the A2 field (byte offset 4) are
forced. “Forced” indicates that the point is scan removed and has an entered value.
• Whenever the force indication bit is set in this field, the corresponding bit in the
A3 Invalidity field (byte offset 6) is also set.
ED Byte Offset: 28
Data Type: String of 30 ASCII Characters
Definition: English Description
• Initialized by the user (default = 30 blanks).
• Provides an expanded description (30 characters maximum) of the point for use
in displays and listings.
• In extended tag DPUs, the ED field contains the point name, not the English
description.
C9 Byte Offset: 58
Data Type: Integer
Definition: In Alarm Bits
• Shows bits which are currently in alarm.
• When any bit of the 16 possible points is in alarm, the packed group point will
be in alarm as determined by the update group algorithm.
D0 Byte Offset: 60
Data Type: Integer
Definition: Algorithm Point Values
• Current values of any points as set by an algorithm.
• Bits used this way must also be marked for this purpose using HW (byte offset
70) and M0 (byte offset 84) to N5 (byte offset 114).
D1 Byte Offset: 62
Data Type: Integer
Definition: Algorithm Invalidity Bits
• Algorithm-set bits whose “bad” quality makes them invalid
• Invalidity does not, of itself, result in an alarm condition for the point.
D2 Byte Offset: 64
Data Type: Integer
Definition: Internal Status Word
Bit Definition
0, 1 = Tag Level
2 = Tag Acknowledge
D3 Byte Offset: 66
Data Type: Integer
Definition: Alarm Delay Counter
• Initialized by the DPU at run time.
• Counts down the alarm delay timer from the Z8 and Z9 fields.
Z8 Byte Offset: 68
Data Type: Byte
Definition: Initial Alarm Delay Time — Seconds
• Initialized by the user.
• Sets the time delay, in seconds, from the sensing of an initial alarm condition to
it being reported. While an alarm condition for a group alarm point must persist
throughout the entire delay period, any single bit on any single point need not
be in alarm for the entire delay period.
• Delay periods may range from 0 to 255 seconds. A value of 0 (zero) indicates
no delay.
Z9 Byte Offset: 69
Data Type: Byte
Definition: Incremental Alarm Delay — Seconds
• Initialized by the user.
• Sets the time delay, in seconds, from the sensing of an incremental alarm
condition to it being reported. While an incremental alarm condition for a group
alarm point must persist throughout the entire delay period, any single bit on any
single point need not be in alarm for the entire delay period
• Delay periods may range from 0 to 255 seconds. A value of 0 (zero) indicates
no delay.
HW Byte Offset: 70
Data Type: Integer
Definition: Offset of Hardware Address (Bytes)
• Initialized by the user.
• If not FFFFH, FFFEH or 0, all 16 digital points are read from or written to the
card at this address. See below:
Table 6-8. BN Points Reference
HW field Definition
0 Invalid Configuration
xxxxH “xxxx” is a valid I/O card address. The A2 field is updated
according to the 16 bit value read from the card address. If bit 2
of LC is set, all 16 bits are inverted before the value is stored into
A2.
HW field Definition
0 The point’s hardware address configuration is contained in the
M0 through N9 fields.
xxxxH “xxxx” is a valid I/O card address. The A2 field is updated
according to the 16-bit value read from the card address. If bit 2
of LC is set, the value is inverted before it is stored into A2. The
M0 field indicates which bits are to be inverted. For example, if
M0 is 8011H, then only bits 0, 4, and 15 will be inverted.
2. Determine the MBU offset (if any) from the hardware drawing. MBU 0 has
an offset of zero. MBU 1 has an offset of 200H.
3. For a packed group alarm point, the hardware offset calculation is:
HW = 2 (ADD) + MBU
where:
HW = hardware offset
ADD = card address (in hexadecimal)
MBU = MBU offset
AP Byte Offset: 72
Data Type: Byte
Definition: Alarm Priority
• Initialized by the user.
0 Low
1
2
3 High
AY Byte Offset: 73
Data Type: 1ASCII Character
Definition: Destination
• Whenever the drop database is updated against the Point Directory, AY is
initialized to be the first character of the characteristics of the point. If a
characteristics statement does not exist for a point, it is initialized to the “wild
card” (-) character.
MM Byte Offset: 74
Data Type: Byte
Definition: Time of Alarm — Month
• Initialized to zero.
• Indicates the month when the point last went into alarm.
• Updated at run time by the packed group alarm scan software when the point
goes into alarm.
NN Byte Offset: 75
Data Type: Byte
Definition: Time of Alarm — Date (Day)
• Initialized to zero.
• Indicates the date (day) when the point last went into alarm.
• Updated at run time by the packed group alarm scan software when the point
goes into alarm.
AH Byte Offset: 76
Data Type: Byte
Definition: Time of Alarm — Hours
• Initialized to zero.
• Indicates the hour of the day when the point last went into alarm.
• Updated at run time by the packed group alarm scan software when the point
goes into alarm.
MN Byte Offset: 77
Data Type: Byte
Definition: Time of Alarm — Hours
• Initialized to zero.
• Indicates the minute when the point last went into alarm.
• Updated at run time by the packed group alarm scan software when the point
goes into alarm.
ZB Byte Offset: 78
Data Type: Byte
Definition: Not Assigned
LC Byte Offset: 79
Data Type: Byte
Description: Include Status Checking
• Initialized by the user. If not initialized by the user, the value of LC defaults to
0 (zero).
— When two or more group members are in alarm, if any of the members are
shelved, released or return to normal, the group point will remain in its
current state.
— If the group point is in the accepted state, when the last remaining group
member returns to normal, is released, or shelved, the group point will go
out of alarm and will remain accepted.
Value Status
(A2 word) (DS word) Description
0000H 0000H No alarms.
0001H 00A0H New alarm, point is unacknowledged.
0111H 40A0H Two new alarms, point is unacknowledged.
0111H 4080H Point is acknowledged.
1111H 00A0H One new alarm, point is unacknowledged.
0111H 40A0H One input is shelved, is released, or returns to
normal. Point remains unacknowledged.,
0111H 4080H Point is acknowledged.
0011H 00A0H One input is shelved, is released, or returns to
normal. Point becomes unacknowledged.
0001H 40A0H One input is shelved, is released, or returns to
normal. Point remains unacknowledged.
0001H 4080H Point is acknowledged.
0000H 0020H Last input is shelved, released, or returns to nor-
mal. Point becomes unacknowledged.
Value Status
(A2 word) (DS word) Description
0000H 0000H No alarms.
0001H 00A0H New alarm, point is unacknowledged.
0111H 40A0H Two new alarms, point is unacknowledged.
0111H 4080H Point is acknowledged.
1111H 00A0H One new alarm, point is unacknowledged.
0111H 00A0H One input is shelved, is released, or returns to
normal.
0111H 0080H Point is acknowledged.
0011H 0080H One input is shelved, is released, or returns to
normal. Point remains acknowledged.
0001H 0080H One input is shelved, is released, or returns to
normal. Point remains acknowledged
0000H 0000H Last input is shelved, released, or returns to nor-
mal. Point remains acknowledged.
E0 Byte Offset: 80
Data Type: Integer
Description: Mask for Alarm Grouping
• Initialized by the user.
• Determines which bits of the A2 field will be scanned to determine the alarm
status of the point.
• If any bit of this field is 1, then the corresponding bit in the A2 field will be
included in the group alarm according to the bit sense as defined by the E1 field.
E1 Byte Offset: 82
Data Type: Integer
Description: Bit Sense for Alarm Grouping
• Initialized by the user.
• Determines whether the SET or RESET state of each bit in the A2 field will
cause the point alarm to be SET.
• If any bit of the E0 field is 1, then the alarm is SET (value of 1 or TRUE) if the
corresponding bit of the A2 field matches the bit of the E1 field in the same
position.
• Alarm checking is performed only for those bits within the value (A2 field, byte
offset 4) specified in the Alarm Mask field (E0, byte offset 80). For bits which
are checked, when the bit’s value is equal to the value specified here, the alarm
condition is set. That is, the corresponding bit in the In Alarm field (C9, byte
offset 58) is set, and the alarm bit in the point status word (bit 7 in the DS field,
byte offset 2) is set.
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
EO 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1
E1 0 0 0 0 0 0 0 0 1 0 1 0 1 0 1 0
A2 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0
C9 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 1
In this example, only bits 0 through 7 are included in alarm checking (as
specified by the E0 field). E1 specifies that for bits 0, 2, 4, and 6, an alarm will
occur when the bit’s value equals 0, and that for bits 1, 3, 5, and 7, an alarm will
occur when the bit’s value equals 1.
For bits 2 and 5, an alarm condition exists. That is, the actual value field (A2)
matches the specified alarm state (E1). Therefore, the applicable bit in the
Alarm Status field (C9) is set for these two bits. A point alarm will also be
generated (bit 7 in the DS field, byte offset 2, will be set).
Note that the value of bits 8 through 15 in A2 also match the values in E1;
however, since they are not selected in E0, these bits are ignored.
M0 Byte Offset: 84
Data Type: Integer
Description: Offset of Hardware Address - Bit 0
• Initialized by the user.
• Provides the offset of the hardware address for the field I/O that will provide a
value for bit 0 of the current value (A2) field.
• The following definitions apply to the M0 through N5 fields when the HW field
is zero (0000H):
— If this field is (0xxx xxxx xxxx xxxxB), then the corresponding bit of A2 is
read from an input card residing at hardware address (0xxx xxxx xxxx
xxxxB).
— If this field is (10xx xxxx xxxx xxxxB), then the corresponding bit of A2 is
read from a control ladder and is written to the output card residing at the
hardware address (00xx xxxx xxxx xxxxB). This value cannot be inverted
or power-checked.
— If this field is (11xx xxxx xxxx xxxxB), then the corresponding bit of A2 is
read from a text algorithm and is written to the output card residing at the
hardware address (00xx xxxx xxxx xxxxB). If bit 2 of LC is set, the value is
inverted before it is stored into A2. This value cannot be power checked.
M1 Byte Offset: 86
Data Type: Integer
Description: Offset of Hardware Address - Bit 1
• Initialized by the user.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 1 of the A2 field.
M2 Byte Offset: 88
Data Type: Integer
Description: Offset of Hardware Address - Bit 2
• Initialized by the user.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 2 of the A2 field.
• If the HW field is zero, refer to description under M0 field.
M3 Byte Offset: 90
Data Type: Integer
Description: Offset of Hardware Address - Bit 3
• Initialized by the user.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 3 of the A2 field.
M4 Byte Offset: 92
Data Type: Integer
Description: Offset of Hardware Address - Bit 4
• Initialized by the user.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 4 of the A2 field.
M5 Byte Offset: 94
Data Type: Integer
Description: Offset of Hardware Address - Bit 5
• Initialized by the user.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 4 of the A2 field.
M6 Byte Offset: 96
Data Type: Integer
Description: Offset of Hardware Address - Bit 6
• Initialized by the user.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 6 of the A2 field.
M7 Byte Offset: 98
Data Type: Integer
Description: Offset of Hardware Address - Bit 7
• Initialized by the user.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 7 of the A2 field.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 8 of the A2 field.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 9 of the A2 field.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 10 of the A2 field.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 11 of the A2 field.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 12 of the A2 field.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 13 of the A2 field.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 14 of the A2 field.
• If the HW field is zero, this field determines the offset of the hardware address
for the field I/O that will provide a value for bit 15 of the A2 field.
Drop Status records are of two types: DU and VU. DU record types are used to store
status information for a drop. Every drop must be configured with at least one point
of type DU.
VU record types (also known as Virtual Drop Status records), are used to link one
Data Highway to another for the WESbridge WEStation system. See the applicable
WESbridge documentation for more information on this record type.
For each of the record types listed above, the record type overview provides a table
showing the record fields included in each record type. These tables include the
following information:
• Size in bytes of each record type (to be used in estimating the amount of
memory required for the point database).
The record type overview tables also show which record fields can be assigned by
the user (an asterisk (*) is shown next to these fields).
The record types overview is followed by reference pages which provide more
detail on the record fields. For each record field, the record field identifier, byte
offset, and type of data value are shown, followed by a detailed description of the
record field's use and possible values.
Record
Type
Record Data Byte
CC Field Type Offset Description
LE I 0 Number of Linear Conversion Coefficients
LA I 2 Number of Linear Conversion Coefficients Allocated
LO I 4 Index of First Linear Conversion Coefficients Array
PE I 6 Number of Polynomial Conversion Coefficients Entered
PA I 8 Number of Polynomial Conversion Coefficients Allocated
PO I 10 Index of First Polynomial Conversion Coefficients Array
QE I 12 Number of Square Root Conversion Coefficients Entered
QA I 14 Number of Square Root Conversion Coefficients Allocated
QQ I 16 Index of First Square Root Conversion Coefficients Array
EE I 18 Number of Exponential Conversion Coefficients Entered
EA I 20 Number of Exponential Conversion Coefficients Allocated
EO I 22 Index of First Exponential Conversion Coefficients Array
SE I 24 Number of Square Root Polynomial Conversion Coefficients
Entered
SA I 26 Number of Square Root Polynomial Conversion Coefficients
Allocated
SO I 28 Index of First Square Root Polynomial Conversion Coefficients
Array
Record
Type
Record Data Byte
CC Field Type Offset Description
GE I 30 Number of 6-Segment Function Generator Conversion
Coefficients Entered
GA I 32 Number of 6-Segment Function Generator Conversion
Coefficients Allocated
GO I 34 Index of First 6-Segment Function Generator Conversion
Coefficients Entered
UE I 36 Not Assigned
UA I 38 Not Assigned
UO I 40 Not Assigned
VE I 42 Not Assigned
VA I 44 Not Assigned
VO I 46 Not Assigned
WE I 48 Not Assigned
WA I 50 Not Assigned
WO I 52 Not Assigned
XE I 54 Not Assigned
XA I 56 Not Assigned
XO I 58 Not Assigned
YE I 60 Not Assigned
YA I 62 Not Assigned
YO I 64 Not Assigned
ZE I 66 Not Assigned
ZA I 68 Not Assigned
ZO I 70 Not Assigned
Record
Type
Record Data Byte
CC Field Type Offset Description
CA Array of 6 Thermocouple Cold Junction
TH
Records
CO Array of Thermocouple Cold Junction Compensation Values
200 R
Number
Record
Type
Record Data
TH Field Type Description
BC R Cold Junction Compensation Value for Thermocouple Type B
EC R Cold Junction Compensation Value for Thermocouple Type E
JC R Cold Junction Compensation Value for Thermocouple Type J
KC R Cold Junction Compensation Value for Thermocouple Type K
RC R Cold Junction Compensation Value for Thermocouple Type R
SC R Cold Junction Compensation Value for Thermocouple Type S
TC R Cold Junction Compensation Value for Thermocouple Type T
QU I Quality of the Above Compensation Values
∗ = User-initialized field
Note
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized by drop configuration program.
• Valid range is 1 through 254; this number is the Data Highway drop number
used for handoffs (or token passing).
FA Byte Offset: 2
Data Type: Integer
Definition: Functional Processor (FP) Status Word 1
• Not initialized by the user.
Bit Definition
0 Not assigned.
1 Not assigned.
2 Not assigned.
3 Not assigned.
4 Drop required operator attention.
5 Alarm acknowledge.
6 Fault condition has been detected in this drop.
Bit Definition
7 Drop is in alarm.
8 Channel 0 was active and is now inactive.
9 Channel 1 was active and is now inactive.
10 Drop requires clock update.
11 Not assigned.
12 Backup “In Synch” with partner when set.
13 Not assigned.
14 Toggle Alarm Bit; indicates a change in alarm state.
15 Data Highway detected a timeout.
Bit Definition
0 Not assigned.
1 Not assigned.
2 Not assigned.
3 FP4 is an MSP (printer)
4 Drop requires operator attention.
5 Alarm acknowledge.
6 Fault condition has been detected in this drop.
7 Drop is in alarm.
8 Channel 0 was active and is now inactive.
9 Channel 1 was active and is now inactive.
10 Drop requires clock update.
11 FP1 is an MSP (CRT 1).
12 FP2 is an MSP (Keyboard).
13 FP3 is an MSP (CRT 2).
14 Toggle Alarm Bit; indicates a change in alarm state.
15 Data Highway detected a timeout.
Bit Definition
0 Bit 0 of retrieval activity (Historian only).
1 Bit1 of retrieval activity (Historian only).
2 Bit2 of retrieval activity (Historian only).
3 Not assigned
4 Drop requires operator attention.
5 Alarm acknowledge.
6 Fault condition has been detected in this drop.
7 Drop is in alarm.
8 Channel 0 was active and is now inactive.
9 Channel 1 was active and is now inactive.
10 Drop requires clock update.
11 Not assigned.
12 Not assigned.
13 Not assigned.
14 Toggle Alarm Bit; indicates a change in alarm state.
15 Data Highway detected a timeout.
FB Byte Offset: 4
Data Type: Byte
Definition: Functional Processor Status Byte (Drop Mode)
• For an 86/05 DPU, the bits are defined as follows.
— Bits 6 and 7 indicate the drop mode, as shown in the following table:
Bits
7 6 Description
0 0 Waiting for download
0 1 In Control mode
Bits
7 6 Description
1 0 In Backup mode
1 1 Restart with database in bubble
• For a WEStation shared Drop Redundancy Record (DRR), this indicates the
current primary drop number.
• For a 6-, 7-, or 8- level MAC controller (DPU or MAC-DS), the bits are defined as:
— Bits 4 through 7 indicate the MAC drop mode, as shown in the following table:
Bits
7 6 5 4 Drop Status Mode
0 0 0 0 Not Used
0 0 0 1 Off-line Configure Mode
0 0 1 0 Off-line Download mode
0 0 1 1 Off-line Fault Mode
0 1 0 0 On-line Control Mode
0 1 0 1 Not Used
0 1 1 0 Not Used
0 1 1 1 Not Used
1 0 0 0 On-line Backup Mode
1 0 0 1 Not Used
1 0 1 0 Not Used
1 0 1 1 Not Used
1 1 0 0 Off-line V_Config Download
1 1 0 1 Off-line V_MSP1 Download
1 1 1 0 Off-line V_MSP2 Download
1 1 1 1 Off-line V_Download
Bits
1 0 Description
0 1 1 Memory board
1 0 2 Memory boards
1 1 3 Memory boards
— Bits 3 is set to 1 to indicate that this drop is a Dual CRT Operator Station.
— Bits 6 and 7 indicate the Station type and mode, as shown below:
Bits
7 6 Description
0 0 Operator Station
0 1 Engineer Station in Operator (OPERATE, UNLOCK,
OR MONITOR) Mode
1 0 Engineer Station in Engineer (CONFIG) Mode
Bits
7 6 Description
0 0 In Download mode
0 1 Collecting
1 0 Not Used
1 1 Restart with database on disk
• For a WEStation shared Drop Redundancy Record (DRR), this indicates the
current primary drop number.
— Bits 4 through 7 indicate the drop mode, as shown in the following table:
Bits
7 6 5 4 Drop Status Mode
0 0 0 0 Not Used
0 0 0 1 Not Used
0 0 1 0 Not Used
0 0 1 1 Off-line Fault Mode
0 1 0 0 On-line Control Mode
0 1 0 1 Not Used
0 1 1 0 Not Used
0 1 1 1 Not Used
1 0 0 0 On-line Backup Mode
1 0 0 1 Not Used
1 0 1 0 Not Used
1 0 1 1 Not Used
1 1 0 0 Not Used
1 1 0 1 Not Used
1 1 1 0 Not Used
1 1 1 1 Not Used
Bit Description
0-2 Reserved for Log Server.
3-4 Computation Server and Software Server.
5 Reserved for application modes HSR.
6-7 Not assigned.
Bits 4 and 3 in the FB field have been allocated for the CS and SS drops, which
operate under the same concept of redundancy. The possible values are defined as:
Bits
4 3 Description
0 0 Backup - The drop’s application has indicated it is a healthy
Backup. This means it is prepared to become Primary.
0 1 Primary - the drop’s application has indicated it is operating as a
healthy Primary.
1 0 Off-line - The drop’s application is nonfunctional. This may
indicate the drop’s executive software (Checker, Server
Monitor, Watchdog, and so forth) has faulted. The application
software may have faulted.
1 1 Undetermined - The application has not yet specified what mode
it is in. If the drop’s SHC is in Primary mode, the application is
preparing to become Primary; if the SHC is in Backup mode, the
application is preparing to become Backup.
• For a Log Server, the bits are defined below. The bits for level 8.4.2 and later are
no longer used by the LS.
Bit Description
0 Alarm Handler subsystem in control / not in control.
1 Report Generator Subsystem in control / not in control.
2 Printer Manages Subsystem in control/ not in control.
FC Byte Offset: 5
Data Type: Byte
Definition: Drop Fault Code
• When equal to zero, indicates that no faults have been detected by the self-test
diagnostics of the drop.
• When not equal to zero, indicates an error code that identifies the fault condition
(for example, the particular piece of hardware that has failed).
• The value contained in the FC field is also written to the DPU's MSQ, MSX, or
MBU LED status display.
• Additional information about the fault is stored in the fault ID (FK field, byte
offset 25) and fault parameters (FS field, byte offset 94, and FO field, byte
offset 96).
• For definitions of the drop fault codes, fault IDs, and parameters, refer to “Self-
Test Diagnostics” (M0-0003).
HC Byte Offset: 6
Data Type: Integer
Definition: Data Highway Controller (DHC) Status Word
• For an MHC, MHR, or MBC Highway interface, the bits are defined as follows:.
Bit Definition
0 Activity detected on Channel 0 (including this drop's own activity) in the last 100 msec period.
1 Activity detected on Channel 1 (including this drop's own activity) in the last 100 µsec period.
2 Channel 0 (Highway 0) relay has been commanded to close.
3 Channel 1 (Highway 1) relay has been commanded to close.
4 Error code posted in Shared Memory location 69AH as follows:
1 = Not assigned.
2 = Channel 0 “RCVA” pointer changed while being read.
3 = Channel 1 “RCVA” pointer changed while being read.
4 =“R5” was zero in URAM when a Fault Analysis dump was triggered.
5 = “R5” did not match URAM when a Fault Analysis dump was triggered.
5 DHC in Idle mode.
6 Drop is designated as a timekeeper.
7 Drop identification has been found in the voted BAL.
8 For Westnet II: Bus Allocation List transmit/receive disabled.
For Westnet 2+: ICIM fault suspected on Channel 0.
9 DHC supports Fast Block Transfer (FBT).
10 Functional processor “deadman” timeout occurred.
11 For Westnet II: MAC mode jumper is in place.
For Westnet 2+: ICIM fault suspected on Channel 1.
12 Timer discrepancy greater than 1.25 millisecond.
13 For Westnet 2+ (Release 1.2 and above): BAL revote may be required (detected significant mis-
match between number of handoffs received and number of TDM entries in BAL).
Bit Definition
14 DHC enabled.
15 DHC in “Failure Analysis” dump mode.
Bit Definition
0 Activity detected on Channel 0 (including this drop's own activity) in the last 100 µsec
period.
1 Activity detected on Channel 1 (including this drop's own activity) in the last 100 µsec
period.
2 Channel 0 (Highway 0) relay has been commanded to close.
3 Channel 1 (Highway 1) relay has been commanded to close.
4 ICIM fault suspected on Channel 0.
5 ICIM fault suspected on Channel 1.
6 Drop is designated a timekeeper.
7 Timer discrepancy is greater than 1.25 milliseconds.
8-10 Operational mode of the SHC as follows:
0 = Off-line.
1 = Primary.
2 = Backup.
3 = Idle.
4 = Receive-only.
Note
The values indicated above are the decimal equivalent
of the data in bits 8-10.
11 TDM drop number found in the Bus Allocation List (BAL).
12 DEM drop number found in the voted BAL
13 For Westnet 2+ (Release 1.2 and above): BAL revote may be required (detected significant
mismatch between number of handoffs received and number of TDM entries in BAL).
14 “Deadman” timer has been disabled.
15 SHC in “Failure Analysis” dump mode.
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the applicable drop configuration function.
• May be useful to an alarm logger as it collects alarms broadcast over the Data
Highway.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen. The number
associated with the drop status record type is shown below:
• For Virtual Drop (VU) record types, the decimal byte offset is 16 (hex byte
offset is 10).
DU 6
JU Byte Offset: 9
Data Type: Byte
Definition: Drop Command
• Not initialized by the user.
• Used by the DPU to receive drop-related commands from the host and other
drops on the network.
• Commands at the current software level (these are DPU specific commands):
JU Description
14 Alarm acknowledge.
15 Re-enable Data Highway.
16 Clear fault indication.
17 Go to Idle mode (fault mode) when DIOB failure occurs.
(This is the default DIOB test configuration.)
18 Report DIOB failures as drop faults. The DPU does not go
to fault mode; it stays in control.
JU Description
19 Ignore DIOB failures. Failures are not reported as drop
faults; the DPU stays in control.
PS Byte Offset: 10
Data Type: Integer
Definition: Partner DPU's Drop System Identification
• For a DPU, the PS field is used as follows:
— For a non-redundant DPU, PS should not be initialized by the user. (This will
result in PS being set to zero, informing the DPU that it is non-redundant.)
— For a redundant DPU, PS should be initialized by the user to equal the drop
number of the redundant (partner) DPU.
— Used by the DPU to determine the mode in which the DPU should be running.
TG Byte Offset: 12
Data Type: Byte
Definition: Count of DHC Status Changes
• This field is set by the Data Highway Controller (DHC).
• For additional information on the DHC status values, refer to the applicable
Highway installation manual and “Self-Test Diagnostics” (M0-0003).
BS Byte Offset: 13
Data Type: Byte
Definition: Last DHC Bad Status (>4) Saved by Drop
• For a list of error conditions, see “Self-Test Diagnostics” (M0-0003).
DG Byte Offset: 14
Data Type: Integer
Definition: Signal Diagram Index
• Initialized by the user.
• For 7-level (below) systems, the signal diagram can be displayed using the
Operator Station CRT 1 DISP DIAG or CRT 2 DISP DIAG key.
• For 8-level systems, the Signal Diagrams can be displayed using the Operator
WEStation point menu.
— Group numbers 5000 through 6999 (to display the diagram specified in the
group's diagram link).
PN Byte Offset: 16
Data Type: String of 8 ASCII Characters
Definition: Point Name
• For DPUs, initialized by the drop configuration function based on user-entered
drop number or point name.
TY Byte Offset: 24
Data Type: Byte
Definition: Drop Type Code
• Defined as follows:
Value Meaning
1 Obsolete
2 6- or 7-level MMI (Engineer Station or Operator Station)
Value Meaning
3 BPU
4 6- or 7-level HSR
5 6- or 7-level Logger
6 CIU
7 Obsolete
8 MAC DPU
9 ABI
10 Obsolete
11 PCI
12 SIU
13 Cell Controller
14 HDR
15 UPCI
16 UXI/MXI
17 PCH
18 TCU
19 - 49 Not Assigned
50 WEStation Drop Status Record (DSR)
51 WEStation Drop Redundancy Record (DRR)
FK Byte Offset: 25
Data Type: Byte
Definition: Fault Identification Code
• Provides additional fault information for each fault code (FC field, byte
offset 5). For definitions of the fault ID values for each fault code, see “Self-
Test Diagnostics” (M0-0003).
TA Byte Offset: 26
Data Type: Integer
Definition: Drop Attention Code
• When not equal to zero, indicates that the drop requires attention.
Bit Definition
0 Pollable messages available in the tape subsystem.
1 The number of days of Daily Summary data available to be written to
tape is equal to or greater than the number of days specified in the HDR
configuration for “period of daily file tape dump.”
2 - 15 Not assigned.
Bit Definition
0 Point file closed.
1 Tape subsystem requires attention.
2 Point file full.
3 HSR in RAM overflow condition.
4 Text file full.
5 Text file closed.
6 Invalid close file time for point file.
7 Invalid close file time for text file.
8 Download complete.
9, 10 Not assigned.
11 Start-up of HSR complete.
12 -15 Not assigned.
ED Byte Offset: 28
Data Type: String of 30 ASCII Characters
Definition: English Description
• Initialized by the user (default = 30 blanks).
• Provides a description (30 characters maximum) of the drop for use in displays
and listings.
DT Byte Offset: 58
Data Type: Integer
Definition: Desired Loop Time
• For single-speed MAC DPU only, initialized by the user through the MAC DPU
Configuration function.
• For multi-speed, MAC DPU indicates the desired loop execution time for the
task in progress (in msec).
CT Byte Offset: 60
Data Type: Integer
Definition: Processing Time
• Not initialized by the user.
• For single-speed DPU, indicates the actual time (in msec) required by the
functional processor to execute its control and scan algorithms in the previous loop.
D1 Byte Offset: 62
Data Type: Integer
Definition: Count of DHC Bad Status (>4)
DR Byte Offset: 64
Data Type: Byte
Definition: Westnet II DHC Drop Number
• Initialized by the drop configuration function based on user-entered drop number.
— The control DPU will contain its TDM drop number in the DR byte.
— The backup DPU will name its normal drop number in the DR byte.
RD Byte Offset: 65
Data Type: Byte
Definition: Two's Complement of Drop Number
• Initialized to the two's complement of the drop number.
D3 Byte Offset: 66
Data Type: Integer
Definition: BAL Vote Quality and Percent TDM (Westnet 2+ Only)
• Not initialized by the user.
• High byte (offset 67) contains BAL vote quality variable. This will be an integer
in the range 0 to 3, indicating the number of BALs which matched at the last
BAL vote. That is, a value of 3 indicates that all three timekeeper drops contain
an identical BAL.
• Low byte (offset 66) contains TDM percent variable. This will be an integer in
the range 0 to 255, representing the percentage of processing time required for
periodic (TDM mode) broadcast. If this value approaches or exceeds 100
percent, the system may not have adequate time for both periodic (TDM mode)
and on-demand (DEM mode) broadcasting.
TF Byte Offset: 68
Data Type: Byte
Definition: Last Test Finished by the DHC
• Not initialized by the user.
• Used by the DHC to inform the functional processor that the last self-test was
completed by the DHC while it was in the disabled (self-test) mode. (Refer to
“Self-Test Diagnostics” (M0-0003) for additional information.)
TM Byte Offset: 69
Data Type: Byte
Definition: On-Line Confidence Check Failure Data
• Not initialized by the user.
• If the on-line confidence check fails, this field will contain the last self-test
passed. This information can be used to determine the test which failed. Note
that the value in this field is valid only when the confidence check failure status
is posted. For additional information, refer to “Self-Test Diagnostics”
(M0-0003).
TS Byte Offset: 70
Data Type: Integer
Definition: DHC Firmware Revision Level
• Not initialized by the user.
b 0 b b
Reserved
s = Sub-revision level
OS Byte Offset: 72
Data Type: Integer
Definition: Pointer to Status Change History Buffer
• Not initialized by the user.
• For Westnet 2+: This field contains the word address where the next DHC status
change will be entered into the circular status history buffer (shared memory
locations 6C0 - 6DF).
D7 Byte Offset: 74
Data Type: Integer
Definition: Information Highway Status Word
• Not initialized by the user.
• Indicates the ‘weight’ given to the drop in the polling process. For details se
“Highway Installation Manual (WEStation Equipped)” (M0-8000).
Bit
Bit Value Definition
0 0 Primary connection selected (voting process).
1 Backup connection selected (voting process).
1 0 Polling evaluations enables (polling process).
1 Polling evaluations suspended (polling process).
2 0 Host is not a polling drop (polling process).
1 Host is a polling drop (polling process).
3 0 Information Highway initialized correctly.
1 Information Highway initialization failed.
4 0 Alive messages are not being sent (voting process).
1 Alive messages are being sent (voting process).
5 0 Host is seen as alive on Primary (voting process)
1 Host is seen as failed on Primary (voting process)
6 0 Host is seen as alive on Backup (voting process)
1 Host is seen as failed on Backup (voting process)
7 Reserved
8 - 15 Weighting factor (a byte value from 1 to 255).
LH Byte Offset: 76
Data Type: Integer
Definition: Reserved
NH Byte Offset: 78
Data Type: Integer
Definition: Reserved
BZ Byte Offset: 80
Data Type: Integer
Definition: Number of Bad Message Interrupts from Channel 0
• Not initialized by the user.
BO Byte Offset: 82
Data Type: Integer
Definition: Number of Bad Message Interrupts from Channel 1
• Not initialized by the user.
BD Byte Offset: 84
Data Type: Integer
Definition: DHC Error Parameter 1
• Not initialized by the user.
• Interpretation of this field depends on the error status posted by the DHC. For
additional information, refer to “Self-Test Diagnostics” (M0-0003).
BI Byte Offset: 86
Data Type: Integer
Definition: DHC Error Parameter 2
• Not initialized by the user.
• Interpretation of this field depends on the error status posted by the DHC. For
additional information, refer to “Self-Test Diagnostics” (M0-0003).
IC Byte Offset: 88
Data Type: Integer
Definition: DHC Error Parameter 3
• Not initialized by the user.
• Interpretation of this field depends on the error status posted by the DHC. For
additional information, refer to “Self-Test Diagnostics” (M0-0003).
E5 Byte Offset: 90
Data Type: Integer
Definition: Drop-Specific Status Information
• For MAC-DS, defined as V-Channel DHC status. For additional information,
refer to “MAC-DS User's Guide” (U0-3001).
• For a WEStation shared Drop Redundancy Record (DRR), specifies the Primary
Drop number.
E6 Byte Offset: 92
Data Type: Integer
Definition: Drop-Specific Status Information
• For MAC-DS, defined as V-Channel custom I/O status. For additional
information, refer to “MAC-DS User's Guide” (U0-3001).
• For Chrono-Log CIU, defined as number of loops during which the drop was in
millisecond alarm (since reset). For additional information, refer to “Clock
Interface Unit User's Guide (Chronolog)” (U0-2101).
• For a WEStation shared Drop Redundancy Record (DRR), specifies the Backup
Drop number.
FS Byte Offset: 94
Data Type: Integer
Definition: Fault Parameter 1 (Left-Most Fault Parameter)
• Provides additional information for certain fault IDs (FK field, byte offset 25).
For definitions of the fault parameters for each fault ID, see “Self-Test
Diagnostics” (M0-0003).
FO Byte Offset: 96
Data Type: Integer
Definition: Fault Parameter 2 (Right-Most Fault Parameter)
• Provides additional information for certain fault IDs (FK field, byte offset 25).
For definitions of the fault parameters for each fault ID, see “Self-Test
Diagnostics” (M0-0003).
E9 Byte Offset: 98
Data Type: Integer
Definition: Drop-Specific Status Information
• For a DPU with distributed 700 Series I/O, represents the number of SIMs
assigned to IOP 1.
• For a WEStation shared Drop Redundancy Record (DRR), stores the failover
frequency (every 0.1 or 1.0 second). For more information on the DRR see
“System Point Directory User’s Guide” (U0-8205).
• For a 6-or 7-level HSR, represents the tape subsystem status, as shown below:
• For an HDR, represents the number of retries for the current or last tape
subsystem function.
• Indicates the second when the drop last went into alarm.
• Indicates the date when the drop last went into alarm.
• Indicates the hour when the drop last went into alarm.
• Indicates the minute when the drop last went into alarm.
Bit Function
1 Q-Line I/O
2 Distributed 700 Series I/O
3 Local 700 Series I/O (Not applicable to DPU)
4 V-Channel (MAC-DS only)
Bit Function
0 22K bytes user memory and single scan.
1 22K or 146K bytes of user memory and single scan.
2 22K or 146K bytes of user memory, single scan, and control loops.
3 370K bytes of user memory, multi-scan, and control loops.
4 Not assigned.
5 410K bytes of user memory, multi-scan, control loops, and expanded
database.
6 410K bytes of user memory, multi-scan, control loops, expanded
database, and Extended System IDs.
• For WEStation drops: Indicates what subsystems are running on the WEStation.
The 16 bits used to indicate the subsystems have the following interpretation:
Bit Function
0 Operator WEStation
1 Historian WEStation (HSR)
2 Logger WEStation
3 Computation WEStation (Computation Server)
4 Software WEStation
5 Reserved.
6 Engineering WEStation (Software Development Station)
7 Datalink Server WEStation.
8 WesBridge
9 - 15 Not Assigned
• For the HDR, represents the tape subsystem status, as shown below:
Bit Function
0 Tape subsystem idle
1 Initialization failure - controller error
2 Initializing tape controller
3 Processing `Read Directory' command
4 Processing `Format' command
5 Processing `Write Hourly Files' command
6 Not assigned
7 Processing `Read' command
Bit Function
8 Processing `Write Daily File' command
9 Initialization failure - drive is off-line
10 Not assigned
11 Initialization failure - timeout
12 Drive test in progress
• Indicates the number of cabinet segments that have RTDs mounted to them for
cold junction compensating thermocouple inputs.
• Used by the CJSCAN routine to determine how many RTD inputs it should scan
and, consequently, use in providing thermocouple input compensation values.
• Indicates the address of the QBO point card used for running a diagnostic on the
UIOB.
• Q0 is one of eight fields (Q0 through Q7) that can be initialized for this diagnostic.
Only one field should be initialized for each QBO card used for this test.
• Indicates the address of the QBO point card used for running a diagnostic on the
UIOB.
• Q1 is one of eight fields (Q0 through Q7) that can be initialized for this diagnostic.
Only one field should be initialized for each QBO card used for this test.
• Indicates the address of the QBO point card used for running a diagnostic on the
UIOB.
• Q2 is one of eight fields (Q0 through Q7) that can be initialized for this diagnostic.
Only one field should be initialized for each QBO card used for this test.
• Indicates the address of the QBO point card used for running a diagnostic on the
UIOB.
• Q3 is one of eight fields (Q0 through Q7) that can be initialized for this diagnostic.
Only one field should be initialized for each QBO card used for this test.
• Indicates the address of the QBO point card used for running a diagnostic on the
UIOB.
• Q4 is one of eight fields (Q0 through Q7) that can be initialized for this diagnostic.
Only one field should be initialized for each QBO card used for this test.
• Indicates the address of the QBO point card used for running a diagnostic on the
UIOB.
• Q5 is one of eight fields (Q0 through Q7) that can be initialized for this diagnostic.
Only one field should be initialized for each QBO card used for this test.
• Indicates the address of the QBO point card used for running a diagnostic on the
UIOB.
• Q6 is one of eight fields (Q0 through Q7) that can be initialized for this diagnostic.
Only one field should be initialized for each QBO card used for this test.
• Indicates the address of the QBO point card used for running a diagnostic on the
UIOB.
• Q7 is one of eight fields (Q0 through Q7) that can be initialized for this diagnostic.
Only one field should be initialized for each QBO card used for this test.
• Set to 1 during the first execution loop following each time the DPU takes over
control of the UIOB (that is, the first following the transaction from BACKUP
to CONTROL mode).
• Set to 2 during the first execution loop following each time the DPU is reset or
powered-up (that is, the first loop after the functional processor has been restarted).
• Used by control algorithms to perform initialization logic for first pass (or failover).
• Informs the eavesdrop routine as to the status of the parallel port when the
routine was called. (The eavesdrop routine provides the DPU with the capability
to communicate with the standard WDPF diagnostic test device.)
• Used whenever the Data Highway is not on-line to determine whether the cause
is an uninitialized Bus Allocation List, or a Data Highway fault.
WN Value Processor
1 Q-Line I/O
2 Distributed 700 Series I/O
3 Local 700 Series I/O (Not applicable to DPU)
4 V-Channel (MAC-DS only)
This section contains the reference pages describing the following Algorithm
Record types and associated record fields:
• K Algorithm Records
• L Algorithm Records
• M Algorithm Records
• P Algorithm Records
For each of the record types listed above, the record type overview provides a table
showing the record fields included in each record type. These tables include the
following information:
• Size in bytes of each record type (to be used in estimating the amount of
memory required for the point database).
The record type overview tables also show which record fields can be assigned by
the user (an asterisk (*) is shown next to these fields).
The record types overview is followed by reference pages which provide more
detail on the record fields. For each record field, the record field identifier, byte
offset, and type of data value are shown, followed by a detailed description of the
record field's use and possible values. Each record type is shown first in tabular
form. Following the table is a listing of the various record fields. For each field, the
byte offset, data type, and description are provided. For many of the fields,
examples of parameter setting are included.
Record Type
Record Data Byte
KV KF Field Type Offset Description
ID I 0 System Identification (page 8-5)
CS I 2 Record Status Word (page 8-5)
A2 I 4 Not Assigned (page 8-5)
A3 I 6 Not Assigned (page 8-6)
RT B 8 Record Type (page 8-6)
CG B 9 Change Flag (page 8-6)
SR B 10 Drop System Identification (page 8-6)
LU B 11 Tuning Diagram Number (page 8-6)
CN I 12 Interface to Keys/Buttons (page 8-7)
CP I 14 Copy of Last CN Control Word (page 8-8)
RR B 16 Byte Constant (page 8-8)
LR B 17 Byte Constant (page 8-8)
RK B 18 Byte Constant (page 8-8)
LK B 19 Byte Constant (page 8-8)
B0 I 20 Integer Constant (page 8-8)
B1 I 22 Integer Constant (page 8-8)
Record Type
Record Data Byte
KV KF Field Type Offset Description
B2 I 24 Integer Constant (page 8-8)
B3 I 26 Integer Constant (page 8-8)
B4 I 28 Integer Constant (page 8-8)
B5 I 30 Integer Constant (page 8-8)
B6 I 32 Integer Constant (page 8-8)
B7 I 34 Integer Constant (page 8-8)
B8 I 36 Integer Constant (page 8-8)
B9 I 38 Integer Constant (page 8-8)
C0 I 40 Integer Constant (page 8-8)
C1 I 42 Integer Constant (page 8-8)
C2 I 44 Integer Constant (page 8-8)
C3 I 46 Integer Constant (page 8-8)
C4 I 48 Integer Constant (page 8-8)
C5 I 50 Integer Constant (page 8-8)
C6 I 52 Integer Constant (page 8-8)
C7 I 54 Integer Constant (page 8-8)
C8 I 56 Integer Constant (page 8-8)
C9 I 58 Integer Constant (page 8-8)
D0 I 60 Integer Constant (page 8-8)
D1 I 62 Integer Constant (page 8-8)
D2 I 64 Integer Constant (page 8-8)
D3 I 66 Integer Constant (page 8-8)
D4 I 68 Integer Constant (page 8-8)
D5 I 70 Integer Constant (page 8-8)
D6 I 72 Integer Constant (page 8-8)
D7 I 74 Integer Constant (page 8-8)
D8 I 76 Integer Constant (page 8-8)
Record Type
Record Data Byte
KV KF Field Type Offset Description
D9 I 78 Integer Constant (page 8-8)
E0 I 80 Integer Constant (page 8-8)
E1 I 82 Integer Constant (page 8-8)
E2 I 84 Integer Constant (page 8-8)
E3 I 86 Integer Constant (page 8-8)
E4 I 88 Integer Constant (page 8-8)
E5 I 90 Integer Constant (page 8-8)
E6 I 92 Integer Constant (page 8-8)
E7 I 94 Integer Constant (page 8-8)
E8 I 96 Integer Constant (page 8-8)
E9 I 98 Integer Constant (page 8-8)
F0 I 100 Integer Constant (page 8-8)
F1 I 102 Integer Constant (page 8-8)
F2 I 104 Integer Constant (page 8-8)
F3 I 106 Integer Constant (page 8-8)
F4 I 108 Integer Constant (page 8-8)
F5 I 110 Integer Constant (page 8-8)
F6 I 112 Integer Constant (page 8-8)
F7 I 114 Integer Constant (page 8-8)
F8 I 116 Integer Constant (page 8-8)
F9 I 118 Integer Constant (page 8-8)
G0 I 120 Integer Constant (page 8-8)
G1 I 122 Integer Constant (page 8-8)
R = Real number (4 Bytes. Floating point number, such as, 10.4 or 0.34
E-2.).
Table 8-2. K AlgorithmRecord Types Size Requirements (Bytes)
Record Type KV KF
Record Size 124 54
Overhead 0 0
Total Size 124 54
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
CS Byte Offset: 2
Data Type: Integer
Definition: Record Status Word
• Should not be used internally by the algorithm.
A2 Byte Offset: 4
Data Type: Integer
Definition: Not Assigned
A3 Byte Offset: 6
Data Type: Integer
Definition: Not Assigned
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the algorithm name
entered by the user.
• May be used for type checking on displayed information. Identifies the type of
record by number. The record type number is commonly used in the Point
Directory listing and Point Details screen. The numbers corresponding to the K
algorithm record type names are shown below:
KF 151
KV 153
CG Byte Offset: 9
Data Type: Byte
Definition: Change Flag
• Initialized to zero.
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
LU Byte Offset: 11
Data Type: Byte
Definition: Tuning Diagram Number
• May be user-initialized.
CN Byte Offset: 12
Data Type: Integer
Definition: Interface to Keys/Buttons
• Interfaces the control functions (keys or buttons) at the operator interface to the
algorithms specified in the graphics control statement. See the applicable
graphic language documentation for information on the control statements
available in a specific software level.
• The Control keys and Programmable keys activate bits as indicated below. The
P-key definitions shown below are defined in the Device Maintenance subscreen
(DEV MAINT key on the Operator Station).
Algorithm Point in
Bit Key Description Control Statement Control_10 Word
0 P1(STOP TRAVEL) or F1 First First
STOP TRAVEL Key First
1 P2(RELEASE CAPTURE) or F2 First Second
CAS Mode Key Second
2 P3(GO TO SUPV) or F3 First Third
SUPV Mode Key Second
3 P4(TRIP ACK) or F4 First Fourth
TRIP ACK Key Second
4 P5(ENABLE LOCKOUT) or F5 Second Fifth
DDC Mode Key Second
5 P6(DISABLE LOCKOUT) or F6 Second Sixth
6 P7(TAGOUT) or F7 Second Seventh
7 P8(REMOVE TAGOUT) or F8 Second Eighth
8 START/OPEN/TRIP First Ninth
ENTER Key or F9 First
9 STOP/CLOSE/RESET First Tenth
CANCL Key or F10 First
10 Raise (↑) Setpoint First
11 Lower (↓) Setpoint First
12 AUTO Second
Algorithm Point in
Bit Key Description Control Statement Control_10 Word
13 MAN Second
14 Raise Demand Second
15 Lower Demand Second
Note
CP Byte Offset: 14
Data Type: Integer
Definition: Copy of Last CN Control Word
RR through G1
The definitions of these fields are specific to each algorithm. For byte offsets and
data types, refer to the Record Types reference page(s).
Record Type
Record Data Byte
LV LF L8 L4 L2 Field Type Offset Description
ID I 0 System Identification (page 8-11)
CS I 2 Record Status Word (page 8-11)
OB I 4 Not Assigned (page 8-11)
A3 I 6 Not Assigned (page 8-11)
RT B 8 Record Type (page 8-11)
NF B 9 Selected Number (page 8-12)
SR B 10 Drop System Identification
(page 8-12)
LU B 11 Tuning Diagram Number
(page 8-12)
R1 R 12 Real Constant (page 8-12)
R2 R 16 Real Constant (page 8-12)
R3 R 20 Real Constant (page 8-12)
R4 R 24 Real Constant (page 8-12)
R5 R 28 Real Constant (page 8-12)
R6 R 32 Real Constant (page 8-12)
R7 R 36 Real Constant (page 8-12)
R8 R 40 Real Constant (page 8-12)
R9 R 44 Real Constant (page 8-12)
S1 R 48 Real Constant (page 8-12)
S2 R 52 Real Constant (page 8-12)
S3 R 56 Real Constant (page 8-12)
S4 R 60 Real Constant (page 8-12)
S5 R 64 Real Constant (page 8-12)
Record Type
Record Data Byte
LV LF L8 L4 L2 Field Type Offset Description
S6 R 68 Real Constant (page 8-12)
S7 R 72 Real Constant (page 8-12)
S8 R 76 Real Constant (page 8-12)
S9 R 80 Real Constant (page 8-12)
T1 R 84 Real Constant (page 8-12)
T2 R 88 Real Constant (page 8-12)
T3 R 92 Real Constant (page 8-12)
T4 R 96 Real Constant (page 8-12)
T5 R 100 Real Constant (page 8-12)
T6 R 104 Real Constant (page 8-12)
T7 R 108 Real Constant (page 8-12)
T8 R 112 Real Constant (page 8-12)
T9 R 116 Real Constant (page 8-12)
G0 I 120 Integer Constant (page 8-12)
G1 I 122 Integer Constant (page 8-12)
R = Real number (4 Bytes. Floating point number, such as, 10.4 or 0.34
E-2.)
Record Type LV LF L8 L4 L2
Record Size 124 84 44 28 20
Overhead 0 0 0 0 0
Total Size 124 84 44 28 20
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
CS Byte Offset: 2
Data Type: Integer
Definition: Record Status Word
• Should not be used internally by the algorithm.
OB Byte Offset: 4
Data Type: Integer
Definition: Not Assigned
A3 Byte Offset: 6
Data Type: Integer
Definition: Not Assigned
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the algorithm name
entered by the user.
• May be use for type checking on displayed information.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen. The numbers
corresponding to the L algorithm record type names are shown below:
NF Byte Offset: 9
Data Type: Byte
Definition: Selected Number
• Initialized by the user for relevant algorithms.
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
• Identifies the drop in which the algorithm record originates.
LU Byte Offset: 11
Data Type: Byte
Definition: Tuning Diagram Number
• May be user-initialized.
• Indicates the diagram number for a tuning diagram.
R1 through G1
The definitions of these fields are specific to each algorithm. For byte offsets and
data types, refer to the Record Types reference page(s).
Record Type
Record Data Byte
MV MA MP Field Type Offset Description
ID I 0 System Identification (page 8-15)
SW I 2 Record Status Word (page 8-15)
VB R 4 Value Buffer (page 8-15)
RT B 8 Record Type (page 8-15)
CG B 9 Change Flag (page 8-16)
SR B 10 Drop System Identification (page 8-16)
LU B 11 Tuning Diagram Number (page 8-16)
CN I 12 Interface to Operator Station Keys (page 8-16)
CP I 14 Copy of Last CN Control Word (page 8-18)
RR B 16 Byte Constant (page 8-18)
LR B 17 Byte Constant (page 8-18)
RK B 18 Byte Constant (page 8-18)
LK B 19 Byte Constant (page 8-18)
TP R 20 Real Constant (page 8-18)
BT R 24 Real Constant (page 8-18)
HM R 28 Real Constant (page 8-18)
HN I 32 Integer Constant (page 8-18)
QC I 34 Integer Constant (page 8-18)
BM B 36 Byte Constant (page 8-18)
BA B 37 Byte Constant (page 8-18)
BR B 38 Byte Constant (page 8-18)
RQ B 39 Byte Constant (page 8-18)
MJ I 40 Integer Constant (page 8-18)
Record Type
Record Data Byte
MV MA MP Field Type Offset Description
AJ I 42 Integer Constant (page 8-18)
RJ I 44 Integer Constant (page 8-18)
C3 I 46 Integer Constant (page 8-18)
S1 R 48 Real Constant (page 8-18)
S2 R 52 Real Constant (page 8-18)
S3 R 56 Real Constant (page 8-18)
S4 R 60 Real Constant (page 8-18)
S5 R 64 Real Constant (page 8-18)
S6 R 68 Real Constant (page 8-18)
S7 R 72 Real Constant (page 8-18)
S8 R 76 Real Constant (page 8-18)
S9 R 80 Real Constant (page 8-18)
T1 R 84 Real Constant (page 8-18)
T2 R 88 Real Constant (page 8-18)
T3 R 92 Real Constant (page 8-18)
T4 R 96 Real Constant (page 8-18)
T5 R 100 Real Constant (page 8-18)
T6 R 104 Real Constant (page 8-18)
T7 R 108 Real Constant (page 8-18)
T8 R 112 Real Constant (page 8-18)
T9 R 116 Real Constant (page 8-18)
U1 R 120 Real Constant (page 8-18)
R = Real number (4 Bytes. Floating point number, such as, 10.4 or 0.34
E-2.)
Table 8-6. M Algorithm Record Types Size Requirements (Bytes)
Record Type MV MA MP
Record Size 124 46 36
Overhead 0 0 0
Total Size 124 46 36
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
SW Byte Offset: 2
Data Type: Integer
Definition: Record Status Word
• Should not be used internally by the algorithm.
VB Byte Offset: 4
Data Type: Real
Definition: Value Buffer
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the algorithm name
entered by the user.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen. The numbers
corresponding to the M algorithm record type names are shown below:
MP 190
MA 195
MV 200
CG Byte Offset: 9
Data Type: Byte
Definition: Change Flag
• Initialized to zero.
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
LU Byte Offset: 11
Data Type: Byte
Definition: Tuning Diagram Number
• May be user-initialized.
CN Byte Offset: 12
Data Type: Integer
Definition: Interface to Keys/Buttons
• Interfaces the control functions (keys or buttons) at the operator interface to the
algorithms specified in the graphics control statement. See the applicable
graphic language documentation for information on the control statements
available in a specific software level.
• The Control keys and Programmable keys activate bits as indicated below. The
P-key definitions shown below are defined in the Device Maintenance subscreen
(DEV MAINT key on the Operator Station)
Algorithm Point in
Bit Key Description Control Statement Control_10 Word
0 P1(STOP TRAVEL) or F1 First First
STOP TRAVEL Key First
1 P2(RELEASE CAPTURE) or F2 First Second
CAS Mode Key Second
2 P3(GO TO SUPV) or F3 First Third
SUPV Mode Key Second
3 P4(TRIP ACK) or F4 First Fourth
TRIP ACK Key Second
4 P5(ENABLE LOCKOUT) or F5 Second Fifth
DDC Mode Key Second
5 P6(DISABLE LOCKOUT) or F6 Second Sixth
6 P7(TAGOUT) or F7 Second Seventh
7 P8(REMOVE TAGOUT) or F8 Second Eighth
8 START/OPEN/TRIP First Ninth
ENTER Key or F9 First
9 STOP/CLOSE/RESET First Tenth
CANCL Key or F10 First
10 Raise (↑) Setpoint First
11 Lower (↓) Setpoint First
12 AUTO Second
13 MAN Second
14 Raise Demand Second
15 Lower Demand Second
Note
CP Byte Offset: 14
Data Type: Integer
Definition: Copy of Last CN Control Word
RR through U1
The definitions of these fields are specific to each algorithm. For byte offset and data
types, refer to the Record Types reference page(s).
Record type
Record Data Byte
P3 P2 P1 Field Type Offset Description
ID I 0 System Identification (page 8-20)
CS I 2 Record Status Word (page 8-20)
A2 I 4 Not Assigned (page 8-20)
A3 I 6 Not Assigned (page 8-20)
RT B 8 Record Type (page 8-21)
CG B 9 Change Flag (page 8-21)
SR B 10 Drop System Identification (page 8-21)
LU B 11 Tuning Diagram Number (page 8-21)
HI R 12 Real Constant (page 8-22)
LW R 16 Real Constant (page 8-22)
GN R 20 Real Constant (page 8-22)
RE R 24 Real Constant (page 8-22)
OI R 28 Real Constant (page 8-22)
OO R 32 Real Constant (page 8-22)
K1 R 36 Real Constant (page 8-22)
K2 R 40 Real Constant (page 8-22)
K3 R 44 Real Constant (page 8-22)
K4 R 48 Real Constant (page 8-22)
LG R 52 Real Constant (page 8-22)
LD R 56 Real Constant (page 8-22)
RA R 60 Real Constant (page 8-22)
OD R 64 Real Constant (page 8-22)
R = Real number (4 Bytes. Floating point number, such as, 10.4 or 0.34
E-2.)
Table 8-8. P Algorithm Record Types Size Requirements (Bytes)
Record Type P3 P2 P1
Record Size 68 44 24
Overhead 0 0 0
Total Size 68 44 24
ID Byte Offset: 0
Data Type: Integer
Definition: System Identification
• Initialized whenever the Point Directory is updated.
CS Byte Offset: 2
Data Type: Integer
Definition: Record Status Word
• Should not be used internally by the algorithm.
A2 Byte Offset: 4
Data Type: Integer
Definition: Not Assigned
A3 Byte Offset: 6
Data Type: Integer
Definition: Not Assigned
RT Byte Offset: 8
Data Type: Byte
Definition: Record Type Number
• Initialized by the MAC Edit function (MEDIT), based on the algorithm name
entered by the user.
• Identifies the type of record by number. The record type number is commonly
used in the Point Directory listing and Point Details screen. The numbers
corresponding to the P algorithm record type names are shown below:
P1 175
P2 180
P3 185
CG Byte Offset: 9
Data Type: Byte
Definition: Change Flag
• Initialized to zero.
SR Byte Offset: 10
Data Type: Byte
Definition: Drop System Identification
• Initialized by the MAC Edit function (MEDIT).
LU Byte Offset: 11
Data Type: Byte
Definition: Tuning Diagram Number
• May be user-initialized.
HI through OD
The definitions of these fields are specific to each algorithm. For byte offsets and
data types, refer to the Record Types reference page(s).
• 1 AB record, 16 bits in, converted to floating point (using QAX, QAV, QAW,
QAI, or QLI cards):
Memory Memory
Total User Allocated to Allocated to
Controller Type Memory Database Control
Single-speed 146 Kbytes 82 Kbytes 64 Kbytes
Multi-speed (5- or 6-level) 370 Kbytes 82 Kbytes 288 Kbytes
Multi-speed (7-level) or higher 410 Kbytes 122 Kbytes 288 Kbytes
If the database reaches any of these limits, the MAC software will not allow new
points (or new points of the specific type) to be added.
Note
In all point records which can be broadcast on the Data Highway (including process
points, algorithm records, and drop status records), the first 2 bytes of the point
record contain the System ID. This unique identification number is used for all Data
Highway communication, as well as within the individual drop's databases.
The System ID number is assigned when the Point Directory is updated, and is
stored in the Point Directory file. It is essential to maintain a single Point Directory
file for the entire system, to ensure that no duplicate System IDs are assigned.
For standard points, the 14 least significant bits are interpreted as an integer System
ID in the range 1 to 16383. For Extended System ID points, the 15 least significant
bits are interpreted as an integer System ID in the range 16384 to 32768 (bit 14 is
always set).
Note
Within the originating drop, the 2 most significant bits (14 and 15) of a standard
point's System ID field may be used to represent additional information (such as
whether the point is digital). This usage depends on the type of drop and the
software level of the system. In all cases, however, when the point information is
received by another drop (such as an Operator Station), these bits are not used. For
this reason, any usage of bits 14 and 15 is normally transparent to the user.
Note that the System ID field is not used to distinguish between standard and
EXSID points. The Data Highway uses a unique message format for EXSID points,
and drops which can use EXSID points maintain a separate internal table for EXSID
point data (refer to “Westnet II Data Highway Description” (M0-0010) for
additional information).
V Z
Value Buffer Z1 record field
M Algorithm Records 8-15 Device Points 5-22
VB record field Z2 record field
M Algorithm Records 8-15 Device Points 5-22
VC Record Type Z3 record field
see Device Point Record Types, table Device Points 5-22
VU Record Type Z4 record field
see Drop Status Record Types, table Device Points 5-22
VU record types (Virtual Drop Status) 7-1, 7- Z5 record field
19 Device Points 5-23
VX Record Type Z6 record field
see Device Point Record Types, table Device Points 5-23
Z7 record field
W Device Points 5-24
W0 record field Z8 record field
Device Points 5-18 Packed Group Alarm 6-34
W1 record field Z9 record field
Device Points 5-19 Packed Group Alarm 6-34
W2 record field ZL record field
Device Points 5-20 Expanded Analog Points 3-70
W3 record field ZM record field
Device Points 5-20 Expanded Analog Points 3-76
W4 record field ZY record field
Device Points 5-21 Packed Group Alarm 6-31
W5 record field Packed Group Points 6-11
Device Points 5-21
W6 record field
Device Points 5-21
W7 record field
Device Points 5-21
Westnet II DHC Drop Number
Drop Status Records 7-24
WF record field
Drop Status Records 7-41
WN record field
Drop Status Records 7-41
Write verification error
Analog Points 3-8
Digital Points 4-8