| |
| Quick Help
The
object name, value, and status are shown for a list of objects starting
with the number entered at the top of the page. Click Prev/Next to
scroll through the list. Click on the object number in the first column
to change name or out-of-service state. Binary Value objects may
be both a source and destination for some other BACnet or
Modbus device. The source of data for the Value object will be
reading from a remote device when associated with a Read Map. The
destination of data for the Value object will be writing to a remote
device when associated with a Write Map. Click on the object number in
the first column for more detail including the links to any client maps
providing data to or receiving data from this object. The
Value object may be simultaneously associated with both Read and Write
maps pointing to the same remote device object. When this Value object
receives new data (from any source), this data will be written to
the mapped remote device before any subsequent read from the same
device. Thus the Value data is not discarded by the read operation
before the new data can be written. Out
of Service means any mapped remote device will be neither read or
written. Reading and writing will resume when placed back in service. Reliability codes may be any of the following: Modbus client/master, no response from slave (64) Modbus client/master, crc error (65) Modbus exception, illegal function code (66) Modbus exception, illegal data address (67) Modbus exception, illegal data value (68) Modbus exception, code+65, rarely used (69..79) Local device, configuration property fault (80) Faulty Modbus packet(81) BACnet client, device timeout (82) BACnet client, error returned by server (83) Host update timeout (84)
Status flags A,B,C,D indicate the following, 0 meaning not true, 1 meaning true: A = in alarm B = fault C = overridden D = out of service | | |