Setup and adjustments
Configuring N2 communications
N2-capable controllers support the full range of
possible N2 device addresses provided by the N2
protocol standard (1-254).
To configure a controller to communicate using the N2
protocol, complete the following steps:
1. Disconnect the 240 VAC supply from the
controller.
2. Set the address switches to the desired N2
address. For details about setting a device
.
3. Reconnect the 240 VAC supply to the controller.
4. Using an SA bus connection, download the
firmware and controller application file configured
for N2 to the controller.
Switching the Communications Protocol
from N2 to MS/TP
For N2 sites that are converting to BACnet MS/TP,
you can switch the communications protocol of N2-
configured MS/TP controllers back to BACnet MS/TP.
To switch the ATC operating in N2 mode back into
BACnet MS/TP mode, complete the following steps:
1. Disconnect the 240 VAC supply from the
controller.
2. Set the address switches to the desired BACnet
MS/TP address. For details about setting a device
.
3. Reconnect the 240 VAC supply to the controller.
4. Using an SA Bus connection, download a
controller application file configured for BACnet
MS/TP to the controller.
Setting the device address
Equipment controllers are master devices on MS/TP
(FC or SA) buses. Before you operate controllers on a
bus, you
must
set a valid and unique device address
for each controller on the bus. You set the ATC device
address by setting the positions of the Device Address
switch on the front of the controller.
The
table describes the valid
device addresses for communications bus applications.
The device address must match the device address
defined in the Controller Configuration Tool (CCT)
under
Define Hardware > Network Settings
.
To set the device addresses on the ATCs, complete the
following steps:
1. Set a unique and sequential device address for
each of the equipment controllers connected on
the FC or SA Bus.
2. To ensure the best bus performance, set
sequential device addresses with no gaps in the
device address range (4, 5, 6, 7, 8, 9, and so on).
The equipment controllers do not need to be
physically connected on the bus in their numerical
device address order.
Setting up a local display
ATC models do not have an integral display, but can be
connected to a DIS1710 Local Controller Display. For
detailed information about setting up and operating
a remotely connected DIS1710 display, refer to the
DIS1710 Local Controller Display Technical Bulletin
(LIT-12011270) .
Input/Output Wiring Validation
The ATCs ship with a default state that can assist in
validating the wiring of the input and output terminals
prior to download of an application file. When the
controller is powered on in this state, the Fault LED will
flash in a pattern of two quick blinks and then a long
pause (see Table 6).
To make use of this feature, make sure that you set
the device address and wire the input and output
terminals. Apply power to the ATC and connect to the
device with either a MAP Gateway or MS-DIS1710-0
Local Display to view the points in the controller. The
ATC reports an Operational status even though there
is no true application loaded. CCT will not be able to
commission or upload the device as a result until a
true application is downloaded. The application name
displayed will be the address of the controller followed
by the model of the controller and “Default State”.
For example, an ATC with device address set to 8 would
have the default state application name of “8-ATC
Default State”.
The default state creates I/O points for all connections
on the input and output terminals. It assumes all
Universal Inputs (UIs) are Nickel temperature sensors.
All Configurable Outputs (COs) are treated as Binary
Outputs (BOs) with an initial value of 0. The default
state also takes input from a Network Sensor at
address 199. If there is no connected Network Sensor,
the startup of this default state will be delayed by
ATC1510 Advanced Terminal Unit Controller Installation Guide
13
