Product Overview
Table Of Contents
- Contents
- General Information (All Output Configurations)
- Overview and General Installation
- Mounting Considerations
- Wiring Considerations
- Inputs and Outputs
- Network Wiring
- Configuration Screens
- Custom Programming
- Sample Custom Applications
- CO2 Sensors and DCV
- Custom Web Graphics
- Hospitality and Locked User Interface Modes
- Motion/Occupancy Sensor
- Support
- Important Notices
- BAC-1xx63/1xxx63 Series (6 Relays and 3 Analog Outputs)
- Bills of Materials (BAC-1xx63/1xxx63)
- Sequence of Operation (BAC-1xx63/1xxx63)
- FlexStat (All Models) Common Features
- Space Temperature Setpoints and Modes
- Occupancy Modes
- Optimum Start
- Standby Mode
- Fan Control
- Sensor 2 (Fan Status or Discharge Air Temp)
- Economizer
- DCV (Demand Controlled Ventilation)—General Information
- DCV—Basic Configuration
- DCV—Standard Configuration
- DCV—Advanced Configuration
- Dehumidification
- Humidification (BAC-1x136 and BAC-1xx136 Only)
- Staged Heating and Cooling Parameters
- User Interface Display Backlight
- BAC-1xx63/1xxx63 Applications
- FlexStat (All Models) Common Features
- BAC-1xx36/1xxx36 Series (3 Relays and 6 Analog Outputs)
- BAC-1xx30 Series (3 Relays and 0 Analog Outputs)
- BAC-1xxx53 (5 Relays, 1 Triac, & 3 Analog Outputs)
- Index
FlexStat (General) 21 Application Guide, Rev S
Using Another Controller’s Sensors
FlexStats can use sensors connected to remote controllers on the same
network. For example, an outside air temperature sensor is wired to AI3
of a dierent networked controller (not a FlexStat) with Device Instance
2010. This program polls the outside air temperature every minute and
assigns the value to AV23 in the local FlexStat.
1. In BACstage or TotalControl add the following Control Basic pro-
gram and congure it to auto-run:
IF INTERVAL( 0:01:00 ) THEN AV23@8 = 2010.AI3
2. Restart the FlexStat.
NOTE: In FlexStats, an OAT sensor is connected to AI4, and AI4 is
mapped via Control Basic to AV23 for reference whenever the
OAT value is needed. The example above assumes the remote
sensor is connected to AI3 of a dierent model of controller.
For other types of sensor inputs, see the values in the chart
below.
FlexStat Sensors
Sensor Input Mapped AV
Space Temperature AI1 AV40
Space Humidity AI5 AV22
Space CO2 AI10 AV78
OAT AI4 AV23
MAT AI3 (None, see below)
DAT or FST AI2 (None, see below)
NOTE: It may take a minute or two before the remote temperature
starts displaying correctly.
If the FlexStat does not have a mapped AV for a desired input (e.g.,
MAT), use the following approach instead. (The example below assumes
a mixed air temperature sensor is wired to AI5 of a dierent networked
controller with Device Instance 2010.)
1. In the local FlexStat, congure the original mixed air temperature
object AI3 to “Out Of Service” in BACstage or TotalControl.
2. Add either one of the following Control Basic programs and cong-
ure it to auto-run:
Code Example #1
IF INTERVAL( 0:01:00 ) THEN AI3 = 2010.AI5
Code Example #2
ALIAS( 2010, AI5, PV, MixedAirTemp, 0:01:00,
NONE )
AI3 = MixedAirTemp
3. Restart the FlexStat.
NOTE: Alias is a command used with the FlexStat, Building Controller
and all new Next Generation KMC BACnet controllers. See the
Help system in TotalControl or BACstage for more informa-
tion.
NOTE: Customized programs are the responsibility of the user. KMC
Controls does not provide support for such programs.
NOTE: For additional custom applications not covered in this section,
see KMC’s Digital Designer’s Guide (SP-022) and adapt pro-
grams for other controllers for use in the FlexStat.