Patent Description:
Each load control system may include various control devices, including control-source devices and control-target devices. The control-target devices may receive messages (e.g., digital messages) from one or more of the control-source devices. The messages may include load control messages for controlling an electrical load. The control-target devices may be capable of directly controlling the electrical load. The control-source devices may be capable of indirectly controlling the electrical load via the control-target device by sending messages to the control-target device that include control instructions for controlling the electrical load controlled by the control-target device.

Window treatments, such as, for example, roller shades, draperies, roman shades, and venetian blinds, are normally mounted in front of windows to provide for control of the amount of sunlight entering a space. A typical venetian blind system comprises a number of elongated slats extending along the width of the window and spaced apart vertically between a head rail and a bottom rail. The blind system typically comprises a lift cord that extends from the bottom rail through openings in the slats to the head rail and provides for lifting the bottom rail to raise and lower the slats. In a manual blind system, the end of the lift cord that is not attached to the bottom rail often hangs down from the head rail, such that a user may pull on the lift cord to raise and lower the slats. The blind system also typically comprises a tilt ladder that extends between the head rail and the bottom rail and operates to support and tilt the slats. Typical prior art manual blind systems include a rod that hangs from the head rail and may be rotated to adjust the tilt angle of the slats. The slats may be oriented substantially horizontal (i.e., perpendicular to the window) to allow sunlight to enter the space, and may be oriented substantially vertical (i.e., parallel to the window) to prevent sunlight from entering the space.

Some prior art venetian blind systems have included a motor to provide for lifting and tilting the slats. Such motorized venetian blind systems typically comprise a single motor coupled to a drive shaft that extends across the width of the head rail. The drive shaft may have at least two drums for winding up the lift cords when the shaft is rotated by the motor. The tilt ladders are typically coupled to the drive shaft through frictional force, such that when the slats have been fully tilted in one direction, the ends of the tilt ladder slip by the drive shaft as the drive shaft is rotated. To adjust the tilt of the slats, the drive shaft may be rotated in the reverse direction, such that the frictional force between the tilt ladder and the drive shaft causes the ends of the tilt ladder to rotate. Accordingly, the motor must be rotated in the reverse direction to adjust the tilt of the slats in typical prior art motorized venetian blind systems that comprise a single motor. <CIT> discloses a system for controlling motorized window coverings. The window coverings each have a processor, a network device and wireless transmitters enabling connection via a network. The network is controlled by one or more mobile devices which receive user input. The mobile devices wirelessly connect to a local area network (LAN) via a hub. One or more hubs are connected via the LAN. The window coverings are networked via a personal area network (PAN). The hubs convert the LAN protocol to the PAN protocol. Sensors send sensor data along with real time weather data to the processor. The processor uses this sensor data to update charts and schedules in memory, then sends commands to the controller based on these updated charts and schedules according to user defined and factory set parameters. The system includes both local and cloud based control. JPH084452A discloses to adjust a slat of a motor-driven Venetian blind to a tilt angle with which the max, limit viewing can be obtained in the state where the directly irradiated solar beam is shielded. A motor for tilting a slat and a driver for controlling the motor are installed on said motor-driven Venetian blind, and the solar beam incidence angle for the window surface at the time is calculated by a microcomputer.

The invention is defined by the blind system according to claim <NUM> and dependent claims <NUM>-<NUM> define further developments thereof.

As described herein, a blind system may be configured to control (e.g., automatically control) an amount of daylight entering a building to prevent direct sunlight from shining into the building, while attempting to maximize the amount of indirect sunlight shining into the building. The blind system may be mounted to cover a window located on a façade of the building. The blind system may comprise a headrail, a bottom bar, a plurality of slats spaced apart vertically between the headrail and the bottom bar, a lift cord extending from the headrail to the bottom bar to provide for raising and lowering the bottom bar, a tilt ladder extending from the headrail to the bottom bar and operable to support the slats and to tilt the slats, and a drive unit operably coupled to the tilt ladder for tilting the slats. The drive unit may be configured to selectively tilt the slats into each of a plurality of tilt positions that include at least: a view tilt position in which the slats are approximately horizontal, a slanted tilt position in which the slats are positioned to block direct sunlight from shining into the building, and a privacy tilt position in which the slats are approximately vertical. The drive unit may be configured to tilt the slats into one of the plurality of tilt positions at each of a plurality of event times according to a timeclock schedule. The plurality of event times may be determined from a predicted position of the sun, such that the drive unit is configured to tilt the slats to the slanted tilt position when the predicted position of the sun indicates that direct sunlight is incident on the façade, tilt the slats to the view tilt position when the predicted position of the sun indicates that no direct sunlight is incident on the façade, and tilt the slats to the privacy tilt position between sunset and sunrise.

In addition, a control device (e.g., a system controller) configured to control a blind system to control ( e.g., automatically control) an amount of daylight entering a building to prevent direct sunlight from shining into the building, while attempting to maximize the amount of indirect sunlight shining into the building. The control device may comprise a communication circuit configured to transmit message including commands for controlling the blind system, and a memory configured to store a timeclock schedule having event times and associated commands for tilting slats of the blind system into one of plurality of tilt positions that include at least: a view tilt position in which the slats are approximately horizontal, a slanted tilt position in which the slats are positioned to block direct sunlight from shining into the building, and a privacy tilt position in which the slats are approximately vertical. The control device may further comprise a control circuit configured to generate the timeclock schedule by determining the plurality of event times from a predicted position of the sun, and, based on the timeclock schedule, transmit, via the communication circuit, messages for controlling the blind system to tilt the slats to the slanted tilt position when the predicted position of the sun indicates that direct sunlight is incident on the façade, tilt the slats to the view tilt position when the predicted position of the sun indicates that no direct sunlight is incident on the façade, and tilt the slats to the privacy tilt position between sunset and sunrise.

Further, a method of configuring a blind system mounted on a façade of a building is also described herein. The method may comprise: (<NUM>) determining a compass direction of the façade using an electronic compass of a mobile device, the mobile device being positioned to face towards an interior surface of the façade; (<NUM>) displaying a top view image of the building on a visual display of the building; (<NUM>) displaying an indication of the compass direction determined from the electronic compass of the mobile device on the top view image of the building; (<NUM>) receiving an indication of an actual direction of the façade in response to a user input at the mobile device; (<NUM>) determining a compensation factor between the compass direction determined from the electronic compass and the actual direction determined from the user input; and (<NUM>) transmitting the actual direction of the façade to a control device for configuration of the blind system based on the actual direction of the façade.

<FIG> depicts a load control system <NUM> that includes load control devices for controlling electrical loads. As shown in <FIG>, the load control system <NUM> may be a load control environment, e.g., a room <NUM> in a building. The load control system <NUM> may include control devices that may be capable of controlling (e.g., directly controlling) an electrical load. The control devices may include control-source devices capable of communicating messages for controlling electrical loads and/or control-target devices capable of controlling electrical loads in response to instructions received in messages. The control-target devices may include load control devices capable of directly controlling the electrical loads in response to the instructions received in the messages from control-source devices.

Lighting control devices, such as the lighting control devices <NUM>, <NUM>, may be an example of control-target devices in the load control system <NUM>. The lighting control device <NUM> may be a dimmer, an electronic switch, a ballast, a light emitting diode (LED) driver, and/or the like. The lighting control device <NUM> may be capable of directly controlling an amount of power provided to lighting load <NUM>. The lighting control device <NUM> may be configured to wirelessly receive messages via the RF signals <NUM> (e.g., from associated control devices) and to control the lighting load <NUM> in response to the received messages.

The lighting control device <NUM> may be a wall-mounted dimmer, a wall-mounted switch, or other keypad device for controlling a lighting load <NUM>. The lighting control device <NUM> may be adapted to be mounted in a standard electrical wallbox. The lighting control device <NUM> may comprise a tabletop or plug-in load control device. The lighting control device <NUM> may comprise one or more buttons for controlling the lighting load <NUM>. The lighting control device <NUM> may include a toggle actuator. Actuations (e.g., successive actuations) of the toggle actuator may toggle (e.g., turn off and on) the lighting load <NUM>. The lighting control device <NUM> may include an intensity adjustment actuator (e.g., a rocker switch or intensity adjustment buttons). Actuations of an upper portion or a lower portion of the intensity adjustment actuator may respectively increase or decrease the amount of power delivered to the lighting load <NUM> and thus increase or decrease the intensity of the receptive lighting load from a minimum intensity (e.g., approximately <NUM>%) to a maximum intensity (e.g., approximately <NUM>%). The lighting control device <NUM> may comprise a plurality of visual indicators, e.g., light-emitting diodes (LEDs), which may be arranged in a linear array and are illuminated to provide feedback of the intensity of the lighting load <NUM>. Examples of wall-mounted dimmers are described in greater detail in <CIT>, entitled LIGHTING CONTROL DEVICE, and <CIT>, entitled WIRELESS LOAD CONTROL DEVICE, the entire disclosures of which are hereby incorporated by reference.

The lighting control device <NUM> may be configured to wirelessly receive messages via wireless signals, such as radio-frequency (RF) signals <NUM> (e.g., from associated control devices) using a first wireless protocol, e.g., a proprietary protocol, such as the CLEAR CONNECT protocol (e.g., the CLEAR CONNECT A and/or CLEAR CONNECT X protocols). The lighting control device <NUM> may be configured to control the lighting load <NUM> in response to the received messages. Examples of dimmer switches operable to transmit and receive messages is described in greater detail in commonly-assigned <CIT>, entitled COMMUNICATION PROTOCOL FOR A RADIO-FREQUENCY LOAD CONTROL SYSTEM, the entire disclosure of which is hereby incorporated by reference.

The load control system <NUM> may comprise a daylight control device, such as a motorized window treatment <NUM>. The motorized window treatment <NUM> may comprise a motor drive unit (not shown) configured to control a position of a covering material <NUM> to control an amount of daylight entering the load control environment <NUM>. For example, the covering material <NUM> may comprise a shade fabric wrapped around a roller tube, and the motor drive unit may be configured to rotate the roller tube to raise and lower the shade fabric. In addition, the motorized window treatment <NUM> may comprise a Venetian blind and the covering material <NUM> may comprise one or more slats. The motor drive unit of the Venetian blind may be configured to raise and lower a bottom bar of the Venetian blind to raise and lower the slats, and/or to tilt the slats to adjust the amount of daylight entering the load control environment <NUM>.

The load control system <NUM> may include one or more other control-target devices, such as a plug-in load control device <NUM> for directly controlling a floor lamp <NUM> a desk lamp, and/or other electrical loads that may be plugged into the plug-in load control device <NUM>, and/or a temperature control device <NUM> (e.g., thermostat) for directly controlling an heating, ventilation, and air-conditioning (HVAC) system. The load control system <NUM> may also, or alternatively, include an audio control device (e.g., a speaker system) and/or a video control device (e.g., a device capable of streaming video content).

The control-source devices in the load control system <NUM> may include a remote control device <NUM>, an occupancy sensor <NUM>, a daylight sensor <NUM>, and/or a window sensor <NUM>. The control-source devices may transmit messages to associated control-target devices for indirectly controlling an electrical load by transmitting messages, such as load control messages, to the control-target devices. The remote control device <NUM> may send messages for controlling control-target devices after actuation of one or more buttons on the remote control device <NUM>. One or more buttons may correspond to a preset (e.g., a scene) for controlling the lighting load <NUM>, the lighting load <NUM>, the lighting load <NUM>, or any combination thereof. The occupancy sensor <NUM> may send messages to control-target devices in response to an occupancy or vacancy condition (e.g., movement or lack of movement) that is sensed within its observable area. The daylight sensor <NUM> may send messages to control-target devices in response to the detection of an amount of light within its observable area. The window sensor <NUM> may send messages to control-target devices in response to a detected level of light received from outside of the load control system <NUM>. For example, the window sensor <NUM> may detect when sunlight is directly shining into the window sensor <NUM>, is reflected onto the window sensor <NUM>, and/or is blocked by external means, such as clouds or a building. The window sensor <NUM> may send messages indicating the detected light level and/or a condition indicating that the detected light level crossed a threshold (e.g., exceeded the threshold or fell below the threshold).

The control-source devices and/or the control-target devices may be in communication with a system controller <NUM>. The system controller <NUM> may be capable of transmitting messages to, and/or receiving messages from, control devices (e.g., control-source devices and/or control-target devices). The messages may include association information for associating control-source devices and control-target devices. The system controller <NUM> may facilitate communication of control information from control-source devices to associated control-target devices using the association information. For example, the system controller <NUM> may communicate with one or more control devices (e.g., control-source devices and/or control-target devices) using the radio frequency (RF) signals <NUM>. When the system controller <NUM> receives a message from a control device, the system controller may facilitate the communication of control instructions and/or other information to associated devices using the association information. The system controller <NUM> may also receive programming data (e.g., settings) for control devices and transmit messages for performing control according to the programming data. In addition, the system controller <NUM> may be configured to messages for controlling the control-target devices in response to a timeclock schedule. The system controller <NUM> may be configured to execute a timeclock (e.g., an astronomical timeclock) for determining a present time in order to determine when to transmit messages for controlling the control-target devices according to event times of the timeclock schedule.

The system controller <NUM> may also, or alternatively, communicate via wireless signals, such as RF signals <NUM>, using a second wireless protocol (e.g., a standard protocol, such as WI-FI, BLUETOOTH, etc.). For example, the system controller <NUM> may communicate with one or more network devices, such as a network device <NUM> (e.g., a mobile device). The network device <NUM> may include a personal computer (PC), a laptop, a tablet, a smart phone, or equivalent device via the RF signals <NUM>. The system controller <NUM> may be a gateway device, a network bridge device, an access point, and/or the like. Examples of load control systems having system controllers <NUM> are described in greater detail in commonly-assigned <CIT>, entitled LOAD CONTROL SYSTEM HAVING INDEPENDENTLY-CONTROLLED UNITS RESPONSIVE TO A BROADCAST CONTROLLER, and <CIT>, entitled WIRELESS LOAD CONTROL SYSTEM, the entire disclosures of which are hereby incorporated by reference.

The control-source devices in load control system <NUM> may be associated with the control-target devices using various association techniques. For example, in an association procedure, the control-source devices may be associated with the control-target devices by the user <NUM> actuating a button on the control-source device and/or the control-target device. The actuation of the button on the control-source device and/or the control-target device may place the control-source device and/or the control-target device in an association mode, for example, for being associated with one another. In the association mode, the control-source device may transmit an association message to the control-target device. The association message from a control-source device may include a unique identifier of the control-source device. The control-target device may locally store the unique identifier of the control-source, such that the control-target device may be capable of recognizing messages (e.g., subsequent messages) from the control-source device that may include load control instructions. The control-target device may be capable of responding to the messages from the associated control-source device by controlling a corresponding electrical load according to the load control instructions received in the messages. Examples of load control systems are described in greater detail in commonly-assigned <CIT>, entitled METHOD AND APPARATUS FOR CONTROLLING AND DETERMINING THE STATUS OF ELECTRICAL DEVICES FROM REMOTE LOCATIONS, and <CIT>, entitled LOAD CONTROL SYSTEM HAVING AN ENERGY SAVINGS MODE, the entire disclosures of which are hereby incorporated by reference.

The load control system <NUM> may be designed and/or configured using a design software, e.g., a graphical user interface (GUI) software and/or a configuration application, running on the network device <NUM> (e.g., such as a personal computer (PC), a laptop, a tablet, a smart phone, or equivalent device having a visual display). Using the design software, a user <NUM> may select the control devices (e.g., the control devices of the load control system, such as control-source devices and/or control target devices) and/or adjust programming data for configuring the system. For example, the user <NUM> may be a homeowner, who may be using the network device <NUM> to design and/or configure the load control system <NUM> in a house in which the homeowner lives. In addition, the user <NUM> may be a worker, such as an electrical contractor, who may be hired by the homeowner to design and/or configured the load control system <NUM> in a house in which the homeowner lives. The design software running on the network device <NUM> may be used to configure the motorized window treatments <NUM> (e.g., as will be described in greater detail below). Examples of configuration procedures for load control systems are described in greater detail in commonly-assigned <CIT>, entitled HANDHELD PROGRAMMER FOR LIGHTING CONTROL SYSTEM, and <CIT>, entitled COMMISSIONING LOAD CONTROL SYSTEMS, the entire disclosures of which are hereby incorporated by reference.

The functionality of the load control system <NUM> may be automatically configured by the design software in response to types of control devices (e.g., lighting control devices, remote control devices, etc.) that are added to the load control system during the configuration procedure. The design software may automatically generate the programming data (e.g., including one or more control features) that defines the operation of the load control system <NUM> based on the location and/or load type of the control devices that have been added to the load control system. After the control devices have been added to the load control system <NUM>, the design software may be configured to review with the user of the design software the details of the control features that were automatically programmed. The user may confirm that the automatically programmed functionality is desired and/or manually edit the control features. Once functionality of the control features is confirmed and/or edited, portions of the programming database may be transmitted to the control devices of the load control system <NUM> for use during normal operation of the load control system. For example, the full programming database may be transferred from the network device <NUM> to the system controller <NUM> and the system controller <NUM> may transmit the portions of the programming database to each of the control devices. As soon as the system controller <NUM> begins to transmit the portions of the programming database to the control devices, the user may be able to use the network device <NUM> to control the operation of the load control system <NUM>. For example, since the entire programming database is stored on the system controller <NUM>, the user may select a command using the network device <NUM> and the network device <NUM> may transmit a message including the command to the system controller <NUM>, which may in turn transmit commands to the appropriate control devices of the load control system <NUM> (e.g., based on the programming data base stored on the system controller. The programming data that is transferred to the control devices may be used when the control devices transmit commands directly to load control devices. As soon as a load control device has its portion of the database, the load control device may be controlled by the control devices (e.g., remote control devices and other control devices in the system).

The design software executing at the system controller <NUM> may automatically update the programming data after the programming data has been transmitted to the control devices and the load control system <NUM> is fully functional (e.g., during normal operation). When one or more control devices (e.g., lighting control devices and/or remote control devices) are added to the load control system <NUM>, the design software executing at the system controller <NUM> may automatically update the control features associated with the added control devices and/or add control features. For example, if the user uses the design software to add a lighting control device to the load control system <NUM> via the network device <NUM>, the design software executing at the system controller <NUM> may automatically add the lighting control device to various scenes and/or schedules. When automatically updating the control features after the programming data is transmitted to the control devices, the design software may not overwrite manual changes previously made by the user to the control features. This may ensure that a user's manual changes are maintained after subsequent automatic updates.

<FIG> is a perspective view of an example motorized window treatment, e.g., a Venetian blind system <NUM>, which may be deployed as the motorized window treatment <NUM> of the load control system <NUM>. <FIG> are side view of blind system <NUM> of <FIG> shown mounted in front of a window <NUM> on a façade <NUM> of a building. The blind system <NUM> may include a covering material, e.g., a plurality of flat slats <NUM>, disposed between a headrail <NUM> and a bottom bar <NUM> (e.g., a bottom rail). The blind system <NUM> may be configured to be mounted in front of the window <NUM>. The blind system <NUM> may include mounting brackets (not shown) coupled to the top of the headrail <NUM> for mounting the blind system <NUM> to a ceiling above the window <NUM>, and side panels (not shown) that may allow for alternatively mounting the blind system <NUM> to walls surrounding the window <NUM>. The blind system <NUM> may also comprise a valance <NUM> located in front of the headrail <NUM>.

The blind system <NUM> may also comprise a drive unit <NUM> (e.g., a motor drive unit or blind drive unit) located in the headrail <NUM> for adjusting the covering material of the blind system <NUM> to control the amount of daylight entering a space. For example, the drive unit <NUM> may comprise a motor (not shown) configured to be operated to raise and lower the bottom bar <NUM> and/or tilt the slats <NUM> to control the amount of daylight entering the space as will be described in greater detail below. In one embodiment, the drive unit <NUM> may be configured to independently control a position of the bottom bar <NUM> and a tilt angle of the slats <NUM>, so as to control the amount of daylight entering the space in which the blind system <NUM> is installed. In other embodiments, the drive unit <NUM> may be configured to only control one or the other of the position of the bottom bar <NUM> or the tilt angle of the slats <NUM>. For example, in various embodiments, the drive unit <NUM> may be configured to only control the tilt angle of the slats <NUM>. In such embodiments, the position of the bottom bar <NUM> may be adjustable manually by a user. The drive unit <NUM> may be configured to receive a supply voltage, e.g., a direct-current (DC) supply voltage from a DC power supply, such as, for example, a battery (e.g., an alkaline battery, a nickel cadmium battery, a nickel metal hydride battery, a lithium ion battery, etc.). The drive unit <NUM> may include a wireless communication circuit, e.g., such as a radio-frequency (RF) receiver or transceiver, for receiving wireless signals (e.g., RF signals). The drive unit <NUM> may be configured to raise and lower the bottom bar <NUM> and/or tilt the slats <NUM> to control the amount of daylight entering a space in response to a command received via the wireless signals. The blind system <NUM> may also comprise one or more batteries (e.g., alkaline batteries, nickel cadmium batteries, nickel metal hydride batteries, lithium ion batteries, etc.) located inside or at least partly inside of the headrail <NUM> for powering the drive unit <NUM>. The batteries may be, for example, D-cell or AA batteries.

The blind system <NUM> may comprise two lift cords <NUM> positioned at the left and right ends of the slats <NUM> to provide for lifting the bottom bar <NUM>. The blind system <NUM> may further comprise two tilt ladders <NUM> positioned at the left and right ends of the slats <NUM> to provide for tilting the slats <NUM>. The motor of the drive unit <NUM> may be operatively coupled to the tilt ladder for tilting the slats. The slats <NUM> may extend across the width of the window <NUM> that the blind system <NUM> (e.g., such that the blind system <NUM> may be capable of covering the window) and the slats <NUM> may be spaced apart equally between the headrail <NUM> and the bottom bar <NUM>. Alternatively, the slats <NUM> may comprise curved slats rather than flat slats. The lift cords <NUM> may each extend from the headrail <NUM> to the bottom bar <NUM> through respective lift cord openings <NUM> in each of the slats <NUM>. In embodiments that include motorized raising and lowering of the bottom bar <NUM>, the drive unit <NUM> may be configured to wind and unwind the lift cords <NUM> to respectively raise and lower the bottom bar <NUM> between a fully-raised position and a fully-lowered position. In such embodiments, as the drive unit <NUM> raises the bottom bar <NUM>, the slats <NUM> may each contact the bottom bar one-by-one and may be raised up with the bottom bar. In addition, the drive unit <NUM> may control the bottom bar <NUM> to a specific intermediate position between the fully-raised position and the fully-lowered position.

The tilt ladders <NUM> may each have a front band <NUM> (e.g., a front ribbon) and a rear band <NUM> (e.g., a rear ribbon) that extend parallel to each other from the headrail <NUM> to the bottom bar <NUM> adjacent to the lift cords <NUM>. The front band <NUM> of the tilt ladders <NUM> may typically be positioned in front of the lift cords <NUM>. Each tilt ladder <NUM> may also comprise a plurality of rungs (not shown) (e.g., bands or ribbons) that extend from the front band <NUM> to the rear band <NUM> between each pair of adjacent slats <NUM> of the blind system <NUM> to thus form a ladder. Accordingly, each of the slats <NUM> may rest on one of the rungs in each of the tilt ladders <NUM>, such that the slats may be equally spaced apart vertically when the bottom bar <NUM> is in the fully-lowered position. In embodiments in which the position of the bottom bar <NUM> is controlled by the drive unit <NUM>, the front and rear bands <NUM>, <NUM> may be coupled to the drive unit <NUM> in the headrail <NUM>. As the drive unit <NUM> winds up the lift cord <NUM> to raise the bottom bar <NUM>, the portions of the tilt ladders <NUM> between adjacent rungs may become slack as the raising bottom bar and accumulating slats <NUM> meet the next slat. The drive unit <NUM> may be configured to tilt the slats <NUM> by vertically moving the front and rear bands <NUM>, <NUM> with respect to each other, such that the rungs, and thus the slats <NUM>, are tilted at an angle with respect to the front and rear bands (e.g., a tilt angle θBLIND). Alternatively, the front and rear bands <NUM>, <NUM> and the rungs of the tilt ladders <NUM> could comprise cords.

As shown in <FIG>, the drive unit <NUM> may tilt the slats <NUM> of the blind system <NUM> into different tilt positions. For example, the drive unit <NUM> may be configured to tilt the slats <NUM> into a view tilt position as shown in <FIG>, a slanted tilt position (e.g., a direct sunlight blocking position or "fade-fighter" tilt position) as shown in <FIG>, and/or a privacy tilt position as shown in <FIG>. The drive unit <NUM> may be configured to control the slats <NUM> to each be in a horizontal orientation (e.g., in a horizontal plane) in the view tilt position to allow daylight (e.g., indirect sunlight) to enter the space in which the blind system <NUM> and/or to allow an occupant of the space to have a view outside of the window. For example, the view tilt position may be considered a <NUM>% tilt position of the blind system <NUM>. The drive unit <NUM> may be configured to tilt the slats <NUM> approximately <NUM>° towards the rear of the blind system <NUM> (e.g., towards the window) into the slanted tilt position to block direct sunlight from shining into the space while still allowing indirect sunlight to enter the space, although it will be appreciated that the drive unit <NUM> may be configured to tilt (e.g., continuously, variably, and reversibly tilt) the slats <NUM> to any angle between <NUM>° and <NUM>°, such as, for example, <NUM>°, <NUM>°, <NUM>°, etc. The slanted tilt position may range from approximately a <NUM>% tilt position to a <NUM>% tilt position of the blind system <NUM> where, for example, a <NUM>° tilt angle may be considered a <NUM>% tilt position. For example, the slanted tilt position may be configured and/or adjusted using the design software running on a network device (e.g., the network device <NUM>). In addition, the drive unit <NUM> may be configured to tilt the slats <NUM> approximately <NUM>° from the horizontal plane towards the rear of the blind system <NUM> into the privacy tilt position as shown in <FIG> to block direct and indirect sunlight from entering the space and/or to block view through the window to provide privacy for the occupant of the space. For example, the privacy tilt position may be considered a <NUM>% tilt position of the blind system <NUM>. Further, the drive unit <NUM> may be configured to tilt the slats approximately <NUM>° from the horizontal plane towards the front of the blind system <NUM> when in the privacy tilt position (e.g., a <NUM>% tilt position of the blind system <NUM>).

The drive unit <NUM> of the blind system <NUM> may be configured to control (e.g., automatically control) the tilt position of the blind system <NUM> (e.g., the slats <NUM>). For example, when direct sunlight may be incident on the façade <NUM> in which the window <NUM> is located, the drive unit <NUM> of the blind system <NUM> may be configured to automatically control the tilt position of the slats <NUM> to the slanted tilt position to block direct sunlight from shining into the space. When direct sunlight may not be incident on the façade <NUM>, the drive unit <NUM> of the blind system <NUM> may be configured to control (e.g., automatically control) the tilt position of the slats <NUM> to the view tilt position to allow indirect sunlight to enter the space and/or to allow the user of the space to have a view outside of the window. For example, the drive unit <NUM> may be configured to delay automatic adjustment of the tilt position for a predetermined amount of time (e.g., one hour) after an adjustment of the tilt position in response to command received via the wireless signals. In addition, the drive unit <NUM> of the blind system <NUM> may be configured to control the tilt position of the slats <NUM> to the privacy tilt position at times relative to sunrise and sunset times for the upcoming day. For example, the drive unit <NUM> of the blind system <NUM> may be configured to control the tilt position of the slats <NUM> to the privacy tilt position between sunset and sunrise. Further, the drive unit <NUM> of the blind system <NUM> may be configured to control the tilt position of the slats <NUM> to the privacy tilt position at predetermined times of the day that may be specified by the user of the space (e.g., during nighttime hours).

The drive unit <NUM> of the blind system <NUM> may be configured to control (e.g., automatically control) the tilt position of the slats <NUM> according to a predetermined timeclock schedule. The timeclock schedule may be generated by a system controller of the load control system of the blind system <NUM> (e.g., the system controller <NUM>). The system controller may be configured to generate a timeclock schedule each day (e.g., during the nighttime hours while the slats <NUM> are in the privacy tilt position). The system controller may be configured to store the timeclock schedule and transmit commands to the drive unit <NUM> of the blind system <NUM> for tilting the slats <NUM> to the appropriate tilt positions according to the timeclock schedule. In addition, the system controller may transmit the timeclock schedule to the drive unit <NUM> of the blind system <NUM> for use during the coming day. The drive unit <NUM> of the blind system <NUM> may be configured to store the timeclock schedule in memory (e.g., a new timeclock schedule each day) and tilt the slats <NUM> to a plurality of tilt positions at respective event times of the timeclock schedule during the day (e.g., the drive unit <NUM> may be configured to execute a timeclock). Further, the drive unit <NUM> of the blind system <NUM> may be configured to generate the timeclock schedule each day itself. Additionally and/or alternatively, the drive unit <NUM> of the blind system <NUM> may be configured to generate timeclock schedules for multiple upcoming days and store the timeclock schedules in the memory.

The system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to calculate a predicted position of the sun at a plurality of discrete times in a day in order to determine when and how to generate the timeclock events of the timeclock schedule for the day. The position of the sun in the sky may be defined by a solar altitude angle at and a solar azimuth angle as. <FIG> is a perspective view of an example building <NUM> on which the window <NUM> of the façade <NUM> may be located. The solar altitude angle at may be the angle between a line <NUM> directed towards the sun and a line <NUM> from the façade <NUM> to the sun projected on the ground (e.g., a line directed towards the horizon at the position of the building <NUM>). The solar altitude angle at may also be thought of as the angle of incidence of the sun's rays on a horizontal surface. The solar azimuth angle as may be the angle formed by a line <NUM> from the façade <NUM> to the south and the line <NUM> from the observer to the sun projected on the ground.

The system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to calculate the solar altitude angle at and the solar azimuth angle as as functions of the date (e.g., a Julian date) and time (e.g., the standard time ts), as well as the position (e.g., longitude λ and latitude Φ) of the building <NUM> in which the window <NUM> is located. For example, the system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to calculate the solar altitude angle at and the solar azimuth angle as using the following equations. The difference in a solar time tsolar (e.g., a time as given by a sundial) and a standard time ts (e.g., a time as given by a clock) due to the obliquity of the Earth's axis of rotation may be defined by an equation of time ET. The equation of time ET can be determined as a function of the present Julian date J using, for example, the equation: <MAT> where A = [ 4π · (J - <NUM>) ] / <NUM> and B = [ 2π · (J- <NUM>) ] / <NUM>. The Julian date J may be a decimal number representing the present day in the year. For example, the Julian date J may equal one for January <NUM>, two for January <NUM>, three for January <NUM>, and so on. The solar time tsolar may be calculated as a function of the standard time ts, the equation of time ET, a standard meridian SM of the time zone of the location of the building, and the longitude λ, for example, using the equation: <MAT> The standard meridian SM may be determined from the time zone of the location of the building <NUM>. Each time zone may have a unique standard meridian, which may define a particular line of latitude within the time zone. There may be approximately <NUM>° between the standard meridians of adjacent time zones.

The solar altitude angle as and the solar azimuth angle az may be determined from a solar declination δ. The solar declination δ may define an angle of incidence of the rays of the sun on the equatorial plane of the Earth. The solar declination δ may be determined using, for example, the equation: <MAT> The solar altitude angle at at the standard time ts may be calculated as a function of the solar time tsolar, the solar declination δ, and the local latitude Φ using, for example, the equation: <MAT> The solar azimuth angle as at the standard time ts may be calculated as a function of the solar time tsolar, the solar declination δ, and the local latitude Φ using, for example, the equation: <MAT> where C = -[ cos(Φ) · sin(δ) + sin(Φ) · cos(δ) · cos(π · tsolar / <NUM>) ].

The system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to determine if the sun is in a position such that sunlight is directly incident on the façade <NUM> by calculating a position metric of the sun. For example, the system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to determine if the sun is directly shining on the façade <NUM> by calculating a profile angle ap of the sun at the façade <NUM>. The profile angle ap of the sun may be calculated using the solar altitude angle at and the solar azimuth angle as of the sun and an elevation angle ae (e.g., a façade angle) of the façade <NUM> on which the window <NUM> is located. The elevation angle ae may be the angle between a line <NUM> that is normal to the façade <NUM> and the line <NUM> that is directed south. The profile angle ap may define an apparent altitude of the sun relative to the façade <NUM>. The profile angle ap may be the angle between a line <NUM> that is normal to the façade <NUM> and a line <NUM> that is the projection of the line <NUM> directed towards the sun onto a vertical plane through the line <NUM> that is normal to the façade <NUM>. The profile angle ap may be calculated as a function of the solar altitude angle at and a solar elevation azimuth angle az using, for example, the equation: <MAT> where the solar elevation azimuth angle az is the difference between the solar azimuth angle as and the elevation angle ae of the façade <NUM> (e.g., az = as - ae). When the profile angle ap is between <NUM>° and <NUM>°, the sun may be in a position to shine on the façade <NUM> (e.g., on a sunny day). When the profile angle ap is less than <NUM>°, the sun may be past the horizon (e.g., before sunrise and/or after sunset). When the profile angle ap is greater than <NUM>°, the sun may have passed over the top of the building <NUM>.

In addition, the system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to determine if the sun is directly shining on the façade <NUM> by calculating the solar azimuth angle as of the sun. The solar azimuth angle as may be calculated as a function of the solar time tsolar, the solar declination δ, and the local latitude Φ using, for example, Equation <NUM> as shown above. The system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to determine solar azimuth angle limits as1, as2 for the façade <NUM> based on the elevation angle ae of the façade <NUM>. When the solar azimuth angle as is between solar azimuth angle limits as1, as2 for the façade <NUM>, the sun may be in a position to shine on the façade <NUM> (e.g., on a sunny day).

The system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to calculate the position metric (e.g., the profile angle ap and/or the solar azimuth angle as) of the sun on the façade <NUM> to determine the times at which direct sunlight may begin being incident on the façade <NUM> and/or the times at which direct sunlight may cease being incident on the façade during the upcoming day. The system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to generate the timeclock events of the timeclock schedule to cause the blind system <NUM> to tilt to the slanted tilt position when the sun is directly shining on the façade <NUM>, and to cause the blind system <NUM> to tilt to the view tilt position when the sun is not directly shining on the façade <NUM> during the upcoming day. For example, the system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to determine one or more fade-fighter tilt times tFF at which to control the blind system <NUM> to the slanted tilt position (e.g., the fade-fighter tilt position), and one or more view tilt times tVIEW at which to the control the blind system <NUM> to the view tilt position during the upcoming day. The system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to generate the timeclock events of the timeclock schedule to cause the blind system <NUM> to tilt to the privacy tilt position starting at or shortly after sunset and ending at sunrise. For example, the system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to determine a privacy tilt position time tPRIV at which to control the motorized blinds to the privacy tilt position based on a sunset time tSUNSET for the upcoming day. In addition, the system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to generate the timeclock events of the timeclock schedule to cause the blind system <NUM> to tilt to the privacy tilt position between predetermined times that may be preconfigured by a user of the blind system <NUM>. For example, the user may override one or more preconfigured tilt positions of the blind system <NUM> (e.g., tilt positions that are based on the sunlight measurements).

The system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to determine the elevation angle ae of the façade <NUM> on which the blind system <NUM> is mounted during a configuration procedure of the blind system <NUM>. During the configuration procedure, the blind system <NUM> may be associated with one of the four different cardinal directions (e.g., north, east, south, and west) or the four different ordinal directions (e.g., north-east, south-east, south-west, and north-west). For example, the blind system <NUM> may be associated with the one of the eight different cardinal or ordinal directions that is closest to the actual elevation angle ae of the façade <NUM>. The elevation angle ae of the façade <NUM> may be estimated during the configuration procedure using an electronic compass of a mobile device (e.g., the network device <NUM>) as will be described in greater detail below with reference to <FIG>.

Since the blind system <NUM> may be associated with (e.g., only associated with) one of the eight different cardinal or ordinal directions, the system controller and/or the drive unit <NUM> of the blind system <NUM> may consider a range of possible elevation angles ae of the façade <NUM> when determining the event times of the timeclock schedule. For example, the elevation angle ae of the façade <NUM> may range by about <NUM>° for each of the eight different cardinal or ordinal directions. Each of the eight different cardinal or ordinal directions may be characterized by a center elevation angles ae0 and two endpoint elevation angles ae1, ae2 as shown in Table <NUM>.

The system controller and/or the drive unit <NUM> of the blind system <NUM> may recall the first and second endpoint elevation angles ae1, ae2 and may determine the event times for the timeclock schedule for the upcoming day based on the first and second endpoint elevation angles ae1, ae2. Although the example embodiment of Table <NUM> includes non-overlapping ranges of endpoint elevation angles ae1, ae2, it will be appreciated that the first and second endpoint elevation angles ae1, ae2 may be selected such that adjacent cardinal and ordinal directions include partially overlapping ranges of elevation angles between the first endpoint elevation angle ae1 and the second endpoint elevation angle ae2.

The system controller may be configured to generate timeclock schedules for a plurality (e.g., all) of the blind systems (e.g., motorized blinds) installed in the building <NUM>. For example, the system controller may be configured to generate timeclock schedules (e.g., individual timeclock schedules) with different event times depending upon which façade of the building <NUM> on which each of the plurality of blind systems are located. The system controller may be configured to combine the timeclock schedules together to generate a system timeclock schedule for the entire building <NUM>. The system controller may be configured to transmit the individual timeclock schedules to the blind systems on the respective façades of the building and/or transmit the system timeclock schedule to all of the blind systems in the building. Additionally and/or alternatively, the system controller may be configured to transmit commands for tilting the slats (e.g., based on the individual timeclock schedules) to each of the blind systems on the respective façades of the building. In addition, as previously mentioned, the drive units of each of the blind systems in the building may be configured to generate a respective individual timeclock schedule for controlling itself during the upcoming day.

The system controller and/or the drive unit <NUM> of the blind system <NUM> may be configured to associate one of the four different cardinal directions or the four different ordinal directions and a geographic region to determine different event times for the timeclock schedule. For example, a first façade located at a first set of geographic coordinates (e.g., global positioning system (GPS)) and facing (e.g., the façade may be associated with) one of the four different cardinal directions or the four different ordinal directions, the time periods during which the sun may be directly on the first façade can be determined. The system controller and/or the drive unit <NUM> of the blind system <NUM> may generate a timeclock schedule for each blind system on the first façade and facing the same one of the four different cardinal directions or the four different ordinal directions.

<FIG> shows an example system timeclock schedule <NUM> for a particular day of the year for a building located at a particular location. The blind systems of the building may be located on the North, East, South, and West façades of the building. The event times may be calculated based on when direct sun may be shining on the different façades. The blinds on the different façades may be controlled to the slanted, view, and privacy tilt positions at the different event times. Each column underneath the different façades may represent an individual timeclock schedule that may be transmitted to only the blind systems located on that façade.

<FIG> are screenshots <NUM>-<NUM> of a configuration application running on a mobile device (e.g., the network device <NUM>) that may be used to configure a motorized blind (e.g., the blind system <NUM>). <FIG> is a flowchart of an example configuration procedure <NUM> for configuring a motorized blind (e.g., using a mobile device running the configuration application that displays the screenshots <NUM>-<NUM> shown in <FIG>). For example, the configuration procedure <NUM> may be completed by an installer of the motorized blind using the mobile device. The mobile device may be configured to communicate with a system controller (e.g., the system controller <NUM> of the load control system <NUM>) and/or directly with the motorized blind. The configuration procedure <NUM> may start at <NUM>. At <NUM>, the installer may open the configuration application running on the mobile device. At <NUM>, the installer may select a control device (e.g., the motorized blind) to configure and/or assign to the load control system and/or other control device. For example, the installer may choose a particular control device (e.g., a wood blind) on the configuration application as shown in the screenshot <NUM> in <FIG>. If a motorized blind is selected at <NUM>, the configuration application may prompt the installer to actuate (e.g., press and hold) a button on a motor drive unit of the motorized blind at <NUM> as shown in the screenshot <NUM> of <FIG>. In response to the actuation of the button on the motorized blind, the system controller may be configured to assign the motorized blind to the load control system and/or another control device (e.g., an input device) of the load control system.

At <NUM>, the installer may use the configuration application running on the mobile device to configure a facing direction of the façade on which the motorized blind is located (e.g., a line normal to the façade, such as the line <NUM> normal to the façade <NUM> shown in <FIG>). For example, the configuration application may prompt the installer to orient (e.g., point) the mobile device (e.g., smart phone) towards the motorized blind that is being configured as shown in the screenshot <NUM> of <FIG>. The configuration application may display (e.g., in response to orienting the mobile device towards the motorized blind) a top view image <NUM> of the building (e.g., house) in which the motorized blind is installed and in which the installer is standing as shown in the screenshot <NUM> shown in <FIG>. The configuration application may also display a location indicator <NUM> (e.g., a dot) over the image <NUM> of the building. The location indicator <NUM> may indicate the location of the installer. The location indicator <NUM> may be surrounded by a compass indicator <NUM>, which may also be overlaid on the image <NUM> of the building. The compass indicator <NUM> may be split into eight different segments to indicate the four different cardinal directions (e.g., north, east, south, and west) and the four different ordinal directions (e.g., north-east, south-east, south-west, and north-west) from the location of the building. The compass indicator <NUM> may indicate the direction that the mobile device is facing (e.g., directed) as determined by an internal electronic compass of the mobile device. The mobile device may be configured to set an orientation of the motorized blind in response to the direction indicated by the electronic compass.

Since the electronic compass of the mobile device may not be accurate (e.g., particularly when located inside of a building), the installer may be able to actuate one of the segments of the compass indicator <NUM> to indicate the actual direction in which the mobile device is facing. For example, the installer may press one of the segments of the compass indicator <NUM> to select the direction corresponding to that segment. The mobile device may update the orientation of the motorized blind in response to the selected segment of the compass indicator <NUM>. The orientation of the motorized blind (e.g., the facing direction of the façade) may be stored in the mobile device and/or the system controller for use when controlling (e.g., automatically controlling) the motorized blind.

At <NUM>, the installer may use the configuration application to assign a location (e.g., room) of the motorized blind being configured as shown in the screenshot <NUM> of <FIG>. At <NUM>, the installer may use the configuration application to enter a name of the motorized blind being configured as shown in the screenshot <NUM> of <FIG>. If there are more control devices to configure at <NUM>, the installer may select an "add another device" button on the configuration application as shown in the screenshot <NUM> of <FIG>, and the configuration procedure <NUM> may loop around to allow another control device to be selected for configuration at <NUM>. When a control device other than a motorized blind (e.g., a dimmer switch, an electronic switch, a temperature control device, a remote control device, an occupancy sensor, a daylight sensor, etc.) is selected at <NUM>, the installer may configure the other control device in an appropriate manner at <NUM>. For example, the installer may actuate a button on the other control device to assign the control device to the load control system (e.g., as in <NUM>), assign a location of the control device (e.g., as in <NUM>), and/or enter a name of the control device (e.g., as in <NUM>). When there are no more control devices to configure at <NUM>, the mobile device and/or system controller may store the configuration data established by the configuration procedure <NUM> and close the configuration application at <NUM>, before the configuration procedure <NUM> exits.

<FIG> is a flowchart of an example orientation configuration procedure <NUM> that may be executed to configure an orientation of a motorized blind (e.g., the blind system <NUM>). For example, the orientation configuration procedure <NUM> may be executed by a mobile device (e.g., the network device <NUM>) as part of a configuration procedure for the motorized blind (e.g., at <NUM> of the configuration procedure <NUM>). The orientation configuration procedure <NUM> may be executed to configure the orientations of all motorized blinds on a single façade (e.g., to configure the facing direction of the façade). The orientation configuration procedure <NUM> may be executed by the mobile device at <NUM>. At <NUM>, the mobile device may determine the direction of the mobile device using an electronic compass of the mobile device. For example, the mobile device may determine the direction in units of degrees from true north at <NUM>. At <NUM>, the mobile device may display a top view image of the building in which the mobile device is located with a compass indicator overlaid over top of the image (e.g., as shown in <FIG>). The top view image of the building allows the mobile device to receive a selection of a specific façade for the building and may allow a user to manually select or correct the direction associated with the façade. If the determined direction is not correct at <NUM>, the mobile device may receive an updated direction at <NUM> (e.g., as set by an installer via the configuration application). At <NUM>, the mobile device may determine a compass compensation factor based on the updated direction. For example, the compass compensation factor may be the difference between the updated direction and the direction as determined by the electronic compass. The mobile device may use the compass compensation factor when determining the direction of the mobile device using an electronic compass for other façades of the building. At <NUM>, the mobile device may update the compass indicator on the image of the building to indicate the updated direction.

When the direction is correct at <NUM>, the mobile device may assign the façade to one of a plurality of predetermined directions based on the measured or corrected compass direction. For example, the predetermined directions may include cardinal and ordinal directions and the mobile device may determine the closest cardinal direction or ordinal direction to the determined orientation of the motorized blind (e.g., the facing direction of the façade) at <NUM>. As another example, the predetermined directions may include the cardinal directions, the ordinal directions, half-wind directions (NNE, ENE, ESE, SSE, SSW, WSW, WNW, and NNW), quarter-wind directions, and/or custom defined directions. At <NUM>, the mobile device may assign additional blind systems <NUM> to the façade and assign the same one of the plurality of predetermined directions to each blind system on the façade. At <NUM>, the mobile device may then store the determined direction in memory as the orientation of one or the motorized blinds on the present façade, and the orientation configuration procedure <NUM> may exit.

<FIG> is a flowchart of an example orientation configuration procedure <NUM> that may be executed to configure an orientation of a motorized blind (e.g., the blind system <NUM>). For example, the orientation configuration procedure <NUM> may be executed by a mobile device (e.g., the network device <NUM>) as part of a configuration procedure for the motorized blind (e.g., at <NUM> of the configuration procedure <NUM>). The orientation configuration procedure <NUM> may be executed to configure the orientations of all motorized blinds on a single façade (e.g., to configure the facing direction of the façade). The orientation configuration procedure <NUM> is similar to the orientation procedure <NUM> discussed above, and similar description is not repeated herein. At <NUM>, the mobile device may determine the location and /or direction of the mobile device using an electronic compass and/or a global positioning system (GPS) receiver of the mobile device. For example, the mobile device may determine the direction in units of degrees from true north at <NUM>. At <NUM>, the mobile device may record movement from a first point along the façade (e.g., a first corner of the façade) to a second point along the façade (e.g., a second corner of the façade). For example, the mobile device may be transported from the first point along the façade to the second point along the façade by a user. At <NUM>, the direction of the façade may be determined based on the location and/or direction determined by the mobile device before and during movement of the mobile device on the façade. As discussed above, if the determined direction is not correct, the mobile device may receive an updated direction at <NUM>, determine a compass compensation factor based on the updated direction at <NUM>, and update direction of the façade at <NUM>. The mobile device may use the compass compensation factor when determining the direction of the mobile device using an electronic compass for other façades of the building. Similarly, as discussed above, the orientation configuration procedure <NUM> determines the closest one of the predetermined directions at <NUM>, may assign additional blind systems to the façade at <NUM>, and stores the direction selected from the plurality of directions for each blind system on the façade.

<FIG> is a flowchart of an example timeclock schedule configuration procedure <NUM> that may be executed to configure a timeclock schedule for controlling (e.g., automatically controlling) tilt positions of one or more motorized blinds (e.g., the motorized window treatments <NUM> and/or the blind system <NUM>). The timeclock schedule configuration procedure <NUM> may be executed by a control device (e.g., the system controller <NUM>) of a load control system that includes the motorized blinds. For example, the timeclock schedule configuration procedure <NUM> may be executed periodically at <NUM>, e.g., once a day to configure timeclock schedules for the motorized blinds for the coming day. At <NUM>, the control device may start with the north façade for configuring timeclock schedules for motorized blinds that may be located on the north façade of the building in which the load control system is installed. If there are blinds located on the present façade (e.g., the north façade) at <NUM>, the control device may configure a timeclock schedule for the blinds on the present façade at <NUM>. For example, the control device may set the events of the timeclock schedule to control the tilt positions of the motorized blinds to maximize indirect sunlight entering the space while preventing direct sunlight from entering the space (e.g., as will be described below with reference to <FIG> and <FIG>). If there are no blinds located on the present façade at <NUM>, the control device may not configure timeclock schedules. If there are more façades on the building at <NUM>, the control device may move to the next façade at <NUM>. The control device may again determine, at <NUM>, if the next façade has blinds. If the next façade has blinds, the control device may configure timeclock schedules for the next façade at <NUM> if there are motorized blinds on the next façade at <NUM>. When there are no more façades on the building at <NUM>, the control device may transmit (e.g., wirelessly transmit) the timeclock schedules to each of the respective motorized blinds (e.g., corresponding to the respective façade) at <NUM>, before the timeclock schedule configuration procedure <NUM> exits. The motorized blinds may each store the respective timeclock schedule and execute respective events of the respective timeclock schedules at the pre-configured times over the coming day.

<FIG> is a flowchart of an example façade timeclock schedule configuration procedure <NUM>. The example façade timeclock schedule configuration procedure <NUM> may be executed to configure a timeclock schedule for controlling (e.g., automatically controlling) tilt positions of one or more motorized blinds (e.g., the motorized window treatments <NUM> and/or the blind system <NUM>) on a particular façade of a building in which the motorized blinds are located. The façade timeclock schedule configuration procedure <NUM> may be executed by a control device (e.g., the system controller <NUM>) of a load control system that includes the motorized blinds. The façade timeclock schedule configuration procedure <NUM> may be executed by the motorized blind for which the timeclock schedule is being configured. For example, the façade timeclock schedule configuration procedure <NUM> may be executed periodically at <NUM>, e.g., once a day to configure timeclock schedules for the motorized blinds for the coming day. The façade timeclock schedule configuration procedure <NUM> may be executed, for example, at <NUM> of the timeclock configuration procedure <NUM> shown in <FIG>. At <NUM>, the control device may determine the endpoint elevation angles ae1, ae2 for the present façade. For example, the control device may recall the endpoint elevation angles ae1, ae2 from memory depending upon the one of the cardinal or ordinal directions to which the present façade is associated (e.g., as shown in Table <NUM> above).

Next, the control device may determine event times for controlling the motorized blinds on the present façade, for example, by separately considering both the first endpoint elevation angle ae1 and the second endpoint elevation angle ae2. For example, at <NUM>, the control device may determine event times for controlling the motorized blinds to prevent direct sunlight from shining into the space assuming that the elevation angle ae of the present façade is equal to the first endpoint elevation angle ae1. At <NUM>, the control device may determine event times for controlling the motorized blinds to prevent direct sunlight from shining into the space assuming that the elevation angle ae of the present façade is equal to the second endpoint elevation angle ae2. At both of the first endpoint elevation angle ae1 and the second endpoint elevation angle ae2, the control device may determine at <NUM> and <NUM> event times for controlling the motorized blinds to the slanted tilt position and/or the view tilt position depending upon the predicted position of the sun throughout the course of the upcoming day. For example, at <NUM> and <NUM>, the control device may determine whether the sun is directly shining on the façade by calculating the profile angle ap of the sun at the first endpoint elevation angle ae1 and the second endpoint elevation angle ae2, respectively, and then determining if the profile angle ap is between <NUM>° and <NUM>°.

At <NUM>, the control device may determine the event times for the final timeclock schedule by comparing the event times as determined at the first endpoint elevation angle ae1 (e.g., at <NUM>) and the event times as determined at the second endpoint elevation angle ae2 (e.g., at <NUM>). For example, when comparing the event times at which the motorized blinds may be controlled to the slanted tilt position (e.g., a fade-fighter tilt time tFF at the first endpoint elevation angle ae1 and a fade-fighter tilt time tFF at the first endpoint elevation angle ae2), the control device may choose the earlier of the two fade-fighter tilt times to be the fade-fighter tilt time in the final timeclock schedule. In addition, the control device may subtract a buffer time tBUFFER (e.g., three minutes) from the earlier of the two fade-fighter tilt times before storing the fade-filter tilt time in the timeclock schedule. For example, a stored fade-fighter tilt time may include the buffer time. The buffer time tBUFFER may help to ensure that the sun does not directly shine into the space during the upcoming day. When comparing the event times at which the motorized blinds may be controlled to the view tilt position (e.g., a view tilt time tFF at the first endpoint elevation angle ae1 and a view tilt time tFF at the first endpoint elevation angle ae2), the control device may choose the later of the two view tilt times to be the view tilt time in the final timeclock schedule. In addition, the control device may add a buffer time tBUFFER (e.g., three minutes) to the later of the two view tilt times before storing the view tilt time in the timeclock schedule. For example, a stored view tilt time may include the buffer time. If there are two fade-filter tilt times and/or two view tilt times in each of the event times determined at the first endpoint elevation angle ae1 and at the second endpoint elevation angle ae2, the control device may compare the events times at the respective timeclock events to determine which event times to use in the final timeclock schedule.

At <NUM>, the control device may determine an event time at which the motorized blinds may be controlled to the privacy tilt position (e.g., a privacy tilt time tPRIV). The privacy tilt time tPRIV may be determined based on a sunset time tSUNSET for the upcoming day. For example, the control device set the privacy tilt time tPRIV to be an offset time tOFFSET (e.g., <NUM> minutes) after the sunset time tSUNSET. At <NUM>, the control device may determine an event time at which the motorized blinds may be controlled out of the privacy tilt position based on a sunrise time tSUNRISE for the upcoming day. For example, if the first fade-fighter tilt time tFF1 is equal to the sunrise time tSUNRISE for the present façade (e.g., the façade is facing in an eastward direction and the sun may be shining directly on the façade at sunrise), the control device does not need to create an additional timeclock event at the sunrise time tSUNRISE to cause the motorized blinds to move from the privacy position (e.g., the motorized blinds will be controlled to the slanted tilt position at the sunrise time tSUNRISE). However, if the first fade-fighter tilt time tFF1 is equal to the sunrise time tSUNRISE for the present façade (e.g., the sun may not be shining directly on the façade at sunrise), the control device may determine an event time for controlling the motorized blinds to the view tilt position at the sunrise time tSUNRISE.

At <NUM>, the control device may generate a timeclock schedule for the motorized blinds on the present façade for the upcoming day for controlling the motorized blinds to the slanted tilt position, the view tilt position, and the privacy tilt position at the determined event times (e.g., as determined at <NUM> and <NUM>). For example, the control device may generate timeclock events for controlling the motorized blinds to the slanted tilt position at one or more determined fade-fighter tilt times tFF, timeclock events for controlling the motorized blinds to the view tilt position at one or more determined view tilt times tVIEW, and/or controlling the motorized blinds to the privacy tilt position at the privacy time tPRIV (e.g., as shown in <FIG>). At <NUM>, the control device may store the timeclock schedule for the motorized blinds on the present façade (e.g., an individual timeclock schedule), before the façade timeclock schedule configuration procedure <NUM> exits. The façade timeclock schedule configuration procedure <NUM> may be repeated (e.g., successively) for one or more other façades of the building that include motorized blinds. Alternatively, the façade timeclock schedule configuration procedures <NUM> for the façades of a building may be performed simultaneously for each of the façades of the building.

<FIG> is a flowchart of another example façade timeclock schedule configuration procedure <NUM>. The example façade timeclock schedule configuration procedure <NUM> may be executed to configure a timeclock schedule for controlling (e.g., automatically controlling) tilt positions of one or more motorized blinds (e.g., the motorized window treatments <NUM> and/or the blind system <NUM>) on a particular façade of a building in which the motorized blinds are located. The façade timeclock schedule configuration procedure <NUM> may be executed by a control device (e.g., the system controller <NUM>) of a load control system that includes the motorized blinds. The façade timeclock schedule configuration procedure <NUM> may also be executed by the motorized blind for which the timeclock schedule is being configured, for example, when the motorized blind is configured to execute a timeclock. For example, the façade timeclock schedule configuration procedure <NUM> may be executed periodically at <NUM>, e.g., once a day to configure timeclock schedules for the motorized blinds for the coming day. The façade timeclock schedule configuration procedure <NUM> may be executed, for example, at <NUM> of the timeclock configuration procedure <NUM> shown in <FIG>.

At <NUM>, the control device may set a solar azimuth angle range by determining solar azimuth angle limits as1, as2 for the façade <NUM> based on the elevation angle ae of the façade. The control device may set the solar azimuth angle limits as1, as2 based on a total façade angle atotal (e.g., approximately <NUM>°). For example, the first solar azimuth angle limit as1 may be set equal to the first endpoint elevation angle ae1 minus half of the total façade angle atotal (e.g., as1 = ae1 - [atotal<NUM>]), and the second solar azimuth angle limit as2 may be set equal to the second endpoint elevation angle ae2 plus half of the total façade angle atotal (e.g., as2 = ae2 + [atotal/<NUM>]). The control device may recall the endpoint elevation angles ae1, ae2 from memory depending upon the one of the cardinal or ordinal directions to which the present façade is associated (e.g., as shown in Table <NUM> above). In addition, a buffer angle abuff (e.g., approximately <NUM>°) may be appended to both the solar azimuth angle limits as1, as2 (e.g., as1 = ae1 - [atotal/<NUM>] - abuff, and as2 = ae2 + [atotal/<NUM>] + abuff).

At <NUM>, the control device may determine event times for controlling the motorized blinds on the present façade to prevent direct sunlight from shining into the space. The control device may determine event times for controlling the motorized blinds to the slanted tilt position and/or the view tilt position depending upon the predicted position of the sun throughout the course of the upcoming day. For example, at <NUM>, the control device may determine whether the sun is directly shining on the façade by calculating the solar azimuth angle as of the sun, and then determining if the profile angle ap is between the solar azimuth angle limits as1, as2 for the façade.

At <NUM>, the control device may determine an event time at which the motorized blinds may be controlled to the privacy tilt position (e.g., a privacy tilt time tPRIV). The privacy tilt time tPRIV may be determined based on a sunset time tSUNSET for the upcoming day. For example, the control device set the privacy tilt time tPRIV to be an offset time tOFFSET (e.g., <NUM> minutes) after the sunset time tSUNSET.

At <NUM>, the control device may determine an event time at which the motorized blinds may be controlled out of the privacy tilt position based on a sunrise time tSUNRISE for the upcoming day. For example, if the first fade-fighter tilt time tFF1 is equal to the sunrise time tSUNRISE for the present façade (e.g., the façade is facing in an eastward direction and the sun may be shining directly on the façade at sunrise), the control device does not need to create an additional timeclock event at the sunrise time tSUNRISE to cause the motorized blinds to move from the privacy position (e.g., the motorized blinds will be controlled to the slanted tilt position at the sunrise time tSUNRISE). However, if the first fade-fighter tilt time tFF1 is equal to the sunrise time tSUNRISE for the present façade (e.g., the sun may not be shining directly on the façade at sunrise), the control device may determine an event time for controlling the motorized blinds to the view tilt position at the sunrise time tSUNRISE.

At <NUM>, the control device may generate a timeclock schedule for the motorized blinds on the present façade for the upcoming day for controlling the motorized blinds to the slanted tilt position, the view tilt position, and the privacy tilt position at the determined event times (e.g., as determined at <NUM> and <NUM>). For example, the control device may generate timeclock events for controlling the motorized blinds to the slanted tilt position at one or more determined fade-fighter tilt times tFF, timeclock events for controlling the motorized blinds to the view tilt position at one or more determined view tilt times tVIEW, and/or controlling the motorized blinds to the privacy tilt position at the privacy time tPRIV (e.g., as shown in <FIG>).

At <NUM> the control device may store the timeclock schedule for the motorized blinds on the present façade (e.g., an individual timeclock schedule), before the façade timeclock schedule configuration procedure <NUM> exits. The façade timeclock schedule configuration procedure <NUM> may be repeated (e.g., successively) for one or more other façades of the building that include motorized blinds. Alternatively, the façade timeclock schedule configuration procedures <NUM> for the façades of a building may be performed simultaneously for each of the façades of the building.

<FIG> is a flowchart of an example timeclock event configuration procedure <NUM> that may be executed to configure timeclock events of a timeclock schedule for controlling (e.g., automatically controlling) tilt positions of one or more motorized blinds (e.g., the motorized window treatments <NUM> and/or the blind system <NUM>). The timeclock event configuration procedure <NUM> may be executed by a control device (e.g., the system controller <NUM>) of a load control system that includes the motorized blinds. The timeclock event configuration procedure <NUM> may be executed by the motorized blind for which the timeclock schedule is being configured. For example, the timeclock event configuration procedure <NUM> may be executed at <NUM> to configure timeclock events for timeclock schedules for the motorized blinds for the coming day. The timeclock event configuration procedure <NUM> may be executed, for example, at <NUM> and <NUM> of the façade timeclock schedule configuration procedure <NUM> shown in <FIG> and/or at <NUM> of the façade timeclock schedule configuration procedure <NUM> shown in <FIG>.

During the façade timeclock event configuration procedure <NUM>, the control device may step through each minute of a day and calculate a position metric of the sun (e.g., a profile angle ap and/or a solar azimuth angle as of the sun) at each minute to determine if the motorized blinds should be controlled to the slanted tilt position and/or the view tilt position. At <NUM>, the control device may determine the position metric of the sun (e.g., the profile angle ap and/or the solar azimuth angle as of the sun) of the sun at the present façade at a present time t. For example, at <NUM>, the control device may calculate the profile angle ap of the sun when executing the façade timeclock schedule configuration procedure <NUM> shown in <FIG>, and may calculate the solar azimuth angle as of the sun when executing the façade timeclock schedule configuration procedure <NUM> shown in <FIG>. The present time t may be initialized to zero (e.g., midnight) when the timeclock event configuration procedure <NUM> is started. For example, the control device may calculate the profile angle ap and/or the solar azimuth angle as at <NUM> using the equations <NUM>-<NUM> shown above. The control device may calculate the profile angle ap and/or the solar azimuth angle as as a function of the longitude λ and the latitude Φ of the building in which the motorized blinds may be installed. The control device may calculate an elevation angle ae of the present façade. The timeclock event configuration procedure <NUM> may be executed multiple times with the elevation angle ae set to the first and second endpoint elevation angles ae1, ae2 (e.g., as shown at <NUM> and <NUM> of the façade timeclock schedule configuration procedure <NUM>). The standard time ts of the equations <NUM>-<NUM> may be set to the present time t.

At <NUM>, the control device may determine if the present time t is at sunrise for the upcoming day. The control device may determine that the present time t is at sunrise by calculating a profile angle ap-east for an elevation angle ae directed due east (e.g., for an elevation angle ae of -<NUM>°). If the profile angle ap-east for the elevation angle ae directed due east just became greater than <NUM>° (e.g., indicates that the sun may have just passed the horizon and became incident on the façade), the control device may conclude that the present time t is at sunrise. If the present time t is at sunrise at <NUM>, the control device may set a sunrise time tSUNRISE equal to the present time t at <NUM>.

At <NUM>, the control device may determine if the determined position metric of the sun indicates that the sun just left the present façade (e.g., stops shining directly on the façade) at the present time t. For example, the control device may determine that the sun just left the present façade at the present time t by determining if a calculated profile angle ap at a previous time was inside of the range of <NUM>° to <NUM>° and a calculated profile angle ap at the present time t is now outside of the range of <NUM>° to <NUM>°. In addition, the control device may determine that the sun just left the present façade at the present time t by determining if a calculated solar azimuth angle as at a previous time was inside of the range between the azimuth angle limits as1, as2, and a calculated solar azimuth angle as at the present time t is now outside of the range between the azimuth angle limits as1, as2. The previous time may be one minute prior to the present time. The previous time may be denoted as t - <NUM>. If the control device determines that the sun just left the present façade at the present time t at <NUM> and a first view tilt time tVIEW1 does not already exist at <NUM>, the control device may set the first view tilt time tVIEW1 to the present time t at <NUM>. If the first view tilt time tVIEW1 already exists at <NUM>, the control device may set a second view tilt time tVIEW2 to the present time t at <NUM>.

If the control device determines that the sun did not just leave (e.g., sunlight is still incident on) the present façade at <NUM>, the control device may determine if the determined position metric of the sun indicates that the sun just came onto (e.g., recently became incident on and/or began shining directly on the façade) the present façade at the present time t at <NUM>. For example, the control device may determine that the sun just came onto the present façade at the present time t by determining if a calculated profile angle ap at the previous time was outside of the range of <NUM>° to <NUM>° and a calculated profile angle ap at the present time t is now inside of the range of <NUM>° to <NUM>°. In addition, the control device may determine that the sun just came onto the present façade at the present time t by determining if a calculated solar azimuth angle as at the previous time was outside of the range between the azimuth angle limits as1, as2, and a calculated solar azimuth angle as at the present time t is now inside of the range between the azimuth angle limits as1, as2. The control device may determine whether a first fade-fighter time tFF1 is defined (e.g., already exists). If the control device determines that the sun just came onto the present façade at the present time t at <NUM> and the first fade-fighter tilt time tFF1 does not already exist at <NUM>, the control device may set the first fade-fighter tilt time tFF1 to the present time t at <NUM>. If the first fade-fighter tilt time tFF1 already exists at <NUM>, the control device may set a second fade-fighter tilt time tFF2 to the present time t at <NUM>.

At <NUM>, the control device may determine if the present time t is at sunset for the upcoming day. The control device may determine that the present time t is at sunset by calculating a profile angle ap-west for an elevation angle ae directed due west (e.g., for an elevation angle ae of <NUM>°). If the profile angle ap-west for the elevation angle ae directed due west just became less than <NUM>°(e.g., indicates that the sun may have just passed the horizon and is no longer incident on the façade), the control device may conclude that the present time t is at sunset. If the present time t is at sunset at <NUM>, the control device may set a sunrise time tSUNSET equal to the present time t at <NUM>. If the present time t is not equal to the end of the upcoming day (e.g., midnight) at <NUM>, the control device may increase the present time t by a step value tSTEP (e.g., one minute) at <NUM>, and the timeclock event configuration procedure <NUM> may loop around to calculate the profile angle ap of the sun at the updated present time t at <NUM>. When the present time t is equal to the end of the upcoming day at <NUM>, the timeclock event configuration procedure <NUM> may exit.

<FIG> is a flowchart of an example façade timeclock schedule configuration procedure <NUM>. The example façade timeclock schedule configuration procedure <NUM> may be executed to configure a timeclock schedule for controlling (e.g., automatically controlling) tilt positions of one or more motorized blinds (e.g., the motorized window treatments <NUM> and/or the blind system <NUM>) on a particular façade of a building in which the motorized blinds are located. The façade timeclock schedule configuration procedure <NUM> may be executed by a control device (e.g., the system controller <NUM> and/or the network device <NUM>) of a load control system that includes the motorized blinds. The façade timeclock schedule configuration procedure <NUM> may be also executed by the motorized blind for which the timeclock schedule is being configured, for example, when the motorized blind is configured to execute a timeclock. For example, the façade timeclock schedule configuration procedure <NUM> may be executed periodically at <NUM>, e.g., once a day, once a week, once a month, once a year, etc. to configure timeclock schedules for the motorized blinds for the coming day. The façade timeclock schedule configuration procedure <NUM> may be executed, for example, at <NUM> of the timeclock configuration procedure <NUM> shown in <FIG>.

At <NUM>, the control device may associate the present façade with one of a predetermined set of directions. For example, the control device may associate the present façade with one of a cardinal or ordinal direction, one of a cardinal, ordinal, or half-wind direction, one of a cardinal, ordinal, half-wind, or quarter-wind direction, one of a user-defined set of directions, etc. At <NUM>, the control device may select a predetermined set of event times for controlling the motorized blinds on the present façade, for example, a predetermined set of event times based on the associated one of the predetermined set of directions. For example, the control device may include a set of predetermined events for each of the potential directions of the façade. The set of predetermined events may be calculated using any suitable method, such as, for example, as discussed above with respect to <FIG>. The predetermined set of event times may include timeclock events for controlling the motorized blinds to the slanted tilt position at one or more determined fade-fighter tilt times tFF, timeclock events for controlling the motorized blinds to the view tilt position at one or more determined view tilt times tVIEW, and/or controlling the motorized blinds to the privacy tilt position at the privacy time tPRIV (e.g., as shown in <FIG>).

The predetermined set of event times may include an event time at which the motorized blinds may be controlled to the privacy tilt position (e.g., a privacy tilt time tPRIV). The privacy tilt time tPRIV may be determined based on a sunset time tSUNSET for the upcoming day. For example, the control device set the privacy tilt time tPRIV to be an offset time tOFFSET (e.g., <NUM> minutes) after the sunset time tSUNSET. Similarly, the predetermined set of event times may determine an event time at which the motorized blinds may be controlled out of the privacy tilt position based on a sunrise time tSUNRISE for the upcoming day. For example, if the first fade-fighter tilt time tFF1 is equal to the sunrise time tSUNRISE for the present façade (e.g., the façade is facing in an eastward direction and the sun may be shining directly on the façade at sunrise), the predetermined set of event times does not need to include an additional timeclock event at the sunrise time tSUNRISE to cause the motorized blinds to move from the privacy position (e.g., the motorized blinds will be controlled to the slanted tilt position at the sunrise time tSUNRISE). However, if the first fade-fighter tilt time tFF1 is equal to the sunrise time tSUNRISE for the present façade (e.g., the sun may not be shining directly on the façade at sunrise), the predetermined set of events may include an event time for controlling the motorized blinds to the view tilt position at the sunrise time tSUNRISE.

At <NUM>, the control device may generate one or more custom events for inclusion in the predetermined set of events obtained at <NUM>. For example, a user may set an additional tPRIV for transitioning a blind system to the privacy tilt angle. Similarly, a user may remove one or more events, such as a fade-fighter tilt time tFF to maintain the blind system <NUM> in the previous configuration (e.g., view tilt position or privacy tilt position). At <NUM>, a user may set one or more custom settings for one or more tilt positions, such as a custom fade fighter tilt percentage greater or lesser than <NUM>%.

At <NUM>, the control device may store the timeclock schedule for the motorized blinds on the present façade (e.g., an individual timeclock schedule), before the façade timeclock schedule configuration procedure <NUM> exits. The façade timeclock schedule configuration procedure <NUM> may be repeated (e.g., successively) for one or more other façades of the building that include motorized blinds. Alternatively, the façade timeclock schedule configuration procedures <NUM> for the façades of a building may be performed simultaneously for each of the façades of the building.

<FIG> is a flowchart of an example timeclock schedule execution <NUM> for a control device including a control-source device. At <NUM>, the control device or blind system detects a time matching an event time contained in a façade timeclock schedule. The event may include a transition to a fade fighter tilt position, a view tilt position, or a privacy tilt position. At <NUM>, the control device determines whether the event is a transition to a fade fighter tilt position. If the event is not a transition to a fade fighter tilt position, the control device executes the event and, at <NUM>, transitions the blind system <NUM> to the tilt position indicated by the event in the timeclock schedule.

If the event is a transition to a fade fighter tilt position, the control device, at <NUM>, determines whether a transition to a fade fighter tilt position is necessary. For example, the control device may receive a signal from a control-source device, such as control-source device <NUM> described in greater detail below. The control-source device may include a sensor configured to detect one or more environmental parameters indicative of whether a transition to the fade fighter tilt position is necessary, such as, for example, an occupancy sensor, a sunlight sensor, a window sensor, etc. For example, if the control-source device is configured to detect direct sunlight (e.g., a daylight sensor, etc.), the control-source device may prevent transition to the fade fighter tilt position when a minimal amount of sunlight (e.g., no sunlight) is detected. As another example, the control device may receive weather data for a geographic area including the façade. If the weather stream indicates there is no direct sunlight, e.g., it is cloudy, raining, etc., the control device may not transition to the fade finder tilt position (as there is no direct sunlight on the façade).

<FIG> is a block diagram illustrating an example computing device <NUM>. As described herein, a computing device may include a network device or a server device (e.g., authorization server, resource server, and/or third party server). The computing device <NUM> may include a control circuit <NUM> for controlling the functionality of the computing device <NUM>. The control circuit <NUM> may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The control circuit <NUM> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the computing device <NUM> to perform as described herein. The control circuit <NUM> may store information in and/or retrieve information from the memory <NUM>. The memory <NUM> may include a non-removable memory and/or a 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. 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 computing device <NUM> may include a communications circuit <NUM> for transmitting and/or receiving information. The communications circuit <NUM> may perform wireless and/or wired communications. The communications circuit <NUM> may include an RF transceiver or other circuit capable of performing wireless communications via an antenna. Communications circuit <NUM> may be in communication with control circuit <NUM> for transmitting and/or receiving information.

The control circuit <NUM> may be in communication with an output device <NUM>, such as a visual output device (e.g., a display) and/or an audible output device (e.g., a speaker), for providing information to a user. The control circuit <NUM> and/or the output device <NUM> may generate a user interface, e.g., a graphical user interface (GUI), for being displayed on the computing device <NUM>. The output device <NUM> and the control circuit <NUM> may be in two-way communication, as the display <NUM> may include a touch screen module capable of receiving a user input and providing such user input to the control circuit <NUM>. The computing device <NUM> may include an actuator <NUM> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <NUM>.

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

<FIG> is a block diagram illustrating an example system controller <NUM> (such as system controller <NUM>, described herein). The system controller <NUM> may include a control circuit <NUM> for controlling the functionality of the system controller <NUM>. The control circuit <NUM> may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The control circuit <NUM> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the system controller <NUM> to perform as described herein. The control circuit <NUM> may be configured to execute a timeclock. The control circuit <NUM> may store information in and/or retrieve information from the memory <NUM>. The memory <NUM> may include a non-removable memory and/or a 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. 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 memory <NUM> may be configured to store a timeclock schedule defining event times and associated commands for controlling control-target devices.

The system controller <NUM> may include a communications circuit <NUM> for transmitting and/or receiving information. The communications circuit <NUM> may perform wireless and/or wired communications. The system controller <NUM> may also, or alternatively, include a communications circuit <NUM> for transmitting and/or receiving information. The communications circuit <NUM> may perform wireless and/or wired communications. The communications circuits <NUM> and <NUM> may be in communication with control circuit <NUM>. The control circuit <NUM> may be configured to transmit messages including commands for controlling control-target devices via the communication circuit <NUM>. The control circuit <NUM> may be configured to transmit message including command for controlling the control-target devices at the event times of the timeclock schedule. The communications circuits <NUM> and <NUM> may include RF transceivers or other communications modules capable of performing wireless communications via an antenna. The communications circuit <NUM> and communications circuit <NUM> may be capable of performing communications via the same communication channels or different communication channels. For example, the communications circuit <NUM> may be capable of communicating via a first wireless communication link, e.g., with a network device, over a network, etc., and the communications circuit <NUM> may be capable of communicating via a second wireless communication link, e.g., with control devices and/or other devices in the load control system.

The control circuit <NUM> may be in communication with an LED indicator <NUM> for providing indications to a user. The control circuit <NUM> may be in communication with an actuator <NUM> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <NUM>. For example, the actuator <NUM> may be actuated to put the control circuit <NUM> in an association mode and/or communicate association messages from the system controller <NUM>.

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

<FIG> is a block diagram illustrating an example control-target device, e.g., a load control device <NUM>, as described herein. The load control device <NUM> may be a dimmer switch, an electronic switch, an electronic ballast for lamps, an LED driver for LED light sources, 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 <NUM> may include a communications circuit <NUM>. The communications circuit <NUM> may include a receiver, an RF transceiver, or other communications module capable of performing wired and/or wireless communications via communications link <NUM>. The communications circuit <NUM> may be in communication with control circuit <NUM>. The control circuit <NUM> may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The control circuit <NUM> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the load control device <NUM> to perform as described herein.

The control circuit <NUM> may store information in and/or retrieve information from the memory <NUM>. For example, the memory <NUM> may maintain a registry of associated control devices and/or control instructions. The memory <NUM> may include a non-removable memory and/or a removable memory. The load control circuit <NUM> may receive instructions from the control circuit <NUM> and may control the electrical load <NUM> based on the received instructions. The load control circuit <NUM> may send status feedback to the control circuit <NUM> regarding the status of the electrical load <NUM>. The load control circuit <NUM> may receive power via the hot connection <NUM> and the neutral connection <NUM> and may provide an amount of power to the electrical load <NUM>. The electrical load <NUM> may include any type of electrical load.

The control circuit <NUM> may be in communication with an actuator <NUM> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <NUM>. For example, the actuator <NUM> may be actuated to put the control circuit <NUM> in an association mode and/or communicate association messages from the load control device <NUM>.

<FIG> is a block diagram illustrating an example control-source device <NUM> as described herein. The control-source device <NUM> may be a remote control device, an occupancy sensor, a daylight sensor, a window sensor, a temperature sensor, and/or the like. The control-source device <NUM> may include a control circuit <NUM> for controlling the functionality of the control-source device <NUM>. The control circuit <NUM> may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The control circuit <NUM> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the control-source device <NUM> to perform as described herein.

The control circuit <NUM> may be in communication with an actuator <NUM> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <NUM>. For example, the actuator <NUM> may be actuated to put the control circuit <NUM> in an association mode and/or communicate association messages from the control-source device <NUM>. The control circuit <NUM> may store information in and/or retrieve information from the memory <NUM>. The memory <NUM> may include a non-removable memory and/or a removable memory, as described herein.

The control-source device <NUM> may include a communications circuit <NUM> for transmitting and/or receiving information. The communications circuit <NUM> may transmit and/or receive information via wired and/or wireless communications. The communications circuit <NUM> may include a transmitter, an RF transceiver, or other circuit capable of performing wired and/or wireless communications. The communications circuit <NUM> may be in communication with control circuit <NUM> for transmitting and/or receiving information.

The control circuit <NUM> may be in communication with an input circuit <NUM>. The input circuit <NUM> may include an actuator (e.g., one or more buttons) or a sensor circuit (e.g., an occupancy sensor circuit, a daylight sensor circuit, or a temperature sensor circuit) for receiving input that may be sent to a device for controlling an electrical load. For example, the control-source device may receive input from the input circuit <NUM> to put the control circuit <NUM> in an association mode and/or communicate association messages from the control-source device. The control circuit <NUM> may receive information from the input circuit <NUM> (e.g., an indication that a button has been actuated or sensed information). Each of the modules within the control-source device <NUM> may be powered by a power source <NUM>.

<FIG> is a simplified block diagram of an example motor drive unit <NUM> (e.g., a motor drive unit of the motorized window treatment <NUM> and/or the drive unit <NUM> of the blind system <NUM>), in accordance with some embodiments. The motor drive unit <NUM> may comprise a motor <NUM> (e.g., a DC motor) that may be operated to raise and lower a cover material and/or tilt slats (e.g., the slats <NUM>) to control the amount of daylight entering a space. The motor <NUM> may be controlled by a pulse-width modulated (PWM) signal and a speed of the mtor may be adjusted by adjusting a duty cycle of the PWM signal applied to the DC motor <NUM>. For example, the motor <NUM> may be operatively coupled to raise and lower a bottom bar and/or tilt slats of a motorized blind (e.g., the bottom bar <NUM> and/or the slats <NUM> of the blind system <NUM>). Changing the magnitude of the DC voltage or the duty cycle of the PWM signal applied to the motor <NUM> may change the rotational speed of the motor. Further, the motor <NUM> may be configured to change the direction of rotation in response to a change in the polarity of the DC voltage or PWM signal applied to the motor <NUM>.

To accomplish this level of control of the motor <NUM>, the motor <NUM> may be coupled to an H-bridge motor drive circuit <NUM>, which may be driven by a control circuit <NUM>. The H-bridge motor drive circuit <NUM> may include four transistors, such as, for example, four field effect transistors (not shown). The transistors may be coupled such that, when two of the transistors are conductive, a positive DC voltage is applied to the motor <NUM> to cause the motor to rotate in a forward direction. When the other two transistors of the H-bridge circuit <NUM> are conductive, a negative DC voltage may be applied to the motor <NUM> to cause the motor <NUM> to rotate in the reverse direction. To control the speed of the motor <NUM>, the control circuit <NUM> may drive at least one transistor of the H-bridge circuit <NUM> with a PWM signal. The control circuit <NUM> may include any suitable processing circuitry, such as, for example, a microprocessor, e.g., a complex instruction set computer (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, and/or a very long instruction word (VLIW) microprocessor), a programmable logic device (PLD), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a chip multiprocessor (CMP) or any suitable processing device or control circuit. The control circuit <NUM> may be configured to execute a timeclock. The control circuit <NUM> may be configured to control the motor <NUM> (e.g., to tilt the slats) at the event times of the timeclock schedule.

The motor drive unit <NUM> may include a rotational position sensor, such as, for example, a Hall effect sensor (HES) circuit <NUM>, which may be configured to provide information regarding the rotational speed and the direction of the motor <NUM> to the control circuit <NUM>. The rotational position sensor may also comprise other suitable position sensors, such as, for example, optical and resistor sensors. The control circuit <NUM> may be configured to determine a rotational position of the motor <NUM> in response to the Hall effect sensor circuit <NUM>. The control circuit <NUM> may use the rotational position of the motor <NUM> to determine a present position of the covering material (e.g., such as the covering material <NUM> of the motorized window treatment <NUM> and/or the bottom bar <NUM> of the drive system <NUM>). The control circuit <NUM> may be coupled to a non-volatile memory <NUM> for storage of the present position of the covering material, the fully open position, and the fully closed position. In addition, the memory <NUM> may be configured to store a timeclock schedule including event times at which to control the motor <NUM> (e.g., to tilt the slats). The memory <NUM> may include an electrically erasable programmable read-only memory (EEPROM), although it will be appreciated that any suitable memory may be used.

The motor drive unit <NUM> may include a communication circuit <NUM> that allows the control circuit <NUM> to transmit and receive communication signals to and from a keypad and/or other motor drive units <NUM>. The motor drive unit <NUM> may further include a plurality of buttons <NUM> that allow a user to provide inputs to the control circuit <NUM> during setup and configuration of a motorized window treatment. The control circuit <NUM> may drive the motor <NUM> in a first direction at a constant rotational speed while a first button of the plurality of buttons <NUM> is pressed and held, and may drive the motor <NUM> in a second direction at a constant rotational speed while a second button of the plurality of buttons <NUM> is pressed. In addition, the control circuit <NUM> may be configured to tilt slats of a motorized blind in a first direction while the first button of the plurality of buttons <NUM> is pressed and in a second direction while the second button of the plurality of buttons <NUM> is pressed.

The control circuit <NUM> may be configured to control the movement of the covering material in response to a covering movement command, e.g., from the communication signals received via the communication circuit <NUM> or the user inputs from the buttons <NUM>. The covering movement command may consist of a command type (e.g., "move to a desired position" or "tilt to a desired tilt position") and/or a desired position (e.g., to which the control circuit <NUM> may be configured to control the covering material and/or tilt the slats of a motorized blind). The desired position may be a preset position, a fully-open position, or a fully-closed position. In addition, the desired position may be a tilt position of a motorized blind.

The motor drive unit <NUM> may receive power from an AC supply voltage VAC (e.g., 24VAC) provided by an alternating-current (AC) power source (not shown). The AC supply voltage VAC may be provided to a full-wave rectifier bridge <NUM> for generating a bus voltage VBUS (e.g., 30VDC), which may be filtered by a storage capacitor <NUM>. The bus voltage VBUS may be provided to the H-bridge motor drive circuit <NUM> for driving the motor <NUM>. A power supply <NUM> may receive the bus voltage VBUS and generate a DC supply voltage Vcc (e.g., 5VDC) for powering the low-voltage circuitry of the motor drive unit <NUM> (e.g., the control circuit <NUM>, the memory <NUM>, and the communication circuit <NUM>).

Claim 1:
A blind system (<NUM>) configured to be mounted to cover a window located on a façade of a building, the blind system (<NUM>) comprising:
a headrail (<NUM>);
a bottom bar (<NUM>);
a plurality of slats (<NUM>) spaced apart vertically between the headrail (<NUM>) and the bottom bar (<NUM>);
a lift cord (<NUM>) extending from the headrail (<NUM>) to the bottom bar (<NUM>) to provide for raising and lowering the bottom bar (<NUM>);
a tilt ladder (<NUM>) extending from the headrail (<NUM>) to the bottom bar (<NUM>) and operable to support the slats (<NUM>) and to tilt the slats (<NUM>); and
a drive unit (<NUM>) operably coupled to the tilt ladder (<NUM>) for tilting the slats (<NUM>), the drive unit (<NUM>) configured to selectively tilt the slats (<NUM>) into each of a plurality of tilt positions that include at least: a view tilt position in which the slats (<NUM>) are approximately horizontal, a slanted tilt position in which the slats (<NUM>) are positioned to block direct sunlight from shining into the building, and a privacy tilt position in which the slats (<NUM>) are approximately vertical;
wherein the drive unit (<NUM>) is configured to tilt the slats (<NUM>) into one of the plurality of tilt positions at each of a plurality of event times according to a timeclock schedule, the plurality of event times determined from a predicted position of the sun, such that the drive unit (<NUM>) is configured to:
tilt the slats (<NUM>) to the slanted tilt position when the predicted position of the sun indicates that direct sunlight is incident on the façade based on a first endpoint elevation angle determined using a facing direction of the facade;
tilt the slats (<NUM>) to the view tilt position when the predicted position of the sun indicates that no direct sunlight is incident on the façade based on a determined second endpoint elevation angle determined using the facing direction of the facade, wherein the second endpoint elevation angle differs from the first endpoint elevation angle; and
tilt the slats (<NUM>) to the privacy tilt position between sunset and sunrise.