Co Level Is "Too High; Dcv Menu Is Not Visible; Input Values Are Outside The Expected Range; Motion/Occupancy Sensor Does Not Work - KMC Controls FlexStat series Operation Manual

CO Level Is "Too High"
2
• See the CO and DCV Sequences Are Not Work-
2
ing section above.
• To reduce nuisance complaints by occupants,
turn off the visibility of the CO
the display. See (Advanced) User Interface (UI)
on page 21.

DCV Menu Is Not Visible

• In the BAC-12xxxx/13xxxx/14xxxx models, DCV
Setup is visible only when an application with a
modulating economizer option is enabled. See
Damper Setup on page

Input Values Are Outside the Expected Range

• Check that ALL the input pull-up resistor
switches are fully latched in the correct positions.
See the Connections and Wiring section of the
relevant FlexStat Installation Guide. A single
incorrect switch position may affect multiple
inputs. All input switches must be latched in
either the 10K Ohm or the 0–12 VDC position
even if no input is connected! Input switch
pairs (3-4, 5-6, and 7-8) must never have both
switches set to the left or both to the right—if
switch 3 is set to the left, for example, 4 must be
set to the right (or vice versa).
• Check that the correct input type is selected on
the Inputs screen. A Type III thermistor is the
default on IN2 through IN4. See (Advanced)
Inputs on page 17.
• Check input wiring. See Wiring Issues on page
• Check connected sensors.
• Using BACstage or TotalControl, check that the
input is not configured as "Out Of Service."
• Restore the FlexStat to factory settings (see Reset-
ting the FlexStat on page
• For an external CO
allow at least 15 minutes after installation for the
reading to stabilize.
FlexStat
level rotation in
2
7.
26) and reconfigure.
sensor connected to IN9,
2

Motion/Occupancy Sensor Does Not Work

• The initial firmware (R.1.0.0.0 and earlier) did not
support this sensor within the built-in selectable
programs. Custom programming was required—
see the FlexStat Application Guide. Upgrade to
the latest firmware for built-in support.
• After an initial power-up or restart, the motion/
occupancy sensor requires about 30 seconds
before it will begin responding to motion.
• The motion/occupancy sensor initiates override
only during "off" times in the schedule. See
Schedules on page
• Check that the motion sensor is enabled and
detects motion. See Motion Sensor Setup on page
8.
• Using BACstage or TotalControl, check that BI6
(occ status) is not configured as "Out Of Service."
• The FlexStat must be installed where there is a
clear view of typical traffic area (reliable range is
out to about 33 feet). Remove or move obstacles.
Reinstall the FlexStat in a more optimal location
if necessary.
• Connect remote motion sensors to an input
(requires custom programming).
• For more information on detection performance,
patterns, configuration, programming, and other
issues, see the Motion/Occupancy Sensor section
in the FlexStat Application Guide.

Temperature Reading Is Incorrect

39.
• Check that the correct °F/°C temperature scale is
selected—see Navigation on page
• Fahrenheit decimal values are not displayed by
default but can be enabled in the User Interface
menu—see Show Temperature Tenths (Decimals)
on page 21.
• Check for the correct remote temperature sensor
configuration—see Sensor Setup on page
• After applying power for the first time (or after an
outage), allow the FlexStat to self-calibrate a few
minutes before verifying temperature reading.
(Allow BAC-13xxxx/14xxxx FlexStats with CO2
sensors to stabilize for about 30 minutes.)
• If the discrepancy is small, adjust the calibration
offset—see (Advanced) Inputs on page
34
24.
4.
17.
Operation Guide, Rev. M
9.