US20060271204A1

US20060271204A1 - Hot Reprogrammability of Building Automation Devices

Info

Publication number: US20060271204A1
Application number: US11/462,749
Authority: US
Inventors: Scott Hesse; Gary Kiwimagi; Craig Ogawa
Original assignee: Colorado vNet LLC
Current assignee: RUSSOUND ACQUISITION CORP; Google LLC
Priority date: 2003-04-24
Filing date: 2006-08-07
Publication date: 2006-11-30
Also published as: WO2004097557A3; US7089066B2; US20040215778A1; WO2004097557A2

Abstract

Systems and methods for implementing hot reprogrammability of building automation devices are disclosed. In an exemplary embodiment a method to soft-update a building automation device may comprise issuing a signal to the building automation device in a response to an event. The method may also comprise executing at least one script at the building automation device in response to receiving the signal to control an automation functioning response to the event based only instructions in the at least one script. The method may also comprise replacing the at least one script with at least one updated script to change control of the automation functioning response to the same event without having to make any hardward changes at the building automation device.

Description

PRIORITY CLAIM

This application claims priority as a continuation-in-part of co-owned U.S. patent application Ser. No. 10/422,525 for “Distributed Control Systems and Methods ” of Hesse, et al., filed Apr. 24, 2003, hereby incorporated by reference in its entirety as though fully set forth herein.

BACKGROUND

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 may be implemented using extensive computer networks. Computer networks are known in which a server computer issues a series of commands over an Ethernet network to an output device. The commands are complex data structures requiring the server computer to establish an elaborate communications protocol between the server computer and the output device, followed by the server transmitting multiple data packets containing the commands.
Transmitting these commands consumes significant bandwidth on the network, especially when more than one command is issued to the same or multiple output devices at the same time or within a close timeframe. Network performance decreases, resulting in slow transmission speeds and sometimes even recognizable delays in the response time. Transmitting commands also increases the potential for data corruption resulting in failed operations. In addition, when the server computer fails, all of the devices on the network are “down.”

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high-level schematic diagram of an exemplary distributed control system.
FIG. 2(a) and (b) are high-level schematic diagrams of an exemplary node that may be implemented in a distributed control system.
FIG. 3 is an illustration of an exemplary signal that may be implemented in a distributed control system.
FIG. 4 is a portion of one embodiment of a script which may be used with the distributed control system of the present invention.
FIG. 5 is a flowchart illustrating exemplary operations in an exemplary distributed control system.

DETAILED DESCRIPTION

Distributed control systems are disclosed as it may be used in a building automation environment, although other uses are also contemplated as being within the scope of the invention (e.g., manufacturing, water supply monitoring, and a variety of other environments). Briefly, distributed control system may be used to automate various functions (e.g., control one or more loads), such as, but not limited to, lighting, climate control, audio/visual output, and various monitoring systems (e.g., security), to name only a few examples.
In an exemplary embodiment, the distributed control systems may include a number of automation devices or “nodes” operatively associated with one another over one or more automation network(s). The nodes may comprise any of a wide variety of control and/or controlled devices now known or later developed. In a building automation environment, for example, the nodes may be devices that respond to events (e.g., keypads, temperature sensors, timers, water-level sensors), devices that control various functions (e.g., lighting controls, motor controls), or a combination thereof.
In exemplary embodiments, individual nodes may be programmed and reprogrammed without affecting the other nodes on the network, without interfering with the operation of other nodes or the building automation network, and without having to shut off or restart other nodes or the building automation network. Accordingly, the distributed control system may be readily modified for different and/or additional devices and functions at any time, either locally or directly at the node, or from a remote location by the user (e.g., a homeowner or service provider). The distributed control system may also be readily modified at any time, even after the initial installation, allowing automated functions to be readily tailored for the user's preferences.
Exemplary System
FIG. 1 is a high-level schematic diagram of any exemplary distributed control system. The distributed control system 100 may comprise a number of automation devices or “nodes” 110. In the embodiment shown in FIG. 1, the nodes 110 are operatively associated with one another over one or more networks 130 (cumulatively referred to as the “automation network”), although it is understood that a “stand-alone” node may also be implemented.
Nodes 110 may be linked to one another over various types of networks. According to one embodiment, nodes 110 are linked using a controller area network (CAN) bus. Such an embodiment of building automation system 100 is described in more detail in co-pending, co-owned U.S. patent application Ser. No. 10/382,979, entitled “BUILDING AUTOMATION SYSTEM AND METHOD” of Hesse, et al., filed on Mar. 5, 2003, which is hereby incorporated herein by reference for all that it discloses.
Briefly, the CAN bus comprises a two-wire differential serial data bus. The CAN bus 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 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 specification for the CAN bus now know or later developed are also contemplated as being within the scope of the invention.
It is understood, however, that the present invention is not limited to use with the CAN bus and other types and/or configurations of networks are also contemplated as being within the scope of the invention. Other networks may also comprise an Ethernet or a wireless network (e.g., radio frequency (RF), BLUETOOTH™, ZIGBEE™), to name only a few. In addition, the network 130 may comprise more than one network (e.g., 131), or subnets as they are sometimes referred to. In another embodiment, for example, the network may comprise a plurality of CAN bus subnets, each linked to one another by an Ethernet network. Bridging apparatus or bridge 180 may be provided to link the networks to one another.
It is also understood that nodes 110 may be operatively associated with the network 130 in any suitable manner, including by permanent, removable, or remote link. By way of example, nodes 110 may be permanently linked to the network 130 by a hard-wire connection. Alternatively, nodes 110 may be removably lined to the network by a “plug-type” connection. Nodes 110 may also be remotely linked to the network, for example via an RF link. Suitable interfaces may be provides for nodes 110 for issuing and receiving signals over the network 130. Such interfaces can be readily provided by one skilled in the art after having become familiar with the teachings of the present invention.
Before continuing, it should be noted that the distributed control system 100 may be provided with an optional link 160 (e.g., linked to the network 130 via an interface). In one embodiment, link 160 may comprise an external link from another network such as the Internet through an Internet service provider (ISP). In another embodiment, link 160 may comprise a link from another device on the same network (e.g., bridge 180 or server computer). Link 160 may be used to import/export the scripts 400 to the nodes 110 during installation or to configure or reconfigure one or more of the nodes 110 at a later time.
Of course, it is understood that the link 160 is not limited to an ISP link. In other embodiments, the link 160 may be via a local area network (LAN), a wide area network (WAN), an Intranet, a telephony link, a digital subscriber line (DSL), T-1 connection, cellular line, satellite link, etc. In addition, 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, link 160 may comprise a temporary connection for use by a service technician or the user. For example, the link 160 may comprise a link for connecting a laptop computer to the network 130.
Nodes 110 may be any device or combination of devices generally configured to respond to an event. Nodes 110 may comprise, but are not limited to, keypads, knobs, sliders, touch-screens, graphical user interfaces (GUI), control systems (e.g., lighting control circuits, HVAC systems, security systems), personal computers (PC) and PC accessories, and other devices that are now known or later developed. In addition, nodes 110 may be operatively associated with, and receive input from external devices (e.g., clocks, water level sensors, temperature sensors, light sensors).
FIGS. 2(a) and (b) are high-level schematic diagrams of an exemplary node that may be implemented in a distributed control system. FIG 2(a) shows one embodiment of an “unscripted” node 200 (e.g., a keypad). Unscripted node 200 may comprise a controller 210 operatively associated with the network 130 via network interface 220. Controller 210 is preferably configured to respond to an event (e.g., receive input 230) by generating a signal 300 associated with the event (e.g., identifies the event). Optionally, the signal 300 may also contain a field identifying an address of the source of the event. Controller 210 may be provided with computer-readable program code (e.g., firmware on computer readable storage 270). In one embodiment, computer-readable program code may comprise program code for processing an event 212 and program code for generating and/or issuing a signal 214. Accordingly, the controller 210 may respond to an event (e.g., by receiving input and generating a signal corresponding to the event). Controller 210 may also generate output 240. For example, output 240 may comprise lighting and LED light (e.g., indicating a pressed key on a keypad, a status light, etc.).
It is noted that controllers such as provided for unscripted node 200 that can perform one or more predetermined functions are well-known in the electronics art and may comprise, by way of example, one or more programmable logic devices (PLDs) such as a field programmable gate array (FPGA), application-specific integrated circuit (ASIC), or microprocessor, to name only a few. It is also noted that network interfaces 220 are also readily available and the selection of a suitable network interface will depend to some extent of the type of network 130.
It is also well within the ability of one skilled in the art to provide computer-readable storage 270 for use with the present invention. Exemplary embodiments of computer-readable storage include, but are not limited to various types of programmable memory, read-only memory (ROM), random access memory (RAM), flash memory, magnetic storage, a combination thereof, etc. It is noted that the memory can also be an integral part of the controller. Further explanation of computer-readable storage 270 is not necessary for a complete understanding of the invention, and therefore is not described in further detail herein.
Unscripted node 200 is preferably used with a “scripted” node. Scripted node 250 is shown according to one embodiment in FIG. 2(b) and may comprise a distributed controller 211 is also preferably operatively associated with computer-readable storage 271. Computer-readable storage 271 may be accessed before, during, or after installation (e.g., via link 160) to provide at least one script for use with the scripted node 250.
Distributed controller 211 is preferably also configured to respond to an event. For example, distributed controller 211 may respond to signal 300 or other input received over network 130. Distributed controller 211 may also generate output (e.g., issue a signal over network 130).
Distributed controller 211 preferably comprises computer-readable program code (e.g., residing on computer-readable storage 270) for responding to signal 300 or other input. In one embodiment, distributed controller 211 may comprise a signal filter 262, program code for executing scripts 264, and program code for controlling one or more loads 266.
Signal filter 262 may be provided to determine whether a signal 300 issued over the network 130 is intended for scripted node 250. For example, signal filter 262 may compare the event associated with the signal to a one or more types of events that the scripted node 250 responds to (e.g., as defined by the script header).
If the signal 300 is intended for scripted node 250, program code for executing the script may read the signal 300 and execute at least one script corresponding to the signal. Embodiments of scripts are described in more detail below. For now, it is enough to understand that the executed script(s) may perform a function, and preferably drives a load (e.g., turn on a lighting circuit).
An unscripted node 200 may receive input and issue signals associated with the input to another node. Unscripted node 200 may receive signals from other nodes and issue a response or action such as, e.g., sending a signal indicating an LED state, or activating an LED. Likewise, a scripted node 250 may receive signals from other nodes and perform one or more functions (e.g., driving a load) corresponding to the signals as instructed by the executed script(s). However, it is understood that the nodes 110 are not limited only to these operations. For example, nodes 110 can be configured to receive input, issue signals and/or perform one or more functions (e.g., driving a load). Such a node, although not shown, may be readily provided by combining components from both embodiments shown in FIGS. 2(a) and (b) and described above.
It is also noted that nodes 110 may also be configured with other sources to receive input and/or send output, and are not limited to I/O operations only with other nodes 110. For example, nodes 110 may receive input directly from sensors or timers operatively associated with the nodes 110, and send output to displays, data logs, etc.
As will be readily appreciated by those skilled in the art, nodes 110 may be provided with various ancillary devices, for example, power supplies, electronic controls, input/output (I/O) devices, 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.
In operation, one or more of the nodes 110 respond to various events. The scope of the present invention is not limited to any particular type of event. By way of example, events may include, but are not limited to a user pressing a key on a keypad, a clock indicating the time, a light sensor indicating the level of outdoor light, a water level sensor indicating the water level in a body of water, a flow control sensor indicating the flow of water, to name only a few.
As briefly described above, an unscripted node 200 may respond to an event by issuing a signal 300 (e.g., over network 130) to a scripted node 250. For purposes of illustration, an unscripted keypad may issue one or more signals in response to the user pressing a key (or sequence of keys). However, it is understood that in other embodiments, a scripted node 250 may issue a signal 300 to an unscripted node 200, or a scripted node 250 may issue a signal 300 to another scripted node 250.
FIG. 3 is an illustration of an exemplary signal that may be implemented in a distributed control system. Signal 300 may comprise one or more fields 310-330. Preferably, at least one of the fields comprises an Event ID field 320 which comprises an event identifier. Signal 300 may also comprise one or fields. For example, signal 300 may comprise an address field 310 with the network address of one or more of the nodes 110 so that the signal 300 can be delivered to one or more addressed nodes in the network 130.
In one embodiment, the node 110 generating signal 300 may issue redundant signals 300. A redundant signal 300 preferably is a copy of the signal 300, which may be issued over the network 130 sequentially, or at a later time (e.g., if the first signal is not received or is corrupted). Accordingly, if one of the signals 300 is misdirected, corrupted or otherwise unusable upon receipt by another device, the redundant signal is issued to the node 110. Redundant signal 300 may be issued automatically (e.g., following a time-out) or at the request of one or more of the nodes 110.
Other embodiments are also contemplated as being within the scope of the invention. As briefly mentioned above, signals 300 may be addressed to specific devices or categories of devices. Alternatively, signal 300 may be a global signal that is issued to all of the nodes 110 on the network 130 or one or more subnets 131. For example, signal 300 may be addressed to groups of nodes 110, such as all the outdoor lighting, so that all of the functions associated with those nodes 110 can be controlled without the need for issuing separate signals to each node 110.
the node(s) receiving signal 300 may respond by executing at least one script to perform any one or more of a variety of functions. Script(s) 400 for performing various functions may be provided on the computer-readable storage 271 of a scripted node 250 and can be executed at the scripted node 250 by the distributed controller 211. In addition, other messages can be received by the node 110 and processed locally without the use of a script.
Executing the at least one script performs one or more functions, and preferably drives a load. For example, the executed script(s) may activate or deactivate a load, and preferably even control one or more parameters of the load (e.g., slew rate or intensity in the case of lighting). If the node 110 is a triac board, for example, the executed program code may turn on lighting (e.g., the load) to 50 % intensity by slewing over 30 seconds.
It will be readily appreciated upon understanding the invention that the manner in which the load is controlled and/or the type of load that is controlled can be readily modified or altogether changed by modifying or replacing the script(s). By way of example, one or more of the buttons on a keypad can be defined to control one or more loads according to various parameters, and later the same buttons can be defined to control one or more different loads, and/or to control the same load in a different manner by modifying or replacing the scripts at the keypad and/or the node controlling the load. The functions of the nodes can be defined and/or redefined by the script(s), without having to modify the hardware itself.
The script(s) may be defined based on various parameters, such as the needs and desires of the building occupant. Although the script(s) may be generic (i.e., applicable to one or more predefined configurations), the script(s) are preferably custom or tailored for each use and is therefore defined once the configuration of a particular building automation system is known. As previously described, the script(s) can preferably also be reconfigured based on the changing needs and/or desires of the building occupants.
It is understood that the script(s) may be defined in any suitable manner. Scripts are computer-readable program code optimized for programmer efficiency (e.g., it is relatively easy to write, flexible, and readily modified). Scripts are preferably independent of the type of processor and/or operating system and are therefore portable to a variety of different environments. Among other advantages, scripts may also comprise predefined, high-level routines, such as string manipulation operators, regular expressions, and associative arrays.
FIG. 4 is a portion of one embodiment of a script 400 which may be used with the distributed control system of the present invention. It is noted, however, that the scripts are not limited to any particular format and the embodiment shown in FIG. 4 is merely exemplary for purposes of illustrating its use with the present invention.
The script 400 shown in FIG. 4 may reside at one or more of the scripted nodes 250. According to this embodiment, each line of script 400 comprises a hexadecimal address 410, a data type 415, and a configuration variable 420. In this embodiment, lines 440, 445 of the script 400 are headers which describe a first and second state of a keypad, respectively, and point to script commands. Lines 450 and 455 of script 400 describe script commands or command sets that the script headers 440, 445 point to, respectively.
It is understood that other exemplary embodiments of scripts may comprise compiled languages and assembly language which can be readily modified to change the functionality of the node 110 without having to modify the hardware itself.
In exemplary embodiments, the script(s) may be modified or replaced. Modifying or replacing the program code is particularly advantageous when one or more nodes 110 are added or removed from the building automation system 100, or where the user desires a change. For example, the script(s) may be modified where the user desires a change. For example, the script(s) may be modified where the user desires to change one or more parameters for node 110 (e.g., defining a new key, changing the lighting intensity or slew rate). For example, when the building changes occupancy, the script(s) may be readily changed to reflect needs and/or desires of the new occupants.
It is understood that node 110 may be provided with script(s) 400 at any time, and may be updated and/or modified at any time to change one or more functions of the node 110 and/or fix program “bugs”. For example, node 110 may be provided with script(s) 400 during manufacture, during installation, or at any time thereafter.
The nodes may also be reprogrammed without having to shut down the automation network, or having to shut down(e.g., turn-off, restart, or otherwise take offline) the other nodes in the automation network. This may be referred to as “hot reprogramming” or “hot reprogrammability” and can be accomplished by updating firmware (e.g., program code residing at the node 110 which reads the signals and executes the corresponding script(s) 400), and/or updating one or more script 400 at the node 110.
In an exemplary embodiment, the bridge 180 (or other computer system) receives firmware and/or script 400 updates. For example, the bridge 180 may receive updates from a remote site (e.g., via an Internet connection). Or for example, the bridge 180 may receive updates generated by a user on-site and linked to the bridge 180. The bridge 180 determines which node(s) 110 in the automation system is to be updated. For example, the bridge 180 may implement a version table identifying each node 110 in the automation network and which firmware version and/or scripts 400 reside at the corresponding nodes 110. When an update is received, the bridge uses the version table to identify node(s) 110. When an update is received, the bridge uses the version table to identify node(s) 110 with an older version of the firmware and/or scripts 400. Alternatively, the user may identify for the bridge 180 one or more of the node(s) 110 that is to be updated.
After identifying the node(s) 110 to be updated, the bridge 180 may “wrap” the firmware and/or scripts 400 in one or more CAN packet (or other suitable protocol) for transmission to the node 110 over the automation network. The bridge 180 “wraps” the firmware and/or scripts 400 by parsing the code comprising the firmware and/or scripts and entering the parsed data into the data portion of the packet. Additional identifiers for reassembling the firmware and/or scripts 400 at the node 110 may also be provided. For example, identifiers may be provided for the start of the code, the ordering of the code, and the end of the code. In addition, the bridge 180 addresses in the packet the node(s) that are to receive the update.
The bridge 180 may then issue the packet to the node(s) 110 over the automation network. After being received at the node(s) 110, the node reassembles the firmware and/or scripts 400 and replaces earlier versions at the node(s) 110. It is noted that only the node(s) 110 receiving the updates are take offline during the update. That is, the node(s) 110 receiving the updates may be logically disconnected from the automation network while replacing the firmware and/or scripts 400 so that the previous version can be removed and the node restarted (if necessary) without interruptions from other operations in the automation network. During this process, however, the other nodes remain online and are able to send, receive, and respond to communications in the automation network.
Optionally, the bridge 180 may implement failure monitoring and recovery operations. In an exemplary embodiment, the node(s) 110 receiving the updates issue at least one acknowledgement (ACK) indicating that each packet (or all of the packets) were received for the update. If the acknowledgement(s) are not received by the bridge 180 within a predetermined time, the bridge 180 may determine that transmission failed and reissue the packets. In another exemplary embodiment, the bridge 180 may test the node(s) 110 to determine whether the update was successful. For example, the bridge 180 may ping the node(s) 110 and in response the nodes(s) 110 respond with version information. If the version information does not match the updated version information, the bridge 180 may determine that the update was unsuccessful and retry the update. If the bridge 180 is unsuccessful at retrying the update (e.g., the node is “hung-up” and requires user intervention to hard-reset the node), the bridge 180 may issue an alert to the user or service provider.
Exemplary Operations
Distributed control system 100 may be operated according to embodiments of the invention, as follows. Node 110 may respond to an event by either executing at least one script to perform a function, or issuing a signal 300 to one or more of the other nodes. The nodes 110 may in turn perform a function corresponding to the signal 300. By way of example, when a user presses a key at a first node (e.g., 111), the first node 111 may issue a signal 300 associated with the event. The signal 300 may be received at a second node (e.g., 112), wherein the second node performs one or more functions (e.g., adjust lighting intensity) corresponding to the signal 300.
FIG. 5 is a flowchart illustrating exemplary operation in an exemplary distributed control system. In operation 500, node 110 may respond to an event 501, (e.g., a keypad button being pushed, output from a timer or sensor, etc.) by performing a function in operation 510. For example, the node 110 may light an LED on the keypad. As another example, the node 110 may execute one or more scripts. Alternatively, or in addition to performing a function, node 110 may generate a signal 300 associated with the event in operation 520. By way of example, node 110 may generate signal(s) that are representative of input received by the node 110 (e.g., the key(s) a user pressed). In another example, executing at least one script (e.g., in operation 510) may generate signal(s) at node 110. In any event, the signal(s) 300 may be received by one or more of the other nodes 110 (or by itself, e.g., in a stand-alone embodiment), in operation 530. Each node 110 receiving the signal determines whether it should respond to the signal 300 in operation 540.
According to one embodiment, the signal(s) 300 are issued by broadcasting the signal(s) 300 over the network 130 to each of the other nodes 110. In this embodiment, operation 540 may comprise signal filter 262 comparing the Event ID 320 of received signal 300 to events that the node 110 responds to. The node 110 responds in operation 550 if the event(s) identified by the Event ID 320 are a type that the node 110 responds to. If the node 110 determines that it should not respond, it does nothing (i.e., the node “ignores” the signal) by ending in operation 555.
In other embodiments, the signal 300 may be addressed to one or more of the nodes 110. Accordingly, the signal filter 262 determines whether the node 110 should respond to the signal 300 based on the Address 310 of the signal 300. It is noted that in any embodiment, more than one node 110 may respond to the signal 300.
The node 110 responds to the signal 300 in operation 550 by executing at least one script corresponding to the signal 300. In exemplary embodiments, executing the script(s) drives a load 560. In one example, the node 110 may comprise lighting controls (e.g., the load). Accordingly, executing the script(s) controls lighting on a lighting circuit.
Having generally described operation of the distributed control system 100 according to embodiments of the invention, the following example is provided to be illustrative of operation of the distributed control system 100 in one embodiment of the invention. In this example, a keypad is a scripted node 250, and a lighting control circuit is an unscripted node 200. With reference again to FIGS. 2(a) and (b), and FIG. 4, the keypad responds to a user pressing a key by executing the script 400 (FIG. 4), as follows. In this example, we will consider two states of one of the keys (i.e., State 01 and State 02).
In the first state (e.g., off), the keypad button is depressed and has a state cButtonState=0×00(line 0000000e). No commands are logically associated with the first state in this example (line 0000000f). Accordingly, nothing happens.
In the second state (e.g., on), keypad button is released and has a state cButtonState=0×001(line 00000017). Two commands are logically associated with the second state in this example (line 00000018). The first command is defined by lines 450. In this example, lines 450 define a load wType=0×0002 (e.g., a lighting control), and corresponding parameters, such as time delay (line 00000021), slew rate (00000022), and so forth.
The second command is defined by lines 455. In this example, lines 455 define a load wType=0×001 (e.g., and LED light next to the key that was pressed), and corresponding parameters such as activating the LED (line 0000002b).
Accordingly, program code for executing the script 400 may call program code for generating a signal 300 and issuing the signal 300 over the network. Signal 300 may comprise control instructions based on the executed script 400. Control instructions are preferably recognizable by the node 110 receiving the signal 300 to activate the lighting circuit as described by the script.
It is readily apparent from an understanding of the above example that script 400 may be readily modified for use by a scripted lighting control. According to such an embodiment, the scripted lighting control may receive a signal 300 (e.g., from a keypad). Signal filter 262 at the scripted lighting control may determine whether the scripted lighting control should respond to the signal 300 (e.g., if the Event ID corresponds to functions in headers 440, 445 of script 400). If the scripted lighting control should respond to the signal 300, distributed controller 211 executes commands defined by lines 450, 455 of script 400. Executing the script may call program code for activating the lights according to the executed script 400.
Of course it is understood that the above example is merely illustrative of one embodiment of the invention, and the scope of the invention is not intended to be limited to the above example. For example, the lighting control in the above example may be a scripted node 250. The distributed control 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.
The following provides a brief overview of operation of the distributed control system 100 according to other embodiments contemplated as being within the scope of the invention. One such embodiment may comprise an unscripted node 200 responding to an event and a scripted node 250 receiving a signal 300 corresponding to the event from the unscripted node 200. In operation, the unscripted node 200 may respond to the event by issuing a signal 300 that identifies the event (e.g., “keypad button one pressed ”). The scripted node 250 receives the signal 300 identifying the event and executes at least one script provided at the scripted node 250 that corresponds to the signal 300 to perform one or more functions corresponding to the signal 300 (e.g., adjust lighting intensity).
In another embodiment, a scripted node 250 may respond to the event, and an unscripted node 200 may receive the signal 300. In operation, the scripted node 250 may respond to the event by executing script(s) provided to generate a signal 300. The signal 300 comprises a control instruction. The unscripted node receives the signal 300 and performs one or more functions defined by the control instruction.
In yet another embodiment, each of the nodes may be scripted nodes 250. In operation, one or more of the scripted nodes 250 may respond to an event by executing script(s). For example, the first node may execute script(s) to activate an LED light next to the key that ways pressed, and the scripted node 250 may also issue a signal 300. The one or more of the other scripted nodes 250 may receive the signal 300 and execute script(s) corresponding to the signal 300 to perform one or more functions (e.g., adjust lighting intensity) corresponding to the signal 300.
In still another embodiment, one or more of the nodes 110 may be “stand-alone” nodes. In operation, the stand-alone node responds to the event by executing script(s) provided at the stand-alone node to perform one or more functions without issuing a signal to the other nodes 110.
In yet other embodiments, a scripted node 250 may also function as an unscripted node 200. Accordingly, the distributed control system 100 can be configured with different types of nodes 110 or operating in different modes to operate according to the various embodiments described herein.
Of course distributed control system 100 may also comprise any combination of these embodiments. Further combinations will also be appreciated by the skilled in the art after having become familiar with the teachings of the present invention.
distributed control system 100 may also be operated to provide acknowledgements. In one exemplary embodiment, the executed script(s) may generate a command signal and issue it to another of the nodes 110. For example, a lighting control node may issue a command signal to a keypad node instructing the keypad node to turn on an LED light or display a message on an LCD display at the keypad indicating to the user that the lighting is turned on.
In another exemplary embodiment, the acknowledgement field of signal 300 may comprise an acknowledgement or “ACK” message. Likewise, the acknowledgement field may be a negative acknowledged or “NAK” message when the received signal(s) cannot be read or are otherwise unusable. Other status signals may also be issued from the node 110 to another to indicate to the user and/or other devices the status of the node 110 issuing the status signal.
The operations shown and described herein are provided to illustrate exemplary embodiments for reprogramming nodes in an automation environment. It is noted that the operations are not limited to the ordering shown. In addition, other operation, not shown, may also be implemented.
In addition to the specific embodiments explicitly set forth herein, other aspects and embodiments will be apparent to those skilled in the art from consideration of the specification disclosed herein. It is intended that the specification and illustrated embodiments be considered as examples only.

Claims

1. A building automation system with hot reprogrammability of building automation devices, comprising:

an automation network communicatively coupling at leas one input device with a plurality of control devices, the input device generating a signal in response to an event and issuing the signal to at least one of the control devices;

at least one script provided at each of the plurality of control devices, the at least one script being executed at the at least one control device receiving the signal from the input device to control a building automation function in response to the event based on instruction in the at least one script;

a bridge communicatively coupled to the automation network, the bridge issuing an updated script to the at least one control device to change control of the building automation function.

2. The building automation system of claim 1, wherein the control of the building automation function is changed by replacing the at least one script with the updated script without changing the signal issued by the input device.

3. The building automation system of claim 1, wherein the control of the building automation function is changed without shutting down the automation network.

4. The building automation system of claim 1, wherein the control of the building automation function is changed without affecting other nodes on the automation network.

5. The building automation system of claim 1, wherein the control of the building automation function is changed during continued operation of the automation network.

6. The building automation system of claim 1, wherein the bridge wraps the updated script in a CAN packet for transmission over the automation network to the at least one control device.

7. The building automation system of claim 1, wherein the bridge monitors progress of updating the at least one control device.

8. The building automation system of claim 1, wherein the bridge retries updating the at least one control device after a failed attempt to update the at least one control device.

9. The building automation system of claim 1, wherein the bridge notifies a user after at least one failed attempt to update the at least one control device.

10. A method to soft-update a building automation device, comprising:

issuing a signal to the building automation device in response to an event;

executing at least one script at the building automation device in response to receiving the signal to control an automation function in response to the event based only instructions in the at least once script;

replacing the at least one script with at least one updated script to change control of the automation function in response to the same event without having to make any hardware changes at the building automation device.

11. The method of claim 10, wherein replacing the at least one script with the at least one updated script changes control of the automation function without changing the issued signal.

12. The method of claim 10, wherein replacing the at least one script with the at lest one updated script is without shutting down a building automation network.

13. The method of claim 10, wherein replacing the at least once script with the at least one updated script is without affecting other nodes on a building automation network.

14. The method of claim 10, wherein replacing the at least one script with the at least one updated script is during continued operation of a building automation network.

15. The method of claim 10, further comprising monitoring progress of replacing the at least one script.

16. The method of claim 15, further comprising retrying replacing the at least one script after a failed attempt.

17. The method of claim 15, further comprising notifying a user after at least one failed attempt at replacing the at least one script.

18. A system for updating a building automation device without changing hardware for the building automation device, comprising:

means for executing program code at the building automation device in response to receiving the signal to control an automation function in response to the event; and

means for changing control of the automation function in response to the same event without having to make any hardware changes at the building automation device.

19. The system of claim 18, wherein the means for changing control of the automation function comprising means for replacing the program code with updated program code.

20. The system of claim 18, wherein the means for changing control of the automation function replacing at least a portion of the program code without shutting down a building automation network and without affecting other nodes in the building automation network.