BAC-19xxxx FlexStat Application Guide 23 AG200824A
the FlexStat operates changes. Read
all notes accompanying the rmware
update!
• Change the state of each custom program
by loading/running each program from KMC
software.
NOTE: See also Control Basic Programs Do
Not Work on page 18.)
NOTE: Customized programs are the
responsibility of the user. KMC Controls
does not provide support for such
programs.
Power Issues
• Check for a tripped circuit breaker to the
transformer.
• Check for proper supply voltage and phasing
from the transformer (or power supply) and
that the transformer has enough capacity
(VA) for all connected devices. See the
devices’ respective data sheets and Tips for
Connecting 24-Volt Power Application Note
(AN0604D).
NOTE: Wiring must be adequate to avoid
excessive voltage drop on long runs!
Allow plenty of “cushion.” A voltage
meter may be too slow to register
transient dips or peaks during startup.
Protocol Issues
NOTE: On “E” models, the default protocol is
BACnet over Ethernet with a Device ID
of 1.
• To see new “E” models in KMC software, be
sure the software attached to the network can
discover BACnet over Ethernet devices. (Add
a BACnet over Ethernet network in BACstac if
needed.) See Ethernet/IP Conguration via
Software on page 7.
• To prevent losing communication with “E”
models, changing from the default Ethernet
to an IP setting requires multiple steps in
software. See Ethernet/IP Conguration via
Software on page 7.
Wiring Issues
• Review the wiring information in Wiring
Considerations on page 13, the BAC-
19xxxx FlexStat Installation Guide, and the
BAC-19xxxx FlexStat Sequence of Operation
and Wiring Guide.
• Remove the FlexStat from the backplate and
inspect the terminals for loose or shorted
wires.
• Check for ground loops. See Avoiding and
Troubleshooting Ground Loops Application
Guide.
• Use a voltmeter and ohmmeter to check
the terminals for expected values. See the
backplate terminals illustration.
NOTE: Voltage on the BACnet MS/TP
terminals changes according to the
signals (passing of the token) between
controllers on the network. No voltage
may indicate a bad connection or
simply no active network.
NOTE: Wiring must be adequate to avoid
excessive voltage drop on long
runs! Allow plenty of “cushion” in
measurements A meter may be too
slow to register transient dips or
peaks during startup. See Wiring
Issues on page 23.
• Check the wiring at the connected devices.
CAUTION
To avoid damage from ground loops
and other communication issues in
networked FlexStats, correct phasing
on network and power connections
on ALL the networked controllers is
critically important.
To Next Page
