阅读说明：本技术 基于相机的调试 (Camera-based debugging ) 是由 乔纳森·耶森 杜亨·梁 于 2019-08-02 设计创作，主要内容包括：可借助于移动装置来调试照明控制系统,以进行编程和/或控制。设计软件可用于创建关于可如何设计照明控制系统的平面图。所述设计软件可为每个照明器材或照明器材群组生成平面图标识符。在所述照明控制系统的调试期间,所述移动装置可用于帮助识别已经安装在物理空间中的照明装置。所述移动装置可从每个照明控制装置接收指示所述照明控制装置的唯一标识符的通信。可通过可见光通信(VLC)或RF通信来传达所述唯一标识符。所述唯一标识符可与所述平面图标识符相关联,以用于将数字消息传达到安装在所述平面图标识符中指示的位置处的照明器材。(The lighting control system may be commissioned for programming and/or control by means of the mobile device. Design software may be used to create a floor plan on how the lighting control system may be designed. The design software may generate a floor plan identifier for each lighting fixture or group of lighting fixtures. During commissioning of the lighting control system, the mobile device may be used to help identify lighting devices that have been installed in a physical space. The mobile device may receive a communication from each lighting control device indicating a unique identifier of the lighting control device. The unique identifier may be communicated by Visible Light Communication (VLC) or RF communication. The unique identifier may be associated with the floor plan identifier for communicating digital messages to lighting fixtures installed at locations indicated in the floor plan identifier.)

1. A method of commissioning a lighting control system using a mobile device, the method comprising:

determining a location of the mobile device;

determining an orientation of the mobile device at the location;

capturing an image within the location on a camera of the mobile device, wherein the image includes a lighting fixture at the location;

superimposing plan view data over the lighting fixture in the image on a display of the mobile device, wherein the plan view data includes a plan view identifier;

receiving, via the mobile device, a unique identifier of a lighting control device for controlling a lighting load in the lighting fixture; and

associating the unique identifier of the lighting control apparatus with the floor plan identifier.

2. The method of claim 1, wherein the location is a room of a building.

3. The method of claim 1, wherein the location is selected from a list or plan of locations displayed on the mobile device.

4. The method of claim 1, wherein the location is determined automatically by a real-time positioning system implemented on the mobile device.

5. The method of claim 4, wherein the automatically determined location is confirmed by a user indication on the mobile device.

6. The method of claim 1, wherein the orientation is determined automatically by identifying a predefined object within an image of the location.

7. The method of claim 6, wherein the predefined object within the image of the location comprises a corner of a room, a lighting fixture, or a window.

8. The method of claim 1, wherein the orientation is determined based on at least two predefined objects within an image of the location.

9. The method of claim 1, wherein the orientation is determined based on an indication from a user of the mobile device.

10. The method of claim 1, wherein the floor plan data comprises at least one of: an icon representing the physical location of the lighting fixture, a representation of a connection between the lighting control apparatus and another apparatus, or a group identifier indicating a group of lighting control apparatuses that are controllable together.

11. The method of claim 1, wherein the mobile device comprises wearable computer glasses.

12. The method of claim 1, wherein the orientation of the mobile device is determined by measuring a distance between two or more predefined objects within an image of the location and identifying the distance as corresponding to a distance in a plan view of the location, the method further comprising using the measured distance to identify the lighting fixture as corresponding to a plan view lighting fixture in the plan view, and wherein associating the unique identifier of the lighting control device with the plan view identifier comprises: storing an association between the unique identifier and the floor plan identifier in a memory of the mobile device.

13. The method of claim 12, wherein the association is confirmed by a user selection on the mobile device.

14. The method of claim 1, wherein the unique identifier of the lighting control device is received via Visible Light Communication (VLC).

15. The method of claim 1, wherein the unique identifier of the lighting control device is received via RF.

16. The method of claim 1, further comprising sending a digital message comprising control instructions configured to control the lighting control device, and wherein the digital message comprises at least one of the unique identifier or the floor plan identifier.

17. A method of commissioning a lighting control system using a mobile device, the method comprising:

capturing an image on a camera of the mobile device, wherein the image includes a lighting fixture within a location of the image;

receiving a unique identifier of a lighting control apparatus for controlling a lighting load in the lighting fixture;

prompting a user to provide a floor plan identifier corresponding to a location of the lighting fixture;

receiving the floor plan identifier; and

associating the unique identifier of the lighting control apparatus with an identity of a floor plan lighting fixture.

18. The method of claim 17, wherein the mobile device comprises wearable computer glasses.

19. The method of claim 17, wherein the unique identifier of the lighting control device is received via Visible Light Communication (VLC).

20. The method of claim 18, wherein the unique identifier is received at a frequency imperceptible to the human eye.

21. The method of claim 17, wherein the identity of the floor plan lighting fixture is a string of alphanumeric characters typed by a user of the mobile device.

22. The method of claim 17, wherein the identity of the floor plan lighting fixture is received based on a selection by a user of the mobile device.

23. The method of claim 17, wherein the unique identifier of the lighting control device is received via RF.

24. The method of claim 16, further comprising sending a digital message comprising control instructions configured to control the lighting control device, and wherein the digital message comprises at least one of the unique identifier or the floor plan identifier.

Background

A lighting control system may include a lighting fixture that includes a lighting load, such as an electrical lighting control device or a light emitting diode for illuminating a space. These lighting fixtures may include lighting control devices, such as Light Emitting Diode (LED) drivers or electrical ballasts, for controlling power to the lighting load. The lighting control system may also include a system controller or hub that can send instructions to the lighting control devices to control the power provided to the lighting loads. Generally, after a lighting control system is installed in a location such as a residence, office, etc., the system controller may assign an address, such as a wireless address or a wired link address, to each lighting control device it controls. The address may be used to send instructions to the lighting control device.

However, when commissioning a lighting control system to achieve proper control of devices in the system, it is difficult to determine the lighting control device at a particular location so that the appropriate lighting control device can be programmed for lighting control. For example, a floor plan (floor plan) of a lighting control system may be designed and programmed on a computing device using design software. The plan view may indicate each lighting fixture and its corresponding location in the room or building. The design software may create a database of programming and/or control information for controlling the lighting control devices at the identified locations in the floor plan. Programming and/or control information may be uploaded to a system controller for controlling the lighting fixtures. However, an installation program at the location of a particular lighting fixture cannot readily identify the particular lighting fixture or lighting fixture address to enable programming and/or control information to be used to communicate appropriate commands to the lighting fixture at the defined location on the floor plan. In some example systems, lighting control devices may be installed at a location and a database may be created at commissioning the system, but after installation to enable proper programming of lighting control, the identity and/or address of the device at a given location may be unknown. Examples of design software for lighting CONTROL SYSTEMs are described in more detail in commonly assigned U.S. patent application No. 2017/0228110, published at 2017, 8-10, U.S. patent application No. 2017/0235470, published at 2017, 8-17, and U.S. patent application publication No. 2018/0203591, all entitled "configuration a LOAD CONTROL SYSTEM," the complete disclosures of which are hereby incorporated by reference.

Determining the identity and/or address assigned to a particular lighting control device or fixture may be time consuming and/or expensive. For example, the installation program may turn on individual lighting control devices (e.g., while other lighting control devices remain off) to associate the physical location of the lighting control device (e.g., as determined by a floor plan stored in a database created by the design software) with a given identifier or address of the lighting control device. In another example, Radio Frequency (RF) signal strength detection may be used to roughly estimate which particular lighting control apparatus or lighting fixture is closest to the installation procedure. The installer may compare the lighting control device with the strongest signal strength to the floor plan and assign a known identity in the floor plan to the serial number of the device associated with the device closest to the current location of the installer.

Disclosure of Invention

The lighting control system may be commissioned for programming and/or control with the mobile device. As described herein, a lighting control system may include a lighting control device for providing an amount of power to a lighting load. The control device may send instructions (e.g., via wired or wireless communication) to the lighting control device to provide an amount of power to the lighting load. The lighting control device may be assigned a unique identifier (e.g., a serial number, an address, such as a wireless address or a wired link address, etc.) to receive instructions to provide an amount of power to the lighting load.

Design software may be implemented to identify the location of the lighting control device within the lighting control system. The location may be, for example, a particular room in a building. For example, design software may be used to create a plan of how a lighting control system may be designed, such as the location of the lighting control devices within a space, the devices with which the lighting control devices interface, and so forth. The design software may also be used to program how the lighting control device is programmed to perform lighting control. The plan view may identify each lighting fixture and its corresponding location in the room or building. The design software may generate a floor plan identifier for each lighting fixture or group of lighting fixtures. The design software may create a database that includes programming and/or control information for controlling the lighting control devices (corresponding to each lighting control device or group of lighting control devices) identified by the floor plan identifiers in the database.

During commissioning of a lighting control system, a mobile device may be used to help identify a lighting device that has been installed in a physical space. For example, the mobile device may receive a communication from each lighting control device indicating a unique identifier (e.g., serial number, address, etc.) of the lighting control device. The unique identifier may be communicated by Visible Light Communication (VLC), such as LiFi, or RF communication, such as bluetooth signals or another RF communication signal.

The lighting control device in the lighting fixture may cause the lighting load to flash a unique identifier of the lighting control device so that the lighting control device may be identified by an image taken by a camera of the mobile device. For example, the orientation of the mobile device may be determined relative to one or more of the lighting loads. The mobile device may generate a video recording or real-time video stream that captures a binary representation of the unique identifier of the lighting control device. For example, the unique identifier may flash at a high frequency, such as a low bandwidth LiFi.

The lighting control devices in the lighting fixture may broadcast the unique identifier of the lighting control device via RF. Wireless technologies and/or protocols (e.g., can be used)Near Field Communication (NFC),THREAD、CLEAR CONNECT^TMEtc.) to broadcast the unique identifier. Multiple unique identifiers may be transmitted simultaneously, such as by multiple lighting control devices. The mobile device may determine which unique identifier corresponds to which lighting control device by measuring the strength of the transmitted signal. For example, the mobile device may determine that the strongest received signal corresponds to the closest transmitting lighting control device, and/or the weakest received signal corresponds to the furthest transmitting lighting control device.

A mobile device with a camera may be helpful in commissioning a lighting control system. The mobile device may be, for example, a cellular telephone, a laptop or tablet computer, or a wearable device (e.g., wearable computer glasses). A lighting control system may include one or more lighting fixtures and one or more lighting control devices. The lighting fixture may be, for example, a ceiling light. The lighting fixtures (e.g., each lighting fixture) may be connected to a lighting control apparatus. In an example, the camera may be directed at one or more lighting fixtures, e.g., on a ceiling of a room. The mobile device may display an image of the lighting fixture on its screen. The lighting fixture may transmit the unique identifier and the mobile device may receive the unique identifier from the lighting fixture. The unique identifier may be, for example, a serial number of the lighting control device that is controlling the fixture. For example, if a lighting control device with a serial number of "ABC 123" is connected to a given fixture, that fixture may transmit a unique identifier of "ABC 123". The unique identifier may be transmitted by, for example, VLC (e.g., LiFi) signals. If the unique identifier is transmitted by a VLC signal, it may be at a frequency high enough to be invisible to the human eye, for example 60 Hz. In addition, the unique identifier may be transmitted by, for example, an RF signal.

In an example, once the mobile device has received the unique identifier transmitted by the lighting fixture, the mobile device may prompt a user of the mobile device to provide an identity of the floor plan lighting fixture corresponding to the physical location of the transmitting lighting fixture. The mobile device may display the received unique identifier and prompt the user to type in an alphanumeric string. For example, the device may display a unique identifier "ABC 123" and the user may identify the fixture as "downlight 3". In addition to the unique identifier, the mobile device may display a plan view and prompt the user to select a plan view lighting fixture from the plan view. For example, the device may display the unique identifier "ABC 123" along with the floor plan, and the user may select the floor plan lighting fixture corresponding to the transmitting lighting fixture. Once the user has provided the identity, the mobile device may associate the identity with the received unique identifier. The association may be stored in a table or otherwise retained. Associating the unique identifier with the identity may include storing information about the physical location of the load control device corresponding to the unique identifier. For example, the association may identify a load control device (e.g., a lighting control device) to which a user may send instructions using the associated unique identifier to control the amount of power provided to the lighting fixture.

For example, commissioning of the lighting control system may be performed, for example, automatically or semi-automatically. The mobile device may determine its location, for example, in a room within a building. In an example, a user of the mobile device may select a location, for example, from a floor plan or list of locations. In another example, the location may be determined automatically, such as by a real-time positioning system implemented on the mobile device. The location may be determined using, for example, Global Positioning System (GPS) data. If the location of the mobile device is automatically located, the user may confirm the location.

Once the location of the mobile device is known, the mobile device can determine its orientation relative to one or more lighting fixtures within the location. For example, one or more of an internal compass, a gyroscope, and/or an accelerometer may be used to determine the orientation of the mobile device. The orientation of the mobile device may be determined by receiving an image from a camera in the mobile device and using one or more known objects and/or points within the location. For example, the device may use the location of one or more lighting fixtures and/or windows to determine its orientation. The device may determine its orientation by detecting the position of two or more corners of the room. The mobile device may receive input from the user regarding its orientation and may factor this input into its determination.

Once the position and orientation of the mobile device is known, the mobile device may capture an image of the position using a built-in camera. The image may include one or more lighting fixtures (e.g., one or more ceiling lights). The lighting fixtures (e.g., each lighting fixture) may be connected to a lighting control apparatus. The plan view data may be superimposed on the image. The plan view data may graphically represent one or more plan view lighting fixtures. A plan view lighting fixture (e.g., each plan view lighting fixture) may be correlated to a lighting fixture (e.g., within a location of a mobile device). The plan view data may include: one or more icons representing physical locations of lighting fixtures, representations of connections with other devices (e.g., other lighting fixtures, switches, sensors, or other devices), group identifiers indicating groups of lighting control devices that may be controlled together, and/or combinations thereof. The plan data may include one or more plan identifiers, e.g., one identifier for each plan lighting fixture. The floor plan data may include programming and/or control information for controlling the lighting control devices at the identified locations in the floor plan. Programming and/or control information may be uploaded to a system controller for controlling the lighting fixtures.

The lighting fixture may transmit the unique identifier and the mobile device may receive the unique identifier from the lighting fixture. The unique identifier may be, for example, a serial number of the lighting control device that is controlling the fixture. For example, if a lighting control device with a serial number of "ABC 123" is connected to a given fixture, that fixture may transmit a unique identifier of "ABC 123". The unique identifier may be transmitted by VLC (e.g., LiFi) or RF, for example. If the unique identifier is transmitted by VLC, it may be at a frequency high enough to be invisible to the human eye, for example 60 Hz.

Once the mobile device has received the unique identifier, the mobile device may associate the received unique identifier with the floor plan lighting fixture that is correlated with the lighting fixture that received the unique identifier. The association may be stored in a table or otherwise maintained. The association may be performed automatically, e.g., without user input. The association may be performed semi-automatically, e.g., the user may confirm that the established association is correct in general and/or individually. Associating the unique identifier with the floor plan lighting fixture may include storing information about the physical location of the load control device corresponding to the unique identifier. For example, the association may identify a load control device to which a user may send instructions for controlling the amount of power provided to the lighting fixture using the associated unique identifier.

Drawings

Fig. 1 is a perspective view of a representative environment for commissioning lighting fixtures.

Fig. 2 is a flow diagram illustrating an example method for identifying and associating lighting fixtures with load control devices.

Fig. 3 illustrates a representative image that may be displayed on a mobile device to identify a lighting fixture.

Fig. 4 illustrates another representative image that may be displayed on a mobile device to identify a lighting fixture.

Fig. 5 illustrates a representative image that may be displayed on a mobile device to associate a lighting fixture with a load control device.

Fig. 6 is a flow diagram illustrating an example method for using floor plan data to identify and associate one or more lighting fixtures with a load control device.

Fig. 7 illustrates a plan view for identifying the physical location of a mobile device.

Fig. 8 shows a plan view for identifying the orientation of a mobile device within a given location.

Fig. 9 illustrates an example of determining an orientation of a mobile device within a given location using two or more objects within the given location.

Fig. 10 illustrates an example of identifying one or more lighting fixtures in a given location using superimposed floor plan data.

FIG. 11 illustrates an example system architecture.

Fig. 12 is a block diagram of an example mobile device.

FIG. 13 is a block diagram of an example system controller.

Fig. 14 is a block diagram illustrating an example load control device.

Detailed Description

Fig. 1 is a perspective view of a representative environment for commissioning a load control system 100 having one or more lighting fixtures 108. As shown in fig. 1, each of the rooms 102, 104, and 106 may be located in the same building and may be fitted with one or more lighting fixtures. Rooms 102 and 104 may be on the same floor. Room 106 may be located on a different floor than rooms 102 and 104. Each lighting fixture 108 may include one or more lighting loads (e.g., Light Emitting Diodes (LEDs), fluorescent lamps, etc.) and one or more lighting control devices (e.g., LED drivers, electronic ballasts, etc.) in communication with a control device (e.g., system controller 112).

The communication between the system controller 112 and the lighting control devices of the lighting fixtures 108 may be wired communication or wireless communication. A Digital Addressable Lighting Interface (DALI) may be an example protocol for wired communication between load control devices. The wireless communication protocol may include Near Field Communication (NFC),THREAD、CLEAR CONNECT^TMAnd/or other wireless communication protocols.

The system controller 112 may assign a unique identifier to each lighting control device or group of lighting control devices with which the system controller may communicate to control the amount of power provided to the lighting load of the corresponding lighting fixture. For example, a unique identifier may be assigned to a lighting control device by the system controller 112 to communicate load control instructions for controlling a lighting load controlled by the lighting control device. The unique identifier may be stored at the lighting control device and may be used by the lighting control device to identify the responding instructions received from the system controller 112. Although a description may be provided for commissioning a lighting fixture having a lighting control device or LED driver, other lighting control devices may be similarly commissioned as described herein. For example, the lighting fixtures may each include a dimming circuit for controlling a dimmable lighting load, such as an incandescent lamp, or another lighting control device for controlling a different type of lighting load.

A unique identifier may be randomly assigned to each lighting control device (e.g., after installation). The unique identifier may not indicate the physical location of the lighting control apparatus, and thus it may be difficult for the user 122 to control the lighting control apparatus based on their corresponding unique identifier. Each lighting control device may also be assigned a floor plan identifier (e.g., during a design process of the load control system prior to installation of the lighting control device), which may identify the physical location of each lighting control device for the user 122. For example, the floor plan identifier may be included on a floor plan of a physical space (e.g., a building, a room, etc.) or on other devices that may enable the user 122 to recognize the physical location of a lighting control device or group of lighting control devices. When user 122 may know the floor plan identifiers associated with each lighting control apparatus, but may not know the unique identifiers used to communicate instructions to the lighting control apparatus, user 122 may be operable to associate each floor plan identifier with a unique identifier assigned to the lighting control apparatus during commissioning of the lighting control system.

As shown in fig. 1, the user 122 may know the floor plan identifier of the lighting control apparatus and may want to associate the lighting control apparatus with the unique identifier assigned to the lighting control apparatus by the system controller 112. To determine the unique identifiers assigned to the lighting control devices, the system controller 112 may instruct the lighting control devices, or a subset thereof, in the rooms 102, 104, and 106 to identify the unique identifiers assigned to them. For example, the system controller 112 may instruct the lighting control device to reveal itself by flashing the corresponding lighting load of the lighting fixture by modulating the luminosity of the light emitted by the lighting fixture (e.g., flashing at a very fast rate) in a manner indicative of the unique identifier. The flashing may be performed at a rate that is not recognizable by the human eye but recognizable by the camera (e.g., greater than about 100 Hz). The lighting control apparatus may identify the unique identifier assigned to the lighting control apparatus using the associated lighting load of the lighting fixture 108 by blinking the lighting load of the lighting fixture 108 in a manner that identifies the unique identifier. The lighting control apparatus may flash the lighting load of the lighting fixture 108 by increasing and decreasing the amount of power provided to the lighting fixture 108 such that the unique identifier is exposed by flashing the lighting load of the lighting fixture 108. For example, the lighting control device may turn the lighting load of the lighting fixture 108 on and off, thereby increasing and decreasing the dimming level of the lighting load, or some combination thereof.

The lighting control device may also or alternatively reveal itself by communicating a digital message that includes a unique identifier assigned to the lighting control device. For example, the RF signal may be transmitted via Radio Frequency (RF) communications (such as,near Field Communication (NFC),CLEAR CONNECT^TMEtc.) communicate a unique identifier from a lighting control device of the lighting fixture.

The mobile device 124 may identify the unique identifier provided by the lighting control device (e.g., by visually identifying the unique identifier in an image captured by the camera of the mobile device 124), and the unique identifier may be associated with the floor plan identifier to which the lighting control device is assigned. The association may be performed via the mobile device 124 (e.g., user device, cellular telephone, tablet computer, wireless load control device, photosensor, etc.), the system controller 112, and/or the server 114 (e.g., remote computer). If the association is performed at the mobile device 124, the association may be sent to the server 114 and/or the system controller 112 for storage.

Upon receiving a trigger from the user 122, the system controller 112 may send an identification instruction to the lighting control apparatus. For example, user 122 may select a button on mobile device 124 that causes mobile device 124 to send a message to system controller 112 that triggers transmission of the identification instruction. Mobile device 124 may communicate directly over a short-range wireless channel (e.g., etc.) and/or indirectly via server 114 and internet 116 (e.g., usingA network, a cellular network,Network, etc.) to communicate with the system controller 112. Server 114 may forward communications received from mobile device 124 to system controller 112 using wired or wireless communications.

In another example, the identification instructions may be sent directly from the mobile device 124 to each lighting control device. For example, the mobile device 124 may send the identification instructions via a broadcast message that may cause any lighting control device receiving the instructions to identify its unique identifier. For example, the wireless communication device may be configured to transmit the wireless communication via any short-range wireless channel (e.g.,etc.) to transmit the broadcast message.

When a lighting control device in the lighting fixture 108 may be included in the group of lighting control devices that have their respective unique identifier flashed, the mobile device 124 may be able to capture an image (e.g., a plurality of sequential images, such as a moving image or video) that includes the unique identifiers of the plurality of lighting control devices without having to change locations. For example, a camera on the mobile device 124 may be capable of capturing an image of each of the lighting fixtures that are flashed by the respective lighting control devices in the group to visually identify a unique identifier for each lighting control device in the group. The camera on the mobile device 124 may be capable of capturing an image of each of the flashing lighting fixtures from one location or may be moved from the physical location of one lighting control device to the next to capture an image of the unique identifier of each lighting control device. Although fig. 1 illustrates identification of the unique identifier of a lighting control device (e.g., an LED driver), the unique identifiers of other lighting control devices (e.g., LED drivers, ballasts, or other lighting control devices) capable of controlling a lighting load may be similarly identified.

Fig. 2 is a flow diagram illustrating an example method 200 for identifying a lighting fixture (e.g., a lighting control device that controls a lighting load of the lighting fixture) and associating a unique identifier with a plan view identifier of the lighting fixture, e.g., using a mobile device. The method 200 may begin at 202. At 204, the mobile device may capture an image of the lighting fixture and display the image of the lighting fixture on a display of the mobile device. The mobile device may be located at a given location. For example, the location may be a hallway or room of a building. The image of the lighting fixture may be a single image or video of the location on the display of the mobile device. The display may show one or more lighting fixtures. The mobile device may highlight or otherwise represent the lighting fixtures so that the user may identify them. The mobile device may prompt the user to select a lighting fixture to be commissioned. Alternatively, the mobile device may automatically select the lighting fixture.

At 206, a unique identifier of a load control device in the lighting fixture may be identified. The unique identifier may be identified by the mobile device, the system controller, or another device. Only forAn identifier may identify a lighting control device that controls the lighting fixture. The unique identifier may be an alphanumeric string. The lighting control device may transmit the unique identifier by, for example, causing the lighting load of the lighting fixture to blink in a predetermined pattern (e.g., modulating light emitted by the lighting fixture to transmit the unique identifier via VLC signals) or otherwise blink, thereby communicating the data. The unique identifier may be conveyed at a frequency imperceptible to the human eye (i.e., greater than about 100 Hz). A camera on the mobile device may capture an image of the signaling that includes the unique identifier, which may be interpreted by the mobile device, the system controller, or another device. The unique identifier may also or alternatively be communicated via RF. For example, use can be made ofNear Field Communication (NFC),CLEAR CONNECT^TMAnd/or another RF protocol to signal the unique identifier. If more than one lighting fixture is present, the mobile device may determine which lighting fixture conveys the unique identifier by comparing signal strengths. For example, the mobile device may determine that the unique identifier associated with the strongest RF signal was received from the lighting control device that is physically closest to the mobile device. The mobile device may prompt the user to confirm that its determination is correct. Alternatively, the user may indicate which lighting fixture conveys the unique identifier. A user may select a button on the mobile device to cause the mobile device to send a digital message to the lighting control device that causes its respective lighting load to blink, so that the user may view the blinking lighting load of the lighting control device in a physical space corresponding to a given RF signal strength or unique identifier.

At 208, the mobile device may prompt the user to enter a floor plan identifier for the lighting fixture from which the unique identifier was received. The mobile device may display a pop-up window showing the received unique identifier. The pop-up window may contain a text box in which the user may type a floor plan identifier. The floor plan identifier may be a string of alphanumeric characters. For example, the floor plan identifier for a given lighting fixture may be "downlight 1". For example, the mobile device may suggest a floor plan identifier to the user based on floor plan data accessible to the mobile device. Before installing the load control system, the floor plan data may be generated during a design process of the load control system. Each lighting fixture within a given location may have a unique floor plan identifier in the floor plan data. The mobile device may prompt the user to confirm that the entered floor plan identifier is correct.

At 210, the entered floor plan identifier may be associated with the received unique identifier. The association may be performed by the mobile device, the system controller, or another device. The association between the floor plan identifier and the unique identifier can be stored in a memory of the mobile device and can be transmitted by the mobile device to an external device (e.g., a system controller, a server, and/or another external device) having a memory and stored on the external device. For example, the system controller and/or the server may be configured to identify a command for the lighting control device using the floor plan identifier and transmit the command to the lighting control device using the unique address of the lighting control device. Additionally, the association may be transmitted to the lighting control device and stored in a memory of the lighting control device such that the lighting control device may recognize the message including its floor plan identifier. The method 200 may end at 212, and the association may be used to configure and/or control lighting loads in the lighting control system.

Fig. 3 illustrates an example image 308 that may be obtained by the mobile device 306 for displaying one or more lighting fixtures (e.g., at 204 of the method 200 of fig. 2). For example, image 308 may represent a frame of a video generated by mobile device 306. The image 308 may include the lighting fixtures or a subset thereof within the room.

The mobile device 306 may detect the lighting fixture 304 automatically or based on a user indication. The mobile device 306 may use an internal camera to capture images or video of the lighting fixture 304. The user may orient mobile device 306 such that the interior camera is pointed at one or more lighting fixtures. Image 308 may be displayed on a display of mobile device 306.

The mobile device 306 may automatically detect the lighting fixture 304 by comparing portions of the image 308 to determine whether one or more portions of the image 308 exceed an intensity threshold. For example, mobile device 306 may determine that a portion of image 308 within region 302 exceeds an intensity threshold, and may determine that region 302 includes lighting fixture 304. The intensity threshold may be relative to the intensity level of other portions of the image 308 to compensate for the illumination level of different videos, images, mobile device displays, and the like. Mobile device 306 may detect lighting fixtures within area 302 by detecting the shape of one or more lighting fixtures within image 308. The mobile device 306 may be preconfigured to identify the size and/or shape of a standard lighting fixture in a building. The lighting fixture may be compared to other parts of the room to determine the relative size of the lighting fixture. For example, the lighting fixture may be compared to ceiling tiles, windows, or other objects within an image to determine the relative size of the lighting fixture. The largest lighting fixture or group of lighting fixtures may be automatically detected by the mobile device 306 for association.

In another example, the user may indicate that the lighting load region 302 includes a lighting fixture 304. The user may provide such an indication by selecting within the area 302, circling the area 302, or otherwise indicating the area 302. As described herein, the mobile device 306 may assume that fixtures are present within a predefined area indicated by the user, or may automatically detect one or more lighting fixtures within the identified portion of the image.

After identifying the lighting load region 302, the mobile device 306 may analyze the incoming video or video frame to detect the unique identifier indicated by the lighting load of the lighting fixture 304. Fig. 4 illustrates an example image 408 that may be generated by the mobile device 306 for commissioning a lighting control device to display and/or identify a unique identifier 414 of the lighting control device (e.g., at 206 of the method 200 of fig. 2). For example, image 408 may represent a frame of a video generated by mobile device 306. The image 408 may include lighting fixtures within a location (e.g., a room of a building) or a subset thereof. The mobile device 306 can overlay planogram data, such as the unique identifier 414 that the mobile device 306 has received from a lighting control device (not shown), onto the image 408. The unique identifier 414 may be signaled by the lighting load of the lighting fixture 304. The unique identifier 414 may be displayed in the pop-up window 410. The mobile device 306 may indicate the lighting fixture 304 associated with the unique identifier 414 via the overlay. If there is more than one lighting control apparatus in the location, the mobile device 306 may indicate to the user which lighting control apparatus sent the unique identifier 414. For example, the mobile device 306 may indicate to the user that the unique identifier 414 was received from a lighting control device that controls the lighting load of the lighting fixture 304. Pop-up window 410 may include a commissioning button 412 that, when pressed, may allow a user to enter floor plan data, such as a floor plan identifier, for lighting fixture 304. The mobile device 306 can prompt the user to confirm that the entered planogram data is correct.

Referring again to fig. 3, a lighting control device (not shown) may control the lighting load of the lighting fixture 304 and may use the lighting load of the lighting fixture 304 to signal the unique identifier of the lighting control device. For example, the mobile device 306 may receive a signal from the lighting load of the lighting fixture 304 and may identify the signaled unique identifier. The unique identifier may be transmitted and received via VLC signals. For example, the unique identifier of the lighting control apparatus may be signaled by flashing the lighting load of the lighting fixture 304 in a pattern, sequence, rate, etc. corresponding to the unique identifier.

The lighting control device may signal its unique identifier via, for example, an RF signal. The mobile device 306 may receive the RF signal from the lighting control device and determine the unique identifier based on the received signal (e.g., included in the RF signal). The RF signal may be a short-range signal (e.g.,a signal,Signals, Near Field Communication (NFC) signals,Signal, CLEAR CONNECT^TMSignal, etc.) or another RF signal. The mobile device 306 may receive unique identifiers from more than one lighting control device at the same time. The mobile device 306 can use the received signal strength to determine which lighting control device sent which unique identifier. For example, the mobile device 306 can determine that the unique identifier associated with the strongest RF signal was received from the lighting control device that is physically closest to the mobile device 306. The mobile device 306 may use information from the image 308 to determine which lighting control device is physically closest to the mobile device 306. For example, the mobile device 306 may identify the lighting control device in the lighting fixture 304 as being physically closest to the mobile device based on the relative sizes of the lighting fixture 304 and the other lighting fixtures. When one lighting fixture is identified, the physically closest lighting control device may be located in a single lighting fixture included in the image. The mobile device 306 may use input from the user to determine which lighting control device is closest to the mobile device 306. For example, the mobile device 306 may prompt the user to select the lighting control device closest to the mobile device 306. The user may select the lighting fixture 304 as the physically closest lighting device. The mobile device 306 can assume the lighting device identified as being physically closest to have a unique identifier received with the strongest RF signal.

Fig. 5 illustrates an example image 508 that may be displayed on a mobile device to associate a unique identifier of a lighting control device with a plan view identifier (e.g., at 208 of the method 200 of fig. 2). For example, image 508 may represent a frame of a video generated by mobile device 306. The image 508 may include lighting fixtures within the room or a subset thereof. The pop-up window 410 may display a text box 514 and/or a confirmation button 512. A text box 514 and/or a confirmation button 512 may be displayed instead of, for example, the debug button 412 shown in fig. 4. After the user has pressed the debug button 412 shown in fig. 4, an image 508 may be displayed on the mobile device 306. The user may type in a floor plan identifier in text box 514. The floor plan identifier may be, for example, an alphanumeric sequence or other sequence of characters. The floor plan identifier may be determined from a blueprint or other drawing showing a floor plan of the building. After the user has entered the floor plan identifier into the text box 514, the user may press the confirmation button 512. The mobile device 306 may associate a unique identifier of a lighting control device (not shown) connected to the lighting fixture 304 with a planar view identifier entered into the text box 514 by the user.

For example, the lighting control apparatus may signal the unique identifier using the lighting load of the lighting fixture 304. The unique identifier may be, for example, "ABC 123". The mobile device 306 can receive the signaled unique identifier. The mobile device 306 can indicate to the user that the unique identifier has been received. The mobile device 306 may prompt the user to commission the lighting control device. The user may indicate that they wish to commission the lighting control apparatus by pressing the commissioning button 412 shown in fig. 4. Mobile device 306 may prompt the user to type a floor plan identifier in text box 514. The user may, for example, type "Down light 1" in text box 514. The floor plan identifier may be automatically presented to the user by the mobile device 306. The user may press a confirmation button 512 to confirm proper entry of the floor plan identifier. Other floor plan data may be presented to or entered by the user. The mobile device 306 can associate the received unique identifier with the typed planar view identifier (e.g., at 210 of the method 200 of fig. 2). The association between the unique identifier and the floor plan identifier can be stored on the mobile device and/or on an external device (e.g., server, system controller, etc.).

Fig. 6 is a flow diagram illustrating an example method 600 for identifying one or more lighting fixtures (e.g., lighting control devices controlling respective lighting loads of the lighting fixtures) and associating unique identifiers with plan view identifiers of each of the lighting fixtures. The method 600 may begin at 602. The method 600 may be performed on a programming device, such as a mobile device, or distributed across multiple programming devices, such as a mobile device, a system controller, or another device. At 604, a location of mobile device 306 may be determined. For example, the location may be a room in a building, such as an office, conference room, hallway, or any other space within the building. The location of the mobile device 306 may be automatically determined. For example, the location of mobile device 306 can be determined by a real-time positioning system (e.g., GPS, triangulation, NFC, geolocation, etc.) implemented on mobile device 306. The location of the mobile device 306 may be determined by user input (e.g., the user may select the correct location from a list of predefined locations). The location may be determined automatically and confirmed by the user.

At 606, an orientation of mobile device 306 (e.g., relative to other objects within the location) may be determined. The orientation may be determined by using a real-time orientation sensor (e.g., a sensor such as an accelerometer, gyroscope, and/or any other sensor for detecting orientation on the mobile device). The orientation may be determined by user input. For example, the user may select an orientation. Mobile device 306 may prompt the user to make a selection on a display of mobile device 306 indicating the orientation of mobile device 306. The orientation may be determined by automatically detecting the relative positions of two or more known objects within the position. The known object may be, for example, a corner of a room, a window, a lighting fixture, or other object within the location. For example, as shown in fig. 9, the mobile device 306 may determine its orientation by automatically detecting two corners of a room in which the mobile device 306 is located.

Referring again to fig. 6, at 608, the mobile device 306 can overlay plan view data onto the image 308 of the location. The plan data may correlate the physical lighting fixtures with corresponding plan identifiers. For example, each of the one or more lighting fixtures 304 may have a corresponding floor plan identifier in the floor plan data. The plan view data may include: one or more icons representing physical locations of lighting fixtures, representations of connections with other devices (e.g., other lighting fixtures, switches, sensors, or other devices), group identifiers indicating groups of lighting control devices that may be controlled together, and/or combinations thereof. The planogram data may include a planogram identifier. The floor plan data may include programming and/or control information for controlling the lighting control devices at the identified locations in the floor plan. Programming and/or control information may be uploaded to a system controller for controlling the lighting fixtures.

At 610, the mobile device 306 may receive one or more unique identifiers from one or more lighting fixtures 304. For example, the mobile device may receive a separate unique identifier from each lighting fixture 304 within the location. The unique identifier may be generated by activating the lighting control device of the lighting load of the corresponding lighting fixture 304. The mobile device 306 can associate the received unique identifier with a corresponding floor plan identifier. The association may be stored in a memory of mobile device 306. The mobile device 306 can transmit the association to an external device having memory (e.g., a server, a system controller, or another external device) and store on the external device. The association may be transmitted to the lighting control device and stored on a memory of the lighting control device. The method 600 may end at 612 and the association may be used to configure and/or control lighting loads in the lighting control system. For example, the user may select on the image of the mobile device 306 that the lighting fixture is identified by the floor plan identifier, and may communicate the configuration information and/or control instructions to the lighting control device of the lighting fixture using the associated unique identifier. The communication may be performed directly or via another device, such as a system controller.

Fig. 7 illustrates an example plan view 704 for identifying a physical location of a mobile device (e.g., at 604 of method 600 of fig. 6). Image 708 may be displayed on mobile device 306. Image 708 may depict one or more floor plans for a given location. The image 708 may display a plan view 704 of a building. The plan view 704 displayed on the image 708 may include a depiction of one or more rooms 710, 712, and 714. Each room 710, 712, and 714 may reflect a location in which one or more lighting fixtures are installed or are to be installed. For example, the location of one or more lighting fixtures B1-B27 within the rooms 710, 712, 714 may be depicted. The lighting fixtures B1-B27 may be installed at a particular distance from other objects in the room (e.g., walls, other lighting fixtures, etc.). After installation, each of the lighting fixtures B1-B27 may be assigned a unique identifier (e.g., a serial number, address, etc.) to communicate with the lighting fixture.

Rooms 710, 712, and 714 may be on the same floor of a building or on different floors. A user of mobile device 306 may select a room in which mobile device 306 is located. For example, the user may select room 710 as the room in which mobile device 306 is located. The user may select the room 710 by pressing the select room button 702 and then selecting, for example, the room 710. Alternatively, the user may select the room 710 and confirm their selection by pressing the select room button 702. The user may select the room 710 by selecting from a list of rooms.

The user may determine and confirm the location and/or orientation of mobile device 306. Fig. 8 shows an example image 808 displayed on mobile device 306, including a plan view 704 (e.g., at 606 of method 600 of fig. 6) for determining a position and/or orientation of mobile device 306 within a given location. Plan view 704 may include a room of a building, such as room 714. The plan view 704 may include one or more icons (such as icon 804), which may represent the physical location of a lighting fixture (e.g., lighting fixture B27 in fig. 8). The plan view 704 may show the locations of the lighting fixtures in relation to each other and/or other objects in space (e.g., relative locations of the lighting fixtures). The mobile device 306 and/or system controller may have stored thereon a floor plan identifier that indicates the location of one or more of the lighting fixtures in the floor plan 704.

The location and/or orientation of the mobile device 306 may be determined based on input from a user. Plan view 704 may include a mobile device icon (such as icon 812) that may indicate a location and/or orientation of mobile device 306. For example, the user may select the direction on the plan view 704 that the user is facing. The location may be automatically determined using a real-time positioning system (e.g., GPS, triangulation, etc.). The orientation may be determined automatically (e.g., using a real-time orientation sensor) and assisted by the user. The orientation may be determined based on user input indicative of two or more defined portions of the room 714. The mobile device 306 can determine its orientation using a weighted calculation. For example, mobile device 306 may use data from a GPS, accelerometer, gyroscope, altimeter, compass, or any combination thereof to determine its orientation. The user may confirm the determined position and/or orientation by pressing a confirm button 802. The mobile device 306 can use information from the internal camera to verify its orientation. The mobile device 306 can automatically determine the location and/or orientation without notifying the user.

Fig. 9 shows an example image 908 (e.g., at 606 of method 600 of fig. 6) of determining an orientation of mobile device 306 within a given location (e.g., a room of a building) using two or more objects within the given location. For example, image 908 may represent a frame of a video generated by mobile device 306. Image 908 may include lighting fixtures within a location or a subset thereof.

The mobile device 306 may determine its orientation based on two or more predetermined objects within the location. The predetermined object may have a fixed position within the location. The mobile devices 306 may determine their orientation using, for example, the position of predetermined objects relative to each other. The predetermined object may be, for example, a corner of a room, a window, a lighting fixture, or a combination thereof. The user may be prompted to select certain predetermined objects to orient the mobile device 306 within the location on the plan view. For example, the mobile device 306 may prompt the user to select two corners 910, 912 on the north wall of the identified room that intersect the ceiling. The user may select the corners 910, 912 of the room to determine their orientation within the plan view.

The mobile device 306 can measure the distance between objects (e.g., 910, 912) at a selected orientation and set the distance in the image 908 equal to the distance indicated between the objects in the plan view data. This distance can be used to calculate the relative size of the objects in the room of the image 908 and the distance between the objects. The mobile device 306 may also or alternatively prompt the user to select two points that are a predetermined predefined object within the room. For example, the mobile device 306 may prompt the user to select top and bottom corners of a door or wall having a standard size.

The mobile device 306 can use information of its orientation to determine its position within the plan view relative to a predetermined object in the image 908. The plan view data may include distances between objects (e.g., walls, lighting fixtures, etc.) in the room. The mobile device 306 may track the size of objects in the image 908 as well as the distance between objects (e.g., corners, lighting fixtures, etc.) to identify one or more lighting fixtures. The mobile device 306 may identify the lighting fixtures within the image based on the position/orientation of the mobile device relative to the object indicated in the floor plan data. For example, the mobile device 306 may identify a lighting fixture within the image based on the location/orientation of the mobile device, the size of the lighting fixture, and/or the distance of the lighting fixture from the selected orientation object (e.g., corners 910, 912).

Fig. 10 illustrates an example image 1008 identifying one or more lighting fixtures in a given location using superimposed floor plan data (e.g., at 608 of method 600 of fig. 6). For example, image 1008 may represent a frame of a video generated by mobile device 306. The image 1008 may include lighting fixtures within a location or a subset thereof. The mobile device 306 may identify the lighting fixture within the location based on the size and/or location of the lighting fixture from the reference point. The mobile device 306 may determine which lighting fixtures indicated in the plan data are within the image 1008 based on the location of the mobile device 306, the orientation of the mobile device 306, and the plan data indicating the locations of the lighting fixtures in the image. Mobile device 306 may identify one or more assets in the image as assets in the planogram data.

Mobile device 306 can overlay the floor plan data over the lighting fixtures displayed in image 1008. For example, the floor plan data may be stored on a memory of the mobile device 306 and/or received from an external device, such as a system controller. The plan view data may identify plan view identifiers corresponding to physical locations of the lighting fixtures. The plan data may include one or more plan identifiers (e.g., one plan identifier for each lighting fixture in image 1008). The plan view data may include: one or more icons representing physical locations of lighting fixtures, representations of connections with other devices (e.g., other lighting fixtures, switches, sensors, or other devices), group identifiers indicating groups of lighting control devices that may be controlled together, and/or combinations thereof. The floor plan data may include programming and/or control information for controlling the lighting control devices at the identified locations in the floor plan. Programming and/or control information may be uploaded to a system controller for controlling the lighting fixtures. The mobile device 306 can overlay the outline 1010 identifying the lighting fixture at the corresponding location in the plan view data. The mobile device 306 may superimpose the floor plan identifier D2 on the lighting fixture 304. The mobile device 306 can prompt the user to confirm that the overlaid floor plan data is correct.

Mobile device 306 may receive one or more unique identifiers from one or more lighting fixtures. The unique identifier may identify a lighting control device (not shown) associated with the lighting fixture. For example, the mobile device 306 may receive a separate unique identifier from each lighting fixture within the location. The unique identifier may be used to communicate with the lighting control device that initiated the lighting load of the corresponding lighting fixture 304.

The mobile device 306 may prompt the user to commission the lighting control device in the fixture by pressing the commissioning button 1002. The lighting control device may be commissioned by associating the floor plan identifier of the lighting fixture with the unique identifier assigned to the lighting control device for performing load control and other communications with the lighting control device. Upon selection of the commissioning button 1002, the mobile device 306 may automatically detect the unique identifier of the lighting control device (e.g., via VLC or RF) corresponding to the lighting fixture in the image, as described herein.

The unique identifier may be communicated via VLC signals. The mobile device 306 may analyze the incoming video or frames of the video to detect the unique identifier indicated by the lighting load of the lighting fixture. For example, the mobile device 306 may receive a signal from the lighting load of the lighting fixture 304 and may identify the unique identifier being signaled. The unique identifier of the lighting control apparatus may be signaled by flashing the lighting load of the lighting fixture 304 in a pattern, sequence, rate, etc. corresponding to the unique identifier. The unique identifier may be transmitted by the lighting load of the lighting fixture and detected by the camera of the mobile device 306 at a frequency that is imperceptible to the human eye.

The unique identifier may be communicated via an RF signal. The mobile device 306 may receive RF signals from the lighting control deviceAnd determines a unique identifier based on the received signal. The RF signal may be, for exampleA signal,Signals, Near Field Communication (NFC) signals,Signal, CLEAR CONNECT^TMA signal or another RF signal. The mobile device 306 may receive unique identifiers from more than one lighting control device at the same time. The mobile device 306 may use, for example, the received signal strength to determine which lighting control device sent which unique identifier. For example, the mobile device 306 may determine that the unique identifier associated with the strongest RF signal is received from the lighting control device in the image that is physically closest to the mobile device 306 (e.g., the lighting control device in the largest lighting fixture). The mobile device 306 may use input from the user to determine which lighting control device is closest to the mobile device 306. For example, the mobile device 306 may prompt the user to select the lighting control device closest to the mobile device 306.

Once the mobile device 306 has received the unique identifier, the mobile device 306 may associate the unique identifier of the lighting control device in the image with the lighting control device indicated in the corresponding floor plan data (e.g., at 610 of method 600 of fig. 6). For example, the mobile device 306 can associate between the unique identifier and the floor plan identifier. The mobile device may prompt the user to confirm one or more associations (e.g., each association). The mobile device 306 may highlight or otherwise indicate the lighting fixture that has been successfully associated. The mobile device 306 can indicate to the user that each association has been completed correctly. The user may correct incorrect associations made by mobile device 306. The association may be stored in a memory of the mobile device 306. The mobile device 306 can transmit the association to an external device (e.g., server, system controller, etc.) having a memory and store on the external device. The association may be transmitted to the lighting control device and stored on a memory of the lighting control device. The associations may be used to configure and/or control lighting loads in the lighting control system. For example, the floor plan identifier may be used to communicate information to and/or from the lighting control apparatus, or a unique identifier of the apparatus may be identified to send a message to the lighting control apparatus having the identified floor plan identifier. For example, the mobile device 304 or system controller may communicate a digital message to the lighting fixture 304 using a unique identifier associated with the floor plan identifier "D4".

Fig. 11 illustrates an example system architecture 1100 as described herein. The system architecture 1100 may include a mobile device 1102. The mobile device 1102 may be, for example, a cellular telephone, a laptop or tablet computer, or a wearable device (e.g., wearable computer glasses). The mobile device 1102 may have an internal camera capable of capturing signals on the VLC communication link 1105 from the lighting fixture 1104 or other light source. Mobile device 1102 can include communication circuitry (e.g., a receiver, transceiver, etc.) that is capable of receiving communications over an RF communication link 1106.

The mobile device 1102 may receive information (e.g., a unique identifier) from a lighting control device 1108 installed in the lighting fixture 1104 to control the lighting load. The data may be transmitted via VLC over VLC communication link 1105 (e.g., LiFi) and/or via RF over RF communication link 1106 (e.g.,near Field Communication (NFC),CLEAR CONNECT^TM) The information is conveyed. A lighting control device 1108 may be installed in the lighting fixture 1104 and may control the lighting load to generate VLC signals over the VLC communication link 1105 at a rate imperceptible to the human eye. The lighting control device 1108 may include communication circuitry (e.g., a transmitter, transceiver, etc.) capable of communicating via the RF communication link 1106. Information included on VLC communication link 1105 or RF communication link 1106 for lightingThe control means 1108 may be unique.

The lighting control device 1108 may be connected to a system controller 1110 (e.g., a hub). The lighting control device 1108 may be connected via a wired communication link (e.g., an ethernet or other wired network communication link) and/or a wireless communication link 1109 (e.g., HSPA +, LTE, 5G, or another wireless communication link) to a system controller 1110. The lighting control device 1108 may send information to the system controller 1110 and/or receive information from the system controller 1110 via a wired and/or wireless communication link 1109. For example, the lighting control device 1108 may be programmed with a unique identifier received from the system controller 1110 for sending and/or receiving digital messages. The association of the unique identifier with the floor plan identifier may also be communicated from the system controller 110 to the lighting control device 1108 via a wired and/or wireless communication link 1109.

System controller 1110 can communicate with mobile device 1102 via RF communication link 1107. RF communication link 1107 may include the use ofCommunication of HSPA +, LTE, 5G, or another wireless communication signal. Although shown as a wireless communication link, the RF communication link 1107 may be replaced by a wired communication link such as ethernet. Mobile device 1102 can receive floor plan data or other system information via RF communication link 1107. The mobile device 1102 may transmit the unique identifier and/or association information including an association between the unique identifier and the planogram data via the RF communication link 1107. The mobile device 1102 can also, or alternatively, communicate directly with a network infrastructure or internet service to send and/or receive information.

The system controller 1110 may be connected to a network infrastructure 1112, such as by a wired communication link (e.g., an Ethernet or other wired network communication link)) And/or a wireless communication link 1109 (e.g.,HSPA +, LTE, 5G, or another wireless communication link). The network infrastructure 1112 may use the internet service 1114 to send information to and/or receive information from remote computing devices.

Internet service 1114 may be used to communicate with design software client 1116. Design software client 1116 may be used to program and/or store planogram data. System controller 1110 can receive information from design software client 1116 and send information to design software client 1116 via network infrastructure 1112 and/or internet service 1114. For example, the system controller 1110 or other devices in the system may access the planogram data or portions thereof by a request from a design software client.

Fig. 12 is a block diagram illustrating an example mobile device 1200 as described herein. For example, mobile device 1200 may include mobile device 124. The mobile device 1200 may include control circuitry 1202 for controlling the functionality of the mobile device 1200. The control circuitry 1202 may include one or more general-purpose processors, special-purpose processors, conventional processors, Digital Signal Processors (DSPs), microprocessors, integrated circuits, Programmable Logic Devices (PLDs), Application Specific Integrated Circuits (ASICs), and the like. The control circuitry 1202 may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the mobile device 1200 to perform as described herein. The control circuit 1202 may store information in and/or retrieve information from the memory 1204. The memory 1204 may include non-removable memory and/or removable memory. The non-removable memory may include Random Access Memory (RAM), Read Only Memory (ROM), a hard disk, or any other type of non-removable memory storage device. The removable memory may include a Subscriber Identity Module (SIM) card, a memory stick, a memory card, or any other type of removable memory.

The mobile device 1200 may include communication circuitry 1208 for transmitting and/or receiving information. The communication circuit 1208 may perform wireless and/or wired communication. The communication circuitry 1208 may include an RF transceiver or other circuitry capable of performing wireless communication via an antenna. The communication circuit 1208 may be in communication with the control circuit 1202 for transmitting and/or receiving information.

The control circuit 1202 may also communicate with a display 1206 to provide information to a user. Control circuitry 1202 and/or display 1206 may generate a GUI for display on mobile device 1200. The display 1206 and the control circuit 1202 may be in bi-directional communication, as the display 1206 may include a touch screen module capable of receiving information from a user and providing such information to the control circuit 1202. The mobile device may also include an actuator 1212 (e.g., one or more buttons) that may be actuated by the user to communicate user selections to the control circuitry 1202.

Each of the modules within the mobile device 1200 may be powered by a power source 1210. The power source 1210 may include, for example, an AC power supply or a DC power supply. The power supply 1210 may generate a supply voltage Vcc for powering modules within the mobile device 1200.

Fig. 13 is a block diagram illustrating an example system controller 1300 as described herein. The system controller may be a gateway system controller, a target system controller, a remote system controller, and/or combinations thereof. The system controller 1300 may include control circuitry 1302 for controlling the functionality of the system controller 1300. The control circuitry 1302 may include one or more general-purpose processors, special-purpose processors, conventional processors, Digital Signal Processors (DSPs), microprocessors, integrated circuits, Programmable Logic Devices (PLDs), Application Specific Integrated Circuits (ASICs), and the like. The control circuitry 1302 may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the system controller 1300 to perform as described herein. The control circuit 1302 may store information in and/or retrieve information from the memory 1304. The memory 1304 may include non-removable memory and/or removable memory. The non-removable memory may include Random Access Memory (RAM), Read Only Memory (ROM), a hard disk, or any other type of non-removable memory storage device. The removable memory may include a Subscriber Identity Module (SIM) card, a memory stick, a memory card, or any other type of removable memory.

System controller 1300 may include communication circuitry 1306 for transmitting and/or receiving information. The communication circuit 1306 may perform wireless and/or wired communication. The system controller 1300 may also or alternatively include a communication circuit 1308 for transmitting and/or receiving information. The communication circuit 1306 may perform wireless and/or wired communication. The communication circuits 1306 and 1308 may communicate with the control circuit 1302. Communication circuits 1306 and 1308 may include an RF transceiver or other communication module capable of performing wireless communication via an antenna. The communication circuit 1306 and the communication circuit 1308 may be capable of performing communication via the same communication channel or different communication channels. For example, the communication circuit 1306 may be capable of communicating via a wireless communication channel (e.g.,near Field Communication (NFC),Cellular, etc.), while the communication circuit 1308 may be capable of communicating via another wireless communication channel (e.g.,or a proprietary communication channel, such as CLEAR CONNECT^TM) Communication is performed (e.g., with a control device and/or other devices in the load control system).

The control circuit 1302 may be in communication with an LED indicator 1312 for providing an indication to a user. The control circuitry 1302 may be in communication with an actuator 1314 (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuitry 1302. For example, the actuator 1314 may be actuated to place the control circuitry 1302 in an association mode and/or to communicate an association message from the system controller 1300.

Each of the modules within the system controller 1300 may be powered by a power supply 1310. The power supply 1310 may include, for example, an AC power supply or a DC power supply. The power supply 1310 may generate a supply voltage Vcc for powering the modules within the system controller 1300.

Fig. 14 is a block diagram illustrating an example control-target device (e.g., load control device 1400) as described herein. The load control device 1400 may be a dimmer switch, an electronic lighting control device for a lamp, an LED driver or other lighting control device for an LED light source, an AC plug-in load control device, a temperature control device (e.g., a thermostat), a motor drive unit for a motorized window treatment, or other load control device. The load control device 1400 may include a communication circuit 1402. The communication circuit 1402 may include a receiver, RF transceiver, or other communication module capable of performing wired and/or wireless communication via a communication link 1410. The communication circuit 1402 may communicate with the control circuit 1404. The control circuitry 1404 may include one or more general purpose processors, special purpose processors, conventional processors, Digital Signal Processors (DSPs), microprocessors, integrated circuits, Programmable Logic Devices (PLDs), Application Specific Integrated Circuits (ASICs), and the like. The control circuit 1404 may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the load control device 1400 to perform as described herein.

The control circuit 1404 may store information in and/or retrieve information from the memory 1406. For example, memory 1406 may maintain a registry and/or control configuration instructions for associated control devices. Memory 1406 can include non-removable memory and/or removable memory. The load control circuit 1408 may receive instructions from the control circuit 1404 and may control the electrical load 1416 based on the received instructions. The load control circuit 1408 may send state feedback to the control circuit 1404 regarding the state of the electrical load 1416. The load control circuit 1408 may receive power via the thermal connection 1412 and the neutral connection 1414 and may provide an amount of power to the electrical load 1416. The electrical load 1416 may include any type of electrical load, such as a lighting load (e.g., an LED, a fluorescent lamp, etc.).

The control circuit 1404 may be in communication with an actuator 1418 (e.g., one or more buttons) that can be actuated by a user to communicate user selections to the control circuit 1404. For example, the actuator 1418 may be actuated to place the control circuit 1404 in an association mode and/or to communicate an association message from the load control device 1400.