BUILDING MANAGEMENT SYSTEM WITH DIGITAL MODULES FOR SENSORS AND CONTROLLED DEVICES

Description

CROSS-REFERENCE TO RELATED PATENT APPLICATION

This patent application claims the benefit of and priority to U.S. Provisional Ser. No. 63/686,553 filed Aug. 23, 2024, the entire disclosure of which is incorporated by reference herein.

BACKGROUND

The present disclosure relates generally to building management systems. The present disclosure relates more particularly to a controls architecture for communications between controllers, sensors, and controlled devices in a building management system.

A building management system (BMS) is, in general, a system of devices configured to control, monitor, and manage equipment in or around a building or building area. A BMS can include a heating, ventilation, or air conditioning (HVAC) system, a security system, a lighting system, a fire alerting system, another system that is capable of managing building functions or devices, or any combination thereof. BMS devices may be installed in any environment (e.g., an indoor area or an outdoor area) and the environment may include any number of buildings, spaces, zones, rooms, or areas. A BMS may include METASYS® building controllers or other devices sold by Johnson Controls, Inc., as well as building devices and components from other sources.

A BMS may include one or more computer systems (e.g., servers, BMS controllers, etc.) that serve as enterprise level controllers, application or data servers, head nodes, master controllers, or field controllers for the BMS. Such computer systems may communicate with multiple downstream building systems or subsystems (e.g., an HVAC system, a security system, etc.) according to like or disparate protocols (e.g., LON, BACnet, etc.). The computer systems may also provide one or more human-machine interfaces or client interfaces (e.g., graphical user interfaces, reporting interfaces, text-based computer interfaces, client-facing web services, web servers that provide pages to web clients, etc.) for controlling, viewing, or otherwise interacting with the BMS, its subsystems, and devices.

SUMMARY

One implementation of the present disclosure is a system for monitoring and controlling building equipment. The system includes a plurality of devices of building equipment configured to be installed in a local operating environment and operable within the local operating environment to affect or measure one or more variable states or conditions of a building, a controller configured to send and receive digital messages for communicating with the building equipment, and a plurality of digital modules configured to be installed in the local operating environment of the building equipment and physically attached to the plurality of devices of the building equipment within the local operating environment. Each digital module of the plurality of digital modules includes a digital communications interface configured to communicate with the controller using the digital messages, an analog communications interface configured to communicate with one or more devices of the plurality of devices of the building equipment using analog signals, and a signal converter configured to convert between the digital messages and the analog signals. The system further includes a communications link physically connecting the controller to the digital communications interface of each of the plurality of digital modules and configured to transmit the digital messages between the controller and the plurality of digital modules.

In some embodiments, the communications link includes a multi-conductor cable having a first conductor configured to transmit the digital messages between the controller and the plurality of digital modules and a second conductor configured to supply power from the controller to the plurality of digital modules.

In some embodiments, each digital module includes a power converter configured to receive power from the communications link at an input voltage, convert the power into an output voltage different from the input voltage, and output the power at the supply voltage to the one or more devices of the building equipment with which the digital module communicates via the analog communications interface.

In some embodiments, the plurality of devices of the building equipment include a sensor configured to measure a variable state or condition and output an analog signal indicating a value of the variable state or condition. In some embodiments, the plurality of digital modules include an input digital module physically attached to the sensor and configured to generate a digital message comprising the value of the variable state or condition based on the analog signal and transmit the digital message to the controller via the communications link.

In some embodiments, the input digital module is configured to generate a sender address of the digital message identifying the sensor or the input digital module as a sender of the digital message, generate a recipient address of the digital message identifying the controller as a recipient of the digital message, and generate a payload of the digital message comprising the value of the variable state or condition measured by the sensor.

In some embodiments, the plurality of devices of the building equipment include a controlled device configured to receive an analog signal and operable to affect a variable state or condition based on a value of the analog signal. In some embodiments, the plurality of digital modules include an output digital module physically attached to the controlled device and configured to generate the analog signal based on a digital message received from the controller via the communications link and transmit the analog signal to the controlled device.

In some embodiments, the output digital module is configured to monitor the digital messages transmitted via the communications link for a digital message addressed to the output digital module or the controlled device, process a payload of the digital message addressed to the output digital module or the controlled device to determine a value of a control signal for the controlled device, and generate the analog signal for the controlled device based on the value of the control signal indicated by the digital message.

In some embodiments, one or more of the plurality of digital modules is a physical device comprising a processing circuit having a processor and memory, the analog communications interface and the digital communications interface are physical interfaces of the physical device, and the analog communications interface is physically coupled to the one or more devices of the plurality of devices of the building equipment with which the physical device communicates using the analog signals.

In some embodiments, one or more of the plurality of digital modules is a virtual device running on hardware of a device of the building equipment with which the virtual device communicates using the analog signals, the digital communications interface is a physical interface of the device of building equipment, and the analog communications interface is a virtual communications interface within the device of the building equipment.

In some embodiments, the communications link physically connects the controller to each of the plurality of digital modules in a single chain or loop.

Another implementation of the present disclosure is a method for monitoring and controlling building equipment. The method includes sending a digital message from a controller via a communications link physically connecting the controller to a plurality of digital modules and receiving the digital message at a digital communications interface of an output digital module of the plurality of digital modules. The output digital module may be installed in a local operating of a controlled device and physically attached to the controlled device within the local operating environment. The method includes converting the digital message into an analog signal at the output digital module, transmitting the analog signal from the output digital module to the controlled device within the local operating environment of the controlled device, and operating the controlled device within the local operating environment to affect a variable state or condition based on a value of the analog signal.

In some embodiments, the method includes determining a recipient of the digital message based on a recipient address of the digital message received at the digital communications interface of the output digital module via the communications link. In some embodiments, the digital message is converted into the analog signal by the output digital module and the analog signal is transmitted from the output digital module to the controlled device in response to determining that the recipient of the digital message is the output digital module or the controlled device. In some embodiments, the digital message is ignored by the output digital module in response to determining that the recipient of the digital message is not the output digital module or the controlled device.

In some embodiments, the output digital module is a physical device including a processing circuit having a processor and memory, the analog communications interface and the digital communications interface of the output digital module are physical interfaces of the physical device, and the analog communications interface of the output digital module is physically coupled to the controlled device.

In some embodiments, the output digital module is a virtual device running on hardware of the controlled device, the digital communications interface of the output digital module is a physical interface of the controlled device, and the analog communications interface of the output digital module is a virtual communications interface within the controlled device.

In some embodiments, the communications link includes a multi-conductor cable. The method may include sending the digital message from the controller to the plurality of digital modules via a first conductor of the multi-conductor cable and supplying power from the controller to the plurality of digital modules via a second conductor of the multi-conductor cable.

Another implementation of the present disclosure is a method for monitoring and controlling building equipment. The method includes receiving an analog signal indicating a value of a variable state or condition measured by a sensor at an analog communications interface of an input digital module physically attached to the sensor. Both the sensor and the input digital module may be installed within a local operating environment of the sensor. The method further includes converting the analog signal into a digital message comprising a value of the variable state or condition measured by the sensor at the input digital module within the local operating environment of the sensor, and transmitting the digital message via a communications link connecting a digital communications interface of the input digital module with a controller and with a plurality of digital modules configured to communicate via the communications link.

In some embodiments, the method includes generating a sender address of the digital message identifying the sensor or the input digital module as a sender of the digital message, generating a recipient address of the digital message identifying the controller as a recipient of the digital message, and generating a payload of the digital message comprising the value of the variable state or condition measured by the sensor.

In some embodiments, the input digital module is a physical device including a processing circuit having a processor and memory, the analog communications interface and the digital communications interface of the input digital module are physical interfaces of the physical device, and the analog communications interface of the input digital module is physically coupled to the sensor.

In some embodiments, the input digital module is a virtual device running on hardware of the sensor, the digital communications interface of the input digital module is a physical interface of the sensor, and the analog communications interface of the input digital module is a virtual communications interface within the sensor.

In some embodiments, the communications link comprises a multi-conductor cable. The method may include transmitting the digital message from the input digital module via a first conductor of the multi-conductor cable and supplying power from the controller to the plurality of digital modules via a second conductor of the multi-conductor cable.

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects, aspects, features, and advantages of the disclosure will become more apparent and better understood by referring to the detailed description taken in conjunction with the accompanying drawings, in which like reference characters identify corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements.

FIG. 1 is a drawing of a building equipped with a building management system (BMS), according to some embodiments.

FIG. 2 is a block diagram of a BMS that serves the building of FIG. 1, according to some embodiments.

FIG. 3 is a block diagram of a BMS controller which can be used in the BMS of FIG. 2, according to some embodiments.

FIG. 4 is another block diagram of the BMS that serves the building of FIG. 1, according to some embodiments.

FIG. 5A is a block diagram of an airside system illustrating a conventional wiring layout in which a controller is connected with sensors and controlled devices using many independent wires, according to some embodiments.

FIG. 5B is another block diagram of the airside system of FIG. 5A illustrating another conventional wiring layout in which the controller is connected with sensors and controlled devices using many independent wires, according to some embodiments.

FIG. 6A is a block diagram of another airside system illustrating an improved wiring layout in which a controller is connected with sensors and controlled devices using a single communications link and digital modules, according to some embodiments.

FIG. 6B is another block diagram of the airside system of FIG. 6A illustrating an improved wiring layout in which the controller is connected with sensors and controlled devices using a single communications link and digital modules, according to some embodiments.

FIG. 7A is a block diagram of a variable air volume (VAV) system in which each VAV unit is connected to a separate VAV controller using a set of wires, according to some embodiments.

FIG. 7B is a block diagram illustrating an improved wiring configuration in the VAV system of FIG. 7A in which a single communications link is used to connect a VAV controller with digital modules, according to some embodiments.

FIG. 8A is a block diagram of a system in which a digital module of FIGS. 6A-6B or 7B is implemented as a physical device and connected to multiple sensors, according to some embodiments.

FIG. 8B is a block diagram of a system in which a digital module of FIGS. 6A-6B or 7B is implemented as a virtual device integrated into building equipment, according to some embodiments.

FIG. 9 is a block diagram of a system in which various digital modules of FIGS. 6A-6B or 7B facilitate communications between equipment and controllers, according to some embodiments.

FIG. 10 is a block diagram of a system in which an input digital module of FIGS. 6A-6B or 7B communicates with a sensor, according to some embodiments.

FIG. 11 is a block diagram of a system in which an output digital module of FIG. 6 communicates with a controlled device, according to some embodiments.

FIG. 12 is a flowchart of a process for monitoring and controlling building equipment using the digital modules of FIGS. 6A-6B or 7B to communicate with controlled devices, according to some embodiments.

FIG. 13 is a flowchart of a process for monitoring and controlling building equipment using the digital modules of FIGS. 6A-6B or 7B to communicate with sensors, according to some embodiments.

DETAILED DESCRIPTION

Overview

Referring generally to the FIGURES, systems and methods for using digital modules to communicate with sensors and controlled devices of building equipment are shown, according to various exemplary embodiments. In a conventional building system, various devices of building equipment communicate with a controller using a set of wires. During installation, each wire in the set of wires must be individually connected to corresponding terminal on the controller or an expansion module coupled to the controller and run to one of the sensors or controlled devices in the system. This approach of using a numerous wires to connect the controller with the sensors and controlled devices has several disadvantages.

For example, some equipment or subsystems of the building system may require a large number of wires (e.g., between forty and sixty wires in a single air handling unit (AHU)) which need to be connected between the controller and the various sensors or controlled devices, which may lead to wiring errors and time wasted fixing those errors. Additionally, the controller may have fixed input/output (I/O) counts and combinations of inputs and outputs. For example, a conventional AHU controller may have nine inputs and nine outputs, some of which may be dedicated binary outputs, analog outputs, or configurable outputs. Each input and output of the AHU controller may require a dedicated terminal on the housing of AHU controller for the corresponding wire to be connected.

When the specific I/O requirements of a set of building equipment exceed the I/O counts of the controller, expansion modules are typically added to the controller and used to make up the difference. An expansion module may include additional I/O terminals to connect additional wires beyond the number of wires supported by the controller. However, conventional expansion modules have fixed I/O counts as well (i.e., a fixed number of I/O terminals) and must be selected to have at least the minimum number of I/O terminals required by the sensors and controlled devices. Due to the rigid controller and expansion module I/O counts, the control solution often has many unused inputs/outputs. For example, wiring a single AHU may require multiple products (e.g., an AHU controller, a first expansion module, a second expansion module, etc.) to accommodate all of the required inputs and outputs. However, these products often lead to many unused input, output, and UI terminals or connections.

The systems and methods described herein provide several significant improvements relative to conventional systems. Most notably, the numerous wires in conventional systems have been replaced with a single digital communications link connecting the controller to the various sensors monitored by the controller and the controlled devices operated by the controller. Rather than exchanging analog signals as in conventional systems, the messages sent to the controller and from the controller via the communications link may be digital. For example, the communications link can be implemented as a digital communications bus or digital controls bus using any of a variety of digital communications protocols (e.g., Ethernet, TCP/IP, etc.) which allows the controller to communicate with multiple components of the building equipment using the same physical connection. The messages exchanged by the controller and other components connected to the communications link can be formatted as digital messages having addresses (e.g., sender address, receiver address, etc.) and routed to the desired recipient using any of a variety of digital networking techniques.

Advantageously, the use of a single digital communications link instead of many individual wires allows the controller to communicate with all of the sensors and controllable devices of the building system or subsystem via a single connection (e.g., a daisy chain or single communications bus). This change eliminates the need for a controller with multiple expansion modules because a single controller is utilized. Additionally, the controller does not require any I/O on board except for communications. Complex wiring is eliminated and the risk of wiring error is significantly reduced. A single communications link may extend from the controller and connect to each of the sensors and/or controllable devices in the system, either directly or digital modules.

Another significant advantage of the systems and methods described herein is the use of digital modules to monitor and control building equipment. Digital modules may be connected to the communications link and can serve as intermediaries between the digital and analog components of the building system. Digital modules allow various components of the building system to remain as conventional analog components (e.g., analog sensors, binary on/off switches, equipment that receives analog control signals, etc.) while enabling digital communications with the controller via the digital communications link. The digital modules can be implemented as physical devices (e.g., separate devices coupled to the sensors or controlled devices via a cable) or as virtual devices (e.g., running on hardware of the sensors or controlled devices) in various embodiments. These and other features and advantages of the present disclosure are described in detail below.

Building and Building Management System

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.).

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.

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.

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).

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.

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.

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.).

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.

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.

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.

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.).

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.

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.).

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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. Ser. No. 12/887,390, filed Sep. 21, 2010, for creating software defined building objects.

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.

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.

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.

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.

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.).

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.

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.

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.

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.

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.

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.

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.).

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.

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.

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).

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.

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.

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.

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.

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.).

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.

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.

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.).

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.

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.

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.

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.).

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.

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.

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.

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.

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.).

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.

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.

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.

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).

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.

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.

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.

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.

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.

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.).

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.).

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.

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.

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.

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.

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.

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.

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.

Digital Modules for Sensors and Controlled Devices

Referring now to FIGS. 5A-6B, block diagrams of two airside systems 500 and 600 are shown, according to exemplary embodiments. Airside system 500 shown in FIGS. 5A-5B is an example of a conventional HVAC system in which equipment of an air handling unit (AHU) (e.g., dampers, fans, actuators, sensors, etc.) communicate with an AHU controller 530 using a set of wires 502. In some installations, AHU controller 530 may be located remotely from the other components of airside system 500 (e.g., in a different room, building zone, etc.) or hanging on a wall nearby the other components of airside system 500. In either case, AHU controller 530 may be connected to the other components of airside system 500 via many wires in the set of wires 502. During installation, each wire in the set of wires 502 must be individually connected to corresponding terminal on AHU controller 530 (or an expansion module coupled to AHU controller 530) and run to one of the sensors or controlled devices in the AHU. Airside system 600 shown in FIGS. 6A-6B is an example of an improved HVAC system in which the AHU equipment communicate with AHU controller 630 via a single digital communications link 602. Communications link 602 may be daisy chained (e.g., connect to each of the AHU equipment in series) or structured as a digital communications bus to which each of the AHU equipment are connected in parallel. Advantageously, airside system 600 greatly simplifies the installation and wiring of the sensors and controlled devices relative to airside system 500 using digital modules 604 and other improvements described in detail below.

It is noted that although airside systems 500 and 600 are provided as examples of HVAC systems to illustrate the improvements provided by digital modules 604, it should be understood that this particular use case is only one potential implementation of the present disclosure and should not be regarded as limiting. It is contemplated that digital modules 604 and the improvements provided thereby can be used in any type of HVAC system (e.g., airside systems, waterside systems, variable refrigerant flow (VRF) systems, thermally activated building systems (TABS), etc.) or any other type of building system or subsystem (e.g., building electrical subsystem 434, ICT subsystem 436, security subsystem 438, HVAC subsystem 440, lighting subsystem 442, lift/escalators subsystem 432, fire safety subsystem 430, etc.). It is also contemplated that the teachings of the present disclosure can be applied to other types of systems or equipment regardless of whether such systems or equipment are implemented in the context of a building. While the following description refers primarily to airside systems 500 and 600 for ease of explanation, it should be understood that these are only one example of many potential use cases or implementations of the systems and methods described herein.

Referring again to FIGS. 5A-5B, an airside system 500 is shown, according to an exemplary embodiment. Airside system 500 may operate to heat or cool an airflow provided to building 10 using a heated or chilled fluid provided by a waterside system (e.g., one or more chillers, boilers, hot water generators, cooling towers, a central plant, a waterside plant, a chiller plant, etc.). Airside system 500 is shown to include an economizer-type air handling unit (AHU) 501 and an AHU controller 530. Economizer-type AHUs vary the amount of outside air and return air used by the air handling unit for heating or cooling. For example, AHU 501 may receive return air 504 from building zone 506 via return air duct 508 and may deliver supply air 510 to building zone 506 via supply air duct 512. In some embodiments, AHU 501 is a rooftop unit located on the roof of building 10 or otherwise positioned to receive both return air 504 and outside air 514. AHU 501 can be configured to operate exhaust air damper 516, mixing damper 518, and outside air damper 520 to control an amount of outside air 514 and return air 504 that combine to form supply air 510. Any return air 504 that does not pass through mixing damper 518 can be exhausted from AHU 501 through exhaust air damper 516 as exhaust air 522.

Each of dampers 516-520 can be operated by an actuator. For example, exhaust air damper 516 can be operated by actuator 524, mixing damper 518 can be operated by actuator 526, and outside air damper 520 can be operated by actuator 528. Actuators 524-528 may communicate with an AHU controller 530 via a set of wires 502. Actuators 524-528 may receive control signals from AHU controller 530 and may provide feedback signals to AHU controller 530 via wires 502. Feedback signals can include, for example, an indication of a current actuator or damper position, an amount of torque or force exerted by the actuator, diagnostic information (e.g., results of diagnostic tests performed by actuators 524-528), status information, commissioning information, configuration settings, calibration data, and/or other types of information or data that can be collected, stored, or used by actuators 524-528. AHU controller 530 can be an economizer controller configured to use one or more control algorithms (e.g., state-based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control actuators 524-528.

AHU 501 is shown to include a preheat coil 572, a cooling coil 534, a heating coil 536, and a supply fan 538 positioned within supply air duct 512. Supply fan 538 can be configured to force supply air 510 through preheat coil 572, cooling coil 534 and/or heating coil 536 and provide supply air 510 to building zone 506. AHU controller 530 may communicate with supply fan 538 via wires 502 to control a flow rate of supply air 510. In some embodiments, AHU controller 530 controls an amount of heating or cooling applied to supply air 510 by modulating a speed of supply fan 538.

Cooling coil 534 may receive a chilled fluid from a waterside system (via piping 542 and may return the chilled fluid to the waterside system via piping 544. Valve 546 can be positioned along piping 542 or piping 544 to control a flow rate of the chilled fluid through cooling coil 534. In some embodiments, cooling coil 534 includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., by AHU controller 530) to modulate an amount of cooling applied to supply air 510.

Heating coil 536 may receive a heated fluid from the waterside system via piping 548 and may return the heated fluid to the waterside system via piping 550. Valve 552 can be positioned along piping 548 or piping 550 to control a flow rate of the heated fluid through heating coil 536. In some embodiments, heating coil 536 includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller 530) to modulate an amount of heating applied to supply air 510.

Similarly, preheat coil 572 may receive a heated fluid from the waterside system via piping 578 and may return the heated fluid to the waterside system via piping 560. Valve 576 can be positioned along piping 578 or piping 560 to control a flow rate of the heated fluid through preheat coil 572. In some embodiments, preheat coil 572 includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller 530) to modulate an amount of heating applied to supply air 510.

Each of valves 546, 552, and 576 can be controlled by an actuator. For example, valve 546 can be controlled by actuator 554, valve 552 can be controlled by actuator 556, and valve 576 can be controlled by actuator 574. Actuators 554, 556, and 574 may communicate with AHU controller 530 via wires 502. Actuators 554, 556, and 574 may receive control signals from AHU controller 530 and may provide feedback signals to controller 530. In some embodiments, AHU controller 530 receives a measurement of the supply air temperature from a temperature sensor 562 positioned in supply air duct 512 (e.g., downstream of cooling coil 534 and/or heating coil 536). AHU controller 530 may also receive a measurement of the temperature of building zone 506 from a temperature sensor 564 located in building zone 506.

In some embodiments, AHU controller 530 operates valves 546, 552, and 576 via actuators 554, 556, and 574 to modulate an amount of heating or cooling provided to supply air 510 (e.g., to achieve a setpoint temperature for supply air 510 or to maintain the temperature of supply air 510 within a setpoint temperature range). The positions of valves 546, 552, and 576 affect the amount of heating or cooling provided to supply air 510 by cooling coil 534, heating coil 536, and/or preheat coil 572 and may correlate with the amount of energy consumed to achieve a desired supply air temperature. AHU controller 530 may control the temperature of supply air 510 and/or building zone 506 by activating or deactivating coils 572, 534, and 536, adjusting a speed of supply fan 538, or a combination of both.

AHU 501 is shown to include a return fan 532 positioned within return air duct 508. Return fan 532 can be configured to force return air 504 through return air duct 508 and through exhaust air damper 516 and/or mixing damper 518. AHU controller 530 may communicate with return fan 532 via wires 502 to control a flow rate of return air 504. AHU controller 530 may receive measurements of various attributes of return air 504 from sensors positioned in return air duct 508. For example, AHU 501 is shown to include a flow sensor 580, a temperature sensor 582, an air quality sensor 584, and a humidity sensor 586 positioned in return air duct 508. Sensors 580-586 may provide measurement signals to AHU controller 530 via wires 502.

Similarly, temperature sensor 566 and humidity sensor 568 can be positioned to measure the temperature and humidity of outside air 514 (e.g., at an inlet of AHU 501, outside building 10, etc.) whereas temperature sensor 540 and limit sensor 558 can be positioned to measure flow and/or temperature of supply air 510 within supply air duct 512. Each of sensors 566, 568, 540, and 558 may provide measurement signals to AHU controller 530 via wires 502. In operation, AHU controller 530 may coordinate all of the controllable equipment of AHU 501 to produce a given (e.g., setpoint) volume of air at a given temperature, humidity, and air quality while keeping building 10 slightly pressurized.

Notably, AHU controller 530 includes numerous connections to various components of AHU 501 via wires 502. Each of the sensors in AHU 501 and each of the controllable devices of AHU 501 (e.g., actuators, fans, dampers, valves, etc.) may communicate with AHU controller 530 via wires 502. In conventional AHUs, communications between AHU controller 530 and the various components of AHU 501 may be transmitted as analog signals via wires 502. When installing AHU 501 each component of AHU 501 may need to be connected to AHU controller 530 via wires 502. Further, each of wires 502 shown in FIGS. 5A-5B may represent any number of actual wires (e.g., one, two, three, four, etc.) running from AHU controller 530 to various components of AHU 501. As shown in FIG. 5A, each individual wire of wires 502 may connect a point or terminal of AHU controller 530 to a corresponding point or terminal on one of the sensors or controllable devices of AHU 501.

As shown in FIG. 5B, wires 502 may include bundles of wires (shown as thick lines) running from AHU controller 530 to junction boxes 503a-503f (collectively junction boxes 503). For example, a set of wires 502 (e.g., 72 wires) may run from AHU controller 530 to junction box 503a. Some of the wires 502 from junction box 503a may attach to sensors 562 and 564, whereas the remainder of the wires 502 (e.g., 60 wires) may continue running from junction box 503a to junction box 503b. From junction box 503b, some of the wires 502 may attach to actuators 554 and 556, whereas the remainder of the wires 502 (e.g., 48 wires) may continue running from junction box 503b to junction box 503c. At junction box 503c, some of the wires 502 may attach to sensors 540 and 558 and supply fan 538, whereas the remainder of the wires 502 (e.g., 34 wires) may continue running from junction box 503c to junction box 503d. Some of the wires 502 may extend from junction box 503d to sensors 566, 568, and 570 and actuator 574, whereas the remainder of the wires 502 (e.g., 22 wires) may continue running from junction box 503d to junction box 503e. From junction box 503e, some of the wires 502 may attach to actuators 524, 526, and 528, whereas the remainder of the wires 502 (e.g., 11 wires) may continue running from junction box 503e to junction box 503f. Finally, the remaining wires 502 may extend from junction box 503f to sensors 580, 582, 584, and 586. In various embodiments, wires 502 may run from AHU controller 530 to each of junction boxes 503 in series as shown in FIG. 5B, or in parallel from AHU controller 530 to each of junction boxes 503.

This approach of using a numerous wires 502 in airside system 500 has several disadvantages. For example, AHU 501 may include a large number of wires 502 (e.g., between forty and sixty wires 502 in some installations) and connections which need to be made between AHU controller 530 and the various components of AHU 501, which may lead to wiring errors and time wasted fixing those errors. Additionally, AHU controller 530 may have fixed input/output (I/O) counts and combinations of inputs and outputs. For example, AHU controller 530 may have nine inputs and nine outputs, some of which may be dedicated binary outputs, analog outputs, or configurable outputs. Each input and output of AHU controller 530 may require a dedicated terminal on the housing of AHU controller 530 for the corresponding wire 502 to be connected.

When the specific I/O requirements of AHU 501 exceed the I/O counts of AHU controller 530, expansion modules are typically added to AHU controller 530 used to make up the difference. An expansion module may include additional I/O terminals to connect additional wires 502 beyond the number of wires 502 supported by AHU controller 530. However, conventional expansion modules have fixed I/O counts as well (i.e., a fixed number of I/O terminals) and must be selected to have at least the minimum number of I/O terminals required by AHU 501. Due to the rigid controller and expansion module I/O counts, the control solution often has many unused inputs/outputs. For example, the exemplary AHU 501 shown in FIGS. 5A-5B may require multiple products (e.g., AHU controller 530, a first expansion module, a second expansion module, etc.) to accommodate all of the required inputs/outputs. However, these products often lead to many unused input, output, and UI terminals or connections.

Referring now to FIGS. 6A-6B, block diagrams of another airside system 600 is shown, according to an exemplary embodiment. Airside system 600 is shown to include the same economizer-type AHU 501 shown in FIGS. 5A-5B with many of the same components having the same reference numbers. However, AHU controller 530 has been replaced with AHU controller 630 and the numerous wires 502 in airside system 500 have been replaced with a single communications link 602 connecting AHU controller 630 to the various sensors and controllable devices of AHU 501. Some of the controllable devices of AHU 501 have also been replaced with smart devices (e.g., smart actuators 624, 626, 628, 654, and 656, smart fan 638, etc.) configured to communicate with AHU controller 630 digitally. Advantageously, airside system 600 simplifies wiring, reduces controller I/O count, and increases controller flexibility relative to airside system 500.

Airside system 600 has several significant improvements relative to airside system 500. Most notably, the numerous wires 502 in airside system 500 have been replaced with a single digital communications link 602 connecting AHU controller 630 to the various components of AHU 501. Rather than exchanging analog signals as in airside system 500, the messages sent to AHU controller 630 and from AHU controller 630 via communications link 602 may be digital. For example, communications link 602 can be implemented as a digital communications bus or digital controls bus using any of a variety of digital communications protocols (e.g., Ethernet, TCP/IP, etc.) which allows AHU controller 630 to communicate with multiple components of AHU 501 using the same physical connection. The messages exchanged by AHU controller 630 and other components connected to communications link 602 can be formatted as digital messages having addresses (e.g., sender address, receiver address, etc.) and routed to the desired recipient using any of a variety of digital networking techniques.

Advantageously, the use of communications link 602 instead of many individual wires 502 allows AHU controller 630 to communicate with all of the sensors and controllable devices of AHU 501 via a single connection (e.g., a daisy chain or single communications bus). This change eliminates the need for an AHU controller 530 with multiple expansion modules because a single AHU controller 630 is utilized. Additionally, AHU controller 630 does not require any I/O on board except for communications. Complex wiring is eliminated and the risk of wiring error is significantly reduced relative to airside system 500. A single communications link 602 may extend from AHU controller 630 and connect to each of the sensors and/or controllable devices in airside system, either directly or via an intermediate component shown as digital modules 604. Alternatively, AHU controller 630 may include both an I/O for communications link 602 and one or more additional I/Os for conventional analog inputs or outputs, as shown in FIGS. 5A-5B. In such an embodiment, AHU controller 630 can be configured to operate in the same manner as AHU controller 530 with respect to the directly connected analog devices connected to the analog I/Os of AHU controller 630, and may additionally communicate with digital modules 604 via communications link 602.

Another significant difference between airside system 500 and airside system 600 is the use of digital modules 604. For example, airside system 600 is shown to include several digital modules 604a, 604b, 604c, 604d, 604e, and 604f (collectively digital modules 604). Digital modules 604 may be connected to communications link 602 and can serve as intermediaries between the digital and analog components of airside system 600. Digital modules 604 allow various components of AHU 501 to remain as conventional analog components (e.g., analog sensors, binary on/off switches, equipment that receives analog control signals, etc.) while enabling digital communications with AHU controller 630 via communications link 602. As shown in FIG. 6A, each digital module 604 may connect communications link 602 to one or more components of AHU 501. As shown in FIG. 6B, digital modules 604 can be implemented as standalone modules (e.g., digital modules 604a, 604b, and 604c), combined with junction boxes 503 (e.g., digital modules 604d, 604e, and 604f), or combined with smart equipment (e.g., smart actuators 624, 626, 628, 654, and 656, smart fan 638, etc.).

In some embodiments, some of digital modules 604 are configured as input modules whereas other digital modules 604 are configured as output modules. Input digital modules 604 can be connected to sensors or other input devices or integrated into such devices. For example, digital module 604a is shown connected to sensors 582-586, digital module 604b is shown connected to sensor 580, digital module 604d is shown connected to sensors 566-570, digital module 604e is shown connected to sensors 540 and 558, and digital module 604f is shown connected to sensors 562 and 564. Input digital modules 604 can be configured to supply power to their connected sensors and convert analog signals received from their connected sensors into digital communications for AHU controller 630.

Output digital modules 604 can be connected to controlled devices (e.g., actuators, fans, dampers, valves, chillers, boilers, etc.) or integrated into the controlled devices. For example, digital module 604c is shown connected to return fan 532. Other controlled devices shown in FIGS. 6A-6B (i.e., dampers 624-628, supply fan 638, and actuators 674, 654, and 656) may be smart equipment that includes digital modules 604 integrated therewith. Output digital modules 604 can be configured to supply power to their connected controlled devices and convert digital communications from AHU controller 630 into analog control signals provided to their controlled devices. Some digital modules 604 can be connected to multiple sensors or controlled devices (e.g., digital modules 604a, 604d, 604e, and 604f), whereas other digital modules 604 can be connected to a single sensor or controlled device (e.g., digital modules 604b and 604c).

In various embodiments, each of digital modules 604 can be configured to function as only an input digital module 604, only an output digital module 604, or as both an input digital module 604 and an output digital module 604. For example, as shown in FIG. 6B, digital module 604b is shown receiving input (e.g., measurements) from flow sensor 580 and providing output (e.g., control signals) to return fan 532 and thus can function as both an input digital module 604 and an output digital module 604. The configuration of digital modules 604 to function as input or output digital modules 604 can be set by their included hardware (e.g., fixed function for a given set of hardware components) or can be set by software, firmware, or variable configuration parameters to allow any given digital module 604 to be configured as an input digital module 604, an output digital module 604, or as both an input digital module 604 and an output digital module 604. In some embodiments, digital modules 604 are configured to detect the types of devices to which they are connected and configure themselves to the appropriate settings depending on the devices to which each digital module 604 is connected. For example, a given digital module 604 can configure itself to function as only an input digital module 604 if connected only to sensors (e.g., digital module 604a), as only an output digital module 604 if connected only to controllable devices (e.g., digital module 604c), or as both an input digital module 604 and an output digital module 604 if connected to both sensors and controllable devices (e.g., digital module 604b as shown in FIG. 6B). Digital modules 604 can be configured to receive any combination of analog inputs and binary inputs and/or provide any combination of analog outputs and binary outputs in various embodiments.

Referring now to FIGS. 7A-7B, an implementation of digital modules 604 in the context of a variable air volume (VAV) system 700 is shown, according to an exemplary embodiment. VAV system 700 may be part of airside system 500 or airside system 600 as described with reference to FIGS. 5A-6B. VAV system 700 may include one or more VAV units, shown as VAV-A 701 and VAV-B 731 (collectively VAVs 701 and 731). Each of VAVs 701 and 731 may receive supply air 510 from an AHU (e.g., AHU 501) and further condition or restrict supply air 510 to form discharge air 511a and 511b. The discharge air 511a and 511b formed by VAVs 701 and 731 may be delivered to respective building zones 506a and 506b.

VAV-A 701 is shown to include several sensors including a supply air temperature sensor 704, a supply air pressure sensor 706 (e.g., a velocity pressure sensor), a discharge air temperature sensor 712, and a zone temperature sensor 714. Supply air sensors 704 and 706 may be positioned near the air intake end of VAV-A 701 and configured to measure the temperature and pressure of supply air 510 respectively entering VAV-A 701. Discharge air temperature sensor 712 may be positioned near the air discharge end of VAV-A 701 and may be configured to measure the temperature of discharge air 511a entering building zone 506a. Zone temperature sensor 714 may be positioned inside building zone 506a and may be configured to measure the temperature of building zone 506a. VAV-A 701 is shown to include several controlled devices including a VAV damper 718 which is operated by damper actuator 708, a box heater 720 which is controlled by valve actuator 710, and a zone heater 722 which is controlled by valve actuator 716.

Similarly, VAV-B 731 is shown to include several sensors including a supply air temperature sensor 734, a supply air pressure sensor 736 (e.g., a velocity pressure sensor), a discharge air temperature sensor 742, and a zone temperature sensor 744. Supply air sensors 734 and 736 may be positioned near the air intake end of VAV-B 731 and configured to measure the temperature and pressure of supply air 510 respectively entering VAV-B 731. Discharge air temperature sensor 742 may be positioned near the air discharge end of VAV-B 731 and may be configured to measure the temperature of discharge air 511b entering building zone 506b. Zone temperature sensor 744 may be positioned inside building zone 506b and may be configured to measure the temperature of building zone 506b. VAV-B 731 is shown to include several controlled devices including a VAV damper 748 which is operated by damper actuator 738, a box heater 750 which is controlled by valve actuator 740, and a zone heater 752 which is controlled by valve actuator 746.

As shown in FIG. 7A, VAV-A controller 702 can be configured to receive input from sensors 704, 706, 712, and 714, and supply control signals to actuators 708, 710, and 716. Similarly, VAV-B controller 732 can be configured to receive input from sensors 734, 736, 742, and 744, and supply control signals to actuators 738, 740, and 746. Each of VAV controllers 702 and 732 may be connected to the various sensors and controlled devices of its respective VAV via a set of wires 502. In the conventional implementation shown in FIG. 7A, one or more individual wires 502 may need to be run from each VAV controller 702 and 732 to each of the sensors and controlled devices of the respective VAV. Although only two VAVs 701 and 731 shown in FIG. 7A for ease of illustration, it is contemplated that any number of VAVs can be present in a building.

As shown in FIG. 7B, an implementation of VAV system 700 with digital modules 604 is shown, according to an exemplary embodiment. In FIG. 7B, VAV system 700 is shown to include many of the same components as shown in FIG. 7A, with the exception that VAV-A controller 702 and VAV-B controller 732 have been replaced with a single VAV controller 762 which monitors and controls both VAV-A 701 and VAV-B 731. Additionally, digital modules 604 are used to connect VAV controller 762 to the various sensors and controlled devices of VAVs 701 and 731. In particular, a first digital module 604a is shown connecting to sensors 704, 706, 712, and 714 and actuators 708, 710, and 716 of VAV-A 701, whereas a second digital module 604b is shown connecting to sensors 734, 736, 742, and 744 and actuators 738, 740, and 746 of VAV-B 731.

Each of digital modules 604a and 604b (collectively digital modules 604) may be connected to VAV controller 762 via a digital communications link 602, which may be the same as described with reference to FIGS. 6A-6B. In some embodiments, communications link 602 may form a loop (e.g., an Ethernet loop) that connects VAV controller 762 with digital modules 604 in series as shown in FIG. 7B. However, it is contemplated that various other architectures can be used for communications link 602 such as a daisy-chain architecture or parallel-connected architecture in which digital modules 604 are connected in parallel to communications link 602, as shown in FIG. 6A. VAV controller 762 can be configured to communicate with digital modules 604 using digital messages transmitted via communications link 602. Digital modules 604 can be configured to translate between the digital messages and analog signals and communicate with the various sensors and controlled devices of VAVs 701 and 731 using analog signals, as described with reference to FIGS. 6A-6B. Advantageously, the implementation shown in FIG. 7B greatly simplifies the installation and wiring of VAV controller 762 because a single communications link 602 is used to connect VAV controller 762 with digital modules 604, rather than requiring individual wires 502 connecting VAV controller 762 directly to each sensor and controlled device of VAVs 701 and 731.

Another advantage of the configuration shown in FIG. 7B is that a single controller (e.g., VAV controller 762) to be used to control any number of controlled devices and receive input from any number of sensors, regardless of the number of physical input/output connections or terminals on the controller because only one physical connection is required for communications link 602. Additionally, a single controller can be used for multiple different types of HVAC systems (e.g., an AHU and a VAV, a temperature control loop and a humidity control loop, etc.) and is not limited to multiple instances of the same type of system (e.g., multiple VAVs). For example, VAV-B 731 shown in FIG. 7B could be replaced with AHU 501 shown in FIGS. 6A-6B and a single controller could be used to perform the functions of both AHU controller 630 and VAV controller 762.

Referring now to FIGS. 8A-9, various implementations of digital modules 604 are shown, according to exemplary embodiments. FIG. 8A illustrates a system 800 in which a digital module 604 is connected to multiple sensors 802, 804, 806, and 808. System 800 can be a portion of airside system 600, VAV system 700, or any other system in which digital modules 604 are implemented. Sensors 802-808 may be any type of sensor used to monitor various measurable conditions (e.g., temperature, pressure, flow rate, voltage, current, air quality, etc.) and may provide analog outputs or signals. Sensors 802-808 can be binary sensors (e.g., limit switches, air proving switches, temperature proving switches, status sensors, etc.) configured to provide a binary output (e.g., on/off, yes/no, true/false, etc.). Digital module 604 can be configured to supply power to sensors 802-808 and convert analog signals received from sensors 802-808 into digital communications transmitted via communications link 602. Digital module 604 can be installed adjacent to sensors 802-808 or remote from sensors 802-808 in various embodiments.

FIG. 8B illustrates a system 820 in which a digital module 604 is integrated into a smart actuator 822. System 820 can be a portion of airside system 600, VAV system 700, or any other system in which digital modules 604 are implemented. Smart actuator 822 may be one of actuators 624-628, 674, 654, or 656 shown in FIG. 6A. Smart actuator 822 is shown to include digital module 604, an actuator controller 824, and a motor 826. Motor 826 may be physically coupled to a valve or damper 828 and configured to operate valve or damper 828 between various positions (e.g., open, closed, intermediate positions, etc.). Digital module 604 can be configured to supply power to smart actuator 822 and convert digital communications received via communications link 602 into analog control signals provided to actuator controller 824. For controllable devices that communicate bidirectionally with other equipment, digital module 604 can be configured convert analog signals received from the controllable device (e.g., actuator controller 824) into digital communications transmitted via communications link 602.

Although smart actuator 822 is provided as one example of a type of equipment which can be integrated with digital module 604, it should be understood that digital module 604 can be integrated into any other type of controllable device (e.g., supply fan 638, chillers, boilers, electric heaters, etc.) or integrated into sensors or other input devices in various embodiments. Accordingly, smart actuator 822 can be replaced with any other type of smart equipment (e.g., smart fan, smart valve, smart sensor, etc.) without departing from the teachings of the present disclosure. Additionally, it is contemplated that an implementation of digital module 604 as a component of smart equipment is not limited to communicating with components of that unit of smart equipment. For example, as shown in FIG. 8B, digital module 604 may communicate with a sensor 830 (e.g., a temperature sensor, flow sensor, position sensor, etc.) located outside of smart actuator 822. Advantageously, digital module 604 can be configured to communicate with multiple different sensors, equipment components, or controlled devices that are located within smart actuator 822 or outside smart actuator 822 (or any other type of smart equipment within which digital module 604 is located).

FIG. 9 illustrates a system 900 in which various digital modules 604g, 604h, 604i, 604j, 604k, and 604l (collectively digital modules 604) facilitate communications between equipment 910, 930, and 950 and controllers 964, 966, and 968, according to an exemplary embodiment. System 900 can be a portion of airside system 600 or any other system in which digital modules 604 are implemented. Equipment 910, 930, and 950 can include any type of equipment which can be used airside system 600, other types of HVAC systems (e.g., waterside systems, VRF systems, TABS, etc.), or any other type of building system or subsystem (e.g., building electrical subsystem 434, ICT subsystem 436, security subsystem 438, HVAC subsystem 440, lighting subsystem 442, lift/escalators subsystem 432, fire safety subsystem 430, etc.). Each of equipment 910, 930, and 950 is shown to include multiple sensors and multiple controlled devices. For example, equipment 910 is shown to include sensors 912, 914, and 916 and controlled devices 918, 920, and 922. Equipment 930 is shown to include sensors 932, 934, and 936 and controlled devices 938, 940, and 942. Equipment 950 is shown to include sensors 952, 954, and 956 and controlled devices 958, 960, and 962.

System 900 is shown to include several controllers including a lead controller 964, a standby controller 966, and a supervisory controller 968. Lead controller 964 may be the primary controller responsible for monitoring and controlling equipment 910, 930, and 950. One example of lead controller 964 is AHU controller 630 in airside system 600. Standby controller 966 may have the same or similar functionality as lead controller 964 and may be configured to take over the responsibilities of lead controller 964 in the event lead controller 964 goes offline (e.g., due to a fault, communication outage, for repair or replacement, etc.). Supervisory controller 968 may be a system-level controller (e.g., BMS controller 12) responsible for monitoring and controlling multiple subsystems (e.g., building subsystems 428). In system 900, communications link 602 is shown connecting digital modules 604 with each of lead controller 964 and standby controller 966, which then communicate with supervisory controller 968 via a separate communications link 970. However, it is contemplated that communications link 602 may also or alternatively connect digital modules 604 directly with supervisory controller 968 in some embodiments.

System 900 is shown to include several digital modules 604, each of which facilitates communications with a subset of the sensors and controlled devices of equipment 910, 930, and 950. For example, digital module 604g is shown as an input digital module configured to convert analog signals from sensors 912-916 of equipment 910 into digital communications transmitted to controllers 964-968 via communications link 602. Digital module 604h is shown as an output digital module configured to convert digital communications from controllers 964-968 via communications link 602 into analog signals provided to controlled devices 918-922 of equipment 910. Digital module 604i is shown as an input digital module configured to convert analog signals from sensors 932-936 of equipment 930 into digital communications transmitted to controllers 964-968 via communications link 602. Digital module 604j is shown as an output digital module configured to convert digital communications from controllers 964-968 via communications link 602 into analog signals provided to controlled devices 938-942 of equipment 930. Digital module 604k is shown as an input digital module configured to convert analog signals from sensors 952-956 of equipment 950 into digital communications transmitted to controllers 964-968 via communications link 602. Digital module 604l is shown as an output digital module configured to convert digital communications from controllers 964-968 via communications link 602 into analog signals provided to controlled devices 958-962 of equipment 950.

Although digital modules 604 are shown separate from equipment 910, 930, and 950 in FIG. 9, it is contemplated that digital modules 604 can be integrated with equipment 910, 930, and/or 950 in various embodiments. Additionally, while each digital module 604 is shown communicating with a subset of sensors and controlled devices within a single unit of equipment 910, 930, or 950, it is contemplated that some digital modules 604 can communicate with sensors or controlled devices distributed across multiple units of equipment 910, 930, or 950. For example, digital module 604g could be configured to receive analog signals from sensors 912-916 of equipment 910 as well as from sensors 932-936 of equipment 930 in some embodiments and is not necessarily specific to equipment 910. Similarly, digital module 604h could be configured to provide signals to controlled devices 918-922 of equipment 910 as well as to controlled devices 938-942 of equipment 930 in some embodiments and is not necessarily specific to equipment 910.

Although each digital module 604 is shown in FIG. 9 as either an input digital module (e.g., digital modules 604g, 604i, and 604k) or output digital module (e.g., digital modules 604h, 604j, and 604l), it is contemplated that some digital modules 604 can function as both input and output digital modules. For example, digital module 604g could be configured to receive signals from sensors 912-916 of equipment 910 and provide control signals to controlled devices of equipment 910, combining the functionality of digital modules 604g and 604h. In general, each digital module 604 can be configured to communicate with any number of sensors and/or controlled devices which may be located in a single unit of equipment 910, 930, or 950, distributed across multiple units of equipment 910, 930, or 950, or implemented as stand-alone sensors or controlled devices separate from equipment 910, 930, or 950.

In various embodiments, digital modules 604 can be implemented as physical devices or virtual devices. A physical device implementation of digital module 604 may include its own hardware (e.g., housing, processing circuit, processor, memory, communications interface(s), etc.) which can be physically attached to the equipment, controlled device, or sensor with which the digital module 604 communicates or is integrated. For example, FIG. 8A illustrates an embodiment in which digital module 604 is implemented as a physical device which communicates with multiple sensors 802-808 separate from digital module 604. A virtual device implementation of digital module 604 may include a container, virtual machine, functional module, or other type of virtual device which runs on the hardware of the equipment, sensor, or controlled device with which digital module 604 is integrated. For example, FIG. 8B illustrates an embodiment in which digital module 604 is integrated with smart actuator 822 and runs on the hardware of smart actuator 822. As another example, any of the digital modules 604g-604l shown in FIG. 9 could be implemented as virtual devices that run on equipment 910, 930, or 950 or any of the sensors or controlled devices thereof.

In some embodiments, system 900 or any of the components thereof (or any other systems or devices described herein) may include any or all of the features or functionality described in U.S. Provisional Ser. No. 63/537,993 filed Sep. 12, 2023, and titled “Building System with Brokering and Distributed Control” (“the '993 application”) the entire disclosure of which is incorporated by reference herein. For example, lead controller 964 and standby controller 966 can be configured to switch between lead and standby roles using the techniques described in the '993 application. The techniques described in the '993 application can also be used to set up and use one or more databases used by the systems and methods described herein. It is contemplated that various combinations of the features or functionality described in the '993 application and the systems and methods described throughout the present disclosure could be used together in some embodiments.

Referring generally to FIGS. 6A-9, digital modules 604 can be installed in the same local operating environment as the building equipment with which digital modules 604 communicate. As used herein, the “local operating environment” of the building equipment refers to the area or volume immediately surrounding the building equipment with which digital modules 604 communicate and within which the building equipment operate to affect or measure a variable state or condition of a building. For example, the local operating environment of AHU 501 shown in FIGS. 6A-6B may include return air duct 508, supply air duct 512, a housing or enclosure of AHU 501, locations at which the various sensors and controlled devices of AHU 501 are mounted or installed, and the areas or volumes immediately surrounding such building equipment. As another example, the local operating environment of VAV system 700 shown in FIGS. 7A-7B may include the ducts within which VAV-A 701 and VAV-B 731 are installed, locations at which the various sensors and controlled devices of VAV-A 701 and VAV-B 731 are mounted or installed, and the areas or volumes immediately surrounding such building equipment. The local operating environment of any sensors or controlled devices located within building zone 506 (e.g., zone temperature sensors 564, 714, and 744, zone heaters 722 and 752, etc.) may include the locations at which such building equipment are mounted or installed within building zone 506 and the areas or volumes immediately surrounding such building equipment.

The area or volume immediately surrounding the building equipment can be defined as the area or volume within a threshold distance of the building equipment (e.g., within 1 foot of the building equipment, within 5 feet of the building equipment, within 10 feet of the building equipment, etc.). In some embodiments, the area or volume immediately surrounding the building equipment includes a mounting surface or structure within the threshold distance of the building equipment (e.g., a wall, a panel, etc.) on which one or more of digital modules 604 can be mounted or installed. The mounting surface or structure may be part of the building equipment (e.g., a housing or enclosure of the building equipment) or separate from the building equipment in various embodiments, but located within the local operating environment of the building equipment. For example, digital module 604a (shown in FIG. 6A) can be physically attached to one or more of sensors 582-586 (e.g., mounted on a housing of sensors 582-586) or physically attached to return air duct 508 within which sensors 582-586 are installed. Similarly, digital module 604c (shown in FIG. 6A) can be physically attached to return fan 532 (e.g., mounted on a housing of return fan 532) or physically attached to return air duct 508 within which return fan 532 is installed.

In some embodiments, the local operating environment of the building equipment includes the area or volume within the building equipment itself. Installing digital modules 604 within the local operating environment of the building equipment may include integrating digital modules 604 with the building equipment with which digital modules 604 communicate. For example, as shown in FIG. 7B, digital module 604 can be installed within smart actuator 822 (e.g., mounted inside a housing or enclosure of smart actuator 822). Digital modules 604 can be mounted or installed within the building equipment (e.g., on a same board or mounting structure, inside a housing or enclosure of the building equipment) and can be added to any type of building equipment as an aftermarket accessory. Alternatively, digital modules 604 may be integral components of the building equipment which are included as parts of the building equipment at the time of manufacture (e.g., for embodiments in which digital module 604 is implemented as a virtual device or otherwise integrated with the building equipment).

Advantageously, locating digital modules 604 within the same local operating environment as the building equipment with which digital modules 604 communicate reduces the distance between digital modules 604 and the building equipment, thereby reducing the length of wires needed to connect digital modules 604 with the building equipment. This greatly simplifies installation and wiring of the building equipment by avoiding multiple lengthy wires 502 running between the building equipment and the controller. Rather, a single communications link 602 can replace multiple wires 502 and can be used to communicate with each of digital modules 602 connected to communications link 602. Each digital module 604 can be physically attached (e.g., mounted on or within, connected via a physical wire/cable or fastener, etc.) to one or more devices of the building equipment. Such installation within the same local operating environment uses relatively shorter wires (e.g., as compared to wires 502), which significantly reduces the wiring and installation complexity of the system of building equipment as a whole.

Referring now to FIGS. 10-11, block diagrams illustrating digital modules 604 in greater detail are shown, according to exemplary embodiments. FIG. 10 illustrates a system 1000 in which an input digital module 604 communicates with a sensor 1008. System 1000 can be a portion of airside system 600 or any other system in which digital modules 604 are implemented. Sensor 1008 may be any type of sensor used to monitor various measurable conditions (e.g., temperature, pressure, flow rate, voltage, current, air quality, etc.). For example, sensor 1008 is shown to include a transducer 1010 which may be configured to measure an environmental condition and output an analog signal indicative of the measured environmental condition.

In some embodiments, the analog signal is a voltage signal having a voltage value within a prescribed output range (e.g., 0V-10V). The value of the voltage signal may correspond to the value of the measured condition measured by transducer 1010. For example, if sensor 1008 is configured to measure temperature, a value of 0V may correspond to the minimum temperature value transducer 1010 is capable of measuring whereas a value of 10V may correspond to the maximum temperature value transducer 1010 is capable of measuring. Transducer 1010 can output any value within its prescribed range based on (e.g., proportional to) the value of the measured condition between the minimum and maximum measurable values. In some embodiments, transducer 1010 is configured to output a binary signal (e.g., on/off, yes/no, true/false, 0V/5V) depending on the value of the measured condition. For example, if sensor 1008 is a limit switch, air proving switch, or status sensor, transducer 1010 can output a value of 0V to indicate a first binary state (e.g., on, closed, true, etc.) and may output a value of 5V (or any other non-zero value) to indicate a second binary state (e.g., off, open, false, etc.).

Sensor 1008 is shown to include three terminals including a supply voltage terminal 1012, a signal terminal 1014, and a ground terminal 1016. Each of terminals 1012, 1014, and 1016 can be coupled to digital module 604 via a corresponding wire 1040, 1042, and 1044. In some embodiments, wires 1040-1044 are combined or bundled into a multi-conductor cable or multi-wire cable. The analog signal measured by transducer 1010 can be provided as an output from sensor 1008 via signal terminal 1014 and transmitted to digital module 604 via signal wire 1042. Supply voltage terminal 1012 can receive power from digital module 604 at a given output voltage via power wire 1040 and supply power to transducer 1010 and/or other powered components of sensor 1008. Ground terminal 1016 can be connected to a ground wire 1044 which is maintained at a ground voltage by digital module 604.

Still referring to FIG. 10, digital module 604 is shown to include a power converter 1018, a processing circuit 1020, an analog communications interface 1027, and a digital communications interface 1026. Power converter 1018 can be configured to receive an input voltage from communications link 602 and convert the input voltage into the output voltage required by sensor 1008. In some embodiments, power converter 1018 includes a step-up transformer or a step-down transformer configured to produce the output voltage required by sensor 1008 from a lower or higher input voltage provided by communications link 602. In some embodiments, power converter 1018 includes an AC/DC converter configured to transform the input voltage provided by communications link 602 (AC or DC) into the required type of output voltage (DC or AC) required by sensor 1008.

Processing circuit 1020 is shown to include a processor 1022 and memory 1024. Processor 1022 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 1022 is configured to execute computer code or instructions stored in memory 1024 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.).

Memory 1024 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 1024 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 1024 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 1024 may be communicably connected to processor 1022 via processing circuit 1020 and may include computer code for executing (e.g., by processor 1022) one or more processes described herein. When processor 1022 executes instructions stored in memory 1024, processor 1022 generally configures digital module 604 (and more particularly processing circuit 1020) to complete such activities.

Memory 1024 is shown to include a signal converter 1030 including an analog to digital converter (ADC) 1032, a signal processor and conditioner 1034, and a message generator 1036. ADC 1032 can receive the analog signal output by sensor 1008 via analog communications interface 1027 and convert the analog signal into a digital message for transmission via digital communications interface 1026. In some embodiments, ADC 1032 is configured to convert an analog voltage value (e.g., 0V-10V) into a corresponding value of the measured state or condition (e.g., temperature in ° C. or ° F.) based on a stored range of values of the analog signal and the corresponding range of values of the measured state or condition sensor 1008 is capable of measuring. For example, if the analog signal from sensor 1008 has a range of 0V corresponding to a measured temperature of 0° C. and 10V corresponding to a measured temperature of 50° C., ADC 1032 can convert an analog voltage of 4V into a corresponding temperature measurement of 20° C. by interpolating within the temperature range.

Signal processor and conditioner 1034 may include an anti-aliasing filter and/or other signal processing and configuration functions for processing the analog signal received from sensor 1008. For example, signal processor and conditioner 1034 can be configured to perform anti-spike filtering, low pass filtering, configuring signal range, signal type, sampling rates, and calibration information. Signal processor and conditioner 1034 can be configured to provide ADC 1032 with the calibration information including ranges of values of the analog signal (e.g., 0V-10V) and/or ranges of values of the measured state or condition (e.g., 0° C.-50° C.) for use in converting the analog signal into a corresponding value of the measured state or condition.

Message generator 1036 can be configured to generate the message transmitted from digital module 604 via digital communications interface 1026 and communications link 602. Message generator 1036 can manage the communications protocol, addressing, and other requirements of the message based on the particular formatting and protocol requirements of AHU controller 630 or other devices configured to listen for messages on communications link 602. For example, message generator 1036 can be configured to generate a digital message in the communications protocol used by communications link 602 (e.g., Ethernet, TCP/IP, etc.). Message generator 1036 can generate various attributes of the message including sender address (e.g., the address of digital module 604 or sensor 1008), receiver address (e.g., the address of AHU controller 630, lead controller 964, or supervisory controller 968), message payload (e.g., measured values, timestamps, etc.), any headers required by the communications protocol, and/or any other metadata. In some embodiments, message generator 1036 generates the payload or attributes of a digital message to be transmitted via communications link 602 based on the digital value generated by ADC 1032. The payload or attributes of the digital message may include, for example, measurement type (e.g., temperature, pressure, flow rate, etc.), a value of the measurement (e.g., 20, 15.4, −10.8, etc.), units of measurement (e.g., ° C., ° F., kPa, m/s, etc.), a timestamp (e.g., 2024-07-22 at 4:30 PM), and/or any other attributes of the message to be transmitted via communications link 602. Message generator 1036 can then send the message via digital communications interface 1026.

Still referring to FIG. 10, communications link 602 is shown to include multiple conductors 602a, 602b, and 602c. Each of conductors 602a, 602b, and 602c may include one or more conductors (e.g., a single wire, a pair of wires, etc.) configured to transmit data, power, or other electrical signals between digital module 604 and any other devices connected to communications link 602. For example, conductor 602a can be configured to supply digital module 604 with an input voltage which is converted to an output voltage by power converter 1018. Conductor 602b may be configured to carry the digital messages generated by digital module 604 and/or any other devices connected to communications link 602. Conductor 602c may include a ground wire configured to provide digital module 604 with the ground voltage which digital module 604 passes through to sensor 1008 via ground wire 1044. Accordingly, communications link 602 can be implemented as a multi-conductor cable or multi-wire cable which allows multiple types of electrical signals to be exchanged with digital module 604 via a single physical cable.

Digital communications interface 1026 may include a wired communications interface (e.g., one or more wire terminals, jacks, receivers, plugs, connectors, etc.) configured to interface with communications link 602. In some embodiments, digital communications interface 1026 includes a single terminal (e.g., connection, port, etc.) with multiple pins (e.g., RJ-11, RJ-45, etc.) each configured to connect to one of the conductors 602a-602c within communications link 602. For example, digital communications interface 1026 may include a first pin or pins configured to make electrical contact with conductor 602a, a second pin or pins configured to make electrical contact with conductor 602b, and a third pin or pins configured to make electrical contact with conductor 602c when communications link 602 is connected to digital module 604 (i.e., plugged-in to digital communications interface 1026). Advantageously, this configuration allows communications link 602 to provide digital module 604 and sensor 1008 with power, exchange data communications with digital module 604 and sensor 1008, and provide a ground signal to digital module 604 and sensor 1008 via a single physical cable or connection. For embodiments in which communications link 602 connects multiple devices of building equipment in a daisy chain, digital communications interface 1026 may include multiple physical interfaces (e.g., multiple wire terminals, jacks, receivers, plugs, connectors, etc.) such that each digital module 604 can be connected in series with each other and with controller 630 in a single chain or loop.

Similarly, analog communications interface 1027 may include a wired communications interface (e.g., one or more wire terminals, jacks, receivers, plugs, connectors, etc.) configured to interface with sensor 1008. In some embodiments, analog communications interface 1027 includes a single terminal (e.g., connection, port, etc.) with multiple pins (e.g., RJ-11, RJ-45, etc.) each configured to connect to one of the wires 1040-1044 extending between analog communications interface 1027 and sensor 1008. In some embodiments, wires 1040-1044 are combined or bundled into a multi-conductor cable or multi-wire cable having a similar structure as communications link 602. For example, analog communications interface 1027 may include a first pin or pins configured to make electrical contact with power wire 1040, a second pin or pins configured to make electrical contact with signal wire 1042, and a third pin or pins configured to make electrical contact with ground wire 1044 when the multi-wire cable is connected to digital module 604 (i.e., plugged-in to analog communications interface 1027). Accordingly, digital module 604 may provide sensor 1008 with power, receive data communications from sensor 1008, and provide a ground signal to sensor 1008 via a single physical cable or connection.

Referring now to FIG. 11, a system 1100 is shown in which an output digital module 604 communicates with a controlled device 1108. System 1100 may be a portion of airside system 600 or any other system in which digital modules 604 are implemented. Controlled device 1108 can include any type of device which operates to affect a variable state or condition in a building (e.g., temperature, pressure, flow rate, humidity, air quality, etc.) or any other environment or setting. For example, controlled device 1108 may include an actuator, a fan, a motor, a chiller, a boiler, an electric heater, etc. Controlled device 1108 is shown to include a transducer 1110 which may be configured to receive an electrical signal and convert the electrical signal into one or more other forms of energy (e.g., heat, kinetic energy, magnetic or electric fields, etc.). For example, transducer 1110 may be a motor configured to convert electricity into rotational kinetic energy or an electric heating element configured to convert electricity into heat. The electrical signal provided as an input to transducer 1110 may be an analog signal generated by digital module 604.

In some embodiments, the analog signal is a voltage signal, electric current signal, or power signal having a value within a prescribed range (e.g., 0V-10V, 4-20 mA, etc.). The value of the analog signal may correspond to the output to be achieved by operating transducer 1110. For example, if controlled device 1108 is an actuator which operates a valve or damper, a value of 0V may correspond to a first end position of the valve or damper (e.g., fully closed) whereas a value of 10V may correspond a second end position of the valve or damper (e.g., fully open). Transducer 1110 can operate to set the position of the valve or damper to any position within its prescribed range based on (e.g., proportional to) the value of the analog signal provided by digital module 604. In some embodiments, transducer 1110 is configured to receive a binary signal (e.g., on/off, yes/no, true/false, 0V/5V) which causes transducer 1110 to switch into a corresponding binary state. For example, if transducer 1110 is an electric relay capable of being open or closed or an electric heating element capable of being on or off, digital module 604 can provide a signal having a value of 0V to cause transducer 1110 to switch into a first binary state (e.g., on, closed, etc.) and may output a value of 5V (or any other non-zero value) to indicate a second binary state (e.g., off, open, etc.).

Controlled device 1108 is shown to include three terminals including a supply voltage terminal 1112, a signal terminal 1114, and a ground terminal 1116. Each of terminals 1112, 1114, and 1116 can be coupled to digital module 604 via a corresponding wire 1140, 1142, and 1144. In some embodiments, wires 1140-1144 are combined or bundled into a multi-conductor cable or multi-wire cable. The analog signal generated by digital module 604 can be provided as an input to controlled device 1108 via signal wire 1142 and received at signal terminal 1114 of controlled device 1108. Supply voltage terminal 1112 can receive power from digital module 604 at a given output voltage via power wire 1140 and supply power to transducer 1110 and/or other powered components of controlled device 1108. Ground terminal 1116 can be connected to a ground wire 1144 which is maintained at a ground voltage by digital module 604.

Still referring to FIG. 11, digital module 604 is shown to include a power converter 1118, a processing circuit 1120, an analog communications interface 1127, and a digital communications interface 1126. These components may be the same as or similar to the like-numbered components of system 1000 in FIG. 10. For example, power converter 1118 can be configured to receive an input voltage from communications link 602 and convert the input voltage into the output voltage required by controlled device 1108. In some embodiments, power converter 1118 includes a step-up transformer or a step-down transformer configured to produce the output voltage required by controlled device 1108 from a lower or higher input voltage provided by communications link 602. In some embodiments, power converter 1118 includes an AC/DC converter configured to transform the input voltage provided by communications link 602 (AC or DC) into the required type of output voltage (DC or AC) required by controlled device 1108.

Processing circuit 1120 is shown to include a processor 1122 and memory 1124. Processor 1122 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 1122 is configured to execute computer code or instructions stored in memory 1124 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.).

Memory 1124 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 1124 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 1124 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 1124 may be communicably connected to processor 1122 via processing circuit 1120 and may include computer code for executing (e.g., by processor 1122) one or more processes described herein. When processor 1122 executes instructions stored in memory 1124, processor 1122 generally configures digital module 604 (and more particularly processing circuit 1120) to complete such activities.

Memory 1124 is shown to include a signal converter 1130 including a digital to analog converter (DAC) 1132, a signal processor and conditioner 1134, and a signal generator 1136. These components may be the same as or similar to ADC 1032, signal processor and conditioner 1034, and message generator 1036 of signal converter 1030 shown in FIG. 10, with the exception that the components of signal converter 1130 operate in reverse relative to signal converter 1030. That is, rather than converting analog signals into digital messages as performed by signal converter 1030, the components of signal converter 1130 operate to convert digital messages from communications link 602 into analog signals for transmission to controlled device 1108. Additionally, signal converter 1130 can be configured to listen for messages addressed to controlled device 1108 or the digital module 604 within which signal converter 1130 is contained, and may act on only the messages addressed to these recipients. Any messages addressed to other controlled devices or other digital modules 604 can be ignored by signal converter 1130.

DAC 1132 can receive a digital message from communications link 602 via digital communications interface 1126 and convert the digital message into an analog signal for controlled device 1108. In some embodiments, DAC 1132 is configured to convert a digital value contained within the message received via communications link 602 (e.g., actuator position in % open) into an analog voltage value (e.g., 0V-10V) based on a stored range of values of the analog signal and the corresponding range of values of the output controlled device 1108 is capable of producing. For example, if controlled device 1108 is an actuator and the analog signal provided to controlled device 1108 has a range of 0V corresponding to a first position of the actuator (e.g., fully closed) and 10V corresponding to a second position of the actuator, DAC 1132 can convert a digital value of “40% open” into an analog voltage of 4V by interpolating within the operating range of controlled device 1108. When this voltage signal is provided to controlled device 1108, controlled device 1108 may operate a motor to achieve an actuator position of 40% open.

Signal processor and conditioner 1134 may include an anti-aliasing filter and/or other signal processing and configuration functions for processing the digital message received from communications link 602. For example, signal processor and conditioner 1134 can be configured to perform anti-spike filtering, low pass filtering, configuring signal range, signal type, sampling rates, and calibration information. Signal processor and conditioner 1134 can be configured to provide DAC 1132 with the calibration information including ranges of values of the analog signal (e.g., 0V-10V) and/or ranges of values contained within the digital message (e.g., 0% open-100% open) for use in converting the digital message into a corresponding value of the analog signal.

Signal generator 1136 can be configured to generate the analog signal transmitted to controlled device 1108 via analog communications interface 1127. Signal generator 1136 can manage the communications protocol and other requirements of the analog signal (e.g., amplitude, frequency, time period, wavelength, and/or phase) based on the particular formatting and protocol requirements of controlled device 1108. For example, signal generator 1136 can be configured to generate an analog signal in the communications protocol used by controlled device 1108. Signal generator 1136 can be configured to parse the attributes of the digital message received via communications link 602 including sender address (e.g., the address of the address of AHU controller 630, lead controller 964, or supervisory controller 968), receiver address (e.g., the address of digital module 604 or controlled device 1108), message payload (e.g., control signal values, timestamps, etc.), any headers required by the communications protocol, and/or any other metadata. In some embodiments, signal generator 1136 generates the attributes of the analog signal to be transmitted to controlled device 1108 based on the analog values generated by DAC 1132. Signal generator 1136 can then send the analog signal to controlled device 1108 via analog communications interface 1127.

Still referring to FIG. 11, communications link 602 is shown to include multiple conductors 602a, 602b, and 602c, which may be the same as described with reference to FIG. 10. Each of conductors 602a, 602b, and 602c may include one or more conductors (e.g., a single wire, a pair of wires, etc.) configured to transmit data, power, or other electrical signals between digital module 604 and any other devices connected to communications link 602. For example, conductor 602a can be configured to supply digital module 604 with an input voltage which is converted to an output voltage by power converter 1118. Conductor 602b may be configured to carry the digital messages generated by digital module 604 and/or any other devices connected to communications link 602. Conductor 602c may include a ground wire configured to provide digital module 604 with the ground voltage which digital module 604 passes through to controlled device 1108 via ground wire 1144. Accordingly, communications link 602 can be implemented as a multi-conductor cable or multi-wire cable which allows multiple types of electrical signals to be exchanged with digital module 604 via a single physical cable.

Digital communications interface 1126 may include a wired communications interface (e.g., one or more wire terminals, jacks, receivers, plugs, connectors, etc.) configured to interface with communications link 602. In some embodiments, digital communications interface 1126 includes a single terminal with multiple pins (e.g., RJ-11, RJ-45, etc.) each configured to connect to one of the conductors 602a-602c within communications link 602. For example, digital communications interface 1126 may include a first pin or pins configured to make electrical contact with conductor 602a, a second pin or pins configured to make electrical contact with conductor 602b, and a third pin or pins configured to make electrical contact with conductor 602c when communications link 602 is connected to digital module 604 (i.e., plugged-in to digital communications interface 1126). Advantageously, this configuration allows communications link 602 to provide digital module 604 and controlled device 1108 with power, exchange data communications with digital module 604 and controlled device 1108, and provide a ground signal to digital module 604 and controlled device 1108 via a single physical cable or connection. For embodiments in which communications link 602 connects multiple devices of building equipment in a daisy chain, digital communications interface 1126 may include multiple physical interfaces (e.g., multiple wire terminals, jacks, receivers, plugs, connectors, etc.) such that each digital module 604 can be connected in series with each other and with controller 630 in a single chain or loop.

Similarly, analog communications interface 1127 may include a wired communications interface (e.g., one or more wire terminals, jacks, receivers, plugs, connectors, etc.) configured to interface with controlled device 1108. In some embodiments, analog communications interface 1127 includes a single terminal (e.g., connection, port, etc.) with multiple pins (e.g., RJ-11, RJ-45, etc.) each configured to connect to one of the wires 1140-1144 extending between analog communications interface 1127 and controlled device 1108. In some embodiments, wires 1140-1144 are combined or bundled into a multi-conductor cable or multi-wire cable having a similar structure as communications link 602. For example, analog communications interface 1127 may include a first pin or pins configured to make electrical contact with power wire 1140, a second pin or pins configured to make electrical contact with signal wire 1142, and a third pin or pins configured to make electrical contact with ground wire 1144 when the multi-wire cable is connected to digital module 604 (i.e., plugged-in to analog communications interface 1127). Accordingly, digital module 604 may provide controlled device 1108 with power, provide controlled device 1108 with data communications, and provide a ground signal to controlled device 1108 via a single physical cable or connection.

Advantageously, digital modules 604 may have a significant impact on the complexity and installation requirements of any HVAC system or other types of system in which digital modules 604 are used. For example, using digital modules 604 allows all connections between controllers, sensors, and controlled devices/equipment to be made via a single communications link 602 rather than requiring individual wires connecting each sensor or controlled device to a corresponding terminal on the controller. This reduces wire count, complexity, and cost of the installation. Additionally, using digital modules 604 reduces hardware requirements for the controller (e.g., AHU controller 630, lead controller 964, standby controller 966, supervisory controller 968) because any number of I/O points can be accommodated via a single communications link 602 and single communications interface on the controller. No expansion modules are required on the controller to accommodate multiple wires such as wires 502 and the controller does not need any I/O connections except for communications. Furthermore, the controller can be generalized to communicate via a standard digital communications protocol used by digital modules 604 and does not need to be capable of communicating with each sensor or controlled device directly, which may use many different device-specific or vendor specific communications protocols. This allows the same controller to be used with many different types of equipment because digital modules 604 can be applied to any type of equipment and configured to communicate with the controller using a standard protocol.

Processes Using Digital Modules for Sensors and Controlled Devices

Referring now to FIG. 12, a process 1200 for monitoring and controlling building equipment using digital modules for sensors and controlled devices is shown, according to an exemplary embodiment. Process 1200 can be performed by one or more components of airside system 600, VAV system 700, system 800, system 820, system 900, system 1000, and/or system 1100 as described with reference to FIGS. 6A-11. In some embodiments, process 1200 is performed by system 1100 using controlled device 1108, output digital module 604 shown in FIG. 11, and one or more controllers (e.g., AHU controller 630, lead controller 964, standby controller 966, supervisory controller 968) configured to communicate with output digital module 604 via communications link 602.

Process 1200 is shown to include sending a digital message from a controller via a communications link connecting the controller to multiple digital modules (step 1202). In some embodiments, step 1202 is performed by AHU controller 630, lead controller 964, standby controller 966, supervisory controller 968, or any other controller coupled to communications link 602. The digital message may include various sections or attributes including a sender address identifying the controller, a recipient address identifying a specific digital module or a controlled device, and a payload indicating a value of a control signal generated by the controller for the controlled device. The digital message can be sent via communications link 602 and may be received at each digital module 604 connected to communications link 602. In some embodiments, communications link 602 includes a multi-conductor cable. Step 1202 may include sending the digital message from the controller to a plurality of digital modules 604 via a first conductor of the multi-conductor cable (e.g., conductor 602a shown in FIG. 10). Other conductors of the multi-conductor cable can be used to provide power from the controller to the plurality of digital modules 604 (e.g., conductor 602b) and/or provide a ground voltage from the controller to the plurality of digital modules 604 (e.g., conductor 602c).

Process 1200 is shown to include receiving the digital message at a digital communications interface of an output digital module (step 1204). In some embodiments, the output digital module is the output digital module 604 shown in FIG. 11 and may include any or all of the features or functionality of output digital module 604 described with reference to FIG. 11. For example, output digital module 604 may include a power converter 1118, a signal converter 1130, an analog communications interface 1127, and/or a digital communications interface 1126. In some embodiments, output digital module 604 is a physical device including a housing and a processing circuit 1120 having a processor 1122 and memory 1124. In this case, analog communications interface 1127 and digital communications interface 1126 may be physical interfaces of the physical device and analog communications interface 1127 may be physically coupled to controlled device 1108 (e.g., via one or more wires, via a multi-conductor cable, etc.). In some embodiments, output digital module 604 is a virtual device running on hardware of controlled device 1108. In this case, digital communications interface 1126 may be a physical interface of controlled device 1108 and analog communications interface 1127 may be a virtual communications interface within controlled device 1108.

In some embodiments, step 1204 includes receiving the digital message at multiple different digital modules 604 connected to communications link 602. Each digital module 604 can monitor communications link 602 for incoming digital messages and inspect each digital message to determine whether the digital message is designated for the digital module 604 or the controlled device 1108 to which the digital module 604 is connected. In some embodiments, step 1204 includes determining a recipient of the digital message based on a recipient address of the digital message received at digital communications interface 1126 of output digital module 604 via communications link 602. If the designated recipient of the digital message (i.e., the recipient specified by the recipient address) is the specific digital module 604 inspecting the digital message or the specific controlled device 1108 to which that digital module 604 is connected, digital module 604 can continue with subsequent steps of process 1200. However, if the designated recipient of the digital message is not the specific digital module 604 inspecting the digital message or the specific controlled device 1108 to which that digital module 604 is connected, digital module 604 can ignore the digital message because the digital message is designated for a different digital module 604 or different controlled device 1108.

Process 1200 is shown to include converting the digital message into an analog signal at the output digital module (step 1206). Step 1206 can be performed by signal converter 1130 of output digital module 604 as described with reference to FIG. 11. For example, step 1206 can include parsing the attributes of the digital message received via communications link 602 including sender address (e.g., the address of the address of AHU controller 630, lead controller 964, or supervisory controller 968), receiver address (e.g., the address of digital module 604 or controlled device 1108), message payload (e.g., control signal values, timestamps, etc.), any headers required by the communications protocol, and/or any other metadata. Step 1206 can include processing a payload of the digital message to determine a value of a control signal for controlled device 1108 and generating an analog signal based on the value of the control signal. In some embodiments, step 1206 includes processing or conditioning the digital message or analog signal (e.g., using anti-spike filtering, low pass filtering, etc.). Step 1206 may include managing the communications protocol and other requirements of the analog signal (e.g., amplitude, frequency, time period, wavelength, and/or phase) based on the particular formatting and protocol requirements of controlled device 1108. For example, step 1206 can include generating an analog signal in the communications protocol used by controlled device 1108.

Process 1200 is shown to include transmitting the analog signal from the output digital module to a controlled device (step 1208). Step 1208 can be performed by output digital module 604 using analog communications interface 1127. The analog signal may indicate a value of a control signal or command for controlled device 1108. In some embodiments, step 1208 includes providing controlled device 1108 with an output voltage and/or a ground voltage in addition to the analog signal. For example, digital module 604 can be connected with controlled device 1108 using a multi-conductor cable or multi-wire cable having a similar structure as communications link 602. Analog communications interface 1127 may include a first pin or pins configured to make electrical contact with power wire 1140, a second pin or pins configured to make electrical contact with signal wire 1142, and a third pin or pins configured to make electrical contact with ground wire 1144 when the multi-wire cable is connected to digital module 604 (i.e., plugged-in to analog communications interface 1127). Accordingly, digital module 604 may provide controlled device 1108 with power, data communications (e.g., the analog signal), and a ground signal via a single physical cable or connection.

Process 1200 is shown to include operating the controlled device to affect a variable state or condition based on a value of the analog signal (step 1210). Step 1210 can be performed by controlled device 1108. Controlled device 1108 can include any type of device which operates to affect a variable state or condition in a building (e.g., temperature, pressure, flow rate, humidity, air quality, etc.) or any other environment or setting. For example, controlled device 1108 may include an actuator, a fan, a motor, a chiller, a boiler, an electric heater, etc. In some embodiments, step 1210 includes energizing a transducer 1110 of controlled device 1108. Transducer 1110 can be configured to receive an electrical signal and convert the electrical signal into one or more other forms of energy (e.g., heat, kinetic energy, magnetic or electric fields, etc.). For example, transducer 1110 may be a motor configured to convert electricity into rotational kinetic energy or an electric heating element configured to convert electricity into heat. The electrical signal provided as an input to transducer 1110 may be the analog signal generated in step 1206.

In some embodiments, the analog signal is a voltage signal, electric current signal, or power signal having a value within a prescribed range (e.g., 0V-10V, 4-20 mA, etc.). The value of the analog signal may correspond to the output to be achieved by operating transducer 1110. For example, if controlled device 1108 is an actuator which operates a valve or damper, a value of 0V may correspond to a first end position of the valve or damper (e.g., fully closed) whereas a value of 10V may correspond a second end position of the valve or damper (e.g., fully open). Step 1210 may include operating transducer 1110 to set the position of the valve or damper to any position within its prescribed range based on (e.g., proportional to) the value of the analog signal provided by digital module 604. In some embodiments, step 1210 includes providing transducer 1110 with a binary signal (e.g., on/off, yes/no, true/false, 0V/5V) which causes transducer 1110 to switch into a corresponding binary state. For example, if transducer 1110 is an electric relay capable of being open or closed or an electric heating element capable of being on or off, step 1210 may include providing transducer 1110 with a signal having a value of 0V to cause transducer 1110 to switch into a first binary state (e.g., on, closed, etc.) and/or a value of 5V (or any other non-zero value) to cause transducer 1110 to switch into a second binary state (e.g., off, open, etc.).

Referring now to FIG. 13, a process 1300 for monitoring and controlling building equipment using digital modules for sensors and controlled devices is shown, according to an exemplary embodiment. Process 1300 can be performed by one or more components of airside system 600, VAV system 700, system 800, system 820, system 900, system 1000, and/or system 1100 as described with reference to FIGS. 6A-11. In some embodiments, process 1300 is performed by system 1000 using sensor 1008, input digital module 604 shown in FIG. 10, and one or more controllers (e.g., AHU controller 630, lead controller 964, standby controller 966, supervisory controller 968) configured to communicate with output digital module 604 via communications link 602.

Process 1300 is shown to include receiving an analog signal indicating a value of a variable state or condition measured by a sensor at an analog communications interface of an input digital module coupled to the sensor (step 1302). In some embodiments, step 1302 is performed by input digital module 604 as shown in FIG. 10 using analog communications interface 1027. The sensor (e.g., sensor 1008) may be any type of sensor used to monitor various measurable conditions (e.g., temperature, pressure, flow rate, voltage, current, air quality, etc.). As shown in FIG. 10, sensor 1008 may include a transducer 1010 which may be configured to measure an environmental condition and output an analog signal indicative of the measured environmental condition. The analog signal output by sensor 1008 can be received at analog communications interface 1027 of input digital module 604.

In some embodiments, input digital module 604 is a physical device including a housing and a processing circuit 1020 having a processor 1022 and memory 1024. In this case, analog communications interface 1027 and digital communications interface 1026 may be physical interfaces of the physical device and analog communications interface 1027 may be physically coupled to sensor 1008 (e.g., via one or more wires, via a multi-conductor cable, etc.). In some embodiments, input digital module 604 is a virtual device running on hardware of sensor 1008. In this case, digital communications interface 1026 may be a physical interface of sensor 1008 and analog communications interface 1027 may be a virtual communications interface within sensor 1008.

Process 1300 is shown to include converting the analog signal into a digital message including a value of the variable state or condition measured by the sensor at the input digital module (step 1304). Step 1304 can be performed by signal converter 1030 of input digital module 604 as described with reference to FIG. 10. For example, step 1304 can include using an analog to digital (ADC) converter 1032 to convert the analog signal into a digital message for transmission via digital communications interface 1026. Step 1304 may include performing anti-spike filtering, low pass filtering, configuring signal range, configuring signal type, configuring sampling rates, or any other function performed by signal converter 1030. In some embodiments, step 1304 includes using calibration information to convert a value of the analog signal (e.g., 5V) into a corresponding value of the measured state or condition (e.g., 50° C.) based on a mapping or function relating the values of the analog signal to the values of the measured state or condition.

Step 1304 can include generating the digital message to be transmitted from digital module 604 via digital communications interface 1026 and communications link 602. Step 1304 can include managing the communications protocol, addressing, and other requirements of the message based on the particular formatting and protocol requirements of the controller or other devices configured to listen for messages on communications link 602. For example, step 1304 can include generating a digital message in the communications protocol used by communications link 602 (e.g., Ethernet, TCP/IP, etc.). Step 1304 can include generating various attributes of the message including sender address (e.g., the address of digital module 604 or sensor 1008), receiver address (e.g., the address of AHU controller 630, lead controller 964, or supervisory controller 968), message payload (e.g., measured values, timestamps, etc.), any headers required by the communications protocol, and/or any other metadata. In some embodiments, step 1304 includes generating the payload or attributes of a digital message to be transmitted via communications link 602 based on the digital value generated by ADC 1032. The payload or attributes of the digital message may include, for example, measurement type (e.g., temperature, pressure, flow rate, etc.), a value of the measurement (e.g., 20, 15.4, −10.8, etc.), units of measurement (e.g., ° C., ° F., kPa, m/s, etc.), a timestamp (e.g., 2024-07-22 at 4:30 PM), and/or any other attributes of the message to be transmitted via communications link 602.

Process 1300 is shown to include transmitting the digital message via a communications link connecting a digital communications interface of the input digital module with a controller and other digital modules that exchange digital messages via the communications link (step 1306). In some embodiments, step 1306 is performed by input digital module 604 using digital communications interface 1026. The digital message can be sent via communications link 602 and may be received at each digital module 604 connected to communications link 602. In some embodiments, communications link 602 includes a multi-conductor cable. Step 1304 may include sending the digital message from input digital module 1304 to the controller and/or plurality of other digital modules 604 via a first conductor of the multi-conductor cable (e.g., conductor 602a shown in FIG. 11). Other conductors of the multi-conductor cable can be used to provide power from the controller to the plurality of digital modules 604 (e.g., conductor 602b) and/or provide a ground voltage from the controller to the plurality of digital modules 604 (e.g., conductor 602c).

Configuration of Exemplary Embodiments

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.

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.

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.