WO2008097992A1

WO2008097992A1 - Modular components for building automation systems

Info

Publication number: WO2008097992A1
Application number: PCT/US2008/053077
Authority: WO
Inventors: Michael J. Crowe; Daniel T. Burns
Original assignee: Johnson Controls Technology Company
Priority date: 2007-02-05
Filing date: 2008-02-05
Publication date: 2008-08-14

Abstract

A building automation control system for controlling a plurality of building automation system devices is provided. The building automation control system is for use with a common mounting element and a power bus for providing power to the control modules. The control system includes a control module having a circuit for controlling at least one building automation device of the plurality of building automation system devices. Each control module includes a flexible form factor electronics circuit. Each control module further includes a mounting component for attaching the control module to the common mounting element. Each control module yet further includes a first interface for connecting to the power bus.

Description

MODULAR COMPONENTS FOR BUILDING AUTOMATION

SYSTEMS

[0001] This application claims the benefit of U.S. Provisional Application No. 60/888,200, filed February 5, 2007, which is incorporated herein by reference in its entirety.

BACKGROUND

[0002] The application generally relates to building automation systems. The application relates more specifically to building automation systems and modular components using flexible form factor electronics.

[0003] Conventional components of building automation systems typically utilize many interconnecting wires and occupy a relatively large amount of space. For example, while a typical building controller may have what many would consider to be a small housing structure, such a controller is often connected to many expansion modules, input/output modules, and supplemental power supplies, and/or any number of other building automation system components. A conventional HVAC control panel may include over a dozen components, have a size of approximately twenty square feet, weigh two hundred and fifty pounds, and include many wires interconnecting the various components of the control panel.

SUMMARY

[0004] The invention relates to a building automation control system for controlling a plurality of building automation system devices. The building automation control system is for use with a common mounting element and a power bus for providing power to the control modules. The control system includes a control module for controlling at least one building automation device of the plurality of building automation system devices. Each control module includes an electronic circuit connected by conductors extending in three dimensions. Each control module further includes a mounting component for attaching the control module to the common mounting element. Each control module yet further includes a first interface for connecting to the power bus.

[0005] The invention further relates to a controller for a building automation system. The controller includes an electronic circuit connected by conductors extending in three dimensions. The controller further includes a mounting component for attaching the control module to the mounting element. The controller yet further includes a processor communicably coupled to memory, the memory including computer code for controlling at least one building automation system device. The controller still further includes a data interface for communicating with a first module, the first module configured for attaching to the mounting element.

[0006] Alternative exemplary embodiments relate to other features and combinations of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE FIGURES

[0007] The application will become more fully understood from the following detailed description, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements, in which:

[0008] FIG. 1 is a perspective view of a building having a plurality of sensor and/or controller devices, according to an exemplary embodiment;

[0009] FIG. 2 is a schematic diagram of a building automation system (BAS) for the building of FIG. 1, according to an exemplary embodiment;

[0010] FIG. 3 is a block diagram of a mesh network for the building of FIG. 1, according to an exemplary embodiment;

[0011] FIG. 4 is a perspective view of a modular control system panel, according to an exemplary embodiment;

[0012] FIG. 5 is a front view of modular control system devices, according to an exemplary embodiment;

[0013] FIG. 6A is a perspective view of modular control system devices disposed on a mounting bar, according to an exemplary embodiment;

[0014] FIG. 6B is a block diagram of a modular device, according to an exemplary embodiment; and

[0015] FIGS. 7A-7C are block diagrams of connections between modular devices of a modular control system, according to alternative exemplary embodiments.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

[0016] Before turning to the figures which illustrate the exemplary embodiments in detail, it should be understood that the application is not limited to the details or methodology set forth in the following description or illustrated in the figures. It should also be understood that the terminology employed is for the purpose of description only and should not be regarded as limiting.

[0017] "Flexible form factor electronics" generally describes electronics circuits formed within or disposed on other than a flat and rigid substrate (e.g., a flat and rigid printed circuit board). For example, flexible form factor electronics may refer to using flexible electronics technology such that electronics circuits better fit housing forms or form factors. Flexible electronics may also be referred to as "three dimensional" electronics technology as the property of being flexible may allow for the irregular bending or manipulation (in three dimensions) of an electronic circuit. Flexible electronics may be referred to in the electronic arts as "flex circuits" or "flex circuit boards."

[0018] Flexible form factor electronics devices may include conventional rigid printed circuit boards and only a few portions of flexible electronics; or flexible form factor electronics devices may include electronic circuits that are disposed on an entirely flexible substrate. The flexible nature of these devices may allow for varying housing sizes and designs, as a flexible circuit may more easily be bent to fit a housing. Other terms used to describe flexible form factor electronics may include "three dimensional electronic substrate" or "flexible electronic substrates."

[0019] Also, "flexible form factor" electronic circuits are not limited to circuits disposed on a flexible substrate. Flexible form factor electronic circuits need not actually be flexible or remain flexible as installed in the housing. For example, flexible form factor electronics may also include injection molded "three dimensional" frames or circuits (e.g., three dimensional multi-layered lead-frames) designed or configured to fit in housing shapes and/or spaces that conventional flat printed circuit boards could not accommodate. Three- dimensional flexible circuits protected by an injection-molded housing may further provide a robust, hermetically sealed package that is highly resistant to heat, moisture, vibration, and other harsh environments. Thus, flexible form factor electronic circuits may be advantageously employed to reduce the size and increase the durability of BAS devices. [0020] FIG. 1 is a perspective view of a building 12 having a plurality of sensing and/or controlling devices 13, also known as BAS devices 13, according to an exemplary embodiment. As illustrated, building 12 may include any number of floors, rooms, spaces, zones, and/or other building structures and areas. According to various exemplary embodiments, building 12 may be any area of any size or type, including an outdoor area. BAS devices 13 may exist inside or outside the building, on walls or on desks, be user interactive or not, and may be any type of building device. For example, a BAS device 13 may be a security device, a light switch, a fan actuator, a temperature sensor, a thermostat, a smoke detector, an occupancy sensor, other various types of sensors (flow, pressure, etc.), etc. BAS devices 13 may be configured to conduct building automation functions (e.g., sense temperature, sense humidity, control a building automation device, etc.). BAS devices 13 may also serve any number of network functions (e.g., RF measuring functions, network routing functions, etc.). A controller system 14 is shown as a desktop wireless device. Controller system 14 may serve as a network coordinator, wireless access point, router, switch, hub, and/or serve as another node on a network. A workstation 19 is shown as a personal workstation. Workstation 19 may allow building engineers to interact with controller system 14. BAS devices 13 may be connected to controller system 14 and/or workstations 19 via a wired and/or wireless connection.

[0021] Building automation systems (BAS) are, in general, hardware and/or software systems configured to control, monitor, and manage equipment in or around a building or building area. BAS equipment can include a heating, ventilation, and air conditioning (HVAC) system, a security system, a lighting system, a fire alerting system, an elevator system, any other system that is capable of managing building functions, or any combination thereof. The BAS as illustrated and discussed in the present disclosure is an example of a facility system that may be used in conjunction with modular control devices; however, other facility management systems may be used as well. According to other exemplary embodiments, modular control devices may be used in conjunction with any type of system (e.g., a general purpose office local area network (LAN), a home LAN, a wide area network (WAN), a wireless hotspot, etc.).

[0022] Referring to FIG. 2, a schematic diagram of a BAS 100 that may be used with the systems of the present disclosure is shown, according to an exemplary embodiment. BAS 100 may include one or more network automation engines (NAEs) 102 connected to a proprietary or standard communications network such as an IP network (e.g., Ethernet, WiFi, ZigBee, Bluetooth, etc.). NAEs 102 may support various field-level communications protocols and/or technology, including various Internet Protocols (IP), BACnet over IP, BACnet Master-Slave/Token-Passing (MS/TP), N2 Bus, N2 over Ethernet, Wireless N2, Lon Works, ZigBee, and any number of other standard or proprietary field- level building management protocols and/or technologies. NAEs 102 may include varying levels of supervisory features and building management features. The user interface of NAEs 102 may be accessed via terminals 104 (e.g., web browser terminals) capable of communicably connecting to and accessing NAEs 102. For example, FIG. 2 shows multiple terminals 104 that may variously connect to NAEs 102 or other devices of BAS 100. For example, terminals 104 may access BAS 100 and connected NAEs 102 via a WAN, local IP network, or via a connected wireless access point. Terminals 104 may also access BAS 100 and connected NAEs 102 to provide information to another source, such as printer 132. [0023] NAEs 102 may be connected to any number of BAS devices. The devices may include, among other devices, devices such as field-level control modules 106, variable air volume modular assemblies (VMAs) 108, integrator units 110, variable air volume (VAV) devices and units 112, extended digital controllers 114, unitary devices 116, air handling unit (AHU) controllers 118, boilers 120, fan coil units 122, heat pump units 124, unit ventilators 126, expansion modules, blowers, temperature sensors, flow transducers, other sensors, motion detectors, actuators, dampers, heaters, air conditioning units, etc. These devices may generally be controlled and/or monitored by NAEs 102. Data generated by or available on the various devices that are directly or indirectly connected to an NAE 102 may be passed, sent, requested, or read by NAE 102 and/or sent to various other systems or terminals 104 of BAS 100. The data may be stored by NAE 102, processed by NAE 102, transformed by NAE 102, and/or sent to various other systems or terminals 104 of the BAS 100. As shown in FIG. 2, the various devices of BAS 100 may be connected to NAE 102 with a wired connection or with a wireless connection.

[0024] Still referring to FIG. 2, an application and data server (ADS) 130 is shown, according to an exemplary embodiment. ADS 130 is a server system that includes a database management system (e.g., a relational database management system, Microsoft SQL Server, SQL Server Express, etc.) and server software (e.g., web server software, application server software, virtual machine runtime environments, etc.) that provide access to data and route commands to BAS 100. For example, ADS 130 may serve user interface applications. ADS 130 may also serve applications such as Java applications, messaging applications, trending applications, database applications, etc. ADS 130 may store trend data, audit trail messages, alarm messages, event messages, contact information, and/or any number of BAS-related data. Terminals may connect to ADS 130 to access the entire BAS 100 and historical data, trend data, alarm data, operator transactions, and any other data associated with BAS 100, its components, or applications. Various local devices such as printer 132 may be attached to components of BAS 100 such as ADS 130. [0025] FIG. 3 is a block diagram of a mesh network 11, according to an exemplary embodiment. A mesh network is an example of a network that might be formed by various wireless BAS devices 13 of the modular control system as described in the present application. According to other exemplary embodiments, the wireless devices may be arranged in another type of network topology.

[0026] In the illustrated embodiment, mesh network 11 includes a building area 12, a plurality of BAS devices 13a and 13b (and/or other devices and nodes), a controller system 14, a network 18, and a workstation 19 (e.g., a desktop computer, a personal digital assistant (PDA), a laptop, etc.). BAS devices 13a and 13b are interconnected by wireless connections 15 (displayed as solid lines on FIG. 3). Wireless connections may be disabled (or otherwise unavailable) for various reasons (displayed as dashed lines on FIG. 3) and are shown by connections 17. As a result, some BAS devices 13a (devices without a solid line connection as illustrated in FIG. 3) may temporarily be disconnected from mesh network 11 , but are configured to automatically connect (or reconnect) to any other suitable device 13a within range. Other BAS devices 13b may be disconnected from mesh network 11 without being able to connect to another device 13a. Controller system 14 may be connected to workstation 19 via network 18 and may include station 14b for receiving input from the various BAS devices 13a and 13b.

[0027] Using a plurality of low-power and multi-function or reduced function wireless devices distributed around a building and configured in a mesh network, a redundant, agile, and cost-effective communications system for building management systems may be provided.

[0028] According to an exemplary embodiment, BAS devices 13a and 13b of FIG. 3 are ZigBee compatible devices. ZigBee is the name of a specification related to low cost and low power digital radios. The ZigBee specification describes a collection of high level communication protocols based on the IEEE 802.15.4 standard. A ZigBee compatible device is a device generally conforming to ZigBee specifications and capable of existing or communicating with a ZigBee network. In other exemplary embodiments, BAS devices 13a and 13b could be any kind of radio frequency communicating wireless device including, but not limited to, Bluetooth devices and traditional 802.11 (Wi-Fi) based devices. According to an exemplary embodiment, BAS devices 13a and 13b may consist of any type of ZigBee device including ZigBee coordinators, ZigBee routers, ZigBee end devices, etc. ZigBee coordinators and routers are generally RF-enabled devices that can act as intermediate routers and may relay data to and from other RF-enabled devices on the network. The devices are sometimes referred to as full function devices as described above. Conversely, ZigBee end devices may not be able to relay data from other devices back onto the network. These devices are sometimes referred to as reduced function devices. [0029] Still referring to FIG. 3, mesh network 11 may include a number of BAS devices 13a and 13b that are either full function devices or reduced function devices. For example, BAS devices 13a that might be end devices or reduced function devices are shown with one connection (and may only have one possible connection) in mesh network 11. Additionally, BAS devices 13b might be coordinators, routers or full function devices that relay information to and from multiple BAS devices 13a and 13b on mesh network 11 (illustrated by a node with multiple connections). The BAS devices 13a and 13b may be configured to determine a shortest path or otherwise exemplary path in which to send data on mesh network 11.

[0030] FIG. 4 is a perspective view of a modular control system panel 400, according to an exemplary embodiment. Panel housing 402 may be provided to protect, organize, and support a variety of modular control devices 420. In a preferred embodiment, the panel housing is a rectangular parallelepiped, although any shape may be used. Panel housing 402 may be made of metal, plastic, or other materials. Panel housing 402 may optionally be provided with a panel door 404. Panel door 404 may be made of the same or different materials as panel housing 402. Panel door 404 may further optionally be provided with openings or windows to provide visual or physical access to the various modules 420. [0031] In one embodiment, panel housing 402 is provided with a removable panel front 406, allowing access to the interior of panel housing 402. In an alternative embodiment, panel front 406 is hingedly attached to panel housing 402. In yet another embodiment, panel front 406 may be omitted.

[0032] Panel front 406 may include one or more openings 418. Openings 418 may be of any size or configuration. Openings 418 may further be of fixed size, or openings 418 may be adjustable. In a preferred embodiment, panel front 406 is provided with one or more removable sections pre-formed in the surface of the panel front ("knockouts"). The knockouts may then be removed as required form openings corresponding to the installed locations of modular control devices 420.

[0033] Panel housing 402 may also be provided with one or more openings 418 on one or more surfaces of panel housing 402. Openings 418 may be of any size or configuration. Openings 418 may further be of fixed size, or openings 418 may be adjustable. In one embodiment, panel housing 402 is provided with one or more removable knockout sections. Conduit 408 may optionally be attached to the panel housing to communicatively allow passage of wiring 660. Wiring 660 may be routed through openings 418, and optionally conduit 408, to provide power to the modular control system, data connectivity to external devices or networks, attachment to any BAS device, or for any other purpose. [0034] A modular control panel may optionally be provided with manual switches, circuit breakers, BAS devices, power supplies, or other devices in combination with the disclosed modular control devices.

[0035] FIG. 5 is a front view of modular control system devices, according to an exemplary embodiment. Types of modular control devices 420 include, but are not limited to, controller modules 422; input/output (I/O) modules 424; and network modules 430. I/O modules 424 may include digital I/O modules 426 and analog I/O modules 428. [0036] In a preferred embodiment, each module is of a common height, for example 3.5 inches. Additionally, each module width is an integer multiple of a standard unit width, such as 0.75 inch. For example, if the standard unit width is 0.75 inch, module widths could be 0.75 inch, 1.5 inches, 2.25 inches, 3.0 inches, etc. Preferably, each module in a modular control system is provided with a standardized mounting component, power interface, and data interface. However, modular control devices may be of any size or shape, and may include any type of connector and/or interface.

[0037] Generally, modules 420 may include connectors that conform to National Electrical Manufacturer's Association (NEMA) standards, German Institute for Standardization (DIN) standards, any other presently developed standards, and any future developed standards. Modules and devices may also include proprietary features, interfaces, protocols, connectors, and/or specifications suited to operate with specific building automation systems. Modules may be designed as drop-in replacements for any type of commercial circuit breaker, BAS device, sensor, switch, relay, and so forth. In an exemplary embodiment, individual modules may be removed, replaced, modified, and/or updated without affecting the functionality of other components in the modular control system.

[0038] FIG. 6A is a perspective view of modular control devices disposed on a mounting element, according to an exemplary embodiment. The mounting element may be a mounting bar 610. Mounting bar 610 may be held to (or slightly away from) mounting surface 600 by any number of fasteners, adhesives, compounds, or other suitable structures. Mounting bar 610 is shown to include a power bus 612 and a data bus 616. In an alternative embodiment, the mounting element, power bus, and/or data bus may be separate components. In another alternative embodiment, power bus 612 and data bus 616 may be combined by modulating a data signal onto power bus 612. One or more mounting components of modular control device 420 may be configured for joining (e.g., snapping, clamping, fastening, compressing, latching, etc.) to a mounting element, such as mounting bar 610. In one embodiment, mounting bar 610 is a standard mounting rail such as a DIN rail.

[0039] Referring now to FIG. 6B, power bus 612 may be or include any conducting element or elements configured to provide power from a source to a modular control device 420 (and/or power to other modules that may be coupled to mounting bar 610). Power bus 612 may provide alternating and/or direct current to each module. In an exemplary embodiment, power bus 612 provides both a standard line voltage, such as 120V AC, and a low voltage, such as 5 V DC. According to another exemplary embodiment, power bus 612 may further include a positive terminal and/or a ground or negative terminal. According to yet other exemplary embodiments, power bus 612 provides a positive power source while another structure provides a negative power terminal.

[0040] Modular control device 420 is shown to include a power interface 614 for receiving power from power bus 612. Power interface 614 may include one or more elements (e.g., pins, screws, plugs, terminals, conductors, clamps, etc.) for touching power bus 612 and for receiving power from bus 612. Modular control device 420 is also shown to include data interface 618. Data interface 618 may include one or more elements (e.g., pins, screws, plugs, terminals, conductors, clamps, etc.) for interfacing with data bus 616 and for exchanging data signals. Data interface 618 may connect with data bus 616 upon attachment of the module to the mounting bar. Interfaces 614 and 618 may be formed from a variety of materials (e.g., copper) and comprise a variety of different shapes according to various exemplary embodiments. In another embodiment, data bus 616 and data interface 618 include an optical connection and interface.

[0041] Referring further to FIG. 6B, data bus 616 may be or include any conducting element or elements configured to provide data signals to and/or from a source to modular control device 420. In an exemplary embodiment, data bus 616 is a serial data bus. According to another exemplary embodiment, data bus 616 may be USB compatible or Ethernet compatible. According to yet other exemplary embodiments, any suitable communications technology or protocol may be used by data bus 616 to exchange data communications with modular control device 420. According to some exemplary embodiments, data bus 616 is not a part of or included on mounting bar 610. [0042] Mounting bar 610 may be configured to provide power bus 612 while other structures or systems may be provided for communicating with modular control device 420. For example, modular control device 420 may include one or more side connectors 620 or connectors located elsewhere on the housing of modular control device 420. Modular control device 420 may also include more than one data interface. For example, data interface 618 may be configured for communicating network information for a LAN, WAN, or for the Internet.

[0043] Connector terminal 630 and connector interface 632 shown at the top of modular control device 420, for example, may be configured for connecting to standard or proprietary field controllers, actuators, sensors, or other wired devices or systems. Connector terminal 630 may be any type of pin, screw, plug, terminal, conductor, clamp, etc. Connector interface 632, may, for example, allow modular control device 420 to support some legacy or old systems that may not be compatible with data bus 616 or another technology or protocol in use by the BAS controller. Additionally, power may be provided to external devices through connectors 630. Inputs and outputs from/to any external device may be switched, regulated, limited, measured, and/or quantified. Information thereby collected may be stored in a memory 624 and/or reported to other modular devices.

[0044] Referring yet further to FIG. 6B, modular control device 420 is shown to include a processor 622 and memory 624, according to an exemplary embodiment. Processor 622 may be a processing circuit comprising one or more processing elements, may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a general purpose processor, a processor configured for real-time computing, a processor configured for embedded applications, or otherwise. According to an exemplary embodiment, processor 622 is configured to access computer code stored in memory 624 and to process the computer code. Memory 624 may include one or more memory devices or units. For example, memory 624 may include volatile memory and non-volatile memory. Memory 624 may include at least one non- volatile memory component for storing computer code for execution by a communicably connected processor (e.g., processor 622). Memory 624 may further include databases or data store of BAS device information. [0045] Modular control device 420 may further include a display 650 and a display driver 648. Display 650 may be configured to provide a local display element for installers and users of module 420. Display 650 may provide user-selectable menu options, inputs, and access to desired information. Display 650 may be a dot matrix display, and LCD display, an OLED display, and/or a display of any other suitable technology. Display driver 648 includes the circuitry for driving display 650 based on commands received from processor 622. The display may further be a touch-sensitive display adapted to receive user input. In another embodiment, module 420 may be provided with one or more user controls 640, such a button, switch, track pad, or other input device. One or more indicators 652 may also be provided in modular control device 420 for providing warning indications, alert indications, "power on" indications, or any other indication to an installer or user. [0046] Modular control device 420 may still further include a network driver circuit 654. In an exemplary embodiment, network driver circuit 654 may communicably connect processor 622 and memory 624 to any type of wired or wireless network, such as 10/100/1000BASE-T, 801.1 la/b/g, 802.15.4 ZigBee, Bluetooth, LonTalk, BACnet, and ModBus. Network driver circuit 654 may enable the module 420 to be a node or controller of a mesh network as shown in FIG. 3.

[0047] The components of modular control device 420 may be interconnected via a circuit element 662. Circuit element 662 is generally configured to interconnect electronics components of modular control device 420 (e.g., processor 622, memory 624, display driver 648, etc.). Circuit element 662 may be a rigid circuit board having printed, traced, or embedded conductors. According to an exemplary embodiment, circuit element 662 is a flexible form factor electronic circuit of the type described in the present application. According to yet other exemplary embodiments, circuit element 662 includes rigid portions and flexible portions.

[0048] Modules 420 as described herein may be general purpose modules 420, controller modules 422, or may be special-purpose modules designed to perform a specific task. In one embodiment, a digital I/O module 426 may be provided with one or more connectors 630. Connectors 630 may be adapted to receive and/or transmit digital signals from one or more BAS devices. The digital signals may be wired, optical, or wireless. Digital I/O modules 426 may receive and/or transmit signals using one or more connection types, including wired connections, wireless connections, optical connections, and/or infrared connections. Digital I/O modules 426 may be adapted to receive and/or transmit digital signals using one or more protocols, including 3 -5 V DC logic control signals, pulse width modulation (PWM), serial data, or any other digital signal or protocol. [0049] In another embodiment, analog I/O modules 428 may be provided with one or more connectors 630. Connectors 630 may be adapted to receive and/or transmit analog signals from one or more BAS devices. Analog I/O modules 428 may receive any analog input type including thermocouple inputs, 0-1 OV analog signals, alarm loops, 0-500V RMS meter, and volt-free contacts. Analog I/O modules 428 may be configured to provide any type of analog output, including 0-15V DC, 0-10OmA current source, 2OmA current loop, line voltage such as 120V AC, 5 A relay control, or any other analog signal. [0050] In yet another embodiment, network modules 430 may be provided with one or more connectors 630. Network modules 430 may receive and/or transmit signals using one or more connection types, including wired connections, wireless connections, optical connections, and/or infrared connections. Network modules 430 may receive and/or transmit signals using one or more protocols, including 10/100/1000BASE-T, 801.1 la/b/g, 802.15.4 ZigBee, Bluetooth, LonTalk, BACnet, and ModBus. Network modules 430 may be nodes or controllers of a mesh network as shown in FIG. 3. Network modules 430 may also include connection types and data protocols developed in the future. [0051] A modular control system may be configured to communicate with external networks. In an exemplary embodiment, a network module 430 may be configured as an interface between an external wired or wireless network, such as a LAN or WAN, and modules 420 coupled to data bus 616. According to this embodiment, a remote user may access and control the functions of any module 420 from a networked terminal 104. A remote user may also diagnose, service, modify, and/or upgrade the modular control system from a networked terminal. In an exemplary embodiment, a user may use a web-based interface to access and control any modular control system or BAS device. [0052] FIGS. 7A-7C are block diagrams of data and power connections between modular devices of a modular building automation system, according to alternative exemplary embodiments.

[0053] Referring to FIG. 7A, modules may be connected in parallel to a common data bus 616. Modules may also be connected in parallel to a common power bus 612. Each module may communicate with other modules across data bus 616. For example, controller module 422 may transmit data to and receive data from any of digital I/O module 426, analog I/O module 428, and/or network module 430. Data communicated on the data bus 616 may include inputs from BAS devices attached to modules 420, including I/O modules 426 and/or 428. Data communicated on data bus 616 may further include signals to and from external networks attached to a network module 430. Additionally, a module 420 may receive wireless signals 619 from BAS devices using one or more protocols, including 801.1 la/b/g, 802.15.4 ZigBee, and/or Bluetooth.

[0054] Referring to FIG. 7B, modules may alternatively be connected in series. In one embodiment, modules are connected to adjacent modules by side connectors 620. In this embodiment, data may also be passed through modules, allowing non-adjacent modules to communicate.

[0055] Referring to FIG. 1C, wireless data 619 may additionally be transmitted between modules wirelessly. Modules may use any wireless protocol, such as 801.11 a/b/g, 802.15.4 ZigBee, and/or Bluetooth. Data may also be transmitted between any module 420 and any BAS device.

[0056] In an exemplary embodiment, a modular control system may be configured perform a variety of building management tasks. A modular control system may be configured to control lighting systems, fire systems, security systems, HVAC systems, communications systems, or any other type of building automation system. Specifically, a modular control system may be coupled to any building component, including ballasts, light switches, dimmers, card readers, door strikes, fire detectors, motion detectors, temperature sensors, humidity sensors, pressure sensors, air handling equipment and control panels, and so forth.

[0057] In one embodiment, modules may measure, store, and communicate energy consumption statistics, thereby providing data for energy conservation. In yet another embodiment, data may be used to monitor and assess the health of equipment and systems. In still other embodiments, a modular control system may be utilized for automated building power conservation, demand-side management, load management, improved safety control, remote operations, and/or building control services.

[0058] While the exemplary embodiments illustrated in the figures and described herein are presently preferred, it should be understood that the embodiments are offered by way of example only. Accordingly, the present application is not limited to a particular embodiment, but extends to various modifications that nevertheless fall within the scope of the appended claims.

[0059] It is important to note that the construction and arrangement of the systems and devices as shown in the various exemplary embodiments is illustrative only. Although only a few embodiments have been described in detail in this disclosure, those skilled in the art who review this disclosure will readily appreciate that many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.) without materially departing from the novel teachings and advantages. For example, elements shown as integrally formed may be constructed of multiple parts or elements, the position of elements may be reversed or otherwise varied, and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure. [0060] Embodiments within the scope of the present disclosure include program products comprising machine -readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a machine, the machine properly views the connection as a machine -readable medium. Thus, any such connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Claims

WHAT IS CLAIMED IS:

1. A building automation control system for controlling a plurality of building automation system devices, the building automation control system for use with a common mounting element and a power bus for providing power to the control modules, the control system comprising: a control module for controlling at least one building automation system device of the plurality of building automation system devices; wherein each control module includes: a circuit, the circuit comprising electronic components connected by circuit conductors extending in three dimensions; a mounting component for attaching the control module to the common mounting element; and a first interface for connecting to the power bus.

2. The building automation control system of Claim 1, wherein each control module further comprises a second interface for communicably connecting to a common data bus.

3. The building automation control system of Claim 1, wherein each control module further comprises a transceiver for communicating with the at least one building automation system device.

4. The building automation control system of Claim 3, wherein the transceiver is further configured to communicate with the transceiver of another control module.

5. The building automation control system of Claim 1, wherein the circuit conductors and electronic components are disposed on a flexible circuit board.

6. The building automation control system of Claim 1, wherein the circuit conductors and electronic components are encapsulated in a plastic material.

7. The building automation control system of Claim 1, wherein the circuit is configured to calculate load information using information available at the first interface.

8. The building automation control system of Claim 7, wherein the circuit is configured to control the at least one building automation system device based on the calculated load information.

9. A controller for a building automation system, the controller comprising: a mounting component for attaching a control module to a mounting element; a circuit, the circuit comprising electronic components connected by circuit conductors extending in three dimensions; a processor communicably coupled to a memory, the memory including computer code for controlling at least one building automation system device; and a data interface for communicating with a first module, the first module configured for attaching to the mounting element.

10. The controller of Claim 9, wherein the first module is a network module.

11. The controller of Claim 9, wherein the memory further includes computer code for sending control signals to a second module via the data interface.

12. The controller of Claim 11 , wherein the second module is an output module for sending the control signals to the at least one building automation system device.

13. The controller of Claim 11 , wherein the memory further includes computer code for receiving communications from the second module via the data interface, wherein the communications are received at the second module from the at least one building automation system device.

14. The controller of Claim 13, wherein the second module is an input and output module for communicating with the at least one building automation system device.

15. The controller of Claim 11 , wherein the memory further includes computer code for receiving a signal from a second module via the data interface, wherein the signal is received at the second module from the at least one building automation system device.

16. The controller of Claim 15, wherein the at least one building automation system device is a sensor.

17. The controller of Claim 16, wherein the memory further includes computer code for adjusting another building automation system device based on the received signal.

18. The controller of Claim 9, wherein the memory includes computer code for responding to a request for monitoring information, the request originating at a remote device or a local device, wherein the memory further includes computer code for providing a response to the remote device or the local device.

19. The controller of Claim 18, wherein the request originates at a graphical user interface at the remote device or the local device.