CN109358529B - Plug and play universal input actuator - Google Patents

Abstract

An actuator in an HVAC system includes a motor and a drive device driven by the motor. The drive device is connected to the movable HVAC component to drive the movable HVAC component between a plurality of positions. The actuator also includes an input connection configured to receive an input signal and a processing circuit connected to the motor. The processing circuit is configured to determine whether the input signal is an AC voltage signal or a DC voltage signal. The processing circuit is configured to operate the motor using an AC motor control technique in response to determining that the input signal is an AC voltage signal and operate the motor using a DC motor control technique in response to determining that the input signal is a DC voltage signal.

Description

Plug and play universal input actuator

The present application is a divisional application of an invention patent application having an application date of 2016, 03, 17, and a national application number of 201610152813.1, entitled "plug and play universal input actuator".

Cross reference to related patent applications

This application claims benefit and priority from U.S. provisional patent application No.62/135,008 filed 3/18/2015 and U.S. provisional patent application No.62/288,402 filed 1/28/2016, both of which are incorporated herein by reference in their entirety.

Technical Field

The invention relates to a plug and play universal input actuator.

Background

The present disclosure relates generally to actuators in heating, ventilation, or air conditioning (HVAC) systems. HVAC actuators are used to operate a wide variety of HVAC components, such as dampers, fluid valves, air handling units, and other components used in HVAC systems. For example, an actuator may be coupled to a damper in an HVAC system and may be used to actuate the damper between an open position and a closed position. The HVAC actuator typically includes an electric motor and a drive (e.g., axle, drive train, etc.) driven by the electric motor and connected to the HVAC component.

There are a variety of wiring configurations for HVAC actuators, including: proportional ON/OFF, float ON/OFF, and float increment. Depending on the wiring configuration, the HVAC actuator may operate in a specific mode of operation, including: a proportional mode in which the actuator is drivable to an intermediate position between a minimum rotational position and a maximum rotational position based on a value of the input signal; and a float mode, wherein the actuator is drivable between a minimum rotational position and a maximum rotational position based on the presence of the input signal. Existing solutions for selecting the operating mode generally involve an external tool or a DIP switch. However, these solutions are unsatisfactory because they rely on the operator to select the mode of operation, which complicates the installation process and introduces the possibility of errors.

Disclosure of Invention

One embodiment of the present disclosure is an actuator in an HVAC system. The actuator includes a motor and a drive device driven by the motor. A drive device is connected to the movable HVAC component to drive the movable HVAC component between a plurality of positions. The actuator further includes an input connection that receives an input signal. The actuator further includes a processing circuit. The processing circuit is coupled to the motor and determines whether the input signal is an AC voltage signal or a DC voltage signal. In response to determining that the input signal is an AC voltage signal, the processing circuit operates the motor using an AC motor control technique. In response to determining that the input signal is a DC voltage signal, the processing circuit further operates the motor using a DC motor control technique.

In some embodiments, the processing circuitry comprises a controller. In some embodiments, the processing circuit includes an AC voltage detector that provides an AC detection signal to the controller in response to determining that the input signal is an AC voltage signal. In some embodiments, the processing circuit includes a DC voltage detector that provides a DC detection signal to the controller in response to determining that the input signal is a DC voltage signal. In response to receiving the AC detection signal from the AC voltage detector, the controller may operate the motor using AC motor control techniques. In response to receiving the DC detection signal from the DC voltage detector, the controller may operate the motor using a DC motor control technique.

In some embodiments, the input connections have a proportional routing configuration. In some embodiments, the proportional wiring configuration may include a clockwise input connection that receives a DC voltage signal. In some embodiments, the proportional wiring configuration may include a counter-clockwise input connection that receives a steady AC or DC voltage.

In some embodiments, the DC motor control technique includes determining a setpoint position of the drive device proportional to a value of the DC voltage signal. In some embodiments, the DC motor control technique includes operating a motor to drive the drive device to the set point position.

In some embodiments, the input connections have an ON/OFF wiring configuration. In some embodiments, the ON/OFF wiring configuration includes a clockwise input connection. The clockwise input connection may include a clockwise input switch. In some embodiments, the clockwise input connection receives a steady AC or DC voltage when the clockwise input switch is closed, and the clockwise input connection receives zero voltage when the clockwise input switch is open. In some embodiments, the ON/OFF wiring configuration includes a counter-clockwise input connection that receives a stable AC or DC voltage.

In some embodiments, the AC motor control technique is an ON/OFF control technique. In some embodiments, the ON/OFF control technique includes operating the motor to drive the drive device in a clockwise direction to a maximum rotational position when the clockwise input switch is closed and a steady AC or DC voltage is received through the clockwise input connection. In some embodiments, the ON/OFF control technique includes operating the motor to drive the drive device in a counterclockwise direction to the minimum rotational position when the clockwise input switch is open and zero voltage is received through the clockwise input connection.

In some embodiments, the input connections have a floating ON/OFF wiring configuration. In some embodiments, the floating ON/OFF wiring configuration includes a clockwise input connection and a counterclockwise input connection. In some embodiments, the floating ON/OFF wiring configuration can further include a switch that switches between a first position and a second position. In the first position, a stable AC or DC voltage may be provided to the clockwise input connection and zero voltage may be provided to the counterclockwise input connection. In the second position, a zero voltage may be provided to the clockwise input connection and a stable AC or DC voltage may be provided to the counterclockwise input connection.

In some embodiments, the AC motor control technique is a floating ON/OFF control technique. In some embodiments, the floating ON/OFF control technique includes operating the motor to drive the drive device in a clockwise direction to a maximum rotational position when the switch is in the first position and a stable AC or DC voltage is provided to the clockwise input connection. In some embodiments, the floating ON/OFF control technique includes operating the motor to drive the drive device in a counterclockwise direction to a minimum rotational position when the switch is in the second position and zero voltage is provided to the clockwise input connection.

In some embodiments, the input connections have a floating incremental wiring configuration. In some embodiments, the floating incremental wiring configuration includes a clockwise input connection. The clockwise input connection may comprise a clockwise input switch. The clockwise input connection may receive a stable AC or DC voltage when the clockwise input switch is closed and zero voltage when the clockwise input switch is open. In some embodiments, the floating incremental routing configuration includes a counterclockwise input connection. The counterclockwise input connection may include a counterclockwise input switch. The counterclockwise input connection may receive a stable AC or DC voltage when the counterclockwise input switch is closed, and receive a zero voltage when the counterclockwise input switch is open.

In some embodiments, the AC motor control technique is a floating delta control technique. In some embodiments, the floating increment control technique may include operating the motor to drive the drive device in a clockwise direction to a maximum rotational position when the clockwise input switch is closed and a steady AC or DC voltage is provided to the clockwise input connection. In some embodiments, the floating increment control technique may include: the motor is operated to drive the drive device in a counterclockwise direction to a minimum rotational position when the counterclockwise input switch is closed and the clockwise input switch is open to provide a stable AC or DC voltage to the counterclockwise input connection and zero voltage to the clockwise input connection. In some embodiments, the floating increment control technique may include: the motor is prevented from driving the drive device when both the clockwise input switch and the counter-clockwise input switch are open such that zero voltage is provided to both the clockwise input connection and the counter-clockwise input connection.

Another embodiment of the present disclosure is a method of controlling an HVAC actuator. The HVAC actuator includes a motor and a drive driven by the motor and connected to the movable HVAC component. The method includes receiving an input signal at an input connection of an actuator. The method involves: by the processing circuit of the actuator, it is determined whether the input signal is an AC voltage signal or a DC voltage signal. The method includes operating, by a processing circuit, a motor using an AC motor control technique in response to determining that the input signal is an AC voltage signal. The method involves: the motor is operated by the processing circuit using a DC motor control technique in response to determining that the input signal is a DC voltage signal.

In some embodiments, the method includes providing an AC detection signal from the AC voltage detector to the controller in response to determining that the input signal is an AC voltage signal. In some embodiments, the motor is operated using an AC motor control technique in response to the controller receiving an AC detection signal from the AC voltage detector. In some embodiments, the method includes providing a DC detection signal from the DC voltage detector to the controller in response to determining that the input signal is a DC voltage signal. In some embodiments, the motor is operated using a DC motor control technique in response to the controller receiving a DC detection signal from the DC voltage detector.

In some embodiments, receiving the input signal at the input connection of the actuator comprises receiving a DC voltage signal at a clockwise input connection. In some embodiments, receiving the input signal at the input connection of the actuator comprises receiving a steady AC or DC voltage at the counter-clockwise input connection.

In some embodiments, operating the motor using DC motor control techniques includes: a set point position of the drive device proportional to the value of the DC voltage signal is determined. In some embodiments, operating the motor using DC motor control techniques includes operating the motor to drive the drive device to the set point position.

In some embodiments, receiving the input signal at the input connection of the actuator comprises: when the clockwise input switch is closed, a stable AC or DC voltage is received at the clockwise input connection. In some embodiments, receiving the input signal at the input connection of the actuator comprises: when the clockwise input switch is open, zero voltage is received at the clockwise input connection. In some embodiments, receiving the input signal at the input connection of the actuator comprises receiving a steady AC or DC voltage at the counter-clockwise input connection.

In some embodiments, operating the motor using AC motor control techniques includes: when the clockwise input switch is closed and a steady AC or DC voltage is received through the clockwise input connection, the motor is operated to drive the drive device in a clockwise direction to a maximum rotational position. In some embodiments, operating the motor using AC motor control techniques includes: when the clockwise input switch is open and zero voltage is received through the clockwise input connection, the motor is operated to drive the drive device in a counterclockwise direction to a minimum rotational position.

In some embodiments, receiving the input signal at the input connection of the actuator comprises: when the switch is switched to the first position, a stable AC or DC voltage is received at the clockwise input connection and a zero voltage is received at the counterclockwise input connection. In some embodiments, receiving the input signal at the input connection of the actuator comprises: when the switch is switched to the second position, a zero voltage is received at the clockwise input connection and a stable AC or DC voltage is received at the counterclockwise input connection.

In some embodiments, operating the motor using AC motor control techniques includes: when the switch is in the first position and a stable AC or DC voltage is provided to the clockwise input connection, the motor is operated to drive the drive device in a clockwise direction to a maximum rotational position. In some embodiments, operating the motor using AC motor control techniques includes: when the switch is in the second position and zero voltage is provided to the clockwise input connection, the motor is operated to drive the drive device in a counterclockwise direction to a minimum rotational position.

In some embodiments, receiving the input signal at the input connection of the actuator comprises: a stable AC or DC voltage is received at the clockwise input connection when the clockwise input switch is closed and a zero voltage is received at the clockwise input connection when the clockwise input switch is open. In some embodiments, receiving the input signal at the input connection of the actuator comprises: a stable AC or DC voltage is received at the counterclockwise input connection when the counterclockwise input switch is closed and a zero voltage is received at the counterclockwise input connection when the counterclockwise input switch is open.

In some embodiments, operating the motor using AC motor control techniques includes: when the clockwise input switch is closed and a stable AC or DC voltage is provided to the clockwise input connection, the motor is operated to drive the drive device in a clockwise direction to a maximum rotational position. In some embodiments, operating the motor using AC motor control techniques includes: the motor is operated to drive the drive device in a counterclockwise direction to a minimum rotational position when the counterclockwise input switch is closed and the clockwise input switch is open such that a stable AC or DC voltage is provided to the counterclockwise input connection and zero voltage is provided to the clockwise input connection. In some embodiments, operating the motor using AC motor control techniques includes: the motor is prevented from driving the drive device when both the clockwise input switch and the counter-clockwise input switch are open such that zero voltage is provided to both the clockwise input connection and the counter-clockwise input connection.

Those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting. Other aspects, novel features, and advantages of the devices and/or processes described herein, as defined solely by the claims, will become apparent from the detailed description set forth herein when considered in conjunction with the accompanying drawings.

Drawings

Fig. 1 is a perspective view of a building having a heating, ventilation, or air conditioning (HVAC) system and a Building Management System (BMS), according to some embodiments.

FIG. 2 is a schematic illustration of a waterside system that may be used to support the HVAC system of FIG. 1 according to some embodiments.

FIG. 3 is a block diagram of an air side system that may be used as part of the HVAC system of FIG. 1 in accordance with some embodiments.

Fig. 4 is a block diagram of a BMS that may be implemented in the building of fig. 1, in accordance with some embodiments.

Fig. 5 is a schematic perspective view of an actuator that may be used in the HVAC system of fig. 1, the water side system of fig. 2, the air side system of fig. 3, or the BMS system of fig. 4 to control an HVAC component, according to some embodiments.

Fig. 6 is a schematic top view of the actuator shown in fig. 5 according to some embodiments.

Fig. 7 is a schematic bottom view of the actuator shown in fig. 5 according to some embodiments.

Fig. 8-11 are detailed wiring diagrams of the actuator shown in fig. 5 according to some embodiments.

FIG. 12 is a block diagram of the actuator shown in FIG. 5 according to some embodiments.

FIG. 13 is a circuit diagram illustrating a universal input detector that may be used in the actuator shown in FIG. 5 according to some embodiments.

14-17 are graphs showing properties of a correction voltage signal, a DC detection signal, and an AC detection signal when various clockwise input signals and counterclockwise signals are provided to a processing circuit according to some embodiments.

FIG. 18 is a flow diagram of general input detection that may be performed by the actuator shown in FIG. 5 according to some embodiments.

Fig. 19 is a table describing desired actuator operation when the processing circuit does not include an AC input detector and a DC input detector, in accordance with some embodiments.

Fig. 20 is a table describing desired actuator operation when the processing circuit includes an AC input detector and a DC input detector, in accordance with some embodiments.

Detailed Description

Summary of the invention

Referring generally to the drawings, there is shown an HVAC actuator having the capability of receiving a general purpose input, in accordance with some embodiments. The actuator may be a windshield actuator, a valve actuator, a fan actuator, a pump actuator, or any other type of actuator that may be used in an HVAC system. The actuator includes: the drive device includes an input connection configured to receive an input signal (e.g., from a controller), a motor, a processing circuit configured to control the motor based on the input signal, and a drive device driven by the motor. The drive device may be connected to a movable HVAC component (e.g., a damper, a valve, etc.) and may be configured to move the HVAC component through a range of multiple positions.

The actuator may receive a number of different types of input signals, such as an AC voltage signal and a DC voltage signal. In some embodiments, the actuator automatically determines whether the input signal is an AC voltage signal or a DC voltage signal. The actuator can operate the motor using an AC motor control technique (e.g., ON/OFF control, floating incremental control, etc.) in response to determining that the input signal is an AC voltage signal. Similarly, the actuator can operate the motor using a DC motor control technique (e.g., proportional control) in response to determining that the input signal is a DC voltage signal. The actuator can automatically select an operating mode based on the type of input signal received without the need for an external configuration tool, a user-operable mode selection switch, or a user-operable DIP switch. Additional features and advantages of the HVAC actuator will be described in greater detail below.

Building management system and HVAC system

Referring now to fig. 1-4, a Building Management System (BMS) and HVAC system are shown in which the systems and methods of the present disclosure can be implemented, according to some embodiments. Referring specifically to fig. 1, a perspective view of a building 10 is shown. Building 10 is serviced by a BMS. A BMS is generally a system of devices configured to control, monitor and manage equipment within or around a building or zone of a building. The BMS may include, for example, HVAC systems, security systems, lighting systems, fire alarm systems, any other system capable of managing building functions or devices, or any combination thereof.

The BMS that services the building 10 includes an HVAC system 100. HVAC system 100 may include a plurality of HVAC devices (e.g., heaters, coolers, air handling units, pumps, fans, thermal energy storage, etc.) configured to provide heating, cooling, ventilation, or other services to building 10. For example, the HVAC system 100 is illustrated as including a waterside system 120 and an air-side system 130. The waterside system 120 may provide heated or cooled fluid to the air handling units of the air-side system 130. The air side system 130 may use the heated or cooled fluid to heat or cool the air flow provided to the building 10. The water side system and the air side system that may be used in the HVAC system 100 will be described in more detail in conjunction with fig. 2-3.

The HVAC system 100 is illustrated as including a chiller 102, a boiler 104, and a rooftop Air Handling Unit (AHU) 106. The waterside system 120 may use the boiler 104 and the cooler 102 to heat or cool a working fluid (e.g., water, glycol, etc.) and may circulate the working fluid to the AHU 106. In various embodiments, the HVAC devices of the waterside system 120 may be located within or around the building 10 (as shown in fig. 1), or at a displaced location such as a central facility (e.g., a chiller facility, a steam facility, a heating facility, etc.). Depending on whether heating or cooling is desired in building 10, the working fluid may be heated in boiler 104 or cooled in cooler 102. The boiler 104 may apply heat to the circulating fluid, for example, by burning combustible materials (e.g., natural gas) or using electric heating elements. The cooler 102 may place the circulating fluid in heat exchange relationship with another fluid (e.g., a refrigerant) in a heat exchanger (e.g., an evaporator) to absorb heat from the circulating fluid. The working fluid from the cooler 102 and/or boiler 104 may be delivered to the AHU 106 via conduit 108.

AHU 106 enables the working fluid to be placed in a heat exchange relationship with the air flow through AHU 106 (e.g., via one or more stages of cooling coils and/or heating coils). The air flow may be, for example, outdoor air, return air from within building 10, or a combination of both. AHU 106 may transfer heat between the air stream and the working fluid to provide heating or cooling of the air stream. For example, AHU 106 may include one or more fans or blowers configured to pass a flow of air to or through a heat exchanger containing a working fluid. The working fluid may then be returned to the cooler 102 or the boiler 104 via conduit 110.

Air side system 130 may deliver an air flow (e.g., a supply air flow) provided by AHU 106 to building 10 via air supply duct 112, and may provide return air from building 10 to AHU 106 via air return duct 114. In some embodiments, the air-side system 130 includes a plurality of Variable Air Volume (VAV) units 116. For example, the air side system 130 is illustrated as including a separate VAV unit 116 on each floor or zone of the building 10. The VAV unit 116 may include a wind deflector or other flow control component that is operable to control the supply of air flow to various areas of the building 10. In other embodiments, the air-side system 130 delivers the supply air flow (e.g., via the supply duct 112) into one or more areas of the building 10 without the use of an intermediate VAV unit 116 or other flow control component. AHU 106 may include various sensors (e.g., temperature sensors, pressure sensors, etc.) configured to measure properties of the supply air flow. AHU 106 may receive input from sensors located in AHU 106 and/or in the building area and may adjust the flow rate, temperature, or other attribute of the supply airflow through AHU 106 to achieve a setpoint condition for the building area.

Referring now to fig. 2, a block diagram of a waterside system 200 according to some embodiments is shown. In various embodiments, the waterside system 200 may be in addition to or in place of the waterside system 120 in the HVAC system 100, or may be implemented independently of the HVAC system 100. When implemented in the HVAC system 100, the waterside system 200 may include a subset of the HVAC devices (e.g., boiler 104, chiller 102, pumps, valves, etc.) in the HVAC system 100 and may operate to supply heated or cooled fluid to the AHU 106. The HVAC devices of waterside system 200 may be located within building 10 (e.g., as a component of waterside system 120) or at a displaced location such as a central facility.

In FIG. 2, the waterside system 200 is illustrated as a central facility having a plurality of sub-facilities 202 and 212. The sub-facilities 202-212 are illustrated as including a heater sub-facility 202, a heat recovery chiller sub-facility 204, a chiller sub-facility 206, a cooling tower sub-facility 208, a Thermal Energy Storage (TES) sub-facility 210, and a cold Thermal Energy Storage (TES) sub-facility 212. The sub-facility 202-212 consumes resources (e.g., water, natural gas, electricity, etc.) from the utility to service the thermal energy load (e.g., hot water, cold water, heating, cooling, etc.) of the building or campus. For example, the heater sub-facility 202 may be configured to heat water in a hot water loop 214, the hot water loop 214 circulating hot water between the heater sub-facility 202 and the building 10. The chiller sub-facility 206 may be configured to cool water in a cold water loop 216 that circulates the cold water between the chiller sub-facility 206 and the building 10. The heat recovery chiller sub-facility 204 may be configured to transfer heat from the cold water loop 216 to the hot water loop 214 to provide additional heating for the hot water and additional cooling for the cold water. The condensate water loop 218 may absorb heat from the cold water in the chiller sub-facility 206 and reject the absorbed heat in the cooling tower sub-facility 208, or transfer the absorbed heat to the hot water loop 214. The hot TES sub-facility 210 and cold TES sub-facility 212 can store hot and cold thermal energy, respectively, for later use.

Hot water loop 214 and cold water loop 216 can deliver heated and/or cooled water to an air handler located on the roof of building 10 (e.g., AHU 106) or to various floors or zones of building 10 (e.g., VAV units 116). The air handler pushes the air through a heat exchanger (e.g., a heating coil or a cooling coil) through which water flows to provide heating or cooling of the air. Heated or cooled air may be delivered to various areas of building 10 to service the thermal energy load of building 10. The water then flows back to sub-facility 202 and 212 to receive further heating or cooling.

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

Each of the sub-facilities 202, 212 may include a variety of devices configured to facilitate sub-facility functionality. For example, the heater sub-facility 202 is illustrated as including a plurality of heating components 220 (e.g., boilers, electric heaters, etc.), which heating components 220 are configured to heat hot water in the hot water loop 214. The heater sub-facility 202 is also illustrated as including several pumps 222, 224 configured to circulate hot water in the hot water loop 214 and control the flow rate of the hot water through each heating element 220. The chiller sub-facility 206 is illustrated as including a plurality of chillers 232 configured to remove heat from the cold water in the cold water loop 216. The chiller sub-facility 206 is also illustrated as including a number of pumps 234, 236 configured to circulate cold water in the cold water loop 216 and control the flow rate of the cold water through each chiller 232.

The heat recovery chiller sub-facility 204 is illustrated as including a plurality of heat recovery heat exchangers 226 (e.g., refrigeration circuits) configured to transfer heat from the cold water loop 216 to the hot water loop 214. The heat recovery chiller sub-facility 204 is also illustrated as including a number of pumps 228, 230 configured to circulate hot and/or cold water through the heat recovery heat exchangers 226 and to control the flow rate of water through each heat recovery heat exchanger 226. The cooling tower sub-facility 208 is illustrated as including a plurality of cooling towers 238 configured to remove heat from the condensate in the condensate loop 218. The cooling tower sub-facility 208 is also illustrated as including a number of pumps 240, the pumps 240 configured to circulate the condensate within the condensate loop 218 and to control the flow rate of the condensate through each cooling tower 238.

The hot TES sub-facility 210 is illustrated as including a hot TES water tank 242 that is configured to store hot water for later use. The hot TES sub-facility 210 may also include one or more pumps or valves configured to control the flow rate of hot water into or out of the hot TES water tank 242. The cold TES sub-facility 212 is illustrated as including a cold TES water tank 244 configured to store cold water for later use. The cold TES sub-facility 212 may also include one or more pumps or valves configured to control the flow rate of cold water into or out of the cold TES water tank 244.

In some embodiments, one or more of the pumps (e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) in the waterside system 200 or the lines in the waterside system 200 includes an isolation valve associated therewith. The isolation valve may be integral with the pump or located upstream or downstream of the pump to control fluid flow in the waterside system 200. In various embodiments, the waterside system 200 may include more, fewer, or different types of devices and/or sub-facilities based on the particular configuration of the waterside system 200 and the type of load being serviced by the waterside system 200.

Referring now to fig. 3, a block diagram of an air-side system 300 is shown, according to some embodiments. In various embodiments, the air-side system 300 can be in addition to or in place of the air-side system 130 in the HVAC system 100, or can be implemented independently of the HVAC system 100. When implemented in the HVAC system 100, the air side system 300 may comprise a subset of the HVAC equipment (e.g., AHU 106, VAV unit 116, duct 112, fan, wind screen, etc.) in the HVAC system 100 and may be located within or around the building 10. The air side system 300 is operable to heat or cool the air flow provided to the building 10 using the heated or cooled fluid provided by the water side system 200.

In fig. 3, an air-side system 300 is illustrated as including an economized Air Handling Unit (AHU) 302. The economized AHU varies the amount of outside air and return air used by the air handling unit to heat or cool. For example, AHU 302 may receive return air 304 from building area 306 via return air conduit 308 and may deliver supply air 310 to building area 306 via supply air conduit 312. In some embodiments, AHU 302 is a rooftop unit that is located on the roof of building 10 (e.g., AHU 106 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 baffle 316, hybrid air baffle 318, and external air baffle 320 to control the amount of external air 314 and return air 304, which external air 314 and return air 304 combine to form supply air 310. Any return air 304 that does not flow through hybrid air deflector 318 may be expelled from AHU 302 through exhaust air deflector 316 as exhaust air 322.

Each of the air deflectors 316-320 may be operated by an actuator. For example, exhaust air flap 316 may be operated by actuator 324, hybrid air flap 318 may be operated by actuator 326, and external air flap 320 may be operated by actuator 328. Actuators 324-328 may communicate with AHU controller 330 via communication link 332. Actuators 324-328 may receive control signals from AHU controller 330 and may provide feedback signals to AHU controller 330. The feedback signal may include, for example, an indication of the current actuator or windshield position, an amount of torque or force applied by the actuator, diagnostic information (e.g., results of diagnostic tests performed by the actuator 324 and 328), status information, delegation information, configuration settings, calibration data, and/or other types of information or data that can be collected, stored, or used by the actuator 324 and 328. The AHU controller 330 may be an economic controller configured to control the actuator 324 and 328 using one or more control algorithms (e.g., a state-based algorithm, an Extremum Seeking Control (ESC) algorithm, a proportional-integral (PI) control algorithm, a proportional-integral-derivative (PID) control algorithm, a Model Predictive Control (MPC) algorithm, a feedback control algorithm, etc.).

Still referring to fig. 3, AHU 302 is illustrated as including cooling coil 334, heating coil 336, and 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 area 306. AHU controller 330 may communicate with fan 338 via communication link 340 to control the flow rate of supply air 310. In some embodiments, AHU controller 330 controls the amount of heating or cooling applied to supply air 310 by adjusting the speed of fan 338.

The cooling coil 334 may receive cooled fluid from the waterside system 200 (e.g., from the cold water loop 216) via a conduit 342 and may return the cooled fluid to the waterside system 200 via a conduit 344. A valve 346 may be positioned along conduit 342 or conduit 344 to control the flow rate of the cooled 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 adjust the amount of cooling applied to supply air 310.

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

Each of the valves 346, 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 and 356 may communicate with AHU controller 330 via communication links 358 and 360. Actuators 354 and 356 may receive control signals from AHU controller 330 and may provide feedback signals to controller 330. In some embodiments, AHU controller 330 receives measurements of the supply air temperature from a temperature sensor 362 positioned in supply air conduit 312 (e.g., downstream of cooling coil 334 and/or heating coil 336). AHU controller 330 may also receive measurements of the temperature of building area 306 from temperature sensors 364 located within building area 306.

In some embodiments, AHU controller 330 operates valves 346, 352 via actuators 354 and 356 to adjust the amount of heating or cooling provided to supply air 310 (e.g., to reach a set point temperature of supply air 310 or to maintain the temperature of supply air 310 within a set point temperature range). The position of valves 346, 352 affects the amount of heating or cooling provided to supply air 310 by cooling coil 334 or heating coil 336 and may be related to the energy consumed to achieve a desired supply air temperature. AHU controller 330 may control the temperature of supply air 310 and/or building area 306 by activating or deactivating coils 334-336, by adjusting the speed of fan 338, or by a combination of both.

Still referring to fig. 3, air side system 300 is illustrated as including 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 function as system level controllers, application or data servers, head nodes, or host controllers for air side system 300, water side system 200, HVAC system 100, and/or other controllable systems that service building 10. BMS controller 366 may communicate with a plurality of downstream building systems or subsystems (e.g., HVAC system 100, security system, lighting system, waterside system 200, etc.) via communication links 370 according to the same or different 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 embodiment, AHU controller 330 may be a software module configured to be executed by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information (e.g., commands, set points, operational boundaries, etc.) from BMS controller 366 and provides information (e.g., temperature measurements, valve or actuator positions, operational status, diagnostics, etc.) to BMS controller 366. For example, AHU controller 330 may provide BMS controller 366 with temperature measurements from temperature sensors 362-364, device on/off status, device operating capabilities, and/or any other information that may be used by BMS controller 366 to monitor or control variable states or conditions within building area 306.

The client device 368 may include one or more human or client interfaces (e.g., graphical user interfaces, reporting interfaces, text-based computer interfaces, client-oriented web services, web servers that provide pages to web clients, etc.) for controlling, browsing, or otherwise interacting with the HVAC system 100, its subsystems, and/or devices. Client device 368 may be a computer workstation, a client, a remote or local interface, or any other type of user interface device. Client device 368 may be a fixed terminal or a mobile device. For example, client device 368 may be a desktop, a computer server with a user interface, a laptop, 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 communication link 372.

Referring now to fig. 4, a block diagram of a Building Management System (BMS)400 is shown, in accordance with some embodiments. BMS 400 may be implemented in building 10 to automatically monitor and control various building functions. BMS 400 is illustrated as including BMS controller 366 and a plurality of building subsystems 428. Building subsystems 428 are illustrated as including a building electrical subsystem 434, an Information Communication Technology (ICT) subsystem 436, a safety subsystem 438, an HVAC subsystem 440, a lighting subsystem 442, a lift/escalator subsystem 432, and a fire safety subsystem 430. In various embodiments, building subsystems 428 may include fewer, additional, or alternative subsystems. For example, building subsystems 428 may additionally or alternatively include a refrigeration subsystem, an advertising or signage subsystem, a cooking subsystem, a vending subsystem, a printer or copy services subsystem, or any other type of building subsystem that uses controllable devices 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 fig. 2-3.

Each of building subsystems 428 can include any number of devices, controllers, and connections to perform its respective functions and control activities. The HVAC subsystem 440 may include many of the same components as the HVAC system 100, as described with reference to fig. 1-3. For example, HVAC subsystem 440 may include a number of chillers, heaters, processing units, economizers, field controllers, supervisory controllers, actuators, temperature sensors, and/or other devices for controlling temperature, humidity, air flow, 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. The 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 illustrated as including communication interface 407 and BMS interface 409. Interface 407 may facilitate communication between BMS controller 366 and external applications (e.g., monitoring and reporting application 422, enterprise control application 426, remote systems and applications 444, applications resident on client device 448, etc.) to allow for user control, monitoring, and adjustment of BMS controller 366 and/or subsystems 428. Interface 407 may also facilitate communication between BMS controller 366 and client device 448. BMS interface 409 may facilitate communication between BMS controller 366 and building subsystems 428 (e.g., HVAC, lighting security, elevator, power distribution, business, etc.).

Interfaces 407, 409 may be or include wired or wireless communication interfaces (e.g., sockets, antennas, transmitters, receivers, transceivers, line terminals, etc.) for performing 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 communication network 446 (e.g., a WAN, the internet, a cellular network, etc.). For example, the interfaces 407, 409 may include ethernet cards and ports for sending and receiving data via an ethernet-based communication link or network. In another example, interfaces 407, 409 may include WiFi transceivers to communicate via a wireless communication network. In another example, one or both of interfaces 407, 409 may include a cellular or mobile telephone communication transceiver. In one embodiment, communication interface 407 is a power line communication interface and BMS interface 409 is an ethernet interface. In other embodiments, both communication interface 407 and BMS interface 409 are ethernet interfaces or the same ethernet interface.

Still referring to fig. 4, BMS controller 366 is illustrated as including processing circuit 404, with processing circuit 404 including processor 406 and memory 408. Processing circuit 404 is communicatively connected to BMS interface 409 and/or communication interface 407 to enable processing circuit 404 and its various components to send and receive data via interfaces 407, 409. Processor 406 may be implemented as a general purpose processor, an Application Specific Integrated Circuit (ASIC), one or more Field Programmable Gate Arrays (FPGAs), a set of processing devices, or other suitable electronic processing device.

Memory 408 (e.g., memory units, storage devices, etc.) may include one or more devices (e.g., RAM, ROM, flash memory, hard disk storage, etc.) for storing data and/or computer code to complete or facilitate the various processes, layers, and modules described herein. Memory 408 can 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 herein. According to some embodiments, memory 408 is communicatively connected to processor 406 via processing circuitry 404 and includes computer code for performing (e.g., by processing circuitry 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 body, etc.). In various other embodiments, BMS controller 366 may be distributed across multiple servers or computers (e.g., can reside at distributed locations). Further, although fig. 4 illustrates applications 422, 426 as residing external to BMS controller 366, in some embodiments applications 422, 426 may be hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is illustrated as including an enterprise integration layer 410, an automatic measurement and verification (AM & V) layer 412, a Demand Response (DR) layer 414, a Fault Detection and Diagnosis (FDD) layer 416, an integration control layer 418, and a building subsystem integration layer 420. Tier 410-420 may be configured to receive input from building subsystems 428 and other data sources, determine an optimal control action for building subsystems 428 based on the input, generate control signals based on the optimal control action, and provide the generated control signals to building subsystems 428. The following figures describe some of the general functions performed by each of the layers 410-420 in BMS 400.

The enterprise integration layer 410 may be configured to provide services for client or local applications through information and services to support a variety of enterprise-level applications. For example, the enterprise control application 426 may be configured to provide subsystem span (spanning) control to a Graphical User Interface (GUI) or any number of enterprise-level business applications (e.g., accounting systems, subscriber identification systems, etc.). Enterprise control application 426 may additionally or alternatively be configured to provide a configuration GUI to configure BMS controller 366. In still other embodiments, enterprise control application 426 may work with layer 410 and 420 to optimize building performance (e.g., efficiency, energy, comfort, or security) 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 subsystem 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 communication between building subsystems 428. The building subsystem integration layer 420 translates communications (e.g., sensor data, input signals, output signals, etc.) between multiple multi-vendor/multi-protocol systems.

Demand response layer 414 may be configured to optimize resource usage (e.g., electricity, gas, water, etc.) and/or the financial cost of such resource usage in response to satisfying the demand of building 10. Optimization may be based on time of use prices, curtailment signals, energy availability, or other data received from the utility provider, distributed energy generation system 424, from energy storage devices 427 (e.g., hot TES 242, cold TES 244, etc.), or from other sources. Demand response layer 414 may receive input from other layers of BMS controller 366 (e.g., building subsystem integration layer 420, integration control layer 418, etc.). The inputs received from the other layers may include environmental inputs or sensor inputs such as temperature, carbon dioxide levels, relative humidity levels, air quality sensor outputs, occupancy sensor outputs, room arrangements, and the like. The inputs may also include the following: such as electricity (e.g., in kWh), thermal load measurements, pricing information, plan pricing, placido pricing, curtailment signals from utilities, and so forth.

According to some embodiments, the demand response layer 414 includes control logic that is responsive to the data and signals it receives. These responses may include communicating with control algorithms in the integrated control layer 418, changing control strategies, changing set points, or activating/deactivating building devices or subsystems in a controlled manner. The demand response layer 414 may also include control logic configured to determine when to utilize the stored energy. For example, demand response layer 414 may determine to begin using energy from energy storage device 427 just prior to the beginning of a peak energy usage period.

In some embodiments, the demand response layer 414 includes a control module configured to actively initiate a control action (e.g., automatically changing a set point) that minimizes energy costs based on one or more inputs representative of demand or based on demand (e.g., price, curtailment signal, demand level, etc.). In some embodiments, the demand response layer 414 uses plant models to determine an optimal set of control actions. The equipment models may include, for example, thermodynamic models describing inputs, outputs, and/or functions performed by various sets of building equipment. The equipment model may represent a collection of building equipment (e.g., sub-facilities, chiller arrays, etc.) or individual devices (e.g., individual chillers, heaters, pumps, etc.).

The demand response layer 414 may further include or utilize one or more demand response policy definitions (e.g., databases, XML files, etc.). The policy definition may be edited or adjusted by the user (e.g., via a graphical user interface) such that the control actions initiated in response to the demand input may be customized for the user's application, the desired comfort level, the particular building equipment, or based on other factors. For example, the demand response strategy definition may specify which device may be turned on or off in response to a particular demand input, how long a system or piece of equipment should be turned off, what set points may be changed, what set point adjustment ranges are allowable, how long a high demand set point is maintained before returning to a normally planned set point, how close to an approximate capacity limit, which device models are utilized, energy conversion rates (e.g., maximum rates, alarm rates, other rate boundary information, etc.) into/out of the energy storage (e.g., thermal storage tanks, battery packs, etc.), and when to dispatch primary energy production (e.g., via fuel cells, motor generator sets, etc.).

Integration control layer 418 may be configured to use data inputs or outputs of building subsystem integration layer 420 and/or demand response layer 414 to make control decisions. Due to the subsystem integration provided by building subsystem integration layer 420, integration control layer 418 may integrate the control activities of subsystems 428 such that subsystems 428 act as a single integrated super system. In some embodiments, integrated control layer 418 includes control logic that uses inputs and outputs from multiple building subsystems to provide greater comfort and energy savings than individual subsystems can provide alone. For example, integrated control layer 418 may be configured to use input from a first subsystem to make energy saving control decisions for a second subsystem. The results of these decisions may be passed back to the building subsystem integration layer 420.

The integrated control layer 418 is illustrated logically below the demand response layer 414. Integrated control layer 418 may be configured to increase 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. Such a configuration can advantageously reduce disruptive demand response behavior relative to conventional systems. For example, the integrated control layer 418 may be configured to ensure that an upward adjustment of the demand response driven set point to the cooling 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 the space) that would result in a greater total building energy usage than the energy saved at the chiller side.

The integral control layer 418 may be configured to provide feedback to the demand response layer 414 so that the demand response layer 414 checks that the constraints (e.g., temperature, lighting level, etc.) are properly maintained even when the requested derating is in progress. Constraints may also include set points or sensed boundaries associated with safety, equipment operating limits and performance, comfort, fire regulations, electrical regulations, energy usage regulations, and the like. An integrated control layer 418 is also logically located below the fault detection and diagnostic layer 416 and the automatic measurement and verification layer 412. Integral control layer 418 may be configured to provide calculated inputs (e.g., sets) to those higher levels based on outputs from more than one building subsystem.

Automatic measurement and verification (AM & V) layer 412 may be configured to verify that the control strategy commanded by integrated control layer 418 or demand response layer 414 is working properly (e.g., using data summarized by AM & V layer 412, integrated control layer 418, building subsystem integration layer 420, FDD layer 416, or other layer). The calculations made by the AM & V layer 412 may be based on the building system energy usage model and/or the equipment models of the individual BMS devices or subsystems. For example, AM & V layer 412 may compare the output predicted by the model to the actual output from building subsystems 428 to determine the accuracy of the model.

Fault Detection and Diagnostic (FDD) layer 416 may be configured to provide persistent fault detection for building subsystems 428, building subsystem devices (e.g., building equipment), and control algorithms used by demand response layer 414 and integrated control layer 418. FDD layer 416 may receive data input from integrated control layer 418, directly from one or more building subsystems or devices, or from another data source. FDD layer 416 is able to automatically diagnose and respond to detected faults. The response to the detected or diagnosed fault may include providing an alert message to a user, a maintenance scheduling system, or a control algorithm configured to attempt to fix or contingent on the fault.

FDD layer 416 may be configured to output a specific identification of the component or cause of the fault (e.g., release of the windshield linkages) using detailed subsystem inputs available at building subsystem integration layer 420. In other embodiments, FDD layer 416 is configured to provide a "failure" event to integrated control layer 418, which integrated control layer 418 executes control policies and policies in response to the received failure event. According to some embodiments, FDD layer 416 (or guidelines executed by the integrated control engine or business rules engine) can shut down the system or direct failed devices or control activities around the system to reduce energy waste, extend equipment life, or ensure proper control response.

FDD layer 416 may be configured to store or access a variety of different system data stores (or data points of real-time data). FDD layer 416 may use some of the contents of the data store to identify faults at the device level (e.g., a particular cooler, a particular AHU, a particular end unit, etc.) and other contents to identify faults at the component or subsystem level. For example, building subsystems 428 may generate time (i.e., time series) data that indicates the performance of BMS 400 and its various components. The data generated by building subsystems 428 may include measured or calculated values that exhibit statistical characteristics and provide information on how to perform a corresponding system or process (e.g., temperature control process, flow control process, etc.) with error from its set point. These processes may be checked by FDD layer 416 to reveal when the system begins to degrade in performance and to alert the user to fix the fault before it becomes more severe.

Universal input actuator

Referring now to fig. 5-7, an actuator 500 for an HVAC system is shown, according to some embodiments. In some embodiments, the actuator 500 may be used in the HVAC system 100, the waterside system 200, the airside system 300, or the BMS 400, as described with respect to fig. 1-4. For example, the actuator 500 may be a windshield actuator, a valve actuator, a fan actuator, a pump actuator, or any other type of actuator that can be used in an HVAC system or BMS. In various embodiments, the actuator 500 may be a linear actuator (e.g., a linear proportional actuator), a non-linear actuator, an elastic return actuator, or a non-elastic return actuator.

The actuator 500 is illustrated as including a housing 502, the housing 502 having a front side 504 (i.e., side a), a rear side 506 (fig. 7) opposite the front side 504 (i.e., side B), and a bottom 508. The housing 502 may contain the mechanical and processing components of the actuator 500. The internal components of the actuator 500 will be described in more detail below in conjunction with fig. 12 and 13.

The actuator 500 is illustrated as including a drive device 510. The drive device 510 may be a drive mechanism, an axle, or other device configured to drive or effect movement of an HVAC system component. For example, the drive 510 may be configured to receive a shaft of a damper, valve, or any other movable HVAC system component to drive (e.g., rotate) the shaft. In some embodiments, the actuator 500 includes a linkage 512, the linkage 512 configured to facilitate connecting the drive 510 to a movable HVAC system component. For example, the connection device 512 may facilitate attachment of the drive device 510 to a valve or a windshield shaft.

Actuator 500 is illustrated as including an input connection 520 and an output connection 522. In some embodiments, input connection 520 and output connection 522 are located along bottom 508. In other embodiments, the input connection 520 and the output connection 522 may be located along one or more other surfaces of the housing 502. Input connection 520 may be configured to receive a control signal (e.g., a voltage input signal) from an external system or device. The actuator 500 may use the control signal to determine a suitable output of the motor. In some embodiments, the control signals are received from a controller, such as an AHU controller (e.g., AHU controller 330), an economy controller, a supervisory controller (e.g., BMS controller 366), a zone controller, a field controller, an enterprise level controller, a motor controller, an equipment level controller (e.g., actuator controller), or any other type of controller that may be used in an HVAC system or BMS.

In some embodiments, the control signal is a DC voltage signal. Actuator 500 may be a linear proportional actuator configured to control the position of drive device 510 according to the value of the DC voltage received at input connection 520. For example, a minimum input voltage (e.g., 0.0VDC) may correspond to a minimum rotational position of the drive device 510 (e.g., 0, 5, etc.), and a maximum input voltage (e.g., 10.0VDC) may correspond to a maximum rotational position of the drive device 510 (e.g., 90, 95, etc.). An input voltage between the minimum and maximum input voltages may cause the actuator 500 to move the drive 510 to an intermediate position between the minimum rotational position and the maximum rotational position. In other embodiments, the actuator 500 may be a non-linear actuator or may use different input voltage ranges or different types of input signals (e.g., AC voltage or current) to control the position and/or rotational speed of the drive device 510.

In some embodiments, the control signal is an AC voltage signal. The input connection 520 may be configured to receive an AC voltage signal having a voltage of 24VAC or a standard power line voltage (e.g., 120VAC or 230VAC at 50/60 Hz). The frequency of the voltage signal may be modulated (e.g., by a controller of the actuator 500) to adjust the rotational position and/or speed of the drive device 510. In some embodiments, the actuator 500 uses voltage signals to power the various components of the actuator 500. The actuator 500 may use the AC voltage signal received via the input connection 520 as a control signal, a source of electrical power, or both. In some embodiments, a voltage signal is received at input connection 520 from a power line that provides an AC voltage having a constant or substantially constant frequency (e.g., 120VAC or 230VAC at 50/60 Hz) to actuator 500. Input connections 520 may include one or more data connections (independent of the power lines) through which actuator 500 receives control signals (e.g., 0-10VDC control signals) from a controller or another actuator.

In some embodiments, a control signal is received at input connection 520 from another actuator. For example, if multiple actuators are interconnected in a series arrangement, the input connection 520 may be connected (e.g., via a communication bus) to an output data connection of another actuator. One of the actuators may be arranged as a master actuator with its input connection 520 connected to the controller, while the other actuators may be configured as slave actuators with their respective input connections connected to the output connection 522 of the master actuator.

The output connection 522 may be configured to provide a feedback signal to a controller (e.g., an AHU controller, an economy controller, a supervisory controller, a zone controller, a field controller, an enterprise-level controller, etc.) of the HVAC system or BMS in which the actuator 500 is implemented. The feedback signal may indicate the rotational position and/or velocity of the actuator 500. In some embodiments, the output connection 522 may be configured to provide a control signal to another actuator (e.g., a slave actuator) arranged in series with the actuator 500. The input connection 520 and the output connection 522 may be connected to a controller or another actuator via a communication bus. The communication bus may be a wired or wireless communication link and may use any of a number of different communication protocols (e.g., BACnet, LON, WiFi, bluetooth, NFC, TCP/IP, etc.).

With particular reference to FIG. 6, various user input controls are illustrated in accordance with one embodiment. For example, the user input control may include a mode selection switch 602. The user may adjust the position of the mode select switch 602 to set the actuator 500 to operate in the direct-acting mode, the reaction mode, or the calibration mode. It should be understood that these controls are optional components and are not necessary for the actuator 500 to perform the processes described herein. Accordingly, one or more of these user input controls may be omitted without departing from the teachings of the present invention.

Referring now to fig. 8-11, various configurations of wiring input connections 520 and output connections 522 are shown, according to some embodiments. In various embodiments, input connections 520 may include a clockwise input connection 802 and a counterclockwise input connection 804. The clockwise input connection 802 and the counterclockwise input connection 804 may be utilized as signals to control both the rotational position and the rotational direction (i.e., clockwise motion or counterclockwise motion) of the drive device 510.

Referring now specifically to FIG. 8, a proportional wiring configuration 800 is shown. In this configuration, the clockwise input 802 is a DC voltage signal, the counterclockwise input 804 is a regulated voltage signal (e.g., 24VAC or 24VDC), and the actuator 500 may be used as a linear proportional actuator. When functioning as a linear proportional actuator, the actuator 500 controls the position of the driving device 510 according to the value of the received DC voltage. For example, a minimum clockwise input voltage (e.g., 0.0VDC) may correspond to a minimum rotational position of the drive device 510 (e.g., 0 °, -5 °, etc.), while a maximum clockwise input voltage (e.g., 10.0VDC) may correspond to a maximum rotational position of the drive device 510 (e.g., 90 °, 95 °, etc.). A clockwise input voltage between the minimum input voltage and the maximum input voltage may cause the actuator 500 to move the drive device 510 to an intermediate position between the minimum rotational position and the maximum rotational position.

Referring now to FIG. 9, an ON/OFF wiring configuration 900 is shown. In this configuration, both the clockwise input 802 and the counterclockwise input 804 are configured to provide a stable voltage signal (e.g., 24VAC or 24VDC), although the clockwise input 802 is connected to a switch that may be between the ON configuration and the OFF configuration. Since the input signal is configured to provide a stable voltage, actuator 500 is not configured to function as a linear proportional actuator (i.e., actuator 500 does not move drive 510 to any intermediate position between the minimum rotational position and the maximum rotational position). When the clockwise input 802 is in the ON position, the clockwise input 802 provides a steady voltage that causes the actuator 500 to move the drive device 510 to its maximum rotational position (e.g., 90 °, 95 °, etc.). When the clockwise input 802 is in the OFF position, the clockwise input 802 provides no voltage (e.g., 0VAC or 0VDC) and the actuator 500 may move the drive device 510 to a minimum rotational position (e.g., 0 °, -5 °, etc.).

Referring now to fig. 10 and 11, two versions of a floating wiring configuration are shown. Fig. 10 depicts a floating ON/OFF wiring configuration 1000 in which both a clockwise input 802 and a counterclockwise input 804 are configured to provide a regulated voltage signal (e.g., 24VAC or 24VDC) and are both connected to a single switch. For example, if the clockwise input 802 is in the ON position, the counterclockwise input 804 must be in the OFF position, and vice versa. Similar to the ON/OFF wiring configuration, when the clockwise input 802 is in the ON position (and the counterclockwise input 804 is in the OFF position), the clockwise input 802 provides a steady voltage that causes the actuator 500 to move the drive 510 to its maximum rotational position (e.g., 90 °, 95 °, etc.). When the clockwise input 802 is in the OFF position (and the counterclockwise input signal is in the ON position), the clockwise input 802 provides no voltage (e.g., 0VAC or 0VDC) and the actuator 500 may move the drive 510 to a minimum rotational position (e.g., 0 °, -5 °, etc.).

Referring now to fig. 11, a different wiring configuration is depicted, namely a floating delta wiring configuration 1100, in which both a clockwise input 802 and a counterclockwise input 804 are configured to provide a regulated voltage signal (e.g., 24VAC or 24VDC), and both input signals are connected to different ON/OFF switches. Unlike the configuration shown in FIG. 10, the presence of the clockwise input 802 does not determine the presence of the counterclockwise input 804, and vice versa. When the clockwise input 802 is in the ON position and the counterclockwise input 804 is in the OFF position, the clockwise input 802 provides a steady voltage that causes the actuator 500 to move the drive 510 to its maximum rotational position (e.g., 90 °, 95 °, etc.). When the clockwise input 802 is in the OFF position and the counterclockwise input 804 is in the ON position, the clockwise input 802 provides no voltage (e.g., 0VAC or 0VDC) and the actuator 500 may move the drive 510 to a minimum rotational position (e.g., 0 °, -5 °, etc.). When both the clockwise input 802 and the counterclockwise input 804 are in the OFF position, the actuator 500 holds the drive 510 in its current position (i.e., either at the minimum rotational position, or at the maximum rotational position, or at incremental positions between the minimum rotational position and the maximum rotational position).

Reference is now made to fig. 12, which is a block diagram illustrating actuator 500 in greater detail, in accordance with some embodiments. The actuator 500 is illustrated as including a ground connection 1202, a counterclockwise input connection 804, a clockwise input connection 802, and an output connection 1208, which are contained within the housing 1200. In some embodiments, counterclockwise input connection 804 and clockwise input connection 802 may be components of input connection 520. The clockwise input connection 802 and the counterclockwise input connection 804 may provide a voltage input to the power converter 1238. In some embodiments, in response, power converter 1238 may provide various output voltages (e.g., V)_MOTOR15VDC, 5VDC, etc.) which may be used to power the actuators.

The actuator 500 is illustrated as further including a motor 1210 coupled to the drive 510 and a position sensor 1214 configured to measure a position of the motor and/or the drive. The position sensor 1214 may include a hall effect sensor, a potentiometer, an optical sensor, or other type of sensor configured to measure the rotational position of the motor and/or drive device. The position sensor 1214 may provide a position signal 1216 to the processing circuitry 1218. The processing circuitry 1218 uses the position signal 1216 to determine whether to operate the motor 1210. For example, the processing circuitry 1218 may compare the current position of the drive device to a position set point received via the input connection 520 and may operate to retrieve the position set point.

Still referring to fig. 12, the processing circuitry 1218 is illustrated as including a processor 1220 and a memory 1222. Processor 1220 may be a general or special purpose processor, an Application Specific Integrated Circuit (ASIC), one or more Field Programmable Gate Arrays (FPGAs), a set of processing devices, or other suitable processing devices. The processor 1220 may be configured to execute computer code or instructions stored in memory or received from other computer readable media (e.g., CDROM, network storage, remote server, etc.).

Memory 1222 may include one or more devices (e.g., memory units, storage devices, etc.) for storing data and/or computer code to perform and/or facilitate the various processes described in this disclosure. Memory 1222 includes Random Access Memory (RAM), Read Only Memory (ROM), hard drive memory, temporary memory, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. Memory 1222 may include database components, object code components, script components, or any other type of information structure that supports the various activities and information structures described in this disclosure. Memory 1222 may be communicatively connected to processor 1220 via processing circuitry 1218 and may include computer code for performing (e.g., by processor) one or more processes described herein. When the processor 1220 executes instructions stored in the memory 1222, the processor 1220 generally configures the actuator 500 (and more specifically the processing circuitry) to accomplish these activities.

The processing circuitry 1218 is illustrated as including an AC input detector 1224, a DC input detector 1226, and a controller 1232. The AC input detector 1224 and the DC input detector 1226 may be configured to receive a control signal 1234 from a clockwise input connection 802, which clockwise input connection 802 may be a component of the input connection 520. The processing circuitry 1218 may be configured to determine whether the control signal 1234 is an AC voltage signal or a DC voltage signal. The processing circuitry 1218 may operate the motor 1210 using AC motor control techniques in response to determining that the control signal 1234 is an AC voltage signal. However, the processing circuitry 1218 may operate the motor 1210 using DC motor control techniques in response to determining that the control signal 1234 is a DC voltage signal. For example, if the control signal 1234 provided by the clockwise input connection 802 is an AC voltage signal, the AC input detector 1224 may be configured to generate an AC detection signal 1228 and, conversely, the DC input detector 1226 may not generate the DC detection signal 1230. If the control signal 1234 provided by the clockwise input connection 802 is a DC voltage signal, the DC input detector 1226 may be configured to generate the DC detection signal 1230 and the AC input detector 1224 may not generate the AC detection signal 1228. Neither the AC input detector 1224 nor the DC input detector 1226 may generate a detection signal if the clockwise input connection 802 provides neither an AC voltage signal nor a DC voltage signal.

Still referring to fig. 12, the processing circuit 1218 is illustrated as including a controller 1232, the controller 1232 configured to receive the AC detection signal 1228 from the AC input detector 1224 and the DC detection signal 1230 from the DC input detector 1226. In some embodiments, upon receiving the AC detection signal 1228 or the DC detection signal 1230, the controller 1232 is configured to generate a motor control signal 1236, the motor control signal 1236 capable of controlling the speed or position of the motor 1210. For example, if the controller 1232 receives the AC detection signal 1228, the controller 1232 may send a motor control signal 1236 to the motor 1210 to move the drive 510 to its maximum rotational position.

Conversely, if the controller 1232 receives the DC detection signal 1230, the controller 1232 can utilize the value of the DC detection signal 1230 to generate the motor control signal 1236, which the motor control signal 1236 causes the motor 1210 to move the drive 510 to a position based on the value of the DC detection signal 1230. For example, the DC detection signal 1230 may be a DC voltage. Based on the value of the DC voltage, the controller 1232 may determine a suitable position that may be proportional to the DC voltage. The position commanded by the DC detect signal 1230 may be a minimum rotational position, a maximum rotational position, or some intermediate position between the minimum rotational position and the maximum rotational position. In other embodiments, the motor control signal 1236 may be generated by an external controller that provides an AC or DC voltage signal.

If the controller 1232 does not receive either the AC detection signal 1228 or the DC detection signal 1230, the controller 1232 can send a motor control signal 1236 to the motor 1210 that causes the motor 1210 to move the drive 510 to the minimum rotational position. If the motor 1210 is powered (e.g., via a voltage input received at the counterclockwise input 804), the motor 1210 may drive the drive 510 to a minimum rotational position (e.g., as is common in ON/OFF control). However, if the motor 1210 is not powered (e.g., no input voltage is received at the CCW input 804 or the CW input 802), the motor 1210 may stop at its current position (e.g., as is common in floating-point control).

Referring now to fig. 13, a circuit diagram 1300 according to some embodiments is shown, the circuit diagram 1300 including a clockwise input connection 802, a counterclockwise input connection 804, an AC input detector 1224, and a DC input detector 1226. Both the AC input detector 1224 and the DC input detector 1226 are illustrated as receiving inputs from a clockwise input connection 802 (represented by the "grey line" in fig. 13). Depending on the state of the clockwise input signal (e.g., AC signal, DC signal, etc.), either AC input detector 1224 produces AC detection signal 1228 or DC input detector 1226 produces DC detection signal 1230.

FIG. 13 additionally plots the corrected voltage (V)_{_Rectified}) Both the contributing clockwise input connection 802 and the counter-clockwise input connection 804. In some embodiments, the corrected voltage may be used as a source of available power for the motor 1210. Although both the clockwise input connection 802 and the counter-clockwise input connection 804 contribute to the corrected voltage, the diode 1240 (illustrated as diode D2) disposed in the current path between the clockwise input connection and the counter-clockwise input connection ensures that only the clockwise input signal is passed by the AC input detector 1224 and the DC input detector 122And 6, evaluating. In other words, diode 1240 blocks the CCW input signal from reaching the input detector, but allows both the CW input and the CCW input to contribute to the corrected voltage. The circuitry in the AC input detector 1224 includes an optocoupler circuit U2, resistors R6, R7, and R8, a diode D1, and a capacitor C4. The circuit in the DC input detector 1226 includes an operational amplifier U1, resistors R1, R2, R3, R4, R5, and R8, a voltage source V2, and capacitors C1, C2, and C3. A capacitor C5 and a variable resistor I1 are connected in parallel between the diode D3 and ground, and a diode D3 is coupled to the red line.

The AC input detector 1224 is configured to provide a square wave AC detection signal 1228 in response to an AC signal on the input connection 802. In some embodiments, the AC signal has a voltage value that oscillates between a voltage above ground (e.g., greater than 0V) and a voltage below ground (e.g., less than 0V). When the voltage value of the AC signal is lower than the ground potential, a current flows through the photo coupling circuit U2 and the diode D1 (downward in the drawing). This current causes the optocoupler circuit U2 to power the transistors within optocoupler circuit U2, which causes the 5V signal to be provided as the value of AC detect signal 1228. When the voltage value of the AC signal is above ground, current does not flow through diode D1. The lack of current causes no power to be supplied to the transistors within the optocoupler circuit U2, which causes the 0V signal to be supplied as the value of the AC detection signal 1228. The square wave AC detect signal 1228 is generated when the voltage value of the AC input signal oscillates between above ground and below ground.

The AC input detector 1224 is configured to provide a low voltage DC signal (e.g., 0VDC) in response to the DC signal on the input connection 802. In some embodiments, the DC signal has a voltage value higher than the ground potential voltage. The AC input detector 1224 responds to a DC input signal having a voltage above ground in the same manner as the above ground portion of the AC signal is processed. When a DC input signal above ground is received at input connection 802, current does not flow through diode D1. The lack of current does not power the transistors within the optocoupler circuit U2, which causes the 0V signal to be provided as the value of the AC detection signal 1228. If the DC input signal has a voltage value that is always above ground, current will not flow through diode D1 and the value of AC detect signal 1228 will be a constant 0V.

The DC input detector 1226 is configured to provide a DC signal (e.g., 0-2.5VDC) in response to the DC signal on the input connection 802. In some embodiments, the incoming DC signal on input connection 802 has a voltage value that may vary within the range of 0-10VDC or 0-12 VDC. The resistors R4 and R5 function as a voltage divider to produce a DC voltage in the range of 0-2.5VDC between the resistors R4 and R5. The value of the 0-2.5VDC voltage signal is proportional to the value of the incoming 0-10VDC or 0-12VDC input signal. For example, a 10VDC input signal results in a 2.5VDC output signal, while a 0VDC input signal results in a 0VDC output voltage. The remaining components of the DC input detector 1226 (i.e., R1, R2, R3, C1, C2, C3, and U1) act as noise filters to reduce noise in the 0-2.5VDC signal. In some embodiments, the DC detection signal 1230 has a value between 0-2.5 VDC. However, any other range of voltage values may be achieved by varying the size of the resistors R4, R5.

The DC input detector 1226 is configured to generate a low voltage signal (e.g., 0V) in response to an AC signal on the input connection 802. In some embodiments, the AC input signal propagates through the DC input detector 1226. The resistors R4, R5 reduce the voltage of the AC input signal in the same manner as the resistors R4, R5 reduce the voltage of the DC input signal. In some embodiments, the cut-off frequency of the noise filter is low, which causes the reduced voltage AC signal to propagate through the DC input detector 1226, thereby resulting in an oscillating DC detection signal 1230. In other embodiments, the cutoff frequency of the noise filter is high, which filters out high frequency oscillations from the AC signal and produces a stable low voltage (e.g., 0V) DC detection signal 1230. In some embodiments, the controller 1232 uses the AC detection signal 1228 as an override signal and ignores the value of the DC detection signal 1230 when an AC signal is detected by the AC input detector 1224.

Graph table

Referring now to fig. 14-17, graphs of input signal detection performed by actuator 500 are shown, according to some embodiments. 14-17 illustrate the corrected voltage signal (V) when different types of clockwise and counterclockwise input signals are provided to the actuator 500_RECT) DC detection signal (V)_{DC_DETECT}) AndAC detection signal (V)_{AC_DETECT}) The nature of (c). The vertical axis of the graphs contained in fig. 14-17 represents voltage, and the scale of each graph depends on the particular voltage signal displayed by the graph. The horizontal axis of the graph represents time in seconds.

Referring to fig. 14, a graph 1400 illustrates properties of the path corrected voltage signal 1402, the DC detection signal 1404, and the AC detection signal 1406 when the processing circuit 1218 receives a non-zero DC voltage signal from the clockwise input connection 1408 and a non-zero AC voltage signal from the counterclockwise input connection 1410. In response, V _RECT1402 is a non-zero voltage signal in the shape of a triangular wave. V_{DC_DETECT}Reference numeral 1404 is a stable non-zero voltage signal in response to detecting the DC voltage signal. V _{AC_DETECT}1406 is a stable zero voltage signal resulting from no AC voltage being provided to the AC input detector 1224. Although the AC voltage signal is provided to the counterclockwise input connection 1410, the voltage is blocked from the AC input detector 1224 by the diode 1240. In this case, the controller 1232 operates the motor 1210 in a proportional input mode based on the value of the DC voltage signal according to some embodiments.

Referring now to fig. 15, a graph 1500 illustrates properties of a corrected voltage signal 1502, a DC detection signal 1504, and an AC detection signal 1506 when processing circuit 1218 receives a non-zero AC voltage signal from a clockwise input connection 1508 and a zero AC voltage signal from a counterclockwise input connection 1510. In response, V_RECT1502 is a triangular wave shaped non-zero voltage signal. V _{DC_DETECT}1504 is a stable zero voltage signal resulting from no DC voltage being provided to the DC input detector 1226. V _{AC_DETECT}1506 is a non-zero voltage signal that appears in a square waveform shape in response to detecting the AC voltage signal. In this case, the controller 1232 provides a motor control signal 1236 that in some embodiments drives the motor 1210 clockwise toward the clockwise termination position 1236. According to some embodiments, the motor 1210 is powered as indicated due to the presence of a non-zero correction voltage, thereby driving the motor 1210 toward a clockwise end position.

Referring now to FIG. 16, a graph 1600 is shown thereinThe physical circuitry 1218 receives the properties of the corrected voltage signal 1602, the DC detection signal 1604, and the AC detection signal 1606 when a zero voltage signal is received from the clockwise input connection 1608 and a non-zero AC voltage signal is received from the counterclockwise input connection 1610. In response, V_RECT1602 is a non-zero voltage signal in the shape of a triangular wave. V _{DC_DETECT}1604 and V_{AC_DETECT}Both 1606 are stable zero voltage signals because neither AC nor DC voltage is provided at the clockwise input connection 1608. Although the AC voltage signal is provided to the counterclockwise input connection 1610, the voltage is blocked from the AC input detector 1224 by the diode 1240. In this case, the controller 1232 provides a motor control signal 1236 that in some embodiments drives the motor 1210 counterclockwise toward the counterclockwise termination position 1236. According to some embodiments, the motor 1210 is powered as indicated due to the presence of a non-zero correction voltage, thereby driving the motor 1210 toward a counterclockwise termination position.

Referring finally to fig. 17, a graph 1700 shows the properties of the corrected voltage signal 1702, DC detect signal 1704, and AC detect signal 1706 when the processing circuit 1218 receives a zero voltage signal from both the clockwise input connection 1708 and the counterclockwise input connection 1710. In response, V_RECT 1702、V_{DC_DETECT}1704 and V _{AC_DETECT}1706 is all stable zero voltage signals. In this case, according to some embodiments, the controller 1232 does not provide the motor control signal 1236, which causes the motor 1210 to remain in its current position. In some embodiments, the controller 1232 provides a motor control signal 1236 that the motor control signal 1236 drives the motor 1210 counterclockwise toward the counterclockwise termination position. However, according to some embodiments, the lack of power to the motor 1210 prevents the motor 1210 from moving, which results in the motor 1210 remaining in its current position.

Flow chart

Referring now to FIG. 18, a flow diagram 1800 is shown representing operation of an HVAC actuator, according to some embodiments. In some embodiments, the HVAC actuator is the same as or similar to the actuator 500 described above with reference to fig. 5-13. The actuator 500 may be a windshield actuator, a valve actuator, a fan actuator, a pump actuator, or any other type of actuator that may be used in an HVAC system or BMS. The actuator 500 may be a linear actuator (e.g., a linear proportional actuator), a non-linear actuator, an elastic return actuator, or a non-elastic return actuator. The actuator may be controlled by a processing circuit of the HVAC actuator to control a motor of the actuator. The actuators may be automatically controlled by one or more components of the processing circuitry, as described with reference to fig. 5-13.

Flowchart 1800 is illustrated as including: the actuator is powered up in step 1802, initialized in step 1804, and a determination is made as to whether a signal to drive the actuator is received. Flowchart 1800 is illustrated as including determining whether a VAC control signal has been received from controller 1232 at step 1806. If a VAC control signal has been received, the controller 1232 may proceed to step 1812 and turn on the motor 1210. If a VAC control signal has not been received, flowchart 1800 is shown as including a determination at step 1808 as to whether a VDC control signal has been received from controller 1232. If a VDC control signal has not been received, the controller 1232 may proceed to step 1812 and turn on the motor 1210. In various embodiments, the signal for driving the actuator may be received as a control signal from a controller, a user device, or any other external system or device.

Flowchart 1800 is illustrated as including: once the VAC or VDC control signal has been received from the controller 1232, the motor 1210 is turned on in step 1812. The motor 1210 may be coupled to a drive that may be connected to a movable HVAC component. In some embodiments, the drive device is the same as or similar to the drive device 510 described with reference to fig. 5-13. The drive device may be configured to receive a shaft of a damper, valve, or any other movable HVAC system component to drive (e.g., rotate) the shaft. Turning on the motor 1210 may cause a corresponding movement of the drive, thereby causing movement of the HVAC component.

Still referring to FIG. 18, flowchart 1800 is illustrated as including a determination of whether a particular location has been reached at step 1814. The particular location may be included in a previously received command or control signal (e.g., a DC voltage value as a DC input signal). In some embodiments, determining whether a particular position has been reached includes determining the position of the drive device 510. The position of the drive 510 may be determined using position signals from one or more position sensors. The position sensor may be a hall effect sensor, a potentiometer, an optical sensor, or any other type of sensor configured to measure the position of the motor, the drive, and/or an HVAC component connected to the drive. The position of the drive 510 may be determined in terms of hall sensor counts, motor revolutions, motor position, drive position, or any other unit that can be used to quantify the position of the motor, drive, and/or HVAC component. For example, the position of the drive 510 may be determined as a number of degrees of rotation of the drive relative to a fixed position (e.g., zero position, mechanical end stop, etc.), a number of revolutions of a motor, a count of hall sensors, and so forth.

At step 1814, the position of the drive device 510 may be compared to a particular position to determine if the particular position has been reached. If a particular position has been reached, the motor 1210 may be turned off. However, if the particular position has not been reached, the controller 1232 may begin to determine whether the actuator 500 has received sufficient power to operate the motor 1210 at step 1816. If the actuator 500 receives sufficient power, the controller 1232 may repeat step 1814 to determine if the position of the drive device 510 has reached a particular position until the particular position is reached. If the actuator 500 does not receive sufficient power to drive the motor 1210, the motor 1210 may be disconnected in step 1818. After the motor 1210 is turned off, the flowchart 1800 is illustrated as including returning to step 1820 to determine whether the actuator 500 has received sufficient power. Once sufficient power has been received, the flow diagram 1800 can reinitialize the actuator 500 at step 1804.

Table form

Referring now to fig. 19, a table 1900 depicts desired actuator operations when processing circuitry 1218 does not include AC and DC input detectors, according to various embodiments. Table 1900 represents the prior art where a user must manually select a mode based on an actuator input wiring configuration. Thus, the first four rows in column 1902 represent desired actuator operation when the user selects the proportional input mode (represented in the table by "PROP"), while the next four rows in column 1902 represent desired actuator operation when the user selects the floating input mode (represented in the table by "FLT").

The table depicts the effect of a user's mode selection when a DC voltage in the range of 0-20VDC is provided to the clockwise input 802. When the user has selected the proportional input mode, the actuator 500 is driven to an end position corresponding to the value of the DC voltage signal or an intermediate position between the minimum and maximum rotational positions. For example, an OV DC voltage input to the clockwise input 802 may drive the actuator 500 to a first end position, a 20V DC voltage input to the clockwise input 802 may drive the actuator 500 to an opposite end position, and a 10V DC voltage input to the clockwise input 802 may drive the actuator 500 to an intermediate position. However, if the user has selected the floating input mode and a DC voltage in the range of 0-20VDC is provided to the clockwise input 802, the actuator 500 remains at its current set point, rather than moving to the position indicated by the DC voltage signal. Such behavior may be undesirable.

Referring now to fig. 20, a table 2000 depicts desired actuator operation when the processing circuitry 1218 does not include an AC input detector and a DC input detector, according to some embodiments. Column 1902 is removed from the table because the presence of AC input detector 1224 and DC input detector 1226 eliminates the need for the user to select either the proportional input mode or the floating input mode. Thus, whenever a DC voltage in the range of 0-20VDC is provided to the clockwise input 8024, the actuator 500 is driven to an end position corresponding to the value of the DC voltage signal or an intermediate position between the minimum and maximum rotational positions. The presence or absence of an AC input signal to the clockwise input 802 causes the actuator 500 to drive toward the terminal position or to remain in its current position, as previously described. Advantageously, this behavior allows the user to provide either an AC voltage signal or a DC voltage signal to the clockwise input 804. Regardless of the type of input signal provided, the actuator 500 will function properly without requiring the user to toggle the manual mode selection switch.

Configuration of the exemplary embodiment

The construction and arrangement of the systems and methods shown in some embodiments is 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 components may be reversed or otherwise varied, and the nature or number of discrete components or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of this 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 embodiments without departing from the scope of the present disclosure.

The present disclosure relates to methods, systems, and program products on any machine-readable media for implementing various operations. Embodiments of the present disclosure may be implemented using an existing computer processor, 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. The machine-readable medium can be any available medium 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 comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Although the figures show a specific order of method steps, the order of the steps may differ from that shown. In addition, two or more steps may be performed simultaneously or partially simultaneously. Such variations may depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the present disclosure. Also, a software implementation can be achieved through standard programming techniques with rule based logic and other logic to implement the various connection steps, processing steps, comparison steps and decision steps.

Claims (20)

1. An actuator in an HVAC system, the actuator comprising:

an electric motor;

a drive device driven by the motor and connected to a movable HVAC component to drive the movable HVAC component between a plurality of positions;

an input connection comprising a clockwise input connection and a counterclockwise input connection configured to connect to a plurality of wiring configurations to receive an input signal; and

a processing circuit connected to the motor and configured to:

determining whether the input signal is an AC voltage signal or a DC voltage signal;

operating the motor using an AC motor control technique in response to determining that the input signal is the AC voltage signal; and

in response to determining that the input signal is the DC voltage signal, operating the motor using a DC motor control technique.

2. The actuator of claim 1, wherein the processing circuit comprises:

a controller;

an AC voltage detector configured to provide an AC detection signal to the controller in response to determining that the input signal is the AC voltage signal; and

a DC voltage detector configured to provide a DC detection signal to the controller in response to determining that the input signal is the DC voltage signal;

wherein the controller is configured to:

operating the motor using the AC motor control technique in response to receiving the AC detection signal from the AC voltage detector;

operating the motor using the DC motor control technique in response to receiving the DC detection signal from the DC voltage detector.

3. The actuator of claim 1, wherein the wiring configuration is a proportional wiring configuration.

4. The actuator of claim 3,

the clockwise input connection receives a variable DC voltage signal from a first signal connection connected to the clockwise input connection; and

the counter-clockwise input connection receives a stabilized AC or DC voltage signal from a second signal connection connected to the counter-clockwise input connection.

5. The actuator of claim 4, wherein the DC motor control technique comprises:

determining a setpoint position of the drive device proportional to a value of the variable DC voltage signal; and

operating the motor to drive the drive device to the set point position.

6. The actuator of claim 1, wherein the wiring configuration is an ON/OFF wiring configuration.

7. The actuator of claim 6,

the clockwise input connection receiving a first stabilized AC or DC voltage signal from a first signal connection connected to the clockwise input connection when the ON/OFF switch is in an ON position and receiving a zero voltage signal when the ON/OFF switch is in an OFF position; and

the counter-clockwise input connection receives a second stabilized AC or DC voltage signal from a second signal connection connected to the counter-clockwise input connection.

8. The actuator of claim 7, wherein the AC motor control technique is an ON/OFF control technique comprising:

operating the motor to drive the drive device in a clockwise direction to a maximum rotational position when the ON/OFF switch is in the ON position; and

operating the motor to drive the drive device in a counterclockwise direction to a minimum rotational position when the ON/OFF switch is in the OFF position.

9. The actuator of claim 1, wherein the wiring configuration is a floating ON/OFF wiring configuration.

10. The actuator of claim 9,

the clockwise input connection receives a first stabilized AC or DC voltage signal from a first signal connection connected to the clockwise input connection when the switch is in a first position and receives a zero voltage signal when the switch is in a second position; and

the counter-clockwise input connection receives a zero voltage signal from a second signal connection connected to the counter-clockwise input connection when the switch is in the first position, and receives a second regulated AC or DC voltage signal when the switch is in the second position.

11. The actuator of claim 10, wherein the AC motor control technique is a floating ON/OFF control technique comprising:

operating the motor to drive the drive device in a clockwise direction to a maximum rotational position when the switch is in the first position; and

operating the motor to drive the drive device in a counterclockwise direction to a minimum rotational position when the switch is in the second position.

12. The actuator of claim 1, wherein the wiring configuration is a floating incremental wiring configuration.

13. The actuator of claim 12,

the clockwise input connection receiving a first stabilized AC or DC voltage signal from a first signal connection connected to the clockwise input connection when the clockwise switch is in an open position and receiving a zero voltage signal when the clockwise switch is in a closed position; and

the counterclockwise input connection receives a second stabilized AC or DC voltage signal from a second signal connection connected to the counterclockwise input connection when the counterclockwise switch is in the open position and receives a zero voltage signal when the counterclockwise switch is in the closed position.

14. The actuator of claim 13, wherein the AC motor control signal technique is a floating incremental control technique comprising:

operating the motor to drive the drive device in a clockwise direction to a maximum rotational position when the clockwise input switch is in the off position;

operating the motor to drive the drive device in a counterclockwise direction to a minimum rotational position when the counterclockwise input switch is in the closed position and when the clockwise input switch is in the open position; and

preventing the motor from driving the drive device when the clockwise input switch and the counterclockwise input switch are both in an open position.

15. A method of controlling an HVAC actuator comprising an electric motor and a drive driven by the electric motor and connected to a movable HVAC component, the method comprising:

receiving an input signal at an input connection of the actuator; the input connections include clockwise input connections and counterclockwise input connections configured to connect to a plurality of wiring configurations, an

Determining, by a processing circuit of the actuator, whether the input signal is an AC voltage signal or a DC voltage signal;

operating, by the processing circuit, the motor using an AC motor control technique in response to determining that the input signal is the AC voltage signal; and

operating, by the processing circuit, the motor using a DC motor control technique in response to determining that the input signal is the DC voltage signal.

16. The method of claim 15, further comprising:

providing an AC detection signal from an AC voltage detector to a controller in response to determining that the input signal is the AC voltage signal, wherein the motor is operated using the AC motor control technique in response to the controller receiving the AC detection signal from the AC voltage detector; and

providing a DC detection signal from a DC voltage detector to the controller in response to determining that the input signal is the DC voltage signal, wherein the motor is operated using the DC motor control technique in response to the controller receiving the DC detection signal from the DC voltage detector.

17. An actuator in an HVAC system, the actuator comprising:

an electric motor;

a drive device driven by the motor and connected to a movable HVAC component to drive the movable HVAC component between a plurality of positions;

an input connection configured to connect to a plurality of wiring configurations to receive an input signal configured to control at least one of a rotational position of the drive device and a rotational direction of the drive device; and

a processing circuit connected to the motor and configured to:

determining whether the input signal is an AC voltage signal or a DC voltage signal;

operating the motor using an AC motor control technique in response to determining that the input signal is the AC voltage signal; and

in response to determining that the input signal is the DC voltage signal, operating the motor using a DC motor control technique.

18. The actuator of claim 17, wherein the plurality of wiring configurations include a proportional wiring configuration, an ON/OFF wiring configuration, a floating ON/OFF wiring configuration, and a floating incremental wiring configuration.

19. The actuator of claim 17, wherein the processing circuit comprises:

a controller;

an AC voltage detector configured to provide an AC detection signal to the controller in response to determining that the input signal is the AC voltage signal; and

a DC voltage detector configured to provide a DC detection signal to the controller in response to determining that the input signal is the DC voltage signal;

wherein the controller is configured to:

operating the motor using the AC motor control technique in response to receiving the AC detection signal from the AC voltage detector;

operating the motor using the DC motor control technique in response to receiving the DC detection signal from the DC voltage detector.

20. The actuator of claim 17, wherein the input connections comprise clockwise input connections and counterclockwise input connections.

Images