Interpretation Of Nvostatus - Honeywell Apex Technical Handbook

MAN0604_Issue 09_02-2013
2110M8030
APPENDIX A - SPECIFICATIONS
A.4.6 Interpretation of nvoStatus
The object status contains a great deal of information about the status of a node. Several bits have
meaning assigned which is specific to Honeywell Analytics.
For example fault_alert (Honeywell nomenclature) has been mapped to mechanical_fault
(LonMark nomenclature).
The following table lists all of these assignments. Blank entries correspond to unimplemented
status bits.
Status Field
object_id (16 bits)
invalid_id
invalid_request
disabled
out_of_limits
open_curcuit
out_of_service
mechanical_fault
feedback_failure
over_range
under_range
electrical_fault
unable_to_measure
comm_failure
fail_self_test
self_test_in_progress
locked_out
manual_control
in_alarm
in_override
report_mask
programming_mode
programming_fail
alarm_notify_disable
Node 0 interpretation
0
object_id>1
Unimplemented request made
Network reporting inhibited
Warning alert active
Not in normal mode
Fault alert active
Concentration > full scale
Sensor is not connected
Error inside LIFELINE II
Error inside LIFELINE II
Remote access unavailable
Alarm level 1 is active
nvoStatus mask report
Request made could not be implemented
Alarm reporting over network is disabled.
118
Apex