DDC Online direct digital controls
Siemens - APOGEE System  

Unitary Controller (UC)

Secondary Control Units
Unitary Controller (UC)
Date Last Saved: 12/13/2007 8:59:58 AM

Product Name(s): Unitary Controller (UC)
Product Description: The Unitary Controller is a programmable, standalone controller with 7/5 I/O, expandable to 14/10 I/O. The Unitary Controller resides on the secondary Floor Level (P1) polling network. The UC can also be configured for typical applications where custom programming is not required.
Product Application(s): The Unitary Controller is designed for control, monitoring and energy management functions for a variety of unitary and packaged equipment, including rooftop units; multizone, VAV, and dual-duct AHU applications; steam converters, and similar equipment. It has vibration protection and an enclosure designed to allow for direct mounting on HVAC equipment if needed. Recent modifications to the MEC (allowing it to host TEC controllers) may cause the MEC to be used in place of the UC for custom programming applications.
Point Quantity Characteristics
Analog Input (AI):
Digital Input (DI): 3 or 6/See below Dry Contact

Up to 10 Hz Pulsed
Note: 1 of the 3 DI points can be pulse accumulator type
Universal Input (AI or DI): 4 or 8/See below 4-20 mA

0-10 Vdc

RTD (1000W platinum)

Dry Contact
Analog Output (AO): 3 or 6 0-20ma

Digital Output (DO): 2 or 4/See below Contact (120 Vac 4A / 240 Vac 2 A)
Universal Output (UO):
A/D Converter Resolution
8 bit
10 bit
12 bit
16 bit
D/A Converter Resolution
6 bit
8 bit
10 bit
No Analog Output
Other 15 bit
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?
Integral Damper Actuator?
Can controller accept occupant override from thermostat?
Can controller accept occupancy sensor input?
Expander Boards The Unitary Controller requires one or two I/O cards. The second card doubles the point counts indicated above.
Expansion Device Model #AIDIUIDOAOUOOther
544 120Unitary Controller I/O Card; *One digital input can be a pulse accumulator. All 3 AO can be field-configured as DO 3* 4 2 3*
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
(1) - Proprietary to secondary 'Protocol 1 Floor Network (P1)' @ 4.8 kbps (polling)
External Communication Ports, Speeds and Access Devices (1) - EIA-232 laptop/PC communication ports with RJ-11 jack @ up to 9.6 kbps
To: Zone-based port on thermostat (optional)
Additional Information (Optional) Up to 32 UCs can be connected to a single P1 LAN, for a maximum of 96 UCs per MBC or other 'field panel'.
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)
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, 8 MHz
Clock Type
Powered, battery-backed
Battery powered
Powered, no battery backing
Clock Synchronization A single workstation is designated as the master time clock. This workstation resets all clocks on the field panels and controllers across the network.
Volatile Memory (RAM) Capacity 32 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
Configuration / Parameter storage
Control Programming storage
Is Volatile Memory Supported By Battery? Yes
Battery Type(s) Lithium
Battery Life Information not provided
Backup Battery Operating Time 5 months (for clock only)
Non-Volatile Memory Capacity (EEPROM/Flash)* 32 kB
Non-Volatile Memory Uses
Data / Trends / Alarms / Calculation Storage
Configuration / Parameter Storage setpoint, parameters, user settings, schedules, etc.
Control Programming Storage
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? Not Applicable
What is the controllers role in trending? None. Trend point data is called by the SI (NCM) and stored temporarily before 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? Not applicable
Programming Method(s) The UC is programmed from an operator workstation or laptop using DOS-based, proprietary line-based programming package Programming Tool Software. This software is the user interface to developing code, which is written using Process Control Language (PCL).

Once entered, programs can be configured using DOS-based Unitary Controller Interface Software (UCIS). UCIS is a template/menu-based program that allows users to communicate directly with the Unitary Controller to view, modify, or command point information. Initially, secondary control units must be configured locally, the 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
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.)
Additional Energy Management functions are resident at SI
Additional Programming Functions
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
Upon restoration of power does the controller:
Auto-reboot without operator intervention? Yes
Automatically reset/synchronize the clock? Yes
Update all monitored functions? Yes
Generate an alarm if backup battery is dead? Yes
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? Information not provided
Internal hardware failure? Information not provided
Open/shortened sensor? Information not provided
Others? Information not provided
Control Enclosure Controller is housed in a metal cabinet with optional door-mounted keypad display. Optional vibration isolation kit is also available.
Power Supply Required
Voltage 24 Vac
VA 42 VA (plus loads)
Surge Protection No
Underwriters Laboratories UL 864 UDTZ


CSA 22.2 No 205
FCC Class A Equipment, Part 15, Subpart J Industrial Control Equipment
CE CISPR 22 Class A

European EMC Directive (CE): Industrial 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