CA2661915C - Method and device for binding an automation component within a building automation system - Google Patents

Method and device for binding an automation component within a building automation system Download PDF

Info

Publication number
CA2661915C
CA2661915C CA2661915A CA2661915A CA2661915C CA 2661915 C CA2661915 C CA 2661915C CA 2661915 A CA2661915 A CA 2661915A CA 2661915 A CA2661915 A CA 2661915A CA 2661915 C CA2661915 C CA 2661915C
Authority
CA
Canada
Prior art keywords
binding
automation
automation component
processor
component
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.)
Active
Application number
CA2661915A
Other languages
French (fr)
Other versions
CA2661915A1 (en
Inventor
Norman R. Mcfarland
Geoffrey D. Nass
Pornsak Songkakul
Jeffrey A. Raimo
John A. Hendrix, Jr.
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens Industry Inc
Original Assignee
Siemens Industry Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Siemens Industry Inc filed Critical Siemens Industry Inc
Publication of CA2661915A1 publication Critical patent/CA2661915A1/en
Application granted granted Critical
Publication of CA2661915C publication Critical patent/CA2661915C/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L2012/284—Home automation networks characterised by the type of medium used
    • H04L2012/2841—Wireless
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements

Abstract

An automation component (200) configured for wireless communication within a building automation system is disclosed. The automation component includes a wireless communications component (210), a processor (202) in communications with the wireless communications component and a memory (204) in communication with the processor, the memory configured to stored computer readable instructions which are executable by the processor. The computer readable instructions are programmed to generate a binding request including a device identifier, broadcast the binding request (412) via the wireless communications component (210), and establish a binding relationship (426) based on a received response to the binding request. A method for binding an automation component within a building automation system is further disclosed. The method includes communicating a binding request (412) via a wireless communication link wherein the binding request includes a device identifier, receiving a binding response via the wireless communication link, and establishing a binding relationship (426) based on the received binding response.

Description

METHOD AND DEVICE FOR BINDING AN AUTOMATION COMPONENT WITHIN
A BUILDING AUTOMATION SYSTEM
[0001]
BACKGROUND
[0002] The present disclosure generally relates to building automation systems. In particular, the present disclosure relates to methods and devices for binding or linking automation components within a building automation system.
[0003] A building automations system (BAS) typically integrates and controls elements and services within a structure such as the heating, ventilation and air conditioning (HVAC) system, security services, fire systems and the like. The integrated and controlled systems are arranged and organized into one or more floor level networks (FLNs) containing application or process specific controllers, sensors, actuators, or other devices distributed or wired to form a network. The floor level networks provide general control for a particular floor or region of the structure. For example, a floor level network may be an RS-485 compatible network that includes one or more controllers or application specific controllers configured to control the elements or services within floor or region. The controllers may, in turn, be configured to receive an input from a sensor or other device such as, for example, a temperature sensor (RTS) deployed to monitor the floor or region. The input, reading or signal provided to the controller, in this example, may be a temperature indication representative of the physical temperature. The temperature indication can be utilized by a process control routine such as a proportional-integral control routine executed by the controller to drive or adjust a damper, heating element, cooling element or other actuator towards a predefined set-point.
[0004] Information such as the temperature indication, sensor readings and/or actuator positions provided to one or more controllers operating within a given floor level network may, in turn, be communicated to an automation level network (ALN) or =

building level network (BLN) configured to, for example, execute control applications, routines or loops, coordinate time-based activity schedules, monitor priority based overrides or alarms and provide field level information to technicians.
Building level networks and the included floor level networks may, in turn, be integrated into an optional management level network (MLN) that provides a system for distributed access and processing to allow for remote supervision, remote control, statistical analysis and other higher level functionality. Examples and additional information related to BAS configuration and organization may be found in U.S. patent serial No. 8,023,440, filed on October 31, 2006, and U.S. patent serial No.
7,860,495, filed on August 8, 2004.
[0005] Wireless devices, such as devices that comply with IEEE 802.15.4/ZigBee protocols, may be implemented within the control scheme of a building automation system without incurring additional wiring or installation costs.
ZigBee-compliant devices such as full function devices (FFD) and reduced function devices (RFD) may be interconnected to provide a device net or mesh within the building automation system. For example, full function devices are designed with the processing power necessary to establish peer-to-peer connections with other full function devices and/or execute control routines specific to a floor or region of a floor level network.
Each of the full function devices may, in turn, communicate with one or more of the reduced function devices in a hub and spoke arrangement. Reduced function devices such as the temperature sensor described above are designed with limited processing power necessary to perform a specific task(s) and communicate information directly to the connected full function device.
[0006] Wireless devices for use within the building automation system must be configured in order to establish communications with the different elements, components and networks that comprise the building automation system. Systems and method for configuring and establishing communications between the wireless devices and the automation components may be desirable and facilitate the setup, configuration, maintenance and operation of the building automation system.
SUMMARY
[0007] The present disclosure generally provides for binding wireless devices and/or automation components operating within a building automation system (BAS).
Wireless devices and/or automation components need to be bound in order to communicate with each other. Generally the disclosed devices and methods are configured to wirelessly communicate information, identifiers and requests configured to establish binding relationships there between.
[0008] In one embodiment, an automation component configured for wireless communication within a building automation system is disclosed. The automation component includes a wireless communications component, a processor in communication with the wireless communications component and a memory in communication with the processor, the memory configured to stored computer readable instructions which are executable by the processor. The computer readable instructions are programmed to generate a binding request including a device identifier, broadcast the binding request via the wireless communications component, and establish a binding relationship based on a received response to the binding request.
[0009] In another embodiment, a method for binding an automation component within a building automation system is further disclosed. The method includes communicating a binding request via a wireless communication link wherein the binding request includes a device identifier, receiving a binding response via the wireless communication link, and establishing a binding relationship based on the received binding response.
[0010] In another embodiment, an automation component configured for wireless communication within a building automation system is disclosed. The automation component includes a processor configured to generate a binding request including a device identifier, a wireless transmitter configured to wirelessly broadcast the binding request to a second automation component, and a receiver configured to receive a binding response communicated from the second automation component, wherein a binding relationship is established with the second automation component based on the received response.
[0010a] In yet another embodiment, there is disclosed a method for binding an automation component within a building automation system, wherein the building automation system comprises a first network connected to a second network via a modular equipment controller, wherein automation components are coupled to the first and second networks and wherein two or more of the automation components form a subnet; the method comprising: a) initiating a binding sequence through a first automation component by means of a portable device that functions within the building automation system; b) communicating a binding request from the first automation component via a wireless communication link to a further automation component, wherein the binding request includes a first device identifier, the first device identifier comprising at least one of a logical identifier, an internet protocol address, a media access control address, and a local network address; c) receiving a binding response through the first automation component from the further automation component via the wireless communication link; and d) establishing a binding relationship based on the received binding response.
[0010b] In still another embodiment, there is disclosed an automation component for use in a building automation system, the automation component comprising: a wireless communication component; a processor that is in communication with the wireless communication component, the processor being configured to initiate a binding sequence by means of a portable device that is connectable to the automation component, communicate a binding request via the wireless communication component to a further automation component, wherein the binding request includes a device identifier, the device identifier comprising at least one of a logical identifier, an internet protocol address, a media access control address, and a local network address, receive a binding response from the further automation component via the wireless communication component, and establish a binding relationship based on the received binding response to the binding request;
and a memory that is in communication with the processor.
[0010c] In a further embodiment, there is disclosed a processor-readable storage medium having stored thereon processor-executable instructions that, when executed by a processor, cause an automation component comprising the processor to initiate a binding sequence by means of a portable device that is connectable to the automation component, communicate a binding request via a wireless communication component to a further automation component, wherein the binding request includes a device identifier, the device identifier comprising at least one of a logical identifier, an internet protocol address, a media access control address, and a local network address, receive a binding response from the further automation component via the wireless communication component, and establish a binding relationship based on the received binding response to the binding request
[0011] Additional features and advantages of the present invention are described in, and will be apparent from, the following Detailed Description and the figures.
BRIEF DESCRIPTION OF THE FIGURES
[0012] The method, system and teaching provided relate to binding automation components within a building automation system (BAS).
[0013] FIG. 1 illustrates an embodiment of a building automation system configured in accordance with the disclosure provided herein;
[0014] FIG. 2 illustrates an embodiment of a wireless device or automation component that may be utilized in connection with the building automation system shown in FIG. 1;
[0015] FIG. 3 illustrates an exemplary flowchart representative of an exemplary binding operation; and - 5a -
[0016] FIG. 4 illustrates an exemplary flowchart representative of a binding operation that may be implemented in connection with the building automation system shown in FIG. 1.
DETAILED DESCRIPTION
[0017] The embodiments discussed herein include automation components, wireless devices and transceivers. The devices may be IEEE 802.15.4/ZigBee-compliant automation components such as: a personal area network (PAN) coordinator which may be implemented as a field panel transceivers (FPX); a full - 5b -function device (FFD) implemented as a floor level device transceiver (FLNX);
and a reduced function device (RFD) implemented as a wireless room temperature sensor (WRTS) that may be utilized in a building automation system (BAS). The devices identified herein are provided as an example of automation components, wireless devices and transceivers that may be integrated and utilized within a building automation system embodying the teachings disclosed herein and are not intended to limit the type, functionality and interoperability of the devices and teaching discussed and claimed herein.
I. BUILDING AUTOMATION SYSTEM OVERVIEW
[0018] One exemplary building automation system that may include the devices and be configured as described above is the APOGEE system provided by Siemens Building Technologies, Inc. The APOGEE system may implement RS-485 wired communications, Ethernet, proprietary and standard protocols, as well as known wireless communications standards such as, for example, IEEE 802.15.4 wireless communications which are compliant with the ZigBee standards and/or ZigBee certified wireless devices or automation components. ZigBee standards, proprietary protocols or other standards are typically implemented in embedded applications that may utilize low data rates and/or require low power consumption.
Moreover, ZigBee standards and protocols are suitable for establishing inexpensive, self-organizing, mesh networks which may be suitable for industrial control and sensing applications such as building automation. Thus, automation components configured in compliance with ZigBee standards or protocols may require limited amounts of power allowing individual wireless devices, to operate for extended periods of time on a finite battery charge.
[0019] The wired or wireless devices such as the IEEE 802.15.4/ZigBee-compliant automation components may include, for example, an RS-232 connection with an RJ11 or other type of connector, an RJ45 Ethernet compatible port, and/or a universal serial bus (USB) connection. These wired, wireless devices or automation components may, in turn, be configured to include or interface with a separate wireless transceiver or other communications peripheral thereby allowing the wired device to communicate with the building automation system via the above-described wireless protocols or standards. Alternatively, the separate wireless transceiver may be coupled to a wireless device such as a IEEE 802.15.4/ ZigBee-compliant automation component to allow for communications via a second communications protocol such as, for example, 802.11x protocols (802.11a, 802.11b ...
802.11n, etc.) These exemplary wired, wireless devices may further include a man-machine interface (MMI) such as a web-based interface screen that provide access to configurable properties of the device and allow the user to establish or troubleshoot communications between other devices and elements of the BAS.
[0020] FIG. 1 illustrates an exemplary building automation system or control system 100 that may incorporate the methods, systems and teaching provided herein. The control system 100 includes a first network 102 such as an automation level network (ALN) or management level network (MLN) in communication with one or more controllers such as a plurality of terminals 104 and a modular equipment controller (MEC) 106. The modular equipment controller or controller 106 is a programmable device which may couple the first network 102 to a second network 108 such as a floor level network (FLN). The second network 108, in this exemplary embodiment, may include a wired network 122 that connects to building automation components 110 (individually identified as automation components 110a to 110f).
The second network 108 may further be coupled to wireless building automation components 112. For example, the building automation components 112 may include wireless devices individually identified as automation components 112a to 112f. In one embodiment, the automation component 112f may be a wired device that may or may not include wireless functionality and connects to the automation component 112e. In this configuration, the automation component 112f may utilize or share the wireless functionality provided by the automation component 112e to define an interconnected wireless node 114.
[0021] The control system 100 may further include automation components generally identified by the reference numerals 116a to 116g. The automation components 116a to 116g may be configured or arranged to establish one or more networks or subnets 118a and 118b. The automation components 116a to 116g such as, for example, full or reduced function devices and/or a configurable terminal equipment controller (TEC), cooperate to wirelessly communicate information between the second network 108, the control system 100 and other devices within the mesh networks or subnets 118a and 118b. For example, the automation component 116a may communicate with other automation components 116b to 116d within the mesh network 118a by sending a message addressed to the network identifier, alias and/or media access control (MAC) address assigned to each of the interconnected automation components 116a to 116g and/or to a field panel 120.
In one configuration, the individual automation components 116a to 116d within the subnet 118a may communicate directly with the field panel 120 or, alternatively, the individual automation components 116a to 116d may be configured in a hierarchal manner such that only one of the components for example, automation component 116c, communicates with the field panel 120. The automation components 116e to 116g of the mesh network 118b may, in turn, communicate with the individual automation components 116a to 116d of the mesh network 118a or the field panel 120.
[0022] The automation components 112e and 112f defining the wireless node 114 may wirelessly communicate with the second network 108, and the automation components 116e to 116g of the mesh network 118b to facilitate communications between different elements, section and networks within the control system 100.
Wireless communication between individual the automation components 112, 116 and/or the subnets 118a, 118b may be conducted in a direct or point-to-point manner, or in an indirect or routed manner through the nodes or devices comprising the nodes or networks 102, 108, 114 and 118. In an alternate embodiment, the wired network 122 is not provided, and further wireless connections may be utilized.
[0023] FIG. 2 illustrates an exemplary automation component 200 that may be utilized within the control system 100. The automation component 200 maybe be a full function device or a reduced function device and may be utilized interchangeably with the automation components 110, 112 and 116 shown and discussed in connection with FIG. 1. The automation component 200 in this exemplary embodiment may include a processor 202 such as an INTEL PENTIUM class processor in communication with a memory 204 or storage medium. The memory 204 or storage medium may contain random access memory (RAM) 206, flashable or non-flashable read only memory (ROM) 208 and/or a hard disk drive (not shown), or any other known or contemplated storage device or mechanism. The automation component may further include a communications component 210. The communications component 210 may include, for example, the ports, hardware and software necessary to implement wired communications with the control system 100.
The communications component 210 may alternatively, or in addition to, contain a wireless transmitter 212 and a receiver 214 communicatively coupled to an antenna 216 or other broadcast hardware.
[0024] The sub-components 202, 204 and 210 of the exemplary automation component 200 may be coupled and able to share information with each other via a communications bus 218. In this way, computer readable instructions or code such as software or firmware may be stored on the memory 204. The processor 202 may read and execute the computer readable instructions or code via the communications bus 218. The resulting commands, requests and queries may be provided to the communications component 210 for transmission via the transmitter 212 and the antenna 216 to other automation components 200, 112 and 116 operating within the first and second networks 102 and 108.
II. AUTOMATION COMPONENT BINDING
[0025] FIG. 3 illustrates an overview of a wireless binding operation or procedure 300 that may be implemented between one or more of the exemplary automation components 200 (see FIG. 2), the automation components 110, 112 and 116 (see FIG. 1) and/or a terminal equipment controller (TEC), other full function devices, a workstation 104, etc. within the control system 100. The wireless binding operation may be utilized to replace and/or augment traditional binding operations in which devices within the control system 100 are physically connected or wired together to define the networks 102, 108 and subnets 118a, 118b of the control system 100.

Binding as used herein describes the logical and communications relationship between devices, components and elements within the control system 100.
[0026] At block 302, one or more of the automation components, for example, the automation components 200, 112 and 116, to be bound together or with other components, elements or subsystems of the control system 100 may be physically setup or emplaced within the structure. While all of the automation components 200, 112 and 116 may be utilized interchangeably with the teachings disclosed herein, the automation component 200 will be referred to herein for convenience and clarity.
The physical setup may include mounting or otherwise positioning the automation component 200 within a given region or area or a structure to be monitored.
For example, if the automation component 200 is a wireless room temperature sensor (WRTS), it may be positioned within an area of the structure in which the temperature is to be monitored. The physical setup may further include positioning or mounting the automation component 200 within a specific distance or range of another automation component 200 and/or other full function or reduced function devices operating within the control system 100. For example, in order to establish the subnet 118b, the automation component 200 may be positioned within two hundred feet (200ft) or approximately sixty meters (60m) of another component or device. The physical setup may further include: ensuring broadcast or line-of-site communications around the mounting position for the automation component 200, checking or monitoring the power source of the automation component 200, e.g., verifying the fuel cell, battery, line power, magnetic resonance receiver, etc.
[0027] At block 304, the basic configuration, logical setup or commissioning of the automation component 200 may be established. The basic configuration may include a network name or alias, a media access control (MAC) address, a network or subnet password, etc. In one embodiment, the automation component 200 may be configured with a list or database of information detailing the component's communication schedule, other devices or components in the control system 100 to which communications should be established, communications or information priorities, etc. The basic configuration may be accomplished by way of a direct, e.g., wired, infrared, etc., connection between a portable device such as a laptop or personal digital assistant. Alternatively, each automation component 200 may be assigned a unique identifier or identification such as a hexadecimal code or string.
The unique identifier may allow a portable device to wirelessly communicate or connect with an automation component 200 that has not been fully configured by addressing commands or communications using the unique identifier. In this way, the portable device contacts the automation component 200 and provides the information, e.g., network alias, password, etc., necessary to complete the basic configuration.
[0028] At block 306, the portable device may connect to the automation component 200 and initiate a binding sequence between the component and one or more devices operating within the control system 100. For example, the portable device may be a laptop computer having a communications program such as, for example, WINDOWS 0 HyperTerminal or other man machine interface (MMI), into which a bind initiate command may be entered and provided to the automation component 200. The bind initiate command may include the network identifier, identification and/or alias of, for example, the terminal equipment controller, full function device or network, to which the automation component 200 is to be bound.
[0029] At block 308, the automation component 200, in response to the received bind initiate command, attempts to contact designated the terminal equipment controller, full function device or network. The communication attempt may query or challenge the designated device and upon receipt of a response establish a connection between the automation component 200 and the designated device. For example, the automation component 200 may initiate a handshake query or communication with the terminal equipment control to which it is to be bound.
The handshake or challenge may be a timed communication such that a response must be received by the transmitting automation component 200 within a given time period, e.g., ten (10) seconds, or else the communication will be denied.
[0030] At block 310, the status of the communication attempt may be evaluated.
If the communication is successful, e.g., the response was received within the allowed time period, the response includes the proper information, password, etc., and/or the response is provided in the proper format, then at block 312, the connection is established between the automation component 200 and the designated device. However, if the communication is not successful, e.g., the response was delayed, the response is incorrect or in provided in an improper format, then at block 314, the connection is not established and an error is generated. The error, in turn, may be communicated to the portable device and displayed via the HyperTerminal program. In another embodiment, the automation component 200 may include indicators such as, for example, light emitting diodes (LEDs) to provide a visual indication of successful or failed communication attempts.
[0031] FIG. 4 illustrates an embodiment of a wireless binding operation or procedure 400 that may be implemented between one or more of the exemplary automation components 200 (see FIG. 2), the automation components 110, 112 and 116 (see FIG. 1) and/or a terminal equipment controller (TEC), other full function devices, a workstation 104, etc. within the control system 100. In this exemplary embodiment, it is assumed that the automation component 200 has been powered up and configured with the basic information, passwords, etc. necessary to successfully perform the binding operation.
[0032] At block 402, the binding sequence may be initiated by sending a bind command to the man machine interface (MM I) of the automation component 200, e.g., the automation component to be bound to one or more of the networks 102, 108, 118, etc. As previously discussed, the bind command may be provided via communications program executing on a portable device in communication with the automation component 200. The bind command may include an address or identifier of the floor level network (FLN) or full function device to which the automation component 200 is to bind.
[0033] At block 404, the automation component 200 may attempt to join a personal area network (PAN). For example, the automation component 200 may attempt to join the PAN of a field panel transceiver (FPX) or floor level data transceiver (FLNX) positioned locally, i.e., nearby. The subsequent PAN of the field panel transceiver and the automation component 200 may form, for example, the subnet 118b.
[0034] At block 406, the status of the communication attempt may be evaluated.
If the communication is not successful, i.e., the automation component 200 cannot communicate or join the personal area network, then at block 408, an error may be generated. The error, in turn, may be communicated to the portable device and displayed via the HyperTerminal program. However, if the communication is successful and the automation component 200 is able to join the personal area network, then at block 410, the automation component prepares a binding request or signal that includes the address pattern of the floor level network automation component designated or provided with the initial bind command.
[0035] At block 412, the automation component 200 generates and transmits a broadcast message. The broadcast message is communicated to each floor level device transceiver (FLNX) and/or full function devices within a given area or region of the structure, e.g., a specific transmission area. An FLNX or other full function device that receives the broadcast message but does not match the specified address pattern will ignore or otherwise not respond to the message.
[0036] At block 414, the status of the broadcast message attempt may be evaluated. If the broadcast message is not successful because an FLNX or other full function device is not assigned the sought after address, then at block 416 the broadcast message will timeout as unanswered. However, if the broadcast message is received by the FLNX or other full function device assigned the correct address, then at block 418, the FLNX will broadcast a response or message back to the automation component 200. The response or message broadcast to the automation component 200 may include a temporary binding or code. The temporary binding or code may be associated with a timer or time period such as, for example, ten seconds (10 sec), after which the temporary binding or code may no longer be valid or used.
[0037] At block 420, the automation component 200 determines if multiple temporary bindings or codes have been received from one or more floor level device transceivers in range of the original broadcast message or binding request. If multiple temporary binding or codes have been received, then at block 422, the automation component 200 generates an error message which can be communicated to the portable device and displayed via the communications or HyperTerminal program. However, if multiple temporary bindings or codes have not been received within a given time period such as, for example, five seconds (5 sec), then at block 424, the automation component 200 can communicate a bind request to the FLNX or full function device that responded to the original broadcast message.
The automation component 200 may communicate the bind request multiple times, for example, once every two seconds (2 sec), in order to establish communications between the two devices.
[0038] At block 426, the FLNX or full function device, upon receiving the bind request, deletes any previous binding relationships established for the automation component 200. The FLNX or full function device will, in turn, stored the MAC
address or logical identifier associated with the automation component 200.
The stored MAC address or logical identifier can be saved or stored in a memory such as an EEPROM or other erasable non-volatile memory. Similarly, the FLNX or full function device will communicate a bind request back to the automation component 200 which, in turn, will establish a binding relationship with the full function device. If the temporary binding or code remains present from previous communications with the FLNX or full function device, the temporary binding can be converted to establish a permanent binding relationship.
[0039] At block 428, a success message or indication may be generated by the man machine interface (MM I) of the automation component 200. The success indication may be communicated to the portable device and displayed via the HyperTerminal program. In another embodiment, on or more light emitting diodes (LEDs) on the automation component 200 may be utilized to indicate the successful completion of the binding. If the binding relationship is not successfully established, but a previous binding relationship between the FLNX or full function device and the automation component 200 has been established, the previous binding relationship may not be deleted or erased allowing the automation component 200 to communicate with the appropriate network for example, the networks 102, 108 and 118.
[0040] At block 430, the automation component 200 may generate a report that includes the configuration parameters associated therewith. The generated report may then be communicated via the newly established binding relationship to the FLNX or full function device. If no response or acknowledgement is received from the FLNX or full function device after one or more communication attempts, then at block 432 a reporting flag can be enabled or set. The reporting flag indicates that whenever the automation component 200 "wakes up" or is otherwise activated to perform one or more assigned tasks, another communication attempt will be made to provide the report to the FLNX or full function device. The reporting flag and the repeated communications can remain active at least until an appropriate acknowledgment is received from the FLNX or full function device.
[0041] At block 434, the configured and bound automation component 200 begins and/or continues operation within the network to which it has been bound. For example, if the automation component 200 is a wireless room temperature sensor (WRTS), then the automation component 200 can begin monitoring and providing temperature readings for an area, region or portion of the structure.
[0042] In an alternate embodiment, the broadcast message communicated at the block 412 can include the effective user identification (EUID) or media access control (MAC) address of the FLNX or full function device. The effective user identification (EUID) or media access control (MAC) address may, in turn, be utilized by the FLNX
or full function device as described above to establish a binding relationship with the automation component 200.
[0043] In yet another alternate embodiment, the broadcast message communicated at the block 412 can be initiated in response to, for example, a push button or other command disposed or provided on both the automation component 200 and the FLNX or full function device. For example, by depressing a binding push button on the automation component 200 and a binding push button on the FLNX or full function device, both devices can be configured to broadcast their media access control (MAC) addresses and/or their floor level network (FLN) address. Each device, upon receipt of the broadcast information, can, in turn, establish a binding relationship based on the received information.
[0044] In yet another embodiment, the automation component 200 may include a switch, toggle or other device that may be utilized to manually provide the media access control (MAC) addresses and/or their floor level network (FLN) address of the FLNX or full function device to which communications is desired. In this way, a user may manually enter or provide the communication information necessary to bind the automation component 200 to the FLNX or full function device. The automation component 200 may, for example, upon power-up broadcast a binding request directly to the FLNX or full function device utilizing the provided address information.
[0045] In yet another embodiment, the automation component 200 may broad cast a discovery message to all floor level device transceivers (FLNX) within a given reception area. Each FLNX or full function device within the reception area can, in turn, respond with a message that includes a media access control (MAC) addresses and/or their floor level network (FLN) address. The automation component 200 may receive each of the response messages and select the FLNX or full function device that provided the message with the greatest signal strength. Upon selection of a given FLNX or full function device, a visual or audio indication may be provided to allow a user to initiate a push button or other binding operation between the two devices.
[0046] It should be understood that various changes and modifications to the presently preferred embodiments described herein will be apparent to those skilled in the art. For example, the elements of these configurations could be arranged and interchanged in any known manner depending upon the system requirements, performance requirements, and other desired capabilities. Well understood changes and modifications can be made based on the teachings and disclosure provided by the present invention and without diminishing from the intended advantages disclosed herein. It is therefore intended that such changes and modifications be covered by the appended claims.

Claims (15)

CLAIMS:
1. A method for binding an automation component within a building automation system, wherein the building automation system comprises a first network connected to a second network via a modular equipment controller, wherein automation components are coupled to the first and second networks and wherein two or more of the automation components form a subnet;
the method comprising:
a) initiating a binding sequence through a first automation component by means of a portable device that functions within the building automation system;
b) communicating a binding request from the first automation component via a wireless communication link to a further automation component, wherein the binding request includes a first device identifier, the first device identifier comprising at least one of a logical identifier, an internet protocol address, a media access control address, and a local network address;
c) receiving a binding response through the first automation component from the further automation component via the wireless communication link; and d) establishing a binding relationship based on the received binding response.
2. The method according to claim 1, wherein communicating the binding request comprises broadcasting the binding request.
3. The method according to claim 1 or 2, wherein a temporary binding relationship based on a received first binding response is established, wherein the temporary binding relationship is associated with a time period, after which the temporary binding relationship is no longer valid.
4. The method according to claim 3, wherein in a case there exists multiple temporary binding relationships an error is communicated to the portable device and displayed.
5. The method according to any one of claims 1 to 4, the method further comprising:
communicating a personal area network binding request with a second device identifier; and establishing a personal area network binding relationship based on a received response to the personal area network binding request.
6. An automation component for use in a building automation system, the automation component comprising:
a wireless communication component;
a processor that is in communication with the wireless communication component, the processor being configured to initiate a binding sequence by means of a portable device that is connectable to the automation component, communicate a binding request via the wireless communication component to a further automation component, wherein the binding request includes a device identifier, the device identifier comprising at least one of a logical identifier, an internet protocol address, a media access control address, and a local network address, receive a binding response from the further automation component via the wireless communication component, and establish a binding relationship based on the received binding response to the binding request; and a memory that is in communication with the processor.
7. The automation component according to claim 6, wherein the processor is further configured to broadcast the binding request.
8. The automation component according to claim 6 or 7, wherein the processor is further configured to establish a temporary binding relationship based on a received first binding response, wherein the temporary binding relationship is associated with a time period, after which the temporary binding relationship is no longer valid.
9. The automation component according to claim 8, wherein, in a case there exists multiple temporary binding relationships, the processor is further configured to communicate an error to the portable device and to display the error.
10. The automation component according to any one of claims 6 to 9, wherein the processor is further configured to communicate a personal area network binding request with a second device identifier; and establish a personal area network binding relationship based on a received response to the personal area network binding request.
11. A processor-readable storage medium having stored thereon processor-executable instructions that, when executed by a processor, cause an automation component comprising the processor to initiate a binding sequence by means of a portable device that is connectable to the automation component, communicate a binding request via a wireless communication component to a further automation component, wherein the binding request includes a device identifier, the device identifier comprising at least one of a logical identifier, an internet protocol address, a media access control address, and a local network address, receive a binding response from the further automation component via the wireless communication component, and establish a binding relationship based on the received binding response to the binding request.
12. The medium according to claim 11, having further instructions stored thereon that, when executed by the processor, cause the automation component comprising the processor to broadcast the binding request.
13. The medium according to claim 11 or 12, having further instructions stored thereon that, when executed by the processor, cause the automation component comprising the processor to establish a temporary binding relationship based on a received first binding response, wherein the temporary binding relationship is associated with a time period, after which the temporary binding relationship is no longer valid.
14. The medium according to claim 13, having further instructions stored thereon that, when executed by the processor, cause the automation component comprising the processor, in a case there exists multiple temporary binding relationships, to communicate an error to the portable device and to display the error.
15. The medium according to any one of claims 11 to 14, having further instructions stored thereon that, when executed by the processor, cause the automation component comprising the processor to communicate a personal area network binding request with a second device identifier; and establish a personal area network binding relationship based on a received response to the personal area network binding request.
CA2661915A 2006-08-29 2007-08-29 Method and device for binding an automation component within a building automation system Active CA2661915C (en)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US82379406P 2006-08-29 2006-08-29
US60/823,794 2006-08-29
US11/846,137 US20080057872A1 (en) 2006-08-29 2007-08-28 Method and device for binding in a building automation system
US11/846,137 2007-08-28
PCT/US2007/077103 WO2008027961A2 (en) 2006-08-29 2007-08-29 Method and device for binding in a building automation system

Publications (2)

Publication Number Publication Date
CA2661915A1 CA2661915A1 (en) 2008-03-06
CA2661915C true CA2661915C (en) 2015-07-07

Family

ID=39136831

Family Applications (1)

Application Number Title Priority Date Filing Date
CA2661915A Active CA2661915C (en) 2006-08-29 2007-08-29 Method and device for binding an automation component within a building automation system

Country Status (4)

Country Link
US (1) US20080057872A1 (en)
CA (1) CA2661915C (en)
DE (1) DE112007001795B4 (en)
WO (1) WO2008027961A2 (en)

Families Citing this family (61)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9030315B2 (en) * 2006-08-29 2015-05-12 Siemens Industry, Inc. Binding methods and devices in a building automation system
US8224888B2 (en) * 2006-11-14 2012-07-17 Honeywell International Inc. Public variable interface system
EP2215872B1 (en) * 2007-11-29 2012-08-29 Tridinetworks Design and control systems, commissioning tools, configuration adapters and method for wireless and wired networks design, installation and automatic formation
US8713697B2 (en) 2008-07-09 2014-04-29 Lennox Manufacturing, Inc. Apparatus and method for storing event information for an HVAC system
US8229575B2 (en) * 2008-09-19 2012-07-24 Rockwell Automation Technologies, Inc. Automatically adjustable industrial control configuration
US8493946B2 (en) * 2008-10-01 2013-07-23 Digi International Inc. Identifying a desired mesh network in a multiple network environment
US8527096B2 (en) 2008-10-24 2013-09-03 Lennox Industries Inc. Programmable controller and a user interface for same
US8255086B2 (en) 2008-10-27 2012-08-28 Lennox Industries Inc. System recovery in a 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
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
US8437877B2 (en) 2008-10-27 2013-05-07 Lennox Industries Inc. System recovery in a heating, ventilation and air conditioning network
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
US8295981B2 (en) 2008-10-27 2012-10-23 Lennox Industries Inc. Device commissioning in a heating, ventilation and air conditioning network
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
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
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
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
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
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
US8694164B2 (en) * 2008-10-27 2014-04-08 Lennox Industries, Inc. Interactive user guidance interface for a heating, ventilation and air conditioning system
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
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
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
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
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
US8600559B2 (en) 2008-10-27 2013-12-03 Lennox Industries Inc. Method of controlling equipment 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
US8798796B2 (en) 2008-10-27 2014-08-05 Lennox Industries Inc. General control techniques 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
US8600558B2 (en) 2008-10-27 2013-12-03 Lennox Industries Inc. System recovery in a 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
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
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
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
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
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
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
USD648641S1 (en) 2009-10-21 2011-11-15 Lennox Industries Inc. Thin cover plate for an electronic system controller
USD648642S1 (en) 2009-10-21 2011-11-15 Lennox Industries Inc. Thin cover plate for an electronic system controller
US20110107422A1 (en) * 2009-10-30 2011-05-05 Patrick Choy Ming Wong Email worm detection methods and devices
WO2011092612A1 (en) * 2010-01-29 2011-08-04 Koninklijke Philips Electronics N.V. A method for operating a radio node in a sensor network
US8982754B2 (en) * 2010-01-29 2015-03-17 Digi International Inc. I/O driven node commissioning in a sleeping mesh network
US8260444B2 (en) 2010-02-17 2012-09-04 Lennox Industries Inc. Auxiliary controller of a HVAC system
US20150277407A1 (en) * 2014-03-27 2015-10-01 Trane International Inc. Location detection of control equipment in a building
US10168065B2 (en) * 2015-01-19 2019-01-01 Lennox Industries Inc. Diagnosing and troubleshooting a heating, ventilation, and air conditioning system
JP7210936B2 (en) * 2018-08-28 2023-01-24 株式会社ノーリツ Hot water system and program

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030020595A1 (en) * 2001-07-12 2003-01-30 Philips Electronics North America Corp. System and method for configuration of wireless networks using position information
DE60312561T2 (en) * 2002-12-19 2008-04-30 Koninklijke Philips Electronics N.V. CONFIGURATION PROCESS FOR A WIRELESSLY CONTROLLED LIGHTING SYSTEM
US7369060B2 (en) * 2004-12-14 2008-05-06 Lutron Electronics Co., Inc. Distributed intelligence ballast system and extended lighting control protocol

Also Published As

Publication number Publication date
WO2008027961A3 (en) 2008-06-19
DE112007001795B4 (en) 2013-01-31
US20080057872A1 (en) 2008-03-06
DE112007001795T5 (en) 2009-10-29
WO2008027961A2 (en) 2008-03-06
CA2661915A1 (en) 2008-03-06

Similar Documents

Publication Publication Date Title
CA2661915C (en) Method and device for binding an automation component within a building automation system
CA2662014C (en) Binding methods and devices in a building automation system
US9967110B2 (en) Method and apparatus for registering remote network devices with a control device
CN101971568B (en) Method and device for communicating change-of-value information in building automation system
US8224282B2 (en) Method and device to manage power of wireless multi-sensor devices
CA2662002C (en) Reprogramming nodes in a wireless automation system
JP6478983B2 (en) Method for configuring a node, and the configured node
RU2581562C2 (en) Method of associating or re-associating devices in control network
EP2193452B1 (en) Method and system for wireless communication with sleeping devices in a wirless sensor control network
WO2005048042A2 (en) Radio frequency lighting control system programming device and method
CN103576664A (en) Automation component for transmitting value change information in intelligent household system and method
CA2836941C (en) Binding methods and devices in a building automation system
CN101512966A (en) Method and device for binding in a building automation system
EP2640137B1 (en) Method for attaching control devices to control system in mesh network

Legal Events

Date Code Title Description
EEER Examination request