Product Overview

Table Of Contents
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 dierent 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 congure 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 dierent 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 dierent networked
controller with Device Instance 2010.)
1. In the local FlexStat, congure 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 cong-
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.