US20040176877A1 - Building automation system and method - Google Patents
Building automation system and method Download PDFInfo
- Publication number
- US20040176877A1 US20040176877A1 US10/382,979 US38297903A US2004176877A1 US 20040176877 A1 US20040176877 A1 US 20040176877A1 US 38297903 A US38297903 A US 38297903A US 2004176877 A1 US2004176877 A1 US 2004176877A1
- Authority
- US
- United States
- Prior art keywords
- bus
- automation system
- building automation
- signal
- control device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 12
- 208000033748 Device issues Diseases 0.000 claims 1
- 230000006870 function Effects 0.000 description 19
- 238000012545 processing Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000009429 electrical wiring Methods 0.000 description 3
- 238000009434 installation Methods 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 238000004378 air conditioning Methods 0.000 description 2
- 238000010438 heat treatment Methods 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 229920000747 poly(lactic acid) Polymers 0.000 description 2
- 238000003825 pressing Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000013515 script Methods 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 1
- 230000003466 anti-cipated effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B15/00—Systems controlled by a computer
- G05B15/02—Systems controlled by a computer electric
Definitions
- the invention generally pertains to building automation, and more specifically, to building automation systems and methods.
- building automation The ability to control one or more devices in a building (e.g., lighting, heating, air conditioning, security systems) based on one or more parameters (e.g., time, temperature, user preference) is known as building automation.
- Building automation may be implemented in any of a number of different types of buildings, including homes, offices, restaurants, stores, theaters, and hotels, to name only a few.
- Building automation systems operate by issuing commands from a control panel (e.g., a keypad) to an output device (e.g., a lamp control).
- a control panel e.g., a keypad
- an output device e.g., a lamp control
- Inexpensive building automation systems are available which use the existing electrical wiring in the building for issuing commands to the output device.
- the control panel and output device are each plugged into electrical outlets in the home and the control panel issues commands via the electrical wiring in the home.
- the commands may be distorted or lost due to “noise” in the electrical wiring.
- such systems are limited to relatively few output devices.
- Inexpensive building automation systems are also available in which the control panel issues radio frequency (RF) commands to the output devices.
- RF radio frequency
- RF transmission is typically limited in range (e.g., by government regulation) and is subject to interference (e.g., from other RF devices).
- RS 232 architecture allows more reliable data exchange between the control panel and the output devices.
- the control panel must be directly connected to each of the output devices to which the control panel issues commands (i.e., a point-to-point or so-called “hub-and-spoke” arrangement).
- a point-to-point or so-called “hub-and-spoke” arrangement Such an arrangement can only be used for short runs and is wiring intensive, which can be expensive to install and maintain.
- the RS 232 architecture does not provide for error-handling.
- a building automation system may comprise a controller area network (CAN) bus for a building.
- CAN controller area network
- At least one control device is operatively associated with the CAN bus, the at least one control device issuing a signal over the CAN bus.
- At least one controlled device is operatively associated with the CAN bus, the at least one controlled device responding to the signal.
- An embodiment of a building automation method may comprise: receiving input at a control device for a building; generating a signal corresponding to the input; issuing the signal over a controller area network (CAN) bus; and responding to the signal at a controlled device for the building.
- CAN controller area network
- FIG. 1 is a high-level schematic diagram of one embodiment of a building automation system
- FIG. 2 is an illustration of one embodiment of an instruction table for use with the building automation system shown in FIG. 1;
- FIG. 3 is a high-level schematic diagram of another embodiment of a building automation system
- FIG. 4 is a high-level schematic diagram showing one embodiment of distributed controllers for the building automation system of FIG. 3;
- FIG. 5 is an illustration of one embodiment of a signal which may be issued over the CAN bus of the building automation system.
- Embodiments of a building automation system 100 are shown and described herein according to the teachings of the present invention.
- the building automation system 100 may be used to automate various functions in a home or other building (not shown). Exemplary functions may include lighting, heating, air conditioning, audio/visual output, operating window coverings to open/close, and security, to name only a few.
- the embodiment of building automation system 100 shown in FIG. 1 may comprise one or more control devices 110 - 113 (e.g., a keypad) operatively associated with one or more controlled devices 120 - 124 (e.g., a triac board).
- Control devices 110 - 113 (hereinafter, generally referred to as control device 110 ) issue commands, which in turn instruct the controlled devices 120 - 124 (hereinafter, generally referred to as controlled device 120 ) to perform a function.
- the central lighting in the room may illuminate to a predetermined intensity (e.g., 50%) and perimeter lighting in the room may be turned on (e.g., at 100% intensity) to illuminate artwork hanging on the walls.
- a predetermined intensity e.g. 50%
- perimeter lighting in the room may be turned on (e.g., at 100% intensity) to illuminate artwork hanging on the walls.
- control devices 110 and controlled devices 120 may comprise any of a wide range of other types and configurations of control devices 110 and controlled devices 120 , and various functions beyond lighting a room, which are now known or that may be developed in the future.
- the particular types and configurations of control devices 110 and controlled devices 120 may depend in part on design considerations, which can be readily defined and implemented by one having ordinary skill in the art after having become familiar with the teachings of the invention.
- control device 110 and controlled device 120 are operatively associated with a control area network (CAN) bus 130 .
- the CAN bus 130 may comprise a two-wire differential serial data bus.
- the CAN bus 130 is capable of high-speed data transmission (about 1 Megabits per second (Mbits/s)) over a distance of about 40 meters (m), and can be extended to about 10,000 meters at transmission speeds of about 5 kilobits per second (kbits/s). It is also a robust bus and can be operated in noisy electrical environments while maintaining the integrity of the data.
- the building automation system 100 of the present invention is not limited to any particular configuration or number of devices, and may comprise as many as 16,000 or more devices linked over extended runs throughout the building.
- the building automation system 100 also preferably comprises error handling and bus arbitration, enhancing its performance.
- the speed with which a number of (i.e., one or more) devices may send and receive signals over a single CAN bus is particularly advantageous for building automation (e.g., lights can be turned on and off immediately without recognizable delay).
- more than one CAN bus 130 , 131 may be combined to extend the functionality of the building automation system 100 .
- a general purpose CAN bus may be provided for lighting and another CAN bus may be dedicated to the security system.
- the building automation system 100 may also be modified for different devices and/or functions, even after the initial installation, allowing the building automation system to be tailored to the user's preferences.
- building automation system 100 may comprise a CAN bus 130 , as shown in FIG. 1.
- At least one control device 110 may be operatively associated with the CAN bus 130
- at least one controlled device 120 may be operatively associated with the CAN bus 130 .
- Suitable interfaces may be provided for control device 110 and controlled device 120 for issuing and receiving signals over the CAN bus 130 .
- Such interfaces can be readily provided by one skilled in the art after having become familiar with the teachings of the present invention.
- the CAN bus 130 may comprise a two-wire differential serial data bus.
- the CAN specification is currently available as version 1.0 and 2.0 and is published by the International Standards Organization (ISO) as standards 11898 (high-speed) and 11519 (low-speed).
- ISO International Standards Organization
- the CAN specification defines communication services and protocols for the CAN bus, in particular, the physical layer and the data link layer for communication over the CAN bus. Bus arbitration and error management is also described.
- the invention is not limited to any particular version and it is intended that other specifications for the CAN bus now known or later developed are also contemplated as being within the scope of the invention.
- Control device 110 may be any suitable device (e.g., a keypad, sensor, etc.) which is generally configured to receive input and generate a signal based on the received input.
- control device 110 may be a keypad or keyboard.
- a key or sequence of keys
- the signal(s) correspond to a predetermined function (e.g., dim central lighting to 50%, activate security system), as will be described in more detail below.
- control device 110 may be any suitable device and is not limited to a keypad or keyboard.
- Examples of control devices 110 also include, but are not limited to, graphical user interfaces (GUI), personal computers (PC), remote control devices, security sensors, temperature sensors, light sensors, and timers.
- GUI graphical user interfaces
- PC personal computers
- remote control devices security sensors, temperature sensors, light sensors, and timers.
- Controlled device 120 may be any suitable device which is generally configured to perform one or more functions in response to a signal issued by control device 110 .
- controlled device 120 may be a controllable alternating current (AC) switch and associated processing hardware and/or software, such as a triac board.
- AC controllable alternating current
- the triac board receives an instruction to dim the main lighting, the triac board causes the main lighting to dim (e.g., to 50% intensity).
- the controlled device 120 receives the instruction over the CAN bus 130 , as will be described in more detail below.
- controlled device 120 may also receive input from sources other than the CAN bus 130 .
- a single device need not be dedicated as a control device 110 , or alternatively, as a controlled device 120 .
- a device which performs the functions of both a control device 110 and a controlled device 120 may also be used according to the teachings of the invention.
- Such a device is represented in the high-level schematic of FIG. 1 as separate devices 110 and 120 . That is, when the device performs the functions of a control device, it is represented in FIG. 1 as control device 110 . When the device performs the functions of a controlled device, it is represented in FIG. 1 as controlled device 120 .
- control device 110 and controlled device 120 may be operatively associated with the CAN bus 130 in any suitable manner, including by permanent, removable, or remote link.
- control device 110 and/or controlled device 120 may be permanently linked to the CAN bus 130 by a hard-wire connection. Alternativley, control device 110 and/or controlled device 120 may be removably linked to the CAN bus 130 by a suitable “plug-type” connection. Control device 110 and/or controlled device 120 may also be remotely linked to the CAN bus 130 , for example via an RF link.
- Building automation system 100 may also comprise a central controller 140 operatively associated with the CAN bus 130 as shown in FIG. 1.
- Central controller 140 may be linked to the CAN bus 130 in any suitable manner, such as was described above for control device 110 and controlled device 120 .
- Central controller 140 may be any suitable device generally configured to receive a signal from control device 110 over the CAN bus 130 , and in turn, to issue a signal with a corresponding instruction over the CAN bus 130 for controlled device 120 .
- central controller 140 may be reprogrammable, i.e., capable of executing computer-readable program code (including but not limited to scripts), which can be changed to reprogram the central controller 140 .
- central controller 140 may comprise one or more personal computers or server computers, microprocessors, programmable logic devices (PLA) such as a field programmable gate array (FPGA) or application-specific integrated circuit (ASIC), to name only a few.
- PDA programmable logic devices
- FPGA field programmable gate array
- ASIC application-specific integrated circuit
- central controller 140 central controller 140 is used to describe the interoperability with more than one of the control devices 110 and controlled devices 120 . It is not intended to limit the physical location of the central controller with respect to the CAN bus 130 (or subnets 131 ) or the devices on the CAN bus 130 .
- central controller 140 may be provided with various ancillary devices, for example, power supplies, electronic controls, input/output (I/O) devices, computer readable storage media, etc.
- ancillary devices for example, power supplies, electronic controls, input/output (I/O) devices, computer readable storage media, etc.
- I/O input/output
- Such ancillary devices are well-understood and therefore are not shown or described herein as further description is not needed for a full understanding of, or to practice the invention.
- the central controller 140 also performs error checking and bus arbitration functions. Error checking and bus arbitration is defined by the CAN specification, currently in versions 1.0 and 2.0. These functions may be provided to enhance performance of the building automation system 100 by reducing the occurrence of corrupt or lost signals on the CAN bus 130 .
- central controller 140 is configured to receive signals over the CAN bus from control device 110 , and issue signals with corresponding instructions over the CAN bus for controlled device 120 .
- Central controller 140 may access the instruction from an instruction table, such as the exemplary instruction table 150 shown in FIG. 2.
- Instruction table 150 may be defined based on various parameters, such as the needs and desires of the building occupant. Although instruction table 150 may be generic (i.e., applicable to one or more predefined configurations of the building automation system 100 ), it is preferably custom or tailored to each building automation system 100 and is therefore defined once the configuration of a particular building automation system 100 is known. In addition, instruction table 150 preferably may be reconfigured based on the changing needs and/or desires of the building occupants.
- the instruction table 150 may comprise signal data 200 and instructions 210 .
- Signal data 200 corresponds to the input received by the central controller 140 .
- signal data 200 comprises the identity of the control device (Device ID) and the type of input received at the control device (Input ID).
- the instructions 210 are functions that the controlled device 120 may perform, and preferably correspond to the signal data 200 .
- the instructions corresponding to this signal data 200 are “Main Lighting 50%” and “Perimeter Lighting ON”.
- instruction table 150 may be defined in any suitable manner.
- instruction table 150 may be defined as a code-driven table. It is understood, however, that instruction table 150 is not limited to any particular format and the embodiment shown in FIG. 2 is merely exemplary for purposes of illustrating its use in the present invention.
- the instruction table 150 is preferably operatively associated with the central controller 140 for use with the building automation system 100 .
- the instruction table 150 may be stored on suitable computer readable storage media accessible by the central controller 140 .
- the instruction table 150 may be modified or replaced. Modifying or replacing the instruction table 150 is particularly advantageous when one or more control devices 110 and/or controlled devices 120 are added or removed from the building automation system 100 . Modifying or replacing the instruction table 150 may also be used to change one or more parameters for control device 110 (e.g., defining a new key) and/or controlled device 120 (e.g., changing the lighting intensity). For example, when the building changes occupancy, the instruction table 150 may be changed to reflect needs and/or desires of the new occupants.
- control device 110 e.g., defining a new key
- controlled device 120 e.g., changing the lighting intensity
- building automation system 100 may comprise an external link 160 .
- external link 160 may comprise a link from central controller 140 to another network such as the Internet via an Internet service provider (ISP).
- ISP Internet service provider
- external link 160 may be used to import/export the instruction table 150 (e.g., at installation or for changes).
- External link 160 may also be used to troubleshoot the building automation system 100 .
- the central controller 140 may generate an error message which may be transmitted to the building owner and/or a monitoring service (e.g., via email, pager alert, etc.).
- the external link 160 is not limited to an ISP link.
- the external link 160 may be via a local area network (LAN), a wide area network (WAN), an Intranet, a telephony link.
- external link 160 may connect to any suitable external device, such as to a laptop computer, personal digital assistant (PDA), pager, facsimile machine, or mobile phone, to name only a few.
- external link 160 may comprise a temporary connection for use by a service technician.
- the external link 160 may comprise a link suitable for connecting a laptop computer to the building automation system 100 .
- Building automation system 100 may also comprise an optional repeater 170 , as shown in FIG. 1 provided in-line on the CAN bus 130 .
- Repeater 170 may be used to extend the physical length of the CAN bus 130 , and/or increase the number of devices that can be provided on the CAN bus 130 .
- repeater 170 may amplify signals and/or “clean” (e.g., improve the signal to noise ratio) the signals issued over CAN bus 130 .
- Building automation system 100 may also comprise one or more additional busses 131 .
- the optional bus 131 is also a CAN bus.
- building automation system 100 may comprise dedicated busses 130 , 131 .
- Dedicated busses 130 , 131 may be categorized by type of device, area of the building (e.g., first floor, bedrooms), or any other suitable category.
- a dedicated CAN bus 130 may be provided for all of the lighting devices and another dedicated CAN bus 131 may be provided for all of the security devices. Accordingly, a failure in one CAN bus 130 preferably does not affect operation of the other CAN bus 131 .
- Building automation system 100 may be operated as follows according to one embodiment of the invention.
- Control device 110 and/or controlled device 120 may be configured during manufacture, during installation, or when reconfiguring the building automation system 100 .
- Instruction table 150 is provided for use by the controller 140 .
- Instruction table 150 is also defined for the building automation system 100 .
- control device 110 may be operated to receive input (e.g., from the user or other source), and generate signals based on the received input.
- input e.g., from the user or other source
- control device 110 may issue signal(s) that are representative of the input (e.g., the keys that were pressed).
- signal(s) e.g., the keys that were pressed.
- control device 110 issues signal(s) corresponding to one or more functions to illuminate the artwork in the room. These signals are issued over the CAN bus 130 for one or more controlled devices 120 .
- the signal(s) are broadcast by the control device 110 over the CAN bus 130 . That is, signals are received by each of the devices ( 110 , 120 , 140 ) on the CAN bus 130 . Each device ( 110 , 120 , 140 ) determines whether it should respond to the signal. For example, the device should respond where a packet identification in the signal is related to the device function(s). It is noted that more than one device may respond to the signal. If the device determines that it should not respond, the device does nothing (i.e., the device “ignores” the signal).
- the central controller 140 responds to signal(s) from control device 110 .
- each of the devices on the CAN bus 130 receive the signal from control device 110 , none of the other devices respond.
- the central controller 140 receives the signal from control device 110 .
- Central controller 140 responds by accessing the instruction table 150 and issuing an instruction based on the signal. For example, when the signal data includes Device ID of “Device 1” and Input ID of “Key 2”, the corresponding instructions according to the instruction table 150 in FIG. 2 are “Main Lighting 50%” and “Perimeter Lighting ON”.
- the central controller 140 issues these instructions over the CAN bus 130 .
- the central controller 140 broadcasts a signal comprising the instructions over the CAN bus 130 .
- the broadcast signal is received by each of the devices ( 110 , 120 , 140 ) on the CAN bus 130 , and each device ( 110 , 120 , 140 ) determines whether it can respond to the instructions. If the device ( 110 , 120 , 140 ) determines that it cannot respond, it ignores the instructions.
- one of the devices may be a triac board for the main lighting circuit
- another of the devices e.g., controlled device 123 in FIG. 1
- controlled device 122 responds to the instruction “Main Lighting 50%” by dimming the main lighting circuit to 50%
- controlled device 123 responds to the instruction “Perimeter Lighting ON” by turning on the recessed perimeter lighting.
- the central lighting in the room dims and the recessed perimeter lighting turns on, illuminating artwork hanging on the walls in the room.
- FIG. 3 Another embodiment of the building automation system 300 is shown in FIG. 3 comprising at least one control device 310 and at least one controlled device 320 linked over CAN bus 330 . It is noted that 300-series reference numbers are used to refer to the like elements shown in FIG. 1, which were described above with respect to embodiment 100 .
- the central controller 140 shown and described above is optional in embodiment 300 , and may not be provided.
- the building automation system 300 comprises distributed controller(s) 400 (see FIG. 4) operativley associated with each control device 310 .
- distributed controller(s) 400 may be operatively associated with each controlled device 320 .
- distributed controllers 400 may be operatively associated both with each control device 310 and with each controlled device 320 .
- Distributed controller 400 may be any suitable device configured to process signals 500 (see FIG. 5).
- distributed controller 400 may be reprogrammable, i.e., capable of executing computer-readable program code (including but not limited to scripts), which can be changed to reprogram the distributed controller 400 .
- One or more of the distributed controllers 400 may also perform error checking and bus arbitration functions for the CAN bus 330 .
- Exemplary distributed controllers 400 may comprise one or more microprocessors, PLAs (e.g., FPGA, ASIC), etc. It should be noted that distributed controllers 400 may be operatively associated with control device 310 and/or controlled device 320 in any suitable manner.
- distributed controllers 400 are provided at, and are directly linked to control device 310 and/or controlled device 320 (e.g., as part of the same computer board).
- distributed controller 400 preferably generates signals 500 comprising signal data in one or more fields 510 - 540 , as shown according to one embodiment in FIG. 5.
- distributed controller 400 may generate a signal 500 comprising an instruction (e.g., field 520 ). That is, when control device 310 receives input, distributed controller 400 may use instruction table 410 to generate a signal 500 comprising corresponding instruction(s) for controlled device 320 .
- distributed controller 400 may perform any number of functions for the controlled device 320 .
- distributed controller 400 generates instructions for controlled device 320 based on signals that are received over the CAN bus 330 .
- control device 310 and controlled device 320 may each comprise a device address 430 (FIG. 4).
- each device address 430 is unique to the device 310 , 320 .
- device addresses 430 may be assigned to the devices 310 , 320 as unique part numbers, although it is noted that the part number need not be numerical.
- the device address 430 may be provided with each device 310 , 320 in a suitable memory, although other embodiments are also contemplated as being within the scope of the invention.
- no other device 310 , 320 has the same device address 430 , thereby reducing the likelihood that the device 310 , 320 is misidentified.
- a triac board is not misidentified on the CAN bus 330 as a security board (e.g., activating an alarm when the user intends to turn on the lights).
- the device address 430 may be unique to a category of devices.
- each triac board may have the same device address 430 , which is different from the device address 430 used to identify electric motor controls.
- Yet other embodiments are also contemplated as being within the scope of the invention and will become apparent to those skilled in the art after having become familiar with the teachings of the invention.
- the address of the devices 310 , 320 may be provided in the signals 500 (FIG. 5), for example, in an address field 510 . Accordingly, the signals 500 may be addressed to specific control devices 310 and/or controlled devices 320 , allowing so called “peer-to-peer” communication over the CAN bus 330 even though the signal 500 is broadcast to each of the devices on the CAN bus 330 . Addressing also allows particular device(s) on the CAN bus 330 to be reset without having to reset all of the devices on the CAN bus 330 (i.e., only the device(s) identified in the address field 510 perform a reset instruction in field 520 ).
- the distributed controller 400 processes the address field 510 of the signal 500 to determine whether it is addressed to the device 310 , 320 .
- the signal 500 may be broadcast over the CAN bus 330 to each of the devices 310 , 320 , as discussed above.
- the distributed controllers 400 read the address in the address field 510 and determine whether it corresponds to the device address 430 . If the address in the address field 510 does not correspond to the device address 430 , the device 310 , 320 does not respond. Preferably, the controller 400 stops processing the signal 500 , thereby conserving processing power and increasing the efficiency of the building automation system 300 . If the address in the address field 510 corresponds to the device address 430 , the controller 400 continues processing the signal 500 . Again, it is noted that more than one device may respond to a signal.
- a signal 500 may be addressed to all of the devices on the CAN bus 330 (e.g., by setting the address field to null). For example, a signal 500 may be addressed to all of the devices so that the user can readily reset all of the devices on the CAN bus 330 after a power outage. Likewise, a signal 500 may be addressed to groups of devices by including a group identification in the address field 510 or another field (e.g., Field n 540 ).
- a signal 500 may be addressed to all of the devices, or particular types of devices (e.g., the lights) or categories of devices (e.g., outdoor lights) so that the user can readily shut all of those devices (e.g., by pressing a single key).
- devices e.g., the lights
- categories of devices e.g., outdoor lights
- the device address 430 itself may be used in the address field 510 (FIG. 5) to identify devices 310 , 320 .
- unique device addresses may comprise many digits (e.g., ten, twenty, or even more).
- a large address field 510 may reduce the size that can be allotted to other fields (e.g., to instruction field 520 ).
- a signal 500 having a large address field 510 may require significant bandwidth for transmission over the CAN bus 330 . High bandwidth signals 500 slow transmission speeds, and may need to be transmitted as multiple packets, increasing congestion on the CAN bus 330 .
- one embodiment of the building automation system may comprise dynamic addresses 420 (FIG. 4) for each device 310 , 320 or category of device. That is, each device 310 , 320 (or category of device) may be assigned a dynamic address 420 that is unique to a particular building automation system 300 .
- the dynamic address 420 is preferably shorter than the device address 430 and still uniquely identifies the device 310 , 320 (or category of device) in a particular building automation system 300 (or on a particular “leg” of the building automation system 300 ).
- each keypad has a unique device address 430 that is different than any other device.
- Keypad A may have device address “123ABC”
- Keypad B may have device address “123XYZ”
- Keypad C may have device address “456ABC”.
- each keypad is assigned a dynamic address 420 when it is provided in the building automation system 300 .
- Keypad A is assigned dynamic address “10”
- Keypad B is assigned dynamic address “20”
- Keypad C is assigned dynamic address “10.”
- Keypad A and Keypad C both have the same dynamic address (i.e., “10), these keypads are used in different building automation systems (System A and System B) and therefore are still uniquely identified in their respective systems.
- System A and System B are both used in System A, and therefore are assigned dynamic addresses that are unique to System A to avoid being misidentified.
- Building automation system 300 may also comprise one or more maps 390 operatively associated with a bridge 380 (discussed in more detail below).
- map 390 is stored in computer-readable storage accessible by the bridge 380 .
- the map 390 may also be operatively associated with one or more of the distributed controllers 400 .
- Map 390 may be defined in any suitable manner.
- map 390 may be defined as a text file using a word processor.
- map 390 may be defined as part of instruction table 410 . It is understood, however, that map 390 is not limited to any particular format.
- map 390 comprises the identity of each device 310 , 320 on the CAN bus 330 .
- a truncated version of the map 390 may also be used and include only some of the devices.
- the truncated version of map 390 stored at a controlled device 320 may only identify control devices 310 from which the controlled device 320 will receive signals.
- truncated versions of the map 390 may be provided at bridges 380 where the building automation system 300 has more than one bridge 380 .
- Each bridge 380 is provided with a truncated map 390 identifying only devices on the CAN bus 330 that are linked to a particular bridge 380 .
- the map 390 may be updated manually (e.g., by exporting, modifying, and importing the map 390 ).
- map 390 may be updated by automatically detecting or determining which of the devices 310 , 320 are on the CAN bus 330 .
- bridge 380 and/or distributed controllers 400 automatically determine the status of the devices 310 , 320 on the CAN bus (i.e., whether a device has been added or removed).
- Bridge 380 and/or distributed controllers 400 preferably update the maps 390 to reflect any changes.
- distributed controller 400 operatively associated with the added device may issue a signal 500 comprising an address field 520 with its device address 430 .
- map 390 may be updated with the identity of the added device.
- map 390 may be updated to indicate that the non-responsive device has been removed from the CAN bus 330 , or is otherwise offline.
- the bridge and/or distributed controllers 400 may also be used to assign a dynamic address to an added device.
- bridge 380 and/or distributed controller 400 may assign a dynamic address that is not already being used, and update the map 390 accordingly.
- the bridge 380 preferably also issues a signal 500 comprising the dynamic address to the distributed controller 400 of the added device (e.g., as dynamic address 420 ).
- the dynamic address 420 may be removed from map 390 when a device is removed from the CAN bus 330 .
- an acknowledgement may be issued over the CAN bus 330 when a signal 500 is received by the device.
- the device sends an acknowledgement defined by the CAN protocol. Accordingly, if a signal is not acknowledged, the sending device may resend the signal.
- the distributed controller 400 of a receiving device may issue a targeted acknowledgement, by returning a signal 500 with an acknowledgement field 530 to the sending device.
- the acknowledgement field may comprise an acknowledgement or “ACK” message when a received signal is processed.
- ACK acknowledgement
- Such an embodiment may be particularly desirable when more than one signal is delivered over the CAN bus 330 and must be assembled at the receiving device before it can be processed.
- the acknowledgement field may be a negative acknowledged or “NAK” message when the received signal(s) cannot be read or are otherwise unusable.
- an error message may also be generated for the user or service technician (e.g., by a suitable error-processing device on the CAN bus 330 and transmitted via external link 360 ).
- building automation system 300 may optionally comprise external link 360 , as shown in FIG. 3.
- External link 360 may interface with the CAN bus 330 through one or more of the control devices 310 , controlled devices 320 , and/or bridge 380 .
- external link 360 may interface via a port provided on the CAN bus 330 .
- external link 360 may be used to import/export instruction table(s) 410 , maps 390 , etc.
- External link 360 may also be used to troubleshoot the building automation system 300 .
- Building automation system 300 may also comprise an optional repeater 370 , as shown in FIG. 3.
- Repeater 370 may be provided on the CAN bus 330 to extend the physical length of the CAN bus 330 .
- repeater 370 may be used to extend the physical length of the CAN bus 130 , and/or increase the number of devices that can be provided on the CAN bus 130 .
- repeater 170 may amplify and/or clean (i.e., by improving the signal to noise ratio) signals issued over the CAN bus 130 .
- Building automation system 300 may also comprise one or more additional busses 331 , which may be linked to one another via bridge 380 as shown in FIG. 3.
- the optional bus 331 may also be a CAN bus.
- building automation system 300 may comprise separate and/or dedicated busses 330 , 331 for different areas of the building and/or for different functions.
Abstract
Description
- The invention generally pertains to building automation, and more specifically, to building automation systems and methods.
- The ability to control one or more devices in a building (e.g., lighting, heating, air conditioning, security systems) based on one or more parameters (e.g., time, temperature, user preference) is known as building automation. Building automation may be implemented in any of a number of different types of buildings, including homes, offices, restaurants, stores, theaters, and hotels, to name only a few.
- Building automation systems operate by issuing commands from a control panel (e.g., a keypad) to an output device (e.g., a lamp control). Inexpensive building automation systems are available which use the existing electrical wiring in the building for issuing commands to the output device. The control panel and output device are each plugged into electrical outlets in the home and the control panel issues commands via the electrical wiring in the home. However, the commands may be distorted or lost due to “noise” in the electrical wiring. In addition, such systems are limited to relatively few output devices.
- Inexpensive building automation systems are also available in which the control panel issues radio frequency (RF) commands to the output devices. However, RF transmission is typically limited in range (e.g., by government regulation) and is subject to interference (e.g., from other RF devices).
- Other building automation systems are available which use an RS 232 architecture to issue commands from the control panel to the output devices. The RS 232 architecture allows more reliable data exchange between the control panel and the output devices. However, the control panel must be directly connected to each of the output devices to which the control panel issues commands (i.e., a point-to-point or so-called “hub-and-spoke” arrangement). Such an arrangement can only be used for short runs and is wiring intensive, which can be expensive to install and maintain. In addition, the RS 232 architecture does not provide for error-handling.
- A building automation system according to one embodiment of the invention may comprise a controller area network (CAN) bus for a building. At least one control device is operatively associated with the CAN bus, the at least one control device issuing a signal over the CAN bus. At least one controlled device is operatively associated with the CAN bus, the at least one controlled device responding to the signal.
- An embodiment of a building automation method may comprise: receiving input at a control device for a building; generating a signal corresponding to the input; issuing the signal over a controller area network (CAN) bus; and responding to the signal at a controlled device for the building.
- Illustrative and presently preferred embodiments of the invention are shown in the drawings, in which:
- FIG. 1 is a high-level schematic diagram of one embodiment of a building automation system;
- FIG. 2 is an illustration of one embodiment of an instruction table for use with the building automation system shown in FIG. 1;
- FIG. 3 is a high-level schematic diagram of another embodiment of a building automation system;
- FIG. 4 is a high-level schematic diagram showing one embodiment of distributed controllers for the building automation system of FIG. 3;
- FIG. 5 is an illustration of one embodiment of a signal which may be issued over the CAN bus of the building automation system.
- Embodiments of a
building automation system 100 are shown and described herein according to the teachings of the present invention. Thebuilding automation system 100 may be used to automate various functions in a home or other building (not shown). Exemplary functions may include lighting, heating, air conditioning, audio/visual output, operating window coverings to open/close, and security, to name only a few. - The embodiment of
building automation system 100 shown in FIG. 1 may comprise one or more control devices 110-113 (e.g., a keypad) operatively associated with one or more controlled devices 120-124 (e.g., a triac board). Control devices 110-113 (hereinafter, generally referred to as control device 110) issue commands, which in turn instruct the controlled devices 120-124 (hereinafter, generally referred to as controlled device 120) to perform a function. By way of example, when a homeowner (or more generally, a user) presses a key on the keypad (e.g., control device 110), the central lighting in the room may illuminate to a predetermined intensity (e.g., 50%) and perimeter lighting in the room may be turned on (e.g., at 100% intensity) to illuminate artwork hanging on the walls. - It should be understood that the foregoing example is provided in order to better understand one environment in which the
building automation system 100 of the present invention may be used. Of course the building automation system of the present invention may comprise any of a wide range of other types and configurations ofcontrol devices 110 and controlleddevices 120, and various functions beyond lighting a room, which are now known or that may be developed in the future. The particular types and configurations ofcontrol devices 110 and controlleddevices 120 may depend in part on design considerations, which can be readily defined and implemented by one having ordinary skill in the art after having become familiar with the teachings of the invention. - According to preferred embodiments of the invention,
control device 110 and controlleddevice 120 are operatively associated with a control area network (CAN)bus 130. The CANbus 130 may comprise a two-wire differential serial data bus. The CANbus 130 is capable of high-speed data transmission (about 1 Megabits per second (Mbits/s)) over a distance of about 40 meters (m), and can be extended to about 10,000 meters at transmission speeds of about 5 kilobits per second (kbits/s). It is also a robust bus and can be operated in noisy electrical environments while maintaining the integrity of the data. - The
building automation system 100 of the present invention is not limited to any particular configuration or number of devices, and may comprise as many as 16,000 or more devices linked over extended runs throughout the building. Thebuilding automation system 100 also preferably comprises error handling and bus arbitration, enhancing its performance. The speed with which a number of (i.e., one or more) devices may send and receive signals over a single CAN bus is particularly advantageous for building automation (e.g., lights can be turned on and off immediately without recognizable delay). In addition, more than oneCAN bus building automation system 100. For example, a general purpose CAN bus may be provided for lighting and another CAN bus may be dedicated to the security system. Thebuilding automation system 100 may also be modified for different devices and/or functions, even after the initial installation, allowing the building automation system to be tailored to the user's preferences. - Having briefly described a building automation system according to an embodiment of the invention, as well as some of the features and advantages of the invention, embodiments of the invention will now be described in detail.
- According to one embodiment of the invention,
building automation system 100 may comprise aCAN bus 130, as shown in FIG. 1. At least onecontrol device 110 may be operatively associated with theCAN bus 130, and at least one controlleddevice 120 may be operatively associated with theCAN bus 130. Suitable interfaces (not shown) may be provided forcontrol device 110 and controlleddevice 120 for issuing and receiving signals over theCAN bus 130. Such interfaces can be readily provided by one skilled in the art after having become familiar with the teachings of the present invention. - As mentioned above, the CAN
bus 130 may comprise a two-wire differential serial data bus. The CAN specification is currently available as version 1.0 and 2.0 and is published by the International Standards Organization (ISO) as standards 11898 (high-speed) and 11519 (low-speed). The CAN specification defines communication services and protocols for the CAN bus, in particular, the physical layer and the data link layer for communication over the CAN bus. Bus arbitration and error management is also described. Of course the invention is not limited to any particular version and it is intended that other specifications for the CAN bus now known or later developed are also contemplated as being within the scope of the invention. -
Control device 110 may be any suitable device (e.g., a keypad, sensor, etc.) which is generally configured to receive input and generate a signal based on the received input. By way of example,control device 110 may be a keypad or keyboard. When the user presses a key (or sequence of keys) on the keypad, one or more signals may be generated that are representative of the key(s) that were pressed. The signal(s), in turn, correspond to a predetermined function (e.g., dim central lighting to 50%, activate security system), as will be described in more detail below. - Of course
control device 110 may be any suitable device and is not limited to a keypad or keyboard. Examples ofcontrol devices 110 also include, but are not limited to, graphical user interfaces (GUI), personal computers (PC), remote control devices, security sensors, temperature sensors, light sensors, and timers. - Controlled
device 120 may be any suitable device which is generally configured to perform one or more functions in response to a signal issued bycontrol device 110. By way of example, controlleddevice 120 may be a controllable alternating current (AC) switch and associated processing hardware and/or software, such as a triac board. When the triac board receives an instruction to dim the main lighting, the triac board causes the main lighting to dim (e.g., to 50% intensity). Preferably, the controlleddevice 120 receives the instruction over theCAN bus 130, as will be described in more detail below. In other embodiments, controlleddevice 120 may also receive input from sources other than theCAN bus 130. - Of course it is understood that a single device need not be dedicated as a
control device 110, or alternatively, as a controlleddevice 120. A device which performs the functions of both acontrol device 110 and a controlleddevice 120 may also be used according to the teachings of the invention. Such a device is represented in the high-level schematic of FIG. 1 asseparate devices control device 110. When the device performs the functions of a controlled device, it is represented in FIG. 1 as controlleddevice 120. - It is also understood that
control device 110 and controlleddevice 120 may be operatively associated with theCAN bus 130 in any suitable manner, including by permanent, removable, or remote link. By way of example,control device 110 and/or controlleddevice 120 may be permanently linked to theCAN bus 130 by a hard-wire connection. Alternativley,control device 110 and/or controlleddevice 120 may be removably linked to theCAN bus 130 by a suitable “plug-type” connection.Control device 110 and/or controlleddevice 120 may also be remotely linked to theCAN bus 130, for example via an RF link. -
Building automation system 100 may also comprise acentral controller 140 operatively associated with theCAN bus 130 as shown in FIG. 1.Central controller 140 may be linked to theCAN bus 130 in any suitable manner, such as was described above forcontrol device 110 and controlleddevice 120. -
Central controller 140 may be any suitable device generally configured to receive a signal fromcontrol device 110 over theCAN bus 130, and in turn, to issue a signal with a corresponding instruction over theCAN bus 130 for controlleddevice 120. In one embodiment,central controller 140 may be reprogrammable, i.e., capable of executing computer-readable program code (including but not limited to scripts), which can be changed to reprogram thecentral controller 140. By way of example,central controller 140 may comprise one or more personal computers or server computers, microprocessors, programmable logic devices (PLA) such as a field programmable gate array (FPGA) or application-specific integrated circuit (ASIC), to name only a few. - Before continuing, it should be noted that the term “central” in “
central controller 140” is used to describe the interoperability with more than one of thecontrol devices 110 and controlleddevices 120. It is not intended to limit the physical location of the central controller with respect to the CAN bus 130 (or subnets 131) or the devices on theCAN bus 130. - It should also be noted that
central controller 140 may be provided with various ancillary devices, for example, power supplies, electronic controls, input/output (I/O) devices, computer readable storage media, etc. Such ancillary devices are well-understood and therefore are not shown or described herein as further description is not needed for a full understanding of, or to practice the invention. - Preferably, the
central controller 140 also performs error checking and bus arbitration functions. Error checking and bus arbitration is defined by the CAN specification, currently in versions 1.0 and 2.0. These functions may be provided to enhance performance of thebuilding automation system 100 by reducing the occurrence of corrupt or lost signals on theCAN bus 130. - As mentioned briefly above,
central controller 140 is configured to receive signals over the CAN bus fromcontrol device 110, and issue signals with corresponding instructions over the CAN bus for controlleddevice 120.Central controller 140 may access the instruction from an instruction table, such as the exemplary instruction table 150 shown in FIG. 2. - Instruction table150 may be defined based on various parameters, such as the needs and desires of the building occupant. Although instruction table 150 may be generic (i.e., applicable to one or more predefined configurations of the building automation system 100), it is preferably custom or tailored to each
building automation system 100 and is therefore defined once the configuration of a particularbuilding automation system 100 is known. In addition, instruction table 150 preferably may be reconfigured based on the changing needs and/or desires of the building occupants. - In one embodiment, the instruction table150 may comprise
signal data 200 andinstructions 210.Signal data 200 corresponds to the input received by thecentral controller 140. In one embodiment,signal data 200 comprises the identity of the control device (Device ID) and the type of input received at the control device (Input ID). In this embodiment, theinstructions 210 are functions that the controlleddevice 120 may perform, and preferably correspond to thesignal data 200. For example, in FIG. 2, signaldata 200 may comprise Device ID=Device 1 and Input ID=Key 1. The instructions corresponding to thissignal data 200 are “Main Lighting 50%” and “Perimeter Lighting ON”. - It is understood that the instruction table150 may be defined in any suitable manner. For example, instruction table 150 may be defined as a code-driven table. It is understood, however, that instruction table 150 is not limited to any particular format and the embodiment shown in FIG. 2 is merely exemplary for purposes of illustrating its use in the present invention.
- The instruction table150 is preferably operatively associated with the
central controller 140 for use with thebuilding automation system 100. For example, the instruction table 150 may be stored on suitable computer readable storage media accessible by thecentral controller 140. - According to preferred embodiments, the instruction table150 may be modified or replaced. Modifying or replacing the instruction table 150 is particularly advantageous when one or
more control devices 110 and/or controlleddevices 120 are added or removed from thebuilding automation system 100. Modifying or replacing the instruction table 150 may also be used to change one or more parameters for control device 110 (e.g., defining a new key) and/or controlled device 120 (e.g., changing the lighting intensity). For example, when the building changes occupancy, the instruction table 150 may be changed to reflect needs and/or desires of the new occupants. - Optionally,
building automation system 100 may comprise anexternal link 160. In one embodiment,external link 160 may comprise a link fromcentral controller 140 to another network such as the Internet via an Internet service provider (ISP). Preferably,external link 160 may be used to import/export the instruction table 150 (e.g., at installation or for changes). -
External link 160 may also be used to troubleshoot thebuilding automation system 100. For example, when an error occurs on theCAN bus 130, thecentral controller 140 may generate an error message which may be transmitted to the building owner and/or a monitoring service (e.g., via email, pager alert, etc.). - Of course, it is understood that the
external link 160 is not limited to an ISP link. In other embodiments, theexternal link 160 may be via a local area network (LAN), a wide area network (WAN), an Intranet, a telephony link. In addition,external link 160 may connect to any suitable external device, such as to a laptop computer, personal digital assistant (PDA), pager, facsimile machine, or mobile phone, to name only a few. In addition,external link 160 may comprise a temporary connection for use by a service technician. For example, theexternal link 160 may comprise a link suitable for connecting a laptop computer to thebuilding automation system 100. -
Building automation system 100 may also comprise anoptional repeater 170, as shown in FIG. 1 provided in-line on theCAN bus 130.Repeater 170 may be used to extend the physical length of theCAN bus 130, and/or increase the number of devices that can be provided on theCAN bus 130. For example,repeater 170 may amplify signals and/or “clean” (e.g., improve the signal to noise ratio) the signals issued overCAN bus 130. -
Building automation system 100 may also comprise one or moreadditional busses 131. Preferably, theoptional bus 131 is also a CAN bus. In one embodiment,building automation system 100 may comprisededicated busses Dedicated busses dedicated CAN bus 130 may be provided for all of the lighting devices and anotherdedicated CAN bus 131 may be provided for all of the security devices. Accordingly, a failure in oneCAN bus 130 preferably does not affect operation of theother CAN bus 131. -
Building automation system 100 may be operated as follows according to one embodiment of the invention.Control device 110 and/or controlleddevice 120 may be configured during manufacture, during installation, or when reconfiguring thebuilding automation system 100. Instruction table 150 is provided for use by thecontroller 140. Instruction table 150 is also defined for thebuilding automation system 100. - In any event, once the
building automation system 100 is configured and ready for use,control device 110 may be operated to receive input (e.g., from the user or other source), and generate signals based on the received input. By way of example, when the user enters input to control device 110 (e.g., by pressing one or more keys on a keypad),control device 110 may issue signal(s) that are representative of the input (e.g., the keys that were pressed). As an illustration, when the user presses the key labeled “Illuminate Artwork”,control device 110 issues signal(s) corresponding to one or more functions to illuminate the artwork in the room. These signals are issued over theCAN bus 130 for one or more controlleddevices 120. - In one embodiment, the signal(s) are broadcast by the
control device 110 over theCAN bus 130. That is, signals are received by each of the devices (110, 120, 140) on theCAN bus 130. Each device (110, 120, 140) determines whether it should respond to the signal. For example, the device should respond where a packet identification in the signal is related to the device function(s). It is noted that more than one device may respond to the signal. If the device determines that it should not respond, the device does nothing (i.e., the device “ignores” the signal). - Preferably in this embodiment, only the
central controller 140 responds to signal(s) fromcontrol device 110. Although each of the devices on theCAN bus 130 receive the signal fromcontrol device 110, none of the other devices respond. - The
central controller 140 receives the signal fromcontrol device 110.Central controller 140 responds by accessing the instruction table 150 and issuing an instruction based on the signal. For example, when the signal data includes Device ID of “Device 1” and Input ID of “Key 2”, the corresponding instructions according to the instruction table 150 in FIG. 2 are “Main Lighting 50%” and “Perimeter Lighting ON”. Thecentral controller 140 issues these instructions over theCAN bus 130. - In one embodiment, the
central controller 140 broadcasts a signal comprising the instructions over theCAN bus 130. The broadcast signal is received by each of the devices (110, 120, 140) on theCAN bus 130, and each device (110, 120, 140) determines whether it can respond to the instructions. If the device (110, 120, 140) determines that it cannot respond, it ignores the instructions. - In the above example, one of the devices (e.g., controlled
device 122 in FIG. 1) may be a triac board for the main lighting circuit, and another of the devices (e.g., controlleddevice 123 in FIG. 1) may be a single-pull single-throw switching board (e.g., a switch with associated processing hardware and software) for the recessed perimeter lighting. Accordingly, controlleddevice 122 responds to the instruction “Main Lighting 50%” by dimming the main lighting circuit to 50%, and controlleddevice 123 responds to the instruction “Perimeter Lighting ON” by turning on the recessed perimeter lighting. The central lighting in the room dims and the recessed perimeter lighting turns on, illuminating artwork hanging on the walls in the room. - Of course it is understood that the above example is merely illustrative of one embodiment of the invention. The scope of the invention is not limited to this example. Indeed, the
building automation system 100 of the present invention is also well-suited for performing more elaborate functions, now know or that may be later developed, as will be readily appreciated by one skilled in the art after having become familiar with the teachings of the present invention. - Another embodiment of the
building automation system 300 is shown in FIG. 3 comprising at least onecontrol device 310 and at least one controlleddevice 320 linked overCAN bus 330. It is noted that 300-series reference numbers are used to refer to the like elements shown in FIG. 1, which were described above with respect toembodiment 100. - The
central controller 140 shown and described above is optional inembodiment 300, and may not be provided. Thebuilding automation system 300 comprises distributed controller(s) 400 (see FIG. 4) operativley associated with eachcontrol device 310. Alternatively, distributed controller(s) 400 may be operatively associated with each controlleddevice 320. In another embodiment, distributedcontrollers 400 may be operatively associated both with eachcontrol device 310 and with each controlleddevice 320. - Distributed
controller 400 may be any suitable device configured to process signals 500 (see FIG. 5). In one embodiment, distributedcontroller 400 may be reprogrammable, i.e., capable of executing computer-readable program code (including but not limited to scripts), which can be changed to reprogram the distributedcontroller 400. One or more of the distributedcontrollers 400 may also perform error checking and bus arbitration functions for theCAN bus 330. Exemplary distributedcontrollers 400 may comprise one or more microprocessors, PLAs (e.g., FPGA, ASIC), etc. It should be noted that distributedcontrollers 400 may be operatively associated withcontrol device 310 and/or controlleddevice 320 in any suitable manner. Preferably, distributedcontrollers 400 are provided at, and are directly linked to controldevice 310 and/or controlled device 320 (e.g., as part of the same computer board). - Advantageously, only the device operatively associated with a failed or otherwise offline distributed
controller 400 is affected by such failure (or by being offline).Other devices building automation system 300 may continue in operation even though one or more of the distributedcontrollers 400 is no longer operational. Further advantages will be described below with regard to various embodiments and will also become apparent to one skilled in the art after having become familiar with the teachings of the invention. - In operation, distributed
controller 400 preferably generatessignals 500 comprising signal data in one or more fields 510-540, as shown according to one embodiment in FIG. 5. For example, distributedcontroller 400 may generate asignal 500 comprising an instruction (e.g., field 520). That is, whencontrol device 310 receives input, distributedcontroller 400 may use instruction table 410 to generate asignal 500 comprising corresponding instruction(s) for controlleddevice 320. Likewise, distributedcontroller 400 may perform any number of functions for the controlleddevice 320. In one embodiment, distributedcontroller 400 generates instructions for controlleddevice 320 based on signals that are received over theCAN bus 330. - According to embodiments of building automation system300 (FIG. 3),
control device 310 and controlleddevice 320 may each comprise a device address 430 (FIG. 4). Preferably, eachdevice address 430 is unique to thedevice devices device address 430 may be provided with eachdevice other device same device address 430, thereby reducing the likelihood that thedevice CAN bus 330 as a security board (e.g., activating an alarm when the user intends to turn on the lights). - It is understood that other embodiments are also contemplated as being within the scope of the invention. In another embodiment, the
device address 430 may be unique to a category of devices. For example, each triac board may have thesame device address 430, which is different from thedevice address 430 used to identify electric motor controls. Yet other embodiments are also contemplated as being within the scope of the invention and will become apparent to those skilled in the art after having become familiar with the teachings of the invention. - The address of the
devices 310, 320 (FIG. 3) may be provided in the signals 500 (FIG. 5), for example, in anaddress field 510. Accordingly, thesignals 500 may be addressed tospecific control devices 310 and/or controlleddevices 320, allowing so called “peer-to-peer” communication over theCAN bus 330 even though thesignal 500 is broadcast to each of the devices on theCAN bus 330. Addressing also allows particular device(s) on theCAN bus 330 to be reset without having to reset all of the devices on the CAN bus 330 (i.e., only the device(s) identified in theaddress field 510 perform a reset instruction in field 520). - In operation, the distributed
controller 400 processes theaddress field 510 of thesignal 500 to determine whether it is addressed to thedevice signal 500 may be broadcast over theCAN bus 330 to each of thedevices controllers 400 read the address in theaddress field 510 and determine whether it corresponds to thedevice address 430. If the address in theaddress field 510 does not correspond to thedevice address 430, thedevice controller 400 stops processing thesignal 500, thereby conserving processing power and increasing the efficiency of thebuilding automation system 300. If the address in theaddress field 510 corresponds to thedevice address 430, thecontroller 400 continues processing thesignal 500. Again, it is noted that more than one device may respond to a signal. - Other embodiments are also contemplated as being within the scope of the invention. A
signal 500 may be addressed to all of the devices on the CAN bus 330 (e.g., by setting the address field to null). For example, asignal 500 may be addressed to all of the devices so that the user can readily reset all of the devices on theCAN bus 330 after a power outage. Likewise, asignal 500 may be addressed to groups of devices by including a group identification in theaddress field 510 or another field (e.g., Field n 540). For example, asignal 500 may be addressed to all of the devices, or particular types of devices (e.g., the lights) or categories of devices (e.g., outdoor lights) so that the user can readily shut all of those devices (e.g., by pressing a single key). - As discussed above, the device address430 (FIG. 4) itself may be used in the address field 510 (FIG. 5) to identify
devices large address field 510 may reduce the size that can be allotted to other fields (e.g., to instruction field 520). In addition, asignal 500 having alarge address field 510 may require significant bandwidth for transmission over theCAN bus 330. High bandwidth signals 500 slow transmission speeds, and may need to be transmitted as multiple packets, increasing congestion on theCAN bus 330. - Accordingly, one embodiment of the building automation system may comprise dynamic addresses420 (FIG. 4) for each
device device 310, 320 (or category of device) may be assigned adynamic address 420 that is unique to a particularbuilding automation system 300. Thedynamic address 420 is preferably shorter than thedevice address 430 and still uniquely identifies thedevice 310, 320 (or category of device) in a particular building automation system 300 (or on a particular “leg” of the building automation system 300). - By way of example, consider three keypads Keypad A, Keypad B, and Keypad C. Keypad A and Keypad B are used in one building automation system (System A), and Keypad C is used in a separate building automation system (System B). Each keypad has a
unique device address 430 that is different than any other device. For example, Keypad A may have device address “123ABC,” Keypad B may have device address “123XYZ,” and Keypad C may have device address “456ABC”. According to this embodiment, each keypad is assigned adynamic address 420 when it is provided in thebuilding automation system 300. For example, Keypad A is assigned dynamic address “10,” Keypad B is assigned dynamic address “20,” and Keypad C is assigned dynamic address “10.” Although Keypad A and Keypad C both have the same dynamic address (i.e., “10), these keypads are used in different building automation systems (System A and System B) and therefore are still uniquely identified in their respective systems. However, Keypad A and Keypad B are both used in System A, and therefore are assigned dynamic addresses that are unique to System A to avoid being misidentified. -
Building automation system 300 may also comprise one ormore maps 390 operatively associated with a bridge 380 (discussed in more detail below). Preferably,map 390 is stored in computer-readable storage accessible by thebridge 380. Themap 390 may also be operatively associated with one or more of the distributedcontrollers 400. -
Map 390 may be defined in any suitable manner. For example, map 390 may be defined as a text file using a word processor. Indeed, map 390 may be defined as part of instruction table 410. It is understood, however, thatmap 390 is not limited to any particular format. - In one embodiment,
map 390 comprises the identity of eachdevice CAN bus 330. Of course, a truncated version of themap 390 may also be used and include only some of the devices. For example, the truncated version ofmap 390 stored at a controlleddevice 320 may only identifycontrol devices 310 from which the controlleddevice 320 will receive signals. As another example, truncated versions of themap 390 may be provided atbridges 380 where thebuilding automation system 300 has more than onebridge 380. Eachbridge 380 is provided with atruncated map 390 identifying only devices on theCAN bus 330 that are linked to aparticular bridge 380. - The
map 390 may be updated manually (e.g., by exporting, modifying, and importing the map 390). Alternatively, map 390 may be updated by automatically detecting or determining which of thedevices CAN bus 330. When adevice CAN bus 330,bridge 380 and/or distributedcontrollers 400 automatically determine the status of thedevices Bridge 380 and/or distributedcontrollers 400 preferably update themaps 390 to reflect any changes. - By way of example, when a
device CAN bus 330, distributedcontroller 400 operatively associated with the added device may issue asignal 500 comprising anaddress field 520 with itsdevice address 430. When thebridge 380 and/or others of the distributedcontrollers 400 receive thesignal 500 and do not recognize the device address 430 (e.g., it is not listed in map 390),map 390 may be updated with the identity of the added device. Similarly, when adevice CAN bus 330, or is otherwise offline. - If dynamic addressing is used, as discussed above, the bridge and/or distributed
controllers 400 may also be used to assign a dynamic address to an added device. For example,bridge 380 and/or distributedcontroller 400 may assign a dynamic address that is not already being used, and update themap 390 accordingly. Thebridge 380 preferably also issues asignal 500 comprising the dynamic address to the distributedcontroller 400 of the added device (e.g., as dynamic address 420). Similarly, thedynamic address 420 may be removed frommap 390 when a device is removed from theCAN bus 330. - Also according to embodiments of building automation system, an acknowledgement may be issued over the
CAN bus 330 when asignal 500 is received by the device. In one embodiment, the device sends an acknowledgement defined by the CAN protocol. Accordingly, if a signal is not acknowledged, the sending device may resend the signal. - According to an alternative embodiment, the distributed
controller 400 of a receiving device may issue a targeted acknowledgement, by returning asignal 500 with anacknowledgement field 530 to the sending device. The acknowledgement field may comprise an acknowledgement or “ACK” message when a received signal is processed. Such an embodiment may be particularly desirable when more than one signal is delivered over theCAN bus 330 and must be assembled at the receiving device before it can be processed. Likewise, the acknowledgement field may be a negative acknowledged or “NAK” message when the received signal(s) cannot be read or are otherwise unusable. Optionally, an error message may also be generated for the user or service technician (e.g., by a suitable error-processing device on theCAN bus 330 and transmitted via external link 360). - As just mentioned,
building automation system 300 may optionally comprise external link 360, as shown in FIG. 3. External link 360 may interface with theCAN bus 330 through one or more of thecontrol devices 310, controlleddevices 320, and/orbridge 380. Alternatively, external link 360 may interface via a port provided on theCAN bus 330. As discussed above forembodiment 100, external link 360 may be used to import/export instruction table(s) 410,maps 390, etc. External link 360 may also be used to troubleshoot thebuilding automation system 300. -
Building automation system 300 may also comprise anoptional repeater 370, as shown in FIG. 3.Repeater 370 may be provided on theCAN bus 330 to extend the physical length of theCAN bus 330. As discussed above forembodiment 100,repeater 370 may be used to extend the physical length of theCAN bus 130, and/or increase the number of devices that can be provided on theCAN bus 130. For example,repeater 170 may amplify and/or clean (i.e., by improving the signal to noise ratio) signals issued over theCAN bus 130. -
Building automation system 300 may also comprise one or moreadditional busses 331, which may be linked to one another viabridge 380 as shown in FIG. 3. Although not required, theoptional bus 331 may also be a CAN bus. As discussed above,building automation system 300 may comprise separate and/ordedicated busses - It is readily apparent that embodiments of the present invention represent an important development in the field of building automation. Having herein set forth preferred embodiments of the present invention, it is anticipated that suitable modifications can be made thereto which will nonetheless remain within the scope of the present invention.
Claims (31)
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/382,979 US20040176877A1 (en) | 2003-03-05 | 2003-03-05 | Building automation system and method |
PCT/US2004/005915 WO2004079461A2 (en) | 2003-03-05 | 2004-02-27 | Building automation system and method |
US11/216,685 US20050288823A1 (en) | 2003-03-05 | 2005-08-31 | Can bus router for building automation systems |
US11/305,793 US7433740B2 (en) | 2003-03-05 | 2005-12-16 | CAN communication for building automation systems |
US12/247,163 US7650323B2 (en) | 2003-03-05 | 2008-10-07 | CAN communication for building automation system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/382,979 US20040176877A1 (en) | 2003-03-05 | 2003-03-05 | Building automation system and method |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/216,685 Continuation-In-Part US20050288823A1 (en) | 2003-03-05 | 2005-08-31 | Can bus router for building automation systems |
Publications (1)
Publication Number | Publication Date |
---|---|
US20040176877A1 true US20040176877A1 (en) | 2004-09-09 |
Family
ID=32926998
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/382,979 Abandoned US20040176877A1 (en) | 2003-03-05 | 2003-03-05 | Building automation system and method |
US11/216,685 Abandoned US20050288823A1 (en) | 2003-03-05 | 2005-08-31 | Can bus router for building automation systems |
US12/247,163 Expired - Fee Related US7650323B2 (en) | 2003-03-05 | 2008-10-07 | CAN communication for building automation system |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/216,685 Abandoned US20050288823A1 (en) | 2003-03-05 | 2005-08-31 | Can bus router for building automation systems |
US12/247,163 Expired - Fee Related US7650323B2 (en) | 2003-03-05 | 2008-10-07 | CAN communication for building automation system |
Country Status (2)
Country | Link |
---|---|
US (3) | US20040176877A1 (en) |
WO (1) | WO2004079461A2 (en) |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040218591A1 (en) * | 2003-04-29 | 2004-11-04 | Craig Ogawa | Bridge apparatus and methods of operation |
US20050044275A1 (en) * | 2003-07-30 | 2005-02-24 | Adamson Hugh P. | Global and local command circuits for network devices |
US20050049730A1 (en) * | 2003-08-29 | 2005-03-03 | Adamson Hugh P. | Keypad for building automation |
US20070016870A1 (en) * | 2005-07-15 | 2007-01-18 | Microsoft Corporation | Control panel framework |
US20080123637A1 (en) * | 2005-06-03 | 2008-05-29 | Ellenberger & Poensgen Gmbh | Multiplexing system for controlling loads in boats or mobile homes |
US7667968B2 (en) | 2006-05-19 | 2010-02-23 | Exceptional Innovation, Llc | Air-cooling system configuration for touch screen |
US20100057943A1 (en) * | 2008-08-28 | 2010-03-04 | Robert Bosch Gmbh | System and method for connecting a security system using a network |
US20100236824A1 (en) * | 2008-04-21 | 2010-09-23 | Inncom International Inc. | Smart wall box |
US20100256816A1 (en) * | 2004-05-06 | 2010-10-07 | Popp Shane M | Manufacturing execution systems (MES) |
US20100324716A1 (en) * | 2004-05-06 | 2010-12-23 | Popp Shane M | Monitoring pharamceutical manufacturing processes |
US20110026535A1 (en) * | 2005-11-29 | 2011-02-03 | Daisuke Ajitomi | Bridge apparatus and bridge system |
US7962130B2 (en) | 2006-11-09 | 2011-06-14 | Exceptional Innovation | Portable device for convergence and automation solution |
US7966083B2 (en) | 2006-03-16 | 2011-06-21 | Exceptional Innovation Llc | Automation control system having device scripting |
US8001219B2 (en) | 2006-03-16 | 2011-08-16 | Exceptional Innovation, Llc | User control interface for convergence and automation system |
US20110213867A1 (en) * | 2010-02-26 | 2011-09-01 | Mccoy Sean | Simultaneous connectivity and management across multiple building automation system networks |
US8155142B2 (en) | 2006-03-16 | 2012-04-10 | Exceptional Innovation Llc | Network based digital access point device |
US8209398B2 (en) | 2006-03-16 | 2012-06-26 | Exceptional Innovation Llc | Internet protocol based media streaming solution |
US8271881B2 (en) | 2006-04-20 | 2012-09-18 | Exceptional Innovation, Llc | Touch screen for convergence and automation system |
WO2013059495A1 (en) * | 2011-10-18 | 2013-04-25 | Schneider Electric Buildings, Llc | Self-healing communications network |
US8725845B2 (en) | 2006-03-16 | 2014-05-13 | Exceptional Innovation Llc | Automation control system having a configuration tool |
WO2014143798A3 (en) * | 2013-03-15 | 2014-11-13 | Siemens Aktiengesellschaft | Redundant bus fault detection |
JP2015503788A (en) * | 2011-12-26 | 2015-02-02 | アーベーベー・リサーチ・リミテッドAbb Research Ltd. | Relay interface module for distributed control systems |
EP2911128A1 (en) * | 2014-02-24 | 2015-08-26 | Siemens Schweiz AG | Hazard warning assembly |
US20150300671A1 (en) * | 2014-04-22 | 2015-10-22 | Trane International Inc. | System and method for controlling hvac equipment so as to obtain a desired range of a sound pressure level and/or sound power level |
US9841210B2 (en) | 2014-04-22 | 2017-12-12 | Trane International Inc. | Sound level control in an HVAC system |
US9892073B1 (en) * | 2014-10-06 | 2018-02-13 | Master Lock Company Llc | Bus addressing systems and methods using repurposed bits |
US10884966B2 (en) | 2018-12-04 | 2021-01-05 | Palo Alto Research Center Incorporated | Method and apparatus to prevent a node device from transmitting an unallowable message onto a CAN bus |
Families Citing this family (91)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2854627B1 (en) * | 2003-05-07 | 2006-05-26 | Saint Gobain | SILICO-SODO-CALCIUM GLASS COMPOSITION, IN PARTICULAR FOR PRODUCING SUBSTRATES |
US20050049754A1 (en) * | 2003-08-29 | 2005-03-03 | Craig Ogawa | Power and data configurations for building automation systems |
CN1855920A (en) * | 2005-04-28 | 2006-11-01 | 西门子(中国)有限公司 | Communication on magnetic resonance system multi-point bus |
US8023440B2 (en) * | 2006-08-30 | 2011-09-20 | Siemens Industry, Inc. | Binding wireless devices in a building automation system |
EP2186251B1 (en) * | 2007-08-28 | 2019-10-09 | ABB Schweiz AG | Real-time communication security for automation networks |
US7915837B2 (en) * | 2008-04-08 | 2011-03-29 | Lumetric, Inc. | Modular programmable lighting ballast |
US20100262296A1 (en) * | 2008-06-25 | 2010-10-14 | HID Laboratories, Inc. | Lighting control system and method |
US8143811B2 (en) * | 2008-06-25 | 2012-03-27 | Lumetric, Inc. | Lighting control system and method |
US8713697B2 (en) | 2008-07-09 | 2014-04-29 | Lennox Manufacturing, Inc. | Apparatus and method for storing event information for an HVAC system |
US8527096B2 (en) | 2008-10-24 | 2013-09-03 | Lennox Industries Inc. | Programmable controller and a user interface for same |
US8762666B2 (en) | 2008-10-27 | 2014-06-24 | Lennox Industries, Inc. | Backup and restoration of operation control data in a heating, ventilation and air conditioning network |
US8437877B2 (en) | 2008-10-27 | 2013-05-07 | Lennox Industries Inc. | System recovery in a heating, ventilation and air conditioning network |
US8874815B2 (en) | 2008-10-27 | 2014-10-28 | Lennox Industries, Inc. | Communication protocol system and method for a distributed architecture heating, ventilation and air conditioning network |
US8548630B2 (en) | 2008-10-27 | 2013-10-01 | Lennox Industries, Inc. | Alarm and diagnostics system and method for a distributed-architecture heating, ventilation and air conditioning network |
US8463443B2 (en) | 2008-10-27 | 2013-06-11 | Lennox Industries, Inc. | Memory recovery scheme and data structure in a heating, ventilation and air conditioning network |
US8442693B2 (en) | 2008-10-27 | 2013-05-14 | Lennox Industries, Inc. | System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network |
US8433446B2 (en) | 2008-10-27 | 2013-04-30 | Lennox Industries, Inc. | Alarm and diagnostics system and method for a distributed-architecture heating, ventilation and air conditioning network |
US9432208B2 (en) | 2008-10-27 | 2016-08-30 | Lennox Industries Inc. | Device abstraction system and method for a distributed architecture heating, ventilation and air conditioning system |
US8352080B2 (en) | 2008-10-27 | 2013-01-08 | Lennox Industries Inc. | Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network |
US8452906B2 (en) | 2008-10-27 | 2013-05-28 | Lennox Industries, Inc. | Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network |
US9377768B2 (en) | 2008-10-27 | 2016-06-28 | Lennox Industries Inc. | Memory recovery scheme and data structure in a heating, ventilation and air conditioning network |
US8255086B2 (en) | 2008-10-27 | 2012-08-28 | Lennox Industries Inc. | System recovery in a heating, ventilation and air conditioning network |
US8977794B2 (en) | 2008-10-27 | 2015-03-10 | Lennox Industries, Inc. | Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network |
US8788100B2 (en) | 2008-10-27 | 2014-07-22 | Lennox Industries Inc. | System and method for zoning a distributed-architecture heating, ventilation and air conditioning network |
US9152155B2 (en) | 2008-10-27 | 2015-10-06 | Lennox Industries Inc. | Device abstraction system and method for a distributed-architecture heating, ventilation and air conditioning system |
US8615326B2 (en) | 2008-10-27 | 2013-12-24 | Lennox Industries Inc. | System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network |
US8437878B2 (en) | 2008-10-27 | 2013-05-07 | Lennox Industries Inc. | Alarm and diagnostics system and method for a distributed architecture heating, ventilation and air conditioning network |
US8352081B2 (en) | 2008-10-27 | 2013-01-08 | Lennox Industries Inc. | Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network |
US9678486B2 (en) | 2008-10-27 | 2017-06-13 | Lennox Industries Inc. | Device abstraction system and method for a distributed-architecture heating, ventilation and air conditioning system |
US8452456B2 (en) | 2008-10-27 | 2013-05-28 | Lennox Industries Inc. | System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network |
US8543243B2 (en) | 2008-10-27 | 2013-09-24 | Lennox Industries, Inc. | System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network |
US9268345B2 (en) | 2008-10-27 | 2016-02-23 | Lennox Industries Inc. | System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network |
US8239066B2 (en) | 2008-10-27 | 2012-08-07 | Lennox Industries Inc. | System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network |
US8295981B2 (en) | 2008-10-27 | 2012-10-23 | Lennox Industries Inc. | Device commissioning in a heating, ventilation and air conditioning network |
US9632490B2 (en) | 2008-10-27 | 2017-04-25 | Lennox Industries Inc. | System and method for zoning a distributed architecture heating, ventilation and air conditioning network |
US8564400B2 (en) | 2008-10-27 | 2013-10-22 | Lennox Industries, Inc. | Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network |
US8798796B2 (en) | 2008-10-27 | 2014-08-05 | Lennox Industries Inc. | General control techniques in a heating, ventilation and air conditioning network |
US8802981B2 (en) | 2008-10-27 | 2014-08-12 | Lennox Industries Inc. | Flush wall mount thermostat and in-set mounting plate for a heating, ventilation and air conditioning system |
US8655490B2 (en) | 2008-10-27 | 2014-02-18 | Lennox Industries, Inc. | System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network |
US8694164B2 (en) | 2008-10-27 | 2014-04-08 | Lennox Industries, Inc. | Interactive user guidance interface for a heating, ventilation and air conditioning system |
US8600559B2 (en) | 2008-10-27 | 2013-12-03 | Lennox Industries Inc. | Method of controlling equipment in a heating, ventilation and air conditioning network |
US8655491B2 (en) | 2008-10-27 | 2014-02-18 | Lennox Industries Inc. | Alarm and diagnostics system and method for a distributed architecture heating, ventilation and air conditioning network |
US8774210B2 (en) | 2008-10-27 | 2014-07-08 | Lennox Industries, Inc. | Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network |
US8892797B2 (en) | 2008-10-27 | 2014-11-18 | Lennox Industries Inc. | Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network |
US8744629B2 (en) | 2008-10-27 | 2014-06-03 | Lennox Industries Inc. | System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network |
US8661165B2 (en) | 2008-10-27 | 2014-02-25 | Lennox Industries, Inc. | Device abstraction system and method for a distributed architecture heating, ventilation and air conditioning system |
US9651925B2 (en) | 2008-10-27 | 2017-05-16 | Lennox Industries Inc. | System and method for zoning a distributed-architecture heating, ventilation and air conditioning network |
US8600558B2 (en) | 2008-10-27 | 2013-12-03 | Lennox Industries Inc. | System recovery in a heating, ventilation and air conditioning network |
US8725298B2 (en) | 2008-10-27 | 2014-05-13 | Lennox Industries, Inc. | Alarm and diagnostics system and method for a distributed architecture heating, ventilation and conditioning network |
US8855825B2 (en) | 2008-10-27 | 2014-10-07 | Lennox Industries Inc. | Device abstraction system and method for a distributed-architecture heating, ventilation and air conditioning system |
US8560125B2 (en) | 2008-10-27 | 2013-10-15 | Lennox Industries | Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network |
US9325517B2 (en) | 2008-10-27 | 2016-04-26 | Lennox Industries Inc. | Device abstraction system and method for a distributed-architecture heating, ventilation and air conditioning system |
US8994539B2 (en) | 2008-10-27 | 2015-03-31 | Lennox Industries, Inc. | Alarm and diagnostics system and method for a distributed-architecture heating, ventilation and air conditioning network |
US8463442B2 (en) | 2008-10-27 | 2013-06-11 | Lennox Industries, Inc. | Alarm and diagnostics system and method for a distributed architecture heating, ventilation and air conditioning network |
US9261888B2 (en) | 2008-10-27 | 2016-02-16 | Lennox Industries Inc. | System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network |
WO2010095087A1 (en) * | 2009-02-19 | 2010-08-26 | Koninklijke Philips Electronics N.V. | Lighting control network |
US8296488B2 (en) | 2009-04-27 | 2012-10-23 | Abl Ip Holding Llc | Automatic self-addressing method for wired network nodes |
US9196009B2 (en) | 2009-06-22 | 2015-11-24 | Johnson Controls Technology Company | Systems and methods for detecting changes in energy usage in a building |
US8731724B2 (en) | 2009-06-22 | 2014-05-20 | Johnson Controls Technology Company | Automated fault detection and diagnostics in a building management system |
US8788097B2 (en) * | 2009-06-22 | 2014-07-22 | Johnson Controls Technology Company | Systems and methods for using rule-based fault detection in a building management system |
US9286582B2 (en) | 2009-06-22 | 2016-03-15 | Johnson Controls Technology Company | Systems and methods for detecting changes in energy usage in a building |
US8600556B2 (en) | 2009-06-22 | 2013-12-03 | Johnson Controls Technology Company | Smart building manager |
US10739741B2 (en) | 2009-06-22 | 2020-08-11 | Johnson Controls Technology Company | Systems and methods for detecting changes in energy usage in a building |
US11269303B2 (en) | 2009-06-22 | 2022-03-08 | Johnson Controls Technology Company | Systems and methods for detecting changes in energy usage in a building |
US9606520B2 (en) | 2009-06-22 | 2017-03-28 | Johnson Controls Technology Company | Automated fault detection and diagnostics in a building management system |
USD648642S1 (en) | 2009-10-21 | 2011-11-15 | Lennox Industries Inc. | Thin cover plate for an electronic system controller |
USD648641S1 (en) | 2009-10-21 | 2011-11-15 | Lennox Industries Inc. | Thin cover plate for an electronic system controller |
EP2524307B1 (en) * | 2010-01-12 | 2016-11-02 | Google, Inc. | Operating system auto-update procedure |
US8260444B2 (en) | 2010-02-17 | 2012-09-04 | Lennox Industries Inc. | Auxiliary controller of a HVAC system |
DE102010043011A1 (en) * | 2010-08-30 | 2012-03-01 | Tridonic Gmbh & Co. Kg | Parallel programming and updating of building services bus subscribers |
DE102011010041B4 (en) * | 2011-02-07 | 2019-04-25 | Göpel electronic GmbH | Modular CAN-SWITCH |
US8775689B2 (en) | 2011-05-02 | 2014-07-08 | Deere & Company | Electronic modules with automatic configuration |
CN102331764A (en) * | 2011-08-03 | 2012-01-25 | 中山大学深圳研究院 | Method and device for intelligently monitoring household based on CAN (Controller Area Network) bus |
CN102331765A (en) * | 2011-08-03 | 2012-01-25 | 中山大学深圳研究院 | Embedded digital household monitoring system |
US9390388B2 (en) | 2012-05-31 | 2016-07-12 | Johnson Controls Technology Company | Systems and methods for measuring and verifying energy usage in a building |
US9749177B2 (en) * | 2012-09-21 | 2017-08-29 | Philips Lighting Holding B.V. | Method and apparatus for dynamic address assignment |
US20160033948A1 (en) * | 2013-03-07 | 2016-02-04 | Pioneer Corporation | Control system |
US10025279B2 (en) * | 2013-06-18 | 2018-07-17 | NuLEDs, Inc. | Controlling loads and collecting building information via IP networks |
US20150177720A1 (en) * | 2013-09-24 | 2015-06-25 | Anuva Automation, Inc. | Building automation system and method |
US10032364B2 (en) * | 2014-05-15 | 2018-07-24 | Savant Systems, Llc | Standalone wireless lighting application |
US9366082B2 (en) * | 2014-06-17 | 2016-06-14 | Crestron Electronics Inc. | Shading control network using a control network |
US10358869B2 (en) | 2014-06-17 | 2019-07-23 | Crestron Electronics, Inc. | Shading control network using a control network |
US10202801B2 (en) | 2014-06-17 | 2019-02-12 | Crestron Electronics, Inc. | Shading and lighting control using a control network |
US20160028687A1 (en) * | 2014-07-25 | 2016-01-28 | David Sheppard | Internet Security Assembly |
US10085328B2 (en) | 2014-08-11 | 2018-09-25 | RAB Lighting Inc. | Wireless lighting control systems and methods |
US10039174B2 (en) | 2014-08-11 | 2018-07-31 | RAB Lighting Inc. | Systems and methods for acknowledging broadcast messages in a wireless lighting control network |
US10531545B2 (en) | 2014-08-11 | 2020-01-07 | RAB Lighting Inc. | Commissioning a configurable user control device for a lighting control system |
CN110521285A (en) | 2017-04-10 | 2019-11-29 | 昕诺飞控股有限公司 | System and method for improving the data rate on addressable lighting network |
CN109274568A (en) * | 2018-09-29 | 2019-01-25 | 广州致远电子有限公司 | A kind of processing method of CAN hub and data information |
DE102018128095A1 (en) * | 2018-11-09 | 2020-05-14 | Lemken Gmbh & Co. Kg | Method for the simultaneous operation of several agricultural implements connected to one another for an application to form a combination of implements |
CN110719218B (en) * | 2019-10-31 | 2021-07-30 | 天津亚东智鑫科技有限公司 | Multi-node interconnection protocol standard method based on CAN bus |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030074511A1 (en) * | 2000-10-18 | 2003-04-17 | Festo Ag & Co. | Bus repeater |
US6609172B1 (en) * | 2000-04-20 | 2003-08-19 | Hewlett-Packard Development Company, L.P. | Breaking up a bus to determine the connection topology and dynamic addressing |
US6728268B1 (en) * | 1999-06-22 | 2004-04-27 | Trimble Navigation Ltd. | Method and system to connect internet protocol hosts via an application specific bus |
Family Cites Families (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU5929190A (en) * | 1989-06-02 | 1991-01-07 | Aisi Research Corporation | Appliance interface for exchanging data |
KR0128169B1 (en) * | 1993-12-31 | 1998-04-15 | 김광호 | Home automation |
US5621662A (en) * | 1994-02-15 | 1997-04-15 | Intellinet, Inc. | Home automation system |
US5551053A (en) * | 1994-02-28 | 1996-08-27 | Eaton Corporation | System and Method for assigning addresses to I/O devices in a control network and for verifying the assigned address of the devices |
US5528215A (en) * | 1994-05-31 | 1996-06-18 | Landis & Gyr Powers, Inc. | Building automation system having expansion modules |
US5510975A (en) * | 1994-07-01 | 1996-04-23 | Atlantic Software, Inc. | Method of logical operations in home automation |
US6297724B1 (en) * | 1994-09-09 | 2001-10-02 | The Whitaker Corporation | Lighting control subsystem for use in system architecture for automated building |
US5572438A (en) | 1995-01-05 | 1996-11-05 | Teco Energy Management Services | Engery management and building automation system |
DE19509558A1 (en) * | 1995-03-16 | 1996-09-19 | Abb Patent Gmbh | Process for fault-tolerant communication under high real-time conditions |
KR100387709B1 (en) * | 1995-11-22 | 2003-10-04 | 삼성전자주식회사 | Home multimedia network architecture |
US5703442A (en) * | 1996-04-29 | 1997-12-30 | Electronic Lighting Incorporated | Method and apparatus for interfacing a light dimming control with an automated control system |
CH690875A5 (en) * | 1996-05-21 | 2001-02-15 | Hts High Technology Systems Ag | Home and building automation system. |
US6192282B1 (en) * | 1996-10-01 | 2001-02-20 | Intelihome, Inc. | Method and apparatus for improved building automation |
DE19710082A1 (en) * | 1997-03-12 | 1998-10-01 | Deere & Co | Drive system for commercial vehicles |
DE19748536C2 (en) * | 1997-11-03 | 2000-06-29 | Daimler Chrysler Ag | Data processing-based electronic control system, in particular for a motor vehicle |
US6104963A (en) * | 1998-04-03 | 2000-08-15 | Johnson Controls Technology Company | Communication system for distributed-object building automation system |
US6832120B1 (en) * | 1998-05-15 | 2004-12-14 | Tridium, Inc. | System and methods for object-oriented control of diverse electromechanical systems using a computer network |
US6914893B2 (en) | 1998-06-22 | 2005-07-05 | Statsignal Ipc, Llc | System and method for monitoring and controlling remote devices |
US6437692B1 (en) | 1998-06-22 | 2002-08-20 | Statsignal Systems, Inc. | System and method for monitoring and controlling remote devices |
US6292862B1 (en) * | 1998-07-28 | 2001-09-18 | Siemens Aktiengesellschaft | Bridge module |
US6199136B1 (en) * | 1998-09-02 | 2001-03-06 | U.S. Philips Corporation | Method and apparatus for a low data-rate network to be represented on and controllable by high data-rate home audio/video interoperability (HAVi) network |
US7103511B2 (en) * | 1998-10-14 | 2006-09-05 | Statsignal Ipc, Llc | Wireless communication networks for providing remote monitoring of devices |
US7213061B1 (en) * | 1999-04-29 | 2007-05-01 | Amx Llc | Internet control system and method |
US6813525B2 (en) * | 2000-02-25 | 2004-11-02 | Square D Company | Energy management system |
DE10018136A1 (en) * | 2000-04-12 | 2001-10-18 | Infineon Technologies Ag | Packet-based data transmission |
US7058508B2 (en) | 2001-01-12 | 2006-06-06 | Energy Control Technologies | Automated building service broker |
US7380210B2 (en) * | 2001-07-20 | 2008-05-27 | Siemens Building Technologies, Inc. | User interface with installment mode |
US7346463B2 (en) * | 2001-08-09 | 2008-03-18 | Hunt Technologies, Llc | System for controlling electrically-powered devices in an electrical network |
US7349761B1 (en) * | 2002-02-07 | 2008-03-25 | Cruse Mike B | System and method for distributed facility management and operational control |
CA2480551A1 (en) * | 2002-03-28 | 2003-10-09 | Robertshaw Controls Company | Energy management system and method |
US7383158B2 (en) * | 2002-04-16 | 2008-06-03 | Trane International Inc. | HVAC service tool with internet capability |
GB0211644D0 (en) | 2002-05-21 | 2002-07-03 | Wesby Philip B | System and method for remote asset management |
US7024282B2 (en) * | 2002-09-26 | 2006-04-04 | Siemens Building Technologies, Inc. | Multi-node utilization of a single network variable input for computation of a single control variable at a sink node |
US7433740B2 (en) * | 2003-03-05 | 2008-10-07 | Colorado Vnet, Llc | CAN communication for building automation systems |
US7089066B2 (en) | 2003-04-24 | 2006-08-08 | Colorado Vnet, Llc | Distributed control systems and methods |
US20040218591A1 (en) * | 2003-04-29 | 2004-11-04 | Craig Ogawa | Bridge apparatus and methods of operation |
US6967565B2 (en) | 2003-06-27 | 2005-11-22 | Hx Lifespace, Inc. | Building automation system |
US7502768B2 (en) * | 2004-02-27 | 2009-03-10 | Siemens Building Technologies, Inc. | System and method for predicting building thermal loads |
US7139239B2 (en) | 2004-10-05 | 2006-11-21 | Siemens Building Technologies, Inc. | Self-healing control network for building automation systems |
-
2003
- 2003-03-05 US US10/382,979 patent/US20040176877A1/en not_active Abandoned
-
2004
- 2004-02-27 WO PCT/US2004/005915 patent/WO2004079461A2/en active Application Filing
-
2005
- 2005-08-31 US US11/216,685 patent/US20050288823A1/en not_active Abandoned
-
2008
- 2008-10-07 US US12/247,163 patent/US7650323B2/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6728268B1 (en) * | 1999-06-22 | 2004-04-27 | Trimble Navigation Ltd. | Method and system to connect internet protocol hosts via an application specific bus |
US6609172B1 (en) * | 2000-04-20 | 2003-08-19 | Hewlett-Packard Development Company, L.P. | Breaking up a bus to determine the connection topology and dynamic addressing |
US20030074511A1 (en) * | 2000-10-18 | 2003-04-17 | Festo Ag & Co. | Bus repeater |
Cited By (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2004097589A2 (en) * | 2003-04-29 | 2004-11-11 | Colorado Vnet | Bridge apparatus and methods of operation |
WO2004097589A3 (en) * | 2003-04-29 | 2005-04-21 | Colorado Vnet | Bridge apparatus and methods of operation |
US20040218591A1 (en) * | 2003-04-29 | 2004-11-04 | Craig Ogawa | Bridge apparatus and methods of operation |
US7472203B2 (en) | 2003-07-30 | 2008-12-30 | Colorado Vnet, Llc | Global and local command circuits for network devices |
US20050044275A1 (en) * | 2003-07-30 | 2005-02-24 | Adamson Hugh P. | Global and local command circuits for network devices |
US20050049730A1 (en) * | 2003-08-29 | 2005-03-03 | Adamson Hugh P. | Keypad for building automation |
US8660680B2 (en) | 2004-05-06 | 2014-02-25 | SMR Logic Systems LLC | Methods of monitoring acceptance criteria of pharmaceutical manufacturing processes |
US9195228B2 (en) | 2004-05-06 | 2015-11-24 | Smp Logic Systems | Monitoring pharmaceutical manufacturing processes |
US8491839B2 (en) | 2004-05-06 | 2013-07-23 | SMP Logic Systems, LLC | Manufacturing execution systems (MES) |
US9304509B2 (en) | 2004-05-06 | 2016-04-05 | Smp Logic Systems Llc | Monitoring liquid mixing systems and water based systems in pharmaceutical manufacturing |
US9008815B2 (en) | 2004-05-06 | 2015-04-14 | Smp Logic Systems | Apparatus for monitoring pharmaceutical manufacturing processes |
US20100256816A1 (en) * | 2004-05-06 | 2010-10-07 | Popp Shane M | Manufacturing execution systems (MES) |
US20100324716A1 (en) * | 2004-05-06 | 2010-12-23 | Popp Shane M | Monitoring pharamceutical manufacturing processes |
US8591811B2 (en) | 2004-05-06 | 2013-11-26 | Smp Logic Systems Llc | Monitoring acceptance criteria of pharmaceutical manufacturing processes |
US9092028B2 (en) | 2004-05-06 | 2015-07-28 | Smp Logic Systems Llc | Monitoring tablet press systems and powder blending systems in pharmaceutical manufacturing |
US20080123637A1 (en) * | 2005-06-03 | 2008-05-29 | Ellenberger & Poensgen Gmbh | Multiplexing system for controlling loads in boats or mobile homes |
US20070016870A1 (en) * | 2005-07-15 | 2007-01-18 | Microsoft Corporation | Control panel framework |
US20110026535A1 (en) * | 2005-11-29 | 2011-02-03 | Daisuke Ajitomi | Bridge apparatus and bridge system |
US9258137B2 (en) * | 2005-11-29 | 2016-02-09 | Kabushiki Kaisha Toshiba | Bridge apparatus and bridge system with a virtual device for protocol conversion |
US8001219B2 (en) | 2006-03-16 | 2011-08-16 | Exceptional Innovation, Llc | User control interface for convergence and automation system |
US7966083B2 (en) | 2006-03-16 | 2011-06-21 | Exceptional Innovation Llc | Automation control system having device scripting |
US8155142B2 (en) | 2006-03-16 | 2012-04-10 | Exceptional Innovation Llc | Network based digital access point device |
US8209398B2 (en) | 2006-03-16 | 2012-06-26 | Exceptional Innovation Llc | Internet protocol based media streaming solution |
US8725845B2 (en) | 2006-03-16 | 2014-05-13 | Exceptional Innovation Llc | Automation control system having a configuration tool |
US8271881B2 (en) | 2006-04-20 | 2012-09-18 | Exceptional Innovation, Llc | Touch screen for convergence and automation system |
US7667968B2 (en) | 2006-05-19 | 2010-02-23 | Exceptional Innovation, Llc | Air-cooling system configuration for touch screen |
US7962130B2 (en) | 2006-11-09 | 2011-06-14 | Exceptional Innovation | Portable device for convergence and automation solution |
US8364319B2 (en) * | 2008-04-21 | 2013-01-29 | Inncom International Inc. | Smart wall box |
US20100236824A1 (en) * | 2008-04-21 | 2010-09-23 | Inncom International Inc. | Smart wall box |
US20100057943A1 (en) * | 2008-08-28 | 2010-03-04 | Robert Bosch Gmbh | System and method for connecting a security system using a network |
US8412789B2 (en) | 2008-08-28 | 2013-04-02 | Robert Bosch Gmbh | System and method for connecting a security system using a network |
US20110213867A1 (en) * | 2010-02-26 | 2011-09-01 | Mccoy Sean | Simultaneous connectivity and management across multiple building automation system networks |
US8219660B2 (en) * | 2010-02-26 | 2012-07-10 | Trane International Inc. | Simultaneous connectivity and management across multiple building automation system networks |
AU2012325996B2 (en) * | 2011-10-18 | 2016-08-25 | Schneider Electric Buildings Americas, Inc. | Self-healing communications network |
US9313042B2 (en) | 2011-10-18 | 2016-04-12 | Schneider Electric Buildings, Llc | Self-healing communications network |
US9497038B2 (en) | 2011-10-18 | 2016-11-15 | Schneider Electric Buildings, Llc | Self-healing communications network |
WO2013059495A1 (en) * | 2011-10-18 | 2013-04-25 | Schneider Electric Buildings, Llc | Self-healing communications network |
JP2015503788A (en) * | 2011-12-26 | 2015-02-02 | アーベーベー・リサーチ・リミテッドAbb Research Ltd. | Relay interface module for distributed control systems |
WO2014143798A3 (en) * | 2013-03-15 | 2014-11-13 | Siemens Aktiengesellschaft | Redundant bus fault detection |
US9244753B2 (en) | 2013-03-15 | 2016-01-26 | Siemens Schweiz Ag | Redundant bus fault detection |
EP2911128A1 (en) * | 2014-02-24 | 2015-08-26 | Siemens Schweiz AG | Hazard warning assembly |
US20150300671A1 (en) * | 2014-04-22 | 2015-10-22 | Trane International Inc. | System and method for controlling hvac equipment so as to obtain a desired range of a sound pressure level and/or sound power level |
US9841210B2 (en) | 2014-04-22 | 2017-12-12 | Trane International Inc. | Sound level control in an HVAC system |
US10372092B2 (en) * | 2014-04-22 | 2019-08-06 | Trane International Inc. | System and method for controlling HVAC equipment so as to obtain a desired range of a sound pressure level and/or sound power level |
US10551086B2 (en) | 2014-04-22 | 2020-02-04 | Trane International Inc. | Sound level control in an HVAC system |
US9892073B1 (en) * | 2014-10-06 | 2018-02-13 | Master Lock Company Llc | Bus addressing systems and methods using repurposed bits |
US10884966B2 (en) | 2018-12-04 | 2021-01-05 | Palo Alto Research Center Incorporated | Method and apparatus to prevent a node device from transmitting an unallowable message onto a CAN bus |
Also Published As
Publication number | Publication date |
---|---|
US20050288823A1 (en) | 2005-12-29 |
WO2004079461A2 (en) | 2004-09-16 |
WO2004079461A3 (en) | 2005-09-15 |
US20090105846A1 (en) | 2009-04-23 |
US7650323B2 (en) | 2010-01-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20040176877A1 (en) | Building automation system and method | |
US7433740B2 (en) | CAN communication for building automation systems | |
US7089066B2 (en) | Distributed control systems and methods | |
US6901439B1 (en) | Method of adding a device to a network | |
US7761563B2 (en) | BACnet communication Status objects and methods of determining communication status of BACnet devices | |
CN108432282B (en) | Method and apparatus for managing electronic devices through wireless communication | |
US6574234B1 (en) | Method and apparatus for controlling network devices | |
US7126291B2 (en) | Radio frequency lighting control system programming device and method | |
KR100559026B1 (en) | Home network system | |
US20040218591A1 (en) | Bridge apparatus and methods of operation | |
US20150084547A1 (en) | DALI commissioning tools and methods for implementing | |
US20080069121A1 (en) | Gateway For A Local Network System | |
CN108886482B (en) | Method for configuring, controlling or monitoring a home automation installation | |
CA2725242A1 (en) | Methods and apparatus for identifying and categorizing distributed devices | |
KR20020091312A (en) | Control System for Home Appliance Network | |
US8484323B2 (en) | Network system connected with multiple master devices and method for operating the same | |
JP2000269998A (en) | Setting method for decentralized system | |
CN1897060A (en) | Network household electrical-appliance with related-controlling function and controlling method | |
WO2000043900A1 (en) | Method of adding a device to a network | |
US20050049726A1 (en) | Input device for building automation | |
US20200371651A1 (en) | User interface device updating system and method | |
AU2022100049A4 (en) | A system for configuring a control device of a mesh network of connected devices | |
CN215576153U (en) | 485 intelligent home gateway system | |
KR100648795B1 (en) | Method for Controlling Electrical Appliances of Home Network System | |
KR101094218B1 (en) | Home Network include Message Hooking Handler and the Method discrimination between Master Packet and Slave Packet in the Above Message Hooking Handler |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: COLORADO VNET, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HESSE, SCOTT;NICOLAY, WILLIAM;ADAMSON, HUGH P.;REEL/FRAME:013908/0311 Effective date: 20030227 |
|
STCB | Information on status: application discontinuation |
Free format text: EXPRESSLY ABANDONED -- DURING EXAMINATION |
|
AS | Assignment |
Owner name: RUSSOUND ACQUISITION CORP., NEW HAMPSHIRE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COLORADO VNET, LLC;REEL/FRAME:024823/0476 Effective date: 20100806 |
|
AS | Assignment |
Owner name: COLORADO VNET CORP., NEW HAMPSHIRE Free format text: CHANGE OF NAME;ASSIGNOR:RUSSOUND ACQUISITION CORP.;REEL/FRAME:024933/0412 Effective date: 20091015 |
|
AS | Assignment |
Owner name: 3VNET, INC., FLORIDA Free format text: CHANGE OF NAME;ASSIGNOR:COLORADO VNET CORP;REEL/FRAME:030111/0296 Effective date: 20120503 |
|
AS | Assignment |
Owner name: AUTOMATED CONTROL TECHNOLOGY PARTNERS, INC., FLORI Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:3VNET,INC.;REEL/FRAME:030460/0468 Effective date: 20130515 |
|
AS | Assignment |
Owner name: GOOGLE INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AUTOMATED CONTROL TECHNOLOGY PARTNERS, INC.;REEL/FRAME:031515/0743 Effective date: 20130819 |