HART communication and mismatch errors (CHARMs I/O)

Tables A and B below list the values expected for diagnostic parameters when the following HART communication and mismatch error conditions are detected by DeltaV Diagnostics:

HART server error
HART communication error
Device revision mismatch
Loop current mismatch
Scale mismatch
Diagnostics in progress
Non-Primary Variable out of limits
Stale

Table: HART communication and mismatch errors (CHARMs I/O) - Table A
Parameter	HART server error⁽¹⁾	HART communication error	Device revision mismatch	Loop current mismatch
OINTEG	BAD	BAD	—	BAD⁽²⁾⁽³⁾
HINTEG	—	TRUE	—	—
NO_COMM	—	TRUE	—	—
DEV_CFG_MISMATCH	—	—	TRUE⁽³⁾
DISPARITY_DETECT	—	—	—	TRUE⁽²⁾⁽³⁾
HART_FIELD_VAL⁽⁴⁾		—	—	—
HART_PV	BadNoCommLUV	BadNoCommLUV	—	—
HART_SV	BadNoCommLUV	BadNoCommLUV	—	—
HART_TV	BadNoCommLUV	BadNoCommLUV	—	—
HART_FV	BadNoCommLUV	BadNoCommLUV	—	—
HART_DV_SLOT0⁽⁵⁾	BadNoCommLUV	BadNoCommLUV	—	—
HART_DV_SLOT1⁽⁵⁾	BadNoCommLUV	BadNoCommLUV	—	—
HART_DV_SLOT2⁽⁵⁾	BadNoCommLUV	BadNoCommLUV	—	—
HART_DV_SLOT3⁽⁵⁾	BadNoCommLUV	BadNoCommLUV	—	—

⁽¹⁾ Including an invalid connection, a decommissioned or missing device, etc.

⁽²⁾ Unless ignored by configuration.

⁽³⁾ Unless disabled by configuration.

⁽⁴⁾ Any condition that causes the analog value FIELD_VAL_PCT to have bad integrity or status will also cause HART_FIELD_VAL to have bad integrity and status.

⁽⁵⁾ This channel parameter is not supported in devices implementing the HART Protocol prior to revision 7. Therefore, any HART communication or mismatch error appearing in DeltaV Diagnostics for a device that implements an earlier level of the HART protocol can be disregarded.

Table: HART communication and mismatch errors (CHARMs I/O) -Table B
Parameter	Scale mismatch	Diagnostics in progress	Update Warning, Busy, Access Restricted, Delayed Response
OINTEG (HART integrity)	BAD	BAD	—
HINTEG	—	—	—
NO_COMM	—	—	—
DEV_CFG_MISMATCH	—	—	—
DISPARITY_DETECT	—	—	—
HART_FIELD_VAL⁽⁴⁾	BadConfigError	BadOutOfService
HART_PV	—	BadOutOfService	UncertainNonSpecific⁽¹⁾
HART_SV	—	BadOutOfService	UncertainNonSpecific⁽¹⁾
HART_TV	—	BadOutOfService	UncertainNonSpecific⁽¹⁾
HART_FV	—	BadOutOfService	UncertainNonSpecific⁽¹⁾
HART_DV_SLOT0⁽⁵⁾	—	BadOutOfService	UncertainNonSpecific⁽¹⁾
HART_DV_SLOT1⁽⁵⁾	—	BadOutOfService	UncertainNonSpecific⁽¹⁾
HART_DV_SLOT2⁽⁵⁾	—	BadOutOfService	UncertainNonSpecific⁽¹⁾
HART_DV_SLOT3⁽⁵⁾	—	BadOutOfService	UncertainNonSpecific⁽³⁾

⁽¹⁾ Whenever an update warning is returned to Command 3, 9, or 33, only the variables affected are set to BAD.