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) 18 Application Guide, Rev S
Modifying the Standard Control Basic Programs
Programs 1 through 5 and 6 through 10
Control Basic programs 1 through 5 are used for built-in applications
and can NOT be modied directly. Programs 6 through 10 are empty and
can be used for additional programming. Using BACstage or TotalControl,
a program (1 through 5) can be copied, pasted into a new program code
object (6 through 10), edited, and run in place of the original. (Although
programs 1–5 cannot be edited, they can be halted and set to not autorun
after restart.)
Because programs are executed sequentially, if a program is copied
and modied, ALL of the following programs must also be copied
(even if they are not modied)! For example, if program 2 is copied
into program 6 and modied, then programs 3 through 5 (even if they
contain no modications) must also be copied into programs 7 through
9. Then programs 2 through 5 are set to NOT autorun, programs 6
through 9 are set to autorun, and the FlexStat is restarted.
Program 1 Common Code and the User Interface
Program 1 interacts with the user interface (display and menus). If
Program 1 is copied and replaced, ensure that the common code (up to
the application branch code section) in Program 1 is running. Failure
to do so may disable one or more user interface functions.
In all models, the common code ends at nearly the boom of the entire
code and is before the application lines (as relevant to the model):
AHU_CODE, FCU_2_PIPE_CODE, etc.
In rmware R1.3.0.8 and after, the branch code section is somewhere
around line 518 to 578 in BAC-1xxx63/1xx63, line 522 to 605 in BAC-
1xxx36/1xx36, or line 370 to 496 in BAC-1xx30 and comes after:
END_COMMON_CODE:
END
Searching for “COMMON” will quickly nd the line. Earlier rmware
versions do not have this convenient ag.
In BAC-1xx63, rmware R1.3.0.4 and earlier, the branch code section is
somewhere around line 457 and looks similar to:
REM PERFORM APPROPRIATE SECTION OF CODE BASED ON
FLEXSTAT CONFIGURATION
IF APP_MAIN_TYPE = AHU THEN
GOTO AHU_CODE
ELSE IF APP_MAIN_TYPE = RTU THEN
GOTO RTU_CODE
ELSE IF APP_MAIN_TYPE = FCU THEN
IF APP_SUB_TYPE = PIPE2 THEN GOTO FCU_2_PIPE_CODE
IF APP_SUB_TYPE = PIPE4 THEN GOTO FCU_4_PIPE_CODE
ELSE IF APP_MAIN_TYPE = HP THEN
GOTO HP_CODE
ENDIF
In BAC-1xx36 rmware R1.3.0.4 and earlier, the branch code section
(ending the common code) is somewhere around line 511 and looks
similar to:
REM PERFORM APPROPRIATE SECTION OF CODE BASED ON
FLEXSTAT CONFIGURATION
IF APP_MAIN_TYPE = AHU THEN
GOTO AHU_CODE
ELSE IF APP_MAIN_TYPE = FCU THEN
IF APP_SUB_TYPE = PIPE2 THEN GOTO FCU_2_PIPE_CODE
IF APP_SUB_TYPE = PIPE4 THEN GOTO FCU_4_PIPE_CODE
ENDIF
END
In a BAC-1xx30, rmware R1.3.0.4 and earlier, because there is nothing
specic to applications other than the AHU, there is no branch code
section. However, there is the AHU_CODE label.
After the common code, the appropriate application specic section
should be copied, modied as necessary, and running as well.
NOTE: Customized programs are the responsibility of the user. KMC
Controls does not provide support for such programs.