DDC Online direct digital controls
Control Pak - EM Turbo  

13/29;48/193;96/193

Secondary Control Units
EM Turbo Series 13/29 48/193 96/193
Date Last Saved: 5/21/2004 11:03:03 AM

Product Name(s): 13/29;48/193;96/193
Product Description: Application specific-like general purpose controllers. Turbo 13/29 has a base point count of 13 expandable to 29. Turbo 48/193 has a base point count of up to 48 points expandable to 193 using a separate expansion unit. Turbo 96/193 has a base point count of up to 96 points expandable to 193 using a separate expansion unit.
Product Application(s): Used in general HVAC applications including medium to high point count air-handling units, chillers, and boilers. The ManagePak software uses worksheets to define object oriented control functions: Zone - schedule of setpoints, optimization selection Loop - demand limiting, PID, deadband Inputs/outputs - temperature humidity, status, etc. Timer - delay, pulsing, duty cycling, counting Optimizer - optimized start/stop Logic - AND, OR, etc Math - add, subtract, multiply, divide, etc. Network - information sharing over LAN Trend - trend log setup Annunciator - Alarms, global scheduling
Point Quantity Characteristics
Analog Input (AI):
Digital Input (DI): See below 34 Hz pulse
Universal Input (AI or DI): See below 0-20 mA
0-2.4 Vdc
500-5000 ohm RTD range
10-24 Vac/Vdc externally powered DI
Analog Output (AO): See below 0-12 Vdc
0-24 Vdc
0-20 mA (into 500 ohm max)
Digital Output (DO): See below Form C relay, 24 Vac / 3 Amp
Universal Output (UO):
Other:
Control Unit Model #:AIDIUIDOAOUOOther
EM Turbo 13/2 1 4 4 4
EM Turbo 48/193 16 1 16 16
EM Turbo 96/193 32 16+1 16 32
A/D Converter Resolution
8 bit
10 bit
12 bit
16 bit
Other (13-bit)
D/A Converter Resolution
6 bit
8 bit
10 bit
No Analog Output
Other
HOA switches provided on each output?
Note: These are also available as an add-on from 3rd party vendors.
No
Both AO and DO
DO Only
Other
Indicating status LED on each output?
No
AO and DO
AO Only
DO Only
Other
Integral Flow Sensor?
Integral Damper Actuator?
Can controller accept occupant override from thermostat?
Can controller accept occupancy sensor input?
Expander Boards
Expansion Device Model #AIDIUIDOAOUOOther
EM Turbo 13/29
P/N 50.1176 (Maximum of 2 Cards) 4
P/N 50.1178 (Maximum of 1 card) 4
P/N 50.1177 (Maximum of 1 card)
EM Turbo 48/193& 96/193
P/N 50.1007 16
P/N 50.1009 P/N 50.1010 (piggy back on 1009) 8/8
P/N 50.1011 16
P/N 50.1074
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
(1) Proprietary to EIA-485 @ 9.6 Kbps
External Communication Ports, Speeds and Access Devices (1) EIA-232, modem/direct connect to OWS @ up to 9.6 Kbps

(1) EIA-232, dumb terminal (CRT/keyboard) @ up to 1.2 Kbps

(1) EIA-232, printer port @ @ up to 1.2 Kbps

(1) Optional serial port for: Handheld or wall-mount Remote Terminal Unit (RTU) for set-up, edit, override, and monitoring functions. Remote Command Units (RCU) for on/off or override actions, a Remote Setpoint Unit (RSU) for setpoint display, or up to 4 Remote Annunciator Units (RAU) for status and alarm indication.

(1) Optional serial port for cassette tape backup of RAM (application control program)
Additional Information (Optional)
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
Other
Controller Access Devices
Laptop/PC
Local Display Panel (controller-mounted)
Local Display Panel (zone-mounted)
Handheld Interface Device (proprietary device)
PDA (3rd-Party HID)
Zone-Based port (details below)
Other
Zone-Based Interface Access None. See 'External Communication Ports, Speeds, and Access Devices' above.
Zone Interface Hardware
Zone-Mounted touchpad (thermostat or stand-alone display)
HID (proprietary device)
PDA (3rd party HID, with software)
Laptop/PC
none
Other
*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
Programs/Logic
O&M SupportTAB/Cx Support
Laptop/PC
Local Display Panel (controller-mounted)
Local Display Panel (zone-mounted)
Handheld Interface Device (proprietary device)
PDA (3rd-Party HID)
Zone-Based port (details below)
Other
Microprocessor(s) 8 bit
Clock Type
Powered, battery-backed
Battery powered
Powered, no battery backing
None
Other
Clock Synchronization Synched up by a master controller (unit 'number one')
Volatile Memory (RAM) Capacity 32 kB RAM for application settings (setpoints, ranges, alarm definitions, trending configurations, custom logic/math functions, etc.)
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
Others
Is Volatile Memory Supported By Battery? Yes
Battery Type(s) Lithium
Battery Life Information not provided
Backup Battery Operating Time 40 days
Non-Volatile Memory Capacity (EEPROM/Flash)* 64 kB ROM contains the control algorithms/programs and energy management routines
Non-Volatile Memory Uses
Data / Trends / Alarms / Calculation Storage
Configuration / Parameter Storage
Control Programming Storage
Controller Operating System
Other
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? Yes
How many total trend values can be stored? Each controller can store up to 99 trend logs (files) with up to 12 different objects (points) contained in each trend log file. Up to 254 trend data values can be obtained per object (point).
What is the controllers role in trending? Trend data can be pulled up by 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? Overwrite data
Programming Method(s) ManagePak software uses template/menu based worksheets. The ManagePak software also provides some line-type programming to perform logical and math operations.
Resident vs Non-Resident Program Execution All program execution is controller resident
Scheduling
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.
Other
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 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 Below
Additional Energy Management functions are resident at SI
Additional Programming Functions Duty cycling, deadband control
DDC Loops (P, PI, PID) PID
Automatic PID Tuning Feature No
Automatical-Dial Alarm Support Abailable from controller
Does controller perform multiple retries and buffer/store alarm until connection is made? Information not provided
Are multiple destinations possible? Yes- up to 3 destinations
Upon controller power loss or hardware failure:
Are network communications affected? No
Is loss recognized on/by the network and alarm reported? Information not provided
DO and AO response?
Outputs fail to a user pre-specified position
Outputs fail to a normal (unpowered) position
Outputs fail to last position
Other
Volatile memory functions?
Lost
Retained for life of backup battery
Other
Upon restoration of power does the controller:
Auto-reboot without operator intervention? Information not provided
Automatically reset/synchronize the clock? Information not provided
Update all monitored functions? Yes
Generate an alarm if backup battery is dead? No
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.)
Information not provided
Does network automatically reconfigure upon restoration? Information not provided
Does network store 'loss of communications' alarm with time of event? Information not provided
Additional Information (optional) Information not provided
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?
 
Control Enclosure 16 gauge welded steel construction
Power Supply Required
Voltage 120 Vac, 60 Hz
VA EM Turbo 13/29: 50 watts
EM Turbo 48/193: 150 watts
EM Turbo 96/193: 150 watts
Surge Protection Metal oxide varistors (MOVs) protect I/O and LAN.
RF filter protects AC power line.
Underwriters Laboratories UL 916 Standard for Energy Management Equipment
FCC
CE
LonMark Certified
Yes
No
No - but LonWorks compatible
Information not provided
BACnet (BTL) Certified
Yes
No
Not submitted for testing
Information not provided
Other