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) 36 Application Guide, Rev S
Remote Sensors (Wired in Parallel)
Connected to a FlexStat Input
FlexStat
Obstruction
Obstruction
Adding Remote Motion Sensors
Situations that would need remote sensors to be connected to the Flex-
Stat include:
• Areas too large for adequate coverage by the FlexStat’s built-in sensor.
• Areas with obstructions that block sensor coverage.
• Use of FlexStat models that do not have a built-in sensor.
Remote motion sensors can be connected to one of the FlexStat’s avail-
able inputs. (Custom programming is required.) Multiple remote sen-
sors with dry (relay/switch) contacts can be wired in parallel to monitor
a variety of dierent zones.
An example Control Basic program (for BACstage or TotalControl) that
turns occupancy override on from remote sensors is:
IF AI2 < 1 THEN START BV40 : REM START EXTERNAL OCC
SNSR BV IF INPUT IS SHORTED
IF AI2 > 1 THEN STOP BV40 : REM STOP EXTERNAL OCC
SNSR BV IF INPUT IS OPEN
IF BV40 AND NOT BV1 THEN START BV2 : REM IF EXTER-
NAL OCC SNSR BV IS ACTIVATED AND FLEXSTAT IS NOT
IN OCC, START OVRD MODE
NOTE: The application must have one unused input. Input #2 is used
in this example and assumes Normally Open relays/switches
in the remote sensors. In such a case, the input pull-up resis-
tors should be set to 10K ohms, and SNSR2 in the Application
menu must be set to NOT USED.
NOTE: To trigger the occupancy override, the remote sensor contacts
must stay closed for two seconds or longer.
SYSTEM
SYSTEM ENABLE: AUTO
OCC OVRIDE (HRS):
INACTIVITY (SECS): 60
DISPLAY BLANKING: NO
0.5
NOTE: All Schedules must
be deleted or set to
OFF.
MOTION SENSOR
OCC OVERRIDE:
STATE: OCCUPIED
STANDBY: DISABLE
ENABLE
SCHEDULE
ENTIRE WEEK [MON–SUN]
WEEKDAYS [MON–FRI]
WEEKEND [SAT–SUN]
INDIVIDUAL DAYS
HOLIDAYS
ENTIRE WEEK
1: 12:00:00 AM
2:
3:
4:
5:
6:
[—>] DELETES ENTRY
OFF
NOTE: Motion Sensor Occupancy
Override must be enabled and
Standby should be disabled.
NOTE: System Occupancy Override
time should usually be re-
duced to 0.5 hours in the Sys-
tem menu. Alternately reduce
the time to less than 0.5 hours
using BACstage or TotalCon-
trol to change AV16’s present
value and relinquish default.
USER INTERFACE
MODE: HOSPITALITY
ROTATION VALUES
SHOW TEMP TENTHS: NO
HOSPITALITY OPTIONS
SETPT CNTRL:
SCHEDULE
NOTE: For Hospitality Mode, Set-
point Control must be set to
Schedule.
Menu Configuration
SENSOR SETUP
IN 2:
IN 9: NOT USED
SPACE TEMP: ONBOARD
-- IN 1 IS ONBOARD
NOT USED
NOTE: If IN2 or IN9 is used for the
input, congure it as “Not
Used” in the Sensor Setup
menu.
NOTE: See the FlexStat
Operation Guide for
more information on
these menus.