Anemostat KMC Conquest User guide

KMC Controls, 19476 Industrial Drive, New Paris, IN 46553 /877-444-5622 /Fax: [phone] /www.kmccontrols.com
KMC Conquest™Controller
Application Guide
Contents
GENERAL INFORMATION....................................................................4
About KMC Conquest...................................................................4
Specications, Accessories, and Installation...................................4
Video Tutorials ...........................................................................5
Submittal Sheets (Diagrams and Operation) ....................................5
Support .....................................................................................6
Important Notices .......................................................................6
Notes and Cautions .....................................................................6
Handling Precautions ..................................................................6
(STATUS) INDICATORS ......................................................................7
Indicators, Connections, and Status ...............................................7
Ready (Power/Status) LEDs (Green) ...............................................7
MS/TP LEDs (Amber)...................................................................7
EIO LEDs (Green) ........................................................................8
Network Isolation Bulbs (HPO-0055)..............................................8
Ethernet LEDs (Green and Amber) ..................................................8
CONNECTIONS (SENSORS, EQUIPMENT, NETWORKS).............................9
Input Connections (Room Sensor Port)...........................................9
Dedicated Use of (STE-9000/6000) Room Sensor Port ................9
Digital STE-9000 Series NetSensors....................................... 10
STE-93xx/95xx CO2 Sensor and DCV....................................... 11
Analog STE-6000 Series Thermistor Sensors ........................... 12
Input Connections (Universal, Terminals)...................................... 13
Output Connections................................................................... 13
Connecting Universal Outputs ............................................... 13
Grounds Versus Switched (Relay) Commons ............................ 14
SC Terminals in Initial BAC-93xx Controllers ........................... 14
Installing Override Boards in BAC/CAN-5900 Series ................. 15
Connecting a VAV Remote Actuator to a BAC-9311................... 18
MS/TP Network Connections ...................................................... 19
Connections and Wiring........................................................ 19
EOL (End of Line) Termination Switches .................................. 20
Ethernet Network Connections .................................................... 20
Power (Controller) Connections................................................... 22
CAN-5900 Series Expansion Modules........................................... 23
Addressing CAN-5900 Modules............................................. 23
Connecting Power to CAN-5900 Modules ................................ 24
EIO LED Communication Indicators......................................... 24
AIR DISTRIBUTION
Anemostat, 1220 E. Watson Center Road, Carson, CA 90745 /310-835-7500 /[email protected] /www.anemostat-hvac.com

2 KMC Conquest Controller Application Guide, AG150217K
CONFIGURATION ............................................................................ 25
Conguring, Programming, and Designing .................................... 25
NFC (Near Field Communication)................................................. 26
Passwords ............................................................................... 27
Controller Conguration with STE-9xx1 Menus .............................. 28
Restore (RSTR) and Application/Units Selection............................. 32
VAV Airflow Balancing with an STE-9xx1 ...................................... 33
RESETTING AND TROUBLESHOOTING ................................................ 36
Resetting Controllers................................................................. 36
Types of Reset.................................................................... 36
Warm and Cold Starts .......................................................... 36
Troubleshooting ....................................................................... 37
Communication Issues ......................................................... 37
LED Indicators and Isolation Bulbs Issues................................ 38
Hardware Issues ................................................................. 39
Input Issues ....................................................................... 39
Output Issues ..................................................................... 41
NetSensor Display is Blank ................................................... 42
Power Issues...................................................................... 42
VAV Airflow Issues .............................................................. 42
Conguration, Programming, and Operation Issues................... 43
Web Page Issues (Ethernet Models) ....................................... 44
Other Issues....................................................................... 44
MAINTENANCE AND UPGRADES ....................................................... 45
Maintenance ............................................................................ 45
Controller Upgrades and Cross-References ................................... 45
SEQUENCES OF OPERATIONS ........................................................... 47
AHU (Air Handling Unit) ............................................................. 47
CAV (Constant Air Volume)......................................................... 47
FCU (Fan Coil Unit).................................................................... 48
Introduction (FCU)............................................................... 49
Room Temperature Setpoints (FCU)........................................ 49
Occupancy, Motion Sensing, and Standby (FCU) ....................... 50
System Mode and Cooling/Heating Changeover (FCU)............... 51
Scheduling Occupancy (FCU)................................................. 51
Dehumidication Sequence (FCU) .......................................... 51
Temperature Sensing Inputs (FCU)......................................... 52
Fan Status (FCU) ................................................................. 52
PID (Proportional Integral Derivative) Loops (FCU).................... 52
Valve Operation (FCU).......................................................... 53
Fan Operation (FCU)............................................................. 54
HPU (Heat Pump Unit) ............................................................... 56
Introduction (HPU) .............................................................. 56
Room Temperature Setpoints (HPU) ....................................... 57
Occupancy, Motion Sensing, and Standby (HPU)....................... 58
System Mode and Cooling/Heating Changeover (HPU)............... 59
Scheduling Occupancy (HPU) ................................................ 59

KMC Conquest Controller Application Guide, AG150217K 3
Dehumidication Sequence (HPU).......................................... 59
Temperature Sensing Inputs (HPU)......................................... 60
Fan Status (HPU)................................................................. 60
PID (Proportional Integral Derivative) Loops (HPU) ................... 60
Staged Heating And Cooling (HPU)......................................... 61
Fan Operation (HPU) ............................................................ 62
Economizer Cooling (HPU) and DCV ....................................... 62
Reversing Valve Action (HPU) ............................................... 63
Auxiliary and Emergency Heat Action (HPU) ............................ 63
RTU (Roof Top Unit) or AHU (Air Handling Unit).............................. 64
Introduction (RTU/AHU)........................................................ 64
Room Temperature Setpoints (RTU/AHU) ................................ 65
Occupancy, Motion Sensing, and Standby (RTU/AHU)................ 66
System Mode & Cooling/Heating Changeover (RTU/AHU)........... 67
Scheduling Occupancy (RTU/AHU) ......................................... 67
Dehumidication Sequence (RTU/AHU)................................... 67
Temperature Sensing Inputs (RTU/AHU).................................. 67
Fan Status (RTU/AHU).......................................................... 68
PID (Proportional Integral Derivative) Loops (RTU/AHU) ............ 68
Modulating Cooling and Heating (RTU/AHU) ............................ 69
Staged Heating And Cooling (RTU/AHU).................................. 69
Fan Control (RTU/AHU)......................................................... 70
Economizer Cooling (RTU/AHU) and DCV (RTU)........................ 70
VAV (Variable Air Volume).......................................................... 71
Introduction (VAV)............................................................... 72
Sensors (VAV) .................................................................... 73
Room Temperature Setpoints (VAV) ....................................... 74
Occupancy, Motion Sensing, and Standby (VAV)....................... 75
Scheduling Occupancy (VAV) ................................................ 76
PID (Proportional Integral Derivative) Loops (VAV) ................... 76
Airflow Setpoints Sequence (VAV) ......................................... 77
Cooling/Heating Changeover (VAV)........................................ 77
Discharge Air Temperature (DAT) Limiting (VAV) ...................... 77
Reheat (VAV)...................................................................... 78
Damper Operation (VAV)....................................................... 79
Fan Operation (VAV) ............................................................ 79
Dual Duct (VAV) .................................................................. 80
Balancing Airflow (VAV) ....................................................... 80
System Diagnostics (VAV) .................................................... 81
SYSTEM INTEGRATION AND NETWORKING......................................... 82
Networking .............................................................................. 82
BACnet Objects List .................................................................. 82
General Notes..................................................................... 82
BAC-5900 Series (General Purpose Controller) Objects ............. 83
BAC-9000 Series (VAV Controller) Objects .............................. 84
BAC-9300 Series (Unitary Controller) Objects.......................... 93
APPENDIX: K FACTORS FOR VAV..................................................... 108
INDEX......................................................................................... 109

4 KMC Conquest Controller Application Guide, AG150217K
About KMC Conquest
KMC Conquest controllers are fully programmable, native BACnet controllers
with integrated alarming, trending, and scheduling. This applications
guide provides expanded installation information, sequences of operation,
troubleshooting, and other information. For additional installation instructions,
see the installation guides for the respective products.
GENERAL INFORMATION
TERMINAL COLOR CODE
Black 24 VAC/VDC Power
Gray MS/TP and CAN Communications
Green Inputs and Outputs
EIO Terminals
and EOL Switch
NFC
Target
Power/Status
LED
Output
Override
Board Slots
& Cover
(Optional)
MS/TP
Status LED,
Network
Bulbs, EOL
Switch, and
Terminals
(Optional)
Ethernet Port
Room
Sensor Port
EIO
Status
LED
Power
Terminals
Input
Terminals
Output
Terminals
Specications, Accessories, and Installation
See the relevant KMC Conquest documents for:
• BAC-5900 Series BACnet General Purpose Controllers
• CAN-5900 Series I/O Expansion Modules
• BAC-9000 Series BACnet VAV Controller-Actuators
• BAC-9300 Series BACnet Unitary Controllers
• STE-9000 Series NetSensors Digital Room Sensors
• TSP-8003 (Dual Duct) Tri-State Actuator with Pressure Sensor
See also the Conquest Selection Guide and the BAC-5051E BACnet Router.
For the STE-9000 Series NetSensors, see also the Room Sensor and Thermostat
Mounting and Maintenance Application Guide.
For 4–20 ma applications, see also the 4–20 mA Wiring for Controllers
Application Guide.
Illustration: Controller Overview (BAC-5901)

KMC Conquest Controller Application Guide, AG150217K 5
Submittal Sheets (Diagrams and Operation)
BAC-9300 series unitary controllers and BAC-9000 series VAV controllers have
a collection of submittal sheets for common applications available through the
KMC Connect, TotalControl, or Converge conguration wizards. The submittal
sheets include wiring diagrams and sequences of operation.
Single Duct Variable Air Volume (VAV) Terminal Unit
Cooling with Staged Electric Reheat and Vent Control
Pressure Independent
Model: BAC-9001/9001CE
SEQUENCE OF OPERATION:
1. Changeover: If the discharge air temperature (DAT) drops below 72°F, cool air is said to be
available. As the DAT rises above 76°F, warm air is said to be available. Any time warm air is
available, auxiliary heat is locked out.
2. Cool air available: As space temperature rises above the cooling setpoint, the controller increases
airflow. At a space temperature of 2°F above the cooling setpoint, maximum cooling airflow is
maintained. On a decrease in space temperature, the controller reduces airflow. From cooling
setpoint to heating setpoint, minimum cooling airflow is maintained. If the temperature drops
further and heating is required, the auxiliary flow rate is maintained.
3. Warm air available: As space temp drops below the heating setpoint, the controller increases
airflow. At a temperature 2°F below the heating setpoint, maximum heating airflow is maintained.
On an increase in space temperature, airflow decreases. As space temperature rises above the
heating setpoint, minimum heating airflow is maintained.
4. CO2 (optional): As CO2 rises above the halfway point between the min CO2 reading (CO2
SAVED LOW) and the max CO2 target (CO2 SETPOINT), the controller increases airflow. At a
CO2 of 600ppm (default) above the min CO2 reading, maximum airflow is maintained. On a
decrease in CO2, the controller reduces airflow. Below the halfway point between max CO2
target and min CO2 reading, minimum airflow is maintained. When CO2 control is enabled, the
damper responds to the greater of CO2 or temperature control.
5. As the space temp drops below the heating setpoint, stages 1, 2 and 3 of electric reheat are
energized respectively. As the space temp rises back toward the heating setpoint, heating stages
3, 2 and 1 turn off respectively.
6. If DAT limiting is enabled and a DAT sensor is detected, the discharge air reheat setpoint is
determined based on the heating loop. The discharge air setpoint is limited to a maximum of
15°F above space temperature.
UI3
RDY COM
GND UI4
HIGH
LOW
-A
+B
S
BACnet MS/TP EOL
10/100
ETHERNET
BAC-9001/9001CE Controller
H L
1/4" (6) O.D. tubing
to flow sensor
CONTROLLER
PREVIOUS
FROM BLK
SHLD
RED
CONTROLLER
NEXT
TO BLK
SHLD
RED
If controllers are to be networked
together via MS/TP, turn ON EOL switch
on the controllers at both physical ends
of the network. Connect shield to earth
ground at only one point.
Connect sensor to the
RJ-45 jack using a max.
75' Ethernet cable.
STE-9521W
STE-6010W10
~
DISCHARGE AIR TEMP
10KΩ, TYPE 3
H N
Line
Voltage
24VAC
NOTES:
1. Controller settings must be initially
set using an STE-9XX1.
2. Recipient(s) must be configured to
utilize preconfigured alarms and
trends.
3. See kmccontrols.com for
accessories and additional details.
External connections::
UI3 = DAT SENSOR
BO7 = REHEAT #1
BO8 = REHEAT #2
BO9 = REHEAT #3
UI5 GND UI6 UO3 GND UO4 GND UO5
T-STAT/
SENSOR
Connect
controller to
network using
standard
Ethernet cable.
(optional)
BO6 BO7 SC BO8 BO9
CREATION DATE: FILENAME:
REVISION DATE:
DRAWING TITLE:
REVISION:
19476 INDUSTRIAL DR.
NEW PARIS, IN 46553
PHONE: [phone]
FAX: [phone]
kmccontrols.com
KMC CONTROLS, INC.©2015
COOLING VAV W/STAGED REHEAT, CO2
SSKV9032_VAV_CLG_3STAGE_RHT_CO2
2/9/2015
2/9/2015 INITIAL RELEASE
OFFON
123
Electric
Reheat
NOTE: ENSURE
WIRING TO
CONTROLLER IS
24VAC ONLY!
MIN CO2
READING
CO2 INCREASE
CFM INCREASE
MAX PRI CFM
CO2 CONTROL SEQUENCE (optional)
600 ppm
MIN PRI CFM
HTG
SP CLG SP
CFM INCREASE
MAX HTG CFM
WARM AIR AVAILABLE SEQUENCE
HTG SPAN
MIN
HTG
CFM
HTG
SP CLG SP
CLG SPAN ROOM
MAX CLG CFM
CFM INCREASE
AUX FLOW CFM
COLD AIR AVAILABLE SEQUENCE
HTG SPAN
MIN
CLG
CFM
-2F +2F
-2F
MAX CO2
TARGET
TEMP
INCREASE
ROOM
TEMP
INCREASE
ROOM
TEMP
INCREASE
HEATING STAGES OPERATION
STAGE 3
STAGE 2
STAGE 1
HTG
SP
.7F1.3F1.9F
Illustration: Sample (VAV) Submittal Sheet
See the applications library in KMC Connect, TotalControl, or Converge to
download the sheets.
Video Tutorials
See also the assorted Conquest videos on KMC’s YouTube channel.
Illustration: KMC YouTube Channel Videos

6 KMC Conquest Controller Application Guide, AG150217K
Notes and Cautions
NOTE: In this document, a NOTE provides additional information that is
important.
CAUTION
In this document, a CAUTION indicates potential personal injury or
equipment or property damage if instructions are not followed.
Additional resources for installation, conguration, application, operation,
programming, upgrading and much more are available on the KMC Controls
web site (www.kmccontrols.com). To see all available les, log-in to the KMC
Partners site.
Support
Important Notices
KMC Controls®and NetSensor®are all registered trademarks of KMC Controls.
KMC Conquest™, KMC Commander™, KMC CommanderBX™, KMC Connect™, KMC
Connect Lite™, KMC Converge™, and TotalControl™ are all trademarks of KMC
Controls. All other products or name brands mentioned are trademarks of their
respective companies or organizations.
All rights reserved. No part of this publication may be reproduced, transmitted,
transcribed, stored in a retrieval system, or translated into any language in any
form by any means without the written permission of KMC Controls, Inc.
The material in this document is for information purposes only. The contents
and the product it describes are subject to change without notice. KMC
Controls, Inc. makes no representations or warranties with respect to this
document. In no event shall KMC Controls, Inc. be liable for any damages, direct
or incidental, arising out of or related to the use of this document.
Specications and design are subject to change without notice.
Handling Precautions
For digital and electronic sensors,
thermostats, and controllers, take reasonable
precautions to prevent electrostatic
discharges to the devices when installing,
servicing, or operating them. Discharge
accumulated static electricity by touching
one’s hand to a securely grounded object before working with each device.
NOTICE
OBSERVE PRECAUTIONS
FOR HANDLING
ELECTROSTATIC
SENSITIVE DEVICES

KMC Conquest Controller Application Guide, AG150217K 7
Indicators, Connections, and Status
Indicators show the status of connections and the controller. Indicator actions
are described below. For troubleshooting faulty operation, see LED Indicators
and Isolation Bulbs Issues on page 38.
Ready
(Power/Status)
LED
MS/TP
Network
Bulbs
MS/TP
COMM
(Status)
LED
EIO COMM
(Status) LED
Illustration: Indicators (BAC-5901C)
Ready
(Power/
Status)
LED
MS/TP
COMM
(Status)
LED
MS/TP
Network
Bulbs
Illustration: Indicators (BAC-9001C)
Ready (Power/Status) LEDs (Green)
Within a few seconds after power is rst applied, the green Ready (power/status)
LED near the power terminals will begin flashing (on for a second and then off
for a second) if the device is functioning normally.
MS/TP LEDs (Amber)
The (optional) MS/TP network has an amber LED that flickers as it receives and
passes the token during communication with the network. When the controller
is powered up (but not communicating on the MS/TP port), these amber LEDs
will flash slowly, about once per second. When the MS/TP port establishes
communications with the network, the amber LED for that MS/TP port will flash
rapidly (multiple times a second) as it receives and passes the token.
(STATUS) INDICATORS

8 KMC Conquest Controller Application Guide, AG150217K
EIO LEDs (Green)
For BAC-5900 series controllers with connected CAN-5900 series expansion
modules, the EIO (Expansion Input Output) network (also known as a CAN bus)
has a green LED (on each end) that flickers as it receives and passes the token
during communication with the network. See CAN-5900 Series Expansion
Modules on page 23 for more information.
Network Isolation Bulbs (HPO-0055)
MS/TP and EIO networks have an assembly of two isolation bulbs located near
the network terminals. Normally the bulbs are not illuminated. If one or both
bulbs are illuminated, it indicates the network is improperly phased (the ground
potential of the controller/module is not the same as on other controllers/
modules on the network).
Amber Ethernet
(Communication
Speed)
Green Ethernet
(Trafc)
Illustration: Ethernet Indicators (2016 and Later BAC-90xxE Shown)
Ethernet LEDs (Green and Amber)
(Optional) Ethernet network connectors have two built-in LEDs:
• The amber LED illuminates when the controller has power and is commu-
nicating at its highest speed (100BaseT). (It is off when the connection is
communicating at 10BaseT.)
• The green LED will blink at a rate in accordance to Ethernet trafc.
• If neither LED is illuminated, controller is unpowered or there is a faulty
Ethernet connection.
Early model BAC-59xxE and BAC-9xxE models had a single Ethernet port. In mid-
2016, dual port models began replacing the single port models. On these newer
models, the Room Sensor port is yellow instead of black to help differentiate it
from the black Ethernet ports.
NOTE: The Room Sensor port is next to the Ethernet ports in the BAC-90xxE
VAV controllers. It is on the opposite side on BAC-93xxE and BAC-59xxE
controllers.

KMC Conquest Controller Application Guide, AG150217K 9
Input Connections (Room Sensor Port)
Dedicated Use of (STE-9000/6000) Room Sensor Port
CAUTION
On Conquest “E” models, do NOT plug a cable meant for Ethernet
communications into the Room Sensor jack. The Room Sensor port
powers a NetSensor, and the supplied voltage may damage an Ethernet
card, switch, or router to which it is accidentally connected. See
Illustration: Inputs and Ports (Early BAC-9001CE) on page 9and
Illustration: Room Sensor and Dual Ethernet Ports on page 9.
Room Sensor Port:
Inputs 1 and 2
Ethernet Port
Removable Screw Terminals:
Inputs 3 through 6
Illustration: Inputs and Ports (Early BAC-9001CE)
(2016 and Later
BAC-90xxE
Shown)
Ethernet
Connections
Room
Sensor
Connection
Illustration: Room Sensor and Dual Ethernet Ports
Early model BAC-59xxE and BAC-9xxE models had a single Ethernet port. In mid-
2016, dual port models began replacing the single port models. On these newer
models, the Room Sensor port is yellow instead of black to help differentiate it
from the black Ethernet ports.
NOTE: The Room Sensor port is next to the Ethernet ports in the BAC-90xxE
VAV controllers. It is on the opposite side on BAC-93xxE and BAC-59xxE
controllers.
CONNECTIONS (SENSORS, EQUIPMENT, NETWORKS)

10 KMC Conquest Controller Application Guide, AG150217K
The dual Ethernet ports on these controllers function as Ethernet switches to
other controllers as well as interfaces within each controller. This allows daisy-
chaining of Ethernet models. See Daisy-Chaining Conquest Ethernet Controllers
Technical Bulletin (TB160426) for more information.
NOTE: The input objects AI1 and AI2 are dedicated for use with analog
electronic STE-6010, STE-6014, and STE-6017 sensors, but not
digital STE-9xx1 NetSensors. See Analog STE-6000 Series Thermistor
Sensors on page 12. When a NetSensor is connected to the port, AI1
and AI2 will appear in software to be unused. The NetSensor digitally
communicates with the value objects AV1, AV4, and AV5. See Digital
STE-9000 Series NetSensors on page 10.
NOTE: For additional information on value objects, see BACnet Objects List on
page 82.
NOTE: AI1 and AI2 can be used with other sensors by connecting to Pin 3 and
Pin 1 and/or Pin 8 of an RJ45-type modular connector inserted in the
Room Sensor port. See Illustration: Room Sensor Port Pinouts on page
10.
Pin 1 = Setpoint Signal to Controller (AI2)
Pin 3 = Ground Reference
Pin 8 = Temperature Signal to Controller (AI1)
Pin
3
Pin
8
Pin
1
Flat,
Pin-Side
of Ethernet
Connector
Illustration: Room Sensor Port Pinouts
Digital STE-9000 Series NetSensors
STE-90xx/93xx STE-92xx/95xx
with Motion Sensor
Illustration: STE-9000 Series NetSensors

KMC Conquest Controller Application Guide, AG150217K 11
These KMC Conquest digital wall sensors include a room temperature sensor,
optional sensors (humidity, motion, and/or CO2), a digital display, and a
push-button interface for entering setpoints and conguring the controllers.
Connection is made using a standard Ethernet patch cable. If an STE-9000
series sensor is detected, the sensor’s temperature is mapped to the Space
Temperature Reference value object (AV1) as the temperature input value. The
cooling and heating setpoints are mapped to Active Cooling Setpoint (AV4) and
Active Heating Setpoint (AV5).
For information about using the NetSensor to congure Conquest controllers,
see Controller Conguration with STE-9xx1 Menus on page 28, Restore
(RSTR) and Application/Units Selection on page 32, and VAV Airflow
Balancing with an STE-9xx1 on page 33.
NOTE: If the display remains blank after plugging it in, see NetSensor Display
is Blank on page 42.
STE-93xx/95xx CO2Sensor and DCV
The space CO2 level read by an STE-93xx/95xx sensor always maps to AV57.
DCV (Demand Control Ventilation) is available in a KMC Conquest controller
(only) when all ve of these conditions are met:
• A BAC-93xx controller is used.
• The HPU or RTU application is chosen.
• An economizer is enabled.
• An STE-93x1/95x1 NetSensor is connected to the Room Sensor port.
• AND the controller rmware is R1.0.0.6 or higher.
After all the DCV conditions are met, adjust these settings:
• DCV, which is disabled by default (under CO2 in the NetSensor System
menu or BV29). Enable it to use it.
• CO2 Setpoint (800 ppm default), which is the value at which DCV control of
the economizer damper position begins (under CO in the NetSensor Setpoint
menu or AV59).
• CO2 Range (200 ppm default), which proportionally controls the economizer
damper position for a given CO2reading above the setpoint (under CORA in
the NetSensor Setpoint menu or AV58).
DCV CONTROL SEQUENCE
POS %
Max
Min
OAD
CO2
Setpoint
CO2
CO2Level
(AV57)
(AV59)
(AV58)
Range
Illustration: DCV Control Sequence
NOTE: At the bottom of the CO2 range, the damper is at the minimum position
(assuming there is no other demand on the economizer). At the top
of the range, the damper opens to the maximum value. For example,
with the defaults and no other ventilation demand, the damper position

12 KMC Conquest Controller Application Guide, AG150217K
would be at its minimum for a CO2reading of 800 ppm and at its
maximum for a CO2reading of 1000 ppm or higher.
For other applications and/or controllers, application programming that
references the (AV57) CO2value may be added to the controller either by
modifying the factory application programming or by adding Control Basic logic
in an unused program.
NOTE: Alternately, to use an easy (menu-congurable) yet advanced DCV
solution for AHU, RTU, FCU, and HPU applications, see the integrated
sensor-and-controller BAC-13xxx and BAC-14xxx series of FlexStats.
NOTE: The STE-93xx/95xx CO2sensor uses a self-calibration technique
designed to be used in applications where CO2 concentrations will
periodically drop to outside ambient conditions (approximately 400
ppm), typically during unoccupied periods. The sensor will typically
reach its operational accuracy after 25 hours of continuous operation
if it was exposed to ambient reference levels of air at 400 ±10 ppm
CO2.The sensor will maintain accuracy specications if it is exposed
to the reference value at least four times in 21 days. (There is no
provision for calibrating with gas.)
NOTE: For troubleshooting tips, see Demand Control Ventilation (DCV) Is Not
Available or Working Properly on page 39.
Analog STE-6000 Series Thermistor Sensors
Three models of the STE-6000 series sensors are compatible with the Room
Sensor port on KMC Conquest VAV controllers. If an STE-6010, STE-6014, or
STE-6017 is connected to the Room Sensor port (with a standard Ethernet patch
cable), the sensor’s temperature from AI1 is mapped to the Space Temperature
Reference value object (AV1) as the temperature input value.
STE-6010 STE-6014 STE-6017
Illustration: STE-601x Sensors Compatible with Room Temp. Port
The STE-6014 and STE-6017 include a dial for adjusting the zone setpoint. If
either of these two sensors is detected, the reading of the dial setting (AI2) is
mapped to the Setpoint Offset (AV2).
The default range of the offset is plus or minus 1° F. This means that, with the
STE-6014/6017, users can adjust the scheduled setpoint by a maximum of one
degree up or down. To change the range, import custom table values into (Table
Object) Input Table 4 using KMC Connect or TotalControl.
The STE-6017 also includes a button that will shunt the thermistor when pushed
(SENSORON) to indicate an override of an unoccupied state. Local Override
(e.g., BV4 in a BAC-9001) then becomes Active until the Local Override Timer
(AV38) value is exceeded. (The controller performs the override function
automatically, and no additional Control Basic programming using SENSORON is
required.)

KMC Conquest Controller Application Guide, AG150217K 13
NOTE: The STE-6014/6017 override button needs to be pressed and held for at
least a half a second to be reliably recognized for override mode.
Input Connections (Universal, Terminals)
NOTE: On Conquest controllers, Inputs 1 and 2 are dedicated to the Room
Sensor port. Terminals on removable green blocks start with Input 3.
(See Illustration: Controller Overview (BAC-5901) on page 4and
Illustration: Inputs and Ports (Early BAC-9001CE) on page 9.) The
input object AI1 is dedicated to the room temperature, and object AI2
is dedicated to room temperature setpoint. If reusing Custom Control
Basic programs from older controllers, make any necessary changes
to the input objects in the program. See Analog STE-6000 Series
Thermistor Sensors on page 12.
The universal inputs on green terminal blocks can be congured as:
• Analog objects—Changing resistance (thermistor) or 0 TO 12 VDC
• Binary objects—Open/Close passive switch or 0 OR 12 VDC
For an active voltage input, congure the input for 0–12 VDC (in the Termination
drop-down selection of KMC Connect, Converge, or TotalControl).
NOTE: For 0–12 VDC inputs, select 0–12 V in the Termination drop-down
box rather than Fixed Bias 0–12 V. Fixed Bias 0–12 V is automatically
selected by built-in applications for mapping some inputs (e.g., AI1 and
AI2 with STE-60xx sensors) into AVs. Other such inputs include: AI7
Primary Duct (BAC-9001), AI8 Primary Position (BAC-9001), and AI9
Duct (BAC-9311).
For passive input signals, such as thermistors or switch contacts, congure the
input for 10K ohm (or 1K ohm for most RTDs) pull-up resistor.
For a pulse input signal, congure the input in the following manner:
• If the pulse input is a passive input, such as switch contacts, then congure
the input for 10K ohm pull-up resistor.
• If the pulse is an active voltage up to a maximum of 12 VDC, then congure
the input for 0–12 VDC.
For a 4–20 mA current loop input, congure the input for 4–20 mA. See also the
4–20 mA Wiring for Controllers Application Guide.
Output Connections
Connecting Universal Outputs
Connect the output device under control between the output terminal and
the ground (GND) terminal on the same bank. On BAC-9300 series, Switched
Common (SC) terminals are used on the BO terminals. On BAC-5900 series
controllers and CAN-5900 series expansion modules, SC terminals are only used
with some of the output override boards. See Grounds Versus Switched (Relay)
Commons on page 14.
The universal outputs (on green terminal blocks) can be congured as:
• Analog objects—0 TO 12 VDC
• Binary objects—0 OR 12 VDC

14 KMC Conquest Controller Application Guide, AG150217K
For either type of output, the DC voltage signals can—within the specication
of the output—connect directly to most equipment. For additional options, see
Installing Override Boards in BAC/CAN-5900 Series on page 15.
NOTE: For 4–20 ma applications, see also the 4–20 mA Wiring for Controllers
Application Guide.
Grounds Versus Switched (Relay) Commons
Use the SC terminal in the same output bank (individual terminal block) as
its output terminal. The switched common terminals are isolated from the
circuit grounds used for the universal output analog circuitry in controllers. See
Illustration: Conquest SC Terminals on page 14.
BO6
BO7
SC
BO8
BO9
BO1
BO2
SC
BO3
BO4
BO5
SC
BO6
GND
UO8
SC
UO7
GND
UO6
SC
UO5
GND
UO4
SC
UO3
GND
UO2
SC
UO1
BAC-5901/CAN-5901
Triacs (HPO-6701), NO Relays (HPO-6703),
or NC Relays (HPO-6705) on Output Override Boards
Internal Triacs
Internal Triacs
BAC-93x1
BAC-90x1
Illustration: Conquest SC Terminals
See also SC Terminals in Initial BAC-93xx Controllers on page 14.
Switched Common (SC) output terminals are unconnected in the BAC-5900
series controller unless the jumper is removed and an appropriate relay/triac
override output board is installed. Use only the Switched (relay) Common
instead of the Ground with the HPO-6701 triac and HPO-6703/6705 relays!
See Illustration: Output Override Boards Conguration on page 16 and
Illustration: Output Schematics on page 16.
SC Terminals in Initial BAC-93xx Controllers
Initial shipments of BAC-93x1 controllers (before Date Code 1535, shipped
Sept. 1, 2015, S/N KMC1509xxxxxx) had the SC (Switched Common) terminals
of the two binary terminal blocks connected together on the circuit board. (See
Illustration: Initial (before Sept. 2015) BAC-93xx Controller SC Terminals on
page 15.)

KMC Conquest Controller Application Guide, AG150217K 15
BO1
BO2
SC
BO3
BO4
BO5
SC
BO6
Internal
Triacs
BAC-93x1
SC
Terminals
Joined
Illustration: Initial (before Sept. 2015) BAC-93xx Controller SC Terminals
Having SC terminals joined together is a convenience for most applications.
CAUTION
If SEPARATE transformers or power supplies are connected to the
SC terminals of these controllers, however, equipment damage could
occur.
For example, a transformer and output device connected to the triac on BO1 and
the corresponding (upper) SC terminal may conflict with another transformer and
device connected to the BO5 triac and the corresponding (lower) SC terminal.
NOTE: The switched common terminals are isolated from the circuit grounds
used for the universal output analog (VDC) circuitry in controllers.
Triacs are for VAC only.
For these BAC-9300 series controllers:
• Connect (only) a single source of power to either SC terminal.
• If separate circuits with separate power sources are needed, connect an in-
termediate relay (such as an REE-3101) to an output or replace the BAC-93xx
with a later unit (after Date Code 1535, shipped Sept. 1, 2015).
Later shipments of BAC-9300 series controllers have the SC terminals separate
as shown in Illustration: Conquest SC Terminals on page 14.
Installing Override Boards in BAC/CAN-5900 Series
For enhanced output options, such as manual control or using large relays or
devices that cannot be powered directly from a standard output, install output
override boards (also called “cards”). See Illustration: Output Override Boards
Conguration on page 16.
Output boards have an accessible three-position slide switch for selecting the
“Hand-Off-Auto” functions:
• While in the “Hand” (H) position, the output is manually energized, and the
controller receives a feedback signal to indicate the output has been overrid-
den.
• While in the “Off” (O) position, the output is manually de-energized, and
the controller receives a feedback signal to indicate the output has been
overridden.
• While in the “Auto” (A) position, the output is under the command of the
controller.
Each output board also has a red LED that illuminates when the output is turned
On (either manually or automatically).

16 KMC Conquest Controller Application Guide, AG150217K
1
2
3
4
5
6
7
8
4–20 mA Device
(on HPO-6704)
Override
Boards
Jumpers
0–10 VDC Device
(on HPO-6702)
UO1
SC
UO2
GND
UO3
SC
UO4
GND
UO5
SC
UO6
GND
UO7
SC
UO8
GND
(+)
(–)
Primary
Voltage
(+)
(–)
Contactor
(on HPO-6701 Triac)
Contactor
(on HPO-6705 NC Relay)
Contactor
(on HPO-6703 NO Relay)
Primary
Voltage
Illustration: Output Override Boards Conguration
UO7 (NO Relay)
SC (7 and 8)
UO8 (NC Relay)
GND
HPO-6703/6705 Relay Boards
(Coils Controlled by Controller Circuitry)
UO3 (Analog)
SC
UO4 (Analog)
GND
Jumpers
To
Controller
Circuitry
Simplified Schematic of Override
Board Relay (SC) Outputs
Simplified Schematic of Standard
Analog (GND) Outputs
Illustration: Output Schematics
The following output boards are available from KMC Controls:
OUTPUT OVERRIDE BOARDS
Model Number Output Type*
HPO-6701** Triac (AC only): zero-cross switching, optical isolation, 12 VAC
min. and 30 VAC max. voltage, 20 mA min. and 1 A max. current
HPO-6702 0–10 VDC analog: short protection, 100 mA max., adjustable
override potentiometer
HPO-6704
4–20 mA current loop: short protection, adjustable override
potentiometer (since the HPO-6704 supplies the power, it will not
work with a 4–20 mA device that also supplies its own power)
HPO-6703* Normally open relay: 30 VAC/VDC, 2 A max.
HPO-6705* Normally closed relay: 30 VAC/VDC, 2 A max.
*For more information, see the HPO-6700 Series Output Override Boards Data
Sheet.
**With the HPO-6701 triac and HPO-6703/6705 relays, use the Switched Com-
mon terminals instead of Ground.

KMC Conquest Controller Application Guide, AG150217K 17
NOTE: For 4–20 ma applications with the HPO6704, see also the 4–20 mA
Wiring for Controllers Application Guide.
CAUTION
Connecting 24 VAC or other signals that exceed the operation
specications of the controller before the output jumper is removed
will damage the controller. Remove the jumper and install the override
board before connecting AC or other voltage to the output terminals of
the controller.
To install the HPO-6700 series override boards:
1. Disconnect the power to the controller.
2. Pull the top edge of the (translucent black) override board cover away from
the case and open the cover.
3. Remove the jumper from the relevant mounting header pins. See Illustration:
Output Override Boards Conguration on page 16.
4. Position the board in the relevant slot with the Hand-Off-Auto selection
switch positioned toward the output connections.
5. Slide the board down the integral board tracks onto the header pins.
6. Set the selection switch on the override board to the desired position. A
(Automatic) is the top position of the switch, O (Off) is the center position,
and H (“Hand” or On) is on the bottom position.
7. Repeat steps 3 through 6 to install additional boards.
8. Close the override board cover.
9. Connect the output devices to the controller outputs. See Grounds Versus
Switched (Relay) Commons on page 14.
10. Reconnect the power.
NOTE: If a board is to be moved or removed, reinstall the (HPO-0063) jumper
(removed in Step 3) on the two pins closest to the outputs.
NOTE: For 4–20 ma applications, see also the 4–20 mA Wiring for Controllers
Application Guide.

18 KMC Conquest Controller Application Guide, AG150217K
Connecting a VAV Remote Actuator to a BAC-9311
Instead of using a BAC-9000 series controller-actuator in a VAV application,
using a BAC-9311 with a remote actuator provides additional options, such as
higher torque or fail-safe. The tri-state actuator should be connected to the BO5,
BO6, and SC terminals of the triac (VAC only) outputs. See Illustration: Remote
Actuator Wiring on page 18.
CW
CCW
T
COM
Actuator
BAC-9311
BO5
SC
BO6
Primary
Voltage
24 VAC (Only)
Illustration: Remote Actuator Wiring
See Illustration: Remote Actuators for a BAC-9311 on page 18 to select an
appropriate actuator. Some applications may require custom programming.
TRI-STATE
MODELS*
TORQUE (IN-LB.)
25 40 45 80 90 180 320
NON-FAIL-SAFE
MEP-4201 4
MEP-40x1/40x3 4
MEP-4501 4
MEP-48x1/48x3 4
MEP-4901 4
MEP-7501/7503 4
MEP-7801/7803 4
FAIL-SAFE
MEP-4251 4
MEP-4551 4
MEP-4951 4
MEP-7551/7553 4
MEP-7851/7853 4
*See the relevant data sheet for options and other specications.
Illustration: Remote Actuators for a BAC-9311

KMC Conquest Controller Application Guide, AG150217K 19
MS/TP Network Connections
Connections and Wiring


























S
+B
-A
S
+B
-A
S
+B
-A
Redundant Wiring
Option for
Enhanced Reliability
Illustration: MS/TP Network Wiring (Standard and Redundant Wiring)
Use the following principles when connecting a controller to an MS/TP network:
• Use 18 gauge, twisted-pair, shielded cable with capacitance of no more
than 51 picofarads per foot (167 pf/m) for all network wiring. (Belden cable
model #82760 or equivalent meets KMC requirements.)
• Connect the –A terminal in parallel with all other –A terminals and the +B
terminal in parallel with all other +B terminals. See Illustration: MS/TP Net-
work Wiring (Standard and Redundant Wiring) on page 19.
• Connect the shields of the cable together at each controller. For KMC BAC-
net controllers use the S (Shield) terminal. The S terminal is provided as a
connecting point for the shield. The terminal is not connected to the circuit
ground of the controller. When connecting to controllers from other manu-
facturers, verify the shield connection is not connected to ground.
• Connect the shield to an earth ground at one end only.
• To maintain communications in case of an open conductor on the network
cable, use redundant wiring routed separately to enhance reliability. See
Illustration: MS/TP Network Wiring (Standard and Redundant Wiring) on
page 19.
• Connect no more than 128 addressable BACnet master devices (total) to
one MS/TP network. The devices can be any mix of controllers or routers.
(Up to 127 slave devices can also be connected.)
• Limiting the MS/TP network size to no more than about 60 controllers will
optimize network performance.
• If the network has more than 31 MS/TP devices or if the cable length ex-
ceeds 4,000 feet (1,220 meters), use a KMD-5575 repeater (on an MS/TP-on-

20 KMC Conquest Controller Application Guide, AG150217K
ly network if the baud rate on the network is no higher than 38.4K baud) or
a faster KMC BAC-5051E router with an Ethernet network. For each network
segment, connect the shields to a good earth ground at only one end of the
segment; tape back the shield ground at the other end. Generally, use no
more than four KMD-5575 repeaters per MS/TP network.
• Use a KMC KMD-5567 surge suppressor where a cable exits the building.
NOTE: See Planning BACnet Networks (Application Note AN0404A) for
additional information about installing controllers.
NOTE: To temporarily disconnect the controller from the network, pull out the
isolation bulb assembly or the MS/TP terminal block from its connector.
EOL (End of Line) Termination Switches
The controllers on the physical ends of the EIA-485 wiring segment must have
EOL (End of Line) termination enabled for proper network operation. In the end
controllers (only), turn the EOL swi tches On. See Illustration: End-of-Line
Termination on page 20. Verify that all other controllers have EOLs turned Off
(as shipped from the factory).
EOL On EOL Off EOL Off EOL On
Illustration: End-of-Line Termination
Ethernet Network Connections
NOTE: See also (Status) Indicators on page 7!
The controller connects in the same manner as other Ethernet devices. Connect
a standard T568B CAT 5 or CAT 6 Ethernet cable from the Ethernet port on the
controller to a network router, switch, or hub.
CAUTION
Do NOT plug the cable meant for Ethernet communications into the
Room Sensor jack. The Room Sensor port powers a NetSensor, and
the supplied voltage may damage an Ethernet card, switch, or router to
which it is accidentally connected. See Illustration: Inputs and Ports
(Early BAC-9001CE) on page 9 and Illustration: Room Sensor and
Dual Ethernet Ports on page 9.
NOTE: Early model BAC-59xxE and BAC-9xxE models had a single Ethernet
port. In mid-2016, dual port models began replacing the single port
models. On these newer models, the Room Sensor port is yellow instead
of black to help differentiate it from the black Ethernet ports.