Dap4 LonWorks Interface Instructions
Document number 600-000-966 Ver. 3
5
Fig. 2 Fig. 3
Fig. 4 Fig. 5
6. Connection to the LonWorks
®
network
The physical connection to the LonWorks
®
network is performed using the connector
with removable terminals fitted on the board, according to the Echelon
®
instructions
and specifications. For further information on installation, maintenance, the cross-
section and type of cable, refer to the LonWorks
®
literature.
Important Note: Data Aire Dap4 Lon interface uses a Carel Lonworks card; if there is
existing equipment provided by others that uses the same Carel Lonworks card then
the device interface file (XIF) of dap4 must be manually loaded during the
commissioning process otherwise Lon network may use an incorrect device interface
template on dap4 that leads to erroneous data.
Service pin
To activate the
service pin
, simply momentarily short-circuit the two
pins
on the
board (see Fig. 1 and no.3) with the tip of a screwdriver or a similar tool.
The
service pin
must only be activated during the installation of the node. When
the
pin
is activated, the node sends a
broadcast
message over the LonWorks®
network, containing the information required for identification. There is sticker on
the card to indicate the Lon card neuron ID, this neuron ID can be used to
manually commission the card if service pin does not work.
After you can commission the card and the red LED is lit, reset the dap4 (power off then
back on). The Red LED should go off after dap4 starts up. If dap4 does not get reset
after commissioning, the erroneous data may appear.
WINK event
A generic supervisor can send the WINK command to a specific node on the
LonWorks
®
network. This generates an event that the application on the specific
node can respond to with any action decided by the programmer.
