SPYDER® BACNET® PROGRAMMABLE CONTROLLERS
5 63-1328—05
Communications
Each controller uses a BACnet MS/TP communications port.
The controller’s data is presented to other controllers over a
twisted-pair MS/TP network, which uses the EIA-485 signaling
standard capable of the following baud rates: 9.6, 19.2, 38.4,
76.8, or 115.2 kilobits per second (configured at global
controller). The Spyder BACnet controllers are master devices
on the MS/TP network. Each Spyder BACnet controller uses a
high-quality EIA-485 transceiver and exerts 1/4 unit load on
the MS/TP network.
Cabling should be selected that meets or exceeds the BACnet
Standard which specifies the following: an MS/TP EIA-485
network shall use shielded, twisted-pair cable with
characteristic impedance between 100 and 130 ohms.
Distributed capacitance between conductors shall be less
than 100 pF per meter (30 pF per foot). Distributed
capacitance between conductors and shield shall be less that
200 pF per meter (60 pF per foot). Foil or braided shields are
acceptable. The Honeywell tested and recommended MS/TP
cable is Honeywell Cable 3322 (18 AWG, 1-Pair, Shielded,
Low Cap, Plenum cable), alternatively Honeywell Cable 3251
(22 AWG, 1-Pair, Shielded, Plenum cable) is available and
meets the BACnet Standard requirements
(www.honeywellcable.com).
The BACnet MS/TP network is polarity sensitive. The
maximum BACnet MS/TP network Bus segment length is
4,000 ft. (1,219 m) using recommended wire. Repeaters must
be used when making runs longer than 4,000 ft. (1,219 m). A
maximum of three repeaters can be used between any two
devices.
MS/TP MAC Address
The MS/TP MAC address for each device must be set to a
unique value in the range of 0-127 on an MS/TP network
segment. DIP switches on the Spyder BACnet controller are
used to set the controller's MAC address.
Device Instance Number
The Device Instance Number must be unique across the
entire BACnet system network because it is used to uniquely
identify the BACnet devices. It may be used to conveniently
identify the BACnet device from other devices during
installation. The Spyder BACnet Controllers Device Instance
Number is automatically set when it is added to a
WEBStation-AX project. The Device Instance Number can be
changed by the user, which may be necessary when
integrating with a third party or when attempting to replace an
existing controller and it is desired to maintain the existing
Device Instance Number.
NOTE: For complete instructions on how to set the MS/
TP MAC address or set the Device Instance Num-
ber refer to the Installation Instructions, form 62-
0310.
Termination Resistors
Matched terminating resistors are required at each end of a
segment bus wired across (+) and (-). Use matched precision
resistors rated 1/4W ±1% / 80 - 130 Ohms. Ideally, the value
of the terminating resistors should match the rated
characteristic impedance of the installed cable. For example, if
the installed MS/TP cable has a a listed characteristic
impedance of 120 Ohm, install 120 Ohm matched precision
resistors.
NOTE: The controller does not provide any network
biasing.
Shield Terminating
Following proper MS/TP cabling shield grounding procedures
is important to minimize the risk of communication problems
and equipment damage caused by capacitive coupling.
Capacitive coupling is caused by placing MS/TP cabling close
to lines carrying higher voltage. The shield should be
grounded on only one end of the MS/TP segment (typically
the router end). Tie the shield through using the SHLD
(terminal 4) on the Spyder BACnet Controller.
Sylk
™
Bus
Sylk is a two wire, polarity insensitive bus that provides both
18 VDC power and communications between a Sylk-enabled
sensor and a Sylk-enabled controller. Using Sylk-enabled
sensors saves I/O on the controller and is faster and cheaper
to install since only two wires are needed and the bus is
polarity insensitive. Sylk sensors are configured using the
latest release of the Spyder Tool for WEBPro and
WEBStation.
Table 4. BACnet Status LED States.
BACnet LED Status Status or Condition
Solid on Controller has power, loader is not
running.
Solid on, blinking off
once in 2.5 sec.
Controller is in reflash mode, no MS/
TP communication.
Solid on, blinking off
twice in 2.5 sec.
Controller is in reflash mode, MS/TP
communication present.
Solid on, blinking off
three times in 2.5 sec.
Controller is in reflash mode, MS/TP
communication data transfer in
progress.
Solid off, there is no
power
No power to processor, LED
damaged, low voltage to board, or
loader damaged.
Solid off, blinking on
once in 2.5 sec.
Controller is running, no MS/TP
communication.
Solid off, blinking on
twice in 2.5 sec.
Controller is running, MS/TP
communication present.
Solid off, blinking on
three times in 2.5 sec.
Controller is running, MS/TP
communication data transfer in
progress.
To Next Page
Loading...
