Modular edge controller in a building management system
The modular edge controller addresses the inflexibility of BMS I/O interfaces by allowing detachable modules with Ethernet and serial communication, reducing costs and enabling adaptable, efficient deployment of building automation systems.
Patent Information
- Application Number
- PCT/CN2026/089899
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-07
- Filing Date
- 2026-04-10
- Publication Date
- 2026-11-12
AI Technical Summary
Existing building management systems (BMS) face challenges due to fixed point counts and types of input/output (I/O) interfaces in field controllers and communication modules, leading to increased costs and redundant circuitry, which are not adaptable to varying system configurations.
A modular edge controller with detachable edge control modules and I/O modules that communicate via Ethernet ports and terminal blocks, supporting multiple protocols and enabling scalable, configurable I/O expansion, and a communication module for high-performance data aggregation and network connectivity.
The modular design reduces redundant circuitry, lowers hardware costs, and supports rapid field reconfiguration, enabling efficient deployment across diverse building automation scenarios with minimal commissioning effort and future-proof integration of legacy and modern systems.
Smart Images

Figure 00000069_0000 
Figure 00000070_0000 
Figure 00000071_0000
Abstract
Description
MODULAR EDGE CONTROLLER IN A BUILDING MANAGEMENT SYSTEMCROSS-REFERENCE TO RELATED PATENT APPLICATIONS
[0001] This application claims the benefit of and priority to P. C. T. Patent Application No. PCT / CN2025 / 093178 filed May 7, 2025, and P. C. T. Patent Application No. PCT / CN2025 / 093181 filed May 7, 2025, both of which are incorporated by reference herein in their entireties.BACKGROUND
[0002] The present disclosure relates generally to the field of communications systems and / or controllers, including but not limited to communication systems and controllers used in building management systems (BMSs) or heating, ventilating, or air conditioning (HVAC) systems.
[0003] A BMS is, in general, a system of devices configured to control, monitor, and / or manage equipment in or around a building, buildings, or building area. A BMS can be or include, for example, an HVAC system, a security system, a lighting system, a fire alerting system, any other system that is capable of managing building functions or devices, and / or any combination thereof.
[0004] Some equipment that operates as part of a BMS may require different types of input / output (I / O) interfaces. For example, field controllers, communication modules, and input output modules (IOMs) in a BMS often have fixed point counts and types (i.e., eight binary inputs) that may not be needed depending on system configuration or applications. The provision of the fixed points on the controller, communication models or IOM adds to the cost of the controller, communication modules, or IOM. In addition, adding I / O interfaces for a particular application may require purchasing a different field controller, communication module, or IOM to obtain to the right fixed point count, type and / or mix of count and type for the application. The additional controllers, communication modules or IOMs add redundant circuitry including a power supply and communication interfaces for the system.SUMMARY
[0005] One implementation of the present disclosure is a modular edge controller in a building system, the modular edge controller including: an edge control module including a first housing and a first circuit contained within the first housing, the first housing including a plurality of Ethernet ports connected to the first circuit; and one or more input / output (I / O) modules each including a second housing and a second circuit contained within the second housing, the second housing including one or more terminal blocks connected to the second circuit; wherein the first housing and the second housing are configured to detachably connect to each other and the first circuit and the second circuit are configured to communicate with each other when the first housing and the second housing are connected.
[0006] In some embodiments, the edge control module is configured to communicate using TCP / IP communications via the plurality of Ethernet ports; and the one or more I / O modules are configured to communicate using serial communications via the one or more terminal blocks.
[0007] In some embodiments, the edge control module is configured to communicate using at least one of BACnet IP, Modbus TCT, or a message queuing telemetry transport (MQTT) protocol via the plurality of Ethernet ports; and the one or more I / O modules are configured to communicate via at least one of BACnet MS / TP or Modbus RTU via the one or more terminal blocks.
[0008] In some embodiments, the edge control module includes one or more memory devices having at least 8 GB of storage capacity within the first housing.
[0009] In some embodiments, the edge control module is configured to communicate with a cloud system using a message queuing telemetry transport (MQTT) protocol via one or more of the plurality of Ethernet ports.
[0010] In some embodiments, the edge control module is configured to form part of a TCP / IP communications network having at least one of a star topology, a daisy chain topology, or a ring topology.
[0011] In some embodiments, the first housing includes a serial communications interface connected to the first circuit and configured to communicate using serial communications.
[0012] In some embodiments, the first circuit is configured to: receive one or more input signals from building equipment of the building via one or more of the Ethernet ports or the one or more terminal blocks; generate a control signal by processing the one or more input signals using control logic stored on the first circuit; and transmit the control signal to the building equipment or other building equipment via one or more of the Ethernet ports or the one or more terminal blocks.
[0013] In some embodiments, the first circuit is configured to use a rapid spanning tree (RSTP) protocol to prevent switching loops while allowing redundant physical communication paths between the edge control module and one or more external systems or devices via the plurality of Ethernet ports.
[0014] In some embodiments, the first circuit is configured to recover from a communication failure via one of the plurality of Ethernet ports in less than one second by rerouting communications to another of the plurality of Ethernet ports.
[0015] Another implementation of the present disclosure is a communication system in a building system, the communication system including: a communication module including a first housing and a first circuit contained within the first housing, the first housing including a plurality of Ethernet ports connected to the first circuit; and one or more input / output (I / O) modules each including a second housing and a second circuit contained within the second housing, the second housing including one or more terminal blocks connected to the second circuit; wherein the first housing and the second housing are configured to detachably connect to each other and the first circuit and the second circuit are configured to communicate with each other when the first housing and the second housing are connected.
[0016] In some embodiments, the communication module is configured to communicate using TCP / IP communications via the plurality of Ethernet ports; and the one or more I / O modules are configured to communicate using serial communications via the one or more terminal blocks.
[0017] In some embodiments, the communication module is configured to communicate using at least one of BACnet IP, Modbus TCT, or a message queuing telemetry transport (MQTT) protocol via the plurality of Ethernet ports; and the one or more I / O modules are configured to communicate via at least one of BACnet MS / TP or Modbus RTU via the one or more terminal blocks.
[0018] In some embodiments, the communication module is configured to communicate with a cloud system using a message queuing telemetry transport (MQTT) protocol via one or more of the plurality of Ethernet ports.
[0019] In some embodiments, the communication module is configured to form part of a TCP / IP communications network having at least one of a star topology, a daisy chain topology, or a ring topology.
[0020] In some embodiments, the first housing includes a serial communications interface connected to the first circuit and configured to communicate using serial communications.
[0021] In some embodiments, the first circuit is configured to use a rapid spanning tree (RSTP) protocol to prevent switching loops while allowing redundant physical communication paths between the communication module and one or more external systems or devices via the plurality of Ethernet ports.
[0022] In some embodiments, the first circuit is configured to recover from a communication failure via one of the plurality of Ethernet ports in less than one second by rerouting communications to another of the plurality of Ethernet ports.
[0023] Another implementation of the present disclosure is a method for communicating using a modular edge controller in a building system, the method including; detachably connecting a first housing of an edge control module to a second housing of an input / output (I / O) module to form the modular edge controller; transmitting or receiving a first communication between the edge control module and one or more other systems or devices using TCP / IP communications via one or more of a plurality of Ethernet ports in the first housing of the edge control module; transmitting or receiving a second communication between the I / O module and one or more external systems or devices using serial communications via the one or more terminal blocks in the second housing of the I / O module; and transmitting or receiving a third communication between the edge control module and the I / O module when the first housing and the second housing are detachably connected.
[0024] In some embodiments, the first communication is transmitted or received using at least one of BACnet IP, Modbus TCT, or a message queuing telemetry transport (MQTT) protocol via one or more of the plurality of Ethernet ports; and the second communication is transmitted or received using at least one of BACnet MS / TP or Modbus RTU via the one or more terminal blocks.BRIEF DESCRIPTION OF THE DRAWINGS
[0025] The disclosure 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.
[0026] FIG. 1 is a drawing of a building equipped with a building management system (BMS) , according to some embodiments.
[0027] FIG. 2 is a block diagram of a BMS that serves the building of FIG. 1, according to some embodiments.
[0028] FIG. 3 is a block diagram of a BMS controller which can be used in the BMS of FIG. 2, according to some embodiments.
[0029] FIG. 4 is another block diagram of the BMS that serves the building of FIG. 1, according to some embodiments.
[0030] FIG. 5 is a schematic perspective view drawing of an example communication system associated with the BMS of FIG. 4, according to some embodiments.
[0031] FIG. 6 is another schematic perspective view drawing of the example communication system of FIG. 5, according to some embodiments.
[0032] FIG. 7 is a schematic perspective view drawing of an example analog module for the communication system of FIG. 5, according to some embodiments.
[0033] FIG. 8 is a perspective view of a modular edge controller including an edge control module and several IO modules, according to some embodiments.
[0034] FIG. 9 is a front view of the modular edge controller of FIG. 8, according to some embodiments.
[0035] FIG. 10 is a perspective view of the edge control module of the modular edge controller of FIG. 8, according to some embodiments.
[0036] FIG. 11 is a front view of the edge control module FIG. 10, according to some embodiments.
[0037] FIG. 12 is a perspective view of a communication system including a communication module and several IO modules, according to some embodiments.
[0038] FIG. 13 is a front view of the communication system of FIG. 12, according to some embodiments.
[0039] FIG. 14 is a perspective view of the communication module of the communication system of FIG. 12, according to some embodiments.
[0040] FIG. 15 is a front view of the communication module of FIG. 14, according to some embodiments.
[0041] FIG. 16 is topology diagram of a communications network having a star topology in which the modular edge controller of FIGS. 8-11 and / or the communication system of FIGS. 12-15 can be implemented, according to some embodiments.
[0042] FIG. 17 is topology diagram of a communications network having a daisy chain topology in which the modular edge controller of FIGS. 8-11 and / or the communication system of FIGS. 12-15 can be implemented, according to some embodiments.
[0043] FIG. 18 is topology diagram of a communications network having a ring topology in which the modular edge controller of FIGS. 8-11 and / or the communication system of FIGS. 12-15 can be implemented, according to some embodiments.
[0044] FIG. 19 is topology diagram of a communications network having a mixed topology in which the modular edge controller of FIGS. 8-11 and / or the communication system of FIGS. 12-15 can be implemented, according to some embodiments.DETAILED DESCRIPTIONOverview
[0045] Referring generally to the FIGURES, a modular edge controller and communication system are shown, according to various exemplary embodiments. The modular edge controller introduces a highly configurable, stackable control architecture in which an edge control module selectively couples to zero or more hot‐pluggable I / O modules via a unified mechanical and electrical interface. The edge control module and attached I / O modules may have separate housings that connect to each other and an end cap to form a single integrated controller housing with a common footprint. This architecture enables controllers to be assembled with only the processing, communication, and I / O resources required for a given application, thereby reducing redundant circuitry, panel space, and hardware cost while enabling rapid field reconfiguration and replacement of individual modules without disturbing existing wiring.
[0046] Advantageously, the edge control module can function as both a programmable controller and a network edge device. The edge control module may include onboard processing, memory, and control logic capable of executing advanced control algorithms while simultaneously supporting multiple wired communication interfaces, including RS‐485 serial communications and multiple Ethernet ports. The Ethernet ports may support TCP / IP‐based building automation protocols and are arranged to permit star, daisy‐chain, and ring network topologies with rapid spanning tree protocol (RSTP) redundancy, enabling sub‐second network recovery and eliminating the long reconvergence times associated with conventional ring networks.
[0047] The modular edge controller may support dynamic, scalable I / O expansion through smart, self‐identifying I / O modules. Each I / O module may be self‐encapsulated, serialized, and addressable, allowing automatic discovery and configuration of installed point types and counts at power‐up. The modular edge controller may support a wide range of universal, binary, analog, configurable, and relay I / O point types, enabling heterogeneous signal support within a single modular assembly. This approach allows factory or field‐level customization of point mix without changing controller models and supports hot‐swapping of failed modules with minimal commissioning effort.
[0048] Complementing the modular edge controller, the communication module provides an IP‐enabled communication bridge that shares the same modular form factor and I / O expansion capability as the modular edge controller, but may omit control functionality, in some embodiment, in favor of high‐performance data aggregation, protocol translation, and network connectivity. The communication module can connect to the same family of stackable I / O modules and end caps, forming a unified housing while serving as an Ethernet‐connected gateway between serial field devices and IP networks. This allows deployment of distributed I / O and data collection nodes without requiring a full controller at each location.
[0049] Like the modular edge controller, the communication module may include multiple Ethernet ports for redundant network connectivity and may implement the same RSTP‐enabled topologies as the edge control module, allowing interchangeable placement within daisy‐chain or ring networks. The communication module may support RS‐485 serial communications, BACnet / IP discovery, offline configuration via data exchange files, and MQTT‐based messaging for cloud or supervisory system integration. The communication module may include substantial onboard memory for local data logging, enabling continued operation and buffering during network outages.
[0050] Collectively, the modular edge controller and communication module provide a unified, modular control and communication platform that departs from monolithic building controllers by separating control, communication, and I / O functions into interoperable modules with a shared mechanical, electrical, and network architecture. This design enables scalable deployment across diverse building automation scenarios, supports rapid field servicing and upgrades, reduces commissioning and maintenance costs, and provides a future‐proof platform capable of integrating legacy serial devices, modern IP networks, and cloud‐based analytics within a single cohesive system. These and other features of the modular edge controller and communication module are described in greater detail below.
[0051] The term controller as used herein is intended to include IOMs. An analog IOM refers to an IOM that is configured to provide or receive an analog signal. Building and Building Management System
[0052] Referring now to FIG. 1, a perspective view of a building 10 is shown, according to an exemplary embodiment. A BMS serves building 10. The BMS for building 10 may include any number or type of devices that serve building 10. For example, each floor may include one or more security devices, video surveillance cameras, fire detectors, smoke detectors, lighting systems, HVAC systems, or other building systems or devices. In modern BMSs, BMS devices can exist on different networks within the building (e.g., one or more wireless networks, one or more wired networks, etc. ) and yet serve the same building space or control loop. For example, BMS devices may be connected to different communications networks or field controllers even if the devices serve the same area (e.g., floor, conference room, building zone, tenant area, etc. ) or purpose (e.g., security, ventilation, cooling, heating, etc. ) .
[0053] BMS devices may collectively or individually be referred to as building equipment. Building equipment may include any number or type of BMS devices within or around building 10. For example, building equipment may include controllers, chillers, rooftop units, fire and security systems, elevator systems, thermostats, lighting, serviceable equipment (e.g., vending machines) , and / or any other type of equipment that can be used to control, automate, or otherwise contribute to an environment, state, or condition of building 10. The terms “BMS devices, ” “BMS device” and “building equipment” are used interchangeably throughout this disclosure.
[0054] Referring now to FIG. 2, a block diagram of a BMS 11 for building 10 is shown, according to an exemplary embodiment. BMS 11 is shown to include a plurality of BMS subsystems 20-26. Each BMS subsystem 20-26 is connected to a plurality of BMS devices and makes data points for varying connected devices available to upstream BMS controller 12. Additionally, BMS subsystems 20-26 may encompass other lower-level subsystems. For example, an HVAC system may be broken down further as “HVAC system A, ” “HVAC system B, ” etc. In some buildings, multiple HVAC systems or subsystems may exist in parallel and may not be a part of the same HVAC system 20.
[0055] As shown in FIG. 2, BMS 11 may include a HVAC system 20. HVAC system 20 may control HVAC operations building 10. HVAC system 20 is shown to include a lower-level HVAC system 42 (named “HVAC system A” ) . HVAC system 42 may control HVAC operations for a specific floor or zone of building 10. HVAC system 42 may be connected to air handling units (AHUs) 32, 34 (named “AHU A” and “AHU B, ” respectively, in BMS 11) . AHU 32 may serve variable air volume (VAV) boxes 38, 40 (named “VAV_3” and “VAV_4” in BMS 11) . Likewise, AHU 34 may serve VAV boxes 36 and 110 (named “VAV_2” and “VAV_1” ) . HVAC system 42 may also include chiller 30 (named “Chiller A” in BMS 11) . Chiller 30 may provide chilled fluid to AHU 32 and / or to AHU 34. HVAC system 42 may receive data (i.e., BMS inputs such as temperature sensor readings, damper positions, temperature setpoints, etc. ) from AHUs 32, 34. HVAC system 42 may provide such BMS inputs to HVAC system 20 and on to middleware 14 and BMS controller 12. Similarly, other BMS subsystems may receive inputs from other building devices or objects and provide the received inputs to BMS controller 12 (e.g., via middleware 14) .
[0056] Middleware 14 may include services that allow interoperable communication to, from, or between disparate BMS subsystems 20-26 of BMS 11 (e.g., HVAC systems from different manufacturers, HVAC systems that communicate according to different protocols, security / fire systems, IT resources, door access systems, etc. ) . Middleware 14 may be, for example, an EnNet server sold by Johnson Controls, Inc. While middleware 14 is shown as separate from BMS controller 12, middleware 14 and BMS controller 12 may integrated in some embodiments. For example, middleware 14 may be a part of BMS controller 12.
[0057] Still referring to FIG. 2, window control system 22 may receive shade control information from one or more shade controls, ambient light level information from one or more light sensors, and / or other BMS inputs (e.g., sensor information, setpoint information, current state information, etc. ) from downstream devices. Window control system 22 may include window controllers 107, 108 (e.g., named “local window controller A” and “local window controller B, ” respectively, in BMS 11) . Window controllers 107, 108 control the operation of subsets of window control system 22. For example, window controller 108 may control window blind or shade operations for a given room, floor, or building in the BMS.
[0058] Lighting system 24 may receive lighting related information from a plurality of downstream light controls (e.g., from room lighting 104) . Door access system 26 may receive lock control, motion, state, or other door related information from a plurality of downstream door controls. Door access system 26 is shown to include door access pad 106 (named “Door Access Pad 3F” ) , which may grant or deny access to a building space (e.g., a floor, a conference room, an office, etc. ) based on whether valid user credentials are scanned or entered (e.g., via a keypad, via a badge-scanning pad, etc. ) .
[0059] BMS subsystems 20-26 may be connected to BMS controller 12 via middleware 14 and may be configured to provide BMS controller 12 with BMS inputs from various BMS subsystems 20-26 and their varying downstream devices. BMS controller 12 may be configured to make differences in building subsystems transparent at the human-machine interface or client interface level (e.g., for connected or hosted user interface (UI) clients 16, remote applications 18, etc. ) . BMS controller 12 may be configured to describe or model different building devices and building subsystems using common or unified objects (e.g., software objects stored in memory) to help provide the transparency. Software equipment objects may allow developers to write applications capable of monitoring and / or controlling various types of building equipment regardless of equipment-specific variations (e.g., equipment model, equipment manufacturer, equipment version, etc. ) . Software building objects may allow developers to write applications capable of monitoring and / or controlling building zones on a zone-by-zone level regardless of the building subsystem makeup.
[0060] Referring now to FIG. 3, a block diagram illustrating a portion of BMS 11 in greater detail is shown, according to an exemplary embodiment. Particularly, FIG. 3 illustrates a portion of BMS 11 that services a conference room 102 of building 10 (named “B1_F3_CR5” ) . Conference room 102 may be affected by many different building devices connected to many different BMS subsystems. For example, conference room 102 includes or is otherwise affected by VAV box 110, window controller 108 (e.g., a blind controller) , a system of lights 104 (named “Room Lighting 17” ) , and a door access pad 106.
[0061] Each of the building devices shown at the top of FIG. 3 may include local control circuitry configured to provide signals to their supervisory controllers or more generally to the BMS subsystems 20-26. The local control circuitry of the building devices shown at the top of FIG. 3 may also be configured to receive and respond to control signals, commands, setpoints, or other data from their supervisory controllers. For example, the local control circuitry of VAV box 110 may include circuitry that affects an actuator in response to control signals received from a field controller that is a part of HVAC system 20. Window controller 108 may include circuitry that affects windows or blinds in response to control signals received from a field controller that is part of window control system (WCS) 22. Room lighting 104 may include circuitry that affects the lighting in response to control signals received from a field controller that is part of lighting system 24. Access pad 106 may include circuitry that affects door access (e.g., locking or unlocking the door) in response to control signals received from a field controller that is part of door access system 26.
[0062] Still referring to FIG. 3, BMS controller 12 is shown to include a BMS interface 132 in communication with middleware 14. In some embodiments, BMS interface 132 is a communications interface. For example, BMS interface 132 may include wired or wireless interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc. ) for conducting data communications with various systems, devices, or networks. BMS interface 132 can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications network. In another example, BMS interface 132 includes a Wi-Fi transceiver for communicating via a wireless communications network. BMS interface 132 may be configured to communicate via local area networks or wide area networks (e.g., the Internet, a building WAN, etc. ) .
[0063] In some embodiments, BMS interface 132 and / or middleware 14 includes an application gateway configured to receive input from applications running on client devices. For example, BMS interface 132 and / or middleware 14 may include one or more wireless transceivers (e.g., a Wi-Fi transceiver, a Bluetooth transceiver, a NFC transceiver, a cellular transceiver, etc. ) for communicating with client devices. BMS interface 132 may be configured to receive building management inputs from middleware 14 or directly from one or more BMS subsystems 20-26. BMS interface 132 and / or middleware 14 can include any number of software buffers, queues, listeners, filters, translators, or other communications-supporting services.
[0064] Still referring to FIG. 3, BMS controller 12 is shown to include a processing circuit 134 including a processor 136 and memory 138. Processor 136 may be a general purpose or specific purpose processor, an application specific integrated circuit (ASIC) , one or more field programmable gate arrays (FPGAs) , a group of processing components, or other suitable processing components. Processor 136 is configured to execute computer code or instructions stored in memory 138 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc. ) .
[0065] Memory 138 may include one or more devices (e.g., memory units, memory devices, storage devices, etc. ) for storing data and / or computer code for completing and / or facilitating the various processes described in the present disclosure. Memory 138 may include random access memory (RAM) , read-only memory (ROM) , hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and / or computer instructions. Memory 138 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. Memory 138 may be communicably connected to processor 136 via processing circuit 134 and may include computer code for executing (e.g., by processor 136) one or more processes described herein. When processor 136 executes instructions stored in memory 138 for completing the various activities described herein, processor 136 generally configures BMS controller 12 (and more particularly processing circuit 134) to complete such activities.
[0066] Still referring to FIG. 3, memory 138 is shown to include building objects 142. In some embodiments, BMS controller 12 uses building objects 142 to group otherwise ungrouped or unassociated devices so that the group may be addressed or handled by applications together and in a consistent manner (e.g., a single user interface for controlling all of the BMS devices that affect a particular building zone or room) . Building objects can apply to spaces of any granularity. For example, a building object can represent an entire building, a floor of a building, or individual rooms on each floor. In some embodiments, BMS controller 12 creates and / or stores a building object in memory 138 for each zone or room of building 10. Building objects 142 can be accessed by UI clients 16 and remote applications 18 to provide a comprehensive user interface for controlling and / or viewing information for a particular building zone. Building objects 142 may be created by building object creation module 152 and associated with equipment objects by object relationship module 158, described in greater detail below.
[0067] Still referring to FIG. 3, memory 138 is shown to include equipment definitions 140. Equipment definitions 140 stores the equipment definitions for various types of building equipment. Each equipment definition may apply to building equipment of a different type. For example, equipment definitions 140 may include different equipment definitions for variable air volume modular assemblies (VMAs) , fan coil units, air handling units (AHUs) , lighting fixtures, water pumps, and / or other types of building equipment.
[0068] Equipment definitions 140 define the types of data points that are generally associated with various types of building equipment. For example, an equipment definition for VMA may specify data point types such as room temperature, damper position, supply air flow, and / or other types data measured or used by the VMA. Equipment definitions 140 allow for the abstraction (e.g., generalization, normalization, broadening, etc. ) of equipment data from a specific BMS device so that the equipment data can be applied to a room or space.
[0069] Each of equipment definitions 140 may include one or more point definitions. Each point definition may define a data point of a particular type and may include search criteria for automatically discovering and / or identifying data points that satisfy the point definition. An equipment definition can be applied to multiple pieces of building equipment of the same general type (e.g., multiple different VMA controllers) . When an equipment definition is applied to a BMS device, the search criteria specified by the point definitions can be used to automatically identify data points provided by the BMS device that satisfy each point definition.
[0070] In some embodiments, equipment definitions 140 define data point types as generalized types of data without regard to the model, manufacturer, vendor, or other differences between building equipment of the same general type. The generalized data points defined by equipment definitions 140 allows each equipment definition to be referenced by or applied to multiple different variants of the same type of building equipment.
[0071] In some embodiments, equipment definitions 140 facilitate the presentation of data points in a consistent and user-friendly manner. For example, each equipment definition may define one or more data points that are displayed via a user interface. The displayed data points may be a subset of the data points defined by the equipment definition.
[0072] In some embodiments, equipment definitions 140 specify a system type (e.g., HVAC, lighting, security, fire, etc. ) , a system sub-type (e.g., terminal units, air handlers, central plants) , and / or data category (e.g., critical, diagnostic, operational) associated with the building equipment defined by each equipment definition. Specifying such attributes of building equipment at the equipment definition level allows the attributes to be applied to the building equipment along with the equipment definition when the building equipment is initially defined. Building equipment can be filtered by various attributes provided in the equipment definition to facilitate the reporting and management of equipment data from multiple building systems.
[0073] Equipment definitions 140 can be automatically created by abstracting the data points provided by archetypal controllers (e.g., typical or representative controllers) for various types of building equipment. In some embodiments, equipment definitions 140 are created by equipment definition module 154, described in greater detail below.
[0074] Still referring to FIG. 3, memory 138 is shown to include equipment objects 144. Equipment objects 144 may be software objects that define a mapping between a data point type (e.g., supply air temperature, room temperature, damper position) and an actual data point (e.g., a measured or calculated value for the corresponding data point type) for various pieces of building equipment. Equipment objects 144 may facilitate the presentation of equipment-specific data points in an intuitive and user-friendly manner by associating each data point with an attribute identifying the corresponding data point type. The mapping provided by equipment objects 144 may be used to associate a particular data value measured or calculated by BMS 11 with an attribute that can be displayed via a user interface.
[0075] Equipment objects 144 can be created (e.g., by equipment object creation module 156) by referencing equipment definitions 140. For example, an equipment object can be created by applying an equipment definition to the data points provided by a BMS device. The search criteria included in an equipment definition can be used to identify data points of the building equipment that satisfy the point definitions. A data point that satisfies a point definition can be mapped to an attribute of the equipment object corresponding to the point definition.
[0076] Each equipment object may include one or more attributes defined by the point definitions of the equipment definition used to create the equipment object. For example, an equipment definition which defines the attributes “Occupied Command, ” “Room Temperature, ” and “Damper Position” may result in an equipment object being created with the same attributes. The search criteria provided by the equipment definition are used to identify and map data points associated with a particular BMS device to the attributes of the equipment object. The creation of equipment objects is described in greater detail below with reference to equipment object creation module 156.
[0077] Equipment objects 144 may be related with each other and / or with building objects 142. Causal relationships can be established between equipment objects to link equipment objects to each other. For example, a causal relationship can be established between a VMA and an AHU which provides airflow to the VMA. Causal relationships can also be established between equipment objects 144 and building objects 142. For example, equipment objects 144 can be associated with building objects 142 representing particular rooms or zones to indicate that the equipment object serves that room or zone. Relationships between objects are described in greater detail below with reference to object relationship module 158.
[0078] Still referring to FIG. 3, memory 138 is shown to include client services 146 and application services 148. Client services 146 may be configured to facilitate interaction and / or communication between BMS controller 12 and various internal or external clients or applications. For example, client services 146 may include web services or application programming interfaces available for communication by UI clients 16 and remote applications 18 (e.g., applications running on a mobile device, energy monitoring applications, applications allowing a user to monitor the performance of the BMS, automated fault detection and diagnostics systems, etc. ) . Application services 148 may facilitate direct or indirect communications between remote applications 18, local applications 150, and BMS controller 12. For example, application services 148 may allow BMS controller 12 to communicate (e.g., over a communications network) with remote applications 18 running on mobile devices and / or with other BMS controllers.
[0079] In some embodiments, application services 148 facilitate an applications gateway for conducting electronic data communications with UI clients 16 and / or remote applications 18. For example, application services 148 may be configured to receive communications from mobile devices and / or BMS devices. Client services 146 may provide client devices with a graphical user interface that consumes data points and / or display data defined by equipment definitions 140 and mapped by equipment objects 144.
[0080] Still referring to FIG. 3, memory 138 is shown to include a building object creation module 152. Building object creation module 152 may be configured to create the building objects stored in building objects 142. Building object creation module 152 may create a software building object for various spaces within building 10. Building object creation module 152 can create a building object for a space of any size or granularity. For example, building object creation module 152 can create a building object representing an entire building, a floor of a building, or individual rooms on each floor. In some embodiments, building object creation module 152 creates and / or stores a building object in memory 138 for each zone or room of building 10.
[0081] The building objects created by building object creation module 152 can be accessed by UI clients 16 and remote applications 18 to provide a comprehensive user interface for controlling and / or viewing information for a particular building zone. Building objects 142 can group otherwise ungrouped or unassociated devices so that the group may be addressed or handled by applications together and in a consistent manner (e.g., a single user interface for controlling all of the BMS devices that affect a particular building zone or room) . In some embodiments, building object creation module 152 uses the systems and methods described in U.S. Patent App. No. 12 / 887,390, filed September 21, 2010, for creating software defined building objects.
[0082] In some embodiments, building object creation module 152 provides a user interface for guiding a user through a process of creating building objects. For example, building object creation module 152 may provide a user interface to client devices (e.g., via client services 146) that allows a new space to be defined. In some embodiments, building object creation module 152 defines spaces hierarchically. For example, the user interface for creating building objects may prompt a user to create a space for a building, for floors within the building, and / or for rooms or zones within each floor.
[0083] In some embodiments, building object creation module 152 creates building objects automatically or semi-automatically. For example, building object creation module 152 may automatically define and create building objects using data imported from another data source (e.g., user view folders, a table, a spreadsheet, etc. ) . In some embodiments, building object creation module 152 references an existing hierarchy for BMS 11 to define the spaces within building 10. For example, BMS 11 may provide a listing of controllers for building 10 (e.g., as part of a network of data points) that have the physical location (e.g., room name) of the controller in the name of the controller itself. Building object creation module 152 may extract room names from the names of BMS controllers defined in the network of data points and create building objects for each extracted room. Building objects may be stored in building objects 142.
[0084] Still referring to FIG. 3, memory 138 is shown to include an equipment definition module 154. Equipment definition module 154 may be configured to create equipment definitions for various types of building equipment and to store the equipment definitions in equipment definitions 140. In some embodiments, equipment definition module 154 creates equipment definitions by abstracting the data points provided by archetypal controllers (e.g., typical or representative controllers) for various types of building equipment. For example, equipment definition module 154 may receive a user selection of an archetypal controller via a user interface. The archetypal controller may be specified as a user input or selected automatically by equipment definition module 154. In some embodiments, equipment definition module 154 selects an archetypal controller for building equipment associated with a terminal unit such as a VMA.
[0085] Equipment definition module 154 may identify one or more data points associated with the archetypal controller. Identifying one or more data points associated with the archetypal controller may include accessing a network of data points provided by BMS 11. The network of data points may be a hierarchical representation of data points that are measured, calculated, or otherwise obtained by various BMS devices. BMS devices may be represented in the network of data points as nodes of the hierarchical representation with associated data points depending from each BMS device. Equipment definition module 154 may find the node corresponding to the archetypal controller in the network of data points and identify one or more data points which depend from the archetypal controller node.
[0086] Equipment definition module 154 may generate a point definition for each identified data point of the archetypal controller. Each point definition may include an abstraction of the corresponding data point that is applicable to multiple different controllers for the same type of building equipment. For example, an archetypal controller for a particular VMA (i.e., “VMA-20” ) may be associated an equipment-specific data point such as “VMA-20. DPR-POS” (i.e., the damper position of VMA-20) and / or “VMA-20. SUP-FLOW” (i.e., the supply air flow rate through VMA-20) . Equipment definition module 154 abstract the equipment-specific data points to generate abstracted data point types that are generally applicable to other equipment of the same type. For example, equipment definition module 154 may abstract the equipment-specific data point “VMA-20. DPR-POS” to generate the abstracted data point type “DPR-POS” and may abstract the equipment-specific data point “VMA-20. SUP-FLOW” to generate the abstracted data point type “SUP-FLOW. ” Advantageously, the abstracted data point types generated by equipment definition module 154 can be applied to multiple different variants of the same type of building equipment (e.g., VMAs from different manufacturers, VMAs having different models or output data formats, etc. ) .
[0087] In some embodiments, equipment definition module 154 generates a user-friendly label for each point definition. The user-friendly label may be a plain text description of the variable defined by the point definition. For example, equipment definition module 154 may generate the label “Supply Air Flow” for the point definition corresponding to the abstracted data point type “SUP-FLOW” to indicate that the data point represents a supply air flow rate through the VMA. The labels generated by equipment definition module 154 may be displayed in conjunction with data values from BMS devices as part of a user-friendly interface.
[0088] In some embodiments, equipment definition module 154 generates search criteria for each point definition. The search criteria may include one or more parameters for identifying another data point (e.g., a data point associated with another controller of BMS 11 for the same type of building equipment) that represents the same variable as the point definition. Search criteria may include, for example, an instance number of the data point, a network address of the data point, and / or a network point type of the data point.
[0089] In some embodiments, search criteria include a text string abstracted from a data point associated with the archetypal controller. For example, equipment definition module 154 may generate the abstracted text string “SUP-FLOW” from the equipment-specific data point “VMA-20.SUP-FLOW. ” Advantageously, the abstracted text string matches other equipment-specific data points corresponding to the supply air flow rates of other BMS devices (e.g., “VMA-18.SUP-FLOW, ” “SUP-FLOW. VMA-01, ” etc. ) . Equipment definition module 154 may store a name, label, and / or search criteria for each point definition in memory 138.
[0090] Equipment definition module 154 may use the generated point definitions to create an equipment definition for a particular type of building equipment (e.g., the same type of building equipment associated with the archetypal controller) . The equipment definition may include one or more of the generated point definitions. Each point definition defines a potential attribute of BMS devices of the particular type and provides search criteria for identifying the attribute among other data points provided by such BMS devices.
[0091] In some embodiments, the equipment definition created by equipment definition module 154 includes an indication of display data for BMS devices that reference the equipment definition. Display data may define one or more data points of the BMS device that will be displayed via a user interface. In some embodiments, display data are user defined. For example, equipment definition module 154 may prompt a user to select one or more of the point definitions included in the equipment definition to be represented in the display data. Display data may include the user-friendly label (e.g., “Damper Position” ) and / or short name (e.g., “DPR-POS” ) associated with the selected point definitions.
[0092] In some embodiments, equipment definition module 154 provides a visualization of the equipment definition via a graphical user interface. The visualization of the equipment definition may include a point definition portion which displays the generated point definitions, a user input portion configured to receive a user selection of one or more of the point definitions displayed in the point definition portion, and / or a display data portion which includes an indication of an abstracted data point corresponding to each of the point definitions selected via the user input portion. The visualization of the equipment definition can be used to add, remove, or change point definitions and / or display data associated with the equipment definitions.
[0093] Equipment definition module 154 may generate an equipment definition for each different type of building equipment in BMS 11 (e.g., VMAs, chillers, AHUs, etc. ) . Equipment definition module 154 may store the equipment definitions in a data storage device (e.g., memory 138, equipment definitions 140, an external or remote data storage device, etc. ) .
[0094] Still referring to FIG. 3, memory 138 is shown to include an equipment object creation module 156. Equipment object creation module 156 may be configured to create equipment objects for various BMS devices. In some embodiments, equipment object creation module 156 creates an equipment object by applying an equipment definition to the data points provided by a BMS device. For example, equipment object creation module 156 may receive an equipment definition created by equipment definition module 154. Receiving an equipment definition may include loading or retrieving the equipment definition from a data storage device.
[0095] In some embodiments, equipment object creation module 156 determines which of a plurality of equipment definitions to retrieve based on the type of BMS device used to create the equipment object. For example, if the BMS device is a VMA, equipment object creation module 156 may retrieve the equipment definition for VMAs; whereas if the BMS device is a chiller, equipment object creation module 156 may retrieve the equipment definition for chillers. The type of BMS device to which an equipment definition applies may be stored as an attribute of the equipment definition. Equipment object creation module 156 may identify the type of BMS device being used to create the equipment object and retrieve the corresponding equipment definition from the data storage device.
[0096] In other embodiments, equipment object creation module 156 receives an equipment definition prior to selecting a BMS device. Equipment object creation module 156 may identify a BMS device of BMS 11 to which the equipment definition applies. For example, equipment object creation module 156 may identify a BMS device that is of the same type of building equipment as the archetypal BMS device used to generate the equipment definition. In various embodiments, the BMS device used to generate the equipment object may be selected automatically (e.g., by equipment object creation module 156) , manually (e.g., by a user) or semi-automatically (e.g., by a user in response to an automated prompt from equipment object creation module 156) .
[0097] In some embodiments, equipment object creation module 156 creates an equipment discovery table based on the equipment definition. For example, equipment object creation module 156 may create an equipment discovery table having attributes (e.g., columns) corresponding to the variables defined by the equipment definition (e.g., a damper position attribute, a supply air flow rate attribute, etc. ) . Each column of the equipment discovery table may correspond to a point definition of the equipment definition. The equipment discovery table may have columns that are categorically defined (e.g., representing defined variables) but not yet mapped to any particular data points.
[0098] Equipment object creation module 156 may use the equipment definition to automatically identify one or more data points of the selected BMS device to map to the columns of the equipment discovery table. Equipment object creation module 156 may search for data points of the BMS device that satisfy one or more of the point definitions included in the equipment definition. In some embodiments, equipment object creation module 156 extracts a search criterion from each point definition of the equipment definition. Equipment object creation module 156 may access a data point network of the building automation system to identify one or more data points associated with the selected BMS device. Equipment object creation module 156 may use the extracted search criterion to determine which of the identified data points satisfy one or more of the point definitions.
[0099] In some embodiments, equipment object creation module 156 automatically maps (e.g., links, associates, relates, etc. ) the identified data points of selected BMS device to the equipment discovery table. A data point of the selected BMS device may be mapped to a column of the equipment discovery table in response to a determination by equipment object creation module 156 that the data point satisfies the point definition (e.g., the search criteria) used to generate the column. For example, if a data point of the selected BMS device has the name “VMA-18. SUP-FLOW” and a search criterion is the text string “SUP-FLOW, ” equipment object creation module 156 may determine that the search criterion is met. Accordingly, equipment object creation module 156 may map the data point of the selected BMS device to the corresponding column of the equipment discovery table.
[0100] Advantageously, equipment object creation module 156 may create multiple equipment objects and map data points to attributes of the created equipment objects in an automated fashion (e.g., without human intervention, with minimal human intervention, etc. ) . The search criteria provided by the equipment definition facilitates the automatic discovery and identification of data points for a plurality of equipment object attributes. Equipment object creation module 156 may label each attribute of the created equipment objects with a device-independent label derived from the equipment definition used to create the equipment object. The equipment objects created by equipment object creation module 156 can be viewed (e.g., via a user interface) and / or interpreted by data consumers in a consistent and intuitive manner regardless of device-specific differences between BMS devices of the same general type. The equipment objects created by equipment object creation module 156 may be stored in equipment objects 144.
[0101] Still referring to FIG. 3, memory 138 is shown to include an object relationship module 158. Object relationship module 158 may be configured to establish relationships between equipment objects 144. In some embodiments, object relationship module 158 establishes causal relationships between equipment objects 144 based on the ability of one BMS device to affect another BMS device. For example, object relationship module 158 may establish a causal relationship between a terminal unit (e.g., a VMA) and an upstream unit (e.g., an AHU, a chiller, etc. ) which affects an input provided to the terminal unit (e.g., air flow rate, air temperature, etc. ) .
[0102] Object relationship module 158 may establish relationships between equipment objects 144 and building objects 142 (e.g., spaces) . For example, object relationship module 158 may associate equipment objects 144 with building objects 142 representing particular rooms or zones to indicate that the equipment object serves that room or zone. In some embodiments, object relationship module 158 provides a user interface through which a user can define relationships between equipment objects 144 and building objects 142. For example, a user can assign relationships in a “drag and drop” fashion by dragging and dropping a building object and / or an equipment object into a “serving” cell of an equipment object provided via the user interface to indicate that the BMS device represented by the equipment object serves a particular space or BMS device.
[0103] Still referring to FIG. 3, memory 138 is shown to include a building control services module 160. Building control services module 160 may be configured to automatically control BMS 11 and the various subsystems thereof. Building control services module 160 may utilize closed loop control, feedback control, PI control, model predictive control, or any other type of automated building control methodology to control the environment (e.g., a variable state or condition) within building 10.
[0104] Building control services module 160 may receive inputs from sensory devices (e.g., temperature sensors, pressure sensors, flow rate sensors, humidity sensors, electric current sensors, cameras, radio frequency sensors, microphones, etc. ) , user input devices (e.g., computer terminals, client devices, user devices, etc. ) or other data input devices via BMS interface 132. Building control services module 160 may apply the various inputs to a building energy use model and / or a control algorithm to determine an output for one or more building control devices (e.g., dampers, air handling units, chillers, boilers, fans, pumps, etc. ) in order to affect a variable state or condition within building 10 (e.g., zone temperature, humidity, air flow rate, etc. ) .
[0105] In some embodiments, building control services module 160 is configured to control the environment of building 10 on a zone-individualized level. For example, building control services module 160 may control the environment of two or more different building zones using different setpoints, different constraints, different control methodology, and / or different control parameters. Building control services module 160 may operate BMS 11 to maintain building conditions (e.g., temperature, humidity, air quality, etc. ) within a setpoint range, to optimize energy performance (e.g., to minimize energy consumption, to minimize energy cost, etc. ) , and / or to satisfy any constraint or combination of constraints as may be desirable for various implementations.
[0106] In some embodiments, building control services module 160 uses the location of various BMS devices to translate an input received from a building system into an output or control signal for the building system. Building control services module 160 may receive location information for BMS devices and automatically set or recommend control parameters for the BMS devices based on the locations of the BMS devices. For example, building control services module 160 may automatically set a flow rate setpoint for a VAV box based on the size of the building zone in which the VAV box is located.
[0107] Building control services module 160 may determine which of a plurality of sensors to use in conjunction with a feedback control loop based on the locations of the sensors within building 10. For example, building control services module 160 may use a signal from a temperature sensor located in a building zone as a feedback signal for controlling the temperature of the building zone in which the temperature sensor is located.
[0108] In some embodiments, building control services module 160 automatically generates control algorithms for a controller or a building zone based on the location of the zone in the building 10. For example, building control services module 160 may be configured to predict a change in demand resulting from sunlight entering through windows based on the orientation of the building and the locations of the building zones (e.g., east-facing, west-facing, perimeter zones, interior zones, etc. ) .
[0109] Building control services module 160 may use zone location information and interactions between adjacent building zones (rather than considering each zone as an isolated system) to more efficiently control the temperature and / or airflow within building 10. For control loops that are conducted at a larger scale (i.e., floor level) building control services module 160 may use the location of each building zone and / or BMS device to coordinate control functionality between building zones. For example, building control services module 160 may consider heat exchange and / or air exchange between adjacent building zones as a factor in determining an output control signal for the building zones.
[0110] In some embodiments, building control services module 160 is configured to optimize the energy efficiency of building 10 using the locations of various BMS devices and the control parameters associated therewith. Building control services module 160 may be configured to achieve control setpoints using building equipment with a relatively lower energy cost (e.g., by causing airflow between connected building zones) in order to reduce the loading on building equipment with a relatively higher energy cost (e.g., chillers and roof top units) . For example, building control services module 160 may be configured to move warmer air from higher elevation zones to lower elevation zones by establishing pressure gradients between connected building zones.
[0111] Referring now to FIG. 4, another block diagram illustrating a portion of BMS 11 in greater detail is shown, according to some embodiments. BMS 11 can be implemented in building 10 to automatically monitor and control various building functions. BMS 11 is shown to include BMS controller 12 and a plurality of building subsystems 428. Building subsystems 428 are shown to include a building electrical subsystem 434, an information communication technology (ICT) subsystem 436, a security subsystem 438, a HVAC subsystem 440, a lighting subsystem 442, a lift / escalators subsystem 432, and a fire safety subsystem 430. In various embodiments, building subsystems 428 can include fewer, additional, or alternative subsystems. For example, building subsystems 428 may also or alternatively include a refrigeration subsystem, an advertising or signage subsystem, a cooking subsystem, a vending subsystem, a printer or copy service subsystem, or any other type of building subsystem that uses controllable equipment and / or sensors to monitor or control building 10.
[0112] Each of building subsystems 428 can include any number of devices, controllers, and connections for completing its individual functions and control activities. HVAC subsystem 440 can include many of the same components as HVAC system 20, as described with reference to FIGS. 2-3. For example, HVAC subsystem 440 can include a chiller, a boiler, any number of air handling units, economizers, field controllers, supervisory controllers, actuators, temperature sensors, and other devices for controlling the temperature, humidity, airflow, or other variable conditions within building 10. Lighting subsystem 442 can include any number of light fixtures, ballasts, lighting sensors, dimmers, or other devices configured to controllably adjust the amount of light provided to a building space. Security subsystem 438 can include occupancy sensors, video surveillance cameras, digital video recorders, video processing servers, intrusion detection devices, access control devices and servers, or other security-related devices.
[0113] Still referring to FIG. 4, BMS controller 12 is shown to include a communications interface 407 and a BMS interface 132. Interface 407 may facilitate communications between BMS controller 12 and external applications (e.g., monitoring and reporting applications 422, enterprise control applications 426, remote systems and applications 444, applications residing on client devices 448, etc. ) for allowing user control, monitoring, and adjustment to BMS controller 12 and / or subsystems 428. Interface 407 may also facilitate communications between BMS controller 12 and client devices 448. BMS interface 132 may facilitate communications between BMS controller 12 and building subsystems 428 (e.g., HVAC, lighting security, lifts, power distribution, business, etc. ) .
[0114] Interfaces 407, 132 can be or include wired or wireless communications interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc. ) for conducting data communications with building subsystems 428 or other external systems or devices. In various embodiments, communications via interfaces 407, 132 can be direct (e.g., local wired or wireless communications) or via a communications network 446 (e.g., a WAN, the Internet, a cellular network, etc. ) . For example, interfaces 407, 132 can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications link or network. In another example, interfaces 407, 132 can include a Wi-Fi transceiver for communicating via a wireless communications network. In another example, one or both of interfaces 407, 132 can include cellular or mobile phone communications transceivers. In one embodiment, communications interface 407 is a power line communications interface and BMS interface 132 is an Ethernet interface. In other embodiments, both communications interface 407 and BMS interface 132 are Ethernet interfaces or are the same Ethernet interface.
[0115] Still referring to FIG. 4, BMS controller 12 is shown to include a processing circuit 134 including a processor 136 and memory 138. Processing circuit 134 can be communicably connected to BMS interface 132 and / or communications interface 407 such that processing circuit 134 and the various components thereof can send and receive data via interfaces 407, 132. Processor 136 can be implemented as a general purpose processor, an application specific integrated circuit (ASIC) , one or more field programmable gate arrays (FPGAs) , a group of processing components, or other suitable electronic processing components.
[0116] Memory 138 (e.g., memory, memory unit, storage device, etc. ) can include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc. ) for storing data and / or computer code for completing or facilitating the various processes, layers and modules described in the present application. Memory 138 can be or include volatile memory or non-volatile memory. Memory 138 can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present application. According to some embodiments, memory 138 is communicably connected to processor 136 via processing circuit 134 and includes computer code for executing (e.g., by processing circuit 134 and / or processor 136) one or more processes described herein.
[0117] In some embodiments, BMS controller 12 is implemented within a single computer (e.g., one server, one housing, etc. ) . In various other embodiments BMS controller 12 can be distributed across multiple servers or computers (e.g., that can exist in distributed locations) . Further, while FIG. 4 shows applications 422 and 426 as existing outside of BMS controller 12, in some embodiments, applications 422 and 426 can be hosted within BMS controller 12 (e.g., within memory 138) .
[0118] Still referring to FIG. 4, memory 138 is shown to include an enterprise integration layer 410, an automated measurement and validation (AM&V) layer 412, a demand response (DR) layer 414, a fault detection and diagnostics (FDD) layer 416, an integrated control layer 418, and a building subsystem integration later 420. Layers 410-420 can be configured to receive inputs from building subsystems 428 and other data sources, determine optimal control actions for building subsystems 428 based on the inputs, generate control signals based on the optimal control actions, and provide the generated control signals to building subsystems 428. The following paragraphs describe some of the general functions performed by each of layers 410-420 in BMS 11.
[0119] Enterprise integration layer 410 can be configured to serve clients or local applications with information and services to support a variety of enterprise-level applications. For example, enterprise control applications 426 can be configured to provide subsystem-spanning control to a graphical user interface (GUI) or to any number of enterprise-level business applications (e.g., accounting systems, user identification systems, etc. ) . Enterprise control applications 426 may also or alternatively be configured to provide configuration GUIs for configuring BMS controller 12. In yet other embodiments, enterprise control applications 426 can work with layers 410-420 to optimize building performance (e.g., efficiency, energy use, comfort, or safety) based on inputs received at interface 407 and / or BMS interface 132.
[0120] Building subsystem integration layer 420 can be configured to manage communications between BMS controller 12 and building subsystems 428. For example, building subsystem integration layer 420 may receive sensor data and input signals from building subsystems 428 and provide output data and control signals to building subsystems 428. Building subsystem integration layer 420 may also be configured to manage communications between building subsystems 428. Building subsystem integration layer 420 translate communications (e.g., sensor data, input signals, output signals, etc. ) across a plurality of multi-vendor / multi-protocol systems.
[0121] Demand response layer 414 can be configured to optimize resource usage (e.g., electricity use, natural gas use, water use, etc. ) and / or the monetary cost of such resource usage in response to satisfy the demand of building 10. The optimization can be based on time-of-use prices, curtailment signals, energy availability, or other data received from utility providers, distributed energy generation systems 424, from energy storage 427, or from other sources. Demand response layer 414 may receive inputs from other layers of BMS controller 12 (e.g., building subsystem integration layer 420, integrated control layer 418, etc. ) . The inputs received from other layers can include environmental or sensor inputs such as temperature, carbon dioxide levels, relative humidity levels, air quality sensor outputs, occupancy sensor outputs, room schedules, and the like. The inputs may also include inputs such as electrical use (e.g., expressed in kWh) , thermal load measurements, pricing information, projected pricing, smoothed pricing, curtailment signals from utilities, and the like.
[0122] According to some embodiments, demand response layer 414 includes control logic for responding to the data and signals it receives. These responses can include communicating with the control algorithms in integrated control layer 418, changing control strategies, changing setpoints, or activating / deactivating building equipment or subsystems in a controlled manner. Demand response layer 414 may also include control logic configured to determine when to utilize stored energy. For example, demand response layer 414 may determine to begin using energy from energy storage 427 just prior to the beginning of a peak use hour.
[0123] In some embodiments, demand response layer 414 includes a control module configured to actively initiate control actions (e.g., automatically changing setpoints) which minimize energy costs based on one or more inputs representative of or based on demand (e.g., price, a curtailment signal, a demand level, etc. ) . In some embodiments, demand response layer 414 uses equipment models to determine an optimal set of control actions. The equipment models can include, for example, thermodynamic models describing the inputs, outputs, and / or functions performed by various sets of building equipment. Equipment models may represent collections of building equipment (e.g., subplants, chiller arrays, etc. ) or individual devices (e.g., individual chillers, heaters, pumps, etc. ) .
[0124] Demand response layer 414 may further include or draw upon one or more demand response policy definitions (e.g., databases, XML files, etc. ) . The policy definitions can be edited or adjusted by a user (e.g., via a graphical user interface) so that the control actions initiated in response to demand inputs can be tailored for the user’s application, desired comfort level, particular building equipment, or based on other concerns. For example, the demand response policy definitions can specify which equipment can be turned on or off in response to particular demand inputs, how long a system or piece of equipment should be turned off, what setpoints can be changed, what the allowable set point adjustment range is, how long to hold a high demand setpoint before returning to a normally scheduled setpoint, how close to approach capacity limits, which equipment modes to utilize, the energy transfer rates (e.g., the maximum rate, an alarm rate, other rate boundary information, etc. ) into and out of energy storage devices (e.g., thermal storage tanks, battery banks, etc. ) , and when to dispatch on-site generation of energy (e.g., via fuel cells, a motor generator set, etc. ) .
[0125] Integrated control layer 418 can be configured to use the data input or output of building subsystem integration layer 420 and / or demand response later 414 to make control decisions. Due to the subsystem integration provided by building subsystem integration layer 420, integrated control layer 418 can integrate control activities of the subsystems 428 such that the subsystems 428 behave as a single integrated supersystem. In some embodiments, integrated control layer 418 includes control logic that uses inputs and outputs from a plurality of building subsystems to provide greater comfort and energy savings relative to the comfort and energy savings that separate subsystems could provide alone. For example, integrated control layer 418 can be configured to use an input from a first subsystem to make an energy-saving control decision for a second subsystem. Results of these decisions can be communicated back to building subsystem integration layer 420.
[0126] Integrated control layer 418 is shown to be logically below demand response layer 414. Integrated control layer 418 can be configured to enhance the effectiveness of demand response layer 414 by enabling building subsystems 428 and their respective control loops to be controlled in coordination with demand response layer 414. This configuration may advantageously reduce disruptive demand response behavior relative to conventional systems. For example, integrated control layer 418 can be configured to assure that a demand response-driven upward adjustment to the setpoint for chilled water temperature (or another component that directly or indirectly affects temperature) does not result in an increase in fan energy (or other energy used to cool a space) that would result in greater total building energy use than was saved at the chiller.
[0127] Integrated control layer 418 can be configured to provide feedback to demand response layer 414 so that demand response layer 414 checks that constraints (e.g., temperature, lighting levels, etc. ) are properly maintained even while demanded load shedding is in progress. The constraints may also include setpoint or sensed boundaries relating to safety, equipment operating limits and performance, comfort, fire codes, electrical codes, energy codes, and the like. Integrated control layer 418 is also logically below fault detection and diagnostics layer 416 and automated measurement and validation layer 412. Integrated control layer 418 can be configured to provide calculated inputs (e.g., aggregations) to these higher levels based on outputs from more than one building subsystem.
[0128] Automated measurement and validation (AM&V) layer 412 can be configured to verify that control strategies commanded by integrated control layer 418 or demand response layer 414 are working properly (e.g., using data aggregated by AM&V layer 412, integrated control layer 418, building subsystem integration layer 420, FDD layer 416, or otherwise) . The calculations made by AM&V layer 412 can be based on building system energy models and / or equipment models for individual BMS devices or subsystems. For example, AM&V layer 412 may compare a model-predicted output with an actual output from building subsystems 428 to determine an accuracy of the model.
[0129] Fault detection and diagnostics (FDD) layer 416 can be configured to provide on-going fault detection for building subsystems 428, building subsystem devices (i.e., building equipment) , and control algorithms used by demand response layer 414 and integrated control layer 418. FDD layer 416 may receive data inputs from integrated control layer 418, directly from one or more building subsystems or devices, or from another data source. FDD layer 416 may automatically diagnose and respond to detected faults. The responses to detected or diagnosed faults can include providing an alert message to a user, a maintenance scheduling system, or a control algorithm configured to attempt to repair the fault or to work-around the fault.
[0130] FDD layer 416 can be configured to output a specific identification of the faulty component or cause of the fault (e.g., loose damper linkage) using detailed subsystem inputs available at building subsystem integration layer 420. In other exemplary embodiments, FDD layer 416 is configured to provide “fault” events to integrated control layer 418 which executes control strategies and policies in response to the received fault events. According to some embodiments, FDD layer 416 (or a policy executed by an integrated control engine or business rules engine) may shut-down systems or direct control activities around faulty devices or systems to reduce energy waste, extend equipment life, or assure proper control response.
[0131] FDD layer 416 can be configured to store or access a variety of different system data stores (or data points for live data) . FDD layer 416 may use some content of the data stores to identify faults at the equipment level (e.g., specific chiller, specific AHU, specific terminal unit, etc. ) and other content to identify faults at component or subsystem levels. For example, building subsystems 428 may generate temporal (i.e., time-series) data indicating the performance of BMS 11 and the various components thereof. The data generated by building subsystems 428 can include measured or calculated values that exhibit statistical characteristics and provide information about how the corresponding system or process (e.g., a temperature control process, a flow control process, etc. ) is performing in terms of error from its setpoint. These processes can be examined by FDD layer 416 to expose when the system begins to degrade in performance and alert a user to repair the fault before it becomes more severe. Communication System with Modular Architecture
[0132] Referring now to FIG. 5, a communication system 500 implemented using a modular architecture is shown, according to some embodiments. Communication system 500 can be used in a BMS (e.g., BMS 11) , a subsystem of a BMS (e.g., any of building subsystems 428) , or any other type of system in which IO modules are used. Communication system 500 can be or include controller 12 (FIG. 4) or any other type of controller in building 10 or can be a communication unit for network 446 or any of building subsystems 428 and devices and networks associated therewith (FIG. 4) . For example, communication system 500 can be employed with or communicate with a valve controller, a damper controller and AHU controller, an RTU controller, a thermostat, a fan speed controller, a compressor controller, combinations thereof, or any device for controlling equipment or communicating with equipment in HVAC subsystem 440 (FIG. 4) .
[0133] In some embodiments, communication system 500 includes a base module, or communication module 502, at least one module 504A-D, and an end cap 506. Modules 504A-D are IOMs in some embodiments. In some embodiments, a number of modules 504A-D installed with communication module 502 or end cap 506 can be slidably engaged with each other. For example, see FIG. 6 where module 504B is slidably connected between modules 504A and 504C. The slidable connection can use a hook and groove interface 561. Modules 502 and 504A-D can be configured as smart modules including processing and communication circuits in some embodiments. In some embodiments, modules 504A-D have a housing that interfaces or integrates with the housing for communication module 502 and end cap 506 when modules 504A-D are plugged into each other so that a unified housing is provided for communication system 500. If a module 504A-D is not provided, a blank or dummy housing component can be provided to protect the interface and to provide an integrated housing appearance in some embodiments.
[0134] Communication module 502 includes a processor, memory and components for performing communication operations including wired communication operations. Communication module 502 includes a connector 509 (e.g., a hot plug connector) for connecting to the module 504. Communication module 502 can include serial ports and communication interfaces for communication with various other devices, systems, and networks. Communication module 502 can house a microcontroller unit (MCU) , a system on a chip (SOC) , or generally any type of circuit such as an integrated circuit (IC) , an application-specific integrated circuit (ASIC) , a daughterboard, or a field-programmable gate array (FPGA) . Communication module 502 may also be a larger device or may be a circuit or chip installed in or connected to a larger device. Further, communication module 502 may connect to existing devices such as a central processing unit (CPU) of a sensor or actuator or may replace processing circuits of existing devices.
[0135] Module 502 includes DIP switches 508 for setting various parameters (e.g., addressing) . Module 502 can also include a connector for providing a physical or magnetic connection. Data and power communication can occur through connector 509 in some embodiments. Connector 509 is a hot plug connector in some embodiments. Module 502 also includes indicators 520.
[0136] Module 502 can house various hardware components and interfaces that may be provided with system 500. The components can include a wireless communications module, a wired communications module, a universal serial bus (USB) module, an RS-485 interface, a Bluetooth module, expandable input / output (I / O) points, and an expandable memory (e.g., SD-RAM) . Other types of modular hardware components are possible and contemplated. Generally, module 502 allows communication system 500 to be customized for a variety of different applications. Using fixed and / or modular hardware components, communication system 500 can communicate with edge and legacy devices, cloud applications, external memory, and a Wi-Fi transceiver in some embodiments.
[0137] In some embodiments, modules 504A-D are terminal devices and can include terminal block 514, terminal block 516, and indicators 518. Module 502 can include similar components. Indicators 518 can be a liquid crystal display (LCD) , lamps, or an LED (red, green and blue) or other lights. In some embodiments, indicators 518 include a microphone, speaker or a buzzer for audio communication. Indicators 518 and terminal blocks 514 and 516 can be specific to certain applications, interfaces or protocols. In some embodiments, communication module 502 communicates with terminal block 514 and 516 via connectors between modules 502 and 504A-D (e.g., on main planar sides) . Power for modules 504A-D can be provided via the connector 509 or main planar side connections.
[0138] Terminal blocks 514 and 516 are mechanical connectors. In some embodiments, terminal blocks 514 and 516 have a specific configuration and number of connections for particular applications (e.g., associated with the IOM) . Terminal blocks 514 and 516 can be modular insulated housing structures with terminals for receiving wires or connections having a variety of pitches and pole numbers. Terminal blocks 514 and 516 can be a printed circuit board mount, a barrier strip, a feed through terminal block, or other connective structure. In some embodiments, terminal blocks 514 and 516 provide different I / O types combined for modularity (e.g., UI –4-20mA, 0-10V, RTD, dry contact BI and UO –AO (4-20mA, 0-10V) , BO (triac, FET) , (SS) RO, wet contact BI) . Terminal blocks 514 and 516 can each be a set of four terminal blocks including fixed points or input output interfaces for communication system 500. Terminal blocks 514 and 516 can be configured to provide the appropriate interface for the signals associated with the application of the IOM. Terminal blocks 514 and 516 can be for an analog input, a digital input, an analog output, a digital output, and combinations thereof.
[0139] In some embodiments, communication system 500 can be attached to a DIN rail at an interface 519. Latches 521 can be used to selectively secure modules 502 and 504 to the DIN rail at interface 519. In some embodiments, communication system 500 also includes one or more additional modules such as a module embodied as a DIN rail mounted controller in some embodiments.
[0140] The architectural design of system 500 allows customers to select only hardware components desired for a specific application without forcing customers to purchase hardware that is not necessary in some embodiments. Moreover, customers can remove any of modules 504A-D if desired. The modular design also allows customers to easily replace a failed component in the field instead of removing the component for servicing or purchasing an entirely new part in some embodiments. In some embodiments, a processor board might have inadequate millions of instructions per second (MIPS) or memory capability and could be replaced with a faster processor or one with more memory. The existing modules 504A-D can remain intact, potentially saving wiring and commissioning time and cost, in addition to saving cost associated with preserving the existing boards in the system.
[0141] In some embodiments, modules 504A-D allow dynamic factory and field configuration of point counts and types. The modules 504A-D are hot-pluggable / swappable and are automatically identified / addressed by the main processor (e.g., by processors using multi-master with address arbitration) or manually addressed via switches or NFC. In some embodiments, each of modules 504A-D is serialized and has a unique address (e.g., processor or EEPROM on an internal serial bus with unique identifier) , which is readable by the processor to determine the I / O point mix that is installed in the overall system. In some embodiments addressing is accomplished by use of a split serial bus. In some embodiments, only one processor board is used in system 500 and, and all IOMs pass a serial signal through a processor onto the next module.
[0142] An independent data signal is electrically shared by all modules 504A-D in some embodiments. In the addressing sequence, a serial signal would communicate from the processor to a first module of modules 504A-D. The first module would receive commands on the serial signal and respond on the shared data signal. After establishing a unique address identifier, the first module acts as a serial pass-through to send address arbitration signaling to the second module, not replying on the shared data signal. This process is carried on, until no response is received on the data line after querying all installed modules 504A-D. This process occurs at each power-up sequence in some embodiments.
[0143] Indicators 518 and 520 provide a user indication of status and / or terminal position. Indications are used for fault and / or I / O status (i.e., wiring fault, out-of-range input, active output, etc. ) in some embodiments. Each modules 504A-D is self-encapsulated for environmental protection and safe handling in the field in some embodiments. In addition, the connections between modules 504A-D and module 502 can be keyed (disallowed in certain positions) and / or physically secured with additional hardware for a robust design.
[0144] Modules 504A-D can be configured for various point types including but not limited to a universal input (UI) , a binary input (BI) , an analog output (AO) , a binary output (BO) , a universal output (UO) , configurable output (CO) , a relay output, and combinations thereof. Point types used by controller model numbers MS-IOM-1711, MS-IOM-2711, MS-IOM-3711, and MS-IOM-4711 manufactured for Johnson Controls International can be used in system 500. In some embodiments, the UI accepts an analog input, voltage mode 0-10 VDC signal, an analog input, current mode 4-20ma signal, an analog input, resistive mode 0-2 Kilo Ohm signal (e.g., for Resistance Temperature Detector (RTD) ) , and a binary input, dry contact maintained mode signal. In some embodiments, the BI accepts a pulse counter mode (high speed) , 100 Hz signal and a binary input, dry contact maintained mode signal. In some embodiments, the AO provides an analog output, voltage mode 0-10 VDC signal, and an analog output, current mode 4-20ma signal. In some embodiments, the BO provides a 24 VAC triac signal. In some embodiments, the UO provides an analog output, voltage mode 0-10 VDC signal, an analog output, current mode 4-20ma signal, and a binary output mode, 24 V AC / DC FET signal. In some embodiments, the CO provides a 24 VAC triac signal. In some embodiments, the UO provides an analog output, voltage mode 0-10 VDC signal, and a binary output mode, 24 VAC triac signal. In some embodiments, the relay output provides 120 / 240 VAC signal. Additional point types and combinations can also be utilized.
[0145] With reference to FIG. 7, a module 550 can be used as one of modules 504A-D (FIG. 5) and is configured for use as a module capable of providing and / or receiving an analog signal via a digital circuit 552. Digital circuit 552 is configured to reduce excessive voltage loss on a transistor 560 (e.g., one or more MOSFETs or other transistors) associated with the analog signal. The reduction reduces high temperature rise of MOSFET / transistor 560, thereby reducing the internal temperature of system 500 and module 550 and reducing the cost of system 500.
[0146] Instead of using linear characteristics of the MOSFET / transistor 560, the circuit 552 uses digital switching characteristics so that the MOSFET / transistor 560 operates like a power switch in some embodiments. In some embodiments, circuit 552 provides a pulse width modulated (PWM) signal to turn on / off the MOSFET / transistor 560. Modular Edge Controller
[0147] Referring now to FIGS. 8-9, a modular edge controller 600 is shown, according to an exemplary embodiment. Controller 600 is shown to include many of the same components as communication system 500 described with reference to FIGS. 5-7. For example, controller 600 is shown to include a number of modules 504A-D and an end cap 506 which may connect to each other using hook and groove interface 561 between each of modules 504A-D and end cap 506. Each of modules 504A-D may include indicators 518, latches 521 and respective terminal blocks 510, 512, 514, and 516. These components of controller 600 may be the same as or similar to the like-numbered components of communication system 500, as described with reference to FIGS. 5-7.
[0148] Controller 600 is shown to include an edge control module 602. Edge control module 602 may be configured for use with modules 504A-D and can be attached to any number of modules 504A-D (i.e., zero or more) to form a customizable and modular edge controller 600. In some embodiments, edge control module 602 replaces module 502 in communication system 500 and can interface with modules 504A-D and / or end cap 506 in the same manner as module 502, as described with reference to FIGS. 5-7. For example, edge control module 602 can interface with modules 504A-D and / or end cap 506 using a slidable connection such as hook and groove interface 561. In some embodiments, edge control module 602 and modules 504A-D are configured as smart modules including processing and communication circuits. Edge control module 602 can be attached to one or more modules 504A-D or can be attached directly to end cap 506, for example if modules 504A-D are omitted. In some embodiments, edge control module 602 has a housing that interfaces or integrates with the housings for modules 504A-D and / or end cap 506 when attached to each other so that a unified housing is provided for modular edge controller 600. Edge control module 602 and modules 504A-D may be self-encapsulated for environmental protection and safe handling in the field in some embodiments. The connections between modules 504A-D and edge control module 602 can be keyed (e.g., disallowed in certain positions) and / or physically secured with additional hardware for a robust design.
[0149] Edge control module 602 may include a processor, memory, and components for performing various communication and control operations, including wired communication operations. For example, edge control module 602 is shown to include terminal blocks 608, which may be the same as or similar to terminal blocks 510-516 as described with reference to FIGS. 5-7. In some embodiments, terminal blocks 608 include mechanical connectors configured to fit into an RS-485 interface on the front face of edge control module 602. Edge control module 602 may use the RS-485 interface and terminal blocks 608 as a physical layer for communications protocols such as Modbus RTU, BACnet MS / TP, and / or other electronic data communications in BMS 11. For example, edge control module 602 can use RS-485 to communicate with other controllers or modules in BMS 11 (e.g., other instances of modular edge controller 600, instances of communication module 702 described in greater detail with reference to FIGS. 12-15, other IO modules, etc. ) , various other devices, systems, and / or networks (e.g., sensors, actuators, or other building equipment in BMS 10) .
[0150] Edge control module 602 is shown to include switches 610 (e.g., push-button switches, sliding switches, etc. ) which can be used to toggle on / off their respective RS-485 interfaces as well as toggle on / off EOL / termination function of the RS-485 interfaces. Edge control module 602 may include indicators 620 showing the status of various components of edge control module 602 (e.g., communications or connections via the RS-485 interface, internal processing operations, etc. ) . Indicators 620 can be a liquid crystal display (LCD) , lamps, an LED (red, green and blue) or other lights. In various embodiments, indicators 620 may provide a user indication of device status, terminal position, fault status, I / O status (e.g., wiring fault, out-of-range input, active output, etc. ) or any other status indication. In some embodiments, indicators 620 include a microphone, speaker or a buzzer for audio communication. Indicators 620 and terminal blocks 608 can be specific to certain applications, interfaces or protocols. In some embodiments, edge control module 602 communicates with terminal blocks 608 via connectors between modules 602 and 504A-D (e.g., on main planar sides) . Power for modules 504A-D can be provided via terminal blocks 608 or main planar side connections.
[0151] In various embodiments, edge control module 602 may include a microcontroller unit (MCU) , a system on a chip (SOC) , or generally any type of circuit such as an integrated circuit (IC) , an application-specific integrated circuit (ASIC) , a daughterboard, or a field-programmable gate array (FPGA) . Edge control module 602 may be a larger device or may be a circuit or chip installed in or connected to a larger device. Further, edge control module 602 may connect to existing devices such as a central processing unit (CPU) of a sensor or actuator or may replace processing circuits of existing devices.
[0152] Edge control module 602 may include various hardware components and interfaces that may be provided with modular edge controller 600. The components can include a wireless communications module, a wired communications module, a universal serial bus (USB) module, an RS-485 interface, a Bluetooth module, expandable input / output (I / O) points, and an expandable memory (e.g., SD-RAM) . For example, edge control module 602 is shown to include a serial (USB) interface 606 (e.g., a USB-C port) , and two Ethernet ports 604A and 604B (collectively Ethernet ports 604) . Serial interface 606 and / or the RS-485 interfaces via terminal blocks 608 may support various types of serial communications such as BACnet MS / TP, Modbus / RTU and sensor-actuator (SA) bus communications. In some embodiments, serial interface 606 and / or the RS-485 interfaces connected to terminal blocks 608 can use a switch to connect or disconnect a terminal resistor.
[0153] Ethernet ports 604 may support various types of TCP / IP communications such as BACnet / IP, Modbus TCP (e.g., function codes 01 / 02 / 03 / 04 / 05 / 06 / 15 / 16) , and MQTT communications. In some embodiments, edge control module 602 uses a license file to activate or deactivate one or more of serial interface 606, the RS-485 interfaces connected to terminal blocks 608, Ethernet port 604A, and / or Ethernet port 604B. Other types of modular hardware components are possible and contemplated. Advantageously, Ethernet ports 604 allow edge control module 602 and modular edge controller 600 to integrate into a variety of different network topologies such as star, daisy chain, and ring topologies with STP / RSTP or other ring topology protocols or RSTP redundancy protocols, as described in greater detail with reference to FIGS. 16-19. In some embodiments, modular edge controller 600 can be attached to a DIN rail at an interface 619. Latches 521 and 621 can be used to selectively secure modules 504A-D and edge control module 602 to the DIN rail at interface 619.
[0154] Generally, edge control module 602 allows modular edge controller 600 to be customized for a variety of different applications. Using fixed and / or modular hardware components, edge control module 602 can communicate with edge and legacy devices, cloud applications, external memory, and a Wi-Fi transceiver, in various embodiments. In some embodiments, edge control module 602 can be connected to many signal modules (e.g., modules 504A-D) and / or physical IO points via direct connection (e.g., via terminal blocks 608) . For example, an exemplary implementation of edge control module 602 may include connecting edge control module 602 to ten modules 504A-D and / or eighty physical IO points via direct connection. Edge control module 602 may support a large number of physical IO points (e.g., 400 or more) via direct connection and / or expansion modules 504A-D. In some embodiments, edge control module 602 can connect to 31 slave devices for each port and may support monitoring and control activities for over 2, 500 objects.
[0155] Edge control module 602 and modules 504A-D can be configured for various point types including but not limited to a universal input (UI) , a binary input (BI) , an analog output (AO) , a binary output (BO) , a universal output (UO) , configurable output (CO) , a relay output, and combinations thereof. Point types used by controller model numbers MS-IOM-1711, MS-IOM-2711, MS-IOM-3711, MS-IOM-4711, SM-16UI, SM-16DI, SM-8AO, and SM-8DO manufactured for Johnson Controls International can be used by modular edge controller 600. In some embodiments, the UI accepts an analog input, voltage mode 0-10 VDC signal, an analog input, current mode 4-20ma signal, an analog input, a resistance input (e.g., for Resistance Temperature Detector (RTD) ) , and a binary input, dry contact maintained mode signal. In some embodiments, the resistance input can be a 0-2 Kilo-Ohm signal or have any other range. In some embodiments, the BI accepts a pulse counter mode (high speed) , 100 Hz signal and a binary input, dry contact maintained mode signal. In some embodiments, the AO provides an analog output, voltage mode 0-10 VDC signal, and an analog output, current mode 4-20ma signal. In some embodiments, the BO provides a 24 VAC triac signal and / or a 24VDC relay signal. In some embodiments, the UO provides an analog output, voltage mode 0-10 VDC signal, an analog output, current mode 4-20ma signal, and a binary output mode, 24 V AC / DC FET signal. In some embodiments, the CO provides a 24 VAC triac signal. In some embodiments, the UO provides an analog output, voltage mode 0-10 VDC signal, and a binary output mode, 24 VAC triac signal and / or a 24VDC relay signal. In some embodiments, the relay output provides 120 / 240 VAC signal. Additional point types and combinations can also be utilized.
[0156] Advantageously, the architectural design of modular edge controller 600 allows customers to select only hardware components desired for a specific application without forcing customers to purchase hardware that is not necessary in some embodiments. Moreover, customers can remove any of modules 504A-D if desired. The modular design also allows customers to easily replace a failed component in the field instead of removing the component for servicing or purchasing an entirely new part in some embodiments. In some embodiments, a processor board might have inadequate millions of instructions per second (MIPS) or memory capability and could be replaced with a faster processor or one with more memory. The existing modules 504A-D and edge control module 602 can remain intact, potentially saving wiring and commissioning time and cost, in addition to saving cost associated with preserving the existing boards in the system.
[0157] Referring now to FIGS. 10-11, edge control module 602 is shown in isolation from modules 504A-D, according to an exemplary embodiment. Edge control module 602 may be configured for use as a module capable of providing and / or receiving an analog signal via a digital circuit 652. Digital circuit 652 may be configured to reduce excessive voltage loss on a transistor 660 (e.g., one or more MOSFETs or other transistors) associated with the analog signal. The reduction reduces high temperature rise of MOSFET / transistor 660, thereby reducing the internal temperature of modular edge controller 600 and edge control module 602 and reducing the cost of modular edge controller 600. Instead of using linear characteristics of the MOSFET / transistor 660, digital circuit 652 may use digital switching characteristics so that the MOSFET / transistor 660 operates like a power switch. In some embodiments, circuit 652 provides a pulse width modulated (PWM) signal to turn on / off the MOSFET / transistor 660.
[0158] Edge control module 602 may operate as a controller (e.g., an edge controller, a field controller, an equipment controller, etc. ) and can be customized to control a variety of different types of HVAC equipment. Edge control module 602 may monitor the status of certain variables or points reported by the equipment or associated sensors via the various data inputs to edge control module 602 (e.g., Ethernet ports 604, serial interface 606, terminal blocks 608, etc. ) and / or the inputs provided via any connected modules 504A-D (e.g., terminal blocks 510-516) . Edge control module 602 can be configured or customized to perform a variety of control operations (e.g., feedback control, PID control, feedforward control, extremum-seeking control, model predictive control, etc. ) by executing one or more control algorithms or control logic stored within edge control module 602.
[0159] In some embodiments, edge control module 602 can be configured to generate and provide a graphical user interface (GUI) for customizing the control algorithms or control logic executed by edge control module 602 (e.g., as a webpage or through a web server) . For example, the GUI provided by edge control module 602 may allow the user to drag-and-drop various functional blocks from a palette window (e.g., proportional gain blocks, integral blocks, derivative blocks, signal filter blocks, arithmetic blocks, etc. ) and connect the inputs / outputs of the functional blocks to apply a variety of calculations or other control logic to any inputs received by edge control module 602. Any inputs received by edge control module 602 via the physical communications interfaces can be connected to inputs to the functional blocks via the GUI (e.g., via an IO manager interface) and processed by edge control module 602 in accordance with the control logic defined by the functional blocks. The outputs of the functional blocks can be connected via the IO manager interface to any outputs of edge control module 602 and provided as analog or digital output signals via any of the communications interfaces of modular edge controller 600 as previously described. As an alternative to the graphical programming interface, edge control module 602 may support importing and exporting configuration data from a configuration file (e.g., spreadsheet, JSON file, etc. ) . In some embodiments, edge control module 602 includes a factory reset button to restore factory settings.
[0160] In some embodiments, edge control module 602 includes a large amount of internal memory (e.g., 8 GB, 16 GB, etc. ) to store or log values the various inputs received at edge control module 602 over time. In some embodiments, the memory used by edge control module 602 is embedded multi-media card (eMMC) flash memory, but can be other types of memory in various other embodiment (e.g., spinning disk, hard drive, solid state drive, M. 2 memory, etc. ) . The large internal data storage capabilities of edge control module 602 may allow edge control module 602 to function as a local or offline controller without requiring a connection to a network, server, or off-site system (e.g., cloud server, cloud controller, etc. ) . However, it is contemplated that edge control module 602 may communicate with other local or remote controllers in various embodiments (e.g., BMS controller 12, network 446, a cloud-based controller, a remote server, etc. ) and may include internal communications stacks or circuits capable of connecting directly to such local or remote controllers. In some embodiments, edge control module 602 uses a Message Queuing Telemetry Transport (MQTT) protocol to send and receive communications between edge control module 602 and another system or device (e.g., a cloud-based controller or server) .
[0161] Edge control module 602 may support BACnet / IP communication (e.g., via Ethernet ports 604 and / or serial interface 606) and may perform online discovery of BACnet / IP devices. In some embodiments, edge control module 602 can be configured or commissioned offline using EDE files to import device data points. Edge control module 602 may be configured with customizable alarm thresholds (e.g., high / low limits) with delay settings. In some embodiments, edge control module 602 can generate and provide a variety of enhanced chart types such as energy dashboards or trend graphs. Edge control module 602 can be configured to perform time-adjusted trends (e.g., year-over-year analysis) to analyze the various points, measurements, or other inputs received by edge control module 602 and facilitate a variety of fault detection, diagnostic, or other functions.
[0162] In some embodiments, edge control module 602 provides a variety of advantages over conventional controllers and / or IO modules. For example, conventional controllers may be oversized which increases control panel material costs. Conventional controllers may have serial port IO limitations which requires physical access to the controller to make parameter adjustments, which has the effect of slowing troubleshooting. Some conventional controllers or IO modules may have slow network recovery as a result of using STP ring network redundancy protocol with long recovery times (e.g., 30-50 seconds) . Conventional controllers or IO modules may not have sufficient electromagnetic interference (EMI) protection from industrial environments, which can corrupt data and cause unreliable communication. Some conventional controllers or IO modules may require multiple tools (e.g., CPT, EP, migration, IO manager, etc. ) to fully configure or use the device, causing reduced efficiency during commissioning or operation. Conventional controllers or IO modules may only support proprietary communications protocols, which limits interoperability and reduces system flexibility.
[0163] Edge control module 602 improves upon conventional controllers or IO modules in a variety of ways. For example, edge control module 602 may have a substantial physical footprint reduction (e.g., 75%) which results in space and cost savings in manufacturing panels. Edge control module 602 can be remotely configured or commissioned, which saves commissioning time and cost (e.g., around 4.7%reduction) . Edge control module 602 may use the rapid spanning tree (RSTP) protocol, which is enabled by having multiple redundant Ethernet ports 604, to reduce interruption time from 30-50 seconds to less than 1 second in the event of a communications failure or break in the communications path via one of Ethernet ports 604. Multiple Ethernet ports 604 also reduces communications failures and saves on maintenance cost (e.g., around 2.8%maintenance cost savings) . The unified tool integration used by edge control module 602 saves commissioning cost (e.g., around 2%commissioning cost savings) . In some embodiments, edge control module 602 uses an open communications protocol, which reduces vendor lock-in, lowers integration costs, improves expansion flexibility, and reduces maintenance expenses.
[0164] In some embodiments, edge control module 602 uses a new and high-performance low-cost SoC platform to support long term development and further enhancements. The power supply output from edge control module 602 may support both up to 10 local signal modules (e.g., modules 504A-D) . In some embodiments, edge control module 602 includes an additional 15V SA bus power supply output. Edge control module 602 may balance compact size and internal management to keep the existing form factor of communication system 500 as described above. Edge control module 602 may support RSTP for ring network topology and enable secure boot via Ethernet ports 604. Edge control module 602 may support MQTT as IO communication protocol via an IO manager configuration. Edge control module 602 may include a configuration tool that supports offline configuration of modules 504A-D for quick replacement at the field. Various other engineering tools or migration tools may be integrated into an IO manager tool used by edge control module 602 for a single common tool. Edge control module 602 may support a BACnet IP device channel, to allow and manage 3rd party BACnet IP devices’ connection and tags. Communication Module
[0165] Referring now to FIGS. 12-13, a communication system 700 is shown, according to an exemplary embodiment. Communication system 700 is shown to include many of the same components as communication system 500 described with reference to FIGS. 5-7. For example, communication system 700 is shown to include a number of modules 504A-D and an end cap 506 which may connect to each other using hook and groove interface 561 between each of modules 504A-D and end cap 506. Each of modules 504A-D may include indicators 518, latches 521 and respective terminal blocks 510, 512, 514, and 516. These components of communication system 700 may be the same as or similar to the like-numbered components of communication system 500, as described with reference to FIGS. 5-7.
[0166] Communication system 700 is shown to include communication module 702. Communication module 702 may include many of the same components and / or features as edge control module 602 described with reference to FIGS. 8-11, with the exception that communication module 702 may not include serial ports (e.g., serial interface 606) or internal control functionality in some embodiments. Communication module 702 can be connected to any number of modules 504A-D and may serve as a communications bridge between modules 504A-D and an IP network. For example, communication module 702 may be configured for use with modules 504A-D and can be attached to any number of modules 504A-D (i.e., zero or more) to form a customizable and modular communication system 700. In some embodiments, communication module 702 replaces module 502 in communication system 500 and can interface with modules 504A-D and / or end cap 506 in the same manner as module 502, as described with reference to FIGS. 5-7. For example, communication module 702 can interface with modules 504A-D and / or end cap 506 using a slidable connection such as hook and groove interface 561.
[0167] In some embodiments, communication module 702 and modules 504A-D are configured as smart modules including processing and communication circuits. Communication module 702 can be attached to one or more modules 504A-D or can be attached directly to end cap 506, for example if modules 504A-D are omitted. In some embodiments, communication module 702 has a housing that interfaces or integrates with the housings for modules 504A-D and / or end cap 506 when attached to each other so that a unified housing is provided for modular communication system 700. Communication module 702 and modules 504A-D may be self-encapsulated for environmental protection and safe handling in the field in some embodiments. The connections between modules 504A-D and communication module 702 can be keyed (e.g., disallowed in certain positions) and / or physically secured with additional hardware for a robust design.
[0168] Communication module 702 may include a processor, memory, and components for performing various communication and control operations, including wired communication operations. For example, communication module 702 is shown to include terminal blocks 708, which may be the same as or similar to terminal blocks 510-516 as described with reference to FIGS. 5-7. In some embodiments, terminal blocks 708 include mechanical connectors configured to fit into a power interface on the front face of communication module 702. Communication module 702 may use the RS-485 interfaces connected to terminal blocks 510-516 as a physical layer for communications protocols such as Modbus RTU, BACnet MS / TP, and / or other electronic data communications in BMS 11. For example, communication module 702 can use RS-485 to communicate with other controllers or modules in BMS 11 (e.g., other instances of communication system 700, instances of modular edge controller 600, other IO modules, etc. ) , various other devices, systems, and / or networks (e.g., sensors, actuators, or other building equipment in BMS 10) . Communication module 702 can also use Ethernet ports 704A and 704B for electronic data communications.
[0169] Communication module 702 is shown to include indicators 720 showing the status of various components of communication module 702 (e.g., communications or connections via the RS-485 interface, internal processing operations, etc. ) . Indicators 720 can be a liquid crystal display (LCD) , lamps, an LED (red, green and blue) or other lights. In various embodiments, indicators 720 may provide a user indication of device status, terminal position, fault status, I / O status (e.g., wiring fault, out-of-range input, active output, etc. ) or any other status indication. In some embodiments, indicators 720 include a microphone, speaker or a buzzer for audio communication. Indicators 720 and terminal block 708 can be specific to certain applications, interfaces or protocols. In some embodiments, communication module 702 communicates with terminal block 708 via connectors between communication module 702 and modules 504A-D (e.g., on main planar sides) . Power for modules 504A-D can be provided via terminal block 708 or main planar side connections.
[0170] In various embodiments, communication module 702 may include a microcontroller unit (MCU) , a system on a chip (SOC) , or generally any type of circuit such as an integrated circuit (IC) , an application-specific integrated circuit (ASIC) , a daughterboard, or a field-programmable gate array (FPGA) . Communication module 702 may be a larger device or may be a circuit or chip installed in or connected to a larger device. Further, communication module 702 may connect to existing devices such as a central processing unit (CPU) of a sensor or actuator or may replace processing circuits of existing devices.
[0171] Communication module 702 may include various hardware components and interfaces that may be provided with communication system 700. The components can include a wireless communications module, a wired communications module, a universal serial bus (USB) module, an RS-485 interface, a Bluetooth module, expandable input / output (I / O) points, and an expandable memory (e.g., SD-RAM) . For example, communication module 702 is shown to include two Ethernet ports 704A and 704B (collectively Ethernet ports 704) .
[0172] Ethernet ports 704 may support various types of TCP / IP communications such as BACnet / IP, Modbus TCP (e.g., function codes 01 / 02 / 03 / 04 / 05 / 06 / 15 / 16) , and MQTT communications. In some embodiments, communication module 702 uses a license file to activate or deactivate one or more of Ethernet ports 704. Other types of modular hardware components are possible and contemplated. Advantageously, Ethernet ports 704 allow communication module 702 and communication system 700 to integrate into a variety of different network topologies such as star, daisy chain, and ring topologies with RSTP redundancy protocols, as described in greater detail with reference to FIGS. 16-19. In some embodiments, communication system 700 can be attached to a DIN rail at an interface 719. Latches 521 and 721 can be used to selectively secure modules 504A-D and communication module 702 to the DIN rail at interface 719.
[0173] Generally, communication module 702 allows communication system 700 to be customized for a variety of different applications. Using fixed and / or modular hardware components, communication module 702 can communicate with edge and legacy devices, cloud applications, external memory, and a Wi-Fi transceiver, in various embodiments. In some embodiments, communication module 702 can be connected to many signal modules (e.g., modules 504A-D) and / or physical IO points via direct connection (e.g., via terminal blocks 510-516) . For example, an exemplary implementation of communication module 702 may include connecting communication module 702 to ten modules 504A-D and / or eighty physical IO points via direct connection. Communication module 702 may support a large number of physical IO points (e.g., 400 or more) via direct connection and / or expansion modules 504A-D. In some embodiments, communication module 702 can natively connect or can be expanded (e.g., via modules 504A-D) to connect to 31 slave devices for each port and may support monitoring and control activities for over 2,500 objects.
[0174] Communication module 702 and modules 504A-D can be configured for various point types including but not limited to a universal input (UI) , a binary input (BI) , an analog output (AO) , a binary output (BO) , a universal output (UO) , configurable output (CO) , a relay output, and combinations thereof. Point types used by controller model numbers MS-IOM-1711, MS-IOM-2711, MS-IOM-3711, MS-IOM-4711, SM-16UI, SM-16DI, SM-8AO, and SM-8DO manufactured for Johnson Controls International can be used by modular edge controller 600. In some embodiments, the UI accepts an analog input, voltage mode 0-10 VDC signal, an analog input, current mode 4-20ma signal, an analog input, a resistance input (e.g., for Resistance Temperature Detector (RTD) ) , and a binary input, dry contact maintained mode signal. In some embodiments, the resistance input can be a 0-2 Kilo-Ohm signal or have any other range. In some embodiments, the BI accepts a pulse counter mode (high speed) , 100 Hz signal and a binary input, dry contact maintained mode signal. In some embodiments, the AO provides an analog output, voltage mode 0-10 VDC signal, and an analog output, current mode 4-20ma signal. In some embodiments, the BO provides a 24 VAC triac signal and / or a 24VDC relay signal. In some embodiments, the UO provides an analog output, voltage mode 0-10 VDC signal, an analog output, current mode 4-20ma signal, and a binary output mode, 24 V AC / DC FET signal. In some embodiments, the CO provides a 24 VAC triac signal. In some embodiments, the UO provides an analog output, voltage mode 0-10 VDC signal, and a binary output mode, 24 VAC triac signal and / or a 24VDC relay signal. In some embodiments, the relay output provides 120 / 240 VAC signal. Additional point types and combinations can also be utilized.
[0175] Advantageously, the architectural design of communication system 700 allows customers to select only hardware components desired for a specific application without forcing customers to purchase hardware that is not necessary in some embodiments. Moreover, customers can remove any of modules 504A-D if desired. The modular design also allows customers to easily replace a failed component in the field instead of removing the component for servicing or purchasing an entirely new part in some embodiments. In some embodiments, a processor board might have inadequate millions of instructions per second (MIPS) or memory capability and could be replaced with a faster processor or one with more memory. The existing modules 504A-D and communication module 702 can remain intact, potentially saving wiring and commissioning time and cost, in addition to saving cost associated with preserving the existing boards in the system.
[0176] Referring now to FIGS. 14-15, communication module 702 is shown in isolation from modules 504A-D, according to an exemplary embodiment. Communication module 702 may be configured for use as a module capable of providing and / or receiving an analog signal via a digital circuit 752. Digital circuit 752 may be configured to reduce excessive voltage loss on a transistor 760 (e.g., one or more MOSFETs or other transistors) associated with the analog signal. The reduction reduces high temperature rise of MOSFET / transistor 760, thereby reducing the internal temperature of communication system 700 and communication module 702 and reducing the cost of modular communication system 700. Instead of using linear characteristics of the MOSFET / transistor 760, digital circuit 752 may use digital switching characteristics so that the MOSFET / transistor 760 operates like a power switch. In some embodiments, circuit 752 provides a pulse width modulated (PWM) signal to turn on / off the MOSFET / transistor 760.
[0177] In some embodiments, communication module 702 can be configured to generate and provide a graphical user interface (GUI) for customizing the configuration and IO connections of communication module 702 (e.g., as a webpage or through a web server) . For example, the GUI provided by communication module 702 may allow the user to drag-and-drop various blocks from a palette window (e.g., signal routing blocks, etc. ) and connect the inputs / outputs of the blocks to apply a variety of signal processing or routing to the inputs received by communication module 702. Any inputs received by communication module 702 via the physical communications interfaces can be connected to inputs to the blocks via the GUI (e.g., via an IO manager interface) and processed by communication module 702 in accordance with the logic defined by the blocks. The outputs of the blocks can be connected via the IO manager interface to any outputs of communication module 702 and provided as analog or digital output signals via any of the communications interfaces of communication system 700 as previously described. As an alternative to the graphical programming interface, communication module 702 may support importing and exporting configuration data from a configuration file (e.g., spreadsheet, JSON file, etc. ) . In some embodiments, communication module 702 includes a factory reset button to restore factory settings.
[0178] In some embodiments, communication module 702 includes a large amount of internal memory (e.g., 8 GB, 16 GB, etc. ) to store or log values the various inputs received at communication module 702 over time. In some embodiments, the memory used by communication module 702 is embedded multi-media card (eMMC) flash memory, but can be other types of memory in various other embodiment (e.g., spinning disk, hard drive, solid state drive, M. 2 memory, etc. ) . The large internal data storage capabilities of communication module 702 may allow communication module 702 to function as a local or offline data storage without requiring a connection to a network, server, or off-site system (e.g., cloud server, cloud controller, etc. ) . However, it is contemplated that communication module 702 may communicate with other local or remote controllers in various embodiments (e.g., BMS controller 12, network 446, a cloud-based controller, a remote server, etc. ) and may include internal communications stacks or circuits capable of connecting directly to such local or remote controllers. In some embodiments, communication module 702 uses a Message Queuing Telemetry Transport (MQTT) protocol to send and receive communications between communication module 702 and another system or device (e.g., a cloud-based controller or server) .
[0179] Communication module 702 may support BACnet / IP communication (e.g., via Ethernet ports 704 and) and may perform online discovery of BACnet / IP devices. In some embodiments, communication module 702 can be configured or commissioned offline using EDE files to import device data points. Communication module 702 may be configured with customizable alarm thresholds (e.g., high / low limits) with delay settings. In some embodiments, communication module 702 can generate and provide a variety of enhanced chart types such as energy dashboards or trend graphs. Communication module 702 can be configured to perform time-adjusted trends (e.g., year-over-year analysis) to analyze the various points, measurements, or other inputs received by communication module 702 and facilitate a variety of fault detection, diagnostic, or other functions.
[0180] In some embodiments, communication module 702 provides a variety of advantages over conventional controllers and / or IO modules. For example, conventional IO modules may be oversized which increases control panel material costs. Conventional IO modules may have serial port IO limitations which requires physical access to the controller to make parameter adjustments, which has the effect of slowing troubleshooting. Some conventional IO modules may have slow network recovery as a result of using STP ring network redundancy protocol with long recovery times (e.g., 30-50 seconds) . Conventional IO modules may not have sufficient electromagnetic interference (EMI) protection from industrial environments, which can corrupt data and cause unreliable communication. Some conventional IO modules may require multiple tools (e.g., CPT, EP, migration, IO manager, etc. ) to fully configure or use the device, causing reduced efficiency during commissioning or operation. Conventional IO modules may only support proprietary communications protocols, which limits interoperability and reduces system flexibility.
[0181] Communication module 702 improves upon conventional IO modules in a variety of ways. For example, communication module 702 may have a substantial physical footprint reduction (e.g., 75%) which results in space and cost savings in manufacturing panels. Communication module 702 can be remotely configured or commissioned, which saves commissioning time and cost (e.g., around 4.7%reduction) . Communication module 702 may use the rapid spanning tree (RSTP) protocol, which is enabled by having multiple redundant Ethernet ports 604, to reduce interruption time from 30-50 seconds to less than 1 second in the event of a communications failure or break in the communications path via one of Ethernet ports 604. Multiple Ethernet ports 704 also reduces communications failures and saves on maintenance cost (e.g., around 2.8%maintenance cost savings) . The unified tool integration used by communication module 702 saves commissioning cost (e.g., around 2%commissioning cost savings) . In some embodiments, communication module 702 uses an open communications protocol, which reduces vendor lock-in, lowers integration costs, improves expansion flexibility, and reduces maintenance expenses.
[0182] In some embodiments, the power supply output from communication module 702 may support both up to 10 local signal modules (e.g., modules 504A-D) . Communication module 702 may balance compact size and internal management to keep the existing form factor of communication system 500 as described above. Communication module 702 may support RSTP for ring network topology and enable secure boot via Ethernet ports 604. Communication module 702 may support MQTT as IO communication protocol via an IO manager configuration. Communication module 702 may include a configuration tool that supports offline configuration of modules 504A-D for quick replacement at the field. Communication module 702 may include a configuration tool that supports offline configuration of modules 504A-D for quick replacement at the field. Various other engineering tools or migration tools may be integrated into an IO manager tool used by communication module 702 for a single common tool. Communication module 702 may support a BACnet IP device channel, to allow and manage 3rd party BACnet IP devices’ connection and tags. Network Topologies
[0183] Referring now to FIGS. 16-19, several different network topologies which can be used with modular edge controller 600 and communication system 700 are shown, according to exemplary embodiments. Advantageously, modular edge controller 600 and communication system 700 can be configured to communicate over TCP / IP networks (e.g., BACnet IP, Modbus TCP, MQTT, etc. ) via Ethernet ports 604 and 704, as well as over serial networks (e.g., RS-485, BACnet MS / TP, Modbus RTU, etc. ) using serial interface 606 of modular edge controller 600 and terminal blocks 510-516, 608, and 708. In some embodiments, modular edge controller 600 and communication system 700 may operate as communications bridges between a TCP / IP network and a serial network as shown in several of FIGS. 16-19.
[0184] Referring particularly to FIG. 16, a network 800 having a star (or hub-and-spoke) topology is shown, according to an exemplary embodiment. In network 800, an Ethernet switch 802 serves as a central hub and each of modular edge controller 600 and communication system 700 are independently connected to Ethernet switch 802. Ethernet switch 802 may have any number of Ethernet ports 804, shown as port A 804A, port B 804B, …, port N 804N. Modular edge controller 600 may be connected to a first Ethernet port 804A of Ethernet switch 802 via a first Ethernet connection 818 extending between Ethernet port 604A and Ethernet port 804A. Communication system 700 may be connected to a second Ethernet port 804B of Ethernet switch 802 via a second Ethernet connection 819 extending between Ethernet port 704A and Ethernet port 804B. Ethernet connections 818-819 may use any of a variety of TCP / IP communications protocols such as BACnet IP, Modbus TCP, MQTT, etc.
[0185] Modular edge controller 600 may connect to a variety of edge devices or other serial devices via serial connection 822. For example, modular edge controller 600 is shown connected to VAV controller 806, IO module 808, electric meter 810, sensor 812, actuator 814, and water meter 816 via serial connection 817. Serial connection 817 can use any of a variety of serial communications protocols such as BACnet MS / TP, Modbus RTU, RS-485, etc. Serial connection 817 may connect to any serial interface of modular edge controller 600 including serial interface 606, terminal blocks 608, and / or terminal blocks 510-516. Although devices 806-816 are shown connected to only modular edge controller 600, it is contemplated that devices 806-816 may additionally or alternatively be connected to communication system 700 in some embodiments. Additionally, although only a few devices 806-816 are shown in FIG. 16 for ease of illustration, it is contemplated that each serial port of modular edge controller 600 and / or communication system 700 may support a large number of devices (e.g., up to 31 devices) .
[0186] Referring now to FIG. 17, a network 820 having a daisy chain topology is shown, according to an exemplary embodiment. In network 820, an Ethernet switch 802 is connected to an instance of modular edge controller 600 and multiple instances of communication system 700 in series via daisy chain connections 822, 824, and 826. Ethernet switch 802 may have any number of Ethernet ports 804, shown as port A 804A, port B 804B, …, port N 804N. Ethernet port 604A of modular edge controller 600 may be connected to port A 804A of Ethernet switch 802 via a first Ethernet connection 822. Ethernet port 604B of modular edge controller 600 may be connected to Ethernet port 704A of a first instance of communication system 700 via a second Ethernet connection 824. Ethernet port 704B of the first instance of communication system 700 may be connected to Ethernet port 704A of a second instance of communication system 700 via a third Ethernet connection 826. Ethernet connections 822-826 may use any of a variety of TCP / IP communications protocols such as BACnet IP, Modbus TCP, MQTT, etc.
[0187] Although simplified versions of modular edge controller 600 and communication system 700 are shown in FIG. 17 for ease of illustration, it should be understood that modular edge controller 600 and communication system 700 may include some or all of the components described with reference to FIGS. 8-15 when implemented in daisy chain network 820. For example, modular edge controller 600 may include edge control module 602 and zero or more of modules 504A-D. Similarly, communication system 700 may include communication module 702 and zero or more of modules 504A-D. Modular edge controller 600 and communication system 700 can be connected to any number of serial devices via serial interface 606, and terminal blocks 510-516, 608, and 708 when implemented in daisy chain network 820. Additionally, it is contemplated that modular edge controller 600 and communication system 700 are interchangeable with each other in daisy chain network 820 because both have multiple Ethernet ports 604 and 704 to support daisy chain communications. The positions of modular edge controller 600 and communication system 700 can be swapped with each other in some embodiments. Additionally, any of modular edge controller 600 or communication system 700 can be swapped with the other and / or with other types of IP networking devices having multiple Ethernet ports (e.g., Ethernet switches, routers, etc. ) in daisy chain network 820.
[0188] Referring now to FIG. 18, a network 840 having a ring topology is shown, according to an exemplary embodiment. The topology of ring network 840 is substantially the same as the topology of daisy chain network 820, with the exception that an additional Ethernet connection 848 exists between the second instance of communication system 700 and Ethernet switch 802 to close the ring. In network 840, Ethernet switch 802 is connected to an instance of modular edge controller 600 and multiple instances of communication system 700 in a closed loop via Ethernet connections 842, 844, 846, and 848. Ethernet switch 802 may have any number of Ethernet ports 804, shown as port A 804A, port B 804B, …, port N 804N. Ethernet port 604A of modular edge controller 600 may be connected to port A 804A of Ethernet switch 802 via a first Ethernet connection 842. Ethernet port 604B of modular edge controller 600 may be connected to Ethernet port 704A of a first instance of communication system 700 via a second Ethernet connection 844. Ethernet port 704B of the first instance of communication system 700 may be connected to Ethernet port 704A of a second instance of communication system 700 via a third Ethernet connection 846. Ethernet port 704B of the second instance of communication system 700 may be connected to Ethernet port 804N of Ethernet switch 802 via a fourth Ethernet connection 848. Ethernet connections 842-848 may use any of a variety of TCP / IP communications protocols such as BACnet IP, Modbus TCP, MQTT, etc.
[0189] Although simplified versions of modular edge controller 600 and communication system 700 are shown in FIG. 18 for ease of illustration, it should be understood that modular edge controller 600 and communication system 700 may include some or all of the components described with reference to FIGS. 8-15 when implemented in ring network 840. For example, modular edge controller 600 may include edge control module 602 and zero or more of modules 504A-D. Similarly, communication system 700 may include communication module 702 and zero or more of modules 504A-D. Modular edge controller 600 and communication system 700 can be connected to any number of serial devices via serial interface 606, and terminal blocks 510-516, 608, and 708 when implemented in ring network 840. Additionally, it is contemplated that modular edge controller 600 and communication system 700 are interchangeable with each other in ring network 840because both have multiple Ethernet ports 604 and 704 to support ring communications. The positions of modular edge controller 600 and communication system 700 can be swapped with each other in some embodiments. Additionally, any of modular edge controller 600 or communication system 700 can be swapped with the other and / or with other types of IP networking devices having multiple Ethernet ports (e.g., Ethernet switches, routers, etc. ) in ring network 840.
[0190] Referring now to FIG. 19, a network 860 having a mixed topology is shown, according to an exemplary embodiment. Network 860 includes several different sections which can be implemented using a variety of different network topologies. For example, mixed network 860 is shown to include an IP ring 862 that includes a set of IP-enabled devices (i.e., modular edge controller 600, Ethernet switch 875, Wi-Fi access point 876, and communication system 700) arranged in a ring topology, similar to ring network 840 in FIG. 18. The label “Communication System (ETH) ” in FIG. 19 refers to communication system 700 and is intended to distinguish “Communication System (RS-485) ” which represents communication system 500. Each of the devices in IP ring 862 may be connected via Ethernet connections as indicated by the solid line connections between devices in FIG. 19. In some embodiments, Wi-Fi access point 876 bridges IP ring 862 with a Wi-Fi network 869 to enable wireless communications between Wi-Fi access point 876 and various wireless BMS devices such as wireless sensor 877 and wireless controller 878. Although not shown in FIG. 19, it is contemplated that any of Ethernet switch 875, modular edge controller 600, and / or communication system 700 in IP ring 862 can be connected to any number of additional devices (e.g., meters, controllers, actuators, etc. ) as shown for other instances of modular edge controller 600 and communication system 700 in FIG. 19.
[0191] Mixed network 860 is also shown to include an IP daisy chain 864, which may be the same as or similar to daisy chain network 820 shown in FIG. 17. IP daisy chain is shown to include several instances of modular edge controller 600 and an instance of communication system 700 arranged in series via daisy chain connections. The daisy chain connections between modular edge controllers 600 and communication system 700 in IP daisy chain 864 may be Ethernet connections. In various embodiments, any of modular edge controller 600 and / or communication system 700 in IP daisy chain 864 may be connected to serial devices via serial connections (e.g., RS-485 connections) as indicated by the dashed connection lines in FIG. 19. For example, one instance of modular edge controller 600 is shown connected to a set of meters 880, whereas another instance of modular edge controller 600 is shown connected to a VAV controller 881. The instance of communication system 700 in IP daisy chain 864 is shown connected to an IO module 879.
[0192] Mixed network 860 is also shown to include another IP daisy chain 866 including several instances of modular edge controller 600 and communication system 700 connected via daisy chained Ethernet connections, as indicated by the solid line connections in IP daisy chain 866. One or more of modular edge controller 600 and / or communication system 700 in IP daisy chain 866 may also be connected to various serial devices via the serial communication interfaces of modular edge controller 600 and communication system 700 (e.g., serial interface 606, terminal blocks 608, 708, 510-516) . For example, one instance of modular edge controller 600 in IP daisy chain 866 is shown connected to multiple instances of communication system 500 via RS-485 connections in a serial branch 868. One or more of communication system 500 may be connected to additional serial devices such as an actuator 882, meters 883, or any other serial connected devices.
[0193] Although only a few examples of different types of connections that can be made between modular edge controller 600, communication system 700, and communication system 500 are shown in FIG. 19, it is contemplated that any combination of connections can be made using the Ethernet ports 604 and 704, serial interface 606, and terminal blocks 608, 708, and 510-516. Any Ethernet connections in mixed network 860 can use any of a variety of TCP / IP communications protocols such as BACnet IP, Modbus TCP, MQTT, etc. Any serial connections in mixed network 860 can use any of a variety of serial communications protocols such as RS-485, BACnet MS / TP, Modbus RTU, etc. It is contemplated that many different network topologies can be constructed using these and other types of connections enabled by the Ethernet ports 604 and 704 of modular edge controller 600 and communication system 700 respectively, as well as serial connections via serial interface 606 and terminal blocks 608, 708, and 510-516. Configuration of Exemplary Embodiments
[0194] The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, 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. ) . For example, the position of elements can be reversed or otherwise varied and the nature or number of discrete elements or positions can 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 can be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions can be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.
[0195] The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure can be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. 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. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, 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.
[0196] Although the figures show a specific order of method steps, the order of the steps may differ from what is depicted. Also, two or more steps can be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.
Claims
1.A modular edge controller in a building system, the modular edge controller comprising:an edge control module comprising a first housing and a first circuit contained within the first housing, the first housing comprising a plurality of Ethernet ports connected to the first circuit; andone or more input / output (I / O) modules each comprising a second housing and a second circuit contained within the second housing, the second housing comprising one or more terminal blocks connected to the second circuit;wherein the first housing and the second housing are configured to detachably connect to each other and the first circuit and the second circuit are configured to communicate with each other when the first housing and the second housing are connected.2.The modular edge controller of Claim 1, wherein:the edge control module is configured to communicate using TCP / IP communications via the plurality of Ethernet ports; andthe one or more I / O modules are configured to communicate using serial communications via the one or more terminal blocks.3.The modular edge controller of Claim 1, wherein:the edge control module is configured to communicate using at least one of BACnet IP, Modbus TCT, or a message queuing telemetry transport (MQTT) protocol via the plurality of Ethernet ports; andthe one or more I / O modules are configured to communicate via at least one of BACnet MS / TP or Modbus RTU via the one or more terminal blocks.4.The modular edge controller of Claim 1, wherein the edge control module comprises one or more memory devices having at least 8 GB of storage capacity within the first housing.5.The modular edge controller of Claim 1, wherein the edge control module is configured to communicate with a cloud system using a message queuing telemetry transport (MQTT) protocol via one or more of the plurality of Ethernet ports.6.The modular edge controller of Claim 1, wherein the edge control module is configured to form part of a TCP / IP communications network having at least one of a star topology, a daisy chain topology, or a ring topology.7.The modular edge controller of Claim 1, wherein the first housing comprises a serial communications interface connected to the first circuit and configured to communicate using serial communications.8.The modular edge controller of Claim 1, wherein the first circuit is configured to:receive one or more input signals from building equipment of the building via one or more of the Ethernet ports or the one or more terminal blocks;generate a control signal by processing the one or more input signals using control logic stored on the first circuit; andtransmit the control signal to the building equipment or other building equipment via one or more of the Ethernet ports or the one or more terminal blocks.9.The modular edge controller of Claim 1, wherein the first circuit is configured to use a rapid spanning tree (RSTP) protocol to prevent switching loops while allowing redundant physical communication paths between the edge control module and one or more external systems or devices via the plurality of Ethernet ports.10.The modular edge controller of Claim 1, wherein the first circuit is configured to recover from a communication failure via one of the plurality of Ethernet ports in less than one second by rerouting communications to another of the plurality of Ethernet ports.11.A communication system in a building system, the communication system comprising:a communication module comprising a first housing and a first circuit contained within the first housing, the first housing comprising a plurality of Ethernet ports connected to the first circuit; andone or more input / output (I / O) modules each comprising a second housing and a second circuit contained within the second housing, the second housing comprising one or more terminal blocks connected to the second circuit;wherein the first housing and the second housing are configured to detachably connect to each other and the first circuit and the second circuit are configured to communicate with each other when the first housing and the second housing are connected.12.The communication system of Claim 11, wherein:the communication module is configured to communicate using TCP / IP communications via the plurality of Ethernet ports; andthe one or more I / O modules are configured to communicate using serial communications via the one or more terminal blocks.13.The communication system of Claim 11, wherein:the communication module is configured to communicate using at least one of BACnet IP, Modbus TCT, or a message queuing telemetry transport (MQTT) protocol via the plurality of Ethernet ports; andthe one or more I / O modules are configured to communicate via at least one of BACnet MS / TP or Modbus RTU via the one or more terminal blocks.14.The communication system of Claim 11, wherein the communication module is configured to communicate with a cloud system using a message queuing telemetry transport (MQTT) protocol via one or more of the plurality of Ethernet ports.15.The communication system of Claim 11, wherein the communication module is configured to form part of a TCP / IP communications network having at least one of a star topology, a daisy chain topology, or a ring topology.16.The communication system of Claim 11, wherein the first housing comprises a serial communications interface connected to the first circuit and configured to communicate using serial communications.17.The communication system of Claim 11, wherein the first circuit is configured to use a rapid spanning tree (RSTP) protocol to prevent switching loops while allowing redundant physical communication paths between the communication module and one or more external systems or devices via the plurality of Ethernet ports.18.The communication module of Claim 11, wherein the first circuit is configured to recover from a communication failure via one of the plurality of Ethernet ports in less than one second by rerouting communications to another of the plurality of Ethernet ports.19.A method for communicating using a modular edge controller in a building system, the method comprising;detachably connecting a first housing of an edge control module to a second housing of an input / output (I / O) module to form the modular edge controller;transmitting or receiving a first communication between the edge control module and one or more other systems or devices using TCP / IP communications via one or more of a plurality of Ethernet ports in the first housing of the edge control module;transmitting or receiving a second communication between the I / O module and one or more external systems or devices using serial communications via the one or more terminal blocks in the second housing of the I / O module; andtransmitting or receiving a third communication between the edge control module and the I / O module when the first housing and the second housing are detachably connected.20.The method of Claim 19, wherein:the first communication is transmitted or received using at least one of BACnet IP, Modbus TCT, or a message queuing telemetry transport (MQTT) protocol via one or more of the plurality of Ethernet ports; andthe second communication is transmitted or received using at least one of BACnet MS / TP or Modbus RTU via the one or more terminal blocks.
