Incremental actuator with feedback control

BACKGROUND

The present disclosure relates generally to actuators for use in a heating, ventilating, or air conditioning (HVAC) system and more particularly to systems and methods for controlling the position of incremental actuators with feedback control.

HVAC actuators are used to operate a wide variety of HVAC components such as air dampers, fluid valves, air handling units, and other components that are typically used in HVAC systems. For example, an actuator may be coupled to a damper in an HVAC system and may be used to drive the damper between an open position and a closed position. An HVAC actuator typically includes a motor and a drive device (e.g., a hub, a gear train, etc.) that is driven by the motor and coupled to the HVAC component.

HVAC actuators typically require accurate position feedback for use in closed-loop control systems. Some HVAC actuators use floating control with incremental actuators to open or close the actuator based on flow requirements for a variable air volume (VAV) unit. An actuator implemented with floating control drives between a minimum rotational position and a maximum rotational position based on an input signal. One disadvantage of this method for actuator control is that the actual position of the actuator is not known, and over time, the actual position can differ from a calculated position. This effect is known as drift. Other HVAC actuators are proportional actuators that control the position of the drive device according to a value of DC voltage received. However, proportional actuators can require additional wiring to be installed and are generally more expensive than incremental actuators. It would be desirable to provide a system and method for controlling the more economical incremental actuator that provides accurate calculated positions for the actuator and requires no additional wiring during installation.

SUMMARY

One implementation of the present disclosure is a system for controlling a flow rate through an HVAC component. The system includes a controller communicably coupled with a potentiometer and an actuator configured to drive the HVAC component between multiple positions to affect the flow rate. The controller configured to determine an actuator position setpoint based on a flow rate setpoint, drive the actuator to the actuator position setpoint using a calculated travel period, and set a current actuator position based on a voltage signal received from the potentiometer upon stopping the actuator at an expiration of the calculated travel period.

In some embodiments, the flow rate setpoint is based on a zone temperature error. In other embodiments, the system includes a temperature sensor communicably coupled to the controller. In still further embodiments, the zone temperature error is based on a zone temperature setpoint and a zone temperature measurement from the temperature sensor.

In some embodiments, the potentiometer is coupled to a gear train of the actuator. In other embodiments, the potentiometer is coupled to an external analog output of the actuator.

In some embodiments, the HVAC component is a damper. In other embodiments, the HVAC component is a valve.

In some embodiments, setting the current actuator position based on the voltage signal received from the potentiometer includes determining whether the voltage signal is lower than a low endpoint threshold, and in response to a determination that the voltage signal is not lower than the low endpoint threshold, determining whether the voltage signal is higher than a high endpoint threshold. In response to a determination that the voltage signal is not higher than the high endpoint threshold, setting the current actuator position includes calculating the current actuator position based on the voltage signal, the low endpoint threshold, and the high endpoint threshold.

In some embodiments, setting the current actuator position based on the voltage signal received from the potentiometer includes determining whether the voltage signal is higher than a high endpoint threshold, and in response to a determination that the voltage signal is higher than the high endpoint threshold, resetting the high endpoint threshold to the voltage signal and calculating the current actuator position based on the high endpoint threshold.

In some embodiments, the calculated travel period is based on a stroke time of the actuator between a low endpoint position and a high endpoint position.

Another implementation of the present disclosure is a method for controlling a flow rate through an HVAC component. The method includes determining an actuator position setpoint based on a flow rate setpoint, driving an actuator coupled to the HVAC component to the actuator position setpoint using a calculated travel period, and setting a current actuator position based on a voltage signal received from a potentiometer coupled to the actuator upon stopping the actuator at an expiration of the calculated travel period.

In some embodiments, the flow rate setpoint is based on a zone temperature error. In other embodiments, the zone temperature error is based on a zone temperature setpoint and a zone temperature measurement from a temperature sensor.

Yet another implementation of the present disclosures is a system for controlling an airflow rate through a damper. The system includes a controller communicably coupled with a potentiometer and an incremental actuator configured to drive the damper between multiple positions to affect the airflow rate. The controller is configured to determine a position setpoint for the incremental actuator based on a zone temperature error, operate the incremental actuator to the position setpoint, receive a feedback signal from the potentiometer once the incremental actuator has stopped changing position, and overwrite a calculated position of the incremental actuator with a current position of the incremental actuator based on the feedback signal.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a heating, ventilating, or air conditioning (HVAC) system and a building management system (BMS), according to an exemplary embodiment.

FIG. 2 is a schematic diagram of a waterside system which may be used to support the HVAC system of FIG. 1, according to an exemplary embodiment.

FIG. 3 is a block diagram of an airside system which may be used as part of the HVAC system of FIG. 1, according to an exemplary embodiment.

FIG. 4 is a block diagram of a BMS which may be implemented in the building of FIG. 1, according to an exemplary embodiment.

FIG. 5 is a block diagram of an incremental actuator and feedback control system that can be utilized in the HVAC system of FIG. 1, according to an exemplary embodiment.

FIG. 6 is a flow diagram of a process for determining the position of the incremental actuator of FIG. 5, according to an exemplary embodiment.

FIG. 7 is a flow diagram of a process for controlling the incremental actuator of FIG. 5, according to an exemplary embodiment.

DETAILED DESCRIPTION

Overview

Before turning to the FIGURES, which illustrate the embodiments in detail, it should be understood that the disclosure is not limited to the details or methodology set forth in the description or illustrated in the FIGURES. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting.

The embodiments and implementation of the systems and methods disclosed herein improve current HVAC systems by providing an incremental actuator with feedback control. For example, the incremental actuator may be a damper actuator. In other embodiments, the incremental actuator may be a valve actuator, a fan actuator, a pump actuator, or any other type of actuator that can be used in a HVAC system that uses incremental or floating control for the actuator.

The incremental actuator includes a potentiometer to measure the position of the incremental actuator. In some embodiments, the potentiometer is incorporated into the gear train for the incremental actuator. In other embodiments, the potentiometer is external to the incremental actuator (e.g., wired to an external analog input of the actuator). The potentiometer provides feedback to the controller corresponding to the position of the incremental actuator by providing a voltage signal proportional to the position. A position feedback controller converts the voltage signal from the potentiometer to a position value. Furthermore, the position feedback controller auto-calibrates the position values by adjusting the voltage signal limits as each of the actuator endpoints or end stops is reached. The high and low voltage values can be measured and can correspond with the endpoints of the incremental actuator (e.g., from 0% to 100%, where 0% may correspond with a fully closed damper and 100% may correspond with a fully open damper). The position feedback controller may further perform one or more processes based on potentiometer feedback to calculate the current position of the incremental actuator, overcoming the effect of drift.

Advantageously, incremental actuators are more affordable for consumers to purchase and can utilize existing controllers (e.g., modular assemblies for VAV controllers) for ease of installation. By providing an accurate current position of the actuator, the incremental actuator with feedback control can be utilized in air handling unit (AHU) applications and may aid in optimizing AHU fan speed and cold air temperature parameters, to name a few examples. Additional features and advantages of the present invention are described in greater detail below.

Building Management System and HVAC System

Referring now to FIGS. 1-4, an exemplary building management system (BMS) and HVAC system in which the systems and methods of the present invention may be implemented are shown, according to an exemplary embodiment. Referring particularly to FIG. 1, a perspective view of a building 10 is shown. Building 10 is served by a BMS. A 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, for example, a HVAC system, a security system, a lighting system, a fire alerting system, any other system that is capable of managing building functions or devices, or any combination thereof.

The BMS that serves building 10 includes an HVAC system 100. HVAC system 100 may include a plurality of HVAC devices (e.g., heaters, chillers, air handling units, pumps, fans, thermal energy storage, etc.) configured to provide heating, cooling, ventilation, or other services for building 10. For example, HVAC system 100 is shown to include a waterside system 120 and an airside system 130. Waterside system 120 may provide a heated or chilled fluid to an air handling unit of airside system 130. Airside system 130 may use the heated or chilled fluid to heat or cool an airflow provided to building 10. An exemplary waterside system and airside system which may be used in HVAC system 100 are described in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and a rooftop air handling unit (AHU) 106. Waterside system 120 may use boiler 104 and chiller 102 to heat or cool a working fluid (e.g., water, glycol, etc.) and may circulate the working fluid to AHU 106. In various embodiments, the HVAC devices of waterside system 120 may be located in or around building 10 (as shown in FIG. 1) or at an offsite location such as a central plant (e.g., a chiller plant, a steam plant, a heat plant, etc.). The working fluid may be heated in boiler 104 or cooled in chiller 102, depending on whether heating or cooling is required in building 10. Boiler 104 may add heat to the circulated fluid, for example, by burning a combustible material (e.g., natural gas) or using an electric heating element. Chiller 102 may place the circulated fluid in a heat exchange relationship with another fluid (e.g., a refrigerant) in a heat exchanger (e.g., an evaporator) to absorb heat from the circulated fluid. The working fluid from chiller 102 and/or boiler 104 may be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship with an airflow passing through AHU 106 (e.g., via one or more stages of cooling coils and/or heating coils). The airflow may be, for example, outside air, return air from within building 10, or a combination of both. AHU 106 may transfer heat between the airflow and the working fluid to provide heating or cooling for the airflow. For example, AHU 106 may include one or more fans or blowers configured to pass the airflow over or through a heat exchanger containing the working fluid. The working fluid may then return to chiller 102 or boiler 104 via piping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e., the supply airflow) to building 10 via air supply ducts 112 and may provide return air from building 10 to AHU 106 via air return ducts 114. In some embodiments, airside system 130 includes multiple variable air volume (VAV) units 116. For example, airside system 130 is shown to include a separate VAV unit 116 on each floor or zone of building 10. VAV units 116 may include dampers or other flow control elements that can be operated to control an amount of the supply airflow provided to individual zones of building 10. In other embodiments, airside system 130 delivers the supply airflow into one or more zones of building 10 (e.g., via supply ducts 112) without using intermediate VAV units 116 or other flow control elements. AHU 106 may include various sensors (e.g., temperature sensors, pressure sensors, etc.) configured to measure attributes of the supply airflow. AHU 106 may receive input from sensors located within AHU 106 and/or within the building zone and may adjust the flow rate, temperature, or other attributes of the supply airflow through AHU 106 to achieve setpoint conditions for the building zone.

Referring now to FIG. 2, a block diagram of a waterside system 200 is shown, according to an exemplary embodiment. In various embodiments, waterside system 200 may supplement or replace waterside system 120 in HVAC system 100 or may be implemented separate from HVAC system 100. When implemented in HVAC system 100, waterside system 200 may include a subset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller 102, pumps, valves, etc.) and may operate to supply a heated or chilled fluid to AHU 106. The HVAC devices of waterside system 200 may be located within building 10 (e.g., as components of waterside system 120) or at an offsite location such as a central plant.

In FIG. 2, waterside system 200 is shown as a central plant having a plurality of subplants 202-212. Subplants 202-212 are shown to include a heater subplant 202, a heat recovery chiller subplant 204, a chiller subplant 206, a cooling tower subplant 208, a hot thermal energy storage (TES) subplant 210, and a cold thermal energy storage (TES) subplant 212. Subplants 202-212 consume resources (e.g., water, natural gas, electricity, etc.) from utilities to serve the thermal energy loads (e.g., hot water, cold water, heating, cooling, etc.) of a building or campus. For example, heater subplant 202 may be configured to heat water in a hot water loop 214 that circulates the hot water between heater subplant 202 and building 10. Chiller subplant 206 may be configured to chill water in a cold water loop 216 that circulates the cold water between chiller subplant 206 and building 10. Heat recovery chiller subplant 204 may be configured to transfer heat from cold water loop 216 to hot water loop 214 to provide additional heating for the hot water and additional cooling for the cold water. Condenser water loop 218 may absorb heat from the cold water in chiller subplant 206 and reject the absorbed heat in cooling tower subplant 208 or transfer the absorbed heat to hot water loop 214. Hot TES subplant 210 and cold TES subplant 212 may store hot and cold thermal energy, respectively, for subsequent use.

Hot water loop 214 and cold water loop 216 may deliver the heated and/or chilled water to air handlers located on the rooftop of building 10 (e.g., AHU 106) or to individual floors or zones of building 10 (e.g., VAV units 116). The air handlers push air past heat exchangers (e.g., heating coils or cooling coils) through which the water flows to provide heating or cooling for the air. The heated or cooled air may be delivered to individual zones of building 10 to serve the thermal energy loads of building 10. The water then returns to subplants 202-212 to receive further heating or cooling.

Although subplants 202-212 are shown and described as heating and cooling water for circulation to a building, it is understood that any other type of working fluid (e.g., glycol, CO2, etc.) may be used in place of or in addition to water to serve the thermal energy loads. In other embodiments, subplants 202-212 may provide heating and/or cooling directly to the building or campus without requiring an intermediate heat transfer fluid. These and other variations to waterside system 200 are within the teachings of the present invention.

Each of subplants 202-212 may include a variety of equipment configured to facilitate the functions of the subplant. For example, heater subplant 202 is shown to include a plurality of heating elements 220 (e.g., boilers, electric heaters, etc.) configured to add heat to the hot water in hot water loop 214. Heater subplant 202 is also shown to include several pumps 222 and 224 configured to circulate the hot water in hot water loop 214 and to control the flow rate of the hot water through individual heating elements 220. Chiller subplant 206 is shown to include a plurality of chillers 232 configured to remove heat from the cold water in cold water loop 216. Chiller subplant 206 is also shown to include several pumps 234 and 236 configured to circulate the cold water in cold water loop 216 and to control the flow rate of the cold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality of heat recovery heat exchangers 226 (e.g., refrigeration circuits) configured to transfer heat from cold water loop 216 to hot water loop 214. Heat recovery chiller subplant 204 is also shown to include several pumps 228 and 230 configured to circulate the hot water and/or cold water through heat recovery heat exchangers 226 and to control the flow rate of the water through individual heat recovery heat exchangers 226. Cooling tower subplant 208 is shown to include a plurality of cooling towers 238 configured to remove heat from the condenser water in condenser water loop 218. Cooling tower subplant 208 is also shown to include several pumps 240 configured to circulate the condenser water in condenser water loop 218 and to control the flow rate of the condenser water through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configured to store the hot water for later use. Hot TES subplant 210 may also include one or more pumps or valves configured to control the flow rate of the hot water into or out of hot TES tank 242. Cold TES subplant 212 is shown to include cold TES tanks 244 configured to store the cold water for later use. Cold TES subplant 212 may also include one or more pumps or valves configured to control the flow rate of the cold water into or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200 (e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines in waterside system 200 include an isolation valve associated therewith. Isolation valves may be integrated with the pumps or positioned upstream or downstream of the pumps to control the fluid flows in waterside system 200. In various embodiments, waterside system 200 may include more, fewer, or different types of devices and/or subplants based on the particular configuration of waterside system 200 and the types of loads served by waterside system 200.

Referring now to FIG. 3, a block diagram of an airside system 300 is shown, according to an exemplary embodiment. In various embodiments, airside system 300 may supplement or replace airside system 130 in HVAC system 100 or may be implemented separate from HVAC system 100. When implemented in HVAC system 100, airside system 300 may include a subset of the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116, ducts 112-114, fans, dampers, etc.) and may be located in or around building 10. Airside system 300 may operate to heat or cool an airflow provided to building 10 using a heated or chilled fluid provided by waterside system 200.

In FIG. 3, airside system 300 is shown to include an economizer-type air handling unit (AHU) 302. 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 302 may receive return air 304 from building zone 306 via return air duct 308 and may deliver supply air 310 to building zone 306 via supply air duct 312. In some embodiments, AHU 302 is a rooftop unit located on the roof of building 10 (e.g., AHU 106 as shown in FIG. 1) or otherwise positioned to receive both return air 304 and outside air 314. AHU 302 may be configured to operate exhaust air damper 316, mixing damper 318, and outside air damper 320 to control an amount of outside air 314 and return air 304 that combine to form supply air 310. Any return air 304 that does not pass through mixing damper 318 may be exhausted from AHU 302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 may be operated by an actuator. For example, exhaust air damper 316 may be operated by actuator 324, mixing damper 318 may be operated by actuator 326, and outside air damper 320 may be operated by actuator 328. Actuators 324-328 may communicate with an AHU controller 330 via a communications link 332. Actuators 324-328 may receive control signals from AHU controller 330 and may provide feedback signals to AHU controller 330. Feedback signals may 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 324-328), status information, commissioning information, configuration settings, calibration data, and/or other types of information or data that may be collected, stored, or used by actuators 324-328. AHU controller 330 may 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 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil 334, a heating coil 336, and a fan 338 positioned within supply air duct 312. Fan 338 may be configured to force supply air 310 through cooling coil 334 and/or heating coil 336 and provide supply air 310 to building zone 306. AHU controller 330 may communicate with fan 338 via communications link 340 to control a flow rate of supply air 310. In some embodiments, AHU controller 330 controls an amount of heating or cooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from waterside system 200 (e.g., from cold water loop 216) via piping 342 and may return the chilled fluid to waterside system 200 via piping 344. Valve 346 may be positioned along piping 342 or piping 344 to control a flow rate of the chilled fluid through cooling coil 334. In some embodiments, cooling coil 334 includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of cooling applied to supply air 310.

Heating coil 336 may receive a heated fluid from waterside system 200 (e.g., from hot water loop 214) via piping 348 and may return the heated fluid to waterside system 200 via piping 350. Valve 352 may be positioned along piping 348 or piping 350 to control a flow rate of the heated fluid through heating coil 336. In some embodiments, heating coil 336 includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of heating applied to supply air 310.

Each of valves 346 and 352 may be controlled by an actuator. For example, valve 346 may be controlled by actuator 354 and valve 352 may be controlled by actuator 356. Actuators 354-356 may communicate with AHU controller 330 via communications links 358-360. Actuators 354-356 may receive control signals from AHU controller 330 and may provide feedback signals to controller 330. In some embodiments, AHU controller 330 receives a measurement of the supply air temperature from a temperature sensor 362 positioned in supply air duct 312 (e.g., downstream of cooling coil 334 and/or heating coil 336). AHU controller 330 may also receive a measurement of the temperature of building zone 306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 via actuators 354-356 to modulate an amount of heating or cooling provided to supply air 310 (e.g., to achieve a setpoint temperature for supply air 310 or to maintain the temperature of supply air 310 within a setpoint temperature range). The positions of valves 346 and 352 affect the amount of heating or cooling provided to supply air 310 by cooling coil 334 or heating coil 336 and may correlate with the amount of energy consumed to achieve a desired supply air temperature. AHU controller 330 may control the temperature of supply air 310 and/or building zone 306 by activating or deactivating coils 334-336, adjusting a speed of fan 338, or a combination of both.

Still referring to FIG. 3, airside system 300 is shown to include a building management system (BMS) controller 366 and a client device 368. BMS controller 366 may include one or more computer systems (e.g., servers, supervisory controllers, subsystem controllers, etc.) that serve as system level controllers, application or data servers, head nodes, or master controllers for airside system 300, waterside system 200, HVAC system 100, and/or other controllable systems that serve building 10. BMS controller 366 may communicate with multiple downstream building systems or subsystems (e.g., HVAC system 100, a security system, a lighting system, waterside system 200, etc.) via a communications link 370 according to like or disparate protocols (e.g., LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMS controller 366 may be separate (as shown in FIG. 3) or integrated. In an integrated implementation, AHU controller 330 may be a software module configured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMS controller 366 (e.g., commands, setpoints, operating boundaries, etc.) and provides information to BMS controller 366 (e.g., temperature measurements, valve or actuator positions, operating statuses, diagnostics, etc.). For example, AHU controller 330 may provide BMS controller 366 with temperature measurements from temperature sensors 362-364, equipment on/off states, equipment operating capacities, and/or any other information that can be used by BMS controller 366 to monitor or control a variable state or condition within building zone 306.

Client device 368 may include 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 HVAC system 100, its subsystems, and/or devices. Client device 368 may be a computer workstation, a client terminal, a remote or local interface, or any other type of user interface device. Client device 368 may be a stationary terminal or a mobile device. For example, client device 368 may be a desktop computer, a computer server with a user interface, a laptop computer, a tablet, a smartphone, a PDA, or any other type of mobile or non-mobile device. Client device 368 may communicate with BMS controller 366 and/or AHU controller 330 via communications link 372.

Referring now to FIG. 4, a block diagram of a building management system (BMS) 400 is shown, according to an exemplary embodiment. BMS 400 may be implemented in building 10 to automatically monitor and control various building functions. BMS 400 is shown to include BMS controller 366 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. In some embodiments, building subsystems 428 include waterside system 200 and/or airside system 300, as described with reference to FIGS. 2-3.

Each of building subsystems 428 may include any number of devices, controllers, and connections for completing its individual functions and control activities. HVAC subsystem 440 may include many of the same components as HVAC system 100, as described with reference to FIGS. 1-3. For example, HVAC subsystem 440 may include and number of chillers, heaters, handling units, economizers, field controllers, supervisory controllers, actuators, temperature sensors, and/or other devices for controlling the temperature, humidity, airflow, or other variable conditions within building 10. Lighting subsystem 442 may 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 may 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 366 is shown to include a communications interface 407 and a BMS interface 409. Interface 407 may facilitate communications between BMS controller 366 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 366 and/or subsystems 428. Interface 407 may also facilitate communications between BMS controller 366 and client devices 448. BMS interface 409 may facilitate communications between BMS controller 366 and building subsystems 428 (e.g., HVAC, lighting security, lifts, power distribution, business, etc.).

Interfaces 407, 409 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, 409 may 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, 409 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, 409 can include a WiFi transceiver for communicating via a wireless communications network. In another example, one or both of interfaces 407, 409 may include cellular or mobile phone communications transceivers. In one embodiment, communications interface 407 is a power line communications interface and BMS interface 409 is an Ethernet interface. In other embodiments, both communications interface 407 and BMS interface 409 are Ethernet interfaces or are the same Ethernet interface.

Still referring to FIG. 4, BMS controller 366 is shown to include a processing circuit 404 including a processor 406 and memory 408. Processing circuit 404 may be communicably connected to BMS interface 409 and/or communications interface 407 such that processing circuit 404 and the various components thereof can send and receive data via interfaces 407, 409. Processor 406 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 408 (e.g., memory, memory unit, storage device, etc.) may 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 408 may be or include volatile memory or non-volatile memory. Memory 408 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 application. According to an exemplary embodiment, memory 408 is communicably connected to processor 406 via processing circuit 404 and includes computer code for executing (e.g., by processing circuit 404 and/or processor 406) one or more processes described herein.

In some embodiments, BMS controller 366 is implemented within a single computer (e.g., one server, one housing, etc.). In various other embodiments BMS controller 366 may 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 366, in some embodiments, applications 422 and 426 may be hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 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 may 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 400.

Enterprise integration layer 410 may 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 may 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 366. 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 409.

Building subsystem integration layer 420 may be configured to manage communications between BMS controller 366 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 translates communications (e.g., sensor data, input signals, output signals, etc.) across a plurality of multi-vendor/multi-protocol systems.

Demand response layer 414 may 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 may 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 (e.g., hot TES 242, cold TES 244, etc.), or from other sources. Demand response layer 414 may receive inputs from other layers of BMS controller 366 (e.g., building subsystem integration layer 420, integrated control layer 418, etc.). The inputs received from other layers may 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 an exemplary embodiment, 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 may 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 may 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 may 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 may 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 may 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 an exemplary embodiment, 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 may 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 may 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 may 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 may 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 may 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 may 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 may 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 may 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 may 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 may 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 an exemplary embodiment, 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 may 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 400 and the various components thereof. The data generated by building subsystems 428 may 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.

Incremental Actuator with Feedback Control

Referring now to FIGS. 5-7, systems and methods to control an incremental actuator with position feedback are shown, according to some embodiments. In brief overview, FIG. 5 is a block diagram of an incremental actuator interacting with a controller. FIG. 6 is a flow diagram of a process for determining the calculated position of an incremental actuator. FIG. 7 is a flow diagram of a process for controlling an incremental actuator using position feedback from a potentiometer.

Referring now to FIG. 5, a block diagram of an incremental actuator and feedback control system 500 is depicted. In various embodiments, the incremental actuator and feedback control system 500 may be used in the HVAC system of FIG. 1, the waterside system of FIG. 2, the airside system of FIG. 3, or the BMS of FIG. 4 to control a HVAC component. Incremental actuator and feedback control system 500 is shown to include a controller 502 that is communicably coupled to a damper actuator 514 and a temperature sensor 518. In some embodiments, controller 502 can be implemented within a single computer (e.g., one server, one housing, etc.). In other embodiments, controller 502 can be distributed across several servers or computers (e.g., that can exist in distributed locations). Furthermore, applications that are carried out by system 500 may exist outside controller 502 or may be hosted within controller 502 (e.g., within memory).

Damper actuator 514 can be configured as an incremental actuator that drives a damper used within an airside system (e.g., airside system 300, as described in detail with reference to FIG. 3). In other embodiments, the incremental actuator drives other components of an HVAC system, such as a fan, a valve, or a pump. Damper actuator 514 can be connected to controller 502 and potentiometer 516 to communicate information on the position of the incremental actuator. In some embodiments, damper actuator 514 is powered by an AC power supply (e.g., the electric utility of building 10) through a wired interface.

Controller 502 is shown to include various components or circuits, including, but not limited to a zone temperature circuit 504, a close output circuit 506, a position feedback controller circuit 508, and an open output circuit 510. Each of the circuits 504-510 may be a subcomponent of a hardware manager 520. Zone temperature 504 can be configured to store information on temperatures for a zone (i.e., a portion of a building, such as a room or a floor) within controller 502. Furthermore, zone temperature 504 may contain applications that calculate a difference or error value between a desired temperature and a calculated temperature. The desired zone temperature may be received from a supervisory controller, from a thermostat or other user device, or from any other source. In some embodiments, this calculation can then be used to determine whether the zone needs more cold airflow to lower the temperature of the room or if the zone is too cold and needs an increase in temperature. Thus, zone temperature 504 can be used for defining the desired airflow to a zone within a building (e.g., building 10). Temperature sensor 518 can be any type of temperature sensor and can be configured to provide real time information to the actuator controller on temperatures of a zone. In some embodiments, temperature sensor 518 provides data points of air temperature in the zone that include a measured data value indicating the temperature measured by the temperature sensor. The data points from temperature sensor 518 can also include timestamps of when the temperature was measured by the temperature sensor.

Still referring to FIG. 5, close output 506 can be configured to send a signal from the controller to an incremental actuator (e.g., damper actuator 514) to close the actuator a certain amount. Close output 506 may contain information in controller 502 on how much the position of the incremental actuator may close in order to maintain a desired airflow. For example, close output may contain a voltage value that corresponds with a position of damper actuator 514, such that the incremental actuator will continue to close until it reaches that position. Open output 510 can also be configured to send a signal from a controller to an incremental actuator (e.g., damper actuator 514), but instead of closing the position, the signal may provide information to open the position a certain amount. In some embodiments, closing the incremental actuator completely means the actuator has a corresponding position value of 0%, while opening the incremental actuator completely means the actuator has a corresponding position value of 100%.

Potentiometer 516 can be configured to produce a voltage signal that is proportional to the position of the incremental actuator (e.g., 0.0-100% open) and to output the voltage signal to the position feedback controller 508 of the incremental actuator. In some embodiments, potentiometer 516 is attached to a gear train of the incremental actuator in order to provide position feedback to the position feedback controller 508 through an internal connection to an analog to digital converter (ADC). In other embodiments, potentiometer 516 is external to the incremental actuator 514 (e.g., wired to an external analog input of the actuator).

The position feedback controller 508 may be responsible for processing inputs and outputs of the actuator controller. The position feedback controller 508 may also be programmed to execute a hardware manager application that converts voltage values from potentiometer 516 to position values and provides an actual position of the incremental actuator to a control primitive. In some embodiments, the control primitive is a Position Adjust Output (PAO). The control primitive PAO can be responsible for managing the position of the incremental actuator (e.g., damper actuator 514). The hardware manager 520 also can auto-calibrate the position value by adjusting signal limits as each endpoint of the incremental actuator is reached. Further details of this auto-calibration process are included below with reference to FIG. 6. In order to prevent operational failure of the incremental actuator, if the position feedback signal from the potentiometer (e.g., potentiometer 516) is lost, the actuator continues using incremental control without position feedback. The PAO can be configured to establish a connection to the hardware manager 520 and to ask for a valid position feedback signal from the potentiometer. If the position feedback signal exists and is also reliable, the hardware manager 520 can send updates of the position value to a current instance of the PAO object.

Referring now to FIG. 6, a flow diagram of process 600 for determining the calculated position of an incremental actuator is shown, according to some embodiments. Process 600 may be completed by various components of system 500, as described in detail with reference to FIG. 5. In some embodiments, process 600 can be executed in part by an application associated with BMS 400. Process 600 provides an overview of a way to determine the current position of an incremental actuator using feedback from a potentiometer. Process 600 can be used for HVAC systems, such as airside system 300, described in detail with reference to FIG. 3. In some embodiments, process 600 is performed each time the incremental actuator stops.

The calculated position of the incremental actuator allows the HVAC system (e.g., HVAC system 100, described in detail with reference to FIG. 1) to open and close the actuator to satisfy airflow requirements while preventing a drift effect. The drift effect occurs when an actuator is open and closed without attention to the actual position of the actuator. The inattention to the actual position of the actuator results in inaccurate information of the position of the actuator, such that the actual current position of the actuator may vary greatly (“drift”) from the calculated position. By continually updating information on the position of the incremental actuator, process 600 can inhibit drift effects in incremental actuators.

Furthermore, knowledge of the position of the actuator can be useful in newer AHU applications. For example, the actuator position can be used to optimize AHU fan speed and cold air temperatures in HVAC systems. However, the operation of the incremental actuator does not depend on an actuator position feedback signal from the potentiometer being received and the completion of process 600. For example, if the feedback signal from the potentiometer on the actuator position feedback is lost during process 600, the actuator can continue to operate normally using incremental control to meet the airflow requirements.

Process 600 is shown to include receiving a measured voltage from a potentiometer (step 602) and determining if the measured voltage signal from the potentiometer position feedback is less than a low endpoint threshold of the incremental actuator (step 604). In some embodiments, a potentiometer (e.g., potentiometer 516) is configured to produce a voltage signal that is proportional to a position of the incremental actuator. After the actuator controller (e.g., controller 502) receives the position feedback from the potentiometer, the hardware manager 520 processes the input and converts the measured voltage to a corresponding percentage value of the incremental actuator position. For example, if the measured voltage signal is equivalent to the lower endpoint threshold of the actuator position, the hardware manager 520 converts the measured voltage value to a position value of 0%. The value of the position for the incremental actuator may then be stored in memory of the position feedback controller 508 to be used for decisions to open or close the actuator based on zone temperature feedback. The low position endpoint may also be stored in memory in position feedback controller 508.

If the measured voltage from the potentiometer is found to be less than the low endpoint threshold of the incremental actuator, process 600 is shown to set the low endpoint to equal the measured voltage from the potentiometer feedback (step 608). The low endpoint of the actuator position may be stored in position feedback controller 508 and rewritten by controller 502 to equal the position from the most recent measured voltage that is less than the voltage value for the current low endpoint. After the low endpoint threshold has been updated to be the position corresponding to the measured voltage reading from the potentiometer position feedback, process 600 continues to step 610.

However, if the measured voltage from the potentiometer is found to be greater than the low endpoint threshold of the incremental actuator, process 600 is shown to proceed with step 606 before determining if the voltage from the potentiometer is greater than the high endpoint threshold of the incremental actuator (step 610). In some embodiments, controller 502 uses the hardware manager 520 to compare voltages for the most recent potentiometer position feedback value and the low endpoint position value. After determining that the low endpoint position voltage value is still lower than the most recent voltage value measured from position feedback, controller 502 can retain the current low endpoint position (step 606) before continuing to step 610 of process 600.

Process 600 is further shown to include determining if the measured voltage signal from potentiometer position feedback is greater than the high endpoint threshold of the incremental actuator (step 610). If the measured voltage from the potentiometer is found to be greater than the high endpoint of the incremental actuator in step 610, process 600 is shown to proceed with setting the high endpoint threshold of the incremental actuator equal to the value of the measured voltage from feedback (step 614). For example, if the measured voltage signal is equivalent to the higher endpoint of the actuator position, the hardware manager 520 converts the measured voltage value to a position value of 100%. The high endpoint of the actuator position may be stored in position feedback controller 508 and rewritten by controller 502 to equal the position from the most recent potentiometer position feedback that is greater than the voltage value for the current high endpoint threshold. After the high endpoint has been set to the measured voltage reading from the potentiometer position feedback, process 600 continues to step 616 to calculate the position of the incremental actuator. However, if the voltage from potentiometer feedback is found to be lower than the current high endpoint, process 600 is shown to proceed with retaining the current high endpoint (step 612) before calculating the position of the incremental actuator in step 616.

Process 600 is shown to include calculating the position of the incremental actuator from the endpoints of the incremental actuator and measured voltage from potentiometer position feedback (step 616). In some embodiments, step 616 is accomplished by controller 502 and values stored in position feedback controller 508. For example, the hardware manager 520 can compare the voltage values for the low position endpoint and high position endpoint with the measured voltage value from potentiometer 516 to calculate what percentage from the low position endpoint to the high position endpoint the measured voltage value falls. Based on that comparison, controller 502 can calculate the percentage of total distance, from one endpoint to the other endpoint, the position of the incremental actuator is away from the low endpoint position.

Referring now to FIG. 7, a flow diagram of process 700 for controlling the incremental actuator of FIG. 5 using feedback from a potentiometer is shown, according to some embodiments. In some embodiments, process 700 is completed by multiple components of system 500, described with reference to FIG. 5, to improve management of HVAC systems, such as airside system 300. Steps within process 700 may occur after or concurrently with process 600 and may use information produced by process 600 to control the incremental actuator (e.g., damper actuator 514) within the HVAC system.

Process 700 is shown to include determining a desired flow rate based on a zone temperature error (step 702). In various embodiments, process 700 may be performed every time the zone temperature error exceeds a certain threshold (e.g., the zone temperature error exceeds 0.5 degrees), or every time controller 502 receives a new zone temperature setpoint (e.g., a user changes a thermostat setting for a building zone). Controller 502 may be configured to determine a temperature error and a desired flow rate for an airside system using information from a temperature sensor (e.g., temperature sensor 518), which may be stored and processed in zone temperature 504. For example, temperature sensor 518 can be configured to communicate to controller 502 that a zone has a current temperature of 79° F., whereas the desired temperature setpoint of the zone is 72° F. Thus, the temperature error of the zone is 7° F. and controller 502 can be configured to determine that there needs to be an increase in airflow to the zone in order to cool down the temperature.

Process 700 is shown to include calculating a desired damper actuator position based on the desired flow rate setpoint through the damper (step 704). Controller 502 and other components of system 500, described in detail with reference to FIG. 5, can be used in completing step 704. For example, if the temperature of a zone is greater than the desired temperature setpoint, an increase in airflow to the zone may be used to lower the temperature of the zone. Therefore, a controller (e.g., controller 502) can determine that the damper should be opened more in order to permit more air to flow through to the zone and to calculate the actuator position setpoint that would allow the correct amount of air to flow into the zone.

Process 700 is shown to include updating the current position based on how much time has elapsed since the actuator began moving (step 706). If the actuator has not yet begun to move, a controller (e.g., controller 502) can utilize the actuator's last calculated position. If the actuator has begun moving, the controller can calculate the actuator's current position based on the stroke time of the actuator and the commanded actuator position setpoint. For example, if the actuator has a stroke time of 100 seconds to move from a low endpoint or fully closed (i.e., 0% open) position to a high endpoint or fully open (i.e., 100% open) position, if the actuator has been moving for 10 seconds from a fully closed position, the controller will calculate that the actuator is in a 10% open position.

Process 700 is further shown to include determining whether the incremental actuator must begin to move or keep moving in order to reach the actuator position setpoint (step 708). In some embodiments, this is accomplished by comparing the calculated current position, determined in step 706, with the desired position setpoint, determined in step 704 and determining whether the current position is equal to the desired position setpoint. For example, a controller (e.g., controller 502) can use information stored about position feedback relating to the current position and calculate a difference between the current position and the desired position. Then, based on the difference between the current position and the desired position, the controller may determine whether an incremental actuator for the damper (e.g., damper actuator 514) is going to open more, close more, or not make any changes to position. For example, if the desired position is fully open and the current position is only half open, then a movement is required and the controller can send a signal to the damper incremental actuator to increase its position to be more open.

If actuator movement is required, process 700 is shown to include starting the actuator (step 710). In some embodiments, starting the actuator may include a controller (e.g., controller 502) commanding open or close output with remaining onTime (step 710). OnTime can be a variable the controller sends to the incremental actuator that informs the actuator how long to remain “on” while changing position. In some embodiments, the primitive control PAO from the controller (e.g., controller 502) for the incremental damper actuator commands the damper to close a specific amount using close output 506. In other embodiments, the next movement required is to open the damper more, thus the controller commands the incremental actuator to open more than its current position using open output 510. PAO can incrementally move the actuator to its new position, updating its calculated position as it moves based on the elapsed travel time since the actuator began moving. As soon as the onTime is over, the incremental actuator can be considered to be “off” and can stop movement, signaling that movement is no longer necessary in order to change the position. Process 700 can then return to step 702 to determine whether the zone temperature error persists.

If a movement is not required at step 708, process 700 is shown to include stopping the incremental actuator (step 712). The controller of the incremental actuator, in this case an incremental damper actuator (e.g., damper actuator 514), can send a signal to the actuator to stop any further movements to change the position. For example, once the incremental actuator has changed the position to be equal or close to the calculated desired position, the incremental actuator no longer needs to open or close more. In some embodiments, the controller (e.g., controller 502) sends a signal to stop the incremental actuator via a communications interface that is similar to communications interface 407 of the building management system, described in detail with reference to FIG. 4.

Once the actuator is stopped after step 712, process 700 is shown to include setting the current position to a feedback value (step 714). In some embodiments, the current position of the incremental damper actuator (e.g., damper actuator 514), is set equal to the feedback value from a potentiometer (e.g., potentiometer 516) by the Hardware Manager of the position feedback controller 508. Furthermore, the feedback value can be a voltage signal produced by the potentiometer that corresponds with a position of the actuator based on the voltages for two endpoint positions. The hardware manager 520 can overwrite the calculated position of the actuator based on the travel time with the new current position. To update the current position, the PAO can verify that a feedback signal is being received by the controller and that the signal is reliable before the hardware manager 520 sends value updates. The current position of the actuator can be stored in memory within controller 502 to be accessed later by the controller. In some embodiments, controller 502 contains memory that is similar to memory 408 of the BMS controller, described in detail with reference to FIG. 4. After the current position of the actuator is updated and saved, it can be used in applications where knowing the actual position of the incremental actuator (e.g., damper actuator 514) can be beneficial, such as in AHUs to optimize fan speed or optimize cold air temperature.

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 may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may 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 may 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.

Number	Name	Date	Kind
5369342	Rudzewicz	Nov 1994	A
20140277764	Burt	Sep 2014	A1

Number	Date	Country
10256220	Feb 2008	DE
H11348538	Dec 1999	JP
2016020720	Feb 2016	JP

Incremental actuator with feedback control

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Term Extension

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED PATENT APPLICATION

US Referenced Citations (2)

Foreign Referenced Citations (3)

Related Publications (1)

Provisional Applications (1)