This disclosure relates generally to a cove light fixture with hidden integrated air return. In particular, the systems and methods of this disclosure can provide a cove lighting structure including a return air structure.
Light fixtures can be installed in various entities (e.g., interior of a building). The light fixtures can be coupled to a power source. The power source can store and supply power for the light fixtures. The light fixtures can receive power from the power source for illumination.
Systems and methods of this disclosure are directed to cove lighting with return air. The return air can be hidden such that it is not viewable from a floor or ground when installed. In various structural architectures, entities may desire to include mechanical systems, components, technologies, or other structures in the interior of their building. However, blending or including some of these structures as part of the interior may interfere with the interior design of the building. It may be difficult to maintain a minimalistic design when certain structures occupy the interior space. Instead, it may be desired for the structures (e.g., lighting, smoke detector, fire suppression system, ventilation system, sensors, or wireless networking components, among other architectural interior components) to operate or function in the background without being in the view of the entities. Further, in certain architectural spaces, flangeless trim return air systems may be installed, which involves tape and spackled into the wall system or ceiling of the building. In such cases, it may be desired to minimize the complexity or resources involved in the installation of certain interior structures or components (e.g., return air system).
The systems and methods discussed herein can provide a cove lighting structure implemented with a return air structure (e.g., return air system). The cove lighting structure can contribute to or enhance the interior design of a building by combining or blending the return air structure, a cove structure, and at least one light fixture as part of the cove lighting structure. By integrating the air return with the cove light fixture, the air return can be hidden or not viewable from certain angles, thereby providing a more seamless design while reducing components or structures and reducing complexity of installation. For example, the cove lighting structure can include a cove structure (e.g., extruded aluminum cove or extrusion) composed of at least one type of suitable material, such as metal (e.g., aluminum, steel, copper, etc.), wood, or plastic, among others. The cove lighting structure can include the return air structure configured to receive return air for a heating, ventilation, and air conditioning (HVAC) system, or other types of ventilation systems. The return air structure may be embedded with the cove structure. The cove lighting structure can include at least one light fixture configured to provide cove lighting for the interior of a building.
The cove structure, the return air structure, and the lighting structure can be a part of a single structure or component for installation in the interior of the building. In some cases, at least one of the cove structure, the return air structure, or the lighting structure may be an independent component/structure coupled to or installed on one or more other structures. The cove structure can be configured to reduce, minimize, or block the visibility of the lighting structure and the return air structure, e.g., from certain viewing angles. Hence, by combining the features of the cove structure, the return air structure, and the lighting structure as part of the cove lighting structure, the systems and methods of the technical solution discussed herein can improve the interior design of the building by hiding the return air structure and the lighting structure from view, and minimize the complexity and resources for installation of the return air structure.
In one aspect, this disclosure is directed to a system for cove lighting. The system can include a cove lighting structure. The cove lighting structure can include a return air structure comprising a vent configured to receive return air. The cove lighting structure can include a cove structure connected with a platform extended laterally from the return air structure. The cove lighting structure can include a light fixture comprising a light source configured to provide cove lighting. The light fixture can be positioned above the platform and between the cove structure and the return air structure.
The vent of the return air structure can detect the return air towards a heating, ventilation, or air condition system. The return air structure can be positioned to dissipate heat from the light source. The return air structure can comprise a plurality of slots to form a plurality of vents. The return air structure can comprise a height that is less than a height of the light fixture.
The cove lighting structure can include a second return air structure separated from the return air structure by a predetermined distance. The cove structure can be mechanically connected to a ceiling. The cove structure can be formed from an extrusion of one or more metals.
The light source can be positioned to direct light towards a surface of at least one of a ceiling or a wall. The light fixture can comprise an optical window that directs light at least 180 degrees. The light source can be electrically connected to a backup battery system. The light source can be closer to a wall of the cove structure relative to the return air structure. The light source can be separated from the return air structure by a predetermined distance.
In an aspect, this technical solution can be directed to an apparatus. The apparatus can include a return air structure comprising a vent configured to receive return air. The apparatus can include a cove structure connected with a platform extended laterally from the return air structure. The apparatus can include a light fixture comprising a light source configured to provide cove lighting. The light fixture can be positioned above the platform and between the cove structure and the return air structure.
The return air structure can comprise a plurality of slots to form a plurality of vents. The apparatus can include a second return air structure separated from the return air structure by a predetermined distance. The cove structure can be formed from an extrusion of one or more metals. The light fixture can comprise an optical window that directs light at least 180 degrees.
In an aspect, this technical solution can be directed to a method. The method can include providing a cove lighting structure. The cove lighting structure can include a return air structure comprising a vent configured to receive return air. The cove lighting structure can include a cove structure connected with a platform extended laterally from the return air structure. The cove lighting structure can include a light fixture comprising a light source configured to provide cove lighting. The light fixture can be positioned above the platform and between the cove structure and the return air structure.
The method can include mechanically connecting the return air structure to direct the return air towards a heating, ventilation, or air condition system. The method can include coupling the cove lighting structure to a ceiling or a wall.
These and other aspects and implementations are discussed in detail below. The foregoing information and the following detailed description include illustrative examples of various aspects and implementations, and provide an overview or framework for understanding the nature and character of the claimed aspects and implementations. The drawings provide illustration and a further understanding of the various aspects and implementations, and are incorporated in and constitute a part of this specification.
The accompanying drawings are not intended to be drawn to scale. Like reference numbers and designations in the various drawings indicate like elements having similar structure or functionality. For purposes of clarity, not every component may be labeled in every drawing. In the drawings:
The features and advantages of the present solution will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, in which like reference characters identify corresponding elements throughout. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.
Following below are more detailed descriptions of various concepts related to, and implementations of, methods, apparatuses, and systems of cove light fixture with hidden integrated air return. The various concepts introduced above and discussed in greater detail below may be implemented in any of numerous ways.
In various structural architectures, it may be desired for an interior of a building to include mechanical systems, components, technologies, or other structures while maintaining a minimalistic design. However, it may be challenging for certain structures, such as a return air system, to operate or function in the background without being in the view of the entities or individuals present in the interior space of the building. In certain architectural spaces, flangeless trim return air systems may be installed, which involves tape and spackled into the wall system or ceiling of the building. In such cases, it may also be desired to minimize the complexity or resources involved in the installation of certain interior structures or components (e.g., return air system).
The systems and methods discussed herein can provide a cove lighting structure implemented with a return air structure (e.g., return air system). The cove lighting structure can contribute to or enhance the interior design of a building by combining or blending the return air structure, a cove structure, and at least one light fixture as part of the cove lighting structure. For example, the cove lighting structure can include a cove structure (e.g., extruded aluminum cove or extrusion) composed of at least one type of suitable material, such as metal (e.g., aluminum, steel, copper, etc.), wood, or plastic, among others. The cove lighting structure can include the return air structure configured to receive return air for a heating, ventilation, and air conditioning (HVAC) system, or other types of ventilation systems. The return air structure may be embedded with the cove structure. The cove lighting structure can include at least one light fixture configured to provide cove lighting for the interior of a building.
The cove structure, the return air structure, and the lighting structure can be a part of a single structure or component for installation in the interior of the building. In some cases, at least one of the cove structure, the return air structure, or the lighting structure may be an independent component/structure coupled to or installed on one or more other structures. The cove structure can be configured to reduce, minimize, or block the visibility of the lighting structure and the return air structure, e.g., from certain viewing angles. Hence, by combining the features of the cove structure, the return air structure, and the lighting structure as part of the cove lighting structure, the systems and methods of the technical solution discussed herein can improve the interior design of the building by hiding the return air structure and the lighting structure from view, and minimize the complexity and resources for installation of the return air structure.
Referring now to
The one or more components of the system 100 (e.g., computing device 101 or light fixture 104) can communicate with each other by establishing a communication channel via the network 102. For example, the computing device 101 can communicate with the light fixture 104 via the network 102. The various different network devices (e.g., computing device 101, light fixture 104, etc.) can establish at least one communication channel between each other via the network 102 or different networks 102, such as for transmission or reception of information. In some cases, one or more of the devices (e.g., computing device 101 or light fixture 104) may be located in a physical location or space (e.g., a building or a structural architecture), such that communication can be performed via wired connection(s).
The network 102 can include computer networks such as the Internet, local, wide, metro or other area networks, intranets, satellite networks, other computer networks such as voice or data mobile phone communication networks, and combinations thereof. The network 102 may be any form of computer network that can relay information between the one or more components of the system 100. The network 102 can relay information between the computing device 101 and light fixtures 104, amongst others. In some implementations, the network 102 may include the Internet and/or other types of data networks, such as a local area network (LAN), a wide area network (WAN), a cellular network, a satellite network, or other types of data networks. The network 102 may also include any number of computing devices (e.g., computers, servers, routers, network switches, etc.) that are configured to receive and/or transmit data within the network 102. The network 102 may further include any number of hardwired and/or wireless connections. Any or all of the devices or components with communication interfaces described herein (e.g., computing device 101 or light fixture 104) may communicate wirelessly (e.g., via Wi-Fi, cellular, radio, etc.) with a transceiver that is hardwired (e.g., via a fiber optic cable, a CAT5 cable, etc.) to other devices or components in the network 102. Any or all of the devices or components described herein (e.g., computing device 101 or light fixture 104) may also communicate wirelessly with other devices or components of the network 102 via a proxy device (e.g., a router, network switch, or gateway).
The computing device 101 (e.g., client device or operator device) can include at least one interface for establishing a connection to the network 102. The computing device 101 can include a lighting application 106. The lighting application 106 can be a hardware, software, or a combination of hardware and software components configured or programmed to interface with the light fixture 104. The computing device 101 can communicate with other components of the system 100 via the network 102, such as the light fixture(s) 104. For example, computing device 101, using the lighting application 106, can communicate with the light fixture 104 by forwarding data packets to the network 102 for forwarding to the light fixture 104. The computing device 101 can send commands or instructions to the light fixture 104 to adjust their setting, such as brightness, color, “on” duration, “off” duration, etc. In some cases, the computing device 101 can communicate directly to the one or more light fixture 104 via wired or wireless connection, such as without communicating with an intermediary device (e.g., the network 102). The computing device 101 may be local to or remote from the physical location of the light fixture 104.
The computing device 101 can include, store, execute, or maintain various application programming interfaces (“APIs”) in the memory (e.g., local to the computing device 101). The APIs can include or be any types of API, such as Web APIs (e.g., open APIs, Partner APIs, Internal APIs, or composite APIs), web server APIs (e.g., Simple Object Access Protocol (“SOAP”), XML-RPC (“Remote Procedure Call”), JSON-RPC, Representational State Transfer (“REST”)), among other types of APIs or protocol. The computing device 101 can use at least one of various protocols for communication other devices. The protocol can include at least a transmission control protocol (“TCP”), a user datagram protocol (“UDP”), or an internet control message protocol (“ICMP”). The communicated data can include a message, a content, a request, or otherwise information to be transmitted from the computing device 101 to other devices in the network 102.
The computing device 101 can be operated by the operator, user, or entity. The computing device 101 can receive the status information from individual light fixtures 104. The computing device 101 can receive a command or instructions input by the operator, such as configuring the setting for the light fixture 104. The computing device 101 can send updated configurations to one or more light fixtures 104. The computing device 101 may update the configurations of the light fixture 104 responsive to receiving inputs from the operator or after a predetermined time interval.
The computing device 101 may include a user interface, such as a graphical user interface (GUI) or one or more input/output (I/O) devices. The GUI can include or correspond to a touchscreen, a display (e.g., including features or functionalities of the display 535), etc. The I/O device can include at least one of a mouse, a keyboard, a microphone, one or more speakers, one or more cameras, one or more biometric scanners, one or more environmental sensors, one or more accelerometers, etc. The GUI may present or enable/activate a display of information related to the lighting application 106, e.g., including information or data associated with the light fixture 104.
For example, the computing device 101 can provide a display of the lighting application 106 via the GUI. The GUI can include any non-limiting GUI elements for presenting the lighting application 106, such as but not limited to icons, interactive elements (e.g., buttons, sliders, or dropdown menus), images, settings, notifications, texts, etc. In some cases, the lighting application 106 can include one or more settings or configurations of the light fixture 104 (or the light module 110). The computing device 101 can provide the one or more settings or configurations of the light fixture 104 for display via the GUI. The computing device 101 may receive instructions or an indication of interaction from the operator via the GUI, e.g., interaction with the lighting application 106. The computing device 101 may receive changes to the settings of the light fixture 104 via the GUI. The computing device 101 may transmit data packets including updated configuration to the light fixture 104 using the lighting application 106.
The light fixture 104 can correspond to an electrical device configured with at least one interface 108, and at least one light module 110, among other hardware or software components, such as sensors, indicators, battery, memory, etc. The light module 110 can include at least one light source 112. The light fixture 104 can be positioned or configured for uplighting. Uplighting can refer to a lighting effect provided by positioning one or more light fixtures 104 vertically, including relatively near the floor and facing the light fixtures 104 relatively upward (e.g., towards the ceiling). The specific configuration, positioning, or lighting direction may be adjustable, and not limited to a specific angle or height, for example. In some cases, the light fixture 104 can be positioned relatively near a cove portion of the wall or ceiling, among other locations. The uplighting can provide a level of lighting to the ceiling, thereby ensuring the ceiling, and the interior space, are lit. In some configurations, the light fixture 104 can be positioned to face other directions, such as the wall, a cove structure, etc. To achieve uplighting, the light fixture 104 can include a wide optical window, thereby ensuring that any opaque part of the light fixture 104 may not create a lighting cutoff, e.g., of less than 180 degrees. For example, the optical window of the light fixture 104 can allow the light source 112 to direct light at least 180 degrees. Ensuring that no cutoff is presented can mitigate scalloping effects or cutoff lines in the illumination generated by the light fixtures 104. For example, the light fixtures 104 can include an optical system (e.g., corresponding to or as a part of the light module 110). The optical system can include a side component at a predefined angle to the optic (e.g., light sources 112) configured to allow the light to reflect and transmit upward, such as towards the ceiling into the space. According to the configuration of the light fixture 104, the light beam can be widened beyond at least 180 degrees to create uplighting.
In some configurations, the light fixture 104 may be positioned relative to a cove portion of other structures, not limited to the wall or ceiling, such as other objects or architectures. For example, in some aspects, the light fixture 104 may be positioned relatively near a cove portion between the floor and the wall, e.g., the light fixture 104 positioned proximate to the floor directing the lighting effect horizontally to the cove portion formed between the floor and the wall. In another example, the light fixture 104 may be positioned relatively near a cove portion of an object or structure, not limited to the wall or the ceiling. In some other aspects, the light fixture 104 may be positioned according to or relative to the location of the vents (e.g., return air vent 204, such as described in conjunction with at least one of
The interface 108 can interface with the network 102, devices, or components within the system 100 (e.g., the computing device 101), or components of the light fixture 104 (e.g., light module 110). The interface 108 can include features and functionalities to interface with the aforementioned components. For example, the interface 108 can include power transmission lines (e.g., cables or conductive structures), standard telephone lines LAN or WAN links (e.g., 802.11, T1, T3, Gigabit Ethernet, Infiniband), broadband connections (e.g., ISDN, Frame Relay, ATM, Gigabit Ethernet, Ethernet-over-SONET, ADSL, VDSL, BPON, GPON, fiber optical including FiOS), wireless connections, or some combination of any or all of the above. Communication connections can be established using a variety of communication protocols (e.g., TCP/IP, Ethernet, ARCNET, SONET, SDH, Fiber Distributed Data Interface (FDDI), IEEE 802.11a/b/g/n/ac CDMA, GSM, WiMax and direct asynchronous connections). Electric power connections can be established via overhead transmission lines, underground transmission lines, or subtransmission lines, among other types of transmission lines. The interface 108 can include at least a built-in network adapter, network interface card, PCMCIA network card, EXPRESSCARD network card, card bus network adapter, wireless network adapter, USB network adapter, modem, or any other device suitable for interfacing one or more devices within the system 100 to any type of network capable of communication. The interface 108 can establish a connection with one or more aforementioned components to receive or transmit information, such as with other light fixtures 104 or devices (e.g., computing device 101) within the network 102. The interface 108 can establish a connection with the computing device 101 directly or communicate with the computing device 101 indirectly via an intermediary device (e.g., gateway device).
In some configurations, the interface 108 can transmit data to the lighting application 106 of the computing device 101 via the network 102. For example, the interface 108 can send information related to the lighting fixture 104 (e.g., the light module 110 or the light source 112), such as settings or configurations of the light fixture 104 for presentation via the GUI of the computing device 101. The setting or configuration may include configurable brightness, color, or effects, among others. In some cases, the light fixture 104 may include one or more sensors, such as at least one positioning sensor (e.g., global positioning sensor (GPS)), temperature sensor, angular position sensor, or electricity meter (or sensor). In this case, the interface 108 may send sensor data to the lighting application 106 for presentation via the GUI of the computing device 101.
The light module 110 can be a housing or a component to contain the light source 112. The light module 110 can be composed of any suitable material, not limited to plastic, wood, acrylic, metal, or glass. The light module 110 can be structured or formed into any non-limiting shape or form. The light source 112 can include or correspond to a device configured to generate illumination when supplied with sufficient electrical power (e.g., 2 watts (W), 5 W, 50 W, 100 W, and so on). The light module 110 can be positioned throughout the light fixture 104.
The light module 110 can be a part or an extension of the light fixture 104. The light module 110 may be fixed to the light fixture 104. In some cases, the light module 110 can be an independent component, capable of coupling to the light fixture 104. For example, the light module 110 can be coupled to or decoupled from the light fixture 104 using at least one suitable coupling mechanism, such as a snap connector, latch coupling, clamp, friction fitting, magnetic coupling, etc.
The light source 112 may be a part of the light module 110, e.g., fixed to the light module 110. In some cases, the light source 112 may be an independent component, capable of coupling to the light module 110. For instance, the light source 112 may be coupled to or decoupled from the light module 110 using at least one suitable coupling mechanism. The light source 112 (or the light fixture 104) can be positioned or angled to direct light toward the surface of at least one of the wall or the ceiling.
In some cases, the light fixture 104 can include at least one memory (e.g., memory device) configured to store data, information, or configurations local to the light fixture 104. The memory can be, for instance, a random access memory (RAM) or other dynamic storage device. For example, the memory can include, store, or maintain the embedded code of the light fixture 104. The memory can store the settings of the light fixture 104, such as on/off state, capabilities (e.g., configurable color or brightness), on or off timer, lighting effects, protocol used for communication, driver information, or other related operating information.
In some cases, the light fixture 104 can include or be coupled to a backup battery (or a backup battery system) internal or external from the light fixture 104. In certain scenarios, the light fixture 104 can switch to the backup battery to enable electric power to be supplied from the backup battery to the light source 112 responsive to detecting, via a sensor, an insufficient amount of power received from a power source (e.g., from an external power source). The backup battery can be coupled to or decoupled from the light fixture 104 via any suitable coupling mechanism. In various configurations, the light fixture 104 can be interconnected with at least one other light fixture. In this case, the light fixtures 104 can communicate with each other via the network 102.
Referring to
The cove structure 208 may be referred to as a cove construction or a cove component of the cove lighting structure 200. The cove structure 208 can be composed of at least one type of suitable material, such as metal, wood, plastic, etc. The cove structure 208 may be fabricated into a relatively small form factor for manufacturing purposes, for example. The cove structure 208 can be a foundation for the installation of the light fixture 104 (e.g., including light module 110). For instance, the cove structure 208 can include or be coupled to the platform 206 for coupling, placing, or positioning the light fixture 104.
The return air structure 202 can include one or more return air vents 204 (e.g., sometimes referred to as return air openings, slots, or entries). For instance, the return air structure 202 can include one or more slots corresponding to or forming the one or more return air vents 204. The return air vents 204 can be configured to receive air (e.g., return air 210) for supplying or directing to an air condition system, heating system, or other ventilation systems (e.g., heating, ventilation, and air conditioning (HVAC) system). The return air 210 can include or correspond to air that returns to the HVAC system, for instance, from the area being cooled or heated. One or more of the return air vents 204 can include similar or different dimensions compared to one or more other return air vents 204, such as similar or different width (e.g., D4), height (e.g., D3), or depth. The return air vents 204 may be separated from each other by a predefined width (e.g., D2). The return air vents 204 proximate to the edge of the return air structure 202 can be separated or distal from the edge by a predefined distance (e.g., D1).
In some cases, the return air structure 202 (or the return air vents 204) can be a part of the cove structure 208. For example, slotted provisions (e.g., vents) for handling the return air can be formed or structured into the cove structure 208. The return air 210 can serve or provide an essential function to any (interior) space of a build. It may be desirable to hide the return air structure 202 (e.g., sometimes referred to as a return air system) from visibility, such as to maintain or provide a particular type of interior design for the building. The return air vents 204 can be positioned below the sight line (e.g., thereby not being visible to an occupant of the space). As shown in
In some configurations, the cove lighting structure 200 can include multiple return air structures 202, such as shown in conjunction with at least
The cove structure 208 can include or be formed from an extrusion 212. The extrusion 212 (e.g., sometimes referred to as an extension) can be composed of at least one suitable material, such as metal, plastic, wood, etc. For example, the cove structure 208 can be extended laterally from the return air structure 202, thereby creating a distance from the edge of the cove structure 208 to the return air structure 202. The distance of the extrusion 212 (or extension) for the cove structure 208 may be configurable. In some cases, the length (e.g., D5) of the extrusion 212 can be predefined according to manufacturing specifications. In some cases, the cove structure 208 can provide a vertical extension (e.g., as part of the extrusion 212) to block or hide the return air vents 204 from visibility by the occupant of the space.
For example, the extrusion 212 of the cove structure 208 can include a predefined vertical height (e.g., D6) suitable to prevent visibility of the return air vents 204 at various viewing angles. In some cases, the extrusion 212 may include a predefined vertical height suitable to hide the visibility of the light fixture 104. In another example, the extrusion 212 may be structured with one or more dimensions suitable to hide the visibility of at least a portion of the return air vent(s) 204 or the light fixture(s) 104.
In some configurations, the cove structure 208 may include at least one alignment pin 216 as part of the extrusion 212, among other parts of the cove structure 208. The alignment pin 216 can be positioned on or at the sides of the cove structure 208, as shown in conjunction with
The cove lighting structure 200 can include or be installed with the light fixture 104. In some cases, the light fixture 104 can be a separate component for installation to the cove lighting structure 200. In some other cases, the light fixture 104 can be embedded as part of the cove lighting structure 200. Using the technology in optical systems or solid state lighting, among other types of lighting technologies, for example, the light fixture 104 can be install relatively close to the ceiling of the interior space (e.g., relatively near the ceiling cove 218, such as shown in conjunction with
The light fixture 104 can be positioned on, above, or at the platform 206 of the cove lighting structure 200. The light fixture 104 can be positioned between the cove structure 208 and the return air structure 202 (or the return air vents 204). In some cases, the light fixture 104 (or the light source 112) can be separated from the return air vent(s) 204 or the return air structure 202 by a predetermined/predefined distance (e.g., D9), for instance, to allow for a desired gap or path to the return air vent(s) 204. The positioning of the light fixture 104 proximate to the return air vent(s) 204 of the return air structure 202 can allow for the dissipation of heat from the light source 112 via the return air vent(s) 204, for example. The light fixture 104 may be positioned at a predefined distance from the cove structure 208 or positioned next to the cove structure 208. As shown in conjunction with at least
In some cases, the return air structure 202 can include a height that is less than the height of the light fixture 104. In some other configurations, the return air structure 202 can include a height that is similar to or greater than the height of the light fixture 104, not limited to a height that is less than the height of the light fixture 104, for example.
The cove lighting structure 200 can be positioned relative to, near, or at a cove structure (e.g., cove portion). For example, the cove lighting structure 200 can be positioned proximate to a ceiling cove 218. The ceiling cove 218 may be formed at a ceiling formation 220. For instance, the ceiling formation 220 may refer to a portion of the wall or the ceiling where the ceiling cove 218, in this case, is formed with a tapered edge, such as shown in conjunction with
In some cases, a portion of the cove lighting structure 200 (e.g., the platform 206) may be extended (or can include an extension extending) under the return air vent 204, such as shown in conjunction with
In various configurations, the cove lighting structure 200 (or one or more components of the cove lighting structure 200) can be aligned with the surface or the curvature of the wall or the ceiling. For example, the cove lighting structure 200 (e.g., the cove structure 208, extrusion 212, light fixture 104, or platform 206) can be linear or straight, e.g., to align with a flat wall or a flat ceiling. In another example, the cove lighting structure 200 (e.g., the cove structure 208, extrusion 212, light fixture 104, or platform 206) can include curvature, be curved, or in some cases, be circular or at least partially have a circular shape, such as an oval or ellipse. For instance, the curvature of the cove lighting structure 200 may align with a curved wall or a curved ceiling. In such cases, the return air structure 202 or the return air vent 204 may be located or configured at the posterior, rear, or back position of the curvature of the cove lighting structure 200, for example. The cove lighting structure 200 may include other alignment features, for example, in addition, or alternative to those discussed herein.
The computer system 500 may be coupled via the bus 505 to a display 535, such as a liquid crystal display, or active matrix display, for displaying information to a user such as an administrator of the data processing system or the utility grid. An input device 530, such as a keyboard or voice interface may be coupled to the bus 505 for communicating information and commands to the processor 510. The input device 530 can include a touch screen display 535. The input device 530 can also include a cursor control, such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor 510 and for controlling cursor movement on the display 535. The display 535 can be part of the computing device 101, or other components of
The processes, systems and methods described herein can be implemented by the computer system 500 in response to the processor 510 executing an arrangement of instructions contained in main memory 515. Such instructions can be read into main memory 515 from another computer-readable medium, such as the storage device 525. Execution of the arrangement of instructions contained in main memory 515 causes the computer system 500 to perform the illustrative processes described herein. One or more processors in a multi-processing arrangement may also be employed to execute the instructions contained in main memory 515. Hard-wired circuitry can be used in place of or in combination with software instructions together with the systems and methods described herein. Systems and methods described herein are not limited to any specific combination of hardware circuitry and software.
The following examples pertain to further embodiments, from which numerous permutations and configurations will be apparent.
Example 1 includes a cove lighting structure, comprising: a return air structure comprising a vent configured to receive return air; a cove structure connected with a platform extended laterally from the return air structure; and a light fixture comprising a light source configured to provide cove lighting, wherein the light fixture is positioned above the platform and between the cove structure and the return air structure.
Example 2 includes the subject matter of Example 1, wherein the vent of the return air structure directs the return air towards a heating, ventilation, or air condition system.
Example 3 includes the subject matter of any one of Examples 1 and 2, wherein the return air structure is positioned to dissipate heat from the light source.
Example 4 includes the subject matter of any one of Examples 1 through 3, wherein the return air structure comprises a plurality of slots to form a plurality of vents.
Example 5 includes the subject matter of any one of Examples 1 through 4, wherein the return air structure comprises a height that is less than a height of the light fixture.
Example 6 includes the subject matter of any one of Examples 1 through 5, comprising: a second return air structure separated from the return air structure by a predetermined distance.
Example 7 includes the subject matter of any one of Examples 1 through 6, wherein the cove structure is mechanically connected to a ceiling.
Example 8 includes the subject matter of any one of Examples 1 through 7, wherein the cove structure is formed from an extrusion of one or more metals.
Example 9 includes the subject matter of any one of Examples 1 through 8, wherein the light source is positioned to direct light towards a surface of at least one of a ceiling or a wall.
Example 10 includes the subject matter of any one of Examples 1 through 9, wherein the light fixture comprises an optical window that directs light at least 180 degrees.
Example 11 includes the subject matter of any one of Examples 1 through 10, wherein the light source is electrically connected to a backup battery system.
Example 12 includes the subject matter of any one of Examples 1 through 11, wherein the light source is closer to a wall of the cove structure relative to the return air structure, and the light source is separated from the return air structure by a predetermined distance.
Example 13 includes an apparatus, comprising: a return air structure comprising a vent configured to receive return air; a cove structure connected with a platform extended laterally from the return air structure; and a light fixture comprising a light source configured to provide cove lighting, wherein the light fixture is positioned above the platform and between the cove structure and the return air structure.
Example 14 includes the subject matter of Example 13, wherein the return air structure comprises a plurality of slots to form a plurality of vents.
Example 15 includes the subject matter of any one of Examples 13 and 14, comprising a second return air structure separated from the return air structure by a predetermined distance.
Example 16 includes the subject matter of any one of Examples 13 through 15, wherein the cove structure is formed from an extrusion of one or more metals.
Example 17 includes the subject matter of any one of Examples 13 through 16, wherein the light fixture comprises an optical window that directs light at least 180 degrees.
Example 18 includes a method, comprising: providing a cove lighting structure, the cove lighting structure comprising: a return air structure comprising a vent configured to receive return air; a cove structure connected with a platform extended laterally from the return air structure; and a light fixture comprising a light source configured to provide cove lighting, wherein the light fixture is positioned above the platform and between the cove structure and the return air structure.
Example 19 includes the subject matter of Example 18, comprising: mechanically connecting the return air structure to direct the return air towards a heating, ventilation, or air condition system.
Example 20 includes the subject matter of any one of Examples 18 and 19, comprising: coupling the cove lighting structure to a ceiling or a wall.
Although an example system has been described in
Some of the descriptions herein emphasize the structural independence of the aspects of the system components (e.g., arbitration component) and illustrate one grouping of operations and responsibilities of these system components. Other groupings that execute similar overall operations are understood to be within the scope of the present application. Modules can be implemented in hardware or as computer instructions on a non-transient computer-readable storage medium, and modules can be distributed across various hardware- or computer-based components.
The systems described above can provide multiple ones of any or each of those components and these components can be provided on either a standalone system or on multiple instantiation in a distributed system. In addition, the systems and methods described above can be provided as one or more computer-readable programs or executable instructions embodied on or in one or more articles of manufacture. The article of manufacture can be cloud storage, a hard disk, a CD-ROM, a flash memory card, a PROM, a RAM, a ROM, or a magnetic tape. In general, the computer-readable programs can be implemented in any programming language, such as LISP, PERL, C, C++, C#, PROLOG, or in any byte code language such as JAVA. The software programs or executable instructions can be stored on or in one or more articles of manufacture as object code.
Example and non-limiting module implementation elements include sensors providing any value determined herein, sensors providing any value that is a precursor to a value determined herein, datalink or network hardware including communication chips, oscillating crystals, communication links, cables, twisted pair wiring, coaxial wiring, shielded wiring, transmitters, receivers, or transceivers, logic circuits, hard-wired logic circuits, reconfigurable logic circuits in a particular non-transient state configured according to the module specification, any actuator including at least an electrical, hydraulic, or pneumatic actuator, a solenoid, an op-amp, analog control elements (springs, filters, integrators, adders, dividers, gain elements), or digital control elements.
The subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. The subject matter described in this specification can be implemented as one or more computer programs, e.g., one or more circuits of computer program instructions, encoded on one or more computer storage media for execution by, or to control the operation of, data processing apparatuses. Alternatively or in addition, the program instructions can be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. A computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. While a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially generated propagated signal. The computer storage medium can also be, or be included in, one or more separate components or media (e.g., multiple CDs, disks, or other storage devices include cloud storage). The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.
The terms “computing device”, “component” or “data processing apparatus” or the like encompass various apparatuses, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations of the foregoing. The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.
A computer program (also known as a program, software, software application, app, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program can correspond to a file in a file system. A computer program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatuses can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). Devices suitable for storing computer program instructions and data can include non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
The subject matter described herein can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described in this specification, or a combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
While operations are depicted in the drawings in a particular order, such operations are not required to be performed in the particular order shown or in sequential order, and all illustrated operations are not required to be performed. Actions described herein can be performed in a different order.
Having now described some illustrative implementations, it is apparent that the foregoing is illustrative and not limiting, having been presented by way of example. In particular, although many of the examples presented herein involve specific combinations of method acts or system elements, those acts and those elements may be combined in other ways to accomplish the same objectives. Acts, elements and features discussed in connection with one implementation are not intended to be excluded from a similar role in other implementations or implementations.
The phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including” “comprising” “having” “containing” “involving” “characterized by” “characterized in that” and variations thereof herein, is meant to encompass the items listed thereafter, equivalents thereof, and additional items, as well as alternate implementations consisting of the items listed thereafter exclusively. In one implementation, the systems and methods described herein consist of one, each combination of more than one, or all of the described elements, acts, or components.
Any references to implementations or elements or acts of the systems and methods herein referred to in the singular may also embrace implementations including a plurality of these elements, and any references in plural to any implementation or element or act herein may also embrace implementations including only a single element. References in the singular or plural form are not intended to limit the presently disclosed systems or methods, their components, acts, or elements to single or plural configurations. References to any act or element being based on any information, act or element may include implementations where the act or element is based at least in part on any information, act, or element.
Any implementation disclosed herein may be combined with any other implementation or embodiment, and references to “an implementation,” “some implementations,” “one implementation” or the like are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in connection with the implementation may be included in at least one implementation or embodiment. Such terms as used herein are not necessarily all referring to the same implementation. Any implementation may be combined with any other implementation, inclusively or exclusively, in any manner consistent with the aspects and implementations disclosed herein.
References to “or” may be construed as inclusive so that any terms described using “or” may indicate any of a single, more than one, and all of the described terms. For example, a reference to “at least one of ‘A’ and ‘B’” can include only ‘A’, only ‘B’, as well as both ‘A’ and ‘B’. Such references used in conjunction with “comprising” or other open terminology can include additional items.
Where technical features in the drawings, detailed description or any claim are followed by reference signs, the reference signs have been included to increase the intelligibility of the drawings, detailed description, and claims. Accordingly, neither the reference signs nor their absence have any limiting effect on the scope of any claim elements.
Modifications of described elements and acts such as variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations can occur without materially departing from the teachings and advantages of the subject matter disclosed herein. For example, elements shown as integrally formed can be constructed of multiple parts or elements, the position of elements can be reversed or otherwise varied, and the nature or number of discrete elements or positions can be altered or varied. Other substitutions, modifications, changes and omissions can also be made in the design, operating conditions and arrangement of the disclosed elements and operations without departing from the scope of the present disclosure.
The systems and methods described herein may be embodied in other specific forms without departing from the characteristics thereof. Scope of the systems and methods described herein is thus indicated by the appended claims, rather than the foregoing description, and changes that come within the meaning and range of equivalency of the claims are embraced therein.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any inventions or of what can be claimed, but rather as descriptions of features specific to particular embodiments of particular aspects. Certain features described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features can be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination can be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing can be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated in a single software product or packaged into multiple software products.
Thus, particular embodiments of the subject matter have been described. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results.
This application claims the benefit of and priority, under 35 U.S.C. § 119, to U.S. Provisional Application No. 63/446,205, filed Feb. 16, 2023, titled “COVE LIGHT FIXTURE WITH HIDDEN INTEGRATED AIR RETURN,” which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
2810823 | Guth, Jr. | Feb 1971 | A |
3560729 | Liberman | Feb 1971 | A |
3796870 | Pettyjohn, Jr. | Mar 1974 | A |
4139770 | Beyersdorf | Feb 1979 | A |
5264997 | Hutchisson et al. | Nov 1993 | A |
5465199 | Bray et al. | Nov 1995 | A |
5561346 | Byrne | Oct 1996 | A |
5783909 | Hochstein | Jul 1998 | A |
5909429 | Satyanarayana et al. | Jun 1999 | A |
5947587 | Keuper et al. | Sep 1999 | A |
6013988 | Bucks et al. | Jan 2000 | A |
6016038 | Mueller et al. | Jan 2000 | A |
6040663 | Bucks et al. | Mar 2000 | A |
6094014 | Bucks et al. | Jul 2000 | A |
6127783 | Pashley et al. | Oct 2000 | A |
6147458 | Bucks et al. | Nov 2000 | A |
6150774 | Mueller et al. | Nov 2000 | A |
6157093 | Giannopoulos et al. | Dec 2000 | A |
6166496 | Lys et al. | Dec 2000 | A |
6194839 | Chang | Feb 2001 | B1 |
6201353 | Chang et al. | Mar 2001 | B1 |
6211626 | Lys et al. | Apr 2001 | B1 |
6234645 | Borner et al. | May 2001 | B1 |
6234648 | Borner et al. | May 2001 | B1 |
6236331 | Dussureault | May 2001 | B1 |
6238065 | Jones | May 2001 | B1 |
6249088 | Chang | Jun 2001 | B1 |
6250774 | Begemann et al. | Jun 2001 | B1 |
6253530 | Price et al. | Jul 2001 | B1 |
6288497 | Chang et al. | Sep 2001 | B1 |
6292901 | Lys et al. | Sep 2001 | B1 |
6299329 | Mui et al. | Oct 2001 | B1 |
6304464 | Jacobs et al. | Oct 2001 | B1 |
6305818 | Lebens et al. | Oct 2001 | B1 |
6340864 | Wacyk | Jan 2002 | B1 |
6340868 | Lys et al. | Jan 2002 | B1 |
6384545 | Lau | May 2002 | B1 |
6411046 | Muthu | Jun 2002 | B1 |
6441558 | Muthu et al. | Aug 2002 | B1 |
6443592 | Unger et al. | Sep 2002 | B1 |
6445139 | Marshall et al. | Sep 2002 | B1 |
6459919 | Lys et al. | Oct 2002 | B1 |
6489731 | Bruning et al. | Dec 2002 | B1 |
6495964 | Muthu et al. | Dec 2002 | B1 |
6507158 | Wang | Jan 2003 | B1 |
6507159 | Muthu | Jan 2003 | B2 |
6510995 | Muthu et al. | Jan 2003 | B2 |
6513949 | Marshall et al. | Feb 2003 | B1 |
6528954 | Lys et al. | Mar 2003 | B1 |
6552495 | Chang | Apr 2003 | B1 |
6576881 | Muthu et al. | Jun 2003 | B2 |
6577080 | Lys et al. | Jun 2003 | B2 |
6577512 | Tripathi et al. | Jun 2003 | B2 |
6580309 | Jacobs et al. | Jun 2003 | B2 |
6586890 | Min et al. | Jul 2003 | B2 |
6596977 | Muthu et al. | Jul 2003 | B2 |
6608453 | Morgan et al. | Aug 2003 | B2 |
6609813 | Showers et al. | Aug 2003 | B1 |
6617795 | Bruning | Sep 2003 | B2 |
6621235 | Chang | Sep 2003 | B2 |
6630801 | Schuurmans | Oct 2003 | B2 |
6636003 | Rahm et al. | Oct 2003 | B2 |
6639368 | Sheoghong | Oct 2003 | B2 |
6676284 | Wynne Willson | Jan 2004 | B1 |
6692136 | Marshall et al. | Feb 2004 | B2 |
6720745 | Lys et al. | Apr 2004 | B2 |
6724159 | Gutta et al. | Apr 2004 | B2 |
6734639 | Chang et al. | May 2004 | B2 |
6741351 | Marshall et al. | May 2004 | B2 |
6762562 | Leong | Jul 2004 | B2 |
6777891 | Lys et al. | Aug 2004 | B2 |
6788011 | Mueller et al. | Sep 2004 | B2 |
6796680 | Showers et al. | Sep 2004 | B1 |
6796686 | Jacob et al. | Sep 2004 | B2 |
6801003 | Schanberger et al. | Oct 2004 | B2 |
6806659 | Mueller et al. | Oct 2004 | B1 |
6831569 | Wang et al. | Dec 2004 | B2 |
6853150 | Clauberg et al. | Feb 2005 | B2 |
6853151 | Leong et al. | Feb 2005 | B2 |
6859644 | Wang | Feb 2005 | B2 |
6922022 | Bucks et al. | Jul 2005 | B2 |
6930452 | De Krijger et al. | Aug 2005 | B2 |
6932477 | Stanton | Aug 2005 | B2 |
6933685 | Gutta et al. | Aug 2005 | B2 |
6933767 | Bucks et al. | Aug 2005 | B2 |
6965205 | Piepgras et al. | Nov 2005 | B2 |
6969954 | Lys | Nov 2005 | B2 |
6972525 | Bucks et al. | Dec 2005 | B2 |
6975079 | Lys et al. | Dec 2005 | B2 |
6992803 | Chang | Jan 2006 | B2 |
6998594 | Gaines et al. | Feb 2006 | B2 |
7014336 | Ducharme et al. | Mar 2006 | B1 |
7030572 | Nijhof et al. | Apr 2006 | B2 |
7031920 | Dowling et al. | Apr 2006 | B2 |
7038398 | Lys et al. | May 2006 | B1 |
7038399 | Lys et al. | May 2006 | B2 |
7064498 | Dowling et al. | Jun 2006 | B2 |
7067992 | Leong et al. | Jun 2006 | B2 |
7071762 | Xu et al. | Jul 2006 | B2 |
7113541 | Lys et al. | Sep 2006 | B1 |
7118248 | Wynne Willson | Oct 2006 | B2 |
7132804 | Lys et al. | Nov 2006 | B2 |
7135824 | Lys et al. | Nov 2006 | B2 |
7139617 | Morgan et al. | Nov 2006 | B1 |
7140752 | Ashdown | Nov 2006 | B2 |
7161311 | Mueller et al. | Jan 2007 | B2 |
7161313 | Piepgras et al. | Jan 2007 | B2 |
7161556 | Morgan et al. | Jan 2007 | B2 |
7178941 | Roberge et al. | Feb 2007 | B2 |
7180252 | Lys et al. | Feb 2007 | B2 |
7186003 | Dowling et al. | Mar 2007 | B2 |
7202608 | Robinson et al. | Apr 2007 | B2 |
7202613 | Morgan et al. | Apr 2007 | B2 |
7202641 | Claessens et al. | Apr 2007 | B2 |
7204622 | Dowling et al. | Apr 2007 | B2 |
7221104 | Lys et al. | May 2007 | B2 |
7228190 | Dowling et al. | Jun 2007 | B2 |
7231060 | Dowling et al. | Jun 2007 | B2 |
7233115 | Lys | Jun 2007 | B2 |
7233831 | Blackwell | Jun 2007 | B2 |
7242152 | Dowling et al. | Jul 2007 | B2 |
7253566 | Lys et al. | Aug 2007 | B2 |
7255457 | Ducharme et al. | Aug 2007 | B2 |
7255458 | Ashdown | Aug 2007 | B2 |
7256554 | Lys | Aug 2007 | B2 |
7262559 | Tripathi et al. | Aug 2007 | B2 |
7267461 | Kan et al. | Sep 2007 | B2 |
7274160 | Mueller et al. | Sep 2007 | B2 |
7300192 | Mueller et al. | Nov 2007 | B2 |
7308296 | Lys et al. | Dec 2007 | B2 |
7309965 | Dowling et al. | Dec 2007 | B2 |
7314289 | Montagne | Jan 2008 | B2 |
7319298 | Jungwirth et al. | Jan 2008 | B2 |
7323676 | Duijve | Jan 2008 | B2 |
7329998 | Jungwirth | Feb 2008 | B2 |
7350936 | Ducharme et al. | Apr 2008 | B2 |
7352138 | Lys et al. | Apr 2008 | B2 |
7352339 | Morgan et al. | Apr 2008 | B2 |
7353071 | Blackwell et al. | Apr 2008 | B2 |
7354172 | Chemel et al. | Apr 2008 | B2 |
7358679 | Lys et al. | Apr 2008 | B2 |
7358681 | Robinson et al. | Apr 2008 | B2 |
7358706 | Lys | Apr 2008 | B2 |
7358929 | Mueller et al. | Apr 2008 | B2 |
7358961 | Zwanenburg | Apr 2008 | B2 |
7387405 | Ducharme et al. | Jun 2008 | B2 |
7388665 | Ashdown | Jun 2008 | B2 |
7394210 | Ashdown | Jul 2008 | B2 |
7420335 | Robinson et al. | Sep 2008 | B2 |
7423387 | Robinson et al. | Sep 2008 | B2 |
7432668 | Zwanenburg et al. | Oct 2008 | B2 |
7443209 | Chang | Oct 2008 | B2 |
7449847 | Schanberger et al. | Nov 2008 | B2 |
7453217 | Lys et al. | Nov 2008 | B2 |
7459864 | Lys | Dec 2008 | B2 |
7462997 | Mueller et al. | Dec 2008 | B2 |
7463070 | Wessels | Dec 2008 | B2 |
7482565 | Morgan et al. | Jan 2009 | B2 |
7482760 | Jungwirth et al. | Jan 2009 | B2 |
7490953 | Holten et al. | Feb 2009 | B2 |
7490957 | Leong et al. | Feb 2009 | B2 |
7495671 | Chemel et al. | Feb 2009 | B2 |
7502034 | Chemel et al. | Mar 2009 | B2 |
7505395 | Ashdown et al. | Mar 2009 | B2 |
7507001 | Kit | Mar 2009 | B2 |
7511436 | Xu | Mar 2009 | B2 |
7511437 | Lys et al. | Mar 2009 | B2 |
7515128 | Dowling | Apr 2009 | B2 |
7520634 | Ducharme et al. | Apr 2009 | B2 |
7521872 | Bruning | Apr 2009 | B2 |
7538499 | Ashdown | May 2009 | B2 |
7542257 | McCormick et al. | Jun 2009 | B2 |
7550931 | Lys et al. | Jun 2009 | B2 |
7550935 | Lys et al. | Jun 2009 | B2 |
7557521 | Lys | Jul 2009 | B2 |
7569807 | Matheson | Aug 2009 | B2 |
7572028 | Mueller et al. | Aug 2009 | B2 |
7573209 | Ashdown et al. | Aug 2009 | B2 |
7573210 | Ashdown et al. | Aug 2009 | B2 |
7573729 | Elferich et al. | Aug 2009 | B2 |
7598681 | Lys et al. | Oct 2009 | B2 |
7598684 | Lys et al. | Oct 2009 | B2 |
7598686 | Lys et al. | Oct 2009 | B2 |
7619370 | Chemel et al. | Nov 2009 | B2 |
7652236 | Cortenraad et al. | Jan 2010 | B2 |
7654703 | Kan et al. | Feb 2010 | B2 |
7656366 | Ashdown | Feb 2010 | B2 |
7658506 | Dowling | Feb 2010 | B2 |
7659673 | Lys | Feb 2010 | B2 |
7659674 | Mueller et al. | Feb 2010 | B2 |
7665883 | Matheson | Feb 2010 | B2 |
7667409 | Geerts et al. | Feb 2010 | B2 |
7675238 | Cortenraad et al. | Mar 2010 | B2 |
7687753 | Ashdown | Mar 2010 | B2 |
7688002 | Ashdown et al. | Mar 2010 | B2 |
7689130 | Ashdown | Mar 2010 | B2 |
7703951 | Piepgras et al. | Apr 2010 | B2 |
7710369 | Dowling | May 2010 | B2 |
7712926 | Matheson | May 2010 | B2 |
7714521 | Qian | May 2010 | B2 |
7731387 | Cortenraad et al. | Jun 2010 | B2 |
7731389 | Draganov et al. | Jun 2010 | B2 |
7731390 | Van Gorkom et al. | Jun 2010 | B2 |
7737643 | Lys | Jun 2010 | B2 |
7738002 | Ashdown et al. | Jun 2010 | B2 |
7740375 | Zou et al. | Jun 2010 | B2 |
7766489 | Duine et al. | Aug 2010 | B2 |
7766518 | Piepgras et al. | Aug 2010 | B2 |
7772787 | Ashdown et al. | Aug 2010 | B2 |
7777427 | Stalker, III | Aug 2010 | B2 |
7781979 | Lys | Aug 2010 | B2 |
7802902 | Moss et al. | Sep 2010 | B2 |
7806558 | Williamson | Oct 2010 | B2 |
7808191 | Wu | Oct 2010 | B2 |
7809448 | Lys et al. | Oct 2010 | B2 |
7810974 | Van Rijswick et al. | Oct 2010 | B2 |
7845823 | Mueller et al. | Dec 2010 | B2 |
7850347 | Speier et al. | Dec 2010 | B2 |
7854539 | Van Duijneveldt | Dec 2010 | B2 |
7868562 | Salsbury et al. | Jan 2011 | B2 |
7878683 | Logan et al. | Feb 2011 | B2 |
7878688 | Paulussen et al. | Feb 2011 | B2 |
7893631 | Speier | Feb 2011 | B2 |
7893661 | Ackermann et al. | Feb 2011 | B2 |
7894050 | Ashdown et al. | Feb 2011 | B2 |
7906917 | Tripathi et al. | Mar 2011 | B2 |
7911151 | Xu | Mar 2011 | B2 |
7914173 | Paulussen et al. | Mar 2011 | B2 |
8022632 | Schulz et al. | Sep 2011 | B2 |
8026673 | Lys | Sep 2011 | B2 |
20020074559 | Dowling et al. | Jun 2002 | A1 |
20030132721 | Jacobs et al. | Jul 2003 | A1 |
20030133292 | Mueller et al. | Jul 2003 | A1 |
20040052076 | Mueller et al. | Mar 2004 | A1 |
20040090191 | Mueller et al. | May 2004 | A1 |
20040178751 | Mueller et al. | Sep 2004 | A1 |
20050236998 | Mueller et al. | Oct 2005 | A1 |
20050275626 | Mueller et al. | Dec 2005 | A1 |
20060002110 | Dowling et al. | Jan 2006 | A1 |
20060076908 | Morgan et al. | Apr 2006 | A1 |
20060104066 | Cini | May 2006 | A1 |
20060114201 | Chang | Jun 2006 | A1 |
20060152172 | Mueller et al. | Jul 2006 | A9 |
20060221606 | Dowling | Oct 2006 | A1 |
20060262521 | Piepgras et al. | Nov 2006 | A1 |
20060274526 | Weston et al. | Dec 2006 | A1 |
20060290624 | Ashdown | Dec 2006 | A1 |
20070063658 | Van Der Veeken | Mar 2007 | A1 |
20070086912 | Dowling et al. | Apr 2007 | A1 |
20070115658 | Mueller et al. | May 2007 | A1 |
20070145915 | Roberge et al. | Jun 2007 | A1 |
20070153514 | Dowling et al. | Jul 2007 | A1 |
20070230159 | Cortenraad et al. | Oct 2007 | A1 |
20070258240 | Ducharme et al. | Nov 2007 | A1 |
20070273290 | Ashdown et al. | Nov 2007 | A1 |
20080042599 | Ashdown | Feb 2008 | A1 |
20080043464 | Ashdown | Feb 2008 | A1 |
20080048582 | Robinson | Feb 2008 | A1 |
20080062413 | Ashdown et al. | Mar 2008 | A1 |
20080089060 | Kondo et al. | Apr 2008 | A1 |
20080094005 | Rabiner et al. | Apr 2008 | A1 |
20080122386 | De Brouwer et al. | May 2008 | A1 |
20080136331 | Schmeikal | Jun 2008 | A1 |
20080136796 | Dowling | Jun 2008 | A1 |
20080140231 | Blackwell et al. | Jun 2008 | A1 |
20080164826 | Lys | Jul 2008 | A1 |
20080164854 | Lys | Jul 2008 | A1 |
20080167734 | Robinson et al. | Jul 2008 | A1 |
20080183081 | Lys et al. | Jul 2008 | A1 |
20080239675 | Speier | Oct 2008 | A1 |
20080265797 | Van Doorn | Oct 2008 | A1 |
20080278092 | Lys et al. | Nov 2008 | A1 |
20080278941 | Logan et al. | Nov 2008 | A1 |
20080285271 | Roberge | Nov 2008 | A1 |
20080290251 | Deurenberg et al. | Nov 2008 | A1 |
20080297066 | Meijer et al. | Dec 2008 | A1 |
20080298330 | Leitch | Dec 2008 | A1 |
20080315798 | Diederiks et al. | Dec 2008 | A1 |
20090002981 | Knibbe | Jan 2009 | A1 |
20090021175 | Wendt et al. | Jan 2009 | A1 |
20090021182 | Sauerlaender | Jan 2009 | A1 |
20090072761 | Wessels | Mar 2009 | A1 |
20090128059 | Joosen et al. | May 2009 | A1 |
20090134817 | Jurngwirth et al. | May 2009 | A1 |
20090160364 | Ackermann et al. | Jun 2009 | A1 |
20090168415 | Franciscus Deurenberg et al. | Jul 2009 | A1 |
20090179587 | Van Der Veen et al. | Jul 2009 | A1 |
20090179596 | Willaert et al. | Jul 2009 | A1 |
20090189448 | Verschueren | Jul 2009 | A1 |
20090224695 | Van Erp et al. | Sep 2009 | A1 |
20090230884 | Van Doorn | Sep 2009 | A1 |
20090243507 | Lucero-Vera et al. | Oct 2009 | A1 |
20090278473 | Van Erp | Nov 2009 | A1 |
20090284174 | Sauerlander et al. | Nov 2009 | A1 |
20090321666 | Hilgers | Dec 2009 | A1 |
20100007600 | Deurenberg et al. | Jan 2010 | A1 |
20100026191 | Radermacher et al. | Feb 2010 | A1 |
20100045478 | Schulz et al. | Feb 2010 | A1 |
20100072901 | De Rijck et al. | Mar 2010 | A1 |
20100072902 | Wendt et al. | Mar 2010 | A1 |
20100079085 | Wendt et al. | Apr 2010 | A1 |
20100079091 | Deixler et al. | Apr 2010 | A1 |
20100084995 | Baaijens et al. | Apr 2010 | A1 |
20100091488 | Ijzerman et al. | Apr 2010 | A1 |
20100094439 | Van De Meulenhof et al. | Apr 2010 | A1 |
20100102732 | Peeters et al. | Apr 2010 | A1 |
20100117543 | Van Der Veen et al. | May 2010 | A1 |
20100117656 | Snelten | May 2010 | A1 |
20100118531 | Montagne | May 2010 | A1 |
20100127633 | Geerts et al. | May 2010 | A1 |
20100134041 | Radermacher et al. | Jun 2010 | A1 |
20100134042 | Willaert | Jun 2010 | A1 |
20100148689 | Morgan et al. | Jun 2010 | A1 |
20100164399 | Radermacher et al. | Jul 2010 | A1 |
20100165618 | Vissenberg et al. | Jul 2010 | A1 |
20100171771 | Otte et al. | Jul 2010 | A1 |
20100181936 | Radermacher et al. | Jul 2010 | A1 |
20100188007 | Deppe et al. | Jul 2010 | A1 |
20100194293 | Deurenberg et al. | Aug 2010 | A1 |
20100231133 | Lys | Sep 2010 | A1 |
20100231363 | Knibbe | Sep 2010 | A1 |
20100244707 | Gaines et al. | Sep 2010 | A1 |
20100244734 | Van Herpen et al. | Sep 2010 | A1 |
20100259182 | Man et al. | Oct 2010 | A1 |
20100264834 | Gaines et al. | Oct 2010 | A1 |
20100271843 | Holten et al. | Oct 2010 | A1 |
20100289532 | Wendt et al. | Nov 2010 | A1 |
20100301780 | Vinkenvleugel | Dec 2010 | A1 |
20100308745 | Delnoij | Dec 2010 | A1 |
20110025205 | Van Rijswick et al. | Feb 2011 | A1 |
20110025230 | Schulz et al. | Feb 2011 | A1 |
20110035404 | Morgan et al. | Feb 2011 | A1 |
20110042554 | Hilgers et al. | Feb 2011 | A1 |
20110090684 | Logan et al. | Apr 2011 | A1 |
20110095694 | Justel et al. | Apr 2011 | A1 |
20110285292 | Mollnow et al. | Nov 2011 | A1 |
20110291812 | Verbrugh | Dec 2011 | A1 |
20120019670 | Chang et al. | Jan 2012 | A1 |
20170321877 | Polidoro | Nov 2017 | A1 |
Number | Date | Country |
---|---|---|
WO-03017733 | Feb 2003 | WO |
Entry |
---|
Application Note AN-944, “Use Gate Charge to Design the Gate Drive Circuit for Power MOSFETs and IGBTs,” International Rectifier, 2001, 5 pages. |
ATAVRFBKIT/EVLB001 User Guide, “Dimmable Fluorescent Ballast”, ATMEL, 2007, 35 pages. |
Barberis, C., “Precision current sink costs less than $20,” EDN Design Ideas, vol. 43, No. 6, Mar. 13, 1998, 2 pages. |
Bellcomb Technologies Incorporated, “Edges, Joiners, Attachments,” retrieved from http://www.bellcomb.com/caps/edges.htm, Apr. 22, 2007, 3 pages. |
Bookmarks Menu, “Controllers / Wireless,” Dec. 6, 2012, 1 page. |
Bowling, S., “Buck-Boost LED Driver Using the PIC16F785 MCU,” Microchip, 2006, 12 pages. |
By Staff—Consulting-Specifying Engineer, “DALI Delivers Control and Cost Savings, Headaches Too,” Consulting-Specifying Engineer, Jun. 1, 2002, 2 pages. |
Canny, D., “Controlling slew times tames EMI in offline supplies”, EDN Design Ideas, Nov. 14, 2002. |
Control Freak, “Addict Data,” Creative Lighting, 2008, 5 pages. |
Curtis, K., “High Power IR LED Driver Using the PIC16C781/782,” Microchip, 2002, 8 pages. |
CybroTech, “Managing Lights with Dali,” Cybrotech Ltd., 2007, 11 pages. |
Cypress Perform, “Implementing an Integrated DMX512 Receiver,” Cypress Semiconductor Corporation, Dec. 16, 2009, 1 page. |
Cypress Perform, “PowerPSoC (R) Intelligent LED Driver,” Cypress Semiconductor Corporation, Jul. 20, 2009, 52 pages. |
Dali, “Dali at work,” News & Events, Apr. 8, 2010, 1 page. |
Dali, “Dali-Protocol,” Davmark Group, 2007, 6 pages. |
Davidovic et al., “Lead-Acid Battery Charger Becomes A Subfunction In A Microcontroller,” The Authority on Emerging Technologies for Design Solutions, Mar. 29, 2007, 2 pages. |
Di Jasio, L., “A Technique to Increase the Frequency Resolution of PICmicro MCU PWM Modules,” Microchip, 2006, 10 pages. |
Dietz et al., “Very Low-Cost Sensing and Communication Using Bidirectional LEDs,” Mitsubishi Electric Research Laboratories, Jul. 2003, 19 pages. |
Distler, T., “LED Effects Stream TM v2.0 Protocol (Revision C),” Jun. 2, 2005, 5 pages. |
Dunn, J., “Matching MOSFET Drivers to MOSEFTs,” Microchip, 2004, 10 pages. |
Fosler et al., “Digitally Addressable DALI Dimming Ballast,” Microchip, 2002, 18 pages. |
Fosler, R., “The RS-232/DALI Bridge Interface,” Microchip, 2002, 8 pages. |
Fosler, R., “Use a microcontroller to design a boost converter,” EDN design ideas, Mar. 4, 2004, pp. 74-75. |
Ghulyani, L., “Simple MPPT-Based Lead Acid Charger Using bq2031,” Texas Instruments, Dec. 3, 2009, 5 pages. |
Goder, D., “Scheme provides high-side current sensing for white-LED drivers,” EDN design ideas, Feb. 19, 2004, 1 page. |
Google Search Results for, “dali query group,” retrieved from http://www.google.com/search?hl=en&client=firefox-a&rls=org.mozilla:en—on Apr. 8, 2010, 2 pages. |
Hardwick, M., “DC power wire also carries clock or data,” EDN Design Ideas, Mar. 13, 1998, 1 page. |
Hexcel Composites, “Sandwich Panel Fabrication Technology,” retrieved from http://www.hexcel.com/NR/rdonlyres/B4574C2C-0644-43AC-96E2-CC15967A4b)5/4547 SandwichFabrication.pdf, dated Jan. 1997, 16 pages. |
Jackson, S., “Circuit protects bus from 5V swings,” EDN Design Ideas, Nov. 14, 2002, p. 102. |
Klepin, K., “Temperature Compensation for High Brightness LEDs using EZ-Color (TM) and PSoC Express,” Cypress Perform, Aug. 10, 2007, 4 pages. |
Kremin et al., “Multichannel LED Dimmer with CapSense Control—AN13943,” Cypress Perform, Jul. 20, 2007, 5 pages. |
Kropf, B., “Firmware—RGB Color Mixing Firmware for EZ-Color (TM)—AN16035,” Cypress Perform, Jun. 13, 2007, 7 pages. |
Lager, A., “Use a 555 timer as a switch-mode power supply,” EDN Design Ideas, Nov. 14, 2002, 1 page. |
Lee, M., “Shunt Battery Charger Provides 1A Continuous Current,” EDN Design Ideas, Nov. 20, 1997, 2 pages. |
Locher, R., “Introduction to Power MOSEFETs and their Applications,” Fairchild Semiconductor (TM), Oct. 1998, 15 pages. |
Miller, R., “Digital addressable lighting interface protocol fosters systems interoperability for lower costs and greater design flexibility,” RNM Engineering, Inc., Apr. 1, 2003, 20 pages. |
Mixed-Signal Design Guide, “1-Wire Products Deliver a Powerful Combination . . . ,” Dallas Semiconductor Maxim, 2005, 7 pages. |
Nell, S., “VCO uses programmable logic,” EDN Design Ideas, Nov. 14, 2002, 1 page. |
News & Events DALI Digital addressable lighting interface lamp luminaire control, accessed at http://www.dali-ag.org/ on Apr. 8, 2010, original publication date unknown, updated Apr. 8, 2010, 1 pg. |
O'Loughlin, M., “350-W, Two-Phase Interleaved PFC Pre-regulator Design Review,” Texas Instruments, Mar. 2007, 21 pages. |
O'Loughlin, M., “PFC Pre-Regulator Frequency Dithering Circuit,” Texas Instruments, May 2007, 8 pages. |
Operating Manual, “DALI to DMX Dekoder 7064A-H Mk1,” SOUNDLIGHT, 2008, 8 pages. |
OWL2c and conductivity, “Conductivity with the BS2/OWL2,” EME Systems, Berkeley CA U.S.A., 2002, 3 pages. |
Perrin, R., “Inexpensive Relays Form Digital Potentiometer,” EDN Design Ideas, 1998, 2 pages. |
Petersen, A., “Harness solar power with smart power-conversion techniques,” EDN designfeature, Feb. 4, 1999, pp. 119-124. |
Prendergast, P., “How to Design a Three-Channel LED Driver,” Cypress Perform, Jan. 2008, 9 pages. |
R8C/25, “Demonstration Example for DALI Lighting Protocol Stack,” Renasas, Jul. 2008, 14 pages. |
Richardson, C., “LM3404 Driving a Seoul Semi Zpower P4 1A LED—RD-I34,” National Semiconductor, Apr. 2007, 6 pages. |
Richardson, C., “Matching Driver to LED,” National Semiconductor, Jan. 2008, 5 pages. |
Rogers, E., “Understanding Boost Power Stages in Switchmode Power Supplies,” Texas Instruments, Mar. 1999, 32 pages. |
Rogers, E., “Understanding Buck Power Stages in Switchmode Power Supplies,” Texas Instruments, Mar. 1999, 36 pages. |
Seattle Robotics Society, “Implementing Infrared Object Detection,” retrieved from http://web.archive.org/web/20080528042614rejwww.seattlerobotics.org/guide/infrared.html on Apr. 7, 2010, 4 pages. |
Shanmugam, S., “Design of a linear Fresnel lens system for solar photovoltaic electrical power source,” Center for Robotics Research, Oct. 5, 2001, 8 pages. |
Shill, M., “Simple logic probe uses bicolor LED,” EDN Design Ideas, Mar. 13, 1998, 2 pages. |
Software Design Specification, “Z-Wave Protocol Overview,” ZENSYS, May 9, 2007, 20 pages. |
Takahashi A., “Methods and Features of LED Drivers,” Electronic Products, Mar. 2008, 3 pages. |
UPB Universal Powerline Bus, “Universal Powerline Bus Communication Technology Overview,” PCS Powerline Control Systems, Jan. 8, 2002, 13 pages. |
UPB Universal Powerline Bus, “UPB Technology Description,” PCS Powerline Control Systems, Apr. 16, 2007, 68 pages. |
Van Dorsten, A., “A Low Cost Step-up Converter by IC 555,” Circuit Project Electronic, Jul. 21, 2007, 2 pages. |
Walma, K., “DALI: Forerunner of Today's Breakthrough Lighting Technology,” Consulting-Specifying Engineer, Feb. 20, 2007, 2 pages. |
Wikipedia, “Digital Addressable Lighting Interface,” retrieved from http://en.wikipedia.org/wikiJDigital_Addressable_Lighting_Interface accessed on Apr. 8, 2010, 3 pages. |
Witt, J., “Switched-capacitor regulator provides gain,” EDN Design Ideas, Mar. 13, 1998, 2 pages. |
Wojslaw, C., “DPP adds versatility to VFC,” EDN Design Ideas, Nov. 14, 2002, 1 page. |
Young, R., “Power circuit terminates DDR DRAMs,” EDN Design Ideas, Nov. 14, 2002, 1 page. |
Z-Wave Vizia Etc thread, “Aspire Control System Wins Major Design Awards,” retrieved from http://groups.google.com/group/comp.home.automation/browse_thread/thread/449c2c66934dfSfb/fSI12116a8231aa1?Ink=st&q=z-wave&rnum=98#fSI12116a8231aa1, www.ztech.com, dated Sep. 10, 2007, 18 pages. |
Zarr, R., “Driving High-Power LEDs,” Machine Design, Oct. 2007, 3 pages. |
Zensys, “ASCII Interface,” VIZIA RF, 2007, 12 pages. |
ZXCT 1009, “High-Side Current Monitor,” ZETEX, Apr. 2001, 8 pages. |
US Non-Final Office Action on U.S. Appl. No. 18/676,438 dated Aug. 19, 2024 (13 pages). |
US Final Office Action on U.S. Appl. No. 18/676,438 dated Nov. 1, 2024. |
US Notice of Allowance on U.S. Appl. No. 18/676,438 dated Apr. 7, 2025. |
Number | Date | Country | |
---|---|---|---|
20240280255 A1 | Aug 2024 | US |
Number | Date | Country | |
---|---|---|---|
63446205 | Feb 2023 | US |