DDC Online direct digital controls
Siemens - APOGEE System  

Terminal Box Controller; Constant Volume Controller; Dual Duct Controller; Unit Conditioner Controller; Unit Vent Controller; Heat Pump Controller; Room Pressurization Controller; Laboratory Room Controller; Fume Hood Controller

Secondary Control Units
Terminal Equipment Controller Series (TEC)
Date Last Saved: 12/13/2007 8:59:41 AM

Product Name(s): Terminal Box Controller; Constant Volume Controller; Dual Duct Controller; Unit Conditioner Controller; Unit Vent Controller; Heat Pump Controller; Room Pressurization Controller; Laboratory Room Controller; Fume Hood Controller
Product Description: The TEC Series are secondary controllers with fixed I/O designed for specific types of air terminal and packaged HVAC equipment applications. They reside on the secondary P1 Field-Level Network, and can be programmed using either standard template-based methods (for common control sequences) or custom programmed.
Product Application(s): Terminal Box Controller - designed for pressure independent VAV air terminal applications with or without reheat options. Constant Volume Controller - designed for pressure independent temperature control and constant volume air terminal applications. Dual-Duct Controller - offered with one and two air velocity sensor configurations and are designed for pressure independent dual-duct VAV and constant volume air terminal applications. Unit Conditioner Controller - designed for pressure dependent boxes, fan coil units, and induction units. Unit Vent Controller - designed for unit ventilators for ASHRAE Cycle I, ASHRAE Cycle II, ASHRAE Cycle III, and Nesbitt Cycle W (0-10V controller only) applications. Heat Pump Controller - designed for water source heat pumps with ventilation or mixed air control and air to air heat pumps with ventilation and mixed air control. Single or multiple stage configurations are offered. Room Pressurization Controller - designed for room pressurization and room temperature control. The RPC controls a room's supply and exhaust terminal units to maintain differential flow between the supply and exhaust. Typical applications include isolation rooms, surgical suites, labs without fume hoods or wherever positive or negative pressurization of the room is critical. Laboratory Room Controller - designed for similar applications as the Room Pressure Controller, but adds the capability to interface with fume hoods and Siemens' Fume Hood Controller. Flow control speed of response listed at 1.5 sec. The pneumatic version uses 2 DO-to-pneumatic converters. Fume Hood Controller - designed for VAV control of laboratory fume hoods. The controller maintains face velocity as the fume hood sash is raised and lowered. This device must be used with Siemens' electronic or pneumatic Fume Hood Exhaust Terminal. An Operator Display Panel is also available. Face velocity is calculated from input parameters and sash position.
Point Quantity Characteristics
Analog Input (AI): See below Thermistor
Velocity Sensor

Setpoint Adj (optional)
Digital Input (DI): See below Dry Contact
Universal Input (AI or DI): See below AI Thermistor
Dry Contact
Analog Output (AO): See below 0-10 Vdc
Digital Output (DO): See below Optically Isolated Triac Switch

(2 Triacs are required per floating control point)
Universal Output (UO):
Control Unit Model #:AIDIUIDOAOUOOther
Terminal Box; 540-100, 540-200; (w/autozero), 540-100C, 540-200C; (w/ Secure Mode) 2 2 1 6 1
Constant Volume; 540-103, 540-104; (w/autozero), 540-103C, 540-104C; (w/ Secure Mode) 2 2 1 6 1
Dual Duct; 540-106, 540-107; (w/autozero) 2 2 1 6 1
Dual Duct Controller; 540-506, 540-507; (w/autozero) 2 2 1 8 2
Unit Conditioner; 540-110, 540-110C; (w/ Secure Mode) 2 2 1 6
Unit Vent; 540-509 2 3 1 8 3
Heat Pump; Single Stage 540-105 2 2 1 6
Heat Pump; Multi Stage 540-505 2 3 1 8
Room Pressurization; 540-516, 540-517; (w/autozero) 2 2 1 8 2
Room Pressurization; Pneumatic Output; 540-716, 540-717; (w/autozero) 2 2 1 8 (3) Pneumatic (using Triacs) 2
Laboratory Room; 540-00362 3 (1 fume hood AI) 2 1 8 2
Laboratory Room; Pneumatic Output; 546-00360, (w/autozero) 3 (1 fume hood AI) 2 1 8 (3) Pneumatic (using Triacs) 2
Fume Hood 2 (Plus 5 sash position sensors) 1 3 (2 for floating) 1 2
A/D Converter Resolution
8 bit
10 bit Air Velocity Sensor (actually a frequency counter)
12 bit
16 bit
Other 6 bit
D/A Converter Resolution
6 bit
8 bit
10 bit
No Analog Output
HOA switches provided on each output?
Note: These are also available as an add-on from 3rd party vendors.
Both AO and DO
DO Only
Indicating status LED on each output?
AO and DO
AO Only
DO Only
Integral Flow Sensor? Yes
Integral Damper Actuator? Yes -- Actuating TEC (ATEC) products offered.
Can controller accept occupant override from thermostat? Yes
Can controller accept occupancy sensor input? Yes
Expander Boards
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
(1) - Proprietary to secondary 'Protocol 1 Field Level Network (P1)' or LonWorks for some TEC models @ 4.8 kbps (polling)
External Communication Ports, Speeds and Access Devices (1) - EIA-232 laptop/PC communication ports with RJ-11 jack @ up to 1.2 kbps
To: Zone-based port on thermostat (optional)
Additional Information (Optional) P1 FLN can be wired or wireless
Network Accessing Capabilities via Controller
Access controller only
Access controller plus additional controllers on network segment / LAN
Access all controllers on system
No access available on this controller
Controller Access Devices
Local Display Panel (controller-mounted)
Local Display Panel (zone-mounted)
Handheld Interface Device (proprietary device)
PDA (3rd-Party HID)
Zone-Based port (details below)
Zone-Based Interface Access Optional thermostats available with port to access controller via laptop.
Zone Interface Hardware
Zone-Mounted touchpad (thermostat or stand-alone display) See Siemens APOGEE 2000 Series thermostat products.
HID (proprietary device)
PDA (3rd party HID, with software)
*Note: This section covers the capabilities for accessing the controller or other parts of the network from the controller (i.e. 'bottom-up').
Standard access functionality is covered in the Architecture and Software sections.
**Does NOT include front-end OI functions. See vendor for specific functions available.
Functions Available Through Field Interface**:View ParamsChange ParamsChange
O&M SupportTAB/Cx Support
Local Display Panel (controller-mounted)
Local Display Panel (zone-mounted)
Handheld Interface Device (proprietary device)
PDA (3rd-Party HID)
Zone-Based port (details below)
Microprocessor(s) Motorola 68HC11
Clock Type
Powered, battery-backed
Battery powered
Powered, no battery backing
Clock Synchronization N.A.
Volatile Memory (RAM) Capacity 0.7 kb
Volatile Memory (RAM) Uses
RAM use unrestricted
RAM use restricted as shown below
Information Not Provided
Program Execution / Calculation storage
Data / Trends / Alarms storage
Data / Trends / Alarms storage
Configuration / Parameter storage
Control Programming storage
Is Volatile Memory Supported By Battery? No
Battery Type(s) N.A.
Battery Life N.A.
Backup Battery Operating Time N.A.
Non-Volatile Memory Capacity (EEPROM/Flash)* 15-20 Kb
Non-Volatile Memory Uses
Data / Trends / Alarms / Calculation Storage
Configuration / Parameter Storage setpoints, parameters, user settings, schedules, etc.
Control Programming Storage
Controller Operating System
Controller Operating System
Additional Information
* Items in NV memory are not lost upon power or battery failure. Other types of NV memory such as EPROM, NOVROM, etc. do not directly impact system performance.
Can trend data be stored in this controller? No
How many total trend values can be stored? N.A.
What is the controllers role in trending? None. Trend point data is called by the SI and stored temporarily before being archived at the OWS.
Can controller be programmed to 'push' data to archive or are trends 'pulled' from controller?
When full, does controller automatically send up trend data, overwrite data, or stop logging data? N.A.
Programming Method(s) Pre-existing programs ('applications') are configured using Voyager. Voyager is a Windows-based program that allows users to communicate directly with any Terminal Equipment Controller to view, modify, or command point information. Initially, secondary control units must be configured locally, then address is kept in EEPROM allowing complete access and re-configuration capability from workstation or portable terminals.
Resident vs Non-Resident Program Execution Resident programming will allow control to function as stand-alone. Primary controllers or supervisory interface devices manage scheduling, trending, global control, and communication functions.
Resident/Supervisory. This controller supervises the scheduling of other controllers.
Resident/Stand Alone. This controller contains its own schedule.
Non-Resident. This controller is dependent upon another controller for its schedule.
None. This controller has no scheduling features.
Resident Energy Management
Energy management algorithms for this controller can be custom programmed
Pre-programmed/built-in algorithms available, and are fully editable using custom programming
Pre-Programmed/built-in with limited editing via template-based programming
Controller is not typically used for energy management functions
Others See 'Additional Programming Functions' below
Specific Pre-Programmed Algorithms Available
None (custom programming only)
None (not applicable)
Optimal Start/Optimal Stop
Peak Demand Limiting/Load Shedding
Economizer (enthalpy, dry-bulb, CO2, modulating/2-position, etc.)
Other See 'Additional Programming Functions' below
Additional Energy Management functions are resident at SI
Additional Programming Functions A wide variety of configurable energy management features are available on the various TECs (dependent on model and application).
DDC Loops (P, PI, PID) PID
Automatic PID Tuning Feature No
Automatical-Dial Alarm Support No
Does controller perform multiple retries and buffer/store alarm until connection is made? No
Are multiple destinations possible? No
Upon controller power loss or hardware failure:
Are network communications affected? No
Is loss recognized on/by the network and alarm reported? Yes
DO and AO response?
Outputs fail to a user pre-specified position
Outputs fail to a normal (unpowered) position
Outputs fail to last position
Volatile memory functions?
Retained for life of backup battery
Other Controller has no volatile memory
Upon restoration of power does the controller:
Auto-reboot without operator intervention? Yes
Automatically reset/synchronize the clock? No clock
Update all monitored functions? Yes - update received from field panel -- MBC/RBC, MEC or FLNC (SI)
Generate an alarm if backup battery is dead? No backup battery
Upon network or communications failure does controller:
Continue to operate standalone? Yes
Operate with last global settings or user-specified value? N.A.
Do broken network segments continue to communicate within the remaining segment?
(Note: May depend on proper termination of segments for higher speed networks.)
Does network automatically reconfigure upon restoration? Yes
Does network store 'loss of communications' alarm with time of event? Yes
Additional Information (optional)
Self Test Diagnostics
Does controller have internal self-test diagnostics to check:
Processor failure? Yes
Internal hardware failure? Yes
Open/shortened sensor? Yes
Control Enclosure Controller is housed in a plastic case.
Power Supply Required
Voltage 24 Vac
VA 3.5 - 6 VA (plus loads)
Surge Protection Yes
Underwriters Laboratories UL 864 UDTZ


CSA 22.2 No 205
FCC Part 15, Sub-Part B, Class A
CE CISPR 22 Class A

European EMC Directive (CE): Commercial Levels

European Low Voltage Directive (LVD)

Australian Compatibility Framework
LonMark Certified
No - but LonWorks compatible
Information not provided
BACnet (BTL) Certified
Not submitted for testing
Information not provided