Honeywell IAQPoint2 Guide De Démarrage Rapide page 77

IAQPoint2™
Relay Output Functional Block
This facilitates controlling the internal relay as a binary output� LonMark calls this
an open loop actuator� Note that this input is only effective if the optional relay
is present and the local user interface is appropriately configured to listen via the
menu Configure\Output\Set Relay Source�
Virtual Functional Block
This object is a catchall for network variable that don't belong to any of the
LonMark functional blocks� This has two NVOs� nvoHeartBeat increments every
two seconds to facilitate confirmation that the IAQPoint2 device is working
properly� nvoChkSum is for internal Honeywell use�
Node Object
This LonMark object is required by LonMark� It is used by Echelon's LonMaker
software to control the LonMark functional blocks� Most other software packages
will not use this�
Network Commissioning
Commissioning a LonWorks network generally requires knowing the neuron ID
of each device� There are two ways of finding the neuron ID of the IAQPoint2�
Both start with the Configure\Fieldbus menu� Pressing the button [Send SERVICE
Msg] causes the IAQPoint2 to broadcast a packet containing its neuron ID�
Network management tools such as Echelon LonMaker can detect this packet�
Alternatively, the Fieldbus menu also displays the neuron ID� This may be typed
into the network management tool directly�
"Wink"
The LonWorks protocol defines a "Wink" packet� This is typically used to confirm
that the correct device is being addressed� Network management tools such
as Echelon LonMaker can transmit winks� LonWorks devices are to respond by
identifying themselves� An IAQPoint2 will respond to a wink by displaying the wink
screen for four seconds as shown in Figure 30� This feature is inhibited during
simulation or gas calibration�
LonWorks "Wink"
LonWorks
"Wink"
Received
Figure 30. LonWorks "wink"
71