Automated Logic UNI/32 Owner's manual

Automated Logic Corporation •1150 Roberts Blvd. •Kennesaw, GA 30144 • 770/429-3000 •770/429-3001 Fax •
www.automatedlogic.com • Copyright 2001 Automated Logic Corporation. All rights reserved. Automated Logic, the
Automated Logic logo, SuperVision, Eikon, Alert, and InterOp are registered trademarks of Automated Logic
Corporation. BACnet®is a registered trademark of ASHRAE. All other brand and product names are trademarked by
their respective companies.
Technical Instructions
UNI/32
Using the UNI/32 2
Specifications 2
Mounting 3
Power Wiring 3
Communicating with the UNI/32 4
Connecting the UNI/32 to the U-cards 4
Connecting the UNI/32 to an ARC156, MS/TP, or Legacy CMnet network segment 5
Addressing 5
Transferring Memory 6
Transferring Memory in WebCTRL 6
Transferring Memory in SuperVision 7
Using Flow Sensors 7
Troubleshooting Tips 7
Communicating with the Workstation Using SuperVision 8
Formatting the Module 8
LEDs 9
Protection 9
Production Date 9

Revised 11/26/01 • UNI/32 2 © 2001 Automated Logic Corporation
Using the UNI/32
The UNI/32 provides the communications
link between an ARC156 or Legacy CMnet
network segment and up to 32 U-cards. The
UNI/32 module can store one module driver
and up to 32 Graphic Function Blocks (GFBs),
depending on the size of the GFBs.
A UNI/32 module contains a 32-bit
microprocessor, flash memory, and non-
volatile RAM (stores data even during a
power failure) for executing GFBs. The
UNI/32 can also communicate with an
optional BACview keypad/display using the
Keypad Display port and can communicate
with a laptop computer running WebCTRL or
SuperVision using the UNI/32’s Access port
and an APT.
The module driver varies depending on what
software you are using. WebCTRL requires
the DRV_UNI32 module driver for the UNI/32;
SuperVision requires the UNM module driver.
See the appropriate module driver document
at http://www.automatedlogic.com or on the
SupportPlus CD for more information.
See Figure 1 for a system architecture
diagram.
CAUTION Changes or modifications to this
unit not expressly approved by the party
responsible for compliance could void the
user’s authority to operate equipment.
NOTE This equipment has been tested and
found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC
Rules. These limits are designed to provide
reasonable protection against harmful
interference when the equipment is operated
in a commercial environment. This
equipment generates, uses, and can radiate
radio frequency energy and, if not installed
and used in accordance with the instruction
manual, may cause harmful interference to
radio communications. Operation of this
equipment in a residential area is likely to
cause harmful interference in which case the
user will be required to correct the
interference at his own expense.
Specifications
Power 24VAC ± 10%, 50-60Hz, 0.3A (7.2VA)
power consumption (single Class 2
source only, 100VA or less).
Communication For WebCTRL, 156 kbps
BACnet-over-ARCNET and 9600 bps or
38.4 kbps EIA-485 BACnet MS/TP. Two
EIA-485 ports for BACnet MS/TP Unet
communication (9600 bps or 38.4 kbps).
For SuperVision, 156 kbps BACnet-over-
ARCNET or 9600 bps or 38.4 kbps Legacy
CMnet. Access Port: 9600 bps or 38.4
kbps EIA-485. Two EIA-485 ports for
BACnet MS/TP Unet communication
(9600 bps or 38.4 kbps).
Environmental Operating Range 0° to
130°F (-17.8° to 54.4°C); 10 to 90%
relative humidity, non-condensing.
Status Indication Visual (LED) status of
network and Unet communication,
running, errors, and power.
Memory 1MB Flash memory and 2MB non-
volatile battery-backed RAM.
Figure 1. System Architecture
MX-Line
CMnet (ARC156)
U-Cards
UNI/32
U-Line: 9600 bps or 38400 bps
TNPB
LGRM-E
For WebCTRL, BACnet/IP.
For SuperVision, BACnet/Ethernet.
S-Line
MX-Line

Revised 11/26/01 • UNI/32 3 © 2001 Automated Logic Corporation
Real Time Clock A battery-backed real
time clock that keeps track of time in the
event of a power failure.
Protection Voltage, current, and ESD
protection on incoming power and
CMnet.
Bat t e ry Lithium 3V Primary Battery, Type
BR2330 (not replaceable). Provides a
minimum of 10,000 hours of data
retention during power outages.
Listed by UL 916 (PAZX), cUL C22.2 No.
205-M1983 (PAZX7), FCC Part 15 -
Subpart B - Class A.
Mounting
Screw the UNI/32 into an enclosed panel
using the mounting holes provided on the
cover plate. Be sure to leave about 2 inches (5
centimeters) on each side for wiring.
Power Wiring
CAUTION The UNI/32 module is a Class 2
device (less than 30VAC, 100VA maximum).
Take appropriate isolation measures when
mounting the UNI/32 module in a control
panel where non-Class 2 devices (for
example, 120VAC) or wiring are present.
You can power several modules from the
same transformer if you maintain the same
polarity.
The UNI/32 has an operating range of
21.6VAC to 26.4VAC. If voltage measured at
the module’s power input terminals is outside
this range, the module may not work
properly.
1. Turn the module’s power off. This
prevents the module from being powered
up before the proper voltage is verified.
2. Make sure the 24VAC power source is off.
3. Connect the power wires to the module’s
power terminals labeled Ground and
24VAC.
4. Apply power to the transformer.
5. Make sure that 24VAC is present at the
module’s power input terminals.
6. Set the module’s address. Refer to
“Addressing” on page 5 for details about
setting the address.
7. Turn the module’s power switch on.
Figure 2. Module Dimensions and Layout
TYPE: COM32
E143900
Open Energy
Management Equipment
88FO
R
Net +
Net -
Optional shield
38.4K
On
1
2
4
8
16
32
64
9600CMnet baud
Diag transmit
Diag receive
Unet transmit
Unet receive
CMnet transmit
CMnet receive
Error
Run
9600/38.4k
ARC156
port
Access
connection
CMnet
(Module)
Address
CMnet
button
Format
CMnet Mode
Unet 1 Connection
Optional Shield
-
+
-
+
EIA-485
N/C
N/C
N/C
UNI
24 Vac
Ground
Only
Conductors
Use Copper
0.3A
7.2VA
50-60 Hz
24 Vac
Class 2
UseSingleClass2Only
Off On Connector
Power
Indicator
Power
Switch
Power
Port
Diag
gnd
dtr
tx
rx
dcd
5
4
3
2
1
9
8
7
6
n/c
n/c
+10v
n/c
EIA-232
Unet 2 Connection
Auxiliary
device
port
Over ARCNET156 KBaud
BACNet
61/4"
15.9 cm
11/8"
2.9 cm
71/8"
18.1 cm
15/8"
4.1 cm
Power Switch
Format Button
Addressing
DIP Switches
Diag Port
Keypad Display Port
LED Indicators
Access Port
UNI/32
2M
Unet Connection Port
Configuration Jumpers
Unet Connection Port
Connection
Port
CMnet

Revised 11/26/01 • UNI/32 4 © 2001 Automated Logic Corporation
When the module turns on, the Power,
Run and Error LEDs turn on and the Run
and Error LEDs begin blinking. The Error
LED then turns off. (See “LEDs” on page 9
for more information about LED signals.)
Communicating with the
UNI/32
The UNI/32 connects to the CMnet through
an EIA-485 CMnet port. A five-pin EIA-485
port provides two connections to U-cards on
the Unet. You can connect an optional
BACview1or BACview2keypad display unit to
the keypad display port (see Figure 2 on page
3).
NOTE The EIA-232 port, labeled Diag Port
in Figure 2 on page 3, is reserved for future
diagnostic capabilities. This feature is not yet
available.
You can use WebCTRL or SuperVision to
transfer memory to the UNI/32. You can
connect a portable computer running
SuperVision to the UNI/32 using the module’s
Access port. For more information about
connecting to a workstation, refer to
“Communicating with the Workstation Using
SuperVision” on page 8.
Connecting the UNI/32 to the U-
cards
The UNI/32 supports up to 32 U-cards. The
baud rate of the Unet is set on the module
driver Properties page in WebCTRL or
Parameter page in SuperVision. Refer to the
appropriate module driver document for more
information.
Automated Logic Corporation recommends a
specific wire for both power and
communications on the Unet. This wire,
which contains a pair of 14AWG wires for
power and a pair of 22AWG wires for
communication, is available from:
Magnum Cable Corporation
Cleveland, OH 44110-0500
[phone]
Product number A3U-LINE
Note that the communication wire is
unshielded. Shielded cable is not required for
the Unet.
Use the Unet connection port to connect the
UNI/32 to the U-cards. The Unet connection
port can make two connections to the Unet,
as shown in Figure 3. Make sure the Unet
connection port configuration jumpers are set
to UNI and EIA-485 (see Figure 4).
Make sure that all U-cards and the TNPB use
the same polarity throughout the subnet. You
can verify that the UNI/32 is communicating
with the subnet by making sure the Unet
transmit and receive LEDs are active.
When adding a new U-card to an existing
subnet, you must transfer memory to the
UNI/32 before the new card is recognized.
Figure 3. Communication wiring
Figure 4. Unet configuration jumpers
NET+
NET- UNI
NET+
NET-
ARC156
network segment
NET+
NET-
Unet 1 Connection
Unet 2 Connection
N/C
EIA-485
UNI
N/C
N/C

Revised 11/26/01 • UNI/32 5 © 2001 Automated Logic Corporation
Connecting the UNI/32 to an
ARC156, MS/TP, or Legacy CMnet
network segment
The UNI/32 supports several
communications options through its CMnet
connection port.
On a WebCTRL system, the UNI/32 can
connect to a legacy CMnet at 9600 bps or 38.4
kbps, to a BACnet-over-ARCNET network
segment at 156 kbps, or to a BACnet MS/TP
at 9600 bps or 38.4 kbps.
NOTE The UNI/32 has the ability to connect
to ARC156, BACnet MS/TP, or Legacy
networks. For maximum performance, ALC
recommends that the UNI/32 be configured
for ARC156. All modules on the CMnet must
already be downloaded with module driver
v1.2 or later to use BACnet MS/TP.
On a SuperVision system, the UNI/32 can
connect to a legacy CMnet at 9600 bps or 38.4
kbps or to a BACnet-over-ARCNET network
segment at 156 kbps.
NOTE BACnet MS/TP is not available on a
SuperVision system.
When communicating on an ARC156 CMnet,
use an A3ARC156 wire available from
Magnum Cable Corp. Use a dedicated 22AWG
to 18AWG twisted pair wire for legacy CMnet
(EIA-485) wiring. For more information about
CMnet wiring, refer to the Technical Handbook
or to the ARC156 CMnet Wiring Technical
Instructions.
To set the baud rate at 156 kbps (when using
an ARC156 CMnet), set the baud rate jumper
to Arc156 (see Figure 5).
To set the baud rate at 38.4 kbps, set the baud
rate jumper to 9600/38.4K, and set the first
switch on the eight-position DIP switch to
38.4K (see Figure 6).
To set the baud rate at 9600 bps, set the baud
rate jumper to 9600/38.4K, and set the first
switch on the eight-position DIP switch to
9600 (see Figure 6).
You can verify that the UNI/32 is
communicating on the CMnet by making sure
the CMnet transmit and receive LEDs are
active.
Addressing
The UNI/32 has an eight-position DIP switch
for assigning the module’s address. Before
setting or changing the address, make sure
the UNI/32’s power is off, since the UNI/32
only reads the address when the module is
turned on.
• For WebCTRL systems, use the switches
to assign the device’s MAC (medium
Figure 5. Setting the CMnet baud rate to 156
kbps
Figure 6. Setting the CMnet port baud rate to
38.4 kbps or 9600 bps
Arc156
9600/38.4K
CMnet Baud 9600
64
32
16
8
4
2
1
38.4k

Revised 11/26/01 • UNI/32 6 © 2001 Automated Logic Corporation
access control) address on the BACnet-
over-ARCNET network segment. The
switches define the MAC address
portion of the device’s BACnet address
which is composed of the network
address and the MAC address.
• For SuperVision systems, use the
switches to assign the device’s module
number.
After changing the address, you must transfer
memory to the module. Refer to the section
“Transferring Memory”.
Switches two through eight of the DIP switch
are labeled with addressing values. The
values of the switches in the on position are
added together to determine the module’s
address. For example, in Figure 7 switch
numbers six and seven are both on, giving the
module an address of six.
Transferring Memory
You should download memory whenever you
make changes to your modules (for example,
change the module number, upgrade the
module driver, or change the FB).
The UNI/32 module can store one module
driver and up to 32 Graphic Function Blocks
(GFBs), depending on the size of the GFBs. All
GFBs stored in the UNI/32 must be made
using the Zone GFB option in Eikon for
WebCTRL if you are using WebCTRL or in
Eikon if you are using SuperVision. Refer to
the Eikon for WebCTRL User’s Guide or the
Eikon User’s Guide for more information.
NOTE This type of download should be
performed with caution. When the module is
automatically restarted before and after
transferring memory, any equipment
controlled by the module is shut down and
restarted. Downloading memory also
overwrites all Function Blocks in the module
causing the module to lose any stored data.
Transferring Memory in WebCTRL
If you are using WebCTRL to transfer memory,
you must use the DRV_UNI32 module driver.
You must be logged in to WebCTRL with the
appropriate privilege to download memory.
For more information about using WebCTRL,
refer to the WebCTRL User’s Guide.
1. Click the CFG button at the bottom of the
navigation pane.
2. Click Download in the CFG tree control.
3. Click the Memory, Parameters, or
Schedules boxes, depending on what you
want to download.
NOTE A memory download includes a
parameter and schedule download.
4. Expand the tree in the action pane, click
the module you want to download to,
then click Add. Click on and Add any
other modules you want to download to.
5. Click the Execute Download button.
If any downloads failed, they are listed in
the Failures section under the tree in the
action pane. To retry a failed download,
click on the module in the Failures list,
click Add, and click the Execute
Download button again. If you do not
want to retry a failed download, click the
Clear Failures button.
Figure 7. Setting the module’s address
CMnet Baud 9600 OFF ON
32
16
8
4
2
1
On
38.4k
CMnet
Address
(Module)
64

Revised 11/26/01 • UNI/32 7 © 2001 Automated Logic Corporation
NOTE Since a failed download indicates
a system problem, you should never clear
a failure. Locate and resolve the problem,
then retry the download.
6. Click the Properties button to refresh the
screen. This removes the items from the
Download Items list.
Transferring Memory in SuperVision
If you are using SuperVision to transfer
memory, you must use SuperVision version
2.6b or later, FBLINK version 2.7a or later, and
the UNM module driver. For more information
about using SuperVision, refer to the
SuperVision User’s Guide.
The first memory transfer to the UNI/32 takes
longer than subsequent memory transfers.
1. Connect your workstation or portable
computer to the UNI/32. Refer to
“Communicating with the Workstation
Using SuperVision” on page 8.
2. Navigate to the module driver and look at
the module status report in SuperVision to
make sure the module type and number
agree with the module.
• To view the module status report in
SuperVision v3.0, click Tools-
Troubleshooting-Module Status.
• To view the module status report in
SuperVision v2.6b, press the Esc key,
type MO , , module address,15
and press Enter.
3. Transfer memory to the module.
• In SuperVision v3.0, click Tools-
Troubleshooting-Transfer Memory to
Module.
• In SuperVision v2.6b, choose Download
Memory for This Module.
4. When the memory transfer is finished,
check the module status report again.
Make sure the FB List on this page shows
all the FBs you intended to transfer.
Using Flow Sensors
The UNI/32 supports U-cards that use flow
sensors. You must calibrate each sensor to
ensure accurate readings. You must also set
the type of U-cards and flow sensors that are
being used by each FB on the module driver
Properties page in WebCTRL or Parameter
page in SuperVision.
• If you are running a WebCTRL system,
configure the type of U-card and flow
sensor on the Airflow microblock
Properties page for each FB that uses a
flow sensor. Refer to the DRV_UNI16
and DRV_UNI32 Module Driver
document for details.
• If you are running a SuperVision
system, configure the type of U-card
and air sources on the module driver
Parameter page. Refer to the UNM
Module Driver document for details.
For more information on calibrating,
see the Test and Balance Technical
Instructions.
Troubleshooting Tips
If you are having trouble communicating with
the UNI/32, check these items before
contacting Technical Support.
• Make sure the U-Line wiring is correct.
In more complex systems, make sure
that all cables involved are attached
correctly.
• Make sure the UNI/32 and the U-cards
have power and are turned on. In more
complex systems, make sure all
equipment has power and is turned on.
Some devices, especially
communication devices, receive power
from a source other than a power cable
or adapter (for example, some devices

Revised 11/26/01 • UNI/32 8 © 2001 Automated Logic Corporation
receive power through communication
lines). Some panels can be reinitialized
by resetting the panel.
• Make sure the module driver and all
GFBs are transferred into the module.
You can verify this by checking the
module status page for the UNI/32
module.
• For WebCTRL systems, make sure the
module driver properties and the
properties for each GFB are set up
properly in WebCTRL.
For SuperVision systems, make sure the
module driver parameters and the
parameters for each GFB are set up
properly in SuperVision.
Communicating with the Workstation
Using SuperVision
When using SuperVision, you can connect a
workstation or portable computer directly to
the UNI/32 module using an APT and the
module’s Access port (see Figure 8).
NOTE This type of connection should only
be used to troubleshoot the module or
transfer memory.
The baud rate of the Access port is
determined by the first switch on the eight-
position DIP switch (see Figure 7 on page 6). If
you need to change the switch’s position, turn
the UNI/32 module off first. Once you have
adjusted the switch, turn the module back on.
1. Connect the computer’s serial port to the
EIA-232 port of the APT using a standard
straight-through serial cable.
2. Set the APT’s Mode Select switch.
• On an ARC156 network segment, use
the TTL setting.
• On a legacy CMnet, use the 485 setting.
3. Connect the Access port of the APT to the
Access port of the module.
4. In SuperVision, define the connection type
using Table 1.
Formatting the Module
If you are unable to communicate with a
module after transferring memory, you can,
as a last resort, manually format the module
to try to restore communication. Formatting
the module erases all memory, so you need to
transfer memory back to the module once it is
formatted.
NOTE Since the module is automatically
formatted when you transfer memory, you
should only manually format the module if
communication was not established after the
memory transfer.
1. Turn the module’s power off. Make sure
the module is addressed correctly.
2. Press and hold the Format button (see
Figure 2 on page 3 for location).
Figure 8. Using the Access Port
9
Rx
61
2- Tx out
3- Rx in
5- Gnd
1,6,8- +10V or floating
Tx +5V
APT
5
Exec. 4 relay
Isolate Network
Mode Select
TTL 485
ACCESS
PORT
EIA-232
Port
Mode Select
Switch
Exec. 4 relay
Switch
Access
Port
UNI
Table 1. Connection Types
SuperVision
Version
Typ e of
CMnet
Gateway
Present?
Use Connection
Type
3.0 any n/a Access Port
2.6 ARC156 yes Direct Connect
2.6 ARC156 no Direct Network
2.6 legacy n/a Direct Network

Revised 11/26/01 • UNI/32 9 © 2001 Automated Logic Corporation
3. While continuing to hold the Format
button, turn the module’s power on.
4. Continue to hold the button until the Error
LED flashes three times in sync with the
Run LED.
5. Release the Format button.
6. Transfer memory to the module. Refer to
“Transferring Memory” on page 6.
LEDs
The UNI/32 module has LED indicators to
show the status of certain functions. Table 2
explains the Run and Error LED signals in
detail to assist troubleshooting.
Power - indicates power is being supplied to
the module.
CMnet Rx - lights when the module receives
data from the CMnet.
CMnet Tx - lights when the module transmits
data over the CMnet.
Unet receive - lights when the module
receives data from the Unet.
Unet transmit - lights when the module
transmits data to the Unet.
Diag receive - lights when the Diag Port
receives data.
Diag transmit - lights when the Diag Port
transmits data.
Protection
The UNI/32 module is protected by internal
solid state Polyswitches on the incoming
power and network connections. These
Polyswitches are not replaceable and will
reset themselves if the condition that caused
the fault returns to normal.
Production Date
To determine when a module was
manufactured, check the module status
report for the module in SuperVision. Refer to
the WebCTRL User’s Guide or the SuperVision
User’s Guide for more information about the
module status report.
Table 2. LED Signals
Run LED Error LED Condition
2 flashes
per second
Off Normal
2 flashes
per second
1 flash,
then pause
Normal, but module is alone
on the CMnet (this sequence
does not occur in WebCTRL)
2 flashes
per second
2 flashes,
alternating
with Run
LED
Five minute auto-restart
delay after system error
2 flashes
per second
2 flashes,
in sync
with Run
LED, then
pause
Module is configured for a
different baud rate than the
rest of the network segment
2 flashes
per second
3 flashes,
then off
Module has just been
formatted
2 flashes
per second
4 flashes,
then pause
Two or more devices on this
network have the same
ARC156 network address
2 flashes
per second
On Exec halted after frequent
system errors or GFBs halted
5 flashes
per second
On Exec start-up aborted, Boot
is running
5 flashes
per second
Off Firmware transfer in
progress, Boot is running
7 flashes
per second
7 flashes
per second,
alternating
with Run
LED
Ten second recovery period
after brownout
14 flashes
per second
14 flashes
per second,
alternating
with Run
LED
Brownout
Table 2. LED Signals (Continued)
Run LED Error LED Condition

Revised 11/26/01 • UNI/32 10 © 2001 Automated Logic Corporation
A sticker on the back of the module also
shows the date the module was
manufactured. The first three characters on
the sticker indicate the type of module. The
next two characters show the year and month
of manufacture. (The month digit is in
hexadecimal.)