DDC Online direct digital controls
Siemens - APOGEE System  

Modular Equipment Controllers (MEC):; POWER MEC Series 1100 (formerly MEC Series 100); POWER MEC Series 1200 (formerly MEC Series 200); POWER MEC Series 1300 (formerly MEC Series 300)

Primary Control Unit
Modular Equipment Controller (MEC)
Date Last Saved: 12/13/2007 8:59:06 AM

Product Name(s): Modular Equipment Controllers (MEC):; POWER MEC Series 1100 (formerly MEC Series 100); POWER MEC Series 1200 (formerly MEC Series 200); POWER MEC Series 1300 (formerly MEC Series 300)
Product Description: MECs are modular, programmable primary control units available with a range of fixed features to meet site-specific needs. All MEC models include 32 fixed on-board I/O, power supply, and controller board. POWER MEC 12xx models add I/O expansion capability. POWER MEC 13xx models add I/O expansion capability and auto-dial modem support. POWER MEC 1xxxEx models support industry standard TCP/IP networks through a 10/100 BaseT for ALN communications. POWER MEC 12xxF and 13xxF models add three FLN connections for a total of 96 devices. POWER MEC 12xxL and 13xxL models have LonWorks compatibility, and are equipped with a Neuron Micropsocessor and FTT-10A Transciever. Instead of three connections, it has a single connection for a LonWorks network.
Product Application(s): MECs provide central monitoring and control and energy management functions for general HVAC applications including air-handling units, chillers/boiler/central plant control and distribution systems, data acquisition, and other multi-equipment applications. MECs are small, fixed-feature APOGEE controllers that can be used (along with the FLNC) as a lower-cost alternative to support a secondary network. When paired with the FLNC, the custom programming capability of the MEC can replace the UC (secondary controller), while still supporting the application-specific TECs as needed.
Point Quantity Characteristics
Analog Input (AI): 8 4-20 mA

0-10 Vdc

RTD (1000 W platinum)
Digital Input (DI): 8 Dry contact (potential free)

Voltage input (250 Vac max)

Up to 25 Hz Pulsed (4 of the 8 DI points can be pulse accumulator points)
Universal Input (AI or DI): N.A.
Analog Output (AO): 8 0-10 Vdc

4-20 mA

0-20 psi
Digital Output (DO): 8 Form C Rated Relays (110/220V)
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
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? N.A.
Integral Damper Actuator? N.A.
Can controller accept occupant override from thermostat? N.A.
Can controller accept occupancy sensor input? N.A.
Expander Boards The MEC Series 2xx and 3xx and POWER MEC Series 12xx and 13xx support analog and digital expansion point blocks.
Expansion Device Model #AIDIUIDOAOUOOther
549-214; Analog Point Block, 24V, HOA-ready 4 4
549-215; Analog Point Block, 24V, with HOA 4 4
549-209; Analog Point Block, 24V 8
549-212; Digital Point Block, 24V, HOA-ready 4 4
549-213; Digital Point Block, 24V, with HOA 4 4
549-210; Digital Point Block, 24V, HOA-ready 8 4
549-211; Digital Point Block, 24V, with HOA 8 4
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
POWER MECs communicate with other field panels or workstations on a peer-to-peer Automation Level Network (ALN) or with an optional remote connection to a central console.

Depending on the model of MEC purchased, the ALN may either be prorietary 'P2" or optional TCP/IP protocol, and the FLN may either be P1, BACnet MS/TP, or LonTalk protocol.

POWER MEC 1xxxEx models support standard TCP/IP networks through a 10/100 BaseT for ALN communications.

POWER MEC 12xxL and 13xxL models have LonWorks compatibility, and are equipped with a Neuron Micropsocessor and FTT-10A Transciever. Instead of three connections, they have a single connection for a LonWorks network.
External Communication Ports, Speeds and Access Devices Single EIA-232 communications port with RJ-11 jack @ up to 38.4 kbps

Series 300 includes additional EIA-232 with RJ-45 jack for modem connection.
Additional Information (Optional) Up to 100 nodes consisting of MBC, RBC, MEC, and SCU primary control units may communicate on the P2 primary peer-to-peer network.

The 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 No access is available to the MBC/RBC from the zone level (connected secondary controllers). The only field interface with the MBC/RBC is through its own field interface port.
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 68302, 16.67 MHz (MEC 1xx, MEC 2xx and MEC 3xx only)

Motorola MPC 857T, 48 MHz (POWER MEC 1xxx and 1xxxE series)

Motorola MPC 860T, 48 MHz (POWER MEC 1xxxf, 1xxxEF and 1xxxL series)
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 32mb RAM (all POWER MEC 1xxx, 1xxxE, 1xxxF and 1xxxL series)
64mb RAM (all POWER MEC 1xxxEF series)
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 set points, parameters, user settings, schedules, etc.
Control Programming storage
Is Volatile Memory Supported By Battery? Yes
Battery Type(s) Replaceable AA Alkaline
Battery Life Information not provided
Backup Battery Operating Time 14 days
Non-Volatile Memory Capacity (EEPROM/Flash)* 8 MB (all POWER MEC 1xxx series)
Non-Volatile Memory Uses
Data / Trends / Alarms / Calculation Storage
Configuration / Parameter Storage
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? Yes
How many total trend values can be stored? Trend storage is limited to available RAM.
What is the controllers role in trending? Programming resident within SI gathers and stores trend data on-board. At set intervals, data is sent by the SI to workstation or called by the workstation for archival.
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? Old data is overwritten if controller trend data memory fills before being called by archive workstation.
Programming Method(s) Primary controllers are programmable from an operator workstation or portable operators terminal using proprietary line-based programming package (Powers Process Control Language; or PCL).
Resident vs Non-Resident Program Execution All programming is resident and executed at the controller.
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 Yes
Automatical-Dial Alarm Support Available from controller with optional modem (Model 300 only)
Does controller perform multiple retries and buffer/store alarm until connection is made? Yes
Are multiple destinations possible? Yes
Upon controller power loss or hardware failure:
Are network communications affected? Communications on the primary P2 network are uninterrupted. Polling network communications on the P1 are interrupted due to the supervisory nature of the MEC.
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? Clock function backed by battery. Clock setting is synchronized at regular intervals by workstation.
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? Yes
Internal hardware failure? Yes
Open/shortened sensor? Yes
Others? Diagnostics and error codes are provided for various hardware failures, communications failures, and software/programming errors. LEDs are also provided to indicate power faults, processor status, and battery low.
Control Enclosure NEMA 1 (2 sizes available)
Power Supply Required
Voltage 24 Vac
VA 35 VA for MEC; additional 17 VA for 4/4 I/O blocks, and 20 VA for 8/4 I/O block.
Surge Protection Provided
Underwriters Laboratories UL 864 UUKL





CSA 22.2 No. 0, 0.4 and 205
FCC Part 15, Sub-Part B, Class A
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