Device-defined data types (HART Output)

4 = 0...20 mA

5 = 4...20 mA

0 = Alarms are enabled

1 = Alarms are disabled

0 = Diagnostics are disabled

1 = Diagnostics are enabled

0 = Ramping is disabled

1 = Ramping to Program Mode is enabled

0 = Ramping is disabled

1 = Ramping to Fault Mode is enabled

0 = Disabled

1 = Enabled

0 = Transition to user-defined value

1 = Hold Last State

0 = Transition to user-defined value

1 = Hold Last State

0 = Channel remains in Program mode

1 = Channel remains in Fault mode

0 = Ramping is disabled

1 = Ramp in Run Mode is enabled

0 = HART is disabled

1 = HART is enabled

0 = HART PV Damping is disabled

1 = HART PV Damping is enabled

0 = HART PV Range is disabled

1 = HART PV Range is enabled

Reserved

PV units code for PV range.

0...255

0 = Forever

1 = 1 second

2 = 2 seconds

5 = 5 seconds

10 = 10 seconds

-1.0E+11...+1.0E+11

A combination of LowSignal, HighSignal, LowEngineering, and HighEngineering are used to scale the input data returned by the device.

-1.0E+11...+1.0E+11

A combination of LowSignal, HighSignal, LowEngineering, and HighEngineering are used to scale the input data returned by the device.

-1.0E+11...+1.0E+11

A combination of LowSignal, HighSignal, LowEngineering, and HighEngineering are used to scale the input data returned by the device.

-1.0E+11...+1.0E+11

A combination of LowSignal, HighSignal, LowEngineering, and HighEngineering are used to scale the input data returned by the device.

-1.0E+11...+1.0E+11

-1.0E+11...+1.0E+11

-1.0E+11...+1.0E+11

Configures the maximum rate that the output value may change when transitioning to either FaultValue or ProgValue if either RampToFault or RampToProg bits are set, respectively, or in Run Mode if RampToRun is set.

-1.0E+11...+1.0E+11

This value is used to correct for actuator inaccuracy in the output actuator. The value is configured per channel and is added to the data before scaling is performed.

-1.0E+11...+1.0E+11

Defines the value for the analog output in case of a communication fault if FaultMode equals zero.

-1.0E+11...+1.0E+11

Defines the value for the analog output when the connection is in Program mode if the ProgMode bit is set to "User-defined Value".

-1.0E+11...+1.0E+11

-1.0E+11...+1.0E+11

-1.0E+11...+1.0E+11

-1.0E+11...+1.0E+11

0 = Idle

1 = Run

0 = A connection exists between the device and the controller

1 = Bad

0 = No diagnostics active

1 = One or more diagnostics are active or the prognostics threshold is reached

-128...127

The value of 0 is skipped except during device power-up.

0 = A fault does not exist

1 = A fault exists

0 = Data is valid

1 = Validity of data is uncertain. Device is operating outside its designed operating range, or data is under manual or override control.

0 = No Load condition does not exist

1 = No Load condition exists, meaning a signal wire is disconnected from the channel or the RTB.

0 = Short Circuit or Overcurrent condition does not exist

1 = Short Circuit or Overcurrent condition exists

0 = Channel is not holding

1 = Channel is holding

0 = Last channel data received was a number

1 = Last channel data received was not a number

0 = The input signal at the channel is greater than the minimum detectable signal

1 = The input signal at the channel is less than or equal to the minimum detectable signal

0 = The input signal at the channel is less than the maximum detectable signal

1 = The input signal at the channel is greater than or equal to the maximum detectable signal

0 = Alarm is not triggered

1 = Alarm is triggered

0 = Alarm is not triggered

1 = Alarm is triggered

0 = Alarm is not triggered

1 = Alarm is triggered

-1.0E+11...+1.0E+11

Any positive value.

RollingTimestamp is a continuously running timer that counts in milliseconds. When an input device scans its channels, it also records the RollingTimestamp value.

0 = Idle

1 = Run

0 = A connection exists between the device and the controller

1 = Bad

0 = No diagnostics active

1 = One or more diagnostics are active or the prognostics threshold is reached

-128...127

The value of 0 is skipped except during device power-up.

0 = A fault does not exist

1 = A fault exists

0 = Data is valid

1 = Validity of data is uncertain. Device is operating outside its designed operating range, or data is under manual or override control.

0 = No Load condition does not exist

1 =No Load condition exists, meaning a signal wire is disconnected from the channel or the RTB.

0 = Short Circuit or Overcurrent condition does not exist

1 = Short Circuit or Overcurrent condition exists

0 = Channel is not holding

1 = Channel is holding

0 = Last channel data received was a number

1 = Last channel data received was not a number

0 = The input signal at the channel is greater than the minimum detectable signal

1 = The input signal at the channel is less than or equal to the minimum detectable signal

0 = The input signal at the channel is less than the maximum detectable signal

1 = The input signal at the channel is greater than or equal to the maximum detectable signal

0 = Alarm is not triggered

1 = Alarm is triggered

0 = Alarm is not triggered

1 = Alarm is triggered

0 = Alarm is not triggered

1 = Alarm is triggered

-1.0E+11...+1.0E+11

Any positive value.

RollingTimestamp is a continuously running timer that counts in milliseconds. When an input device scans its channels, it also records the RollingTimestamp value.

HART device status information.

GeneralStatus bit 0

0 = If Ch0x.DeviceStatus.HARTCommFail is 1, then HART is not enabled on this channel.

1 = If Ch0x.DeviceStatus.HARTCommFail is 1, then this device is sending out HART messages to attempt to establish communication with a HART device.

GeneralStatus bit 1

HART communication failure, device not found, or HART not enabled.

If this bit is 1, none of the other data in the HART part of the input tag are valid.

GeneralStatus bit 2

0 = Passthrough message reply is not ready for query service.

1 = Passthrough message reply is ready for query service.

GeneralStatus bit 3

0 = Analog current measurement matches the current value reported by the field device over the HART network.

1 = Analog current measurement does not match the current value reported by the field device over the HART network.

GeneralStatus bit 4

If this bit is 1, it indicates that the field device configuration changed and new configuration information can be obtained from the 1718/1719 HART device. Use CIP MSG GetDeviceInfo to retrieve the new configuration information and clear this bit.

GeneralStatus bit 5

0 = No maintenance required.

1 = Maintenance required.

Bit 0 of extended device statuu (if using command 9, or from command 48, if supported).

GeneralStatus bit 6

If this bit is 1, it indicates that new device diagnostic information is available. Use a CIP Message with Service 4C to retrieve the new diagnostic information.

GeneralStatus bit 7

0 = Good

1 = An issue with HART data from the field device on this channel exists.

Examples that can cause this issue include, HART not enabled, HART device not connected, and HART communication failure due to noise.

Examples of field device status conditions that can cause this issue include, device malfunction, PV out of limits, loop current saturated, and loop current fixed.

HART communication status byte or Response code from a recent HART reply.

For more information, see the Response Codes and Field Device Status table in the 1719 Ex I/O User Manual, publication 1719-UM001.

HART device status byte from a recent HART reply. This value indicates the health of the HART field device.

For more information, see the Field Device Status Bit Mask Definitions table in the 1719 Ex I/O User Manual, publication 1719-UM001.

FieldDeviceStatus bit 0

0 = Good

1 = The primary variable is beyond its operating limit.

FieldDeviceStatus bit 1

0 = Good

1 = A device variable that is not mapped to the PV is beyond its operating limit.

FieldDeviceStatus bit 2

0 = Good

1 = The loop current reached its upper or lower endpoint limit and cannot increase or decrease any further.

FieldDeviceStatus bit 3

0 = Good

1 = The loop current is being held at a fixed value and is not responding to process variations.

FieldDeviceStatus bit 4

0 = Good

1 = More status information is available, which can be retrieved using command 48, "Read additional device status".

FieldDeviceStatus bit 5

0 = Good

1 = A power failure or device reset occurred.

FieldDeviceStatus bit 6

0 = Good

1 = An operation was performed that changed the device configuration.

FieldDeviceStatus bit 7

0 = Good

1 = The device detected a serious error or failure that compromises device operation.

0 = Good

1 = PV auto-configuration failed

Dynamic variable used for mapping a HART device variable.

Dynamic variable used for mapping a HART device variable.

Dynamic variable used for mapping a HART device variable.

Dynamic variable used for mapping a HART device variable.

Device variable status value that indicates the quality of the associated device variable.

For more information, see the HART PV, SV, TV, and FV Status Values table in the 1719 Ex I/O User Manual, publication 1719-UM001.

Device variable status value that indicates the quality of the associated device variable.

For more information, see the HART PV, SV, TV, and FV Status Values table in the 1719 Ex I/O User Manual, publication 1719-UM001.

Device variable status value that indicates the quality of the associated device variable.

For more information, see the HART PV, SV, TV, and FV Status Values table in the 1719 Ex I/O User Manual, publication 1719-UM001.

Device variable status value that indicates the quality of the associated device variable.

For more information, see the HART PV, SV, TV, and FV Status Values table in the 1719 Ex I/O User Manual, publication 1719-UM001.

Engineering units for the HART PV.

Engineering units for the HART PV.

Engineering units for the HART PV.

Engineering units for the HART PV.

-1.0E+11...+1.0E+11