FlexStat 34 Operation Guide, Rev. R
CO
2
Level Is “Too High”
• See the CO
2
and DCV Sequences Are Not Work-
ing section above.
• To reduce nuisance complaints by occupants,
turn o the visibility of the CO
2
level rotation in
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 witha
modulatingeconomizeroptionisenabled. See
Damper Setup on page 7.
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. Asingle
incorrectswitchpositionmayaectmultiple
inputs.Allinputswitchesmustbelatchedin
eitherthe10KOhmorthe0–12VDCposition
evenifnoinputisconnected!Inputswitch
pairs(3-4,5-6,and7-8)mustneverhaveboth
switchessetinthesamedirection—ifswitch3
issettotheleft,forexample,4mustbesetto
theright(orviceversa).
• Check that the correct input type is selected on
the Inputs screen. A Type III thermistor is the
default on external inputs. See (Advanced) Inputs
on page 17.
• Check input wiring. See Wiring Issues on page 39.
• Check connected sensors.
• Using BACstage or TotalControl, check that the
input is not congured as “Out Of Service.”
• Restore the FlexStat to factory seings (see Reset-
ting the FlexStat on page 26) and recongure.
• For an external CO
2
sensor connected to IN9,
allow at least 15 minutes after installation for the
reading to stabilize.
Humidification/Dehumidification Issues
• See Humidity Setup on page 8.
Motion/Occupancy Sensor Does Not Work
• The initial rmware (R.1.0.0.0 and earlier) did not
support this sensor within the built-in selectable
programs. Custom programming was required—
see the FlexStatApplicationGuide. Upgrade to
the latest rmware 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 “o” times in the schedule. See
Schedules on page 24.
• 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 congured as “Out Of Service.”
• The FlexStat must be installed where there is a
clear view of typical trac 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,
paerns, conguration, programming, and other
issues, see the Motion/Occupancy Sensor section
in the FlexStatApplicationGuide.
Temperature Reading Is Incorrect
• Check that the correct °F/°C temperature scale is
selected—see Navigation on page 4.
• 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
conguration—see Sensor Setup on page 9.
• After applying power for the rst 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
oset—see (Advanced) Inputs on page 17.
• Check that the thermistor (on models without
humidity sensors) is centered in its hole at the
boom of the case and has an air gap around it.