Bacharach LonWorks FT-10 - Manual (Page 9)

9 of 18
LonWorks Objects and Network Variables
The adapter contains one Node Object, sixteen Zone Objects, one General Status Object,
and one Alarm Control Object. There is one Zone Object for each refrigerant sampling
zone.
Object 0 – The Node Object
Network input variable nviRequest allows the user to request information from
different objects in the node. The nviRequest contains an object ID field that specifies
which object receives the request. The following request types are supported:
1. RQ_NORMAL (value 0) – This request is accepted by any of the objects for
compatibility with LonMark requirements, but the request does not cause any
change in the objects whatsoever. It does cause the status of the specified object
to be reported through nvoStatus (works identically to RQ_UPDATE_STATUS).
2. RQ_UPDATE_STATUS (value 2) – Requests the status of the object specified in the
object ID field. If sent to the Object Node (Node 0), the status response contains the
status bits of all the node objects logically ORed together. The status response is
returned through nvoStatus.
3. RQ_REPORT_MASK (value 5) – Requests the object to report which status bits it
supports. All objects support the same status bits, thus the report mask returns
the same value no matter which object is requested. These are the status bits
supported:
mechanical_fault (for no flow or excessive HGM internal temperatures)
electrical_fault (for HGM internal electrical faults)
unable_to_measure (any time can’t get HGM data for whatever reason)
comm_failure (HGM-to-adapter failure or adapter internal failure)
in_alarm (when sampled PPM exceeds an alarm threshold on any zone)