Carrier Fan Coil, Руководство по интеграции

Страница: 20 / 50

Communications wiring
Fan Coil CARRIER CORPORATION ©2020
Integration Guide All rights reserved
16
4
Set both DIP switches 1 ON and 2 OFF for 38.4 kbps baud.
NOTE Use the same baud rate for all devices on the network segment.
5
Set both DIP switches 3 and 4 ON for LON.
The following example is set for 38.4 kbps and LonWorks.
CAUTION The controller must be OFF before being connected.
6
Connect the LonWorks network to the LonWorks Option Card's 2-pin Net port.
NOTE The 2-pin Net port provides TP/FT-10 channel compatibility. The TP/FT-10 or "Free Topology" network
type is polarity insensitive . Use 24 to 16 AWG twisted pair wire.
7
Turn on the power for the Fan Coil by connecting power terminals.
8
Commission the controller for LonWorks communication. See instructions below.
Commissioning the controller for LonWorks communication
Before a device can communicate on a LonWorks network, it must be commissioned. Commissioning allows the
system integrator to associate the device
hardware with the LonWorks system’s network layout diagram. This is
done using the device’s uni que Neuron ID.
A network management tool such as Echelon’s LonMaker is used to commission each device, as well as, to assign
addressing. Specific instructions regarding the commissioning of LonWorks devices should be obtained from
documentation supplied with the LonWorks Network Management Tool.
When a new device is first commissioned onto the LonWorks network, the system integrator must upload the
device’s Exte rnal Interface File (XIF) information. LonWorks uses the XIF to determine the points (network
variables) that are available from a device. The Fan Coil has a set of predefined network variables. These
variables can be bound or accessed by the Network Management Tool.
The Browse feature of the Network Management Tool allows you to read real-time values from the Fan Coil. The
Network Management Tool allows you to test integration prior to binding the controller's network variables to other
LonWorks nodes.