Controller for optically switchable devices
By using a printed circuit board controller system and the G.hn protocol, the color transitions of multiple heat-insulating glass units are monitored and controlled. Combined with cloud computing and sky sensor equipment, the problems of intelligent dimming and system integration efficiency of optically switchable windows are solved, achieving efficient optical transition control and anomaly detection.
Patent Information
- Application Number
- CN202280058292.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-07-27
- Filing Date
- 2022-07-22
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-07-22
AI Technical Summary
Existing technologies struggle to effectively control the optical transitions of optically switchable windows to provide the required illumination conditions, while simultaneously reducing device power consumption and improving system integration efficiency.
The system employs a printed circuit board controller system, which includes multiple device packages and processing units. It provides power and data signals via the G.hn protocol and different cable types, monitors and controls the tinting transitions of multiple insulated glass units, and combines cloud computing and sky sensor equipment for intelligent regulation.
It achieves efficient control of the optical switchable window, reduces power consumption and improves system integration efficiency, and supports intelligent dimming and abnormal event detection.
Smart Images

Figure CN117881870B_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This application claims priority to U.S. Provisional Application No. 63 / 203,543 (Attorney’s File No. VIEWP132P), filed July 27, 2021, which is incorporated herein by reference in its entirety and for all purposes. This application claims priority to a continuation-in-part of U.S. Patent Application No. 17 / 654,458 (Attorney's File No. VIEWP083C2), filed March 11, 2022, which is a continuation-in-part of U.S. Patent Application No. 16 / 568,639 (Attorney's File No. VIEWP083C1), filed September 12, 2019; U.S. Patent Application No. 15 / 334,835 (Attorney's File No. VIEWP083), filed October 26, 2016; and U.S. Provisional Patent Application No. 62 / 248,181 (Attorney's File No. VIEWP083P), filed October 29, 2015. U.S. Patent Application No. 15 / 334,835 is a continuation-in-part of U.S. Patent Application No. 14 / 998,019 (Attorney's File No. VIEWP081), filed October 6, 2015. This application claims priority to a portion of the continuation-in-process application of International Patent Application Serial No. PCT / US2021 / 017946 (Attorney File No. VIEWP072X5WO), filed February 12, 2021, which claims priority to U.S. Provisional Patent Application No. 62 / 977,001 (Attorney File No. VIEWP072X5P), filed February 14, 2020; U.S. Provisional Patent Application No. 62 / 978,755 (Attorney File No. VIEWP072X5P2), filed February 19, 2020; U.S. Provisional Patent Application No. 63 / 027,452 (Attorney File No. VIEWP072X5P3), filed May 20, 2020; and U.S. Provisional Patent Application No. 63 / 146,365 (Attorney File No. VIEWP072X5P4), filed February 5, 2021. This application claims priority to a portion of a continuation-into-file of U.S. Patent Application No. 16 / 949,855 (Attorney’s File No. VIEWP041C3), filed November 17, 2020, which is a continuation-into-file of U.S. Patent Application No. 16 / 948,341 (Attorney’s File No. VIEWP041C2US), filed September 14, 2020, which is a continuation-into-file of U.S. Patent Application No. 15 / 882,719 (Attorney’s File No. VIEWP041C1US), filed January 29, 2018, which is a continuation-into-file of U.S. Patent Application No. 13 / 449,248 (Attorney’s File No. VIEWP041US), filed April 17, 2012.This application claims priority to a portion of a continuation-in-service application of U.S. Patent Application No. 17 / 247,662 (Attorney’s File No. VIEWP008X1C4), filed December 18, 2020, which is a continuation-in-service of U.S. Patent Application No. 16 / 386,094 (Attorney’s File No. VIEWP008X1C1US), filed April 16, 2019, which is a continuation-in-service of U.S. Patent Application No. 16 / 253,994 (Attorney’s File No. VIEWP008X1C1US), filed January 22, 2019. This is a continuation application of U.S. Patent Application No. 14 / 951,410 (Attorney's File No. VIEWP008X1D1US), filed November 24, 2015, which claims priority to U.S. Provisional Patent Application No. 62 / 085,179 (Attorney's File No. VIEWP008X1PUS), filed November 26, 2014. The entire contents of each of these applications are incorporated herein by reference for all purposes. Technical Field
[0003] This disclosure relates in its entirety to optically switchable devices, and more specifically to controllers for optically switchable devices. Background Technology
[0004] The development and deployment of optically switchable windows have increased due to growing concerns about energy efficiency and system integration. Electrochromic windows are a promising class of optically switchable windows. Electrochromism is a phenomenon in which a material exhibits reversible, electrochemically mediated changes in one or more optical properties when stimulated to different electronic states. Electrochromic materials and devices made from them can be incorporated into windows for, for example, residential, commercial, or other applications. The color, hue, transmittance, absorptivity, or reflectivity of an electrochromic window can be altered by inducing changes in the electrochromic material, for example, by applying a voltage to the electrochromic material. This capability allows for control over the intensity of light of various wavelengths that can pass through the window. A recent area of interest is intelligent control systems and algorithms for driving optical transitions in optically switchable windows to provide the desired lighting conditions while reducing the power consumption of these devices and improving the efficiency of systems integrated with them. Summary of the Invention
[0005] This article discloses a controller for optically switchable windows.
[0006] According to some specific embodiments, a window controller system for controlling multiple optically switchable devices includes a printed circuit board comprising a first plurality of device packages and a second plurality of device packages, wherein a first plurality of components are mounted to the first plurality of device packages, and a subgroup of the second plurality of device packages is filled with the second plurality of components. The first plurality of components includes: a plurality of insulated glass unit (IGU) controllers, each configured to control an IGU operatively coupled to a corresponding plurality of IGUs in the window controller system; and a processing unit configured to control each of the plurality of IGU controllers. The second plurality of components are selected based on the cable type and / or protocol type used to provide power and data signals to the printed circuit board.
[0007] In some examples, the protocol type includes at least one of the following: Home Networking Protocol or Power over Ethernet (PoE) Protocol. In some examples, the Home Networking Protocol is the G.hn protocol.
[0008] In some examples, the cable type includes at least one of the following: coaxial cable, power line cable, or twisted pair cable.
[0009] In some examples, the protocol type includes G.hn, and the second set of components includes one of: (i) a first subgroup of components configured to utilize G.hn coaxial inputs, or (ii) a second subgroup of components configured to utilize G.hn power line inputs. In some examples, the first subgroup of components configured to utilize G.hn coaxial inputs includes a shunt configured to be operatively connected to the trunk line and a coaxial coupling circuit configured to supply power from the trunk line to the analog front-end component. In some examples, the analog front-end component is operatively connected to the processing unit. In some examples, the second subgroup of components configured to utilize G.hn power line inputs includes an analog front-end component and a power line coupling circuit configured to be operatively connected to an AC power outlet. In some examples, the analog front-end component is operatively connected to the processing unit. In some examples, the second set of components also includes an analog-to-digital converter (ADC) configured to convert an AC signal from an AC power outlet into a DC signal.
[0010] In some examples, the protocol type includes G.hn, and the second plurality of components includes a third subgroup of components to be used in conjunction with either a G.hn coaxial input or a G.hn power line input.
[0011] In some examples, the first plurality of components also includes a memory device. In some examples, the memory device includes a flash memory device. In some examples, the memory device is configured to store indications of the cable type and / or protocol type used to provide power and data signals.
[0012] In some examples, the processing unit is configured to characterize the leakage current from one or more of the corresponding plurality of IGUs.
[0013] In some examples, the processing unit is further configured to communicate with a computing device. In some examples, the computing device is a cloud device located remotely from a building on which a window controller system is installed. In some examples, the processing unit is further configured to: detect anomaly events based on characterized leakage current; and, in response to detecting an anomaly event, cause data associated with the characterized leakage current to be transmitted to the computing device. In some examples, the computing device is a cloud computing device. In some examples, the computing device is housed in a control panel installed in a facility where a window controller system is installed.
[0014] In some examples, the window controller system also includes a memory device configured to store window banding information associated with the plurality of IGUs and / or shading scheduling information associated with the plurality of IGUs. In some examples, the processing unit is further configured to: receive window banding information and / or shading scheduling information from a computing device; and cause the window banding information and / or shading scheduling information to be stored in memory.
[0015] In some examples, the processing unit is configured to: receive an overwrite of a coloring command for at least one of the plurality of IGUs; and cause the at least one IGU to transition to a coloring state based on the received overwrite. In some examples, the overwrite is received via an application running on a mobile device. In some examples, the overwrite is received via a local network communicatively connected to the processing unit. In some examples, the overwrite is based on information obtained by a sky sensor device configured to measure solar radiation outside a facility where a window controller system is installed. In some examples, the overwrite is received via a local network communicatively connected to both the sky sensor device and the processing unit.
[0016] In some examples, the processing unit is configured such that each IGU controller applies a drive voltage with a ramp rate to the corresponding IGU, wherein the first ramp rate associated with a first IGU among the plurality of IGUs is different from the second ramp rate associated with a second IGU among the plurality of IGUs. In some examples, the drive voltage is applied to the first IGU from a time point offset from when the drive voltage is applied to the second IGU.
[0017] In some examples, the processing unit is configured to communicate with at least one computing device configured to control the operation of a building in which a window controller system is installed. In some examples, the at least one computing device is an edge server. In some examples, the processing unit is configured to enter a sleep mode in response to a signal from the at least one computing device.
[0018] In some examples, the first plurality of components also includes at least one component configured to provide one or more wireless communication channels. In some examples, the one or more wireless communication channels utilize at least one of a Wi-Fi communication protocol or a Bluetooth communication protocol. In some examples, the processing unit is configured to communicate with a cloud device using a Wi-Fi communication protocol. In some examples, the processing unit is configured to receive one or more updates from a cloud device using a Wi-Fi communication protocol. In some examples, the processing unit is configured to participate in a mesh network together with at least one other processing unit associated with at least one other window controller system.
[0019] In some examples, the window controller system further includes a second processing unit operatively coupled between the processing unit and each of the plurality of IGU controllers, wherein the second processing unit is configured to control each of the plurality of IGU controllers.
[0020] According to some specific embodiments, a window controller system for controlling multiple optically switchable windows includes: a housing comprising a 3- or 4-port socket box and a panel. The window controller system may include a printed circuit board comprising multiple components, including: multiple insulated glass unit (IGU) controllers, each configured to control an IGU operatively coupled to a corresponding IGU in the window controller system; and a processing unit configured to control each of the multiple IGU controllers.
[0021] In some examples, the window controller system also includes a heat sink housed within the housing.
[0022] In some examples, the panel is attached to a 3- or 4-gang socket box via multiple screws.
[0023] In some examples, at least one edge of the panel is angled.
[0024] In some examples, the panel includes multiple air vents.
[0025] In some examples, the window controller system also includes a cooling fan housed within the housing.
[0026] In some examples, the window controller system also includes multiple light-emitting diode (LED) indicators.
[0027] In some examples, the window controller system also includes a second printed circuit board configured to provide power and / or data via a power line system. In some examples, the second printed circuit board includes an AC power connector. In some examples, the second printed circuit board is positioned above and closer to the panel than the printed circuit board. In some examples, the printed circuit board includes a notch configured to allow power line cables to pass through the notch to reach the second printed circuit board.
[0028] According to some specific embodiments, a method for controlling the shading of a plurality of optically switchable devices includes: (a) applying a drive voltage to two or more optically switchable devices via a window controller in conjunction with a shading transition from a first shading state to a second shading state, wherein applying the drive voltage to the two or more optically switchable devices includes providing a voltage from a power supply shared by the two or more optically switchable devices. The method may involve (b) monitoring, for each of the two or more optically switchable devices, a parameter indicating the state of the shading transition. The method may involve (c) repeating (a) and (b) until it is determined that one or more optically switchable devices have completed the shading transition to the second shading state. The method may involve (d) in response to determining at (c) that the one or more optically switchable devices have completed the shading transition to the second state, applying a holding voltage to the one or more optically switchable devices while continuing to apply drive voltages to the remaining one or more optically switchable devices among the two or more optically switchable devices that have not yet completed the shading transition. The method may involve (e) repeating (b) to (d) until the two or more optically switchable devices have completed the shading transition.
[0029] In some examples, monitoring parameters indicating the state of a color transition includes individually measuring the open-circuit voltage (Voc) and / or the delivered charge for each of the two or more optically switchable devices. In some examples, determining that the one or more optically switchable devices have completed a color transition to a second color state includes (i) determining that the Voc measured for the one or more optically switchable devices meets or exceeds a target Voc, and / or (ii) determining that the charge delivered to the one or more optically switchable devices meets or exceeds a target charge to be delivered to the one or more optically switchable devices.
[0030] In some examples, the method may also involve: (f) measuring the hold state Voc for an optically switchable device to which a hold voltage is being applied; (g) determining whether the hold state Voc is less than a predetermined Voc threshold; and (h) applying a voltage pulse to the optically switchable device in response to determining that the hold state Voc is less than the predetermined Voc threshold. Attached Figure Description
[0031] Figure 1 A cross-sectional side view of an exemplary electrochromic window 100 according to some specific implementation is shown.
[0032] Figure 2 Exemplary control curves according to some specific implementations are shown.
[0033] Figure 3 A block diagram of an exemplary network system operable to control multiple IGUs according to some specific implementations is shown.
[0034] Figure 4 A block diagram of an exemplary master controller (MC) according to some specific implementations is shown.
[0035] Figure 5 A block diagram of an exemplary network controller (NC) according to some specific implementations is shown.
[0036] Figure 6 A circuit diagram of an exemplary window controller (WC) according to some specific implementations is shown.
[0037] Figure 7 A diagram is shown illustrating an exemplary connectivity architecture for connecting a window controller to an IGU, according to some specific implementations.
[0038] Figure 8 A block diagram of an exemplary module of a network controller according to some specific implementations is shown.
[0039] Figure 9 A flowchart is shown, illustrating an exemplary process for controlling multiple IGUs according to some specific implementations.
[0040] Figure 10 A flowchart is shown as an exemplary process for monitoring the drive voltage of multiple IDUs according to some specific implementations.
[0041] Figure 11 A schematic diagram of an exemplary system for controlling multiple IGUs is shown according to some specific implementations.
[0042] Figure 12 A schematic diagram of an exemplary circuit board layout for controlling multiple IGUs according to some specific implementations is shown.
[0043] Figures 13A to 13C Various views of an exemplary system, including a housing, for controlling multiple IGUs according to some specific implementations are shown.
[0044] Figure 14 An exemplary control panel system for interfacing with one or more controllers for controlling multiple IGUs is shown according to some specific implementations.
[0045] Figure 15 An exemplary block diagram of a system for controlling multiple IGUs, according to some specific implementations, is shown.
[0046] Figure 16 An exemplary block diagram of a system for communicating with multiple IGUs using various wireless communication protocols, according to some specific implementations, is shown.
[0047] Similar reference numerals and names in various figures indicate similar elements. Detailed Implementation
[0048] The following detailed description relates to specific exemplary embodiments of the disclosed subject matter. While the disclosed embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosed subject matter, this disclosure is not limited to the specific features of the particular exemplary embodiments described herein. Rather, the concepts and teachings disclosed herein can be implemented and applied in a variety of different forms and manners without departing from the spirit and scope of the invention. For example, while the disclosed specific embodiments focus on electrochromic windows (also known as smart windows), some of the systems, devices, and methods disclosed herein can be manufactured, applied, or used without excessive experimentation to combine or simultaneously combine with other types of optically switchable devices. Some other types of optically switchable devices include liquid crystal devices, suspended particle devices, and miniature blinds, etc. For example, some or all of these other optically switchable devices may be powered, driven, or otherwise controlled or integrated with one or more of the controller embodiments described herein. Additionally, in the following description, the phrases “operable as,” “adapted to,” “configured as,” “designed as,” “programmed as,” or “capable” may be used interchangeably where appropriate.
[0049] Exemplary electrochromic window architecture
[0050] Figure 1A cross-sectional side view of an exemplary electrochromic window 100 according to some specific embodiments is shown. An electrochromic window is an optically switchable window that includes an electrochromic device (ECD) for providing color or tinting. The exemplary electrochromic window 100 may be manufactured, configured, or otherwise provided as an insulating glass unit (IGU), and is also referred to IGU 100 hereinafter. This practice is commonly used, for example, because it is common and because when provided for installation in a building, it may be desirable to use the IGU as the basic construction for holding electrochromic panes (also referred to as “lites”). The IGU sheet or pane can be a single-substrate or multi-substrate construction, such as a laminate of two substrates. IGUs (particularly those with double or triple pane configurations) can provide many advantages over single pane configurations; for example, multi pane configurations can provide enhanced thermal insulation, noise insulation, environmental protection, and / or durability compared to single pane configurations. For example, the multi-pane configuration can also provide enhanced protection for the ECD, since the electrochromic film, along with associated layers and conductive interconnects, can be formed on the inner surface of the multi-pane IGU and protected by an inert gas filling the internal volume 108 of the IGU.
[0051] Figure 1 More specifically, an exemplary embodiment of the IGU 100 is shown, which includes a first pane 104 having a first surface S1 and a second surface S2. In some embodiments, the first surface S1 of the first pane 104 faces the external environment, such as the outdoors or the outside environment. The IGU 100 also includes a second pane 106 having a first surface S3 and a second surface S4. In some embodiments, the second surface S4 of the second pane 106 faces the internal environment, such as the interior environment of a home, building, or vehicle, or a room or compartment within a home, building, or vehicle.
[0052] In some implementations, each of the first pane 104 and the second pane 106 is transparent or translucent—at least for light in the visible spectrum. For example, each of panes 104 and 106 may be formed of a glass material, particularly architectural glass or other shatterproof glass materials, such as those based on silica (SO₄). xThe glass material is as follows. As a more specific example, each of the first pane 104 and the second pane 106 can be a soda-lime glass substrate or a float glass substrate. Such glass substrates may consist of, for example, about 75% silica (SiO2) along with Na2O, CaO, and several trace additives. However, each of the first pane 104 and the second pane 106 can be formed from any material having suitable optical, electrical, thermal, and mechanical properties. For example, other suitable substrates that can be used as one or both of the first pane 104 and the second pane 106 may comprise other glass materials as well as plastics, semi-plastics, and thermoplastics (e.g., poly(methyl methacrylate), polystyrene, polycarbonate, allyl diglyceride carbonate, SAN (styrene-acrylonitrile copolymer), poly(4-methyl-1-pentene), polyester, polyamide) or mirror materials. In some embodiments, each of the first pane 104 and the second pane 106 may be strengthened, for example, by tempering, heating, or chemical strengthening.
[0053] Typically, each of the first pane 104 and the second pane 106, as well as the entire IGU 100, is rectangular. However, in some other embodiments, other shapes may be possible and may be desired (e.g., circular, elliptical, triangular, curved, convex, or concave). In some specific embodiments, the length “L” of each of the first pane 104 and the second pane 106 may range from approximately 20 inches (in.) to approximately 10 feet (ft.), the width “W” of each of the first pane 104 and the second pane 106 may range from approximately 20 inches to approximately 10 feet, and the thickness “T” of each of the first pane 104 and the second pane 106 may range from approximately 0.3 millimeters (mm) to approximately 10 millimeters (although smaller and larger other lengths, widths, or thicknesses are possible and may be required depending on the needs of the specific user, manager, administrator, builder, architect, or owner). In examples where the thickness T of the substrate 104 is less than 3 mm, the substrate is typically laminated to a thicker additional substrate to protect the thin substrate 104. Additionally, while IGU 100 includes two panes (104 and 106), in some other embodiments, the IGU may include three or more panes. Furthermore, in some embodiments, one or more panes may themselves be a laminated structure of two, three, or more layers or sub-panes.
[0054] The first pane 104 and the second pane 106 are spaced apart from each other by a spacer 118, which is typically a frame structure to form an internal volume 108. In some embodiments, the internal volume is filled with argon (Ar), but in other embodiments, the internal volume 108 may be filled with another gas, such as another inert gas (e.g., krypton (Kr) or xenon (Xn)), another (non-precious) gas, or a mixture of gases (e.g., air). Filling the internal volume 108 with gases such as Ar, Kr, or Xn can reduce conductive heat transfer through the IGU 100 because these gases have low thermal conductivity and improve sound insulation due to their increased atomic weight. In some other embodiments, the internal volume 108 may be evacuated with air or other gases. The spacer 118 typically defines the height “C” of the internal volume 108; that is, the spacing between the first pane 104 and the second pane 106. Figure 1 In this drawing, the thicknesses of the ECD, sealant 120 / 122, and manifold 126 / 128 are not drawn to scale; these components are typically very thin but are exaggerated here for illustrative purposes only. In some embodiments, the spacing “C” between the first pane 104 and the second pane 106 ranges from approximately 6 mm to approximately 30 mm. The width “D” of the spacer 118 may range from approximately 5 mm to approximately 15 mm (but other widths may be possible and may be expected).
[0055] Although not shown in the cross-sectional view, spacer 118 is typically a frame structure formed around all sides of IGU 100 (e.g., the top, bottom, left, and right sides of IGU 100). For example, spacer 118 may be formed of foam or plastic material. However, in some other embodiments, spacer 118 may be formed of metal or other conductive material, such as a metal tube or channel structure with at least three sides, two sides for sealing to each substrate and one side for supporting and separating lites and serving as a surface 124 for applying sealant. First main seal 120 adheres to and hermetically seals the spacer 118 and the second surface S2 of the first pane 104. Second main seal 122 adheres to and hermetically seals the spacer 118 and the first surface S3 of the second pane 106. In some specific embodiments, each main seal 120 and 122 may be formed of an adhesive sealant, such as, for example, polyisobutylene (PIB). In some embodiments, the IGU 100 also includes an auxiliary seal 124 that hermetically seals the boundary of the entire IGU 100 surrounding the spacer 118. For this purpose, the spacer 118 can be inserted at a distance “E” from the edges of the first pane 104 and the second pane 106, where “E” can be in the range of approximately 4 mm to approximately 8 mm (but other distances may be possible and may be desired). In some embodiments, the auxiliary seal 124 may be formed of an adhesive sealant, such as a water-resistant polymeric material that provides structural support to the assembly, such as silicone, polyurethane, and similar structural sealants that form a waterproof seal.
[0056] exist Figure 1In the specific configuration and shape factor depicted, the ECD coating on surface S2 of substrate 104 extends around its entire periphery to spacer 118 and below it. This configuration is functionally ideal because it protects the edge of the ECD within the main sealant 120 and is aesthetically ideal because there is a monolithic ECD without any busbars or scribe lines within the inner periphery of spacer 118. Such configurations are described in U.S. Patent No. 8,164,818 (Attorney's File No. VIEWP006), published April 24, 2012, entitled "ELECTROCHROMIC WINDOW FABRICATION METHODS"; U.S. Patent Application No. 13 / 456,056 (Attorney's File No. VIEWP006X1), filed April 25, 2012, entitled "ELECTROCHROMIC WINDOW FABRICATION METHODS"; PCT Patent Application No. PCT / US2012 / 068817 (Attorney's File No. VIEWP036WO), filed December 10, 2012, entitled "THIN-FILM DEVICES AND FABRICATION"; and a patent application filed June 4, 2014, entitled "THIN-FILM DEVICES AND FABRICATION". The entire contents of U.S. Patent Application No. 14 / 362,863 entitled “FABRICATION” (Attorney’s File No. VIEWP036US) and PCT Patent Application No. PCT / US2014 / 073081 entitled “THIN-FILM DEVICES AND FABRICATION” (Attorney’s File No. VIEWP036X1WO), filed on December 13, 2014, are incorporated herein by reference for all purposes.
[0057] exist Figure 1In the specific embodiment shown, ECD 110 is formed on the second surface S2 of the first pane 104. In some other embodiments, ECD 110 may be formed on another suitable surface, such as the first surface S1 of the first pane 104, the first surface S3 of the second pane 106, or the second surface S4 of the second pane 106. ECD 110 includes an electrochromic (“EC”) stack 112, which itself may include one or more layers. For example, EC stack 112 may include an electrochromic layer, an ion-conducting layer, and a counter electrode layer. In some embodiments, the electrochromic layer is formed of one or more inorganic solid materials. The electrochromic layer may include one or more of a variety of electrochromic materials, or be formed of one or more of a variety of electrochromic materials, including electrochemical cathode or electrochemical anode materials. For example, a metal oxide suitable for use as an electrochromic layer may include tungsten oxide (WO3) and its doping agents. In some embodiments, the electrochromic layer may have a thickness of about 0.05 μm to about 1 μm.
[0058] In some embodiments, the counter electrode layer is formed of an inorganic solid material. The counter electrode layer typically includes one or more of a variety of materials or material layers that can serve as an ion reservoir when the EC device 110 is in, for example, a transparent state. In some embodiments, the counter electrode serves not only as an ion storage layer but also as an anode coloring agent. For example, as non-limiting examples, suitable materials for the counter electrode layer include nickel oxide (NiO) and nickel tungsten oxide (NiWO), and their doped forms, such as nickel tungsten tantalum oxide, nickel tungsten tin oxide, nickel vanadium oxide, nickel chromium oxide, nickel aluminum oxide, nickel manganese oxide, nickel magnesium oxide, nickel tantalum oxide, and nickel tin oxide. In some embodiments, the counter electrode layer may have a thickness of approximately 0.05 μm to approximately 1 μm.
[0059] When the EC stack 112 transitions between optical states, the ion-conducting layer serves as a medium for transporting ions (e.g., in an electrolyte manner) through it. In some embodiments, the ion-conducting layer has high conductivity for the associated ions of the electrochromic layer and the counter electrode layer, but also sufficiently low electronic conductivity to allow negligible electron transfer (electrical short circuit) to occur during normal operation. The thin ion-conducting layer with high ion conductivity enables rapid ion conduction and thus rapid switching for high-performance EC devices 110. In some embodiments, the thickness of the ion-conducting layer can be from about 1 nm to about 500 nm, more typically from about 5 nm to about 100 nm. In some embodiments, the ion-conducting layer is also an inorganic solid. For example, the ion-conducting layer can be formed from one or more silicates, silicon oxides (including silicon-aluminum oxides), tungsten oxides (including lithium tungstate), tantalum oxide, niobium oxide, lithium oxide, and borates. These materials can also be doped with various dopants, including lithium; for example, lithium-doped silicon oxides include lithium silicon-aluminum oxide, lithium phosphorus oxynitride (LiPON), etc.
[0060] In some other embodiments, the electrochromic layer and the counter electrode layer are formed adjacent to each other, sometimes in direct contact, without an ion-conducting layer between them, and then an ion-conducting material is formed in situ between the electrochromic layer and the counter electrode layer. Further description of suitable devices can be found in U.S. Patent No. 8,764,950, entitled *ELECTROCHROMIC DEVICES*, published July 1, 2014, by Wang et al., and U.S. Patent No. 9,261,751, entitled *ELECTROCHROMIC DEVICES*, published February 16, 2016, each of which is incorporated herein by reference in its entirety and is used for all purposes. In some specific embodiments, the EC stack 112 may also include one or more additional layers, such as one or more passive layers. For example, passive layers can be used to improve certain optical properties, provide moisture, or provide scratch resistance. These or other passive layers may also be used to hermetically seal the EC stack 112. Alternatively, various layers, including conductive layers (such as the first TCO layer 114 and the second TCO layer 116 described below), can be treated with anti-reflective or protective oxide or nitride layers.
[0061] The selection or design of the electrochromic and counter electrode materials typically controls the possible optical transitions. During operation, in response to a voltage generated across the thickness of the EC stack 112 (e.g., between the first TCO layer 114 and the second TCO layer 116), the electrochromic layer transfers or exchanges ions to or from the counter electrode layer to drive the electrochromic layer to the desired optical state. In some embodiments, a positive voltage is applied to the EC stack 112 (e.g., making the electrochromic layer more positive than the counter electrode layer) to transition the EC stack 112 to a transparent state. In some such embodiments, in response to the application of a positive voltage, the available ions in the stack are primarily located in the counter electrode layer. When the magnitude of the potential on the EC stack 112 decreases or when the polarity of the potential reverses, ions are transported back to the electrochromic layer through the ion-conducting layer, causing the electrochromic material to transition to an opaque state (or a "more colored," "darker," or "less transparent" state). Conversely, in some other embodiments using electrochromic layers with different properties, a negative voltage can be applied to the electrochromic layer relative to the counter electrode layer to make the EC stack 112 opaque. In such embodiments, when the magnitude of the potential on the EC stack 112 decreases or its polarity reverses, ions are transported back to the electrochromic layer through the ion-conducting layer, causing the electrochromic material to become transparent or "bleached" (or "less colored," "brighter," or "more transparent").
[0062] In some embodiments, the transfer or exchange of ions to or from the counter electrode layer also results in an optical transition within the counter electrode layer. For example, in some embodiments, the electrochromic layer and the counter electrode layer are complementary coloring layers. More specifically, in some such embodiments, the counter electrode layer becomes more transparent when or after ions are transferred into it, and similarly, the electrochromic layer becomes more transparent when or after ions are transferred out of it. Conversely, both the counter electrode layer and the electrochromic layer become less transparent when the polarity is switched or the potential decreases, and ions are transferred from the counter electrode layer into the electrochromic layer.
[0063] In a more specific example, in response to the application of an appropriate potential across the thickness of the EC stack 112, the counter electrode layer transfers all or part of its held ions to the electrochromic layer, thereby causing an optical transition in the electrochromic layer. In some such embodiments, for example, when the counter electrode layer is formed of NiWO, the counter electrode layer also optically transitions as it loses the ions that have been transferred to the electrochromic layer. When the charge is removed from the counter electrode layer made of NiWO (i.e., ions are transported from the counter electrode layer to the electrochromic layer), the counter electrode layer will transition in the opposite direction.
[0064] Typically, the transition of an electrochromic layer from one optical state to another can be caused by reversible ion insertion into the electrochromic material (e.g., via intercalation) and corresponding charge-balancing electron injection. In some cases, a portion of the ions responsible for the optical transition are irreversibly bound in the electrochromic material. Some or all of the irreversibly bound ions can be used to compensate for "blind charge" in the material. In some embodiments, suitable ions include lithium ions (Li+) and hydrogen ions (H+) (i.e., protons). In some other embodiments, other ions may be suitable. Lithium ions intercalate into, for example, tungsten oxide (WO 3-y (0<y≤~0.3)) causes tungsten oxide to change from a transparent state to a blue state.
[0065] The following description generally focuses on tinting transitions. One example of a tinting transition is a transition from a transparent (or "translucent", "bleached" or "least tinted") state to an opaque (or "fully darkened" or "fully tinted") state. Another example of a tinting transition is the reverse — a transition from an opaque state to a transparent state. Other examples of tinting transitions include transitions to various intermediate tint states, for example, a transition from a less tinted, brighter or more transparent state to a more tinted, darker or more opaque state, and vice versa. Each of these tint states, as well as the tinting transitions between them, may be characterized or described in terms of percent transmission. For example, a tinting transition can be described as changing from a current percent transmission (%T) to a target %T. Conversely, in some other instances, each tint state and the tinting transitions between them can be characterized or described in terms of percent tint; for example, changing from a current percent tint to a target percent tint.
[0066] However, while the following description generally focuses on hue states and tint transitions between hue states, other optical states and transitions may be realized in various embodiments. Therefore, references to hue states or tint transitions are intended to cover other optical states and transitions as appropriate and unless otherwise stated. In other words, optical states and optical state transitions will also be referred to herein as hue states and hue state transitions, respectively, but this is not intended to limit the optical states and state transitions achievable by the IGU 302. For example, such other optical states and state transitions may include states and state transitions related to various colors, color intensities (e.g., from light blue to dark blue and vice versa), reflectivity (e.g., from less reflective to more reflective and vice versa), polarization (e.g., from less polarized to more polarized and vice versa), and scattering density (e.g., from less scattering to more scattering and vice versa). Similarly, references to devices, control algorithms, or processes for controlling hue states (including inducing tint transitions and maintaining hue states) are also intended to include such other optical transitions and states. Additionally, the control provided to the optically switchable device with voltage, current or other electrical characteristics, as well as the functions or operations associated with such control, may also be described below as “driving” the device or the corresponding IGU, whether or not the driving involves a shading state transition or maintaining the current shading state.
[0067] ECD 110 typically includes a first conductive and a second conductive (or “conductive”) layer. For example, ECD 110 may include a first transparent conductive oxide (TCO) layer 114 adjacent to a first surface of EC stack 112 and a second TCO layer 116 adjacent to a second surface of EC stack 112. In some embodiments, the first TCO layer 114 may be formed on the second surface S2, EC stack 112 may be formed on the first TCO layer 114, and the second TCO layer 116 may be formed on EC stack 112. In some embodiments, the first TCO layer 114 and the second TCO layer 116 may each be formed from one or more metal oxides, including metal oxides doped with one or more metals. For example, suitable metal oxides and doped metal oxides may include indium oxide, indium tin oxide (ITO), doped indium oxide, tin oxide, doped tin oxide, fluorinated tin oxide, zinc oxide, zinc aluminum oxide, doped zinc oxide, ruthenium oxide, and doped ruthenium oxide, etc. Although these materials are referred to as TCOs in this document, the term encompasses both non-oxides and transparent and conductive oxides, such as certain thin-film metals and certain non-metallic materials, such as conductive metal nitrides and composite conductors, etc. In some embodiments, the first TCO layer 114 and the second TCO layer 116 are substantially transparent, at least within the wavelength range in which the EC stack 112 exhibits electrochromic properties. In some embodiments, both the first TCO layer 114 and the second TCO layer 116 may be deposited by physical vapor deposition (PVD) processes, including, for example, sputtering. In some embodiments, the first TCO layer 114 and the second TCO layer 116 may each have a thickness of approximately 0.01 micrometers (μm) to approximately 1 μm. The electronic conductivity of transparent conductive materials is typically significantly greater than that of electrochromic materials or counter electrode materials.
[0068] First TCO layer 114 and second TCO layer 116 are used to distribute charge on respective first and second surfaces of EC stack 112 to apply a potential (voltage) across the thickness of EC stack 112. For example, a first applied voltage can be applied to the first TCO layer, and a second applied voltage can be applied to the second TCO layer. In some embodiments, first bus 126 distributes the first applied voltage to first TCO layer 114 and second bus 128 distributes the second applied voltage to second TCO layer 116. In some other embodiments, one of first bus 126 and second bus 128 can ground a corresponding one of first TCO layer 114 and second TCO layer 116. In other embodiments, the load can float relative to the two TCOs. In various embodiments, in order to modify one or more optical properties of EC stack 112 and thus cause an optical shift, the controller can change one or both of the first and second applied voltages to cause a change in the amplitude and polarity of the effective voltage applied to EC stack 112. Ideally, the first TCO layer 114 and the second TCO layer 116 are used to uniformly distribute charge on their respective surfaces of the EC stack 112, with a relatively small ohmic potential drop from the outer region to the inner region of the respective surface. Therefore, it is generally desirable to minimize the sheet resistance of the first TCO layer 114 and the second TCO layer 116. In other words, it is generally desirable for each of the first TCO layer 114 and the second TCO layer 116 to behave as substantially equipotential layers across all portions of the respective layer. In this way, the first TCO layer 114 and the second TCO layer 116 can uniformly apply a potential across the thickness of the EC stack 112 to achieve a uniform optical transition of the EC stack 112.
[0069] In some embodiments, each of the first busbar 126 and the second busbar 128 is printed, patterned, or otherwise formed such that it is oriented along at least one boundary of the EC stack 112 along the length of the first pane 104. For example, each of the first busbar 126 and the second busbar 128 can be formed by depositing a conductive ink, such as silver ink, in the form of a line. In some embodiments, each of the first busbar 126 and the second busbar 128 extends along the entire length (or nearly the entire length) of the first pane 104, and in some embodiments, extends along more than one edge of the EC stack 112.
[0070] In some embodiments, the first TCO layer 114, EC stack 112, and second TCO layer 116 do not extend to the edge of the first pane 104. For example, laser edge removal (LED) or other operations can be used to remove portions of the first TCO layer 114, EC stack 112, and second TCO layer 116, such that these layers are separated from or embedded at a distance “G” from the corresponding edge of the first pane 104, which can be in the range of approximately 8 mm to approximately 10 mm (although other distances are possible and may be desirable). Additionally, in some specific embodiments, edge portions of the EC stack 112 and second TCO layer 116 along one side of the first pane 104 are removed to allow a first busbar 126 to be formed on the first TCO layer 114 to achieve conductive coupling between the first busbar 126 and the first TCO layer 114. A second busbar 128 is formed on the second TCO layer 116 to achieve conductive coupling between the second busbar 128 and the second TCO layer 116. In some specific implementations, the first busbar 126 and the second busbar 128 are formed in the area between the spacer 118 and the first window pane 104, such as Figure 1 As shown. For example, each of the first busbar 126 and the second busbar 128 can be inserted from the inner edge of the spacer 118 at least a distance “F”, which can be in the range of about 2 mm to about 3 mm (although other distances are possible and may be desirable). This arrangement can be advantageous for a variety of reasons, including, for example, concealing the busbars.
[0071] As mentioned above, the use of the IGU convention is merely for convenience. In practice, in some embodiments, the basic unit of an electrochromic window can be defined as a pane or substrate of transparent material on which an ECD is formed or otherwise arranged, and associated electrical connections are coupled to that pane or substrate (to drive the ECD). Therefore, the description of IGU in the following description does not necessarily include references to [other technologies / methods]. Figure 1 All components described in the IGU 100.
[0072] Exemplary control curves for driving optical conversion
[0073] Figure 2Exemplary control curves 200 according to some specific implementations are shown. Control curves 200 can be used to drive transitions in optically switchable devices (such as the ECD 110 described above). In some implementations, a window controller can be used to generate and apply control curves 200 to drive the ECD from a first optical state (e.g., a transparent state or a first intermediate state) to a second optical state (e.g., a fully tinted state or a more tinted intermediate state). To drive the ECD in reverse—from a more tinted state to a less tinted state—the window controller can apply a similar but reversed approach. For example, the control curve used to drive the ECD from a second optical state to a first optical state could be... Figure 2 The voltage control curve shown is a mirror image. In some other embodiments, the control curves for coloring and brightening can be asymmetrical. For example, the transition from a first more colored state to a second less colored state may take longer in some cases than the reverse transition; that is, the transition from the second less colored state to the first more colored state. In some other instances, the reverse transition may be true; that is, the transition from the second less colored state to the first more colored state may take longer. In other words, depending on the device structure and materials, bleaching or brightening is not necessarily simply the opposite of coloring or tinting. In fact, due to the difference in the driving forces of ion insertion and deintercalation in the electrochromic material, the ECD typically behaves differently for each transition.
[0074] In some implementations, control curve 200 is a voltage control curve implemented by changing the voltage supplied to the ECD. For example, Figure 2 The solid line in the figure represents the effective voltage V applied to the ECD during the color transition and subsequent maintenance. Eff In other words, the solid line can represent the voltage V applied to the two conductive layers of the ECD (e.g., the first TCO layer 114 and the second TCO layer 116 of the ECD 110). App1 and V App2 The relative difference. Figure 2 The dashed lines represent the corresponding current (I) through the device. In the illustrated example, the voltage control curve 200 includes four stages: the ramp-to-drive stage 202 for initiating the transition, the drive stage for continuing the drive transition, the ramp-to-hold stage, and the subsequent hold stage.
[0075] The characteristic of the ramp-to-drive stage 202 is the application of a voltage ramp, the magnitude of which increases from an initial value at time t0 to a maximum drive value V at time t1. Drive The transition from ramp to drive phase 202 can be defined by three drive parameters known or set by the window controller: the initial voltage at t0 (the current voltage on the ECD at the start of the transition), V... DriveThe value of the ramp (controlling the end of the optical state) and the duration of the applied ramp (determining the transition speed). Additionally or alternatively, the window controller can also set a target ramp rate, a maximum ramp rate, or a ramp type (e.g., linear ramp, second-degree ramp, or nth-degree ramp). In some applications, the ramp rate can be limited to avoid damaging the ECD.
[0076] The driving stage 204 is characterized by the application of a constant voltage V Drive The optical state ends (or is approximately reached) at time t2, starting at time t1 and ending at time t2. The ramp-to-hold phase 206 is characterized by the application of a voltage ramp, the magnitude of which is derived from the drive value V at time t2. Drive The minimum hold value V at time t3 is reduced. Hold In some specific implementations, the ramp-to-hold phase 206 can be defined by three drive parameters, either known or set by the window controller: drive voltage V Drive , holding voltage V Hold The window controller can also set the ramp rate or ramp type (e.g., linear ramp, second-degree ramp, or nth-degree ramp).
[0077] The characteristic of holding phase 208 is that a constant voltage V is applied starting at time t3. Hold Maintain voltage V Hold This is used to maintain the ECD in its final optical state. Therefore, a holding voltage V is applied. Hold The duration of leakage current I can coincide with the duration for which the ECD will be held in the final optical state. For example, due to non-ideal factors associated with the ECD, the leakage current I... Leak This can lead to a slow discharge of charge from the ECD. This discharge can cause a corresponding reversal of ions across the ECD, and thus a slow reversal of the optical transition. In such applications, the holding voltage V... Hold It can be continuously applied to offset or prevent leakage current. In some other specific implementations, the holding voltage V is maintained. Hold Periodically apply a "refresh" to the desired optical state, or in other words, bring the ECD back to the desired optical state.
[0078] refer to Figure 2 The voltage control curve 200 shown and described is merely one example of a voltage control curve suitable for certain specific implementations. However, in such implementations or in various other implementations or applications, many other options may be desired or suitable. These other curves can also be readily implemented using the controllers and optically switchable devices disclosed herein. For example, in some embodiments, a current curve may be applied instead of a voltage curve. In some such instances, a similar curve may be applied... Figure 2The current control curve for the current density is shown. In some other implementations, the control curve may have more than four stages. For example, the voltage control curve may include one or more overdrive stages. In one exemplary implementation, the magnitude of the voltage ramp applied during the first stage 202 may increase beyond the drive voltage V. Drive The overdrive voltage V is reached OD In some such implementations, the first stage 202 can be followed by a ramp stage 203, during which the applied voltage changes from the overdrive voltage V. OD Reduce to driving voltage V Drive In some other specific implementations of this kind, the voltage can be shifted to the drive voltage V. Drive Previously applied drive voltage V OD Relatively short duration.
[0079] Additionally, in some implementations, the applied voltage or current profile may be interrupted for a relatively short duration to provide an open-circuit state throughout the device. While this open-circuit state is effective, the actual voltage or other electrical characteristics can be measured, detected, or otherwise determined to monitor how far the optical transition has progressed and, in some cases, to determine whether a profile alteration is necessary. Such an open-circuit condition may also be provided during the holding phase to determine whether a holding voltage V should be applied. Hold Or maintain voltage V Hold Whether the value should be changed. Additional information relating to driving and monitoring optical transitions is provided in PCT patent application No. PCT / US14 / 43514, filed June 20, 2014, entitled “CONTROLLING TRANSITIONS IN OPTICALLY SWITCHABLE DEVICES,” which is incorporated herein by reference in its entirety and for all purposes.
[0080] Exemplary controller network architecture
[0081] In many cases, switchable light windows can form or occupy a large portion of a building's exterior wall. For example, switchable light windows can form a large portion of the walls, facades, and even roofs of office buildings, other commercial buildings, or residential buildings. In various implementations, a distributed network of controllers can be used to control the switchable light windows. Figure 3 A block diagram of an exemplary network system 300 is shown, which is operable to control multiple IGUs 302 according to some specific implementation. For example, each IGU 302 may be associated with the above reference. Figure 1The IGU 100 described is identical or similar. A primary function of the network system 300 is to control the optical state of the ECD (or other optically switchable device) within the IGU 302. In some embodiments, one or more windows in window 302 may be multi-band windows, for example, where each window contains two or more independently controllable ECDs or bands. In various specific implementations, the network system 300 may be used to control the electrical characteristics of the power signals supplied to the IGU 302. For example, the network system 300 may generate and communicate shading instructions (also referred to herein as “hue commands”) to control the voltage applied to the ECD within the IGU 302.
[0082] In some implementations, another function of the network system 300 is to acquire status information from the IGU 302 (hereinafter, "information" and "data" are used interchangeably). For example, the status information for a given IGU may include identification of the current hue state of the ECD within the IGU or information about said current hue state. The network system 300 is also used to acquire data from various sensors, whether these sensors are integrated on or within the IGU 302 or located in, on, or around the building, such as temperature sensors, photoelectric sensors (also referred to herein as light sensors), humidity sensors, airflow sensors, or occupancy sensors.
[0083] Network system 300 may include any suitable number of distributed controllers with various capabilities or functions. In some implementations, the functions and arrangement of the various controllers are defined hierarchically. For example, network system 300 includes multiple distributed window controllers (WC) 304, multiple network controllers (NC) 306, and a master controller (MC) 308. In some implementations, MC 308 may communicate with and control dozens or hundreds of NC 306. In various implementations, MC 308 issues high-level commands to NC 306 via one or more wired or wireless links 316 (hereinafter collectively referred to as "links 316"). Commands may include, for example, coloring commands to cause changes in the optical state of an IGU 302 controlled by a corresponding NC 306. Each NC 306 may then communicate with and control multiple WC 304 via one or more wired or wireless links 314 (hereinafter collectively referred to as "links 314"). For example, each NC 306 may control dozens or hundreds of WC 304. Each WC 304 can then communicate with, drive, or otherwise control one or more corresponding IGUs 302 via one or more wired or wireless links 312 (hereinafter collectively referred to as "links 312").
[0084] MC 308 can issue communications including coloring commands, status request commands, data (e.g., sensor data) request commands, or other instructions. In some embodiments, MC 308 may issue such communications periodically at certain predefined times of day (which may vary based on a day of the week or a day of the year) or based on the detection of a specific event, condition, or combination of events or conditions (e.g., determined by acquired sensor data, or based on the receipt of a request initiated by a user or application, or a combination of such sensor data and such request). In some specific embodiments, when MC 308 determines that a coloring state change has been caused in one or more IGUs 302, MC 308 generates or selects a coloring value corresponding to the desired coloring state. In some embodiments, the set of IGUs 302 is associated with a first protocol identifier (ID) (e.g., BACnet ID). MC 308 then generates and sends a communication—referred to herein as the “primary coloring command”—including the coloring value and the first protocol ID on link 316 via a first communication protocol (e.g., a BACnet compatible protocol). In some implementations, MC 308 addresses the primary shading command to a specific NC 306 that controls one or more specific WCs 304, which in turn controls a set of IGUs 302 to be shaded.
[0085] NC 306 receives a primary shading command including a shading value and a first protocol ID, and maps the first protocol ID to one or more second protocol IDs. In some implementations, each of the second protocol IDs identifies a corresponding one among WCs 304. NC 306 then sends an auxiliary shading command including the shading value to each identified WC 304 via link 314 using a second communication protocol. In some implementations, each WC 304 receiving the auxiliary shading command then selects a voltage or current distribution from its internal memory based on the shading value to drive its respective connected IGU 302 to a shading state consistent with the shading value. Each WC 304 then generates and provides a voltage or current signal to its respective connected IGU 302 via link 312 to apply the voltage or current distribution.
[0086] In some implementations, the various IGUs 302 can advantageously be divided into zones of EC windows, each zone containing a subset of IGUs 302. In some implementations, each zone of IGUs 302 is controlled by one or more corresponding NCs 306 and one or more corresponding WCs 304 controlled by these NCs 306. In some more specific implementations, each zone may be controlled by a single NC 306 and two or more WCs 304 controlled by the single NC 306. In other words, zones may represent logical groupings of IGUs 302. For example, each zone may correspond to a set of IGUs 302 in a specific location or area of a building, the IGUs being driven together based on their location. As a more specific example, consider a building with the following four sides: north, south, east, and west. Also consider a building with ten floors. In this illustrative example, each zone may correspond to a set of electrochromic windows 100 on a specific floor and one of the four sides. Alternatively, each zone may correspond to a group of IGUs 302 that share one or more physical characteristics (e.g., device parameters, such as size or age). In some other embodiments, the zones of IGUs 302 may be grouped based on one or more non-physical characteristics (e.g., security designation or business hierarchy) (e.g., IGUs 302 defining managerial offices may be grouped in one or more zones, while IGUs 302 defining non-manager offices may be grouped in one or more different zones).
[0087] In some such implementations, each NC 306 can address all IGUs 302 in each of one or more corresponding zones. For example, MC 308 can issue a primary hue command to NC 306 controlling the target zone. The primary hue command may contain an abstract identifier of the target zone (hereinafter also referred to as the “zone ID”). In some such implementations, the zone ID may be a first protocol ID, such as the protocol ID just described in the example above. In this case, NC 306 receives a primary hue command including a hue value and the zone ID, and maps the zone ID to a second protocol ID associated with a WC 304 within the zone. In some other implementations, the zone ID may be a higher-level abstraction than the first protocol ID. In this case, NC 306 may first map the zone ID to one or more first protocol IDs, and then subsequently map the first protocol ID to the second protocol ID.
[0088] Interaction between users or third parties and the network
[0089] In some implementations, MC 308 is coupled to one or more outward-facing networks 310 (hereinafter collectively referred to as "outward-facing networks 310") via one or more wired or wireless links 318 (hereinafter "links 318"). In some such implementations, MC 308 can transmit acquired status information or sensor data to or from the outward-facing network 310 to a remote computer, mobile device, server, or database accessible by the outward-facing network 310. In some implementations, various applications running within such remote devices, including third-party applications or cloud-based applications, can access data from or provide data to MC 308. In some implementations, authorized users or applications can transmit requests via network 310 to modify the hue state of various IGUs 302 to MC 308. In some specific implementations, MC 308 can first determine whether to grant the request (e.g., based on power considerations or based on whether the user has appropriate authorization) before issuing a hue command. MC 308 can then calculate, determine, select, or otherwise generate shading values and send them in the main shading command to enable shading state transitions in the associated IGU 302.
[0090] For example, a user can submit such a request from a computing device, such as a desktop computer, laptop computer, tablet computer, or mobile device (e.g., a smartphone). In some such implementations, the user's computing device can execute a client application capable of communicating with the MC 308 and, in some cases, with a main controller application running within the MC 308. In some other implementations, the client application can communicate with a separate application on the same or a different physical device or system than the MC 308, and the MC 308 then communicates with the main controller application to achieve the desired hue state modification. In some implementations, the main controller application or other separate application can be used to authenticate the user to authorize the request submitted by the user. In some implementations, the user can select the IGU 302 to be tinted and notify the MC 308 of the selection by entering the room number via the client application.
[0091] Alternatively or concurrently, in some implementations, a user's mobile device or other computing device may wirelessly communicate with various WC304 units. For example, a client application running on the user's mobile device may wirelessly transmit signals, including tone state control signals, to the WC304 to control the tone state of the individual IGUs 302s connected to the WC304. For instance, a user may use the client application to maintain or modify the tone state of an IGU 302 adjacent to a room occupied by the user (or to be occupied by the user or others in the future). Various wireless network topologies and protocols may be used to generate, format, or transmit such wireless communications (see below). Figure 6 (WC 600 described in more detail).
[0092] In some such implementations, control signals sent from a user's mobile device (or other computing device) to the corresponding WC 304 may override hue values previously received by the WC 304 from the corresponding NC 306. In other words, the WC 304 may provide the applied voltage to the IGU 302 based on control signals from the user's computing device rather than on hue values. For example, a control algorithm or rule set stored in and executed by the WC 304 may instruct one or more control signals from an authorized user's computing device to take precedence over hue values received from the NC 306. In some other cases, such as in high-demand situations, control signals such as hue values from the NC 306 may take precedence over any control signals received by the WC 304 from the user's computing device. In some other instances, the control algorithm or rule set may instruct that hue coverage from only a specific user or group or user class may be prioritized solely based on permissions granted to those users, and in some cases, other factors including time of day or the location of the IGU 302.
[0093] In some implementations, based on control signals received from an authorized user's computing device, MC 308 can use information about combinations of known parameters to calculate, determine, select, or otherwise generate hue values that provide typical lighting conditions required by the user, while also efficiently utilizing electricity in some cases. In other implementations, MC 308 can determine hue values based on preset preferences defined by a specific user requesting a change in hue state via a computing device. For example, the user may be required to enter a password or otherwise log in or be authorized to request a change in hue state. In this case, MC 308 can identify the user based on a password, security token, or an identifier based on a specific mobile device or other computing device. After identifying the user, MC 308 can then retrieve the user's preset preferences and use them alone or in combination with other parameters (e.g., power considerations or information from various sensors) to generate and send hue values for use in coloring the corresponding IGU 302.
[0094] Wall-mounted equipment
[0095] In some implementations, network system 300 may also include wall switches, dimmers, or other color temperature control devices. A wall switch typically refers to an electromechanical interface connected to the WC. The wall switch can transmit coloring commands to the WC, which can then be transmitted to the NC. Such devices are also collectively referred to below as "wall devices," although these devices are not necessarily limited to wall-mounted implementations (e.g., such devices can also be located in the ceiling or floor, or integrated into or within a desktop or conference table). For example, some or all offices, meeting rooms, or other rooms in a building may include such wall devices for controlling the color temperature of adjacent IGUs 302. For example, IGUs 302 adjacent to a particular room may be grouped into zones. Each wall device can be operated by an end user (e.g., the occupant of the corresponding room) to control the color temperature or other functions or parameters of the IGUs 302 adjacent to the room. For example, at certain times of day, adjacent IGUs 302 may be tinted to a dark state to reduce the light energy entering the room from the outside (e.g., to reduce AC cooling requirements). Now assume a user wishes to use the room. In various implementations, the user can operate the wall device to transmit control signals to change the hue state from a dark state to a brighter hue state.
[0096] In some implementations, each wall device may include one or more switches, buttons, dimmers, dials, or other physical user interface controls that allow a user to select a specific hue state or increase or decrease the current hue level of the IGU 302 in an adjacent room. Additionally or alternatively, the wall device may include a display with a touchscreen interface that allows a user to select a specific hue state (e.g., by selecting a virtual button, choosing from a drop-down menu, or by entering a hue level or hue percentage) or modify the hue state (e.g., by selecting a “darken” virtual button, a “lighten” virtual button, or by rotating a virtual dial or sliding a virtual bar). In some other implementations, the wall device may include a docking interface that allows a user to physically and communicatively dock a portable device such as a smartphone, multimedia device, tablet computer, or other portable computing device (e.g., an iPhone, iPod, or iPad manufactured by Apple Inc. in Cupertino, California). In such an implementation, the user can control the hue level by inputting to the portable device, which is then received by the wall device via the docking interface and subsequently transmitted to MC 308, NC 306, or WC 304. In such an implementation, the portable device may include an application for communicating with the API presented by the wall device.
[0097] For example, a wall device may send a request for a change in hue state to MC 308. In some implementations, MC 308 may first determine whether to grant the request (e.g., based on power considerations or based on whether the user has appropriate authorization / permission). MC 308 may then calculate, determine, select, or otherwise generate a hue value and send the hue value in a master hue command to enable a hue state transition in the adjacent IGU 302. In some such implementations, each wall device may be connected to MC 308 via one or more wired links (e.g., via a communication line such as CAN or Ethernet compatible cable or via powerline connection using powerline communication technology). In some other implementations, each wall device may be connected to MC 308 via one or more wireless links. In some other implementations, the wall device may be connected (via one or more wired or wireless connections) to an external network 310 (e.g., a customer-facing network), and then network 310 communicates with MC 308 via link 318.
[0098] In some implementations, MC 308 can identify the IGU 302 associated with the wall device based on previously programmed or discovered information linking the wall device to the IGU 302. In some specific implementations, a control algorithm or rule set stored in and executed by MC 308 can instruct one or more control signals from the wall device to take precedence over coloring values previously generated by MC 308. In some other instances, such as during high demand (e.g., high power demand), a control algorithm or rule set stored in and executed by MC 308 can instruct previously generated coloring values from MC 308 to take precedence over any control signals received from the wall device.
[0099] In some other implementations or instances, based on a hue state change request or control signal received from the wall device, the MC 308 can use information about a combination of known parameters to generate hue values that provide the desired lighting conditions for a typical user, while also efficiently utilizing electricity in some cases. In some other implementations, the MC 308 can generate hue values based on preset preferences defined by a specific user requesting a hue state change via the wall device. For example, the user may be required to enter a password or use a security token or key (e.g., IBUTTON or other 1-Wire devices) to gain access to the wall device. In this case, the MC 308 can identify the user based on the password, security token, or security key card, retrieve the user's preset preferences, and use the preset preferences alone or in combination with other parameters (e.g., power considerations or information from various sensors) to calculate, determine, select, or otherwise generate hue values for each IGU 302.
[0100] In some other embodiments, the wall device may send a hue state change request to the appropriate NC 306, which then transmits the request or communication based on the request to the MC 308. For example, each wall device may be connected to the corresponding NC 306 via one or more wired links, such as those just described for the MC 308, or via wireless links (such as those described below). In some other embodiments, the wall device may send a request to the appropriate NC 306, which then determines itself whether it overrides a primary hue command previously received from the MC 308 or a primary or secondary hue command previously generated by the NC 306 (as described below, in some embodiments the NC 306 may generate a hue command without first receiving a hue command from the MC 308). In some other embodiments, the wall device may transmit the request or control signal directly to the WC 304 controlling the adjacent IGU 302. For example, each wall device may be connected to the corresponding WC 304 via one or more wired links, such as those just described for the MC 308, or via wireless links (such as those referred to below). Figure 6 (Those described in WC 600).
[0101] In some specific implementations, NC 306 or MC 308 determines whether control signals from the wall device should take precedence over hue values previously generated by NC 306 or MC 308. As mentioned above, in some implementations, the wall device can communicate directly with NC 306. However, in some other implementations, the wall device can transmit a request directly to MC 308 or directly to WC 304, which then transmits the request to NC 306. In other implementations, the wall device can transmit a request to a customer-facing network (such as a network managed by the building owner or operator), and then the request (or a request based thereon) is passed directly or indirectly to NC 306 via MC 308. In some implementations, a control algorithm or rule set stored in and executed by NC 306 or MC 308 can instruct one or more control signals from the wall device to take precedence over hue values previously generated by NC 306 or MC 308. In some other cases, such as under high demand (e.g., high power demand), the control algorithm or rule set stored in the NC 306 or MC 308 and executed by the NC 306 or MC 308 may instruct the hue value previously generated by the NC 306 or MC 308 to take precedence over any control signal received from the wall device.
[0102] As described above with reference to MC 308, in some other embodiments, based on a hue state change request or control signal received from the wall device, NC 306 can use information about a combination of known parameters to generate hue values that provide desired lighting conditions for a typical user, while also efficiently utilizing electricity in some cases. In some other embodiments, NC 306 or MC 308 can generate hue values based on preset preferences defined by a specific user requesting a hue state change via the wall device. As described above with reference to MC 308, the user may be required to enter a password or use a security token or security key (e.g., IBUTTON or other 1-Wire devices) to gain access to the wall device. In this case, NC 306 can communicate with MC 308 to identify the user, or MC 308 can identify the user independently based on a password, security token, or security key card, retrieve the user's preset preferences, and use the preset preferences alone or in combination with other parameters (e.g., power considerations or information from various sensors) to calculate, determine, select, or otherwise generate hue values for each IGU 302.
[0103] In some implementations, MC 308 is coupled to an external database (or "data storage" or "data warehouse") 320. In some implementations, database 320 may be a local database coupled to MC 308 via a wired hardware link 322. In some other implementations, database 320 may be a remote database or a cloud-based database accessible by MC 308 via an internal private network or on an external network 310. In some implementations, other computing devices, systems, or servers may also access the database 320 to read data stored therein, for example, via the external network 310. Additionally, in some implementations, one or more control applications or third-party applications may also access the database to read data stored therein via the external network 310. In some cases, MC 308 stores in database 320 a record including all hue commands with corresponding hue values issued by MC 308. MC 308 may also collect and store status and sensor data in database 320. In this configuration, WC 304 can collect sensor data and status data from IGU 302 and transmit the sensor data and status data to the corresponding NC 306 via link 314, for communication with MC 308 via link 316. Alternatively or additionally, NC 306 or MC 308 can also be connected to various sensors, such as light, temperature, or floor space sensors within a building, and light or temperature sensors located on, around, or otherwise external to the building (e.g., on the roof of the building). In some embodiments, NC 306 or WC 304 can also send status or sensor data directly to database 320 for storage.
[0104] Integration with other systems or services
[0105] In some implementations, network system 300 may also be designed as an integrated and efficient energy control system for an entire building or building complex, in conjunction with modern heating, ventilation, and air conditioning (HVAC) systems, interior lighting systems, security systems, or electrical systems. Some implementations of network system 300 are suitable for integration with building management system (BMS) 324. A BMS is broadly a computer-based control system that can be installed in a building to monitor and control the building's mechanical and electrical equipment, such as HVAC systems (including furnaces or other heaters, air conditioners, blowers, and vents), lighting systems, power systems, elevators, fire protection systems, and security systems. A BMS may include hardware and associated firmware and software for maintaining the building's condition according to preferences set by occupants, building managers, or other administrators. The software may be based on, for example, Internet Protocol or open standards. BMS is typically used in large buildings where its function is to control the environment within the building. For example, a BMS can control lighting, temperature, carbon dioxide levels, and humidity within the building. To control the building environment, a BMS can turn various mechanical and electrical devices on and off according to rules or in response to conditions. For example, these rules and conditions can be selected or specified by the building manager or administrator. One function of a BMS can be to maintain a comfortable environment for the building's occupants while minimizing heating and cooling energy losses and costs. In some implementations, a BMS can be configured not only for monitoring and control but also to optimize the synergy between various systems, for example, to save energy and reduce building operating costs.
[0106] Additionally or alternatively, some specific implementations of the network system 300 are suitable for integrating smart thermostat services, alarm services (e.g., fire detection), security services, or other device automation services. An example of a home automation service is manufactured by Nest Labs in Palo Alto, California. ( (This is a registered trademark of Google Inc., Mountain View, California). As used herein, in some implementations, references to BMS may also include or be replaced with other such automated services.
[0107] In some implementations, the MC 308 and a separate automation service (e.g., the BMS 324) can communicate via an application programming interface (API). For example, the API can execute with a main controller application (or platform) within the MC 308, or with a building management application (or platform) within the BMS 324. The MC 308 and BMS 324 can communicate via one or more wired links 326 or via an external network 310. In some cases, the BMS 324 can transmit instructions for controlling the IGU 302 to the MC 308, which then generates a master tone command and sends it to the appropriate NC 306. In some implementations, the NC 306 or WC 304 can also communicate directly with the BMS 324 (whether via a wired / hardware link or wirelessly via a wireless data link). In some implementations, the BMS 324 can also receive data collected by one or more of the MC 308, NC 306, and WC 304, such as sensor data, status data, and associated timestamp data. For example, MC 308 can publish such data via network 310. In some other embodiments where such data is stored in database 320, BMS 324 can access some or all of the data stored in database 320.
[0108] Exemplary main controller
[0109] Figure 4 A block diagram of an exemplary master controller (MC) 400 according to some specific implementation is shown. For example, Figure 4 The MC400 can be used to execute the above reference. Figure 3 The network system 300 describes MC 308. As used herein, the expression "MC 400" also encompasses MC 308, and vice versa; in other words, the two expressions are used interchangeably. MC 400 may be implemented or implemented as one or more computers, computing devices, or computer systems (where appropriate, they are used interchangeably herein unless otherwise indicated). Furthermore, references to "MC 400" collectively refer to any suitable combination of hardware, firmware, and software used to implement the described functions, operations, processes, or capabilities. For example, MC 400 may refer to a computer executing a main controller application (also referred to herein as a "program" or "task").
[0110] like Figure 4As shown, MC 400 typically includes one or more processors 402 (hereinafter also collectively referred to as "processor 402"). Processor 402 may be or may include a central processing unit (CPU), such as a single-core or multi-core processor. In some embodiments, processor 402 may additionally include a digital signal processor (DSP) or a network processor. In some embodiments, processor 402 may also include one or more application-specific integrated circuits (ASICs). Processor 402 is connected to main memory 404, secondary memory 406, inward network interface 408, and outward network interface 410. Main memory 404 may include one or more high-speed memory devices, such as one or more random access memory (RAM) devices including dynamic RAM (DRAM) devices. Such DRAM devices may include, for example, synchronous DRAM (SDRAM) devices and dual data rate SDRAM (DDR SDRAM) devices (including DDR2 SDRAM, DDR3 SDRAM, and DDR4 SDRAM), thyristor RAM (T-RAM), and zero-capacitor RAM. And other suitable storage devices.
[0111] Auxiliary storage 406 may include one or more hard disk drives (HDDs) or one or more solid-state drives (SSDs). In some embodiments, storage 406 may store processor-executable code (or "programming instructions") for executing a multitasking operating system, for example, based on... The kernel-based operating system. In some other implementations, the operating system can be based on a similar... Or a Unix operating system, based on Microsoft The memory 406 may also store the operating system or other suitable operating system. The memory 406 may also store code executable by the processor 402 to execute the aforementioned main controller application, as well as code for executing other applications or programs. The memory 406 may also store status information, sensor data, or other data collected from the network controller, window controller, and various sensors.
[0112] In some implementations, MC 400 is a “headless” system; that is, a computer that does not include a display monitor or other user input devices. In some such implementations, an administrator or other authorized user can log in to or otherwise access MC 400 from a remote computer or mobile computing device via a network (e.g., network 310) to access and retrieve information stored in MC 400, write or otherwise store data in MC 400, and control various functions, operations, processes, or parameters performed or used by MC 400. In some other implementations, MC 400 may also include a display monitor and direct user input devices (e.g., one or more of a mouse, keyboard, and touchscreen).
[0113] In various implementations, the in-line network interface 408 enables the MC 400 to communicate with various distributed controllers, and in some implementations, also with various sensors. The in-line network interface 408 may collectively refer to one or more wired network interfaces or one or more wireless network interfaces (including one or more radio transceivers). Figure 3 In the context of the network system 300, MC 400 can implement MC 308, and the inward-facing network interface 408 can enable communication with the downstream NC 306 via link 316.
[0114] The external network interface 410 enables the MC 400 to communicate with various computers, mobile devices, servers, databases, or cloud-based database systems via one or more networks. The external network interface 410 can also collectively refer to one or more wired network interfaces or one or more wireless network interfaces (including one or more radio transceivers). Figure 3 In the context of network system 300, the external network interface 410 can communicate via link 318 with various computers, mobile devices, servers, databases, or cloud-based database systems accessible through the external network 310. As described above, in some embodiments, various applications executing within such remote devices, including third-party applications or cloud-based applications, can access data from or provide data to or via MC 400 to database 320. In some embodiments, MC 400 includes one or more APIs for facilitating communication between MC 400 and various third-party applications. Some exemplary embodiments of the APIs that MC 400 can implement are described in PCT patent application No. PCT / US15 / 64555 (Attorney General's File No. VIEWP073WO), filed December 8, 2015, entitled "MULTIPLE INTERACTING SYSTEMS AT ASITE," which is incorporated herein by reference in its entirety for all purposes. For example, such third-party applications may include various monitoring services, including thermostat services, alarm services (e.g., fire detection), security services, or other equipment automation services. Additional examples of monitoring services and systems can be found in PCT patent application No. PCT / US2015 / 019031 (Attorney’s File No. VIEWP061WO), filed March 5, 2015, entitled “MONITORING SITES CONTAINING SWITCHABLE OPTICAL DEVICES AND CONTROLLERS,” which is incorporated herein by reference in its entirety and for all purposes.
[0115] In some implementations, one or both of the inward-facing network interface 408 and the outward-facing network interface 410 may include a BACnet-compatible interface. BACnet is a communication protocol commonly used in building automation and control networks, defined by the ASHRAE / ANSI 135 and ISO 16484-5 standards. The BACnet protocol broadly provides a mechanism for computerized building automation systems and devices to exchange information, regardless of the specific services they perform. For example, BACnet is traditionally used to enable communication between heating, ventilation, and air conditioning (HVAC) control systems, lighting control systems, access or security control systems, fire detection systems, and their associated equipment. In some other implementations, one or both of the inward-facing network interface 408 and the outward-facing network interface 410 may include an oBIX (Open Building Information Interchange)-compatible interface or another RESTful Web service-based interface. Therefore, while the following description sometimes focuses on BACnet implementations, in other implementations, other protocols compatible with oBIX or other RESTful Web services may be used.
[0116] The BACnet protocol is typically based on a server-client architecture. In some implementations, MC 400 acts as a BACnet server when viewed from the external network 310. For example, MC 400 can publish various information through the external network interface 410 to various authorized computers, mobile devices, servers, or databases, or various authorized applications running on these devices. When viewed from the rest of the network system 300, MC 400 can act as a client. In some such implementations, NC 306 acts as a BACnet server, collecting and storing status data, sensor data, or other data acquired from WC 304, and publishing the acquired data so that MC 400 can access it.
[0117] The MC 400 can communicate with each NC 306 as a client using the BACnet standard data type. This BACnet data type can include analog values (AVs). In some such implementations, each NC 306 stores an array of AVs. The AV array can be organized by BACnet IDs. For example, each BACnet ID can be associated with at least two AVs; the first AV in the array can be associated with a coloring value set by the MC 400, and the second AV in the array can be associated with a status indication value from (or received) a corresponding WC 304. In some implementations, each BACnet ID can be associated with one or more WC 304s. For example, each WC 304 can be identified by a second protocol ID, such as a Controller Area Network (CAN) vehicle bus standard ID (hereinafter referred to as "CAN ID"). In such an implementation, each BACnet ID can be associated with one or more CAN IDs in the NC 306.
[0118] In some implementations, when MC 400 determines to color one or more IGUs 302, MC 400 writes a specific hue value into NC 306 to the AV associated with one or more corresponding WC 304s controlling the target IGU 302. In some more specific implementations, MC 400 generates a primary hue command that includes a BACnet ID associated with the WC 304 controlling the target IGU 302. The primary hue command may also include the hue value of the target IGU 302. MC 400 can use the network address of NC 306 to direct the transmission of the primary hue command through inward-facing interface 408 and the specific NC 306. For example, the network address of NC 306 may include an Internet Protocol (IP) address (e.g., an IPv4 or IPv6 address) or a Media Access Control (MAC) address (e.g., when communicating via Ethernet link 316).
[0119] The MC400 can calculate, determine, select, or otherwise generate hue values for one or more IGU302s based on combinations of parameters. For example, combinations of parameters may include time or calendar information, such as the time of day, a day of the year, or the time of a season. Additionally or alternatively, combinations of parameters may include solar calendar information, such as the sun's direction relative to the IGU 302. In some cases, the sun's direction relative to the IGU 302 may be determined by the MC400 based on time and calendar information, as well as known information about the geographical location of buildings on Earth and the orientation of the IGUs (e.g., in a northeast-down coordinate system). Combinations of parameters may also include external temperature (outside a building), internal temperature (in a room adjacent to the target IGU 302), or temperature within the internal volume of the IGU 302. Combinations of parameters may also include weather information (e.g., whether it is sunny, cloudy, overcast, rainy, or snowy). Parameters such as the time of day, a day of the year, or the sun's direction can be programmed into and tracked by the MC 308. Parameters such as external temperature, internal temperature, or IGU temperature can be obtained from sensors integrated on or inside the IGU 302, or in or around the building. Some information about the weather can also be obtained from these sensors. Additionally or alternatively, parameters such as time of day, time of year, sun direction, or weather can be provided or determined via network 310 from information provided by various applications, including third-party applications. Additional examples of algorithms, routines, modules, or other means for generating color values are described in U.S. Patent Application No. 13 / 722,969 (Attorney General's File No. VIEWP049), filed February 21, 2013, entitled "CONTROL METHOD FOR TINTABLE WINDOWS," and PCT Patent Application No. PCT / 2015 / 029675 (Attorney General's File No. VIEWP049X1WO), filed May 7, 2015, entitled "CONTROL METHOD FOR TINTABLE WINDOWS," both of which are incorporated herein by reference in their entirety and for all purposes.
[0120] Typically, each ECD within each IGU 302 is capable of coloring to virtually any hue state within a continuous hue spectrum defined by the material properties of the EC stack, in response to a suitable drive voltage applied to the EC stack. However, in some implementations, the MC 400 is programmed to select a hue value from a finite number of discrete hue values. For example, hue values can be specified as integer values. In some such implementations, the number of available discrete hue values can be 4, 8, 16, 32, 64, 128, or 256 or more. For example, a 2-bit binary number can be used to specify any one of four possible integer hue values, a 3-bit binary number can be used to specify any one of eight possible integer hue values, a 4-bit binary number can be used to specify any one of sixteen possible integer hue values, a 5-bit binary number can be used to specify any one of thirty-two possible integer hue values, and so on. Each hue value can be associated with a target hue level (e.g., expressed as a maximum hue, a maximum safe hue, or a maximum desired color or a percentage of available hues). For illustrative purposes, consider an example where the MC 400 selects from four available hue values: 0, 5, 10, and 15 (using 4 bits or more of binary numbers). Hue values 0, 5, 10, and 15 can be associated with target hue levels of 60%, 40%, 20%, and 4%, or 60%, 30%, 10%, and 1%, respectively, or another desired favorable or appropriate target hue level.
[0121] Exemplary network controller
[0122] Figure 5 A block diagram of an exemplary network controller (NC) 500 according to some specific implementation is shown. For example, Figure 5 The NC500 can be used to execute the above reference. Figure 3 The network system 300 describes NC306. As used herein, the expression "NC 500" also encompasses NC 306, and vice versa; in other words, the two expressions are used interchangeably. MC 500 may be implemented or embodied as one or more network components, network devices, computers, computing devices, or computer systems (used interchangeably herewhere appropriate, unless otherwise indicated). Furthermore, the expression "NC 500" collectively refers to any suitable combination of hardware, firmware, and software used to implement the described functions, operations, processes, or capabilities. For example, MC 500 may refer to a computer that executes a network controller application program (also referred to herein as a "program" or "task").
[0123] like Figure 5As shown, NC 500 typically includes one or more processors 502 (hereinafter collectively referred to as "processor 502"). In some embodiments, processor 502 may be implemented as a microcontroller or as one or more logic devices, including one or more application-specific integrated circuits (ASICs) or programmable logic devices (PLDs), such as field-programmable gate arrays (FPGAs) or complex programmable logic devices (CPLDs). If executed in a PLD, the processor can be programmed to be permanently formed in the PLD as a block of intellectual property (IP) or as an embedded processor core. In some other implementations, processor 502 may be or may include a central processing unit (CPU), such as a single-core or multi-core processor. Processor 502 is coupled to main memory 504, auxiliary memory 506, downstream network interface 508, and upstream network interface 510. In some embodiments, main memory 504 may be integrated with processor 502, for example, as a system-on-a-chip (SOC) package or in embedded memory within the PLD itself. In some other embodiments, the NC 500 may alternatively or additionally include one or more high-speed memory devices, such as one or more RAM devices.
[0124] Auxiliary memory 506 may include one or more solid-state drives (SSDs) storing one or more lookup tables or value arrays. In some embodiments, auxiliary memory 506 may store lookup tables that map a first protocol ID (e.g., BACnet ID) received from MC 400 to a second protocol ID (e.g., CAN ID), each protocol ID identifying a corresponding one in WC 304, and vice versa. In some embodiments, auxiliary memory 506 may additionally or alternatively store one or more arrays or tables. In some embodiments, such arrays or tables may be stored as comma-separated value (CSV) files or via another tabular structure file format. For example, each row of the file may be identified by a timestamp corresponding to a transaction with WC 304. Each row may include the coloring value (C) of IGU 302 controlled by WC 304 (e.g., as set by MC400 in a master coloring command); the status parameter (S) of IGU 302 controlled by WC 304; and the setpoint voltage (e.g., the effective applied voltage V). Eff The actual voltage level V measured, detected, or otherwise determined on the ECD within the IGU 302. Act The actual current level I determined by measurement, detection, or other means using the ECD within the IGU 302. ActThis includes various sensor data. In some implementations, each line of the CSV file may include status information for each and all WC 304s controlled by the NC 500. In some such implementations, each line may also include a CAN ID or another ID associated with each of the corresponding WC 304s.
[0125] In some implementations of the NC 500 within a computer executing network controller applications, auxiliary memory 506 may also store data for implementing a multitasking operating system, such as a system based on... The kernel is the processor-executable code (or "programming instructions") of the operating system. In some other implementations, the operating system can be based on a similar... Or a Unix operating system, based on Microsoft The memory 506 may also store code executable by the processor 502 to execute the aforementioned network controller application, as well as code for executing other applications or programs.
[0126] In various implementations, the downstream network interface 508 enables the NC 500 to communicate with the distributed WC 304, and in some implementations, also enables communication with various sensors. Figure 3 Within the context of the network system 300, NC 500 can execute NC 306, and downstream network interface 508 can enable communication with WC 304 via link 314. Downstream network interface 508 may collectively refer to one or more wired network interfaces or one or more wireless network interfaces (including one or more radio transceivers). In some embodiments, downstream interface 508 may include a CANbus interface, enabling NC 500 to distribute commands, requests, or other instructions to various WC 304s and receive responses including status information from CAN 304s according to the CANbus protocol (e.g., via the CANopen communication protocol). In some embodiments, a single CANbus interface can enable communication between NC 500 and tens, hundreds, or thousands of WC 304s. Additionally or alternatively, downstream interface 508 may include one or more Universal Serial Bus (USB) interfaces (or "ports"). In some such implementations, to enable communication via the CANbus communication protocol, a USB to CAN adapter can be used to couple the USB port of downstream interface 508 to a CANbus-compatible cable. In some such implementations, in order for the NC 500 to control even more WC 304s, a USB hub (e.g., with 2, 3, 4, 5, 10 or more hub ports) can be plugged into the USB port of the downstream interface 508. A USB to CAN adapter can then be plugged into each hub port of the USB hub.
[0127] The upstream network interface 510 enables the NC 500 to communicate with the MC 400, and in some implementations, also with various other computers, servers, or databases (including database 320). The upstream network interface 510 can also collectively refer to one or more wired network interfaces or one or more wireless network interfaces (including one or more radio transceivers). Figure 3 In the context of network system 300, upstream network interface 510 can enable communication with MC 308 via link 318. In some implementations, upstream network interface 510 can also be coupled to communicate with applications, including third-party applications and cloud-based applications, via external network 310. For example, in an implementation where NC 500 is implemented as a network controller application executing as a task within a computer, the network controller application can communicate directly with external network 310 via the operating system and upstream network interface 510. In some other implementations, NC 500 can be implemented as a task running on MC 308 and managing CANbus devices via a CANbus interface. In such implementations, communication can be supplemented or replaced by UNIX domain sockets (UDS) or other communication methods, such as shared memory or other non-IP communication methods, as a supplement to or alternative to TCP / IP or UDP / IP communication to MC.
[0128] In some implementations, the upstream interface 510 may include a BACnet-compatible interface, an oBIX-compatible interface, or another interface based on a RESTful web service. (See above reference...) Figure 4 In some specific implementations, the NC 500 acts as a BACnet server, collecting and storing status data, sensor data, or other data acquired from the WC 304, and publishing the acquired data so that the MC 400 can access it. In some implementations, the NC 500 can also directly publish the acquired data through network 310; that is, without first transmitting the data to the MC 400. The NC 500 also functions similarly to a router in some respects. For example, the NC 500 can act as a BACnet gateway for a CANBus network, receiving communications sent from the MC 400 according to the BACnet protocol, converting commands or messages from the BACnet protocol to the CANBus protocol (e.g., the CANopen communication protocol), and distributing commands or other instructions to various WC 304s according to the CANBus protocol.
[0129] BACnet is built on the User Datagram Protocol (UDP). In some other implementations, non-broadcast communication protocols can be used for communication between the MC 400 and NC 500. For example, Transmission Control Protocol (TCP) can be used as the transport layer instead of UDP. In some such implementations, the MC 400 can communicate with the NC 500 via an oBIX-compatible communication protocol. In some other implementations, the MC 400 can communicate with the NC 500 via a WebSocket-compatible communication protocol. Such TCP protocols can also allow the NC 500s to communicate directly with each other.
[0130] In various implementations, the NC 500 can be configured to perform protocol conversions (or "transformations") between one or more upstream protocols and one or more downstream protocols. As described above, the NC 500 can perform a conversion from BACnet to CANopen and vice versa. As another example, the NC 500 can receive upstream communication from the MC 400 via the oBIX protocol and convert the communication to CANopen or another CAN-compatible protocol for transmission to the downstream WC 304, and vice versa. In some wireless implementations, the NC 500 or MC 400 can also convert various wireless protocols, including those based on the IEEE 802.11 standard (e.g., WiFi), those based on the IEEE 802.15.4 standard (e.g., ZigBee, 6LoWPAN, ISA100.11a, WirelessHART, or MiWi), those based on the Bluetooth standard (including Bluetooth Classic, Bluetooth High Speed, and Bluetooth Low Energy protocols, as well as Bluetooth versions v4.0, v4.1, and v4.2), or those based on the EnOcean standard (ISO / IEC 14543-3-10). For example, the NC 500 can receive upstream communication from the MC 400 via the oBIX protocol and convert the communication to WiFi or 6LowPAN for transmission to the downstream WC 304, and vice versa. As another example, the NC 500 can receive upstream communication from the MC 400 via WiFi or 6LowPAN and convert the communication to CANopen for transmission to the downstream WC 304, and vice versa. In some other examples, the MC 400, instead of the NC 500, handles this conversion for transmission to the downstream WC 304.
[0131] As referenced above Figure 4When MC 400 determines to color one or more IGU 302s, MC 400 may write a specific coloring value into NC 500 to one or more corresponding WC 304s associated with the target IGU 302. In some embodiments, for this purpose, MC 400 generates a master color command communication, which includes a BACnet ID associated with the WC 304 of the target IGU 302. The master color command may also include the color value of the target IGU 302. MC 400 may use a network address (e.g., IP address or MAC address) to direct the transmission of the master color command to NC 500. In response to receiving such a master color command from MC 400 via upstream interface 510, NC 500 may unpack the communication, map the BACnet ID (or other first protocol ID) in the master color command to one or more CAN IDs (or other second protocol IDs), and write the color value from the master color command to the first of the respective AVs associated with each CAN ID.
[0132] In some implementations, the NC 500 then generates an auxiliary hue command for each WC 304 identified by the CAN ID. Each auxiliary hue command can be addressed to a corresponding WC 304 via the corresponding CAN ID. Each auxiliary hue command may also include a hue value extracted from the primary hue command. The NC 500 sends the auxiliary hue command to the target WC 304 via a second communication protocol (e.g., via the CANOpen protocol) through downstream interface 508. In some implementations, when a WC 304 receives such an auxiliary hue command, the WC 304 sends a status value back to the NC 500 indicating the status of the WC 304. For example, the hue status value may represent "coloring status" or "transition status," indicating that the WC is in the process of coloring the target IGU 302; an "active" or "complete" status indicates that the target IGU 302 is in the target hue state or the transition has been completed; or an "error status" indicates an error. After the status value has been stored in the NC 500, the NC 500 can publish status information or otherwise make the status information accessible to the MC 400 or various other authorized computers or applications. In some other implementations, the MC400 can request specific WC 304 status information from the NC 500 based on intelligence, scheduling policies, or user overlays. For example, intelligence can be within the MC 400 or within the BMS. Scheduling policies can be stored in the MC 400, in another storage location within the network system 300, or within a cloud-based system.
[0133] Integrated main controller and network controller
[0134] As described above, in some embodiments, the MC 400 and NC 500 can be implemented as the main controller application and the network controller application, respectively, executing within their respective physical computers or other hardware devices. In some alternative embodiments, each of the main controller application and the network controller application can be implemented within the same physical hardware. For example, each of the main controller application and the network controller application can be implemented as a separate task executing within a single computer device, which includes a multitasking operating system, such as those based on... The kernel of the operating system or other suitable operating system.
[0135] In some such integrated implementations, the host controller application and the network controller application can communicate via an application programming interface (API). In some specific implementations, the host controller and network controller applications can communicate via a loopback interface. For reference, a loopback interface is a virtual network interface implemented by the operating system that enables communication between applications running within the same device. Loopback interfaces are typically identified by IP addresses (usually in the 127.0.0.0 / 8 address block in IPv4, or the 0:0:0:0:0:0:0:1 address in IPv6 (also represented as ::1)). For example, the host controller application and the network controller application can each be programmed to send communications targeting each other to the IP address of the loopback interface. In this way, communication does not need to leave the computer when the host controller application sends communication to the network controller application, or vice versa.
[0136] In implementations where the MC 400 and NC 500 are respectively used as master controller and network controller applications, there are generally no restrictions on the available protocols applicable to communication between the two applications. This typically holds true regardless of whether the master controller application and the network controller application are executed as tasks within the same or different physical computers. For example, broadcast communication protocols such as BACnet, which limit communication with a network segment defined by switch or router boundaries, are not required. For instance, the oBIX communication protocol may be used for communication between the MC 400 and NC 500 in some implementations.
[0137] In the context of network system 300, each NC 500 can be implemented as an instance of a network controller application executing a task within a corresponding physical computer. In some implementations, at least one of the computers executing the instance of the network controller application also executes an instance of a master controller application to implement MC 400. For example, while only one instance of the master controller application can be actively executed in network system 300 at any given time, two or more computers executing the instance of the network controller application can install instances of the master controller application. In this way, redundancy is added so that the computer currently executing the master controller application is no longer a single point of failure for the entire system 300. For example, if the computer executing the master controller application fails or a particular instance of the master controller application stops running, another computer with the master network application instance installed can begin executing the master controller application to take over the other failed instance. In some other applications, more than one instance of the master controller application can be executed simultaneously. For example, the functionality, processes, or operations of the master controller application can be distributed to two (or more) instances of the master controller application.
[0138] Example window controller
[0139] Figure 6 A circuit diagram of an exemplary window controller (WC) 600 according to some specific implementations is shown. For example, Figure 6 The NC 600 can be used to execute the above reference. Figure 3 The network system 300 describes each WC in WC 304. As used herein, the expression "WC 600" also covers WC 304, and vice versa; in other words, the two expressions are used interchangeably. As stated above, WC 600 is generally operable and suitable for driving one or more connected optically switchable devices (such as those referenced above). Figure 1 The optical state transition or maintenance of the described ECD 110. In some specific implementations, one or more ECDs coupled to the WC 600 are configured in a corresponding IGU 602 (such as the one mentioned above). Figure 1 The WC 600 is described within the IGU 100. The WC 600 is also operable to communicate with a connected IGU 602, for example, to read data from or transmit data to the IGU 602.
[0140] WC 600 broadly includes processing unit 604. WC 600 also broadly includes power supply circuitry 606, drive circuitry 608, and feedback circuitry 610 (each depicted with thick dashed lines and gray shading). In the illustrated specific embodiment, WC 600 additionally includes communication circuitry 612. Each of drive circuitry 608, power supply circuitry 606, feedback circuitry 610, and communication circuitry 612 may include multiple individual circuit components, including integrated circuits (ICs). Each of the various components described in more detail below can be described as a “part” of a corresponding one of the aforementioned circuits 606, 608, 610, and 612. However, grouping components into corresponding circuits in circuits 606, 608, 610, and 612 is merely nominal and for the purpose of facilitating disclosure of the described specific embodiment. Therefore, the functions, capabilities, and limitations of the various described components are not intended to be defined by the corresponding groupings; rather, the functions, capabilities, and limitations of each individual component are defined only by the functions, capabilities, and limitations of those components themselves, and by the integration of those components with other components to which they are electrically connected or coupled.
[0141] WC 600 includes a first upstream interface (or interface group) 614 for coupling to an upstream cable assembly 616. For example, the upstream cable assembly 616 may perform the above-referenced... Figure 3 The network system 300 describes link 314. In some embodiments, the upstream cable group 616 includes at least four wires: two distribution lines and two communication lines. In some five-wire embodiments, the upstream cable group 616 additionally includes a system ground wire, such as building ground or earth ground (for practical purposes, an absolute ground that can measure all other voltages in the building). The upstream interface 614 may include a corresponding number of pins (not shown)—one pin connects each wire in the upstream cable group 616 to the WC 600. For example, a first pin can connect a first distribution line from the distribution lines of the upstream cable group 616 to a first power line 622 within the WC 600. A second pin can connect a second distribution line (e.g., a power loop) from the upstream cable group 616 to a second power line 624 within the WC 600. A third pin can connect a first communication line from the communication lines of the upstream cable group 616 to a first communication line 626 within the WC 600. The fourth pin of the pinout can connect the second communication line from the upstream cable group 616 to the second communication line 628 within the WC 600. In a specific implementation that includes a system ground wire, the fifth pin of the pinout can connect the system ground wire from the upstream cable group 616 to the system ground wire 630 within the WC 600.
[0142] The two distribution wires in the upstream cable assembly 616 can be implemented as two separate cables or configured together as, for example, a twisted pair cable. The first power line 622 carries the first supply voltage V. Sup1 Furthermore, the second power supply line 624 is a power supply circuit. In some specific implementations, the first supply voltage V... Sup1 This is a DC voltage with values ranging from approximately 5 volts (V) to 42V, and in one exemplary application, a value of 24V (although higher voltages may be desired and are possible in other specific implementations). In some other specific implementations, the first supply voltage V... Sup1 This can be a pulsed voltage power signal. As mentioned above, the second power line in power line 624 can be a power loop, also known as signal ground (or "common ground"). In other words, the voltage V on the second power line in the power line... Sup2 This could be a reference voltage, such as ground potential. In this specific implementation, the voltage of interest is the first supply voltage V. Sup1 With the second supply voltage V Sup2 The voltage difference between them, which is relative to the individual voltage V relative to system ground. Sup1 and V Sup2 The actual value is the opposite. For example, V Sup1 and V Sup2 The difference can range from approximately 5V to 42V, and in one exemplary application it is 24V. In specific implementations that include a system ground wire, the system ground wire can be implemented as a single cable or two distribution wires configured with the 3-wire cable described above.
[0143] The two communication lines in the upstream cable group 616 can also be implemented as two separate cables or configured together as a twisted-pair cable. In some other embodiments, the two communication lines can be bundled with two distribution wires, just described as a 4-wire cable, or bundled with two distribution wires and a system ground wire as a 5-wire cable. As described above, pins or other interconnections within the upstream interface 614 electrically connect the first and second communication lines in the upstream cable group 616 to the first communication line 626 and the second communication line 628 in the WC 600, respectively. The first communication line 626 and the second communication line 628, also collectively referred to herein as communication bus 632, can carry the first data signal Data1 and the second data signal Data2, respectively.
[0144] At different times or stages throughout the optical transformation cycle, or at other times, data signals Data1 and Data2 can transmit information from an upstream network controller (such as NC 306 or NC 400) to WC 600 or from WC 600 to the network controller. As an example of downstream communication, data signals Data1 and Data2 may include shading commands or other instructions (e.g., auxiliary shading commands as described above) sent from the network controller to WC 600. As an example of upstream communication, data signals Data1 and Data2 may include status information (such as the current shading state) or sensor data to be sent to the network controller. In some specific implementations, signals Data1 and Data2 are complementary signals, for example, forming a differential signal pair (also collectively referred to herein as differential signals).
[0145] In some implementations, the communication bus 632 is designed, deployed, and otherwise configured according to the Controller Area Network (CAN) vehicle bus standard. In terms of the Open Systems Interconnection (OSI) model, the physical (PHY) layer can be implemented according to the ISO 11898-2 CAN standard, and the data link layer can be implemented according to the ISO 11898-1 CAN standard. In some such implementations, the first data signal Data1 may refer to a high CAN signal (as it is typically referred to as the "CANH signal" in the CAN protocol), while the second data signal Data2 may refer to a low CAN signal ("CANL signal"). In some implementations, the WC 600 communicates with the upstream network controller via the communication bus 632 (and the communication lines connected in the upstream cable group 616) according to the CANopen communication protocol. In terms of the OSI model, the CANopen communication protocol implements the network layer and other layers above the network layer (e.g., the transport layer, session layer, presentation layer, and application layer). According to the CAN protocol, it is the difference between the CANH and CANL signal values that determines the value of the bit transmitted by the differential pair.
[0146] In some embodiments, the upstream cable group 616 is directly connected to the upstream network controller. In other embodiments, the upstream cable group 616 includes a set of branches connected to a trunk line containing corresponding distribution lines and communication lines (e.g., branching off from the trunk line). In some such latter embodiments, each of the plurality of WCs 600 may be connected to the same trunk line via a corresponding set of branches. In some such embodiments, each of the plurality of WCs 600 connected to the same trunk line may communicate with the same network controller via communication lines within the trunk line. In some embodiments, the distribution lines supplying power to the WCs 600 may also be connected to the same network controller to supply power to that network controller. In other embodiments, different sets of distribution lines may supply power to the network controller. In any case, the distribution lines supplying power to the WCs 600 may terminate at a power control panel or other power outlet.
[0147] WC 600 also includes a second downstream interface (or interface group) 618 for connection to a downstream cable assembly 620. For example, the downstream cable assembly 620 may perform the above-referenced... Figure 3 The network system 300 describes link 312. In some implementations, the downstream cable group 620 also includes at least four lines: two power distribution lines and two communication lines. The downstream interface 618 may also include a corresponding number of pins (not shown) – one pin connects each line in the downstream cable group 620 to the WC 600. For example, a first pin can connect a first power distribution line 633 from the downstream cable group 620 to a first power drive line 634 within the WC 600. A second pin can connect a second power distribution line 635 from the downstream cable group 620 to a second power drive line 636 within the WC 600. A third pin can connect a first communication line 637 from the downstream cable group 620 to a first communication line 638 within the WC 600. A fourth pin can connect a second communication line 639 from the downstream cable group 620 to a second communication line 640 within the WC 600. In a specific implementation that includes a fifth line, the fifth pin in the pin configuration can connect the fifth line 641 from the downstream cable group 620 to the fifth line 642 within the WC 600.
[0148] The two distribution wires 633 and 635 in the downstream cable assembly 620 can be implemented as two separate cables or configured together as, for example, a twisted pair cable. In some specific embodiments, the first distribution wire 633 carries a first applied voltage V. App1 And the second distribution wire 635 carries the second applied voltage V App2 In some specific implementations, for all intents and purposes, the first applied voltage V is... App1 Second applied voltage VApp2 It is a DC voltage signal. In some other specific implementations, the first applied voltage V App1 Second applied voltage V App2 This can be a pulsed voltage signal (e.g., a pulse width modulation (PWM) signal). In some specific implementations, the first applied voltage V App1 It can have values ranging from approximately 0V to 10V, and in some specific applications, values ranging from approximately 0V to 5V. In some specific implementations, the second applied voltage V App2 It can have values ranging from approximately 0V to -10V, and in some specific applications, values ranging from approximately 0V to -5V. In some other specific embodiments, the second distribution line 635 in the downstream cable group 620 can be a power supply loop, also known as signal ground or common ground. In other words, the voltage V on the second distribution line... App2 It can be a reference voltage, for example, a floating ground.
[0149] The first distribution wire 633 and the second distribution wire 635 in the downstream cable assembly 620 are supplied to each of one or more IGUs 602 controlled by the WC 600. More specifically, the first distribution wire 633 and the second distribution wire 635 are electrically connected (or coupled) to the busbar and conductive layer (e.g., to supply power to the electrochromic state and state transition of the corresponding ECD) Figure 1 The first bus 126 and the second bus 128 in the IGU 100, as well as the first TCO layer 114 and the second TCO layer 116. In some specific embodiments, the voltage of interest is the first applied voltage V. App1 With the second applied voltage V App2 The voltage difference between them, which is relative to the individual voltage V relative to system ground. App1 and V App2 The actual value is the opposite. For example, V App1 With V App2 The difference between them—referred to in this paper as the “effective applied voltage” V Eff Or simply applied voltage V Eff — In some applications, it can be in the range of approximately -10V to 10V, and in some specific applications, it can be in the range of approximately -5V to 5V, depending on various device parameters and drive parameters.
[0150] The two communication lines 637 and 639 in the downstream cable bundle 620 can also be implemented as two separate cables or configured together as a twisted pair cable. In some other embodiments, the two communication lines 637 and 639 can be bundled with the two distribution wires 633 and 635, which were just described as a 4-wire cable, or bundled with the two distribution wires and a fifth wire to form a 5-wire cable. As described above, pins or other interconnections within the downstream interface 618 electrically connect the first communication line 637 and the second communication line 639 in the downstream cable bundle 620 to the first communication line 638 and the second communication line 640 within the WC 600. The first communication line 638 and the second communication line 640, also collectively referred to herein as communication bus 644, can carry data signals Data3 and Data4, respectively.
[0151] At different times or stages throughout the transition cycle, or at other times, data signals Data3 and Data4 can transmit information from WC 600 to one or more connected IGUs 602, or from one or more IGUs 602 to WC 600. As an example of downstream communication, data signals Data3 and Data4 may include status request commands or other instructions to be sent to one or more IGUs 602. As an example of upstream communication, data signals Data3 and Data4 may include status information (such as the current coloring state) or sensor data sent from one or more IGUs 602 to WC 600. In some implementations, the communication bus 644 is designed, deployed, and otherwise configured according to a 1-wire device communication bus system protocol. In such a 1-wire implementation, communication line 638 is a data line and data signal Data3 conveys the data to be transmitted, while communication line 640 is a signal ground line and data signal Data4 provides a reference voltage, such as signal ground, relative to which data signal Data3 is measured or compared to recover the data of interest.
[0152] Exemplary connection architecture
[0153] In some embodiments, the downstream cable group 620 is directly connected to a single IGU 602. In other embodiments, the downstream cable group 620 includes a connector that connects the downstream cable group 620 to two or more IGU 602 via a corresponding cable group. Figure 7A diagram illustrates an exemplary connection architecture 700 for connecting a window controller to an IGU, according to some specific embodiments. In the illustrated embodiment, connection architecture 700 connects a WC 600 to an IGU 602 including an ECD 746 (only the end portions of the IGU 602 and ECD 746 are shown). Although only one IGU 602 is shown, as described above, connection architecture 700 can connect the WC 600 to multiple IGUs 602. To facilitate such multi-IGU implementations, a downstream cable bundle 620 can connect the WC 600 to a connector 748. In some embodiments, connector 748 electrically connects each of wires 633, 635, 637, 639, and box 641 within the downstream cable bundle 620 to multiple auxiliary cable bundles 7501-750. N The corresponding lines in each of them are 734, 736, 738, 740, and 742. In this way, a single WC 600 can supply power to multiple IGU 602s.
[0154] In the illustrated illustrative embodiment, IGU 602 includes a plug-in component 752 that facilitates connection of downstream cable bundle 620, or more specifically auxiliary cable bundle 7501, to IGU 602 and the ECD 746 therein. In some embodiments, the plug-in component 752 can be easily inserted into and removed from IGU 602 (e.g., for ease of manufacture, maintenance, or replacement). As shown, the plug-in component 752 includes an interface 754 (which may be similar to interface 618 of WC 600) for receiving distribution lines 734 and 736, communication lines 738 and 740, and a fifth line 742 (in embodiments including the fifth line). In some embodiments, the ends of lines 734, 736, 738, 740, and 742 may include connectors adapted for insertion into corresponding connection receivers within the interface 754. The plug-in component 752 is used to electrically connect distribution lines 734 and 736 to busbars 758 and 760, respectively. Busbars 758 and 760 are then electrically connected to the corresponding conductive layers on either side of the EC stack of ECD 746.
[0155] The plug-in component 752 includes a communication module 756 connected to transmit and receive data from the WC 600 via communication lines 738 and 740. In some embodiments, the communication module 756 may be implemented as a single chip. In some such embodiments, the communication module 756 may be implemented as a one-wire chip, which includes non-volatile memory, such as, for example, EEPROM (Electronic EPROM). 2EPROM, flash memory, or other suitable solid-state memory. Each communication module 756 may also include various processing, controller and logic functionalities, authentication capabilities, or other functionalities or capabilities. When implemented as a 1-wire chip, each communication module 756 can be identified by a unique 1-wire ID (e.g., a 48-bit serial number). An example of such a 1-wire chip suitable for some specific implementations is the DS28EC20, 20Kb 1-wire EPROM chip, supplied by Maxim Integrated Products, Inc., San Jose, California. In some other specific implementations, the communication module 756 may include a memory chip (including non-volatile memory and memory controller functionality) and a separate ID chip storing a unique ID (e.g., a 1-wire ID). Examples of functions and hardware that may be associated with such a 1-line chip are described in U.S. Patent Application No. 13 / 049,756 (Attorney’s File No. VIEWP007), filed March 16, 2011, entitled “MULTIPURPOSE CONTROLLER FOR MULTISTATE WINDOWS”, which is incorporated herein by reference in its entirety and for all purposes.
[0156] In some embodiments, various device parameters or drive parameters for a particular ECD 746 are programmed into and stored in a memory component within the communication module 756 (e.g., during or at the end of the manufacturing or production of the ECD or IGU, or during or after installation). For example, such pre-programmed device parameters for the ECD 746 may include length, width, thickness, cross-sectional area, shape, age, model, version number, or the number of previous optical transitions of the corresponding ECD 746 or associated with it (on which panes are formed or otherwise arranged). Pre-programmed drive parameters may include, for example, ramp-to-drive rate, drive voltage, drive voltage duration, ramp-to-hold rate, and holding voltage for each possible combination of the current shading state and the target shading state. In some embodiments, the processing unit 604 reads the device parameters and drive parameters before each shading state transition begins. Additionally or alternatively, in some embodiments, the processing unit 604 reads the device parameters and drive parameters when the corresponding IGU 602 is powered on and being debugged. The processing unit 604 may additionally or alternatively read device parameters and drive parameters periodically (such as daily).
[0157] In some other embodiments, the surface of the communication module 756 may additionally or alternatively have an identification (ID) etched or engraved thereon. For example, the ID may be etched or etched onto the communication module 756 during or after ECD production. In some embodiments, the ID is a lite ID of the lite (pane) on which the ECD is formed. Additionally or alternatively, the ID may include the IGU ID of the associated IGU 302. In some embodiments, the WC 304 will then optically or electronically read this information after it is connected to the ECD. In some such embodiments, the WC 304 may retrieve parameters such as length, width, thickness, cross-sectional area, shape, age, model, version number, etc., from the MC 308. For example, the MC 400 may have been previously programmed to store such parameters. In some other specific implementations, MC 400 may retrieve such parameters from the ECD / IGU producer via an external communication interface (e.g., interface 410) in advance or in response to a request for such parameters or related information from WC 304 or NC 306.
[0158] The number and size of the IGUs 602 that each WC 600 can drive are typically limited by the load on the WC 600. The load is typically limited by the voltage, current, or power requirements necessary to induce the desired optical transition in the IGUs 602 driven by the WC 600 within the desired time frame. Because the maximum load that a given WC 600 can drive is typically limited by the capabilities and safe operating range of the electrical components within the WC 600, or by the power carrying capacity limitations of the power drive lines 634 and 636 or the distribution lines 633 and 635, a trade-off may exist between the acceptable transition time and the number and size of the ECDs driven by each WC 600.
[0159] The power requirement necessary to induce the desired optical transition in an IGU 602 driven by a given WC 600 within the desired time frame is a function of the surface area of the connected IGU 602, and more specifically, a function of the surface area of the ECD within the IGU 602. This relationship can be non-linear; that is, the power requirement can increase non-linearly with the surface area of the ECD. This non-linearity can exist at least partially because the sheet resistance of the conductive layers (such as the first TCO layer 114 and the second TCO layer 116 of the IGU 100) of the electrochromic stack used to deliver the applied voltage to the ECD increases non-linearly with the distance across the length and width of the respective conductive layers. For example, driving a single 50ft… 2 ECD drives two 25ft 2 ECD requires more power. System or building-wide power considerations may also require that the power available to each WC 600 be limited to less than the power that the WC 600 can handle and supply to the connected IGU 602.
[0160] In some specific implementations, such as reference Figure 7 As described in the connection architecture 700, each IGU in the IGU 602 connected to the WC 600 may include its own corresponding plug-in component 752 and communication module 756. Each communication module 756 may include a corresponding 1-wire chip storing device parameters for the corresponding ECD. In some specific implementations, each IGU 602 connected in parallel receives the same voltage V. App1 and V App2 In some such specific implementations, it may generally be desirable or preferred that each IGU in the IGU 602 connected to a single WC600 has the same or similar device parameters (such as surface area), such that each ECD in the corresponding ECD responds to voltage V App1 and V App2 And behave in the same or similar manner. For example, it is generally expected that each IGU 602 connected to a given WC 600 will have the same coloring, both during transitions and during hold periods between transitions. However, in a specific implementation in which the IGU 602 have different device parameters, the processing unit 604 may compare or otherwise integrate the device parameters from each connected IGU 602 to generate a command signal V. Drive This results in the optimal or least harmful effective applied voltage V. Eff For example, the voltage is maintained within a safe but effective range for all connected IGU 602s.
[0161] In some other embodiments, a one-to-one relationship may exist between the number of WC 600s and IGU 602s; that is, each IGU 602 may be driven or otherwise controlled by a corresponding dedicated WC 600. In some such integrated embodiments, the WC 600 may be located within the IGU 602, for example, within a housing having a thin form factor within the internal volume of the IGU. In some other embodiments, the WC 600 may be positioned adjacent to the IGU 602, for example, concealed by a frame or eaves supporting the IGU 602. In some other embodiments, the WC 600 may be located at the lower internal boundary or an internal corner of the IGU 602, where the WC is not easily seen or noticed, but is still accessible to the installer or technician. For example, such a latter embodiment may be used for applications where easier access to the WC 600 is desired (e.g., for replacing, repairing, or mapping the WC 600).
[0162] Additionally, such embodiments are also desirable where the WC 600 may include an energy storage device (e.g., a rechargeable battery, battery pack, or supercapacitor), which can be easily replaced by a technician. For example, the IGU may include a docking module into which a battery can be inserted. In such cases, the docking module may be electrically connected to the WC 600 rather than directly to the battery. In embodiments where the WC 600 is integrated with the IGU 602, the WC 600 itself may include a docking module into which a battery can be inserted. In embodiments where the WC 600 is integrated with the IGU 602, the IGU 602 may still include a plug-in component 752 connected to the WC 600. In some other integration embodiments, the WC 600 may be directly connected to the busbar of the associated ECD. In such a latter integration embodiment, the communication module storing the device parameters of the ECD may be located within the WC 600, for example, in non-volatile memory within the WC 600. Further examples of the use of integrated window controllers and energy storage devices are described in U.S. Patent Application No. 14 / 951,410, filed November 24, 2015, entitled “SELF-CONTAINED EC IGU” (Attorney’s File No. VIEWP008X1US), and PCT Patent Application No. PCT / US16 / 41176, filed July 6, 2016, entitled “POWER MANAGEMENT FOR ELECTROCHROMIC WINDOW NETWORKS” (Attorney’s File No. VIEWP080WO), both of which are incorporated herein by reference in their entirety and for all purposes.
[0163] Processing unit 604
[0164] At a higher level, processing unit 604 communicates with the upstream network controller and controls the shading state of IGU 602 connected to WC 600. A primary function of processing unit 604 is to generate command signals V. DCmnd As will be described in more detail below, the command signal V DCmnd Provided to the drive circuit 608 for generating the applied voltage signal V App1 and V App2 The applied voltage signal is output from WC 600 to drive one or more IGU 602 controlled by WC 600. In various specific implementations, processing unit 604 can generate command signal V based on multiple different device parameters, drive parameters, input values, algorithms, or instructions. DCmnd For example, processing unit 604 can generate a command signal V based on a coloring command received from the upstream network controller. DCmndAs described above, the shading command may include shading values corresponding to the target shading state of the IGU 602 controlled by the WC 600.
[0165] In some implementations, in response to receiving a shading command, processing unit 604 initiates a shading transition in one or more of the IGUs 602 controlled by WC 600. In some implementations, processing unit 604 calculates, selects, determines, or otherwise generates a command signal V based on driving parameters (based on the shading values in the shading command) including the current shading state of the IGU 602 to be transitioned and the target shading state of the IGU 602. DCmnd The processing unit 604 can also generate command signals V based on other drive parameters. DCmnd Other driving parameters include, for example, ramp-to-drive rate, drive voltage, drive voltage duration, ramp-to-hold rate, and holding voltage for each possible combination of the current shading state and the target shading state. Other driving parameters may include parameters based on current or recent sensor data, such as indoor temperature, outdoor temperature, temperature within the internal volume of IGU 602 (or one or more panes in the panes), light intensity in a room adjacent to IGU 602, and light intensity outside IGU 602, as well as other suitable or desired parameters. In some embodiments, such sensor data may be provided to WC 600 via communication lines 626 and 628 via an upstream network controller. Additionally or alternatively, sensor data may be received from sensors located within or on various portions of IGU 602. In some such embodiments, sensors may be located within or otherwise coupled to a communication module (such as communication module 756) within IGU 602. For example, multiple sensors, including light sensors, temperature sensors, or transmittance sensors, may be connected via a 1-wire communication protocol. Figure 7 The same communication lines 739 and 741 shown are connected.
[0166] In some specific implementations, the processing unit 604 can also generate a command signal V based on device parameters associated with the ECD within the IGU 602. DCmnd As described above, the device parameters of the ECD may include length, width, thickness, cross-sectional area, shape, age, model, version number, or the number of previous optical transitions of the corresponding ECD or its associated (on which panes are formed or otherwise arranged) IGU 602. In some specific embodiments, the processing unit 604 is configured to track the number of shading transitions of each connected IGU 602.
[0167] In some specific implementations, the processing unit 604 generates the command signal V based on the voltage control curve. DCmnd For example, such as the references above. Figure 2The voltage control curve is described above. For example, processing unit 604 can use drive parameters and device parameters to select a voltage control curve from a predefined set of voltage control curves stored within processing unit 604 or in a memory accessible by the processing unit. In some embodiments, each set of voltage control curves is defined for a specific set of device parameters. In some embodiments, each voltage control curve in a given set of voltage control curves is defined for a specific combination of drive parameters. Processing unit 604 generates a command signal V. DCmnd This enables the drive circuit 608 to achieve the selected voltage control curve. For example, the processing unit 604 adjusts the command signal V. DCmnd This allows the drive circuit 608 to adjust the applied voltage signal V. App1 and V App2 More specifically, the drive circuit 608 adjusts the applied voltage signal V. App1 and V App2 This makes the effective voltage V applied to the ECD... Eff Track the voltage level indicated by the voltage control curve throughout the entire progression of the curve.
[0168] In some specific implementations, the processing unit 604 can also dynamically modify the command signal V based on the sensor data. DCmnd (Whether during the transition or during the hold period after the transition). As described above, such sensor data can be received from various sensors within or otherwise integrated with the connected IGU 602, or from other external sensors. In some such embodiments, the processing unit 604 may include intelligence (e.g., in the form of programmed instructions including rules or algorithms) that enables the processing unit 604 to determine how to modify the command signal V based on the sensor data. DCmnd In some other embodiments, sensor data received by the WC 600 from such sensors can be transmitted to the network controller, and in some instances, from the network controller to the main controller. In such embodiments, the network controller or main controller can modify the shading values of the IGU 602 based on the sensor data and transmit the modified shading commands to the WC 600. Additionally or alternatively, the network controller or main controller can receive sensor data from one or more other sensors outside the building, such as one or more light sensors located on the roof or facade of the building. In some such embodiments, the main controller or network controller can generate or modify shading values based on such sensor data.
[0169] In some specific implementations, the processing unit 604 may also base its processing on one or more feedback signals V received from the feedback circuit 610. Feed To dynamically generate or modify the drive signal VDrive For example, and as will be described in more detail below, the feedback circuit 610 can provide one or more voltage feedback signals V based on the actual voltage level detected on the ECD. OC (For example, as measured during a periodic open-circuit instance), one or more current feedback signals V are provided based on the actual current level detected by the ECD. Cur Alternatively, it can be based on the applied voltage signal V provided by the IGU 602 along the direction. App1 and V App2 The voltage drop detected or determined on the power transmission line is associated with one or more voltage compensation signals V. Comp .
[0170] Generally, processing unit 604 can be implemented using any suitable processor or logic device, including combinations of such devices capable of performing the functions or processes described herein. In some specific implementations, processing unit 604 is a microcontroller (also known as a microcontroller unit (MCU)). In some more specific applications, processing unit 604 may be a microcontroller specifically designed for embedded applications. In some specific implementations, processing unit 604 includes a processor core (e.g., a 200MHz processor core or other suitable processor core), program memory (e.g., 2018KB or other suitable non-volatile memory), random access memory (RAM) (e.g., 512KB or other suitable RAM), and various I / O interfaces. Program memory may include, for example, code executable by the processor core to implement the functions, operations, or procedures of processing unit 604.
[0171] In some implementations, RAM can store status information of the IGU 602 controlled by WC 600. RAM can also store device parameters for the ECD within the IGU 602. In other implementations, processing unit 604 can store such status information or device parameters in another memory device (e.g., a flash memory device) external to processing unit 604 but within WC 600. In some specific implementations, the I / O interface of processing unit 604 includes one or more CAN interfaces, one or more synchronous serial interfaces (e.g., 4-wire Serial Peripheral Interface (SPI) interfaces), and one or more inter-integrated circuit (I / O) interfaces. 2 C) Interface. An example of such a controller suitable for some specific implementations is the PIC32MZ2048ECH064 controller provided by Microchip Technology Inc., Chandler, Arizona.
[0172] exist Figure 6In the illustrated embodiment, WC 600 additionally includes a data bus transceiver 664. The data bus transceiver 664 is connected to the upstream interface 614 via a communication bus 632. The data bus transceiver 664 is also connected to the processing unit 604 via a communication bus 666. As described above, in some embodiments, the communication bus 632 is designed, deployed, and otherwise configured according to the CAN bus standard, which is a differential bus standard. In some embodiments, the communication bus 666 also conforms to the CAN bus standard and includes differential line pairs for transmitting differential signal pairs. Therefore, the data bus transceiver 664 may include two sets of differential ports: a first set of ports for connection to the communication bus 632 and a second set of ports for connection to the communication bus 666, which in turn connect to the CAN interface of the processing unit 604.
[0173] In various embodiments, data bus transceiver 664 is configured to receive data from a network controller (such as NC 500) via communication bus 666, process the data, and transmit the processed data to processing unit 604 via communication bus 632. Similarly, data bus transceiver 664 is configured to receive data from processing unit 604 via communication bus 666, process the data, and transmit the processed data to interface 614 via communication bus 632, and ultimately transmit it to the network controller via upstream cable assembly 616. In some such embodiments, data processing includes converting or translating data from a first protocol to a second protocol (e.g., from a CAN protocol (such as CANopen) to a protocol readable by processing unit 604, and vice versa). An example of such a data bus transceiver suitable for some embodiments is the SN65HVD1050 data bus transceiver supplied by Texas Instruments Inc., Dallas, Texas. In some other embodiments, processing unit 604 may include an integrated data bus transceiver or otherwise include the functionality of data bus transceiver 664, thereby making it unnecessary to include an external data bus transceiver 664.
[0174] Power supply circuit
[0175] At a higher level, the power supply circuit 606 is operable to receive power from power lines 622 and 624 and supply power to various components of the WC 600, including the processing unit 604, drive circuit 608, feedback circuit 610, and communication circuit 612. As described above, the first power line 622 receives the supply voltage V. Sup1 For example, a DC voltage with a value in the range of approximately 5V to 42V (relative to the supply voltage V). Sup2And in one exemplary application, it has a value of 24V (although higher voltages may be desired and are possible in other specific implementations). Also as mentioned above, the second power line 624 can be a power loop. For example, the voltage V on the second power line 624... Sup2 It can be a reference voltage, for example, a floating ground.
[0176] Power supply circuit 606 includes a function to reduce supply voltage V Sup1 At least one buck converter (also referred to herein as a "buck converter"). In an illustrated embodiment, power supply circuit 606 includes two buck converters: a first relative low power (LP) buck converter 668 and a second relative high power (HP) buck converter 670. The function of the LP buck converter 668 is to convert the supply voltage V... Sup1 Reduced to the first buck converter voltage V Dwn1 In some specific implementations, the voltage V after step-down conversion... Dwn1 It can have values in the range of approximately 0 to 5V, and in one exemplary application, it has a value of approximately 3.3V. The voltage V after buck conversion. Dwn1 It is provided to the processing unit 604 for powering the processing unit 604. An example of an LP buck converter suitable for some specific implementations is the TPS54240 2.5 Ampere (Amp) DC-DC buck converter supplied by Texas Instruments Inc., Dallas, Texas.
[0177] The HP step-down converter 670 converts the supply voltage V... Sup1 Reduced to the second buck converter voltage V Dwn2 An example of an HP buck converter suitable for some specific implementations is the TPS54561 5Amp DC-DC buck converter, supplied by Texas Instruments Inc., Dallas, Texas. In some specific implementations, the buck-converted voltage V... Dwn2 It can have values ranging from approximately 6V to 24V, and in one exemplary application, it has a value of approximately 6V. The voltage V after buck conversion. Dwn2 The voltage regulator 680 is provided as described below with reference to drive circuit 608. In some specific embodiments, the buck-converted voltage V will also be provided. Dwn2 The remaining parts within the WC 600 that require power to perform their respective functions are provided with power (but these connections are not shown to avoid making the illustration too complex and to avoid obscuring other parts and connections).
[0178] In some implementations, the HP buck converter 670 provides the buck-converted voltage V only when enabled (or indicated).Dwn2 For example, when or when processing unit 604 asserts the enable signal En. In some embodiments, the enable signal En is provided to the HP buck converter 670 via a Serial Peripheral Interface (SPI) interface bus 686. Although the SPI interface bus 686 may be described herein in the singular, SPI bus 686 may collectively refer to two or more SPI buses, each of which can be used to communicate with a corresponding component of the WC 600. In some embodiments, the processing unit asserts the enable signal En only when the WC 600 is in an "active mode," the opposite of a "sleep mode."
[0179] In some embodiments, the power supply circuit 606 also includes or is connected to an energy storage device (or “energy trap”) 672, such as a capacitive storage device, like a rechargeable battery (or battery pack) or a supercapacitor. For example, one example of a supercapacitor suitable for some embodiments may have a capacitance C of at least 400 farads at 0.4 watt-hours (Wh). S In some embodiments, the energy storage device 672 can be charged by a charger 674. In some such embodiments, the charger 674 can be powered by a supply voltage V. Sup1 Power supply. One example of such a charger suitable for some specific implementations is the LT3741 constant current, constant voltage, buck controller supplied by Linear Technology Corp. of Milpitas, California. In some specific implementations, charger 674 is further configured to supply power stored in energy storage device 672 to power line 622.
[0180] In some embodiments, the charger 674 may optionally or additionally be powered by one or more photovoltaic (or “solar”) cells. For example, such photovoltaic (PV) cells may be integrated onto or within an IGU 602 controlled by the WC 600, such as on one or more panes of the IGU. In some such embodiments, the power received via the PV cells may be regulated by a voltage regulator 676 before being supplied to the charger 674 and ultimately to the energy storage device 672. For example, the voltage regulator 676 may be used to increase or decrease the voltage of the power received from the PV cells. The voltage regulator 676 may also typically be used to regulate the power supplied by the PV cells, as such power fluctuates throughout the day, for example, to maintain the voltage of the power at a fixed level. In some embodiments, the power stored in the energy storage device 672 is released via the charger 674 when desired or needed. In some specific implementations, to prevent reverse drive (i.e., to ensure that power from energy storage device 672 or PV battery does not flow upstream through upstream cable assembly 616), power supply circuit 606 may be supplemented with an asymmetric conductor 678, such as a low-loss semiconductor diode, like a Schottky junction diode or a pn junction diode. The use of such diodes 678 in situations where the supply voltage V... Sup1 and V Sup2 One or more of the pulsed embodiments may be particularly advantageous. Further examples of the use of integrated PV cells are described in U.S. Patent Application No. 14 / 951,410 (Attorney’s File No. VIEWP008X1), filed November 24, 2015, entitled “SELF-CONTAINED ECIGU”, which is incorporated herein by reference in its entirety and for all purposes.
[0181] Integration of energy storage devices can be advantageous for a variety of reasons, whether such devices are included within a specific WC 600 (e.g., energy storage device 672) or otherwise distributed throughout the network system (e.g., network system 300). For example, the power circuit 606 within each WC 600 can supplement or increase the power supplied by the corresponding power lines 622 and 624 using power drawn from the energy storage device 672. Additionally or alternatively, energy storage devices external to the WC 600 can directly supply power to the distribution lines that distribute power throughout the network system to supply power to the WC 600. Such implementations can be particularly advantageous in high-demand instances where many IGU 602s will be simultaneously converted. Under lower demand conditions, normal power sources (e.g., power supplied by building sources) can recharge the energy storage devices. Further examples of the use of energy storage devices are described in U.S. Patent Application No. 14 / 951,410, filed November 24, 2015, entitled “SELF-CONTAINED EC IGU” (Attorney’s File No. VIEWP008X1), and PCT Patent Application No. PCT / US16 / 41176, filed July 6, 2016, entitled “POWERMANAGEMENT FOR ELECTROCHROMIC WINDOW NETWORKS” (Attorney’s File No. VIEWP080WO), both of which are incorporated herein by reference in their entirety and for all purposes.
[0182] Additionally or alternatively, in some implementations, the transitions of IGU 602 can be staggered. For example, MC 400 or NC 500 can issue coloring commands for subgroups of WC 600 at different times to keep the total power consumed by the network system (or a portion of the network system) at any given time below desired, safe, permissible, or maximum limits. In some other implementations, WC 304 can be programmed to delay their transitions via various parameters received from MC 400 or NC 500. For example, auxiliary coloring commands issued by NC 500 may also include a delay value that informs WC 400 to begin coloring changes after a time associated with that delay value has elapsed. As another example, auxiliary coloring commands issued by NC 500 may also include a time value that informs WC 400 to begin coloring changes when a time associated with that time value has been reached. In the latter two examples, the NC 500 can issue shading commands to the WC 304 approximately simultaneously or concurrently, while ensuring that the interleaving of the transformations is still achieved.
[0183] drive circuit
[0184] At a higher level, the drive circuit 608 is typically operable to receive a command signal V from the processing unit 604. DCmnd And based on the command signal V DCmnd Provide applied voltage signal V App1 and V App2 This is used to drive the connected IGU 602. The drive circuit 608 includes receiving a buck-converted voltage V from the HP buck converter 670 in the power supply circuit 606. Dwn2 Voltage regulator 680. Voltage regulator 680 regulates, adjusts, or otherwise transforms voltage V. Dwn2 Based on command signal V DCmnd To provide (or "generate") the first regulated voltage signal V P1 Second regulated voltage signal V P2 In some specific implementations, voltage regulator 680 is a buck-boost converter; that is, voltage regulator 680 can be used as a buck converter to reduce voltage V. Dwn2 And it can be used as a boost converter to increase the input voltage V. Dwn2 Whether the voltage regulator 680 acts as a buck converter or a boost converter depends on the command signal V. DCmnd For example, the values for buck conversion or boost conversion, respectively. In some more specific embodiments, the voltage regulator 680 is a synchronous buck-boost DC-DC converter. In some such embodiments, the regulated voltage signal V is viewed from the IGU 602, and specifically from the ECD within the IGU 602. P1 and V P2 It is a DC signal with an effective fixed amplitude.
[0185] As described in more detail above, the processing unit 604 can generate a command signal V based on multiple different parameters, input values, algorithms, or instructions. DCmnd In some specific implementations, the processing unit 604 generates the command signal V in the form of a digital voltage signal. DCmnd In some such implementations, the drive circuit 608 may be additionally included for transmitting the digital command signal V. DCmnd Converted to analog command voltage signal V ACmnd The digital-to-analog converter (DAC) 682 is described. In some embodiments, the DAC 682 may be external to the processing unit 604, while in other embodiments, the DAC 682 may be internal to the processing unit 604. In such embodiments, the voltage regulator 680 is more specifically based on a command voltage signal V. ACmnd To generate the regulated voltage signal V P1 and V P2An example of a DAC applicable to some specific implementations is the AD5683R DAC from Analog Devices Inc. in Norwood, Massachusetts.
[0186] In some specific implementations, the voltage signal V is adjusted. P1 and V P2 This is a rectangular wave (or "pulse") DC signal, such as a voltage signal modulated by pulse width modulation (PWM). In some such implementations, the voltage regulator 680 includes an H-bridge circuit to generate a regulated voltage signal V. P1 and V P2 In some specific implementations of this kind, the voltage signal V is adjusted. P1 and V P2 Each of them has the same frequency. That is, in the regulated voltage signal V P1 V P2 In each of these, the time interval from the start of the current pulse to the start of the next pulse has the same duration. In some specific implementations, the voltage regulator 680 is operable to modify the corresponding voltage signal V. P1 and V P2 The duty cycle of the first voltage signal V is adjusted so that the corresponding duty cycles are not equal. In this way, although the first voltage signal V is adjusted... P1 The amplitude (or "magnitude") of the pulse can be equal to that of the second regulated voltage signal V. P2 The magnitude of the pulse, but from the perspective of the corresponding busbar and conduction layer of the ECD in the IGU 602, the first regulated voltage signal V P1 Second regulated voltage signal V P2 Each of these can have a different effective DC voltage value. However, in some other implementations, the voltage regulator 680 can additionally or alternatively modify the voltage signal V. P1 and V P2 The corresponding value of the pulse.
[0187] For example, consider an application where the voltage signal V is regulated. P1 and V P2 Each of the pulses in the series has an amplitude of 5V, but the first voltage signal V... P1 The second voltage signal V has a 60% duty cycle. P2 It has a 40% duty cycle. In this type of application, it is powered by a regulated voltage signal V. P1 and V P2 The effective DC voltage provided by each of these can be approximated as the product of the corresponding pulse amplitude and the fraction of the duty cycle occupied by the corresponding pulse. For example, from the first voltage signal V... P1 The effective DC voltage provided can be approximated as 3V (the product of 5V and 0.6), while the voltage provided by the second voltage signal V is...P2 The provided effective voltage can be approximated as 2V (the product of 5V and 0.4). In some specific implementations, the first voltage signal V P1 The duty cycle and the second voltage signal V P2 Their duty cycles are complementary. For example, as in the example just provided, if the first voltage signal V P1 With a duty cycle of X%, the second voltage signal V P2 The duty cycle can be Y%, where Y% = 100% - X%. In some such implementations, the first voltage signal V P1 The duration of the "on" signal can be related to the second voltage signal V. P2 The durations of the "disconnection" coincide, and similarly, the first voltage signal V P1 The duration of the "disconnection" can be related to the second voltage signal V. P2 The "on" durations overlap. In some other implementations, the duty cycles do not necessarily have to be complementary; for example, the first voltage signal V... P1 It can have a 50% duty cycle, while the second voltage signal V P2 It can have a 15% duty cycle.
[0188] As described above, in some specific implementations, from the perspective of IGU 602, and specifically from the ECD within IGU 602, the regulated voltage signal V P1 and V P2 It is a DC signal with an effective fixed amplitude. For another such embodiment, the voltage regulator 680 may also include one or more electronic filters, and specifically, one or more passive filter components, such as one or more inductors. Such filters or filter components can first smooth and then provide a regulated voltage signal V. P1 and V P2 To ensure the regulated voltage signal V P1 and V P2 It is a DC signal with an effective fixed amplitude. To further promote the regulated voltage signal V... P1 and V P2 Smoothing, in some specific implementations, voltage signal V P1 and V P2 The frequency of the pulses can be greater than or equal to 1 kilohertz (kHz). For example, as those skilled in the art will understand, the higher the frequency of the voltage oscillation applied to a conductor, the less capable the charge in the conductor is of responding to the voltage oscillation. Furthermore, the greater the inductance of the inductor, the smoother the voltage oscillation provided by the inductor.
[0189] In some implementations, the voltage regulator 680 may advantageously operate in burst mode to reduce the power consumption of the WC600 over time. In burst operation mode, the voltage regulator 680 automatically enters and exits burst mode to minimize its power consumption. An example of such a voltage regulator suitable for some implementations is the LTC3112 15V, 2.5Amp Synchronous Buck-Boost DC / DC Converter, supplied by Linear Technology Corp., Milpitas, California.
[0190] In some specific implementations, the voltage signal V is adjusted. P1 and V P2 These are the applied voltage signal V App1 and V App2 In some specific implementations of this kind, the voltage signal V is adjusted. P1 With V P2 The difference between them is the effective voltage V. Eff In some specific implementations, in order to achieve the lightening / shading transition, the processing unit 604 generates a command signal V. DCmnd This enables the voltage regulator 680 to provide a positive effective voltage V. Eff In order to achieve the darkening color transition, the processing unit 604 generates a command signal V. DCmnd This enables the voltage regulator 680 to provide a negative effective voltage V. Eff Conversely, in some other specific implementations involving different electrochromic layers or counter electrode layers, by providing a positive effective voltage V Eff This achieves the darkening shading transition by providing a negative effective voltage V. Eff To achieve the lightening and color transformation.
[0191] Regardless of the method, the voltage regulator 680 can provide a positive effective voltage V. Eff By increasing the duty cycle V of the first voltage signal P1 Alternatively, by reducing the second voltage signal V P2 The duty cycle makes the first voltage signal V P1 The duty cycle is greater than that of the second voltage signal V. P2 The duty cycle, and therefore, the first applied voltage signal V App1 The effective DC voltage is greater than the second applied voltage signal V. App2 The effective DC voltage. Similarly, voltage regulator 680 can provide a negative effective voltage V. Eff By reducing the first voltage signal V P1 The duty cycle or by increasing the second voltage signal V P2 The duty cycle makes the first voltage signal V P1The duty cycle is less than that of the second voltage signal V. P2 The duty cycle, and therefore, the first applied voltage signal V App1 The effective DC voltage is less than the second applied voltage signal V. App2 The effective DC voltage.
[0192] In some other specific implementations (including) Figure 6 In the specific implementation illustrated, the drive circuit 608 further includes a polarity switch 684. The polarity switch 684 receives two regulated voltage signals V from the voltage regulator 680. P1 and V P2 And output the applied voltage signal V to power lines 634 and 636 respectively. App1 and V App2 The polarity switch 482 can be used to switch the effective voltage V. Eff The polarity switches from positive to negative, and vice versa. Similarly, in some implementations, the voltage regulator 680 can increase the first voltage signal V. P1 The duty cycle or by reducing the second voltage signal V P2 Duty cycle relative to V P2 Increase V P1 The value of V, and therefore increases V. Eff The magnitude of the voltage. Similarly, the voltage regulator 680 can reduce the first voltage signal V. P1 The duty cycle or by increasing the second voltage signal V P2 Duty cycle relative to V P2 Decrease V P1 The magnitude of V, and therefore decreases V. Eff The value of.
[0193] In some other specific implementations, the second voltage V P2 It can be signal ground. In this specific implementation, the second voltage V P2 It can remain fixed or float during the transition and in the time between transitions. In such a specific implementation, the voltage regulator 680 can increase or decrease the first voltage signal V. P1 The duty cycle is used to increase or decrease V. P1 The value of V, and thus increase or decrease V. Eff The magnitude of the voltage. In some other such embodiments, the voltage regulator 680 can adjust or not adjust the first voltage signal V. P1 Directly increase or decrease the first voltage signal V under the condition of duty cycle P1 The amplitude of V is used to increase or decrease P1 The value of V, and thus increase or decrease V. Eff The magnitude of the signal. In fact, in this latter specific implementation, the first voltage signal V... P1It can be a fixed DC signal instead of a pulse signal.
[0194] In a specific implementation including polarity switch 684, the second voltage signal V P2 It can be signal ground, and the first voltage signal V P1 It can always be relative to the second voltage signal V P2 The positive voltage. In such a specific implementation, the polarity switch 684 may include two configurations (e.g., two electrical configurations or two mechanical configurations). The processing unit 604 can be connected via, for example, a control signal V provided through the SPI bus 686. Polar The polarity switch 684 is controlled to be in a specific configuration. For example, the processing unit 604 can select a first configuration when implementing a brightening transition and a second configuration when implementing a darkening transition. For example, when the polarity switch 684 is in the first configuration, the polarity switch can output a voltage signal V relative to the second applied voltage signal. App2 The first applied voltage signal V is positive App1 Conversely, when the polarity switch 684 is in the second configuration, the polarity switch can output a voltage signal V relative to the second applied voltage signal. App2 The first applied voltage signal V is negative. App1 .
[0195] In some specific implementations, when in the first configuration, the polarity switch 684 transmits a first voltage signal V. P1 As the first applied voltage signal V App1 And transmit the second voltage signal V P2 As the second applied voltage signal V App2 This generates a positive effective voltage V. Eff In some specific implementations, when in the second configuration, the polarity switch 684 transmits the first voltage signal V. P1 As the second applied voltage signal V App2 And transmit the second voltage signal V P2 As the first applied voltage signal V App2 This generates a negative effective voltage V. Eff In some implementations, the polarity switch 684 may include an H-bridge circuit. According to V... Polar The value of the H-bridge circuit allows it to operate in either the first or second configuration. An example of a polarity switch suitable for some specific implementations is the IRF7301 HEXFET PowerMOSFET supplied by International Rectifier Corp., San Jose, California.
[0196] In some specific implementations, when from a positive voltage V Eff Switch to negative voltage V EffOr conversely, the polarity switch 684 can be configured to switch from a first conduction mode to a high-impedance mode and then to a second conduction mode, or vice versa. For illustrative purposes, consider the first regulated voltage V. P1 An instance where the polarity switch 684 is in a positive holding value and in a first configuration. As described above, in some specific implementations, the polarity switch 684 transmits V P1 As the first applied voltage V App1 This generates a first applied voltage V that is also in a positive holding value. App1 For the sake of simplicity, let's assume V. P2 and V App2 Both are signal grounded. The result will be an effective applied voltage V that is in a positive holding value. Eff Now consider that processing unit 604 is initiating a process that will result in an effective applied voltage V. Eff A color transition ending in a negative hold value. In some implementations, to achieve the color transition, processing unit 604 adjusts the command signal V based on the negative ramp-to-drive curve. DCmnd So that the voltage regulator 680 reduces the voltage V P1 The value of the quantity. In some specific implementations, when the voltage V P1 When the value of the signal reaches a threshold close to zero (e.g., 10 millivolts (mV)), the processing unit 604 will switch the polarity switching signal V. Polar The value is changed from the first value to the second value so that the polarity switch 684 switches from the positive conduction mode (the first configuration described above) to the high impedance mode.
[0197] When in high-impedance mode, polarity switch 684 does not transmit V. P1 Conversely, the polarity switch 684 can output V based on predefined calculations or estimates. App1 (or V) App2 The value of ) is also displayed. Meanwhile, the voltage regulator 680 continues to adjust V. P1 The value of V decreases to zero. P1 When the value reaches zero, the voltage regulator 680 begins to reduce V. P1 The magnitude of V increases to the magnitude of the negative driving value. P1 When the value reaches a threshold (e.g., 10mV), the processing unit 604 then switches the polarity switching signal V. Polar The value is changed from the second to the third to switch the polarity switch 684 from a high-impedance mode to a negative conduction mode (the second configuration described above). As mentioned above, in some such implementations, the polarity switch 684 transmits V... P1 As the second applied voltage V App2 The first applied voltage V App1 It's a signal ground. In short, when V... P1When the magnitude is greater than or equal to the threshold voltage (e.g., 10mV), depending on whether the polarity switch 684 is in positive conduction mode (first configuration) or negative conduction mode (second configuration), the polarity switch 684 transmits the regulated voltage V. P1 As the first applied voltage V App1 Or the second applied voltage V App2 Therefore, the effective applied voltage V Eff By V P1 The magnitude and polarity configuration indication of the polarity switch 684, while V Eff The value is less than or equal to -10mV or greater than or equal to +10mV. However, when the polarity switch 684 is in high-impedance mode, the value is less than or equal to -10mV. <V Eff In the range of <10mV, V Eff The value of V and more generally App1 and V App2 The value is determined based on predefined calculations or estimates.
[0198] Feedback circuit
[0199] As described above, in some specific implementations, the processing unit 604 may be based on one or more feedback signals V Feed Modify the command signal V during operation (e.g., during a color transition or between color transitions). DCmnd In some specific implementations, the feedback signal V Feed Based on one or more voltage feedback signals V OC The voltage feedback signal is then based on the actual voltage level detected on the ECD of the connected IGU. This type of voltage feedback signal V OC It can be measured during periodic open-circuit conditions (during or between transitions) while the applied voltage V is applied. App1 and V App2 The circuit is disconnected for a short duration during this period. For example, a differential amplifier 688 can be used to measure the open-circuit voltage feedback signal V. OC The differential amplifier has a first input connected to power line 634, a second input connected to power line 636, and an output connected to an analog-to-digital converter (ADC) 692. The ADC 692 can be internal or external relative to the processing unit 604. An example of a differential amplifier suitable for some specific implementations is the low-power, adjustable-gain, precision LT1991, supplied by Linear Technology Corp., Milpitas, California.
[0200] Additional or alternative ground, second feedback signal V Feed It can be based on one or more current feedback signals V CurThe current feedback signal is then based on the actual current level detected by the ECD. This type of current feedback signal V Cur The measurement can be performed using an operational amplifier 690, which has a first input connected to a first input terminal of a resistor 691, which is also connected to the output of a polarity switch 684. A second input of the operational amplifier 690 can be connected to a second terminal of the resistor 691, which is also connected to a voltage V supplied by a second power supply. Sup2 The node. The output of operational amplifier 690 can be connected to ADC 692. An example of an operational amplifier suitable for some specific implementations is the low-noise, CMOS, precision AD8605, supplied by Analog Devices Inc., Norwood, Massachusetts. Because the resistance R of resistor 691... F Since this is known, the actual current flowing from the polarity switch 684 can be determined by the processing unit 604 based on the voltage difference signal V. Cur To determine.
[0201] In some specific implementations, the processing unit 604 is further configured to compensate for voltage signal V App1 and V App2 Transmission losses caused by conductive distribution lines 633 and 635 are transmitted. More specifically, the actual voltage supplied to a given busbar of IGU 602 may be less than the voltage V at the output of WC 600. App1 and V App2 Therefore, the actual voltage V applied to the ECD within the IGU 402 is... Act It can be less than the output voltage V of WC 600 App1 With V App2 The difference between them. For example, the resistance of power distribution lines 634 and 636—schematically represented as each having a resistance R. T The resistors in these resistors can cause a significant voltage drop along distribution wires 634 and 636. Of course, the resistance of each distribution wire is directly proportional to its length and inversely proportional to its cross-sectional area. Therefore, the expected voltage drop can be calculated based on the knowledge of the wire length. However, this length information is not always available. For example, the installer may not have recorded such length information during the installation of the IGU, or may not have recorded it accurately, precisely, or correctly. Additionally, in some conventional installations utilizing existing wiring, such length information may not be available.
[0202] If information about the length of the power distribution cable is available, this information can be used to create a lookup table, for example, stored in a memory chip within the insert component. This length information can then be read by the WC 600 upon power-up. In such a specific implementation, the voltage V... App1 and V App2It is possible to increase (e.g., using firmware or software) the estimated voltage drop along the respective distribution lines 634 and 636 to compensate. While such compensation schemes and algorithms are effective to some extent, they cannot accurately account for the dynamic changes in the resistance of the distribution lines caused by temperature variations in the distribution lines, which can vary greatly based on the use of the distribution lines, the position of the sun as the earth rotates, weather conditions, and seasons on a given date.
[0203] Additional or alternative location, third feedback signal V Feed It can be based on one or more voltage compensation signals V Comp The voltage compensation signal is then based on the actual voltage drop detected along at least one of the distribution lines. For example, a differential amplifier 694 can be used to measure such a voltage compensation signal V. Comp The differential amplifier has a first input connected to one of the distribution lines 634 in the WC 600, a second input connected to the fifth line 642 in the WC 600, and an output connected to the ADC 692. In some such embodiments, such as reference... Figure 7 As shown and described, the insert component 752 includes a voltage compensation circuit 762. In one exemplary embodiment, the voltage compensation circuit 762 includes a conductor that provides a short circuit within the insert component 752 between the fifth line 742 and either the first distribution line 734 or the second distribution line 736. In such an embodiment, the differential amplifier 694 detects the offset voltage V. Comp This offset voltage is proportional to the current I through the power distribution line between WC 600 and IGU 602, as well as the length and cross-sectional area of the power distribution line between WC 600 and IGU 602. The current I is determined by the processing unit 604 based on the signal V output from the operational amplifier 690. Cur This is determined by [the process unit]. In this way, the processing unit can increase or decrease the command voltage signal V. DCmnd This is to compensate for static and dynamic voltage drops along the distribution line without needing to know the length or cross-sectional area of the distribution line directly.
[0204] In one specific implementation, by using V Comp Divide by I to calculate the resistance R of each power distribution line between WC 600 and IGU 602. T Then, the resistance information is stored in the parameter table within the WC 600. Then V... Comp Calculated dynamically as 2*R T *V Cur Voltage signal V App1 and V App2 The calculated V can then be used. CompThe quantity is automatically and dynamically adjusted to compensate for the voltage drop in lines 633 and 635. In another case, the voltage signal V... App1 and V App2 Through 2*V Comp To dynamically adjust and address voltage drops in lines 633 and 635.
[0205] Voltage compensation is also described in more detail in U.S. Patent Application No. 13 / 449,248 (Attorney General's File No. VIEWP041), filed April 17, 2012, entitled "CONTROLLER FOR OPTICALLY SWITCHABLE WINDOWS," and U.S. Patent Application No. 13 / 449,251 (Attorney General's File No. VIEWP042), filed April 17, 2012, entitled "CONTROLLER FOR OPTICALLY SWITCHABLE WINDOWS," the entire contents of which are incorporated herein by reference and are used for all purposes. In some other embodiments, voltage compensation circuit 762 may be connected to communication lines 739 and 741, which are connected to chip 756. In some other embodiments, voltage compensation circuit 762 may be directly connected to communication lines 637 and 639 via interface 754 and communication lines 738 and 740.
[0206] Open circuit voltage feedback signal V OC Current feedback signal V Cur and voltage compensation feedback signal V Comp Each of these can be digitized by the ADC 692 and used as a feedback signal V. Feed Provided to processing unit 604. An example of an ADC suitable for some specific implementations is the low-power AD7902 from Analog Devices Inc., Norwood, Massachusetts. In some of the examples above, although the feedback signal V... Feed Referenced in singular form, but the feedback signal V Feed They can collectively refer to three (or more, or fewer) individual feedback signals: the first for digitizing the open-circuit voltage signal V. OC The second one is used for digitizing the current signal V. Cur And the third is used for digital voltage compensation signal V. Comp Feedback signal V Feed It can be provided to the processing unit 604 via the SPI bus 686. The processing unit 604 can then use the feedback signal V Feed To dynamically modify the command signal VD Cmnd This makes the actual value V of the voltage applied on the ECD stack of the IGU 602... Act Approximately equal to the desired effective voltage V EffAnd thus achieve the target coloring state.
[0207] For example, when the external environment becomes brighter, the WC 600 can receive a shading command from the NC 500 to darken the IGU 602. However, in some specific implementations or instances, as the corresponding ECD becomes more chromatic, the ECD temperature can rise significantly due to increased photon absorption. Because the shading of the ECD can depend on its temperature, if the command signal V is not adjusted... DCmnd To compensate for temperature changes, the coloring state can be altered. In some specific implementations, the processing unit 604 can adjust the command signal V based on the actual voltage detected on the ECD or the actual current detected by the ECD. DCmnd such as via feedback signal V OC and V Cur It is determined by, rather than directly detecting, temperature fluctuations.
[0208] Additionally, as mentioned above, each WC 600 can be connected to and power multiple IGUs 602s. While the cross-sectional area of the set of distribution wires connecting a given WC 600 to each of the multiple connected IGUs 602s is typically the same, the length of each set of distribution wires can differ based on the position of the respective IGU 602 relative to the WC 600. Therefore, when the WC 600 supplies voltage V to the multiple connected IGUs 602s via a common node... App1 and V App2 Time (such as through the above reference) Figure 7 The described coupling connector 748, which is actually received by each of the plurality of IGU 602s, has a voltage V. App1 and V App2 The value can vary based on the location of the corresponding IGU in IGU 402 relative to WC 600. In some specific implementations, it may be desirable to have the same or similar length of the distribution cable connecting each of the IGU 602 to a given WC 600 to reduce the difference between the actual applied voltages received by the IGU 602.
[0209] Communication circuit
[0210] Communication circuitry 612 is typically configured to enable communication between processing unit 604 and various other components within or outside WC 600. For example, communication circuitry 612 may include bridge device 696. In some embodiments, bridge device 696 enables processing unit 696 to transmit and receive data signals Data3 and Data4 via communication lines 638 and 640 (collectively referred to as data bus 644) and corresponding communication lines 637 and 639. In some embodiments, bridge device 696 may be a one-wire bridge device configured to communicate according to a one-wire communication protocol. In some such embodiments, communication lines 639 and 640 may be signal grounds, while communication lines 637 and 639 carrying data signal Data3 may provide both data and power to chip 756 and to any number of one-wire compatible sensors within IGU 602. In some embodiments, chip 756 within IGU 602 may serve as an intermediary for data communication between processing unit 604 and sensors within IGU 602. For example, the sensor can be connected to communication lines 739 and 741, which in turn connect to chip 756. In some other embodiments, the sensor can be directly connected to communication lines 637 and 639 via interface 754 and communication lines 738 and 740. At other times, data signal Data3 can transmit sensor data back to processing unit 604.
[0211] The bridge device 696 is configured to manage communication to, from, and between devices on the same line. The processing unit 604 can communicate via I / O. 2 The C-bus 697 transmits commands to or receives data from the bridge device 696. Although I 2 The C-bus 697 can be described in the singular form herein, but I 2 The C bus 697 can collectively refer to two or more I... 2 C-buses, each of which can be used to communicate with a corresponding component of the WC 600. Therefore, in some specific implementations, the bridge device 696 is used as an I-bus. 2 C-to-1 bridge, its direct interface is to I 2 C main equipment (processing unit 604) I 2 The C host port performs bidirectional protocol conversion between processing unit 604 and downstream 1-line slave devices (including any sensors on or within chip 756 and IGU 602). One such bridge device suitable for some implementations is the DS2482 1-line master device supplied by Maxim Integrated Products, Inc., San Jose, California. In some other implementations, the functionality of bridge device 696 can be integrated into processing unit 604.
[0212] In some implementations, in response to power-on or otherwise activation of the processing unit 604, the processing unit 604 instructs the communication module 756 within the plug-in component 752 to transmit device parameters and drive parameters to the RAM or other memory device within the processing unit 604 via the bridge device 696. Additionally or alternatively, the processing unit 604 may periodically poll the communication module 756 via the bridge device 696. The communication module 756 may then respond to the polling by transmitting drive parameters to the RAM or other memory device within the WC 600 via the bridge device 696.
[0213] In some implementations, the communication circuit 612 also includes a radio transceiver 698. For example, the radio transceiver 698 can be connected via I... 2 The C-bus 697 communicates with the processing unit 604. The radio transceiver 698 enables wireless communication between the processing unit 604 and other devices having such radio transceivers, including, for example, other WC 600, NC 500, IGU 602, mobile devices, or other computing devices. Although referred to herein in the singular, radio transceiver 698 may collectively refer to one or more radio transceivers, each configured to communicate wirelessly according to a different, appropriate protocol. For example, some wireless network protocols suitable for certain implementations may be based on the IEEE 802.11 standard, such as Wi-Fi (or “WiFi”). Additionally or alternatively, radio transceiver 698 may be configured to communicate based on the IEEE 802.15.4 standard, which defines the physical layer and media access control for Low Rate Wireless Personal Area Networks (LR-WPANs). For example, higher-level protocols compatible with the IEEE 802.15.4 standard can be based on ZigBee, 6LoWPAN, ISA100.11a, WirelessHART, or MiWi specifications and standards. Additionally or alternatively, the radio transceiver 698 can be configured to communicate based on Bluetooth standards (including Bluetooth Classic, Bluetooth High Speed, and Bluetooth Low Energy protocols, and including Bluetooth v4.0, v4.1, and v4.2 versions). Additionally or alternatively, the radio transceiver 698 can be configured to communicate based on the EnOcean standard (ISO / IEC 14543-3-10).
[0214] As described above, wireless communication can replace communication via a physical cable between the WC 600 and NC 500. In some other embodiments, both wired and wireless communication can be established between the WC 600 and NC 500. In other words, at least two communication links of different types can be maintained simultaneously to transmit data between the WC and MC. For example, the WC can use CANbus for wired communication with the NC for transmitting low-data-intensity messages such as WC voltage data, current data, and sensor data. Simultaneously, the WC can communicate wirelessly with the NC via WiFi or any other wireless communication technology disclosed herein for high-data-intensity communication (such as video camera feeds and / or audio feeds). When two or more communication links are maintained, one communication link can serve as a backup for another in the event of an interruption or other error condition. In some embodiments, sensors and other devices can communicate with the WC using wireless links, wired links, or both. In some implementations, the distributed WC 600 can form a mesh network for communicating various information with each other or to the MC 400, NC 500, or other devices, making physical communication lines between various controllers in the network system, such as network system 300, unnecessary. As mentioned above, the WC 600 can communicate wirelessly with the IGU 602 it controls. For example, the communication module 756 within each IGU 602 may also include a radio transceiver for communicating with the radio transceiver 698 and the processing unit 604 of the WC 600. In some implementations, wireless communication can replace communication via physical cables between the WC 600 and the IGU 602. For example, wireless communication can replace the one-wire communication bus 644, communication lines 637 and 639, and communication lines 738 and 740. Such wireless implementations facilitate the manufacture and installation of self-contained IGUs, e.g., IGUs that do not require attached physical cables. In some such self-sufficient implementations, each IGU may include an energy storage device and an integrated photovoltaic cell for charging the energy storage device. The energy storage device can then supply power to the coloring state and coloring state transition of the ECD within the IGU.
[0215] In some implementations, the communication circuit 612 may additionally or alternatively include a power line communication module 699. The power line communication module 699 can be used in a configuration where data is transmitted via a supply voltage signal V. Sup1 (And in some cases, it can also be done via V) Sup2 In specific implementations or instances, the power line communication module 699 can also transmit data via communication lines 622 and 624 or wirelessly, instead of (or otherwise) through communication lines 622 and 624. As shown, the power line communication module 699 can also transmit data via I... 2 The C-bus 697 communicates with the processing unit 604.
[0216] Automatic / Semi-automatic debugging / Self-discovery
[0217] In some implementations, after installation and once the WC is powered on, the WC can request or poll the 1-wire IDs within the IGU602. These 1-wire IDs are then sent from the WC to the NC and ultimately to the MC, allowing the MC to associate the WC's CANbus ID with the 1-wire IDs of the IGUs it controls. In other implementations, the IGU may also include a wireless transceiver. For example, a Bluetooth transceiver within each IGU can broadcast a beacon containing the IGU's ID, which the WC can then pick up. Once the IDs of the IGUs connected to the WC are known, a person carrying a mobile device (phone, iPad, or proprietary device) can move through the building to associate each IGU with a physical location.
[0218] Sleep mode
[0219] In some implementations, the WC 600 is configured to enter and exit one or more sleep modes in addition to the normal (or "active") operating mode. For example, after a target shading state has been reached and a holding voltage has been applied for a certain duration, the processing unit 604 may stop asserting (deasserting) the enable signal EN, and thus disable the HP buck converter 670. Because the HP buck converter 670 supplies power to most components within the WC 600, the WC 600 enters a first sleep mode when the enable signal EN is deasserted. Alternatively, instead of turning off or disabling the HP buck converter 670, the processing unit may individually disable each component within the WC 600 or selectively disable such individual components or groups of components by deasserting other enable signals (not shown) for such individual components or groups. In some implementations, before disabling the HP buck converter 670 or otherwise disabling desired components within the WC 600, the processing unit 604 asserts a control signal Cntrl, which causes the voltage regulator 680 to enter a high-impedance mode, for example, preventing charge stored in the EC stack of the connected IGU 602 from flowing back from the IGU to the WC 600 when other components are disconnected. In some implementations, the LP buck converter 668 remains on during the first sleep mode to provide full power to the processing unit 604. In some implementations, the processing unit 604 may periodically enable the differential amplifier 688 and the ADC 692 to determine V. OC Has it fallen (or risen) below a threshold level, for example, to determine if the IGU's shading state has changed beyond an acceptable level? When V OCWhen the voltage drops below a threshold (or rises above a threshold), processing unit 604 can "wake up" WC 600 (e.g., exit sleep mode and return to normal operating mode) by turning on the HP buck converter 670 or otherwise activating components necessary to drive the EC stack of the IGU to an acceptable level. In some implementations, upon exiting sleep mode, processing unit 604 may cause a voltage ramp to be applied to the EC stack, followed by a holding voltage.
[0220] In some implementations, processing unit 604 can be configured to cause WC 600 to enter a second (or "deep") sleep mode different from the first (or "light") sleep mode. For example, after WC 600 has been in the first sleep mode for a certain duration, processing unit 604 can disable some of its functionalities to further save power. In effect, processing unit 604 itself enters sleep mode. Processing unit 604 still obtains 3.3V from the LP buck converter, but it is configured to be in a low-power mode with reduced functionality, in which it consumes significantly less power than in the normal full-function mode. When in such a second sleep mode, processing unit 604 can be woken up in one or more of a variety of ways. For example, processing unit 604 can wake itself up periodically (e.g., every minute, every few minutes, every 10 minutes). As described above, processing unit 604 can then enable differential amplifier 688 and ADC 692 to determine V. OC Has it fallen below a threshold level (or risen above a threshold level), for example, to determine if the IGU's shading state has changed beyond an acceptable level? When V OC When the voltage drops below (or rises above) a threshold, processing unit 604 can wake up WC 600 by turning on the HP buck converter 670 or otherwise activating components necessary to drive the EC stack of the IGU to an acceptable level. In some implementations, upon exiting sleep mode, processing unit 604 may cause a voltage ramp to be applied to the EC stack, followed by a holding voltage.
[0221] Additionally or alternatively, processing unit 604 may be awakened from such deep sleep mode based on an interrupt (such as a command from NC 500) or based on a signal from an occupancy sensor communicatively connected to processing unit 604. When such an occupancy sensor detects an occupant, it may provide a signal to processing unit 604, causing the processing unit to wake up and return WC 600 to active mode (in some other embodiments, the occupancy sensor may be connected to NC 500, and the NC subsequently sends a wake-up command to WC 500 based on the signal from the occupancy sensor). In some embodiments, such as in scenarios where the user carries a device including Bluetooth or other suitable types of transceivers that periodically poll or send beacons for pairing, processing unit 604 may periodically wake up so that radio transceiver 698 can determine whether any such device is nearby.
[0222] Additionally, to further conserve power during such sleep modes, processing unit 604 can enable voltage regulator 680 via control signal Cntrl to draw power from the charge stored in the EC stack of IGU 602 to supply power to processing unit 604 and radio transceiver 698. Further examples of power saving and intelligent, efficient power allocation are described in PCT patent application No. PCT / US16 / 41176 (Attorney's File No. VIEWP080WO), filed July 6, 2016, entitled “POWER MANAGEMENT FOR ELECTROCHROMIC WINDOWNETWORKS,” which is incorporated herein by reference in its entirety and for all purposes. Furthermore, with the acquisition of V OC The relevant subject matter is further described in U.S. Patent Application No. 13 / 931,459 (Attorney’s File No. VIEWP052), filed June 28, 2013, entitled “CONTROLLING TRANSITIONS IN OPTICALLY SWITCHABLE DEVICES”, which is incorporated herein by reference in its entirety and for all purposes.
[0223] Intelligent Network Controller
[0224] In some specific implementations, refer to Figure 5 The NC 500 described above can take over the functions described above. Figure 4 The NC 500 may include some of the functions, processes, or operations that are part of the MC 400's responsibilities. Additionally or alternatively, the NC 500 may include additional functions or capabilities not described in reference to the MC 400. Figure 8 A block diagram of an exemplary module of a network controller according to some specific implementations is shown. For example, Figure 8The modules can be implemented in the NC 500 with any suitable combination of hardware, firmware, and software. In some specific implementations where the NC 500 is implemented as a network controller application running within a computer, Figure 9 Each module can also be implemented as an application, task, or subtask that executes within the network controller application.
[0225] In some implementations, the NC 500 periodically requests status information from the WCs 600 it controls. For example, the NC 500 may send status requests to each WC 600 it controls every few seconds, every tens of seconds, every minute, every few minutes, or after any desired time period. In some implementations, each status request is directed to a corresponding WC 600 using a CAN ID or another identifier for the corresponding WC 600. In some implementations, the NC 500 sequentially passes through all the WCs 600 it controls during each round of status acquisition. In other words, the NC 500 cycles through all the WCs 600 it controls, sending a status request sequentially to each WC 600 in each round of status acquisition. After a status request has been sent to a given WC 600, the NC 500 then waits to receive status information from the respective WC before sending a status request to the next WC 600 in the status acquisition round.
[0226] In some implementations, after receiving status information from all WCs 600 controlled by the NC 500, the NC 500 then performs a round of coloring command allocation. For example, in some implementations, each round of status acquisition is followed by a round of coloring command allocation, then the next round of status acquisition and the next round of coloring command allocation, and so on. In some implementations, during each round of coloring command allocation, the NC 500 continues to send coloring commands to each WC 600 controlled by the NC 500. In some such implementations, the NC 500 also sequentially passes through all WCs 600 it controls during the coloring command distribution round. In other words, the NC 500 cycles through all WCs 600 it controls, such that coloring commands are sent sequentially to each WC 600 in each round of coloring command distribution.
[0227] In some embodiments, each status request includes an instruction indicating what status information is requested from the corresponding WC 600. In some embodiments, in response to receiving such a request, the corresponding WC 600 responds by sending the requested status information to the NC 500 (e.g., via a communication line in the upstream cable group 616). In some other embodiments, by default, each status request causes the WC 600 to send a predefined set of information from a set of IGUs 602s it controls. In either case, the status information that the WC 600 communicates with the NC 500 in response to each status request may include a hue status value (S) of the IGU 602, for example, indicating whether the IGU 602 is undergoing a hue transition or has completed one. Additionally or alternatively, the hue status value S or another value may indicate a specific stage in the hue transition (e.g., a specific stage of a voltage control curve). In some embodiments, the status value S or another value may also indicate whether the WC 600 is in sleep mode. The status information transmitted in response to a status request may also include the coloring value (C) of the IGU 602, for example, set by the MC 400 or NC 500. The response may also include the setpoint voltage (e.g., the effectively applied V) set by the WC 600 based on the coloring value. Eff The value of the response may also be included in some implementations. In some specific implementations, the response may also include a near-real-time actual voltage level V measured, detected, or otherwise determined on the ECD within the IGU 602 (e.g., via amplifier 688 and feedback circuit 610). Act In some implementations, the response may also include a near-real-time actual current level I measured, detected, or otherwise determined by an ECD within the IGU602 (e.g., via amplifier 690 and feedback circuit 610). Act The response may also include various near real-time sensor data, such as those collected from photoelectric or temperature sensors integrated on or within the IGU 602.
[0228] Some protocols (such as CANOpen) limit the size of each frame of data sent from WC 600 to NC 500, and vice versa. In some cases, sending each status request and receiving status information in response to such a request actually involves multiple bidirectional communications, and therefore multiple frames. For example, each of the status requests described above may include a separate sub-request for each of the aforementioned status values. As a more specific example, each status request from NC 500 to a particular WC 600 may include a first sub-request requesting status value S. In response to the first sub-request, WC 600 may transmit an acknowledgment frame to NC 500 including status value S. NC 500 may then transmit a second sub-request requesting color value C to WC 600. In response to the second sub-request, WC 600 may transmit an acknowledgment frame to NC 500 including color value C.Eff V Act and I Act The values and sensor data can be obtained similarly using separate corresponding sub-requests and responses.
[0229] In some other implementations, the NC 500 can asynchronously send status requests to specific WC 600s, instead of sequentially polling or sending status requests to each WC 600. For example, it can periodically receive status information (including C, S, V) from all WC 600s. Eff V Act and I Act This might not be useful. For example, you might want to asynchronously request this information only from a specific WC 600 that has recently received or implemented a shading command, whether it is currently undergoing a shading transition, recently completed a shading transition, or from which state information has not been collected for a relatively long time.
[0230] In some other implementations, each WC 600 can periodically broadcast its status information (including C, S, V). Eff V Act and I Act Instead of polling or sending status requests to each WC 600 individually, whether sequentially or asynchronously, each WC 600 can wirelessly broadcast status information. For example, each WC 600 can broadcast status information every few seconds, tens of seconds, minutes, or tens of minutes. In some implementations, WC 600s can be synchronized to broadcast their respective status information at certain times to avoid consuming large amounts of collective bandwidth. Furthermore, the broadcast time can differ for different groups of WC 600s (such as the zones mentioned above) and at different times, for example, based on the location of the corresponding IGU in the building and its position relative to the sun, or based on whether the room adjacent to the IGU is occupied.
[0231] In some other implementations, each WC 600 may broadcast its state information in response to certain conditions, such as when a shading transition begins, when a shading transition ends, or when V... Act When the threshold is changed, when I ActThe status information can be broadcast when the threshold changes, when sensor data (e.g., light intensity or temperature) changes the threshold, when the occupancy sensor indicates that an adjacent room is occupied, or when entering or exiting sleep mode. The NC 500 can listen for such broadcast status information and record the status information when it hears it. Advantageously, in the broadcast implementation, the time required to receive status information from a group of WC 600s is reduced by approximately half because there is no need to request status information from WC 600s, and therefore no round-trip delay associated with each WC 600. Instead, there is only a one-way waiting time associated with the time required to send status information from each WC 600 to the NC 500.
[0232] In some other implementations, upon or after power-on, each WC 600 can be configured to read device parameters, driver parameters, and lite ID or other ECD IDs from the IGU used for connection. The WC then broadcasts its CAN ID, along with the lite ID and associated device and driver parameters. That is, in some implementations, this broadcast is initiated by one or more processors within the WC, regardless of any requests for such data from the NC or other controllers. The NC 500 can receive and process the IDs and parameters when broadcast. In some implementations, the lite ID and parameters from the message broadcast by the WC are then transmitted from the NC to the MC, which stores them in a table, for example, containing a list of known CAN IDs. For example, each row of the table may include the CAN ID, the WC location ID associated with the CAN ID, the connected lite ID, the location of the respective window associated with the lite ID, and the device and driver parameters of the corresponding ECD. In some implementations, the MC may store the table in a cloud-based database system, allowing another MC to be instantiated and the table in the cloud to be accessed even if the MC fails.
[0233] In some cases, during commissioning, field service technicians may intervene and attempt to perform specific lite-to-lite matching based on perceived differences in hue between two or more adjacent windows. In this scenario, the technician can determine that the drive parameters of one or more ECDs should be modified and then implement those modifications. In some implementations, the WC is configured to broadcast the modified parameters to the corresponding NC, from which the parameters can be passed to the MC. In the event of a WC failure or error, the NC or MC can determine that the WC has failed, for example, because the WC is no longer broadcasting data, such as the WC's CAN ID and / or WC location ID, when the WC is configured to periodically broadcast data. When the faulty WC is replaced with a new WC and then powered on, the new WC will read the corresponding lite ID and, as described above, broadcast the new WC's CAN ID and the associated lite ID. When the NC or MC receives this information, the NC or MC can be configured to perform a table lookup using the lite ID to retrieve the modified drive parameters of the faulty WC from a database table. In this case, the NC or MC is also configured to automatically update the table by assigning a new CAN ID to the WC location ID and the associated lite ID. Then, the NC or MC will automatically transmit the modified drive parameters to the new WC. In this way, even when the corresponding WC is replaced, the ECD whose drive parameters were modified during debugging can still be driven by the modified drive parameters. In some specific implementations, other techniques for automatically modifying, updating, and applying drive parameters can be implemented, as further described in U.S. Provisional Application No. 62 / 305,892 (Attorney General's File No. VIEWP008X2P), filed March 9, 2016, entitled "METHOD OF COMMISSIONING ELECTROCHROMIC WINDOWS," which is incorporated herein by reference in its entirety and is used for all purposes.
[0234] In some such implementations, instead of sending coloring commands sequentially to each WC 600, the NC 500 can asynchronously send coloring commands to specific WC 600s via a wired or wireless connection. For example, periodically sending coloring commands to all WC 600s might not be useful. It might be necessary to asynchronously send coloring commands only to specific WC 600s that are transitioning to a different coloring state, whose status information has just been (or recently) received, or whose coloring commands have not been sent for a relatively long time.
[0235] Data logger
[0236] In some embodiments, the NC 500 further includes a data logging module (or “data logger”) 802 for recording data associated with the IGU controlled by the NC 500. In some embodiments, the data logger 802 records status information included in each of some or all responses to a status request. As described above, the status information transmitted by the WC 600 to the NC 500 in response to each status request may include: a shading status value (S) of the IGU 602, a value indicating a specific stage in a shading transition (e.g., a specific stage of a voltage control curve), a value indicating whether the WC 600 is in sleep mode, a shading value (C), and a setpoint voltage (e.g., the effectively applied V) set by the WC 600 based on the shading value. Eff The value of V, the actual voltage level V measured, detected, or otherwise determined on the ECD within the IGU 602. Act The actual current level I is determined by measuring, detecting, or otherwise using the ECD within the IGU 602. Act This includes various sensor data, such as those collected from photoelectric sensors or temperature sensors integrated on or within the IGU 602. In some other implementations, the NC 500 may collect and queue status information in message queues, such as RabbitMC, ActiveMQ, or Kafka, and stream the status information to the MC for subsequent processing, such as data reduction / compression, event detection, etc., as further described herein.
[0237] In some implementations, the data logger 802 within the NC 500 collects and stores various information received from the WC 600 in the form of a log file such as a comma-separated value (CSV) file or through another tabular structured file format. For example, each line of the CSV file can be associated with a corresponding status request and can include C, S, V. Eff V Act and I Act The values and sensor data (or other data) received in response to a status request. In some implementations, each row is identified by a timestamp corresponding to the respective status request (e.g., when the NC 500 sends a status request, when the WC 600 collects data, when a response including data is transmitted via the WC 600, or when a response is received via the NC 500). In some implementations, each row also includes a CAN ID or another ID associated with the corresponding WC 600.
[0238] In some other implementations, each row of the CSV file may include the requested data for all WC 600s controlled by the NC 500. As mentioned above, the NC 500 can sequentially cycle through all the WC 600s it controls during each round of status requests. In some such implementations, each row of the CSV file is still identified by a timestamp (e.g., in the first column), but the timestamp may be associated with the start of each round of status requests rather than with each individual request. In one specific example, columns 2-6 may respectively include the C, S, V for the first WC among the WC 600s controlled by the NC 500. Eff V Act and I Act Values, columns 7-11 can respectively include C, S, V for the second WC in WC 600. Eff V Act and I Act Values, columns 12-16 can respectively include C, S, V for the third WC in WC 600. Eff V Act and I Act The values are then repeated for all WC 600s controlled by the NC 500. Subsequent rows in the CSV file can contain the corresponding values for the next round of status requests. In some implementations, each row may also include sensor data obtained from photoelectric sensors, temperature sensors, or other sensors integrated with the corresponding IGU controlled by each WC 600. For example, such sensor data values can be input into the C, SV of the first WC in the WC 600. Eff V Act and I Act The values are in the corresponding columns, but in that row are used for the C, S, V of the next WC in WC 600. Eff V Act and I Act Prior to the value. Additionally or alternatively, each row may include sensor data values from one or more external sensors, for example, located on one or more facades or the roof of a building. In some such implementations, the NC 500 may send a status request to the external sensors at the end of each round of status requests.
[0239] compact state
[0240] As mentioned above, some protocols, such as CANopen, limit the size of each frame sent from WC 600 to NC 500, and vice versa. In some cases, sending each status request and receiving status information in response to such a request actually involves multiple bidirectional communications and frames. For example, each of the aforementioned status requests may include a separate sub-request for each of the aforementioned status values. In some specific implementations, the requested values C, S, VEff V Act and I Act Each of two or more of these can be transmitted together within a single response—a compact state response. For example, in some specific implementations, C, S, V Eff V Act and I Act Two or more values in the frame are formatted to fit into a frame. For example, the CANopen protocol limits the size of the data payload that can be sent in each frame to 8 bytes (where each byte consists of 8 bits). And in implementations using the CANopen Service Data Object (SDO) sub-protocol, the maximum size of the data payload portion of a CANopen frame is 4 bytes (32 bits). In some specific implementations, the value V... Eff V Act and I Act Each element in V is 10 bits in size. Therefore, V can be... Eff V Act and I Act Each of the values is encapsulated within a single SDO frame. This leaves 2 bits. In some implementations, each value of C and S can be specified with a single corresponding bit. In such cases, C, S, V Eff V Act and I Act All values can be specified using only 32 bits, and are therefore encapsulated within an SDO CANopen frame.
[0241] In some implementations, using broadcast status requests can achieve additional time savings. For example, instead of sending status requests to each WC 600 on an individual (or "unicast") basis, the NC 500 can broadcast a single status request to all WC 600s it controls. As described above, in response to receiving a status request, each WC 600 can be programmed to transmit status information such as values C, S, V in one or more compact status responses. Eff V Act and I Act To respond.
[0242] Protocol conversion module
[0243] As described above, one function of NC 500 may be to perform conversions between various upstream and downstream protocols, for example, to enable the distribution of information between WC 600 and MC 400 or between WC and the outward-facing network 310. In some embodiments, protocol conversion module 804 is responsible for such conversion or conversion services. In various embodiments, protocol conversion module 904 may be programmed to perform conversions between any of a plurality of upstream protocols and any of a plurality of downstream protocols. As described above, such upstream protocols may include UDP protocols such as BACnet, TCP protocols such as oBix, other protocols built upon these protocols, and various wireless protocols. Downstream protocols may include, for example, CANopen, other CAN-compatible protocols, and various wireless protocols, such as protocols based on the IEEE 802.11 standard (e.g., WiFi), protocols based on the IEEE 802.15.4 standard (e.g., ZigBee, 6LoWPAN, ISA100.11a, WirelessHART, or MiWi), protocols based on the Bluetooth standard (including Bluetooth Classic, Bluetooth High Speed, and Bluetooth Low Energy protocols, as well as Bluetooth v4.0, v4.1, and v4.2 versions), or protocols based on the EnOcean standard (ISO / IEC 14543-3-10).
[0244] ensemble analysis
[0245] In some implementations, the NC 500 periodically (e.g., every 24 hours) uploads information recorded by the data logger 802 (e.g., as a CSV file) to the MC 400. For example, the NC 500 can send the CSV file to the MC 400 via Ethernet data link 316 through File Transfer Protocol (FTP) or another suitable protocol. In some such implementations, the status information can then be stored in a database 320 or made accessible to applications via an external network 310.
[0246] In some implementations, NC 500 may also include the ability to analyze information recorded by data logger 802. For example, analysis module 906 may receive and analyze raw information recorded by data logger 802 in real time. In various implementations, analysis module 806 may be programmed to make decisions based on raw information from data logger 802. In some other implementations, analysis module 806 may communicate with database 320 to analyze state information recorded by data logger 802 after data logger 802 has been stored in database 320. For example, analysis module 806 may analyze raw values of electrical characteristics (such as V...) Eff V Act and I ActThe analysis module 806 compares the data with expected values or ranges and flags specific conditions based on these comparisons. For example, such flagged conditions could include power spikes indicating faults such as short circuits, errors, or ECD malfunctions. In some implementations, the analysis module 806 transmits such data to the hue determination module 810 or the power management module 812.
[0247] In some implementations, the analysis module 806 may also filter the raw data received from the data logger 802 to store information in the database 320 more intelligently or efficiently. For example, the analysis module 806 may be programmed to pass only information of “interest” to the database manager 808 for storage in the database 320. For example, information of interest may include outliers, values that deviate from expected values (e.g., based on empirical or historical values), or specific periods in which transitions occurred. A more detailed description of how raw data is filtered, parsed, temporarily stored, and effectively stored in a database long-term is provided in PCT patent application No. PCT / 2015 / 029675 (Attorney’s File No. VIEWP049X1WO), filed May 7, 2015, entitled “CONTROL METHOD FOR TINTABLE WINDOWS,” which is incorporated herein by reference in its entirety and for all purposes.
[0248] Database Manager
[0249] In some implementations, the NC 500 includes a database manager module (or "database manager") 808 configured to periodically store information recorded by the data logger 804 into a database, such as hourly, every few hours, or every 24 hours. In some implementations, the database may be an external database, such as the database 320 described above. In some other implementations, the database may be internal to the NC 500. For example, the database may be implemented as a time-series database, such as the Graphite database within the NC 500's secondary storage 506 or another long-term storage within the NC 500. In some example implementations, the database manager 808 may be implemented as a Graphite daemon executed as a background process, task, subtask, or application within the NC 500's multitasking operating system. Time-series databases may be superior to relational databases such as SQL because they are more effective for analyzing data over time.
[0250] In some implementations, database 320 may collectively refer to two or more databases, each storing some or all of the information acquired by some or all of the NCs 500 in the network system 300. For example, for redundancy purposes, it may be desirable to store copies of information in multiple databases. In some implementations, database 320 may collectively refer to multiple databases, each within a corresponding NC 500 (such as Graphite or other time-series databases). It is also desirable to store copies of information in multiple databases so that information requests from applications, including third-party applications, can be distributed across the databases and processed more efficiently. In some such implementations, the databases may be periodically or otherwise synchronized to maintain consistency.
[0251] In some implementations, database manager 808 may also filter data received from analysis module 806 to store information more intelligently or efficiently in internal or external databases. For example, database manager 808 may be additionally or alternatively programmed to store only information of "interest" into the database. Again, information of interest may include outliers, values that deviate from expected values (e.g., based on empirical or historical values), or specific periods in which transitions occurred. A more detailed description of how raw data is filtered, parsed, temporarily stored, and effectively stored in a database long-term is provided in PCT patent application No. PCT / 2015 / 029675 (Attorney's File No. VIEWP049X1WO), filed May 7, 2015, entitled "CONTROL METHOD FOR TINTABLE WINDOWS," which is incorporated herein by reference in its entirety and for all purposes.
[0252] Colorimetric determination
[0253] In some implementations, the NC 500 or MC 400 includes intelligence for calculating, determining, selecting, or otherwise generating IGU 602 shading values. For example, as referenced above... Figure 4Similar to the MC 400, the color determination module 810 can execute various algorithms, tasks, or subtasks to generate color values based on a combination of parameters. This combination of parameters can include, for example, state information collected and stored by the data logger 802. It can also include time and calendar information, such as the time of day, the days of the year, or the time of the season. Additionally or alternatively, it can include solar calendar information, such as the sun's direction relative to the IGU 602. It can also include external temperature (outside the building), internal temperature (in a room adjacent to the target IGU 602), or the temperature within the internal volume of the IGU 602. It can also include weather information (e.g., whether it is sunny, sunny, cloudy, rainy, or snowy). Parameters such as the time of day, the day of the year, or the sun's direction can be programmed into the NC 500 and tracked by the MC 500. Parameters such as external temperature, internal temperature, or IGU temperature can be obtained from sensors integrated into or within the IGU 602, or in or around the building. In some implementations, various parameters can be provided by various applications, or determined based on the information they provide, including third-party applications that can communicate with the NC 500 via an API. For example, the network controller application or the operating system it runs on can be programmed to provide an API.
[0254] In some implementations, the hue determination module 810 may also determine hue values based on user coverage received via various mobile device applications, wall devices, or other devices. In some implementations, the hue determination module 810 may also determine hue values based on commands or instructions received from various applications, including third-party applications and cloud-based applications. For example, such third-party applications may include various monitoring services, including thermostat services, alarm services (e.g., fire detection), security services, or other device automation services. Additional examples of monitoring services and systems can be found in PCT / US2015 / 019031 (Attorney General's File No. VIEWP061WO), filed March 5, 2015, entitled “MONITORING SITES CONTAINING SWITCHABLE OPTICAL DEVICES AND CONTROLLERS”. These applications may communicate with the hue determination module 810 and other modules within the NC 500 via one or more APIs. Some examples of APIs that can be enabled under NC 500 are described in U.S. Provisional Application No. 62 / 088,943 (Agent's File No. VIEWP073P), filed December 8, 2014, entitled "MULTIPLE INTERFACING SYSTEMS AT A SITE".
[0255] Power Management
[0256] As described above, the analysis module 806 can analyze V Eff V Act and I Act The analysis module 806 compares the values of the sensors, as well as the sensor data acquired in real time and / or previously stored in the database 320, with the expected values or expected value ranges, and marks special conditions based on this comparison. The analysis module 806 can pass such marked data, marked conditions, or related information to the power management module 812. For example, such marked conditions may include power spikes indicating ECD short circuits, errors, or damage. The power management module 812 can then modify its operation based on the marked data or conditions. For example, the power management module 812 may delay hull commands until power demand decreases, stop sending commands to faulty WCs (and place them in an idle state), begin interleaving commands to WCs, manage peak power, or issue a distress signal.
[0257] Control multiple optical switchable devices
[0258] For example, due to manufacturing differences or other variations between IGUs, applying the same shading distribution to multiple IGUs under the control of a single window controller may result in IGUs having different shading characteristics. For instance, IGUs may shading at different rates, end shading transitions at different shading states, etc. Different shading characteristics can cause windows that are close to and / or adjacent to each other to appear visually different. Applying different shading distributions individually to each IGU may be wasteful of resources. For example, driving each IGU individually under the control of a window controller may waste power available from the power supply associated with the window controller. Therefore, this document discloses techniques, methods, systems, and apparatus for controlling multiple IGUs using a single window controller, such that the multiple IGUs are driven together for a portion of a shading transition and subsequently fine-tuned individually to achieve shading uniformity. For example, fine-tuning can occur after a large number of shading transitions have occurred.
[0259] In some implementations, a single window controller can control multiple optically switchable devices (e.g., IGUs). For example, in some implementations, the window controller can control two IGUs, four IGUs, six IGUs, etc. In some implementations, each IGU may be similar in one or more characteristics, such as size (e.g., surface area), dimensions, busbar size, etc. In some implementations, the multiple IGUs may be positioned and / or located in the same area of the facility (e.g., in the same area of a building, facing the same geographical direction, located on the same floor of a building, etc.). In some implementations, the window controller controlling the multiple IGUs may be located near the multiple IGUs, such as in a ceiling area near the multiple IGUs. By controlling multiple IGUs with a single window controller, the multiple IGUs may be able to change tinting in a similar manner (e.g., such that the IGUs change tinting relatively simultaneously). Additionally, using a single window controller can provide cost savings because the cost of the window controller can be distributed across the multiple IGUs controlled by the window controller. For example, the cost of a single power supply can be shared among multiple IGUs. Furthermore, using a single window controller to control multiple IGUs can reduce communication network and / or power distribution network infrastructure, as a relatively small number of window controllers can be operatively connected to the trunk line while controlling a larger number of IGUs than window controllers connected to the trunk line.
[0260] In some implementations, the window controller can apply a drive voltage to multiple (e.g., two or more) IGUs. The drive voltage can be applied in conjunction with the color transition of each IGU to be applied to (e.g., a common color transition from a first color state to a second color state). The drive voltage can be provided via a power supply (e.g., a common DC power supply). In some implementations, the window controller can monitor parameters indicating the state of a color transition for each IGU. In some implementations, in response to determining that at least one IGU has completed a color transition, the window controller can switch that at least one IGU to a holding voltage while continuing to apply drive voltages to the remaining IGUs. The window controller can then cycle through the remaining IGUs and can switch each of the remaining IGUs to a holding voltage when it is determined that an IGU has completed a color transition. By initially driving all IGUs with a common drive voltage (e.g., until at least one IGU has completed a color transition), a large amount of ion charge transfer can be completed synchronously for all IGUs. IGUs that complete color transitions more slowly can then be charged until a color transition is completed by continuing to provide drive voltages. This allows IGU to transition to the same shading state in a more synchronized and uniform manner.
[0261] In some implementations, parameters indicating the state of the color transition include the open-circuit voltage (Voc) of the IGU and / or the amount of charge transferred to the IGU. For example, a determination that an IGU has completed its color transition may be made in response to determining that the Voc of the IGU meets or exceeds a target Voc and / or in response to determining that the amount of charge delivered to the IGU meets or exceeds a target charge to be delivered to the IGU. In some implementations, each IGU is operatively connected to a common power supply via a switch. In some implementations, the switch may be an H-bridge circuit. In some implementations, the Voc measurement associated with the IGU may be performed by causing the corresponding switch operatively connecting the IGU to the common power supply to be in a high-impedance mode.
[0262] In some implementations, the amount of charge transferred to or delivered to the IGU is used to determine whether the IGU has completed its color transition. In some implementations, the charge delivered per unit area is considered, which may be referred to as delivered charge or charge density, or total delivered charge or charge density. In some implementations, the delivered charge or charge density can be determined by determining the amount of current delivered to the IGU over a period of time (e.g., by integrating the current delivered over a period of time).
[0263] In some implementations, to determine whether the color transition has been completed, the total delivered charge or charge density can be compared to the threshold charge or threshold charge density (also known as the target charge or charge density). The threshold charge or threshold charge density can be selected based on the minimum charge or charge density required to fully or nearly complete the optical transition under possible operating conditions. In various cases, the threshold charge or threshold charge density can be selected / estimated based on the charge or charge density required to fully or nearly complete the optical transition at defined temperatures (e.g., at about -40°C, about -30°C, about -20°C, about -10°C, about 0°C, about 10°C, about 20°C, about 25°C, about 30°C, about 40°C, about 60°C, etc.). A suitable threshold charge or threshold charge density may also be affected by the leakage current of the electrochromic device. Devices with higher leakage current should have higher threshold charge densities. In some implementations, an appropriate threshold charge or threshold charge density can be empirically determined for individual apertures or aperture designs. In other cases, an appropriate threshold can be calculated / selected based on window characteristics such as size, busbar spacing, leakage current, and start and end optical states. Example threshold charge densities range from approximately 1 × 10⁻⁶. -5 C / cm 2 and approximately 5C / cm 2 Between, for example, about 1×10 -4 and approximately 0.5C / cm 2 Between, or approximately 0.005-0.05 C / cm 2 Between, or approximately 0.01-0.04 C / cm2 The threshold charge density is between, and in many cases between, approximately 0.01 and 0.02. Smaller threshold charge densities can be used for partial transitions (e.g., from fully transparent to 25% tinting), and larger threshold charge densities can be used for full transitions. A first threshold charge or charge density can be used for bleaching / transparency transitions, and a second threshold charge or charge density can be used for tinting / coloring transitions. In some embodiments, the threshold charge or charge density is higher for tinting transitions than for transparent transitions. In a specific example, the threshold charge density for tinting is approximately 0.013–0.017 C / cm². 2 The threshold charge density for transparency is between 0.016 and 0.020 C / cm³. 2 In situations where the aperture can transition between more than two states, an additional threshold charge density may be appropriate. For example, if the device switches between four different optical states: A, B, C, and D, a different threshold charge or charge density can be used for each transition (e.g., A to B, A to C, A to D, B to A, etc.). In some implementations, the threshold charge or threshold charge density is determined empirically. For example, the amount of charge required to achieve a specific transition between desired end states can be characterized for devices of different sizes. A curve can be fitted for each transition to correlate the busbar separation distance with the required charge or charge density. This information can be used to determine the minimum threshold charge or threshold charge density required for a specific transition on a given aperture. In some cases, the information gathered in such empirical determinations is used to calculate the amount of charge or charge density corresponding to a specific level of change (increase or decrease) in optical density.
[0264] Figure 9 An example of a process 900 for controlling multiple IGUs is shown according to some embodiments. Process 900 may be executed by a window controller. In some embodiments, the window of process 900 may differ from... Figure 9The execution order is shown. In some embodiments, two or more blocks of process 900 may be executed substantially in parallel. In some embodiments, one or more blocks of process 900 may be omitted. At 910, process 900 combines a color transition by applying a drive voltage to two or more IGUs via a window controller. For example, the color transition may be a common color transition, such that all two or more IGUs transition from a first color state to a second color state. In some embodiments, the window controller and each of the two or more IGUs are operatively coupled to a common power supply. At 920, process 900 monitors parameters indicating the state of the color transition for each of the two or more IGUs. The parameters indicating the state of the color transition may include the Voc associated with each IGU and / or the amount of charge delivered to each IGU. At 930, process 900 determines whether any IGU has completed a color transition. For example, process 900 may determine that a particular IGU has completed a color transition in response to determining that the Voc associated with the IGU meets or exceeds a target Voc. For example, process 900 may determine that a particular IGU has completed its color transition in response to determining that more than a target amount of charge has been delivered to the IGU. If at 930, process 900 determines that no IGU has completed its color transition ("No" at 930), then process 900 may cycle back to block 920. Process 900 may cycle through blocks 920 and 930 until process 900 determines that at least one IGU has completed its color transition. Conversely, if at 930, process 900 determines that at least one IGU has completed its color transition ("Yes" at 930), then process 900 may proceed to 940 and may transition the IGUs that have completed their color transition (e.g., one or more IGUs that have completed their color transition) to a holding voltage while continuing to apply a drive voltage to the remaining IGUs that have not yet completed their color transition. It should be noted that in instances where two or more IGUs transition to a holding voltage, the two or more IGUs may transition to the same holding voltage and / or different holding voltages. At 950, process 900 may determine whether all IGUs have completed their color transition. For example, in some embodiments, process 900 may determine whether all IGUs have transitioned to the holding voltage. At 950, if process 900 determines that not all IGUs have completed their color transition (e.g., there are remaining IGUs that have not yet completed their transition), or if the result at 950 is "No", process 900 may loop back to block 920 and may continue to monitor parameters indicating the state of the color transition for any remaining IGUs that have not yet completed their color transition (and therefore have not yet transitioned to the holding voltage). Conversely, if at 950 process 900 determines that all IGUs have completed their color transition (if the result at 950 is "Yes"), process 900 may terminate.
[0265] In some implementations, after the IGU has transitioned to the holding voltage (e.g., in response to determining that the IGU has completed the color transition), the IGU can be monitored, for example, to determine whether the IGU has deviated from the final color state associated with the color transition. In some specific implementations, in response to determining that the IGU has deviated from the final color state, an additional voltage pulse can be applied to the IGU. This can have the effect of filling or saturating the IGU, for example, to counteract leakage associated with the IGU that causes it to deviate from the final state. In some implementations, the voltage pulse can be a voltage pulse associated with the drive voltage.
[0266] In some implementations, whether an IGU has deviated from the final tinting state associated with the tinting transition can be determined based on a measurement of the Voc associated with the IGU. For example, a determination that an IGU has deviated from the final state can be made in response to determining that the Voc associated with the IGU has dropped below a target Voc. In some implementations, in instances where a window controller controls multiple IGUs, the window controller can cause the Voc associated with each IGU to be measured sequentially or simultaneously. In some implementations, the window controller can then apply voltage pulses to one or more IGUs that have deviated from the final tinting state.
[0267] Figure 10An exemplary process 1000 for monitoring IGUs after a shading transition is illustrated according to some embodiments. The blocks of process 1000 may be executed by a window controller. In some embodiments, two or more blocks of process 1000 may be executed substantially simultaneously. In some embodiments, one or more blocks of process 1000 may be omitted. Process 1000 begins at 1010, monitoring deviations from the final shading state for two or more IGUs currently in a hold state. The final shading state may be the shading state associated with a completed shading transition. The final shading state may be the same for each of the two or more IGUs. In some specific embodiments, monitoring deviations from the final shading state may include measuring the Voc associated with each IGU. At 1020, process 1000 determines whether any IGU has deviated from the final shading state. For example, process 1000 may determine that an IGU has deviated from the final shading state in response to determining that the Voc of an IGU has dropped below a target Voc. If at 1020, process 1000 determines that no IGU has deviated from the final shading state ("No" at 1020), then process 1000 loops back to box 1010. Conversely, if at 1020, process 1000 determines that at least one IGU has deviated from the final shading state ("Yes" at 1020), then process 1000 proceeds to 1030 and applies a voltage pulse to any IGU that has deviated from the final shading state (e.g., the at least one IGU). In some specific implementations, the voltage pulse may have a magnitude corresponding to a drive voltage (e.g., a drive voltage used to transition the IGU to the final shading state).
[0268] In some embodiments, a window controller (which may include one or more processors) can control multiple (e.g., two or more) IGUs. In some embodiments, the window controller and the multiple IGUs can be operatively coupled to a power supply (e.g., a DC power supply). For example, the window controller can transmit instructions to the power supply causing the power supply to provide a drive voltage to the multiple IGUs. In some specific embodiments, each of the multiple IGUs is operatively coupled to the power supply via a switch. The switch can switch between an enabled state (e.g., a low-impedance state) and a disabled state (e.g., a high-impedance state) such that when the switch associated with an IGU is enabled, the IGU receives a voltage (e.g., a drive voltage) supplied by the power supply, and such that when the switch is disabled, the IGU is in a held state and does not receive a voltage (e.g., a drive voltage) supplied by the power supply. In some specific embodiments, the window controller (e.g., one or more processors of the window controller) provides each switch with instructions causing the switch to change its state (e.g., from enabled to disabled, or vice versa). In some embodiments, the switch operatively coupled to the power supply for the IGUs can be an H-bridge.
[0269] In some implementations, each IGU is operatively coupled to a voltage measurement circuit configured to measure the open-circuit voltage (e.g., Voc) across the IGU. In some implementations, the voltage measurement circuit includes a differential amplifier (e.g., such as...). Figure 6 As shown and combined Figure 6 (as described above). In some embodiments, the voltage measurement circuit is operatively coupled to a corresponding switch (e.g., an H-bridge). For example, the voltage measurement circuit can be configured to measure Voc on the IGU when the corresponding switch is disabled.
[0270] In some implementations, the switch is operatively coupled to the IGU via a trunk segment. In some implementations, the voltage drop (e.g., Vdrop) on each trunk segment is measured via a voltage measurement circuit. In one example, the voltage measurement circuit includes a differential amplifier (e.g., such as...). Figure 6 As shown and combined Figure 6 In some embodiments, voltage drop measurements are provided to the window controller. For example, the window controller (e.g., one or more processors of the window controller) may cause the voltage supplied by the power supply to change based on the voltage drop measurements (e.g., by transmitting a command to the power supply to increase the supplied voltage, wherein the increase is determined at least in part based on the voltage drop measurements). In some embodiments, the voltage drop measurements may be provided to the window controller via a serial communication interface and / or using a serial communication protocol. Examples of serial communication interfaces include a 1-wire interface.
[0271] In some implementations, a current measurement circuit is used to measure the current through the plurality of IGWs. In some implementations, the current measurement circuit may include an operational amplifier (e.g., such as...). Figure 6 As shown and combined Figure 6 (as described above). In some embodiments, the current through the IGU can be used to determine the charge delivered to the IGU, for example, by integrating the current delivered over a period of time.
[0272] Figure 11An exemplary system 1100 for controlling multiple IGUs using a window controller is illustrated according to some embodiments. As shown, system 1100 includes a window controller 1102. Window controller 1102 may include one or more processors (e.g., hardware processors). Window controller 1102 controls IGUs 1104, 1106, 1108, and 1110. Each of IGUs 1104, 1106, 1108, and 1110 receives power from power supply 1112. For example, in some embodiments, window controller 1102 transmits an instruction to power supply 1112 causing power supply 1112 to provide a drive voltage to any of IGUs 1104, 1106, 1108, and 1110. Each IGU is operatively coupled to power supply 1112 via an H-bridge. For example, IGU 1104 is operatively connected to power supply 1112 via H-bridge 1114, IGU 1106 is operatively connected to power supply 1112 via H-bridge 1116, IGU 1108 is operatively connected to power supply 1112 via H-bridge 1118, and IGU 1110 is operatively connected to power supply 1112 via H-bridge 1120. In some embodiments, each IGU is operatively connected to a Voc circuit (e.g., a circuit configured to measure open-circuit voltage). In some embodiments, the Voc circuit may include a differential amplifier. The Voc circuit is operatively connected to the corresponding H-bridge. For example, Voc circuit 1122 is operatively connected to H-bridge 1114 and IGU 1104, Voc circuit 1124 is operatively connected to H-bridge 1116 and IGU 1106, Voc circuit 1126 is operatively connected to H-bridge 1118 and IGU 1108, and Voc circuit 1128 is operatively connected to H-bridge 1120 and IGU 1110. The Voc circuits can be configured to measure the open-circuit voltage across the corresponding IGU when the corresponding H-bridge is in a disabled (e.g., high-impedance) state. Each IGU is operatively connected to a Vdrop measurement circuit. The Vdrop measurement circuit measures the voltage drop across the distribution line segment to the IGU. For example, IGU 1104 is operatively connected to Vdrop measurement circuit 1130, IGU 1106 is operatively connected to Vdrop measurement circuit 1132, IGU 1108 is operatively connected to Vdrop measurement circuit 1134, and IGU 1110 is operatively connected to Vdrop measurement circuit 1136. Voltage drop measurement results are transmitted to window controller 1102 via serial communication interface 1140 (e.g., a 1-wire master interface). Measurement results are transmitted via a 1-wire bus. Current measurement circuit 1138 is used to measure the current supplied to IGUs 1104, 1106, 1108, and 1110. Current measurement circuit 1138 may include operational amplifiers operatively connected to power supply 1112 and each IGU.In some implementations, an analog-to-digital converter (ADC) 1142 is used to digitize the data provided to the window controller 1102.
[0273] In some implementations, the window controller system used to control multiple IGUs can be implemented using a printed circuit board (PCB). It should be noted that in instances where multiple IGUs are controlled by a single window controller system, each IGU can vary in size / dimension, cable length connecting the IGU to the window controller system, device parameters, and other aspects. In some cases, the window controller system may be able to drive up to 10 watts or up to 15 watts per IGU, allowing for relatively rapid coloring of each IGU.
[0274] In some implementations, the window controller system PCB can be configured to be used in conjunction with various types of power and / or communication protocols / systems, such as the G.hn protocol which provides 48V DC power via coaxial cable through a trunk line, the G.hn protocol which provides 110V AC power (e.g., from building power) via power lines, Power over Ethernet (PoE), etc. In other words, the common PCB can be filled with components based on the type of cable and / or protocol to be used to provide power and / or data signals to the PCB and therefore to be utilized by the window controller system. Utilizing a single PCB layout and filling the PCB during manufacturing can result in substantial cost savings in the manufacture of the window controller system. Furthermore, some implementations demonstrate particularly advantageous applications in buildings such as commercial office buildings or residential buildings. Some implementations are particularly suitable and appropriate for use in the construction of new buildings. For example, some implementations are designed to be used in conjunction with modern or new heating, ventilation, and air conditioning (HVAC) systems, indoor lighting systems, security systems, and electrical systems as a single, integrated, high-efficiency energy control system for the entire building or building complex. Some implementations are particularly suitable for integration with building management systems (BMS). Furthermore, implementations with Ethernet, Wi-Fi, Bluetooth, G.hn, or other communication capabilities are also well-suited for residential and other smaller-scale non-commercial applications. Other examples of implementations well-suited for residential or other smaller-scale applications are described in U.S. Patent Application No. 16 / 949,855 (Attorney’s File No. VIEWP041C3US), entitled “CONTROLLER FOR OPTICALLY-SWITCHABLE WINDOWS,” the entire contents of which are incorporated herein by reference.
[0275] In some implementations, the PCB may include a first set of components that are typically used regardless of the power / communication system employed. In other words, the first set of components may be attached (e.g., soldered or otherwise connected to) the PCB, regardless of the power / communication system used. The first set of components may include a processing unit, a memory device (e.g., a flash memory device), one or more IGU controllers, and / or connectors for each IGU controlled by the processing unit, each of the one or more IGU controllers corresponding to a different IGU to be controlled by the processing unit. The processing unit may perform many of the functions described herein as being performed by a window controller. For example, the processing unit may determine or control the color transition of each of the plurality of IGUs controlled by the processing unit, receive voltage and / or current data that can be used to determine an error state, etc. The processing unit is operatively coupled to each IGU controller such that the processing unit controls each IGU controller, and each IGU controller, in turn, controls each IGU. The processing unit may be communicatively coupled to another controller (e.g., a higher-level controller, such as a network controller or a master controller). The communication coupling may be a wired communication channel or a wireless communication channel. For example, as... Figure 16 As shown and in conjunction with the following text Figure 16 The processing unit can communicate with a higher-level controller or control panel using Wi-Fi and / or Bluetooth. The processing unit can be configured to generate various information in the PCB's memory device, such as color scheduling information, window band information, user preferences, etc., so that the processing unit can utilize the stored information regardless of whether the processing unit is communicatively connected to a control panel or a higher-level controller at a given time. For example, in some implementations, the processing unit can use the stored information to control each connected IGU in "offline" mode. In some embodiments, the memory device may store information indicating the power / communication system used to provide power and / or data signals to the PCB.
[0276] The PCB may also include a second set of components, wherein the components in the second set can be determined based on the power / communication system used. For example, the second set of components may include components specific to the utilized power / communication system, such as analog front-ends, splitters, and adapters. As a more specific example, in an instance providing a G.hn coaxial input (e.g., as power / communication to a window controller system), the second set of components may include a splitter operatively connected to the trunk and / or a coaxial coupling circuit configured to supply power from the trunk to the analog front-end components. As another more specific example, in an instance providing a G.hn powerline input, the second set of components may include a powerline coupling circuit configured to operatively connect to an AC power outlet (e.g., providing 110V AC or 220V AC) and an analog front-end component. The second set of components may also include an analog-to-digital converter configured to convert AC signals to DC signals. As yet another more specific example, in an instance providing an Ethernet input, the second set of components may include various connectors and / or adapters configured to receive Ethernet cables, process power and / or data signals using PoE, etc.
[0277] In some implementations, the cable network to one or more downstream devices (e.g., window controllers, sensor units, or assemblies, etc.) (e.g., those providing power and / or communication) may include at least one distribution connector, which may be referred to herein as a "splitter" or "connector". In some implementations, the distribution connector may be integrated into the window controller system PCB (e.g., as shown in the image). Figure 12 As shown and in conjunction with the following text Figure 12(As described above). For example, in some embodiments, the window controller PCB may be filled with one or more components that perform the functions of the distribution connector. The distribution connector (e.g., the circuitry and functions performed by the distribution connector) is described in more detail in PCT / US / 2021 / 017946, entitled “DATA AND POWER NETWORK OF AFACILITY,” the entire contents of which are incorporated herein by reference and for all purposes. In some embodiments, the distribution connector may include at least one connector. The distribution connector may distribute one or more time-varying signals and / or DC power within a network infrastructure. The distribution connector may couple two or more circuits together. For example, the distribution connector may couple at least two of an upstream circuit, a downstream circuit, and a branch circuit together. The upstream and downstream circuits may be part of a network bus (also referred to herein as a trunk). In some embodiments, the bus is a subsystem for connecting components and transferring data (e.g., signals) and / or DC power between those components. The distribution connector may be passive or active. The distribution connector may include active and passive components. A distribution connector may include one or more ground paths in an upstream circuit, downstream circuit, and branch circuit that are electrically connected together. A distribution connector may include a microprocessor or be operationally grounded to a microprocessor. A cable network may include passive distribution connectors and / or active distribution connectors. An active distribution connector has at least one active component. A passive distribution connector has passive components and no active components. In some embodiments, the distribution connector provides impedance matching. In some embodiments, the distribution connector may include a transformer. For example, implementations of distribution connectors utilizing transformers can provide impedance matching. Impedance matching can be used to reduce (e.g., eliminate) unwanted signal reflections from distribution connectors within the network infrastructure. In some embodiments, the distribution connector includes at least one filter. The distribution connector may include one or more low-pass filters, high-pass filters, and / or band-pass filters. Filters can be used to block certain frequencies from branch circuits (e.g., when branch circuits do not utilize such frequencies) and / or certain frequencies from downstream circuits (e.g., when all downstream circuits do not utilize such frequencies). For example, by blocking such frequencies (e.g., signal portions) as signals propagate through the network (e.g., through a bus), filters can reduce noise in the network. In some implementations, the distribution connector includes frequency offset capabilities. Specifically, control panels and distribution connectors can frequency offset one or more time-varying signals to reduce interference as the signal travels through the network. The signal can be offset to an unused region of the available spectrum on the medium (e.g., coaxial cable). The distribution connector may include passive or active components that remove the frequency offset when the signal is delivered from the network bus to a branch circuit, and that insert the frequency offset when the signal is delivered from the branch circuit to the network bus.The control panel may include a G.hn header (or other component) that adds a frequency offset to the time-varying signal when the control panel transmits the time-varying signal, and removes the frequency offset from the time-varying signal when it is received at the control panel.
[0278] In some implementations, the window controller system PCB can distribute power and / or data signals to and from the PCB's processing unit. Data signals may include time-varying signals, which may be referred to as digital communication, digital data, etc. Digital data may include power line communication signals, such as G.hn, etc. Or HD-PLC compatible signals. Digital data may include signals compatible with the MoCA (Multimedia Consortium for Coaxial Cable) protocol. Digital data may include signals compatible with other protocols, including Ethernet protocols such as 802.3bw, 802.3bp, 802.3ch, and / or 802.3cq. The first frequency window may extend from approximately 2MHz to approximately 200MHz (e.g., as used in the G.hn protocol). For example, the first frequency window may extend from approximately 500MHz to approximately 600MHz, from approximately 875MHz to approximately 1GHz, and / or from approximately 1.15GHz to approximately 1.5GHz.
[0279] Figure 12 This is a schematic diagram of an exemplary window controller system PCB according to certain specific implementations. As shown, the PCB may include a first set of components that can be used regardless of the power / communication system utilized. Therefore, the PCB may be filled with a first set of components for various different types of power / communication systems / protocols. The first set of components may include a DC / DC converter 1202, a processing unit 1204, a memory device 1206, an authentication device 1208, a set of IGU controllers (1210a, 1210b, 1210c, and 1210d) corresponding to a set of IGUs controlled by the window controller system, and a corresponding set of IGU connectors (1212a, 1212b, 1212c, and 1212d).
[0280] DC / DC converter 1202 can be configured to convert a first DC voltage to a second DC voltage (e.g., from 48V to 5V, from 23V to 5V, from 5V to 48V, etc.). DC / DC converter 1202 can provide DC power to other components of the window controller system PCB, such as processing unit 1206, Ethernet controller 1218, memory device 1206, IGU control circuits 1210a-1210d, etc. It should be noted that DC / DC converter 1202 can be configured to (where appropriate) increase or decrease the DC voltage.
[0281] Processing unit 1204 may be a processor that implements many of the functions described herein as being performed by a window controller. For example, processing unit 1204 may determine the shading level of a particular IGU, determine the drive voltage to be used, determine scheduling information instructing a particular IGU to transition to a particular shading state on a given date / time, communicate with a higher-level controller (e.g., a network controller or master controller) or control panel, receive electrical characteristics (e.g., voltage information, current information such as current leakage) to identify faulty states or malfunctioning IGUs, etc.
[0282] In some specific implementations, the processing unit 1204 can jointly control a group of IGUs, so that the IGUs simultaneously or almost simultaneously achieve a given shading state (e.g., as described above). Figure 9 and / or Figure 10 (as described above). In some implementations, processing unit 1204 can control the initial ramp time across a set of IGUs, such that the ramp-to-start time of the driving step is staggered across IGUs. This can reduce the power consumption of the window controller system to allow IGUs to color in combination with each other. In some implementations, processing unit 1204 can determine the ramp type and / or ramp rate of a given color transition to be performed by a given IGU. Note that the above is combined with... Figure 2 The slope type and slope rate are described in more detail. In some specific implementations, processing unit 1204 can determine different slope types and / or different slope rates for two different IGUs controlled by the window controller system. Therefore, processing unit 1204 can then transmit instructions indicating the determined slope type and / or determined slope rate to each IGU controller (e.g., 1210a-1210d), such that two different IGUs controlled by the same window controller can be colored using different slope types and / or different slope rates.
[0283] In some embodiments, processing unit 1204 may receive overwrite information. For example, overwriting may overwrite a shading state determined based on scheduling information, current photoelectric sensor information, etc. Overwriting may be received via the facility's local network. Overwriting may be received from a user device (e.g., a mobile phone, tablet computer, laptop computer, etc.), for example, via an application running on the user device. Overwriting may be received from a higher-level controller or other computing device (which may include cloud computing devices, control panel computing devices installed in the facility, or any other suitable computing device). In some embodiments, overwriting may be based on photoelectric sensor information (e.g., a photoelectric sensor as part of a sky sensor device configured to determine sky temperature, a photoelectric sensor located near the shading window, etc.).
[0284] It should be noted that in some embodiments, processing unit 1204 may be a G.hn baseband processing unit, and there may be an additional processor or microcontroller 1205 operatively coupled between processing unit 1204 and each IGU controller 1210a-1210d. In such embodiments, the functionality described herein, as performed by processing unit 1204, may be performed by processing unit 1204, additional processor or microcontroller 1205, or may be split between processing unit 1204 and additional processor or microcontroller 1205 in any suitable manner.
[0285] In some implementations, the processing unit 1204 can be configured to enter a sleep mode. When in sleep mode, the processing unit 1204 and other components of the window controller system consume less power. (The above is combined with...) Figure 6 The window controller sleep mode is described in PCT / US2016 / 041176 entitled "POWER MANAGEMENT FOR ELECTROCHROMIC WINDOW NETWORKS," the entire contents of which are incorporated herein by reference and are used for all purposes. In some embodiments, processing unit 1204 can enter sleep mode in response to a command from a higher-level controller, processor, or other computing device to which the window controller system (and therefore processing unit 1204) is communicatively coupled. The higher-level controller, processor, or other computing device may be within a facility (e.g., connected to the window controller system via one or more trunk segments, via a local area network, via a wireless network, etc.) or remotely (e.g., as a cloud controller or other remote computing device). Examples of higher-level controllers, processors, or computing devices include network controllers, main controllers, edge servers, control panels, etc. In some embodiments, the window controller system (e.g., including processing unit 1204) can wake from sleep mode. In some implementations, waking from sleep mode may be in response to a subsequent wake-up command from a higher-level controller, processor, or other computing device. Additionally or alternatively, in some implementations, waking from sleep mode may be in response to the elapsed duration of a predetermined time (e.g., five minutes, thirty minutes, one hour, etc.).
[0286] Memory device 1206 may store device parameters (e.g., associated with each IGU controlled by the window controller system), coloring scheduling information, etc. In some embodiments, processing unit 1204 may retrieve device parameters, scheduling information, etc., from memory device 1206. In some embodiments, update information (e.g., pushed from network controller, main controller, cloud computing device, etc.) may be stored in memory device 1206. Updates may be stored periodically (e.g., every 24 hours, weekly, monthly, etc.) or non-periodically.
[0287] The authentication device 1208 can store any suitable encrypted information and can allow the processing unit 1204 to securely communicate with and / or control the group of IGUs. Specifically, the authentication device 1208 can be a cryptographic coprocessor configured to accelerate the execution time of various cryptographic algorithms (e.g., those used in secure public-key authentication). An example of a component that can be utilized is the ATECC508A.
[0288] The window controller system may include a set of IGU controllers, each IGU controller being operatively connected to a given IGU. Processing unit 1204 can control each IGU controller, and each IGU controller in turn controls its corresponding IGU. Examples of IGU controllers are 1210a-1210d. Each IGU may be operatively connected to its corresponding IGU controller via a connected IGU (e.g., 1212a-1212d). It should be noted that in some specific implementations, processing unit 1204 may be able to perform computations, etc., that are more computationally intensive than those performed by the IGU controllers.
[0289] As described above, the PCB may also include a second set of components, which are attached to the PCB based on the power / communication system utilized. In other words, in a layout, the PCB may include space and traces for all possible second set of components, wherein the PCB is filled based on the power / communication system to be utilized.
[0290] For example, in an instance utilizing Ethernet (e.g., for PoE), the PCB may be filled with an Ethernet connector 1214, an Ethernet controller 1216, and PoE circuitry 1218. The Ethernet connector 1214 may be an Ethernet connector with Power over Ethernet (PoE) capability, such that the Ethernet connector 1214 is configured to provide power and data transmission capabilities. The Ethernet connector 1214 may provide 100Base Ethernet and / or 1000Base Ethernet connectivity. The Ethernet connector 1214 may be an RJ45 connector. The Ethernet controller 1216 may be bidirectionally coupled to the processing unit 1204 and may be configured to provide data in an appropriate physical layer format for subsequent transmissions as Ethernet transmissions. For example, the Ethernet controller 1216 may be configured to decode Ethernet data from an end device (e.g., an IGU controller) and provide unencoded data to the processing unit 1204 for subsequent upstream transmissions (e.g., to a control panel, to a higher-level controller / processor / computing device, etc.). Ethernet controller 1214 can be configured to receive downstream data (e.g., from a control panel, from a higher-level controller / processor / computing device, etc.) and provide downstream data to processing unit 1204. PoE circuitry 1218 can be configured to send and receive data. PoE circuitry 1218 can be configured to make power available for transmission over a physical line that can also carry Ethernet-formatted data.
[0291] For example, in an example where G.hn is used in conjunction with a coaxial input, the PCB may be filled with a splitter 1220, a coaxial coupling circuit 1222, and a filter 1224. The splitter 1220 can be configured to split or tapp power and / or data from the trunk line, which can be received via a coaxial cable. Note that the data can be formatted and / or encoded according to the G.hn protocol. Note that the splitter 1220 can be considered part of a distribution connector, as described above. The coaxial coupling circuit 1222 can be configured to connect signals from the splitter 1220 to an analog front-end 1226, which in turn connects to the processing unit 1204.
[0292] For example, in an example where G.hn is used in conjunction with a power line input, the PCB may contain a power line coupling circuit 1228, an analog front end 1230, an AC-to-DC voltage converter 1234, and a filter 1232. The power line coupling circuit 1228 can be configured to connect a signal from the power line input to the analog front end 1230, which is then connected to the processing unit 1204. The AC-to-DC voltage converter 1234 can be configured to convert 120V (or 220V) AC voltage to DC voltage, such as 48V. It should be noted that in some specific implementations, the analog front end 1226 can be used in conjunction with a G.hn input for both coaxial and power line inputs.
[0293] It should be understood that in some specific implementations, various other components may be provided in the window controller system. In some implementations, such components may be mounted on a subboard that is operatively connected to the main window controller system PCB.
[0294] In some implementations, the window controller system can be housed in a housing suitable for insertion into a wall socket. For example, in some implementations, the window controller system can be housed in a standard three- or four-gang socket box. Such housings allow for relatively direct installation in residential spaces (e.g., single-family homes, apartment buildings, etc.) or small commercial spaces. The housing may include a socket box in which the window controller system PCB is housed. (The above is a summary of the previous text.) Figure 12 Examples of such window controller system PCBs are shown and described. The window controller system PCB may include connectors for connecting to multiple (e.g., two, three, four, eight, etc.) IGUs. In some embodiments (e.g., in instances utilizing G.hn power line power / communication systems), the housing may be attached to include a power line PCB for receiving power and / or data signals, for example, via G.hn power lines. In some specific embodiments, the window controller system PCB and the power line PCB may be separated by a fixed interval. For example, in some specific embodiments, the power line PCB may be positioned above the window controller system PCB, with a fixed gap between the two PCBs. The fixed gap may be achieved via a spacer element positioned on the rear portion of an upper PCB (e.g., the PCB closer to the panel covering the housing), which rests on the upper portion of the lower PCB.
[0295] The window controller system may be attached to a panel that covers internal components (e.g., those housed within a socket box). The panel may be attached to the socket box via screws or any other suitable mechanism. In some embodiments, at least one outer edge of the socket box may be angled, for example, downward toward the panel. The panel may include one or more vents to allow airflow. In some embodiments, the one or more vents may be along an outer edge, which may be an angled outer edge. Alternatively, in some embodiments, the one or more vents may be located in the central portion of the panel. It should be noted that in some embodiments, a heat sink may be additionally disposed within the socket box. In such embodiments, the heat sink and the one or more vents may collectively provide cooling for the window controller system. In some embodiments, the panel may be attached to one or more LEDs that provide indications of the current state of any component. For example, in some embodiments, there may be an LED corresponding to each IGU that the window controller system can connect to and / or control, where each LED indicates the current state of the corresponding IGU. For example, red can indicate an error state associated with the IGU (e.g., the IGU is not currently properly connected to the window controller system, there is an error or malfunction associated with the IGU, etc.), and green can indicate that the corresponding IGU is operating correctly. Note that one or more light guides may be present, configured to direct light from the PCB within the housing to the panel.
[0296] Figure 13A and Figure 13B Different views of the window controller system housed within the housing are shown. As illustrated... Figure 13A A four-gang socket box 1302 is depicted. However, it should be noted that in some specific embodiments, a three-gang socket box may be used instead. Set within the socket box are a window controller system PCB 1304 and a power line PCB 1306. A panel 1310 may form a cover (e.g., to cover internal components such as PCBs 1304 and 1306) and may be attached to the socket box 1302 via one or more screws 1316. Note the sloping outer edge of the panel 1310. The window controller system PCB 1304 may include a set of IGU connectors, such as IGU connector 1308. Each IGU connector may be configured to connect to a single IGU controller via the window controller system. Although in Figure 13AFour IGU connectors are shown, but in some implementations, any suitable number of IGU connectors (e.g., two, three, eight, etc.) corresponding to the number of IGUs controllable by the window controller system may be included. Note that panel 1310 includes a set of LEDs, such as LED 1312. Each LED can indicate the current state of a given component associated with the window controller system (such as the POE system, IGUs connected to the window controller system, etc.). Each LED may have a corresponding light guide, such as light guide 1314 for guiding light upwards to panel 1310. Additionally, panel 1310 includes vents, such as vent 1318, which allow airflow and provide cooling for components of the window controller system.
[0297] Figure 13B This is a cross-sectional side view of an exemplary window controller system and housing. As shown in the figure, Figure 13B A portion of a socket box 1352 is depicted. A panel 1354 is attached (e.g., via one or more screws, not shown) to the socket box 1352. Note the angled outer edges of the panel 1354 (e.g., the top and bottom outer edges). Within the housing formed by the socket box 1352 and the panel 1354 are a power line PCB 1356 and a window controller system PCB 1358. The power line PCB 1356 may be configured with an AC power connector 1360 configured to receive an AC power cable. The window controller system PCB 1358 may be configured with an IGU connector 1362 to connect multiple IGUs to the window controller system (e.g., connected to the window controller system PCB 1358). Figure 13B Heat sink 1364 is also shown, which may be omitted in some specific implementations.
[0298] Figure 13C Views of a window controller system PCB 1370 and power line PCB 1372 according to some specific implementations are shown. It should be noted that the window controller system PCB 1370 and power line PCB 1372 can be housed within a housing formed by a socket box and a panel, such as... Figure 13A and Figure 13B As shown and in conjunction with the above text Figure 13A and Figure 13BAs shown in the figure, the window controller system PCB 1370 may include multiple IGU connectors, such as IGU connector 1382. Each IGU connector can be configured to receive a cable that connects the window controller system PCB 1370 to a corresponding IGU controlled by the window controller system PCB 1370. In one example, the IGU connector may be an M8K connector. The window controller system PCB 1370 may also include an Ethernet connector 1384. In one example, the Ethernet connector 1384 may be an IX connector. Panel 1376 shows a side view of the window controller system 1370. IGU connector 1382 can be seen in the side view of the window controller system 1370.
[0299] As shown in the figure, the power line PCB 1372 may include an AC power connector 1386, which is also visible in the side view of the power line PCB 1372 in panel 1374. In some embodiments, the power line PCB 1372 may be stacked on top of the window controller system PCB 1370 within the housing. In such embodiments, a notch 1388 may be present in the window controller system PCB 1370 to allow cables connected to the AC power connector 1386 to pass through.
[0300] As described above, in some embodiments, the window controller system is operatively coupled to a higher-level controller (e.g., a network controller or master controller) and / or a control panel, which may include a higher-level processor controlling the window controller. In some embodiments, such a control panel may include a housing sized to fit appropriately into, for example, a residential electrical enclosure panel. For example, in some embodiments, the height and / or width of the control panel may be less than about 24 inches, or less than about 18 inches. In some embodiments, the depth of the control panel may be less than about 6 inches, or less than about 4 inches, thereby allowing the control panel to be easily set flush with the wall during installation.
[0301] The control panel may include one or more processors or other computing devices. The processor may be configured for building or industrial automation. The control panel may include a DC power supply (e.g., a 48V power supply). The control panel may include one or more AC line filters. The control panel may include one or more power line bridges configured to provide networking capabilities to the control panel and any connected devices. The control panel may include an Ethernet port switch, which may be configured for any suitable number of ports (e.g., 8, 10, 12, etc.).
[0302] Figure 14A diagram illustrating an example of a powerline communication control panel 1400 is shown. As shown, the control panel 1400 includes a housing 1402. The control panel 1400 includes a set of DIN rail terminal blocks, such as DIN rail terminal block 1404. Each DIN rail terminal block can provide protection for electrical equipment that is part of the control panel 1400, for example, by preventing short circuits. The control panel 1400 may include one or more AC line filters, such as AC line filter 1406. The line filter can prevent downstream communication signals from propagating upstream to AC circuits outside of the desired network broadcast. This may be important, for example, when creating a separate control unit, such as in an apartment building. The control panel 1400 may include one or more powerline bridges, such as powerline bridge 1408. Each powerline bridge 1408 can be configured to provide networking (e.g., data) capability to connected devices via a connection to an AC power supply circuit that feeds downstream devices. The powerline bridge can incorporate communication signals on top of AC power-bearing signals. The control panel 1400 may include an Ethernet port switch 1410. The control panel 1400 may include a DC power supply 1412, which may be a 24V power supply, a 48V power supply, etc.
[0303] In some implementations, the window controller system can communicatively connect to a higher-level controller or processor, such as a network controller or master controller. For example, the window controller system can receive instructions and / or data from the higher-level controller or processor, where instructions may include shading scheduling (e.g., shading transition times and / or shading levels for various IGUs under the control of the window controller system), instructions for implementing shading overwrite commands, firmware updates utilized by the window controller system, etc. The window controller system can transmit data to the higher-level controller or processor, such as electrical characteristics associated with the IGUs controlled by the window controller system. In some implementations, the higher-level controller or processor can utilize electrical characteristics (e.g., voltage on the IGU, leakage current, etc.) to identify IGU faults or failures, to identify that specific components of the IGU may fail in the near future, etc. More detailed techniques for identifying error states have been described above. As described above, in some implementations, instructions received at the window controller system from a higher-level controller or processor can be stored in the window controller system's local memory, such that the window controller system is configured to use the stored instructions even when the communication channel between the window controller system and the higher-level controller or processor is inoperable (e.g., in "offline" mode). When update instructions are transmitted by the higher-level controller or processor, for example, in "online" mode, the window controller system can then update the stored instructions.
[0304] In some implementations, higher-level controllers or processors can be implemented on an edge server within the facility but remote from the window controller system. For example, in instances where a window controller system is implemented in a given room of a residence (e.g., living room, bedroom, etc.) or other facility (e.g., conference room, etc. in an office building), the edge server can be within the facility but remote from the window controller system, such as in a common area of the building or other locations where building operating equipment can be housed. Additionally or alternatively, the higher-level controller or processor can be a remote cloud device remote from the facility.
[0305] In some implementations, a higher-level controller or processor may receive data from one or more sensors distributed throughout the facility. These sensors may include light detectors (e.g., photoelectric sensors), sound sensors, motion detectors, volatile organic compound (VOC) sensors, humidity sensors, temperature sensors, carbon dioxide sensors, etc. The higher-level controller or processor may then use, for example, one or more machine learning models to determine the shading level of a specific window or window zone based on the sensor data. The shading level can then be transmitted to a given window controller system that controls the specific window or window zone. In some implementations, the higher-level controller or processor may then be communicatively coupled to another controller or processor, which may be facility-local or remote and can be configured to transmit updates to the machine learning model, etc., to an intermediate controller (e.g., an edge computer). For example, as described above, a network controller may be coupled to a main controller.
[0306] Figure 15 and Figure 16 Two exemplary methods are shown in a window controller system that can communicatively connect to a higher-level controller or processor. Figure 15 The example shown utilizes a wired communication system. In contrast, in... Figure 16 The example shown utilizes a wireless communication system. It should be understood that the following text, in conjunction with... Figure 15 and Figure 16 The window controller system shown and described can be used in conjunction with the above. Figure 12 The window controller system PCB shown and described is configured and can optionally be housed in a housing including a socket box and a panel, as described above. Figures 13A to 13C Shown and described. For example, in order to utilize Figure 15 The wired communication system shown can be configured with Ethernet or G.hn powerline power / communication system components on the window controller system PCB. To utilize... Figure 16The wireless communication system shown may include a window controller system PCB configured with components providing Wi-Fi and / or Bluetooth communication. It should be noted that in some implementations, components for performing wireless communication (e.g., Wi-Fi, Bluetooth, etc.) may be provided on the window controller system PCB via a daughterboard operatively connected to the main window controller system PCB, as described above. Figure 12 The PCB shown and described.
[0307] Turn Figure 15 Window controllers 1502 and 1504 are shown. Each window controller can control multiple IGUs. For example, window controller 1502 controls IGUs 1506a-1506d, and window controller 1504 controls IGUs 1508a-1508d. It should be noted that although four IGUs are depicted as being controlled by each window controller, this is merely exemplary, and in some specific implementations, each window controller can control any suitable number of IGUs (e.g., one, two, five, ten, fifteen, etc.). Communication and / or data can be provided to each window controller via a networking component 1510, which may include a residential gateway 1512, an Ethernet / G.hn adapter 1514, and a thread boundary router 1516. In some specific implementations, the thread boundary router 1516 can wirelessly communicate with one or more IoT devices communicatively connected to the thread boundary router 1516 (e.g., using the Wi-Fi protocol). In some embodiments, the components in the networking component 1510 may be packaged together in a single housing.
[0308] As shown in the figure, the residential gateway 1512 is operatively connected to an Ethernet switch 1524, which in turn is operatively connected to an edge server 1522. The edge server 1522 can implement a higher-level controller or processor relative to window controllers 1502 and / or 1504. For example, the edge server 1522 can determine building operation control parameters, which may include color transitions of IGUs connected to window controllers 1502 and / or 1504. The edge server 1522 can determine building operation control parameters (including color transitions) based on sensor device data from one or more sensors located in the facility. The edge server 1522 can be operatively connected to the Internet 1526 via a router 1520. In some implementations, the edge server 1522 can transmit and / or receive data, programs, etc., from cloud devices or remote servers. For example, the edge server 1522 can receive updates to one or more machine learning algorithms from cloud devices or remote servers, wherein the machine learning algorithms are configured to use sensor data to determine building operation parameters. In some implementations, the edge server 1522 can push the collected building data (which may include sensor data and / or IGU data) to cloud devices or remote servers for data analysis.
[0309] Figure 16 An exemplary system is shown, according to some specific implementations, in which window controllers communicate with higher-level controllers using wireless communication protocols. As shown, window controller 1602 controls IGUs 1606a-1606d, and window controller 1604 controls IGUs 1608a-1608d. Each window controller can be configured to utilize one or more wireless communication protocols, such as Wi-Fi, Bluetooth, etc. For example, each window controller system PCB (e.g.) Figure 12 As shown and in conjunction with the above Figure 12The window controller system may be populated with one or more chips or components configured to provide wireless communication capabilities to the window controller system. It should be noted that the number of window controllers and the number of IGUs controlled by each window controller are merely illustrative. Any suitable number of window controllers (e.g., ten, twenty, one hundred, etc.) can be present in the facility, each controlling any suitable number of IGUs (one, two, five, ten, etc.). Each window controller can communicatively connect to Wi-Fi access point 1610. Wi-Fi access point 1610 can be located within the facility. Each window controller can communicate with a remote cloud controller 1612 using a wireless communication protocol such as Wi-Fi. It should be noted that in this example, the facility does not require an edge computer, control panel, or other higher-level controllers local to the facility, which may be advantageous in some residential environments (such as single-family homes). Similar to the above, the cloud controller 1612 can communicatively connect to the window controllers 1602 and / or 1604 to send and receive data, instructions, programs, etc. For example, the cloud controller 1612 can be configured to push instructions, color scheduling, etc., to the window controllers 1602 and / or 1604. Furthermore, the window controllers 1602 and / or 1604 can be configured to transmit electrical characteristics and / or other IGU data to the cloud controller 1612, for example, to diagnose faults or error states. Similar to the above... Figure 12 and Figure 15 As described, window controllers 1602 and / or 1604 can be configured to operate in an "offline" mode, where stored instructions can be utilized when the window controllers are not communicatively connected to cloud controller 1612.
[0310] In some embodiments, multiple window controllers (e.g., window controllers 1602 and / or 1604) configured for Wi-Fi and / or Bluetooth communication within a facility or area of a facility can be configured to form a mesh network. In some such embodiments, the window controllers may be able to wirelessly communicate with each other (e.g., using Wi-Fi and / or Bluetooth) without utilizing intermediate nodes. Furthermore, in some embodiments where multiple window controllers are connected in a network (e.g., a mesh network), wireless power can be delivered from one window in the network to another. In some embodiments, each window controller configured with wireless capabilities (e.g., Wi-Fi and / or Bluetooth capabilities) can be considered a radio node or client. The mesh network may also include mesh routers and gateways, where routers forward traffic to and from gateways. In some embodiments, the gateway may be connected to the network. In some implementations, radio nodes or clients (e.g., window controllers of the mesh network) may form a “mesh cloud” to store and / or process data collected by the individual window controllers. In some specific implementations, data from the mesh cloud can be transmitted to, for example, a c...
Claims
1. A window controller system for controlling multiple optically switchable devices, the window controller system comprising: A printed circuit board, the printed circuit board including a first plurality of device packages and a second plurality of device packages, the first plurality of components being mounted to the first plurality of device packages, wherein a subgroup of the second plurality of device packages is filled with the second plurality of components, and wherein the first plurality of components includes: Multiple insulated glass unit (IGU) controllers, each configured to operatively connect to a corresponding IGU in the window controller system, and A processing unit, configured to control each of the plurality of IGU controllers, And wherein the second plurality of components are selected based on the cable type and / or protocol type used to provide power and data signals to the printed circuit board; At least one of the plurality of IGU controllers is configured to place the at least one of the plurality of IGUs in a predetermined optical state in response to leakage current from the corresponding at least one of the plurality of IGUs by applying a holding voltage to the corresponding at least one of the plurality of IGUs.
2. The window controller system of claim 1, wherein the protocol type includes at least one of the following: Home Networking Protocol or Power over Ethernet (PoE) protocol.
3. The window controller system according to claim 2, wherein the home networking protocol is the G.hn protocol.
4. The window controller system of claim 1, wherein the cable type includes at least one of the following: coaxial cable, power line cable, or twisted pair cable.
5. The window controller system of claim 1, wherein the protocol type includes G.hn, and wherein the second plurality of components includes one of: (i) a first subgroup component configured to utilize G.hn coaxial input, or (ii) a second subgroup component configured to utilize G.hn power line input.
6. The window controller system of claim 5, wherein the first subgroup component configured to utilize the G.hn coaxial input includes a splitter configured to be operatively coupled to the trunk and a coaxial coupling circuit configured to provide power from the trunk to the analog front-end component.
7. The window controller system of claim 6, wherein the analog front-end component is operatively coupled to the processing unit.
8. The window controller system of claim 5, wherein the second subgroup of components configured to utilize the G.hn power line input includes an analog front-end component and a power line coupling circuit configured to be operatively connected to an AC power outlet.
9. The window controller system of claim 8, wherein the analog front-end component is operatively coupled to the processing unit.
10. The window controller system of claim 9, wherein the second subgroup further includes an analog-to-digital converter (ADC) configured to convert an AC signal from the AC power outlet into a DC signal.
11. The window controller system of claim 1, wherein the protocol type includes G.hn, and wherein the second plurality of components includes a third subgroup of components to be used in conjunction with either a G.hn coaxial input or a G.hn powerline input.
12. The window controller system of claim 1, wherein the first plurality of components further comprises a memory device.
13. The window controller system of claim 12, wherein the memory device comprises a flash memory device.
14. The window controller system of claim 12, wherein the memory device is configured to store an indication of the cable type and / or the protocol type for providing the power and the data signals.
15. The window controller system of claim 1, wherein the processing unit is configured to characterize leakage current from one or more of the corresponding plurality of IGIUs.
16. The window controller system of claim 1, wherein the processing unit is further configured to communicate with a computing device.
17. The window controller system of claim 16, wherein the computing device is a cloud device located remotely from the building on which the window controller system is installed.
18. The window controller system of claim 16, wherein the processing unit is further configured to: Detecting abnormal events based on the characterized leakage current; and In response to the detection of the anomalous event, data associated with the characterized leakage current is transmitted to the computing device.
19. The window controller system of claim 18, wherein the computing device is a cloud computing device.
20. The window controller system of claim 18, wherein the computing device is housed in a control panel installed in the facility, wherein the window controller system is installed in the facility.
21. The window controller system of claim 1, further comprising a memory configured to store window band information associated with the plurality of IGUs and / or shading scheduling information associated with the plurality of IGUs.
22. The window controller system of claim 21, wherein the processing unit is configured to: Receive the window zone information and / or the shading scheduling information from the computing device; and The window zone information and / or the coloring scheduling information are stored in the memory.
23. The window controller system of claim 1, wherein the processing unit is configured to: Receive overwrite of a coloring command for at least one of the plurality of IGUs; and This causes the at least one IGU to transition to a colored state based on the received overwrite.
24. The window controller system of claim 23, wherein the overwrite is received via an application running on a mobile device.
25. The window controller system of claim 23, wherein the overwrite is received via a local network communicatively connected to the processing unit.
26. The window controller system of claim 23, wherein the overwriting is based on information obtained by a sky sensor device configured to measure solar radiation outside the facility in which the window controller system is installed.
27. The window controller system of claim 26, wherein the overwrite is received via a local network communicatively connected to the sky sensor device and the processing unit.
28. The window controller system of claim 1, wherein the processing unit is configured such that each IGU controller applies a drive voltage with a ramp rate to the corresponding IGU, wherein the first ramp rate associated with a first IGU among the plurality of IGUs is different from the second ramp rate associated with a second IGU among the plurality of IGUs.
29. The window controller system of claim 28, wherein the drive voltage is applied to the first IGU at a time offset from when the drive voltage is applied to the second IGU.
30. The window controller system of claim 1, wherein the processing unit is configured to communicate with at least one computing device, the at least one computing device being configured to control the operation of a building in which the window controller system is disposed.
31. The window controller system of claim 30, wherein the at least one computing device is an edge server.
32. The window controller system of claim 26, wherein the processing unit is configured to enter a sleep mode in response to a signal from at least one computing device.
33. The window controller system of claim 1, wherein the first plurality of components further includes at least one component configured to provide one or more wireless communication channels.
34. The window controller system of claim 33, wherein the one or more wireless communication channels utilize at least one of the Wi-Fi communication protocol or the Bluetooth communication protocol.
35. The window controller system of claim 34, wherein the processing unit is configured to communicate with a cloud device using the Wi-Fi communication protocol.
36. The window controller system of claim 35, wherein the processing unit is configured to receive one or more updates from the cloud device using the Wi-Fi communication protocol.
37. The window controller system of claim 34, wherein the processing unit is configured to participate in a mesh network together with at least one other processing unit associated with at least one other window controller system.
38. The window controller system of claim 1, further comprising a second processing unit operatively connected between the processing unit and each of the plurality of IGU controllers, wherein the second processing unit is configured to control each of the plurality of IGU controllers.
39. A window controller system for controlling multiple optically switchable devices, the window controller system comprising: Housing, wherein the housing includes a 3- or 4-gang socket box and a panel; and A printed circuit board comprising multiple components, the multiple components including: multiple insulated glass unit (IGU) controllers, each of the multiple IGU controllers being configured to control an IGU among a corresponding plurality of IGUs operatively connected to the window controller system; and a processing unit configured to control each of the multiple IGU controllers; At least one of the plurality of IGU controllers is configured to place the at least one of the plurality of IGUs in a predetermined optical state in response to leakage current from the corresponding at least one of the plurality of IGUs by periodically applying a holding voltage to the corresponding at least one of the plurality of IGUs.
40. The window controller system of claim 39 further includes a heat sink disposed in the housing.
41. The window controller system of claim 39, wherein the panel is attached to the 3- or 4-gang socket box via a plurality of screws.
42. The window controller system of claim 39, wherein at least one edge of the panel is angled.
43. The window controller system of claim 39, wherein the panel includes a plurality of air vents.
44. The window controller system of claim 39 further includes a cooling fan disposed within the housing.
45. The window controller system of claim 39 further includes a plurality of light-emitting diode (LED) indicator symbols.
46. The window controller system of claim 39 further includes a second printed circuit board configured to provide power and / or data via a power line system.
47. The window controller system of claim 46, wherein the second printed circuit board includes an AC power connector.
48. The window controller system of claim 46, wherein the second printed circuit board is disposed above the printed circuit board and closer to the panel than the printed circuit board.
49. The window controller system of claim 48, wherein the printed circuit board includes a notch configured to allow a power line cable to pass through the notch to reach the second printed circuit board.
50. A method for controlling the shading of multiple optically switchable devices, comprising: (a) In conjunction with the shading transition from a first shading state to a second shading state, a drive voltage is applied to two or more optically switchable devices via a window controller, wherein applying the drive voltage to the two or more optically switchable devices includes providing a voltage from a power supply shared by the two or more optically switchable devices; (b) For each of the two or more optically switchable devices, monitor parameters indicating the state of the color transition; (c) Repeat (a) and (b) until it is determined that one or more optically switchable devices have completed the color transition to the second color state; (d) In response to determining at (c) that the one or more optical switchable devices have completed the color transition to the second state, a holding voltage is applied to the one or more optical switchable devices, while the driving voltage is continued to be applied to the remaining one or more optical switchable devices among the two or more optical switchable devices that have not yet completed the color transition; as well as (e) Repeat (b) to (d) until the two or more optically switchable devices have completed the color transition; The window controller is configured to place the optical switchable device in a predetermined optical state in response to leakage current from one of the two or more optical switchable devices by applying a holding voltage to the optical switchable device.
51. The method of claim 50, wherein monitoring the parameters indicating the state of the color transition includes individually measuring the open-circuit voltage (Voc) and / or the delivered charge for each of the two or more optically switchable devices.
52. The method of claim 51, wherein determining that the one or more optically switchable devices have completed the shading transition to the second shading state comprises (i) determining that the Voc measured for the one or more optically switchable devices meets or exceeds a target Voc, and / or (ii) determining that the charge delivered to the one or more optically switchable devices meets or exceeds a target charge to be delivered to the one or more optically switchable devices.
53. The method of claim 50, further comprising: (f) For an optically switchable device to which the holding voltage is being applied, measure the holding state Voc; (g) Determine whether the Voc of the holding state is less than a predetermined Voc threshold; as well as (h) In response to determining that the hold state Voc is less than the predetermined Voc threshold, a voltage pulse is applied to the optical switchable device.
Citation Information
Patent Citations
Self-contained EC IGU
US10303035B2
Multi-sensor having a light diffusing element around a periphery of a ring of photosensors
US10690540B2
Controller for optically-switchable windows
US10809589B2
Controllers for optically-switchable devices
US11300848B2
Self-contained EC IGU
US11314139B2
