DDC Online direct digital controls
Siemens - APOGEE System  

Modular Building Controller (MBC); Remote Building Controller (RBC)

Primary Control Unit
Modular (MBC) and Remote (RBC) Building Controller
Date Last Saved: 12/13/2007 8:58:55 AM

Product Name(s): Modular Building Controller (MBC); Remote Building Controller (RBC)
Product Description: The MBC and RBC are modular, programmable primary controllers with supervisory interface capability to monitor a secondary controller network. The MBCs are available in 48 I/O (24 module ports) or 80 I/O (40 module ports) capacity enclosures. RBCs have a 24 I/O (12 module ports) capacity enclosure. The enclosure assembly includes: enclosure; backplane; mounting rails for the Open Processor, Power Module, and Point Termination Modules; a duplex receptacle; and a step-down isolation transformer.
Product Application(s): The MBC and RBC are designed to control general HVAC applications including air-handling units, chillers/boiler/central plant control and distribution systems, data acquisition, and other multi-equipment applications. The RBC is a smaller capacity version of the MBC with more communications and security options to allow for remote communications. Both the MBC and RBC provide on-board control of I/O points and central monitoring for distributed secondary control units and other building systems (e.g. fire/life safety, security, and lighting).
Point Quantity Characteristics
Analog Input (AI): Modular I/O(see below) 4-20 mA
0-10 Vdc
Thermistor (100 K )
RTD (1000 W platinum)
Digital Input (DI): Modular I/O(see below) Dry contact
Voltage input (250 Vac max)
Pulse counting up to 25 Hz
Universal Input (AI or DI):
Analog Output (AO): Modular I/O(see below) 0-10 Vdc
4-20 mA
0-20 psi
Digital Output (DO): Modular I/O(see below) Dry contact (240 Vac/4 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
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 Each MBC/RBC must be set up using 2-point I/O modules (Point Termination Modules). Each of the following occupy one of the 24 or 40 available modules ports (MBC) or 12 available module ports (RBC).
Expansion Device Model #AIDIUIDOAOUOOther
PTM6.2P1K; 100 Ohm platinum RTD 2
PTM6.2N100K; 100K Ohm Thermistor 2
PTM6.2U10; 0-10; Vdc, Industry Std. 2
PTM6.2I420; 4-20; ma, 2wire, 3wire 2
PTM6.4D20; Dry Contact, Potential Free 4
PTM6.2D20; Dry Contact, Potential Free 2
PTM6.2C; Pulse Accumulator, 25 Hz 2
PTM6.2D250; Voltage Sensing, 250 Vac max 2
PTM6.2Y10S; 0-10 Vdc, LED, Industry Std 2
PTM6.2Y10S-M; 0-10 Vdc, LED, Industry Std. Auto/Manual and Gradual Adj 2
PTM6.2Y420; 4-20 ma, LED, Industry Std. 2
PTM6.1PSI20-M; 0-20 PSI, LEDAuto/Manual and Gradual Adj 2
PTM6.2Q250; Contact, 240 Vac / 4A 2
PTM6.2Q250-M; Contact, 240 Vac / 4ASupervised HOA 2
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
(1) - Proprietary ('P2') to primary 'Automation Level Network (ALN)' @ 9.6 to 115.2 kbps (peer-to-peer)

(3) - Proprietary ('P1') to secondary 'Field Level Network (FLN)' @ 4.8 kbps (polling)(wired or wireless)

(1) Ethernet Port - New 'POWER' Open Processors come with 1 Ethernet port for direct BLN communication over Ethernet TCP/IP, at 10/100 BaseT.
External Communication Ports, Speeds and Access Devices (2) - EIA-232 laptop/PC communication ports with RJ-11 jack @ up to 38.4 kbps.
Note: A modem or Ethernet Microserver (which provides direct connection to the MLN) can be installed on one of these ports.
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.

New 'POWER' Open Processors, which include additional features and memory capacity, come standard to all new MBC kits sold. MBC POWER Open Processors are also available for sale as replacements for older MBC Open Processors.

POWER Open Processors come standard with 72mb RAM, a Compact Flash port, and Ethernet port for Peer-to-Peer communication over Ethernet TCP/IP.
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 (In older MBC Open Processors)
- or -
Motorola MPC 862T, 48 Mhz (In new 'POWER' version of Open Processor)
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 Available in 2 MB or 4 MB RAM configurations for older MBC Open Processors - or - 72 MB for new 'POWER' MBC Open Processors
Volatile Memory (RAM) Uses
RAM use unrestricted
RAM use restricted as shown below
Information Not Provided
Program Execution / Calculation storage
Data / Trends / Alarms storage Calculating 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 Lithium battery for older MBC Open Processors
- or -
Replaceable AA Alkaline battery with new 'POWER' MBC Open Processors
Battery Life Information not provided
Backup Battery Operating Time 60 days for Lithium battery and 20 days for AA Alkaline battery.
Non-Volatile Memory Capacity (EEPROM/Flash)* 2MB
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 PPCL).
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 Yes
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 MBC/RBC.
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 or NEMA 12 (optional)
Power Supply Required
Voltage 120 Vac
VA Not applicable
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