Method and system for retrieving building automation system controller information using near field communication

Abstract

The subject matter of the present invention is "A method and system for retrieving building automation system controller information using near field communication". A process for retrieving configuration information for a controller of a building automation system (BAS) includes verifying login information on a mobile computing device to ensure that the mobile computing device has permission to access a wiring diagram. The mobile computing device then receives identity information associated with the controller from the memory of an NFC tag associated with the controller via an NFC read operation, and uses the identity information to retrieve the wiring diagram from a storage medium. The mobile computing device also displays the retrieved wiring diagram associated with the controller.

Description

Technical Field

[0001] The present disclosure generally relates to building automation systems (BAS), and more particularly to using near field communication (NFC) technology to retrieve configuration information for BAS controllers, such as wiring diagrams and cable labels. Background Art

[0002] Building automation systems (BAS) are used to manage and automate the control of various environmental, physical, and electrical building subsystems. In particular, BAS systems are commonly used for the coordination and control of heating, ventilation, and air conditioning (HVAC) as well as climate control systems, but are also often used for security systems, lighting systems, and other connected building subsystems.

[0003] BAS systems typically utilize a series of interconnected controller devices that coordinate the control and automation of such subsystems. Large-scale BAS systems can include hundreds or even thousands of controllers.

[0004] However, the configuration and commissioning of BAS controllers typically require a team of service engineers to physically connect to each BAS controller via a laptop or another computing device (e.g., using wired Ethernet or other wired connections) to initialize each BAS controller with wireless communication parameters and many other configuration parameters that define the communication and other operating characteristics of the controller. Configuration and commissioning also require connecting many wires / cables to each BAS controller and labeling these wires / cables. Thus, traditional techniques for configuring and commissioning BAS controllers for operation typically require a significant expenditure of service engineering and / or technician resources, thereby increasing the time and cost associated with the installation and maintenance of BAS systems. Summary of the Invention

[0005] In one example, a process for retrieving configuration information for a controller of a building automation system (BAS) includes verifying login information on a mobile computing device to ensure that the mobile computing device has permission to access a wiring diagram. The mobile computing device then receives, via a near field communication (NFC) read operation, identity information associated with the controller from a memory of an NFC tag associated with the controller, and uses the identity information to retrieve the wiring diagram from a storage medium. The mobile computing device also displays the retrieved wiring diagram associated with the controller.

[0006] In another example, a system for retrieving configuration information for a controller includes: a near field communication (NFC) tag including an NFC memory storing identity information corresponding to the controller; a storage medium configured to store electronic (i.e., digital) data; and a mobile computing device including an NFC transceiver and configured to receive the identity information from the NFC tag and retrieve a wiring diagram associated with the controller from the storage medium. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 is a block diagram showing an example system including a building automation system (BAS) controller having a near field communication (NFC) tag and a mobile computing device communicating with the NFC tag.

[0008] Figure 2 shows Figure 1 further details of the computing device in block diagram.

[0009] Figure 3 is a flowchart showing an example method for retrieving configuration information. DETAILED DESCRIPTION

[0010] Methods and systems for retrieving configuration information for a building automation system (BAS) controller via a mobile computing device utilized by a service engineer or other technician are disclosed herein, the configuration information such as wiring diagrams, cable labels, manual instructions, and / or building floor plans. The configuration information can be stored in various locations for subsequent retrieval (and modification) by the mobile computing device, such as in the memory of a near field communication (NFC) tag associated with the BAS controller, in the memory of the mobile computing device, and / or in a storage medium remote from the mobile computing device and the NFC tag.

[0011] The methods and systems described herein provide secure and reliable NFC communication between a mobile computing device and a BAS controller, as well as the ability to verify that the mobile computing device has permission to access configuration information based on identity information associated with the BAS controller stored in the memory of the NFC tag. Additionally, the use of passive NFC tag technology enables the identity and configuration information to be determined and stored in the memory of the NFC tag when the BAS controller is in a powered-off state, thereby increasing the flexibility of scheduling commissioning / installation operations associated with the controller. Using configuration information including a wiring diagram for instructions to connect cables to the BAS controller and cable labels for labeling the cables being connected to the BAS controller, only one service engineer / technician is required to perform both the wiring and the labeling, thus reducing the time and corresponding cost associated with the configuration and commissioning of the BAS controller. Additionally, the mobile computing device facilitates the amendment of the wiring diagram and cable labels (as well as other configuration information, such as manual instructions and floor plans). The mobile computing device facilitates storing the amended wiring diagram and / or cable labels on any storage medium, where the amended wiring diagram and / or cable labels can be retrieved by being identified with the previous identity information stored in the memory of the NFC tag or new, updated identity information.

[0012] Figure 1 is a block diagram showing an example system 10 including a building automation system (BAS) 11, a BAS controller 12, a mobile computing device 14, a storage medium 16, and a printer 18. As Figure 1 shown, the BAS controller 12 includes an NFC tag 20 associated therewith. For example, the NFC tag 20 can be integrated with the computer-readable memory of the BAS controller 12, attached to the BAS controller 12 (e.g., adhesively or otherwise attached to the interior or exterior of the housing of the BAS controller 12), or otherwise associated with the BAS controller 12. As Figure 1 further shown, the NFC tag 20 includes an NFC memory 22 that stores identity information 24, a wiring diagram 26, cable labels 28, manual instructions 29, and / or a floor plan 30.

[0013] The BAS 11 is used to manage and automate the control of various environmental, physical, and electrical building systems of the building in which the BAS 11 is located. In particular, the BAS 11 can be used for the coordination and control of heating, ventilation, and air conditioning (HVAC) as well as climate control systems. Additionally, the BAS 11 can be used for security systems, lighting systems, and other connected building subsystems. The BAS 11 utilizes a plurality of interconnected BAS controllers 12 to coordinate the control and automation of the various building subsystems. The number of BAS controllers 12 in the BAS 11 can be as few as one or two, or as many as thousands.

[0014] The BAS controller 12 can be one of a plurality of BAS controllers, each of the plurality of BAS controllers being electrically coupled and / or communicatively coupled to one or more BAS 11 subsystems and / or components (not shown) (such as heating, ventilation, and air conditioning (HVAC) components, security system components, lighting system components, or other building subsystems and / or components). Thus, although shown and described with respect to a single BAS controller (i.e., BAS controller 12 in this example), it should be understood that the techniques described herein can be applied to systems including multiple BAS controllers (such as dozens, hundreds, thousands, or other numbers of BAS controllers). Figure 1 The example described herein is for illustrative purposes only and should not be construed as limiting the scope of the invention. The techniques described herein can be applied to systems including multiple BAS controllers (such as dozens, hundreds, thousands, or other numbers of BAS controllers).

[0015] The NFC tag 20 associated with the BAS controller 12 includes a radio frequency (RF) antenna and other circuitry (not shown) for communicating with an NFC transceiver within range via NFC read and write operations, the range being, for example, 20 centimeters (7.87 inches) or less. The NFC tag 20 can be a passive NFC tag that draws power by magnetic induction from an active device within range, such as via an NFC signal generated by the NFC transceiver of the mobile computing device 14. Thus, as described further below, even when the BAS controller 12 is in a power-off state, the NFC tag 20 can enable data transfer between the NFC memory 22 and the NFC transceiver of the mobile computing device 14.

[0016] As Figure 1 shown, the mobile computing device 14 is remote from (i.e., physically distant from) the BAS controller 12 and includes an NFC transceiver that wirelessly communicates with the BAS controller 12 to retrieve and store configuration information corresponding to the BAS controller 12 within the NFC memory 22 (such as a wiring diagram 26, cable labels 28, manual instructions 29, and a floor plan 30). Examples of the mobile computing device 14 can include, but are not limited to, portable or mobile devices such as laptop computers, tablet computers, smart phones, personal digital assistants (PDAs), or other mobile computing devices including at least one NFC transceiver capable of communicating with the NFC tag 20 via NFC read and write operations. Although described as a mobile device, the mobile computing device 14 can be a non-mobile device (such as a desktop computer) capable of communicating with the NFC tag 20 via NFC read and write operations.

[0017] In operation, identity information 24 corresponding to the BAS controller 12 is stored in the NFC memory 22 during, for example, manufacturing or other pre-commissioning activities. For example, the identity information 24 can be stored in the NFC memory 22 by the BAS controller 12, such as via the NFC transceiver of the BAS controller 12 or via the NFC transceiver of a remote device, such as a smart phone, laptop computer, tablet computer, or other NFC programmer in a manufacturing or other production facility. The identity information 24 can include, for example, any one or more of the following: the media access control (MAC) address of the BAS controller 12, the MAC address of the wireless transceiver of the BAS controller 12, the model number of the BAS controller 12, the Internet protocol (IP) address, the building automation control network (BACnet) MAC address, the hardware address, the vendor identification number, the device identification number, the serial number of the BAS controller 12 (e.g., a unique serial number), the serial number of the NFC tag 20, the device / BAS controller 12 location, the firmware or other software version number associated with the BAS controller 12, or other identity information associated with the BAS controller 12. In some examples (such as Figure 1 the example of Figure 1 ), the configuration information can also be stored in the NFC memory 22 during manufacturing or other pre-commissioning activities, such as via a remote computing device or the NFC transceiver of the BAS controller 12. The identity information 24 provides some security to the system 10 because when the configuration information is stored on the mobile computing device 14 and / or the storage medium 16, the configuration information may not be accessed without first obtaining the identity information 24 from the NFC tag 20. The identity information 24 can be used as a map to give the mobile computing device 14 the location where the configuration information is stored.

[0018] In a typical installation, the BAS controller 12 is delivered to and installed (e.g., physically installed) at the installation location before the electrical and other building subsystems are completed. Thus, the BAS controller 12 including the NFC tag 20 can be transported to and installed at the delivery location while the BAS controller 12 is in a power-off state (i.e., not powered). The techniques of the present disclosure enable the configuration information (e.g., the wiring diagram 26, the cable label 28, the manual instructions 29, and the floor plan 30) to be determined and stored in the NFC memory 22 while the BAS controller 12 is in a power-off state, rather than requiring the determination of the configuration information and other associated commissioning activities to wait until power is available and delivered to the BAS controller 12.

[0019] For example, as further described below, when the BAS controller 12 is in a power-off state (e.g., installed at the final destination and in a power-off state), a service engineer or other technician can use the mobile computing device 14 to retrieve configuration information and store it in the NFC memory 22. For example, when within the range of NFC communication (e.g., when placed within the range of NFC communication by a service engineer), the mobile computing device 14 can retrieve the identity information 24 via an NFC read operation initiated by the NFC transceiver of the mobile computing device 14. The identity information 24 is then used to access / retrieve configuration information (e.g., wiring diagram 26, cable label 28, manual instructions 29, and / or floor plan 30). The configuration information can be stored in various locations, including stored in the NFC memory 22, stored in the memory of the mobile computing device 14 (as explained with respect to Figure 2 and / or stored in a storage medium 16 remote from the NFC tag 20 and the mobile computing device 14. In an example where the NFC memory 22 stores the configuration information, the mobile computing device 14 can retrieve the configuration information via an NFC read operation for display and / or modification by a service engineer or other technician. In an example where the configuration information is stored in the memory of the mobile computing device 14 and / or a separate storage medium 16, the mobile computing device 14 uses the identity information 24 to access and retrieve the configuration information for display and / or modification / correction.

[0020] The configuration information described herein includes a wiring diagram 26, cable labels 28, manual instructions 29, and / or a floor plan 30. The wiring diagram 26 is a schematic (e.g., a visual representation) showing the physical connections and physical layout of the wires / cables to be connected to the BAS controller 12. Service engineers and / or technicians use the wiring diagram 26 as a blueprint for instructions on how to connect the wires / cables to the ports of the BAS controller 12. The wiring diagram 26 shows how the wires / cables are interconnected and may show where fixed equipment and components can be connected to the BAS controller 12. The cable labels 28 are markings attached to the wires / cables connected to the BAS controller 12. To achieve certification of the BAS 11, it is necessary to label the wires / cables with the cable labels 28 so that service engineers, technicians, and others can determine what the wire / cable is and whether it is correctly connected to the BAS controller 12. The manual instructions 29 may be instructions for guiding and / or troubleshooting the connection of the wires / cables to the BAS controller 12 by service engineers and / or technicians. The manual instructions 29 may include voice-based instructions that can respond to text-based and / or audible questions using text-based instructions and / or audio instructions. The manual instructions 29 may have other capabilities to assist service engineers and / or technicians in connecting and labeling the wires / cables. The floor plan 30 may be a blueprint of the BAS 11 or the entire building (or group of buildings) in which the BAS 11 is located. It should be noted that when the wiring diagram 26, cable labels 28, manual instructions 29, and floor plan 30 are discussed as being stored in the NFC memory 22, mobile computing device 14, and / or storage medium 16, they are stored as electronic (e.g., digital) files and not as hard copy printouts of the corresponding files. For example, the cable labels 28 are stored as a digital file that includes a list of labels formatted in such a way that physical cable labels can be easily attached to the cables when printed by the printer 18. Although the configuration information is described herein as the wiring diagram 26, cable labels 28, manual instructions 29, and / or floor plan 30, the configuration information may include other information related to the BAS controller 12.

[0021] If configuration information (e.g., wiring diagram 26, cable label 28, manual instruction 29, and / or floor plan 30) is stored in the NFC memory 22, the mobile computing device 14 may not need the identity information 24 for access and retrieval of the configuration information. Instead, login information (e.g., login username and password) entered into the mobile computing device 14 by a service engineer and / or technician can provide the necessary security clearance to allow access to the configuration information without the need for the identity information 24, which can be used as a reference number to ensure that the mobile computing device 14 has permission to access the configuration information and to help locate the configuration information from a location external to the NFC memory 22. Because the configuration information does not need to be located on the mobile computing device 14 or on a separate storage medium when it is stored in the NFC memory 22, the identity information 24 may not be required, and the mobile computing device 14 can retrieve the configuration information without further authorization.

[0022] After retrieving the configuration information, the mobile computing device 14 can display the configuration information on a display, such as the screen of a laptop computer, a tablet computer, a smart phone, etc. The mobile computing device 14 can facilitate a service engineer and / or technician to revise the configuration information and store the revised configuration information identified by the previous identity information 24 (e.g., overwrite the previous identity information) or store it under new identity information 24 that allows access / retrieval of the configuration information. Using NFC read and write operations, the mobile computing device 14 can then transmit and store the new identity information 24 associated with the revised configuration information in the NFC memory 22. If the configuration information is stored in the NFC memory 22, the mobile computing device 14 can transmit the configuration information and store it on the NFC tag 20. Such an operation facilitates subsequent retrieval of the revised configuration information.

[0023] As described above, the identity information 24 can be used to access / retrieve configuration information from the storage medium 16, which is remote and separate from the NFC tag 20 and the mobile computing device 14. For example, the storage medium 16 can be a cloud-based data storage facility, such as a server remote from the BAS 11. When the configuration information is stored in the storage medium 16, the mobile computing device 14 communicates with the storage medium 16 and can retrieve the configuration information via wired or wireless communication.

[0024] Printer 18 can be a mobile or stationary printer that communicates with or is incorporated into mobile computing device 14. Printer 18 is configured to print out part or all of any one of wiring diagram 26, cable label 28, manual instruction 29, and floor plan 30. Mobile computing device 14 can be configured such that after retrieving configuration information, the configuration information is automatically transmitted to printer 18, and printer 18 then automatically prints the configuration information. For example, mobile computing device 14 can retrieve cable label 28 (as a digital file), transmit the digital file of cable label 28 to printer 18, and then printer 18 can print a physical version of cable label 28. The physical cable label 28 is then attached to the corresponding cable / wire of BAS controller 12. Printer 18 can be configured to print the configuration information in any format, such as printing cable label 28 as a series of adhesive tapes / markers.

[0025] Figure 2 is a block diagram showing Figure 1 further details of computing device 14, which can be a laptop computer, tablet computer, smart phone, or other mobile computing device capable of communicating via NFC read and write operations and with NFC memory 22 of NFC tag 20 associated with BAS controller 12 ( Figure 1 ). As shown Figure 2 in, computing device 14 can include one or more processors 32, user interface 34, NFC transceiver 36, wireless transceiver 38, and computer-readable memory 40. Computer-readable memory 40 can store configuration information, which can include wiring diagram 26, cable label 28, manual instruction 29, and / or floor plan 30.

[0026] Processor 32 can be configured to implement functionality and / or process instructions for execution within computing device 14. For example, processor 32 is capable of processing instructions stored in computer-readable memory 40, such as computer-readable instructions associated with wiring diagram 26, cable label 28, manual instruction 29, and floor plan 30 (collectively referred to as configuration information) herein. Examples of processor 32 can include any one or more of a microprocessor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other equivalent discrete or integrated logic circuits.

[0027] The mobile computing device 14 utilizes the user interface 34 to receive input from and output information to a user, such as a service engineer, technician, and / or other users. The user interface 34 may include physical and / or graphical control elements that enable user input to interact with the computing device 14. For example, the user interface 34 may take the form of a graphical user interface (GUI) that presents graphical control elements at a display device of the user interface 34, for example. In some examples, the computing device 14 may present the GUI at a touch-sensitive and / or presence-sensitive display screen to receive user input in the form of gestures such as touch gestures, scroll gestures, zoom gestures, or other gesture inputs. In some examples, the user interface 34 may include a physical keyboard, mouse, physical buttons, keys, knobs, or other physical control elements configured to receive user input to interact with the mobile computing device 14. The user interface 34 is configured to display and facilitate corrections to the wiring diagram 26, cable labels 28, manual instructions 29, and floor plan 30. In the case of the manual instructions 29, the internal interface 34 may be configured to play audio instructions and facilitate audio, visual, and other interactions with the manual instructions 29.

[0028] The mobile computing device 14 utilizes the NFC transceiver 36 to communicate with one or more remote NFC transceivers and / or NFC tags, such as the NFC tag 20 ( Figure 1 ). As described further below, the mobile computing device 14 may use the NFC transceiver 36 to retrieve information from the NFC memory 22 ( Figure 1 ) via NFC read and write operations and store information in the NFC memory 22 ( Figure 1 ).

[0029] The mobile computing device 14 may also utilize the wireless transceiver 38 to communicate with the storage medium 16 and / or the printer 18. The wireless transceiver 38 may be used to retrieve configuration information from the storage medium 16 (possibly by using the identity information 24) and / or transmit the configuration information to the printer 18 for printing. The wireless transceiver 38 may also be used to send and receive information regarding the authentication of login information to ensure that the mobile computing device 14 has permission to access the configuration information. Although described herein as having wireless capabilities, the wireless transceiver 38 may communicate with the storage medium 16 and the printer 18 via other communications such as a wired connection. For example, the printer 18 may be incorporated into the mobile computing device 14 such that the communication with the printer 18 is wired. Additionally, the wireless transceiver 38 may be incorporated into the NFC transceiver 36 such that the two are one element.

[0030] The computer-readable memory 40 can be configured to store information within the mobile computing device 14 during operation. In some examples, the computer-readable memory 40 can include non-transitory memory. The term "non-transitory" can indicate that the storage medium is not embodied in a carrier wave or propagated signal. In certain examples, the non-transitory memory can store data that can change over time (e.g., in RAM or a cache).

[0031] In some examples, the computer-readable memory 40 can include volatile memory elements that do not retain the stored content when power to the mobile computing device 14 is removed. Examples of volatile memory elements can include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), and other forms of volatile memory. In certain examples, the computer-readable memory 40 can include non-volatile memory elements configured for long-term storage of information. Examples of such non-volatile memory elements can include, for example, magnetic hard disks, optical disks, flash memory, or forms of electrically programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM).

[0032] As Figure 2 shown, the computer-readable memory 40 can store one or more electronic (e.g., digital) files including a wiring diagram 26, a cable label 28, manual instructions 29, and / or a floor plan 30 (collectively referred to as configuration information). The configuration information can take the form of computer-readable instructions that, when executed by the processor 32, cause the computing device 14 to implement functionality for, e.g., the display of the configuration information. Generally, the computer-readable memory 40 can store computer-readable instructions that, when executed by the processor 40, cause the computing device 14 to operate in accordance with the techniques described herein.

[0033] For example, the mobile computing device 14 may perform steps that cause the NFC transceiver 36 to retrieve the identity information 24 and configuration information from the NFC memory 18 via an NFC read operation. The computing device 14 may also execute instructions to verify the login information entered by the user to ensure that the mobile computing device 14 has permission to access the configuration information. As described above, the computer-readable memory 40 may store the configuration information such that the configuration information is retrieved from the computer-readable memory 40 within the mobile computing device 14 and does not require retrieval of the configuration information from the NFC tag 20 or the storage medium 16. The configuration information may be stored in the computer-readable memory 40 under the identity information 24 such that the identity information 24 indicates a location and permits access to the configuration information. The mobile computing device 14 may allow the user to modify the configuration information (i.e., the wiring diagram 26, the cable label 28, the manual instructions 29, and the floor plan 30). The modified configuration information may then be stored in the computer-readable memory 40 under the new identity information 24 or the old identity information 24 (i.e., overwriting the previous configuration information). The new identity information 24 is then transmitted to the NFC tag 20 via an NFC read and write operation such that the new identity information 24 is used for subsequent retrieval of the modified configuration information.

[0034] Figure 3 is a flowchart illustrating an example method for retrieving and modifying configuration information. The method 42 may include six sets of steps, each of which may include multiple sub-steps. The method 42 includes a cable label generation step 44, a login information verification 46, a wiring diagram step 48, a manual instructions step 50, a cable label retrieval step 52, and a floor plan step 54. The method 42 disclosed herein may include additional steps of those steps described below, or may include only one step or subset of the steps set forth below. Thus, the method 42 is not exclusive and may be added to, subtracted from, or otherwise modified depending on the configuration information intended to be retrieved, modified, printed, etc.

[0035] Method 42 may include a step 44 of generating a cable label, which includes automatically formulating a cable label 44A and storing the cable label 44B. The entirety of the BAS can be designed and displayed in a controller program, such as an AutoCAD file or other general design program. The program / design may include information for creating a wiring diagram and cable labels, so a digital file of the cable label can be formulated from the controller program. The information to be used for creating the cable label can be marked or otherwise identified / annotated such that when instructed or when the information including the cable label is complete, the controller program can automatically formulate the cable label 44A. After formulating the cable label 44A, the cable label is stored 44B. The cable label can be stored in various electronic (e.g., digital) storage media, including being stored in the memory of an NFC tag, in the memory of a mobile computing device, or in a storage medium remote from the NFC tag and the mobile computing device (such as cloud storage). The controller program can automatically upload / transfer the cable label to the storage medium via wired and / or wireless communication, can be transferred via NFC read and write operations, and / or can store the cable label by other means for subsequent retrieval by the mobile computing device.

[0036] Method 42 may also include a step 46 of verifying login information, which ensures that a user of the mobile computing device (such as a service engineer or technician) has appropriate permissions to access configuration information and prevents unauthorized users from viewing and / or amending the configuration information. Verifying the login information 46 may include verifying a username and password entered into the mobile computing device, using a virtual private network (VPN) or another security protocol on the mobile computing device.

[0037] Method 42 may include a wiring diagram step 48, which may include a plurality of sub-steps. First, the mobile computing device receives identity information 48A from the memory of the NFC tag via an NFC read operation. As described above, the identity information can provide location details of the configuration information, which can be stored on the NFC tag, on the mobile computing device, and / or in a storage medium. If the configuration information is stored in the memory of the NFC tag, step 48A may not be necessary because location details will not be needed to locate the configuration information: the configuration information is easily found on the NFC tag.

[0038] Next, the mobile computing device retrieves a wiring diagram 48B from a storage medium, which can be the memory of the NFC tag, the memory of the mobile computing device, and / or a storage medium remote from the NFC tag and the mobile computing device. The retrieval of the wiring diagram 48B can be based on the identity information such that the identity information provides the mobile computing device with location information related to the location of the wiring diagram.

[0039] Then, the wiring diagram 48C is displayed for viewing by a user of the mobile computing device, such as a service engineer or technician. The display 48C of the wiring diagram can be on the screen of the mobile computing device or can be in other ways. For example, the mobile computing device can instruct a printer to print a hard copy of the wiring diagram, and then the hard copy of the wiring diagram can be viewed.

[0040] Based on the connection mode and / or identity of the cable / wire connected to the BAS controller by the user / service engineer / technician via the mobile computing device, the wiring diagram 48D can be corrected. During the wiring of the BAS controller, the service engineer or technician may deviate from the wiring diagram. In such a case, the wiring diagram 48D can be corrected to reflect the actual wiring of the BAS controller (e.g., the connection mode and / or the identity of the cable / wire).

[0041] After correcting the wiring diagram 48D, the corrected wiring diagram 48E is stored. The corrected wiring diagram can be stored in the memory of the NFC tag, in the memory of the mobile computing device, and / or in a separate storage medium. The storage 48E of the corrected wiring diagram can include overwriting the previous wiring diagram or storing a new file with the corrected wiring diagram.

[0042] If the corrected wiring diagram is stored in the mobile computing device and / or a separate storage medium, it may be necessary to perform the step of storing new identity information 48F in the memory of the NFC tag for later retrieval operations. The new identity information can provide the location where the corrected wiring diagram is stored. If the corrected wiring diagram is stored in the location of the previous identity information (and thus the previous wiring diagram has been overwritten), step 48F may not be necessary because the identity information will already have the location details of the wiring diagram. Additionally, if the corrected wiring diagram is stored in the memory of the NFC tag, step 48F may not be necessary because the location of the corrected wiring diagram can be easily found and identity information is not required.

[0043] The method 42 can include a manual instruction step 50, which can include retrieving a manual instruction 50A and displaying a manual instruction 50B. Retrieving the manual instruction 50A can be performed by the mobile computing device, and the manual instruction can be stored in any of the above storage media. Retrieving the manual instruction 50A can be similar to the process of retrieving the wiring diagram 48B.

[0044] Next, display the manual instruction 50B. The display of the manual instruction can include visually displaying text, diagrams, or other instructions. Additionally, the display of the manual instruction can include audibly playing the instruction via a speaker associated with or communicating with the mobile computing device. Other embodiments can include voice-based instructions that can respond to text-based and / or audible questions by displaying visual (e.g., text-based) instructions and / or audio instructions. If the configuration information does not include a manual instruction and / or if the service engineer and / or technician does not require a manual instruction to install the BAS controller, method 42 may not include sub-steps 50A and 50B. Additionally, manual instruction step 50 can include additional steps similar to steps 48D-48F regarding the wiring diagram (e.g., correcting the manual instruction, storing the corrected manual instruction, and storing new identity information).

[0045] The step 52 of retrieving the cable label is similar to the wiring diagram step 48. If not already performed, perform sub-step 48A (the mobile computing device receives identity information from the memory of the NFC tag via an NFC reading operation). Then, the mobile computing device retrieves the cable label 52A from a storage medium, which can be the memory of the NFC tag, the memory of the mobile computing device, and / or a storage medium remote from the NFC tag and the mobile computing device. The retrieval 52A of the cable label can be based on the identity information such that the identity information provides the mobile computing device with location information regarding the location of the cable label file.

[0046] Next, display the cable label 52B for viewing by a user of the mobile computing device, such as a service engineer or technician. The display 52B of the cable label can be on the screen of the mobile computing device or can be in other ways. Other processes of method 42 can include steps where the cable label 52B is not displayed and instead the cable label is sent to a printer for printing and viewing as a hard copy.

[0047] The cable label can be transmitted by the mobile computing device to the printer 52C via wired or wireless communication. As described above, the printer can be a component separate from the mobile computing device or can be incorporated into the mobile computing device. Step 52C can be automatically performed by the mobile computing device after retrieving the cable label 52A, or the cable label can be transmitted to the printer 52C in response to an instruction from a user of the mobile computing device.

[0048] After the digital file of the cable label is transferred to printer 52C, the printer prints a hard copy 52D of the cable label. The physical hard copy of the cable label can then be attached by the service engineer and / or technician to the corresponding cable / wire of the BAS controller. The cable label 52D can be printed in various configurations / formats, such as printing the cable label as a series of adhesive tapes / markers for easier attachment to the cable / wire.

[0049] Similar to step 48D regarding the wiring diagram, the digital file 52E of the cable label can be corrected according to the cable / wire connected to the BAS controller by the user / service engineer / technician via the mobile computing device. During the wiring and / or marking of the BAS controller, the service engineer or technician may deviate from the wiring diagram (or the marking of the designed cable). In such a case, the cable label 52E can be corrected to reflect the actual wiring and marking of the BAS controller cables. Then, the corrected cable label can be transferred to the printer and printed (thus, repeating steps 52C and 52D if necessary).

[0050] After correcting the cable label 52E, the corrected cable label 52F is stored. The corrected cable label can be stored in the memory of the NFC tag, in the memory of the mobile computing device, and / or on a separate storage medium. The storage 52F of the corrected cable label can include overwriting the previous cable label or storing a new file with the corrected cable label.

[0051] If the corrected cable label is being stored in the mobile computing device and / or on a separate storage medium, the step of storing new identity information 52G in the memory of the NFC tag for subsequent retrieval operations is performed. The new identity information can provide the location where the corrected cable label is stored. If the corrected cable label is stored in the location of the previous identity information (and thus the previous cable label has been overwritten), step 52G is performed because the identity information will already have the location details of the cable label. Additionally, if the corrected cable label is stored in the memory of the NFC tag, step 52G may not be required because the location of the corrected cable label is easily found and identity information is not needed.

[0052] Method 42 can also include a floor plan step 54, which can include retrieving a floor plan 54A and displaying a floor plan 54B. Retrieving the floor plan 54A can be performed by the mobile computing device, and the floor plan can be stored in any of the above storage media. Retrieving the floor plan 54A can be similar to the process of retrieving the wiring diagram 48B. Similar to other files / information of the configuration information, the retrieval 54A of the floor plan can be based on the identity information, such that the identity information tells the mobile computing device where the floor plan is located.

[0053] Next, the floor plan 54B is displayed for viewing by a user of the mobile computing device, such as a service engineer or technician. The display 54B of the floor plan can be on the screen of the mobile computing device or can be in other ways. For example, the mobile computing device can instruct a printer to print a hard copy of the floor plan, and then the hard copy of the floor plan can be viewed. Additionally, the floor plan step 54 can include additional steps similar to steps 48D - 48F regarding the wiring diagram (e.g., modifying the floor plan, storing the modified floor plan, and storing new identity information).

[0054] The system 10 and method 42 described herein provide secure and reliable NFC communication between the mobile computing device 14 and the BAS controller 12, and the ability to verify that the mobile computing device 14 has permission to access configuration information based on the identity information 24 stored in the NFC memory 22 of the NFC tag 20. Additionally, the use of passive NFC tag technology enables the identity and configuration information to be determined and stored in the NFC memory 22 of the NFC tag 20 when the BAS controller 12 is in a power-off state, thereby increasing the flexibility of scheduling the commissioning / installation operations associated with the BAS controller 12. With configuration information including the wiring diagram 26 for instructions on connecting cables to the BAS controller 12 and the cable tags 28 for labeling the cables being connected to the BAS controller 12, only one service engineer / technician is required to perform both the wiring and the tagging, thus reducing the time and corresponding costs associated with the configuration and commissioning / installation of the BAS controller 12. Further, the mobile computing device 14 facilitates the modification of the wiring diagram 26 and the cable tags 28 (as well as other configuration information, such as the manual instructions 29 and the floor plan 30). The mobile computing device 14 facilitates storing the modified wiring diagram 26 and / or cable tags 28 on any storage medium, where the modified wiring diagram 26 and / or cable tags 28 can be retrieved by being identified using the previous identity information 24 or new, updated identity information 24 stored in the NFC memory 22 of the NFC tag 20.

[0055] Discussion of possible embodiments

[0056] The following is a non-exclusive description of possible embodiments of the present invention.

[0057] In one example, a process for retrieving configuration information for a controller of a building automation system (BAS) includes verifying login information on a mobile computing device to ensure that the mobile computing device has permission to access a wiring diagram. The mobile computing device then receives identity information associated with the controller from the memory of an NFC tag associated with the controller via an NFC read operation, and uses the identity information to retrieve the wiring diagram from a storage medium. The mobile computing device also displays the retrieved wiring diagram associated with the controller.

[0058] Additionally and / or alternatively, the method of the preceding paragraph may optionally include any one or more of the following features, configurations, operations, steps, and / or additional components:

[0059] The identity information includes at least one of the following: a media access control (MAC) address, a model number of the controller, an Internet protocol (IP) address, a building automation control network (BACnet) MAC address, a hardware address, a vendor identification number, a device identification number, a serial number of the controller, a serial number of the NFC tag, and a device location.

[0060] The step of retrieving the wiring diagram from the storage medium further includes: retrieving the wiring diagram from a storage medium that is remote from and communicates with the mobile computing device such that the wiring diagram is not stored on the mobile computing device.

[0061] The step of retrieving the wiring diagram from the storage medium further includes: retrieving the wiring diagram from the memory of the mobile computing device such that the wiring diagram is stored on the mobile computing device.

[0062] The step of retrieving the wiring diagram from the storage medium further includes: retrieving the wiring diagram from the memory of the NFC tag such that the wiring diagram is stored on the NFC tag.

[0063] The login information includes a username and a password provided to a user interface of the mobile computing device.

[0064] The method further includes retrieving, by the mobile computing device, manual instructions associated with the controller from the storage medium.

[0065] The method further includes displaying, by the mobile computing device, the retrieved manual instructions associated with the controller.

[0066] The manual instructions include voice-based instructions for guiding and troubleshooting the connection of cables to the controller.

[0067] The method further includes retrieving, by the mobile computing device, cable labels associated with cables configured to connect to the controller using the identity information, wherein retrieving the identity information includes retrieving the identity information from the storage medium.

[0068] The method further includes displaying, by the mobile computing device, the retrieved cable label associated with the controller.

[0069] The method further includes transmitting, by the mobile computing device in response to retrieving the cable label, the cable label to a printer; and printing, by the printer, the cable label.

[0070] The method further includes: modifying the cable label; storing, by the mobile computing device, the modified cable label and new identity information associated with the controller; and storing the new identity information in the memory of the NFC tag for subsequent retrieval operations by the controller.

[0071] The method further includes: automatically formulating, from a controller program, the cable label; and storing the cable label in a storage medium for subsequent retrieval operations by the mobile computing device.

[0072] The method further includes modifying a wiring diagram.

[0073] The method further includes: storing, by the mobile computing device, the modified wiring diagram and new identity information associated with the controller; and storing the new identity information in the memory of the NFC tag for subsequent retrieval operations by the controller.

[0074] The method further includes storing the modified wiring diagram in the memory of the NFC tag.

[0075] The method further includes: using, by the mobile computing device, the identity information to retrieve a floor plan associated with a building in which the controller is located, wherein retrieving the floor plan includes retrieving the floor plan from a storage medium; and displaying, by the mobile computing device, the retrieved floor plan.

[0076] In another example, a system for retrieving configuration information for a controller includes: a near field communication (NFC) tag including an NFC memory storing identity information corresponding to the controller; a storage medium configured to store electronic (i.e., digital) data; and a mobile computing device including an NFC transceiver and configured to receive the identity information from the NFC tag and retrieve a wiring diagram associated with the controller from the storage medium.

[0077] Additionally and / or alternatively, the system of the preceding paragraph may optionally include any one or more of the following features, configurations, operations, steps, and / or additional components:

[0078] The mobile computing device is further configured to retrieve a cable label associated with a cable to be connected to the controller from the storage medium and transmit the cable label to a printer.

[0079] The system further includes a printer configured to automatically print the cable label in response to the mobile computing device retrieving the cable label and transmitting the cable label to the printer.

[0080] Although the invention has been described with reference to one or more exemplary embodiments, those skilled in the art will understand that various changes can be made and elements thereof can be replaced with equivalents without departing from the scope of the invention. In addition, many modifications can be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiments disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.

Claims

1. A method for retrieving configuration information for a controller, the method comprising: Verifying login information on a mobile computing device to ensure that the mobile computing device has permission to access a wiring diagram; Receiving, by the mobile computing device via a Near Field Communication (NFC) read operation, identity information associated with the controller from a memory of an NFC tag associated with the controller, wherein the NFC tag is passive and configured to draw power via magnetic induction from an NFC signal generated by an NFC transceiver of the mobile computing device within the range of the NFC tag and when the controller is in a powered-off state; Retrieving, by the mobile computing device, the wiring diagram from a storage medium using the identity information, including: retrieving the wiring diagram from the memory of the NFC tag when the controller is in a powered-off state, such that the wiring diagram is stored on the NFC tag; And Displaying, by the mobile computing device, the retrieved wiring diagram associated with the controller.

2. The method of claim 1, wherein the identity information includes at least one of the following: Media Access Control (MAC) address, model number of the controller, Internet Protocol (IP) address, Building Automation Control Network (BACnet) MAC address, hardware address, vendor identification number, device identification number, serial number of the controller, serial number of the NFC tag, and device location.

3. The method of claim 1, wherein the step of retrieving the wiring diagram from the storage medium further includes: Retrieving the wiring diagram from a storage medium remote from the mobile computing device and communicating with the mobile computing device, such that the wiring diagram is not stored on the mobile computing device.

4. The method of claim 1, wherein the step of retrieving the wiring diagram from the storage medium further includes: Retrieving the wiring diagram from a memory of the mobile computing device, such that the wiring diagram is stored on the mobile computing device.

5. The method of claim 1, wherein the login information includes a username and password provided to a user interface of the mobile computing device.

6. The method of claim 1, further comprising: Retrieving, by the mobile computing device, manual instructions associated with the controller from the storage medium.

7. The method of claim 6, further comprising: Displaying, by the mobile computing device, the retrieved manual instructions associated with the controller.

8. The method of claim 6, wherein the manual instructions include voice-based instructions for guiding and troubleshooting the connection of cables to the controller.

9. The method of claim 1, further comprising: Retrieving, by the mobile computing device, cable labels associated with cables configured to connect to the controller using the identity information, wherein retrieving the identity information includes retrieving the identity information from the storage medium.

10. The method of claim 9, further comprising: Displaying, by the mobile computing device, the retrieved cable labels associated with the controller.

11. The method of claim 9, further comprising: The mobile computing device transmits the cable label to a printer in response to retrieving the cable label; and the printer prints the cable label.

12. The method according to claim 9, further comprising: modifying the cable label; the mobile computing device stores the modified cable label and new identity information associated with the controller; and stores the new identity information in the memory of the NFC tag for subsequent retrieval operations by the controller.

13. The method according to claim 9, further comprising: automatically formulating the cable label from a controller program; and stores the cable label in the storage medium for subsequent retrieval operations by the mobile computing device.

14. The method according to claim 1, further comprising: modifying the wiring diagram.

15. The method according to claim 14, further comprising: the mobile computing device stores the modified wiring diagram and new identity information associated with the controller; and stores the new identity information in the memory of the NFC tag for subsequent retrieval operations by the controller.

16. The method according to claim 14, further comprising: stores the modified wiring diagram in the memory of the NFC tag.

17. The method according to claim 1, further comprising: the mobile computing device uses the identity information to retrieve a floor plan associated with the building in which the controller is located, wherein retrieving the floor plan includes retrieving the floor plan from the storage medium; and the mobile computing device displays the retrieved floor plan.

18. A system for retrieving configuration information for a controller, the system comprising: a near field communication (NFC) tag including an NFC memory storing identity information corresponding to the controller; a storage medium configured to store digital data; and a mobile computing device including an NFC transceiver, wherein the NFC tag is passive and configured to draw power via magnetic induction within the range of an NFC signal generated by the NFC transceiver of the mobile computing device and when the controller is in a powered-off state, and wherein the mobile computing device is configured to receive the identity information from the NFC tag and retrieve a wiring diagram associated with the controller from the storage medium, including: retrieving the wiring diagram from the NFC memory of the NFC tag when the controller is in a powered-off state such that the wiring diagram is stored on the NFC tag.

19. The system according to claim 18, wherein the mobile computing device is further configured to retrieve a cable label associated with a cable to be connected to the controller from the storage medium and transmit the cable label to a printer, and the system further comprises: The printer is configured to automatically print the cable label in response to the mobile computing device retrieving the cable label and transmitting the cable label to the printer.

Images